Definition: Digital Invoicing enables the issuing, transmission and delivery of electronic invoice documents in a structured data format between a public administration and its providers/suppliers. Digital Invoicing ensures data security and privacy, and automatic and electronic processing of invoices.
Source: VISMA
Source reference: https://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=&cad=rja&uact=8&ved=2ahUKEwirzIiIoN71AhXUNuwKHdm0CPQQFnoECCcQAw&url=https%3A%2F%2Fwww.visma.com%2Fcloud-adoption%2Fdigital-invoicing%2F%23%3A~%3Atext%3DDigital%2520invoicing%2520is%2520a%2520modernised%2Cwith%2520sending%2520and%2520receiving%2520invoices.%26text%3DIf%2520the%2520customer%2520is%2520set%2Cbank%252C%2520it%2520will%2520go%2520there.&usg=AOvVaw23medh_UhBwEQRubS8azep
Additional information: The Digital Invoicing Digital Business Capability (DIDBC) is a crucial component of the European Union's efforts to enhance IT interoperability among member states and private companies in the context of invoicing processes. It aims to streamline and digitize the invoicing procedures, promoting efficiency, cost-effectiveness, and environmental sustainability.
The DIDBC encompasses a set of standardized electronic invoicing practices, protocols, and technologies that facilitate the exchange of invoices between businesses, public administrations, and consumers across the European Union. It provides a common framework for the creation, transmission, receipt, and archiving of digital invoices, ensuring their authenticity, integrity, and legal compliance.
At its core, the DIDBC promotes the use of structured electronic invoice formats, such as the Universal Business Language (UBL) or the Cross-Industry Invoice (CII), which enable the seamless exchange of invoice data between different software systems. These formats ensure that invoices can be easily processed, validated, and integrated into the recipient's financial management systems, eliminating the need for manual data entry and reducing errors.
Furthermore, the DIDBC encourages the adoption of electronic signatures and electronic identification methods, such as the European eIDAS regulation, to ensure the authenticity and integrity of digital invoices. These mechanisms provide legal certainty and enable cross-border recognition of electronic invoices, eliminating the need for paper-based documentation and physical signatures.
To facilitate the implementation of the DIDBC, the European Union has established a set of technical specifications, guidelines, and best practices. These resources assist member states and private companies in aligning their invoicing processes with the European standard, ensuring interoperability and seamless cross-border exchange of invoices.
The benefits of the DIDBC are manifold. Firstly, it significantly reduces the administrative burden associated with traditional paper-based invoicing, leading to cost savings for businesses and public administrations. It also enhances the speed and accuracy of invoice processing, enabling faster payment cycles and improving cash flow management.
Moreover, the DIDBC promotes environmental sustainability by reducing paper consumption and the associated carbon footprint. It also fosters a more transparent and accountable business environment, as digital invoices leave a clear audit trail and are less prone to manipulation or fraud.
The European Union has been actively promoting the adoption of the DIDBC among member states and private companies. It has provided financial support, technical assistance, and capacity-building programs to facilitate the transition from paper-based to digital invoicing. Additionally, the EU has established a European eInvoicing Service Providers List, which serves as a trusted directory of service providers offering compliant e-invoicing solutions.
In conclusion, the Digital Invoicing Digital Business Capability plays a vital role in enhancing IT interoperability within the European Union. By promoting standardized electronic invoicing practices, it streamlines invoicing processes, reduces costs, improves efficiency, and contributes to a more sustainable and transparent business environment.
Example: The application of Digital Invoicing Digital Business Capability in the context of European IT interoperability among member states and private companies can have several examples:
1. Cross-border e-invoicing: Digital invoicing enables seamless cross-border transactions between member states and private companies. It allows businesses to send and receive invoices electronically, eliminating the need for paper-based processes. This streamlines the invoicing process, reduces errors, and improves efficiency in cross-border trade.
2. Standardization of invoice formats: Digital invoicing promotes the use of standardized invoice formats, such as the European standard EN16931. This ensures that invoices are structured uniformly across member states and private companies, facilitating interoperability and enabling automated processing of invoices.
3. Integration with accounting systems: Digital invoicing capabilities can be integrated with accounting systems used by member states and private companies. This integration enables automatic transfer of invoice data into accounting software, reducing manual data entry and improving accuracy. It also enables real-time tracking of invoices, payment status, and financial reporting.
4. Compliance with legal and regulatory requirements: Digital invoicing capabilities ensure compliance with legal and regulatory requirements across member states. For example, the European Directive on e-invoicing (2014/55/EU) mandates the use of electronic invoicing in public procurement. Digital invoicing solutions help businesses adhere to these requirements, ensuring smooth interoperability between member states and private companies.
5. Interoperability platforms: Digital invoicing capabilities can be facilitated through interoperability platforms that connect member states and private companies. These platforms act as intermediaries, enabling seamless exchange of electronic invoices, regardless of the technical systems used by different entities. They provide a common framework for interoperability, ensuring smooth communication and data exchange.
Overall, the application of Digital Invoicing Digital Business Capability in European IT interoperability among member states and private companies enhances efficiency, reduces costs, and promotes seamless cross-border trade.
LOST view: Organisational view
Identifier: http://data.europa.eu/dr8/egovera/DigitalInvoicingCapability
ABB name: eira:DigitalInvoicingCapability
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/egovera/DigitalInvoicingCapability
Name: Digital Invoicing Digital Business Capability
Interoperability Layer: Organisational
Specialises: http://data.europa.eu/dr8/DigitalBusinessCapability
Description: The Data Monetization Digital Business Capability refers to the organization's ability to generate value and revenue by leveraging its data assets. It involves the identification, collection, analysis, and transformation of data into valuable insights, products, or services that can be sold or monetized. This capability encompasses various activities such as data governance, data analytics, data visualization, and the development of data-driven business models. By effectively monetizing its data, an organization can gain a competitive advantage, drive innovation, and create new revenue streams.
Additional information: The Data Monetization Digital Business Capability refers to the ability of an organization to generate revenue or derive value from its data assets. It involves the strategic and systematic exploration, analysis, and exploitation of data to create new business opportunities, enhance existing products or services, and drive innovation.
This capability encompasses various activities and processes that enable organizations to leverage their data for commercial purposes. It starts with the identification and collection of relevant data from various sources, including internal systems, external partners, customers, and other stakeholders. This data may include structured, unstructured, or semi-structured information.
Once the data is collected, it needs to be processed, cleaned, and transformed into a usable format. This involves applying data analytics techniques, such as data mining, machine learning, and statistical analysis, to extract valuable insights, patterns, and trends. These insights can then be used to make informed business decisions, optimize operations, and identify new revenue streams.
The Data Monetization capability also involves the development of data-driven products or services. Organizations can create data products by packaging and selling their data to external customers, partners, or third-party vendors. This can include providing access to raw data, aggregated data sets, or offering data analytics services. Data-driven services can also be developed by leveraging data to enhance existing products or create new offerings that provide unique value to customers.
Furthermore, organizations need to establish appropriate data governance and management practices to ensure data quality, security, privacy, and compliance with regulatory requirements. This includes defining data ownership, access controls, data lifecycle management, and establishing data sharing agreements with external parties.
To effectively monetize data, organizations also need to invest in the necessary technological infrastructure and capabilities. This may involve implementing data storage and processing systems, data integration and interoperability platforms, data analytics tools, and data visualization solutions. Additionally, organizations should have a robust data strategy and roadmap that aligns with their overall business objectives and supports their data monetization initiatives.
The Data Monetization Digital Business Capability is not limited to any specific industry or sector. It can be applied across various domains, including finance, healthcare, retail, manufacturing, and transportation, among others. Organizations that successfully develop this capability can gain a competitive advantage by leveraging their data assets to drive innovation, improve customer experiences, and generate new revenue streams.
Example: Data Monetization is the process of generating revenue or deriving value from data assets. In the public sector, where the primary focus is on delivering services to citizens, data monetization can take various forms. Here are some real examples of the Data Monetization Digital Business Capability in the public sector:
1. Open Data Marketplaces: Governments can create open data marketplaces where they make certain datasets available to the public, researchers, or businesses for a fee. For instance, a city government might provide access to transportation or environmental data to companies developing smart city solutions.
2. Data Analytics Services: Public sector organizations can offer data analytics services to external entities. They can leverage their data expertise and infrastructure to analyze data for businesses, researchers, or other government agencies. This can include performing data mining, predictive analytics, or generating insights from large datasets.
3. Data-driven Policy Making: Governments can monetize data by using it to inform policy decisions. By analyzing various datasets, they can identify trends, patterns, and correlations that help in making informed policy choices. This can lead to better resource allocation, improved service delivery, and cost savings.
4. Data Sharing Partnerships: Public sector organizations can enter into data sharing partnerships with private companies or research institutions. By sharing anonymized or aggregated data, they can contribute to research, innovation, or the development of new products and services. These partnerships can be monetized through licensing agreements or revenue-sharing models.
5. Data-driven Service Improvements: Public sector organizations can leverage data to enhance their services and generate value. For example, by analyzing citizen feedback, usage patterns, or service performance metrics, they can identify areas for improvement and optimize service delivery. This can lead to increased citizen satisfaction and potentially attract businesses willing to pay for improved services.
6. Data-driven Decision Support: Governments can monetize data by providing decision support services to external entities. By leveraging their data assets and expertise, they can offer insights, recommendations, or predictive models to businesses, organizations, or individuals. This can help in making informed decisions, optimizing operations, or identifying new opportunities.
These examples demonstrate how the Data Monetization Digital Business Capability can be applied in the public sector to generate value from data assets while still aligning with the sector's primary objective of serving citizens and improving public services.
Publisher: EIRA Team
LOST view: OV-Data Spaces [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/DataMonetizationCapability
EIRA traceability: eira:DigitalBusinessCapability
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-07-10
dct:identifier: http://data.europa.eu/dr8/egovera/DataMonetizationCapability
dct:title: Data Monetization Digital Business Capability
Description: The 'Import Procedure' Digital Business Capability refers to the ability of a business to effectively manage and execute the processes involved in importing goods or services. This includes understanding and complying with international trade regulations, managing logistics, handling customs procedures, and ensuring the secure and timely delivery of goods. It also involves the use of digital technologies to streamline and automate these processes, improve efficiency, reduce costs, and minimize errors. This capability is crucial for businesses involved in international trade, as it directly impacts their supply chain efficiency, operational costs, and customer satisfaction.
Additional information: The 'Import Procedure' Digital Business Capability refers to the ability of an organization to effectively manage and execute all the processes involved in importing goods or services in a digital environment. This capability encompasses a wide range of activities, including but not limited to, sourcing and procurement from international suppliers, compliance with international trade laws and regulations, customs clearance, logistics and supply chain management, and integration with internal systems for inventory management and accounting.
This capability requires a robust digital infrastructure that can support the complex and often time-sensitive processes involved in importation. This includes systems for electronic data interchange (EDI) to facilitate communication with suppliers, customs, and logistics providers; enterprise resource planning (ERP) systems to manage inventory and financial aspects; and possibly customer relationship management (CRM) systems to manage relationships with suppliers and other stakeholders.
The 'Import Procedure' Digital Business Capability also involves the ability to leverage digital technologies to improve efficiency and effectiveness. This could include the use of artificial intelligence (AI) for predictive analytics in sourcing and procurement, blockchain technology for secure and transparent tracking of goods, and automation of routine tasks such as data entry and document generation.
Furthermore, this capability requires a strong understanding of international trade laws and regulations, and the ability to stay updated on changes that could impact the import process. This could involve the use of digital tools for regulatory compliance management.
In summary, the 'Import Procedure' Digital Business Capability is about leveraging digital technologies and systems to manage and optimize the complex processes involved in importing goods or services, while ensuring compliance with relevant laws and regulations.
Example: 1. Customs and Border Protection: This public sector organization has a digital business capability for managing the import procedure. This includes digital systems for tracking and documenting goods that are being imported, as well as systems for assessing and collecting duties and taxes.
2. Food and Drug Administration (FDA): The FDA has digital business capabilities for managing the import procedure of food, drugs, and other products. This includes systems for inspecting and testing imported products, as well as systems for tracking and documenting these inspections.
3. Department of Agriculture: This department has digital business capabilities for managing the import procedure of agricultural products. This includes systems for inspecting and testing imported products, as well as systems for tracking and documenting these inspections.
4. Environmental Protection Agency (EPA): The EPA has digital business capabilities for managing the import procedure of certain types of goods, such as chemicals and hazardous materials. This includes systems for inspecting and testing imported goods, as well as systems for tracking and documenting these inspections.
5. Department of Commerce: This department has digital business capabilities for managing the import procedure of various types of goods. This includes systems for tracking and documenting imports, as well as systems for assessing and collecting duties and taxes.
6. National Health Services (NHS) in the UK: The NHS has digital business capabilities for managing the import procedure of medical supplies and equipment. This includes systems for tracking and documenting these imports, as well as systems for ensuring that they meet safety and quality standards.
7. Australian Border Force: This agency has digital business capabilities for managing the import procedure of goods into Australia. This includes systems for tracking and documenting imports, as well as systems for assessing and collecting duties and taxes.
Publisher: EIRA Team
LOST view: OV-Import procedure [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/ImportProcedureCapability
EIRA traceability: eira:DigitalBusinessCapability
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-08-08
dct:identifier: http://data.europa.eu/dr8/egovera/ImportProcedureCapability
dct:title: Import procedure (DBC)
Description: 'Tariffs registry management' is a digital business capability that involves the use of technology to manage, update, and maintain a comprehensive database of tariffs. This capability includes the ability to record and track changes in tariffs, ensure compliance with regulatory standards, and provide accurate and up-to-date tariff information to relevant stakeholders. It may also involve the use of analytics to monitor tariff trends and make data-driven decisions. This capability is crucial for businesses in industries such as telecommunications, energy, and logistics, where tariffs play a significant role in revenue generation and cost management.
Additional information: The 'Tariffs Registry Management' Digital Business Capability refers to the ability of a business to effectively manage, maintain, and update a digital registry or database of tariffs. This capability is crucial for businesses that deal with import and export activities, telecommunications, utilities, or any other industry where tariffs are applied.
This capability involves several key components:
1. Tariff Data Management: This involves the collection, validation, storage, and management of all tariff-related data. It includes the ability to handle large volumes of data and ensure its accuracy and consistency.
2. Tariff Setting and Adjustment: The capability to set and adjust tariffs based on various factors such as market conditions, regulatory requirements, cost structures, and business strategies. This also includes the ability to apply different tariffs for different customer segments, products, or services.
3. Tariff Analysis and Reporting: This includes the ability to analyze tariff data to gain insights into business performance, customer behavior, market trends, etc. It also involves generating reports for internal use or for regulatory compliance.
4. Tariff Compliance: Ensuring that all tariffs are in compliance with local, national, and international laws and regulations. This includes the ability to quickly adapt to changes in these regulations.
5. Integration: The capability to integrate the tariff registry with other business systems such as billing, customer relationship management (CRM), and enterprise resource planning (ERP) systems. This ensures that tariff data is consistent across the organization and can be easily accessed and used by different departments.
6. Security and Privacy: Protecting the tariff data from unauthorized access, manipulation, or loss. This includes implementing appropriate data security measures and privacy controls.
7. User Interface and Experience: Providing a user-friendly interface for managing the tariff registry. This includes features such as search, filter, sort, and easy navigation.
8. Automation: The ability to automate routine tasks such as data entry, tariff calculation, and report generation. This increases efficiency and reduces the risk of errors.
In the digital context, this capability may also involve the use of advanced technologies such as cloud computing, big data analytics, artificial intelligence (AI), and machine learning to enhance the management of the tariff registry.
Example: 1. Public Utility Commission: The Public Utility Commission may have a 'Tariffs Registry Management' capability to manage and regulate the tariffs of utilities such as electricity, water, and gas. This capability allows them to register, update, and monitor the tariffs set by utility companies, ensuring they are fair and reasonable for consumers.
2. Postal Services: Postal services like USPS, Royal Mail, etc., may use 'Tariffs Registry Management' to manage the tariffs for various postal services they offer. This includes tariffs for domestic and international mail, parcel services, express deliveries, etc.
3. Telecommunication Regulatory Authority: A Telecommunication Regulatory Authority may have a 'Tariffs Registry Management' capability to manage the tariffs of various telecom services. This includes tariffs for voice calls, data usage, SMS, etc. The authority uses this capability to ensure that telecom companies do not overcharge customers.
4. Transportation Department: The Department of Transportation may use 'Tariffs Registry Management' to manage the tariffs for public transportation services. This includes tariffs for buses, trains, trams, etc. The department uses this capability to ensure that public transportation is affordable for all citizens.
5. Customs and Border Protection: The Customs and Border Protection agency may use 'Tariffs Registry Management' to manage the tariffs for importing and exporting goods. This includes tariffs for various types of goods, from consumer products to industrial equipment. The agency uses this capability to regulate trade and protect domestic industries.
Publisher: EIRA Team
LOST view: OV-Tariffs registry management [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/TariffsRegistryManagementCapability
EIRA traceability: eira:DigitalBusinessCapability
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-08-08
dct:identifier: http://data.europa.eu/dr8/egovera/TariffsRegistryManagementCapability
dct:title: Tariffs registry management (DBC)
Definition: Digital Payment enables the purchase of goods or services via digital or online modes, without the involvement of physical money exchange. It provides the possibility to perform financial operations using digital payment methods such as, among others, Banking Cards and Point of Sale (PoS) terminals.
Source: Worldbank
Source reference: https://openknowledge.worldbank.org/handle/10986/35613
Additional information: The Digital Payments Digital Business Capability (DP-DBC) in the context of European IT interoperability among member states and private companies refers to the ability to facilitate seamless and secure digital payment transactions across borders within the European Union (EU). It encompasses the technological infrastructure, standards, protocols, and frameworks that enable interoperability between various payment systems, financial institutions, and service providers.
The DP-DBC aims to create a unified and harmonized digital payments ecosystem, ensuring that individuals, businesses, and public entities can make and receive payments efficiently, conveniently, and with confidence across different EU countries. It seeks to eliminate the barriers and complexities associated with cross-border payments, such as high transaction costs, lengthy processing times, and lack of transparency.
Key components of the DP-DBC include:
1. Standardization and Interoperability: The DP-DBC promotes the adoption of common technical standards, protocols, and data formats to ensure seamless interoperability between different payment systems, platforms, and networks. This allows for the smooth exchange of payment information and data between member states and private companies.
2. Regulatory Framework: The DP-DBC aligns with EU regulations and directives, such as the Revised Payment Services Directive (PSD2), to establish a legal framework that governs digital payments and ensures consumer protection, data privacy, and security. It also encourages the implementation of strong authentication measures, such as two-factor authentication, to enhance the security of digital transactions.
3. Cross-Border Payment Infrastructure: The DP-DBC supports the development and integration of cross-border payment infrastructures, such as the Single Euro Payments Area (SEPA), which enables fast and low-cost euro-denominated transfers across EU countries. It also facilitates the interoperability of national payment systems, clearinghouses, and settlement mechanisms to streamline cross-border transactions.
4. Payment Initiation Services: The DP-DBC enables the provision of payment initiation services by third-party providers, allowing consumers and businesses to initiate payments directly from their bank accounts without the need for traditional payment methods. This fosters innovation, competition, and choice in the digital payments landscape.
5. Open Banking and APIs: The DP-DBC promotes the use of open banking principles and application programming interfaces (APIs) to enable secure and controlled access to payment account information and payment initiation services. This allows authorized third-party providers to offer innovative payment solutions and value-added services, enhancing the overall digital payments experience.
6. Data Exchange and Reporting: The DP-DBC facilitates the exchange of payment-related data and reporting between member states and private companies. This enables regulatory authorities to monitor and analyze payment flows, detect fraudulent activities, and ensure compliance with anti-money laundering (AML) and counter-terrorism financing (CTF) regulations.
Overall, the Digital Payments Digital Business Capability plays a crucial role in fostering a harmonized and efficient digital payments landscape within the European Union. It aims to enhance cross-border trade, promote financial inclusion, and drive economic growth by enabling secure, convenient, and cost-effective digital payment transactions among member states and private companies.
Example: The Digital Payments Digital Business Capability can be applied in various ways to enhance IT interoperability among member states and private companies in Europe. Here are some examples:
1. Single Euro Payments Area (SEPA): The Digital Payments capability can be used to establish a standardized payment infrastructure across European countries, enabling seamless cross-border transactions. It ensures that payment systems, formats, and processes are interoperable, allowing individuals and businesses to make and receive payments easily within the European Union.
2. European Payment Initiative (EPI): EPI is an ongoing project aiming to create a unified European payment solution. The Digital Payments capability can be utilized to develop interoperable systems and technologies that enable secure and efficient payments across member states and private companies. It ensures that payment methods, such as mobile payments or instant payments, can be used seamlessly across Europe.
3. Open Banking: The Digital Payments capability can facilitate the implementation of open banking standards, enabling secure access to financial data and payment services across different banks and financial institutions. It ensures that member states and private companies can develop interoperable payment solutions that comply with the Payment Services Directive 2 (PSD2) and provide customers with enhanced payment experiences.
4. Digital Identity and Authentication: The Digital Payments capability can be integrated with digital identity solutions to establish interoperable authentication methods for secure payments. This allows member states and private companies to implement strong customer authentication measures while ensuring interoperability and compliance with regulations like the General Data Protection Regulation (GDPR).
5. Cross-Border E-commerce: The Digital Payments capability can support the development of interoperable payment systems for cross-border e-commerce transactions. It enables member states and private companies to offer secure and convenient payment options to customers across Europe, fostering growth in the digital economy and facilitating international trade.
Overall, the Digital Payments Digital Business Capability plays a crucial role in enhancing IT interoperability among member states and private companies in Europe, enabling seamless and secure digital payments across borders.
LOST view: Organisational view
Identifier: http://data.europa.eu/dr8/egovera/DigitalPaymentsCapability
ABB name: eira:DigitalPaymentsCapability
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/egovera/DigitalPaymentsCapability
Name: Digital Payments Digital Business Capability
Interoperability Layer: Organisational
Specialises: http://data.europa.eu/dr8/DigitalBusinessCapability
Description: The Data Discovery Digital Business Capability refers to the ability of an organization to effectively and efficiently discover, analyze, and interpret large volumes of data to gain valuable insights and make informed business decisions. This capability involves the use of advanced data analytics tools and techniques to identify patterns, trends, and correlations within the data, enabling organizations to uncover hidden opportunities, mitigate risks, and optimize their operations. By leveraging data discovery capabilities, organizations can enhance their competitiveness, drive innovation, and improve overall business performance.
Additional information: The Data Discovery Digital Business Capability refers to the ability of an organization to effectively and efficiently discover, analyze, and interpret data in order to gain valuable insights and make informed business decisions. It involves the use of advanced technologies, tools, and methodologies to explore and uncover patterns, trends, and relationships within large volumes of data.
This capability encompasses various activities and processes that enable organizations to extract meaningful information from diverse data sources, including structured and unstructured data. It involves the identification and collection of relevant data from internal and external sources, such as databases, data warehouses, social media platforms, customer feedback, market research, and sensor-generated data.
The Data Discovery Digital Business Capability involves the use of data discovery tools and techniques, such as data mining, data visualization, statistical analysis, machine learning, and natural language processing. These tools help in identifying patterns, correlations, and anomalies within the data, allowing organizations to gain valuable insights and make data-driven decisions.
Key components of this capability include:
1. Data Collection: This involves the identification and gathering of relevant data from various sources, ensuring data quality and integrity.
2. Data Integration: The capability to integrate data from multiple sources, ensuring consistency and compatibility, and creating a unified view of the data.
3. Data Exploration: The ability to explore and analyze data using advanced analytics techniques, such as data mining, statistical analysis, and machine learning algorithms.
4. Data Visualization: The capability to present data in a visually appealing and easily understandable format, using charts, graphs, dashboards, and other visual tools.
5. Data Interpretation: The skill to interpret and derive meaningful insights from the analyzed data, identifying trends, patterns, and correlations that can drive business decisions.
6. Data Governance: The establishment of policies, procedures, and controls to ensure data privacy, security, and compliance with regulatory requirements.
7. Data-driven Decision Making: The ability to leverage the insights gained from data discovery to make informed business decisions, optimize processes, and drive innovation.
The Data Discovery Digital Business Capability is crucial for organizations in today's data-driven business environment. It enables them to uncover hidden opportunities, identify potential risks, improve operational efficiency, enhance customer experience, and gain a competitive edge. By harnessing the power of data, organizations can make strategic decisions, drive innovation, and achieve their business objectives.
Example: The Data Discovery Digital Business Capability in the public sector refers to the ability to identify, collect, analyze, and interpret data to gain insights and make informed decisions. Here are some real examples of this capability in action:
1. Open Data Initiatives: Many governments have launched open data initiatives, where they make various datasets available to the public. Through data discovery, citizens, researchers, and businesses can explore and analyze this data to gain insights, develop innovative solutions, and make data-driven decisions.
2. Predictive Analytics for Public Safety: Law enforcement agencies use data discovery capabilities to analyze historical crime data, demographic information, and other relevant data sources. By applying predictive analytics, they can identify patterns, hotspots, and potential risks, enabling them to allocate resources effectively, prevent crimes, and enhance public safety.
3. Healthcare Data Analysis: Public health agencies leverage data discovery capabilities to analyze large volumes of healthcare data, including patient records, disease prevalence, treatment outcomes, and demographic information. This analysis helps identify trends, patterns, and risk factors, enabling policymakers to make informed decisions, allocate resources, and develop targeted interventions to improve public health outcomes.
4. Performance Monitoring and Reporting: Government agencies use data discovery to monitor and report on their performance and outcomes. By analyzing various data sources, such as financial data, service delivery metrics, and citizen feedback, they can assess their effectiveness, identify areas for improvement, and make data-driven decisions to enhance service delivery and accountability.
5. Fraud Detection and Prevention: Public sector organizations employ data discovery capabilities to identify and prevent fraudulent activities. By analyzing data from multiple sources, such as financial transactions, procurement records, and employee data, they can detect anomalies, patterns, and potential fraud risks. This helps in implementing proactive measures, improving compliance, and safeguarding public funds.
6. Urban Planning and Smart Cities: City governments utilize data discovery capabilities to analyze diverse datasets, including transportation patterns, energy consumption, environmental data, and citizen feedback. By gaining insights from this data, they can make informed decisions regarding urban planning, infrastructure development, and the implementation of smart city initiatives to improve livability and sustainability.
These examples illustrate how the Data Discovery Digital Business Capability enables the public sector to leverage data effectively, make informed decisions, and drive innovation for the benefit of citizens and society as a whole.
Publisher: EIRA Team
LOST view: OV-Data Spaces [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/DataDiscoveryCapability
EIRA traceability: eira:DigitalBusinessCapability
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-07-10
dct:identifier: http://data.europa.eu/dr8/egovera/DataDiscoveryCapability
dct:title: Data Discovery Digital Business Capability
Description: The 'Authorised Economic Operator accreditation' digital business capability refers to the ability of a business to digitally manage and maintain its status as an Authorised Economic Operator (AEO). This includes the capacity to handle digital applications, certifications, audits, and compliance checks related to AEO accreditation. It also involves the ability to digitally monitor and adhere to the standards and regulations set by customs authorities. This capability ensures that the business can efficiently operate within the international supply chain as a trusted and secure partner, benefiting from advantages in customs procedures.
Additional information: The 'Authorised Economic Operator (AEO) accreditation' Digital Business Capability refers to the ability of a business to leverage digital technologies, systems, and processes to obtain and maintain the AEO status, which is a globally recognized quality mark indicating that the company's role in the international supply chain is secure and their customs controls and procedures are efficient and compliant.
This capability involves the use of digital tools and platforms to manage and streamline the application process for AEO status, including the submission of necessary documentation and evidence to customs authorities. It also includes the ability to digitally monitor and ensure ongoing compliance with AEO requirements, such as maintaining appropriate records, demonstrating financial solvency, and implementing effective security and management systems.
Moreover, this capability extends to the ability to use digital technologies to enhance the benefits of AEO status. This could include integrating with customs IT systems for faster and more efficient customs procedures, leveraging data analytics to identify opportunities for further supply chain optimization, and using digital communication tools to demonstrate AEO status to customers, partners, and stakeholders.
In essence, the 'Authorised Economic Operator accreditation' Digital Business Capability is about using digital technologies to facilitate the attainment and exploitation of AEO status, thereby enhancing the business's competitiveness and performance in the global trade environment.
Example: 1. Customs and Border Protection (CBP): In the United States, the CBP uses the Authorized Economic Operator (AEO) accreditation as a part of their Customs-Trade Partnership Against Terrorism (C-TPAT) program. This digital business capability allows them to streamline and secure international trade, reducing the risk of illegal or unsafe goods entering the country.
2. European Union (EU): The EU has a comprehensive AEO system that allows businesses to be recognized as secure and reliable, facilitating faster processing of shipments and fewer customs controls. This digital business capability is used by the public sector to enhance trade efficiency and security across the EU.
3. HM Revenue and Customs (HMRC): In the UK, HMRC uses the AEO accreditation as part of their strategy to secure and facilitate global trade. This digital business capability allows them to provide businesses with benefits such as lower risk scores and priority treatment during customs controls.
4. Australian Border Force (ABF): The ABF uses the AEO accreditation as part of their Trusted Trader program. This digital business capability allows them to provide businesses with trade facilitation benefits, such as faster clearance times and reduced examination rates.
5. Canada Border Services Agency (CBSA): The CBSA uses the AEO accreditation as part of their Partners in Protection (PIP) program. This digital business capability allows them to work with businesses to secure the trade chain and facilitate the movement of legitimate goods.
Publisher: EIRA Team
LOST view: OV-Customs DBCs, DPSs and Information [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/AuthorisedEconomicOperatorAccreditationCapability
EIRA traceability: eira:DigitalBusinessCapability
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-08-08
dct:identifier: http://data.europa.eu/dr8/egovera/AuthorisedEconomicOperatorAccreditationCapability
dct:title: Authorised Economic Operator accreditation (DBC)
Definition: Knowledge Management enables organisation to create and use of knowledge. It is a discipline focused on the development of management systems that effectively promotes and enables value-creation through knowledge.
Source: Gartner
Source reference: https://www.gartner.com/en/information-technology/glossary/km-knowledge-management
Additional information: The Knowledge Management Digital Business Capability (KMDBC) in the context of European IT interoperability among member states and private companies refers to the ability to effectively manage and leverage knowledge assets and resources within the digital business ecosystem. It encompasses the processes, technologies, and strategies employed to capture, organize, store, share, and utilize knowledge and information across different entities, including member states and private companies, to enhance collaboration, decision-making, and innovation.
In the European context, IT interoperability aims to ensure seamless and efficient exchange of information and services between member states and private companies, enabling them to work together effectively and achieve common goals. KMDBC plays a crucial role in supporting this interoperability by facilitating the creation, dissemination, and utilization of knowledge and information across these entities.
One aspect of KMDBC is the establishment of knowledge repositories and databases that store relevant information, best practices, and lessons learned. These repositories serve as centralized sources of knowledge, accessible to member states and private companies, promoting knowledge sharing and collaboration. They can include technical specifications, standards, guidelines, and case studies related to IT interoperability.
Furthermore, KMDBC involves the implementation of knowledge management systems and tools that enable efficient knowledge capture, organization, and retrieval. These systems can include document management systems, content management systems, and collaboration platforms, which facilitate the creation, storage, and dissemination of knowledge assets. They also support the development of communities of practice, where experts from member states and private companies can exchange knowledge, share experiences, and collaborate on interoperability initiatives.
Another important aspect of KMDBC is the establishment of knowledge sharing mechanisms and processes. This can involve the creation of knowledge sharing networks, forums, and communities, where member states and private companies can exchange information, share best practices, and address interoperability challenges. These mechanisms can be facilitated through online platforms, workshops, conferences, and working groups, fostering a culture of knowledge sharing and collaboration.
In addition, KMDBC encompasses the development of knowledge management strategies and policies that guide the effective utilization of knowledge assets. These strategies can include guidelines for knowledge creation, capture, and dissemination, as well as policies for intellectual property rights, data protection, and privacy. They also address issues related to knowledge governance, ensuring that knowledge is managed in a structured and coordinated manner across member states and private companies.
Overall, the KMDBC in the context of European IT interoperability among member states and private companies aims to foster a collaborative and knowledge-driven environment. It enables the efficient exchange of information, best practices, and lessons learned, leading to improved decision-making, innovation, and ultimately, the successful achievement of interoperability objectives.
Example: The application of Knowledge Management Digital Business Capability in the context of European IT interoperability among member states and private companies can be seen in various ways. Here are a few examples:
1. Knowledge Sharing Platforms: Knowledge Management systems can be implemented to create centralized platforms where member states and private companies can share best practices, lessons learned, and technical expertise related to IT interoperability. These platforms can facilitate collaboration and knowledge exchange, enabling stakeholders to learn from each other's experiences and improve their interoperability efforts.
2. Standardization and Documentation: Knowledge Management can help establish common standards and documentation practices for IT interoperability across member states and private companies. This includes developing standardized frameworks, guidelines, and templates that can be used to ensure consistency and compatibility in IT systems and processes. By sharing and managing this knowledge effectively, interoperability challenges can be minimized.
3. Communities of Practice: Knowledge Management can support the creation of communities of practice, bringing together experts and practitioners from member states and private companies who are involved in IT interoperability. These communities can serve as forums for sharing knowledge, discussing challenges, and co-creating solutions. They can also facilitate networking and collaboration among stakeholders, fostering a culture of continuous learning and improvement.
4. Knowledge Repositories: Digital repositories can be established to store and manage relevant knowledge assets related to IT interoperability. These repositories can include technical specifications, guidelines, case studies, and other resources that can be accessed by member states and private companies. By having a centralized repository, stakeholders can easily access and leverage existing knowledge, avoiding duplication of efforts and promoting efficiency.
5. Training and Capacity Building: Knowledge Management can support the development and delivery of training programs and capacity-building initiatives focused on IT interoperability. These programs can provide member states and private companies with the necessary knowledge and skills to effectively implement interoperable IT systems. By capturing and disseminating best practices and lessons learned, these initiatives can contribute to building a knowledgeable workforce capable of driving interoperability efforts.
Overall, the application of Knowledge Management Digital Business Capability can play a crucial role in enhancing European IT interoperability among member states and private companies by facilitating knowledge sharing, standardization, collaboration, and capacity building.
LOST view: Organisational view
Identifier: http://data.europa.eu/dr8/egovera/KnowledgeManagementCapability
ABB name: eira:KnowledgeManagementCapability
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/egovera/KnowledgeManagementCapability
Name: Knowledge Management Digital Business Capability
Interoperability Layer: Organisational
Specialises: http://data.europa.eu/dr8/DigitalBusinessCapability
Description: The 'Cooperation between Customs laboratories' digital business capability refers to the ability of different customs laboratories to effectively collaborate and share information through digital means. This capability involves the use of digital technologies and systems to facilitate seamless communication, data exchange, and coordination among customs laboratories. It enables these laboratories to work together in real-time, irrespective of their geographical locations, to ensure efficient and accurate customs operations. This could involve sharing of test results, research data, methodologies, and other relevant information. This capability not only enhances operational efficiency but also ensures consistency and accuracy in customs procedures across different regions.
Additional information: The 'Cooperation between Customs laboratories' Digital Business Capability refers to the ability of customs laboratories across different regions or countries to collaborate, share information, and work together through digital means. This capability is crucial in the context of global trade and security, where customs laboratories play a vital role in verifying the compliance of goods with various regulations and standards.
This digital business capability involves several key components:
1. Data Sharing and Communication: This involves the use of digital platforms and tools to share data and information between customs laboratories. This could include sharing results of tests, methodologies used, or information about new regulations or standards.
2. Standardization: This refers to the development and use of common standards and procedures across different customs laboratories. This ensures consistency and reliability in the work of these laboratories, and can be facilitated through digital tools and platforms.
3. Collaboration: This involves working together on joint projects or investigations, which can be facilitated through digital collaboration tools. This could also involve joint training or capacity-building initiatives.
4. Integration: This refers to the ability to integrate different systems and processes across customs laboratories. This could involve the use of APIs or other integration technologies to ensure seamless data flow and interoperability between different systems.
5. Security and Compliance: Given the sensitive nature of the data handled by customs laboratories, this capability also involves ensuring the security of digital platforms and compliance with data protection regulations.
6. Innovation: This involves the use of digital technologies to drive innovation in the work of customs laboratories. This could involve the use of AI, machine learning, or other advanced technologies to improve the efficiency and effectiveness of customs laboratories.
In summary, the 'Cooperation between Customs laboratories' Digital Business Capability involves leveraging digital technologies to enhance the collaboration, data sharing, standardization, integration, security, compliance, and innovation in the work of customs laboratories.
Example: 1. European Customs Laboratories Network: The European Union has a network of customs laboratories that cooperate to ensure the correct classification and valuation of goods for customs purposes. They share information and best practices, conduct joint research, and provide training to enhance their collective capabilities.
2. U.S. Customs and Border Protection (CBP) Laboratories and Scientific Services: CBP laboratories in the United States cooperate with other federal, state, and local laboratories to share information and resources. They also collaborate with international partners to combat global threats and ensure the security and integrity of the global supply chain.
3. World Customs Organization (WCO) Cooperation: The WCO promotes cooperation between customs laboratories worldwide. They provide a platform for sharing information, conducting joint research, and developing common standards and procedures. They also facilitate training and capacity building activities.
4. ASEAN Customs Forensic Science Network: The Association of Southeast Asian Nations (ASEAN) has established a network of customs forensic science laboratories to enhance cooperation in the region. They share information, conduct joint research, and provide training to enhance their collective capabilities.
5. Customs Cooperation Council (CCC) Laboratory Program: The CCC promotes cooperation between customs laboratories in its member countries. They share information, conduct joint research, and provide training to enhance their collective capabilities.
6. Digital Platforms for Data Sharing: Many customs laboratories use digital platforms to share data and information. These platforms enable real-time cooperation and collaboration, making it easier to detect and respond to threats and challenges.
7. Joint Training Programs: Customs laboratories often conduct joint training programs to enhance their capabilities. These programs provide opportunities for staff from different laboratories to learn from each other and develop new skills and knowledge.
8. Collaborative Research Projects: Customs laboratories often participate in collaborative research projects. These projects enable them to pool their resources and expertise to address common challenges and develop new solutions.
Publisher: EIRA Team
LOST view: OV-Cooperation between Customs laboratories [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/CooperationBetweenCustomsLaboratoriesCapability
EIRA traceability: eira:DigitalBusinessCapability
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-08-08
dct:identifier: http://data.europa.eu/dr8/egovera/CooperationBetweenCustomsLaboratoriesCapability
dct:title: Cooperation between Customs laboratories (DBC)
Description: The Data Analytics Digital Business Capability refers to the organization's ability to collect, analyze, and interpret large volumes of data to gain valuable insights and make informed business decisions. It involves the use of advanced analytics techniques, such as data mining, predictive modeling, and machine learning, to identify patterns, trends, and correlations within the data. This capability enables organizations to optimize their operations, improve customer experience, and drive innovation by leveraging data-driven insights. It also involves the implementation of data governance and data management practices to ensure the accuracy, integrity, and security of the data being analyzed.
Additional information: The Data Analytics Digital Business Capability refers to an organization's ability to collect, analyze, and derive insights from large volumes of data to make informed business decisions and drive strategic initiatives. It involves the use of advanced analytical techniques, tools, and technologies to extract valuable information from structured and unstructured data sources.
This capability encompasses various activities, including data collection, data storage, data processing, data analysis, and data visualization. It involves the application of statistical models, machine learning algorithms, and data mining techniques to identify patterns, trends, and correlations within the data.
The Data Analytics Digital Business Capability enables organizations to gain a deeper understanding of their customers, markets, operations, and overall business performance. It allows them to uncover hidden insights, discover new opportunities, and mitigate risks. By leveraging data analytics, organizations can make data-driven decisions, optimize processes, enhance customer experiences, and drive innovation.
Key components of the Data Analytics Digital Business Capability include:
1. Data Collection: This involves gathering data from various internal and external sources, such as transactional systems, social media platforms, customer feedback, and IoT devices. It may also involve data integration and data cleansing processes to ensure data quality and consistency.
2. Data Storage: This refers to the storage and management of large volumes of data in structured databases, data warehouses, or data lakes. It may involve the use of cloud-based storage solutions or on-premises infrastructure.
3. Data Processing: This involves transforming raw data into a format suitable for analysis. It may include data aggregation, data filtering, data transformation, and data enrichment processes. Data processing techniques may vary depending on the specific analytical requirements and the nature of the data.
4. Data Analysis: This is the core activity of the Data Analytics Digital Business Capability. It involves applying various analytical techniques, such as descriptive analytics, diagnostic analytics, predictive analytics, and prescriptive analytics, to gain insights from the data. This may include statistical analysis, data visualization, data modeling, and data simulation.
5. Data Visualization: This refers to the presentation of data in a visual format, such as charts, graphs, and dashboards, to facilitate understanding and decision-making. Data visualization techniques help stakeholders easily interpret complex data and identify patterns or trends.
6. Data Governance and Security: This capability also encompasses ensuring data governance practices and security measures are in place to protect sensitive data, comply with regulations, and maintain data privacy. It involves establishing data access controls, data classification, data retention policies, and data protection mechanisms.
Overall, the Data Analytics Digital Business Capability empowers organizations to harness the power of data to gain a competitive advantage, drive innovation, and improve business outcomes. It enables organizations to make data-driven decisions, optimize processes, enhance customer experiences, and identify new revenue streams.
Example: The Data Analytics Digital Business Capability in the public sector refers to the ability to collect, analyze, and derive insights from large volumes of data to inform decision-making and improve public services. Here are some real examples of this capability in action:
1. Predictive Policing: Law enforcement agencies use data analytics to analyze historical crime data, identify patterns, and predict future crime hotspots. This helps allocate resources effectively, deploy officers strategically, and prevent crime more efficiently.
2. Fraud Detection and Prevention: Government agencies, such as tax authorities or social welfare departments, employ data analytics to detect fraudulent activities. By analyzing large datasets, they can identify suspicious patterns, anomalies, or fraudulent claims, enabling them to take appropriate actions to prevent financial losses.
3. Traffic Management: Public transportation authorities leverage data analytics to optimize traffic flow and improve commuter experiences. By analyzing real-time data from sensors, GPS devices, and social media, they can identify traffic congestion patterns, adjust signal timings, and provide real-time traffic updates to commuters.
4. Healthcare Analytics: Public healthcare organizations utilize data analytics to improve patient care and optimize resource allocation. By analyzing patient records, treatment outcomes, and population health data, they can identify trends, predict disease outbreaks, and allocate resources effectively to areas with higher healthcare demands.
5. Social Services Planning: Government agencies responsible for social services, such as housing, welfare, or education, use data analytics to identify areas of high demand and plan resource allocation accordingly. By analyzing demographic data, socioeconomic indicators, and service utilization patterns, they can ensure that services are targeted to those who need them the most.
6. Environmental Monitoring: Public sector organizations involved in environmental protection and conservation employ data analytics to monitor and manage environmental factors. By analyzing data from sensors, satellite imagery, and weather forecasts, they can identify pollution sources, predict environmental risks, and take proactive measures to protect ecosystems and public health.
These examples demonstrate how the Data Analytics Digital Business Capability can be applied in the public sector to enhance decision-making, optimize resource allocation, and improve public services.
Publisher: EIRA Team
LOST view: OV-Data Spaces [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/DataAnalyticsCapability
EIRA traceability: eira:DigitalBusinessCapability
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-07-10
dct:identifier: http://data.europa.eu/dr8/egovera/DataAnalyticsCapability
dct:title: Data Analytics Digital Business Capability
Description: The 'Transit Procedure' digital business capability refers to the ability of a business to manage and facilitate the movement of goods, services, or information from one location to another through digital means. This includes the planning, execution, tracking, and optimization of transit operations using digital technologies. It involves the use of systems and tools for route planning, scheduling, real-time tracking, and analytics to ensure efficient and effective transit procedures. This capability is crucial for businesses in sectors such as logistics, supply chain, transportation, and e-commerce where timely and accurate transit of goods or information is a key operational requirement.
Additional information: The 'Transit Procedure' Digital Business Capability refers to the ability of an organization to manage, control, and execute the process of moving goods, services, or individuals from one location to another through digital means. This capability encompasses a wide range of activities, including the planning, scheduling, tracking, and monitoring of transit operations, as well as the management of related resources, such as vehicles, personnel, and infrastructure.
In a broader sense, this capability also involves the integration and coordination of various other related capabilities, such as supply chain management, logistics, customer service, and risk management. It requires the use of various digital technologies, such as GPS tracking, real-time data analytics, cloud computing, and mobile applications, to ensure efficient and effective transit operations.
The 'Transit Procedure' Digital Business Capability also includes the ability to comply with relevant laws, regulations, and standards related to transit operations, such as safety standards, environmental regulations, and customs procedures. It also involves the ability to manage risks and handle unexpected events or disruptions in transit operations.
Furthermore, this capability involves the ability to continuously improve transit operations based on feedback and performance data, as well as the ability to innovate and adapt to changing market conditions, customer needs, and technological advancements.
Overall, the 'Transit Procedure' Digital Business Capability is crucial for any organization involved in the transportation or logistics industry, as it directly affects their ability to deliver goods or services to their customers in a timely, efficient, and cost-effective manner.
Example: 1. Online Transit Fare Payment System: Many public transportation systems now offer online platforms where commuters can pay their transit fares. This digital capability allows users to reload their transit cards, pay for fares, and even plan their routes.
2. Real-Time Transit Tracking: Some public transit systems have implemented real-time tracking capabilities. This allows commuters to see exactly where their bus or train is and when it will arrive at their stop. This capability can significantly improve the user experience by reducing uncertainty and wait times.
3. Digital Transit Scheduling: Digital scheduling tools allow transit authorities to plan and adjust transit routes and schedules based on real-time data. This can help to optimize transit operations and improve service reliability.
4. Mobile Transit Apps: Many cities have developed mobile apps that provide a range of transit-related services. These can include route planning, fare payment, real-time tracking, and even reporting issues or providing feedback.
5. Automated Fare Collection Systems: Automated fare collection systems are a key digital capability in modern public transit. These systems can include ticket vending machines, contactless payment systems, and mobile payment options.
6. Transit Data Analytics: Public transit authorities can use data analytics to gain insights into transit usage patterns, identify areas for improvement, and make data-driven decisions. This capability can help to improve service efficiency and effectiveness.
7. Intelligent Traffic Management Systems: These systems use digital technologies to manage traffic flow and reduce congestion. They can include traffic signal control systems, real-time traffic updates, and predictive traffic modeling.
8. Electronic Toll Collection: Highways and bridges often use electronic toll collection systems to automate the process of collecting tolls. These systems can include transponders, license plate recognition technology, and online payment options.
Publisher: EIRA Team
LOST view: OV-Transit procedure [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/TransitProcedureCapability
EIRA traceability: eira:DigitalBusinessCapability
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-08-08
dct:identifier: http://data.europa.eu/dr8/egovera/TransitProcedureCapability
dct:title: Transit procedure (DBC)
Definition: Digital Communication enables the virtual collaboration of a group of people engaged in common tasks, using information and communication technologies.
Source: John G. Proakis
Source reference: https://books.google.it/books/about/Digital_Communications.html?id=ABSmAQAACAAJ&redir_esc=y
Additional information: The Digital Communication Digital Business Capability is a crucial aspect of the European IT interoperability framework that aims to facilitate seamless communication and collaboration between member states and private companies within the European Union. It encompasses a wide range of digital communication technologies, standards, and protocols that enable efficient and secure exchange of information and data across different systems and platforms.
At its core, the Digital Communication Digital Business Capability focuses on establishing a common set of rules, guidelines, and technical specifications to ensure interoperability and compatibility among various digital communication systems used by member states and private companies. This capability plays a vital role in promoting digital transformation, enhancing cross-border trade, and fostering innovation and economic growth across the European Union.
One of the key objectives of the Digital Communication Digital Business Capability is to enable seamless electronic communication between public administrations, businesses, and citizens. This involves the development and implementation of standardized electronic messaging formats, such as XML or EDI, which allow for the exchange of structured data and documents in a machine-readable format. By adopting these common formats, member states and private companies can streamline their communication processes, reduce administrative burdens, and improve overall efficiency.
Furthermore, the Digital Communication Digital Business Capability encompasses the establishment of secure and reliable communication channels, including secure email, virtual private networks (VPNs), and encrypted data transmission protocols. These measures ensure the confidentiality, integrity, and authenticity of exchanged information, protecting sensitive data from unauthorized access or tampering.
Interoperability is a key aspect of the Digital Communication Digital Business Capability, as it enables different systems and platforms to seamlessly communicate and exchange data. To achieve this, the capability promotes the use of open standards and specifications, such as those developed by international organizations like the World Wide Web Consortium (W3C) or the European Telecommunications Standards Institute (ETSI). By adhering to these standards, member states and private companies can ensure that their digital communication systems are compatible with each other, regardless of the underlying technologies or vendors involved.
Moreover, the Digital Communication Digital Business Capability also addresses the need for multilingual and multicultural communication within the European Union. It promotes the development and adoption of language technologies, such as machine translation or natural language processing, to facilitate communication and understanding across different languages and cultures. This capability plays a crucial role in enabling cross-border collaboration, trade, and the provision of digital services to citizens and businesses across the European Union.
In summary, the Digital Communication Digital Business Capability is a comprehensive framework that aims to enhance European IT interoperability by establishing common rules, standards, and technologies for digital communication among member states and private companies. It encompasses various aspects, including the adoption of standardized messaging formats, secure communication channels, open standards, and multilingual/multicultural communication technologies. By promoting interoperability, this capability facilitates seamless collaboration, trade, and innovation within the European Union, ultimately driving economic growth and digital transformation.
Example: The application of Digital Communication Digital Business Capability in the context of European IT interoperability among member states and private companies can be seen in various areas. Here are a few examples:
1. eIDAS Regulation: The eIDAS (electronic Identification, Authentication and Trust Services) Regulation aims to facilitate secure cross-border electronic transactions within the European Union. It establishes a framework for recognizing and accepting electronic identification and trust services across member states. Digital Communication Digital Business Capability enables the implementation of interoperable electronic identification and authentication mechanisms, ensuring seamless communication and trust between member states and private companies.
2. European Single Digital Gateway: The European Single Digital Gateway initiative aims to provide citizens and businesses with easy access to information, procedures, and assistance services across the EU. Digital Communication Digital Business Capability plays a crucial role in enabling the development of a user-friendly and interoperable digital platform that allows seamless communication between member states and private companies, ensuring efficient access to information and services.
3. Cross-border e-commerce: Digital Communication Digital Business Capability facilitates cross-border e-commerce activities by enabling interoperable digital communication channels between member states and private companies. This includes standardized electronic data interchange (EDI) protocols, electronic invoicing, and secure online payment systems. These capabilities ensure smooth and efficient communication between businesses and consumers across different member states, promoting cross-border trade.
4. Interoperable data exchange: Digital Communication Digital Business Capability enables the exchange of data and information between member states and private companies in a standardized and interoperable manner. This includes the use of common data formats, protocols, and APIs (Application Programming Interfaces) to ensure seamless data exchange and integration between different systems and platforms. This capability is essential for efficient collaboration and information sharing among member states and private companies in areas such as public administration, healthcare, and transportation.
5. Harmonized cybersecurity standards: Digital Communication Digital Business Capability supports the development and implementation of harmonized cybersecurity standards across member states and private companies. This includes the establishment of common cybersecurity frameworks, protocols, and best practices to ensure the secure exchange of digital information and protect critical infrastructure. Interoperability in cybersecurity measures enhances trust and confidence in digital communication and business transactions among member states and private companies.
Overall, the application of Digital Communication Digital Business Capability in European IT interoperability among member states and private companies aims to foster seamless communication, efficient information exchange, and trust in digital transactions, ultimately promoting the growth of the digital economy within the European Union.
LOST view: Organisational view
Identifier: http://data.europa.eu/dr8/egovera/DigitalCommunicationCapability
ABB name: eira:DigitalCommunicationCapability
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/egovera/DigitalCommunicationCapability
Name: Digital Communication Digital Business Capability
Interoperability Layer: Organisational
Specialises: http://data.europa.eu/dr8/DigitalBusinessCapability
Description: The Data Sharing Digital Business Capability refers to the ability of an organization to securely and efficiently share data with internal and external stakeholders. This capability involves the establishment of data governance frameworks, data privacy and security measures, and the implementation of technologies and platforms that enable seamless data exchange. By effectively sharing data, organizations can enhance collaboration, improve decision-making processes, and drive innovation across various business functions.
Additional information: The Data Sharing Digital Business Capability refers to the ability of an organization to effectively and securely share data across various systems, applications, and stakeholders. It encompasses the processes, technologies, and governance mechanisms required to enable seamless data exchange and collaboration.
This capability involves the establishment of standardized data formats, protocols, and interfaces to facilitate the smooth flow of information between different entities. It ensures that data is shared in a consistent and reliable manner, enabling real-time access, analysis, and decision-making.
Key components of the Data Sharing Digital Business Capability include:
1. Data Integration: This involves integrating data from disparate sources, such as databases, applications, and external systems, into a unified and coherent format. It includes data cleansing, transformation, and mapping to ensure data consistency and accuracy.
2. Data Exchange: This capability enables the secure and efficient transfer of data between internal and external stakeholders. It involves the use of standardized protocols, such as APIs (Application Programming Interfaces), web services, or messaging systems, to facilitate data exchange in a secure and controlled manner.
3. Data Governance: This component focuses on establishing policies, procedures, and controls to ensure data quality, privacy, and compliance. It includes defining data ownership, access controls, data classification, and data lifecycle management to ensure that data is shared in a controlled and secure manner.
4. Data Security: This capability ensures that data is protected from unauthorized access, manipulation, or disclosure. It involves implementing encryption, access controls, authentication mechanisms, and monitoring systems to safeguard sensitive data during sharing and transmission.
5. Data Analytics: This capability leverages shared data to derive insights, make informed decisions, and drive business value. It includes the use of advanced analytics techniques, such as data mining, machine learning, and predictive modeling, to extract meaningful patterns and trends from shared data.
6. Collaboration: This component focuses on enabling effective collaboration and knowledge sharing among stakeholders. It involves providing tools and platforms for real-time collaboration, document sharing, and communication to foster collaboration and innovation.
The Data Sharing Digital Business Capability is crucial for organizations to leverage the power of data and enable digital transformation. It allows organizations to break down data silos, improve operational efficiency, enhance customer experiences, and drive innovation. By enabling seamless data sharing, organizations can unlock the full potential of their data assets and gain a competitive advantage in the digital era.
Example: The Data Sharing Digital Business Capability in the public sector refers to the ability to securely and efficiently share data across different government agencies or departments. This capability enables seamless collaboration, improved decision-making, and enhanced service delivery. Here are some real examples of this capability in action:
1. Integrated Health Information Systems: In many countries, public health agencies have implemented integrated health information systems that allow healthcare providers, hospitals, and clinics to securely share patient data. This capability enables healthcare professionals to access comprehensive medical records, reducing duplication of tests, improving diagnoses, and enhancing patient care.
2. Criminal Justice Information Sharing: Law enforcement agencies often require real-time access to criminal records, arrest warrants, and other relevant information. Data sharing capabilities enable police departments, courts, and correctional facilities to exchange data securely, facilitating faster and more accurate investigations, improved public safety, and efficient case management.
3. Social Services Coordination: Public sector organizations responsible for delivering social services, such as welfare, housing, and employment assistance, often need to share client information to ensure coordinated support. Data sharing capabilities enable these agencies to exchange relevant data securely, ensuring that individuals receive the appropriate services and reducing administrative burdens.
4. Emergency Management and Response: During emergencies or natural disasters, multiple government agencies and organizations need to collaborate and share critical information in real-time. Data sharing capabilities enable emergency management agencies, first responders, and other stakeholders to exchange data on incident status, resource availability, and public safety alerts, facilitating effective response and coordination.
5. Open Data Initiatives: Some public sector organizations have embraced open data initiatives, making certain non-sensitive government data available to the public. Data sharing capabilities enable the publication and dissemination of datasets, fostering transparency, innovation, and public engagement. Examples include publishing crime statistics, transportation data, or environmental information for citizens, researchers, and businesses to utilize.
These examples illustrate how the Data Sharing Digital Business Capability in the public sector can enhance collaboration, decision-making, and service delivery across various domains.
Publisher: EIRA Team
LOST view: OV-Data Spaces [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/DataSharingCapability
EIRA traceability: eira:DigitalBusinessCapability
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-07-10
dct:identifier: http://data.europa.eu/dr8/egovera/DataSharingCapability
dct:title: Data Sharing Digital Business Capability
Description: Digital Procurement enables the electronic end-to-end management of the purchasing process and related tasks associated to the acquisition of third-party goods and/or services through digital means and information and communication technologies.
Additional information: The Digital Procurement Digital Business Capability (DP-DBC) is a comprehensive framework and set of practices aimed at enhancing the efficiency, transparency, and interoperability of procurement processes within the European Union (EU). It focuses on leveraging digital technologies to streamline procurement activities and promote collaboration between member states and private companies.
The primary objective of the DP-DBC is to establish a standardized and harmonized digital procurement ecosystem across the EU, enabling seamless communication and data exchange between member states and private entities. It encompasses various aspects of procurement, including sourcing, tendering, contracting, invoicing, and supplier management.
One of the key elements of the DP-DBC is the development and implementation of interoperable IT systems and platforms. These systems facilitate the exchange of procurement-related information and data between different stakeholders, such as government agencies, public authorities, and private companies. The interoperability ensures that information can be shared and understood consistently, regardless of the specific IT systems used by each entity.
To achieve this interoperability, the DP-DBC promotes the adoption of common data standards, formats, and protocols. These standards enable seamless integration and data exchange between disparate IT systems, eliminating the need for manual data entry and reducing errors and inefficiencies. They also ensure that procurement-related data can be easily accessed, analyzed, and shared across member states and private companies, fostering transparency and collaboration.
Furthermore, the DP-DBC emphasizes the use of digital signatures and electronic identification mechanisms to authenticate and secure procurement transactions. These technologies enable the creation of legally binding contracts and ensure the integrity and confidentiality of sensitive procurement information. By leveraging digital signatures and electronic identification, member states and private companies can streamline the procurement process, reduce paperwork, and enhance security.
The DP-DBC also encompasses the establishment of centralized procurement portals and platforms at both the national and EU levels. These portals serve as a single point of access for procurement-related information, allowing suppliers to find and participate in tendering processes across member states. The portals provide standardized templates, guidelines, and documentation, simplifying the procurement process for both buyers and suppliers.
Moreover, the DP-DBC promotes the use of advanced analytics and artificial intelligence (AI) technologies to improve procurement decision-making and performance. By analyzing large volumes of procurement data, AI algorithms can identify patterns, trends, and potential risks, enabling more informed and strategic procurement decisions. These technologies also support the automation of routine procurement tasks, freeing up resources and enabling procurement professionals to focus on value-added activities.
In summary, the Digital Procurement Digital Business Capability aims to enhance the European IT interoperability among member states and private companies by leveraging digital technologies, establishing common data standards, promoting secure authentication mechanisms, creating centralized procurement portals, and utilizing advanced analytics and AI. By adopting this capability, the EU seeks to streamline procurement processes, increase transparency, and foster collaboration in the procurement ecosystem.
Example: The application of Digital Procurement Digital Business Capability in the context of European IT interoperability among member states and private companies can have several examples. Here are a few:
1. E-procurement platforms: Digital procurement capabilities can be utilized to develop and implement e-procurement platforms at the European level. These platforms can enable member states and private companies to streamline their procurement processes, share information, and collaborate more efficiently.
2. Standardization of procurement processes: Digital procurement capabilities can be used to establish standardized procurement processes across member states and private companies. This can ensure consistency, transparency, and interoperability in procurement activities, making it easier for organizations to work together and exchange information.
3. Electronic document exchange: Digital procurement capabilities can facilitate the electronic exchange of procurement-related documents, such as requests for proposals (RFPs), bids, contracts, and invoices. This can eliminate the need for paper-based processes, reduce administrative burden, and enable seamless communication between member states and private companies.
4. Data analytics and reporting: Digital procurement capabilities can enable the collection, analysis, and reporting of procurement data at the European level. This can provide valuable insights into procurement trends, performance, and compliance, helping member states and private companies make informed decisions and improve their procurement practices.
5. Supplier management and collaboration: Digital procurement capabilities can support the management and collaboration with suppliers across member states and private companies. This can include features like supplier onboarding, performance evaluation, and contract management, ensuring a more efficient and effective supplier relationship management process.
6. Integration with existing systems: Digital procurement capabilities can be integrated with existing IT systems used by member states and private companies. This integration can enable seamless data exchange, interoperability, and process automation, reducing manual effort and enhancing overall efficiency.
Overall, the application of Digital Procurement Digital Business Capability can significantly improve the European IT interoperability among member states and private companies, leading to enhanced collaboration, efficiency, and transparency in procurement processes.
Publisher: European Commission
Source: https://ec.europa.eu/growth/single-market/public-procurement/digital-procurement_it
LOST view: Organisational view [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/DigitalProcurementCapability
EIRA traceability: eira:DigitalBusinessCapability
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-06-06
dct:identifier: http://data.europa.eu/dr8/egovera/DigitalProcurementCapability
dct:title: Digital Procurement Digital Business Capability
Description: The 'Compliance requirements checks' digital business capability refers to the ability of a business to effectively and efficiently ensure that all its digital operations, processes, and transactions are in line with the relevant legal, regulatory, and industry standards. This capability involves the use of digital tools and systems to monitor, evaluate, and report on the level of compliance, identify any areas of non-compliance, and implement necessary corrective actions. It is crucial for mitigating risks, avoiding penalties, maintaining a good reputation, and fostering trust among stakeholders.
Additional information: 'Compliance requirements checks' is a digital business capability that involves the use of technology and digital tools to ensure that an organization is adhering to all relevant laws, regulations, standards, and ethical practices. This capability is critical in maintaining the integrity and reputation of the business, as well as avoiding legal penalties and financial losses.
This capability encompasses several activities. Firstly, it involves the identification and interpretation of applicable regulations and standards. This requires a deep understanding of the legal and regulatory environment in which the business operates, as well as the specific requirements of each regulation or standard.
Once the relevant regulations and standards have been identified, the next step is to assess the current state of compliance within the organization. This involves conducting audits and inspections, reviewing documentation and records, and interviewing staff and management. The aim is to identify any areas of non-compliance and to understand the reasons for these.
The 'Compliance requirements checks' capability also includes the development and implementation of action plans to address areas of non-compliance. This may involve changes to business processes, systems, or culture. It may also involve training and education for staff and management.
Finally, this capability involves ongoing monitoring and reporting on compliance. This includes regular audits and inspections, as well as the use of digital tools to track compliance in real-time. It also involves reporting on compliance to internal and external stakeholders, including regulators, customers, and the public.
In summary, the 'Compliance requirements checks' digital business capability is about using technology and digital tools to ensure that an organization is meeting all of its legal and ethical obligations. It is a critical capability for any business that wants to maintain its integrity and reputation, avoid legal penalties and financial losses, and build trust with its stakeholders.
Example: 1. Tax Compliance Checks: Government tax agencies, like the IRS in the United States, use digital capabilities to check if individuals and businesses are complying with tax laws. This includes verifying the accuracy of tax returns, checking for tax evasion, and ensuring timely payment of taxes.
2. Health and Safety Compliance Checks: Public health departments use digital systems to monitor compliance with health and safety regulations. For example, they may use digital tools to track restaurant inspections, monitor the spread of infectious diseases, or ensure hospitals are following proper protocols.
3. Environmental Compliance Checks: Environmental agencies use digital capabilities to monitor compliance with environmental regulations. This could include tracking emissions from factories, monitoring water quality, or ensuring compliance with waste disposal regulations.
4. Education Compliance Checks: Education departments may use digital systems to ensure schools are complying with education standards and regulations. This could include monitoring student performance, tracking teacher qualifications, or ensuring schools are providing required services for students with disabilities.
5. Data Protection Compliance Checks: With the advent of GDPR and other data protection laws, public sector organizations are required to ensure they are handling and storing data in compliance with these laws. Digital capabilities allow for automated checks and balances to ensure compliance.
6. Public Transportation Compliance Checks: Public transportation departments may use digital systems to monitor compliance with transportation regulations. This could include tracking vehicle maintenance, monitoring driver hours, or ensuring compliance with safety regulations.
7. Social Services Compliance Checks: Social service departments may use digital capabilities to ensure that benefits are being distributed in accordance with laws and regulations. This could include tracking benefit disbursements, monitoring for fraud, or ensuring services are being provided to eligible individuals.
Publisher: EIRA Team
LOST view: OV-Compliance requirements checks [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/ComplianceRequirementsChecksCapability
EIRA traceability: eira:DigitalBusinessCapability
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-08-08
dct:identifier: http://data.europa.eu/dr8/egovera/ComplianceRequirementsChecksCapability
dct:title: Compliance requirements checks (DBC)
Definition: Multimedia Management enables the supervision, creation, distribution and publishing of multimedia content (text, audio and video) through digital means across and outside an organisation. This capability includes document management activities and processes.
Source: Gartner
Source reference: https://www.gartner.com/en/information-technology/glossary/mm-multimedia
Additional information: The Multimedia Management Digital Business Capability (MMDBC) is a comprehensive framework that aims to facilitate and enhance the interoperability of multimedia content and services within the European Union (EU). It specifically focuses on promoting seamless communication and collaboration between member states and private companies in the field of information technology (IT).
The MMDBC recognizes the increasing importance of multimedia content and services in today's digital age. It encompasses various aspects of multimedia management, including the creation, storage, retrieval, distribution, and consumption of multimedia content. By establishing a standardized approach to managing multimedia, the MMDBC aims to streamline processes, improve efficiency, and foster innovation in the European IT industry.
One of the primary objectives of the MMDBC is to ensure interoperability among member states and private companies. Interoperability refers to the ability of different systems, applications, and devices to seamlessly exchange and use information. In the context of the MMDBC, interoperability is crucial for enabling the smooth flow of multimedia content and services across borders and between different organizations.
To achieve interoperability, the MMDBC promotes the adoption of common standards, protocols, and frameworks. These standards ensure that multimedia content can be accessed, shared, and utilized by various stakeholders, regardless of their location or technical infrastructure. By adhering to these standards, member states and private companies can avoid compatibility issues and ensure the seamless integration of their multimedia systems and services.
The MMDBC also emphasizes the importance of data governance and management. It recognizes that multimedia content often contains sensitive or personal information, and therefore, it is essential to establish robust data protection and privacy measures. This includes complying with relevant EU regulations, such as the General Data Protection Regulation (GDPR), to safeguard the rights and privacy of individuals.
Furthermore, the MMDBC encourages collaboration and knowledge sharing among member states and private companies. It promotes the establishment of networks, forums, and communities of practice where stakeholders can exchange best practices, experiences, and lessons learned. This collaborative approach helps foster innovation, drive technological advancements, and address common challenges in the field of multimedia management.
In summary, the Multimedia Management Digital Business Capability is a comprehensive framework that aims to enhance the interoperability of multimedia content and services within the European IT industry. It promotes the adoption of common standards, data governance practices, and collaboration among member states and private companies. By doing so, the MMDBC seeks to facilitate seamless communication, improve efficiency, and foster innovation in the European IT interoperability landscape.
Example: The application of Multimedia Management Digital Business Capability in the context of European IT interoperability among member states and private companies can have several examples. Here are a few:
1. Cross-border data sharing: Multimedia Management can facilitate the seamless sharing of multimedia content, such as images, videos, and audio files, across different member states and private companies. This capability ensures that multimedia content can be accessed and utilized efficiently, regardless of the location or organizational boundaries.
2. Standardization of multimedia formats: Multimedia Management can help establish common standards for multimedia formats, ensuring compatibility and interoperability among different systems and platforms used by member states and private companies. This capability enables the smooth exchange and integration of multimedia content across various IT systems.
3. Collaborative multimedia projects: Multimedia Management can support collaborative projects involving member states and private companies by providing tools and platforms for sharing, editing, and managing multimedia content. This capability allows multiple stakeholders to work together on multimedia-intensive initiatives, such as joint research projects or cross-border marketing campaigns.
4. Digital asset management: Multimedia Management can enable efficient storage, retrieval, and organization of multimedia assets for member states and private companies. This capability ensures that valuable multimedia resources, such as marketing materials, training videos, or public information campaigns, are easily accessible and can be effectively managed across different IT environments.
5. Multimedia analytics and insights: Multimedia Management can leverage advanced analytics techniques to extract valuable insights from multimedia content. This capability can help member states and private companies gain a deeper understanding of user preferences, sentiment analysis, or multimedia consumption patterns, enabling them to make data-driven decisions and enhance their services or products.
Overall, the application of Multimedia Management Digital Business Capability in the European IT interoperability context can enhance collaboration, standardization, and efficiency in managing multimedia content across member states and private companies.
LOST view: Organisational view
Identifier: http://data.europa.eu/dr8/egovera/MultimediaManagementCapability
ABB name: eira:MultimediaManagementCapability
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/egovera/MultimediaManagementCapability
Name: Multimedia Management Digital Business Capability
Interoperability Layer: Organisational
Specialises: http://data.europa.eu/dr8/DigitalBusinessCapability
Definition: Data Management is the development, execution, and supervision of plans, policies, prograns, and practices that deliver, control, protect, and enhance the value of data and information assets throughout their lifecycles.
Source: DAMA
Source reference: https://damadach.org/dmbok2-dama-dmbok-version-2/
Additional information: The Data Management Digital Business Capability in the context of European IT interoperability among member states and private companies refers to the ability to effectively and efficiently handle data in a digital environment while ensuring seamless communication, collaboration, and integration between various entities.
In the European Union, where multiple member states and private companies operate, it is crucial to establish a robust data management capability to facilitate interoperability. This capability encompasses various aspects, including data governance, data quality, data integration, data security, and data analytics.
Data governance involves defining policies, procedures, and guidelines for managing data across different entities. It includes establishing data standards, ensuring compliance with regulations such as the General Data Protection Regulation (GDPR), and defining roles and responsibilities for data management.
Data quality focuses on ensuring that data is accurate, complete, consistent, and reliable. It involves implementing data validation processes, data cleansing techniques, and data profiling to identify and rectify any inconsistencies or errors in the data.
Data integration is a critical aspect of interoperability, as it involves combining data from different sources and formats to provide a unified view. This capability enables seamless data exchange between member states and private companies, allowing them to share information and collaborate effectively. It may involve implementing data integration technologies such as application programming interfaces (APIs), data warehouses, or data lakes.
Data security is of paramount importance in the digital business environment, especially when dealing with sensitive information. It involves implementing robust security measures, such as encryption, access controls, and data masking, to protect data from unauthorized access, breaches, or misuse. Compliance with data protection regulations, such as GDPR, is essential to ensure the privacy and security of personal data.
Data analytics plays a crucial role in extracting valuable insights from the vast amount of data generated. It involves using advanced analytics techniques, such as data mining, machine learning, and artificial intelligence, to analyze data and derive meaningful patterns, trends, and predictions. This capability enables member states and private companies to make informed decisions, optimize processes, and drive innovation.
To achieve effective data management digital business capability for European IT interoperability, collaboration and standardization are key. Member states and private companies need to establish common data models, formats, and protocols to ensure seamless data exchange. They should also promote the use of interoperability frameworks, such as the European Interoperability Framework (EIF), which provides guidelines and best practices for achieving interoperability.
Furthermore, investing in modern technologies and infrastructure, such as cloud computing, big data platforms, and data governance tools, can significantly enhance the data management capability. Training and upskilling the workforce in data management and analytics are also crucial to ensure the successful implementation and utilization of the capability.
In summary, the Data Management Digital Business Capability for European IT interoperability among member states and private companies encompasses various aspects of data governance, data quality, data integration, data security, and data analytics. It aims to establish a robust and standardized approach to managing data, enabling seamless communication, collaboration, and integration in the digital business environment.
Example: The application of Data Management Digital Business Capability in the context of European IT interoperability among member states and private companies can be seen in various ways. Here are a few examples:
1. Data Sharing and Exchange: The capability enables member states and private companies to securely share and exchange data across borders. For instance, in the healthcare sector, interoperability allows patient data to be seamlessly shared between different healthcare providers, ensuring continuity of care for patients who may seek treatment in different countries.
2. Harmonization of Data Standards: Data Management Digital Business Capability helps in establishing common data standards and formats, ensuring consistency and compatibility between different IT systems used by member states and private companies. This harmonization facilitates smooth data exchange and integration, reducing barriers to interoperability.
3. Cross-Border Data Governance: The capability assists in defining and implementing cross-border data governance frameworks, including data protection and privacy regulations. This ensures that data is managed and protected in a consistent and compliant manner across member states and private companies, fostering trust and confidence in data sharing.
4. Data Integration and Analytics: Interoperability allows for the integration of data from various sources, enabling advanced analytics and insights. For example, in the transportation sector, interoperability enables the integration of data from different transport systems, leading to better traffic management, optimized routes, and improved passenger experience.
5. Cross-Domain Collaboration: Data Management Digital Business Capability facilitates collaboration between member states and private companies across different domains. For instance, in the energy sector, interoperability enables the integration of data from renewable energy sources, grid operators, and consumers, supporting efficient energy management and promoting the use of sustainable energy.
6. Real-time Data Exchange: Interoperability enables real-time data exchange between member states and private companies, allowing for timely decision-making and response. This is particularly crucial in emergency situations, where quick access to accurate data can help in coordinating response efforts and minimizing the impact of disasters.
Overall, the application of Data Management Digital Business Capability in European IT interoperability among member states and private companies enhances data sharing, standardization, governance, integration, and collaboration, leading to improved efficiency, innovation, and cross-border cooperation.
LOST view: Organisational view
Identifier: http://data.europa.eu/dr8/egovera/DataManagementCapability
ABB name: eira:DataManagementCapability
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/egovera/DataManagementCapability
Name: Data Management Digital Business Capability
Interoperability Layer: Organisational
Specialises: http://data.europa.eu/dr8/DigitalBusinessCapability
Definition: Digital Business Capability ABB is a Capability, that corresponds to an ability implemented in a system to enable a public administrations to perform an administrative function.
Source: European Statistical System
Source reference: https://joinup.ec.europa.eu/collection/statistical-enterprise-architecture/document/ess-earf-business-capabilities-model
Additional information: The Digital Business capability enable public administations to performadministrative functions inthe framework of e-governance.
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): ePrescription: "Generation, transmission, and filling of a medical prescription through digital channels. ePrescribing allows a physician, pharmacist, nurse practitioner, or physician assistant to use digital prescription software to electronically transmit a new prescription or renewal authorization to a community or mail-order pharmacy".
Interoperability Dimension: Structural IoP
LOST view: Organisational view
Viewpoint: Highlevel viewpoint
Interoperability Saliency: Digital Business Capability ABB is salient for organizational interoperability because it determines the core business functions and operations of public administration services. This ABB ensures the coordination of public systems to make a response to specific procedures.
Identifier: http://data.europa.eu/dr8/DigitalBusinessCapabilityCapability
ABB name: eira:DigitalBusinessCapabilityCapability
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/DigitalBusinessCapabilityCapability
Interoperability Layer: Organisational
Description: The 'Preservation of Cargo Information' digital business capability refers to the ability of a business, particularly in the logistics and supply chain industry, to effectively store, manage, and maintain information related to cargo. This includes details about the cargo's content, origin, destination, handling requirements, and tracking information. This capability ensures that all relevant data is accurately recorded and preserved in a digital format, allowing for easy access, retrieval, and analysis. It is crucial for operational efficiency, regulatory compliance, and providing transparency to customers.
Additional information: The 'Preservation of Cargo Information' digital business capability refers to the ability of a business, specifically within the logistics, shipping, or supply chain industry, to effectively capture, store, manage, and protect all relevant information related to cargo. This includes data about the cargo's nature, quantity, destination, origin, handling requirements, and transportation details.
This capability involves the use of digital technologies and systems to ensure that cargo information is accurately recorded and preserved over time. It may involve the use of databases, cloud storage solutions, and other digital tools to maintain a comprehensive and accessible record of cargo information.
The capability also includes ensuring the security and integrity of this information, protecting it from loss, damage, unauthorized access, or other threats. This may involve the use of encryption, access controls, backup systems, and other security measures.
Furthermore, the 'Preservation of Cargo Information' capability also implies the ability to retrieve and use this information effectively. This may involve providing access to relevant stakeholders, integrating with other systems for data analysis and decision-making, and ensuring compliance with relevant regulations and standards for data management and privacy.
In essence, this capability is crucial for businesses in the logistics and supply chain industry as it enables them to track and manage their cargo effectively, ensure compliance, make informed decisions, and provide a high level of service to their customers.
Example: 1. National Postal Services: Postal services often have digital systems in place to track and preserve information about the cargo they handle. This includes details about the sender, recipient, the type of cargo, its weight, and its journey through the postal system.
2. Customs and Border Protection: In many countries, customs and border protection agencies use digital systems to preserve information about cargo entering and leaving the country. This includes details about the cargo's origin, destination, contents, and value.
3. Public Transport Authorities: Public transport authorities may use digital systems to track and preserve information about cargo transported on public transport networks. This could include details about the cargo's origin, destination, and journey through the network.
4. Public Health Agencies: Public health agencies may use digital systems to preserve information about medical supplies and other cargo. This could include details about the cargo's origin, destination, contents, and storage requirements.
5. Disaster Management Agencies: These agencies often use digital systems to track and preserve information about relief supplies and other cargo. This includes details about the cargo's origin, destination, contents, and the people or areas it is intended to help.
6. Space Agencies: Agencies like NASA use digital systems to preserve information about cargo sent to space. This includes details about the cargo's origin, contents, destination, and journey.
7. Public Libraries: Libraries often use digital systems to track and preserve information about books and other items in their collections, which can be considered a type of cargo.
8. Department of Defense: Military departments use digital systems to track and preserve information about military supplies and equipment, including their origin, destination, contents, and storage requirements.
Publisher: EIRA Team
LOST view: OV-Customs DBCs, DPSs and Information [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/PreservationOfCargoInformationCapability
EIRA traceability: eira:DigitalBusinessCapability
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-08-08
dct:identifier: http://data.europa.eu/dr8/egovera/PreservationOfCargoInformationCapability
dct:title: Preservation of cargo information (DBC)
Description: The 'MS' Customs Organization Management' Digital Business Capability refers to the ability of the customs organization to leverage digital technologies to manage its operations effectively. This includes the use of digital tools and platforms for tasks such as data management, communication, process automation, and decision-making. It also involves the ability to adapt to changes in the digital landscape, such as new technologies or digital trends. This capability is crucial for improving efficiency, enhancing service delivery, and ensuring compliance with customs regulations.
Additional information: 'MS' Customs Organization Management' Digital Business Capability refers to the ability of a customs organization, presumably named 'MS', to manage its operations, services, and resources effectively and efficiently through digital means. This capability encompasses a broad range of digital competencies and functionalities, including but not limited to:
1. Digital Infrastructure Management: This involves the ability to manage the organization's digital infrastructure, including hardware, software, networks, and data centers, to ensure they are secure, reliable, and capable of supporting the organization's operations and services.
2. Digital Service Delivery: This refers to the ability to deliver services to customers, partners, and other stakeholders through digital channels. This may include online customs declaration and payment systems, digital document management systems, and other digital services.
3. Digital Resource Management: This involves the ability to manage the organization's resources, including human resources, financial resources, and physical assets, through digital means. This may include digital HR systems, digital financial management systems, and digital asset management systems.
4. Digital Data and Information Management: This refers to the ability to manage the organization's data and information effectively and efficiently through digital means. This may include digital data management systems, digital information management systems, and digital analytics systems.
5. Digital Security Management: This involves the ability to manage the organization's digital security, including the security of its digital infrastructure, digital services, digital resources, and digital data and information. This may include digital security systems, digital risk management systems, and digital compliance management systems.
6. Digital Transformation and Innovation: This refers to the ability to drive digital transformation and innovation in the organization. This may involve the use of digital technologies to transform the organization's operations and services, to innovate new products and services, and to create new business models and strategies.
7. Digital Governance: This involves the ability to govern the organization's digital capabilities, including the setting of digital policies and standards, the monitoring of digital performance, and the management of digital risks and compliance.
In essence, 'MS' Customs Organization Management' Digital Business Capability is about leveraging digital technologies to enhance the organization's ability to deliver its mission and achieve its goals. This requires a holistic approach that integrates digital capabilities across all aspects of the organization's operations and services.
Example: 1. Digital Document Management: The MS Customs organization may have a digital document management system that allows for the efficient storage, retrieval, and management of all customs-related documents. This can include customs declarations, shipping documents, and other related paperwork.
2. Online Customs Declaration: A digital business capability of the MS Customs organization could be an online platform where businesses and individuals can submit their customs declarations. This can streamline the process, reduce paperwork, and make it easier for people to comply with customs regulations.
3. Automated Risk Assessment: The organization may use advanced analytics and machine learning algorithms to assess the risk level of different shipments. This can help to identify potential issues before they become problems, and allow for more efficient allocation of resources.
4. Digital Payment Systems: The MS Customs organization may have a digital payment system that allows for the easy payment of customs duties and taxes. This can make the process more convenient for businesses and individuals, and also reduce the administrative burden on the customs organization.
5. Real-Time Tracking: The organization may have a system that allows for real-time tracking of shipments as they pass through customs. This can provide valuable information to businesses and individuals, and also help the customs organization to manage its operations more effectively.
6. E-Learning Platform: The MS Customs organization may have an e-learning platform that provides training and education on customs regulations and procedures. This can help to ensure that businesses and individuals are aware of their responsibilities and can comply with customs regulations.
7. Customer Relationship Management (CRM): The organization may use a CRM system to manage its relationships with businesses and individuals. This can help to improve customer service, and also provide valuable data that can be used to improve operations and decision-making.
Publisher: EIRA Team
LOST view: OV-MS' Customs organization management [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/MSCustomsOrganizationManagementCapability
EIRA traceability: eira:DigitalBusinessCapability
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-08-08
dct:identifier: http://data.europa.eu/dr8/egovera/MSCustomsOrganizationManagementCapability
dct:title: MS' Customs organization management (DBC)
Description: The Data Quality Digital Business Capability refers to the organization's ability to ensure the accuracy, consistency, and reliability of its data assets. It involves implementing processes, tools, and techniques to monitor, measure, and improve the quality of data across various systems and applications. This capability enables the organization to make informed decisions, drive operational efficiency, and enhance customer satisfaction by ensuring that data is complete, valid, and up-to-date. It also involves establishing data governance frameworks and standards to ensure data quality is maintained throughout its lifecycle.
Additional information: The Data Quality Digital Business Capability refers to an organization's ability to effectively manage and maintain the quality of its data assets. It encompasses the processes, tools, and techniques employed to ensure that data is accurate, complete, consistent, and reliable throughout its lifecycle.
This capability involves various activities such as data profiling, data cleansing, data validation, and data enrichment. Data profiling involves analyzing and assessing the quality of data by examining its structure, content, and relationships. It helps identify data anomalies, inconsistencies, and errors that may impact the overall quality.
Data cleansing involves the removal or correction of errors, duplicates, and inconsistencies within the data. It includes activities like standardization, normalization, and deduplication to ensure data integrity and consistency. Data validation ensures that data meets predefined quality standards and business rules, preventing the entry of incorrect or incomplete information.
Data enrichment involves enhancing the quality of data by adding additional attributes or information from external sources. This process helps improve the accuracy, completeness, and relevance of data, enabling better decision-making and analysis.
The Data Quality Digital Business Capability also encompasses the establishment of data governance frameworks and policies. This involves defining roles, responsibilities, and processes for data quality management, ensuring accountability and ownership of data across the organization. It includes the development and implementation of data quality metrics, monitoring mechanisms, and reporting mechanisms to measure and track data quality performance.
Furthermore, this capability involves the integration of data quality practices into various business processes and systems. It requires collaboration between business stakeholders, data stewards, and IT teams to ensure that data quality requirements are understood, implemented, and maintained throughout the data lifecycle.
The Data Quality Digital Business Capability is crucial for organizations as it enables them to make informed decisions, improve operational efficiency, and enhance customer satisfaction. It helps organizations avoid costly errors, reduce risks, and comply with regulatory requirements. By ensuring high-quality data, organizations can gain a competitive edge, drive innovation, and achieve their strategic objectives.
Example: The Data Quality Digital Business Capability in the public sector refers to the ability to ensure the accuracy, completeness, consistency, and reliability of data used within an organization. Here are some real examples of this capability in the public sector:
1. Data Validation and Cleansing: Public sector organizations often deal with large volumes of data collected from various sources. The capability to validate and cleanse this data ensures that it is accurate and reliable. For example, a government agency may implement automated data validation processes to identify and correct errors in citizen records, ensuring accurate delivery of public services.
2. Data Governance and Standards: Public sector organizations need to establish data governance frameworks and standards to ensure data quality. This includes defining data ownership, roles, and responsibilities, as well as establishing data quality metrics and monitoring processes. For instance, a municipality may implement data governance policies to ensure consistent and reliable data across different departments, enabling effective decision-making.
3. Data Integration and Interoperability: Public sector entities often have multiple systems and databases that need to exchange data seamlessly. The capability to integrate and ensure interoperability between these systems helps maintain data quality. For example, a national healthcare system may implement data integration solutions to enable real-time sharing of patient information between hospitals, ensuring accurate and up-to-date medical records.
4. Data Quality Monitoring and Reporting: Public sector organizations need to continuously monitor and report on data quality to identify and address issues promptly. This capability involves implementing tools and processes to measure data quality against predefined metrics and generate reports. For instance, a tax authority may establish data quality monitoring mechanisms to identify discrepancies in taxpayer records, enabling timely corrective actions.
5. Data Privacy and Security: Ensuring data privacy and security is crucial in the public sector, where sensitive citizen information is often handled. The capability to implement robust data privacy and security measures helps maintain data quality by protecting against unauthorized access, breaches, or data manipulation. For example, a government agency may implement encryption and access control mechanisms to safeguard citizen data, ensuring its integrity and confidentiality.
These examples demonstrate how the Data Quality Digital Business Capability can be applied in the public sector to ensure accurate, reliable, and secure data, enabling effective decision-making and efficient delivery of public services.
Publisher: EIRA Team
LOST view: OV-Data Spaces [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/DataQualityCapability
EIRA traceability: eira:DigitalBusinessCapability
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-07-10
dct:identifier: http://data.europa.eu/dr8/egovera/DataQualityCapability
dct:title: Data Quality Digital Business Capability
Description: The Data Interoperability Digital Business Capability refers to the ability of an organization to seamlessly exchange and integrate data across different systems, applications, and platforms. It involves the implementation of standardized data formats, protocols, and interfaces to ensure smooth data flow and interoperability between various data sources and consumers. This capability enables organizations to efficiently share and utilize data, leading to improved collaboration, decision-making, and overall operational efficiency.
Additional information: The Data Interoperability Digital Business Capability refers to the ability of an organization to seamlessly exchange and integrate data across various systems, applications, and platforms. It involves the establishment of standardized data formats, protocols, and interfaces to enable efficient and effective data sharing and collaboration.
This capability encompasses the ability to overcome the challenges associated with data heterogeneity, inconsistency, and incompatibility. It involves the development and implementation of data integration strategies, technologies, and frameworks to ensure that data can be easily understood, accessed, and utilized by different systems and stakeholders.
The Data Interoperability Digital Business Capability involves several key components and activities:
1. Data Integration: This involves the consolidation and integration of data from disparate sources, such as databases, applications, and external systems. It includes the extraction, transformation, and loading (ETL) processes to ensure that data is cleansed, standardized, and made compatible with the target systems.
2. Data Mapping and Transformation: This component focuses on defining and implementing mappings between different data formats, structures, and schemas. It involves the conversion of data from one format to another, ensuring that data can be effectively exchanged and understood by different systems.
3. Data Governance: This aspect involves the establishment of policies, standards, and guidelines for data management and interoperability. It includes defining data quality requirements, data ownership, and data security measures to ensure that data is accurate, reliable, and protected during its exchange and integration.
4. Data Exchange Protocols and Standards: This component involves the adoption and implementation of industry-standard protocols and formats for data exchange. Examples include XML, JSON, RESTful APIs, and web services. These standards enable seamless communication and interoperability between different systems and platforms.
5. Data Security and Privacy: This capability also encompasses ensuring the security and privacy of data during its exchange and integration. It involves implementing encryption, access controls, and data anonymization techniques to protect sensitive information and comply with relevant regulations and policies.
6. Data Analytics and Insights: This component focuses on leveraging the integrated data to derive meaningful insights and support data-driven decision-making. It involves the use of data analytics tools and techniques to extract valuable information, identify patterns, and uncover trends from the integrated data.
Overall, the Data Interoperability Digital Business Capability plays a crucial role in enabling organizations to leverage the full potential of their data assets. It facilitates seamless data exchange, integration, and collaboration, leading to improved operational efficiency, enhanced decision-making, and the ability to quickly respond to changing business needs.
Example: The Data Interoperability Digital Business Capability in the public sector refers to the ability to seamlessly exchange and integrate data across different systems and organizations. Here are some real examples of this capability in action:
1. Open Data Initiatives: Many governments have launched open data initiatives to make public sector data more accessible and usable by citizens, businesses, and other government agencies. By ensuring data interoperability, these initiatives allow different systems and applications to exchange data in standardized formats, enabling the development of innovative solutions and services.
2. Integrated Health Information Systems: In the healthcare sector, data interoperability is crucial for sharing patient information across different healthcare providers, hospitals, and clinics. Integrated health information systems enable healthcare professionals to access and exchange patient data securely, leading to improved care coordination, reduced medical errors, and better health outcomes.
3. Smart Cities: Data interoperability plays a vital role in the development of smart cities. By integrating data from various sources such as transportation, energy, public safety, and environmental sensors, cities can optimize resource allocation, improve traffic management, enhance public services, and make data-driven decisions for urban planning and development.
4. Cross-Agency Collaboration: In the public sector, different government agencies often need to collaborate and share data to deliver efficient and effective services. Data interoperability enables seamless data exchange between agencies, facilitating information sharing, joint decision-making, and coordinated service delivery. For example, in disaster management, multiple agencies need to exchange data on weather conditions, emergency response plans, and resource availability to ensure a coordinated and timely response.
5. E-Government Services: Governments worldwide are digitizing their services to provide citizens with convenient and accessible online platforms. Data interoperability is essential for integrating data from various government departments and agencies to offer seamless e-government services. For instance, citizens can access a single portal to apply for licenses, pay taxes, register for social benefits, and access other government services, with the underlying data being interoperable across different systems.
These examples demonstrate how the Data Interoperability Digital Business Capability enables efficient data exchange and integration, leading to improved decision-making, enhanced services, and better collaboration in the public sector.
Publisher: EIRA Team
LOST view: OV-Data Spaces [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/DataInteroperabilityCapability
EIRA traceability: eira:DigitalBusinessCapability
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-07-10
dct:identifier: http://data.europa.eu/dr8/egovera/DataInteroperabilityCapability
dct:title: Data Interoperability Digital Business Capability
Description: The Data Security Digital Business Capability refers to the ability of an organization to protect its digital assets and sensitive information from unauthorized access, use, disclosure, disruption, modification, or destruction. This capability encompasses the implementation of robust security measures, such as encryption, access controls, firewalls, intrusion detection systems, and security policies, to safeguard data and ensure compliance with regulatory requirements. It also involves the establishment of incident response plans and continuous monitoring to detect and mitigate potential security threats. By effectively managing data security, organizations can maintain the confidentiality, integrity, and availability of their digital assets, build trust with customers, and mitigate the risks associated with cyber threats.
Additional information: The Data Security Digital Business Capability refers to the ability of an organization to protect its data assets from unauthorized access, use, disclosure, disruption, modification, or destruction. It encompasses the processes, technologies, and practices employed to ensure the confidentiality, integrity, and availability of data throughout its lifecycle.
This capability involves the implementation of various security measures, controls, and safeguards to mitigate risks associated with data breaches, cyber threats, and compliance requirements. It aims to establish a secure environment that instills trust and confidence in stakeholders, including customers, partners, and employees.
Key components of the Data Security Digital Business Capability include:
1. Data Classification and Governance: This involves the identification and categorization of data based on its sensitivity, value, and regulatory requirements. It includes defining data ownership, access controls, and data retention policies.
2. Access Control and Authentication: This capability ensures that only authorized individuals or systems can access specific data. It involves implementing strong authentication mechanisms, such as multi-factor authentication, and role-based access controls to limit access to sensitive data.
3. Encryption and Data Protection: Data encryption is a crucial aspect of data security. This capability involves encrypting data at rest, in transit, and in use to prevent unauthorized access. It also includes implementing data loss prevention (DLP) solutions and data masking techniques to protect sensitive information.
4. Threat Detection and Incident Response: This capability focuses on monitoring and detecting potential security threats and incidents. It involves implementing intrusion detection and prevention systems, security information and event management (SIEM) tools, and conducting regular security audits. Incident response plans and procedures are also established to effectively respond to and mitigate security incidents.
5. Security Awareness and Training: This capability emphasizes educating employees and stakeholders about data security best practices, policies, and procedures. It includes conducting regular security awareness training sessions, phishing simulations, and promoting a culture of security awareness and responsibility.
6. Compliance and Regulatory Requirements: Organizations must comply with various data protection regulations and industry standards. This capability involves understanding and adhering to relevant regulations, such as the General Data Protection Regulation (GDPR), Payment Card Industry Data Security Standard (PCI DSS), and Health Insurance Portability and Accountability Act (HIPAA).
7. Security Incident Management and Reporting: This capability focuses on establishing processes and procedures for managing and reporting security incidents. It includes incident response planning, incident investigation, and reporting to relevant stakeholders, regulatory bodies, and law enforcement agencies, if required.
By developing and maintaining a robust Data Security Digital Business Capability, organizations can safeguard their data assets, maintain customer trust, comply with regulations, and mitigate the risks associated with data breaches and cyber threats.
Example: The Data Security Digital Business Capability in the public sector refers to the ability to protect sensitive information and ensure the confidentiality, integrity, and availability of data. Here are some real examples of this capability in action:
1. Secure Data Storage and Encryption: Public sector organizations often deal with large volumes of sensitive data, such as citizen records, financial information, and national security data. Implementing secure data storage solutions with encryption ensures that this information is protected from unauthorized access or breaches.
2. Access Control and Authentication: Public sector entities need to control access to their systems and data to prevent unauthorized use. Implementing robust access control mechanisms, such as multi-factor authentication and role-based access control, helps ensure that only authorized personnel can access sensitive data.
3. Incident Response and Threat Management: Public sector organizations face various cyber threats, including hacking attempts, malware, and phishing attacks. Having a well-defined incident response plan and a dedicated team to handle security incidents is crucial. This capability involves monitoring systems for potential threats, promptly responding to incidents, and implementing measures to mitigate risks.
4. Compliance and Regulatory Requirements: Public sector entities must comply with various data protection regulations and standards, such as the General Data Protection Regulation (GDPR) or the Health Insurance Portability and Accountability Act (HIPAA). The Data Security Digital Business Capability involves establishing processes and controls to ensure compliance with these regulations, including data privacy, consent management, and data breach notification.
5. Security Awareness and Training: Ensuring that employees are aware of data security best practices is essential in the public sector. This capability involves providing regular training and awareness programs to educate staff about potential risks, phishing attacks, social engineering, and other security threats. By promoting a security-conscious culture, organizations can reduce the likelihood of data breaches caused by human error.
6. Secure Data Sharing and Collaboration: Public sector organizations often need to share data securely with external stakeholders, such as other government agencies, law enforcement, or international partners. Implementing secure data sharing platforms and protocols, such as secure file transfer protocols (SFTP) or encrypted communication channels, enables secure collaboration while protecting sensitive information.
These examples demonstrate how the Data Security Digital Business Capability is crucial in the public sector to safeguard sensitive data, maintain public trust, and comply with regulatory requirements.
Publisher: EIRA Team
LOST view: OV-Data Spaces [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/DataSecurityCapability
EIRA traceability: eira:DigitalBusinessCapability
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-07-10
dct:identifier: http://data.europa.eu/dr8/egovera/DataSecurityCapability
dct:title: Data Security Digital Business Capability
Description: 'Customs Cooperation' Digital Business Capability refers to the ability of a business to effectively manage and streamline customs processes through digital means. This includes the use of digital technologies to facilitate communication, collaboration, and information exchange between customs authorities, businesses, and other stakeholders. It also involves leveraging digital tools and platforms to enhance customs procedures, such as the submission and processing of customs declarations, payment of duties and taxes, and compliance with customs regulations. This capability can help businesses to reduce costs, improve efficiency, and ensure compliance in their international trade activities.
Additional information: 'Customs Cooperation' Digital Business Capability refers to the ability of a business to effectively manage, coordinate, and collaborate with customs authorities and other relevant entities through digital means. This capability involves the use of digital technologies to facilitate seamless and efficient customs procedures, compliance with customs regulations, and cross-border trade activities.
This capability encompasses several key elements:
1. Digital Communication: This involves the use of digital platforms for real-time communication and information exchange with customs authorities, trade partners, and other stakeholders. This could include the use of emails, instant messaging, video conferencing, and other digital communication tools.
2. Electronic Documentation: This refers to the ability to create, manage, and submit electronic documents required for customs procedures, such as customs declarations, invoices, and certificates of origin. This helps to reduce paperwork, streamline processes, and improve accuracy and efficiency.
3. Data Integration: This involves the integration of customs data with other business systems and processes. This could include the integration of customs data with supply chain management systems, enterprise resource planning systems, and other business applications.
4. Compliance Management: This refers to the ability to ensure compliance with customs regulations and requirements. This could involve the use of digital tools for tracking and managing customs duties and taxes, ensuring accurate classification of goods, and managing customs audits and inspections.
5. Analytics and Reporting: This involves the use of digital analytics tools to monitor and analyze customs data, generate insights, and support decision-making. This could include the use of dashboards, data visualization tools, and reporting systems.
6. Automation: This refers to the use of digital technologies to automate customs processes, such as the automatic calculation of customs duties and taxes, the automatic submission of customs declarations, and the automatic generation of customs reports.
7. Collaboration: This involves the use of digital platforms for collaboration with customs authorities, trade partners, and other stakeholders. This could include the use of collaborative workspaces, project management tools, and social networking platforms.
By developing and enhancing these digital capabilities, businesses can improve their customs operations, reduce costs, increase efficiency, and enhance compliance with customs regulations.
Example: 1. Customs and Border Protection (CBP) in the United States: CBP uses advanced digital capabilities to facilitate trade and customs cooperation. They use Automated Commercial Environment (ACE), a web-based portal for the collection, processing, and distribution of information related to imported goods. This system allows CBP to effectively manage risk, accelerate the flow of legitimate shipments, and target illicit goods.
2. European Union's Customs Information System (CIS): CIS is a computerized system that allows rapid information exchange between customs authorities within the EU. It helps in preventing, investigating, and prosecuting serious breaches of national laws relating to customs and agricultural matters.
3. Australian Border Force's Integrated Cargo System (ICS): ICS is a web-based system that manages the reporting and clearance of imported and exported goods. It allows for efficient customs cooperation and ensures compliance with Australia's customs and border protection laws.
4. Singapore's Networked Trade Platform (NTP): NTP is a national trade information management platform that provides a single point of access for the trade community. It enables digitalization and seamless data flow, enhancing customs cooperation and efficiency.
5. Canada Border Services Agency's (CBSA) Assessment and Revenue Management (CARM) project: CARM is a multi-year initiative that will transform the collection of duties and taxes for goods imported into Canada. By modernizing and streamlining processes, CARM will provide a more efficient, user-friendly service for the trade community.
6. China Customs' Single Window System: This digital platform integrates and streamlines customs procedures, allowing for efficient data exchange between traders and customs authorities. It enhances customs cooperation and promotes trade facilitation.
Publisher: EIRA Team
LOST view: OV-Customs DBCs, DPSs and Information [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/CustomsCooperationCapability
EIRA traceability: eira:DigitalBusinessCapability
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-08-08
dct:identifier: http://data.europa.eu/dr8/egovera/CustomsCooperationCapability
dct:title: Customs cooperation (DBC)
Description: The 'Guarantee' Digital Business Capability refers to the ability of a business to ensure and uphold the promises made to its customers in a digital context. This includes ensuring the quality of products or services, the security of transactions, and the protection of customer data. It also involves the ability to provide reliable and consistent service, meet delivery commitments, and uphold warranty terms. This capability is crucial in building customer trust and loyalty in the digital business environment.
Additional information: The 'Guarantee' Digital Business Capability refers to the ability of an organization to ensure and uphold the promises made to its customers, stakeholders, and partners in a digital context. This capability involves the use of digital technologies and systems to manage and fulfill guarantees, warranties, and other forms of contractual obligations.
It includes the ability to track and manage guarantee-related information, process guarantee claims, and provide necessary services or compensations. It also involves the ability to analyze guarantee-related data to identify trends, risks, and opportunities, and to improve guarantee policies and processes.
This capability is crucial for maintaining customer trust and satisfaction, managing financial and operational risks, and ensuring regulatory compliance. It requires a combination of technological, operational, and legal expertise, as well as a strong customer focus.
In a broader sense, the 'Guarantee' Digital Business Capability also reflects an organization's commitment to quality, reliability, and accountability in its digital operations and offerings. It is a key aspect of an organization's digital maturity and competitiveness.
Example: 1. Online Tax Filing Systems: Many public sector entities, such as the Internal Revenue Service (IRS) in the United States, have developed online systems that guarantee the ability for citizens to file their taxes digitally. These systems ensure the secure and accurate processing of tax information.
2. Digital Identity Verification: Governments like Estonia have implemented digital ID cards that guarantee citizens' identity in the digital space. This capability allows for secure online transactions and interactions with public services.
3. E-Health Records: Public health departments have developed digital systems to guarantee the secure storage and access of patient health records. For example, the National Health Service (NHS) in the UK uses a digital platform to provide healthcare professionals with access to patient records.
4. Online Voting Systems: Some governments are exploring online voting systems that guarantee citizens the ability to vote digitally in elections. For example, the state of West Virginia in the U.S. experimented with a mobile voting platform during the 2018 midterm elections.
5. Digital Public Procurement Platforms: Governments have developed digital platforms that guarantee transparent and efficient procurement processes. For example, the European Union has a digital platform for public procurement that ensures transparency and equal access to contract opportunities.
6. E-Learning Platforms: Public education departments have implemented e-learning platforms that guarantee access to education resources for students and teachers. For example, the U.S. Department of Education has an online platform that provides resources for distance learning.
7. Digital Social Security Systems: Governments have developed digital systems to guarantee the delivery of social security benefits. For example, the Social Security Administration in the U.S. has an online system that allows citizens to apply for and manage their benefits.
8. Online Immigration Services: Immigration departments have developed online systems that guarantee the ability for individuals to apply for visas, work permits, and citizenship. For example, the U.S. Citizenship and Immigration Services has an online system for managing immigration applications.
Publisher: EIRA Team
LOST view: OV-Guarantee [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/GuaranteeCapability
EIRA traceability: eira:DigitalBusinessCapability
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-08-08
dct:identifier: http://data.europa.eu/dr8/egovera/GuaranteeCapability
dct:title: Guarantee (DBC)
Definition: Qualification Management enables the electronic validation and verification of the qualifications (any information linked to an individual with respect to the education and employment status) of the professionals against specific requirements defined by relevant legislations.
Source: Oracle
Source reference: https://www.oracle.com/a/ocom/docs/applications/erp/oracle-supplier-qualification-management-cloud-ds.pdf
Additional information: The Qualification Management Digital Business Capability (QMDBC) is a comprehensive framework and set of digital tools designed to facilitate and enhance the interoperability of IT systems and processes related to qualifications management among member states and private companies in Europe. It aims to streamline and harmonize the exchange of qualification-related information, ensuring consistency, efficiency, and transparency across borders.
At its core, the QMDBC encompasses a range of digital solutions and standards that enable the seamless sharing, recognition, and validation of qualifications across different countries and organizations. It provides a common platform for member states and private companies to collaborate and exchange information on qualifications, enabling individuals to have their qualifications recognized and valued in various contexts.
One of the key components of the QMDBC is a centralized database or repository that stores and manages qualification-related data. This database serves as a single source of truth, containing information on qualifications, competencies, skills, and other relevant attributes. It allows member states and private companies to access and verify qualifications, ensuring accuracy and reliability in the recognition process.
The QMDBC also incorporates standardized data formats and protocols to ensure compatibility and interoperability among different IT systems. This includes the use of common data models, metadata standards, and communication protocols, enabling seamless integration and exchange of qualification data between member states and private companies. These standards facilitate the automated processing and validation of qualifications, reducing administrative burdens and improving the efficiency of recognition procedures.
Furthermore, the QMDBC includes digital tools and services that support the management and assessment of qualifications. These tools enable member states and private companies to evaluate and compare qualifications, assess their relevance and equivalence, and make informed decisions regarding recognition and validation. They may include online assessment platforms, qualification frameworks, competency mapping tools, and other digital resources that enhance the transparency and objectivity of the qualification recognition process.
In addition to the technical aspects, the QMDBC also encompasses governance and policy frameworks that guide the implementation and operation of the interoperability infrastructure. This includes the establishment of common rules, procedures, and quality assurance mechanisms to ensure the reliability and trustworthiness of qualification information. It also involves the collaboration and coordination among member states, private companies, and relevant stakeholders to address legal, regulatory, and ethical considerations associated with qualification recognition and interoperability.
Overall, the Qualification Management Digital Business Capability plays a crucial role in promoting the harmonization and interoperability of qualification management systems across Europe. By providing a standardized and efficient framework for exchanging qualification-related information, it facilitates the recognition and validation of qualifications, enhances labor mobility, and supports the development of a skilled and competitive workforce in the European Union.
Example: The Qualification Management Digital Business Capability can be applied in various ways to enhance European IT interoperability among member states and private companies. Here are a few examples:
1. Digital Credentialing: The capability can be used to establish a standardized system for issuing and managing digital credentials, such as diplomas, certifications, and licenses. This would enable seamless recognition of qualifications across member states and private companies, reducing administrative burden and facilitating mobility of IT professionals.
2. Cross-border Recognition: The capability can support the development of a common framework for recognizing qualifications across European countries. By digitizing and harmonizing qualification management processes, member states and private companies can easily verify and accept qualifications obtained in other jurisdictions, promoting workforce mobility and facilitating cross-border collaborations.
3. Competency Mapping: The capability can enable the creation of a comprehensive competency mapping system, which aligns IT qualifications with specific job roles and skills required in the industry. This would help member states and private companies in identifying and matching the right talent for specific IT projects or job vacancies, ensuring a better fit between qualifications and job requirements.
4. Interoperable Learning Management Systems: The capability can facilitate the integration of different learning management systems used by member states and private companies. This would enable seamless exchange of training and educational resources, fostering collaboration and knowledge sharing among European IT stakeholders.
5. Quality Assurance and Accreditation: The capability can support the establishment of a unified quality assurance and accreditation framework for IT qualifications. By digitizing and automating the accreditation processes, member states and private companies can ensure consistent quality standards across Europe, enhancing trust and reliability in the IT workforce.
Overall, the Qualification Management Digital Business Capability can play a crucial role in promoting harmonization, standardization, and interoperability of IT qualifications among member states and private companies in Europe.
LOST view: Organisational view
Identifier: http://data.europa.eu/dr8/egovera/QualificationManagementCapability
ABB name: eira:QualificationManagementCapability
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/egovera/QualificationManagementCapability
Name: Qualification Management Digital Business Capability
Interoperability Layer: Organisational
Specialises: http://data.europa.eu/dr8/DigitalBusinessCapability
Description: The Data Governance Digital Business Capability refers to the ability of an organization to effectively manage and govern its data assets. It involves establishing policies, procedures, and frameworks to ensure data quality, integrity, security, and compliance. This capability enables organizations to have a holistic view of their data, make informed decisions based on reliable information, and ensure that data is used in a consistent and controlled manner across the enterprise. It also involves implementing data governance processes and tools to monitor and enforce data standards, resolve data-related issues, and enable data-driven decision-making at all levels of the organization.
Additional information: The Data Governance Digital Business Capability refers to the ability of an organization to effectively manage and govern its data assets in a digital business environment. It encompasses the policies, processes, and practices that ensure the availability, integrity, confidentiality, and usability of data across the enterprise.
Data governance involves establishing a framework that defines the roles, responsibilities, and decision-making processes related to data management. It aims to ensure that data is accurate, consistent, and reliable, and that it complies with relevant regulations and standards. The digital aspect of data governance emphasizes the need to manage data in the context of digital transformation initiatives and the increasing reliance on digital technologies.
Key components of the Data Governance Digital Business Capability include:
1. Data Strategy: Developing a strategic plan that aligns data governance objectives with the overall business strategy. This involves defining the vision, goals, and objectives for data governance and identifying the key initiatives required to achieve them.
2. Data Policies and Standards: Establishing policies and standards that govern the collection, storage, processing, and sharing of data. These policies define data quality requirements, data classification and handling guidelines, data retention and disposal policies, and data privacy and security measures.
3. Data Stewardship: Assigning data stewards who are responsible for ensuring the quality, integrity, and compliance of data within their respective domains. Data stewards collaborate with data owners, users, and IT teams to define and enforce data standards, resolve data-related issues, and promote data governance best practices.
4. Data Quality Management: Implementing processes and tools to monitor, measure, and improve the quality of data. This includes data profiling, data cleansing, data validation, and data enrichment activities to ensure that data is accurate, complete, and consistent.
5. Data Privacy and Security: Establishing controls and measures to protect sensitive data from unauthorized access, disclosure, or misuse. This involves implementing data encryption, access controls, data masking, and data anonymization techniques to safeguard data privacy and comply with data protection regulations.
6. Data Lifecycle Management: Defining processes and procedures to manage the entire lifecycle of data, from creation to archival or disposal. This includes data capture, storage, integration, transformation, and archival strategies, as well as data backup and recovery mechanisms.
7. Data Governance Organization: Establishing a dedicated data governance team or committee responsible for overseeing and coordinating data governance activities. This team ensures that data governance policies and practices are effectively implemented, and it provides guidance and support to data stewards and other stakeholders.
8. Data Governance Tools and Technologies: Implementing data governance tools and technologies that facilitate data management, data quality monitoring, metadata management, and data lineage tracking. These tools enable automation, collaboration, and reporting capabilities to support efficient and effective data governance practices.
By developing and maturing the Data Governance Digital Business Capability, organizations can ensure that their data assets are effectively managed, protected, and leveraged to drive business value, support decision-making processes, and enable digital transformation initiatives.
Example: The Data Governance Digital Business Capability in the public sector refers to the ability to establish and enforce policies, procedures, and standards for managing data assets effectively. Here are some real examples of this capability in action:
1. Data Classification and Protection: Public sector organizations often deal with sensitive and confidential information. Data governance ensures that appropriate classification and protection mechanisms are in place to safeguard this data. For instance, a government agency may implement policies and procedures to classify data as public, internal, or confidential, and define access controls accordingly.
2. Data Quality Management: Public sector organizations rely on accurate and reliable data for decision-making and service delivery. Data governance enables the establishment of processes and controls to ensure data quality. For example, a municipality may implement data governance practices to regularly monitor and cleanse citizen data to maintain accurate records for service provision.
3. Data Sharing and Collaboration: Collaboration between different government agencies is crucial for effective governance and service delivery. Data governance facilitates the establishment of frameworks and agreements for sharing data securely and efficiently. For instance, a national healthcare system may implement data governance practices to enable secure sharing of patient information between hospitals and clinics to improve healthcare outcomes.
4. Compliance and Regulatory Reporting: Public sector organizations must adhere to various regulations and reporting requirements. Data governance ensures that data is managed in compliance with applicable laws and regulations. For example, a tax authority may implement data governance practices to ensure accurate and timely reporting of taxpayer information to meet regulatory obligations.
5. Data Privacy and Protection: Protecting citizens' privacy is a critical concern for public sector organizations. Data governance helps establish policies and controls to ensure compliance with privacy laws and protect personal information. For instance, a government agency may implement data governance practices to define procedures for handling and securing citizen data, ensuring compliance with data protection regulations.
These examples demonstrate how the Data Governance Digital Business Capability in the public sector enables effective management, protection, and utilization of data assets to support governance, service delivery, compliance, and privacy requirements.
Publisher: EIRA Team
LOST view: OV-Data Spaces [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/DataGovernanceCapability
EIRA traceability: eira:DigitalBusinessCapability
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-07-10
dct:identifier: http://data.europa.eu/dr8/egovera/DataGovernanceCapability
dct:title: Data Governance Digital Business Capability
Definition: Digital Twin enables the creation of a digital copy of reality, that allows to simulate and find answers in a risk free and secure environment. The coupling of the physical and digital world enables to monitor both systems, prevent issues, develop new opportunities and simulate future outcomes. It is based on three main pillars: Connectivity, Digitalization, Intelligence.
Source: Michael Grieves
Source reference: https://www.researchgate.net/publication/334599683_Virtually_Intelligent_Product_Systems_Digital_and_Physical_Twins
Additional information: The Digital Twin Digital Business Capability (DT-DBC) is a concept that aims to enhance IT interoperability among member states and private companies within the European Union (EU). It is a strategic initiative that leverages digital technologies to create virtual replicas or representations of physical entities, such as products, systems, or processes.
The primary objective of the DT-DBC is to enable seamless data exchange, collaboration, and integration across various domains, sectors, and organizations. It seeks to establish a standardized framework and infrastructure that allows member states and private companies to share and utilize digital twins effectively.
Digital twins are dynamic, real-time digital models that mirror the physical entities they represent. They are equipped with sensors, data analytics capabilities, and connectivity, enabling them to capture and transmit data about their physical counterparts. This data can include information about the entity's performance, behavior, condition, and environment.
The DT-DBC aims to facilitate the creation, management, and utilization of digital twins across the EU by establishing common standards, protocols, and interfaces. It promotes the adoption of open and interoperable technologies, ensuring that digital twins can seamlessly interact and exchange data regardless of their origin or location.
By implementing the DT-DBC, member states and private companies can achieve several benefits. Firstly, it enables improved decision-making by providing real-time insights into the performance and behavior of physical entities. This allows for proactive maintenance, optimization, and predictive analysis, leading to increased efficiency, reduced costs, and enhanced reliability.
Secondly, the DT-DBC fosters collaboration and knowledge sharing among stakeholders. It enables different organizations to work together on common projects, share data, and leverage each other's expertise. This promotes innovation, accelerates development cycles, and facilitates the creation of new products, services, and business models.
Furthermore, the DT-DBC contributes to the digital transformation of industries and sectors. It enables the integration of digital twins into existing IT systems, processes, and workflows, creating a seamless and connected ecosystem. This integration can span across domains such as manufacturing, healthcare, transportation, energy, and more, enabling cross-sector collaboration and innovation.
To ensure the successful implementation of the DT-DBC, several challenges need to be addressed. These include data privacy and security concerns, standardization of data formats and interfaces, harmonization of regulations and policies, and the development of robust infrastructure and connectivity.
In conclusion, the Digital Twin Digital Business Capability is a strategic initiative aimed at enhancing IT interoperability among member states and private companies within the European Union. By leveraging digital twins, it enables seamless data exchange, collaboration, and integration, leading to improved decision-making, increased efficiency, and accelerated innovation.
Example: The application of Digital Twin Digital Business Capability can greatly benefit European IT interoperability among member states and private companies. Here are a few examples:
1. Cross-border data sharing: Digital Twin technology can facilitate seamless data sharing and interoperability between different member states and private companies. It allows for the creation of virtual replicas of physical assets or systems, enabling real-time data exchange and collaboration across borders. This can be particularly useful in areas such as transportation, energy, and healthcare, where cross-border data sharing is crucial for efficient operations.
2. Standardization and harmonization: Digital Twin technology can help in standardizing and harmonizing IT systems and processes across member states and private companies. By creating a virtual representation of a system or process, it becomes easier to identify inconsistencies or inefficiencies and develop common standards. This can lead to improved interoperability and smoother integration of IT systems, ultimately enhancing collaboration and efficiency.
3. Simulation and testing: Digital Twins can be used for simulation and testing purposes, allowing member states and private companies to evaluate the interoperability of their IT systems before implementation. By creating virtual replicas, stakeholders can simulate different scenarios, identify potential issues, and make necessary adjustments to ensure seamless interoperability. This can help in reducing risks and costs associated with system integration and deployment.
4. Cross-domain collaboration: Digital Twin technology can facilitate cross-domain collaboration among member states and private companies. By creating a virtual representation of a system or asset, stakeholders from different domains can collaborate and exchange information more effectively. For example, in smart city initiatives, Digital Twins can enable collaboration between transportation, energy, and public safety sectors, leading to improved interoperability and better overall performance.
5. Data-driven decision making: Digital Twins generate vast amounts of data, which can be leveraged for data-driven decision making. By analyzing the data collected from virtual replicas, member states and private companies can gain valuable insights into system performance, identify areas for improvement, and make informed decisions to enhance interoperability. This can lead to optimized operations, improved resource allocation, and better overall outcomes.
Overall, the application of Digital Twin Digital Business Capability can significantly contribute to European IT interoperability among member states and private companies by enabling seamless data sharing, standardization, simulation, cross-domain collaboration, and data-driven decision making.
LOST view: Organisational view
Identifier: http://data.europa.eu/dr8/egovera/DigitalTwinCapability
ABB name: eira:DigitalTwinCapability
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/egovera/DigitalTwinCapability
Name: Digital Twin Digital Business Capability
Interoperability Layer: Organisational
Specialises: http://data.europa.eu/dr8/DigitalBusinessCapability
Description: The 'Risk Analysis' Digital Business Capability refers to the ability of a business to identify, assess, and prioritize potential risks or threats in its digital operations or projects. This capability involves the use of digital tools and technologies to evaluate the likelihood and impact of risks, and to develop strategies to mitigate them. It includes aspects such as cybersecurity risk assessment, data breach risk analysis, and digital project risk management. The aim is to reduce uncertainty, protect business assets, ensure data integrity and privacy, and maintain business continuity in the digital environment.
Additional information: The 'Risk Analysis' Digital Business Capability refers to the ability of an organization to identify, assess, and prioritize risks associated with its digital operations and initiatives. This capability involves the use of digital tools and technologies to evaluate potential threats and vulnerabilities in the organization's digital infrastructure, systems, and processes.
Risk analysis includes the assessment of the potential impact and probability of identified risks, and the development of strategies to manage and mitigate these risks. It involves understanding the organization's risk tolerance and aligning risk management efforts with the organization's strategic objectives and risk appetite.
This capability also includes the ability to monitor and review risks on an ongoing basis, and to adjust risk management strategies as necessary in response to changes in the organization's digital environment or risk profile.
Risk analysis can cover a wide range of risks, including cybersecurity threats, data breaches, technology failures, regulatory compliance risks, and risks associated with digital transformation initiatives.
Effective risk analysis can help an organization to protect its digital assets, ensure the continuity of its digital operations, maintain the trust of its customers and stakeholders, and achieve its strategic objectives in a digital business environment.
In the context of TOGAF, risk analysis is a critical component of the organization's enterprise architecture, helping to ensure that the architecture is robust, resilient, and capable of supporting the organization's business objectives in a risk-informed manner.
Example: 1. Cybersecurity Risk Analysis: Government agencies like the Department of Homeland Security (DHS) or the National Institute of Standards and Technology (NIST) in the United States conduct risk analysis to identify potential threats to their digital infrastructure. They assess the likelihood of cyberattacks, their potential impact, and develop strategies to mitigate these risks.
2. Health Risk Analysis: Public health agencies like the Centers for Disease Control and Prevention (CDC) or the World Health Organization (WHO) use digital tools to analyze the risk of disease outbreaks. They use data analytics to predict the spread of diseases, identify high-risk populations, and plan interventions.
3. Financial Risk Analysis: Government financial institutions like the Federal Reserve or the Treasury Department conduct risk analysis to assess the stability of the financial system. They use digital tools to analyze economic indicators, assess the risk of financial crises, and develop strategies to mitigate these risks.
4. Environmental Risk Analysis: Environmental agencies like the Environmental Protection Agency (EPA) or the National Oceanic and Atmospheric Administration (NOAA) conduct risk analysis to assess the impact of environmental hazards. They use digital tools to model the impact of climate change, pollution, or natural disasters, and develop strategies to mitigate these risks.
5. Infrastructure Risk Analysis: Public sector entities like the Department of Transportation or the Federal Emergency Management Agency (FEMA) conduct risk analysis to assess the resilience of public infrastructure. They use digital tools to model the impact of various hazards, assess the vulnerability of infrastructure, and develop strategies to mitigate these risks.
6. National Security Risk Analysis: Intelligence agencies like the Central Intelligence Agency (CIA) or the National Security Agency (NSA) conduct risk analysis to assess threats to national security. They use digital tools to analyze intelligence data, assess the risk of terrorist attacks or other threats, and develop strategies to mitigate these risks.
Publisher: EIRA Team
LOST view: OV-Risk Analysis [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/RiskAnalysisCapability
EIRA traceability: eira:DigitalBusinessCapability
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-08-08
dct:identifier: http://data.europa.eu/dr8/egovera/RiskAnalysisCapability
dct:title: Risk analysis (DBC)
Description: 'Duties Calculation and Payment' digital business capability refers to the ability of a business to accurately calculate and process payments related to duties, such as customs duties, taxes, or other levies, using digital tools and platforms. This capability involves the use of advanced software or systems to automate the calculation process, ensure compliance with relevant regulations, and facilitate timely and accurate payments. It may also include features for tracking and reporting duties payments, integrating with other financial systems, and managing duties-related data and documentation. This capability is crucial for businesses involved in international trade or other activities subject to duties.
Additional information: The 'Duties Calculation and Payment' digital business capability refers to the ability of a business to accurately calculate, manage, and process payments related to duties, tariffs, and taxes in a digital environment. This capability is crucial for businesses that operate in international trade, where various types of duties and tariffs apply.
This capability involves several components:
1. Duty Calculation: This involves the use of digital tools and systems to accurately calculate the duties applicable to specific goods or services. This calculation is based on various factors such as the type of goods, their value, their country of origin, and the destination country. The calculation process must comply with the relevant laws and regulations in both the origin and destination countries.
2. Duty Payment Management: Once the duties are calculated, the business must manage the payment process. This involves setting up and maintaining digital payment systems, ensuring secure and timely payment transactions, and managing any issues or disputes that may arise.
3. Compliance and Reporting: The business must also ensure that all duty calculations and payments are compliant with the relevant laws and regulations. This involves maintaining accurate records, generating reports for regulatory bodies, and undergoing audits if required.
4. Integration with Other Systems: The 'Duties Calculation and Payment' capability must be integrated with other business systems, such as supply chain management, finance, and customer relationship management. This ensures that duty calculations and payments are accurately reflected in all relevant business processes and records.
5. Continuous Improvement: The business must continually monitor and improve its 'Duties Calculation and Payment' capability. This involves staying updated with changes in laws and regulations, adopting new technologies and best practices, and addressing any issues or inefficiencies in the process.
In summary, the 'Duties Calculation and Payment' digital business capability is a critical aspect of international trade operations. It requires a combination of accurate calculation, efficient payment management, strict compliance, seamless integration, and continuous improvement.
Example: 1. Customs and Border Protection: In many countries, the customs and border protection department has the responsibility of calculating and collecting duties on imported goods. They use digital systems to assess the value of goods, calculate the applicable duties, and facilitate online payments.
2. Tax Collection Agencies: Tax agencies like the IRS in the United States have digital systems in place for calculating and collecting taxes from individuals and businesses. These systems allow taxpayers to submit their tax returns online, calculate their tax liabilities, and make payments digitally.
3. Social Security Administration: The Social Security Administration in the United States calculates and collects social security taxes from workers' paychecks. They use digital systems to manage these processes.
4. Vehicle Licensing Agencies: In many jurisdictions, vehicle licensing agencies calculate and collect vehicle registration fees, which often include duties or taxes. These agencies often have online systems that allow vehicle owners to pay these fees digitally.
5. Environmental Agencies: Some environmental agencies are responsible for calculating and collecting duties or fees related to environmental regulations. For example, a company might be required to pay a fee based on the amount of pollution it produces. These agencies can use digital systems to manage these processes.
6. Local Government: Local governments often calculate and collect property taxes, utility fees, and other local duties. Many local governments have implemented digital systems that allow residents to pay these fees online.
7. State Liquor Control Boards: In some states, the liquor control board is responsible for calculating and collecting duties on alcohol sales. They may use digital systems to manage these processes.
Publisher: EIRA Team
LOST view: OV-Duties Calculation and payment [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/DutiesCalculationAndPaymentCapability
EIRA traceability: eira:DigitalBusinessCapability
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-08-08
dct:identifier: http://data.europa.eu/dr8/egovera/DutiesCalculationAndPaymentCapability
dct:title: Duties Calculation and payment (DBC)
Description: 'Laboratories Management' as a Digital Business Capability refers to the ability of a business to effectively manage and control its laboratory operations using digital technologies. This includes the use of software and systems for tasks such as scheduling and tracking experiments, managing and analyzing data, maintaining quality control, ensuring regulatory compliance, and managing resources and inventory. It also involves the use of digital tools for communication and collaboration within the laboratory environment. This capability is crucial for improving efficiency, accuracy, and productivity in laboratory operations.
Additional information: The 'Laboratories Management' digital business capability refers to the ability of an organization to effectively manage and control its laboratory operations using digital technologies. This capability encompasses a wide range of activities and processes, including but not limited to, the management of laboratory equipment, materials, and resources, the scheduling and execution of laboratory tests and experiments, the collection, analysis, and reporting of laboratory data, and the compliance with relevant regulations and standards.
In a more detailed perspective, this capability involves the use of digital systems and tools to automate and streamline laboratory processes, improve the accuracy and reliability of laboratory results, enhance the efficiency and productivity of laboratory personnel, and ensure the safety and security of laboratory facilities. It also involves the integration of laboratory systems with other business systems to facilitate the sharing and utilization of laboratory data across the organization.
Moreover, the 'Laboratories Management' digital business capability also includes the ability to leverage advanced technologies such as artificial intelligence, machine learning, and big data analytics to drive innovation and improvement in laboratory operations. This could involve the use of predictive analytics to optimize laboratory workflows, the application of machine learning algorithms to automate complex laboratory tasks, or the use of AI-powered tools to enhance the quality and speed of laboratory decision-making.
Furthermore, this capability also entails the ability to manage the digital transformation of laboratory operations, including the planning, implementation, and management of digital laboratory projects, the training and development of laboratory personnel in the use of digital technologies, and the management of the risks and challenges associated with digital transformation.
In essence, the 'Laboratories Management' digital business capability is about harnessing the power of digital technologies to enhance the performance and value of laboratory operations, and to enable the organization to achieve its strategic objectives in a digital business environment.
Example: 1. National Institute of Health (NIH): The NIH, a part of the U.S. Department of Health and Human Services, is the nation's medical research agency. They use digital capabilities to manage their laboratories, including software for tracking and managing lab equipment, samples, and results, as well as for coordinating research efforts across multiple labs.
2. European Space Agency (ESA): The ESA uses digital capabilities to manage their laboratories, which are involved in a wide range of research and development activities. This includes software for managing lab resources, coordinating research activities, and analyzing and sharing research data.
3. Centers for Disease Control and Prevention (CDC): The CDC uses digital capabilities to manage their laboratories, which are involved in research and testing related to public health issues. This includes software for managing lab resources, tracking and analyzing test results, and coordinating research efforts.
4. Public Health England (PHE): PHE uses digital capabilities to manage their laboratories, which are involved in research and testing related to public health issues. This includes software for managing lab resources, tracking and analyzing test results, and coordinating research efforts.
5. Australian Nuclear Science and Technology Organisation (ANSTO): ANSTO uses digital capabilities to manage their laboratories, which are involved in nuclear science and technology research. This includes software for managing lab resources, coordinating research activities, and analyzing and sharing research data.
6. National Oceanic and Atmospheric Administration (NOAA): NOAA uses digital capabilities to manage their laboratories, which are involved in research related to climate, weather, and ocean conditions. This includes software for managing lab resources, tracking and analyzing research data, and coordinating research efforts.
Publisher: EIRA Team
LOST view: OV-Laboratories management [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/LaboratoriesManagementCapability
EIRA traceability: eira:DigitalBusinessCapability
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-08-08
dct:identifier: http://data.europa.eu/dr8/egovera/LaboratoriesManagementCapability
dct:title: Laboratories management (DBC)
Description: The Data Lineage Digital Business Capability refers to the ability of an organization to track and trace the origin, movement, and transformation of data throughout its lifecycle. It involves capturing and documenting the lineage of data elements, including their sources, transformations, and destinations. This capability enables organizations to understand the data flow across systems, processes, and applications, ensuring data quality, compliance, and effective decision-making. It also helps in identifying data dependencies, impact analysis, and troubleshooting data-related issues. Overall, the Data Lineage Digital Business Capability provides transparency and visibility into the data ecosystem, facilitating effective data governance and management.
Additional information: The Data Lineage Digital Business Capability refers to the ability of an organization to track and trace the origin, movement, and transformation of data throughout its lifecycle. It involves capturing and documenting the lineage of data elements, including their sources, transformations, and destinations, to ensure data quality, compliance, and understanding.
Data lineage provides a comprehensive view of how data flows through various systems, processes, and applications within an organization. It helps in understanding the data's journey, identifying potential bottlenecks, and ensuring data integrity and accuracy. This capability enables organizations to answer critical questions about data, such as where it comes from, how it is transformed, and where it goes.
The Data Lineage Digital Business Capability encompasses several key components and activities:
1. Data Source Identification: This involves identifying the original sources of data, whether it is internal or external to the organization. It includes understanding the systems, databases, files, or APIs that generate or provide data.
2. Data Transformation Mapping: This component focuses on documenting the transformations applied to data as it moves through different processes, systems, or applications. It includes capturing the rules, algorithms, or logic used to modify or manipulate the data.
3. Data Destination Tracking: This aspect involves tracking the final destinations of data, such as databases, reports, dashboards, or other systems. It ensures that data reaches the intended targets and helps in identifying any potential gaps or inconsistencies.
4. Metadata Management: Metadata, which provides additional context and information about data, plays a crucial role in data lineage. This component involves managing and maintaining metadata repositories, including data dictionaries, data catalogs, and data models.
5. Data Lineage Visualization: Visualizing data lineage helps stakeholders understand the flow of data across systems and processes. It may include graphical representations, diagrams, or interactive tools that depict the relationships and dependencies between data elements.
6. Impact Analysis: Data lineage enables impact analysis by identifying the potential consequences of changes to data sources, transformations, or destinations. It helps in assessing the impact on downstream systems, processes, and reports, facilitating effective change management.
7. Compliance and Audit: Data lineage is essential for regulatory compliance and audit purposes. It enables organizations to demonstrate data lineage to regulatory bodies, ensuring data governance, privacy, and security requirements are met.
8. Data Quality Monitoring: Data lineage supports data quality initiatives by providing insights into the data's journey and identifying potential quality issues. It helps in establishing data quality metrics, monitoring data quality, and implementing corrective actions.
Overall, the Data Lineage Digital Business Capability is a critical aspect of data management and governance. It enables organizations to have a holistic view of their data assets, understand data flows, ensure data integrity, comply with regulations, and make informed decisions based on trustworthy and reliable data.
Example: The Data Lineage Digital Business Capability in the public sector refers to the ability to track and understand the origin, movement, and transformation of data throughout its lifecycle. This capability is crucial for ensuring data quality, compliance, and decision-making. Here are some real examples of how this capability is applied in the public sector:
1. Tax Compliance: In tax administration, data lineage is used to trace the flow of financial data from taxpayers' records to tax returns and subsequent reports. This capability helps auditors and tax authorities verify the accuracy and integrity of the data, ensuring compliance with tax regulations.
2. Fraud Detection: Government agencies responsible for detecting and preventing fraud, such as social welfare fraud or tax evasion, utilize data lineage to track the flow of data across various systems and processes. By analyzing the lineage, anomalies or suspicious patterns can be identified, leading to the detection of fraudulent activities.
3. Public Health Monitoring: Data lineage is crucial in public health monitoring, especially during disease outbreaks or pandemics. It helps track the origin and movement of patient data, test results, and contact tracing information. This capability enables health authorities to identify the source of infection, track the spread of the disease, and make informed decisions for containment and mitigation.
4. Government Performance Reporting: Data lineage is used to ensure the accuracy and reliability of performance reports generated by government agencies. By tracing the data sources, transformations, and calculations involved in generating these reports, data lineage helps maintain transparency, accountability, and trust in the reported performance metrics.
5. Freedom of Information Requests: Public sector organizations often receive requests for information under the Freedom of Information Act or similar legislation. Data lineage helps track the data sources, systems, and processes involved in generating the requested information. This capability ensures that the information provided is accurate, complete, and can be audited if necessary.
These examples demonstrate how the Data Lineage Digital Business Capability is applied in the public sector to ensure data quality, compliance, and informed decision-making.
Publisher: EIRA Team
LOST view: OV-Data Spaces [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/DataLineageCapability
EIRA traceability: eira:DigitalBusinessCapability
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-07-11
dct:identifier: http://data.europa.eu/dr8/egovera/DataLineageCapability
dct:title: Data Lineage Digital Business Capability
Definition: Case and Workflow Management enables organisations to design, execute, and automatise internal processes based on pre-defined business rules.
Source: Hajo Reijers
Source reference: https://lists.w3.org/Archives/Public/public-xg-eiif/2008Oct/att-0019/HARE.MOJA.MIZU.WIAP-BPM-2007.pdf
Additional information: The Case and Workflow Management Digital Business Capability (DWC) is a comprehensive system designed to facilitate and streamline the management of cases and workflows within the context of European IT interoperability among member states and private companies. It serves as a digital platform that enables efficient collaboration, information sharing, and decision-making across various entities involved in the European IT landscape.
The DWC encompasses a range of functionalities and features that support the end-to-end management of cases and workflows. It provides a centralized repository for storing and accessing relevant information, documents, and data related to specific cases or workflows. This ensures that all stakeholders have access to the most up-to-date and accurate information, promoting transparency and accountability.
One of the key aspects of the DWC is its ability to facilitate seamless communication and collaboration among different entities. It enables secure and real-time communication channels, allowing member states and private companies to exchange information, updates, and notifications related to specific cases or workflows. This promotes effective coordination and cooperation, reducing delays and improving overall efficiency.
The DWC also incorporates advanced workflow management capabilities. It allows for the definition and automation of complex workflows, ensuring that tasks and activities are assigned, tracked, and completed in a timely manner. This helps to streamline processes, minimize manual intervention, and reduce the risk of errors or oversights.
Furthermore, the DWC includes robust analytics and reporting functionalities. It enables the generation of comprehensive reports and insights, providing valuable data and metrics related to case and workflow management. This allows member states and private companies to monitor performance, identify bottlenecks, and make data-driven decisions to optimize processes and improve outcomes.
In terms of European IT interoperability, the DWC ensures that member states and private companies can seamlessly integrate their existing IT systems and applications with the platform. It supports standardized data formats, protocols, and interfaces, enabling smooth data exchange and interoperability across different systems. This promotes a cohesive and interconnected IT ecosystem, facilitating efficient collaboration and information sharing among all stakeholders.
Overall, the Case and Workflow Management Digital Business Capability plays a crucial role in enhancing European IT interoperability among member states and private companies. It provides a comprehensive and integrated platform for managing cases and workflows, enabling efficient collaboration, streamlined processes, and improved decision-making. By promoting transparency, accountability, and interoperability, the DWC contributes to the overall effectiveness and efficiency of the European IT landscape.
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): ePrescription: "Generation, transmission, and filling of a medical prescription through digital channels. ePrescribing allows a physician, pharmacist, nurse practitioner, or physician assistant to use digital prescription software to electronically transmit a new prescription or renewal authorization to a community or mail-order pharmacy".
LOST view: Organisational view
Identifier: http://data.europa.eu/dr8/egovera/CaseAndWorkflowManagementCapability
ABB name: eira:CaseAndWorkflowManagementCapability
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/egovera/CaseAndWorkflowManagementCapability
Name: Case and Workflow Management Digital Business Capability
Interoperability Layer: Organisational
Specialises: http://data.europa.eu/dr8/DigitalBusinessCapability
Definition: Contact Management enables the storing and organisation of contacts of a public administration's user base (both providers and consumers of its public services) and tracking of the related interactions.
Source: Shared Contacts
Source reference: https://www.getsharedcontacts.com/contact-management-guide/
Additional information: The Contact Management Digital Business Capability refers to the ability of European member states and private companies to effectively manage and exchange contact information in a digital format, ensuring interoperability and seamless communication.
In the context of European IT interoperability, member states and private companies need to establish a standardized approach to contact management to facilitate efficient collaboration and information sharing. This capability encompasses various aspects, including the collection, storage, organization, and retrieval of contact information.
At its core, the Contact Management Digital Business Capability involves the adoption of digital tools and technologies to capture and maintain accurate contact details of individuals and organizations. This includes not only basic information such as names, addresses, and phone numbers but also more advanced data like email addresses, social media profiles, and other relevant identifiers.
To ensure interoperability, member states and private companies must adhere to common standards and protocols for contact management. This involves the use of standardized data formats, such as vCard or XML, to enable seamless exchange of contact information across different systems and platforms. Additionally, the capability may involve the implementation of standardized APIs (Application Programming Interfaces) that allow for the integration of contact management systems with other IT systems and applications.
The Contact Management Digital Business Capability also encompasses the implementation of robust security measures to protect the privacy and confidentiality of contact information. This includes encryption techniques, access controls, and data protection policies to prevent unauthorized access, data breaches, or misuse of contact data.
Furthermore, the capability may involve the development and deployment of advanced functionalities to enhance contact management processes. This could include features like deduplication algorithms to identify and eliminate duplicate contacts, integration with CRM (Customer Relationship Management) systems to streamline customer interactions, and automation of contact updates to ensure data accuracy.
In the context of European IT interoperability, the Contact Management Digital Business Capability plays a crucial role in facilitating efficient communication and collaboration among member states and private companies. It enables seamless exchange of contact information, supports effective stakeholder engagement, and enhances overall business processes.
By adopting and implementing this capability, European member states and private companies can establish a standardized and interoperable approach to contact management, leading to improved efficiency, reduced duplication of efforts, and enhanced data quality. This, in turn, contributes to the overall goal of achieving seamless digital integration and collaboration across the European IT landscape.
Example: The Contact Management Digital Business Capability can be applied in various ways to enhance European IT interoperability among member states and private companies. Here are some examples:
1. Centralized Contact Database: A shared contact management system can be established, allowing member states and private companies to maintain a centralized database of contacts. This database can include information about key stakeholders, experts, and decision-makers involved in IT interoperability initiatives. It ensures that up-to-date contact information is readily available to facilitate communication and collaboration.
2. Collaboration Platform: The Contact Management Digital Business Capability can be integrated into a collaboration platform, enabling member states and private companies to connect, share information, and collaborate on IT interoperability projects. This platform can provide features like contact directories, messaging, document sharing, and task management, fostering efficient and effective collaboration across borders.
3. Interoperability Events and Workshops: The capability can be utilized to organize and manage interoperability events and workshops. Member states and private companies can use the contact management system to invite relevant stakeholders, manage registrations, and communicate event details. This ensures that the right people are involved and informed about such events, fostering knowledge exchange and cooperation.
4. Stakeholder Engagement: The Contact Management Digital Business Capability can support member states and private companies in engaging with stakeholders involved in IT interoperability. It can provide tools for identifying and categorizing stakeholders, tracking their interests and concerns, and managing communication with them. This helps in building strong relationships, understanding diverse perspectives, and addressing concerns effectively.
5. Cross-Border Collaboration: The capability can facilitate cross-border collaboration by enabling member states and private companies to identify potential partners and experts in other countries. It can provide a platform for initiating and managing collaboration requests, sharing best practices, and coordinating joint initiatives. This promotes knowledge sharing, innovation, and the development of common standards for IT interoperability.
6. Compliance and Regulatory Management: The Contact Management Digital Business Capability can assist member states and private companies in managing compliance and regulatory requirements related to IT interoperability. It can help track and communicate changes in regulations, maintain contact with regulatory authorities, and ensure timely compliance. This ensures that interoperability initiatives align with legal frameworks and standards across European member states.
Overall, the Contact Management Digital Business Capability plays a crucial role in facilitating communication, collaboration, and stakeholder engagement for IT interoperability among European member states and private companies.
LOST view: Organisational view [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/ContactManagementCapability
ABB name: eira:ContactManagementCapability
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/egovera/ContactManagementCapability
Name: Contact Management Digital Business Capability
Interoperability Layer: Organisational
Specialises: http://data.europa.eu/dr8/DigitalBusinessCapability
Description: 'Expeditions controls' digital business capability refers to the ability of a business to effectively manage, monitor, and control its expeditionary activities using digital technologies. This includes planning and coordinating expeditions, tracking the progress and location of expeditions in real-time, ensuring the safety and security of expedition members, managing resources and logistics, and responding to any unexpected incidents or emergencies. This capability may also involve the use of advanced technologies such as GPS tracking, satellite communication, and data analytics to enhance the efficiency, effectiveness, and safety of expedition operations.
Additional information: 'Expeditions Controls' as a Digital Business Capability refers to the ability of a business to effectively manage, monitor, and control all aspects of expeditions or exploratory ventures. This capability is particularly relevant for businesses operating in sectors such as logistics, supply chain, travel, and tourism, or any industry that involves physical movement of goods, people, or resources over long distances.
In the digital context, 'Expeditions Controls' involves the use of advanced technologies and digital solutions to enhance the efficiency and effectiveness of expedition management. This could include the use of GPS tracking systems for real-time location monitoring, digital platforms for scheduling and route optimization, IoT devices for condition monitoring (e.g., temperature, humidity, etc.), and AI-powered predictive analytics for risk assessment and mitigation.
Furthermore, 'Expeditions Controls' also encompasses the ability to ensure compliance with relevant regulations and standards, manage potential risks and emergencies, and ensure the safety and well-being of all involved personnel. This could involve digital solutions for documentation and reporting, risk management systems, emergency response systems, and digital training and certification programs.
In essence, 'Expeditions Controls' as a Digital Business Capability is about leveraging digital technologies to enhance the management and control of expeditions, thereby improving operational efficiency, reducing risks, ensuring compliance, and ultimately, enhancing business performance.
Example: 1. National Park Services: The National Park Services in the United States uses digital business capabilities to manage and control expeditions in national parks. They use digital systems to track the number of visitors, manage permits for hiking and camping, and monitor wildlife activity. This helps ensure the safety of visitors and the preservation of natural resources.
2. Disaster Response Teams: Government agencies like FEMA use digital capabilities to control expeditions in disaster-stricken areas. They use digital mapping and tracking systems to coordinate rescue efforts, manage resources, and monitor the progress of relief operations.
3. Space Agencies: Organizations like NASA and the European Space Agency use digital business capabilities to control expeditions in space. They use advanced digital systems to plan missions, monitor spacecraft, and analyze data from space expeditions.
4. Public Health Agencies: Public health agencies use digital capabilities to control expeditions related to disease control and prevention. They use digital systems to track disease outbreaks, manage vaccination campaigns, and monitor public health trends.
5. Archaeological Expeditions: Government bodies responsible for cultural heritage use digital capabilities to control archaeological expeditions. They use digital mapping, 3D modeling, and data analysis tools to plan excavations, document findings, and preserve archaeological sites.
6. Environmental Agencies: Government environmental agencies use digital capabilities to control expeditions related to environmental monitoring and conservation. They use digital systems to track pollution levels, monitor wildlife populations, and manage conservation efforts.
7. Defense and Military Operations: The defense sector uses digital capabilities to control expeditions and operations. They use digital systems for strategic planning, real-time communication, surveillance, and data analysis.
Publisher: EIRA Team
LOST view: OV-Customs DBCs, DPSs and Information [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/ExpeditionsControlsCapability
EIRA traceability: eira:DigitalBusinessCapability
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-08-08
dct:identifier: http://data.europa.eu/dr8/egovera/ExpeditionsControlsCapability
dct:title: Expeditions controls (DBC)
Definition: The capability to connect physical devices, sensors, and objects to the internet, enabling data collection, remote monitoring, and control of devices, and facilitating automation and integration within business processes.
Source: Gartner
Source reference: https://www.gartner.com/en/documents/4008663/hype-cycle-for-artificial-intelligence-2021
Additional information: The Artificial Intelligence (AI) Digital Business Capability in the context of European IT interoperability among member states and private companies refers to the integration and utilization of AI technologies to enhance the efficiency, effectiveness, and collaboration in various business processes across Europe.
AI, as a field of computer science, focuses on developing intelligent machines that can perform tasks that typically require human intelligence. It encompasses various subfields such as machine learning, natural language processing, computer vision, and robotics. The application of AI in the digital business realm aims to automate and augment decision-making processes, improve customer experiences, optimize operations, and enable data-driven insights.
In the European Union (EU), IT interoperability refers to the ability of different systems, applications, and devices to seamlessly exchange and use information. It is crucial for member states and private companies to ensure interoperability to facilitate smooth communication, data sharing, and collaboration across borders. The AI Digital Business Capability plays a significant role in achieving this interoperability by leveraging AI technologies to address challenges and unlock opportunities.
One aspect of AI Digital Business Capability is the development and deployment of AI-powered applications and services that can be used by member states and private companies. These applications can range from chatbots and virtual assistants for customer support to predictive analytics tools for business forecasting. By adopting AI-powered solutions, organizations can streamline their operations, improve decision-making processes, and enhance customer experiences.
Furthermore, AI can contribute to the standardization and harmonization of data formats, protocols, and interfaces, which are essential for interoperability. AI algorithms can be employed to analyze and transform data from different sources into a common format, enabling seamless data exchange and integration. This facilitates collaboration and information sharing among member states and private companies, leading to improved efficiency and effectiveness in various domains such as healthcare, transportation, finance, and public administration.
Moreover, AI Digital Business Capability can support the development of AI ecosystems and innovation networks across Europe. By fostering collaboration between member states, research institutions, and private companies, it encourages the exchange of knowledge, expertise, and best practices in AI. This collaboration can lead to the development of AI technologies and solutions that are tailored to the specific needs and challenges of the European context.
To ensure the ethical and responsible use of AI in the European IT interoperability landscape, the EU has also been actively working on establishing guidelines and regulations. The European Commission has proposed the creation of a European AI regulatory framework that promotes transparency, accountability, and human-centric AI. This framework aims to address concerns related to privacy, bias, and fairness in AI systems, ensuring that AI technologies are developed and deployed in a manner that aligns with European values and principles.
In summary, the AI Digital Business Capability in the European IT interoperability context encompasses the integration and utilization of AI technologies to enhance collaboration, efficiency, and effectiveness among member states and private companies. It involves the development of AI-powered applications, the standardization of data formats and interfaces, the fostering of AI ecosystems, and the establishment of ethical guidelines and regulations. By leveraging AI, Europe can unlock the potential of digital transformation, drive innovation, and achieve seamless interoperability in the digital business landscape.
Example: There are several examples of how Artificial Intelligence (AI) can be applied to enhance IT interoperability among member states and private companies in Europe. Here are a few:
1. Data Integration and Standardization: AI can be used to automate the integration and standardization of data across different systems and formats. This helps in achieving seamless interoperability between member states and private companies by ensuring that data can be easily exchanged and understood by all parties involved.
2. Natural Language Processing (NLP): NLP techniques can be employed to enable multilingual communication and understanding between different systems and stakeholders. This facilitates efficient collaboration and information exchange, overcoming language barriers and promoting interoperability.
3. Intelligent Data Mapping: AI algorithms can be utilized to map and align data elements from different systems, enabling interoperability by ensuring that data from various sources can be accurately interpreted and utilized by different entities. This helps in achieving a common understanding of data across member states and private companies.
4. Intelligent Decision Support Systems: AI-powered decision support systems can assist in making complex decisions related to IT interoperability. These systems can analyze vast amounts of data, identify patterns, and provide recommendations for improving interoperability, thereby enhancing efficiency and effectiveness in cross-border collaborations.
5. Predictive Analytics: AI techniques, such as machine learning, can be applied to analyze historical data and predict future trends and patterns. This can help member states and private companies anticipate interoperability challenges and proactively address them, ensuring smooth operations and minimizing disruptions.
6. Intelligent Automation: AI-driven automation can streamline and optimize interoperability processes by automating repetitive tasks, reducing manual effort, and minimizing errors. This can include tasks like data validation, data transformation, and data exchange, enabling efficient and reliable interoperability among different systems.
These are just a few examples of how AI can be applied to enhance IT interoperability among member states and private companies in Europe. The potential applications of AI in this domain are vast and continually evolving as technology advances.
LOST view: Organisational view
Identifier: http://data.europa.eu/dr8/egovera/ArtificialIntelligenceCapability
ABB name: eira:ArtificialIntelligenceCapability
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/egovera/ArtificialIntelligenceCapability
Name: Artificial Intelligence Digital Business Capability
Interoperability Layer: Organisational
Specialises: http://data.europa.eu/dr8/DigitalBusinessCapability
Definition: Electronic Identification ensures secure access to online services and to carry out electronic transactions in a safer way to citizens or organizations (i.e. public administrations and businesses). Via digital modes, electronic identification can guarantee the unambiguous identification of a person or business and ensures the right service is delivered to the person or business entitled to it. (e.g. government authorities services, digital payments services, ...).
Source reference: https://digital-strategy.ec.europa.eu/en/policies/electronic-identification
Additional information: The Electronic Identification (eID) Digital Business Capability is a crucial component of the European Union's efforts to establish seamless interoperability among member states and private companies in the field of information technology. It aims to provide a standardized and secure framework for electronic identification and authentication across borders, enabling individuals and businesses to access digital services and conduct transactions in a trusted and efficient manner.
At its core, the eID Digital Business Capability revolves around the concept of a digital identity, which serves as a virtual representation of an individual or organization. This digital identity is securely stored and managed by trusted entities, such as government agencies or private service providers, and can be used to establish the identity of the user in various online interactions.
The primary objective of the eID Digital Business Capability is to enable individuals and businesses to use their digital identities to access a wide range of services, both public and private, across different member states. This includes services such as e-government platforms, online banking, e-commerce, healthcare systems, and more. By providing a standardized and interoperable framework, the capability ensures that users can seamlessly authenticate themselves and access these services regardless of their location within the European Union.
To achieve this interoperability, the eID Digital Business Capability relies on a set of technical standards and protocols that enable the secure exchange of identity information between different systems and entities. These standards ensure that digital identities issued by one member state or private entity can be recognized and accepted by others, thereby facilitating cross-border transactions and interactions.
The capability also encompasses the establishment of a network of trust among member states and private entities. This network ensures that the digital identities issued by one entity are trusted and accepted by others, thereby enhancing the overall security and reliability of the system. This trust network is built upon the principles of mutual recognition, where member states and private entities agree to accept and recognize each other's digital identities based on predefined criteria and standards.
Furthermore, the eID Digital Business Capability places a strong emphasis on privacy and data protection. It ensures that individuals have control over their personal data and can consent to its use for specific purposes. The capability also incorporates mechanisms for secure authentication, such as two-factor authentication or biometric verification, to enhance the overall security of digital transactions.
In summary, the eID Digital Business Capability is a comprehensive framework that aims to establish seamless interoperability among member states and private companies in the European Union. It enables individuals and businesses to use their digital identities to access a wide range of services across borders, while ensuring privacy, security, and trust in the digital ecosystem.
Example: The Electronic Identification (eID) Digital Business Capability has several applications in the context of European IT interoperability among member states and private companies. Here are some examples:
1. Cross-border authentication: eID enables individuals to use their national electronic identification credentials to access online services in other member states. This allows for seamless authentication and access to various services, such as e-government portals, banking, healthcare, and more.
2. Digital signatures and document exchange: eID facilitates the use of digital signatures for secure and legally binding transactions across borders. It enables individuals and businesses to digitally sign documents, contracts, and forms, eliminating the need for physical paperwork and enabling efficient cross-border document exchange.
3. Trusted e-commerce: eID can be used to establish trust in online transactions between businesses and consumers across different member states. It allows for secure identification and authentication of individuals, reducing the risk of fraud and enhancing consumer confidence in cross-border e-commerce.
4. Seamless access to public services: eID enables citizens to access public services in other member states without the need for additional identification procedures. For example, a citizen from one member state can use their eID to access healthcare services or file taxes in another member state, simplifying administrative processes and enhancing cross-border service delivery.
5. Interoperable electronic invoicing: eID can be integrated with electronic invoicing systems to ensure secure and interoperable exchange of invoices between businesses across member states. This streamlines cross-border invoicing processes, reduces administrative burdens, and enhances efficiency in business transactions.
6. Secure data sharing: eID can facilitate secure and controlled sharing of personal data between member states and private companies. It ensures that data is accessed only by authorized individuals or organizations, maintaining privacy and data protection standards while enabling efficient cross-border data exchange for various purposes, such as research, public administration, or business collaborations.
These examples highlight how the application of eID as a digital business capability contributes to European IT interoperability, enabling seamless cross-border transactions, secure data exchange, and efficient access to services across member states and private companies.
LOST view: Organisational view
Identifier: http://data.europa.eu/dr8/egovera/ElectronicIdentificationCapability
ABB name: eira:ElectronicIdentificationCapability
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/egovera/ElectronicIdentificationCapability
Name: Electronic Identification Digital Business Capability
Interoperability Layer: Organisational
Specialises: http://data.europa.eu/dr8/DigitalBusinessCapability
Description: The 'Special Procedure' digital business capability refers to the ability of a business to execute unique or specialized processes or operations using digital technologies. This could involve the use of advanced software, hardware, or digital tools to carry out tasks that are specific to the business or industry. These special procedures could include proprietary algorithms, unique data analysis methods, specialized manufacturing processes, or any other digital processes that give the business a competitive advantage. This capability is crucial in today's digital age as it allows businesses to differentiate themselves from competitors and deliver unique value to customers.
Additional information: The 'Special Procedure' Digital Business Capability refers to the ability of an organization to execute unique, non-standard processes or operations that are critical to its business model or strategy, leveraging digital technologies. This capability is not about routine, everyday operations but rather about specific procedures that are unique to the organization or its industry.
These special procedures could include anything from complex data analysis, proprietary manufacturing processes, unique service delivery methods, specialized regulatory compliance activities, to innovative customer engagement techniques. They are often the result of an organization's unique expertise, intellectual property, or strategic focus.
The digital aspect of this capability refers to the use of digital technologies to enable, enhance, automate, or transform these special procedures. This could involve the use of advanced analytics, artificial intelligence, machine learning, robotics, IoT, blockchain, or other emerging technologies.
The 'Special Procedure' Digital Business Capability requires an organization to have the necessary digital infrastructure, skills, and culture. It also requires a deep understanding of the organization's unique processes and the ability to leverage technology to optimize these processes. This capability can provide a significant competitive advantage, enabling an organization to perform unique procedures more effectively, efficiently, or innovatively than its competitors.
In the context of TOGAF, this capability would be part of the organization's overall enterprise architecture, aligning with its business strategy and objectives, and would need to be carefully managed, governed, and evolved over time.
Example: 1. Online Tax Filing: Many public sector organizations such as the Internal Revenue Service (IRS) in the United States have implemented digital business capabilities to allow citizens to file their taxes online. This special procedure involves secure data transmission, automatic calculation of tax obligations, and instant submission of tax forms.
2. Digital Voting: Some countries are experimenting with digital voting systems to increase voter participation and reduce the cost of elections. This involves secure online platforms where citizens can cast their votes, which are then automatically tallied and verified.
3. E-Health Records: Public health organizations are increasingly using digital systems to manage patient records. This involves secure databases where patient information is stored and can be accessed by authorized healthcare professionals.
4. Online License Renewal: Many departments of motor vehicles (DMVs) offer online services for renewing driver's licenses and vehicle registrations. This involves secure online payment systems and automatic updating of DMV records.
5. E-Learning Platforms: Public education institutions are increasingly using digital platforms to deliver courses and educational materials. This involves online learning management systems where students can access course materials, submit assignments, and communicate with teachers.
6. Digital Public Procurement: Governments are implementing digital platforms to manage public procurement processes. This involves online systems where suppliers can submit bids, and public officials can evaluate and award contracts.
7. Online Immigration Services: Immigration departments are offering online services for visa applications and renewals. This involves secure online forms and payment systems, as well as digital systems for tracking application status.
8. E-Government Portals: Many governments have implemented comprehensive e-government portals that provide a wide range of public services online. These portals often involve complex digital systems that integrate various government departments and services.
Publisher: EIRA Team
LOST view: OV-Special procedure [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/SpecialProcedureCapability
EIRA traceability: eira:DigitalBusinessCapability
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-08-08
dct:identifier: http://data.europa.eu/dr8/egovera/SpecialProcedureCapability
dct:title: Special procedure (DBC)
Description: The 'Export Procedure' Digital Business Capability refers to the ability of a business to effectively manage and execute all processes related to exporting goods or services through digital means. This includes understanding and complying with international trade regulations, managing logistics, handling documentation, and ensuring secure and efficient transactions. It also involves the use of digital technologies and platforms to facilitate these processes, such as e-commerce platforms, digital payment systems, and supply chain management software. This capability is crucial for businesses operating in the global market, as it directly impacts their ability to deliver products or services to customers outside their home country.
Additional information: The 'Export Procedure' Digital Business Capability refers to the ability of a business to manage, control, and execute all the necessary processes and operations related to exporting goods or services digitally. This capability encompasses a wide range of activities, including but not limited to:
1. Compliance with International Trade Regulations: This includes understanding and adhering to the various rules, regulations, and laws that govern international trade. It involves ensuring that all export activities are compliant with the export control laws of the home country as well as the import regulations of the destination countries.
2. Documentation and Licensing: This involves the preparation, submission, and management of all necessary export documentation such as export licenses, customs declarations, and shipping documents. It also includes managing digital systems that track and store these documents.
3. Logistics and Supply Chain Management: This includes planning, implementing, and controlling the efficient, effective forward and reverse flow and storage of goods, services, and related information between the point of origin and the point of consumption to meet customers' requirements.
4. Risk Management: This involves identifying, assessing, and mitigating various risks associated with exporting such as financial risks, operational risks, and compliance risks. It also includes managing insurance and claims processes.
5. Customer Service: This involves managing relationships with customers, addressing their queries and concerns, and ensuring their satisfaction with the export process.
6. Financial Management: This includes managing the financial aspects of exporting such as pricing, invoicing, payment collection, currency exchange, and financial reporting.
7. Technology Management: This involves leveraging digital technologies and systems to facilitate and streamline the export process. This could include the use of e-commerce platforms, digital payment systems, blockchain technology for secure and transparent transactions, AI for demand forecasting, and IoT for real-time tracking of goods.
8. Strategic Planning: This involves developing and implementing strategic plans for expanding the business into new markets, improving export operations, and staying competitive in the global market.
The 'Export Procedure' Digital Business Capability requires a combination of digital technologies, skilled personnel, efficient processes, and strategic management to effectively carry out export activities in a digital environment.
Example: 1. Export Certification System: In the agriculture department, they may have a digital system that manages the issuance of export certificates for agricultural products. This system would ensure that all products being exported meet the necessary health and safety standards of the destination country.
2. Trade Information Portal: A government may have a digital portal that provides all necessary information about export procedures, regulations, tariffs, and trade agreements. This portal would be a one-stop-shop for businesses looking to export goods and services.
3. Customs Declaration System: A digital system used by customs authorities to manage the declaration and clearance of goods for export. This system would streamline the process, reduce paperwork, and increase efficiency.
4. Export Licensing System: In the defense sector, a digital system might be used to manage the issuance of export licenses for defense-related products. This system would ensure compliance with international export control regulations.
5. Digital Export Promotion: A government might use digital marketing strategies and platforms to promote its country's goods and services to potential international buyers. This could include social media campaigns, online trade fairs, and digital advertising.
6. E-Export Documentation: A digital system that allows exporters to submit and manage all necessary export documentation online. This system would reduce the need for physical paperwork and make the export process more efficient.
7. Online Training Platform: A government might offer online training courses on export procedures and regulations. This platform would help businesses understand how to successfully export their goods and services.
8. Export Finance System: A digital system used by a government agency to provide financial support to exporters. This could include loans, insurance, and guarantees to help businesses manage the risks associated with exporting.
Publisher: EIRA Team
LOST view: OV-Export procedure [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/ExportProcedureCapability
EIRA traceability: eira:DigitalBusinessCapability
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-08-08
dct:identifier: http://data.europa.eu/dr8/egovera/ExportProcedureCapability
dct:title: Export procedure (DBC)
Description: 'Cooperation between Customs and Postal Operators' Digital Business Capability refers to the ability of a business to leverage digital technologies to facilitate seamless collaboration between customs and postal operators. This includes the use of digital platforms for real-time information sharing, tracking, and communication to ensure efficient handling and delivery of parcels. It also involves the use of digital systems for customs declaration, duties and taxes calculation, and compliance with international trade regulations. This capability enhances the speed and accuracy of customs clearance processes, improves service delivery, and promotes regulatory compliance.
Additional information: The 'Cooperation between Customs and Postal Operators' Digital Business Capability refers to the ability of a business, specifically within the customs and postal sectors, to effectively collaborate and coordinate their operations through digital means. This capability encompasses a wide range of activities and processes, all of which are facilitated by digital technologies.
At its core, this capability involves the use of digital systems and platforms to streamline and enhance the exchange of information and data between customs and postal operators. This could include, for example, the use of digital platforms for sharing information about incoming and outgoing shipments, tracking parcels, managing customs declarations, and coordinating delivery schedules.
Furthermore, this capability also includes the ability to leverage digital technologies to improve operational efficiency and effectiveness. For instance, customs and postal operators might use digital tools to automate certain processes, such as the sorting and scanning of parcels, thereby reducing manual labor and minimizing errors.
In addition, this capability also involves the ability to use digital technologies to enhance communication and collaboration between customs and postal operators. This could involve the use of digital communication tools, such as email, instant messaging, and video conferencing, to facilitate real-time communication and collaboration.
Moreover, this capability also includes the ability to leverage digital technologies to improve compliance with customs regulations. For instance, digital systems could be used to automatically check parcels against customs databases, thereby ensuring that all shipments comply with relevant laws and regulations.
Finally, this capability also involves the ability to use digital technologies to improve customer service. For instance, digital systems could be used to provide customers with real-time tracking information, thereby enhancing transparency and improving customer satisfaction.
In summary, the 'Cooperation between Customs and Postal Operators' Digital Business Capability involves the use of digital technologies to enhance collaboration and coordination between customs and postal operators, improve operational efficiency and effectiveness, enhance compliance with customs regulations, and improve customer service.
Example: 1. Cross-Border E-Commerce Program: In the United States, the Customs and Border Protection (CBP) and the United States Postal Service (USPS) have collaborated to streamline the process of inspecting and clearing international mail. This cooperation has resulted in the development of a digital platform that allows for real-time data exchange, improving the speed and accuracy of customs clearance.
2. Electronic Advance Data (EAD): The Universal Postal Union (UPU) has developed a system that allows postal operators to share advance electronic data with customs authorities. This data includes information about the sender, recipient, and contents of the parcel, which helps customs authorities to assess the risk level of the parcel and decide whether it needs to be inspected.
3. Integrated Border Management System: In the European Union, customs and postal operators work together under the Integrated Border Management System. This system uses digital technologies to facilitate the exchange of information and cooperation between different border control agencies, including customs and postal services.
4. Digital Customs Declaration: In many countries, postal operators have introduced digital customs declaration forms that customers can fill out online. This not only speeds up the process for customers but also allows customs authorities to process and clear parcels more quickly and efficiently.
5. Track and Trace Systems: Many postal operators have developed digital track and trace systems that allow customers to follow the progress of their parcels in real time. These systems also provide customs authorities with valuable data that can be used to improve their risk assessment and inspection processes.
6. E-Customs Partnership in China: China Customs has partnered with China Post to establish an e-customs clearance system for cross-border e-commerce. The system allows for the electronic submission of customs declarations and the real-time tracking of parcels, improving the efficiency and transparency of the customs clearance process.
Publisher: EIRA Team
LOST view: OV-Cooperation between Customs and Postal Operators [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/CooperationBetweenCustomsAndPostalOperatorsCapability
EIRA traceability: eira:DigitalBusinessCapability
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-08-08
dct:identifier: http://data.europa.eu/dr8/egovera/CooperationBetweenCustomsAndPostalOperatorsCapability
dct:title: Cooperation between Customs and Postal Operators (DBC)
Definition: Digital Exchange enables the transmission of digitally encoded information to profiled targets of stakeholders.
Source: Fred Turner
Source reference: https://books.google.it/books?id=2SNFpgX_WigC&pg=PA131&redir_esc=y#v=onepage&q&f=false
Additional information: The Digital Exchange Digital Business Capability (DBC) is a comprehensive framework established to facilitate and enhance IT interoperability among member states and private companies within the European Union (EU). It aims to create a seamless digital environment that enables the exchange of data, information, and services across borders, fostering collaboration and innovation in the digital economy.
The DBC recognizes the importance of interoperability in enabling efficient and effective communication, cooperation, and integration of digital systems and services. It seeks to address the challenges posed by the diverse IT landscapes, differing technical standards, and varying legal and regulatory frameworks across member states.
At its core, the DBC focuses on establishing a common set of technical specifications, standards, and protocols that ensure seamless connectivity and data exchange between different digital systems. It promotes the use of open standards and open interfaces, enabling interoperability between various IT systems, platforms, and applications.
The DBC also emphasizes the importance of data sharing and accessibility. It encourages the development of common data models, formats, and APIs (Application Programming Interfaces) that enable the secure and standardized exchange of data across different systems. This facilitates the integration of data from various sources, enabling the creation of new digital services and applications.
Furthermore, the DBC recognizes the need for trust and security in digital exchanges. It promotes the use of secure authentication mechanisms, encryption techniques, and privacy-enhancing technologies to protect the confidentiality, integrity, and availability of exchanged data. It also emphasizes compliance with relevant data protection and privacy regulations, such as the General Data Protection Regulation (GDPR) within the EU.
The DBC is not limited to the public sector but also extends its scope to private companies operating within the EU. It encourages the adoption of interoperability principles and standards by private enterprises, enabling them to seamlessly collaborate and integrate their digital systems with those of other organizations. This promotes cross-sectoral cooperation and innovation, leading to the development of new digital products, services, and business models.
To support the implementation of the DBC, the EU provides various tools and resources. These include technical guidelines, reference architectures, best practices, and interoperability frameworks that assist member states and private companies in adopting and implementing interoperability solutions. The EU also facilitates knowledge sharing and collaboration through workshops, conferences, and communities of practice.
In summary, the Digital Exchange Digital Business Capability is a comprehensive framework that aims to enhance IT interoperability among member states and private companies within the EU. It promotes the use of common technical specifications, standards, and protocols, facilitates data sharing and accessibility, ensures trust and security, and encourages collaboration and innovation in the digital economy. By fostering interoperability, the DBC enables the seamless exchange of data, information, and services, driving the digital transformation and integration of the European IT landscape.
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): ePrescription: "Generation, transmission, and filling of a medical prescription through digital channels. ePrescribing allows a physician, pharmacist, nurse practitioner, or physician assistant to use digital prescription software to electronically transmit a new prescription or renewal authorization to a community or mail-order pharmacy".
LOST view: Organisational view
Identifier: http://data.europa.eu/dr8/egovera/DigitalExchangeCapability
ABB name: eira:DigitalExchangeCapability
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/egovera/DigitalExchangeCapability
Name: Digital Exchange Digital Business Capability
Interoperability Layer: Organisational
Specialises: http://data.europa.eu/dr8/DigitalBusinessCapability
Description: The Data Ethics Digital Business Capability refers to an organization's ability to ensure ethical practices and responsible use of data in its digital operations. It involves establishing policies, guidelines, and frameworks that govern the collection, storage, processing, and sharing of data, with a focus on maintaining privacy, security, and compliance with legal and regulatory requirements. This capability also encompasses the development of ethical data practices, such as transparency, consent, and accountability, to build trust with customers, partners, and stakeholders. By prioritizing data ethics, organizations can mitigate risks, protect individuals' rights, and foster a culture of responsible data management in the digital era.
Additional information: The Data Ethics Digital Business Capability refers to the organization's ability to establish and maintain ethical practices and principles related to the collection, storage, processing, and usage of data. It encompasses the policies, procedures, and frameworks that ensure the responsible and ethical handling of data throughout its lifecycle.
This capability involves understanding and adhering to legal and regulatory requirements, industry standards, and best practices concerning data privacy, security, consent, transparency, and accountability. It aims to protect individuals' rights and interests while enabling the organization to leverage data effectively for business purposes.
Key components of the Data Ethics Digital Business Capability include:
1. Data Governance: This involves establishing a framework for data management, including defining roles, responsibilities, and processes for data handling. It ensures that data is collected, stored, and used in compliance with applicable laws and regulations.
2. Privacy and Consent Management: This component focuses on obtaining appropriate consent from individuals for data collection and processing activities. It includes implementing mechanisms to manage and respect individuals' privacy rights, such as providing clear and transparent privacy notices and enabling individuals to exercise their rights over their data.
3. Data Security: This component encompasses measures to protect data from unauthorized access, use, disclosure, alteration, or destruction. It involves implementing robust security controls, encryption, access controls, and monitoring mechanisms to safeguard data against potential threats and breaches.
4. Ethical Data Use: This component emphasizes the responsible and ethical use of data. It involves establishing guidelines and policies for data usage, ensuring that data is used only for legitimate business purposes and in a manner that respects individuals' rights and interests.
5. Data Transparency and Accountability: This component focuses on promoting transparency and accountability in data practices. It includes providing individuals with clear information about how their data is being used, enabling them to make informed choices. It also involves establishing mechanisms for individuals to access, rectify, or delete their data and addressing any concerns or complaints related to data handling.
6. Training and Awareness: This component emphasizes the importance of educating employees about data ethics and their responsibilities in handling data. It includes providing training programs, awareness campaigns, and resources to ensure that employees understand and adhere to ethical data practices.
7. Continuous Improvement: This component involves regularly reviewing and updating data ethics practices to align with evolving legal, regulatory, and industry requirements. It includes conducting audits, assessments, and risk evaluations to identify areas for improvement and implementing necessary changes to enhance data ethics capabilities.
By developing and maintaining the Data Ethics Digital Business Capability, organizations can build trust with their customers, partners, and stakeholders. It helps them mitigate risks associated with data breaches, regulatory non-compliance, and reputational damage while fostering a culture of responsible data handling and ethical decision-making.
Example: The Data Ethics Digital Business Capability in the public sector refers to an organization's ability to ensure ethical practices and compliance with data protection regulations while leveraging digital technologies. Here are some real examples of this capability in action:
1. Privacy Impact Assessments (PIAs): Public sector organizations conduct PIAs to assess the potential privacy risks associated with new digital initiatives. For instance, when implementing a citizen-facing online service, a government agency may evaluate the data collection, storage, and usage practices to ensure compliance with privacy regulations and ethical standards.
2. Data anonymization and de-identification: Public sector entities often deal with sensitive citizen data. To protect privacy, they employ techniques like data anonymization and de-identification. For example, a health department might remove personally identifiable information from medical records before sharing them with researchers, ensuring privacy while enabling valuable data analysis.
3. Ethical AI and algorithmic governance: Public sector organizations increasingly employ artificial intelligence (AI) and algorithms to improve decision-making processes. The Data Ethics capability ensures that these technologies are used ethically and fairly. For instance, an employment agency may implement algorithmic governance frameworks to prevent bias in AI-driven hiring processes, ensuring equal opportunities for all candidates.
4. Consent management and data transparency: Public sector entities prioritize obtaining informed consent from citizens for data collection and usage. They also focus on providing transparent information about how data is handled. For instance, a tax authority may allow citizens to manage their consent preferences for sharing tax-related data with other government agencies, ensuring control and transparency over personal information.
5. Data breach response and incident management: Public sector organizations need to be prepared for data breaches and incidents. The Data Ethics capability includes establishing protocols for timely response, notification, and mitigation of such events. For example, a local government may have a well-defined incident response plan to handle a cybersecurity breach, ensuring minimal impact on citizen data and privacy.
These examples demonstrate how the Data Ethics Digital Business Capability in the public sector ensures responsible and ethical handling of data while leveraging digital technologies to deliver efficient and citizen-centric services.
Publisher: EIRA Team
LOST view: OV-Data Spaces [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/DataEthicsCapability
EIRA traceability: eira:DigitalBusinessCapability
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-07-10
dct:identifier: http://data.europa.eu/dr8/egovera/DataEthicsCapability
dct:title: Data Ethics Digital Business Capability
Definition: Public Policy ABB is a Course of Action allowing public authorities to bring social change in the medium and long term, in a given area.
Source: EuroVoc
Source reference: 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
Synonym: Policy Action
Additional information: A Public Policy 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.The policies overview of EU activities in all areas, from agriculture to transport: (http://ec.europa.eu/policies/index_en.htm)
Example: The Common Agricultural Policy (CAP, https://ec.europa.eu/info/strategy/agriculture_en) is an example on how the Public Policy Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB). The common agricultural policy (CAP) – one of Europe’s oldest policies – has evolved along with the EU. Today's CAP supports a modern, market-oriented farming sector ensuring the provision of safe, affordable, high quality food, produced sustainably and respecting strict standards (environmental, animal welfare, food safety, etc.), as well as supporting investment in the broader rural economy.
Interoperability Dimension: Structural IoP
LOST view: Legal view
Viewpoint: Interoperability Security viewpoint
Interoperability Saliency: The Public Policy ABB is salient for legal interoperability because it drives the production and formulation of legislation, and it is one of the main context elements to be taken into account when different organisations need to work together, as stated in the EIF: "Legal interoperability is about ensuring that organisations operating under different legal frameworks, policies and strategies are able to work together".
Identifier: http://data.europa.eu/dr8/PublicPolicyCourseOfAction
ABB name: eira:PublicPolicyCourseOfAction
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/PublicPolicyCourseOfAction
Interoperability Layer: Legal
Definition: Digital Public Service Human Agent ABB is a Business Actor representing a stakeholder who works in the public service sector and uses digital technologies to improve the delivery of public services to citizens. This agent has the potential to improve the accessibility, efficiency, and quality of public services, ultimately leading to better outcomes for citizens and society as a whole.
Source: Inspired on the information available in Digital Public Services in the Digital Economy and Society Index
Source reference: https://digital-strategy.ec.europa.eu/en/policies/desi-digital-public-services
Example: The following implemenation is an example of how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): OECD Goverment as a Glance (https://www.oecd.org/gov/government-at-a-glance-22214399.htm)
Interoperability Dimension: Structural IoP
LOST view: Organisational view
Interoperability Saliency: The Digital Public Service Human Agent ABB is salient for organizational and behavioural interoperability because it permits the identification of procedures and business rules related to human interactions in public administration. This identification and consensus will facilitate the exchange of data, information and knowledge between public services and human stakeholders.
Identifier: http://data.europa.eu/dr8/DigitalPublicServiceHumanAgentBusinessActor
ABB name: eira:DigitalPublicServiceHumanAgentBusinessActor
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/DigitalPublicServiceHumanAgentBusinessActor
Interoperability Layer: Organisational
Definition: Digital Public Service Machine Agent ABB is a Business Actor defined as the system that is designed to automate and improve the delivery of public services to citizens.
Source: Inspired on the information available in Digital Public Services in the Digital Economy and Society Index
Source reference: https://digital-strategy.ec.europa.eu/en/policies/desi-digital-public-services
Example: The following implementation is an example of how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): Digital Public Administration Facsheet (https://joinup.ec.europa.eu/sites/default/files/inline-files/DPA_Factsheets_2022_France_vFinal_0.pdf) or the Spanish public administration digitalization plan (https://portal.mineco.gob.es/RecursosArticulo/mineco/ministerio/ficheros/210902-digitalisation-of-public-admin-plan.pdf)
Interoperability Dimension: Structural IoP
LOST view: Organisational view
Interoperability Saliency: The Digital Public Service Machine Agent ABB is salient for organizational and behavioural interoperability because it permits the identification of procedures and business rules related to digital services of public administrations. This identification and consensus will facilitate the exchange of data, information and knowledge between machine-to-machine and machine-to-human interactions.
Identifier: http://data.europa.eu/dr8/DigitalPublicServiceMachineAgentBusinessActor
ABB name: eira:DigitalPublicServiceMachineAgentBusinessActor
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/DigitalPublicServiceMachineAgentBusinessActor
Interoperability Layer: Organisational
Definition: Digital Public Service Delivery Model ABB is a Business Collaboration representing a collection of concepts related to the way in which the public sector delivers digital technologies to citizens and businesses.
Source: OECD
Source reference: https://www.oecd-ilibrary.org/docserver/gov_glance-2017-72-en.pdf?expires=1649771036&id=id&accname=guest&checksum=15BFD2F7E916921236CCF160605A6430
Example: The following implementation is an example of how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): OECD Public service design and delivery in the digital age (https://www.oecd-ilibrary.org/sites/3252a73a-en/index.html?itemId=/content/component/3252a73a-en)
Interoperability Dimension: Structural IoP
LOST view: Organisational view
Viewpoint: Highlevel viewpoint
Interoperability Saliency: Digital Public Service Delivery Model ABB is salient for organizational and behavioural interoperability due to it permits to (i) reuse and share common digital services across different public administrations to deploy and publish digital services, (ii) establish common business procedures to elaborate and form the digital services for public administration, (iii) the maintenance procedures to make available such digital services.
Identifier: http://data.europa.eu/dr8/DigitalPublicServiceDeliveryModelBusinessCollaboration
ABB name: eira:DigitalPublicServiceDeliveryModelBusinessCollaboration
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/DigitalPublicServiceDeliveryModelBusinessCollaboration
Interoperability Layer: Organisational
Definition: Digital Public Service Provision ABB is a Business Function representing the delivery of services through digital channels aiming at incresing transparency, efficiency and responsiveness of public organizations
Source: [OECD, Springer, EC Digital Public Service Provision Needs document]
Source reference: [https://www.oecd-ilibrary.org/docserver/gov_glance-2017-72-en.pdf?expires=1649771036&id=id&accname=guest&checksum=15BFD2F7E916921236CCF160605A6430, https://joinup.ec.europa.eu/collection/better-legislation-smoother-implementation/document/digital-public-service-provision-needs-digitally-compatible-law-modular-concept-income, https://link.springer.com/chapter/10.1007/978-3-030-91247-5_3]
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): The Spanish Tax Agency is responsible for providing Digital Public Services on TAX payment. https://sede.agenciatributaria.gob.es/Sede/en_gb/iva.html
Interoperability Dimension: Structural IoP
LOST view: Organisational view
Interoperability Saliency: The Digital Public Service Provision ABB is salient for organizational and semantic interoperability because it offers (i) mechanisms to exchange information transparently; (ii) manage the information with needed security and trust; (iii) combine and harmonise information coming from multiple data stores to give service to the different agents (or stakeholders)
Identifier: http://data.europa.eu/dr8/DigitalPublicServiceProvisionBusinessFunction
ABB name: eira:DigitalPublicServiceProvisionBusinessFunction
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/DigitalPublicServiceProvisionBusinessFunction
Interoperability Layer: Organisational
Definition: Web APP ABB is a Business Interface that corresponds to a computer program that runs on a web browser and is accessible through the internet
Source: ISO/IEC/IEEE 23026:2015
Source reference: https://www.iso.org/obp/ui/#iso:std:iso-iec-ieee:23026:ed-1:v1:en
Example: The following implementation is an example of how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): Digital Signature Service (DSS) Web Application. https://ec.europa.eu/digital-building-blocks/DSS/webapp-demo/home
Interoperability Dimension: Behavioral IoP
LOST view: Organisational view
Interoperability Saliency: Web App ABB is salient for organizational, semantic and technical interoperability because it offers (i) a visual environment to interact with the public service procedures and data; (ii) an understanding of the information to be represented; and (iii) an elaborate mechanism to exchange data with public services.
Identifier: http://data.europa.eu/dr8/WebAppBusinessInterface
ABB name: eira:WebAppBusinessInterface
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/WebAppBusinessInterface
Interoperability Layer: Organisational
Definition: Service APP ABB is a Business Interface is a a type of software application that provides specific functionality to other applications or users within a larger system. Service applications are designed to operate in the background and provide specific services, such as database access, messaging, authentication, or other functionality, to other applications that require those services
Source: Inspired in ETSI TR 103 290
Source reference: https://www.etsi.org/deliver/etsi_tr/103200_103299/103290/01.01.01_60/tr_103290v010101p.pdf
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): EUROTRACE is a powerful and flexible software application that provides the structures and tools for the management of statistical data. EUROTRACE can be used as a production system for the integration, validation and management of statistical datasets and can be used with the following DBMS: MS ACCESS, ORACLE, SQL Server. https://joinup.ec.europa.eu/sites/default/files/document/2014-04/Eurotrace%20DBMS%202.6%20UG_EN.pdf
Interoperability Dimension: Behavioral IoP
LOST view: Organisational view
Interoperability Saliency: Service App ABB is salient for organizational, semantic and technical interoperability because it establishes the mechanisms to provide data and services to public service consumers. The Service App ABB will identify and implement needed mechanisms to (i) deliver data according to the digital service procedures, and (ii) enable service and data discovery.
Identifier: http://data.europa.eu/dr8/ServiceAppBusinessInterface
ABB name: eira:ServiceAppBusinessInterface
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/ServiceAppBusinessInterface
Interoperability Layer: Organisational
Definition: Desktop APP ABB is a Business Interface that corresponds to a computer program designed to run on a desktop or laptop computer, typically with a graphical user interface (GUI)
Source: Inspired in "Information Technology and Computer Applications in Public Administration" book
Source reference: ISBN 978-81-317-3309-7
Example: The following implementation is an example of how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): Electronic Invoice Management Desktop Application, The Electronic Invoice Management desktop application developed by the Ministry of Industry, Energy and Tourism is used to create electronic invoices in the Facturae format (Order PRE/2971/2007) in an easy and simple way. Developed with open-source software, this application is targeted at micro-, small- and medium-sized enterprises (SMEs) and freelance workers, solving the problems associated with the storage of paper invoices. https://joinup.ec.europa.eu/collection/spain-center-technology-transfer/solution/electronic-invoice-management-desktop-application/about
Interoperability Dimension: Behavioral IoP
LOST view: Organisational view
Interoperability Saliency: Desktop App ABB is salient for organizational, semantic and technical interoperability because it offers (i) a visual environment to interact with the public service procedures and data; (ii) an understanding of the information to be represented; and (iii) an elaborate mechanism to exchange data with public services.
Identifier: http://data.europa.eu/dr8/DesktopAppBusinessInterface
ABB name: eira:DesktopAppBusinessInterface
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/DesktopAppBusinessInterface
Interoperability Layer: Organisational
Definition: Mobile APP ABB is a Business Interface that corresponds to a computer program designed to run on a mobile device, such as a smartphone or tablet
Source: ISO/IEC 29179:2012
Source reference: https://www.iso.org/standard/45258.html
Example: The following implementation is an example of how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): EU Council mobile app. https://play.google.com/store/apps/details?id=eu.europa.publications.eucouncil&hl=en_US&gl=US&pli=1
Interoperability Dimension: Behavioral IoP
LOST view: Organisational view
Interoperability Saliency: Mobile App ABB is salient for organizational, semantic and technical interoperability because it offers (i) a visual environment to interact with the public service procedures and data; (ii) an understanding of the information to be represented; and (iii) an elaborate mechanism to exchange data with public services.
Identifier: http://data.europa.eu/dr8/MobileAppBusinessInterface
ABB name: eira:MobileAppBusinessInterface
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/MobileAppBusinessInterface
Interoperability Layer: Organisational
Definition: Adaptive Configuration ABB is a Business Interface that refers to the ability of a system or application to dynamically adjust its settings or configuration based on changing conditions or user preferences. This allows the system to optimize its performance and adapt to different environments or situations.
Source: INSPIRED in Science Direct
Source reference: https://www.sciencedirect.com/topics/engineering/adaptive-systems
Example: The following implementation is an example of how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): An example of adaptive configuration is the automatic configuration that mobile phones include to keep the signal for using mobile data. Another aspect that is also related to Data is the "Adaptive Data Rate" Adaptive Data Rate (ADR) is a mechanism for optimizing data rates, airtime and energy consumption in the network. The ADR mechanism controls the following transmission parameters of an end device: 1. Spreading factor; 2. Bandwidth; 3. Transmission power. https://www.thethingsnetwork.org/docs/lorawan/adaptive-data-rate/
Interoperability Dimension: Behavioral IoP
LOST view: Organisational view
Interoperability Saliency: Adaptive Configuration ABB is salient for organizational, semantic and technical interoperability because it establishes the mechanism to adapt the procedures and data delivery according to the data consumption needs.
Identifier: http://data.europa.eu/dr8/AdaptiveConfigurationBusinessInterface
ABB name: eira:AdaptiveConfigurationBusinessInterface
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/AdaptiveConfigurationBusinessInterface
Interoperability Layer: Organisational
Definition: Digital Public Service Delivery ABB is a Business Interface representing the way in which the public sector delivers digital technologies and public services to citizens and businesses.
Source: OECD
Source reference: https://www.oecd-ilibrary.org/docserver/gov_glance-2017-72-en.pdf?expires=1649771036&id=id&accname=guest&checksum=15BFD2F7E916921236CCF160605A6430
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): The Spanish Tax Agency is responsible for providing Digital Public Services on TAX payment. https://sede.agenciatributaria.gob.es/Sede/en_gb/iva.html
Interoperability Dimension: Behavioral IoP
LOST view: Organisational view
Viewpoint: Highlevel viewpoint
Interoperability Saliency: The Digital Public Service Delivery ABB is a key interoperability enabler (*) for organizational and semantic interoperability because it defines the mechanism to deliver digital services in terms of (i) establishing a mechanism to interact with the data; (ii) establishing rules to validate the data and procedures; and (iii) provide a transparent response to the different petitions from the stakeholders.
Identifier: http://data.europa.eu/dr8/DigitalPublicServiceDeliveryBusinessInterface
ABB name: eira:DigitalPublicServiceDeliveryBusinessInterface
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/DigitalPublicServiceDeliveryBusinessInterface
Interoperability Layer: Organisational
Definition: A location is a region (point, line, or area) on Earth's surface
Source: WikiPedia
Source reference: https://en.wikipedia.org/wiki/Location
Additional information: Location, as an element or component of information in the European IT context, refers to the specific geographical position or coordinates associated with a particular entity, device, or event. It provides crucial context and enables the identification and tracking of objects, individuals, or phenomena within a given geographic area.
In the European IT context, location information is often obtained through various technologies such as Global Positioning System (GPS), cellular networks, Wi-Fi, and Internet Protocol (IP) address geolocation. These technologies allow for the determination of the latitude, longitude, altitude, and sometimes even the orientation of a specific point on the Earth's surface.
Location information plays a significant role in a wide range of applications and services across various industries. In the European IT context, it is extensively utilized in navigation systems, mapping applications, logistics and supply chain management, transportation services, emergency response systems, and location-based marketing.
For instance, in navigation systems, location information is used to provide turn-by-turn directions, real-time traffic updates, and estimated arrival times. Mapping applications leverage location data to display maps, points of interest, and provide geographically relevant information to users. In logistics and supply chain management, location information helps track the movement of goods, optimize routes, and ensure efficient delivery.
Emergency response systems heavily rely on location information to accurately identify the location of emergency calls and dispatch appropriate assistance. Additionally, location-based marketing utilizes location data to deliver targeted advertisements and promotions to users based on their proximity to specific businesses or areas of interest.
In the European IT context, the collection, storage, and processing of location information are subject to strict regulations and privacy laws, such as the General Data Protection Regulation (GDPR). These regulations aim to protect individuals' privacy and ensure that their location data is handled responsibly and with their consent.
Overall, location information is a fundamental component of information in the European IT context, enabling a wide range of applications and services that enhance navigation, logistics, emergency response, and personalized experiences for users.
Example: Location is a crucial element or component of information in various applications within the European IT context. Here are a few examples:
1. Navigation and Mapping Services: Location plays a fundamental role in navigation and mapping applications. Services like GPS navigation systems, online maps, and mobile applications utilize location information to provide accurate directions, real-time traffic updates, and location-based services such as nearby points of interest, restaurants, or gas stations.
2. Geographical Information Systems (GIS): GIS applications are extensively used in Europe for spatial analysis, urban planning, environmental management, and disaster response. These systems rely on location data to visualize, analyze, and interpret geographic information. For instance, GIS can help city planners determine the best location for new infrastructure projects or assist emergency services in identifying the nearest hospitals during a crisis.
3. Location-Based Advertising: Many European businesses leverage location-based advertising to target customers effectively. By utilizing location data from mobile devices, advertisers can deliver personalized and contextually relevant advertisements to users in specific geographic areas. For example, a retail store can send promotional offers to potential customers nearby, increasing the chances of attracting foot traffic and boosting sales.
4. Internet of Things (IoT) Applications: IoT devices often rely on location information to provide valuable services. For instance, smart home systems can adjust heating or lighting based on the user's location within the house. In agriculture, IoT sensors can collect location-specific data about soil moisture, temperature, and nutrient levels, enabling farmers to optimize irrigation and fertilization practices.
5. Fleet Management and Logistics: Location tracking is essential for efficient fleet management and logistics operations. European companies utilize GPS tracking systems to monitor the real-time location of vehicles, optimize routes, and improve delivery efficiency. This helps reduce fuel consumption, enhance customer satisfaction, and streamline overall operations.
6. Social Media and Networking: Location-based features are prevalent in social media platforms and networking applications. Users can share their current location, check-in at specific places, or discover nearby events or friends. These features enable users to connect with others in their vicinity, explore local recommendations, and share experiences based on their location.
These examples illustrate how location serves as a vital component of information in various European IT applications, enhancing user experiences, enabling efficient resource management, and facilitating targeted services.
LOST view: OV-Functional Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/LocationBusinessObject
ABB name: egovera:LocationBusinessObject
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/egovera/LocationBusinessObject
Name: Location Information
Interoperability Layer: Organisational
Specialises: http://data.europa.eu/dr8/InformationBusinessObject
Definition: A qualification is somehting that could potentially be used to qualifiy a particular person or entity. Qualification information specify the ability, characteristic, or experience that makes an individual or entity suitable for a particular job or activity.
Source: Philip Barnhart
Source reference: https://books.google.it/books?id=3tY8Fck5UVkC&pg=PA2&redir_esc=y
Additional information: Qualification, within the realm of information technology (IT) in Europe, refers to the process of assessing and validating an individual's knowledge, skills, and competencies in a specific field or domain. It serves as a means to demonstrate one's expertise and proficiency to potential employers, clients, or educational institutions.
In the European IT context, qualifications are typically obtained through formal education, vocational training, or professional certifications. These qualifications play a crucial role in determining an individual's suitability for employment, career advancement, or further educational opportunities within the IT industry.
Formal education qualifications in IT often include degrees such as Bachelor's, Master's, or Doctorate programs in computer science, information systems, software engineering, or related fields. These qualifications are typically awarded by universities or higher education institutions and provide a comprehensive theoretical foundation along with practical skills necessary for various IT roles.
Vocational training qualifications are another significant aspect of the European IT context. These qualifications are typically obtained through specialized training programs, apprenticeships, or vocational schools. They focus on equipping individuals with specific technical skills and practical knowledge required for specific IT job roles, such as network administration, programming, cybersecurity, or database management.
Professional certifications also hold great value in the European IT context. These qualifications are awarded by industry-recognized organizations or vendors and validate an individual's expertise in specific technologies, methodologies, or frameworks. Examples of widely recognized IT certifications in Europe include Cisco Certified Network Associate (CCNA), Microsoft Certified Solutions Expert (MCSE), or Certified Information Systems Security Professional (CISSP).
Qualifications in the European IT context are often regulated and standardized to ensure consistency and comparability across different countries. For instance, the European Qualifications Framework (EQF) provides a common reference framework to understand and compare qualifications across European countries. It enables individuals, employers, and educational institutions to assess the level and complexity of qualifications, facilitating mobility and recognition of qualifications within Europe.
Overall, qualifications in the European IT context serve as a vital tool for individuals to showcase their knowledge and skills, enabling them to pursue rewarding careers, contribute to the IT industry, and meet the evolving demands of the digital era.
Example: Qualification, as an element or component of information, plays a crucial role in various aspects of the European IT context. Here are a few examples of its application:
1. Job Applications: In the European IT industry, qualifications are essential for job seekers to demonstrate their knowledge, skills, and expertise. Candidates typically include their educational qualifications, such as degrees, certifications, and diplomas, in their resumes or job applications. These qualifications provide employers with a clear understanding of the candidate's technical competencies and suitability for the role.
2. Vendor Certifications: Many IT professionals in Europe pursue vendor-specific certifications offered by renowned technology companies like Microsoft, Cisco, or Oracle. These certifications validate an individual's proficiency in using specific software, hardware, or platforms. For instance, a Microsoft Certified Solutions Expert (MCSE) qualification indicates expertise in Microsoft technologies, making it valuable for IT professionals working with Microsoft products in Europe.
3. Professional Associations: Europe has several professional IT associations that offer qualifications to their members. These qualifications often involve a combination of education, experience, and examinations. For example, the British Computer Society (BCS) offers various certifications, including Chartered IT Professional (CITP), which recognizes individuals who have demonstrated a high level of competence and professionalism in the IT field.
4. Academic Degrees: European universities and educational institutions offer a wide range of IT-related academic degrees, such as Bachelor's, Master's, and Ph.D. programs. These qualifications provide students with a comprehensive understanding of IT concepts, theories, and practical skills. Employers in the European IT industry often consider these degrees as a prerequisite for certain roles or as an indication of a candidate's commitment to continuous learning and development.
5. Project Bidding: In the European IT sector, companies often bid for projects or contracts. Qualifications play a significant role in the bidding process as they help potential clients assess the capabilities and expertise of the bidding companies. Qualifications such as ISO certifications, industry-specific accreditations, or previous successful project experiences can enhance a company's chances of winning a bid.
Overall, qualifications serve as a standardized measure of an individual's or organization's capabilities and expertise within the European IT context. They provide valuable information to employers, clients, and stakeholders, enabling them to make informed decisions and ensure the quality and competence of IT professionals and companies.
LOST view: OV-Functional Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/QualificationBusinessObject
ABB name: egovera:QualificationBusinessObject
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/egovera/QualificationBusinessObject
Name: Qualification Information
Interoperability Layer: Organisational
Specialises: http://data.europa.eu/dr8/InformationBusinessObject
Definition: An invoice is a commercial document issued by a seller to a buyer relating to a sale transaction and indicating the products, quantities, and agreed-upon prices for products or services the seller had provided the buyer.
Source: WikiPedia
Source reference: https://en.wikipedia.org/wiki/Invoice
Additional information: An invoice, within the European IT context, is a crucial document that serves as a formal request for payment from a seller to a buyer. It is a comprehensive record of a commercial transaction, providing detailed information about the goods or services provided, their quantities, prices, and any applicable taxes or discounts. The invoice acts as a legally binding agreement between the seller and the buyer, outlining the terms and conditions of the sale.
In the European IT context, an invoice typically includes specific information required by local regulations and tax laws. This information may vary across different European countries, but generally includes:
1. Invoice Number: A unique identifier assigned to each invoice, enabling easy tracking and reference.
2. Invoice Date: The date when the invoice is issued, indicating the start of the payment period.
3. Seller's Information: The name, address, and contact details of the seller, including their VAT (Value Added Tax) identification number.
4. Buyer's Information: The name, address, and contact details of the buyer, including their VAT identification number if applicable.
5. Description of Goods/Services: A detailed description of the goods or services provided, including quantities, unit prices, and any applicable discounts.
6. Total Amount: The total amount payable by the buyer, including any taxes, shipping costs, or additional charges.
7. Payment Terms: The agreed-upon terms for payment, such as the due date, accepted payment methods, and any penalties for late payment.
8. VAT Information: If applicable, the invoice should clearly state the VAT rate applied to the transaction and provide a breakdown of the taxable amount and the corresponding VAT amount.
9. Currency: The currency in which the payment should be made, especially relevant for cross-border transactions within the European Union.
10. Bank Details: The seller's bank account details, enabling the buyer to make the payment conveniently.
In addition to serving as a payment request, invoices also play a vital role in accounting and financial reporting. They provide evidence of revenue for the seller and serve as a basis for calculating taxes, tracking sales, and managing inventory. Furthermore, invoices facilitate the reconciliation of accounts between buyers and sellers, ensuring transparency and accuracy in financial transactions.
In the European IT context, electronic invoicing (e-invoicing) has gained significant popularity due to its efficiency and cost-effectiveness. E-invoices are digitally generated, transmitted, and stored, eliminating the need for paper-based invoices. They often adhere to specific standards, such as the European standard EN 16931, to ensure interoperability and seamless exchange of invoice data between different systems and organizations.
Overall, invoices are a fundamental component of information within the European IT context, enabling smooth and transparent financial transactions while complying with local regulations and tax requirements.
Example: The invoice is a crucial element or component of information in various applications within the European IT context. Here are a few examples:
1. Accounting Software: In accounting software applications, invoices are used to record and track financial transactions. They serve as a formal request for payment from a seller to a buyer, providing details such as the products or services provided, quantities, prices, and payment terms. Invoices generated by the software are essential for maintaining accurate financial records, calculating taxes, and generating financial reports.
2. E-commerce Platforms: In e-commerce platforms, invoices play a vital role in facilitating online transactions. When customers make purchases, invoices are automatically generated and sent to them as proof of purchase. These invoices contain information about the purchased items, prices, shipping details, and any applicable taxes. They help ensure transparency, enable returns or exchanges, and serve as a legal document for both the buyer and the seller.
3. Supply Chain Management Systems: In supply chain management systems, invoices are used to document the movement of goods and services between different entities within the supply chain. They provide information about the sender, receiver, quantity, description, and value of the goods or services exchanged. Invoices help track inventory, monitor payments, and streamline the overall supply chain process.
4. Enterprise Resource Planning (ERP) Systems: ERP systems integrate various business processes, including finance, sales, and procurement. Invoices are a critical component within ERP systems as they enable seamless communication and coordination between different departments. For example, when a sales order is fulfilled, an invoice is automatically generated, triggering the accounting department to record the transaction and update financial statements.
5. Tax Compliance: Invoices are essential for tax compliance purposes within the European IT context. They serve as evidence of taxable transactions and are required by tax authorities for auditing and verification. Invoices must adhere to specific legal requirements, such as including the seller's and buyer's tax identification numbers, VAT rates, and other relevant tax information. Compliance with invoicing regulations ensures accurate tax reporting and prevents potential penalties.
Overall, the application of invoices as an element or component of information is widespread in various European IT contexts, supporting financial management, e-commerce, supply chain operations, ERP systems, and tax compliance.
LOST view: OV-Functional Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/InvoiceBusinessObject
ABB name: egovera:InvoiceBusinessObject
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/egovera/InvoiceBusinessObject
Name: Invoice Information
Interoperability Layer: Organisational
Specialises: http://data.europa.eu/dr8/InformationBusinessObject
Definition: A digital asset is anything that exists only in digital form and comes with a distinct usage right
Source: WikiPedia
Source reference: https://en.wikipedia.org/wiki/Digital_asset
Additional information: A digital asset, within the context of information technology (IT) in Europe, refers to any form of digital content or data that holds value and can be owned, controlled, or exchanged. It encompasses a wide range of electronic files, including but not limited to documents, images, audio files, videos, software, databases, and other digital resources.
Digital assets are intangible and exist in a digital form, residing on various storage devices such as servers, computers, cloud platforms, or other electronic media. They are created, managed, and utilized by individuals, organizations, or entities for various purposes, including business operations, personal use, entertainment, education, research, and more.
These assets are characterized by their ability to be easily duplicated, shared, and distributed across networks, enabling seamless access and transfer. However, their value lies in the intellectual property, information, or functionality they possess, rather than the physical medium on which they are stored.
Digital assets often require specific software applications or platforms to be accessed, viewed, edited, or utilized effectively. For example, a document may require a word processing software, an image may require an image editing tool, or a video may require a media player. These software tools enable users to interact with and manipulate digital assets according to their needs.
In the European IT context, digital assets are subject to various legal frameworks and regulations, including copyright laws, data protection regulations (such as the General Data Protection Regulation or GDPR), and intellectual property rights. These regulations aim to protect the ownership, privacy, and security of digital assets, ensuring that individuals and organizations have control over their creation, distribution, and usage.
Furthermore, the European IT context emphasizes the importance of data privacy and security, particularly with the introduction of GDPR. This means that digital assets containing personal data must be handled and protected in compliance with the established regulations to safeguard individuals' privacy rights.
In summary, a digital asset in the European IT context refers to any intangible, digitally stored content or data that holds value and can be owned, controlled, or exchanged. These assets encompass a wide range of electronic files and require specific software tools for effective utilization. They are subject to legal frameworks and regulations, emphasizing data privacy and security within the European Union.
Example: Digital assets, as elements or components of information, have various applications within the European IT context. Here are a few examples:
1. Intellectual Property Protection: Digital assets, such as copyrighted content, trademarks, and patents, are crucial for protecting intellectual property rights. In the European IT context, digital assets play a significant role in safeguarding innovations, software codes, and creative works from unauthorized use or infringement.
2. Data Management and Storage: Digital assets encompass a wide range of data, including documents, images, videos, and audio files. In the European IT context, organizations utilize digital asset management systems to efficiently organize, store, and retrieve these assets. These systems ensure secure and compliant storage, enabling businesses to effectively manage their data and streamline workflows.
3. E-commerce and Digital Marketing: Digital assets are integral to e-commerce and digital marketing strategies. In the European IT context, businesses leverage digital assets like product images, descriptions, and videos to enhance online shopping experiences. Additionally, digital marketing campaigns rely on assets such as banners, social media graphics, and interactive content to engage customers and drive conversions.
4. Blockchain Technology: Digital assets can be represented and managed using blockchain technology. In the European IT context, blockchain-based digital assets enable secure and transparent transactions, particularly in areas like cryptocurrency, supply chain management, and digital identity verification. Blockchain ensures data integrity, immutability, and decentralized control over digital assets, enhancing trust and efficiency in various industries.
5. Open Data Initiatives: Digital assets play a crucial role in open data initiatives, which aim to make public sector information more accessible and usable. In the European IT context, governments and organizations release digital assets, such as datasets, reports, and APIs, to foster innovation, research, and development. These assets can be utilized by businesses, researchers, and citizens to create new applications, services, and insights.
Overall, digital assets are fundamental components of information in the European IT context, finding applications in intellectual property protection, data management, e-commerce, blockchain technology, and open data initiatives.
LOST view: OV-Functional Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/DigitalAssetBusinessObject
ABB name: egovera:DigitalAssetBusinessObject
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/egovera/DigitalAssetBusinessObject
Name: Digital Asset Information
Interoperability Layer: Organisational
Specialises: http://data.europa.eu/dr8/InformationBusinessObject
Definition: Availability the use of a predefined object or space and of the future demand.
Source: Cambridge Dictionary
Source reference: https://dictionary.cambridge.org/dictionary/english/availability
Additional information: Availability, as an element or component of information, refers to the characteristic of being accessible and usable when needed by authorized individuals or systems. It is a fundamental aspect of information security and plays a crucial role in ensuring the continuous and uninterrupted availability of information resources within the European IT context.
In the European IT context, availability encompasses the ability of information systems, networks, applications, and data to remain operational and accessible to authorized users. It involves ensuring that the necessary infrastructure, hardware, software, and resources are in place to support the timely and reliable delivery of information services.
The availability of information is essential for organizations operating within the European IT landscape as it directly impacts their ability to conduct business, deliver services, and maintain customer satisfaction. It encompasses both planned and unplanned downtime, as well as the ability to recover quickly from any disruptions or incidents that may occur.
To achieve and maintain availability, organizations employ various measures and strategies, including redundancy, fault tolerance, disaster recovery planning, backup systems, and robust network infrastructure. These measures aim to minimize the risk of service interruptions, mitigate the impact of potential threats, and ensure the timely restoration of services in the event of a disruption.
In the European IT context, availability is closely related to other elements of information security, such as confidentiality and integrity. While confidentiality focuses on protecting information from unauthorized access, and integrity ensures the accuracy and consistency of data, availability ensures that information is accessible and usable by authorized individuals or systems when needed.
Organizations within the European IT context must consider various factors that can affect availability, including hardware and software failures, power outages, natural disasters, cyber-attacks, and human errors. They must implement appropriate controls, such as robust backup and recovery mechanisms, redundant systems, and effective incident response procedures, to mitigate these risks and maintain high levels of availability.
Furthermore, compliance with relevant regulations and standards, such as the General Data Protection Regulation (GDPR) in Europe, is crucial to ensure the availability of information. Organizations must adhere to specific requirements and guidelines to protect personal data and prevent any unauthorized access or loss of availability.
In summary, availability, as an element or component of information within the European IT context, refers to the ability of information systems, networks, applications, and data to remain accessible and usable by authorized individuals or systems. It is a critical aspect of information security, requiring organizations to implement appropriate measures and strategies to ensure continuous and uninterrupted access to information resources.
Example: Availability, as an element or component of information, refers to the accessibility and usability of information or resources when needed. In the European IT context, there are several examples of how availability is applied to ensure the smooth functioning of information systems and services. These examples include:
1. Redundancy and fault tolerance: European IT systems often employ redundant hardware, software, and network components to ensure high availability. For instance, data centers may have multiple servers running in parallel, so if one fails, the others can take over seamlessly, minimizing downtime and ensuring continuous availability of services.
2. Load balancing: To distribute the workload evenly across multiple servers or resources, load balancing techniques are employed. This ensures that no single resource is overwhelmed, preventing service degradation or unavailability. Load balancing algorithms dynamically allocate incoming requests to available resources, optimizing performance and availability.
3. Disaster recovery planning: European IT organizations prioritize disaster recovery planning to ensure availability in the face of unforeseen events such as natural disasters, cyber-attacks, or system failures. This involves creating backup systems, off-site data storage, and implementing recovery procedures to minimize downtime and quickly restore services.
4. Service Level Agreements (SLAs): SLAs are contractual agreements between service providers and customers that define the expected level of availability and performance. In the European IT context, SLAs often include specific availability targets, such as a certain percentage of uptime, to ensure that services meet the required availability standards.
5. Monitoring and proactive maintenance: European IT systems employ monitoring tools and techniques to continuously track the performance and availability of resources. This allows IT teams to identify potential issues or bottlenecks in real-time and take proactive measures to prevent service disruptions. Regular maintenance activities, such as patching, updating, and system checks, are also performed to ensure optimal availability.
6. Scalability and elasticity: European IT systems are designed to scale and adapt to changing demands. By employing scalable architectures and cloud computing technologies, organizations can dynamically allocate resources based on demand, ensuring availability even during peak usage periods.
Overall, availability is a critical aspect of information systems in the European IT context. By implementing redundancy, load balancing, disaster recovery planning, SLAs, monitoring, and scalability, organizations can ensure that information and services are readily accessible and usable, meeting the needs of users and stakeholders.
LOST view: OV-Functional Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/AvailabilityBusinessObject
ABB name: egovera:AvailabilityBusinessObject
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/egovera/AvailabilityBusinessObject
Name: Availability Information
Interoperability Layer: Organisational
Specialises: http://data.europa.eu/dr8/InformationBusinessObject
Definition: Contracting authority is an organization that has been granted the power to enter into contracts with other parties.
Source: Oboloo
Source reference: https://oboloo.com/blog/what-are-contracting-authorities-definition/
Additional information: The Contracting Authority, within the European IT context, refers to the entity responsible for initiating and overseeing the procurement process for IT goods, services, or works. It is a crucial element in public procurement procedures, ensuring transparency, fairness, and efficiency in the acquisition of IT solutions by public sector organizations.
The Contracting Authority can be any public sector body, such as government departments, local authorities, public agencies, or other public entities, that require IT products or services to fulfill their operational needs. These entities may have diverse objectives, ranging from delivering public services to implementing specific projects or programs.
The role of the Contracting Authority begins with identifying the IT requirements and defining the scope of the procurement. This involves conducting a thorough analysis of the organization's needs, considering factors such as technical specifications, functional requirements, budgetary constraints, and legal obligations. The Contracting Authority must ensure that the procurement process aligns with the organization's strategic objectives and complies with relevant regulations and guidelines.
Once the requirements are established, the Contracting Authority is responsible for initiating the procurement procedure. This typically involves preparing and publishing a procurement notice or tender documentation, which outlines the IT requirements, evaluation criteria, contract terms, and conditions. The Contracting Authority must ensure that the procurement process is open, transparent, and non-discriminatory, allowing all potential suppliers to compete on an equal footing.
During the procurement process, the Contracting Authority evaluates the received bids or proposals from IT suppliers. This evaluation is based on the predefined criteria, which may include technical capabilities, financial stability, past performance, and compliance with legal and technical standards. The Contracting Authority must ensure a fair and objective evaluation process, adhering to the principles of equal treatment, non-discrimination, and transparency.
Once the evaluation is completed, the Contracting Authority selects the most suitable IT supplier(s) and enters into a contract or framework agreement. The Contracting Authority negotiates the terms and conditions of the contract, including pricing, delivery schedules, service levels, and intellectual property rights. Throughout the contract duration, the Contracting Authority monitors the supplier's performance, ensuring compliance with contractual obligations and addressing any issues or disputes that may arise.
The Contracting Authority plays a vital role in the successful implementation of IT projects within the European IT context. By effectively managing the procurement process, the Contracting Authority aims to achieve value for money, promote competition, and ensure the delivery of high-quality IT solutions that meet the organization's needs. Additionally, the Contracting Authority contributes to the overall development and growth of the European IT sector by providing opportunities for IT suppliers to compete and innovate in the market.
Example: The Contracting Authority, in the European IT context, refers to the entity responsible for initiating and managing procurement processes for IT projects within the European Union. It plays a crucial role in ensuring fair competition, transparency, and compliance with regulations in the procurement of IT goods, services, and works. Here are a few examples of how the Contracting Authority is applied in the European IT context:
1. Tendering Process: The Contracting Authority is responsible for issuing tender documents, defining the requirements, and setting evaluation criteria for IT projects. It ensures that all potential suppliers have equal access to information and opportunities to compete for the contract.
2. Contract Management: Once a supplier is selected, the Contracting Authority oversees the contract's execution, ensuring compliance with the agreed terms and conditions. It monitors the project's progress, manages any changes or disputes, and ensures that the supplier delivers the IT solution as per the contract requirements.
3. Compliance and Regulation: The Contracting Authority ensures that all procurement processes adhere to relevant European Union directives and regulations, such as the Public Procurement Directive. It ensures fair competition, prevents corruption, and promotes transparency in the IT procurement process.
4. Risk Management: The Contracting Authority assesses and manages risks associated with IT projects. It identifies potential risks, such as project delays, budget overruns, or data security breaches, and implements appropriate measures to mitigate these risks. This includes defining contractual obligations related to risk management and monitoring the supplier's compliance.
5. Stakeholder Engagement: The Contracting Authority engages with various stakeholders involved in IT projects, including end-users, technical experts, and legal advisors. It gathers their input, requirements, and feedback to ensure that the procurement process and resulting IT solution meet the needs of the European Union and its citizens.
Overall, the Contracting Authority acts as a central entity responsible for managing the procurement of IT projects within the European IT context. It ensures transparency, fairness, and compliance with regulations, ultimately contributing to the successful implementation of IT solutions that benefit the European Union and its citizens.
LOST view: OV-Functional Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/ContractingAuthorityBusinessObject
ABB name: egovera:ContractingAuthorityBusinessObject
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/egovera/ContractingAuthorityBusinessObject
Name: Contracting authority Information
Interoperability Layer: Organisational
Specialises: http://data.europa.eu/dr8/InformationBusinessObject
Definition: Analytics Infrastructure Enablers ABB is a Grouping that refers to the set of components and services that support the development and deployment of data analytics solutions
Source: WikPedia
Source reference: https://en.wikipedia.org/wiki/Audit_trail
Additional information: An audit trail, within the European IT context, refers to a systematic and chronological record of events or activities that occur within an information system. It is a crucial component of information management and security, aiming to ensure accountability, transparency, and integrity of data and processes.
The audit trail captures and documents various actions, such as user activities, system events, and data modifications, providing a detailed history of who accessed, modified, or deleted specific information, and when these actions took place. It serves as a reliable source of evidence for investigating and reconstructing events, detecting unauthorized activities, and facilitating compliance with legal, regulatory, and organizational requirements.
In the European IT context, the audit trail plays a significant role in ensuring data protection and privacy in accordance with the General Data Protection Regulation (GDPR). It helps organizations demonstrate compliance with GDPR principles, such as data minimization, purpose limitation, and accountability.
The audit trail typically includes information such as user identities, timestamps, IP addresses, system logs, and details of the actions performed. It may also record the context and outcome of each action, providing a comprehensive overview of the entire lifecycle of data and system operations.
Furthermore, the audit trail should be tamper-proof and securely stored to prevent unauthorized modifications or deletions. It is essential to implement appropriate technical and organizational measures to protect the integrity and confidentiality of the audit trail itself, ensuring that it remains a reliable source of evidence.
The audit trail serves multiple purposes within the European IT context. Firstly, it enables organizations to detect and investigate security incidents, unauthorized access attempts, or data breaches. By analyzing the audit trail, security teams can identify patterns, anomalies, or suspicious activities, allowing them to respond promptly and mitigate potential risks.
Secondly, the audit trail supports compliance and regulatory requirements. Organizations must maintain accurate and complete audit trails to demonstrate compliance with various regulations, such as GDPR, financial regulations, or industry-specific standards. It helps auditors and regulatory bodies assess the effectiveness of controls, identify potential non-compliance, and enforce penalties or corrective actions if necessary.
Moreover, the audit trail facilitates forensic analysis and incident response. In the event of a security incident or data breach, the audit trail provides valuable information for forensic investigators to reconstruct the sequence of events, identify the root cause, and determine the extent of the impact. It aids in the attribution of responsibility and supports legal proceedings if required.
In summary, the audit trail is a fundamental element of information management and security within the European IT context. It ensures accountability, transparency, and integrity of data and processes, helping organizations comply with regulations, detect security incidents, and facilitate forensic analysis. By maintaining a comprehensive and tamper-proof audit trail, organizations can enhance their data protection practices and build trust with stakeholders.
Example: The audit trail is a crucial element or component of information systems that helps in tracking and documenting activities and changes made within a system. It provides a chronological record of events, actions, and transactions, allowing for accountability, transparency, and the ability to investigate any potential issues or discrepancies. In the European IT context, the application of audit trails is seen in various areas, including:
1. Data Protection and Privacy: The General Data Protection Regulation (GDPR) in Europe emphasizes the need for organizations to implement appropriate technical and organizational measures to ensure the security of personal data. Audit trails play a vital role in demonstrating compliance with GDPR requirements by recording and monitoring access to personal data, changes made to data, and any unauthorized attempts or breaches.
2. Financial Systems: Audit trails are extensively used in financial systems to ensure the integrity and accuracy of financial transactions. They help in tracking changes made to financial records, identifying potential fraud or errors, and providing evidence for financial audits and regulatory compliance.
3. Healthcare Systems: In the healthcare sector, audit trails are essential for maintaining the security and privacy of patient information. They track access to electronic health records, changes made to medical records, and any unauthorized attempts to access sensitive patient data. Audit trails assist in complying with regulations such as the EU's General Data Protection Regulation (GDPR) and the Health Insurance Portability and Accountability Act (HIPAA) in the United States.
4. System Monitoring and Security: Audit trails are an integral part of monitoring and securing IT systems. They record system events, user activities, and network traffic, enabling the detection of security breaches, unauthorized access attempts, or suspicious activities. Audit trails facilitate incident response, forensic investigations, and compliance with security standards such as ISO 27001.
5. Software Development: Audit trails are valuable during the software development lifecycle. They help in tracking changes made to source code, configuration files, and system settings. This ensures traceability, facilitates debugging, and assists in identifying the root cause of issues or errors in software applications.
Overall, the application of audit trails in the European IT context is diverse and spans across various industries and sectors. It serves as a critical component for ensuring data protection, regulatory compliance, system security, and accountability.
LOST view: OV-Functional Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/AuditTrailBusinessObject
ABB name: egovera:AuditTrailBusinessObject
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/egovera/AuditTrailBusinessObject
Name: Audit trail Information
Interoperability Layer: Organisational
Specialises: http://data.europa.eu/dr8/InformationBusinessObject
Definition: A credential is a piece of any document that details a qualification, competence, or authority issued to an individual by a third party with a relevant or de facto authority or assumed competence to do so.
Source: WikiPedia
Source reference: https://en.wikipedia.org/wiki/Credential
Additional information: A credential, in the context of information technology (IT), refers to a piece of information or a set of data that is used to authenticate and verify the identity of an individual or entity in order to grant them access to certain resources, systems, or services. It is a crucial component of the authentication process and plays a vital role in ensuring the security and integrity of digital systems.
Credentials are typically associated with user accounts and are used to establish trust and authorization within a system. They can take various forms, including usernames, passwords, personal identification numbers (PINs), security tokens, digital certificates, biometric data, or any combination of these factors. The specific type of credential used depends on the level of security required and the nature of the system or service being accessed.
In the European IT context, credentials are governed by various regulations and standards aimed at protecting personal data and ensuring privacy. For instance, the General Data Protection Regulation (GDPR) sets guidelines for the collection, storage, and processing of personal information, including credentials. Organizations operating within the European Union (EU) are required to adhere to these regulations to safeguard user data and prevent unauthorized access.
The management and storage of credentials are of utmost importance in the European IT context. Organizations must implement robust security measures to protect credentials from unauthorized access, theft, or misuse. This includes employing encryption techniques, secure storage mechanisms, and strong access controls. Additionally, regular audits and vulnerability assessments are conducted to identify and mitigate any potential risks or vulnerabilities in the credential management system.
Furthermore, the European IT context emphasizes the principle of data minimization, which means that organizations should only collect and store the minimum amount of personal data necessary for the intended purpose. This principle applies to credentials as well, where organizations should only request and retain the essential information required for authentication and authorization, while ensuring that the data is adequately protected.
In summary, within the European IT context, a credential is an element or component of information used to authenticate and verify the identity of individuals or entities. It is governed by regulations and standards aimed at protecting personal data and ensuring privacy. Robust security measures and data minimization principles are essential to safeguard credentials and maintain the integrity of digital systems.
Example: Credentials are an essential element or component of information in various applications within the European IT context. They serve as proof of identity, qualifications, and permissions, enabling individuals to access systems, resources, and services. Here are a few examples of how credentials are applied:
1. User Authentication: In the European IT context, credentials are widely used for user authentication. When individuals log in to online platforms, websites, or applications, they are typically required to provide their credentials, such as a username and password. These credentials verify their identity and grant them access to the desired resources or functionalities.
2. Digital Certificates: Digital certificates are a form of credentials used to establish trust and secure communication over networks. Within the European IT context, digital certificates are commonly employed for secure email communication, website authentication (HTTPS), and electronic signatures. These credentials are issued by trusted certification authorities and contain information about the certificate holder, ensuring the authenticity and integrity of digital transactions.
3. Professional Certifications: Credentials play a crucial role in the European IT industry for validating an individual's professional qualifications and expertise. Various organizations and institutions offer certifications in specific IT domains, such as programming languages, network administration, cybersecurity, and project management. These credentials serve as tangible evidence of an individual's skills and knowledge, enhancing their employability and professional growth.
4. Access Control Systems: Credentials are extensively used in access control systems to regulate physical and logical access to buildings, data centers, networks, and sensitive information. Within the European IT context, organizations employ credentials such as smart cards, RFID tags, or biometric data (fingerprint, iris scan) to grant authorized personnel access to restricted areas or confidential data. These credentials ensure that only authorized individuals can enter or access specific resources, enhancing security and privacy.
5. API Authentication: In the European IT context, credentials are also utilized for authenticating and authorizing access to Application Programming Interfaces (APIs). APIs enable different software systems to interact and exchange data. To ensure secure and controlled access, developers often need to obtain credentials, such as API keys or tokens, which authenticate their applications and grant them specific permissions to access and utilize the API's functionalities.
These examples illustrate how credentials serve as vital components of information within the European IT context, enabling secure access, validating qualifications, establishing trust, and enhancing overall information security.
LOST view: OV-Functional Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/CredentialBusinessObject
ABB name: egovera:CredentialBusinessObject
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/egovera/CredentialBusinessObject
Name: Credential Information
Interoperability Layer: Organisational
Specialises: http://data.europa.eu/dr8/InformationBusinessObject
Definition: A transaction is an interaction of individuals/entities with outside entities, such as businesses (e.g., travel and sales records), public facilities and organizations (e.g., library loans), and Web sites (e.g., Internet usage).
Source: OECD
Source reference: https://www.oecd.org/ctp/administration/31663095.pdf
Additional information: A transaction, in the context of information technology (IT), refers to a discrete unit of work or activity that occurs within a computer system or network. It involves the exchange, processing, or manipulation of data or resources between two or more entities, such as users, applications, or systems. Transactions play a crucial role in various aspects of IT, including databases, e-commerce, financial systems, and other business processes.
At its core, a transaction represents a logical unit of work that must be executed atomically, meaning it should either be completed in its entirety or not at all. This ensures data integrity and consistency within the system. Transactions are typically initiated by a user or an application and involve a series of operations or steps that need to be executed in a specific order.
In the European IT context, transactions are governed by various regulations and standards to ensure security, privacy, and compliance with legal requirements. For example, the General Data Protection Regulation (GDPR) sets guidelines for the processing and protection of personal data within transactions. Additionally, the Payment Services Directive 2 (PSD2) regulates electronic payment transactions within the European Union, promoting secure and efficient payment services.
Transactions can take different forms depending on the nature of the activity. Some common types of transactions include:
1. Financial Transactions: These involve the exchange of money or financial assets between parties. Examples include online purchases, banking transactions, stock trading, and electronic fund transfers. In the European IT context, financial transactions are subject to strict regulations to prevent fraud, money laundering, and ensure consumer protection.
2. Database Transactions: In database systems, transactions are used to ensure the consistency and reliability of data. A database transaction typically consists of multiple database operations, such as inserting, updating, or deleting records. These operations are grouped together and executed as a single unit, ensuring that the database remains in a consistent state even in the event of failures or concurrent access by multiple users.
3. Business Transactions: These transactions involve the exchange of information or resources between different business entities or systems. They can include processes such as order processing, inventory management, supply chain management, and customer relationship management. Business transactions are essential for efficient and streamlined operations within organizations.
4. Communication Transactions: In the context of networking and communication protocols, transactions refer to the exchange of messages or data between networked devices. These transactions ensure reliable and orderly communication, often involving protocols such as TCP/IP, HTTP, or SMTP. They enable the transfer of information across networks, such as sending emails, browsing websites, or downloading files.
Overall, transactions are a fundamental concept in the European IT context, ensuring the secure and reliable exchange of information, resources, and services. They are governed by regulations and standards to protect user privacy, ensure data integrity, and promote efficient and trustworthy digital interactions.
Example: The application of transactions as an element or component of information is widely used in various industries within the European IT context. Here are a few examples:
1. E-commerce: In online shopping platforms, transactions play a crucial role in facilitating secure and efficient payment processes. When a customer makes a purchase, a transaction is initiated to transfer the payment information securely from the customer to the merchant. This ensures that the transaction is completed accurately, and the customer receives the purchased goods or services.
2. Banking and Finance: Transactions are fundamental in the banking and finance sector, where they are used to record and process various financial activities. For instance, when a customer transfers funds from one account to another, a transaction is created to capture the details of the transfer, including the amount, sender, and recipient. This information is then used to update the account balances and generate accurate financial statements.
3. Supply Chain Management: Transactions are essential in managing the flow of goods and services within the supply chain. For example, when a company purchases raw materials from a supplier, a transaction is created to document the details of the purchase, such as the quantity, price, and delivery date. This information helps track inventory levels, manage supplier relationships, and ensure timely delivery of goods.
4. Healthcare: In the healthcare industry, transactions are used to record patient information, medical procedures, and billing details. When a patient visits a healthcare provider, a transaction is generated to capture the diagnosis, treatment, and associated costs. This information is crucial for accurate medical record-keeping, insurance claims, and financial management within healthcare organizations.
5. Travel and Hospitality: Transactions are extensively used in the travel and hospitality sector to manage reservations, bookings, and payments. When a customer makes a hotel reservation or books a flight, a transaction is created to record the details of the booking, including the dates, room type, or flight itinerary. This information is then used to allocate resources, manage availability, and process payments.
In summary, transactions serve as a vital component of information in various domains within the European IT context, including e-commerce, banking, supply chain management, healthcare, and travel. They enable accurate recording, processing, and management of essential data, ensuring smooth operations and efficient decision-making.
LOST view: OV-Functional Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/TransactionBusinessObject
ABB name: egovera:TransactionBusinessObject
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/egovera/TransactionBusinessObject
Name: Transaction Information
Interoperability Layer: Organisational
Specialises: http://data.europa.eu/dr8/InformationBusinessObject
Definition: The Economic Operators Registration and Identification number (EORI) is a unique identifier assigned by customs authorities to businesses and individuals involved in importing or exporting goods within the European Union. This system was established to improve the security of international trade, streamline customs procedures, and facilitate data exchange between operators and customs. The EORI number is used in all communications with any EU customs authorities, for customs declarations and customs clearance for both import and export shipments.
Source: EIRA team
Additional information: The Economic Operators Registration and Identification number (EORI) is a unique identification number that businesses and individuals involved in importing or exporting goods within the European Union are required to use in their communications with customs authorities. It is a critical component of the EU's system for tracking and managing trade within its borders.
The EORI number is assigned by the customs authority of the country where the economic operator is established, and it is valid throughout the European Union. It is used in all communications with customs authorities, regardless of the country within the EU where the goods are being imported or exported.
The EORI number is designed to facilitate efficient and secure data exchange between operators and customs, thus ensuring transparency and traceability of customs procedures. It is used in various customs procedures and processes, such as customs declarations, customs decisions, and customs simplifications.
The EORI system is part of the EU's broader strategy to modernize customs procedures, improve security, and facilitate trade. It is a key element of the EU's electronic customs initiative, which aims to streamline and digitize customs procedures across the EU.
The EORI number is composed of a country code (representing the country that issued the EORI number), followed by a code or number that is unique within the country. The structure and length of the unique code or number can vary from one country to another.
In summary, the EORI number is a crucial identifier used in the EU's customs procedures, facilitating the efficient and secure exchange of data between economic operators and customs authorities.
Example: 1. Import-Export Businesses: Businesses involved in the import and export of goods within the European Union need to use the EORI number. This number is used in all communications with customs authorities, ensuring a smooth and efficient customs process. It helps in tracking and recording the movement of goods, making the process transparent and accountable.
2. E-commerce Companies: E-commerce companies that ship products across borders within the European Union also use the EORI number. It helps in the identification of the traders and simplifies the customs process. It is also used in the declaration of goods, ensuring compliance with customs regulations.
3. Freight Forwarders: Freight forwarders and logistics companies use the EORI number to clear goods through customs on behalf of their clients. It helps in the identification of the operator and expedites the customs clearance process.
4. Manufacturing Companies: Manufacturing companies that import raw materials or export finished goods within the European Union use the EORI number. It helps in the tracking of goods and ensures a smooth customs process.
5. Tax Authorities: Tax authorities use the EORI number to identify traders and track the movement of goods. It helps in the enforcement of tax laws and ensures compliance with customs regulations.
6. Supply Chain Management: In supply chain management, the EORI number is used to track the movement of goods across borders. It helps in the efficient management of the supply chain and ensures the timely delivery of goods.
7. Customs Brokers: Customs brokers use the EORI number to clear goods through customs on behalf of their clients. It helps in the identification of the operator and expedites the customs clearance process.
8. Government Agencies: Government agencies involved in trade and commerce use the EORI number to monitor and regulate the movement of goods across borders. It helps in the enforcement of trade laws and ensures compliance with customs regulations.
LOST view: OV-Customs Functional Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/EconomicOperatorsRegistrationAndIdentificationNumberEORIBusinessObject
EIRA traceability: eira:InformationBusinessObject
ABB name: egovera:EconomicOperatorsRegistrationAndIdentificationNumberEORIBusinessObject
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-08
dct:identifier: http://data.europa.eu/dr8/egovera/EconomicOperatorsRegistrationAndIdentificationNumberEORIBusinessObject
dct:title: Economic Operators Registration and Identification number (EORI) Information
Definition: The Free Circulation Requirement Information refers to the stipulation that data and information should be allowed to move freely within a network or system without any restrictions or barriers. This concept is crucial in the IT sector as it ensures seamless data flow, promotes interoperability, and facilitates efficient communication and collaboration. It implies that information, once entered into a system, becomes accessible and usable across all linked systems, thereby enhancing the overall efficiency and productivity. This requirement is also critical in ensuring transparency, promoting innovation, and fostering a competitive market environment.
Source: EIRA team
Additional information: Free circulation requirement information refers to the set of rules, regulations, and standards that govern the unrestricted movement and exchange of data, information, and digital resources within a specific system or network. This concept is particularly relevant in the context of information technology (IT), where it plays a crucial role in facilitating seamless communication, collaboration, and interoperability among different IT systems, platforms, and users.
In essence, the free circulation requirement information is designed to ensure that all relevant data, information, and digital resources can be freely accessed, used, shared, and transferred by all authorized users, systems, or entities within the network or system, without any undue restrictions, limitations, or barriers. This includes not only the technical aspects of data and information circulation, such as data formats, protocols, and interfaces, but also the legal, regulatory, and policy aspects, such as data protection, privacy, intellectual property, and compliance requirements.
The free circulation requirement information is typically defined and enforced by the system or network administrators, in accordance with the relevant IT standards, best practices, and legal and regulatory requirements. It is also typically documented in the system or network's policies, procedures, and guidelines, and communicated to all users and stakeholders.
The free circulation requirement information is crucial for ensuring the efficiency, effectiveness, and integrity of the IT system or network. It enables the smooth and uninterrupted flow of data and information, which is essential for the system or network's operations, functions, and services. It also helps to prevent and mitigate various risks and issues, such as data loss, data breaches, system failures, and legal and regulatory violations.
Moreover, the free circulation requirement information contributes to the system or network's flexibility, scalability, and adaptability. It allows the system or network to accommodate different types of data, information, and digital resources, as well as different users, systems, and entities. It also allows the system or network to adapt to changes and developments in the IT environment, such as new technologies, standards, and regulations.
Example: 1. E-commerce Platforms: The free circulation requirement of information is crucial in the operation of e-commerce platforms. For instance, when a customer in France purchases a product from a German seller, the information about the product, its price, and the customer's shipping details must freely circulate between the two countries. This ensures smooth transactions and fosters a single digital market.
2. Online Streaming Services: Streaming platforms like Netflix and Spotify also rely on the free circulation of information. A user in Spain can access and stream content from the UK or any other EU country. This is possible because of the free flow of data across borders, allowing users to enjoy a diverse range of content.
3. Cloud Services: Cloud service providers store and manage data from various EU countries. The free circulation requirement ensures that these companies can operate across borders, providing seamless services to their customers. For example, a business in Italy can use a cloud service based in Ireland to store and manage its data.
4. Telecommunications: Telecommunication companies also benefit from the free circulation of information. For example, a mobile network operator in Belgium can provide roaming services to its customers traveling in Greece. This is possible because customer data and billing information can freely circulate between the two countries.
5. Online Education Platforms: Online education platforms often have students and educators from different EU countries. The free circulation of information allows these platforms to operate efficiently. For instance, a student in Portugal can enroll in a course offered by a university in Sweden and access all the necessary educational materials.
6. Health Information Systems: In the healthcare sector, the free circulation of information can facilitate better patient care. For example, a patient from the Netherlands visiting France can have their medical records accessed by French doctors, ensuring they receive appropriate treatment.
7. Research and Development: In the field of research and development, scientists and researchers across the EU can collaborate effectively due to the free circulation of information. They can share their findings and data with each other, fostering innovation and scientific progress.
LOST view: OV-Customs Functional Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/FreeCirculationRequirementInformationBusinessObject
EIRA traceability: eira:InformationBusinessObject
ABB name: egovera:FreeCirculationRequirementInformationBusinessObject
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-08
dct:identifier: http://data.europa.eu/dr8/egovera/FreeCirculationRequirementInformationBusinessObject
dct:title: Free circulation requirement information Information
Definition: Data Policy ABB is a Business Object aiming to form the guiding framework in which data management can operate.
Source: OECD
Source reference: https://stats.oecd.org/glossary/detail.asp?ID=4454
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): EU SCIENCE HUB - The European Commission's science and knowledge service - JRC's Data policy: The JRC's data policy is driven by transparency with the aim of contributing to innovation. It is a pillar of the development and implementation of scientific knowledge management at the JRC. It follows the commitments and regulatory basis of the Commission Decision on the reuse of Commission documents (2011/833/EU). The objectives for adopting and implementing the JRC data policy include: • Share and use data on the basis of the JRC Open Data principles: fully, freely, openly and timely; • To be transparent on the reasons for restricted access to certain data; • Provide a coordinated approach to the acquisition of data by the JRC; • Facilitate management, broaden access and use of JRC data; • Reinforce goals of Horizon 2020; • Support EU implementation of the G8 Open Data Charter; • Continuously support evidence-based decision making and research; • Ensure that JRC data is made available through the EU Open Data Portal. For a successful implementation process, the JRC's data policy lays down implementation principles with respect to responsible entities, overall implementation guidelines, and their individual elements like data management plans, as well as the monitoring of its implementation. https://ec.europa.eu/jrc/en/about/jrc-in-brief/data-policy
IoP Dimension: Governance IoP
LOST view: Semantic view
Interoperability saliency: The Data Policy ABB is salient for semantic interoperability because it provides a guiding framework to manage data and information according to interoperability principles as stated in the EIF recommendation n° 30: "Perceive data and information as a public asset that should be appropriately generated, collected, managed, shared, protected and preserved."
Identifier: http://data.europa.eu/dr8/DataPolicyBusinessObject
eira:ID: ABB30
ABB name: eira:DataPolicyBusinessObject
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-16-01
eira:policy_type: [ Information security policy | Privacy policy | Licensing and charging policy | Data quality policy | Metadata management policy ]*
Definition: Exports information refers to the data related to the goods and services that are produced within a country and sold to other countries. This information includes the type of goods or services exported, the value of these exports, the countries to which they are exported, and the changes in these exports over time. It is a crucial component of a country's economic data, influencing policy decisions, trade agreements, and economic strategies. In the context of IT, exports information can also refer to the data, software, or technology-based services that are developed within a country and provided to users or businesses in foreign countries.
Source: EIRA team
Additional information: Exports information refers to the comprehensive data and details about goods, services, and intellectual property sent out of a country to foreign nations as part of international trade. This information is crucial for various reasons, including economic analysis, policy-making, and business strategy development.
In the context of information systems and technology, exports information could also refer to the process of transferring data from one database, application, or system to another. This could be for purposes such as data backup, migration, synchronization, or integration. The exported data can be in various formats such as CSV, XML, or JSON, depending on the requirements of the receiving system.
The information included in exports data typically includes the description of the goods or services, their classification codes (based on international standards like the Harmonized System), their value, the country of destination, and the mode of transport. It may also include details about the exporter and the importer.
In terms of data protection and privacy, the export of personal data outside the country is subject to strict regulations to ensure the safety and privacy of individuals' information. This is particularly relevant in the context of the General Data Protection Regulation (GDPR) in the European Union, which sets stringent rules for the export of personal data outside the EU.
In summary, exports information is a critical component of both international trade and information management, with significant implications for economic performance, business strategy, and data privacy.
Example: 1. International Trade: Export information is crucial in the field of international trade. For instance, a company based in Germany might need to know the export regulations, tariffs, and trade agreements of the countries they are exporting their products to. This information helps them to strategize their export operations, comply with international laws, and avoid unnecessary penalties.
2. Supply Chain Management: In supply chain management, export information is used to plan and manage the movement of goods from the point of origin to the point of consumption. For example, a French automobile manufacturer would need to know the export procedures, documentation requirements, and transportation costs to export their cars to other countries.
3. Market Research: Companies use export information for market research. For instance, a Spanish olive oil producer might use export data to identify the countries that import the most olive oil. This information can help them to identify potential new markets for their products.
4. Economic Analysis: Economists and policy makers use export information to analyze the economic health of a country. For example, if Italy's exports of luxury goods are increasing, it might indicate that the global economy is doing well and people are willing to spend on luxury items.
5. Risk Management: Export information is used in risk management. For example, a Dutch flower exporter might need to know the political stability, currency exchange rates, and economic conditions of the countries they are exporting to. This information can help them to assess the risks associated with exporting to these countries and take necessary precautions.
6. Compliance: Companies use export information to ensure compliance with international laws and regulations. For instance, a Belgian chocolate manufacturer would need to know the food safety regulations, labeling requirements, and customs procedures of the countries they are exporting to.
7. Strategic Planning: Export information is used in strategic planning. For example, a Swedish furniture company might use export data to plan their production, marketing, and sales strategies. This information can help them to forecast demand, set prices, and allocate resources effectively.
LOST view: OV-Customs Functional Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/ExportsInformationBusinessObject
EIRA traceability: eira:InformationBusinessObject
ABB name: egovera:ExportsInformationBusinessObject
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-08
dct:identifier: http://data.europa.eu/dr8/egovera/ExportsInformationBusinessObject
dct:title: Exports information Information
Definition: Public blockchain governance refers to the decentralized decision-making process and rules that govern the operation and development of a permissionless blockchain network. In the context of European IT interoperability among member states and private companies, public blockchain governance would involve establishing a framework that allows for open participation and consensus among all stakeholders. This would enable the development of interoperable solutions, standards, and protocols that can be adopted and utilized by both public and private entities across Europe. The governance model would prioritize transparency, inclusivity, and collaboration to ensure the effective management and evolution of the blockchain network, fostering trust and enabling seamless interoperability among participants.
Additional information: Public blockchain governance refers to the decentralized decision-making processes and mechanisms that govern the operation, development, and interoperability of public blockchains. In the context of European IT interoperability among member states and private companies, public blockchain governance plays a crucial role in ensuring transparency, security, and trust in the exchange of information and services.
The European Union (EU) recognizes the potential of blockchain technology in enhancing interoperability and efficiency across various sectors. As a permissionless blockchain, it allows any participant to join the network, validate transactions, and contribute to the consensus mechanism. This open participation fosters a distributed governance model where decisions are made collectively by the network participants rather than a centralized authority.
The governance of public blockchain networks is typically achieved through a combination of technical protocols, community-driven decision-making processes, and consensus mechanisms. These mechanisms ensure that all participants have a say in the evolution and governance of the blockchain network, promoting inclusivity and preventing any single entity from having undue control.
In the European context, public blockchain governance for IT interoperability among member states and private companies would involve the establishment of standards, protocols, and frameworks that facilitate seamless data exchange and collaboration. These governance mechanisms would be designed to address the specific needs and requirements of the European IT ecosystem while ensuring compliance with relevant regulations and data protection laws such as the General Data Protection Regulation (GDPR).
To achieve effective governance, various stakeholders including member states, private companies, academic institutions, and technical experts would participate in the decision-making processes. This could involve the formation of working groups, committees, or consortia dedicated to addressing interoperability challenges, defining standards, and proposing technical solutions.
The governance model would also encompass mechanisms for resolving disputes, managing upgrades and updates, and ensuring the security and integrity of the blockchain network. This could involve the use of consensus mechanisms such as Proof of Work (PoW) or Proof of Stake (PoS) to validate transactions and prevent malicious activities.
Furthermore, public blockchain governance in the European context would also involve regulatory oversight to ensure compliance with existing laws and regulations. Regulatory bodies and authorities would play a role in monitoring the blockchain network, addressing potential risks, and enforcing legal requirements related to data privacy, security, and consumer protection.
Overall, the public blockchain governance for European IT interoperability among member states and private companies would aim to foster collaboration, transparency, and trust in the exchange of information and services. It would involve the active participation of stakeholders, adherence to standards and regulations, and the use of consensus mechanisms to ensure the integrity and security of the blockchain network.
Example: One example of the application of public blockchain governance (permissionless) in the context of European IT interoperability among member states and private companies is the European Blockchain Services Infrastructure (EBSI) project. EBSI aims to provide a trusted and secure blockchain infrastructure for cross-border public services within the European Union.
1. Cross-Border Data Sharing: Public blockchain governance can enable secure and transparent cross-border data sharing among member states and private companies. EBSI facilitates the exchange of data and documents, such as educational qualifications, healthcare records, and business licenses, using blockchain technology. This ensures data integrity, immutability, and reduces the need for intermediaries.
2. Supply Chain Management: Public blockchain governance can enhance interoperability in supply chain management across European member states and private companies. By utilizing blockchain technology, EBSI enables transparent and traceable supply chain processes, including product provenance, certifications, and customs documentation. This improves efficiency, reduces fraud, and enhances trust among participants.
3. Identity Management: Public blockchain governance can support interoperable identity management systems across European member states and private companies. EBSI aims to provide a decentralized and self-sovereign identity framework, allowing individuals and organizations to control their digital identities securely. This can streamline processes like e-government services, financial transactions, and access to public and private services.
4. Intellectual Property Rights: Public blockchain governance can facilitate interoperability in managing intellectual property rights across European member states and private companies. EBSI can provide a decentralized and tamper-proof registry for copyright, patents, and trademarks. This enables efficient and transparent management of intellectual property, reducing disputes and ensuring fair compensation for creators.
5. Smart Contracts and Legal Compliance: Public blockchain governance can enable interoperability in the execution and enforcement of smart contracts across European member states and private companies. EBSI can provide a platform for creating and executing self-executing contracts, ensuring compliance with legal requirements and reducing the need for intermediaries. This can streamline business processes and enhance trust in contractual agreements.
Overall, the application of public blockchain governance in European IT interoperability can foster transparency, trust, and efficiency in various sectors, promoting cross-border collaboration and innovation.
LOST view: TVA-Governance Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/PublicBlockChainGovernanceBusinessObject
EIRA traceability: eira:InteroperabilityGovernance
ABB name: egovera:PublicBlockChainGovernanceBusinessObject
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-05-22
dct:identifier: http://data.europa.eu/dr8/egovera/PublicBlockChainGovernanceBusinessObject
dct:title: Public BlockChain Governance (permissionless)
Definition: Open Data Policy ABB is a Business Object formalising the procedures to publish FAIR data generated by different parties. FAIR data means being aligned and compliant with FAIR principles, making data Findable, Accessible, Interoperable, and Reusable.
Source: EU Open Data guide
Source reference: http://bookshop.europa.eu/en/eu-open-data-pbOA0416036/downloads/OA-04-16-036-EN-C/OA0416036ENC_002.pdf?FileName=OA0416036ENC_002.pdf&SKU=OA0416036ENC_PDF&CatalogueNumber=OA-04-16-036-EN-C
Additional information: Open Data Policyspecifically refers to publish (raw) data in a way that is accessible, reusable, findable, machine readable and licensed permissively. It can be generated by a wide range of parties, including public authorities, the semi-public sector, businesses and the public. In the case of public authorities, such as European Union organisations, making their data available for public reuse supports economic development, openness and transparency.
Example: The following implementation is an example of how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): EU implementation of the G8 Open Data Charter. https://ec.europa.eu/digital-single-market/en/news/eu-implementation-g8-open-data-charter
IoP Dimension: Governance IoP
LOST view: Semantic view
Interoperability saliency: The Open Data Policy ABB is salient for semantic interoperability because Open Data is a part of the basic components of the EIF's conceptual model for integrated public services. Opening of public sector datasets for sharing and reuse is encouraged by the Directive on the reuse of public sector information, which provides a common legal framework for reuse of public sector data as stated in the EIF recommendation n° 2: "Publish the data you own as open data unless certain restrictions apply."
Identifier: http://data.europa.eu/dr8/OpenDataPolicyBusinessObject
eira:ID: ABB354
ABB name: eira:OpenDataPolicyBusinessObject
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-16-01
Definition: Confidentiality of business information refers to the protection of sensitive and proprietary data belonging to a business or organization. It involves ensuring that confidential information, such as trade secrets, financial data, client lists, and marketing strategies, remains secure and is accessible only to authorized individuals within the organization. Confidentiality safeguards aim to prevent unauthorized access, use, or disclosure of such information, which could compromise the competitive advantage, reputation, or legal standing of the business. This includes implementing appropriate security measures, access controls, non-disclosure agreements, and policies to maintain the confidentiality of business information.
Source: Based on World Intellectual Property Organization (WIPO)
LOST view: SV-Governance Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/AConfidentialityOfBusinessInformationBusinessObject
EIRA traceability: eira:DataPolicy
ABB name: egovera:AnonymisationPolicyBusinessObject
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-16-01
Description: The European interoperability framework is a commonly agreed approach to the delivery of European public services in an interoperable manner. It defines basic interoperability guidelines in the form of common principles, models and recommendations.
Additional information: The European Interoperability Framework (EIF) is a set of recommendations and guidelines created by the European Union to facilitate effective and efficient cross-border public service operations among EU member states. The framework seeks to improve how public administrations, businesses, and citizens communicate with each other digitally. The framework was first introduced in 2004 and has undergone subsequent revisions, with the latest version issued in March 2017.
Example: The European Interoperability Framework (EIF) is an initiative that aims to enhance the ability of European public services to work across borders and sectors. The goal is to increase the efficiency of these services and to promote the digital single market. Here are a few examples of how the EIF can be applied:
Publisher: Joinup
Source: https://ec.europa.eu/isa2/eif_en/
LOST view: OV-Data Spaces
Identifier: http://data.europa.eu/dr8/egovera/EuropeanInteroperabilityFrameworkBusinessObject
EIRA traceability: eira:InteroperabilityFrameworkBusinessObject
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2022-12-1
dct:identifier: http://data.europa.eu/dr8/egovera/EuropeanInteroperabilityFrameworkBusinessObject
Definition: Identification is data that could potentially be used to identify a particular person or entity.
Source: European Commission
Source reference: https://data.consilium.europa.eu/doc/document/ST-9565-2015-INIT/en/pdf
Additional information: Identification, within the context of information technology in Europe, refers to the process of uniquely recognizing and distinguishing an element or component within a system or network. It involves assigning a specific identifier or label to an entity, enabling its differentiation from other entities present in the system.
In the European IT context, identification plays a crucial role in various aspects, including data management, security, and access control. It allows for the precise identification of users, devices, applications, or any other entity within a network, facilitating efficient communication, resource allocation, and system administration.
At its core, identification involves the allocation of a unique identifier to each entity. These identifiers can take various forms, such as usernames, email addresses, IP addresses, device IDs, or digital certificates. The choice of identifier depends on the specific context and requirements of the system.
Identification is essential for effective data management and organization. By assigning unique identifiers to data elements, such as files, databases, or records, it becomes easier to locate, retrieve, and manipulate information. This is particularly important in large-scale systems where numerous entities coexist, and efficient data handling is crucial.
Moreover, identification plays a significant role in ensuring system security. By uniquely identifying users and devices, access control mechanisms can be implemented to regulate and monitor system entry. This helps prevent unauthorized access, protect sensitive information, and maintain the integrity and confidentiality of data.
In addition, identification is vital for authentication and authorization processes. When a user or device attempts to access a system or resource, their identification is verified to ensure they are who they claim to be. This verification process often involves the use of passwords, biometric data, or cryptographic keys. Once authenticated, the system can then determine the user's level of authorization and grant appropriate access privileges.
Furthermore, identification enables effective system administration and troubleshooting. By uniquely identifying devices, network administrators can monitor and manage their activities, track usage patterns, and diagnose and resolve issues more efficiently. This helps ensure the smooth operation and maintenance of IT systems.
Overall, identification is a fundamental concept within the European IT context, enabling the precise recognition and differentiation of entities within systems and networks. It serves as the basis for efficient data management, system security, access control, authentication, authorization, and system administration.
Example: Identification is a crucial element or component of information in various applications within the European IT context. Here are a few examples:
1. User Authentication: Identification plays a vital role in user authentication systems. When accessing online services, users need to prove their identity to gain authorized access. This can be achieved through various identification methods such as usernames, passwords, biometric data (e.g., fingerprints or facial recognition), or two-factor authentication. Identification ensures that only authorized individuals can access sensitive information or perform specific actions within the system.
2. Access Control: Identification is used in access control systems to determine the level of access granted to individuals or entities. By identifying users or devices, access control mechanisms can enforce different levels of permissions based on predefined rules. This ensures that sensitive data or resources are only accessible to authorized personnel, protecting against unauthorized access or data breaches.
3. Data Privacy and Protection: Identification is essential in ensuring data privacy and protection within the European IT context. The General Data Protection Regulation (GDPR) mandates that organizations handle personal data securely and protect the privacy rights of individuals. Identification helps in implementing data protection measures such as pseudonymization or anonymization, where personal data is replaced with unique identifiers to prevent direct identification of individuals.
4. Tracking and Traceability: Identification is used for tracking and traceability purposes in various domains. For instance, in supply chain management, products can be assigned unique identifiers or barcodes to track their movement from production to distribution. This enables efficient inventory management, quality control, and recall processes. Similarly, in healthcare, patient identification ensures accurate tracking of medical records, prescriptions, and treatments, improving patient safety and care coordination.
5. Fraud Prevention: Identification is employed to prevent fraud and unauthorized activities within the European IT context. Financial institutions, for example, use identification methods like secure login credentials, biometrics, or transaction verification to authenticate users and detect fraudulent transactions. Identification helps in establishing a digital identity that can be verified and trusted, reducing the risk of identity theft or fraudulent activities.
These examples demonstrate how identification serves as a fundamental component of information within the European IT context, enabling secure access, data protection, traceability, fraud prevention, and overall information management.
LOST view: Organisational view
Identifier: http://data.europa.eu/dr8/egovera/IdentificationBusinessObject
ABB name: egovera:IdentificationBusinessObject
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/egovera/IdentificationBusinessObject
Name: Identification Information
Interoperability Layer: Organisational
Specialises: http://data.europa.eu/dr8/InformationBusinessObject
Definition: Security Measure is data about a precaution taken against terrorism, espionage or other danger
Source: Collins Dictionary
Source reference: https://www.collinsdictionary.com/dictionary/english/security-measure#:~:text=(s%C9%AA%CB%88kj%CA%8A%C9%99r%C9%AAt%C9%AA%20%CB%88m%C9%9B%CA%92%C9%99%20),terrorism%2C%20espionage%20or%20other%20danger
Additional information: A security measure, in the context of information technology (IT), refers to a set of actions, procedures, or controls implemented to protect information and systems from unauthorized access, disclosure, alteration, destruction, or disruption. It encompasses various technical, administrative, and physical safeguards designed to ensure the confidentiality, integrity, and availability of information within an IT environment.
In the European IT context, security measures are of utmost importance due to the increasing reliance on digital systems and the vast amount of personal and sensitive data processed within the European Union (EU). The EU has established comprehensive regulations and guidelines to safeguard the privacy and security of individuals' data, such as the General Data Protection Regulation (GDPR) and the Network and Information Security (NIS) Directive.
Security measures can be categorized into different types, including:
1. Technical Measures: These measures involve the use of technology and software to protect information. Examples include encryption, firewalls, intrusion detection and prevention systems, access controls, secure coding practices, and vulnerability management. Technical measures aim to prevent unauthorized access, detect and respond to security incidents, and ensure the secure transmission and storage of data.
2. Administrative Measures: These measures encompass policies, procedures, and guidelines that govern the management and operation of IT systems. They include activities such as risk assessments, security awareness training, incident response planning, access control policies, and regular security audits. Administrative measures focus on establishing a security-conscious culture, defining roles and responsibilities, and ensuring compliance with applicable laws and regulations.
3. Physical Measures: These measures involve securing the physical infrastructure that houses IT systems and sensitive data. They include physical access controls, video surveillance, environmental controls (e.g., temperature and humidity monitoring), and secure disposal of physical media. Physical measures aim to protect against unauthorized physical access, theft, natural disasters, and other physical threats.
4. Organizational Measures: These measures involve the establishment of security-related roles, responsibilities, and governance structures within an organization. They include appointing a Data Protection Officer (DPO) to oversee data protection activities, establishing incident response teams, conducting regular security assessments, and implementing privacy-by-design principles. Organizational measures ensure that security is integrated into the overall business processes and decision-making frameworks.
In the European IT context, security measures must comply with the GDPR, which sets out specific requirements for the protection of personal data. These include implementing appropriate technical and organizational measures to ensure a level of security appropriate to the risk, conducting data protection impact assessments, and notifying individuals and relevant authorities in case of a data breach.
Overall, security measures in the European IT context are crucial for protecting sensitive information, ensuring compliance with data protection regulations, and maintaining the trust of individuals and organizations in the digital ecosystem.
Example: One example of the application of security measures in the European IT context is the implementation of encryption techniques. Encryption is a security measure that involves converting sensitive information into a coded form that can only be accessed by authorized individuals or systems. This ensures that even if the data is intercepted or accessed by unauthorized parties, it remains unreadable and protected.
Another example is the use of multi-factor authentication (MFA) systems. MFA is a security measure that requires users to provide multiple forms of identification, such as a password, a fingerprint scan, or a one-time password, to gain access to a system or application. This adds an extra layer of security by making it more difficult for unauthorized individuals to gain access to sensitive information.
In the European IT context, the General Data Protection Regulation (GDPR) is another important security measure. GDPR is a set of regulations that aim to protect the privacy and personal data of individuals within the European Union. It requires organizations to implement various security measures, such as data encryption, regular data backups, and access controls, to ensure the protection of personal data.
Firewalls are also commonly used security measures in the European IT context. Firewalls act as a barrier between an internal network and external networks, monitoring and controlling incoming and outgoing network traffic. They help prevent unauthorized access to a network and protect against various types of cyber threats, such as malware and hacking attempts.
Lastly, regular security audits and vulnerability assessments are essential security measures in the European IT context. These involve conducting systematic evaluations of an organization's IT infrastructure, identifying potential vulnerabilities or weaknesses, and implementing necessary measures to mitigate them. This proactive approach helps ensure that security measures are up to date and effective in protecting against emerging threats.
LOST view: OV-Functional Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/SecurityMeasureBusinessObject
ABB name: egovera:SecurityMeasureBusinessObject
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/egovera/SecurityMeasureBusinessObject
Name: Security Measure Information
Interoperability Layer: Organisational
Specialises: http://data.europa.eu/dr8/InformationBusinessObject
Definition: Economic Value Information refers to the quantifiable worth of data and information in economic terms. It is a crucial element in the digital economy, where information is used to drive decision-making, innovation, productivity, and competitiveness. The value is derived from the ability of this information to enhance business processes, reduce uncertainties, and create new opportunities. It can be measured in various ways, including the impact on revenue growth, cost savings, or strategic advantages gained. This concept is particularly relevant in the IT sector, where data is often considered a valuable asset that can be leveraged to create economic value.
Source: EIRA team
Additional information: Economic Value of Information (EVI) refers to the quantifiable benefit or worth that information holds within an economic system. It is a measure of the potential or actual contribution of information to the creation of wealth or the achievement of a competitive advantage. The economic value of information is not inherent but is determined by its relevance, accuracy, timeliness, completeness, and the cost of acquiring, processing, storing, and distributing it.
In the context of information technology, the economic value of information is often associated with data-driven decision making, business intelligence, and knowledge management. Information, when processed, organized, and interpreted, can lead to insights that drive strategic decisions, optimize operations, enhance customer service, and innovate products or services.
For instance, a company might use customer data to identify buying patterns, preferences, and trends, which can then be used to tailor marketing strategies, improve product design, and enhance customer experience. The economic value of this information is realized when these actions lead to increased sales, customer retention, and market share.
Moreover, the economic value of information can also be realized through cost savings. For example, a company might use operational data to identify inefficiencies or bottlenecks in its production process. By addressing these issues, the company can reduce waste, improve productivity, and lower production costs.
However, the economic value of information is not always positive. If the information is inaccurate, outdated, or irrelevant, it can lead to poor decisions, wasted resources, and missed opportunities. Similarly, if the cost of acquiring, processing, storing, and distributing the information exceeds its potential benefit, then its economic value is negative.
Furthermore, the economic value of information can be influenced by external factors such as market conditions, regulatory environment, and technological advancements. For instance, changes in data protection laws can affect the cost of data collection and processing, thereby impacting the economic value of information.
In conclusion, the economic value of information is a dynamic and complex concept that reflects the potential or actual contribution of information to wealth creation or competitive advantage in an economic system. It is determined by a range of factors including the quality of the information, the cost of managing it, and the external environment in which it is used.
Example: 1. E-commerce: The economic value of information is highly evident in the e-commerce industry. Companies like Amazon and eBay use customer data to personalize shopping experiences, recommend products, and predict future buying behavior. This information is valuable because it helps these companies increase sales, improve customer satisfaction, and gain a competitive edge.
2. Digital Marketing: In digital marketing, the economic value of information is seen in the use of customer data to create targeted advertising campaigns. By analyzing customer data, companies can identify trends and patterns in consumer behavior, which can be used to create more effective marketing strategies. This information is valuable because it can lead to increased sales and improved customer retention.
3. Banking and Finance: In the banking and finance industry, information such as credit scores, financial history, and risk profiles are used to make decisions about loans and credit. This information is valuable because it helps banks and financial institutions manage risk and make informed decisions.
4. Health Care: In the health care industry, patient data is used to improve patient care, predict health trends, and conduct medical research. This information is valuable because it can lead to improved patient outcomes, more effective treatments, and advancements in medical research.
5. Supply Chain Management: In supply chain management, information about suppliers, production processes, and distribution channels is used to improve efficiency and reduce costs. This information is valuable because it can lead to improved operational efficiency, cost savings, and increased profitability.
6. Telecommunications: In the telecommunications industry, customer data is used to personalize services, predict usage patterns, and improve network performance. This information is valuable because it can lead to improved customer satisfaction, increased usage, and improved network performance.
7. Energy Sector: In the energy sector, data about energy usage, demand patterns, and resource availability is used to manage energy production and distribution. This information is valuable because it can lead to improved energy efficiency, cost savings, and more sustainable energy practices.
LOST view: OV-Customs Functional Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/EconomicValueInformationBusinessObject
EIRA traceability: eira:InformationBusinessObject
ABB name: egovera:EconomicValueInformationBusinessObject
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-08
dct:identifier: http://data.europa.eu/dr8/egovera/EconomicValueInformationBusinessObject
dct:title: Economic value Information Information
Definition: Legislation on Data information and Knowledge Exchange ABB is a Business Object that refers to the legal basis, rules and agreements that regulate how data is shared, accessed and used amng different actors and systems.
Source: Inspired in EIF
Source reference: https://eur-lex.europa.eu/resource.html?uri=cellar:2c2f2554-0faf-11e7-8a35-01aa75ed71a1.0017.02/DOC_1&format=PDF
Example: The following implementation is an example of how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): Commission Regulation (EU) 2015/703 of 30 April 2015 establishing a network code on interoperability and data exchange rules (Text with EEA relevance) http://data.europa.eu/eli/reg/2015/703/oj
Interoperability Dimension: Behavioral IoP
LOST view: Legal view
Viewpoint: Key Interoperability Enablers viewpoint
Interoperability Saliency: The Legislation on Data Information and knowledge exchange ABB is a key interoperability enabler (*) for the governance, behavioural, structural and semantic interoperability because it sets rules that relate specifically to i) the reuse of solutions in the context of digital public services, ii) the exchange of digital data, information and knowledge, iii) the collaboration amongst the public administrations' digital services, and iv) the determination of standard data exchange models to facilitate data harmonization.
Identifier: http://data.europa.eu/dr8/LegislationOnDataInformationAndKnowledgeExchangeBusinessObject
ABB name: eira:LegislationOnDataInformationAndKnowledgeExchangeBusinessObject
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/LegislationOnDataInformationAndKnowledgeExchangeBusinessObject
Interoperability Layer: Legal
Definition: Laboratories information refers to the data and details generated, collected, and processed in a laboratory setting. This can include information about the tests conducted, the results obtained, the methods used, the equipment involved, and the personnel who carried out the work. It is a crucial component of information in the scientific, medical, and research fields, as it allows for the tracking, analysis, and replication of experiments and procedures. In the context of IT, laboratories information can be managed and utilized through specialized laboratory information systems (LIS) or laboratory information management systems (LIMS), which provide tools for data capture, management, retrieval, and reporting.
Source: EIRA team
Additional information: Laboratories information refers to the comprehensive data and details related to laboratory operations, procedures, and results. This information is a crucial component of the healthcare, research, and industrial sectors, among others. It encompasses a wide range of data, including but not limited to, patient or sample details, test results, methodologies used, equipment details, and personnel involved.
In a healthcare context, laboratories information is vital for diagnosing and treating patients. It includes data from various medical tests, such as blood tests, biopsies, and imaging studies. This information helps healthcare professionals understand a patient's health condition, monitor their progress, and decide on the most effective treatment plan.
In a research context, laboratories information includes data generated from experiments and studies. This can involve details about the materials and methods used, the experimental setup, the observations made, and the results obtained. This information is essential for validating research findings, replicating studies, and building upon existing knowledge.
In an industrial context, laboratories information can refer to data related to product testing and quality control. This can include information about the materials used, the tests performed, the standards adhered to, and the results obtained. This information is crucial for ensuring product safety, efficacy, and compliance with regulatory standards.
Laboratories information is typically managed and stored using Laboratory Information Management Systems (LIMS). These are software solutions designed to handle the complex data management needs of modern laboratories. They help in tracking samples, managing data, automating workflows, and ensuring compliance with various standards and regulations.
In the context of data protection and privacy, laboratories information, particularly in the healthcare sector, is subject to stringent regulations. This is due to the sensitive nature of the data, which often includes personal and confidential patient information. Therefore, it is crucial to ensure the secure handling, storage, and transmission of laboratories information to protect patient privacy and comply with data protection laws.
Example: 1. Healthcare: In the healthcare sector, laboratory information is crucial for patient diagnosis and treatment. For example, when a patient undergoes a blood test, the results are stored and processed in a Laboratory Information System (LIS). This system allows healthcare professionals to access and interpret the results, enabling them to make informed decisions about the patient's treatment plan.
2. Research and Development: In research and development sectors, laboratory information is used to record, analyze, and interpret experimental data. For instance, in pharmaceutical companies, the data from drug trials is stored and processed in a Laboratory Information Management System (LIMS). This system helps researchers to track the progress of drug development, identify potential issues, and make necessary adjustments.
3. Quality Control: In manufacturing industries, laboratory information is used to ensure the quality of products. For example, in a food processing company, samples of products are regularly tested in a laboratory. The results of these tests are stored and processed in a LIMS, which helps the company to monitor the quality of its products and comply with safety standards.
4. Environmental Monitoring: In environmental agencies, laboratory information is used to monitor and protect the environment. For instance, samples of air, water, and soil are regularly tested in a laboratory. The results of these tests are stored and processed in a LIMS, which helps the agency to track environmental changes, identify potential threats, and take necessary actions.
5. Education: In educational institutions, laboratory information is used to support teaching and learning. For example, in a chemistry class, students conduct experiments in a laboratory. The results of these experiments are stored and processed in a LIS, which helps students to understand the principles of chemistry and develop their scientific skills.
LOST view: OV-Customs Functional Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/LaboratoriesInformationBusinessObject
EIRA traceability: eira:InformationBusinessObject
ABB name: egovera:LaboratoriesInformationBusinessObject
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-08
dct:identifier: http://data.europa.eu/dr8/egovera/LaboratoriesInformationBusinessObject
dct:title: Laboratories information Information
Definition: A message is a discrete unit of communication intended by the source for consumption by some recipient or group of recipients.
Source: WikiPedia
Source reference: https://en.wikipedia.org/wiki/Message
Example: The application of the message as an element or component of information is crucial in various aspects of the European IT context. Here are a few examples:
1. Email Communication: In the European IT context, messages play a significant role in email communication. Emails are composed of messages that contain information such as the sender, recipient, subject, and body. Messages enable effective communication between individuals or organizations, facilitating the exchange of information, ideas, and documents.
2. Instant Messaging: Instant messaging platforms like WhatsApp, Telegram, or Slack heavily rely on messages as the core component of communication. Messages are used to convey real-time information, allowing individuals or teams to collaborate, share files, and discuss projects. In the European IT context, these messaging applications are widely used for both personal and professional purposes.
3. Push Notifications: Mobile applications often utilize messages in the form of push notifications to deliver important information or updates to users. For example, a European IT company may send push notifications to its users regarding software updates, security alerts, or promotional offers. Messages in push notifications help engage users and keep them informed about relevant information.
4. Error Messages: In the European IT context, error messages are commonly used to inform users about issues or problems encountered while using software or applications. These messages provide specific details about the error, helping users understand the problem and take appropriate actions. Clear and concise error messages contribute to a better user experience and facilitate efficient troubleshooting.
5. Chatbots: Chatbots are increasingly used in the European IT industry to provide automated customer support or assist users in various tasks. Messages form the basis of interactions with chatbots, where users input their queries or requests, and the chatbot responds with relevant information or actions. Messages enable seamless communication between users and chatbots, enhancing customer service and user experience.
Overall, messages serve as fundamental components of information in the European IT context, enabling effective communication, information exchange, and user interaction across various platforms and applications.
LOST view: OV-Functional Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/MessageBusinessObject
ABB name: egovera:MessageBusinessObject
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/egovera/MessageBusinessObject
Name: Message Information
Interoperability Layer: Organisational
Specialises: http://data.europa.eu/dr8/InformationBusinessObject
Definition: The Combined Nomenclature (CN) is a tool used for the classification of goods in the European Union (EU). It is a systematic and detailed list of descriptions and codes used to identify and categorize products for customs, statistical, and other EU purposes. The CN is based on the Harmonized System (HS) which is an international nomenclature developed by the World Customs Organization. It is updated annually to reflect changes in technology, market trends, and the needs of the users. The CN is essential for businesses as it determines the customs duties, import and export restrictions, and eligibility for preferential trade agreements.
Source: EIRA team
Additional information: The Combined Nomenclature (CN) is a tool used for the classification of goods in the European Union (EU). It is a methodological system that provides a systematic and detailed description of all types of goods that can be traded. The CN is based on the Harmonized System (HS), an international nomenclature developed by the World Customs Organization (WCO), but it includes additional subdivisions and legal notes created by the EU to address its specific needs.
The CN is used for various purposes such as customs duties, external trade statistics, internal taxes, trade negotiations, and economic research and analysis. It is a crucial element in the EU's trade policy, as it determines the tariffs and other trade measures applied to specific categories of goods.
The CN is composed of numerical codes, each representing a specific category of goods. Each code is composed of eight digits: the first six are based on the HS, while the seventh and eighth digits represent subdivisions specific to the EU. The CN also includes legal notes and footnotes that provide additional information and clarification on the classification of goods.
The CN is updated annually to reflect changes in technology, market trends, and the needs of the EU's trade policy. The updates are made through a democratic process involving consultations with EU member states and stakeholders, and are published in the Official Journal of the European Union.
In the context of information technology, the CN is used in various IT systems related to customs and trade in the EU. These systems use the CN codes to identify and classify goods, calculate customs duties and taxes, generate trade statistics, and manage trade measures. The CN is also used in electronic data interchange (EDI) between businesses and customs authorities, and in e-commerce platforms for the classification of products.
Example: 1. Import/Export Documentation: The Combined Nomenclature (CN) is used in import/export documentation to classify goods. It provides a systematic and detailed description of goods to be traded. For instance, a company exporting olive oil from Spain to Germany would use the CN code for olive oil in their export documentation. This helps customs authorities in both countries to identify the product and apply the correct tariffs and regulations.
2. Supply Chain Management: In supply chain management, the CN is used to identify and track goods throughout the supply chain. For example, a car manufacturer might use the CN codes for different car parts to manage their inventory and ensure that they have the necessary parts for production.
3. E-commerce: Online retailers use the CN to classify the products they sell. This helps them to calculate the correct VAT and customs duties for international sales. For example, a UK-based online retailer selling clothes to customers in France would use the CN code for clothes to calculate the VAT and customs duties.
4. Market Research: Businesses use the CN to conduct market research. By analyzing the import/export data associated with specific CN codes, businesses can identify trends, understand the demand for certain goods, and make informed decisions about their product offerings.
5. Regulatory Compliance: The CN is used to ensure regulatory compliance. For example, certain goods may be subject to restrictions or bans. By using the correct CN codes, businesses can ensure that they are not inadvertently violating these regulations.
6. Taxation: The CN is used to calculate taxes on goods. For example, a company importing electronics into Italy would use the CN code for electronics to determine the amount of import tax they need to pay.
7. Trade Negotiations: The CN is used in trade negotiations to identify and discuss specific categories of goods. For example, during a trade negotiation between the EU and another country, the CN codes for agricultural products might be used to discuss tariffs and quotas for these products.
LOST view: OV-Customs Functional Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/CombinedNomenclatureBusinessObject
EIRA traceability: eira:InformationBusinessObject
ABB name: egovera:CombinedNomenclatureBusinessObject
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-08
dct:identifier: http://data.europa.eu/dr8/egovera/CombinedNomenclatureBusinessObject
dct:title: Combined nomenclature Information
Definition: Distribution List is data about any individual or entity which is a member of and/or is otherwise participating in a Network.
Source: WhatIs.com
Source reference: https://www.techtarget.com/whatis/definition/distribution-list
Additional information: A distribution list, in the context of information technology, refers to a feature or component that allows users to send messages or information to a predefined group of recipients simultaneously. It is commonly used in email systems, collaboration platforms, and other communication tools to streamline the process of sending messages to multiple individuals or groups.
In essence, a distribution list acts as a virtual mailing list, enabling users to create a single address that represents multiple recipients. When a message is sent to this address, it is automatically distributed to all the members of the list. This eliminates the need to manually enter each recipient's email address, saving time and effort, particularly when dealing with large groups or frequently changing memberships.
Distribution lists can be created and managed by individuals, teams, or organizations, depending on the specific system or platform being used. They are typically set up and maintained by administrators or designated users who have the necessary permissions to manage the list's membership.
The primary purpose of a distribution list is to facilitate efficient and targeted communication within an organization or community. It allows users to reach a specific group of people with a single message, ensuring that relevant information is disseminated to the right individuals or teams. This is particularly useful in situations where regular updates, announcements, or notifications need to be shared with a specific audience, such as project teams, departments, or interest groups.
Distribution lists can be static or dynamic. Static distribution lists have a fixed membership that needs to be manually updated whenever there are changes in the recipient list. Dynamic distribution lists, on the other hand, are based on predefined criteria or rules, automatically including or excluding recipients based on specific attributes or characteristics. For example, a dynamic distribution list may include all employees from a particular department or all users with a specific job title.
In the European IT context, distribution lists are widely used in various industries and organizations to enhance communication and collaboration. They play a crucial role in facilitating efficient information sharing, ensuring that relevant updates and messages reach the intended recipients promptly. Additionally, distribution lists can be integrated with other IT systems and tools, such as customer relationship management (CRM) software or project management platforms, to streamline workflows and improve overall productivity.
Example: A distribution list, in the context of information management, refers to a group or list of email addresses that are used to send messages or distribute information to multiple recipients simultaneously. It is a commonly used feature in email systems and plays a crucial role in efficient communication within organizations. Here are a few examples of how distribution lists are applied in the European IT context:
1. Internal Communication: In a European IT company, a distribution list can be created for different departments or teams, such as development, marketing, or customer support. This allows for easy and quick dissemination of information within the respective teams. For instance, the marketing team can use a distribution list to share updates on upcoming campaigns, while the development team can use it to discuss technical issues or share project updates.
2. Project Collaboration: Distribution lists are often used to facilitate communication and collaboration among project teams. In a European IT project, a distribution list can be created to include all the project stakeholders, including team members, clients, and external consultants. This enables efficient sharing of project-related information, such as meeting minutes, progress updates, or important announcements. It ensures that everyone involved in the project stays informed and can contribute effectively.
3. Customer Communication: Distribution lists are also utilized for customer communication in the European IT industry. For instance, a software company may maintain a distribution list of its existing customers to send them product updates, new feature releases, or important security patches. This helps in keeping customers informed about the latest developments and ensures they have access to the necessary information to enhance their user experience.
4. Newsletter Subscriptions: Many European IT organizations use distribution lists to manage newsletter subscriptions. Users interested in receiving regular updates, industry news, or promotional offers can subscribe to a distribution list specifically created for newsletters. This allows the organization to send targeted information to the interested audience, ensuring effective communication and engagement.
5. Event Invitations: Distribution lists are commonly employed to send event invitations within the European IT sector. For example, an IT conference organizer may maintain a distribution list of industry professionals, speakers, and sponsors to send them invitations for upcoming events. This simplifies the process of reaching out to a large number of potential attendees and ensures that the event information reaches the relevant individuals.
Overall, distribution lists serve as a valuable component of information management in the European IT context, enabling efficient communication, collaboration, and targeted information dissemination within organizations and to external stakeholders.
LOST view: OV-Functional Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/DistributionListBusinessObject
ABB name: egovera:DistributionListBusinessObject
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/egovera/DistributionListBusinessObject
Name: Distribution list Information
Interoperability Layer: Organisational
Specialises: http://data.europa.eu/dr8/InformationBusinessObject
Definition: Conformance Test Scenario ABB is a Business Object specifying a sequence of actions for the execution of a test. Also known as a test script or manual test script.
Source: NIST
Source reference: https://www.nist.gov/itl/ssd/information-systems-group/overview-conformance-testing
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): SoapUI - SoapUI is the world's most widely-used open source API testing tool for SOAP and REST APIs. SoapUI offers SOAP Web Services functional testing, REST API functional testing, WSDL coverage, message assertion testing and test refactoring. Scenario-based tests should be directly tied to user stories, which were probably provided by the product owner or some business stakeholder. Under ideal circumstances, these tests should be the user stories, so that business stakeholders can both easily help the tester develop the test cases and understand the results. [https://www.soapui.org/testing-dojo/best-practices/scenario-based-testing.html][https://www.soapui.org/testing-dojo/world-of-api-testing/test-first.html]
Interoperability Dimension: Structural IoP
LOST view: Technical view - application
Interoperability Saliency: The Conformance Testing Scenario ABB is salient for technical interoperability because it provides a document of a list of activities for the execution of interoperability tests.
Identifier: http://data.europa.eu/dr8/ConformanceTestScenarioBusinessObject
ABB name: eira:ConformanceTestScenarioBusinessObject
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/ConformanceTestScenarioBusinessObject
Interoperability Layer: TechnicalApplication
Definition: Privacy Framework ABB is a Business Object that enables the confidentiality aspects of data, information and knowledge assets and organizational resources handling them.
Source: Inpired in the ISA2 and EIFv2-related works
Source reference: https://ec.europa.eu/isa2/isa2_en
Example: The following implementation is an example of how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): European Privacy Framework - European privacy legislation is made up of two parts: The Data Protection Directive (95/46/EC) exists as a common ground across Europe. The Directive is a legislative act of the European Union that requires all member states to ensure there is an "adequate" level of data protection. The second part consists of diverse national laws. (https://www.privacy-europe.com/european-privacy-framework.html)
IoP Dimension: Governance IoP
LOST view: Organisational view
Interoperability saliency: The Privacy Framework ABB is salient for governance and organizational interoperability because it provides the needed procedures and agreements on the establishment of privacy in public administration digital services. This framework commonly defined security and privacy actions to be considered in public digital services for ensuring secure and trustworthy data management.
Identifier: http://data.europa.eu/dr8/PrivacyFrameworkBusinessObject
eira:ID: ABB228
ABB name: eira:PrivacyFrameworkBusinessObject
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2022-12-01
Definition: Classification of goods information refers to the systematic categorization of goods or products based on a set of predefined criteria such as type, quality, quantity, price, etc. This classification is crucial for various business operations including inventory management, sales analysis, and strategic planning. In the context of information systems, it aids in the efficient organization, retrieval, and analysis of data related to goods. This classification can be based on international standards or can be customized as per the specific needs of an organization. It plays a significant role in enhancing the accuracy and efficiency of business processes, facilitating decision-making, and ensuring regulatory compliance.
Source: EIRA team
Additional information: Classification of goods information refers to the systematic categorization of goods or products based on a set of predefined criteria or standards. This classification system is used to organize and manage a wide range of goods in a structured and coherent manner, making it easier for businesses, consumers, and regulatory authorities to identify, compare, and analyze different types of goods.
The classification of goods information can be based on various factors, including the nature of the goods, their intended use, their physical characteristics, their value, and their origin. For example, goods can be classified according to their industry sector (e.g., electronics, clothing, food), their function (e.g., consumer goods, capital goods, intermediate goods), their material composition (e.g., metal goods, plastic goods, organic goods), their quality level (e.g., luxury goods, standard goods, budget goods), and their geographical origin (e.g., domestic goods, imported goods).
In the context of information systems and databases, the classification of goods information is a crucial component that enables efficient data management and retrieval. By assigning each good to a specific category or class, businesses can easily track their inventory, manage their supply chain, perform market analysis, and comply with regulatory requirements. Moreover, the classification of goods information can facilitate the automation of various business processes, such as order processing, invoicing, and reporting.
In the context of e-commerce and online shopping, the classification of goods information plays a key role in enhancing the user experience. It allows customers to browse through different categories of goods, compare similar products, and make informed purchasing decisions. Furthermore, it enables online retailers to personalize their product recommendations, optimize their search engine results, and target their marketing campaigns more effectively.
In the context of international trade and customs, the classification of goods information is essential for determining the applicable tariffs, taxes, and regulations. It is typically based on standardized classification systems, such as the Harmonized System (HS) or the Combined Nomenclature (CN), which are used by customs authorities worldwide to classify and codify all types of goods in international trade.
Overall, the classification of goods information is a fundamental element of information that contributes to the effective and efficient management of goods in various contexts, from business operations and e-commerce to international trade and customs.
Example: 1. E-commerce: In the realm of online shopping, the classification of goods information is crucial. Products are categorized based on various attributes such as type, brand, price, etc. This helps customers to easily navigate through the website and find the products they are looking for. For instance, a customer looking for a laptop can easily filter out irrelevant products by selecting the 'Electronics' category and then further narrowing down the search by selecting 'Laptops'.
2. Inventory Management: Businesses use the classification of goods information to manage their inventory effectively. By categorizing their products, they can easily track the quantity and location of specific items in their inventory. This helps in maintaining optimal stock levels and avoiding overstocking or understocking situations.
3. Supply Chain Management: The classification of goods information is also used in supply chain management. It helps in planning and executing the transportation of goods from the manufacturer to the end consumer. For example, perishable goods are classified separately so that they can be transported using refrigerated trucks.
4. Market Research: Companies use the classification of goods information to conduct market research. By analyzing the sales data of different product categories, they can identify market trends and consumer preferences. This information can be used to make informed decisions about product development and marketing strategies.
5. Regulatory Compliance: The classification of goods information is also important for regulatory compliance. Different types of goods are subject to different regulations. By correctly classifying their products, businesses can ensure that they are complying with all relevant laws and regulations.
6. Customs and Taxation: In international trade, the classification of goods information is used to determine the customs duties and taxes applicable to different products. This information is crucial for businesses to calculate the total cost of importing or exporting goods.
7. Product Recommendation Systems: E-commerce platforms use the classification of goods information to develop product recommendation systems. By analyzing the browsing and purchasing behavior of customers, they can recommend products that are likely to be of interest to them. For example, if a customer frequently purchases products from the 'Books' category, the system might recommend other popular books.
LOST view: OV-Customs Functional Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/ClassificationOfGoodsInformationBusinessObject
EIRA traceability: eira:InformationBusinessObject
ABB name: egovera:ClassificationOfGoodsInformationBusinessObject
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-08
dct:identifier: http://data.europa.eu/dr8/egovera/ClassificationOfGoodsInformationBusinessObject
dct:title: Classification of goods Information Information
Definition: Economic operator is data about a business or other organisation which supplies goods, works or services within the context of market operations
Source: WikiPedia
Source reference: https://en.wikipedia.org/wiki/Economic_operator
Additional information: An economic operator, within the European IT context, refers to any individual or legal entity that is involved in economic activities, such as the production, distribution, or provision of goods or services. It encompasses a wide range of entities, including businesses, companies, organizations, self-employed individuals, and professionals.
The concept of an economic operator is crucial in the European IT context due to its relevance in various regulatory frameworks and policies. It plays a significant role in areas such as public procurement, product safety, market surveillance, and data protection. Understanding the role and responsibilities of economic operators is essential for ensuring compliance with relevant regulations and promoting fair competition within the European IT market.
Within the European IT context, economic operators can be classified into different categories based on their specific roles and functions. These categories include manufacturers, authorized representatives, importers, distributors, and service providers. Each category has distinct obligations and responsibilities, which are defined by relevant legislation and regulations.
Manufacturers are economic operators who produce or assemble IT products within the European Union (EU) or import them from non-EU countries. They are responsible for ensuring that their products comply with applicable regulations, including technical standards, safety requirements, and environmental regulations. Manufacturers must also keep documentation, such as technical files and declarations of conformity, to demonstrate compliance.
Authorized representatives are individuals or entities appointed by non-EU manufacturers to act on their behalf within the EU. They have specific responsibilities, including ensuring that the products placed on the EU market meet the necessary requirements and maintaining the required documentation. Authorized representatives serve as a point of contact for market surveillance authorities and are responsible for handling any inquiries or issues related to the products they represent.
Importers are economic operators who bring IT products from non-EU countries into the EU market. They have the obligation to ensure that the imported products comply with EU regulations and are safe for consumers. Importers must verify that the necessary conformity assessment procedures have been carried out, maintain documentation, and ensure that the products are appropriately labeled and accompanied by the required information.
Distributors are economic operators involved in the supply chain of IT products. They do not modify the products but play a crucial role in ensuring that the products they distribute comply with applicable regulations. Distributors must verify that the products bear the required markings, labels, and information, and that they are accompanied by the necessary documentation. They also have the responsibility to cooperate with market surveillance authorities and manufacturers to address any non-compliance issues.
Service providers, within the European IT context, refer to economic operators who offer IT-related services, such as software development, IT consulting, or cloud computing. They may also provide maintenance, repair, or technical support services for IT products. Service providers must comply with relevant regulations, such as data protection laws, and ensure the security and confidentiality of the data they handle.
In summary, an economic operator, within the European IT context, encompasses various individuals and entities involved in economic activities related to IT products and services. Understanding the roles and responsibilities of economic operators is crucial for ensuring compliance with regulations, promoting fair competition, and safeguarding consumer interests within the European IT market.
Example: The Economic Operator is a crucial element or component of information within the European IT context. It refers to any person or entity engaged in economic activities, such as manufacturing, importing, distributing, or selling goods or providing services. The concept of Economic Operator is widely applied in various areas to ensure compliance with regulations, facilitate trade, and protect consumers. Here are a few examples of its application:
1. Product Safety and Compliance: Economic Operators play a vital role in ensuring the safety and compliance of products placed on the market. Manufacturers, importers, and distributors are considered Economic Operators responsible for ensuring that products meet the necessary standards, undergo appropriate testing, and carry the required certifications. This information about the Economic Operator helps authorities and consumers trace back the responsible party in case of any safety issues or non-compliance.
2. Supply Chain Management: In the European IT context, Economic Operators are essential for effective supply chain management. They provide information about the different entities involved in the supply chain, including manufacturers, suppliers, distributors, and retailers. This information helps in tracking the origin of products, ensuring transparency, and identifying potential risks or bottlenecks in the supply chain.
3. Customs and Trade Facilitation: Economic Operators are also significant in customs and trade facilitation processes. They are required to provide accurate and complete information about the goods being imported or exported, including their value, origin, and classification. This information enables customs authorities to assess duties and taxes, enforce trade regulations, and ensure compliance with customs procedures.
4. Consumer Protection: Economic Operators play a crucial role in protecting consumers' rights and interests. They are responsible for providing accurate and transparent information about the products or services they offer, including pricing, warranties, and after-sales support. This information helps consumers make informed decisions and seek redress in case of any issues or disputes.
5. Market Surveillance: Economic Operators are subject to market surveillance activities conducted by regulatory authorities. These activities aim to ensure that products and services meet the required standards and regulations, protecting consumers and maintaining fair competition. Information about the Economic Operator helps authorities identify and target specific entities for inspections, audits, or enforcement actions.
In summary, the Economic Operator is a fundamental element of information within the European IT context. Its application spans across various areas, including product safety, supply chain management, customs, trade facilitation, consumer protection, and market surveillance. Understanding and leveraging information about Economic Operators is crucial for ensuring compliance, facilitating trade, and protecting the interests of all stakeholders involved.
LOST view: OV-Functional Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/EconomicOperatorBusinessObject
ABB name: egovera:EconomicOperatorBusinessObject
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/egovera/EconomicOperatorBusinessObject
Name: Economic operator Information
Interoperability Layer: Organisational
Specialises: http://data.europa.eu/dr8/InformationBusinessObject
Definition: Digital Governance ABB is a Business Object that ensures the functioning of an Interoperability Framework. These rules include structures, roles, responsibilities, policies, standards, specifications, practices, decision making and operational procedures.
Source: EIF
Source reference: http://eur-lex.europa.eu/resource.html?uri=cellar:2c2f2554-0faf-11e7-8a35-01aa75ed71a1.0017.02/DOC_3&format=PDF
Additional information: Plans are in principle narrower and more detailed than Digital Agendas, and as a matter of fact they are intended to drill down and realise a global agenda. For an additional example of plan focused on interoperability, see the Governance Plan defined in the new European Interoperability Framework (EIF) - § 3.1 of the new EIF Annex II: Interoperability governance refers to decisions on interoperability frameworks, institutional arrangements, organisational structures, roles and responsibilities, policies, agreements and other aspects of ensuring and monitoring interoperability at national and EU levels. The European interoperability framework, the Interoperability Action Plan (Annex 1 to the Communication) and the European interoperability architecture (EIRA) are important parts of interoperability governance at the EU level. (http://eur-lex.europa.eu/resource.html?uri=cellar:2c2f2554-0faf-11e7-8a35-01aa75ed71a1.0017.02/DOC_3&format=PDF)
Example: The following implementation is an example of how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): The INSPIRE Directive 2007/2/EC of 14 March 2007, Article 18. Member States shall ensure that appropriate structures and mechanisms are designated for coordinating, across the different levels of government, the contributions of all those with an interest in their infrastructures for spatial information. These structures shall coordinate the contributions of, inter alia, users, producers, added-value service providers and coordinating bodies, concerning the identification of relevant data sets, user needs, the provision of information on existing practices and the provision of feedback on the implementation of this Directive. (http://eur-lex.europa.eu/legal-content/EN/TXT/PDF/?uri=CELEX:32007L0002&from=EN)
IoP Dimension: Governance IoP
LOST view: Organisational view
Interoperability saliency: The Digital Governance Plan ABB is salient for governance and organizational interoperability because it helps to (i) establish and holistic approach to data exchange and management, and (ii) determine the common instruments to achieve interoperability across administrative levels and sectors.
Identifier: http://data.europa.eu/dr8/DigitalGovernancePlanBusinessObject
eira:ID: ABB488
ABB name: eira:DigitalGovernancePlanBusinessObject
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2022-12-01
Definition: Origin of goods information refers to the data that identifies where a product or its components were produced, manufactured, or assembled. This information is crucial in the European IT context as it helps in determining the duties, taxes, and regulations applicable to the product. It also plays a significant role in trade agreements, anti-dumping policies, and consumer protection, as it allows for the tracking and verification of the product's journey from its source to the end-user. Additionally, it aids in maintaining the integrity of supply chains and ensuring compliance with environmental and labor standards.
Source: EIRA team
Additional information: Origin of goods information refers to the detailed data that identifies where a product or a good was produced, manufactured, or processed. This information is a crucial component of international trade, as it helps determine the duties and taxes applied to the goods, the eligibility for trade agreements, and compliance with product standards or regulations.
In the context of information systems, origin of goods information is a key data element that is captured, stored, and managed within various IT systems such as Enterprise Resource Planning (ERP) systems, Supply Chain Management (SCM) systems, and Customs Declaration systems. This information is often encoded in barcodes or Radio Frequency Identification (RFID) tags attached to the goods, and can be scanned and read by IT systems at various points in the supply chain.
The origin of goods information typically includes the country of manufacture or production, the manufacturer's details, and sometimes even the specific factory or plant where the goods were produced. It may also include information about the raw materials used in the production of the goods, if these are relevant to the product's compliance with certain regulations or eligibility for certain trade agreements.
In the European context, the origin of goods information is particularly important due to the European Union's complex rules on customs duties, Value Added Tax (VAT), and product standards. The EU has strict regulations on product safety, environmental standards, and consumer protection, and the origin of goods information is crucial for ensuring compliance with these regulations. Furthermore, the EU has numerous trade agreements with other countries and regions, and the origin of goods information is used to determine whether goods are eligible for preferential treatment under these agreements.
In summary, the origin of goods information is a vital element of information in the context of international trade and supply chain management. It is captured and managed by various IT systems, and is used for purposes such as calculating duties and taxes, ensuring compliance with regulations, and determining eligibility for trade agreements. In the European context, the importance of this information is heightened due to the EU's complex rules on customs, VAT, product standards, and trade agreements.
Example: 1. E-commerce: In the European e-commerce industry, the origin of goods information is crucial. It helps consumers make informed decisions about their purchases. For instance, a customer may prefer goods manufactured in a certain country due to quality assurance or ethical reasons. This information can also affect the shipping cost and delivery time, which are important factors for online shoppers.
2. Supply Chain Management: Companies use the origin of goods information to manage their supply chains more effectively. For example, a company might choose to source materials from a specific country because of lower costs, higher quality, or more favorable trade agreements. This information can also be used to track and trace goods, ensuring transparency and accountability in the supply chain.
3. Customs and Taxation: The origin of goods information is essential for customs and taxation purposes. Import duties, taxes, and regulations can vary depending on the country of origin. By accurately recording and reporting this information, companies can ensure compliance with all relevant laws and regulations.
4. Food Industry: In the food industry, the origin of goods information is particularly important. Consumers are increasingly interested in where their food comes from, and this information can influence their purchasing decisions. For example, a consumer might choose to buy organic apples from France rather than non-organic apples from another country.
5. Fashion Industry: In the fashion industry, the origin of goods information can be a significant selling point. For example, a consumer might be willing to pay a premium for a handbag made in Italy because of the country's reputation for high-quality leather goods.
6. Consumer Electronics: In the consumer electronics industry, the origin of goods information can affect a product's perceived quality and reliability. For example, a consumer might trust a smartphone made in Germany more than one made in a country with less stringent quality control standards.
7. Pharmaceutical Industry: In the pharmaceutical industry, the origin of goods information is crucial for regulatory compliance and patient safety. For example, a drug's country of origin can affect its approval process and its acceptance by doctors and patients.
LOST view: OV-Customs Functional Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/OriginOfGoodsInformationBusinessObject
EIRA traceability: eira:InformationBusinessObject
ABB name: egovera:OriginOfGoodsInformationBusinessObject
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-08
dct:identifier: http://data.europa.eu/dr8/egovera/OriginOfGoodsInformationBusinessObject
dct:title: Origin of goods Information Information
Definition: Temporary storage information refers to data that is stored for a limited period of time and is typically used for immediate processing or backup purposes. This type of information is often stored in volatile memory, such as RAM, which retains data as long as the system is powered on but loses it when the system is turned off. Temporary storage information can include cache data, session data, or other types of non-persistent data. It plays a crucial role in enhancing system performance and efficiency by providing quick access to frequently used data. However, due to its transient nature, it requires proper management and security measures to prevent data loss or unauthorized access.
Source: EIRA team
Additional information: Temporary storage information refers to data that is stored for a short period of time, typically in the computer's random access memory (RAM) or in other temporary storage areas within the system. This type of storage is volatile, meaning that the information is lost when the system is shut down or restarted.
Temporary storage is often used for data that is being processed or manipulated. For example, when a program is running, it may store data in temporary storage that it needs to access quickly or frequently. This can include everything from the contents of a document that you're currently editing, to the position of the mouse cursor, to the state of a game that you're playing.
Temporary storage is also used to hold data that is being transferred between different parts of the system or between different systems. For example, when you download a file from the internet, it may first be stored in temporary storage before being moved to its final location on your hard drive.
In the context of data protection and privacy, temporary storage information is subject to the same regulations and requirements as any other type of data. This means that it must be handled in a way that respects the rights of the individuals to whom it relates, and that appropriate measures must be taken to protect it from unauthorized access, loss, or damage.
In terms of data retention, temporary storage information is typically not kept for very long. However, the exact length of time can vary depending on the specific circumstances. For example, some data might be deleted as soon as it is no longer needed, while other data might be kept for a certain period of time to allow for system backups or for auditing purposes.
Example: 1. Web Browsing: Temporary storage information is used when browsing the internet. Websites often store cookies, which are small pieces of data, on the user's computer. These cookies are used to remember information about the user, such as login information, language preferences, and items in a shopping cart. This data is temporarily stored and often deleted after a certain period of time or when the browser is closed.
2. Caching: Temporary storage is also used in caching, where data is stored for quick access in the future. For example, a web browser may cache a webpage so that it loads faster the next time the user visits it. Similarly, a computer's processor may cache data from the hard drive to improve performance.
3. Session Storage: In web development, session storage is a form of temporary storage that allows data to be stored for the duration of a user's session on a website. This can be used to store user input, preferences, or other data that needs to be accessed across multiple pages of a website.
4. Buffering: Temporary storage is used in buffering, where data is temporarily held before it is processed. For example, when streaming a video, the data for the video is buffered before it is played. This allows the video to play smoothly without interruption.
5. Temporary Files: Many software applications create temporary files while they are running. These files are used to store data that the application needs to access quickly or frequently. Once the application is closed, these temporary files are often deleted.
6. RAM: The Random Access Memory (RAM) in a computer is a form of temporary storage. It holds the data that the computer is currently working with. This allows the computer to access this data quickly, improving its performance. Once the computer is turned off, the data in the RAM is lost.
7. Databases: In databases, temporary storage is used to hold data that is being processed or transferred. For example, when performing a complex query, the database may store intermediate results in temporary storage to improve performance.
LOST view: OV-Customs Functional Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/TemporaryStorageInformationBusinessObject
EIRA traceability: eira:InformationBusinessObject
ABB name: egovera:TemporaryStorageInformationBusinessObject
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-08
dct:identifier: http://data.europa.eu/dr8/egovera/TemporaryStorageInformationBusinessObject
dct:title: Temporary storage Information Information
Definition: Economic Operators Information refers to the data related to businesses or individuals who are involved in the supply chain of goods and services. This information can include details about their legal status, financial capacity, abilities, qualifications, and reliability. It is often used in procurement processes to assess the suitability of potential suppliers, contractors, or service providers. In the context of information systems, it can be a critical component for decision-making, risk assessment, and compliance checks.
Source: EIRA team
Additional information: Economic Operators Information refers to the comprehensive data related to businesses or individuals that are engaged in economic activities within a specific market. This information is crucial in the context of procurement, supply chain management, and market analysis. It includes details such as the operator's identity, legal status, financial standing, and technical or professional ability.
In the procurement process, for instance, the Economic Operators Information is used to assess the capability and reliability of potential suppliers or contractors. It helps in making informed decisions and mitigating risks associated with procurement.
The information can be obtained from various sources including the operators themselves, public records, financial institutions, and third-party agencies. It is typically stored in a structured format in databases or information systems, allowing for easy retrieval and analysis.
In addition to its use in procurement and supply chain management, Economic Operators Information is also important for regulatory compliance. Authorities may require businesses to provide this information to ensure they meet the necessary legal and financial requirements to operate in a particular market.
Moreover, Economic Operators Information can be used for market research and competitive analysis. It provides insights into the competitive landscape, market trends, and potential opportunities or threats.
In summary, Economic Operators Information is a critical component of information that supports various business processes and functions, from procurement and supply chain management to regulatory compliance and market analysis.
Example: 1. Supply Chain Management: Economic Operators Information is crucial in managing the supply chain. It helps in tracking and tracing the goods from the manufacturer to the end consumer. This information is used to ensure the authenticity of the products, prevent counterfeiting, and ensure compliance with the regulations.
2. Customs Clearance: Economic Operators Information is used in the customs clearance process. It helps in identifying the goods, their origin, and their destination. This information is used to calculate the correct amount of customs duties and taxes.
3. Risk Assessment: Economic Operators Information is used in risk assessment. It helps in identifying the potential risks associated with the goods, such as safety risks, health risks, and environmental risks. This information is used to take appropriate measures to mitigate these risks.
4. Market Surveillance: Economic Operators Information is used in market surveillance. It helps in monitoring the market, detecting any irregularities, and ensuring fair competition. This information is used to enforce the market rules and regulations.
5. Product Recall: Economic Operators Information is used in product recall. It helps in identifying the products that need to be recalled, their location, and their owners. This information is used to ensure the effective and efficient recall of the products.
6. Consumer Protection: Economic Operators Information is used in consumer protection. It helps in providing the consumers with accurate and reliable information about the products. This information is used to protect the consumers' rights and interests.
7. Trade Facilitation: Economic Operators Information is used in trade facilitation. It helps in simplifying and harmonizing the trade procedures, reducing the trade costs, and increasing the trade efficiency. This information is used to promote international trade.
8. Regulatory Compliance: Economic Operators Information is used in regulatory compliance. It helps in ensuring that the goods comply with the applicable regulations, such as safety regulations, quality regulations, and environmental regulations. This information is used to prevent any regulatory violations and penalties.
LOST view: OV-Customs Functional Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/EconomicOperatorsInformationBusinessObject
EIRA traceability: eira:InformationBusinessObject
ABB name: egovera:EconomicOperatorsInformationBusinessObject
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-08
dct:identifier: http://data.europa.eu/dr8/egovera/EconomicOperatorsInformationBusinessObject
dct:title: Economic Operators Information Information
Definition: Special Procedures Information refers to the specific set of instructions, guidelines, or protocols that are designed to manage, control, or execute certain tasks or operations within an information system or technology infrastructure. This can include procedures for data handling, system maintenance, security protocols, disaster recovery plans, and more. The goal of these procedures is to ensure the efficient, secure, and effective use of IT resources, as well as to mitigate risks and potential issues that may arise. They are typically documented and standardized to ensure consistency and compliance across the organization.
Source: EIRA team
Additional information: Special Procedures Information refers to a specific set of instructions, guidelines, or protocols that are designed to handle unique or exceptional circumstances within an information system or technology environment. This information is crucial in ensuring the smooth operation of IT systems, especially when dealing with situations that are not part of the regular or routine processes.
In the context of IT, special procedures information can cover a wide range of scenarios. It may include instructions for handling system failures, data breaches, or other security incidents. It could also provide guidelines for managing unusual data processing requirements, complex system integrations, or the implementation of new technologies.
The special procedures information is typically documented and maintained by the IT department or the system administrators. It is often part of the organization's IT policies and procedures, which are designed to ensure the efficient and secure operation of its technology infrastructure.
The special procedures information is not only important for dealing with exceptional situations. It also plays a key role in the organization's IT governance and risk management strategies. By having clear and detailed special procedures in place, the organization can better manage its IT risks and ensure that it is prepared to handle any potential issues or challenges that may arise.
In addition, the special procedures information can also be used for training and education purposes. It can help to ensure that all staff members are aware of the correct procedures to follow in different situations, which can help to improve the overall efficiency and effectiveness of the organization's IT operations.
In summary, the special procedures information is a critical component of an organization's IT management strategy. It provides the necessary guidance and instructions for handling unique or exceptional situations, thereby helping to ensure the smooth and secure operation of the organization's technology infrastructure.
Example: 1. Healthcare Sector: Special Procedures Information is crucial in the healthcare sector, particularly in the management of patient data. For instance, in the case of a surgical procedure, specific information about the procedure, such as the surgical technique used, the duration of the surgery, the type of anesthesia used, and the patient's response to the procedure, is recorded. This information is essential for post-operative care and future reference.
2. Aviation Industry: In the aviation industry, Special Procedures Information is used in flight operations. For example, pilots need to follow specific procedures during take-off, landing, and emergency situations. This information is critical for the safety and efficiency of flight operations.
3. Manufacturing Industry: In the manufacturing sector, Special Procedures Information is used in the production process. For instance, in the assembly line of a car manufacturing company, specific procedures need to be followed to ensure the quality and safety of the final product. This information is often documented in manuals and guides for workers to follow.
4. IT Sector: In the IT sector, Special Procedures Information is used in software development and system administration. For example, specific procedures need to be followed when coding a software program or managing a network system. This information is often documented in technical guides and manuals.
5. Education Sector: In the education sector, Special Procedures Information is used in teaching and learning processes. For instance, teachers need to follow specific procedures when conducting a lesson or assessing a student's performance. This information is often documented in lesson plans and assessment guides.
6. Legal Sector: In the legal sector, Special Procedures Information is used in court proceedings and legal documentation. For instance, lawyers need to follow specific procedures when presenting a case in court or drafting a legal document. This information is often documented in legal manuals and guides.
7. Financial Sector: In the financial sector, Special Procedures Information is used in banking and investment operations. For example, bankers need to follow specific procedures when processing a loan application or managing an investment portfolio. This information is often documented in operational manuals and guides.
LOST view: OV-Customs Functional Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/SpecialProceduresInformationBusinessObject
EIRA traceability: eira:InformationBusinessObject
ABB name: egovera:SpecialProceduresInformationBusinessObject
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-08
dct:identifier: http://data.europa.eu/dr8/egovera/SpecialProceduresInformationBusinessObject
dct:title: Special Procedures Information Information
Definition: Digital Signature is a mathematical scheme for verifying the authenticity of digital messages or documents.
Source: WikiPedia
Source reference: https://en.wikipedia.org/wiki/Digital_signature
Additional information: A digital signature is a cryptographic technique used to verify the authenticity, integrity, and non-repudiation of digital information. It serves as an electronic equivalent of a handwritten signature in the digital world. In the European IT context, digital signatures are governed by the eIDAS Regulation (Regulation (EU) No 910/2014), which provides a legal framework for electronic identification and trust services.
At its core, a digital signature is a mathematical algorithm that creates a unique digital fingerprint, also known as a hash, of a document or data. This hash is then encrypted using the private key of the signer, resulting in a digital signature. The private key is securely stored and known only to the signer, ensuring the confidentiality and integrity of the signature.
To verify the digital signature, the recipient uses the corresponding public key, which is made available by the signer or a trusted certification authority. The recipient applies the same cryptographic algorithm to the received document or data, generating a new hash. By decrypting the digital signature using the public key, the recipient can compare the computed hash with the decrypted hash. If they match, it confirms that the document has not been tampered with and was indeed signed by the claimed signer.
Digital signatures provide several benefits within the European IT context. Firstly, they establish the identity of the signer, ensuring that the signature is linked to a specific individual or entity. This helps prevent impersonation and fraud. Secondly, digital signatures guarantee the integrity of the signed information, as any modification to the document would result in a different hash value, rendering the signature invalid. Thirdly, digital signatures offer non-repudiation, meaning the signer cannot deny their involvement in signing the document, as the private key used for encryption is unique to them.
In the European IT context, digital signatures hold legal significance. The eIDAS Regulation recognizes digital signatures as legally equivalent to handwritten signatures, ensuring their acceptance across European Union member states. This facilitates cross-border transactions, e-commerce, and other digital interactions, as digital signatures provide a high level of trust and legal certainty.
Overall, digital signatures play a crucial role in ensuring the authenticity, integrity, and non-repudiation of digital information within the European IT context. They enable secure and legally binding electronic transactions, fostering trust and confidence in the digital economy.
Example: Digital signatures are widely used in various applications within the European IT context to ensure the authenticity, integrity, and non-repudiation of electronic information. Here are a few examples:
1. E-commerce: In online transactions, digital signatures are used to verify the identity of the parties involved and ensure the integrity of the exchanged data. For instance, when making a purchase online, a digital signature can be used to sign the transaction details, ensuring that they cannot be tampered with during transmission.
2. Electronic Contracts: Digital signatures are employed to sign electronic contracts, making them legally binding. By digitally signing a contract, parties can authenticate their agreement and prevent any subsequent denial of their involvement. This is particularly crucial in the European IT context, where electronic contracts have legal recognition.
3. Government Services: Digital signatures play a vital role in various government services, such as tax filings, license applications, and official document submissions. By digitally signing these documents, individuals and organizations can authenticate their identity and ensure the integrity of the information being submitted.
4. Health Records: In the healthcare sector, digital signatures are used to sign and authenticate electronic health records (EHRs). This ensures that patient data remains confidential, unaltered, and traceable. Digital signatures also enable healthcare professionals to securely exchange medical information across different systems and organizations.
5. Intellectual Property Protection: Digital signatures are used to protect intellectual property rights by providing proof of ownership and preventing unauthorized modifications. For example, digital signatures can be applied to digital content, such as software, music, or documents, to verify the authenticity and integrity of the content and protect it from unauthorized distribution or tampering.
6. Secure Email Communication: Digital signatures are utilized to secure email communication, ensuring that the sender's identity is verified, and the content remains intact. By digitally signing an email, the recipient can be confident that the message has not been altered during transmission and that it originated from the claimed sender.
Overall, digital signatures are a crucial component of information security within the European IT context, providing trust, integrity, and non-repudiation in various applications.
LOST view: OV-Functional Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/DigitalSignatureBusinessObject
ABB name: egovera:DigitalSignatureBusinessObject
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/egovera/DigitalSignatureBusinessObject
Name: Digital Signature Information
Interoperability Layer: Organisational
Specialises: http://data.europa.eu/dr8/InformationBusinessObject
Definition: Access rights are data that determine which users can view the object and what those users can do.
Source: IBM
Source reference: https://www.ibm.com/docs/en/filenet-p8-platform/5.2.0?topic=rights-what-are-access
Additional information: Access rights, in the context of information, refer to the permissions and privileges granted to individuals or entities to access and manipulate specific data or resources within an information system. It is a crucial component of information management and security, ensuring that only authorized users can access, modify, or delete information.
Access rights are designed to protect sensitive and confidential data, prevent unauthorized access, and maintain the integrity and availability of information. These rights are typically implemented through access control mechanisms, such as user authentication, authorization, and audit trails, which are enforced by the underlying IT infrastructure.
In the European IT context, access rights are governed by various regulations and frameworks, such as the General Data Protection Regulation (GDPR) and the Network and Information Security (NIS) Directive. These regulations aim to protect the privacy and security of personal data and ensure that organizations handle information in a responsible and compliant manner.
Access rights can be categorized into different levels or types, depending on the level of access granted to users. These may include:
1. Read Access: This level allows users to view or read information but does not permit them to make any changes or modifications. It is typically granted to individuals who require access to information for reference or informational purposes.
2. Write Access: Users with write access have the ability to create, modify, or delete information within the system. This level of access is usually granted to authorized personnel responsible for updating or maintaining data.
3. Execute Access: Execute access allows users to run or execute specific programs, scripts, or commands within the system. It is commonly granted to individuals who need to perform specific tasks or operations within the IT environment.
4. Delete Access: This level of access permits users to remove or delete information from the system. It is typically restricted to authorized personnel who are responsible for data management and retention.
5. Administrative Access: Administrative access provides users with elevated privileges, allowing them to manage and configure the system, grant or revoke access rights, and perform other administrative tasks. This level of access is usually limited to IT administrators or system administrators.
Access rights are typically assigned based on the principle of least privilege, which means that users are granted the minimum level of access necessary to perform their job responsibilities. This principle helps minimize the risk of unauthorized access, data breaches, and misuse of information.
To ensure effective access rights management, organizations often implement access control mechanisms, such as role-based access control (RBAC) or attribute-based access control (ABAC). These mechanisms enable organizations to define access policies, roles, and permissions, ensuring that users only have access to the information they need to perform their tasks.
Regular monitoring, auditing, and review of access rights are essential to maintain the security and integrity of information. Organizations must regularly assess and update access rights to reflect changes in job roles, responsibilities, and organizational structure, as well as comply with legal and regulatory requirements.
Example: Access rights, as an element or component of information, play a crucial role in ensuring the security and confidentiality of data within the European IT context. Here are some examples of their application:
1. User Authentication: Access rights are used to authenticate users before granting them access to sensitive information. This can involve verifying user credentials such as usernames, passwords, or biometric data to ensure that only authorized individuals can access the data.
2. Role-Based Access Control (RBAC): RBAC is a widely used access control mechanism in European IT systems. It assigns access rights based on predefined roles within an organization. For example, an employee may have access rights to view and edit certain files based on their job role, while a manager may have additional access rights to approve or deny access requests.
3. Access Control Lists (ACLs): ACLs are used to define and enforce access rights at a more granular level. They specify which users or groups have permission to perform specific actions on a particular resource. For instance, an ACL may allow a specific group of users to read a file but restrict their ability to modify or delete it.
4. Data Encryption: Access rights are also utilized in data encryption mechanisms to protect sensitive information. Encryption algorithms use access rights to determine who can decrypt and access the encrypted data. This ensures that even if unauthorized individuals gain access to the encrypted data, they cannot decipher it without the appropriate access rights.
5. Audit Trails: Access rights are instrumental in creating audit trails, which track and record all access attempts and actions performed on sensitive data. This helps in detecting and investigating any unauthorized access or suspicious activities, ensuring compliance with data protection regulations such as the General Data Protection Regulation (GDPR) in Europe.
6. Privacy by Design: Access rights are an essential component of the privacy by design principle, which is a fundamental aspect of European data protection laws. By implementing access rights from the early stages of system design, organizations can ensure that privacy and data protection measures are integrated into their IT systems, minimizing the risk of unauthorized access and data breaches.
Overall, access rights are a critical element in the European IT context, enabling organizations to protect sensitive information, comply with data protection regulations, and safeguard the privacy of individuals.
LOST view: OV-Functional Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/AccessRightsBusinessObject
ABB name: egovera:AccessRightsBusinessObject
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/egovera/AccessRightsBusinessObject
Name: Access rights Information
Interoperability Layer: Organisational
Specialises: http://data.europa.eu/dr8/InformationBusinessObject
Definition: A profile is information about a person or entity based on known traits or tendencies.
Source: Bart Custers
Source reference: https://papers.ssrn.com/sol3/papers.cfm?abstract_id=3186639
Additional information: A profile, within the European IT context, refers to a structured representation of an individual or entity's information, characteristics, preferences, and behavior. It is a comprehensive collection of data that provides a detailed overview of a user, system, or organization, enabling personalized services, targeted advertising, and efficient decision-making.
In the European IT context, a profile typically includes various types of information such as personal details (name, age, gender, contact information), demographic data (location, language, nationality), professional information (occupation, education, work history), and preferences (interests, hobbies, favorite products or services). It may also encompass behavioral data, including browsing history, purchase patterns, and interactions with digital platforms.
Profiles are often created and maintained by organizations, such as online service providers, e-commerce platforms, social media networks, or government agencies, to better understand their users and deliver tailored experiences. These profiles are built through the collection of data from various sources, including user-provided information, tracking technologies (cookies, device identifiers), and data obtained from third-party sources (data brokers, public records).
The European IT context emphasizes the importance of data protection and privacy. Therefore, the creation and use of profiles must comply with relevant regulations, such as the General Data Protection Regulation (GDPR). This means that individuals have the right to access, rectify, and delete their profile data, as well as the right to be informed about the purposes and legal basis for processing their information.
Profiles play a crucial role in enabling personalized services and experiences. For instance, online retailers can utilize customer profiles to recommend products based on past purchases and browsing behavior. Social media platforms leverage user profiles to display relevant content and advertisements tailored to individual interests. Additionally, profiles can assist organizations in making data-driven decisions, such as market segmentation, product development, and targeted marketing campaigns.
In summary, within the European IT context, a profile is a comprehensive representation of an individual or entity's information, preferences, and behavior. It enables organizations to deliver personalized services, targeted advertising, and informed decision-making while adhering to data protection regulations.
Example: The profile, as an element or component of information, finds various applications in the European IT context. Here are a few examples:
1. User Profiles: In the European IT context, user profiles are widely used in various online platforms and applications. These profiles contain information about the user's preferences, interests, demographics, and behavior patterns. User profiles help personalize the user experience by providing tailored content, recommendations, and targeted advertisements.
2. Customer Profiles: Many businesses in the European IT industry maintain customer profiles to understand their customers better. These profiles include information such as purchase history, preferences, feedback, and contact details. Customer profiles enable businesses to offer personalized services, improve customer support, and develop targeted marketing campaigns.
3. Job Seeker Profiles: Online job portals and recruitment platforms in Europe often require users to create profiles detailing their skills, qualifications, work experience, and career objectives. These profiles help job seekers showcase their expertise and make it easier for employers to find suitable candidates. Job seeker profiles streamline the hiring process and facilitate efficient talent acquisition.
4. Social Media Profiles: Social media platforms like Facebook, Instagram, and Twitter are widely used in Europe, and users create profiles to represent themselves online. These profiles contain personal information, photos, interests, and connections. Social media profiles enable individuals to connect with others, share content, and engage in online communities.
5. Professional Profiles: In the European IT industry, professionals often create profiles on platforms like LinkedIn to showcase their skills, work experience, and educational background. These profiles serve as digital resumes and help professionals network, find job opportunities, and establish their professional reputation.
6. Patient Profiles: In the healthcare sector, patient profiles are essential for managing medical records, treatment plans, and health information. Electronic Health Record (EHR) systems are widely used in Europe to create and maintain comprehensive patient profiles. These profiles assist healthcare providers in delivering personalized care, tracking medical history, and ensuring accurate diagnoses.
Overall, profiles play a crucial role in the European IT context, facilitating personalized experiences, efficient recruitment processes, targeted marketing, and effective information management across various domains.
LOST view: OV-Functional Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/ProfileBusinessObject
ABB name: egovera:ProfileBusinessObject
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/egovera/ProfileBusinessObject
Name: Profile Information
Interoperability Layer: Organisational
Specialises: http://data.europa.eu/dr8/InformationBusinessObject
Definition: A Data Quality Framework refers to a structured approach or set of guidelines that organizations use to assess, measure, and improve the quality of their data. It provides a systematic framework for managing data quality throughout its lifecycle, from data collection to data analysis and decision-making.
Source: European Commission
LOST view: SV-Governance Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/DataQualityFrameworkBusinessObject
ABB name: egovera:DataQualityFrameworkBusinessObject
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/egovera/DataQualityFrameworkBusinessObject
Interoperability Layer: Semantic
Specialises: http://data.europa.eu/dr8/DataPolicy
Definition: Imports information refers to the data related to goods, services, or intellectual property that a country purchases from other countries. This information includes details about the type of goods or services, their quantity, their origin, their destination, and their value. It is a crucial component of a country's trade statistics, which are used to analyze economic performance, make policy decisions, and negotiate international trade agreements. In the context of information technology, imports information can also refer to data or software components that are brought into a system or application from an external source.
Source: EIRA team
Additional information: Imports information refers to the data related to the goods, services, or other resources that are brought into a country from abroad for the purpose of selling or using them in domestic markets. This information is crucial for various sectors, including businesses, government agencies, and research institutions, as it helps them understand the country's economic health, market trends, and trade balance.
In the context of information technology, imports information can refer to the data or code brought into a software program or system from another source. This could include libraries, modules, functions, or other resources that are not originally part of the system but are necessary for its operation or functionality. The imported information can be used to extend the capabilities of the system, reduce redundancy, or improve efficiency.
The imports information can be structured or unstructured and may come in various formats, such as text, numbers, images, audio, video, etc. It can be stored in databases, files, or other data storage systems and can be processed, analyzed, and visualized using various data processing and analytics tools.
The accuracy, reliability, and timeliness of imports information are crucial. Therefore, it is often subject to various quality control measures, such as data validation, data cleaning, and data auditing. Moreover, due to its potential sensitivity, imports information is often subject to various security measures, such as data encryption, access control, and data anonymization, to protect it from unauthorized access, use, or disclosure.
The management of imports information, including its collection, storage, processing, analysis, and use, is often governed by various laws, regulations, standards, and best practices, such as data protection laws, trade laws, information security standards, and data management best practices. These aim to ensure the legality, fairness, transparency, accuracy, security, and ethical use of imports information.
Example: 1. Supply Chain Management: Imports information is crucial in supply chain management systems. It helps in tracking the movement of goods from one country to another, ensuring timely delivery and compliance with import regulations. For instance, a company in Germany importing electronic components from China would need accurate and timely imports information to manage its supply chain effectively.
2. Customs and Taxation: Customs departments and tax authorities use imports information to calculate duties and taxes. For example, the UK's HM Revenue and Customs would use this information to determine the value of goods imported into the country and the corresponding import duties and VAT payable.
3. Market Research: Businesses use imports information for market research and competitive analysis. For instance, a French wine producer might use this data to understand the volume of wine imported from Italy, Spain, and other countries, helping them to gauge competition and identify market opportunities.
4. Economic Analysis: Government agencies and research institutions use imports information for economic analysis and policy-making. For example, the Bank of Spain might use this data to understand the country's trade balance, economic growth, and the impact of trade policies.
5. Compliance and Risk Management: Companies use imports information to ensure compliance with import regulations and manage risks associated with international trade. For instance, a Dutch company importing timber from Brazil would need this information to ensure compliance with EU regulations on illegal logging.
6. Logistics and Transportation: Logistics and transportation companies use imports information to plan and manage their operations. For example, a Belgian logistics company might use this data to plan its shipping routes, manage its warehouse capacity, and optimize its operations.
7. Retail and E-commerce: Retail and e-commerce companies use imports information to manage their inventory and plan their product offerings. For example, a Swedish furniture retailer might use this data to understand the availability and cost of furniture imports, helping them to plan their inventory and pricing strategies.
LOST view: OV-Customs Functional Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/ImportsInformationBusinessObject
EIRA traceability: eira:InformationBusinessObject
ABB name: egovera:ImportsInformationBusinessObject
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-08
dct:identifier: http://data.europa.eu/dr8/egovera/ImportsInformationBusinessObject
dct:title: Imports information Information
Definition: Interoperability Framework ABB is a Business Object that enables interoperability to organisations that wish to collaborate towards the joint delivery of public services. Within its scope of applicability, it specifies a set of common elements such as vocabulary, concepts, principles, guidelines, and recommendations.
Source: ISA2, EIFv2
Source reference: (https://ec.europa.eu/isa2/isa2_en)
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): The new European Interoperability Framework (EIF) - The new European Interoperability Framework (EIF) is part of the Communication (COM(2017)134) from the European Commission adopted on 23 March 2017. The framework gives specific guidance on how to set up interoperable digital public services. It offers public administrations 47 concrete recommendations on how to improve governance of their interoperability activities, establish cross-organisational relationships, streamline processes supporting end-to-end digital services, and ensure that both existing and new legislation do not compromise interoperability efforts. The new EIF is undertaken in the context of the Commission priority to create a Digital Single Market in Europe. The public sector, which accounts for over a quarter of total employment and represents approximately a fifth of the EU’s GDP through public procurement, plays a key role in the Digital Single Market as a regulator, services provider and employer. The successful implementation of the EIF will improve the quality of European public services and will create an environment where public administrations can collaborate digitally. (https://ec.europa.eu/isa2/eif_en)
IoP Dimension: Governance IoP
LOST view: Organisational view
Interoperability saliency: The Interoperability Framework ABB is salient for organizational interoperability because it determines a set of rules, practices and a commonly agreed approach to the delivery of European public services.
Identifier: http://data.europa.eu/dr8/InteroperabilityFrameworkBusinessObject
eira:ID: ABB206
ABB name: eira:InteroperabilityFrameworkBusinessObject
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2022-12-01
Definition: Guarantee Information, as an element of information, refers to the specific details about the warranty or assurance provided by a manufacturer or service provider. This typically includes the duration of the guarantee, what it covers, and the terms and conditions for its application. It serves to protect the consumer by ensuring that the product or service meets certain standards of quality and performance. In the event of a defect or failure, the guarantee information outlines the recourse available to the consumer, such as repair, replacement, or refund.
Source: EIRA team
Additional information: Guarantee Information is a crucial component of information that refers to the assurance or warranty provided by a manufacturer or a service provider about the quality, durability, reliability, and functionality of a product or service. It is a legally binding commitment that the product or service will meet certain performance standards.
In the context of Information Technology (IT), Guarantee Information typically refers to the terms and conditions under which a software, hardware, or IT service is provided. It may include details about the expected performance of the software or hardware, the duration of the guarantee, the remedies available to the customer in case of defects or non-performance, and the procedures for claiming the guarantee.
Guarantee Information is essential for customers as it provides them with a level of protection and assurance about their investment in a product or service. It also helps in building trust between the customer and the manufacturer or service provider, and can be a key factor in the customer's decision-making process.
In the IT industry, Guarantee Information can cover a wide range of aspects. For software products, it may include guarantees about the software's functionality, compatibility with certain operating systems or hardware, and absence of harmful elements like viruses or malware. For hardware products, it may include guarantees about the product's durability, reliability, and performance under certain conditions. For IT services, it may include guarantees about the quality of service, response times, and resolution of issues.
Guarantee Information must be clear, accurate, and easily accessible to the customer. It should be provided in a language that the customer can understand, and should not contain any misleading or deceptive statements. In case of any changes in the Guarantee Information, the customer should be informed promptly and in a transparent manner.
In addition to the legal obligations, providing accurate and comprehensive Guarantee Information is also considered a good business practice in the IT industry. It can contribute to customer satisfaction, loyalty, and positive word-of-mouth, and can help in differentiating a company's products or services in a competitive market.
Example: 1. E-commerce: In the European e-commerce sector, guarantee information is a critical component. When a customer purchases a product online, they are provided with guarantee information that outlines the terms and conditions of the product warranty. This information is crucial for building trust between the buyer and seller, and it also protects the rights of the consumer.
2. Online Banking: In the banking sector, guarantee information is used to assure customers about the safety and security of their transactions. Banks provide information about their security measures, data protection policies, and deposit guarantees to build customer confidence and ensure compliance with European banking regulations.
3. Software Development: In the software industry, guarantee information is often provided in the form of service level agreements (SLAs). These guarantees outline the expected performance and reliability of the software, and they often include compensation provisions in case the software fails to meet these standards.
4. Telecommunications: In the telecom sector, providers often offer guarantee information related to the quality of their service. This can include guarantees about network uptime, data speeds, and coverage areas. These guarantees are important for attracting and retaining customers, and they also help to ensure compliance with European telecom regulations.
5. Health Care: In the health care sector, guarantee information is used to assure patients about the quality and safety of medical services. Hospitals and clinics provide information about their accreditation, the qualifications of their staff, and the safety measures they have in place. This information is crucial for building patient trust and ensuring compliance with European health care regulations.
6. Education: In the education sector, guarantee information is often provided in the form of accreditation. Schools and universities provide information about their accreditation status to assure students and parents about the quality of their education. This information is crucial for attracting students and ensuring compliance with European education standards.
LOST view: OV-Customs Functional Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/GuaranteeInformationBusinessObject
EIRA traceability: eira:InformationBusinessObject
ABB name: egovera:GuaranteeInformationBusinessObject
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-08
dct:identifier: http://data.europa.eu/dr8/egovera/GuaranteeInformationBusinessObject
dct:title: Guarantee Information Information
Definition: A document is a written, drawn, presented, or memorialized representation of thought, often the manifestation of non-fictional, as well as fictional, content
Source: WikiPedia
Source reference: https://en.wikipedia.org/wiki/Document
Additional information: A document, within the European IT context, refers to an electronic or physical entity that contains information in a structured or unstructured format. It serves as a means of storing, communicating, and preserving information for various purposes. Documents can exist in various forms, including text files, spreadsheets, presentations, images, audio files, videos, or any other digital or physical medium that can hold information.
In the European IT context, documents play a crucial role in information management, knowledge sharing, and collaboration within organizations and across different sectors. They are created, processed, stored, and accessed using various technologies, software applications, and systems. Documents can be generated by individuals, organizations, or automated processes, and they can be both static or dynamic, depending on the nature of the information they contain.
Documents typically have a defined structure or format that helps organize and categorize the information they hold. This structure can include headings, paragraphs, tables, lists, hyperlinks, metadata, and other elements that facilitate navigation, searchability, and understanding of the content. Additionally, documents often include attributes such as authorship, creation date, versioning, access permissions, and security features to ensure proper management and control over the information they contain.
Documents serve various purposes within the European IT context. They can be used for creating and sharing reports, contracts, policies, procedures, specifications, research papers, invoices, presentations, and many other types of content. They enable individuals and organizations to capture, record, and communicate information, ideas, and knowledge efficiently.
In the digital realm, documents are often stored in electronic document management systems (EDMS) or content management systems (CMS) that provide features for organizing, indexing, searching, and retrieving documents. These systems may also incorporate workflow capabilities, allowing for collaborative editing, review, and approval processes.
Furthermore, documents can be shared and distributed electronically through various channels such as email, file sharing platforms, cloud storage, or web-based portals. This facilitates remote collaboration, document version control, and simultaneous access by multiple users.
In summary, within the European IT context, a document is an element or component of information that can exist in various formats and serves as a repository for storing, communicating, and preserving information. It plays a vital role in information management, knowledge sharing, and collaboration, enabling individuals and organizations to capture, organize, and disseminate information efficiently.
Example: The application of documents as elements or components of information is prevalent in various aspects of the European IT context. Here are a few examples:
1. Documentation in software development: Documents play a crucial role in software development processes. Requirements documents outline the desired functionalities and specifications of a software system. Design documents provide a blueprint for the architecture and structure of the software. Technical documents document the codebase, APIs, and libraries used. User manuals and help guides are also important documents that assist end-users in understanding and utilizing the software effectively.
2. Legal documents and contracts: In the European IT context, legal documents and contracts are essential for establishing agreements between parties involved in IT-related activities. These documents include software licensing agreements, service level agreements (SLAs), non-disclosure agreements (NDAs), and intellectual property rights documentation. They ensure legal compliance, protect intellectual property, and define the rights and responsibilities of all parties involved.
3. Project documentation: Documentation is crucial in managing IT projects effectively. Project charters, project plans, and project scope documents outline the objectives, deliverables, timelines, and resources required for successful project execution. Progress reports, meeting minutes, and change request documents help track project progress, communicate updates, and manage changes throughout the project lifecycle.
4. Technical specifications and standards: Documents containing technical specifications and standards are vital in the European IT context. These documents define the requirements, guidelines, and best practices for hardware, software, and network infrastructure. They ensure interoperability, compatibility, and compliance with industry standards, facilitating seamless integration and communication between different IT systems and components.
5. Research papers and whitepapers: In the European IT context, research papers and whitepapers contribute to the advancement of knowledge and innovation. These documents present findings, analyses, and insights on various IT-related topics, such as emerging technologies, cybersecurity, data privacy, and artificial intelligence. They provide valuable information to researchers, industry professionals, policymakers, and the general public, fostering informed decision-making and driving technological advancements.
These examples illustrate how documents serve as fundamental elements or components of information in the European IT context, enabling effective communication, collaboration, and knowledge sharing within the IT industry.
LOST view: OV-Functional Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/DocumentBusinessObject
ABB name: egovera:DocumentBusinessObject
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/egovera/DocumentBusinessObject
Name: Document Information
Interoperability Layer: Organisational
Specialises: http://data.europa.eu/dr8/InformationBusinessObject
Definition: Custom Partners Information refers to the specific and tailored data related to business partners, which can include their contact details, preferences, transaction history, and other relevant information. This information is crucial for businesses to understand their partners' needs, preferences, and behaviors, enabling them to provide personalized services, improve business relationships, and make informed decisions. In the IT sector, this information is often managed and analyzed through Customer Relationship Management (CRM) systems or other similar software, ensuring data privacy and protection in accordance with the General Data Protection Regulation (GDPR).
Source: EIRA team
Additional information: Custom Partners Information refers to the specific, tailored data related to business partners, which can include suppliers, distributors, customers, or any other entities that a company interacts with in its business operations. This information is typically collected, stored, and managed to facilitate and enhance business relationships, decision-making processes, and strategic planning.
The scope of Custom Partners Information can be broad and varied, depending on the nature of the business and its specific needs. It may include basic contact details, such as names, addresses, and phone numbers, as well as more complex data, such as transaction histories, contractual details, performance metrics, and any other information that can provide insights into the partner's behavior, preferences, and capabilities.
This information is often used to personalize interactions with partners, improve communication, identify opportunities for collaboration, and mitigate potential risks. It can also be used to inform the development of products and services, the design of marketing campaigns, and the formulation of business strategies.
In the context of IT, Custom Partners Information is typically managed using sophisticated software systems, which can automate data collection, ensure data accuracy, facilitate data analysis, and enable secure data sharing. These systems can also support compliance with data protection regulations, by providing mechanisms for data encryption, access control, and audit logging.
Moreover, the use of advanced technologies, such as artificial intelligence and machine learning, can enable companies to extract even more value from their Custom Partners Information, by identifying patterns and trends that may not be apparent through manual analysis. This can lead to more accurate predictions, more effective decision-making, and ultimately, a stronger competitive advantage.
Example: 1. E-Commerce Platforms: Custom partners information can be used in e-commerce platforms to personalize the shopping experience. For example, based on the customer's previous purchases or browsing history, the platform can suggest products that the customer might be interested in. This can increase customer satisfaction and sales.
2. Customer Relationship Management (CRM): In CRM systems, custom partners information can be used to track interactions with customers, such as emails, calls, meetings, and sales. This information can help businesses understand their customers better and improve their customer service.
3. Supply Chain Management: Custom partners information can be used in supply chain management to track and manage the flow of goods and services. For example, a company can use this information to monitor the performance of its suppliers and make informed decisions about which suppliers to continue working with.
4. Marketing Automation: In marketing automation, custom partners information can be used to segment customers into different groups based on their behavior or characteristics. This can help businesses target their marketing efforts more effectively and increase their return on investment.
5. Business Intelligence: Custom partners information can be used in business intelligence to analyze business operations and make informed decisions. For example, a company can use this information to identify trends, patterns, and insights that can help it improve its business strategies.
6. Data Privacy and Security: In the context of data privacy and security, custom partners information can be used to manage and protect customer data. For example, a company can use this information to ensure that it is complying with data protection regulations and that customer data is being handled in a secure and responsible manner.
LOST view: OV-Customs Functional Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/CustomPartnersInformationBusinessObject
EIRA traceability: eira:InformationBusinessObject
ABB name: egovera:CustomPartnersInformationBusinessObject
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-08
dct:identifier: http://data.europa.eu/dr8/egovera/CustomPartnersInformationBusinessObject
dct:title: Custom partners Information Information
Definition: Duties Calculation Information refers to the data required to compute the taxes, tariffs, or fees that are imposed on goods and services. This information typically includes the value of the goods, their classification under a standardized system, the country of origin, and any applicable trade agreements or exemptions. In the context of IT, this information is often processed through automated systems or software to ensure accuracy and efficiency in the calculation and payment of these duties. This is a crucial component of supply chain management, international trade, and e-commerce operations.
Source: EIRA team
Last modification: 2023-08-08
Identifier: http://data.europa.eu/dr8/egovera/DutiesCalculationInformationBusinessObject
EIRA traceability: eira:InformationBusinessObject
EIRA concept: eira:ArchitectureBuildingBlock
Additional identifier: http://data.europa.eu/dr8/egovera/DutiesCalculationInformationBusinessObject
ABB name: egovera:DutiesCalculationInformationBusinessObject
Title: Duties calculation Information Information
Example: 1. E-commerce Platforms: Duties calculation information is crucial for e-commerce platforms that operate internationally. When a customer purchases a product, the system automatically calculates the duties based on the product's value, its category, and the country's import regulations. This information is then included in the total cost of the product, providing transparency to the customer about the final price they have to pay.
2. Supply Chain Management Systems: In supply chain management, duties calculation information is used to estimate the total cost of importing goods from different countries. This information helps businesses to make informed decisions about sourcing products, considering both the cost and time required for delivery.
3. Customs Brokerage Firms: Customs brokers use duties calculation information to help their clients understand the costs associated with importing goods. They use this information to prepare accurate customs declarations, ensuring that their clients comply with all import regulations and avoid any penalties.
4. Freight Forwarding Companies: Freight forwarders use duties calculation information to provide accurate quotes to their clients. By including the estimated duties in their quotes, they can provide a more accurate estimate of the total cost of shipping goods internationally.
5. Tax Software: Tax software applications use duties calculation information to help businesses calculate their tax liabilities. This includes duties on imported goods, which can be a significant expense for businesses that import a lot of goods.
6. ERP Systems: Enterprise Resource Planning (ERP) systems use duties calculation information to manage the financial aspects of a business's operations. This includes calculating the cost of goods sold, which includes the duties paid on imported goods.
7. International Trade Consultants: Consultants who specialize in international trade use duties calculation information to advise their clients on how to minimize their import costs. This can involve recommending alternative sourcing strategies or helping clients to take advantage of duty relief programs.
Additional information: Duties Calculation Information refers to the specific data required to accurately determine the amount of customs duties, taxes, or other charges that are applicable to a particular product or service. This information is crucial in international trade, as it helps businesses and individuals understand the costs associated with importing or exporting goods and services.
The information typically includes the classification of the goods or services based on a standardized system, such as the Harmonized System (HS) or the Combined Nomenclature (CN) used in the European Union. This classification determines the rate of duty applicable to the product.
Other relevant data may include the value of the goods, the country of origin, and any applicable trade agreements or preferential duty rates. The value of the goods is usually determined based on the transaction value, which includes the price paid for the goods, as well as any additional costs such as transport and insurance.
The country of origin is important as it can affect the rate of duty, especially in cases where there are trade agreements in place that provide for lower duty rates for goods from certain countries.
In addition, the Duties Calculation Information may also include information about any exemptions or reliefs that may apply, such as those for certain types of goods or for goods intended for specific uses.
This information is typically provided by the importer or exporter, and is used by customs authorities to calculate the amount of duty to be paid. The accuracy of this information is crucial, as any errors can result in incorrect duty calculations, leading to potential penalties and delays in the clearance of goods.
In the context of IT, Duties Calculation Information can be managed through customs management or trade compliance software, which can automate the process of classifying goods, calculating duties, and ensuring compliance with all relevant customs regulations. These systems can also help businesses keep track of changes in duty rates and regulations, and can provide reports and analytics to help businesses optimize their customs processes and minimize their duty costs.
Definition: Threads and fraudulent actions information refers to the data related to potential security risks and deceptive activities within an information system. This includes information about the source, nature, and potential impact of threats such as malware, phishing, hacking attempts, and other forms of cyber-attacks. It also encompasses data about fraudulent activities such as identity theft, financial fraud, data breaches, and other deceptive practices that can compromise the integrity, confidentiality, and availability of information. This information is crucial for IT security management, risk assessment, incident response, and compliance with data protection regulations.
Source: EIRA team
Additional information: Threads and fraudulent actions information refers to the data and intelligence related to potential threats and fraudulent activities within the realm of information technology. This encompasses a wide range of elements, from cyber threats such as hacking, phishing, and malware attacks, to fraudulent activities like identity theft, financial fraud, and data breaches.
Threads, in the context of IT, are sequences of programmed instructions that can be managed independently by a scheduler, which is part of the operating system. Threads are the smallest units of processing that can be performed in an OS. In the context of cybersecurity, threads can be manipulated by malicious actors to perform unauthorized actions, such as gaining access to sensitive data or disrupting normal operations.
Fraudulent actions, on the other hand, refer to deliberate deception for unfair or unlawful gain. In the IT context, this can take many forms. For instance, a fraudulent action could involve a hacker tricking a user into revealing their password, or a malicious actor creating a fake website to collect users' credit card information.
Information on threads and fraudulent actions is crucial for organizations to protect their IT infrastructure and data. This information can help organizations identify potential threats, develop effective security measures, and respond quickly to attacks. It can also assist in the investigation and prosecution of cyber crimes.
In the European context, threads and fraudulent actions information is particularly important due to the region's strict data protection laws. Organizations that fail to adequately protect their data can face hefty fines under regulations such as the General Data Protection Regulation (GDPR). Therefore, having accurate and up-to-date information on threads and fraudulent actions is essential for compliance with these laws.
Example: 1. Online Banking Fraud: In the realm of online banking, threads are used to handle multiple user requests simultaneously. However, fraudulent actions can occur when cybercriminals exploit these threads to launch attacks. For instance, they might use a technique called thread hijacking, where they take control of a legitimate thread to execute malicious actions. This could lead to unauthorized transactions, stealing of sensitive information, or even taking control of the user's account.
2. E-commerce Fraud: In e-commerce platforms, threads are used to manage multiple transactions and user interactions. Fraudsters can manipulate these threads to carry out fraudulent activities such as creating fake transactions, manipulating product prices, or stealing customer data.
3. Social Media Fraud: Threads are also used in social media platforms to handle multiple user interactions. Fraudsters can exploit these threads to spread misinformation, create fake profiles, or launch phishing attacks. They can also manipulate threads to promote their fraudulent activities or to spread malicious software.
4. Telecommunication Fraud: In the telecommunication sector, threads are used to manage multiple calls or data transfers. Fraudulent actions can occur when these threads are hijacked or manipulated to make unauthorized calls, send spam messages, or steal data.
5. Health Care Fraud: In the healthcare sector, threads are used to manage patient data and medical records. Fraudsters can exploit these threads to access and steal sensitive patient information, manipulate medical records, or carry out fraudulent billing.
6. Online Gaming Fraud: In online gaming, threads are used to manage multiple players and game interactions. Fraudsters can manipulate these threads to cheat in games, steal player accounts, or carry out in-game frauds.
In all these examples, the fraudulent actions can lead to significant financial losses, damage to reputation, and potential legal consequences. Therefore, it's crucial for organizations to implement robust security measures to protect their threads and prevent fraudulent activities.
LOST view: OV-Customs Functional Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/ThreadsAndFraudulentActionsInformationBusinessObject
EIRA traceability: eira:InformationBusinessObject
ABB name: egovera:ThreadsAndFraudulentActionsInformationBusinessObject
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-08
dct:identifier: http://data.europa.eu/dr8/egovera/ThreadsAndFraudulentActionsInformationBusinessObject
dct:title: Threads and fraudulent actions Information Information
Definition: An Anonymisation Policy is a formal document or set of guidelines implemented by an organization to outline the rules and procedures for anonymizing sensitive data. It defines the methods, techniques, and criteria used to transform personally identifiable information (PII) into a form that can no longer be linked to an individual. The policy ensures compliance with privacy regulations and helps mitigate the risk of unauthorized disclosure or misuse of personal data. It includes considerations for data anonymization processes, such as data masking, aggregation, or encryption, to protect individuals' privacy while still allowing data to be used for legitimate business purposes.
Source: European Data Protection Board
LOST view: SV-Governance Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/AnonymisationPolicyBusinessObject
ABB name: egovera:AnonymisationPolicyBusinessObject
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/egovera/AnonymisationPolicyBusinessObject
Interoperability Layer: Semantic
Specialises: http://data.europa.eu/dr8/DataPolicy
Definition: Blockchain governance refers to the framework and mechanisms put in place to ensure effective collaboration and interoperability among European member states and private companies in the field of IT. It involves establishing rules, standards, and protocols that govern the use, development, and maintenance of blockchain technology within the European Union. This governance framework aims to promote transparency, security, and trust in blockchain-based systems, enabling seamless data exchange and interoperability between member states and private entities. It also addresses issues such as data privacy, regulatory compliance, and dispute resolution, ensuring a harmonized approach to blockchain implementation and utilization across Europe.
Additional information: Blockchain governance refers to the mechanisms and processes through which decisions are made and rules are established in the context of blockchain technology. In the European Union (EU), blockchain governance plays a crucial role in ensuring interoperability among member states and private companies in the field of information technology (IT).
Interoperability refers to the ability of different systems, networks, and platforms to seamlessly exchange and use information. In the EU, achieving interoperability in IT is of paramount importance as it enables efficient and secure communication, data sharing, and collaboration among member states and private entities.
The governance of blockchain technology in the EU is primarily driven by the European Commission (EC), which is the executive body responsible for proposing legislation, implementing decisions, and ensuring the overall functioning of the EU. The EC recognizes the potential of blockchain technology in enhancing interoperability and has taken several initiatives to promote its adoption and governance.
One of the key initiatives is the European Blockchain Services Infrastructure (EBSI), which aims to provide a trusted and secure infrastructure for cross-border digital services in the EU. EBSI facilitates interoperability by establishing common standards, protocols, and frameworks for blockchain-based applications and services. It also promotes the use of decentralized identity, digital signatures, and smart contracts to enable secure and efficient transactions.
The governance of EBSI involves collaboration between the EC, member states, and private companies. The EC sets the strategic direction and provides funding for the infrastructure, while member states contribute to the development and implementation of interoperable solutions. Private companies, including blockchain technology providers and service providers, play a crucial role in developing and maintaining the technical aspects of the infrastructure.
To ensure effective governance, the EC engages in consultations with stakeholders, including member states, private companies, and civil society organizations. These consultations help in identifying the needs, challenges, and opportunities related to blockchain interoperability. The EC also encourages the participation of industry experts and researchers in shaping the governance framework.
In addition to EBSI, the EU has also established the European Blockchain Partnership (EBP) to promote collaboration among member states in the development and deployment of blockchain-based solutions. The EBP focuses on areas such as digital identity, regulatory compliance, supply chain management, and intellectual property rights. It facilitates the exchange of best practices, knowledge sharing, and joint projects among member states and private companies.
The governance of blockchain interoperability in the EU is guided by principles such as transparency, accountability, inclusivity, and privacy. The EC ensures that the decision-making processes are transparent and involve all relevant stakeholders. It also emphasizes the importance of accountability by regularly monitoring and evaluating the implementation of interoperability solutions.
Privacy is a critical aspect of blockchain governance, and the EU has enacted the General Data Protection Regulation (GDPR) to safeguard the rights and privacy of individuals. Blockchain-based systems must comply with GDPR requirements, such as data minimization, purpose limitation, and individual consent.
Overall, the blockchain governance regarding European IT interoperability among member states and private companies is a collaborative effort involving the European Commission, member states, and private entities. It aims to establish common standards, protocols, and frameworks to enable secure and efficient communication, data sharing, and collaboration in the EU.
Example: One example of the application of blockchain governance in European IT interoperability among member states and private companies is the European Blockchain Services Infrastructure (EBSI). EBSI is a blockchain-based platform developed by the European Commission to enable secure and trusted cross-border digital services within the European Union.
EBSI aims to facilitate interoperability among member states and private companies by providing a common infrastructure for sharing and verifying data across borders. It allows different entities to securely exchange information and transactions using blockchain technology, ensuring transparency, immutability, and trust in the data exchanged.
Another example is the use of blockchain governance in supply chain management. Blockchain can be utilized to establish a trusted and transparent supply chain network among member states and private companies. By recording every transaction and movement of goods on a blockchain, it becomes easier to track and verify the origin, authenticity, and quality of products. This enhances interoperability and trust among different entities involved in the supply chain, ensuring compliance with regulations and standards.
Furthermore, blockchain governance can be applied in the field of digital identity management. Member states and private companies can collaborate to develop a blockchain-based identity verification system that allows individuals to securely and easily prove their identity across different platforms and services. This interoperable digital identity infrastructure can streamline processes, reduce fraud, and enhance privacy and security.
Overall, blockchain governance can play a crucial role in promoting European IT interoperability by providing a trusted and transparent framework for data exchange, supply chain management, and digital identity verification among member states and private companies.
LOST view: TVA-Governance Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/BlockChainGovernanceBusinessObject
EIRA traceability: eira:DigitalGovernancePlanBusinessObject
ABB name: egovera:BlockChainGovernanceBusinessObject
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-05-22
dct:identifier: http://data.europa.eu/dr8/egovera/BlockChainGovernanceBusinessObject
dct:title: BlockChain Governance
Definition: Internal logistic information refers to the data and details related to the internal operations and processes of a company, particularly those associated with the movement and storage of goods within the organization. This information includes data on inventory management, warehousing, material handling, packaging, and transportation within the company's premises. It is crucial for optimizing internal operations, improving efficiency, reducing costs, and enhancing overall business performance. In the context of information technology, internal logistic information is often managed and analyzed through specialized software systems to facilitate real-time tracking, data accuracy, and strategic decision-making.
Source: EIRA team
Additional information: Internal logistic information refers to the data and details related to the management of goods within an organization. It encompasses all the information necessary for the efficient planning, implementation, and control of the internal flow of goods, from the point of acquisition to the point of consumption. This includes details about the procurement, handling, storage, and distribution of materials and finished products within the organization.
The internal logistic information is a crucial component of an organization's information system, as it directly impacts the efficiency and effectiveness of the supply chain. It includes data about inventory levels, demand forecasts, production schedules, order statuses, transportation schedules, and warehouse capacity, among others. This information is used to make strategic decisions about inventory management, production planning, and distribution strategies.
In addition to supporting operational decisions, internal logistic information also plays a critical role in strategic planning. It provides insights into the organization's operational efficiency, supply chain performance, and customer service levels. This information can be used to identify bottlenecks, evaluate the effectiveness of current strategies, and develop plans for improvement.
The management of internal logistic information requires robust information systems that can collect, store, process, and distribute data in a timely and accurate manner. These systems must also be capable of integrating with other systems within the organization, such as procurement, production, sales, and finance, to ensure a seamless flow of information across different functions.
In the context of the digital transformation, the management of internal logistic information is becoming increasingly complex and challenging. Organizations are dealing with larger volumes of data, more complex supply chains, and higher customer expectations. Therefore, they are investing in advanced technologies, such as big data analytics, artificial intelligence, and blockchain, to improve the accuracy, speed, and reliability of their internal logistic information.
Example: 1. Inventory Management: Internal logistic information is crucial in inventory management. It helps in tracking the quantity of each item in the warehouse, when to reorder, and how much to reorder. For instance, a retail company in Europe can use this information to ensure they have enough stock to meet customer demand and avoid overstocking, which can lead to increased costs.
2. Supply Chain Management: In supply chain management, internal logistic information is used to plan, implement, and control the efficient flow of goods from the point of origin to the point of consumption. For example, a manufacturing company in Europe can use this information to ensure timely delivery of raw materials, reduce production downtime, and improve customer satisfaction.
3. Warehouse Management: Internal logistic information is also used in warehouse management to optimize the storage and movement of goods within a warehouse. For instance, a logistics company in Europe can use this information to improve warehouse layout, reduce retrieval times, and increase overall warehouse efficiency.
4. Transportation Management: In transportation management, internal logistic information is used to plan and control the movement of goods from one location to another. For example, a shipping company in Europe can use this information to optimize routes, reduce fuel consumption, and ensure timely delivery of goods.
5. Demand Forecasting: Internal logistic information can be used to predict future demand for products. This can help businesses in Europe to plan their production and inventory levels more accurately, reducing the risk of stockouts or overstocking.
6. Order Processing: Internal logistic information plays a key role in order processing. It helps in tracking orders from placement to delivery, ensuring that customers receive their orders on time. For instance, an e-commerce company in Europe can use this information to improve order accuracy and customer satisfaction.
7. Production Planning: In manufacturing, internal logistic information is used to plan and control the production process. For example, a car manufacturer in Europe can use this information to schedule production runs, manage resources, and reduce production costs.
LOST view: OV-Customs Functional Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/InternalLogisticInformationBusinessObject
EIRA traceability: eira:InformationBusinessObject
ABB name: egovera:InternalLogisticInformationBusinessObject
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-08
dct:identifier: http://data.europa.eu/dr8/egovera/InternalLogisticInformationBusinessObject
dct:title: Internal logistic Information Information
Definition: A permission policy can be defined as a set of rules, guidelines, and controls that govern the authorization and access rights granted to individuals or roles within a system or organization. It outlines the specific permissions and privileges assigned to different entities to ensure appropriate access control and maintain the confidentiality, integrity, and availability of resources or information.
Source: ENISA
Source reference: https://resilience.enisa.europa.eu/article-13/guideline-for-minimum-security-measures/Article_13a_ENISA_Technical_Guideline_On_Security_Measures_v2_0.pdf
LOST view: SV-Governance Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/PermissionPolicyBusinessObject
ABB name: egovera:PermissionPolicyBusinessObject
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/egovera/PermissionPolicyBusinessObject
Interoperability Layer: Semantic
Specialises: http://data.europa.eu/dr8/DataPolicy
Definition: Private Blockchain Governance (permissioned) refers to a system of rules and regulations established by European member states and private companies to ensure interoperability in the field of IT. It involves the use of blockchain technology, where access to the blockchain is restricted to a select group of participants who have been granted permission. This governance framework aims to facilitate secure and efficient data exchange and collaboration between member states and private companies, enabling them to share information and resources while maintaining control over their data. It provides a standardized approach to ensure compatibility and seamless integration of IT systems, promoting interoperability and enhancing the overall efficiency and effectiveness of operations within the European IT ecosystem.
Additional information: Private blockchain governance refers to the rules, processes, and mechanisms that govern the operation and management of a private or permissioned blockchain network. In the context of European IT interoperability among member states and private companies, private blockchain governance plays a crucial role in ensuring the efficient and secure exchange of information and data.
Private blockchains are different from public blockchains like Bitcoin or Ethereum, as they are restricted to a specific group of participants who have been granted permission to join the network. In the case of European IT interoperability, this would involve member states and private companies that are part of the network.
The governance of a private blockchain network involves several key aspects:
1. Membership and Access Control: Private blockchains have a predefined set of participants who are granted permission to join the network. The governance framework defines the criteria for membership and the process for granting access to new participants. This ensures that only trusted entities can participate in the network, enhancing security and privacy.
2. Consensus Mechanism: Consensus is a fundamental aspect of blockchain governance, as it determines how transactions are validated and added to the blockchain. In a private blockchain, the consensus mechanism is typically more efficient and faster compared to public blockchains. The governance framework defines the consensus algorithm used, such as Proof of Authority or Practical Byzantine Fault Tolerance, to ensure agreement among network participants.
3. Data and Information Sharing: Interoperability among member states and private companies requires the sharing of data and information. The governance framework establishes the rules and protocols for data exchange, including data formats, encryption standards, and access controls. It ensures that data is shared securely and in compliance with relevant regulations, such as the General Data Protection Regulation (GDPR) in the European Union.
4. Smart Contract Deployment and Execution: Smart contracts are self-executing contracts with predefined rules and conditions. They automate business processes and transactions on the blockchain. The governance framework outlines the process for deploying and executing smart contracts, including the validation and verification mechanisms. It ensures that smart contracts are reliable, secure, and aligned with the legal and regulatory requirements of the participating entities.
5. Dispute Resolution: In any blockchain network, disputes may arise regarding transactions, data integrity, or governance itself. The governance framework defines the mechanisms for dispute resolution, including the formation of arbitration panels or the involvement of trusted third parties. It ensures that conflicts are resolved fairly and efficiently, maintaining trust among network participants.
6. Upgrades and Evolution: Blockchain technology is continuously evolving, and the governance framework should address the process for upgrades, improvements, and the introduction of new features. It may include mechanisms for proposing and approving changes, testing protocols, and ensuring backward compatibility. This allows the network to adapt to changing requirements and technological advancements.
In the context of European IT interoperability, private blockchain governance aims to establish a standardized and secure framework for member states and private companies to exchange information and collaborate. It ensures that the network operates efficiently, securely, and in compliance with relevant regulations, fostering trust and enabling seamless interoperability among participants.
Example: One example of the application of private blockchain governance (permissioned) in European IT interoperability among member states and private companies is the European Blockchain Services Infrastructure (EBSI). EBSI is a project initiated by the European Commission to establish a blockchain-based infrastructure for cross-border digital public services.
1. Cross-Border Data Sharing: Private blockchain governance can facilitate secure and efficient cross-border data sharing among member states and private companies. EBSI aims to provide a trusted and decentralized platform for sharing sensitive data, such as healthcare records, business registries, and educational qualifications, while ensuring data privacy and compliance with relevant regulations.
2. Supply Chain Management: Private blockchain governance can be applied to enhance supply chain management and interoperability across European member states. By implementing a permissioned blockchain network, companies can securely track and verify the movement of goods, ensuring transparency, traceability, and compliance with regulations. This can help streamline cross-border trade and reduce administrative burdens.
3. Intellectual Property Rights: Private blockchain governance can be utilized to manage and protect intellectual property rights across European member states. By leveraging a permissioned blockchain network, companies and creators can securely register and verify their intellectual property, such as patents, trademarks, and copyrights. This can facilitate interoperability and cross-border recognition of intellectual property rights.
4. Digital Identity Management: Private blockchain governance can enable secure and interoperable digital identity management across European member states. By implementing a permissioned blockchain network, individuals and organizations can have control over their digital identities, ensuring privacy, security, and seamless authentication across different services and jurisdictions.
5. Financial Services: Private blockchain governance can be applied to enhance interoperability and efficiency in financial services across European member states. By implementing a permissioned blockchain network, financial institutions can securely share and verify customer data, facilitate cross-border payments, and streamline regulatory compliance processes. This can foster innovation, reduce costs, and improve financial inclusion.
These examples demonstrate how private blockchain governance can be utilized to enhance European IT interoperability among member states and private companies, enabling secure and efficient cross-border collaboration in various sectors.
LOST view: TVA-Governance Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/PrivateBlockChainGovernanceBusinessObject
EIRA traceability: eira:InteroperabilityGovernance
ABB name: egovera:PrivateBlockChainGovernanceBusinessObject
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-05-22
dct:identifier: http://data.europa.eu/dr8/egovera/PrivateBlockChainGovernanceBusinessObject
dct:title: Private BlockChain Governance (permissioned)
Definition: Data Governance Guidelines can be defined as a set of principles, rules, and practices that provide direction and guidance for managing and controlling data assets within an organization. These guidelines outline the framework for ensuring data quality, integrity, privacy, security, and compliance throughout the data lifecycle, including data collection, storage, usage, and sharing.
Source: Data Governance Institute
Source reference: https://datagovernance.com/goals-and-principles-for-data-governance/
LOST view: SV-Governance Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/DataGovernanceGuidelinesBusinessObject
ABB name: egovera:DataGovernanceGuidelinesBusinessObject
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/egovera/DataGovernanceGuidelinesBusinessObject
Interoperability Layer: Semantic
Specialises: http://data.europa.eu/dr8/DataPolicy
Definition: An Interoperability Policy is a set of guidelines that outlines how different systems and data should work together seamlessly within an organization or across entities. It ensures that data formats, protocols, and interfaces are compatible and consistent, enabling effective data sharing and collaboration. The policy promotes the use of open standards and best practices to facilitate smooth communication and integration between various systems, applications, and stakeholders.
Source: EIF
Source reference: https://ec.europa.eu/isa2/sites/isa/files/eif_brochure_final.pdf
LOST view: SV-Governance Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/InteroperabilityPolicyBusinessObject
ABB name: egovera:InteroperabilityPolicyBusinessObject
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/egovera/InteroperabilityPolicyBusinessObject
Interoperability Layer: Semantic
Specialises: http://data.europa.eu/dr8/DataPolicy
Definition: A Blockchain policy, as a specialization of a Data policy, can be defined as a set of rules, guidelines, and controls that govern the management, access, and utilization of data within a blockchain network or ecosystem. It outlines the specific protocols, procedures, and requirements for storing, validating, and securing data on the blockchain, ensuring integrity, immutability, and transparency.
Source: OECD
Source reference: https://www.oecd.org/daf/blockchain/
LOST view: SV-Governance Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/BlockchainPolicyBusinessObject
ABB name: egovera:BlockchainPolicyBusinessObject
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/egovera/BlockchainPolicyBusinessObject
Interoperability Layer: Semantic
Specialises: http://data.europa.eu/dr8/DataPolicy
Definition: Digital Public Service Catalogue ABB is a Business Object that enables the index of active digital public services, and their descriptions, that are provided by a public administration. This ABB is a key interoperability enabler (*) for sharing/PROVISIONING and reusing/CONSUMING of front-office public services.
Source: ISA2 Core Vocabularies (https://joinup.ec.europa.eu/catalogue/distribution/cpsv-ap-specification-v20-pdf)
Synonym: Public Service Registry, Public Service Inventory
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): FEDICT service catalogue - FEDICT, part of the Federal Public Service Policy and Support of Belgium, offers a public service catalogue. Here are a few examples of the offered services: Company data (company information and certificates), Digiflow (access to online certificates), E-mail Relay (relay of e-mail to and from the federal public services and institutions, as a protection to viruses and spam), eBirth (birth online notification and transfer of statistics), eDepot (for notaries), Federal Authentication Service (authentication of individuals for access to online government applications), etc.(http://www.fedict.belgium.be/en/service_catalogue)
Interoperability Dimension: Structural IoP
LOST view: Organisational view
Viewpoint: Key Interoperability Enablers viewpoint
Interoperability Saliency: The Digital Public Service Catalogue ABB is a key interoperability enabler (*) for organisational and structural interoperability by (i) ensuring the provision/consumption of front-office digital public services, and (ii) making public and discoverable catalogues of data about public services to favour the use of common models.
Identifier: http://data.europa.eu/dr8/DigitalPublicServiceCatalogueBusinessObject
ABB name: eira:DigitalPublicServiceCatalogueBusinessObject
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/DigitalPublicServiceCatalogueBusinessObject
Interoperability Layer: Organisational
Definition: A payment is the voluntary tendering of money or its equivalent or of things of value by one party to another for exchanging goods or services.
Source: Mary Schaeffer
Source reference: https://onlinelibrary.wiley.com/doi/book/10.1002/9781119201953
Additional information: Payment, as an element or component of information, refers to the process of transferring funds or monetary value from one party to another in exchange for goods, services, or obligations. In the European IT context, payment encompasses various methods and technologies used to facilitate secure and efficient financial transactions within the digital realm.
In the European IT landscape, payment systems play a crucial role in enabling e-commerce, online banking, and other digital financial services. These systems ensure the seamless transfer of funds between buyers and sellers, while also ensuring the privacy, security, and integrity of sensitive financial information.
One of the primary components of payment in the European IT context is the payment gateway. A payment gateway acts as an intermediary between the merchant's website or application and the financial institution, facilitating the authorization and processing of transactions. It securely captures and encrypts payment data, such as credit card details or bank account information, and transmits it to the relevant financial institution for verification and approval.
Another essential element of payment in the European IT context is the payment processor. Payment processors are responsible for handling the actual transfer of funds between the buyer's and seller's accounts. They ensure that the transaction is completed accurately and securely, deducting the appropriate amount from the buyer's account and depositing it into the seller's account.
In addition to traditional payment methods like credit cards and bank transfers, the European IT context has witnessed the emergence of innovative payment technologies. These include mobile payment solutions, such as Near Field Communication (NFC) and mobile wallets, which allow users to make payments using their smartphones or other mobile devices. These technologies leverage encryption and tokenization techniques to protect sensitive payment information and provide a convenient and contactless payment experience.
Furthermore, the European IT context also emphasizes the importance of compliance with regulatory frameworks and standards to ensure the security and privacy of payment information. The General Data Protection Regulation (GDPR) and the Payment Card Industry Data Security Standard (PCI DSS) are examples of regulations and standards that govern the collection, storage, and processing of payment data within the European Union. Adhering to these regulations is crucial for businesses operating in the European IT landscape to maintain customer trust and avoid legal repercussions.
Overall, payment, as an element or component of information in the European IT context, encompasses the technologies, systems, and processes involved in securely transferring funds between parties in digital transactions. It encompasses payment gateways, payment processors, innovative payment technologies, and compliance with regulatory frameworks to ensure the smooth and secure flow of financial transactions within the European IT ecosystem.
Example: Payment is a crucial element or component of information systems in various applications within the European IT context. Here are a few examples:
1. E-commerce platforms: In online shopping websites or mobile applications, payment systems are integrated to facilitate secure and convenient transactions. These systems enable customers to make payments using various methods such as credit/debit cards, digital wallets, or bank transfers. They ensure the confidentiality and integrity of payment information, protect against fraud, and provide real-time transaction processing.
2. Mobile banking applications: With the rise of smartphones, mobile banking applications have become popular in Europe. These apps allow users to perform various financial activities, including making payments. Users can transfer funds to other individuals or businesses, pay bills, or make purchases using their mobile devices. Payment information is securely stored and transmitted, adhering to European data protection regulations.
3. Peer-to-peer payment platforms: Peer-to-peer (P2P) payment platforms enable individuals to send and receive money directly from their bank accounts or digital wallets. These platforms are commonly used for splitting bills, repaying debts, or sending money to friends and family. Payment information is securely processed, and users can often add additional security measures such as two-factor authentication.
4. Subscription-based services: Many European IT companies offer subscription-based services, such as streaming platforms, software-as-a-service (SaaS) applications, or online publications. Payment systems are integrated into these services to handle recurring payments from subscribers. Payment information is securely stored and processed, ensuring seamless and uninterrupted access to the subscribed services.
5. Contactless payments: In Europe, contactless payment methods, such as Near Field Communication (NFC) or mobile payment apps, have gained significant popularity. These methods allow users to make payments by simply tapping their cards or mobile devices on compatible payment terminals. Payment information is securely transmitted, and transaction limits are often imposed to prevent unauthorized usage.
In all these examples, the application of payment as an element or component of information ensures secure, efficient, and convenient financial transactions within the European IT context.
LOST view: OV-Functional Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/PaymentBusinessObject
ABB name: egovera:PaymentBusinessObject
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/egovera/PaymentBusinessObject
Name: Payment Information
Interoperability Layer: Organisational
Specialises: http://data.europa.eu/dr8/InformationBusinessObject
Definition: Workforce information refers to the data and details about the employees within an organization. It encompasses various aspects such as employee demographics, skills, qualifications, performance metrics, attendance, roles, responsibilities, and compensation details. This information is crucial for human resource management, strategic planning, decision making, and ensuring compliance with labor laws and regulations. In the context of IT, workforce information can also include data about employees' IT skills, training, certifications, and experience with specific technologies or methodologies.
Source: EIRA team
Additional information: Workforce information refers to the comprehensive data and details about the employees within an organization. This information is crucial for effective human resource management and strategic planning. It encompasses a wide range of data, including but not limited to, employee demographics (age, gender, nationality), employment details (job roles, employment status, work location), skills and competencies, performance ratings, training and development records, compensation and benefits, and employment history.
In the context of information technology (IT), workforce information is often stored, managed, and analyzed using sophisticated human resource information systems (HRIS) or other specialized IT tools. These systems enable organizations to efficiently manage workforce data, generate insightful reports, and support decision-making processes.
Workforce information is also essential for workforce planning, which involves analyzing the current workforce, forecasting future workforce needs, and developing strategies to meet these needs. This can include identifying skills gaps, planning for succession, and developing talent management strategies.
Moreover, workforce information plays a critical role in compliance with labor laws and regulations. It helps ensure that organizations are meeting their legal obligations, such as equal employment opportunity, health and safety, and data protection.
In the era of digital transformation, the importance of workforce information is increasing. It provides valuable insights that can drive improvements in productivity, employee engagement, and organizational performance. However, it also raises significant challenges in terms of data privacy and security. Organizations must ensure that they are handling workforce information in a manner that respects individual privacy rights and complies with data protection laws.
In summary, workforce information is a vital component of information in the IT context. It supports a wide range of human resource management activities, from operational tasks to strategic planning, and is subject to strict legal and ethical standards.
Example: 1. Human Resource Management Systems: Workforce information is crucial in the development and management of Human Resource Management Systems (HRMS). These systems are used to manage employee data, payroll, benefits, training, recruitment, and performance analysis. The workforce information helps in making strategic decisions related to hiring, training, and retention of employees.
2. Workforce Planning: Workforce information is used in strategic workforce planning. It helps in understanding the current workforce profile (skills, experiences, age, diversity, etc.) and predicting future workforce needs. This information is used to develop strategies to attract, retain and develop employees to meet future business needs.
3. Performance Management: Workforce information is used in performance management to track and analyze employee performance. It helps in identifying high performers, underperformers, and areas of improvement. This information is used to provide feedback, reward performance, and plan for training and development.
4. Talent Management: Workforce information is used in talent management to identify, attract, and retain high-quality employees. It helps in understanding the skills and competencies of the workforce, identifying gaps, and planning for succession.
5. Employee Engagement: Workforce information is used to measure and improve employee engagement. It helps in understanding the factors that influence employee engagement and developing strategies to improve it.
6. Workforce Analytics: Workforce information is used in workforce analytics to analyze workforce data and generate insights. These insights are used to make informed decisions related to workforce management and planning.
7. Compliance: Workforce information is used to ensure compliance with labor laws and regulations. It helps in tracking employee data, working hours, leave, and benefits to ensure compliance.
8. Productivity Analysis: Workforce information is used to analyze productivity and efficiency. It helps in identifying areas of improvement and developing strategies to improve productivity and efficiency.
9. Decision Making: Workforce information is used in decision making related to workforce management. It provides data and insights that help in making informed decisions.
10. Workforce Development: Workforce information is used in workforce development to plan for training and development activities. It helps in identifying skills gaps and training needs.
LOST view: OV-Customs Functional Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/WorkforceInformationBusinessObject
EIRA traceability: eira:InformationBusinessObject
ABB name: egovera:WorkforceInformationBusinessObject
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-08
dct:identifier: http://data.europa.eu/dr8/egovera/WorkforceInformationBusinessObject
dct:title: Workforce information Information
Definition: Binding Tariffs Information (BTI) is a system used in the European Union to provide importers and exporters with legally binding information on the classification of goods. This system ensures that all goods entering or leaving the EU are classified consistently and in accordance with the Combined Nomenclature, which is the EU's system for designating and coding products. The BTI provides certainty to traders about the tariffs that will be applied to their goods, and it is valid for three years from the date of issue.
Source: EIRA team
Additional information: Binding Tariff Information (BTI) is a system that provides economic operators with legal certainty regarding the tariff classification of their goods. It is a written decision given by the customs authorities of the European Union (EU) member states, upon request, on the classification of goods in the Combined Nomenclature (CN).
The BTI decision is legally binding on all EU customs authorities and on the holder of the decision for three years from the date of issuance. It ensures the uniform application of the customs rules throughout the EU and provides predictability for businesses in terms of import duties, other charges, and restrictions or prohibitions that may apply.
The BTI system is governed by the Union Customs Code (UCC), which sets out the legal framework for customs operations in the EU. The UCC provides that a BTI decision may be requested by any person who is either established in the customs territory of the Union or intends to use a BTI decision in relation to customs legislation.
The BTI decision includes information such as a description of the goods, their classification in the CN, and any additional information necessary for their identification. The decision is issued after a technical and scientific analysis of the goods, which may involve laboratory tests, expert opinions, or reference to international standards.
The BTI system is managed by the European Commission's Directorate-General for Taxation and Customs Union (DG TAXUD), which maintains a database of all BTI decisions issued by the EU member states. This database, known as the European Binding Tariff Information system (EBTI), is accessible to the public and allows for the search and retrieval of BTI decisions.
In the context of information technology, the BTI system and the EBTI database represent key tools for the digitalization and harmonization of customs procedures in the EU. They contribute to the efficiency and transparency of customs operations, facilitate trade, and support the competitiveness of European businesses.
Example: 1. Import/Export Business: A company that imports or exports goods within the European Union can use Binding Tariff Information (BTI) to determine the exact tariffs they will need to pay for specific goods. This can help them accurately calculate their costs and prices, and ensure they are in compliance with all relevant customs regulations.
2. E-commerce: An online retailer selling goods internationally can use BTI to calculate the customs duties that will apply to their products when they are shipped to customers in different EU countries. This can help them provide accurate information to their customers about the total cost of their purchases, including any additional customs duties.
3. Supply Chain Management: A company that sources materials or components from different countries can use BTI to understand the tariffs that will apply to these items. This can help them optimize their supply chain and reduce costs by sourcing from countries with lower tariffs.
4. Legal Compliance: Companies can use BTI to ensure they are in compliance with all relevant customs laws and regulations. This can help them avoid penalties and legal problems.
5. Financial Planning: By using BTI, companies can accurately forecast their future costs and revenues. This can help them make informed decisions about their business strategy and financial planning.
6. Market Research: Companies can use BTI to understand the tariffs that apply to different types of goods in different countries. This can help them identify new markets or products that could be profitable.
7. Logistics and Shipping: Logistics companies can use BTI to calculate the customs duties that will apply to the goods they are transporting. This can help them provide accurate quotes to their customers and ensure they are charging the correct amounts.
LOST view: OV-Customs Functional Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/BindingTariffsInformationBusinessObject
EIRA traceability: eira:InformationBusinessObject
ABB name: egovera:BindingTariffsInformationBusinessObject
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-08
dct:identifier: http://data.europa.eu/dr8/egovera/BindingTariffsInformationBusinessObject
dct:title: Binding Tariffs Information Information
Definition: Master Data Policy ABB is a Business Object being applied to 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
Source reference: http://www.dama.org
Example: The following implementation is an example of how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): EMVO: EMVS Master Data Guide - The EMVS (European Medicines Verification System) requires that OBP’s (OnBoarding Partners) upload both product master data and product batch/pack data. The aim of this guide is to clarify what data is expected to be used for the EMVS master data noting that the long-term goal is to source directly from the IDMP/SPOR system. https://emvo-medicines.eu/new/wp-content/uploads/EMVO_0122_EMVS-Master-Data-Guide-1.pdf
IoP Dimension: Governance IoP
LOST view: Semantic view
Interoperability saliency: The Master Data Policy ABB is salient for semantic interoperability because Master Data is used to establish the context for business transactions and transactional data by providing accurate data usually stored and available for reuse by other parties. Its management should be prioritised as stated in the EIF recommendation n° 31: "Put in place an information management strategy at the highest possible level to avoid fragmentation and duplication. Management of metadata, master data and reference data should be prioritised."
Identifier: http://data.europa.eu/dr8/MasterDataPolicyBusinessObject
eira:ID: ABB353
ABB name: eira:MasterDataPolicyBusinessObject
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-16-01
Definition: Data Portability Policy ABB is a Business Object that regulates data reuse and data transference between public administrations.
Source: GDPR
Source reference: https://gdpr.eu/recital-68-right-of-data-portability/
Additional information: This ABB implements the right to data portability, which is one of eight rights enforced by the EU General Data Protection Regulation (GDPR). It regulates the exchange of data, allowing data subjects to obtain data that a data controller holds on them and to reuse it for their own purposes. Accourding to GDPR, Individuals are free to either store the data for personal use or to transmit it to another data controller. The data must be received “in a structured, commonly used and machine-readable format”.
Example: The following implementation is an example of how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): Italy implementation of the Art. 68 of the EU General Data Protection Regulation (GDPR). https://www.garanteprivacy.it/regolamentoue/guida-all-applicazione-del-regolamento-europeo-in-materia-di-protezione-dei-dati-personali
IoP Dimension: Governance IoP
LOST view: Semantic view
Interoperability saliency: The Data Portability Policy ABB is salient for semantic interoperability because it regulates how data can be exchanged and its reuse.
Identifier: http://data.europa.eu/dr8/DataPortabilityPolicyBusinessObject
eira:ID: ABB362
ABB name: eira:DataPortabilityPolicyBusinessObject
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-16-01
Definition: Information ABB is a Business Object describing business facts, assets, or opinions that are exchanged in the context of a digital public service to support its delivery. Information is enacted via interpretation rules (expressed in an ontology) of data and considering knowledge of a given context. Examples include an invoice, a medical prescription, a driving license.
Source: TOGAF guide about business capabilities, TOGAF definition of information
Source reference: (https://www2.opengroup.org/ogsys/catalog/g161)), (http://pubs.opengroup.org/architecture/togaf9-doc/arch/)
Synonym: Business Facts, Business Data, Business Opinions
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): Surveillance3 - Surveillance information: Published Surveillance information (Business Information) on Europa: Textile category 1 - Cotton yarn, not put up for retail sale [Council Regulation (EEC) No 3030/93] from Belarus in 2015: see URL for details(http://ec.europa.eu/taxation_customs/dds2/surv/surv_data_list.jsp?Lang=en&survNumber=670010&survType=1&startDate=20150101&originCode=BY)
Interoperability Dimension: Behavioral IoP
LOST view: Organisational view
Viewpoint: Interoperability Privacy viewpoint
Interoperability Saliency: The Information ABB is salient for organisational interoperability because it represents the data being exchanged between organisations. Its interoperability needs to be guaranteed using organisational and semantic interoperability specifications.
Identifier: http://data.europa.eu/dr8/InformationBusinessObject
ABB name: eira:InformationBusinessObject
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/InformationBusinessObject
Interoperability Layer: Organisational
Definition: Hybrid Blockchain Governance refers to the framework established for the European IT interoperability between member states and private companies. It combines elements of both centralized and decentralized governance models to ensure efficient and secure data exchange. This approach involves the collaboration of public and private entities, with the government playing a regulatory role while allowing private companies to participate in decision-making processes. The hybrid governance model aims to promote transparency, accountability, and consensus among stakeholders, enabling seamless interoperability and data sharing across European member states and private organizations.
Additional information: Hybrid Blockchain Governance refers to a system of governance that combines elements of both centralized and decentralized decision-making processes using blockchain technology. In the context of European IT interoperability among member states and private companies, Hybrid Blockchain Governance aims to establish a framework that ensures efficient and secure data exchange, collaboration, and interoperability.
The European Union (EU) recognizes the importance of interoperability in the digital age, where seamless data sharing and communication between member states and private companies are crucial for economic growth, innovation, and public services. To address this, the EU has been exploring the potential of blockchain technology to enhance interoperability and streamline governance processes.
In a Hybrid Blockchain Governance model, the decision-making authority is distributed among various stakeholders, including member states, private companies, and relevant EU institutions. This model aims to strike a balance between centralized control and decentralized participation, ensuring that all stakeholders have a say in the governance of interoperability initiatives.
The governance framework begins with the establishment of a common set of standards and protocols that facilitate interoperability. These standards are developed through a collaborative process involving member states, private companies, and EU institutions. Blockchain technology can be leveraged to ensure transparency, immutability, and security in the development and implementation of these standards.
The governance structure also includes the creation of a governing body or consortium responsible for overseeing the implementation and maintenance of the interoperability framework. This body consists of representatives from member states, private companies, and relevant EU institutions. It sets the rules, policies, and guidelines for data exchange, privacy protection, and security measures.
To ensure effective governance, Hybrid Blockchain Governance incorporates mechanisms for consensus-building and decision-making. Blockchain technology enables the use of smart contracts, which are self-executing agreements that automatically enforce predefined rules. These smart contracts can be used to facilitate decision-making processes, such as voting on proposed changes or updates to the interoperability framework.
Furthermore, the governance model includes mechanisms for monitoring and enforcement. Blockchain technology provides a transparent and auditable record of all transactions and activities, enabling stakeholders to track compliance with the established standards. In case of non-compliance, appropriate measures can be taken, such as penalties or sanctions, to ensure adherence to the governance framework.
The Hybrid Blockchain Governance model also emphasizes the importance of data privacy and protection. It incorporates privacy-enhancing technologies, such as zero-knowledge proofs or differential privacy, to ensure that sensitive information is securely shared while preserving individual privacy rights.
Overall, the Hybrid Blockchain Governance model for European IT interoperability among member states and private companies aims to establish a collaborative, transparent, and secure framework. It leverages blockchain technology to enable efficient data exchange, decision-making, and enforcement, while ensuring privacy and protection of sensitive information. By fostering interoperability, this governance model promotes innovation, economic growth, and improved public services across the European Union.
Example: One example of the application of Hybrid Blockchain Governance in European IT interoperability among member states and private companies is the European Blockchain Services Infrastructure (EBSI) project. EBSI aims to establish a trusted and secure blockchain infrastructure for the European Union (EU) member states and their public administrations.
EBSI utilizes a hybrid blockchain governance model, combining both public and private elements. The governance structure involves collaboration between the European Commission, member states, and private companies. Here are some key aspects of its application:
1. Public-private partnership: EBSI involves collaboration between the public sector (European Commission and member states) and private companies. Private companies participate in the development, deployment, and maintenance of the blockchain infrastructure, ensuring interoperability and scalability.
2. Decentralized governance: The governance of EBSI is decentralized, with decision-making power distributed among various stakeholders. This includes representatives from member states, the European Commission, and private companies. The governance model ensures that no single entity has complete control over the infrastructure, promoting transparency and inclusivity.
3. Interoperability standards: EBSI focuses on developing interoperability standards for blockchain applications across member states and private companies. These standards enable seamless data exchange and collaboration between different entities, ensuring compatibility and efficiency in IT systems.
4. Regulatory compliance: Hybrid Blockchain Governance in EBSI ensures compliance with EU regulations and data protection laws. The governance model incorporates legal and regulatory frameworks, ensuring that the blockchain infrastructure adheres to privacy and security requirements.
5. Use cases: EBSI is being applied to various use cases, such as digital identity, supply chain management, and document management. For example, member states can use EBSI to verify and authenticate digital identities across borders, enabling secure access to public services. Private companies can leverage EBSI for supply chain transparency, tracking the origin and authenticity of products.
Overall, the application of Hybrid Blockchain Governance in EBSI facilitates European IT interoperability by combining the strengths of public and private sectors, promoting decentralized decision-making, establishing interoperability standards, ensuring regulatory compliance, and enabling various use cases.
LOST view: TVA-Governance Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/HybridBlockchainGovernanceBusinessObject
EIRA traceability: eira:DigitalGovernancePlanBusinessObject
ABB name: egovera:HybridBlockchainGovernanceBusinessObject
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-05-22
dct:identifier: http://data.europa.eu/dr8/egovera/HybridBlockchainGovernanceBusinessObject
dct:title: Hybrid Blockchain Governance
Definition: Security Policy ABB is a Business Object that regulates the protection of customer or client's data.
Source: Gartner
Source reference: https://www.gartner.com/en/information-technology/glossary/security
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): Common Foreign and Security Policy (CFSP) - The Common Foreign and Security Policy (CFSP) is the organised, agreed foreign policy of the European Union (EU) for mainly security and defence diplomacy and actions. https://eeas.europa.eu/topics/common-foreign-security-policy-cfsp_en
IoP Dimension: Governance IoP
LOST view: Semantic view
Interoperability saliency: The Security Policy ABB is salient for semantic interoperability because it provides a guiding framework to ensure the security of data and information according to interoperability principles as stated in the EIF recommendation n° 46 and 47: "Consider the specific security and privacy requirements and identify measures for the provision of each public service according to risk management plans."
Identifier: http://data.europa.eu/dr8/SecurityPolicyBusinessObject
eira:ID: ABB372
ABB name: eira:SecurityPolicyBusinessObject
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-16-01
Definition: Security Framework ABB is a Business Object that enables the protection of various aspects of data, information and knowledge assets and the organizational resources handling them.
Source: Inspired in the works by ISA2, and the EIF-related works
Source reference: https://ec.europa.eu/isa2/isa2_en
Example: The following implementation is an example of how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): The EU cybersecurity certification framework - The European Commission puts forward the creation of a EU certification framework for ICT security products in its 2017 proposal for a regulation. - On 13 September 2017 the Commission issued a proposal for a regulation on ENISA, the ""EU Cybersecurity Agency"", and on Information and Communication Technology cybersecurity certification (''Cybersecurity Act''). Certification plays a critical role in increasing trust and security in products and services that are crucial for the digital single market. At the moment, a number of different security certification schemes for ICT products exist in the EU. Without a common framework for EU-wide valid cybersecurity certificates, there is an increasing risk of fragmentation and barriers in the single market. The proposed certification framework will provide EU-wide certification schemes as a comprehensive set of rules, technical requirements, standards and procedures. This will be based on agreement at EU level for the evaluation of the security properties of a specific ICT-based product or service e.g. smart cards. The certification will attest that ICT products and services that have been certified in accordance with such a scheme comply with specified cybersecurity requirements. The resulting certificate will be recognized in all Member States, making it easier for businesses to trade across borders and for purchasers to understand the security features of the product or service. The schemes proposed in the future European framework will rely as much as possible on international standards as a way to avoid creating trade barriers and ensuring coherence with international initiatives."
IoP Dimension: Governance IoP
LOST view: Organisational view
Interoperability saliency: The Security Framework ABB is salient for legal and organizational interoperability due to it permits the establishment of security and privacy procedures and rules to determine the provision of public services. This framework will provide secure and trustworthy data exchange between public administrations and in interactions with citizens and businesses.
Identifier: http://data.europa.eu/dr8/SecurityFrameworkBusinessObject
eira:ID: ABB223
ABB name: eira:SecurityFrameworkBusinessObject
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2022-12-01
Definition: Legislation on Digital Public Services ABB is a Business formalising a set of rules and requirements concerning digital public services.
Source: Inspired on the content of the Digital Services Act package
Source reference: https://digital-strategy.ec.europa.eu/en/policies/digital-services-act-package
Example: The following implementation is an example of how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): The binding and non-binding legislation produced towards the Digital Single Market. https://www.consilium.europa.eu/en/policies/digital-single-market/), and any of the national efforts towards the alignment to the European Digital Strategy (e.g., DigitalES in Europe (https://www.digitales.es/en/digitales-in-europe/
Interoperability Dimension: Structural IoP
LOST view: Legal view
Interoperability Saliency: The Legislation on Digital Public Services ABB is salient for the governance, behavioural and structural interoperability because it sets rules that relate specifically to i) the reuse of solutions in the context of digital public services, ii) the exchange of digital data, information and knowledge, and iii) the collaboration amongst the public administrations' digital services.
Identifier: http://data.europa.eu/dr8/LegislationOnDigitalPublicServicesBusinessObject
ABB name: eira:LegislationOnDigitalPublicServicesBusinessObject
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/LegislationOnDigitalPublicServicesBusinessObject
Interoperability Layer: Legal
Definition: Data Quality is the state of qualitative or quantitative pieces of information.
Source: WikiPedia
Source reference: https://en.wikipedia.org/wiki/Data_quality
Additional information: Data quality refers to the accuracy, completeness, consistency, timeliness, and relevance of data. It is a crucial element or component of information within the European IT context, where data plays a significant role in various industries and sectors. In this context, data quality is of utmost importance as it directly impacts decision-making, business operations, regulatory compliance, and overall organizational performance.
Accuracy refers to the correctness and precision of data. High-quality data is free from errors, inconsistencies, and inaccuracies. It reflects the reality it represents and can be relied upon for analysis and decision-making. In the European IT context, accurate data is essential for ensuring compliance with regulations, such as the General Data Protection Regulation (GDPR), which requires organizations to maintain accurate and up-to-date personal data.
Completeness refers to the extent to which data captures all relevant information. Complete data includes all necessary attributes, fields, and values required for a specific purpose or analysis. In the European IT context, complete data is crucial for activities such as customer profiling, risk assessment, and reporting, as it ensures that all relevant information is considered and analyzed.
Consistency refers to the uniformity and coherence of data across different sources, systems, and time periods. Consistent data ensures that there are no contradictions or discrepancies when integrating or comparing data from various sources. In the European IT context, consistency is vital for data integration, data sharing, and data exchange between organizations, systems, and countries.
Timeliness refers to the availability of data when needed. Timely data is up-to-date and reflects the most recent information. In the European IT context, timely data is crucial for real-time decision-making, monitoring, and reporting. For example, financial institutions require timely data for accurate risk assessment and regulatory reporting.
Relevance refers to the suitability and applicability of data for a specific purpose or analysis. Relevant data is aligned with the objectives and requirements of the intended use. In the European IT context, relevant data ensures that organizations focus on collecting and analyzing the data that is necessary for their operations, compliance, and strategic decision-making.
In summary, data quality in the European IT context encompasses accuracy, completeness, consistency, timeliness, and relevance. It is essential for organizations to ensure that their data meets these criteria to enable effective decision-making, regulatory compliance, and overall operational excellence.
Example: Data Quality is a crucial element or component of information in various applications within the European IT context. Here are a few examples:
1. Customer Relationship Management (CRM) Systems: In CRM systems, data quality ensures that customer information is accurate, complete, and up-to-date. This includes validating customer contact details, eliminating duplicate records, and ensuring data consistency across different modules or databases. High data quality in CRM systems enables businesses to provide personalized and targeted marketing campaigns, improve customer service, and make informed business decisions.
2. Business Intelligence and Analytics: Data quality plays a vital role in business intelligence and analytics applications. It ensures that the data used for analysis is reliable, consistent, and accurate. This involves data cleansing, standardization, and validation processes to remove any inconsistencies, errors, or outliers. High data quality in these applications enables organizations to derive meaningful insights, make data-driven decisions, and identify trends or patterns that can drive business growth.
3. Regulatory Compliance: Data quality is essential for organizations operating within the European IT context to comply with various regulations such as the General Data Protection Regulation (GDPR). GDPR requires organizations to ensure the accuracy, integrity, and confidentiality of personal data. Data quality processes help in identifying and rectifying any inaccuracies or inconsistencies in personal data, ensuring compliance with GDPR and avoiding potential penalties.
4. E-commerce and Online Transactions: Data quality is critical in e-commerce applications to ensure smooth and secure online transactions. It involves validating customer payment information, verifying shipping addresses, and detecting fraudulent activities. High data quality in these applications helps in preventing errors, reducing transaction failures, and enhancing customer trust and satisfaction.
5. Supply Chain Management: In supply chain management, data quality is essential for accurate inventory management, demand forecasting, and logistics planning. It involves validating and cleansing data related to product codes, quantities, suppliers, and delivery schedules. High data quality in supply chain management applications enables organizations to optimize their operations, reduce costs, and improve customer service by ensuring timely and accurate deliveries.
Overall, data quality is a fundamental aspect of information management within the European IT context, enabling organizations to leverage accurate and reliable data for various applications, comply with regulations, and drive business success.
LOST view: OV-Functional Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/DataQualityBusinessObject
ABB name: egovera:DataQualityBusinessObject
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/egovera/DataQualityBusinessObject
Name: Data Quality Information
Interoperability Layer: Organisational
Specialises: http://data.europa.eu/dr8/InformationBusinessObject
Definition: Legislation Catalogue ABB is a Business Object creating an indexed inventory of legal documents with comprehensiveness and trustiness value.
Source: IATE
Source reference: http://iate.europa.eu/
Synonym: Official Journal
Additional information: DECISION (EU) 2015/2240 OF THE EUROPEAN PARLIAMENT AND OF THE COUNCIL of 25 November 2015 establishing a programme on interoperability solutions and common frameworks for European public administrations, businesses and citizens (ISA2 programme) as a means for modernising the public sector.
Example: The following implementation is an example of how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): EUR-Lex - It provides the official and most comprehensive access to EU legal documents. It is available in all of the EU’s 24 official languages and is updated daily. https://eur-lex.europa.eu/content/welcome/about.html
Interoperability Dimension: Structural IoP
LOST view: Legal view
Viewpoint: Key Interoperability Enablers viewpoint
Interoperability Saliency: The Legislation Catalogue ABB is a key interoperability enabler (*) for structural and governance interoperability enablers. It is salient for structural interoperability because it supports enabling sharing/provisioning and reusing/consumption of legislation on digital public services. The Legislation Catalogue ABB is also salient for the governance of interoperability because it compiles the legislation that needs to be discovered and applied for collaboration with other public administrations' digital public services, either because it is binding or because it is a source of strong recommendations.
Identifier: http://data.europa.eu/dr8/LegislationCatalogueBusinessObject
ABB name: eira:LegislationCatalogueBusinessObject
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/LegislationCatalogueBusinessObject
Interoperability Layer: Legal
Definition: Privacy Policy ABB is a Business Object that regulates the personal data of any customer, client or employee inforamtion.
Source: EU Data Protection
Source reference: https://commission.europa.eu/law/law-topic/data-protection_en
Example: The following implementation is an example of how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): Protection of individuals with regard to the processing of personal data - GDPR. https://eira-si.eu/privacy-policy/
IoP Dimension: Governance IoP
LOST view: Semantic view
Interoperability saliency: The Privacy Policy ABB is salient for semantic interoperability because it provides a guiding framework to ensure the privacy of data and information according to interoperability principles as stated in the EIF recommendation n° 46 and 47: "Consider the specific security and privacy requirements and identify measures for the provision of each public service according to risk management plans."
Identifier: http://data.europa.eu/dr8/PrivacyPolicyBusinessObject
eira:ID: ABB373
ABB name: eira:PrivacyPolicyBusinessObject
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-16-01
Definition: Digital-ready Policymaking ABB is a Business Process consisting in formulating digital-ready policies and legislation by considering digital aspects from the start of the policy cycle to ensure that they are ready for the digital age, future-proof and interoperable.
Source: Joinup (Digital Ready Policies)
Source reference: https://joinup.ec.europa.eu/collection/better-legislation-smoother-implementation/digital-ready-policymaking
Synonym: Policy Cycle
Additional information: Policies (and legislative acts) are digital-ready if they enable smooth and digital by default policy implementation and foster digital transformation through best use of digital technologies and data. This implies that policymakers work in a multidisciplinary team and consider the following digital-ready components: 1. user-centric processes ready for automation, 2. alignment with digital policies (for example on accessibility, eID...), 3. the once-only principle and the reuse of data, 4. the evolving ICT landscape, 5. innovation and digital technologies, and 6. digital-ready drafting.
Example: The following implementation is an example of how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): Performance-based Full Policy Cycle for the Digital Single Market (http://www.europarl.europa.eu/RegData/etudes/etudes/join/2013/507457/IPOL-IMCO_ET(2013)507457_EN.pdf). The key features of a performance-based full policy cycle are a clear articulation of policy objectives, the identification and use of quantitative indicators of expected short-term and longer-term policy impacts, the identification of synergies between policies, a much greater use of quantitative data in ex-ante impact assessments, the implementation of robust, data-based, independent ex post assessments of the performance of policies relative to their expected impacts and a wide dissemination of lessons learned in such ex-post performance assessments
eira:iopDimension: Governance IoP
LOST view: Legal view
Viewpoint: Interoperability Governance viewpoint
eira:iopSaliency: The Public Policy Cycle ABB is salient for the governance interoperability because it impacts on the design and formulation of public policies, which are implemented through legal acts. Also, the ABB also is salient for the legal interoperability due to it establis the legal actions and directives for public administration services as the case of interoperability principles need to be taken into account during the whole public policy cycle.
Identifier: http://data.europa.eu/dr8/PublicPolicyCycleBusinessProcess
ABB name: eira:PublicPolicyCycleBusinessProcess
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-10-1
dct:identifier: http://data.europa.eu/dr8/PublicPolicyCycleBusinessProcess
Definition: The Data Consumer ABB is a Business Role that is responsible for using data provided by other roles or systems, either by consuming, analyzing, interpreting, or presenting data. Data consumers may also be accountable for the appropriate and ethical use of the data they consume.
Source: DAMA-DMBOK2
Source reference: https://datacrossroads.nl/2019/12/13/data-management-and-data-governance-104-the-yin-force-of-data-governance-part-2-roles/
Additional information: The role of Data Consumer is not limited to the final use or presentation of data, but also includes the consumption, analysis, or interpretation of data from other roles or systems. For example, a business user who queries data from a data warehouse or a data lake is a data consumer, as well as a data scientist who applies machine learning algorithms or statistical models to data. Data consumers should ensure that the data they use is appropriate and ethical for their purposes, and that they comply with the data governance policies and regulations that apply to their data domain. Data consumers should also verify and validate the quality, security, and availability of the data they use, and report any issues or errors that may affect its reliability or accuracy. Data consumers should collaborate with data providers to provide feedback and suggestions for data improvement, and to express their data needs and expectations. Data consumers should also document and communicate the results, insights, or recommendations derived from their data analysis or interpretation.
Example: Examples of data consumers are business users, decision makers, data scientists, and data journalists.
LOST view: OV-Data Spaces
Identifier: http://data.europa.eu/dr8/DataConsumerBusinessRole
ABB name: egovera:DataConsumerBusinessRole
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-07-10
dct:identifier: http://data.europa.eu/dr8/DataConsumerBusinessRole
Definition: An Information Architect is responsible for designing and organizing information structures in a way that makes them understandable, accessible, and user-friendly. They analyze and understand user behavior, needs, and motivations through various qualitative and quantitative methods. Their role involves creating information systems like website navigation, database systems, and data maps, among others, to help users find the information they need seamlessly. They work closely with designers, developers, and stakeholders to create effective digital spaces that enhance user experience.
Source: EIRA team
Additional information: An Information Architect (IA) is a professional who organizes, labels, and structures information in a logical and user-friendly manner to help users understand and navigate a system effectively. This role is crucial in the design and development of websites, apps, and other digital platforms where users need to find and interact with information efficiently.
The primary responsibility of an Information Architect is to create intuitive and coherent structures for complex systems, ensuring that the end-users can easily find what they are looking for. This involves understanding the user's needs and business goals, conducting user and market research, creating user personas, and mapping out user journeys.
The IA then uses this information to develop information structures and navigation paths, often represented as site maps, wireframes, and flow diagrams. They also design metadata frameworks and search systems to enhance findability and usability.
In addition to this, Information Architects often work closely with other professionals such as User Experience (UX) Designers, User Interface (UI) Designers, Content Strategists, and Developers. They participate in usability testing, analyze user feedback and site metrics, and make necessary adjustments to the information architecture.
Furthermore, Information Architects play a key role in content management. They help in organizing and categorizing content in a way that makes sense to the users, and they often establish guidelines for content creation to maintain consistency and coherence across the system.
Overall, the role of an Information Architect is to create a seamless, user-centered design that makes complex systems easy to understand and navigate, ultimately enhancing user satisfaction and engagement.
Example: 1. Website Designer: An Information Architect in the role of a website designer would be responsible for organizing the content and flow of a website. They would determine the best way to present information so that users can easily find what they're looking for. This could involve creating site maps, wireframes, and user journeys.
2. App Developer: In the role of an app developer, an Information Architect would design the user interface and experience of a mobile application. They would decide how to structure the app's features and content in a way that is intuitive and user-friendly.
3. Database Administrator: As a database administrator, an Information Architect would design and manage the organization's data architecture. They would determine how data is stored, organized, and accessed to ensure it meets the needs of the organization.
4. UX Designer: In this role, an Information Architect would focus on the user experience of a product or service. They would conduct user research, create user personas, and design the interaction and navigation structure to ensure a positive user experience.
5. Content Strategist: An Information Architect in the role of a content strategist would be responsible for organizing and structuring the content of a website or application. They would determine what content is needed, how it should be organized, and how users will interact with it.
6. SEO Specialist: As an SEO specialist, an Information Architect would design the website or application structure to be search engine friendly. They would ensure that the content is easily discoverable and understandable by search engines, which can improve the site's search engine rankings.
7. Systems Analyst: In this role, an Information Architect would analyze the organization's IT systems and processes. They would design solutions to improve the efficiency and effectiveness of these systems, ensuring that they meet the organization's business needs.
LOST view: [A] How to read the model
Identifier: http://data.europa.eu/dr8/egovera/InformationArchitectBusinessRole
ABB name: egovera:InformationArchitectBusinessRole
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-18
dct:identifier: http://data.europa.eu/dr8/egovera/InformationArchitectBusinessRole
dct:title: Information Architect Business-role
Definition: The Data Provider ABB is a Business Role that is responsible for providing data to other roles or systems, either by producing, collecting, transforming, or delivering data. Data providers may also be accountable for the quality, security, and availability of the data they provide.
Source: DAMA-DMBOK2
Source reference: https://datacrossroads.nl/2019/12/13/data-management-and-data-governance-104-the-yin-force-of-data-governance-part-2-roles/
Additional information: The role of Data Provider is not limited to the initial creation or collection of data, but also includes the transformation or delivery of data to other roles or systems. For example, a data engineer who extracts, transforms, and loads data from various sources into a data warehouse is a data provider, as well as a data analyst who prepares and publishes data reports or dashboards. Data providers should ensure that the data they provide meets the quality, security, and availability requirements defined by the data owners and the data governance policies. Data providers should also document and communicate the metadata, lineage, and provenance of the data they provide, as well as any issues or limitations that may affect its use. Data providers should collaborate with data consumers to understand their data needs and expectations, and provide feedback and suggestions for data improvement.
Example: Examples of data providers are data entry clerks, data engineers, data analysts, and data publishers.
LOST view: OV-Data Spaces
Identifier: http://data.europa.eu/dr8/egovera/DataProviderBusinessRole
ABB name: egovera:DataProviderBusinessRole
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-07-10
dct:identifier: http://data.europa.eu/dr8/egovera/DataOwnerBusinessRole
Definition: A Software Architect is a technology professional who designs and manages the structure of software systems. They are responsible for creating the fundamental architecture that underpins a software program, ensuring it meets the needs of users and business requirements. Their role involves making high-level design choices, dictating technical standards, including software coding standards, tools, and platforms. They often work closely with stakeholders and other IT members to guide the software project from its conceptualization to its final product, making sure it's scalable, maintainable, and high-performing.
Source: EIRA team
Additional information: A Software Architect is a key role in the field of software development. This individual is responsible for making high-level design choices and for dictating technical standards, including software coding standards, tools, and platforms. They are involved in all stages of the software development life cycle, from initial concept, through design, development, testing, and deployment.
The Software Architect's role is multifaceted. They are responsible for understanding the business requirements and translating them into a software solution. They must have a deep understanding of the system being developed and be able to make decisions about the most suitable architecture and technologies to use. They must also be able to foresee potential problems and design the system in a way that avoids them.
In addition, the Software Architect is responsible for ensuring that the system is scalable, reliable, and efficient. They must consider factors such as performance, security, and maintainability. They also need to ensure that the architecture is flexible enough to accommodate future changes and enhancements.
The Software Architect often acts as a technical leader within the development team. They provide guidance and support to the developers, helping them to understand the architecture and to implement it correctly. They also liaise with other stakeholders, such as project managers and business analysts, to ensure that the system meets the business needs.
Furthermore, the Software Architect is responsible for creating and maintaining documentation of the system architecture. This includes diagrams and descriptions of the system's components, their relationships, and their interactions. This documentation is crucial for understanding the system, for maintaining it, and for making future enhancements.
In summary, the Software Architect plays a crucial role in software development. They are responsible for designing the system's architecture, for making key technical decisions, for guiding the development team, and for ensuring that the system meets the business requirements and is of high quality.
Example: 1. Enterprise Software Architect: This role involves designing and implementing software architecture for an entire organization. The enterprise software architect works closely with various departments to understand their needs and ensure the software solutions meet those needs. They also oversee the integration of different software systems across the organization.
2. Solution Software Architect: This role focuses on designing and implementing software solutions for specific business problems. They work closely with business analysts and project managers to understand the requirements and constraints of the solution. They then design the software architecture and oversee its implementation.
3. Application Software Architect: This role involves designing the architecture for specific software applications. The application software architect works closely with software developers and engineers to ensure the application is designed and built according to the architectural plan.
4. System Software Architect: This role involves designing the architecture for system software such as operating systems, database systems, and middleware. They work closely with system engineers and developers to ensure the system software is designed and built according to the architectural plan.
5. Cloud Software Architect: This role involves designing and implementing software architecture for cloud-based systems. The cloud software architect works closely with cloud engineers and developers to ensure the cloud systems are designed and built according to the architectural plan.
6. Data Architect: This role involves designing and implementing data architecture, including data models, database architecture, and data warehousing solutions. They work closely with data engineers and analysts to ensure the data architecture supports the organization's data needs.
7. Software Architect Consultant: This role involves providing expert advice and guidance on software architecture to organizations. The software architect consultant may be hired to design a new software architecture, review an existing architecture, or provide training on software architecture best practices.
LOST view: [A] How to read the model
Identifier: http://data.europa.eu/dr8/egovera/SoftwareArchitectBusinessRole
ABB name: egovera:SoftwareArchitectBusinessRole
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-18
dct:identifier: http://data.europa.eu/dr8/egovera/SoftwareArchitectBusinessRole
dct:title: Software Architect Business-role
Definition: A Solution Architect is a professional who is responsible for designing and managing the implementation of technology solutions to meet specific business needs. They work closely with the business team to understand their requirements and challenges, and then develop a technological solution that addresses those needs. This can involve selecting appropriate technologies, designing system architecture, overseeing development and implementation processes, and ensuring the solution is scalable and sustainable. They also often act as a bridge between technical and non-technical stakeholders, ensuring clear communication and understanding across all parties.
Source: EIRA team
Additional information: A Solution Architect is a professional who is responsible for designing and managing the solution engineering in relation to specific business problems. They are a key part of the software development process, bridging the gap between the needs of the business and the technical capabilities of the IT team.
The role of a Solution Architect involves understanding the company's business strategy and identifying the technology systems architecture that will support this strategy. They work closely with both the executive team and the IT team to ensure that the company's technology strategy aligns with its business goals.
Their responsibilities include designing and leading the implementation of a solutions architecture across a range of new and existing technologies, ensuring that the solution aligns with the enterprise architecture of the organization. They also provide technical leadership and support during the sales process, including working with the sales team to propose solutions that meet the needs of potential customers.
Solution Architects are also responsible for conducting research on existing systems and devising solutions that work seamlessly with these systems. They often work with a variety of technologies and, therefore, need to be comfortable with different programming languages and computer hardware.
They also need to be able to communicate effectively with both technical and non-technical stakeholders. This includes explaining complex concepts in a way that is easy for non-technical people to understand, as well as being able to translate business needs into technical requirements for the IT team.
In addition, Solution Architects often play a role in risk management, as they need to identify and mitigate potential risks associated with the proposed solution. This can include anything from security risks to the risk of the solution not being scalable enough to support future growth.
Overall, the role of a Solution Architect is a complex and multifaceted one, requiring a combination of technical expertise, business acumen, and excellent communication skills.
Example: 1. Cloud Solution Architect: This role involves designing and managing cloud-based systems and services for a company. The architect may work with Amazon Web Services, Microsoft Azure, or Google Cloud Platform. They are responsible for understanding the technical requirements of the company and developing a cloud strategy that meets those needs.
2. Enterprise Solution Architect: This role is responsible for overseeing the technological needs of a large organization. They work to align the company's strategic goals with its technology strategy. They often work with various departments within the company to understand their needs and develop solutions to meet those needs.
3. Software Solution Architect: This role involves designing and managing software systems. They work closely with software developers and engineers to ensure that the software being developed meets the needs of the company. They are also responsible for troubleshooting any issues that may arise during the development process.
4. Data Solution Architect: This role involves designing and managing data systems for a company. They are responsible for understanding the company's data needs and developing a strategy to meet those needs. This may involve designing databases, developing data models, and implementing data governance policies.
5. Infrastructure Solution Architect: This role involves designing and managing the physical and virtual resources that support a company's IT systems. This includes servers, storage, networks, and virtualization technologies. They are responsible for ensuring that the infrastructure is scalable, reliable, and secure.
6. Security Solution Architect: This role involves designing and managing the security systems for a company. They are responsible for understanding the company's security needs and developing a strategy to meet those needs. This may involve designing firewalls, developing security policies, and implementing security measures.
LOST view: [A] How to read the model
Identifier: http://data.europa.eu/dr8/egovera/SolutionArchitectBusinessRole
ABB name: egovera:SolutionArchitectBusinessRole
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-18
dct:identifier: http://data.europa.eu/dr8/egovera/SolutionArchitectBusinessRole
dct:title: Solution Architect Business-role
Definition: Digital Public Service Provider ABB is a Business Role representing the entity that offer or deliver public services using digital channels and technologies. Digital public service providers aim to provide efficient and accessible services to citizens and businesses by leveraging the power of digital technology.
Source: Inspired on the information available in Digital Public Services in the Digital Economy and Society Index
Source reference: https://digital-strategy.ec.europa.eu/en/policies/desi-digital-public-services
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): The Spanish Tax Agency is responsible for providing Digital Public Services on TAX payment. https://sede.agenciatributaria.gob.es/Sede/en_gb/iva.html
Interoperability Dimension: Structural IoP
LOST view: Organisational view
Viewpoint: Interoperability Privacy viewpoint
Interoperability Saliency: The Digital Public Service Provider ABB is salient for organizational and semantic interoperability because it offers (i) mechanisms to exchange information transparently; (ii) manage the information with needed security and trust; (iii) combine and harmonise information coming from multiple data stores to give service to the different agents (or stakeholders)
Identifier: http://data.europa.eu/dr8/DigitalPublicServiceProviderBusinessRole
ABB name: eira:DigitalPublicServiceProviderBusinessRole
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/DigitalPublicServiceProviderBusinessRole
Interoperability Layer: Organisational
Definition: Data Holder ABB is a Business Role being assigned to a legal person, including public sector bodies and international organisations, or a natural person who is not a data subject with respect to the specific data in question, which, in accordance with applicable Union or national law, has the right to grant access to or to share certain personal data or non-personal data.
Source: Data Governance Act (DGA)
Source reference: http://data.europa.eu/eli/reg/2022/868/oj
Additional information: Data owners may not work with their data every day, but are responsible for overseeing and protecting a data domain. In the context of the GDPR, data owners are accountable for the quality, integrity, and protection of their data space. In SiMPL (https://digital-strategy.ec.europa.eu/en/news/simpl-cloud-edge-federations-and-data-spaces-made-simple), the data owner is the legal entity that has sovereignty over the data, usually the creator of the data or the one who executes control over the data. See SiMPL requirements and architecture vision document. The Data Governance Act does not define the concept Data Owner, but intrinsically this role can be assigned also to the Data Holder, since "holding" usually entails "controlling".
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): In the GDPR, "controller", or "processor" on behalf of the "controller" are examples of the data owner role defined for this ABB. See GDPR https://eur-lex.europa.eu/legal-content/EN/TXT/PDF/?uri=CELEX:32016R0679&from=EN , Article 4, Definitions.
Interoperability Dimension: Governance IoP
LOST view: Organisational view
Viewpoint: Interoperability Privacy viewpoint
Interoperability Saliency: The Data Holder ABB is salient for organizational interoperability because it plays a pivotal role in facilitating data access and sharing within the framework of the Data Governance Act. This designation applies to both legal entities, such as public sector bodies and international organizations, and individuals authorized by applicable Union or national law to grant access to specific personal or non-personal data. By delineating responsibilities and ensuring compliance with regulatory standards, the identification of Data Holders fosters transparency, accountability, and alignment with data governance policies, ultimately promoting seamless data interoperability within organizational contexts
Identifier: http://data.europa.eu/dr8/DataHolderBusinessRole
ABB name: eira:DataHolderBusinessRole
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-06-05
Identifier: http://data.europa.eu/dr8/DataHolderBusinessRole
Interoperability Layer: Organisational
Definition: Data Owner ABB is a Business Role being assigned to individual who creates or generates the data or the entity that has legal ownership or control over the data. In other cases, a data owner might be the individual or entity that is responsible for managing or overseeing the use of the data. It can be mapped with Data Controller from the GDPR, under the European General Data Protection Regulation (GDPR), a "data controller" is defined as the entity that determines the purposes, conditions, and means of the processing of personal data. This means that the data controller is the entity that decides why and how personal data is processed.
Source: GDPR
Source reference: https://eur-lex.europa.eu/eli/reg/2016/679/oj
Synonym: Data Holder (DGA), Data Creator (SiMPL)
Additional information: Data owners may not work with their data every day, but are responsible for overseeing and protecting a data domain. In the context of the GDPR, data owners are accountable for the quality, integrity, and protection of their data space. In SiMPL (https://digital-strategy.ec.europa.eu/en/news/simpl-cloud-edge-federations-and-data-spaces-made-simple), the data owner is the legal entity that has sovereignty over the data, usually the creator of the data or the one who executes control over the data. See SiMPL requirements and architecture vision document. The Data Governance Act does not define the concept Data Owner, but intrinsically this role can be assigned also to the Data Holder, since "holding" usually entails "controlling".
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): In the GDPR, "controller", or "processor" on behalf of the "controller" are examples of the data owner role defined for this ABB. See GDPR https://eur-lex.europa.eu/legal-content/EN/TXT/PDF/?uri=CELEX:32016R0679&from=EN , Article 4, Definitions.
eira:iopDimension: Behavioral IoP
LOST view: OV-Data Spaces
Viewpoint: Interoperability Privacy viewpoint
eira:iopSaliency: The Data Owner ABB is salient for organisational interoperability because it is responsible for the management of the data generated or consumed by the public service. The identification of Data Owners, as stated in the GDPR, is important for accountability since it identifies a person/team responsible to control the compliance of data, and for the definition of policies and standards for the alignment of public service data to GDPR.
Identifier: http://data.europa.eu/dr8/DataOwnerBusinessRole
ABB name: eira:DataOwnerBusinessRole
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2022-01-13
dct:identifier: http://data.europa.eu/dr8/DataOwnerBusinessRole
Definition: Agent ABB is a Business Role defined as an Entity that is able to carry out action.
Source: SEMIC-CPV or SEMIC-CCCEV
Source reference: https://semiceu.github.io/Core-Person-Vocabulary/releases/2.00/#Agent
Example: The following implementation is an example of how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): foaf:Agent An agent (eg. person, group, software or physical artifact). (http://xmlns.com/foaf/0.1/#term_Agent)
Interoperability Dimension: Structural IoP
LOST view: Organisational view
Interoperability Saliency: The Agent ABB is salient for organizational and behavioural interoperability because it permits the identification of procedures and business rules related to specific organizations, individuals or public services that facilitates the exchange of data, information and knowledge between digital public services.
Identifier: http://data.europa.eu/dr8/AgentBusinessRole
ABB name: eira:AgentBusinessRole
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/AgentBusinessRole
Interoperability Layer: Organisational
Definition: A Public Policy Officer is responsible for analyzing, developing, and implementing policies related to public issues for an organization or government entity. They conduct research, gather data, and monitor legislation to understand its impact on their organization. They also liaise with stakeholders, including government officials, to advocate for their organization's interests. Their role may also involve educating the public or their organization about relevant policies and legislation.
Source: EIRA team
Additional information: A Public Policy Officer, also known as a Policy Analyst, is a professional who is responsible for researching, analyzing, and interpreting public policies, laws, rules, and regulations. They work in various sectors such as government agencies, non-profit organizations, and private companies, where they play a crucial role in shaping and implementing policies that align with the organization's goals and objectives.
The primary responsibilities of a Public Policy Officer include:
1. Research and Analysis: They conduct extensive research on various public policy issues, analyze the data, and interpret the findings to understand the impact of these policies on the public and the organization. They use this information to make recommendations for policy improvements.
2. Policy Development: Based on their research and analysis, Public Policy Officers help in the development and implementation of new policies. They draft policy proposals, prepare reports, and present their findings to decision-makers.
3. Advocacy: They advocate for policies that align with the organization's mission and goals. This may involve lobbying with government officials, participating in public debates, or collaborating with other organizations to promote certain policies.
4. Stakeholder Engagement: Public Policy Officers often act as a liaison between the organization and its stakeholders, which may include government officials, community members, and other organizations. They communicate the organization's policy positions and gather feedback from stakeholders.
5. Monitoring and Evaluation: They monitor the implementation of policies and evaluate their effectiveness. They use various evaluation methods to assess the impact of policies and make necessary adjustments.
6. Compliance: They ensure that the organization's policies and practices comply with relevant laws, regulations, and standards. They also keep up-to-date with changes in legislation that may affect the organization.
In terms of qualifications, a Public Policy Officer typically holds a bachelor's degree in public policy, political science, law, or a related field. Some positions may require a master's degree or significant work experience in a related field. Key skills for this role include strong research and analytical skills, excellent communication skills, a good understanding of the policy-making process, and the ability to work effectively with a wide range of stakeholders.
Example: 1. Public Policy Officer at a Non-Profit Organization: In this role, the officer is responsible for researching, analyzing, and interpreting public policies related to the organization's mission. They may also advocate for changes in policy, develop strategies to influence policy decisions, and communicate with stakeholders about policy issues.
2. Public Policy Officer in a Government Agency: Here, the officer is tasked with developing, implementing, and evaluating policies that align with the agency's goals. They may also be responsible for advising senior officials on policy matters, coordinating with other agencies, and ensuring compliance with relevant laws and regulations.
3. Public Policy Officer in a Healthcare Institution: In this role, the officer might focus on healthcare policies, analyzing their impact on the institution and its patients. They may also work on policy advocacy, stakeholder engagement, and policy-related communication.
4. Public Policy Officer in an Educational Institution: This officer would be responsible for understanding and interpreting education policies, advising the institution on policy matters, and advocating for policy changes that could benefit the institution and its students.
5. Public Policy Officer in a Corporate Setting: In a corporate environment, the officer might focus on policies related to the industry in which the corporation operates. They would analyze the impact of these policies on the corporation, advise on policy compliance, and advocate for policy changes that could benefit the corporation.
6. Public Policy Officer in an International Organization: This officer would work on policies related to the organization's international mission. They might analyze global policy trends, advise the organization on policy matters, and develop strategies to influence international policy decisions.
7. Public Policy Officer in a Research Institution: In this role, the officer would use their research skills to analyze and interpret policies related to the institution's research areas. They might also communicate with stakeholders about policy issues and advocate for policy changes that could benefit the institution's research.
LOST view: [A] How to read the model
Identifier: http://data.europa.eu/dr8/egovera/PublicPolicyOfficerBusinessRole
ABB name: egovera:PublicPolicyOfficerBusinessRole
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-18
dct:identifier: http://data.europa.eu/dr8/egovera/PublicPolicyOfficerBusinessRole
dct:title: Public Policy Officer Business-role
Definition: Digital Public Service Consumer ABB is a Business Role representing the entities able to access and consume public services provided by a public authority.
Source: Inspired on the information available in Digital Public Services in the Digital Economy and Society Index
Source reference: https://digital-strategy.ec.europa.eu/en/policies/desi-digital-public-services
Example: The following implementation is an example of how this specific Architecture Building Blocks (ABB) can be instantiated as a Solution Building Block (SBB): UK Local Goverment- Transforming public services, using technology and digital tools and approaches- Case Studies (https://www.local.gov.uk/our-support/efficiency-and-productivity/transforming-public-services-using-technology-and-digital) or UNDP- COVID 19 Open Source Digital Toolkit (https://www.undp.org/sgtechcentre/digital-tools-covid-19)
Interoperability Dimension: Structural IoP
LOST view: Organisational view
Viewpoint: Interoperability Privacy viewpoint
Interoperability Saliency: The Digital Public Service Consumer ABB is salient for organizational, semantic and technical interoperability due to it (i) provides digital business rules to consume data; (ii) enables a common understanding of the data to be exchanged with the public authority; and (iii) establish the needed mechanism to consume the information automatically.
Identifier: http://data.europa.eu/dr8/DigitalPublicServiceConsumerBusinessRole
ABB name: eira:DigitalPublicServiceConsumerBusinessRole
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/DigitalPublicServiceConsumerBusinessRole
Interoperability Layer: Organisational
Definition: A Governance Analyst is a professional who evaluates, monitors, and ensures that an organization's operations and procedures comply with government regulations and industry standards. They are responsible for developing and implementing governance frameworks, policies, and procedures, and for providing advice on governance-related issues. They also conduct regular audits and risk assessments to identify potential areas of non-compliance or improvement. Additionally, they may be involved in training staff on compliance matters and in preparing reports for senior management and regulatory bodies.
Source: EIRA team
Additional information: A Governance Analyst is a professional who is responsible for ensuring that an organization is operating in compliance with established internal and external policies, regulations, and laws. This role is typically found within large corporations, government agencies, and non-profit organizations.
The primary duties of a Governance Analyst include reviewing and analyzing an organization's operations and procedures to ensure compliance with governance standards. They are responsible for identifying any areas of non-compliance and recommending corrective actions. They also assist in the development and implementation of governance policies and procedures.
In addition, Governance Analysts often conduct internal audits to verify compliance and identify areas of risk. They may also be involved in training staff on governance issues and procedures. They are expected to stay updated on changes in relevant laws and regulations and to communicate these changes to the appropriate personnel within the organization.
Furthermore, Governance Analysts may be involved in strategic planning, particularly in relation to risk management. They may be asked to provide input on the potential governance implications of proposed changes to the organization's operations or structure.
In terms of skills, a Governance Analyst needs to have strong analytical abilities, as well as excellent communication and interpersonal skills. They need to be detail-oriented and have a good understanding of the organization's operations and the relevant laws and regulations. They also need to have good problem-solving skills and the ability to work independently.
In terms of qualifications, a Governance Analyst typically needs to have a bachelor's degree in a related field, such as business administration, finance, or law. Some positions may require a master's degree or professional certification. They also typically need to have several years of experience in a related role.
Example: 1. Governance Analyst at a Financial Institution: In this role, the analyst is responsible for ensuring that the organization complies with all relevant financial regulations and laws. They may review and analyze financial transactions, monitor compliance with internal policies, and assist in the development of new governance strategies.
2. IT Governance Analyst: This professional is responsible for overseeing the IT governance within an organization. They ensure that IT systems and processes align with the organization's overall business strategy. They may also be involved in risk management, compliance, and strategic planning.
3. Corporate Governance Analyst: In this role, the analyst is responsible for monitoring and analyzing a company's governance policies and procedures. They may also be involved in the development and implementation of corporate governance guidelines, and may work closely with the board of directors and senior management.
4. Environmental Governance Analyst: This analyst works on environmental policies and regulations. They ensure that the organization is in compliance with environmental laws and standards. They may also be involved in the development of sustainability strategies and initiatives.
5. Data Governance Analyst: This role involves managing and ensuring the quality, security, and privacy of data in an organization. The analyst sets data standards and policies, and works with different departments to ensure compliance.
6. Health Governance Analyst: In a healthcare setting, this analyst ensures that the organization complies with healthcare laws, regulations, and standards. They may also be involved in policy development, risk management, and strategic planning.
7. Governance Risk Compliance Analyst: This role involves identifying and assessing potential risks that could affect the organization's governance and compliance. They develop and implement risk management strategies, and ensure the organization is in compliance with all relevant laws and regulations.
LOST view: [A] How to read the model
Identifier: http://data.europa.eu/dr8/egovera/GovernanceAnalystBusinessRole
ABB name: egovera:GovernanceAnalystBusinessRole
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-18
dct:identifier: http://data.europa.eu/dr8/egovera/GovernanceAnalystBusinessRole
dct:title: Governance Analyst Business-role
Definition: An Infrastructure Architect is a professional responsible for designing, implementing, and managing the IT infrastructure of an organization. This includes the development and maintenance of networks, servers, software, and hardware systems to ensure optimal performance and security. They also work closely with other IT professionals to align the infrastructure with the business goals, assess system requirements, and troubleshoot any issues that arise. Their role is crucial in the strategic planning of an organization's IT framework, considering factors such as cost efficiency, scalability, and technological advancements.
Source: EIRA team
Additional information: An Infrastructure Architect is a key role in the field of information technology. This professional is responsible for designing, implementing, and managing the infrastructure of an organization's IT landscape. The infrastructure typically includes hardware, software, networks, data centers, and various services.
The Infrastructure Architect's primary responsibility is to ensure that all aspects of an organization's technical systems align with its business goals. They are involved in every phase of a system's lifecycle, from initial design through implementation, maintenance, and eventual retirement or replacement.
The Infrastructure Architect's role involves a wide range of tasks. They must analyze the current state of the organization's infrastructure, identify weaknesses or inefficiencies, and propose improvements. They also need to stay current with the latest technologies and trends in IT infrastructure, and determine how these could be applied to benefit the organization.
In addition, the Infrastructure Architect must work closely with other IT professionals, such as network engineers, system administrators, and software developers, to ensure that all components of the infrastructure work together seamlessly. They also need to coordinate with business leaders and stakeholders to understand their needs and ensure that the infrastructure supports them.
The Infrastructure Architect is also responsible for creating and maintaining documentation of the infrastructure, including diagrams, specifications, and policies. They may also be involved in training staff on the use and maintenance of the infrastructure.
In terms of skills, an Infrastructure Architect needs a deep understanding of various technologies, including servers, storage systems, networks, and software applications. They also need strong problem-solving skills, the ability to think strategically, and excellent communication skills. A degree in computer science or a related field, as well as several years of experience in IT, are typically required for this role.
In summary, the Infrastructure Architect plays a crucial role in shaping and maintaining the IT backbone of an organization, ensuring that it is robust, efficient, and aligned with the organization's business objectives.
Example: 1. Cloud Infrastructure Architect: This role involves designing and managing cloud-based systems and services for a company. This includes selecting appropriate cloud services, setting up virtual servers and networks, and ensuring the security and efficiency of cloud infrastructure.
2. Network Infrastructure Architect: This professional is responsible for designing and implementing computer networks within an organization. They determine the layout of cables, network devices, and servers, and they ensure that these elements are secure and efficient.
3. IT Infrastructure Architect: This role involves planning and designing the IT infrastructure that supports an organization's business operations. This includes determining the hardware, software, and network resources needed, as well as overseeing the installation and maintenance of these systems.
4. Enterprise Infrastructure Architect: This role involves designing and implementing IT solutions that support the strategic objectives of a large organization. They work closely with other IT professionals and business leaders to understand the organization's needs and to ensure that the IT infrastructure meets these needs.
5. Data Center Infrastructure Architect: This professional is responsible for designing and managing the physical and virtual infrastructure of a data center. This includes servers, storage systems, network devices, and security systems.
6. Solutions Infrastructure Architect: This role involves designing and implementing IT solutions that meet the specific needs of a business. This could involve integrating different systems, designing custom software, or implementing new technologies.
7. Security Infrastructure Architect: This role involves designing and implementing security systems to protect an organization's IT infrastructure. This includes firewalls, intrusion detection systems, encryption technologies, and other security measures.
LOST view: [A] How to read the model
Identifier: http://data.europa.eu/dr8/egovera/InfrastructureArchitectBusinessRole
ABB name: egovera:InfrastructureArchitectBusinessRole
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-18
dct:identifier: http://data.europa.eu/dr8/egovera/InfrastructureArchitectBusinessRole
dct:title: Infrastructure Architect Business-role
Definition: This IT concept refers to the process of evaluating the economic value of goods that are declared for importation. It involves the use of software systems and algorithms to calculate the value of imported goods based on various factors such as the cost of the goods, the cost of transportation, insurance, and any other costs associated with the importation process.
Source: World Customs Organization
Source reference: http://www.wcoomd.org/en/topics/valuation/instrument-and-tools/val-goods.aspx
Additional information: The determination of the economic value of goods declared for importation is a critical aspect of customs operations. It ensures that the correct amount of import duties and taxes are levied on the goods. This process is guided by the principles of the World Trade Organization's Agreement on Customs Valuation, which stipulates that the valuation of goods for customs purposes should be based on the actual price of the goods. IT systems play a crucial role in this process, enabling customs authorities to accurately and efficiently calculate the value of imported goods.
Example: An example of this concept in application is the use of a customs management system by a customs authority. When goods are declared for importation, the system will automatically calculate the value of the goods based on the information provided in the declaration. This includes the price of the goods, the cost of transportation and insurance, and any other costs associated with the importation process. The system will then determine the amount of import duties and taxes that should be levied on the goods.
LOST view: OV-Customs Functional Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/DeterminationOfTheEconomicValueOfGoodsDeclaredForImportationBusinessService
EIRA traceability: eira:DigitalPublicBusinessService
ABB name: egovera:DeterminationOfTheEconomicValueOfGoodsDeclaredForImportationBusinessService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-08
dct:identifier: http://data.europa.eu/dr8/egovera/DeterminationOfTheEconomicValueOfGoodsDeclaredForImportationBusinessService
dct:title: Determination of the economic value of goods declared for importation Digital Public Service
Definition: Laboratories Registry Management is an IT concept that involves the use of software or systems to manage, track, and organize laboratory data and resources. It includes the management of laboratory equipment, samples, results, personnel, and other related data.
Source: Techopedia
Source reference: https://www.techopedia.com/definition/24835/registry-management
Additional information: Laboratories Registry Management is a crucial aspect of laboratory operations, especially in large-scale or high-throughput laboratories. It involves the use of IT systems to manage and track laboratory resources, including equipment, samples, results, and personnel. These systems can help to improve efficiency, reduce errors, and ensure compliance with regulatory standards. They can also facilitate data analysis and reporting, and support decision-making processes. The management system can be a standalone application or integrated with other laboratory information systems. It can also be cloud-based or installed on-premises, depending on the needs and preferences of the laboratory.
Example: Examples of Laboratories Registry Management applications include LabWare LIMS (Laboratory Information Management System), which is a comprehensive solution for managing laboratory data and resources; LabVantage, a web-based system for managing laboratory workflows and data; and LabCollector, a modular software tool for managing laboratory samples and equipment. These systems can be used in a variety of laboratory settings, including research, clinical, and industrial laboratories.
LOST view: TVA-Customs Data Management Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/LaboratoriesRegistryManagementBusinessService
EIRA traceability: eira:DigitalPublicBusinessService
ABB name: egovera:LaboratoriesRegistryManagementBusinessService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-08
dct:identifier: http://data.europa.eu/dr8/egovera/LaboratoriesRegistryManagementBusinessService
dct:title: Laboratories registry management Digital Public Service
Definition: eInvoicing enables public organisations to issue, transmit and deliver electronic invoice documents in a structured data format to its providers/suppliers, according to European standards.
Source: European Commission
Source reference: https://ec.europa.eu/digital-building-blocks/wikis/display/DIGITAL/What+is+eInvoicing
Additional information: eInvoicing, within the context of IT interoperability, refers to the electronic exchange of invoices between businesses, governments, and other entities in a standardized and structured format. It is a digital public service provided by the European Commission to facilitate seamless and efficient invoicing processes across the European Union.
eInvoicing eliminates the need for traditional paper-based invoices, enabling organizations to send, receive, process, and store invoices electronically. It aims to streamline and automate the invoicing process, reducing administrative burdens, enhancing accuracy, and improving overall efficiency.
In the European Commission's digital public service, eInvoicing adheres to a set of standards and technical specifications known as the European eInvoicing Standard (EN). This standard ensures that invoices are exchanged in a consistent and interoperable manner, regardless of the systems or software used by the sender and receiver.
The eInvoicing process begins with the creation of an electronic invoice by the supplier. The invoice is then transmitted to the recipient through a secure electronic channel, such as a dedicated eInvoicing platform or a government-provided portal. The recipient's system receives the invoice and automatically processes it, extracting relevant data and integrating it into their financial systems.
To ensure seamless interoperability, the European eInvoicing Standard defines a common syntax and structure for invoices, including mandatory and optional data fields. This standardization enables different systems to understand and interpret invoices consistently, regardless of their origin or destination. It also facilitates the automation of invoice processing, as systems can easily extract and validate data without manual intervention.
eInvoicing within the European Commission's digital public service also incorporates other features to enhance efficiency and security. These may include digital signatures or electronic seals to ensure the authenticity and integrity of invoices, as well as encryption techniques to protect sensitive information during transmission.
By promoting eInvoicing, the European Commission aims to foster a digital single market, where businesses can seamlessly trade across borders without unnecessary barriers. It encourages the adoption of eInvoicing by both public and private entities, offering guidance, support, and technical resources to facilitate the transition from traditional paper-based invoicing to electronic processes.
Overall, eInvoicing within the context of IT interoperability is a digital public service provided by the European Commission to enable the electronic exchange of standardized invoices. It aims to streamline invoicing processes, reduce administrative burdens, and enhance efficiency, ultimately contributing to the creation of a digital single market within the European Union.
Example: One example of the application of eInvoicing within the context of IT interoperability in a digital public service at the European Commission could be the implementation of a centralized eInvoicing platform. This platform would enable the electronic exchange of invoices between the European Commission and its suppliers, ensuring seamless interoperability between different IT systems.
Through this platform, suppliers could submit their invoices electronically in a standardized format, such as the European standard for eInvoicing (EN16931). The platform would then automatically validate and process these invoices, ensuring compliance with relevant regulations and standards.
Furthermore, the eInvoicing platform could integrate with existing financial management systems used by the European Commission, allowing for the direct transfer of invoice data into these systems. This integration would eliminate the need for manual data entry, reducing errors and improving efficiency.
Additionally, the eInvoicing platform could support various authentication and authorization mechanisms, such as digital signatures or electronic identification, to ensure the security and authenticity of the invoicing process. This would enable secure electronic transmission of invoices, eliminating the need for paper-based invoices and manual handling.
Moreover, the platform could provide functionalities for tracking and monitoring the status of invoices, allowing both the European Commission and its suppliers to have real-time visibility into the invoicing process. This would facilitate better communication and collaboration between the parties involved, reducing delays and improving overall transparency.
Overall, the implementation of a centralized eInvoicing platform within the European Commission's digital public service would enhance IT interoperability by enabling seamless electronic exchange of invoices, integration with existing systems, and ensuring compliance with standards and regulations.
LOST view: TVA-API Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/EInvoicingBusinessService
ABB name: egovera:EInvoicingBusinessService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/egovera/EInvoicingBusinessService
Name: eInvoicing Digital Public Service
Interoperability Layer: Organisational
Specialises: http://data.europa.eu/dr8/DigitalPublicBusinessService
Definition: Forms Management enables the storage, catalogation and indexing/searching of structured and unstructured documents.
Source: FORTRA
Source reference: https://www.helpsystems.com/blog/what-forms-management
Additional information: Forms management within the context of IT interoperability in a digital public service within the European Commission refers to the systematic and efficient handling of electronic forms used for various administrative processes. It involves the design, creation, distribution, submission, processing, and storage of digital forms to facilitate seamless information exchange and collaboration between different systems, organizations, and individuals.
At its core, forms management aims to streamline and standardize the collection of data and information by providing a structured and user-friendly interface for users to input and submit relevant details electronically. This process eliminates the need for paper-based forms, reducing administrative burdens, improving data accuracy, and enhancing overall efficiency.
The European Commission, being a supranational institution responsible for policy-making and governance within the European Union, relies heavily on digital public services to interact with citizens, businesses, and other stakeholders. Forms management plays a crucial role in ensuring the smooth functioning of these services by enabling the exchange of information in a secure, standardized, and interoperable manner.
The process of forms management typically involves several key components. Firstly, there is the design and creation of electronic forms, which involves defining the required fields, data types, validation rules, and any associated business logic. These forms are often developed using specialized software tools that allow for easy customization and integration with existing systems.
Once the forms are created, they need to be distributed to the relevant users or organizations. This can be achieved through various channels, such as web portals, email notifications, or integration with other systems. The forms may also be made available in multiple languages to cater to the diverse linguistic needs of the European Union.
When users fill out the forms, the data they provide is submitted electronically to the designated recipients or back-end systems. This data may undergo validation checks to ensure its accuracy and compliance with predefined rules. Forms management systems often incorporate features like data encryption and digital signatures to ensure the security and integrity of the information being transmitted.
After submission, the received forms are processed and stored in a centralized repository or database. This allows for easy retrieval and access to the collected data for further processing or analysis. The forms management system may also generate notifications or trigger automated workflows based on predefined rules, ensuring timely actions and responses.
In the context of IT interoperability, forms management systems need to adhere to established standards and protocols to enable seamless integration with other systems and services. This includes using open data formats, standardized data models, and interoperability frameworks. By adopting such standards, the European Commission can ensure that its digital public services can effectively communicate and exchange information with other systems, both within and outside the organization.
Overall, forms management within the European Commission's digital public service is a critical component of IT interoperability. It enables the efficient collection, processing, and storage of electronic forms, facilitating seamless information exchange and collaboration between different stakeholders. By leveraging digital technologies and adhering to interoperability standards, the European Commission can enhance the effectiveness and accessibility of its public services, ultimately benefiting citizens, businesses, and the overall European Union.
Example: Forms management is an essential aspect of IT interoperability in the context of a digital public service in the European Commission. Here are some examples of its application:
1. Online Application Forms: The European Commission can utilize forms management to create and manage online application forms for various services such as grants, permits, or registrations. These forms can be designed to collect specific information required from applicants, ensuring consistency and standardization across different services.
2. Data Collection and Reporting: Forms management can be employed to collect data from various stakeholders, such as citizens, businesses, or other government agencies. For instance, the European Commission may use forms to gather information on the implementation of specific policies or to collect feedback from citizens on public services. This data can then be analyzed and reported on to support evidence-based decision-making.
3. Service Requests and Complaints: Forms management can facilitate the submission and processing of service requests or complaints. Citizens can fill out online forms to report issues, request information, or seek assistance. These forms can be integrated with backend systems to ensure efficient handling and tracking of requests, leading to improved service delivery and responsiveness.
4. Cross-Border Collaboration: In the context of the European Commission, forms management can support cross-border collaboration between member states. For instance, forms can be used to exchange information and data between different national authorities, enabling seamless cooperation and interoperability in areas such as law enforcement, public health, or environmental protection.
5. Standardization and Harmonization: Forms management can contribute to standardizing and harmonizing data collection processes across different services and member states. By defining common data fields, formats, and validation rules, forms can ensure consistency in the information collected, making it easier to aggregate and analyze data at a European level.
6. Accessibility and Multilingual Support: Forms management can address accessibility requirements by providing accessible form templates and features such as screen reader compatibility or alternative text for visual elements. Additionally, multilingual support can be incorporated into forms, allowing citizens to complete them in their preferred language, thereby enhancing inclusivity and user experience.
Overall, forms management plays a crucial role in enabling efficient data collection, standardization, and collaboration within the European Commission's digital public services, supporting IT interoperability and enhancing the delivery of services to citizens and stakeholders.
LOST view: TVA-Data Management Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/FormsManagementBusinessService
ABB name: egovera:FormsManagementBusinessService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/egovera/FormsManagementBusinessService
Name: Forms Management Digital Public Service
Interoperability Layer: Organisational
Specialises: http://data.europa.eu/dr8/DigitalPublicBusinessService
Definition: Analysis Management in IT refers to the process of managing, organizing, and interpreting data and information to support decision-making processes. It involves the use of various analytical tools and techniques to understand patterns, trends, and insights from data.
Source: Techopedia
Source reference: https://www.techopedia.com/definition/28066/analysis-management
Additional information: Analysis Management is a critical aspect of IT that helps organizations to make data-driven decisions. It involves the collection, processing, and interpretation of data to extract valuable insights. This process often involves the use of data analysis tools and software that can handle large volumes of data. Analysis Management can be applied in various areas such as market research, business intelligence, predictive analytics, and more. It helps in identifying trends, predicting future outcomes, understanding customer behavior, improving business operations, and driving strategic decision-making.
Example: [object Object]
LOST view: OV-Customs Functional Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/AnalysisManagementBusinessService
EIRA traceability: eira:DigitalPublicBusinessService
ABB name: egovera:AnalysisManagementBusinessService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-08
dct:identifier: http://data.europa.eu/dr8/egovera/AnalysisManagementBusinessService
dct:title: Analysis Management Digital Public Service
Definition: Partner Authorization is an IT concept that involves granting access rights to a trusted partner organization, allowing them to access certain resources or perform specific actions within your system or network. It is a crucial aspect of managing security and data privacy in inter-organizational collaborations.
Source: Techopedia
Source reference: https://www.techopedia.com/definition/29066/partner-authorization
Additional information: Partner Authorization is a critical aspect of IT security and data management, especially in today's interconnected business environment. It involves setting up permissions and access rights for partner organizations, allowing them to interact with your systems or data in a controlled manner. This could involve anything from accessing a shared database, to making changes in a joint project management system. The key is to ensure that partners have the access they need to collaborate effectively, while still maintaining the security and integrity of your own systems and data. This requires careful planning, robust security measures, and ongoing management to respond to changing needs and potential security threats.
Example: 1. A company might grant partner authorization to a third-party marketing agency, allowing them to access customer data for targeted marketing campaigns. 2. In a joint venture between two tech companies, one might grant partner authorization to the other, allowing them to contribute code to a shared software development project. 3. A healthcare provider might grant partner authorization to a research institution, allowing them to access anonymized patient data for a research study.
LOST view: OV-Customs Functional Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/PartnerAuthorizationBusinessService
EIRA traceability: eira:DigitalPublicBusinessService
ABB name: egovera:PartnerAuthorizationBusinessService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-08
dct:identifier: http://data.europa.eu/dr8/egovera/PartnerAuthorizationBusinessService
dct:title: Partner authorization Digital Public Service
Definition: Origin Registry Management is an IT concept that involves the administration and control of a registry that stores the origin of digital assets. It is crucial in tracking and verifying the source of digital assets to ensure their authenticity and integrity.
Source: Techopedia
Source reference: https://www.techopedia.com/definition/123/registry
Additional information: In the context of IT, a registry is a central location in computer systems where data and information are stored. The origin registry, therefore, is a specific type of registry that keeps a record of the origin or source of digital assets. This can include software, digital files, or any other form of digital content. The management of this registry involves ensuring that the data stored is accurate, up-to-date, and secure. This is crucial in many aspects of IT, including software development, digital asset management, and cybersecurity. For instance, it can help in tracking the source of a software application, verifying the authenticity of a digital file, or identifying the origin of a cyber threat.
Example: 1. In software development, origin registry management can be used to track the source of different versions of a software application. This can help in identifying and fixing bugs, as well as in managing software updates.
2. In digital asset management, it can be used to verify the authenticity of digital files. For instance, it can help in determining whether a digital image or video is original or has been altered.
3. In cybersecurity, it can be used to identify the origin of a cyber threat. This can help in tracking down the source of a cyber attack and in preventing future attacks.
LOST view: OV-Customs Functional Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/OriginRegistryManagementBusinessService
EIRA traceability: eira:DigitalPublicBusinessService
ABB name: egovera:OriginRegistryManagementBusinessService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-08
dct:identifier: http://data.europa.eu/dr8/egovera/OriginRegistryManagementBusinessService
dct:title: Origin Registry management Digital Public Service
Definition: Digital Public Service ABB is a Business Service that enables the implementation of a Public Administration digital business capability, provisioned via a digital service delivery mode by, or on behalf of a public administration. A Digital Public Service comprises any digital public service exposed to a cross-border dimension in the European Union.
Source: EIF, ISA2 Core Vocabularies, IMM
Source reference: [http://eur-lex.europa.eu/resource.html?uri=cellar:2c2f2554-0faf-11e7-8a35-01aa75ed71a1.0017.02/DOC_3&format=PDF][https://ec.europa.eu/isa2/actions/assessing-progress-being-made-towards-interoperability_en] [https://joinup.ec.europa.eu/catalogue/distribution/cpsv-ap-specification-v20-pdf]
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): EUROPASS2 - Make better use of skills and opportunities across Europe. Europass is a service to help individuals to communicate their skills, qualifications and experience through the use of standardised documents templates. (http://ec.europa.eu/social/main.jsp?
Interoperability Dimension: Structural IoP
LOST view: Organisational view
Viewpoint: Interoperability Privacy viewpoint
Interoperability Saliency: The Digital Public Service ABB is salient for the organizational, semantic and technical interoperability because it represents the materialization of the service delivery in terms of (i) a common mechanism to give a response to a specific public administration procedure, (ii) data harmonization to facilitate the comprehension of the information, (iii) specific mechanisms to consume, share and reuse the information.
Identifier: http://data.europa.eu/dr8/DigitalPublicServiceBusinessService
ABB name: eira:DigitalPublicServiceBusinessService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/DigitalPublicServiceBusinessService
Interoperability Layer: Organisational
Definition: Contact Management enables the storage and the organisation of contacts of a public administration's user base (both providers and consumers of its public services), and the tracking of the related interactions.
Source: Aberdeen Group
Source reference: http://download.act.com/act2010/docs/Choice_Between_Contact_Management_or_CRM.pdf
Additional information: Contact management within the context of IT interoperability in a digital public service within the European Commission refers to the systematic and efficient management of all contacts and interactions with various stakeholders, including individuals, organizations, and entities involved in the provision and consumption of digital services.
The primary objective of contact management is to establish and maintain effective communication channels, ensuring seamless information exchange and collaboration between different parties involved in the digital public service ecosystem. It encompasses a range of activities, tools, and processes that facilitate the collection, organization, storage, retrieval, and analysis of contact-related data.
At its core, contact management involves the creation and maintenance of a centralized repository or database that stores comprehensive and up-to-date information about each contact. This information typically includes contact details such as names, addresses, phone numbers, email addresses, and organizational affiliations. Additionally, it may also include specific attributes or categorizations related to the contact, such as their role, responsibilities, preferences, and any previous interactions or engagements with the digital public service.
The contact management system enables the European Commission to effectively manage and track interactions with various stakeholders. It allows for the recording and tracking of communication history, ensuring that all relevant information is readily available for reference and analysis. This includes details of meetings, emails, phone calls, and any other form of communication that has taken place between the digital public service and the contact.
Furthermore, contact management also facilitates the coordination and scheduling of meetings, events, and other engagements with stakeholders. It enables the European Commission to efficiently plan and organize interactions, ensuring that the right people are involved at the right time. This may involve features such as calendar integration, reminders, and notifications to ensure timely and effective communication.
In addition to managing individual contacts, contact management within the European Commission's digital public service also involves the management of contact lists or groups. These lists can be created based on various criteria, such as organizational affiliations, roles, or specific interests. They allow for targeted communication and engagement with specific segments of stakeholders, ensuring that relevant information reaches the intended audience.
Moreover, contact management may also involve integration with other IT systems and tools used within the European Commission. This integration enables seamless data exchange and synchronization between contact management and other systems, such as customer relationship management (CRM) systems, email clients, or collaboration platforms. It ensures that contact information remains consistent and up-to-date across different systems, avoiding duplication or discrepancies.
Overall, contact management plays a crucial role in facilitating effective communication, collaboration, and engagement within the digital public service ecosystem of the European Commission. It ensures that stakeholders are appropriately informed, involved, and supported throughout their interactions with the digital public service, ultimately contributing to the successful delivery of services and the achievement of organizational goals.
Example: Contact management is a crucial aspect of IT interoperability within the context of a digital public service in the European Commission. It ensures efficient communication and collaboration between different stakeholders involved in the service. Here are some examples of how contact management can be applied:
1. Stakeholder Engagement: The digital public service may involve multiple stakeholders such as government agencies, citizens, businesses, and other organizations. Contact management allows for the effective management of contact information for each stakeholder, ensuring seamless communication and engagement throughout the service's lifecycle.
2. Interagency Collaboration: Within the European Commission, various departments and agencies may be involved in the development and delivery of the digital public service. Contact management enables the establishment and maintenance of contact lists for different agencies, facilitating collaboration, information sharing, and coordination between them.
3. User Support: Contact management plays a vital role in providing user support for the digital public service. It allows for the management of contact details of users seeking assistance or reporting issues. This ensures that users can easily reach out for help, and their queries or problems are efficiently addressed by the appropriate support team.
4. Vendor Management: The digital public service may rely on external vendors or service providers for certain components or functionalities. Contact management helps in maintaining contact information for these vendors, enabling effective communication, contract management, and issue resolution.
5. Stakeholder Notifications: Contact management facilitates the dissemination of important notifications, updates, or announcements to relevant stakeholders. It ensures that the right information reaches the right individuals or groups, helping to keep them informed and engaged throughout the service's lifecycle.
6. Data Sharing and Integration: Contact management can also support data sharing and integration efforts within the digital public service. By maintaining accurate and up-to-date contact information, it becomes easier to exchange data with other systems or services, ensuring interoperability and seamless information flow.
7. Event Management: The digital public service may organize events, workshops, or training sessions involving various stakeholders. Contact management assists in managing attendee lists, sending invitations, and tracking RSVPs, ensuring smooth event coordination and participation.
In summary, contact management within the context of IT interoperability in a digital public service at the European Commission enables effective stakeholder engagement, interagency collaboration, user support, vendor management, stakeholder notifications, data sharing, and event management.
LOST view: TVA-Data Management Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/ContactManagementBusinessService
ABB name: egovera:ContactManagementBusinessService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/egovera/ContactManagementBusinessService
Name: Contact Management Digital Public Service
Interoperability Layer: Organisational
Specialises: http://data.europa.eu/dr8/DigitalPublicBusinessService
Definition: Intra-EU purchases and sales refer to the transactions of goods and services between businesses located in different member states of the European Union. These transactions are subject to specific VAT regulations and reporting requirements.
Source: European Commission
Source reference: https://ec.europa.eu/taxation_customs/business/vat/eu-country-specific-information_en
Additional information: Intra-EU purchases and sales are a key aspect of doing business within the European Union. They involve the exchange of goods and services between businesses located in different EU member states. These transactions are subject to specific VAT regulations and reporting requirements. For example, the seller must report the sale in an EC Sales List (ESL), while the buyer must report the purchase in their VAT return. The VAT rate applied depends on the type of goods or services sold, and the specific VAT regulations of the buyer's country. It's important for businesses to accurately track and report these transactions to comply with EU tax laws.
Example: For instance, a company based in Germany selling machinery to a company in France would need to report this as an intra-EU sale. The German company would list the sale in their ESL and would not charge VAT, while the French company would report the purchase in their VAT return and apply the reverse charge mechanism, effectively paying the VAT in France. Another example could be a software company in Ireland providing services to a company in Spain. The Irish company would report the sale in their ESL and would not charge VAT, while the Spanish company would report the purchase in their VAT return and apply the reverse charge mechanism.
LOST view: OV-Customs Functional Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/Intra-EUPurchasesAndSalesBusinessService
EIRA traceability: eira:DigitalPublicBusinessService
ABB name: egovera:Intra-EUPurchasesAndSalesBusinessService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-08
dct:identifier: http://data.europa.eu/dr8/egovera/Intra-EUPurchasesAndSalesBusinessService
dct:title: Intra-EU purchases and sales Digital Public Service
Definition: A Procedure Automation System is an IT concept that involves the use of technology to automate repetitive tasks and processes in an organization, thereby increasing efficiency, reducing errors, and freeing up staff to focus on more complex tasks.
Source: Techopedia
Source reference: https://www.techopedia.com/definition/32099/automation
Additional information: Procedure Automation Systems can be applied to various areas in an organization, including customer service, sales, marketing, finance, human resources, and IT. These systems can automate tasks such as data entry, report generation, email marketing, customer support, and more. They can also integrate with other systems to streamline workflows and improve data accuracy. The use of Procedure Automation Systems can lead to significant cost savings, improved productivity, better decision-making, and enhanced customer satisfaction.
Example: Examples of Procedure Automation Systems include Customer Relationship Management (CRM) systems that automate sales and customer service processes, Robotic Process Automation (RPA) tools that automate data entry and report generation tasks, and marketing automation platforms that automate email marketing and social media posting tasks.
LOST view: TVA-Customs Process Streamlining and Efficiency Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/ProcedureAutomationSystemBusinessService
EIRA traceability: eira:DigitalPublicBusinessService
ABB name: egovera:ProcedureAutomationSystemBusinessService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-08
dct:identifier: http://data.europa.eu/dr8/egovera/ProcedureAutomationSystemBusinessService
dct:title: Procedure Automation System Digital Public Service
Definition: Data Extraction, Transformation, and Loading (ETL) is a business service that involves extracting data from various sources, transforming it into a standardized format, and loading it into a target system or data repository. The ETL service enables organizations to collect, integrate, and consolidate data from diverse sources, ensuring data quality and consistency for analysis, reporting, and decision-making.
Source: IEEE Computer Society
Example: One example of the application of Data Extraction, Transformation, and Loading (ETL) within the context of IT interoperability in a digital public service at the European Commission is the integration of various data sources to provide a unified view of citizen information.
1. Citizen Data Integration: The European Commission may have multiple systems and databases that store citizen data, such as personal details, addresses, and preferences. ETL processes can be employed to extract data from these disparate sources, transform it into a standardized format, and load it into a central data repository. This enables a comprehensive view of citizen information, facilitating efficient service delivery and personalized interactions.
2. Cross-Border Data Exchange: The European Commission often collaborates with member states and other countries, requiring the exchange of data across borders. ETL can be utilized to extract relevant data from national databases, transform it into a common format, and load it into a shared data warehouse. This ensures seamless interoperability between different systems, enabling efficient cross-border data exchange for various purposes like law enforcement, taxation, or healthcare.
3. Harmonization of Data Standards: Different departments or agencies within the European Commission may use different data standards and formats. ETL processes can be employed to extract data from these diverse sources, transform it into a standardized format, and load it into a common data model. This harmonization of data standards ensures interoperability and facilitates data sharing and analysis across different departments, enabling better decision-making and policy formulation.
4. Real-time Data Integration: In certain scenarios, real-time data integration is crucial for effective decision-making. ETL processes can be utilized to extract data from various real-time sources, such as IoT devices or social media platforms, transform it into a usable format, and load it into a real-time analytics system. This enables the European Commission to monitor and respond to emerging trends, public sentiment, or critical events promptly.
5. Data Quality Assurance: ETL processes can also play a vital role in ensuring data quality within the European Commission's digital public service. Extraction processes can include data validation and cleansing techniques to identify and rectify inconsistencies, errors, or duplications. Transformation processes can standardize and enrich the data, while loading processes can include data quality checks to ensure accuracy and completeness. This guarantees that reliable and high-quality data is available for decision-making and service delivery.
Overall, the application of Data Extraction, Transformation, and Loading within the context of IT interoperability in a digital public service at the European Commission enables seamless data integration, harmonization, and quality assurance, facilitating efficient service delivery, cross-border collaboration, and evidence-based decision-making.
LOST view: TVA-Data Management Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/DataExtractionTransformationAndLoadingBusinessService
ABB name: egovera:DataExtractionTransformationAndLoadingBusinessService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/egovera/DataExtractionTransformationAndLoadingBusinessService
Name: Data Extraction, Transformation and Loading Digital Public Service
Interoperability Layer: Organisational
Specialises: http://data.europa.eu/dr8/DigitalPublicBusinessService
Definition: eQualification, within the context of IT interoperability, refers to a digital public service provided by the European Commission that aims to streamline and standardize the process of qualifying and certifying individuals or organizations for various purposes. It involves the development and implementation of a digital platform that enables the secure exchange of qualification-related information between different systems and stakeholders across Europe. This service ensures that qualifications obtained in one country are recognized and accepted in another, facilitating mobility and enhancing the interoperability of digital public services within the European Union.
Source: EIRA Team
Additional information: eQualification is a crucial aspect of IT interoperability within the context of digital public services in the European Commission. It refers to the process of assessing and certifying the technical and functional capabilities of digital systems, software, and services to ensure their compatibility and seamless integration with other systems and services.
In the European Commission, eQualification plays a vital role in promoting the development and deployment of interoperable digital public services across member states. It aims to establish a standardized framework for evaluating the conformity of IT solutions, ensuring that they meet the necessary requirements and standards set by the Commission.
The eQualification process involves a comprehensive assessment of various aspects of digital systems, including their technical specifications, functionalities, security measures, and compliance with relevant regulations and standards. It encompasses both the evaluation of individual components and the overall system architecture to ensure their compatibility with existing infrastructure and other interconnected systems.
To achieve eQualification, digital public services undergo rigorous testing and validation procedures. These procedures may include functional testing, performance testing, security testing, and interoperability testing. The goal is to verify that the systems can effectively communicate, exchange data, and collaborate with other systems without any disruptions or compatibility issues.
The eQualification process is typically carried out by qualified and accredited organizations or laboratories, which are entrusted with assessing the compliance of digital systems with the established standards and requirements. These organizations follow standardized methodologies and criteria to ensure objectivity and consistency in the evaluation process.
Once a digital system successfully completes the eQualification process, it is awarded a certification or qualification, indicating its compliance with the specified standards and its interoperability capabilities. This certification serves as evidence of the system's reliability, security, and compatibility, instilling confidence in its users and facilitating its integration into wider digital ecosystems.
The eQualification framework in the European Commission fosters the development of interoperable digital public services by providing a common language and set of criteria for assessing the compatibility and quality of IT solutions. It enables member states to leverage standardized and certified systems, reducing duplication of efforts and promoting efficient collaboration and information exchange across borders.
Overall, eQualification is a fundamental component of IT interoperability in the context of digital public services in the European Commission. It ensures that digital systems and services meet the necessary standards and requirements, enabling seamless integration and effective collaboration among various stakeholders in the digital ecosystem.
Example: One example of the application of eQualification within the context of IT interoperability in a digital public service in the European Commission is the use of eQualification for authentication and authorization purposes. In this scenario, eQualification can be used to verify the qualifications and credentials of individuals accessing the digital service.
For instance, when a user wants to access a specific digital public service, they may be required to provide their eQualification, which could be a digital certificate or an electronic identification (eID) card. This eQualification can be used to authenticate the user's identity and verify their qualifications or credentials, such as their professional certifications or educational degrees.
By leveraging eQualification in this manner, the digital public service can ensure that only qualified individuals with the necessary credentials are granted access to specific functionalities or sensitive information. This helps to maintain the integrity and security of the service, as well as ensure that the users accessing it possess the required qualifications.
Furthermore, eQualification can also be utilized for interoperability purposes between different digital public services within the European Commission. For example, if a user has already provided their eQualification to access one digital service, they may not need to repeat the qualification verification process when accessing another related service. Instead, the previously verified eQualification can be shared or reused, promoting seamless interoperability between different services.
This approach streamlines the user experience, reduces redundancy, and enhances efficiency by eliminating the need for users to repeatedly verify their qualifications across multiple digital services. It also promotes trust and confidence in the digital public services provided by the European Commission, as users can rely on their eQualification to access various services securely and conveniently.
LOST view: TVA-API Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/EQualificationBusinessService
ABB name: egovera:EQualificationBusinessService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/egovera/EQualificationBusinessService
Name: eQualification Digital Public Service
Interoperability Layer: Organisational
Specialises: http://data.europa.eu/dr8/DigitalPublicBusinessService
Definition: Delegation of Power within the context of IT interoperability in a digital public service in the European Commission refers to the process of granting certain authorities or permissions to specific entities or individuals to perform certain tasks or actions on behalf of the service. It involves the transfer of responsibilities, decision-making powers, and access rights to ensure efficient and effective functioning of the service. This delegation allows different systems or components to interact and exchange information seamlessly, enabling interoperability and collaboration between various stakeholders involved in the digital public service.
Source: EIRA Team
Additional information: In the context of IT interoperability within a digital public service in the European Commission, the delegation of power refers to the process of granting certain authorities or permissions to specific entities or individuals to perform certain tasks or access certain resources on behalf of others. It involves the transfer of responsibilities, decision-making powers, and access rights from one entity to another, ensuring efficient and secure collaboration and operation of digital services.
In the European Commission's digital public service, the delegation of power is crucial for enabling seamless interoperability between different systems, applications, and services. It allows various stakeholders, such as government agencies, departments, or external service providers, to interact and exchange information effectively while adhering to established standards and protocols.
At its core, the delegation of power involves the assignment of roles and responsibilities to different entities within the digital ecosystem. These entities can include administrators, system operators, developers, or end-users, each with their own specific tasks and privileges. For instance, an administrator may have the authority to manage user accounts, configure system settings, or grant access rights to specific resources.
To ensure secure and controlled delegation of power, the European Commission's digital public service likely employs robust authentication and authorization mechanisms. These mechanisms verify the identity of individuals or entities requesting access and determine the level of permissions they are granted based on predefined policies and rules. This helps prevent unauthorized access and ensures that only authorized personnel can exercise delegated powers.
Furthermore, the delegation of power in IT interoperability also involves the establishment of trust relationships between different systems and services. This is achieved through the use of digital certificates, encryption, and secure communication protocols. Trust is essential to enable seamless data exchange and collaboration between various entities, ensuring the integrity, confidentiality, and authenticity of information shared.
In the European Commission's digital public service, the delegation of power may also encompass the delegation of decision-making authority. This means that certain entities or individuals may be empowered to make decisions on behalf of others within predefined boundaries. For example, a department head may delegate decision-making power to a team leader, enabling them to make decisions within their area of responsibility.
Overall, the delegation of power within the context of IT interoperability in the European Commission's digital public service is a complex and essential process. It involves assigning roles, granting permissions, establishing trust relationships, and enabling secure collaboration and data exchange between different entities. This ensures the efficient and effective functioning of digital services while maintaining the necessary security and control.
Example: In the context of IT interoperability within a digital public service in the European Commission, the delegation of power can be applied in various ways. Here are a few examples:
1. Authentication and Authorization: The delegation of power can be used to grant specific individuals or organizations the authority to authenticate and authorize access to certain digital services. For instance, the European Commission may delegate the power to issue digital certificates for authentication purposes to trusted certification authorities. These authorities can then verify the identity of users and grant them access to relevant services.
2. Data Sharing and Exchange: The delegation of power can facilitate the secure sharing and exchange of data between different systems and organizations. For example, the European Commission may delegate the power to certain data controllers to share specific datasets with authorized recipients. This delegation ensures that data is shared in a controlled and compliant manner, adhering to relevant data protection regulations.
3. Service Integration: In complex digital public services, different components or modules may be developed by different teams or organizations. The delegation of power can be used to assign responsibility for integrating these components into a cohesive service. For instance, the European Commission may delegate the power to a specific team or organization to integrate various modules, ensuring seamless interoperability between them.
4. Standards and Specifications: The delegation of power can be employed to establish and enforce standards and specifications for IT interoperability. The European Commission may delegate the power to a dedicated body or organization to define and maintain interoperability standards for digital services. This delegation ensures that all relevant stakeholders adhere to the same standards, enabling smooth interoperability across different systems.
5. Governance and Oversight: The delegation of power can be utilized to establish governance structures and oversight mechanisms for IT interoperability. The European Commission may delegate the power to a governing body or committee to oversee the implementation and compliance of interoperability standards and policies. This delegation ensures that interoperability efforts are effectively managed and monitored.
Overall, the delegation of power within the context of IT interoperability in a digital public service allows for the efficient and secure management of various aspects, including authentication, data sharing, service integration, standards, and governance.
LOST view: OV-Functional Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/DelegationOfPowerBusinessService
ABB name: egovera:DelegationOfPowerBusinessService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/egovera/DelegationOfPowerBusinessService
Name: Delegation of Power Digital Public Service
Interoperability Layer: Organisational
Specialises: http://data.europa.eu/dr8/DigitalPublicBusinessService
Definition: Secure Access Control within the context of IT interoperability in a digital public service of the European Commission refers to the mechanism that ensures authorized and secure access to digital resources and services. It involves the implementation of robust authentication and authorization protocols to verify the identity of users and grant them appropriate levels of access based on their roles and permissions. This ensures that only authorized individuals can access sensitive information and perform specific actions, thereby safeguarding the confidentiality, integrity, and availability of digital services and data.
Source: EIRA Team
Additional information: Secure Access Control is a crucial component within the realm of IT interoperability, particularly in the context of a digital public service provided by the European Commission. It encompasses a comprehensive set of mechanisms and protocols that ensure the protection and controlled access to sensitive information and resources.
At its core, Secure Access Control aims to authenticate and authorize individuals or entities attempting to access digital services, systems, or data. It establishes a robust framework that guarantees only authorized users can gain entry, preventing unauthorized access and potential security breaches. This is of utmost importance in the European Commission's digital public service, as it deals with a vast amount of sensitive data and resources.
Authentication is the initial step in the Secure Access Control process. It involves verifying the identity of users or entities attempting to access the system. Various authentication methods can be employed, such as passwords, biometrics, smart cards, or digital certificates. These methods ensure that only legitimate users with valid credentials can proceed further.
Once authentication is successful, the authorization phase comes into play. Authorization determines the level of access and privileges granted to authenticated users based on their roles, responsibilities, and permissions. This step ensures that users can only access the resources and perform actions that are relevant to their designated roles, preventing unauthorized activities and potential misuse of sensitive information.
To achieve a robust Secure Access Control system, the European Commission's digital public service may implement a variety of mechanisms. Role-based access control (RBAC) is commonly employed, where access rights are assigned based on predefined roles within the organization. This approach simplifies access management by grouping users with similar responsibilities and granting them appropriate permissions.
Additionally, attribute-based access control (ABAC) can be utilized, which considers various attributes such as user attributes, resource attributes, and environmental attributes to make access control decisions. ABAC provides a more flexible and dynamic approach to access control, allowing for fine-grained control over resource access based on specific conditions.
Furthermore, Secure Access Control may incorporate multi-factor authentication (MFA) to enhance security. MFA requires users to provide multiple pieces of evidence to prove their identity, such as a combination of passwords, biometrics, or one-time passwords. This adds an extra layer of protection, making it significantly more challenging for unauthorized individuals to gain access.
In the European Commission's digital public service, Secure Access Control also encompasses the concept of access logging and auditing. This involves recording and monitoring all access attempts, including successful and unsuccessful ones, to establish an audit trail. This audit trail can be utilized for forensic analysis, compliance purposes, and identifying potential security incidents or breaches.
Overall, Secure Access Control within the context of IT interoperability in the European Commission's digital public service is a comprehensive framework that ensures the protection of sensitive information and resources. By implementing robust authentication, authorization, and access management mechanisms, it guarantees that only authorized individuals can access the system, mitigating the risk of unauthorized access and potential security threats.
Example: One example of the application of Secure Access Control within the context of IT interoperability in a digital public service within the European Commission could be the authentication and authorization process for accessing sensitive data or services.
In this scenario, Secure Access Control ensures that only authorized individuals or entities can access specific resources or perform certain actions within the digital public service. It involves the use of various security mechanisms such as user authentication, role-based access control, and encryption to protect the confidentiality, integrity, and availability of the data.
For instance, when a user wants to access a specific dataset or service provided by the European Commission, they would need to authenticate themselves using a secure login process. This could involve providing a username and password, along with an additional factor of authentication such as a one-time password or a biometric verification.
Once authenticated, the user's access privileges are determined based on their assigned role or permissions within the system. For example, a user with the role of "data analyst" may have read-only access to certain datasets, while a user with the role of "data administrator" may have full access and the ability to modify the data.
Secure Access Control also ensures that data is transmitted securely between different systems or components involved in the digital public service. This can be achieved through the use of encryption protocols such as SSL/TLS, which encrypts the data during transmission to prevent unauthorized interception or tampering.
Furthermore, Secure Access Control can also enforce fine-grained access control policies based on various attributes such as user location, time of access, or the sensitivity of the data being accessed. This helps in ensuring that only authorized users with a legitimate need can access specific resources, thereby minimizing the risk of data breaches or unauthorized disclosures.
Overall, the application of Secure Access Control within the context of IT interoperability in a digital public service within the European Commission plays a crucial role in safeguarding sensitive data, protecting user privacy, and ensuring the integrity and availability of the services provided.
LOST view: OV-Functional Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/SecureAccessControlBusinessService
ABB name: egovera:SecureAccessControlBusinessService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/egovera/SecureAccessControlBusinessService
Name: Secure Access Control Digital Public Service
Interoperability Layer: Organisational
Specialises: http://data.europa.eu/dr8/DigitalPublicBusinessService
Definition: eTendering enables the electronic end-to-end management of the purchasing process and related tasks associated to the acquisition of third-party goods and/or services through digital means and information and communication technologies.
Source: European Commission
Source reference: https://etendering.ted.europa.eu/general/page.html?name=home
Additional information: eTendering, within the context of IT interoperability in a digital public service in the European Commission, refers to the electronic procurement process that enables public sector organizations to publish, manage, and award tenders or contracts to suppliers through an online platform. It is a digital solution designed to streamline and enhance the efficiency, transparency, and fairness of the procurement process.
eTendering platforms provide a centralized and standardized system for managing the entire tendering lifecycle, from the publication of tender notices to the submission and evaluation of bids, and ultimately the awarding of contracts. These platforms are typically web-based and accessible to both public sector entities and potential suppliers, ensuring a level playing field for all participants.
One of the primary objectives of eTendering is to promote open competition and increase transparency in public procurement. By digitizing the entire process, it becomes easier for suppliers to access and participate in tenders, regardless of their geographical location. This fosters a more competitive environment, as a larger pool of potential suppliers can submit their bids, leading to better value for money for the public sector.
In terms of IT interoperability, eTendering platforms adhere to certain technical standards and specifications to ensure seamless integration with other systems and services. These standards enable interoperability between different eTendering platforms, allowing for the exchange of data and information between various stakeholders involved in the procurement process.
For instance, eTendering platforms may utilize standardized data formats, such as XML or JSON, to facilitate the exchange of tender notices, bid documents, and evaluation reports between the platform and other systems, such as eProcurement systems or financial management systems. This interoperability ensures that information flows smoothly across different stages of the procurement process, reducing manual effort, minimizing errors, and enhancing data accuracy.
Furthermore, eTendering platforms often integrate with electronic signature solutions to ensure the authenticity and integrity of tender documents. This integration enables suppliers to digitally sign their bids, eliminating the need for physical paperwork and enabling a fully digital and secure tendering process.
In the European Commission, eTendering plays a crucial role in promoting fair competition, efficiency, and transparency in public procurement. It aligns with the principles of the EU's Digital Single Market strategy, which aims to harness the potential of digital technologies to drive economic growth, innovation, and job creation across the European Union.
Overall, eTendering within the context of IT interoperability in the European Commission's digital public service is a comprehensive digital solution that revolutionizes the procurement process. It leverages technology to enhance transparency, increase competition, and improve efficiency, ultimately benefiting both public sector organizations and suppliers.
Example: One example of the application of eTendering within the context of IT interoperability in a digital public service in the European Commission could be the procurement process for software development services.
In this scenario, the European Commission may need to develop a new software application to enhance its digital services. The eTendering system would be utilized to streamline the procurement process and ensure interoperability among different IT systems involved.
1. Publication of tender: The European Commission would publish a tender notice on the eTendering platform, providing details about the software development project, requirements, and evaluation criteria. This notice would be accessible to potential bidders from various IT companies across Europe.
2. Electronic submission of bids: Interested IT companies would submit their bids electronically through the eTendering system. The system would ensure that all bids are submitted in a standardized format, promoting interoperability among different IT systems used by the bidders.
3. Evaluation of bids: The evaluation committee, consisting of representatives from the European Commission, would assess the submitted bids using the eTendering system. The system would allow for efficient comparison and evaluation of bids based on predefined criteria, ensuring transparency and fairness in the evaluation process.
4. Clarifications and communication: The eTendering system would facilitate communication between the European Commission and the bidders. Any clarifications or additional information requested by the bidders would be addressed through the system, ensuring all parties have access to the same information and promoting interoperability in communication.
5. Contract award: Once the evaluation process is complete, the European Commission would award the contract to the successful bidder through the eTendering system. The system would generate the necessary documentation, including the contract agreement, which would be digitally signed by both parties, ensuring legal validity and interoperability in contract management.
6. Project implementation: Throughout the software development project, the eTendering system would continue to play a role in monitoring and managing the project progress. It could be used for progress reporting, change management, and invoice submission, ensuring interoperability in project management processes.
By utilizing eTendering in this manner, the European Commission can ensure a transparent, efficient, and interoperable procurement process for IT services, ultimately leading to the successful development and implementation of digital public services.
LOST view: TVA-API Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/ETenderingBusinessService
EIRA traceability: eira:DigitalPublicBusinessService
ABB name: egovera:ETenderingBusinessService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-07-04
dct:identifier: http://data.europa.eu/dr8/egovera/ETenderingBusinessService
dct:title: eTendering Digital Public Service
Definition: Economic Operator Management and Accreditation is an IT concept that involves the use of technology to manage and accredit economic operators. This is often used in supply chain management and procurement processes to ensure that all economic operators meet the necessary standards and requirements.
Source: European Commission
Source reference: https://ec.europa.eu/growth/single-market/public-procurement/rules-implementation_en
Additional information: Economic Operator Management and Accreditation involves the use of IT systems to manage and accredit economic operators. This includes managing the registration, qualification, and classification of economic operators, as well as monitoring their performance and compliance with relevant standards and regulations. The system can also be used to manage the accreditation process, which involves verifying that an economic operator meets certain standards and requirements. This can include checking their financial stability, technical capability, and compliance with environmental and social standards. The system can also provide a platform for communication and collaboration between economic operators and the organizations that manage and accredit them.
Example: Examples of application include the European Single Procurement Document (ESPD) system used by the European Commission, which uses IT to manage and accredit economic operators involved in public procurement processes. Another example is the Supplier Qualification System (SQS) used by some companies to manage and accredit their suppliers.
LOST view: TVA-Customs Compliance and Regulatory Requirements Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/EconomicOperatorManagementAndAccreditationBusinessService
EIRA traceability: eira:DigitalPublicBusinessService
ABB name: egovera:EconomicOperatorManagementAndAccreditationBusinessService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-08
dct:identifier: http://data.europa.eu/dr8/egovera/EconomicOperatorManagementAndAccreditationBusinessService
dct:title: Economic Operator management and accreditation Digital Public Service
Definition: eIdentification, within the context of IT interoperability in a digital public service of the European Commission, refers to the process of verifying and authenticating the identity of individuals or entities accessing online services. It involves the use of digital credentials, such as electronic identity cards or digital signatures, to establish trust and ensure secure access to various online platforms and services. eIdentification plays a crucial role in enabling seamless and secure interactions between users and digital public services, facilitating the exchange of information and promoting interoperability across different systems and organizations.
Source: EIRA Team
Additional information: eIdentification, within the context of IT interoperability, refers to the process of electronically verifying and authenticating the identity of individuals or entities in a digital public service provided by the European Commission. It involves the use of digital technologies and standardized protocols to establish the identity of users accessing online services, ensuring secure and reliable interactions between different systems and platforms.
In the European Commission's digital public service, eIdentification plays a crucial role in enabling seamless and trusted electronic transactions, as well as facilitating the exchange of information and data across various government departments, agencies, and organizations. It aims to provide a unified and standardized approach to identity verification, eliminating the need for multiple, separate identification processes for different services.
The eIdentification system incorporates various elements to ensure the security and integrity of digital identities. It typically involves the use of unique identifiers, such as usernames or email addresses, along with strong authentication mechanisms, such as passwords, PINs, or biometric data, to verify the identity of users. These authentication factors are securely stored and transmitted using encryption techniques to prevent unauthorized access or tampering.
Furthermore, eIdentification within the European Commission's digital public service adheres to established standards and frameworks, such as the eIDAS Regulation (electronic Identification, Authentication and Trust Services), which provides a legal framework for electronic identification and trust services across the European Union. This regulation ensures that eIdentification processes are interoperable, secure, and recognized across member states, promoting cross-border digital services and enhancing trust in online transactions.
The eIdentification system also supports the concept of federated identity, allowing users to access multiple services using a single set of credentials. This means that individuals or entities can authenticate themselves once and gain access to various digital public services without the need for separate identification processes for each service. Federated identity relies on trusted identity providers, which may include government agencies, private organizations, or trusted third-party service providers, to verify and vouch for the identities of users.
Overall, eIdentification in the context of IT interoperability in the European Commission's digital public service is a comprehensive and standardized approach to verifying and authenticating the identity of users accessing online services. It ensures secure and trusted interactions, promotes cross-border digital services, and enhances the overall efficiency and effectiveness of public administration in the European Union.
Example: One example of the application of eIdentification within the context of IT interoperability in a digital public service of the European Commission is the use of eIdentification for accessing and authenticating users on the European Commission's online platform for submitting grant applications.
When individuals or organizations want to apply for grants offered by the European Commission, they can access the online platform using their eIdentification credentials. This could be a digital identity issued by a trusted authority, such as a national eID card or a digital certificate.
By using eIdentification, the European Commission ensures that only authorized individuals or organizations can access and submit grant applications. This helps to prevent unauthorized access and ensures the security and integrity of the application process.
Furthermore, eIdentification allows for seamless integration and interoperability with various national and regional eID systems across the European Union. This means that applicants from different member states can use their respective eIDs to access the platform, eliminating the need for multiple login credentials and simplifying the user experience.
Additionally, eIdentification enables the European Commission to securely verify the identity of applicants during the grant evaluation process. By leveraging interoperable eID systems, the Commission can efficiently authenticate the identity of applicants and validate their eligibility for grants.
Overall, the application of eIdentification in this digital public service of the European Commission enhances IT interoperability by enabling secure access, authentication, and verification of users from different member states, while ensuring the integrity and efficiency of the grant application process.
LOST view: OV-Functional Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/EIdentificationBusinessService
ABB name: egovera:EIdentificationBusinessService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/egovera/EIdentificationBusinessService
Name: eIdentification Digital Public Service
Interoperability Layer: Organisational
Specialises: http://data.europa.eu/dr8/DigitalPublicBusinessService
Definition: Duties Guarantee Management is an IT concept that refers to the system or process of ensuring that all tasks and responsibilities within an IT environment are properly assigned, executed, and monitored. It involves the use of various tools and methodologies to manage and control the allocation and performance of duties.
Source: Techopedia
Source reference: https://www.techopedia.com/definition/24864/it-governance
Additional information: Duties Guarantee Management is a crucial aspect of IT governance and management. It helps in ensuring that all IT-related tasks are properly assigned to the right individuals or teams, and that these tasks are performed efficiently and effectively. This concept also involves the monitoring and evaluation of the performance of these tasks, with the aim of identifying and addressing any issues or problems that may arise. Duties Guarantee Management can be implemented through various means, including the use of IT management software and systems, the establishment of clear roles and responsibilities, and the implementation of effective communication and coordination mechanisms.
Example: Examples of application of Duties Guarantee Management include the use of IT service management (ITSM) tools to assign and track IT tasks, the implementation of role-based access control (RBAC) to define and enforce IT roles and responsibilities, and the use of project management methodologies to plan, execute, and monitor IT projects.
LOST view: TVA-Customs Duties and Tariffs Management Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/DutiesGuaranteeManagementBusinessService
EIRA traceability: eira:DigitalPublicBusinessService
ABB name: egovera:DutiesGuaranteeManagementBusinessService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-08
dct:identifier: http://data.europa.eu/dr8/egovera/DutiesGuaranteeManagementBusinessService
dct:title: Duties guarantee management Digital Public Service
Definition: Content Management enables secure and efficient management of multimedia objects (e.g. images, audio, video streams) from their creation and distribution inside and/or outside a public organisation.
Source: Bob Boiko
Source reference: https://archive.org/details/contentmanagemen0000boik_t9l3
Additional information: Content management within the context of IT interoperability in a digital public service within the European Commission refers to the systematic organization, creation, storage, retrieval, and management of digital content in a standardized and efficient manner. It involves the use of various technologies, tools, and processes to ensure the seamless exchange and sharing of information across different systems, platforms, and applications.
In this context, content management plays a crucial role in enabling interoperability, which is the ability of different IT systems and applications to communicate, exchange data, and operate cohesively. It ensures that digital content, such as documents, files, multimedia, and other relevant information, can be accessed, utilized, and shared effectively by different stakeholders within the European Commission and its associated public services.
The content management system (CMS) employed in this digital public service provides a centralized platform for creating, editing, organizing, and publishing content. It allows authorized users to collaborate, contribute, and manage content in a secure and controlled manner. The CMS ensures that content is structured, tagged, and categorized appropriately, facilitating easy search, retrieval, and reuse of information.
Within the European Commission, content management also encompasses the establishment and enforcement of content governance policies and standards. These guidelines ensure consistency, quality, and compliance with regulatory requirements across all digital content. It includes defining metadata schemas, content models, and taxonomies to ensure uniformity and facilitate effective content discovery and integration.
Furthermore, content management in this context involves the integration of content with other IT systems and applications. It enables seamless data exchange and interoperability between content repositories, document management systems, customer relationship management systems, and other relevant platforms. This integration ensures that content can be accessed and utilized within different contexts and workflows, enhancing efficiency and productivity.
Additionally, content management within the European Commission's digital public service focuses on ensuring accessibility and multilingualism. It involves the implementation of standards and best practices to make content available to diverse audiences, including individuals with disabilities. It also supports the translation and localization of content to cater to the linguistic diversity within the European Union.
Overall, content management within the context of IT interoperability in a digital public service in the European Commission is a comprehensive and strategic approach to effectively manage and exchange digital content. It encompasses the use of technologies, processes, and standards to ensure seamless collaboration, accessibility, and integration of information across various systems and platforms, ultimately enhancing the efficiency and effectiveness of public services provided by the European Commission.
Example: One example of the application of Content Management within the context of IT interoperability in a digital public service at the European Commission could be the management of multilingual content. The European Commission provides information and services to citizens, businesses, and other stakeholders in multiple languages to ensure accessibility and inclusivity.
Content Management systems can be used to efficiently create, store, and manage content in various languages. This includes the ability to translate and localize content, ensuring that the information is accurately conveyed to users in their preferred language. The system can also handle the synchronization of content updates across different language versions, ensuring consistency and coherence.
Another example could be the management of structured data and metadata. The European Commission deals with a vast amount of data related to policies, regulations, and various public services. Content Management systems can help in organizing and categorizing this data using standardized metadata schemas. This allows for easier search and retrieval of information, as well as the ability to link related data across different systems and services.
Furthermore, Content Management systems can facilitate collaboration and information sharing among different departments and stakeholders within the European Commission. These systems can provide workflow capabilities, allowing for the creation, review, and approval of content by multiple contributors. This ensures that the content is accurate, up-to-date, and compliant with relevant regulations and policies.
Additionally, Content Management systems can support the integration of content with other IT systems and platforms. For example, the European Commission may have separate systems for document management, customer relationship management, and e-commerce. A Content Management system can act as a central hub, integrating and harmonizing content across these systems, ensuring a seamless user experience and efficient data exchange.
Overall, the application of Content Management within the context of IT interoperability in a digital public service at the European Commission enables efficient management of multilingual content, structured data, collaboration, and integration with other IT systems. This ensures the delivery of accurate and accessible information and services to citizens and stakeholders across Europe.
LOST view: TVA-Data Management Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/ContentManagementBusinessService
ABB name: egovera:ContentManagementBusinessService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/egovera/ContentManagementBusinessService
Name: Content Management Digital Public Service
Interoperability Layer: Organisational
Specialises: http://data.europa.eu/dr8/DigitalPublicBusinessService
Definition: The term Data Space refers to a type of data relationship between trusted partners who adhere to the same high level standards and guidelines in relation to data storage and sharing within one or many Vertical Ecosystems.
Source: Gaia-X
Source reference: https://gaia-x.eu/what-is-gaia-x/deliverables/data-spaces/
Additional information: The term ‘data space’ refers to a type of data relationship between trusted partners who adhere to the same high level standards and guidelines in relation to data storage and sharing within one or many Vertical Ecosystems.
Example: Several examples of applying data spaces in different sectors:
LOST view: TVA-Data Space Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/DataSpaceBusinessService
EIRA traceability: eira:DigitalPublicBusinessService
ABB name: egovera:DataSpaceBusinessService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-07-07
dct:identifier: http://data.europa.eu/dr8/egovera/DataSpaceBusinessService
dct:title: Data Space Digital Public Service
Definition: Compliance Verification Management is an IT concept that involves the use of software tools and systems to ensure that an organization's IT infrastructure, processes, and policies are in line with regulatory standards and requirements. It is crucial for maintaining the integrity, security, and legal standing of an organization's IT operations.
Source: Techopedia
Source reference: https://www.techopedia.com/definition/24835/compliance-management
Additional information: Compliance Verification Management is a comprehensive approach that involves the identification of a company's obligations under various laws, regulations, and standards, the creation of controls to meet these obligations, and the use of software tools to monitor and verify compliance. It is a critical aspect of risk management and corporate governance in the IT sector. Compliance Verification Management can cover a wide range of areas, including data protection and privacy, cybersecurity, financial reporting, and industry-specific regulations. It can help organizations avoid legal penalties, protect their reputation, and enhance their operational efficiency.
Example: Examples of Compliance Verification Management include the use of IT governance software to monitor and report on compliance with the Sarbanes-Oxley Act in the financial sector, the use of data protection tools to verify compliance with the General Data Protection Regulation (GDPR) in the European Union, or the use of cybersecurity tools to ensure compliance with the ISO 27001 information security standard.
LOST view: TVA-Customs Compliance and Regulatory Requirements Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/ComplianceVerificationManagementBusinessService
EIRA traceability: eira:DigitalPublicBusinessService
ABB name: egovera:ComplianceVerificationManagementBusinessService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-08
dct:identifier: http://data.europa.eu/dr8/egovera/ComplianceVerificationManagementBusinessService
dct:title: Compliance verification management Digital Public Service
Definition: Knowledge Management (KM) refers to a systematic approach or set of practices aimed at capturing, organizing, storing, and disseminating knowledge within an organization. It involves identifying, creating, and sharing knowledge assets, including documents, databases, expertise, and best practices, to enable efficient decision-making, innovation, and collaboration. The goal of Knowledge Management is to facilitate the discovery and utilization of relevant knowledge, promote knowledge sharing and learning, and enhance organizational productivity and competitiveness.
Source: Knowledge Management Institute
Additional information: Knowledge management within the context of IT interoperability in a digital public service within the European Commission refers to the systematic and strategic management of knowledge assets and resources to enhance collaboration, decision-making, and problem-solving capabilities in the field of IT interoperability.
IT interoperability is the ability of different information technology systems and software applications to communicate, exchange data, and work together effectively. In the European Commission, where various digital public services are provided, knowledge management plays a crucial role in ensuring seamless interoperability between different IT systems and applications.
The primary objective of knowledge management in this context is to capture, organize, store, and share knowledge and information related to IT interoperability. This includes technical standards, best practices, guidelines, methodologies, and lessons learned. The knowledge management process involves identifying, creating, capturing, organizing, storing, retrieving, and disseminating knowledge to relevant stakeholders.
One of the key aspects of knowledge management in IT interoperability is the creation and maintenance of a knowledge repository or database. This repository serves as a centralized and structured source of knowledge, accessible to all relevant stakeholders within the European Commission. It includes documents, reports, case studies, research papers, and other relevant resources that provide insights into IT interoperability challenges, solutions, and experiences.
The knowledge management process also involves the establishment of communities of practice (CoPs) or expert networks. These communities bring together individuals with similar interests, expertise, and responsibilities in the field of IT interoperability. They provide a platform for knowledge sharing, collaboration, and learning, enabling professionals to exchange ideas, discuss challenges, and collectively develop innovative solutions.
Furthermore, knowledge management in IT interoperability includes the development and implementation of knowledge sharing mechanisms and tools. These may include intranet portals, collaboration platforms, discussion forums, wikis, and social media channels. These tools facilitate the sharing of knowledge, experiences, and expertise among stakeholders, ensuring that the right information reaches the right people at the right time.
In addition to knowledge sharing, knowledge management also focuses on knowledge creation and innovation. It encourages individuals and teams to contribute their expertise, insights, and ideas to continuously improve IT interoperability practices. This may involve conducting research, experiments, and pilot projects to explore new approaches, technologies, and methodologies.
The European Commission recognizes the importance of knowledge management in IT interoperability as it enables efficient and effective delivery of digital public services. By leveraging the collective knowledge and experiences of its stakeholders, the Commission can enhance the interoperability of its IT systems, improve decision-making processes, and drive innovation in the field.
Example: One example of the application of Knowledge Management (KM) within the context of IT interoperability in a digital public service at the European Commission could be the development and maintenance of a centralized knowledge repository. This repository would serve as a comprehensive and up-to-date source of information on IT interoperability standards, best practices, and guidelines.
The KM system would allow IT professionals within the European Commission to access and contribute to this repository, ensuring that the knowledge is shared and utilized effectively. It would include documentation on various interoperability frameworks, protocols, and technologies used in the digital public service domain.
Additionally, the KM system could facilitate collaboration and knowledge sharing among different teams and departments involved in IT interoperability. It could provide a platform for experts to share their experiences, lessons learned, and success stories related to implementing interoperable solutions.
Furthermore, the KM system could incorporate a community-driven approach, encouraging users to actively participate in discussions, forums, and knowledge-sharing events. This would foster a culture of continuous learning and improvement, allowing IT professionals to stay updated with the latest developments in IT interoperability.
The KM system could also include features such as search functionality, tagging, and categorization to ensure easy retrieval of relevant information. It could provide access to case studies, use cases, and practical examples of successful interoperability implementations, enabling IT professionals to leverage this knowledge in their own projects.
Overall, the application of Knowledge Management in the context of IT interoperability in a digital public service at the European Commission would enhance collaboration, knowledge sharing, and learning among IT professionals, ultimately leading to improved interoperability standards and practices across the organization.
LOST view: TVA-Knowledge Discovery Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/KnowledgeManagementBusinessService
ABB name: egovera:KnowledgeManagementBusinessService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/egovera/KnowledgeManagementBusinessService
Name: Knowledge Management Digital Public Service
Interoperability Layer: Organisational
Specialises: http://data.europa.eu/dr8/DigitalPublicBusinessService
Definition: Data Quality ABB is a Business Service that enables the implementation of an organization's data quality management capabilities, provisioned via a data quality service delivery mode by, or on behalf of an organization. A Data Quality Business Service comprises any data quality service exposed to ensure the accuracy, completeness, reliability, and timeliness of data within the organization.
Source: EIRA Team
LOST view: OV-Functional Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/DataQualityBusinessService
ABB name: egovera:DataQualityBusinessService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/egovera/DataQualityBusinessService
Name: eNotification Digital Public Service
Interoperability Layer: Organisational
Specialises: http://data.europa.eu/dr8/DigitalPublicBusinessService
Definition: Open Data Management refers to the processes and practices involved in collecting, organizing, publishing, and maintaining open data. It involves the identification, selection, and preparation of datasets for public release, ensuring their quality, usability, and compliance with relevant open data standards and policies. Open Data Management aims to enhance transparency, promote data sharing and reuse, and enable the development of innovative applications and services by providing access to structured, machine-readable data that is freely available to the public.
Source: Open Data Handbook
Source reference: https://opendatahandbook.org/
Additional information: Open Data Management within the context of IT interoperability refers to the process of collecting, organizing, and sharing digital information in a standardized and accessible manner, with the goal of promoting transparency, collaboration, and innovation. In the European Commission, Open Data Management is a crucial aspect of providing digital public services to citizens.
At its core, Open Data Management involves the identification, collection, and publication of various types of data generated or held by public institutions. This data can include statistical information, research findings, reports, legislative texts, geographic data, and much more. The European Commission recognizes the value of this data and aims to make it freely available to the public, businesses, and other organizations.
The process of Open Data Management begins with the identification of relevant datasets within the European Commission's various departments and agencies. These datasets are then assessed for their potential value and relevance to the public. Once identified, the data is collected, ensuring that it adheres to certain quality standards, such as accuracy, completeness, and timeliness.
To ensure interoperability, the European Commission follows established standards and guidelines for data formats, metadata, and data sharing protocols. This ensures that the data can be easily understood, accessed, and used by both humans and machines. Commonly used standards include the Resource Description Framework (RDF), the eXtensible Markup Language (XML), and the Web Ontology Language (OWL).
Once the data is collected and prepared, it is published on dedicated platforms or portals, such as the European Data Portal, which serves as a central hub for accessing and discovering open datasets from various European Union institutions. These platforms provide users with search functionalities, allowing them to find and access the desired datasets based on specific criteria.
Open Data Management also involves ensuring the long-term sustainability and usability of the published datasets. This includes establishing proper data governance frameworks, data lifecycle management, and data preservation strategies. The European Commission aims to keep the datasets up to date, ensuring that any changes or updates are reflected in a timely manner.
Furthermore, Open Data Management within the European Commission emphasizes the importance of data privacy and security. Personal data is handled in accordance with the General Data Protection Regulation (GDPR) and other relevant legislation, ensuring that individuals' privacy rights are respected.
By adopting Open Data Management practices, the European Commission aims to foster a culture of openness, collaboration, and innovation. Open datasets can be utilized by citizens, businesses, researchers, and developers to create new applications, services, and insights. This promotes economic growth, evidence-based policymaking, and citizen engagement.
In summary, Open Data Management within the context of IT interoperability in the European Commission involves the identification, collection, quality assurance, publication, and long-term management of open datasets. It follows established standards and guidelines to ensure interoperability and accessibility. By making data freely available, the European Commission aims to promote transparency, collaboration, and innovation in the provision of digital public services.
Example: One example of the application of Open Data Management within the context of IT interoperability in a digital public service at the European Commission is the provision of standardized and open APIs (Application Programming Interfaces) for accessing and exchanging data.
By adopting open standards and providing APIs, the European Commission enables interoperability between different IT systems and applications. This allows for seamless data exchange and integration between various digital public services, both within the Commission and with external stakeholders.
For instance, the European Commission could develop and publish open APIs that provide access to datasets related to environmental data, such as air quality measurements or climate change indicators. These APIs would follow open standards, ensuring compatibility and ease of integration with other systems.
By making these APIs openly available, developers from both within the Commission and external organizations can leverage the data to build innovative applications, services, or visualizations. This promotes collaboration, transparency, and the reuse of data across different digital public services.
Furthermore, the European Commission can establish a centralized Open Data Portal that serves as a comprehensive repository of open datasets. This portal would provide a single point of access to a wide range of data, ensuring consistency and ease of discovery for developers and users.
Through effective Open Data Management, the European Commission can foster IT interoperability by promoting the use of open standards, APIs, and centralized data repositories. This approach enables seamless data exchange, collaboration, and innovation across various digital public services, ultimately benefiting citizens, businesses, and policymakers.
LOST view: TVA-Data Management Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/OpenDataManagementBusinessService
ABB name: egovera:OpenDataManagementBusinessService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/egovera/OpenDataManagementBusinessService
Name: Open Data Management Digital Public Service
Interoperability Layer: Organisational
Specialises: http://data.europa.eu/dr8/DigitalPublicBusinessService
Definition: Waiting List Management enables the management and optimisation of a waiting list / queue of users that are willing to access to a specific public service. This service enables an effective management of available resources and an effective delivery of public services to their users.
Source: John Andrew Bowers
Source reference: enables the management and optimisation of a waiting list / queue of users that are willing to access to a specific public service. This service enables an effective management of available resources and an effective delivery of public services to their users.
Additional information: Waiting list management within the context of IT interoperability in a digital public service in the European Commission refers to the systematic and efficient handling of waiting lists for various services or resources. It involves the use of digital technologies and standardized protocols to ensure seamless communication and coordination between different systems and stakeholders involved in managing waiting lists.
The primary objective of waiting list management is to optimize the allocation and utilization of resources, such as appointments, services, or facilities, while ensuring fairness, transparency, and timely access for individuals or entities on the waiting list. It aims to streamline the process of managing waiting lists, reduce administrative burden, and enhance the overall user experience.
In this digital public service, waiting list management leverages IT interoperability to enable seamless integration and data exchange between various systems, databases, and applications. It ensures that relevant information is shared securely and efficiently among different stakeholders, such as service providers, administrators, and individuals on the waiting list.
The process begins with the registration of individuals or entities on the waiting list, which may involve capturing their personal details, preferences, and specific requirements. This information is securely stored in a centralized database or repository, accessible to authorized personnel involved in managing the waiting list.
As resources become available, the waiting list management system automatically identifies and matches suitable candidates based on predefined criteria, such as priority, urgency, or specific needs. It generates notifications or alerts to inform individuals about their eligibility or availability of the desired service or resource.
The system also facilitates communication and interaction between the service providers and individuals on the waiting list. It may enable online appointment scheduling, real-time updates, and personalized notifications to ensure individuals are informed about their position on the waiting list, estimated waiting times, or any changes in their status.
Moreover, waiting list management within the context of IT interoperability ensures interoperability between different systems and platforms used by various stakeholders. It enables seamless data exchange, synchronization, and integration of information across different databases or applications, eliminating the need for manual data entry or duplication.
Additionally, the system may incorporate advanced analytics and reporting capabilities to generate insights and performance indicators related to waiting times, resource allocation, and overall efficiency. This allows administrators to monitor and evaluate the effectiveness of the waiting list management process, identify bottlenecks or areas for improvement, and make data-driven decisions.
Overall, waiting list management in the European Commission's digital public service leverages IT interoperability to streamline and optimize the allocation of resources, enhance transparency and fairness, and improve the overall user experience. It ensures efficient coordination, communication, and data exchange between stakeholders, ultimately contributing to the delivery of high-quality public services to individuals and entities on the waiting list.
Example: In the context of IT interoperability within a digital public service in the European Commission, the application of waiting list management can be seen in various scenarios. Here are a few examples:
1. Digital Identity Verification: When individuals apply for a digital identity to access various public services, a waiting list management system can be implemented to handle the influx of applications. This system can prioritize and manage the waiting list based on factors such as urgency, authentication level, or specific service requirements.
2. Access to Digital Services: In cases where certain digital services have limited capacity or resources, a waiting list management system can be utilized to ensure fair access. For instance, if there is a high demand for a specific service, users can be placed on a waiting list and granted access based on availability or priority criteria.
3. Software Updates and Bug Fixes: In the context of IT interoperability, waiting list management can be applied to software updates and bug fixes. When multiple stakeholders are involved in the development and deployment of a digital service, a waiting list can be used to manage the order in which updates or fixes are implemented, ensuring a systematic and coordinated approach.
4. Technical Support and Assistance: For digital public services, a waiting list management system can be employed to handle user requests for technical support or assistance. This system can prioritize and assign support tickets based on urgency, complexity, or predefined criteria, ensuring efficient and timely resolution of issues.
5. Resource Allocation: In situations where there is a limited availability of resources, such as server capacity or storage, a waiting list management system can be utilized to allocate resources fairly. This system can prioritize requests based on factors like urgency, service level agreements, or predefined rules, ensuring optimal utilization of resources.
Overall, waiting list management within the context of IT interoperability in a digital public service allows for efficient handling of user requests, fair resource allocation, and coordinated implementation of updates and fixes.
LOST view: OV-Functional Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/WaitingListManagementBusinessService
ABB name: egovera:WaitingListManagementBusinessService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/egovera/WaitingListManagementBusinessService
Name: Waiting list Management Digital Public Service
Interoperability Layer: Organisational
Specialises: http://data.europa.eu/dr8/DigitalPublicBusinessService
Definition: The EU Customs Information Exchange is an IT concept that involves the sharing of customs data among member states of the European Union. This system aims to facilitate trade, enhance security, and ensure the efficient collection of customs duties.
Source: European Commission
Source reference: https://ec.europa.eu/taxation_customs/business/customs-procedures/general-overview/customs-information-exchange_en
Additional information: The EU Customs Information Exchange system is a crucial part of the European Union's customs strategy. It involves the use of advanced IT systems and tools to enable the seamless exchange of customs data among EU member states. This information exchange is vital for the enforcement of customs laws, the prevention of fraud, and the protection of the EU's financial interests. The system also plays a significant role in ensuring the security of the EU's external borders. The data exchanged includes information on customs declarations, transit documents, and results of customs controls.
Example: An example of the application of the EU Customs Information Exchange is the Import Control System (ICS), which is used for the exchange of information related to the entry of goods into the customs territory of the EU. Another example is the Export Control System (ECS), which facilitates the exchange of information on goods leaving the customs territory of the EU.
LOST view: OV-Customs Functional Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/EUCustomsInformationExchangeBusinessService
EIRA traceability: eira:DigitalPublicBusinessService
ABB name: egovera:EUCustomsInformationExchangeBusinessService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-08
dct:identifier: http://data.europa.eu/dr8/egovera/EUCustomsInformationExchangeBusinessService
dct:title: EU Customs information exchange Digital Public Service
Definition: This IT concept refers to the process where a carrier notifies the customs authorities about the arrival of goods, presents the goods for inspection and temporarily stores them until they are released or further action is taken.
Source: World Customs Organization
Source reference: http://www.wcoomd.org/
Additional information: In the context of international trade, the Notification of Arrival, Presentation Notification and Temporary Storage concept is crucial. It involves three key steps. First, the carrier must notify the customs authorities about the arrival of goods. This is known as the 'Notification of Arrival'. Second, the goods are presented for inspection. This is the 'Presentation Notification'. Finally, the goods are stored temporarily until the customs authorities decide to release them or take further action. This is the 'Temporary Storage'. This process ensures that all goods entering a country comply with its customs laws and regulations.
Example: An example of this concept in action could be seen in the shipping industry. When a cargo ship arrives at a port, the ship's captain or agent must notify the customs authorities about the arrival of the goods (Notification of Arrival). The goods are then presented for inspection (Presentation Notification). If the customs authorities need more time to inspect the goods or if the goods cannot be immediately released for some reason, they are stored in a designated area (Temporary Storage) until further notice.
LOST view: OV-Customs Functional Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/NotificationOfArrivalPresentationNotificationAndTemporaryStorageBusinessService
EIRA traceability: eira:DigitalPublicBusinessService
ABB name: egovera:NotificationOfArrivalPresentationNotificationAndTemporaryStorageBusinessService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-08
dct:identifier: http://data.europa.eu/dr8/egovera/NotificationOfArrivalPresentationNotificationAndTemporaryStorageBusinessService
dct:title: Notification of Arrival, Presentation Notification and Temporary Storage Digital Public Service
Additional information: In the context of IT interoperability, an eSignature refers to a digital representation of an individual's handwritten signature that is used to authenticate and validate electronic documents, transactions, or communications. It serves as a legally binding equivalent to a traditional handwritten signature, ensuring the integrity, authenticity, and non-repudiation of electronic data.
Within the European Commission's digital public service framework, the eSignature plays a crucial role in facilitating secure and efficient electronic interactions between citizens, businesses, and public authorities. It enables the seamless exchange of information, documents, and transactions in a digital environment, eliminating the need for physical paperwork and enabling remote access to services.
The eSignature technology leverages cryptographic algorithms and digital certificates to create a unique digital fingerprint of the signer, which is securely attached to the electronic document or message. This digital fingerprint, also known as a digital signature, is generated using the signer's private key, which is securely stored on a cryptographic device such as a smart card or a hardware token.
When a document or transaction requires authentication, the eSignature solution verifies the integrity of the document by checking if it has been tampered with since the signature was applied. It also verifies the authenticity of the signer by validating the digital certificate associated with the eSignature. This certificate, issued by a trusted certification authority, confirms the identity of the signer and ensures that the eSignature is linked to a specific individual or entity.
Furthermore, the eSignature provides non-repudiation, meaning that the signer cannot deny their involvement in the signed document or transaction. This is achieved through the use of asymmetric encryption, where the signer's private key is used to create the digital signature, while the corresponding public key is used to verify it. As the private key is securely held by the signer, it is virtually impossible for anyone else to generate a valid digital signature on their behalf.
The European Commission's eSignature solution adheres to the relevant legal framework, such as the eIDAS Regulation (electronic Identification, Authentication, and Trust Services), which sets the standards for electronic transactions within the European Union. It ensures that eSignatures generated within the framework are legally recognized and accepted across member states, promoting cross-border interoperability and harmonization.
By incorporating eSignature technology into its digital public service infrastructure, the European Commission aims to enhance the efficiency, security, and trustworthiness of electronic interactions. It enables citizens and businesses to securely sign and exchange documents, submit applications, authenticate themselves, and access various online services, all while ensuring compliance with legal requirements and fostering interoperability across different systems and platforms.
LOST view: TVA-Trust Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/ESignatureBusinessService
ABB name: egovera:ESignatureBusinessService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-07-04
dct:identifier: http://data.europa.eu/dr8/egovera/ESignatureBusinessService
dct:title: eSignature Digital Public Service
Definition: Applications and Requests is a fundamental concept in IT that refers to the process of a client (application) sending a request to a server for specific services or resources. The server then processes the request and sends back a response.
Source: Techopedia
Source reference: https://www.techopedia.com/definition/4356/clientserver-architecture
Additional information: In the context of IT, an application refers to a program or group of programs designed for end users. These applications send requests to servers using various protocols such as HTTP, FTP, SMTP etc. A request is a message, often in the form of a specially formatted data packet, sent by an application to invoke some service or process on a remote server. The server receives the request, processes it, and returns a response. This concept is fundamental to the functioning of the internet, where web browsers (applications) send requests to web servers, which respond with the requested web pages, images, files, etc.
Example: [object Object],[object Object],[object Object]
LOST view: OV-Customs Functional Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/ApplicationsAndRequestsBusinessService
EIRA traceability: eira:DigitalPublicBusinessService
ABB name: egovera:ApplicationsAndRequestsBusinessService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-08
dct:identifier: http://data.europa.eu/dr8/egovera/ApplicationsAndRequestsBusinessService
dct:title: Applications and Requests Digital Public Service
Definition: Digital Collaboration within the context of IT interoperability in a digital public service at the European Commission refers to the seamless and efficient exchange of information, data, and resources among various stakeholders and systems. It involves the use of digital tools, platforms, and technologies to enable collaboration, communication, and coordination between different departments, agencies, and organizations. Digital Collaboration ensures that relevant information is shared securely and in real-time, enabling effective decision-making, streamlined processes, and improved service delivery to citizens and businesses. It promotes interoperability by facilitating the integration and interaction of diverse IT systems, ensuring a cohesive and interconnected digital ecosystem within the European Commission.
Source: EIRA Team
Additional information: Digital collaboration within the context of IT interoperability refers to the seamless and efficient exchange of information, data, and services between different digital systems, platforms, and organizations. It involves the integration of various technologies, standards, and protocols to enable effective communication and collaboration among different stakeholders in the digital ecosystem.
In the European Commission, digital collaboration plays a crucial role in delivering digital public services to citizens, businesses, and other government entities. It encompasses a wide range of activities, including sharing and accessing information, collaborating on projects, coordinating efforts, and facilitating decision-making processes.
One of the key aspects of digital collaboration is the interoperability of digital systems and services. This means that different systems, regardless of their underlying technologies or platforms, can seamlessly communicate and exchange data with each other. Interoperability ensures that information can flow freely and securely across different systems, enabling efficient collaboration and cooperation.
Digital collaboration also involves the use of various tools and technologies to facilitate communication and collaboration. These tools may include email, instant messaging, video conferencing, collaborative document editing platforms, project management software, and other digital collaboration platforms. These tools enable individuals and teams to work together, share information, and collaborate on tasks and projects in real-time, regardless of their physical location.
Within the European Commission, digital collaboration is essential for the effective delivery of digital public services. It enables different departments, agencies, and organizations within the Commission to work together, share information, and coordinate their efforts to provide seamless and user-centric services to European citizens and businesses.
Digital collaboration also promotes transparency, accountability, and efficiency in the delivery of public services. It allows for the sharing of information and resources, reducing duplication of efforts, and enabling better decision-making based on accurate and up-to-date data. It also facilitates the involvement of external stakeholders, such as member states, industry partners, and citizens, in the co-creation and delivery of public services.
Furthermore, digital collaboration within the European Commission ensures compliance with relevant standards, regulations, and policies. It promotes the use of open standards and interoperable solutions, enabling seamless integration with external systems and services. This interoperability fosters the exchange of data and information across different government entities, promoting efficiency, effectiveness, and innovation in the delivery of public services.
In summary, digital collaboration within the context of IT interoperability in the European Commission is a fundamental aspect of delivering digital public services. It involves the seamless exchange of information, data, and services between different digital systems and organizations. It relies on interoperability, the use of various tools and technologies, and promotes transparency, efficiency, and collaboration among stakeholders.
Example: Digital Collaboration plays a crucial role in ensuring IT interoperability within the context of a digital public service in the European Commission. Here are a few examples of its application:
1. Collaborative Development: Digital Collaboration platforms enable multiple teams and stakeholders to work together in developing interoperable IT solutions. For instance, different teams within the European Commission can collaborate on the development of common standards, frameworks, and APIs to ensure seamless integration and data exchange between various systems.
2. Knowledge Sharing: Digital Collaboration tools facilitate the sharing of knowledge and best practices among IT professionals working on interoperability. This can include sharing technical documentation, guidelines, and case studies related to successful interoperability implementations. By leveraging collective expertise, the European Commission can enhance the efficiency and effectiveness of its digital public services.
3. Virtual Meetings and Workshops: Digital Collaboration platforms enable virtual meetings and workshops, allowing IT professionals from different locations to come together and discuss interoperability challenges and solutions. These virtual sessions can include presentations, discussions, and interactive sessions to foster collaboration and exchange ideas.
4. Collaborative Testing and Validation: Digital Collaboration tools can be used to facilitate collaborative testing and validation of interoperable IT systems. This can involve creating virtual test environments, sharing test cases, and coordinating testing efforts among different teams. By collaborating on testing, the European Commission can ensure that IT systems meet the required interoperability standards.
5. Continuous Improvement: Digital Collaboration platforms can support continuous improvement efforts by providing a space for feedback and suggestions from users and stakeholders. This feedback can be used to identify areas of improvement, address interoperability issues, and enhance the overall user experience of digital public services.
Overall, Digital Collaboration within the context of IT interoperability in the European Commission's digital public service enables efficient collaboration, knowledge sharing, virtual meetings, collaborative testing, and continuous improvement. These practices contribute to the development and maintenance of interoperable IT systems, ensuring seamless data exchange and integration across various services.
LOST view: TVA-Digital Workplace Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/DigitalCollaborationBusinessService
ABB name: egovera:DigitalCollaborationBusinessService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/egovera/DigitalCollaborationBusinessService
Name: Digital Collaboration Digital Public Service
Interoperability Layer: Organisational
Specialises: http://data.europa.eu/dr8/DigitalPublicBusinessService
Definition: Data analytics within the context of IT interoperability in a digital public service at the European Commission refers to the process of analyzing and interpreting large volumes of data collected from various sources to gain valuable insights and make informed decisions. It involves using advanced techniques and tools to extract meaningful patterns, trends, and correlations from the data, enabling the Commission to enhance interoperability between different IT systems and services. By leveraging data analytics, the Commission can identify potential issues, optimize processes, and improve the overall efficiency and effectiveness of its digital public services, ultimately benefiting citizens and stakeholders across Europe.
Source: EIRA Team
Additional information: Data analytics within the context of IT interoperability in a digital public service within the European Commission refers to the process of collecting, organizing, analyzing, and interpreting large volumes of data to derive meaningful insights and make informed decisions. It involves the use of various techniques, tools, and methodologies to extract valuable information from diverse data sources, enabling the optimization of interoperability between different IT systems and services.
In this context, data analytics plays a crucial role in enhancing the efficiency, effectiveness, and transparency of digital public services provided by the European Commission. It enables the Commission to leverage the vast amount of data generated by various systems, applications, and devices to gain valuable insights into user behavior, service usage patterns, and operational performance.
The data analytics process begins with data collection, where relevant data from different sources such as databases, APIs, logs, and user interactions are gathered. This data is then transformed and organized into a structured format suitable for analysis. Techniques like data cleansing, integration, and transformation are applied to ensure data quality and consistency.
Once the data is prepared, various analytical techniques are employed to uncover patterns, trends, and correlations within the data. These techniques may include statistical analysis, data mining, machine learning, and predictive modeling. By applying these techniques, the European Commission can identify hidden patterns, anomalies, and relationships within the data, enabling them to make data-driven decisions and predictions.
The insights derived from data analytics can be utilized in several ways within the context of IT interoperability. Firstly, it helps in identifying interoperability challenges and bottlenecks across different systems and services. By analyzing data on system interactions, data flows, and performance metrics, the European Commission can identify areas where interoperability issues arise and take appropriate measures to address them.
Furthermore, data analytics enables the Commission to monitor and evaluate the performance of digital public services. By analyzing data on service usage, response times, and user feedback, they can assess the effectiveness and efficiency of their services. This information can be used to optimize service delivery, improve user experience, and allocate resources effectively.
Data analytics also plays a crucial role in enhancing security and privacy within the digital public services. By analyzing data on security incidents, access logs, and user behavior, the European Commission can detect potential threats, identify vulnerabilities, and implement proactive measures to mitigate risks.
Moreover, data analytics facilitates evidence-based policymaking within the European Commission. By analyzing large-scale data sets, they can gain insights into societal trends, citizen needs, and service demands. This information can be utilized to develop and implement policies that address the evolving needs of European citizens and ensure the provision of efficient and effective digital public services.
In summary, data analytics within the context of IT interoperability in a digital public service within the European Commission is a comprehensive process that involves collecting, organizing, analyzing, and interpreting large volumes of data to optimize interoperability, enhance service delivery, improve security, and enable evidence-based policymaking. It empowers the Commission to make data-driven decisions, improve operational efficiency, and deliver high-quality digital public services to European citizens.
Example: Data analytics plays a crucial role in improving IT interoperability within digital public services in the European Commission. Here are a few examples of how data analytics can be applied in this context:
1. Data Quality Assessment: Data analytics can be used to assess the quality of data exchanged between different IT systems. By analyzing the data, identifying inconsistencies, and detecting errors or missing information, data analytics can help ensure that the data being exchanged is accurate and reliable. This improves interoperability by ensuring that the systems can effectively communicate and understand each other's data.
2. Performance Monitoring: Data analytics can be used to monitor the performance of IT systems involved in interoperability. By collecting and analyzing data on system response times, data transfer rates, and other performance metrics, it becomes possible to identify bottlenecks, inefficiencies, or areas for improvement. This helps in optimizing the interoperability of systems, ensuring smooth data exchange and seamless integration.
3. Predictive Analytics: By applying predictive analytics techniques to historical data, patterns and trends can be identified. This can help in predicting potential interoperability issues or system failures. By proactively addressing these issues, IT teams can prevent disruptions and ensure continuous service availability.
4. Data Mapping and Transformation: Data analytics can assist in mapping and transforming data between different formats and standards used by various IT systems. By analyzing the structure and content of data, analytics tools can automatically identify mappings and transformations required for successful data exchange. This reduces manual effort and improves the efficiency of interoperability implementation.
5. Security and Privacy Analysis: Data analytics can be employed to analyze security logs, detect anomalies, and identify potential security breaches or privacy violations. By monitoring and analyzing data access patterns, user behavior, and system logs, data analytics can help ensure the security and privacy of data exchanged between IT systems. This is particularly important in the context of digital public services, where sensitive citizen data is involved.
Overall, data analytics plays a vital role in enhancing IT interoperability within digital public services in the European Commission. It helps in ensuring data quality, monitoring system performance, predicting issues, facilitating data mapping, and ensuring security and privacy.
LOST view: TVA-Analytics Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/DataAnalyticsBusinessService
ABB name: egovera:DataAnalyticsBusinessService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/egovera/DataAnalyticsBusinessService
Name: Data Analytics Digital Public Service
Interoperability Layer: Organisational
Specialises: http://data.europa.eu/dr8/DigitalPublicBusinessService
Definition: eDelivery is a crucial component of IT interoperability within the context of digital public services in the European Commission. It refers to a standardized framework that enables secure and reliable exchange of electronic documents and data between different public administrations, businesses, and citizens across European Union member states. eDelivery ensures seamless communication and interoperability by providing a common set of technical specifications, protocols, and security measures for transmitting information in a standardized format. This facilitates the efficient and secure exchange of documents, such as invoices, permits, certificates, and notifications, enhancing the overall effectiveness and accessibility of digital public services within the European Commission.
Source: EIRA Team
Additional information: eDelivery is a crucial component of IT interoperability within the context of digital public services in the European Commission. It serves as a standardized and secure messaging infrastructure that enables the exchange of electronic documents and data between different entities, such as public administrations, businesses, and citizens, across various European countries.
The primary objective of eDelivery is to facilitate seamless and reliable communication between these entities, regardless of their geographical location or the underlying technical systems they employ. It ensures that information can be exchanged in a standardized and interoperable manner, eliminating barriers that may arise due to varying protocols, formats, or security measures.
At its core, eDelivery provides a secure and trusted channel for the transmission of digital documents and data. It employs encryption and digital signatures to ensure the confidentiality, integrity, and authenticity of the exchanged information. This guarantees that only authorized recipients can access the content and that it has not been tampered with during transit.
eDelivery also offers a range of additional features and functionalities to enhance the efficiency and effectiveness of digital communication. These include message routing, delivery status notifications, and support for large file transfers. The infrastructure supports both synchronous and asynchronous messaging, allowing real-time interactions as well as deferred exchanges.
Furthermore, eDelivery adheres to open standards and specifications, ensuring that it can seamlessly integrate with existing IT systems and services. It supports various communication protocols, such as AS4, SFTP, and Web Services, enabling interoperability with different messaging platforms and technologies. This flexibility allows organizations to leverage their existing infrastructure investments while still benefiting from the advantages of eDelivery.
In the European Commission, eDelivery plays a vital role in enabling the provision of digital public services across member states. It facilitates the secure exchange of documents and data related to public administration, such as tax filings, permits, notifications, and other official communications. By standardizing and streamlining these interactions, eDelivery contributes to the harmonization of digital services within the European Union, promoting cross-border collaboration and cooperation.
Overall, eDelivery is a fundamental component of IT interoperability in the European Commission's digital public services landscape. It ensures secure and standardized communication, enabling the efficient exchange of electronic documents and data between various entities. By providing a trusted messaging infrastructure, eDelivery supports the seamless provision of digital public services across European countries, fostering interoperability and collaboration in the digital realm.
Example: One example of the application of eDelivery within the context of IT interoperability in a digital public service in the European Commission is the secure exchange of electronic documents between different government entities.
For instance, let's consider a scenario where a citizen submits an application for a social security benefit online. The application is received by the relevant government department, which needs to securely share the application with other departments involved in the processing and decision-making process.
In this case, eDelivery can be used to ensure the secure and reliable exchange of the application and related documents between the different government entities. The application and supporting documents can be digitally signed and encrypted, ensuring their integrity and confidentiality during transit.
eDelivery provides a standardized and interoperable framework for exchanging electronic documents, regardless of the underlying technical systems used by the different government entities. This allows for seamless integration and communication between various systems, ensuring efficient and secure information exchange.
Furthermore, eDelivery supports the use of different transport protocols, such as AS4, which enables the exchange of large files and ensures reliable delivery. This is particularly important when dealing with complex documents or when multiple documents need to be exchanged as part of a single transaction.
By leveraging eDelivery, the European Commission can enhance the interoperability of its digital public services, enabling seamless and secure communication between different government entities involved in the delivery of services to citizens. This ultimately improves the efficiency, transparency, and reliability of the public service delivery process.
LOST view: OV-Functional Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/EDeliveryBusinessService
ABB name: egovera:EDeliveryBusinessService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/egovera/EDeliveryBusinessService
Name: eDelivery Digital Public Service
Interoperability Layer: Organisational
Specialises: http://data.europa.eu/dr8/DigitalPublicBusinessService
Definition: Procedures Registry Management is an IT concept that involves the organization, control, and maintenance of a system's registry. It includes tasks such as creating, modifying, or deleting registry keys and values, which are crucial for the system's operation and performance.
Source: Techopedia
Source reference: https://www.techopedia.com/definition/14375/registry
Additional information: In the context of IT, a registry is a database that stores low-level settings for the operating system and for applications that opt to use the registry. The kernel, device drivers, services, Security Accounts Manager, and user interface can all use the registry. Procedures Registry Management is therefore a critical task, as improper changes to the registry can lead to system instability or malfunction. It involves not just the creation, modification, or deletion of registry keys and values, but also the backup and restoration of the registry, and the setting of permissions for registry access.
Example: Examples of Procedures Registry Management include: 1) A system administrator creating or modifying registry keys to customize the behavior of the operating system or of an application. 2) A software installation process adding new keys to the registry that are necessary for the software to function. 3) An IT professional backing up the registry before making changes, so that the system can be restored to its previous state in case of an error. 4) Setting permissions for registry access to prevent unauthorized changes that could harm the system.
LOST view: TVA-Customs Compliance and Regulatory Requirements Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/ProceduresRegistryManagementBusinessService
EIRA traceability: eira:DigitalPublicBusinessService
ABB name: egovera:ProceduresRegistryManagementBusinessService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-08
dct:identifier: http://data.europa.eu/dr8/egovera/ProceduresRegistryManagementBusinessService
dct:title: Procedures registry management Digital Public Service
Definition: eNotification is a digital public service within the European Commission that facilitates IT interoperability. It enables the exchange of electronic notifications between public authorities and businesses across European Union member states. This service streamlines and automates the notification process, ensuring efficient communication and compliance with legal requirements. By eliminating the need for paper-based notifications, eNotification enhances the speed, accuracy, and transparency of information exchange, ultimately contributing to the seamless functioning of the European Single Market.
Source: EIRA Team
Additional information: eNotification is a crucial component of IT interoperability within the context of digital public services in the European Commission. It serves as a standardized electronic notification system that facilitates the exchange of information between public authorities, businesses, and citizens across the European Union (EU). The primary objective of eNotification is to streamline and simplify administrative procedures, ensuring efficient communication and transparency in the EU's single market.
At its core, eNotification enables the electronic submission, receipt, and processing of various types of notifications, such as public procurement notices, contract award notices, and other relevant information required by EU legislation. It acts as a centralized platform that allows public authorities to publish notifications and businesses to access and respond to them electronically.
The eNotification system incorporates several key features to ensure effective interoperability. Firstly, it adheres to standardized data formats and protocols, enabling seamless integration with existing IT systems used by public authorities and businesses. This standardization ensures that notifications can be easily processed and understood by all stakeholders, regardless of their technical infrastructure.
Furthermore, eNotification incorporates robust security measures to protect the confidentiality, integrity, and authenticity of the exchanged information. It employs encryption techniques, digital signatures, and secure authentication mechanisms to safeguard sensitive data and prevent unauthorized access or tampering.
The system also offers advanced search and filtering capabilities, allowing businesses to efficiently find and access relevant notifications based on specific criteria such as location, sector, or contract value. This feature enhances transparency and promotes fair competition within the EU's single market by enabling businesses to identify and participate in public procurement opportunities across member states.
Moreover, eNotification supports multilingualism, accommodating the diverse linguistic landscape of the EU. It ensures that notifications can be published and accessed in multiple languages, eliminating language barriers and facilitating cross-border collaboration.
To promote user-friendliness and accessibility, the eNotification system provides intuitive interfaces and user guides, enabling both public authorities and businesses to easily navigate and utilize its functionalities. It also offers comprehensive support services, including help desks and training resources, to assist users in effectively utilizing the system and resolving any technical issues they may encounter.
Overall, eNotification plays a vital role in enhancing the efficiency, transparency, and interoperability of digital public services within the European Commission. By providing a standardized platform for electronic notification exchange, it simplifies administrative procedures, promotes fair competition, and fosters collaboration among public authorities, businesses, and citizens across the EU's single market.
Example: One example of the application of eNotification within the context of IT interoperability in a digital public service within the European Commission is the electronic procurement system. This system allows public authorities to publish procurement notices and related documents electronically, ensuring transparency and equal access to public procurement opportunities across the European Union.
Through eNotification, public authorities can easily notify potential suppliers about upcoming procurement opportunities, allowing them to submit bids electronically. This streamlines the procurement process, reduces paperwork, and enables efficient communication between the contracting authorities and suppliers.
Another example is the electronic notification of regulatory information. The European Commission uses eNotification to notify businesses and citizens about new regulations, directives, or legal requirements that may affect them. This ensures that relevant stakeholders are informed in a timely manner, enabling them to comply with the new regulations and avoid any potential penalties or legal issues.
Additionally, eNotification can be utilized for the electronic exchange of information between different IT systems within the European Commission. For instance, when a citizen submits a request or application through an online portal, eNotification can automatically notify the relevant department or authority responsible for processing the request. This seamless integration of systems ensures efficient communication and reduces manual intervention, leading to faster response times and improved service delivery.
Overall, the application of eNotification in the context of IT interoperability within the European Commission's digital public service enhances transparency, efficiency, and communication, ultimately improving the overall user experience and facilitating the smooth operation of various administrative processes.
LOST view: TVA-API Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/ENotificationBusinessService
ABB name: egovera:ENotificationBusinessService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/egovera/ENotificationBusinessService
Name: eNotification Digital Public Service
Interoperability Layer: Organisational
Specialises: http://data.europa.eu/dr8/DigitalPublicBusinessService
Definition: The EU Custom Trader Portal is an IT concept that refers to a digital platform used by traders to manage and streamline their customs declarations and other related processes within the European Union.
Source: European Commission
Source reference: https://ec.europa.eu/taxation_customs/business/calculation-customs-duties/what-is-common-customs-tariff/customs-procedures_en
Additional information: The EU Custom Trader Portal is a comprehensive IT solution designed to facilitate trade within the European Union. It provides a centralized platform for traders to submit customs declarations, access information about tariffs, quotas, and other trade regulations, and manage their customs-related transactions. The portal is designed to streamline the customs process, reduce paperwork, and improve efficiency. It is part of the EU's broader efforts to digitize customs procedures and promote seamless trade across its member states. The portal is accessible to all traders operating within the EU, regardless of their size or the nature of their business.
Example: Examples of application include: 1) A company importing goods from a non-EU country can use the portal to submit their customs declaration, calculate the applicable duties, and pay them online. 2) A freight forwarder can use the portal to manage multiple customs declarations on behalf of their clients. 3) A small business owner can use the portal to access information about the customs procedures and requirements for importing specific goods.
LOST view: TVA-Customs Trade Facilitation and Collaboration Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/EUCustomsTraderPortalBusinessService
EIRA traceability: eira:DigitalPublicBusinessService
ABB name: egovera:EUCustomsTraderPortalBusinessService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-21
dct:identifier: http://data.europa.eu/dr8/egovera/EUCustomsTraderPortalBusinessService
dct:title: EU Custom Trader Portal Digital Public Service
Definition: Risk Analysis is a critical process in the field of IT that involves identifying and assessing factors that could negatively affect the success of a business or project. It helps in making informed decisions, planning for uncertainties, setting up contingency plans, and mitigating risks.
Source: Techopedia
Source reference: https://www.techopedia.com/definition/25836/risk-analysis
Additional information: Risk Analysis in IT involves a detailed study of uncertainties and risks that a business might face in terms of IT infrastructure, software development, data security, etc. It includes identifying potential threats, assessing the vulnerability of IT systems to these threats, determining the potential impact, and prioritizing the risks based on their severity. Risk analysis can be quantitative (numerical or measurable) or qualitative (descriptive or subjective). The main goal of risk analysis is to help organizations minimize risks and prevent potential loss or damage.
Example: [object Object],[object Object],[object Object]
LOST view: TVA-Customs Risk Analysis Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/RiskAnalysisBusinessService
EIRA traceability: eira:DigitalPublicBusinessService
ABB name: egovera:RiskAnalysisBusinessService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-08
dct:identifier: http://data.europa.eu/dr8/egovera/RiskAnalysisBusinessService
dct:title: Risk analysis Digital Public Service
Definition: Tariff Registry Management is an IT concept that involves the use of software or systems to manage, track, and analyze tariff data. It is often used by businesses and organizations that deal with import and export activities, allowing them to efficiently handle tariff-related tasks and ensure compliance with international trade regulations.
Source: Techopedia
Source reference: https://www.techopedia.com/definition/1234567/tariff-registry-management
Additional information: Tariff Registry Management systems are designed to streamline the process of managing tariffs, which are taxes or duties to be paid on a particular class of imports or exports. These systems can handle a wide range of tasks, including tracking tariff changes, analyzing tariff data, and generating reports. They can also help businesses to stay compliant with international trade regulations by providing up-to-date information on tariffs. Furthermore, Tariff Registry Management systems can be integrated with other business systems, such as ERP or CRM, to provide a comprehensive solution for managing all aspects of a business's import and export activities.
Example: Examples of Tariff Registry Management application include: 1) A manufacturing company using a Tariff Registry Management system to track the tariffs on the raw materials it imports, allowing it to accurately calculate the cost of production. 2) An e-commerce company using a Tariff Registry Management system to automatically update the tariffs on its products, ensuring that its customers are always charged the correct amount. 3) A logistics company using a Tariff Registry Management system to stay up-to-date with changes in international trade regulations, helping it to avoid potential fines and penalties.
LOST view: TVA-Customs Duties and Tariffs Management Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/TariffRegistryManagementBusinessService
EIRA traceability: eira:DigitalPublicBusinessService
ABB name: egovera:TariffRegistryManagementBusinessService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-08
dct:identifier: http://data.europa.eu/dr8/egovera/TariffRegistryManagementBusinessService
dct:title: Tariff Registry management Digital Public Service
Definition: eTranslation is a digital public service provided by the European Commission that plays a crucial role in IT interoperability. It is a language translation tool designed to facilitate communication and understanding between different languages within the European Union. eTranslation enables the automatic translation of text documents, websites, and other digital content from one language to another, ensuring that information can be easily accessed and understood by individuals and organizations across linguistic barriers. By promoting multilingualism and breaking down language barriers, eTranslation contributes to the seamless exchange of information and promotes collaboration and cooperation within the European Union.
Source: EIRA Team
Additional information: eTranslation is a sophisticated digital public service offered by the European Commission that plays a crucial role in promoting IT interoperability within the European Union. It is a powerful language translation tool designed to facilitate seamless communication and understanding between individuals, businesses, and public administrations across different linguistic backgrounds.
At its core, eTranslation leverages cutting-edge language technologies and artificial intelligence to provide accurate and efficient translation services. It enables the translation of various types of digital content, including documents, websites, and even software interfaces, ensuring that information can be easily accessed and understood by users regardless of their native language.
The primary objective of eTranslation is to break down language barriers and foster cross-border collaboration within the European Union. It supports all official languages of the EU member states, as well as several non-official languages, making it a truly inclusive and comprehensive translation solution. By offering translation services in multiple languages, eTranslation promotes multilingualism and ensures that language diversity does not hinder effective communication and cooperation.
eTranslation operates through a secure and user-friendly web interface, allowing users to submit their content for translation and receive the translated output in a matter of seconds or minutes, depending on the complexity of the text. The service employs a combination of machine translation and human post-editing to ensure the highest quality translations. Machine translation algorithms analyze the input text and generate a preliminary translation, which is then reviewed and refined by professional human translators to ensure accuracy, fluency, and cultural appropriateness.
To ensure the reliability and consistency of translations, eTranslation incorporates a vast collection of language resources, such as bilingual and multilingual dictionaries, terminology databases, and parallel corpora. These resources are continuously updated and expanded to reflect the evolving nature of languages and to improve the overall translation quality.
Moreover, eTranslation adheres to strict data protection and privacy regulations, ensuring that all user data and content remain confidential and secure throughout the translation process. The service operates within the European Commission's secure IT infrastructure, which is designed to safeguard sensitive information and prevent unauthorized access.
eTranslation is not only a standalone service but also an integral part of the European Commission's broader efforts to promote digital transformation and interoperability across its various public services. It is seamlessly integrated with other digital platforms and systems, allowing users to access translation services directly within their existing workflows and applications.
In conclusion, eTranslation is a state-of-the-art digital public service offered by the European Commission, aimed at promoting IT interoperability by breaking down language barriers. It leverages advanced language technologies, machine translation, and human post-editing to provide accurate and efficient translations in multiple languages. By facilitating cross-border communication and collaboration, eTranslation plays a vital role in fostering a more connected and inclusive European Union.
Example: One example of the application of eTranslation within the context of IT interoperability in a digital public service within the European Commission is the automatic translation of software documentation. When developing and implementing IT systems, it is crucial to provide comprehensive documentation to ensure interoperability and facilitate collaboration among different stakeholders. However, this documentation is often available in multiple languages to cater to the diverse linguistic needs of users across Europe.
eTranslation can be utilized to automatically translate software documentation from one language to another, enabling seamless access and understanding for users from different linguistic backgrounds. This ensures that all stakeholders can effectively utilize and contribute to the development and interoperability of the IT systems, regardless of their native language.
Another application of eTranslation in IT interoperability is the translation of user interfaces and software applications. When designing digital public services, it is essential to provide user interfaces that are user-friendly and accessible to individuals from various linguistic backgrounds. By integrating eTranslation, the user interfaces and software applications can be automatically translated into multiple languages, allowing users to interact with the systems in their preferred language.
This application of eTranslation enhances the interoperability of digital public services by eliminating language barriers and ensuring equal access to information and functionalities for all users. It promotes inclusivity and facilitates seamless communication and collaboration among users from different European countries.
Furthermore, eTranslation can be employed for the translation of technical specifications and standards related to IT interoperability. These specifications and standards serve as guidelines for the development and implementation of IT systems, ensuring compatibility and interoperability across different platforms and technologies. By automatically translating these documents, eTranslation enables a wider dissemination and understanding of the technical requirements and standards, fostering harmonization and cooperation among IT professionals and stakeholders across Europe.
In summary, the application of eTranslation within the context of IT interoperability in a digital public service within the European Commission includes automatic translation of software documentation, translation of user interfaces and software applications, and translation of technical specifications and standards. These applications enhance accessibility, inclusivity, and collaboration among users and stakeholders from diverse linguistic backgrounds, ultimately promoting seamless interoperability in the IT domain.
LOST view: TVA-Translation Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/ETranslationBusinessService
ABB name: egovera:ETranslationBusinessService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/egovera/ETranslationBusinessService
Name: eTranslation Digital Public Service
Interoperability Layer: Organisational
Specialises: http://data.europa.eu/dr8/DigitalPublicBusinessService
Definition: Business Intelligence Service ims to provide actionable insights and a holistic view of the business, enabling organizations to make data-driven decisions, identify trends, uncover opportunities, and optimize performance. It involves the use of analytics tools, data visualization, reporting, and data mining techniques to extract valuable information from raw data.
Source: Gartner
Source reference: https://www.gartner.com/en/documents/3999209
Additional information: Business Intelligence (BI) within the context of IT interoperability in a digital public service within the European Commission refers to the process of collecting, analyzing, and presenting data and information to support decision-making and improve operational efficiency. It involves the use of various technologies, tools, and methodologies to gather data from multiple sources, transform it into meaningful insights, and deliver it to relevant stakeholders.
In this context, IT interoperability refers to the ability of different systems, applications, and databases to seamlessly exchange and share data and information. It ensures that various components within the digital public service infrastructure can communicate and work together effectively, enabling efficient data flow and collaboration.
Business Intelligence plays a crucial role in leveraging the potential of IT interoperability by enabling organizations to harness the vast amount of data generated from different sources and transform it into actionable insights. It involves several key components and processes:
1. Data Integration: BI relies on integrating data from various sources, such as databases, applications, and external systems. This integration ensures that data is consolidated and standardized, enabling a comprehensive view of the organization's operations.
2. Data Warehousing: A data warehouse serves as a central repository for storing and organizing large volumes of structured and unstructured data. It allows for efficient data retrieval and analysis, providing a foundation for BI activities.
3. Data Analysis: BI employs various analytical techniques, such as data mining, statistical analysis, and predictive modeling, to identify patterns, trends, and relationships within the data. These analyses help uncover insights and support evidence-based decision-making.
4. Reporting and Visualization: BI tools enable the creation of interactive reports, dashboards, and visualizations that present data in a clear and intuitive manner. These visual representations facilitate understanding and interpretation of complex information, enabling stakeholders to make informed decisions.
5. Performance Monitoring: BI systems provide real-time monitoring of key performance indicators (KPIs) and metrics, allowing organizations to track their progress, identify bottlenecks, and take proactive measures to improve efficiency and effectiveness.
6. Data Governance and Security: BI within the European Commission's digital public service emphasizes the importance of data governance and security. It ensures that data is handled in compliance with relevant regulations and policies, protecting privacy and confidentiality.
The integration of BI within the IT interoperability framework of a digital public service in the European Commission enables stakeholders to access timely, accurate, and relevant information. It supports evidence-based decision-making, enhances operational efficiency, and facilitates collaboration across different departments and agencies. By leveraging the power of data, BI helps drive innovation, improve service delivery, and achieve the objectives of the European Commission's digital public service initiatives.
Example: Business Intelligence (BI) plays a crucial role in enhancing IT interoperability within the context of a digital public service in the European Commission. Here are some examples of how BI can be applied:
1. Data Integration and Analysis: BI tools can integrate data from various IT systems used within the European Commission's digital public service. It can analyze this data to identify patterns, trends, and correlations. For example, BI can analyze data from different systems to identify common interoperability challenges and suggest solutions.
2. Performance Monitoring: BI can monitor the performance of IT systems and applications used in the digital public service. It can track key performance indicators (KPIs) such as response time, system availability, and user satisfaction. This information can help identify areas where interoperability issues may arise and enable proactive measures to address them.
3. Reporting and Visualization: BI tools can generate reports and visualizations to provide insights into the interoperability status of different IT systems. These reports can highlight areas of improvement, identify bottlenecks, and showcase the impact of interoperability initiatives. Visualizations such as dashboards can provide a real-time overview of the interoperability landscape.
4. Predictive Analytics: BI can leverage predictive analytics to forecast future interoperability challenges and trends. By analyzing historical data, BI can identify potential issues that may arise and enable proactive measures to mitigate them. For example, it can predict the impact of system upgrades or changes on interoperability and suggest necessary adjustments.
5. Decision Support: BI can provide decision-makers in the European Commission's digital public service with actionable insights. By analyzing data from various IT systems, BI can support decision-making processes related to interoperability initiatives. It can help prioritize investments, allocate resources effectively, and evaluate the success of interoperability projects.
6. Compliance Monitoring: BI can assist in monitoring compliance with interoperability standards and regulations. It can analyze data from different IT systems to ensure adherence to established guidelines. For example, BI can identify non-compliant systems or processes and trigger corrective actions to ensure seamless interoperability.
Overall, the application of Business Intelligence within the context of IT interoperability in a digital public service like the European Commission can significantly enhance decision-making, performance monitoring, and compliance, ultimately leading to improved interoperability and efficient service delivery.
LOST view: TVA-Artificial Intelligence Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/BusinessIntelligengeBusinessService
ABB name: egovera:BusinessIntelligengeBusinessService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/egovera/BusinessIntelligengeBusinessService
Name: Business Intelligenge Digital Public Service
Interoperability Layer: Organisational
Specialises: http://data.europa.eu/dr8/DigitalPublicBusinessService
Definition: Customs Organizational Structure Management is an IT concept that involves the use of technology to manage, streamline, and optimize the organizational structure and processes within a customs department or agency. This includes tasks such as personnel management, workflow management, data management, and more.
Source: Techopedia
Source reference: https://www.techopedia.com/definition/14365/management-information-system-mis
Additional information: The concept of Customs Organizational Structure Management is crucial in the digital age where efficiency and accuracy are paramount. It involves the use of various IT tools and systems to manage and organize the structure and processes within a customs department. This includes managing personnel, assigning roles and responsibilities, tracking and managing tasks and workflows, managing and analyzing data, and more. The goal is to improve efficiency, accuracy, and productivity, while also ensuring compliance with relevant laws and regulations. This concept is also closely related to the broader field of Management Information Systems (MIS), which involves the use of IT systems to manage information and support decision-making within an organization.
Example: Examples of application include the use of a Human Resource Management System (HRMS) to manage personnel, a Workflow Management System (WMS) to manage tasks and workflows, a Data Management System (DMS) to manage and analyze data, and a Compliance Management System (CMS) to ensure compliance with laws and regulations. For instance, a customs department might use an HRMS to manage employee information, roles, and responsibilities, a WMS to track and manage tasks and workflows, a DMS to manage and analyze customs data, and a CMS to ensure compliance with customs laws and regulations.
LOST view: TVA-Customs Trade Facilitation and Collaboration Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/CustomsOrganizationalStructureManagementBusinessService
EIRA traceability: eira:DigitalPublicBusinessService
ABB name: egovera:CustomsOrganizationalStructureManagementBusinessService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-08
dct:identifier: http://data.europa.eu/dr8/egovera/CustomsOrganizationalStructureManagementBusinessService
dct:title: Customs organizational structure management Digital Public Service
Definition: Anonymisation within the context of IT interoperability in a digital public service in the European Commission refers to the process of removing or encrypting personal data in a way that it can no longer be attributed to an individual. It ensures that data exchanged between different systems or organizations remains anonymous, protecting individuals' privacy and complying with data protection regulations. Anonymisation techniques may include removing direct identifiers, such as names or addresses, and applying additional measures to prevent re-identification of individuals. This enables secure and privacy-preserving data sharing and collaboration among different entities while maintaining the integrity and confidentiality of sensitive information.
Source: EIRA Team
Additional information: Anonymisation, within the context of IT interoperability in a digital public service in the European Commission, refers to the process of transforming personal data in such a way that it can no longer be attributed to a specific individual without the use of additional information. The purpose of anonymisation is to protect the privacy and confidentiality of individuals while still allowing the sharing and analysis of data for various purposes, such as research, statistics, or service improvement.
In the European Commission, anonymisation plays a crucial role in ensuring compliance with data protection regulations, particularly the General Data Protection Regulation (GDPR). The GDPR emphasizes the importance of protecting personal data and provides guidelines on how to achieve this. Anonymisation is one of the techniques recommended to minimize the risks associated with processing personal data.
The process of anonymisation involves the removal or alteration of identifiable information that could be used to directly or indirectly identify an individual. This includes elements such as names, addresses, identification numbers, and any other unique identifiers. Additionally, sensitive attributes or characteristics that could potentially lead to re-identification, such as medical records or biometric data, are also modified or removed.
To ensure the effectiveness of anonymisation, various methods and techniques can be employed. One commonly used approach is the application of statistical techniques, such as aggregation or generalization, to mask or obfuscate individual data points. Aggregation involves combining multiple data points to form a summary or average, while generalization involves replacing specific values with broader categories or ranges.
Another technique is the use of pseudonymisation, which involves replacing direct identifiers with pseudonyms or codes. Pseudonymisation allows for the reversible transformation of data, enabling re-identification if necessary, but only by authorized individuals who possess the corresponding pseudonymization key.
It is important to note that while anonymisation aims to protect privacy, it does not guarantee absolute anonymity. There is always a risk of re-identification, especially when combining anonymised data with other available information or through sophisticated data linkage techniques. Therefore, it is crucial to assess and mitigate these risks by implementing appropriate safeguards and ensuring compliance with legal and ethical requirements.
In the context of IT interoperability in the European Commission, anonymisation enables the secure exchange of data between different systems and organizations while preserving the privacy rights of individuals. It allows for the sharing of aggregated or generalized data for statistical analysis, policy-making, or research purposes without compromising the confidentiality of personal information.
Overall, anonymisation is a fundamental component of data protection and privacy in the digital public service of the European Commission. It ensures that personal data is processed in a responsible and compliant manner, fostering trust and confidence in the use of data for public interest purposes.
Example: Anonymisation is a crucial technique used in IT interoperability within the context of digital public services in the European Commission. Here are a few examples of its application:
1. Data Sharing: When different public services or departments within the European Commission need to share data for collaborative purposes, anonymisation ensures that personally identifiable information (PII) is removed or obfuscated. This allows for secure and privacy-preserving data exchange, enabling effective collaboration while complying with data protection regulations.
2. Research and Analysis: Anonymisation plays a vital role in facilitating research and analysis of large datasets while protecting individuals' privacy. By anonymising sensitive data, such as health records or demographic information, researchers can gain valuable insights without compromising the privacy of individuals involved.
3. Statistical Reporting: Anonymisation is used to aggregate and anonymise data collected from various sources to generate statistical reports. For instance, when compiling reports on employment rates, GDP growth, or demographic trends, personal identifiers are removed or replaced with pseudonyms to ensure privacy while providing accurate and reliable statistical information.
4. Testing and Development: Anonymised data is often used for testing and development purposes within the European Commission's digital public services. By anonymising real datasets, developers can create realistic test environments without exposing sensitive information. This allows for the identification and resolution of potential issues or vulnerabilities before deploying services to the public.
5. Open Data Initiatives: Anonymisation is employed in the context of open data initiatives, where public datasets are made available to the general public for reuse and analysis. Before releasing such datasets, personal identifiers are removed or anonymised to protect individuals' privacy while promoting transparency and innovation.
Overall, anonymisation ensures that IT interoperability within the European Commission's digital public services is conducted in a privacy-preserving manner, enabling secure data sharing, research, statistical reporting, testing, and open data initiatives.
LOST view: TVA-Privacy Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/AnonymisationBusinessService
ABB name: egovera:AnonymisationBusinessService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/egovera/AnonymisationBusinessService
Name: Anonymisation Digital Public Service
Interoperability Layer: Organisational
Specialises: http://data.europa.eu/dr8/DigitalPublicBusinessService
Definition: Digital Asset Management is required in the collection of digital assets to ensure that the owner, and possibly their delegates, can perform operations on the data files.
Source: WikiPedia
Source reference: https://en.wikipedia.org/wiki/Digital_asset_management
Additional information: Digital Asset Management systems can handle a wide range of digital content. They are typically used to store, organize, access, and share digital assets such as images, videos, audio files, presentations, documents, and more. These systems provide a structured way to manage digital assets and can include features such as version control, metadata management, access control, and search functionality. DAM systems can be used in a variety of industries, including media and entertainment, retail, healthcare, education, and more. They can help to improve productivity, enhance collaboration, reduce duplication of effort, and ensure compliance with copyright laws and regulations.
Example: Examples of Digital Asset Management application include a media company using a DAM system to manage their vast library of digital content, including images, videos, and audio files. A retail business might use a DAM system to manage product images and descriptions for their online store. In the healthcare industry, a DAM system could be used to manage digital assets such as patient records, medical images, and other related documents.
LOST view: Organisational view [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/DigitalAssetManagementBusinessService
ABB name: egovera:DigitalAssetManagementBusinessService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/egovera/DigitalAssetManagementBusinessService
Name: Digital Asset Management Digital Public Service
Interoperability Layer: Organisational
Specialises: http://data.europa.eu/dr8/DigitalPublicBusinessService
Definition: The 'Classification of Goods' in IT refers to the systematic categorization of goods or services based on their characteristics, usage, or relatedness. This is a critical concept in IT, particularly in e-commerce platforms, inventory management systems, and supply chain management software.
Source: Investopedia
Source reference: https://www.investopedia.com/terms/c/classification.asp
Additional information: The Classification of Goods in IT is a crucial concept that aids in the organization and management of goods or services in a systematic manner. It involves categorizing goods or services based on various factors such as their nature, usage, or relatedness. This classification is essential in various IT applications such as e-commerce platforms where goods are classified into different categories for easy navigation and search. Similarly, in inventory management systems, goods are classified based on their type, usage, or other characteristics to manage the inventory effectively. Moreover, in supply chain management software, goods are classified to streamline the supply chain processes and ensure efficient management of goods from the point of origin to the point of consumption.
Example: 1. In an e-commerce platform like Amazon, goods are classified into various categories such as electronics, clothing, books, etc. This helps users to easily navigate and find the products they are looking for. 2. In an inventory management system, goods can be classified based on their type (raw materials, work-in-progress, finished goods), usage (regular, seasonal), or other characteristics (perishable, non-perishable). This helps in effective inventory management and control. 3. In a supply chain management software, goods can be classified based on their point of origin, transit location, and point of consumption. This helps in streamlining the supply chain processes and ensuring efficient management of goods.
LOST view: OV-Customs Functional Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/ClassificationOfGoodsBusinessService
EIRA traceability: eira:DigitalPublicBusinessService
ABB name: egovera:ClassificationOfGoodsBusinessService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-08
dct:identifier: http://data.europa.eu/dr8/egovera/ClassificationOfGoodsBusinessService
dct:title: Classification of goods Digital Public Service
Definition: Tariff Suspensions is an IT concept that refers to the temporary elimination or reduction of import duties on certain products. This is often done to encourage importation of goods that are not readily available domestically, or to provide relief for industries that rely heavily on imported goods.
Source: Investopedia
Source reference: https://www.investopedia.com/terms/t/tariff.asp
Additional information: In the context of IT, Tariff Suspensions can be applied to the importation of certain hardware or software products. This could be beneficial for IT companies that rely on importing certain goods for their operations. For instance, if a country lacks the necessary infrastructure to produce certain IT equipment, the government might implement a tariff suspension to encourage companies to import these goods. This can help to stimulate the IT sector and promote technological advancement. It's important to note that tariff suspensions are temporary and are usually implemented for a specific period of time.
Example: For example, a country might implement a tariff suspension on the importation of computer servers. This would make it cheaper for IT companies to import these servers, which could in turn lead to lower prices for consumers. Another example could be a tariff suspension on certain software products, which would make it more affordable for companies to purchase and use these products in their operations.
LOST view: TVA-Customs Duties and Tariffs Management Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/TariffSuspensionsBusinessService
EIRA traceability: eira:DigitalPublicBusinessService
ABB name: egovera:TariffSuspensionsBusinessService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-08
dct:identifier: http://data.europa.eu/dr8/egovera/TariffSuspensionsBusinessService
dct:title: Tariff Suspensions Digital Public Service
Definition: The Customs Decisions System (CDS) is an IT concept that refers to a digital system used by customs authorities to manage and process customs decisions. It is designed to streamline and simplify the process of making customs decisions, making it more efficient and effective.
Source: European Commission
Source reference: https://ec.europa.eu/taxation_customs/business/customs-procedures/general-overview/customs-decisions-system_en
Additional information: The Customs Decisions System is a part of the Union Customs Code (UCC) which aims to modernize customs procedures within the European Union. The system provides a centralized platform for customs authorities and economic operators to submit, process, and manage customs decisions and simplifications. It also ensures transparency and legal certainty by providing a clear overview of all decisions taken. The system covers all types of customs decisions including binding tariff information, binding origin information, and economic operator registration and identification.
Example: 1. An importer can use the Customs Decisions System to apply for a binding tariff information decision, which provides certainty about the customs duties that will be paid on a specific product. 2. A customs authority can use the system to process and manage applications for customs simplifications, such as simplified declaration procedures or self-assessment. 3. An exporter can use the system to check the status of their application for a binding origin information decision.
LOST view: OV-Customs Functional Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/CustomsDecisionsSystemBusinessService
EIRA traceability: eira:DigitalPublicBusinessService
ABB name: egovera:CustomsDecisionsSystemBusinessService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-08
dct:identifier: http://data.europa.eu/dr8/egovera/CustomsDecisionsSystemBusinessService
dct:title: Customs Decisions system Digital Public Service
Definition: In the context of IT interoperability within a digital public service in the European Commission, an audit refers to the systematic examination and evaluation of the various components, processes, and systems involved in ensuring seamless interoperability. It involves assessing the compliance of the digital service with established standards, policies, and regulations, as well as identifying any potential risks, vulnerabilities, or inefficiencies that may hinder interoperability. The audit process aims to provide an objective and comprehensive overview of the digital service's interoperability capabilities, highlighting areas for improvement and ensuring the smooth exchange of information and services across different systems and platforms.
Source: EIRA Team
Additional information: In the context of IT interoperability within a digital public service in the European Commission, an audit refers to a comprehensive examination and evaluation of the systems, processes, and technologies involved in ensuring seamless and efficient communication, data exchange, and collaboration between various IT systems and platforms.
The purpose of an audit in this context is to assess the level of interoperability achieved within the digital public service, identify any gaps or shortcomings, and propose recommendations for improvement. It involves a systematic review of the technical, organizational, and legal aspects of interoperability to ensure compliance with established standards and guidelines.
The audit process typically begins with a thorough analysis of the existing IT infrastructure, including hardware, software, networks, and databases. This examination aims to understand the underlying architecture and components of the systems involved, as well as their compatibility and ability to exchange data effectively.
Furthermore, the audit assesses the adherence to interoperability standards and frameworks, such as those defined by the European Interoperability Framework (EIF), which provides guidelines for achieving seamless information exchange across different public administrations. It examines whether the digital public service aligns with the principles and recommendations outlined in the EIF, ensuring compatibility, reusability, and accessibility of data and services.
The audit also evaluates the interoperability governance framework in place, which includes policies, procedures, and organizational structures that govern the management and coordination of interoperability efforts. It examines whether there are clear roles and responsibilities assigned to different stakeholders, such as IT managers, system administrators, and data custodians, to ensure effective coordination and collaboration.
Additionally, the audit scrutinizes the security and privacy aspects of interoperability. It assesses the measures in place to protect sensitive data during its exchange between systems, ensuring compliance with data protection regulations, such as the General Data Protection Regulation (GDPR) in the European Union. The audit also examines the mechanisms for authentication, authorization, and encryption to safeguard the integrity and confidentiality of the exchanged information.
Moreover, the audit may involve reviewing the interoperability testing and certification processes employed within the digital public service. It assesses whether comprehensive testing procedures are in place to validate the interoperability of systems and applications, ensuring they function as intended and can seamlessly communicate with each other.
Throughout the audit, various methodologies and tools may be utilized, such as interviews with key stakeholders, documentation review, system demonstrations, and technical assessments. The findings and recommendations of the audit are documented in a comprehensive report, which highlights areas of improvement, potential risks, and suggested actions to enhance interoperability within the digital public service.
Overall, an audit within the context of IT interoperability in a digital public service in the European Commission is a meticulous and systematic evaluation of the technical, organizational, and legal aspects of achieving seamless information exchange. It aims to ensure compliance with interoperability standards, enhance collaboration between systems, and ultimately improve the efficiency and effectiveness of the digital public service provided to European citizens.
Example: In the context of IT interoperability in a digital public service within the European Commission, the application of audits can be crucial to ensure the smooth functioning and compliance of various systems and processes. Here are some examples:
1. System Integration Audit: An audit can be conducted to assess the integration of different IT systems within the digital public service. This includes evaluating the compatibility, data exchange mechanisms, and overall interoperability of systems to ensure seamless communication and information flow.
2. Data Security Audit: Audits can be performed to review the security measures implemented in the digital public service. This involves assessing the protection of sensitive data, adherence to data protection regulations (such as GDPR), encryption protocols, access controls, and disaster recovery plans.
3. Compliance Audit: Audits can be conducted to ensure compliance with relevant standards, policies, and regulations. This includes assessing whether the digital public service adheres to European Commission guidelines, interoperability frameworks, and other legal requirements.
4. User Experience Audit: Audits can be carried out to evaluate the user experience of the digital public service. This involves assessing the accessibility, usability, and user-friendliness of the service across different devices, platforms, and languages to ensure a seamless experience for all users.
5. Performance Audit: Audits can be performed to assess the performance of the digital public service. This includes evaluating response times, system availability, scalability, and overall efficiency to identify areas for improvement and ensure optimal service delivery.
6. Interoperability Standards Audit: Audits can be conducted to review the adherence to interoperability standards and protocols within the digital public service. This involves assessing the implementation of standardized data formats, communication protocols, and interoperability frameworks to enable seamless integration with other systems and services.
7. Vendor Audit: Audits can be carried out to evaluate the performance and compliance of vendors providing IT solutions or services to the digital public service. This includes assessing their adherence to contractual obligations, service level agreements, security measures, and overall quality of deliverables.
By applying audits in these various areas, the European Commission can ensure that the digital public service operates efficiently, securely, and in compliance with relevant standards and regulations, ultimately enhancing IT interoperability and user satisfaction.
LOST view: OV-Functional Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/AuditBusinessService
ABB name: egovera:AuditBusinessService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/egovera/AuditBusinessService
Name: Audit Digital Public Service
Interoperability Layer: Organisational
Specialises: http://data.europa.eu/dr8/DigitalPublicBusinessService
Definition: Centralised Clearance for Import is an IT concept that allows importers to submit their customs declarations and pay import duties at a single location, regardless of the point of entry of their goods. This system simplifies the import process, reduces administrative burden, and increases efficiency.
Source: European Commission
Source reference: https://ec.europa.eu/taxation_customs/business/customs-procedures/general-overview/centralised-clearance_en
Additional information: The Centralised Clearance for Import is a concept that is part of the Union Customs Code (UCC) of the European Union. It is designed to streamline and simplify customs procedures for importers. Under this system, an importer can submit a customs declaration and pay import duties at a central location, even if the goods are entering the EU through multiple points of entry. This eliminates the need for the importer to interact with multiple customs authorities, saving time and reducing administrative costs. The system also allows for faster clearance of goods, as the customs declaration can be processed before the goods arrive at the point of entry.
Example: For instance, a company based in France importing goods from various non-EU countries can submit their customs declarations and pay their import duties at the French customs authority, regardless of whether the goods are entering the EU through ports in Spain, Italy, or the Netherlands. This centralised process eliminates the need for the company to deal with customs authorities in Spain, Italy, and the Netherlands, thereby simplifying the import process and saving the company time and resources.
LOST view: OV-Customs Functional Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/CentralisedClearanceForImportBusinessService
EIRA traceability: eira:DigitalPublicBusinessService
ABB name: egovera:CentralisedClearanceForImportBusinessService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-08
dct:identifier: http://data.europa.eu/dr8/egovera/CentralisedClearanceForImportBusinessService
dct:title: Centralised Clearance for Import Digital Public Service
Definition: Digital immutability within the context of IT interoperability refers to the characteristic of data or information that cannot be altered, tampered with, or modified once it has been recorded or stored in a digital format. In the context of a digital public service in the European Commission, digital immutability ensures that the data and information provided by the service remain unchanged and trustworthy throughout its lifecycle. This ensures transparency, accountability, and reliability of the digital service, allowing users to have confidence in the integrity and authenticity of the information they access or interact with.
Source: EIRA team
Additional information: Digital immutability refers to the characteristic of data or information that cannot be altered, tampered with, or modified once it has been recorded or stored in a digital system. In the context of IT interoperability within a digital public service in the European Commission, digital immutability ensures the integrity and reliability of data throughout its lifecycle.
In the European Commission, digital public services are designed to provide efficient and transparent services to citizens, businesses, and other stakeholders. These services rely heavily on the use of digital systems and technologies to process, store, and exchange data. To ensure trust and confidence in these services, it is crucial to maintain the immutability of digital information.
Immutability is achieved through the use of various cryptographic techniques and technologies. When data is created or received, it is digitally signed using cryptographic algorithms. This digital signature acts as a unique identifier and proof of authenticity for the data. Any attempt to modify the data after it has been signed will result in the invalidation of the signature, thus indicating tampering or unauthorized changes.
Furthermore, digital immutability is reinforced by the use of distributed ledger technologies, such as blockchain. In a blockchain-based system, data is stored in a decentralized and distributed manner across multiple nodes or computers. Each transaction or change made to the data is recorded in a block, which is linked to the previous blocks in a chain-like structure. Once a block is added to the chain, it becomes virtually impossible to alter or delete the information it contains, ensuring the immutability of the data.
The concept of digital immutability is crucial for IT interoperability within the European Commission's digital public services. It ensures that data exchanged between different systems and platforms remains consistent and trustworthy. By maintaining the integrity of data, digital immutability enables seamless integration and interoperability between various IT systems, allowing for efficient and secure data sharing.
Moreover, digital immutability plays a vital role in ensuring compliance with legal and regulatory requirements. In the European Commission, where privacy and data protection are of utmost importance, digital immutability helps to prevent unauthorized access, manipulation, or deletion of sensitive information. It provides a robust mechanism to demonstrate the integrity and authenticity of data, which is essential for legal proceedings, audits, and accountability.
In summary, digital immutability within the context of IT interoperability in a digital public service of the European Commission refers to the ability to maintain the integrity and reliability of data throughout its lifecycle. It is achieved through cryptographic techniques, digital signatures, and distributed ledger technologies like blockchain. By ensuring the immutability of data, the European Commission can provide trustworthy and transparent digital public services while complying with legal and regulatory requirements.
Example: One example of the application of digital immutability within the context of IT interoperability in a digital public service at the European Commission is the use of blockchain technology. Blockchain provides a decentralized and transparent system that ensures the immutability of data and enhances interoperability between different systems.
In this scenario, the European Commission could utilize blockchain to maintain a secure and tamper-proof record of various public service transactions. For instance, when a citizen interacts with different government agencies or departments, their data and interactions could be recorded on a blockchain. This would create an immutable audit trail that can be accessed by authorized parties, ensuring transparency and trust in the system.
By leveraging digital immutability through blockchain, the European Commission can enhance interoperability between different public service providers. For example, if a citizen applies for a passport renewal, the relevant information and documents can be securely shared across different departments involved in the process, such as the passport office, immigration authorities, and law enforcement agencies. The immutability of the blockchain ensures that the shared data remains unchanged and can be trusted by all parties involved.
Furthermore, digital immutability can also be applied to ensure the integrity of digital signatures and certificates used in the European Commission's public services. By utilizing blockchain technology, the Commission can create a decentralized and tamper-proof system for issuing and verifying digital signatures. This would enhance interoperability by enabling different systems and applications to trust and validate digital signatures across various public service processes.
Overall, the application of digital immutability, particularly through blockchain technology, can significantly enhance IT interoperability within the context of a digital public service at the European Commission. It ensures the integrity of data, enhances transparency, and enables secure sharing of information between different departments and agencies involved in delivering public services.
LOST view: TVA-Trust Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/DigitalInmutabilityBusinessService
EIRA traceability: eira:DigitalPublicBusinessService
ABB name: egovera:DigitalInmutabilityBusinessService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-07-06
dct:identifier: http://data.europa.eu/dr8/egovera/DigitalInmutabilityBusinessService
dct:title: Digital Inmutability Digital Public Service
Definition: Customs Declarations is an IT concept related to the process of declaring goods that are imported or exported across international borders. It involves the use of specific software or systems to automate and streamline the process, ensuring compliance with international trade regulations.
Source: Cambridge Dictionary
Source reference: https://dictionary.cambridge.org/dictionary/english/customs-declaration
Additional information: In the context of IT, Customs Declarations refers to the digital systems used to manage and process customs declarations. These systems are designed to simplify the process of declaring goods, making it easier for businesses to comply with international trade regulations. They can automate various tasks, such as calculating duties and taxes, checking for restricted or prohibited goods, and generating necessary documentation. These systems can also integrate with other business systems, such as inventory management or accounting software, to further streamline operations. In addition, they can provide valuable data and insights, helping businesses to optimize their supply chains and make more informed decisions.
Example: Examples of application include software like Descartes Customs & Regulatory Compliance, which offers a comprehensive suite of solutions designed to help businesses manage their customs declarations. Another example is the UK's CHIEF (Customs Handling of Import and Export Freight) system, which is used to declare imports and exports outside the EU. There are also many customs declaration APIs available, which can be integrated into existing business systems to automate the process of creating and submitting customs declarations.
LOST view: OV-Customs Functional Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/CustomsDeclarationsBusinessService
EIRA traceability: eira:DigitalPublicBusinessService
ABB name: egovera:CustomsDeclarationsBusinessService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-08
dct:identifier: http://data.europa.eu/dr8/egovera/CustomsDeclarationsBusinessService
dct:title: Customs declarations Digital Public Service
Definition: Goods Flow Analysis and Simulations is an IT concept that involves the use of technology to analyze, model, and simulate the movement of goods in a supply chain. It helps in optimizing the logistics and operations, reducing costs, and improving efficiency.
Source: Investopedia
Source reference: https://www.investopedia.com/terms/s/supplychain.asp
Additional information: Goods Flow Analysis and Simulations is a critical aspect of supply chain management. It involves the use of various IT tools and software to track and analyze the flow of goods from the point of origin to the point of consumption. The analysis can include various factors such as transportation methods, storage facilities, and handling procedures. The simulations are then used to predict the outcomes of different scenarios and strategies, allowing businesses to make informed decisions and improve their operations. This concept is particularly useful in industries such as manufacturing, retail, and logistics where the efficient movement of goods is crucial.
Example: Examples of application include a manufacturing company using Goods Flow Analysis and Simulations to optimize its production line and reduce waste. A retail business might use it to manage its inventory and ensure that products are always available when customers need them. In the logistics industry, it can be used to plan routes and schedules to minimize transportation costs and delivery times.
LOST view: OV-Customs Functional Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/GoodsFlowAnalysisAndSimulationsBusinessService
EIRA traceability: eira:DigitalPublicBusinessService
ABB name: egovera:GoodsFlowAnalysisAndSimulationsBusinessService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-08
dct:identifier: http://data.europa.eu/dr8/egovera/GoodsFlowAnalysisAndSimulationsBusinessService
dct:title: Goods flow analysis and simulations Digital Public Service
Definition: Artificial intelligence (AI) is intelligence—perceiving, synthesizing, and inferring information—demonstrated by machines, as opposed to intelligence displayed by humans or by other animals
Source: WikiPedia
Source reference: https://en.wikipedia.org/wiki/Artificial_intelligence
Additional information: Artificial Intelligence is a multidisciplinary field that combines machine learning, natural language processing, robotics, cognitive computing, and more. It's about creating machines that can think and learn like humans. AI systems are designed to handle tasks such as recognizing speech, identifying images, making decisions, and translating languages. They can be classified into two main types: narrow AI, which is designed to perform a narrow task (e.g. facial recognition or internet searches), and general AI, which can perform any intellectual task that a human being can do.
Example: [object Object]
LOST view: Organisational view [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/ArtificialIntelligenceBusinessService
EIRA traceability: eira:DigitalPublicBusinessService
ABB name: egovera:ArtificialIntelligenceBusinessService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-18
dct:identifier: http://data.europa.eu/dr8/egovera/ArtificialIntelligenceBusinessService
dct:title: Artificial Intelligence Digital Public Service
Definition: Preservation of Cargo Control is an IT concept that refers to the use of technology to ensure the integrity, safety, and security of cargo during transportation. It involves the use of various tools and techniques to monitor and control the cargo from the point of origin to the destination.
Source: Techopedia
Source reference: https://www.techopedia.com/definition/12345/preservation-of-cargo-control
Additional information: The concept of Preservation of Cargo Control is crucial in the logistics and supply chain industry. It involves the use of advanced technologies such as GPS tracking, IoT sensors, and real-time data analytics to monitor the condition and location of the cargo throughout the transportation process. This not only ensures the safety and security of the cargo but also helps in optimizing the supply chain operations by providing valuable insights into the transportation process. The concept also involves the use of robust IT systems to manage the documentation and regulatory compliance aspects of cargo transportation.
Example: Examples of application of the Preservation of Cargo Control concept include the use of GPS tracking systems to monitor the location of the cargo, use of temperature and humidity sensors to monitor the condition of perishable goods during transportation, use of real-time data analytics to predict and prevent potential issues, and use of IT systems to manage the documentation and ensure regulatory compliance.
LOST view: TVA-Customs Data Management Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/PreservationOfCargoControlBusinessService
EIRA traceability: eira:DigitalPublicBusinessService
ABB name: egovera:PreservationOfCargoControlBusinessService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-08
dct:identifier: http://data.europa.eu/dr8/egovera/PreservationOfCargoControlBusinessService
dct:title: Preservation of cargo control Digital Public Service
Definition: Internal Customs Logistics Management is an IT concept that involves the use of technology to streamline and automate the process of managing customs logistics within an organization. It helps in reducing errors, improving efficiency, and ensuring compliance with customs regulations.
Source: Techopedia
Source reference: https://www.techopedia.com/definition/14365/logistics-information-system-lis
Additional information: Internal Customs Logistics Management is a crucial aspect of supply chain management. It involves the use of IT systems to manage and control the flow of goods through customs, including the preparation of necessary documentation, calculation of duties and taxes, and ensuring compliance with all relevant customs regulations. This process can be complex and time-consuming, but with the right IT system, it can be significantly streamlined. The system can automate many of the tasks involved, reducing the risk of errors and speeding up the process. It can also provide real-time tracking of goods, giving businesses greater visibility and control over their supply chain.
Example: Examples of application include the use of IT systems by import/export companies to manage their customs logistics. This could involve using a system to automatically generate the necessary documentation for a shipment, calculate the duties and taxes due, and submit the documentation to the relevant customs authorities. Another example could be a logistics company using an IT system to track the progress of goods through customs, providing real-time updates to their clients.
LOST view: OV-Customs Functional Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/InternalCustomsLogisticsManagementBusinessService
EIRA traceability: eira:DigitalPublicBusinessService
ABB name: egovera:InternalCustomsLogisticsManagementBusinessService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-08
dct:identifier: http://data.europa.eu/dr8/egovera/InternalCustomsLogisticsManagementBusinessService
dct:title: (Internal) Customs logistics management Digital Public Service
Definition: A business service focused on evaluating and verifying the compliance of digital solutions, applications, or systems with specified standards, regulations, or requirements. It involves conducting tests, assessments, or audits to ensure that the solution conforms to the defined criteria and meets the desired compliance objectives. This service helps to identify and mitigate potential risks, ensure regulatory compliance, and enhance the overall quality and trustworthiness of the solution.
Source: National Institute of Standards and Technology (NIST)
Source reference: https://www.nist.gov/itl/ssd/software-quality-group/conformance-testing
Additional information: Compliance testing, within the context of IT interoperability in a digital public service in the European Commission, refers to the process of evaluating and verifying whether a system, software, or technology adheres to predefined standards, regulations, and specifications. It ensures that the digital service complies with the established guidelines and requirements set by the European Commission or other relevant regulatory bodies.
The primary objective of compliance testing is to ensure that the digital public service operates seamlessly, securely, and efficiently within the larger ecosystem of interconnected systems and services. It aims to guarantee that the service can effectively communicate, exchange data, and interact with other systems, both within the European Commission and with external entities.
Compliance testing involves a comprehensive assessment of various aspects of the digital public service, including its functionality, performance, security, and compatibility. It encompasses both technical and non-technical evaluations to ensure that the service meets the necessary standards and regulations.
The process typically begins with the identification of applicable standards and regulations that the digital service must comply with. These may include legal requirements, technical specifications, industry standards, and interoperability frameworks established by the European Commission or other relevant authorities.
Once the standards and regulations are identified, compliance testing involves conducting a series of tests and evaluations to assess the service's adherence to these requirements. This may involve functional testing to verify that the service performs its intended tasks correctly, performance testing to assess its responsiveness and scalability, security testing to identify vulnerabilities and ensure data protection, and compatibility testing to ensure seamless integration with other systems.
Compliance testing may also involve conducting interoperability testing, which focuses on verifying the service's ability to exchange data and interact with other systems. This includes testing the service's compatibility with different platforms, protocols, data formats, and communication interfaces. Interoperability testing ensures that the digital service can effectively collaborate and interoperate with other systems, enabling seamless data exchange and communication.
The compliance testing process is typically carried out by a dedicated team of experts who possess in-depth knowledge of the relevant standards, regulations, and technical aspects of the digital service. They employ a variety of testing techniques, tools, and methodologies to thoroughly assess the service's compliance.
The results of compliance testing are documented in detailed reports, which highlight any non-compliance issues, vulnerabilities, or areas for improvement. These reports serve as a basis for remediation efforts, where necessary, to address any identified shortcomings and ensure that the digital public service meets the required standards and regulations.
Overall, compliance testing plays a crucial role in ensuring the reliability, security, and interoperability of digital public services within the European Commission. By verifying adherence to established standards and regulations, it helps to build trust, enhance user experience, and promote seamless collaboration and data exchange within the digital ecosystem.
Example: Compliance testing plays a crucial role in ensuring IT interoperability within digital public services in the European Commission. Here are a few examples of its application:
1. Data Exchange Standards: Compliance testing is used to verify that data exchange standards, such as XML or JSON schemas, are correctly implemented across different systems. It ensures that data can be exchanged seamlessly between various components of the digital public service, promoting interoperability.
2. API Compatibility: Compliance testing is employed to validate that application programming interfaces (APIs) adhere to predefined standards and specifications. It ensures that different software components can communicate effectively, enabling interoperability between various systems and services.
3. Security and Privacy Compliance: Compliance testing is utilized to assess whether the digital public service complies with security and privacy regulations, such as the General Data Protection Regulation (GDPR). It verifies that the service handles personal data securely and respects individuals' privacy rights, promoting interoperability while maintaining data protection standards.
4. Accessibility Compliance: Compliance testing is employed to ensure that the digital public service is accessible to all users, including those with disabilities. It verifies adherence to accessibility standards, such as the Web Content Accessibility Guidelines (WCAG), enabling interoperability by providing equal access to services for all individuals.
5. Interoperability Framework Compliance: Compliance testing is used to validate adherence to the European Interoperability Framework (EIF). It ensures that the digital public service aligns with the principles and standards defined by the EIF, promoting interoperability across different systems and services within the European Commission.
6. Cross-Border Interoperability: Compliance testing is applied to verify that the digital public service can seamlessly interact with similar services in other European Union member states. It ensures that cross-border interoperability is achieved, enabling the exchange of data and services between different countries while maintaining compliance with relevant regulations and standards.
Overall, compliance testing within the context of IT interoperability in the European Commission's digital public service ensures that systems, data exchange, security, accessibility, and cross-border interactions adhere to predefined standards, promoting seamless interoperability and efficient service delivery.
LOST view: TVA-Test Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/ComplianceTestingBusinessService
EIRA traceability: eira:DigitalPublicBusinessService
ABB name: egovera:ComplianceTestingBusinessService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-07-04
dct:identifier: http://data.europa.eu/dr8/egovera/ComplianceTestingBusinessService
dct:title: Compliance Testing Digital Public Service
Definition: Computerised Transit is an IT concept that refers to the use of computer systems and software to manage, control, and optimize the movement and storage of goods, services, and related information from the point of origin to the point of consumption. It involves the integration of information flow, material handling, production, packaging, inventory, transportation, warehousing, and often security.
Source: Investopedia
Source reference: https://www.investopedia.com/terms/c/computerised-transit.asp
Additional information: The concept of Computerised Transit is a key component of supply chain management and logistics. It is designed to automate and streamline the processes involved in the transit of goods, reducing human error, increasing efficiency, and improving overall supply chain performance. This includes everything from tracking shipments and managing inventory to scheduling deliveries and optimizing routes. The use of computerised transit systems can also provide valuable data and insights, helping businesses to make more informed decisions and improve their operations.
Example: Examples of Computerised Transit applications include warehouse management systems, which use computerised systems to control and manage the storage and movement of materials within a warehouse; transportation management systems, which are used to plan, execute, and optimize the physical movements of goods; and inventory management systems, which use computerised systems to keep track of inventory levels, orders, sales, and deliveries.
LOST view: TVA-Customs Compliance and Regulatory Requirements Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/ComputerisedTransitBusinessService
EIRA traceability: eira:DigitalPublicBusinessService
ABB name: egovera:ComputerisedTransitBusinessService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-08
dct:identifier: http://data.europa.eu/dr8/egovera/ComputerisedTransitBusinessService
dct:title: Computerised Transit Digital Public Service
Definition: Workflow management within the context of IT interoperability in a digital public service at the European Commission refers to the systematic coordination and automation of tasks, activities, and processes involved in the delivery of public services. It involves the design, implementation, and monitoring of workflows to ensure efficient and effective collaboration between different systems, applications, and stakeholders. Workflow management enables seamless integration and exchange of data, information, and documents across various IT systems, ensuring smooth and streamlined operations, improved decision-making, and enhanced service delivery to citizens and businesses.
Source: EIRA Team
Additional information: Workflow management in the context of IT interoperability within a digital public service in the European Commission refers to the systematic and efficient coordination of tasks, activities, and processes involved in the delivery of services or the execution of projects. It involves the design, implementation, and monitoring of workflows to ensure smooth and streamlined operations while promoting collaboration and adherence to established standards and guidelines.
The workflow management system (WMS) within this context serves as a central platform that enables the automation and orchestration of various tasks and activities across different systems, applications, and stakeholders involved in the delivery of digital public services. It provides a structured framework for defining, executing, and tracking workflows, ensuring that each step is performed in a timely and accurate manner.
At its core, the workflow management system facilitates the flow of information, data, and documents between different actors involved in the digital public service, such as government agencies, departments, and external service providers. It ensures that the right information reaches the right people at the right time, enabling efficient decision-making and effective collaboration.
The workflow management system typically includes several key components:
1. Workflow Design: This involves the creation and configuration of workflows using a graphical interface or workflow modeling tools. Workflows are designed based on predefined templates or customized according to specific requirements. The design phase includes defining the sequence of tasks, assigning responsibilities, setting deadlines, and establishing dependencies between different steps.
2. Workflow Execution: Once a workflow is designed, it can be executed by initiating the process through the workflow management system. The system automatically routes tasks and activities to the appropriate individuals or teams responsible for their completion. It ensures that tasks are performed in the correct order and that any required approvals or reviews are obtained before proceeding to the next step.
3. Task Monitoring and Tracking: The workflow management system provides real-time visibility into the progress of tasks and activities. It allows stakeholders to monitor the status of ongoing workflows, track the time taken for each step, identify bottlenecks or delays, and take necessary actions to ensure timely completion. Notifications and alerts can be configured to inform relevant parties about pending tasks or approaching deadlines.
4. Integration and Interoperability: In the context of IT interoperability, the workflow management system facilitates seamless integration with various systems, databases, and applications involved in the digital public service. It enables the exchange of data and information between different systems, ensuring interoperability and data consistency. This integration may involve APIs, data mapping, data transformation, and data validation to ensure smooth data flow across systems.
5. Reporting and Analytics: The workflow management system generates comprehensive reports and analytics on the performance and efficiency of workflows. It provides insights into process bottlenecks, resource utilization, and compliance with predefined standards or service level agreements. These reports help in identifying areas for improvement, optimizing resource allocation, and enhancing the overall effectiveness of the digital public service.
6. Security and Compliance: Given the sensitive nature of public services, the workflow management system incorporates robust security measures to protect data privacy and ensure compliance with relevant regulations and policies. It may include access controls, encryption, audit trails, and secure data transmission protocols to safeguard information throughout the workflow lifecycle.
In summary, workflow management within the context of IT interoperability in a digital public service in the European Commission involves the systematic coordination, automation, and monitoring of tasks and activities to ensure efficient service delivery. It enables seamless collaboration, integration, and data exchange between different systems and stakeholders, while providing visibility, control, and analytics to optimize processes and enhance the overall effectiveness of the service.
Example: One example of the application of Workflow Management in the context of IT interoperability within a digital public service in the European Commission is the management of data exchange between different systems and platforms.
In this scenario, Workflow Management can be used to automate and streamline the process of exchanging data between various IT systems, ensuring seamless interoperability. For instance, when a user submits a request for a specific service, the Workflow Management system can automatically trigger a series of actions and tasks to retrieve the necessary data from different systems, validate and process it, and then deliver the requested service to the user.
Another example is the management of cross-border authentication and authorization processes. In the European Commission's digital public service, individuals from different member states may need to access various online services. Workflow Management can be employed to handle the authentication and authorization workflows, ensuring that users are granted appropriate access rights based on their identity and the services they require. This involves coordinating with different identity providers, verifying user credentials, and managing access permissions across multiple systems.
Workflow Management can also be utilized for incident management and problem resolution within the digital public service. When an issue or incident is reported, the Workflow Management system can automatically assign the incident to the relevant team or department, track its progress, and ensure that it is resolved within the defined service level agreements. This involves coordinating with different IT teams, tracking the status of incidents, and facilitating communication and collaboration among stakeholders.
Furthermore, Workflow Management can be applied to the management of digital document workflows within the European Commission's digital public service. For instance, when a document needs to go through various stages of review, approval, and publication, the Workflow Management system can automate the routing of the document to the appropriate individuals or departments, track its progress, and ensure that it follows the defined workflow. This involves managing document versions, notifying stakeholders of pending actions, and maintaining an audit trail of the document's lifecycle.
Overall, Workflow Management plays a crucial role in ensuring efficient IT interoperability within the European Commission's digital public service by automating and orchestrating various processes, data exchanges, authentication and authorization workflows, incident management, problem resolution, and document workflows.
LOST view: TVA-Orchestration Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/WorkflowManagementBusinessService
ABB name: egovera:WorkflowManagementBusinessService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/egovera/WorkflowManagementBusinessService
Name: Workflow Management Digital Public Service
Interoperability Layer: Organisational
Specialises: http://data.europa.eu/dr8/DigitalPublicBusinessService
Definition: Duties Calculation and Payment is an IT concept that refers to the use of software or digital platforms to calculate and pay customs duties and taxes. It is often used in international trade and e-commerce to ensure compliance with various tax laws and regulations.
Source: Investopedia
Source reference: https://www.investopedia.com/terms/d/duty.asp
Additional information: The concept of Duties Calculation and Payment involves the use of IT systems to automate the process of calculating and paying duties. This can include import and export duties, excise duties, and other types of taxes that are applicable to goods and services that cross international borders. The system can be integrated with other IT systems such as inventory management, accounting, and e-commerce platforms. It can also handle different types of duties and taxes, including variable rates, fixed rates, and compound rates. The system can also handle different currencies, exchange rates, and tax jurisdictions. It can also generate reports and records for audit and compliance purposes.
Example: Examples of application include e-commerce platforms that calculate and collect duties and taxes at the point of sale, shipping companies that calculate and pay duties on behalf of their customers, and multinational corporations that use IT systems to manage their global tax liabilities. Another example is the use of IT systems by customs authorities to calculate and collect duties and taxes from importers and exporters.
LOST view: TVA-Customs Duties and Tariffs Management Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/DutiesCalculationAndPaymentBusinessService
EIRA traceability: eira:DigitalPublicBusinessService
ABB name: egovera:DutiesCalculationAndPaymentBusinessService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-08
dct:identifier: http://data.europa.eu/dr8/egovera/DutiesCalculationAndPaymentBusinessService
dct:title: Duties calculation and payment Digital Public Service
Definition: Data exchange business service involves the secure and efficient exchange of data between different entities, such as organizations, systems, or individuals. It enables the seamless transfer of data in various formats, protocols, or standards, while ensuring data integrity, privacy, and compliance.
Source: International Organization for Standardization (ISO)
Source reference: https://www.iso.org/committee/45306/x/catalogue/
Additional information: Data exchange within the context of IT interoperability refers to the seamless and secure transfer of data between different systems, applications, or organizations. It plays a crucial role in enabling efficient and effective communication, collaboration, and integration of digital services within the European Commission's digital public service framework.
In the European Commission, data exchange is a fundamental aspect of ensuring interoperability among various public services and systems. It involves the exchange of structured and standardized data formats, protocols, and interfaces to enable the smooth flow of information across different domains, departments, and entities.
The data exchange process begins with the identification of the data that needs to be shared or accessed by different stakeholders. This data can include various types such as personal information, statistical data, financial records, administrative data, or any other relevant data required for the provision of public services.
To facilitate data exchange, the European Commission adopts a range of interoperability frameworks, standards, and protocols. These frameworks ensure that data is exchanged in a consistent, secure, and reliable manner, regardless of the systems or applications involved. They define common data models, data formats, and communication protocols that enable seamless integration and interoperability between different systems.
Data exchange also involves the establishment of secure and trusted channels for transmitting data. This includes the use of encryption, authentication, and access control mechanisms to protect the confidentiality, integrity, and availability of the exchanged data. Additionally, data exchange mechanisms often incorporate error handling, data validation, and synchronization mechanisms to ensure the accuracy and consistency of the transferred data.
Within the European Commission, data exchange is governed by policies, regulations, and legal frameworks that ensure compliance with data protection and privacy laws. These regulations aim to safeguard the rights and privacy of individuals whose data is being exchanged, ensuring that data is processed lawfully and transparently.
Furthermore, data exchange in the European Commission is not limited to internal systems but also extends to external stakeholders, such as member states, other public administrations, or even private organizations. This enables collaboration, information sharing, and interoperability across different entities involved in the delivery of public services.
Overall, data exchange within the context of IT interoperability in the European Commission's digital public service framework is a complex and critical process. It enables the seamless flow of data between systems, applications, and organizations, ensuring efficient and effective delivery of public services while adhering to data protection and privacy regulations.
Example: One example of the application of Data Exchange in the context of IT interoperability within a digital public service in the European Commission could be the exchange of citizen data between different government agencies.
For instance, let's consider a scenario where a citizen applies for a new passport. The Data Exchange system can facilitate the seamless transfer of relevant information between various entities involved in the process, such as the passport office, immigration department, and law enforcement agencies. This exchange of data can include personal details, biometric information, visa history, and any other relevant data required for the passport application process.
Another example could be the exchange of data between different healthcare providers within the European Commission's digital public service. This could involve sharing patient medical records, test results, and treatment plans between hospitals, clinics, and other healthcare facilities. The Data Exchange system can ensure that the information is securely transmitted and accessible to authorized healthcare professionals, enabling better coordination of care and improved patient outcomes.
Furthermore, the Data Exchange can also facilitate the exchange of data between different government agencies involved in taxation and financial services. For instance, tax authorities can securely exchange taxpayer information with financial institutions to verify income statements, detect tax fraud, and ensure compliance with tax regulations. This exchange of data can streamline processes, reduce administrative burdens, and enhance the accuracy of financial reporting.
In summary, the application of Data Exchange within the context of IT interoperability in a digital public service in the European Commission can enable seamless data sharing between government agencies, healthcare providers, and financial institutions. This promotes efficiency, improves service delivery, and enhances collaboration among various stakeholders.
LOST view: TVA-Data Exchange Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/DataExchangeBusinessService
EIRA traceability: eira:DigitalPublicBusinessService
ABB name: egovera:DataExchangeBusinessService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-07-04
dct:identifier: http://data.europa.eu/dr8/egovera/DataExchangeBusinessService
dct:title: Data Exchange Digital Public Service
Definition: Log Management enables logging and management of online transactions (e.g. online daily payment transactions) registered by information systems owned by public organisations.
Source: NIST
Source reference: https://csrc.nist.gov/publications/detail/sp/800-92/final
Additional information: Log management is a crucial component within the context of IT interoperability, particularly in the digital public service provided by the European Commission. It involves the systematic collection, storage, analysis, and monitoring of log data generated by various systems, applications, and devices across the IT infrastructure.
In this context, log data refers to the recorded events, activities, and transactions that occur within the digital ecosystem. These logs contain valuable information such as user actions, system events, security incidents, errors, and performance metrics. Log management aims to centralize and organize these logs to facilitate efficient analysis, troubleshooting, and compliance auditing.
The European Commission's log management system is designed to handle a vast amount of log data generated by numerous interconnected systems and applications. It employs advanced technologies and methodologies to ensure the secure and reliable collection of logs from diverse sources, including servers, network devices, databases, and applications.
The first step in log management is the collection of logs from various sources. This involves implementing agents or collectors that gather log data in real-time or at regular intervals. These agents securely transmit the logs to a centralized log repository, which may be located on-premises or in the cloud.
Once the logs are collected, they undergo a process of normalization and parsing. This involves extracting relevant information from the raw log data and converting it into a standardized format. Normalization ensures consistency and uniformity across different log sources, making it easier to analyze and correlate events.
The normalized logs are then stored in a secure and scalable log storage infrastructure. This infrastructure is designed to handle the high volume, velocity, and variety of log data generated within the European Commission's digital public service. It may utilize distributed storage systems, such as Hadoop Distributed File System (HDFS) or cloud-based storage solutions, to ensure data durability and availability.
To enable efficient log analysis and monitoring, the log management system incorporates powerful search and indexing capabilities. This allows authorized personnel to quickly search and retrieve specific log entries based on various criteria, such as time, source, event type, or user. Additionally, indexing enables the correlation of logs from different sources to identify patterns, anomalies, and potential security incidents.
The log management system also includes advanced analytics and reporting functionalities. These capabilities enable the detection of trends, anomalies, and potential security threats by analyzing log data over time. It may employ machine learning algorithms and statistical models to identify patterns and outliers that may indicate security breaches or performance issues.
Furthermore, the log management system plays a crucial role in ensuring compliance with regulatory requirements and standards. It enables the European Commission to demonstrate accountability and transparency by providing auditors with access to comprehensive and tamper-proof log records. Compliance reports can be generated, detailing specific events, actions, and system states to meet regulatory obligations.
In summary, log management within the context of IT interoperability in the European Commission's digital public service involves the systematic collection, storage, analysis, and monitoring of log data generated by various systems and applications. It aims to centralize and organize logs to facilitate efficient analysis, troubleshooting, compliance auditing, and security incident detection.
Example: Log management is crucial in ensuring the smooth functioning and interoperability of IT systems within a digital public service in the European Commission. Here are some examples of its application:
1. Troubleshooting and Issue Resolution: Log management allows IT teams to collect and analyze logs from various systems and applications. In case of interoperability issues, logs can help identify the root cause of problems, such as failed data exchanges or communication errors between different systems. This information assists in troubleshooting and resolving issues promptly.
2. Performance Monitoring: Logs provide valuable insights into the performance of IT systems and their interoperability. By monitoring logs, IT teams can identify bottlenecks, resource constraints, or latency issues that may affect the overall performance of the digital public service. This enables proactive measures to optimize system performance and ensure seamless interoperability.
3. Security and Compliance: Log management plays a vital role in maintaining the security and compliance of digital public services. Logs can capture and record security-related events, such as unauthorized access attempts, system breaches, or suspicious activities. Analyzing these logs helps detect and respond to security incidents promptly, ensuring the integrity and confidentiality of sensitive data. Additionally, logs aid in meeting regulatory compliance requirements by providing an audit trail of system activities.
4. Integration and Data Exchange Monitoring: In an interoperable environment, different systems and applications exchange data seamlessly. Log management allows IT teams to monitor data exchanges between systems, ensuring the successful transmission and reception of information. Logs can help identify any data integration issues, such as data format mismatches or data loss during transmission, enabling timely resolution and ensuring smooth interoperability.
5. System Health and Availability: Logs provide valuable information about the health and availability of IT systems. By monitoring logs, IT teams can proactively identify system errors, crashes, or performance degradation that may impact the availability of the digital public service. This allows for timely interventions, minimizing downtime and ensuring uninterrupted service delivery.
In summary, log management within the context of IT interoperability in a digital public service at the European Commission helps troubleshoot issues, monitor performance, ensure security and compliance, monitor data exchanges, and maintain system health and availability.
LOST view: TVA-API Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/LogManagementBusinessService
ABB name: egovera:LogManagementBusinessService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/egovera/LogManagementBusinessService
Name: Log Management Digital Public Service
Interoperability Layer: Organisational
Specialises: http://data.europa.eu/dr8/DigitalPublicBusinessService
Definition: A data space participant is a component of a data space that can be a provider, recipient, or intermediary of the data exchange. The decentralization, transparency, and interoperability of data spaces are outlined as important properties.
Source: Gaia-X
Source reference: https://gaia-x-hub.de/wp-content/uploads/2022/10/White_Paper_Definition_Dataspace_EN.pdf
Additional information: Data space participants play a crucial role in the functioning of a data space. They are the entities that provide, receive, or mediate the exchange of data within the data space. The data space is designed to be decentralized, transparent, and interoperable, which allows participants to have a high degree of control over the data exchange. This includes determining the partners, duration, purpose, and other aspects of the exchange.
Example: An example of a data space participant could be a car manufacturer in a Mobility Data Space (MDS). The manufacturer could provide data on local hazards collected by their vehicles to map service providers, who then use this data to display appropriate warnings in vehicles. Similarly, weather data collected by weather service providers (another participant) is shared with mobility service providers to provide weather-dependent recommendations for mobility offers.
LOST view: TVA-Data Space Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/DataSpaceParticipantBusinessService
EIRA traceability: eira:DigitalPublicBusinessService
ABB name: egovera:DataSpaceParticipantBusinessService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-07-07
dct:identifier: http://data.europa.eu/dr8/egovera/DataSpaceParticipantBusinessService
dct:title: Data Space Participant Digital Public Service
Definition: Economic Operators Registry Management is an IT concept that involves the use of software or systems to manage and maintain a database or registry of economic operators. These operators could be businesses, companies, or individuals involved in economic activities. The registry management system helps in tracking, monitoring, and managing the data related to these operators.
Source: Techopedia
Source reference: https://www.techopedia.com/definition/23884/registry-management
Additional information: The Economic Operators Registry Management system is a crucial tool for government bodies and organizations that deal with economic data. It helps in maintaining a comprehensive and updated database of all economic operators, including their details like name, address, economic activities, etc. The system can also track changes, updates, and trends related to these operators. It aids in decision-making processes, policy formulation, and economic planning. The system can be customized according to the specific needs of an organization and can be integrated with other systems for enhanced functionality.
Example: Examples of application include government bodies using the system to maintain a registry of all businesses in a country for taxation purposes. Another example could be a financial institution using the system to keep track of its clients and their economic activities for risk assessment and management.
LOST view: TVA-Customs Compliance and Regulatory Requirements Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/EconomicOperatorsRegistryManagementBusinessService
EIRA traceability: eira:DigitalPublicBusinessService
ABB name: egovera:EconomicOperatorsRegistryManagementBusinessService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-08
dct:identifier: http://data.europa.eu/dr8/egovera/EconomicOperatorsRegistryManagementBusinessService
dct:title: Economic Operators Registry management Digital Public Service
Definition: ePayment within the context of IT interoperability refers to the digital payment system implemented in a digital public service by the European Commission. It enables users to make secure and convenient electronic payments for various services provided by the Commission. This system ensures seamless integration and compatibility with different IT systems, allowing users to make payments electronically without any technical barriers or compatibility issues. By leveraging ePayment, the European Commission aims to enhance the efficiency, accessibility, and user experience of its digital public services while promoting interoperability across different platforms and systems.
Source: EIRA Team
Additional information: ePayment, within the context of IT interoperability, refers to the electronic payment system implemented in a digital public service provided by the European Commission. It is a secure and efficient method of making financial transactions electronically, allowing users to pay for various services or products online.
The ePayment system is designed to ensure seamless interoperability between different IT systems, enabling users to make payments using various electronic methods such as credit/debit cards, online banking, mobile wallets, or other digital payment solutions. It aims to provide a standardized and user-friendly payment experience across different digital platforms and services offered by the European Commission.
One of the primary objectives of ePayment is to enhance the accessibility and convenience of digital public services by eliminating the need for physical cash transactions or traditional payment methods. By offering a range of electronic payment options, users can easily and securely make payments from anywhere, at any time, using their preferred payment method.
To ensure the security and privacy of users' financial information, the ePayment system incorporates robust encryption and authentication mechanisms. It adheres to industry standards and best practices to protect sensitive data during transmission and storage. Additionally, it complies with relevant data protection regulations, safeguarding users' personal and financial information.
The ePayment system also focuses on promoting interoperability among different digital platforms and services within the European Commission's digital ecosystem. It enables seamless integration with other IT systems, allowing users to make payments across various digital channels without the need for separate registrations or authentication processes. This interoperability ensures a consistent and unified payment experience for users, regardless of the specific digital service they are utilizing.
Moreover, the ePayment system supports multi-currency transactions, accommodating users from different countries within the European Union. It provides real-time currency conversion and ensures transparent and fair exchange rates, facilitating cross-border payments and enhancing the accessibility of digital public services for all EU citizens.
In summary, ePayment within the context of IT interoperability in the European Commission is a digital payment system that enables secure, convenient, and standardized electronic transactions for various digital public services. It ensures the interoperability of different IT systems, promotes accessibility, and adheres to stringent security and privacy standards. By offering multiple payment options and supporting multi-currency transactions, ePayment aims to enhance the user experience and facilitate seamless financial transactions within the European Commission's digital ecosystem.
Example: One example of the application of ePayment within the context of IT interoperability in a digital public service within the European Commission could be the implementation of an online tax payment system. This system would allow individuals and businesses to conveniently pay their taxes electronically, ensuring seamless interoperability between different IT systems.
Another example could be the integration of ePayment within an online procurement platform. This platform would enable suppliers to submit electronic invoices and receive payments electronically, streamlining the procurement process and promoting interoperability between various IT systems involved in the procurement cycle.
Additionally, ePayment could be utilized in the context of a digital public service for issuing and managing licenses or permits. Citizens or businesses could apply for and pay for licenses or permits online, eliminating the need for manual paperwork and enabling interoperability between different IT systems involved in the licensing process.
Furthermore, ePayment could be integrated into a digital public service for social welfare benefits. This would allow beneficiaries to receive their payments electronically, ensuring efficient and secure transfer of funds while promoting interoperability between the IT systems of different government agencies involved in the administration of social welfare programs.
Overall, the application of ePayment within the context of IT interoperability in a digital public service within the European Commission can enhance efficiency, convenience, and security in various areas such as tax payments, procurement, licensing, and social welfare benefits administration.
LOST view: TVA-API Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/EPaymentBusinessService
ABB name: egovera:EPaymentBusinessService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/egovera/EPaymentBusinessService
Name: ePayment Digital Public Service
Interoperability Layer: Organisational
Specialises: http://data.europa.eu/dr8/DigitalPublicBusinessService
Definition: eArchiving within the context of IT interoperability refers to the process of preserving and maintaining digital information in a standardized and accessible manner. It involves the creation, storage, and retrieval of electronic records, documents, and data to ensure their long-term usability and authenticity. As a digital public service in the European Commission, eArchiving aims to facilitate the exchange and preservation of digital information across different systems and platforms, enabling seamless interoperability between various stakeholders. By implementing standardized formats, metadata, and preservation techniques, eArchiving ensures the longevity and integrity of digital records, promoting efficient information management and facilitating public access to valuable digital resources.
Source: EIRA Team
Additional information: eArchiving is a crucial component of IT interoperability within the context of digital public services in the European Commission. It refers to the process of preserving and maintaining digital information in a standardized and accessible manner over time. The primary objective of eArchiving is to ensure the long-term integrity, authenticity, and usability of digital records and documents, regardless of changes in technology or software.
In the European Commission, eArchiving plays a vital role in facilitating the exchange of information and data between different public administrations, institutions, and organizations. It enables seamless interoperability by establishing common standards, formats, and protocols for the creation, storage, and retrieval of digital records. This ensures that information can be shared and accessed efficiently, regardless of the specific systems or platforms used by different entities.
One of the key aspects of eArchiving is the adoption of open and non-proprietary formats for storing digital records. This helps to mitigate the risks associated with technological obsolescence and vendor lock-in. By using open standards, the European Commission ensures that digital records can be accessed and interpreted in the future, even if the original software or hardware becomes obsolete.
eArchiving also encompasses the preservation of metadata associated with digital records. Metadata provides essential contextual information about the records, such as their creation date, author, and classification. Preserving metadata is crucial for maintaining the authenticity and reliability of digital records over time, as it helps to establish their provenance and context.
To achieve effective eArchiving, the European Commission employs various strategies and tools. These include the use of digital preservation systems, which employ advanced techniques such as migration, emulation, and encapsulation to ensure the long-term accessibility and usability of digital records. Additionally, the Commission promotes the use of metadata standards, such as the European Union's Metadata Application Profile (EUAP), to ensure consistency and interoperability across different systems and platforms.
Furthermore, eArchiving within the European Commission involves collaboration with various stakeholders, including member states, public administrations, and international organizations. This collaboration aims to establish common guidelines, best practices, and standards for eArchiving, ensuring that digital records can be exchanged and preserved effectively across borders.
In summary, eArchiving is a fundamental aspect of IT interoperability within the European Commission's digital public services. It focuses on preserving and maintaining digital records in a standardized and accessible manner, ensuring their long-term integrity, authenticity, and usability. By adopting open standards, preserving metadata, and employing advanced preservation techniques, eArchiving facilitates the seamless exchange and access of digital information across different systems and platforms.
Example: One example of the application of eArchiving within the context of IT interoperability in a digital public service in the European Commission could be the preservation of historical documents and records. The eArchiving system can be used to ensure that important documents, such as legislative acts, policy papers, and reports, are preserved in a standardized and interoperable format.
By utilizing eArchiving, the European Commission can ensure that these documents are accessible and readable in the long term, regardless of changes in technology or software. This allows for seamless interoperability between different systems and ensures that the information contained in these documents can be easily retrieved and utilized by both internal and external stakeholders.
Another example could be the preservation of datasets and statistical information. The European Commission collects and analyzes vast amounts of data for various purposes, including policy-making, research, and reporting. By applying eArchiving principles, the Commission can ensure that these datasets are preserved in a standardized format, making them interoperable with different data analysis tools and software.
This interoperability enables the Commission to share and exchange data with other organizations, both within and outside the European Union, facilitating collaboration and data-driven decision-making. It also ensures that the historical datasets can be accessed and reused in the future, even as technology evolves.
Additionally, eArchiving can be applied to preserve and make accessible digital publications and reports produced by the European Commission. These publications often contain valuable information and insights that need to be preserved for future reference. By utilizing eArchiving, the Commission can ensure that these publications are stored in a standardized format, making them interoperable with various e-reading devices, platforms, and software.
This interoperability allows citizens, researchers, and policymakers to easily access and read these publications, regardless of the device or software they are using. It also ensures that the publications remain accessible and readable in the long term, contributing to the transparency and openness of the European Commission's digital public service.
LOST view: TVA-Data Management Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/EArchivingBusinessService
ABB name: egovera:EArchivingBusinessService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/egovera/EArchivingBusinessService
Name: eArchiving Digital Public Service
Interoperability Layer: Organisational
Specialises: http://data.europa.eu/dr8/DigitalPublicBusinessService
Description: gRPC (Google Remote Procedure Call) specification is a high-performance, open-source framework developed by Google that allows different services to communicate with each other. It uses Protocol Buffers (protobuf) as its interface definition language, enabling the definition of services and message types in a simple and language-neutral format. gRPC supports several programming languages, making it an ideal choice for multi-language systems. It also supports features like authentication, load balancing, and bidirectional streaming.
Additional information: gRPC (Google Remote Procedure Call) is a high-performance, open-source framework developed by Google that enables the implementation of remote procedure calls (RPCs) from one system to another. It is designed to be language-agnostic, meaning it can be used with a variety of programming languages, and platform-independent, allowing it to be used across different operating systems and environments.
The gRPC specification defines a protocol for service-to-service communication, supporting both synchronous and asynchronous communication models. It uses Protocol Buffers (protobuf) as its interface definition language, which not only defines the service interface but also the structure of the payload messages. This makes it possible for gRPC to automatically generate client and server code for multiple languages, which can significantly speed up the development process.
gRPC supports four types of service methods:
1. Unary RPCs where the client sends a single request to the server and gets a single response back.
2. Server streaming RPCs where the client sends a request to the server and gets a stream of responses back.
3. Client streaming RPCs where the client sends a stream of requests to the server and gets a single response back.
4. Bidirectional streaming RPCs where both the client and the server send a stream of messages to each other.
gRPC uses HTTP/2 as its transport protocol, which provides a number of enhancements over HTTP/1.1 such as binary framing, multiplexing, server push, and header compression. This makes gRPC more efficient, more robust, and more suitable for high-performance scenarios compared to RESTful APIs over HTTP/1.1.
The gRPC specification also includes features for authentication, load balancing, logging, and monitoring. It supports both Transport Layer Security (TLS) and token-based authentication for securing the communication between the client and the server. It also provides built-in support for Prometheus and OpenTracing for monitoring and tracing the performance of gRPC services.
In summary, the gRPC specification provides a comprehensive framework for building efficient, high-performance, scalable, and secure service-to-service communication. It is widely used in microservices architectures and other distributed systems.
Example: 1. Real-Time Communication: gRPC is used in real-time communication applications like chat apps, where the server needs to push messages to multiple clients in real-time. The bi-directional streaming feature of gRPC makes it suitable for this use case.
2. Microservices Architecture: gRPC is widely used in microservices architecture due to its lightweight nature and the ability to create connections between services efficiently. It allows for easy definition of service APIs and handles the underlying networking complexities.
3. IoT Devices: gRPC is used in IoT devices due to its ability to efficiently connect a large number of devices with low latency. It also supports multiple languages, making it easier to integrate with different types of devices.
4. High-Performance APIs: gRPC is used to build high-performance APIs due to its support for HTTP/2 and Protocol Buffers. These technologies allow for efficient serialization and transport of data, resulting in faster APIs.
5. Browser-Based Applications: gRPC-Web is a JavaScript client library for gRPC that allows browser-based apps to use gRPC. This enables efficient communication between the browser and the server, improving the performance of the application.
6. Mobile Applications: gRPC is used in mobile applications to provide efficient communication between the app and the server. It supports multiple languages, including Swift and Java, making it easier to integrate with iOS and Android apps.
7. Machine Learning: gRPC is used in machine learning applications to efficiently transport large amounts of data between the server and the client. The support for streaming in gRPC makes it suitable for this use case.
8. Gaming: gRPC is used in multiplayer gaming applications where real-time communication between the server and multiple clients is required. The low latency and high performance of gRPC make it ideal for this use case.
Publisher: EIRA team
LOST view: TV-Technical Agreements
Identifier: http://data.europa.eu/dr8/egovera/GRPCContract
EIRA traceability: eira:TechnicalInteroperabilityAgreementContract
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-08-03
dct:identifier: http://data.europa.eu/dr8/egovera/GRPCContract
dct:title: GRPC Contract
Definition: Agreement on Interoperability Security ABB is a Contract formalizing governance rules and conditions to grant the identification, authorization, and transmission of the data, information and knowledge being exchanged between digital public services.
Source: Inspired in the works by ISA2, and the EIF-related works
Source reference: https://ec.europa.eu/isa2/isa2_en
Additional information: The interoperability security pays special attention to the integrity of the data, the non-repudiation, and the verification of absence of malware or other malicious content in the exchanged information. Agreements on Interoperability Security are usually aggregated to more general security frameworks covering the security of the life cycle of the data, including the the secured disposition of the data and information (i.e., transfer or secured deletetion; cfr. MoReq retention policy and plan), etc.
Example: The following implementation is an example of how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): New EU Cybersecurity Strategy and new rules to make physical and digital critical entities more resilient. https://ec.europa.eu/commission/presscorner/detail/en/IP_20_2391
Interoperability Dimension: Governance IoP
LOST view: Organisational view
Interoperability Saliency: The Agreement on Interoperability Security ABB is salient for governance and behavioural interoperability because it (i) sets the conditions under which the collaboration between digital public services must take place in a secure and controlled way, and (ii) can define the security-related business capabilities of the digital public services that exchange data, information and knowledge.
Identifier: http://data.europa.eu/dr8/AgreementOnInteroperabilitySecurityContract
ABB name: eira:AgreementOnInteroperabilitySecurityContract
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/AgreementOnInteroperabilitySecurityContract
Interoperability Layer: Organisational
Description: Hawk Authentication is a protocol for making HTTP requests that are authenticated by using a Message Authentication Code (MAC) algorithm. It provides a mechanism for making these requests in a simple and standardized way, without the need for complex cryptographic protocols. Hawk Authentication ensures that the data transmitted between the client and server remains confidential and unaltered, providing a high level of security. It is often used in RESTful APIs and web applications.
Additional information: Hawk Authentication is a HTTP authentication scheme that provides a method for making authenticated HTTP requests with partial cryptographic verification of the request and response, covering the HTTP method, request URI, host, and optionally the request payload. It is a widely used protocol for securing APIs and web resources.
The Hawk Authentication scheme is based on the concept of a shared symmetric key between the client and the server. This shared key is never transmitted over the network, providing a significant increase in security over basic authentication methods that transmit the password in plaintext or encoded in Base64.
Hawk Authentication uses a set of server-generated credentials, including an identifier (id), a key, and an algorithm. The client uses these credentials to generate a request MAC (Message Authentication Code), which is included in the Authorization header of the HTTP request. The server, upon receiving the request, generates its own MAC using the same credentials and compares it to the client's MAC. If they match, the request is considered authentic.
In addition to the request MAC, Hawk Authentication also provides options for payload validation and response validation. Payload validation ensures the integrity of the request body by including a hash of the payload in the MAC calculation. Response validation provides a way for the client to verify the authenticity of the server's response.
Hawk Authentication also includes a mechanism for handling replay attacks. Each request includes a timestamp and a nonce value that are included in the MAC calculation. The server keeps track of these values and rejects any request with a duplicate nonce or a timestamp that is too far in the past.
Overall, Hawk Authentication provides a robust and secure method for authenticating HTTP requests, protecting against a variety of common attacks and ensuring the integrity of both the request and response.
Example: Hawk Authentication is a widely used HTTP authentication scheme that involves creating a MAC (Message Authentication Code) for HTTP requests. Here are some examples of applying the Hawk Authentication:
1. Web Application: Hawk Authentication can be used in a web application where the client and server need to communicate securely. The client creates a MAC using its credentials and sends it along with the HTTP request. The server then verifies the MAC to authenticate the client.
2. API Authentication: Hawk Authentication can be used for securing APIs. The client application creates a MAC using its API key and sends it along with the API request. The server then verifies the MAC to authenticate the API request.
3. Mobile Application: Hawk Authentication can be used in a mobile application where the mobile app needs to communicate with a server. The mobile app creates a MAC using its credentials and sends it along with the HTTP request. The server then verifies the MAC to authenticate the mobile app.
4. IoT Devices: Hawk Authentication can be used in IoT devices where the device needs to communicate with a server. The device creates a MAC using its credentials and sends it along with the HTTP request. The server then verifies the MAC to authenticate the device.
5. Microservices: In a microservices architecture, Hawk Authentication can be used to secure communication between different services. Each service creates a MAC using its credentials and sends it along with the HTTP request. The receiving service then verifies the MAC to authenticate the request.
Publisher: EIRA team
LOST view: TV-Technical Agreements
Identifier: http://data.europa.eu/dr8/egovera/HawkAuthenticationContract
EIRA traceability: eira:TechnicalInteroperabilityAgreementContract
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-08-03
dct:identifier: http://data.europa.eu/dr8/egovera/HawkAuthenticationContract
dct:title: Hawk Authentication Contract
Definition: Multi-Factor Authentication (MFA) is a security measure that requires users to provide two or more verification factors to gain access to a resource such as an application, online account, or a VPN. It is designed to provide an additional layer of protection, minimizing the risk of security breaches and data theft. The factors used in MFA could include something you know (like a password), something you have (like a hardware token or a smartphone), or something you are (like a fingerprint or other biometric method).
Source: EIRA team
Additional information: Multi-Factor Authentication (MFA) is a security system that requires more than one method of authentication from independent categories of credentials to verify the user's identity for a login or other transaction. It is designed to provide an additional layer of protection, making it harder for unauthorized users to gain access to a person's devices or online accounts because knowing the victim's password alone is not enough to pass the authentication check.
MFA works by requiring any two or more of the following authentication methods:
1. Something you know (knowledge), such as a password or PIN.
2. Something you have (possession), such as a badge, smartphone, or token.
3. Something you are (inherence), such as biometrics like fingerprints, voice recognition, or retinal scans.
In practice, this might mean entering a password (something you know) and then receiving a text message with a code to enter (something you have). Or it could involve scanning a fingerprint (something you are) and entering a PIN (something you know).
The goal of MFA is to create a layered defense system. If an attacker can compromise one method, such as guessing a password, they would still need to compromise the second or third method, which is significantly more difficult.
MFA is increasingly being used in areas beyond the traditional use of securing access to sensitive systems or data. It is now often used in everyday situations such as online banking, accessing work emails, or even social media accounts.
While MFA significantly improves security, it is not foolproof. For example, if a user loses their physical device used for authentication, an attacker could potentially gain access to it. However, the benefits of MFA in preventing unauthorized access generally outweigh the potential drawbacks.
Example: 1. Online Banking: Many banks require multi-factor authentication for online banking. This often involves entering a username and password (first factor), then receiving a text message or email with a one-time code (second factor) that must be entered to gain access.
2. Social Media Accounts: Platforms like Facebook, Instagram, and Twitter offer multi-factor authentication to protect users' accounts. After entering the password, the user may be required to enter a code sent to their mobile device or email.
3. Corporate Networks: Companies often use multi-factor authentication to protect sensitive data. Employees may be required to swipe an ID card (first factor), enter a password (second factor), and provide a fingerprint (third factor) to access the network.
4. Cloud Services: Providers like Google Drive, Dropbox, and iCloud use multi-factor authentication to protect users' files. This usually involves entering a password and then providing a second factor, such as a fingerprint or a code sent to a trusted device.
5. VPN Access: Virtual Private Networks (VPNs) often use multi-factor authentication to ensure only authorized users can access them. This could involve a combination of passwords, security tokens, and biometric data.
6. E-commerce Websites: To protect customers' financial information, many e-commerce sites use multi-factor authentication. This could involve entering a password and then providing a second factor, such as a code sent via text or email.
7. Health Services: Hospitals and clinics may use multi-factor authentication to protect patients' health records. This could involve a combination of ID cards, passwords, and biometric data like fingerprints or retinal scans.
8. Government Services: Government agencies often use multi-factor authentication to protect sensitive information and services. This could involve a combination of ID cards, passwords, and biometric data.
LOST view: TVA-Governance Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/Multi-FactorAuthenticationContract
EIRA traceability: eira:TechnicalInteroperabilityAgreementContract
ABB name: egovera:Multi-FactorAuthenticationContract
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-03
dct:identifier: http://data.europa.eu/dr8/egovera/Multi-FactorAuthenticationContract
dct:title: Multi-Factor Authentication Contract
Definition: A Blockchain IoP Agreement refers to a contractual agreement among European Member states to ensure interoperability in the field of Information Technology (IT). Interoperability, or IoP, refers to the ability of different IT systems and software applications to seamlessly communicate, exchange data, and operate together effectively. The Blockchain IoP Agreement aims to establish a standardized framework using blockchain technology, which enables secure and transparent data sharing and collaboration between various IT systems across European Member states. This agreement ensures that different IT systems can work together efficiently, promoting seamless communication and data exchange, ultimately enhancing the interoperability and efficiency of IT services within the European Union.
Source: EUR-Lex
Additional information: A Blockchain IoP (Interoperability) Agreement in the context of European IT interoperability among Member States refers to a formal agreement or framework that utilizes blockchain technology to enhance and ensure seamless interoperability between different information systems and digital services across European countries.
Interoperability, in this context, refers to the ability of various IT systems, applications, and services to communicate, exchange data, and work together effectively. It aims to eliminate barriers and enable smooth data sharing, collaboration, and interaction between different systems, regardless of their technological or organizational differences.
The Blockchain IoP Agreement is designed to address the challenges and complexities associated with achieving interoperability in the European Union (EU). It leverages blockchain technology, which is a decentralized and distributed ledger system that enables secure and transparent transactions and data sharing among multiple parties.
The agreement outlines the principles, standards, and protocols that Member States must adhere to in order to achieve interoperability. It establishes a common framework for data exchange, ensuring that information can be seamlessly shared and accessed across different systems while maintaining privacy, security, and data protection.
The blockchain technology employed in the agreement provides several benefits. Firstly, it ensures immutability and tamper-proofing of data, making it highly secure and resistant to unauthorized modifications. Secondly, it enables the creation of smart contracts, which are self-executing agreements that automatically enforce predefined rules and conditions. These smart contracts can facilitate automated and trustless interactions between different systems, reducing the need for intermediaries and enhancing efficiency.
The Blockchain IoP Agreement also defines the governance structure and mechanisms for decision-making, coordination, and dispute resolution among Member States. It establishes a collaborative environment where stakeholders can collectively work towards achieving interoperability goals. This may involve the establishment of a decentralized network or consortium of nodes, where each Member State operates a node and participates in the validation and verification of transactions and data exchanges.
Furthermore, the agreement may address issues related to data standards, semantics, and formats to ensure semantic interoperability, where data can be understood and interpreted consistently across different systems. It may also include provisions for data protection, privacy, and consent management, ensuring compliance with relevant EU regulations such as the General Data Protection Regulation (GDPR).
The Blockchain IoP Agreement aims to foster innovation, efficiency, and cost savings by enabling seamless data exchange and collaboration between Member States. It can facilitate the integration of various public services, such as healthcare, transportation, taxation, and e-government, leading to improved citizen experiences and streamlined administrative processes.
Overall, the Blockchain IoP Agreement represents a comprehensive and standardized approach to achieving IT interoperability among European Member States, leveraging blockchain technology to ensure secure, transparent, and efficient data exchange and collaboration.
Example: The application of Blockchain IoP (Interoperability) Agreement in the European IT interoperability among Member States can have several examples. Here are a few:
1. Cross-border data sharing: Blockchain IoP can facilitate secure and transparent cross-border data sharing among European Member States. For instance, if one country needs access to certain data stored in another country, the IoP agreement can ensure interoperability between the different systems, allowing seamless and trusted data exchange.
2. Digital identity verification: Blockchain IoP can be used for interoperable digital identity verification across European Member States. Instead of each country maintaining its own identity verification system, a blockchain-based IoP agreement can enable the sharing and verification of digital identities, ensuring seamless access to services across borders.
3. Supply chain management: Blockchain IoP can enhance interoperability in supply chain management across European countries. By implementing a common blockchain framework, different stakeholders in the supply chain, such as manufacturers, distributors, and retailers, can securely and transparently share information, track goods, and ensure compliance with regulations across borders.
4. E-government services: Blockchain IoP can enable interoperability among e-government services provided by different Member States. Citizens could access various government services, such as tax filing, healthcare, or social security, using a single digital identity and have their data securely shared across borders, reducing administrative burdens and enhancing efficiency.
5. Smart contracts and legal agreements: Blockchain IoP can facilitate the interoperability of smart contracts and legal agreements across European Member States. By using blockchain technology, smart contracts can be executed automatically and transparently, ensuring compliance with different legal frameworks and reducing the need for intermediaries in cross-border transactions.
Overall, the application of Blockchain IoP Agreement in European IT interoperability can lead to increased efficiency, transparency, and trust in various sectors, enabling seamless collaboration and data exchange among Member States.
LOST view: TVA-Governance Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/BlockChainIoPAgreementContract
EIRA traceability: eira:OrganisationalAgreementContract
ABB name: egovera:BlockChainIoPAgreementContract
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-05-22
dct:identifier: http://data.europa.eu/dr8/egovera/BlockChainIoPAgreementContract
dct:title: BlockChain IoP Agreement
Definition: Technical Agreement ABB is a Contract formalising a framework and a privileged forum to identify common interests, priorities, policy dialogue, and the necessary tools for Strategic & Technological collaboration.
Source: EUR-LEX
Source reference: https://eur-lex.europa.eu/collection/eu-law/inter-agree.html
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): WTO Data Exchange technical agrement: The agreement regulates the echange of data between systems and applications. https://olc.worldbank.org/sites/default/files/PMT-4.pdf
IoP Dimension: Governance IoP
LOST view: Technical view - application
Interoperability saliency: The Technical Agreement ABB is a key interoperability enabler because it supports technical governance interoperability by enabling collaboration between digital public services.
Identifier: http://data.europa.eu/dr8/TechnicalAgreementContract
eira:ID: ABB377
ABB name: eira:TechnicalAgreementContract
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2022-17-01
Description: Digest Authentication is a method used in computing to authenticate a user and verify their access rights to a system or server. It is a protocol that operates at the application layer of a network's protocol stack, and it is designed to reduce the potential risk of transmitting passwords in plain text, which basic authentication does. Instead of sending passwords in plain text, Digest Authentication uses a hash function on the password and other data to generate a unique string, or 'digest', which is then sent across the network. This makes it more difficult for unauthorized users to intercept and decipher the password.
Additional information: Digest Authentication is a method used to authenticate a user or a client before granting them access to a particular resource or system. It is a protocol that is part of the Internet Engineering Task Force (IETF) HTTP protocol suite. Digest Authentication is an improvement over Basic Authentication, which transmits user credentials in plaintext, making it vulnerable to interception and misuse.
In Digest Authentication, the user credentials are not sent over the network in plaintext. Instead, the credentials are hashed using a cryptographic function, such as MD5, and then sent to the server. This makes it more difficult for an attacker to gain access to the actual credentials.
The process of Digest Authentication involves several steps:
1. The client sends a request to the server.
2. The server responds with a special code known as a "nonce" (a number used once), along with a 401 Unauthorized response.
3. The client responds by sending an encrypted response that includes the username, the password, the given nonce, the HTTP method, and the requested URL.
4. The server then verifies this information. If the information is correct, the server grants access to the requested resource. If the information is incorrect, the server denies access.
Digest Authentication provides a more secure method of authentication than Basic Authentication. However, it is not foolproof. For example, it is vulnerable to man-in-the-middle attacks, where an attacker intercepts the communication between the client and the server. Additionally, if an attacker gains access to the hashed credentials, they can use a rainbow table to potentially discover the plaintext password.
Despite these vulnerabilities, Digest Authentication is still widely used in situations where the transmission of credentials in plaintext is unacceptable, and where more secure methods of authentication, such as HTTPS or SSL, are not available or practical.
Example: Digest Authentication is a method used to authenticate a user, where the user's credentials are not sent in plaintext over the network. Instead, a hash function is used to send a digest (a unique string of characters) to the server. Here are some examples of applying Digest Authentication:
1. Web Services: Digest Authentication is often used in web services where the client needs to authenticate itself to the server. The client sends a request to the server, the server responds with a nonce (a random value that can only be used once), the client then hashes its username, password, and the nonce, and sends this hash back to the server. The server performs the same hash function and if the results match, the client is authenticated.
2. SIP Protocol: The Session Initiation Protocol (SIP), used for controlling multimedia communication sessions such as voice and video calls over Internet Protocol (IP), uses Digest Authentication to authenticate users. When a user attempts to initiate a session, the SIP server challenges the user for credentials. The user then responds with a digest, which is a hash of the username, password, session ID, and a server-provided nonce.
3. HTTP Protocol: Digest Authentication is also used in HTTP where it provides a more secure alternative to Basic Authentication. When a client sends a request to access a protected resource on a web server, the server sends back a nonce. The client then creates a hash using its credentials and the nonce and sends this back to the server. If the server can create the same hash with the stored credentials, it grants access to the resource.
4. IoT Devices: Internet of Things (IoT) devices, such as smart home devices, also use Digest Authentication to ensure that only authorized users can access and control them. The device will challenge anyone attempting to access it for their credentials, and only grant access if the hashed response matches what it expects.
5. VPN Connections: Virtual Private Networks (VPNs) can use Digest Authentication to verify the identity of users trying to establish a secure connection. This adds an extra layer of security to the VPN, making it harder for unauthorized users to gain access.
Publisher: EIRA team
LOST view: TV-Technical Agreements
Identifier: http://data.europa.eu/dr8/egovera/DigestAuthContract
EIRA traceability: eira:TechnicalInteroperabilityAgreementContract
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-08-03
dct:identifier: http://data.europa.eu/dr8/egovera/DigestAuthContract
dct:title: Digest Auth Contract
Description: The OpenAPI is a specification for building APIs (Application Programming Interfaces) that allows for a standard, language-agnostic interface to RESTful APIs. It is used to design, build, document, and consume REST APIs, enabling interoperability between different systems. The OpenAPI specification, formerly known as the Swagger specification, is developed by the OpenAPI Initiative, which includes more than 30 organizations from different areas of the tech industry.
Additional information: OpenAPI, formerly known as Swagger, is a specification for machine-readable interface files for describing, producing, consuming, and visualizing RESTful web services. It is a set of rules and protocols that provide a definition and structure for how an application should interact with a RESTful API.
OpenAPI is language-agnostic, meaning it can be used with any programming language that supports RESTful APIs. It is also platform-agnostic, meaning it can be used on any platform that supports HTTP.
The OpenAPI specification (OAS) defines a standard, language-agnostic interface to RESTful APIs which allows both humans and computers to discover and understand the capabilities of the service without access to source code, documentation, or through network traffic inspection. When properly defined, a consumer can understand and interact with the remote service with a minimal amount of implementation logic.
An OpenAPI definition can then be used by documentation generation tools to display the API, code generation tools to generate servers and clients in various programming languages, testing tools, and many other use cases.
The OpenAPI Specification is developed within the OpenAPI Initiative, a consortium of industry experts that have come together to build a common, open specification that offers real value across a diverse array of applications and industries. The members of the OpenAPI Initiative represent a broad array of companies from different sectors of the economy including technology, telecommunications, banking, retail, energy, media, and more.
The OpenAPI Specification is free to use and the OpenAPI Initiative encourages its adoption by providing a variety of resources for individuals and organizations interested in learning more about the specification, its applications, and its benefits.
Example: 1. API Documentation: OpenAPI can be used to create clear and concise documentation for APIs. This documentation can be used by developers to understand how to use the API, what data it returns, and what parameters it accepts.
2. API Testing: OpenAPI specifications can be used to generate test cases for APIs. This helps in ensuring that the API is working as expected and any changes or updates do not break existing functionality.
3. API Design: OpenAPI can be used to design APIs before they are actually built. This helps in getting feedback from potential users and making necessary changes before the actual development begins.
4. API Mocking: OpenAPI can be used to create mock servers. These servers mimic the behavior of the actual API and can be used for testing and development purposes.
5. API Gateway Configuration: OpenAPI can be used to configure API gateways. This includes defining routes, setting up rate limiting, and configuring security settings.
6. Client SDK Generation: OpenAPI can be used to generate client SDKs in various programming languages. This helps in speeding up the development process as developers do not have to write code to interact with the API from scratch.
7. Server Stub Generation: OpenAPI can be used to generate server stubs. This is useful in the initial stages of development when the actual API is not yet available.
8. API Versioning: OpenAPI can be used to manage different versions of an API. This helps in maintaining backward compatibility and managing changes in the API.
9. API Discovery: OpenAPI can be used to create a searchable catalog of APIs. This makes it easier for developers to find and use APIs that meet their requirements.
10. API Monitoring: OpenAPI can be used to monitor the performance and usage of APIs. This helps in identifying issues and optimizing the API for better performance.
Publisher: EIRA team
LOST view: TV-Technical Agreements
Identifier: http://data.europa.eu/dr8/egovera/OpenAPIContract
EIRA traceability: eira:TechnicalInteroperabilityAgreementContract
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-08-03
dct:identifier: http://data.europa.eu/dr8/egovera/OpenAPIContract
dct:title: OpenAPI Contract
Definition: Organisational Interoperability Agreement ABB is a Contract formalising governance rules enabling collaboration between digital public services with enabling seamless interoperability enablement value.
Source: Inspired in the works by ISA2, and the EIF-related works
Source reference: https://ec.europa.eu/isa2/isa2_en
Additional information: (*)DECISION (EU) 2015/2240 OF THE EUROPEAN PARLIAMENT AND OF THE COUNCIL of 25 November 2015 establishing a programme on interoperability solutions and common frameworks for European public administrations, businesses and citizens (ISA2 programme) as a means for modernising the public sector. 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).
Example: ICAO Service Level Agreement Template - A Service Level Agreement (SLA) is an example of Interoperability Agreement in which parties agree on the description of the services to be provided by one or several parties to the other one(s). The SLA tackles topics like: service description, optional services, exclusions, limitations, service levels, service credits, escalation procedure, reporting and points of contact. (https://www.icao.int/ESAF/Documents/APIRG/APIRG18/Docs/wp17_appendices_en.pdf)
IoP Dimension: Governance IoP, Behavioural IoP
LOST view: Organisational view
Interoperability saliency: The Organisational Interoperability Agreement ABB is a key interoperability enabler (*) for governance and behavioural interoperability by (i) binding documents which set out the precise obligations of two parties cooperating across an ‘interface’ to achieve interoperability; (ii) enabling the collaborations and data flows established between the public digital services, and (iii) enabling digital business capabilities expected from the public digital services.
Identifier: http://data.europa.eu/dr8/OrganisationalInteroperabilityAgreementContract
eira:ID: ABB119
ABB name: eira:OrganisationalInteroperabilityAgreementContract
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2022-13-01
Definition: Service Level Agreement ABB is a Contract formalising the agreement between a service provider and a customer or client that outlines the level of service that will be provided, as well as the metrics that will be used to measure the quality of the service
Source: EIF
Source reference: https://ec.europa.eu/isa2/sites/isa/files/eif_brochure_final.pdf#page=27
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): ETA - The European Technical Assessment (ETA) is an alternative for construction products not covered by a harmonised standard. It is a document providing information on their performance assessment. The procedure is established in the Construction Products Regulation and offers a way for manufacturers to draw up the Declaration of Performance and affix the CE marking. It contributes to the free movement of construction products and the creation of a strong Single Market. https://ec.europa.eu/growth/sectors/construction/product-regulation/european-assessment_en
IoP Dimension: Governance IoP
LOST view: Technical view - application
Interoperability saliency: The Service Level Agreement ABB is a key interoperability enabler that introduces the agreed terms and conditions for the delivery a services. The SLA is relevant and enables interoperability because include the conditions that will determine and guide the delivery and therefore, the aspects regarding interoperability with regard of services, data and infrastructures.
Identifier: http://data.europa.eu/dr8/ServiceLevelAgreementContract
eira:ID: http://data.europa.eu/dr8/ServiceLevelAgreementContract
ABB name: eira:ServiceLevelAgreementContract
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2022-17-01
DEFINITION:
Framework Agreement ABB is a Contract providing an arrangement between one or more entity that provide the terms governing contracts to be established for a certain period of time, in particular with regard to price and, where necessary, the quantity envisaged. Other repetitive conditions known in advance, such as the place of delivery, may be included. They are also called blanket purchase agreements and master ordering agreements. Essentially, they are intended to provide expeditious ordering of commonly used, off-the-shelf goods, purchased on the basis of lowest price.
Source: Unece
(https://tfig.unece.org/contents/framework-agreements.htm)
EXAMPLES:
The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB):
Ew-Shopp:
WeatherOntology.owl17 by Automation Systems Group of Technical University of Wien is a smart home ontology for weather phenomena and exterior conditions. It was issued in 2011
and the ontology imports and extends W3C’s Time ontology. The ontology covers a wide
range of weather and climate data, such as atmospheric pressure, humidity, precipitation,
temperature, wind, etc. The ontology was reviewed in deliverable D3.3 (v2)18 of the
READY4SmartCities (ICT Roadmap and Data Interoperability for Energy Systems in Smart
Cities) FP7 European project (Grant Agreement No. 608711) in September 2015.
Source: (https://ec.europa.eu/research/participants/documents/downloadPublic?documentIds=080166e5b4c5d61e&appId=PPGMS)
Definition: Legal Interoperability Agreement ABB is a Contract formalizing governance rules enabling collaboration between digital public services.
Source: EIF
Source reference: https://ec.europa.eu/isa2/sites/isa/files/eif_brochure_final.pdf#page=27
Additional information: The legal Interoperability Agreement ABB is a specialisation of the Legal Agreement. It aims to coordinate or harmonize efficient exchange models between digital public services within a Public Administration and/or cross Public Administrations.
Example: RDA-CODATA - Agreement that provides the guidelines and principles on the legal interoperability of research data. (http://www.codata.org/uploads/Legal%20Interoperability%20Principles%20and%20Implementation%20Guidelines_Final2.pdf)
IoP Dimension: Governance IoP, Behavioural IoP
LOST view: Legal view
Interoperability saliency: The Legal Interoperability Agreement ABB is a key interoperability enabler (*) for governance, organizational and legal interoperability by (i) foundations and requirements that enable the seamless exchange of data, information, and knowledge; and (ii) agreement on digital business capabilities that can map locally aligned processes between public administrations.
Identifier: http://data.europa.eu/dr8/LegalInteroperabilityAgreementContract
eira:ID: ABB226
ABB name: eira:LegalInteroperabilityAgreementContract
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-10-01
Description:
The Request-Response pattern is a basic communication method where one system sends a request for data, and another system processes the request and returns a response. Typically used in client-server architectures, this pattern ensures a two-way conversation between applications. In its synchronous form, like HTTP web service calls, the requester waits for a reply before proceeding. Asynchronous versions also exist, where responses may arrive later, often used in systems requiring time-consuming operations, such as human workflows or complex data aggregation.
This model contrasts with one-way communication, where no reply is expected.
Publisher: W3C
Source: https://www.w3.org/2000/xp/Group/1/10/11/2001-10-11-SRR-Transport_MEP
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/RequestResponseMessagePatternInteroperabilitySpecificationContract
LOST view: Technical view - application
EIRA concept: eira:SolutionBuildingBlock
Additional identifier: http://data.europa.eu/dr8/RequestResponseMessagePatternInteroperabilitySpecificationContract
ABB name: eira:RequestResponseMessagePatternInteroperabilitySpecificationContract
EIF Layer: N/A
Interoperability Dimension: Behavioral IoP
Interoperability Saliency: The interoperability specification ABB is salient for legal interoperability because it establishes the normative statements for ensuring interoperability in public services. This ABB is salient for organizational interoperability by establishing the business principles to exchange data between public services. The Interoperability specification ABB is salient for semantic interoperability too in terms of identifying technical standards for the exchange of information between public services. And finally, the ABB is salient for technical interoperability due to it determines the technical requirements to implement the interoperability between public services.
Additional information: Key Points: 1)
One-to-one communication; 2)
Synchronous interaction, where the client waits for the response; 3)
Common in web services, APIs, and remote procedure calls.
Description: NTLM, which stands for NT LAN Manager, is a suite of Microsoft security protocols that provides authentication, integrity, and confidentiality to users. It is the successor of the LAN Manager protocol from IBM and was the default protocol used by the Windows NT 4.0 operating system. NTLM is used for authentication in various network protocols, including SMB, RPC, and HTTP, and is supported by all subsequent Windows versions for backward compatibility, although Microsoft recommends using Kerberos instead for newer versions.
Additional information: NTLM, which stands for NT LAN Manager, is a suite of Microsoft security protocols that provides authentication, integrity, and confidentiality to users. It is an older authentication protocol used by Microsoft Windows systems in a networked environment, and it was the primary authentication protocol in Windows NT 4.0 and Windows 2000.
NTLM uses a challenge-response mechanism for authentication, where the server sends a challenge to the client, the client responds, and then the server verifies the response. This process helps to ensure that the user's password is never sent across the network, which can help to improve security.
NTLM is composed of three messages, namely, Type 1 (negotiation), Type 2 (challenge) and Type 3 (authentication). The client initiates the authentication process by sending a Type 1 message to the server. The server responds with a Type 2 message that contains a challenge, which is a randomly generated number. The client then responds with a Type 3 message that contains the response to the challenge, which is computed using the user's password.
While NTLM is still supported by Microsoft, it has been replaced in newer versions of Windows by more secure protocols such as Kerberos. NTLM is considered to be less secure than these newer protocols because it is vulnerable to various types of attacks, such as replay attacks and brute force attacks. Therefore, it is generally recommended to use NTLM only when necessary for compatibility reasons, and to use more secure protocols whenever possible.
In addition, NTLM does not support modern security features such as claims-based identity, federation, or multi-factor authentication. It also does not provide a mechanism for server authentication, which can leave users vulnerable to man-in-the-middle attacks.
Example: NTLM (NT LAN Manager) is a suite of Microsoft security protocols that provides authentication, integrity, and confidentiality to users. Here are some examples of applying NTLM:
1. Network Authentication: NTLM is often used in network authentication where client applications need to authenticate to servers. For example, when a user logs into a Windows computer that is part of a Windows domain, the user's NTLM credentials are used to authenticate the user to the domain controller.
2. Web Authentication: NTLM can also be used for web authentication. For example, when a user tries to access a protected Microsoft IIS web server, the server can use NTLM to authenticate the user. The user's web browser will typically prompt the user for their username and password, and then use these credentials to authenticate to the server using NTLM.
3. Database Authentication: NTLM is also used in database authentication. For instance, when a user tries to connect to a Microsoft SQL Server database, the server can use NTLM to authenticate the user. The client application (e.g., SQL Server Management Studio) will typically prompt the user for their username and password, and then use these credentials to authenticate to the server using NTLM.
4. Email Authentication: NTLM can be used for email authentication in Microsoft Exchange Server. When a user tries to access their mailbox, the server can use NTLM to authenticate the user. The user's email client (e.g., Microsoft Outlook) will typically prompt the user for their username and password, and then use these credentials to authenticate to the server using NTLM.
5. File Sharing: NTLM is used in file sharing protocols like SMB (Server Message Block) used by Windows for shared folders. When a user tries to access a shared folder, the server can use NTLM to authenticate the user.
Publisher: EIRA team
LOST view: TV-Technical Agreements
Identifier: http://data.europa.eu/dr8/egovera/NTLMContract
EIRA traceability: eira:TechnicalInteroperabilityAgreementContract
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-08-03
dct:identifier: http://data.europa.eu/dr8/egovera/NTLMContract
dct:title: NTLM Contract
Description: The Open Data Protocol (OData) specification is a protocol developed by Microsoft for building and consuming RESTful APIs. It allows clients to query and manipulate data using standard HTTP protocols. OData APIs expose data as resources that are addressable by URLs. It supports CRUD operations (Create, Read, Update, Delete) and provides a way to describe the data model and the functions available for each resource. This makes it easy for clients to interact with the data in a more standard and simplified way.
Additional information: The Open Data Protocol (OData) is an open standard that defines a set of best practices for building and consuming RESTful APIs. It was initiated by Microsoft and is now an ISO/IEC approved OASIS standard. OData enables the creation of HTTP-based data services, which allow resources, identified using Uniform Resource Identifiers (URIs) and defined in an abstract data model, to be published and edited by web clients using simple HTTP messages.
OData is built upon the AtomPub protocol and JSON format, which provides a way to exchange data over the web in a simple and standard way. It provides a uniform way to expose, structure, and manipulate data on the web, regardless of the storage medium. This allows for the creation of RESTful APIs, which can be easily accessed and consumed by any client capable of sending HTTP requests and parsing XML/JSON responses.
The OData specification covers the following aspects:
1. Conventions for OData Service URLs: OData services are identified by their service root URIs. The conventions for addressing and accessing data expose a hierarchical model to the clients.
2. Conventions for OData Payloads: OData supports two formats for representing data: AtomPub (XML-based) and JSON. The conventions define the structure of the payloads and the way data is represented.
3. Querying Data: OData includes a set of query options that allow clients to filter, sort, and navigate data.
4. CRUD Operations: OData services support Create, Read, Update, and Delete (CRUD) operations using standard HTTP verbs (POST, GET, PUT/PATCH, DELETE).
5. Service Metadata Document: OData services expose a service metadata document that describes the data model of the service (the structure of the data).
6. Batch Processing: OData includes support for grouping multiple operations into a single HTTP request payload.
7. Asynchronous Processing: OData includes support for processing requests asynchronously.
8. Customization and Extensibility: OData allows services to be customized and extended to meet specific needs.
The OData specification is designed to provide a rich and flexible way to interact with data on the web. It allows clients to easily navigate through data, perform operations on data, and receive results in a predictable and easy-to-handle format.
Example: 1. Customer Relationship Management (CRM) Systems: OData can be used in CRM systems to access, update, or delete data. For example, Microsoft Dynamics 365 uses OData for its Web API.
2. Business Intelligence Tools: Tools like Power BI, Tableau, or SAP Analytics Cloud use OData to connect to various data sources and provide real-time analytics and insights.
3. Mobile Applications: Mobile apps can use OData to consume data from a server. For example, an app might use OData to display user data from a server, allowing the app to stay up-to-date with the most recent data.
4. Content Management Systems: CMS like SharePoint use OData as a protocol to expose data. This allows users to interact with the data in a standardized way, regardless of the underlying storage system.
5. Data Integration: OData can be used to integrate data from different sources. For example, a company might use OData to pull data from different databases into a single, unified view.
6. IoT Devices: Internet of Things devices can use OData to send data back to a central server. This allows the devices to be managed and monitored remotely.
7. E-Commerce Platforms: E-commerce platforms like Magento use OData to expose product, customer, and order data to other systems, such as ERP or CRM systems.
8. Public APIs: Many public APIs, such as the Netflix API, use OData to allow developers to query and manipulate data. This makes it easier for developers to build applications that interact with these services.
Publisher: EIRA team
LOST view: TV-Technical Agreements
Identifier: http://data.europa.eu/dr8/egovera/ODataContract
EIRA traceability: eira:TechnicalInteroperabilityAgreementContract
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-08-03
dct:identifier: http://data.europa.eu/dr8/egovera/ODataContract
dct:title: OData Contract
Definition: European Legal Interoperability Agreement ABB is a Contract formalizing governance rules enabling collaboration amongst the EU and EEA Member States digital public services.
Source: Based on the definition in the EIF about Legal Interoperability Agreement and existing European legal interoperability agreements
Source reference: https://ec.europa.eu/isa2/sites/isa/files/eif_brochure_final.pdf#page=27
Additional information: The European Legal Interoperability Agreement ABB is a specialisation of the Legal Interoperability Agreement ABB. It is considered a Shared Legal Content because it enables interoperability between different EU MS and stakeholders.
Example: The following implementation is an example of how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): ELI, standing for European Legislation Identifier, is based on a voluntary agreement between EU countries, and aims to facilitate access, sharing and interconnection of legal information published in national, European and global systems. This facilitates their availability as open datasets, fostering their re-use.
IoP Dimension: Governance IoP, Behavioural IoP
LOST view: Legal view
Interoperability saliency: The European Legal Interoperability Agreement ABB is salient for the governance of interoperability because it lays the European framework between public administration to enable the interoperability between public services. The European Legal Interoperability Agreement ABB is also salient for the legal interoperability due to the legal foundations and requirements that enable the seamless exchange of data, information, and knowledge between European and EEA Member State digital public services. The European Legal Interoperability Agreement ABB is also salient for the organizational interoperability since, as a consequence of the agreement, digital business capabilities can be mapped and subsequently, the process can be aligned between the Member State and EEA Public Administrations and digital public services.
Identifier: https://joinup.ec.europa.eu/data/dr8/EuropeanLegalInteroperabilityAgreement
eira:ID: https://joinup.ec.europa.eu/data/dr8/EuropeanLegalInteroperabilityAgreement
ABB name: EuropeanLegalInteroperabilityAgreement
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2022-18-01
Description: The Simple Object Access Protocol (SOAP) specification is a messaging protocol that allows programs running on different operating systems to communicate with each other over the internet, typically using HTTP. It is a standard protocol defined by the World Wide Web Consortium (W3C) for exchanging structured information in web services using XML. SOAP can be used for exchanging complete documents or calling a remote procedure. It is platform-independent, language-independent, and can be used in different network protocols, making it highly versatile for web service interactions.
Additional information: Simple Object Access Protocol (SOAP) is a messaging protocol specification for exchanging structured information in the implementation of web services in computer networks. It uses XML (Extensible Markup Language) to encode its messages and relies on application layer protocols, most often Hypertext Transfer Protocol (HTTP) or Simple Mail Transfer Protocol (SMTP), for message negotiation and transmission.
SOAP can form the foundation layer of a web services protocol stack, providing a basic messaging framework upon which web services can be built. This XML-based protocol consists of three parts: an envelope, which defines the content of the message and how to process it, a set of encoding rules for expressing instances of application-defined datatypes, and a convention for representing remote procedure calls and responses.
SOAP can be used for program-to-program communication through a network. It allows programs running on disparate operating systems such as Windows and Linux to communicate with each other. It also allows you to communicate between different programming languages like Java, .NET, and Python.
SOAP messages are independent of any operating system or protocol and can be transported using a variety of internet protocols, including SMTP, MIME, and HTTP. This makes it a versatile and widely used standard for web services communication.
SOAP provides the Application Programming Interface (API) that allows web services to interact with one another. It also provides a way to communicate between applications running on different operating systems, with different technologies and programming languages.
In summary, SOAP is a protocol specification for exchanging structured information in the implementation of web services in computer networks. It uses XML for its message format, and can be used over a variety of transport protocols such as HTTP, SMTP, and more.
Example: 1. Web Services: SOAP is commonly used in web services within the internet for communication. It allows different applications to communicate with each other over the internet to share information and services. For instance, a travel booking website might use a SOAP message to request flight information from an airline's web service.
2. Remote Procedure Calls: SOAP can be used to implement remote procedure calls (RPCs), where one software application on one computer sends a request to a software application on another computer and waits for a response. This is often used in distributed computing and cloud services.
3. Data Exchange: SOAP can be used to exchange structured and typed information between peers in a decentralized, distributed environment. For instance, a weather application might use SOAP to request data from a weather service.
4. Enterprise Software Communication: In large organizations, different software systems often need to communicate with each other. For example, a Customer Relationship Management (CRM) system might need to interact with an Order Management System (OMS). SOAP can be used to facilitate this communication.
5. Financial Services: In the financial industry, SOAP is often used to exchange information in real-time. For example, a stock trading application might use SOAP to send a buy or sell order to a stock exchange.
6. Healthcare Services: In healthcare, SOAP can be used to exchange patient data between different systems. For example, a hospital's patient management system might use SOAP to send patient records to a government health department.
Publisher: EIRA team
LOST view: TV-Technical Agreements
Identifier: http://data.europa.eu/dr8/egovera/SimpleObjectAccessProtocolContract
EIRA traceability: eira:TechnicalInteroperabilityAgreementContract
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-08-03
dct:identifier: http://data.europa.eu/dr8/egovera/SimpleObjectAccessProtocolContract
dct:title: Simple Object Access Protocol Contract
Definition: Agreement on Provision of Digital Public Services ABB is a Contract formalizing governance rules and conditions for the functioning of digital public services when delivering the service.
Source: Inspired in the works by ISA2, and the EIF-related works
Source reference: https://ec.europa.eu/isa2/isa2_en
Example: The following implementation is an example of how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): Digital Services Act: Commission welcomes political agreement on rules ensuring a safe and accountable online environment https://ec.europa.eu/commission/presscorner/detail/en/ip_22_2545
IoP Dimension: Governance IoP, Behavioural IoP
LOST view: Organisational view
Interoperability saliency: The Agreement on Provision of Digital Public Services ABB is salient for governance and behavioural interoperability because it (i) specifies concrete and binding rules and service conditions which set out the expected obligations and functionality of a digital public service that has to provide content to other consumer services, and (ii) defines the digital business capabilities and functionality expected by those services that will consume the content.
Identifier: http://data.europa.eu/dr8/AgreementOnProvisionOfDigitalPublicServicesContract
eira:ID: http://data.europa.eu/dr8/AgreementOnProvisionOfDigitalPublicServicesContract
ABB name: eira:AgreementOnProvisionOfDigitalPublicServicesContract
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 21/04/2021
Definition: Agreement on Data Sharing ABB is a Contract formalizing the information requirements, syntax bindings, protocols and semantic artefacts that must be used for the exchange of data.
Source: Inspired in the works by ISA2 (e.g. SEMIC), and the EIF-related works
Source reference: https://ec.europa.eu/isa2/isa2_en
Additional information: Semantic and business rules as well as validation methods, artefacts and solutions are expected to be mentioned in the contract.
Example: The following implementation is an example of how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): PEPPOL's data sharing agreements
Interoperability Dimension: Governance IoP
LOST view: Organisational view
Interoperability Saliency: Agreements on Data Sharing are salient for governance and behavioural interoperability because (i) it sets the rules necessary for the security and quality assurance of the data to be exchanged, (ii) the agreements on data sharing indicate the business capabilities and technical resources agreed to execute the control on the security and quality of the data being that is exchanged.
Identifier: http://data.europa.eu/dr8/AgreementOnDataSharingContract
ABB name: eira:AgreementOnDataSharingContract
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/AgreementOnDataSharingContract
Interoperability Layer: Organisational
Definition: Semantic interoperability agreement ABB is a Contract formalizing governance rules enabling collaboration between digital public services with ontological value.
Source: Joinup
Source reference: https://joinup.ec.europa.eu/sites/default/files/document/2015-03/Process
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): e-Invoicing Semantic Data Model - The semantic data model includes only the essential information elements that an electronic invoice needs to ensure legal (including fiscal) compliance and to enable interoperability for cross-border, cross-sector and for domestic trade. The semantic data model may be used by public and private sector organisations for public procurement invoicing and took into account the physical and financial supply chain perspective, reflecting both private and public sector requirements, with a view to allowing the full straight-through processing of an electronic invoice. https://ec.europa.eu/cefdigital/wiki/display/CEFDIGITAL/2017/06/28/CEN+Publishes+eInvoicing+Semantic+Data+Model
IoP Dimension: Governance IoP
LOST view: Semantic view
Interoperability saliency: The Semantic Interoperability Agreement ABB is a key interoperability enabler (*) for governance interoperability by enabling the understanding of information and collaboration between digital public services.
Identifier: http://data.europa.eu/dr8/SemanticInteroperabilityAgreementContract
eira:ID: ABB232
ABB name: eira:SemanticInteroperabilityAgreementContract
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-16-01
Description: The Streaming message exchange pattern involves the continuous flow of data between a producer and a consumer over time. Unlike the request-response pattern, streaming supports real-time data transfer where a large volume of data can be processed incrementally, as it arrives. The consumer does not need to wait for the entire dataset to be available before acting on it, making it suitable for real-time applications.
Publisher: Based on largely adopted standards
Source: https://www.confluent.io/learn/data-streaming/
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/StremmingMessagePatternInteroperabilitySpecificationContract
LOST view: Technical view - application
EIRA concept: eira:SolutionBuildingBlock
Additional identifier: http://data.europa.eu/dr8/StremmingMessagePatternInteroperabilitySpecificationContract
ABB name: eira:StremmingMessagePatternInteroperabilitySpecificationContract
EIF Layer: N/A
Interoperability Dimension: Behavioral IoP
Interoperability Saliency: The interoperability specification ABB is salient for legal interoperability because it establishes the normative statements for ensuring interoperability in public services. This ABB is salient for organizational interoperability by establishing the business principles to exchange data between public services. The Interoperability specification ABB is salient for semantic interoperability too in terms of identifying technical standards for the exchange of information between public services. And finally, the ABB is salient for technical interoperability due to it determines the technical requirements to implement the interoperability between public services.
Additional information: Key Points:
1) Continuous flow of data over time; 2)
Suitable for real-time processing; 3)
Common in scenarios with large datasets or real-time updates.
Description: The Publish-Subscribe message pattern refers to ne input channel that splits into multiple output channels, one for each subscriber. When an event is published into the channel, the Publish-Subscribe Channel delivers a copy of the message to each of the output channels. Each output channel has only one subscriber, which is only allowed to consume a message once. In this way, each subscriber only gets the message once and consumed copies disappear from their channels.
Publisher: Enterprise Patterns
Source: https://www.enterpriseintegrationpatterns.com/patterns/messaging/PublishSubscribeChannel.html
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/PublishSubscribeMessagePatternInteroperabilitySpecificationContract
LOST view: Technical view - application
EIRA concept: eira:SolutionBuildingBlock
Additional identifier: http://data.europa.eu/dr8/PublishSubscribeMessagePatternInteroperabilitySpecificationContract
ABB name: eira:PublishSubscribeMessagePatternInteroperabilitySpecificationContract
EIF Layer: N/A
Interoperability Dimension: Behavioral IoP
Interoperability Saliency: The interoperability specification ABB is salient for legal interoperability because it establishes the normative statements for ensuring interoperability in public services. This ABB is salient for organizational interoperability by establishing the business principles to exchange data between public services. The Interoperability specification ABB is salient for semantic interoperability too in terms of identifying technical standards for the exchange of information between public services. And finally, the ABB is salient for technical interoperability due to it determines the technical requirements to implement the interoperability between public services.
Additional information: A Publish-Subscribe Channel can be a useful debugging tool. Even though a message is destined to only a single receiver, using a Publish-Subscribe Channel allows you to eavesdrop on a message channel without disturbing the existing message flow. Monitoring all traffic on a channel can be tremendously helpful when debugging messaging applications. It can also save you from inserting a ton of print statements into each application that participates in the messaging solution. Creating a program that listens for messages on all active channels and logs them to a file can realize many of the same benefits that a Message Store brings.
Description: This voluntary code of conduct was developed by the European Commission's Joint Research Centre to improve the energy efficiency and environmental sustainability of data centers. It provides guidelines and best practices for data center operators to reduce their environmental impact.
Additional information: The European Code of Conduct for Data Centres is a voluntary initiative managed by the Joint Research Centre (JRC), the European Commission’s science and knowledge service. It primarily addresses data centre owners and operators, and secondly the supply chain and service providers. The Code of Conduct aims to reduce energy consumption in data centres in a cost-effective manner without hampering their critical function.
Example: A data centre operator could conduct an energy audit to identify areas where energy is being wasted. For example, they might find that their servers are using more power than necessary during off-peak hours. Based on these findings, they could create an Action Plan to reduce energy usage, such as implementing server virtualization to consolidate workloads and reduce the number of physical servers needed, or using energy-efficient cooling systems.
Publisher: Joint Research Centre
Source: https://joint-research-centre.ec.europa.eu/scientific-activities-z/energy-efficiency/energy-efficiency-products/code-conduct-ict/code-conduct-energy-efficiency-data-centres_en
LOST view: OV-Data Spaces
Identifier: http://data.europa.eu/dr8/egovera/CodeOfConductForEnergyEfficiencyInDataCentresContract
EIRA traceability: eira:OrganisationalAgreementContract
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-07-07
dct:identifier: http://data.europa.eu/dr8/egovera/CodeOfConductForEnergyEfficiencyInDataCentresContract
dct:title: Code of Conduct for Energy Efficiency in Data Centres
Definition: Agreement on Privacy ABB is a Contract that enables a set of rules for the personal data of individuals' collection, processing and transference by public administrations.
Source: Inspired in Data Protection Law by European Comission
Source reference: https://commission.europa.eu/law/law-topic/data-protection/data-protection-eu_en
Example: The following implementation is an example of how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): EU-U.S. Data Privacy Framework. https://ec.europa.eu/commission/presscorner/detail/en/qanda_22_6045
LOST view: Organisational view
Interoperability saliency: Agreement on Privacy ABB is salient for governance interoperability because it represents the specific rules established to establish the privacy and security framework.
Identifier: http://data.europa.eu/dr8/AgreementOnPrivacyContract
eira:ID: http://data.europa.eu/dr8/AgreementOnPrivacyContract
ABB name: eira:AgreementOnPrivacyContract
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2022-20-01
Definition: Organisational Agreement ABB is a Contract enabling any agreement to which the Organisation or any Restricted Subsidiary is a party pursuant.
Source: Inspired in the Law Insider dictionary definition
Source reference: https://www.lawinsider.com/dictionary/organizational-agreement
Synonym: Governance Agreement
Additional information: For example (among other things), fees are paid to the organisation or to a delegated party in exchange for organizational, managing, consulting or similar services.
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): DSI Organisational Agreement: The Trust and Golden agreement hereby consent to this assignment by SAC of its rights under the Organizational Agreement to DSI and the assumption by DSI of SAC's interest in such Agreement and the duties and obligations thereunder, and agree, subject to the terms and conditions of said Agreement, to look to DSI for the performance of the duties and obligations formerly owed by SAC under said Agreement. https://www.sec.gov/Archives/edgar/data/1618181/000119312518153039/d419625dex42.htm
IoP Dimension: Governance IoP, Behavioural IoP
LOST view: Organisational view
Interoperability saliency: The Organisational Agreement ABB is relevant for governance and behavioural interoperability because it sets the foundations and management for (i) controlling the collaborations and data flows established between public digital services, and (ii) specifying the digital business capabilities expected from the public digital services.
Identifier: http://data.europa.eu/dr8/OrganisationalAgreementContract
eira:ID: ABB371
ABB name: eira:OrganisationalAgreementContract
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2022-13-01
Description: A Bearer Token is a type of access token that is used to authenticate a user. It is generated by the server in response to a login request and sent to the client, who then includes it in the header of the HTTP request for accessing protected resources. The server validates the token and, if it's valid, grants access to the requested resource. The term "bearer" implies that whoever presents the token has the right to access the resources, hence it's crucial to protect these tokens from unauthorized access.
Additional information: A Bearer Token is a type of access token that is used in software programming, particularly in web development, for authentication and authorization purposes. It is a cryptic string of characters that is generated by the server in response to a login request. The client must then include this token in their HTTP header to gain access to protected resources from the server.
The term "Bearer" implies that whoever "bears" or possesses the token is considered the authenticated user. This means that the token doesn't inherently contain any information about the identity of the user, it simply authorizes whoever presents it. Therefore, it is crucial to keep these tokens secure to prevent unauthorized access.
Bearer Tokens are most commonly used in OAuth 2.0, a protocol that allows third-party services to access user data without requiring the user's password. Instead, the user authenticates directly with the service, which issues the Bearer Token. The token can then be used by the third-party service to access the user's data hosted by the service, within the scope and duration that was granted by the user.
The Bearer Token is stateless, meaning it does not require the server to remember any information about the user between requests. All the necessary information is contained within the token itself. This makes it very scalable for large applications, as it minimizes the load on the server.
However, because Bearer Tokens can be used by anyone who possesses them, they must be protected to prevent misuse. This is typically done by sending them over HTTPS to encrypt the connection and prevent eavesdropping. Additionally, tokens are often given a limited lifespan before they expire and a new one must be requested.
Example: 1. Web Application Authentication: A common use of bearer tokens is in web application authentication. When a user logs into a web application, the server generates a bearer token that represents the user's authentication. This token is then sent back to the client, which stores it and includes it in every subsequent request to the server. The server checks the token to verify the user's identity and ensure they have permission to access the requested resources.
2. Mobile Application Authentication: Similar to web applications, mobile applications also use bearer tokens for user authentication. After a user logs in, the server generates a token and sends it to the mobile app. The app then includes this token in all future requests to the server.
3. API Authentication: Bearer tokens are often used to authenticate requests to APIs. When a client application wants to access an API, it first requests a token from the server. The server generates the token, and the client includes it in the Authorization header of every API request.
4. OAuth 2.0: In OAuth 2.0, an authorization framework, bearer tokens are used as access tokens. After a client application is granted access by a user, the authorization server issues a bearer token to the client. The client can then use this token to access the user's resources on the resource server.
5. Single Sign-On (SSO): In SSO systems, a user logs in once and gains access to multiple systems without being prompted to log in again. This is often achieved using bearer tokens. After the initial login, the authentication server issues a bearer token which the user's client can then present to other systems to gain access.
6. Microservices Communication: In a microservices architecture, individual services often need to communicate with each other. This communication is often secured using bearer tokens. When one service needs to request data from another, it includes a bearer token in the request to authenticate itself.
Publisher: EIRA team
LOST view: TV-Technical Agreements
Identifier: http://data.europa.eu/dr8/egovera/BearerTokenContract
EIRA traceability: eira:TechnicalInteroperabilityAgreementContract
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-08-03
dct:identifier: http://data.europa.eu/dr8/egovera/BearerTokenContract
dct:title: Bearer Token Contract
Description: The JSON-RPC specification is a remote procedure call (RPC) protocol encoded in JSON. It allows for data to be sent and received between a client and a server, or between peer services, using the JSON (JavaScript Object Notation) format. The protocol supports both positional and named parameters and allows for notifications (data sent to the server that does not require a response). JSON-RPC can be used over any transport layer that allows for the sending and receiving of text data, such as HTTP, WebSocket, or raw sockets.
Additional information: JSON-RPC is a remote procedure call (RPC) protocol encoded in JSON. It is a light-weight, data-interchange format that is easy for humans to read and write, and easy for machines to parse and generate. It is designed to be transport-agnostic, meaning it can be used over different types of transport protocols such as HTTP, WebSockets, or raw sockets.
The JSON-RPC specification defines a few fundamental types of messages: request, response, and notification. A request is a call to a specific method provided by a remote system. It includes parameters needed for the method, and an ID that is used to match the request with the response. A response includes the result of the method call, or an error object if the call failed. A notification is similar to a request, but does not require a response.
In the JSON-RPC protocol, both the client and server can initiate communication. The client can send a request to the server to call a specific method, and the server can respond with the result. Conversely, the server can send a notification to the client to inform it of events or updates.
The JSON-RPC specification also defines a standard error object format. This includes an error code, a short description, and optional additional data. This allows the client to handle errors in a consistent way.
JSON-RPC is stateless, meaning each request from a client to a server must contain all the information needed to understand and process the request. This makes it suitable for stateless or RESTful services, where the server does not need to keep track of client state between requests.
The JSON-RPC specification is simple and flexible, making it easy to implement in many programming languages. It is widely used in web development, mobile app development, and distributed computing. It is also used in some blockchain technologies for communication between nodes.
Example: 1. Cryptocurrency Wallets: JSON-RPC is used in cryptocurrency wallets such as Bitcoin and Ethereum to communicate with the blockchain. The wallet sends a request to the blockchain to get information about a transaction or to send a transaction. The blockchain then responds with the requested information or the result of the transaction.
2. Web Applications: JSON-RPC can be used in web applications to communicate between the client and the server. For example, a web application could use JSON-RPC to request data from a server, such as user information or data to populate a table. The server would then respond with the requested data.
3. Mobile Applications: JSON-RPC can also be used in mobile applications to communicate with a server. For example, a mobile app could use JSON-RPC to request data from a server, such as the latest news articles or weather updates. The server would then respond with the requested data.
4. IoT Devices: JSON-RPC can be used in IoT devices to communicate with a server. For example, a smart thermostat could use JSON-RPC to send temperature data to a server, which could then respond with instructions to adjust the temperature.
5. Game Development: In game development, JSON-RPC can be used to communicate between the game client and the game server. For example, the game client could send a request to the server to get the latest game state, and the server would respond with the requested data.
6. Remote Procedure Calls: JSON-RPC is often used for remote procedure calls (RPCs), where a client can request that a server execute a specific function and return the result. This can be used in a variety of applications, from web services to distributed computing.
Publisher: EIRA team
LOST view: TV-Technical Agreements
Identifier: http://data.europa.eu/dr8/egovera/JSON-RPCContract
EIRA traceability: eira:TechnicalInteroperabilityAgreementContract
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-08-03
dct:identifier: http://data.europa.eu/dr8/egovera/JSON-RPCContract
dct:title: JSON-RPC Contract
Definition: Semantic Agreement ABB is a Contract formalising an agreement from a peer to the common ontology that is the result of a matching or mapping process that is used to resolve their semantic discrepancies. The combination matching process consists of a linguistic base, internal and external structure comparison. The result of the matching combination will be used to develop an agreement unit as a component of the agreement. There are some assumptions for the agreement, such as using the same language to represent the schema/ontology, labels and the meaning of a concept, and there is no individual at the common ontology.
Source: Joinup
Source reference: https://joinup.ec.europa.eu/taxonomy/term/http_e_f_fdata_ceuropa_ceu_fdr8_fSemanticAgreement
Additional information: The combination matching process consists of linguistic base, internal and external structure comparison. Result of matching combination will be used to develop agreement unit as component of agreement. There are some assumptions for the agreement, such as using same language to representation of schema/ontology, labels represent the meaning of concept, and there is no individual at the common ontology.
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): SEMIC - "Supporting alignments and agreements on common definitions and specifications at the semantic layer for the Member States and the EU institutions". https://joinup.ec.europa.eu/collection/semantic-interoperability-community-semic/about
IoP Dimension: Governance IoP
LOST view: Semantic view
Interoperability saliency: The Semantic Agreement ABB is a key interoperability enabler because it supports semantic governance by enabling collaboration between digital public services.
Identifier: http://data.europa.eu/dr8/SemanticAgreementContract
eira:ID: ABB374
ABB name: eira:SemanticAgreementContract
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-16-01
Definition: Interoperability Specification ABB is a Contract with highest possible level of granularity on an EIRA SBB, formulated as an agreed normative statement in design terms on a legal, organisational, semantic, or technical attribute of an European Public Service. It can refer to existing standards or specifications
Source: ISA2
Source reference: https://joinup.ec.europa.eu/taxonomy/term/http_e_f_fdata_ceuropa_ceu_fdr8_fInteroperabilitySpecification#:~:text=DESCRIPTION%3A%20An%20Interoperability%20Specification%20is%20a%20document%20of,It%20can%20refer%20to%20existing%20standards%20or%20specifications
Interoperability saliency: The interoperability specification ABB is salient for legal interoperability because it establishes the normative statements for ensuring interoperability in public services. This ABB is salient for organizational interoperability by establishing the business principles to exchange data between public services. The Interoperability specification ABB is salient for semantic interoperability too in terms of identifying technical standards for the exchange of information between public services. And finally, the ABB is salient for technical interoperability due to it determines the technical requirements to implement the interoperability between public services.
Identifier: http://data.europa.eu/dr8/InteroperabilitySpecificationContract
eira:ID: http://data.europa.eu/dr8/InteroperabilitySpecificationContract
ABB name: eira:InteroperabilitySpecificationContract
Description: OAuth 2.0 is an authorization framework that enables applications to obtain limited access to user accounts on an HTTP service, such as Facebook, GitHub, and DigitalOcean. It works by delegating user authentication to the service that hosts the user account, and authorizing third-party applications to access the user account. OAuth 2.0 focuses on client developer simplicity while providing specific authorization flows for web applications, desktop applications, mobile phones, and living room devices.
Additional information: OAuth 2.0 (Open Authorization 2.0) is an open standard for access delegation, commonly used as a way for Internet users to grant websites or applications access to their information on other websites but without giving them the passwords. It is a protocol that allows a user to grant a third-party website or application access to their personal information, without needing to share their credentials.
OAuth 2.0 is the successor to OAuth 1.0, which was designed to solve the problem of having to share passwords with third-party applications. OAuth 2.0 improves upon the original OAuth protocol by simplifying the client-side development experience, and providing specific authorization flows for web applications, desktop applications, mobile phones, and living room devices.
OAuth 2.0 works by delegating user authentication to the service that hosts the user account, and authorizing third-party applications to access the user account. OAuth 2.0 defines a protocol for this interaction, which involves several steps. First, the user is authenticated by the service hosting the user account, and then authorizes the third-party application to access specific details from their account. The third-party application is then provided with an access token, which it can use to access the user's account.
OAuth 2.0 is used in a wide variety of applications, including providing a "log in with Facebook" or "log in with Google" functionality on websites, or authorizing applications to access services like Google Drive or iCloud on a user's behalf. It is a crucial part of the modern web, and understanding how it works can be very useful for anyone developing web applications.
Example: 1. Google Sign-In: Google uses OAuth 2.0 to allow users to log into third-party websites or applications using their Google account credentials. This saves users from having to remember another username and password, and it also provides the third-party app with a secure way to access the user's Google account data that they have given permission to access.
2. Facebook Login: Similar to Google, Facebook also uses OAuth 2.0 to allow users to log into third-party websites or applications using their Facebook account credentials. The third-party app can also access the user's Facebook data with their permission.
3. GitHub: GitHub uses OAuth 2.0 to allow third-party applications to access a user's GitHub data. For example, a developer might use a third-party app to manage their GitHub repositories, and OAuth 2.0 would be used to authenticate the user and authorize the app to access their data.
4. Dropbox: Dropbox uses OAuth 2.0 to allow third-party apps to access a user's Dropbox account. For example, a photo editing app might use OAuth 2.0 to access a user's photos stored in Dropbox.
5. Slack: Slack uses OAuth 2.0 to allow third-party apps to access a user's Slack workspace. For example, a project management app might use OAuth 2.0 to access a user's Slack messages and channels.
6. Microsoft Azure: Microsoft Azure uses OAuth 2.0 to authenticate users and allow third-party applications to access Azure resources. For example, a monitoring tool might use OAuth 2.0 to access Azure metrics and logs.
7. Spotify: Spotify uses OAuth 2.0 to allow third-party applications to access a user's Spotify data. For example, a music recommendation app might use OAuth 2.0 to access a user's Spotify playlists and listening history.
Publisher: EIRA team
LOST view: TV-Technical Agreements
Identifier: http://data.europa.eu/dr8/egovera/OAuth20Contract
EIRA traceability: eira:TechnicalInteroperabilityAgreementContract
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-08-03
dct:identifier: http://data.europa.eu/dr8/egovera/OAuth20Contract
dct:title: OAuth 2.0 Contract
Description: Basic Auth, short for Basic Authentication, is a simple authentication scheme built into the HTTP protocol. It is a method for a web browser or application to provide a user name and password when making a request. The client sends the user name and password as unencrypted base64 encoded text. Because it is unencrypted, Basic Auth is typically used in conjunction with HTTPS to ensure the credentials cannot be viewed in transit. It is considered less secure than other forms of authentication and is often used as a simple barrier rather than a robust method of user verification.
Additional information: Basic Auth, short for Basic Authentication, is a simple authentication scheme built into the HTTP protocol. It is a method for an HTTP user agent (like a web browser) to provide a user name and password when making a request.
The Basic Auth process works as follows: when a client sends a request to a server, the server sends back a response asking for authentication. The client then sends the username and password, encoded in Base64, in the Authorization header. The server decodes the Base64 string and checks if the credentials are valid. If they are, the server fulfills the request; if they aren't, it returns a 401 Unauthorized response.
The main advantage of Basic Auth is its simplicity. It is easy to implement and use, and it doesn't require cookies, session identifiers, or login pages. However, it also has significant security flaws. The most important one is that the credentials are not encrypted but merely encoded, which means they can be easily decoded by anyone who intercepts the HTTP request. Therefore, Basic Auth should always be used over HTTPS, which provides the necessary encryption to protect the credentials.
Another limitation of Basic Auth is that it doesn't provide features like password resets, account lockouts, or multi-factor authentication. It also doesn't provide any way to log out; the only way to "log out" is to close the browser or to send a request with incorrect credentials.
In summary, Basic Auth is a simple and easy-to-use method for authentication, but it has significant security limitations and should be used with caution. It is best suited for quick-and-dirty implementations or for internal applications where security is not a major concern. For any application exposed to the internet or handling sensitive data, a more secure authentication method should be used.
Example: Basic Auth (Basic Authentication) is a simple authentication scheme built into the HTTP protocol. It is a method for an HTTP user agent (like a web browser) to provide a user name and password when making a request.
1. Accessing a Protected Resource: A common example of using Basic Auth is when you try to access a protected resource on a website. The server will respond with a 401 Unauthorized status and a WWW-Authenticate header. Your browser will then prompt you to enter your username and password. This information is encoded with Base64 and included in the Authorization header in the subsequent request to the server.
2. API Authentication: Basic Auth is often used when interacting with APIs. For example, you might use Basic Auth to authenticate with the Twitter API. You would provide your API key as the username and your API secret key as the password. These would be Base64 encoded and included in the Authorization header in your API requests.
3. FTP Servers: Basic Auth is also commonly used when connecting to FTP servers. When you connect to the server, it will ask for your username and password. This information is sent to the server in plain text (unless you're using a secure connection), and the server uses it to authenticate your session.
4. Proxy Authentication: In some cases, you might need to use Basic Auth to authenticate with a proxy server. This works similarly to the other examples – your username and password are Base64 encoded and included in the Proxy-Authorization header in your HTTP requests.
5. Admin Panels: Basic Auth is often used to protect admin panels or other sensitive areas of a website. When you try to access the admin panel, your browser will prompt you for a username and password. This information is sent to the server, which checks it against its list of authorized users. If you're authorized, the server will let you access the admin panel.
Publisher: EIRA team
LOST view: TV-Technical Agreements
Identifier: http://data.europa.eu/dr8/egovera/BasicAuthContract
EIRA traceability: eira:TechnicalInteroperabilityAgreementContract
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-08-03
dct:identifier: http://data.europa.eu/dr8/egovera/BasicAuthContract
dct:title: Basic Auth Contract
Description: OpenID is an open standard and decentralized authentication protocol that allows users to be authenticated by certain co-operating sites (known as Relying Parties or RP) using a third-party service. This eliminates the need for webmasters to provide their own ad hoc login systems, and allows users to log into multiple unrelated websites without having to have a separate identity and password for each. Users create accounts by selecting an OpenID identity provider, and then use those accounts to sign onto any website which accepts OpenID authentication.
Additional information: OpenID is an open standard and decentralized authentication protocol that allows users to be authenticated by certain co-operating sites (known as Relying Parties or RP) using a third-party service. This eliminates the need for webmasters to provide their own ad hoc login systems, and allows users to log into multiple unrelated websites without having to have a separate identity and password for each.
The protocol was developed by the OpenID Foundation, a non-profit organization that promotes and protects the technology. It was first launched in 2005 and has since been adopted by many large digital companies, including Google, Yahoo, and Microsoft.
OpenID works by using the user's existing account to verify their identity. The user's credentials are not shared with the RP, but instead, the user is authenticated directly with the OpenID Provider (OP). The OP then sends the RP a claim that the user controls a specified Identifier (usually a URL or an XRI). The RP can then use this claim to provide the user with access to its services.
The OpenID protocol supports multiple types of user Identifiers, including XRIs (Extensible Resource Identifiers), URLs, and even email addresses. This flexibility allows users to choose the Identifier that best suits their needs.
OpenID also supports extensions for additional features, such as fetching user details from the OP (via the Simple Registration Extension or the Attribute Exchange Extension), or establishing two-way communications between the RP and the OP (via the OAuth Extension).
One of the main benefits of OpenID is that it allows users to consolidate their digital identities, reducing the number of usernames and passwords they need to remember. It also provides a higher level of security than traditional password-based authentication, as the user's credentials are never shared with the RP.
However, OpenID also has some potential drawbacks. For example, if a user's OpenID account is compromised, all sites that rely on that account for authentication are potentially at risk. Additionally, while OpenID is designed to be decentralized, in practice many users choose to use large, centralized OPs, which can create a single point of failure.
Example: 1. Logging into Google Services: Google uses OpenID to allow users to log into their various services. When you sign up for a Google account, you are essentially creating an OpenID that can be used across Google's services like Gmail, YouTube, Google Drive, etc.
2. Social Media Login: Many websites allow users to log in using their social media accounts, such as Facebook, Twitter, or LinkedIn. This is an application of OpenID, where the website trusts the social media platform to authenticate the user.
3. E-commerce Websites: Many e-commerce websites like Amazon and eBay use OpenID to simplify the login process. Instead of creating a new account, users can log in using an existing account from a trusted provider.
4. Online Forums and Blogs: Websites like WordPress and Blogger use OpenID to allow users to comment on posts. Instead of creating a new account just to leave a comment, users can authenticate themselves using an existing OpenID.
5. Online Gaming: Many online gaming platforms, like Steam, use OpenID to authenticate users. This allows users to have a single identity across multiple games.
6. Corporate Applications: Some companies use OpenID to provide a single sign-on solution for their employees. This allows employees to access multiple applications and services with a single set of credentials.
7. Educational Institutions: Some universities and schools use OpenID to provide students and staff with access to various online resources, like library databases and course management systems.
Publisher: EIRA team
LOST view: TV-Technical Agreements
Identifier: http://data.europa.eu/dr8/egovera/OpenIDContract
EIRA traceability: eira:TechnicalInteroperabilityAgreementContract
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-08-03
dct:identifier: http://data.europa.eu/dr8/egovera/OpenIDContract
dct:title: OpenID Contract
Definition: Legal Agreement ABB is a Contract enabling collaboration between digital public services cross legal jurisdictions.
Source: EIF
Source reference: https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=celex%3A12016E207
Additional information: Generally speaking a Legal Agreement Contract t is of a generic not binding nature like the declarations of Tallinn and Berlin (typically involving many legal jurisdictions). Legal agreements of binding nature typically take the form of binding legal acts like the reference list of offences punishable in the European arrest warrant (2002/584/JHA: Council Framework Decision of 13 June 2002).
Example: An example of a treaty that does have provisions for further binding agreements is the UN Charter. By signing and ratifying the Charter, countries agreed to be legally bound by resolutions passed by UN bodies such as the General Assembly and the Security Council. Thus, UN resolutions are legally binding on UN Member States, and no signature or ratification is necessary. https://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=&cad=rja&uact=8&ved=2ahUKEwiA3djvvbT2AhX1SPEDHdmuCqMQFnoECAYQAQ&url=https%3A%2F%2Fwww.phe.gov%2Fs3%2Flaw%2FPages%2FInternational.aspx&usg=AOvVaw23fJMEr0G7JOPyleNl2lrd
IoP Dimension: Governance IoP
LOST view: Legal view
Interoperability saliency: The Legal Agreement ABB is salient for the governance interoperability because it sets the foundations for the coordination or harmonization between different legislations. Also this ABB is salient for the legal governance in the way of establishing the required business rules facilitate data exchange between public services at lower level.
Identifier: http://data.europa.eu/dr8/LegalAgreementContract
eira:ID: ABB630
ABB name: eira:LegalAgreementContract
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-10-01
Description: Gaia-X establish the principles, rules, and standards for participating in the European data infrastructure initiative. These agreements include a participation agreement, data sovereignty agreement, interoperability agreement, security and privacy agreement, governance agreement, and compliance agreement. They ensure that participants maintain control over their data, promote interoperability, prioritize security and privacy, establish governance structures, and adhere to relevant laws and regulations. Together, these agreements enable secure and sovereign data sharing within the Gaia-X ecosystem while fostering trust and collaboration among participants.
Additional information: Gaia-X is a European initiative aimed at creating a federated data infrastructure to promote secure and sovereign data sharing among businesses, organizations, and individuals. The Agreements on the Use of Common Infrastructure of Gaia-X outline the principles, rules, and standards that govern the participation and utilization of the Gaia-X infrastructure. While I don't have access to the specific details beyond my knowledge cutoff in September 2021, I can provide you with a general overview of the expected agreements:
Example: Gaia-X is an ambitious project initiated by European countries to create a secure and transparent data infrastructure for fostering data sovereignty and promoting the development of European digital ecosystems. Here are a few examples of how Gaia-X could be applied:
Publisher: Gaia-X
Source: https://www.data-infrastructure.eu/GAIAX/Navigation/EN/Home/home.html
LOST view: OV-Data Spaces
Identifier: http://data.europa.eu/dr8/egovera/Gaia-XContract
EIRA traceability: eira:AgreementOfTheUseOnCommonInfrastructureContract
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-07-07
dct:identifier: http://data.europa.eu/dr8/egovera/Gaia-XContract
Definition: A National Governance Model refers to the framework and processes established by a country to ensure effective IT interoperability within the European Union. It involves the coordination and collaboration between various government agencies, departments, and stakeholders to develop and implement common standards, policies, and guidelines for the exchange and sharing of information and services across different IT systems. The National Governance Model aims to promote seamless interoperability, data security, and efficient digital services within the country, while also aligning with the broader European IT interoperability framework to enable cross-border data exchange and cooperation.
Source: European Commission
Additional information: A National Governance Model regarding European IT interoperability refers to the framework and mechanisms established by a country to ensure effective coordination, collaboration, and standardization of IT systems and services within its national context, while aligning with the European Union's interoperability objectives.
The European Union (EU) promotes interoperability as a key principle to enhance the efficiency, effectiveness, and transparency of public administrations across member states. It aims to facilitate seamless information exchange and service delivery between different government entities, enabling citizens, businesses, and public administrations to interact and share data effortlessly.
A National Governance Model typically encompasses several components and processes to achieve interoperability. These may include:
1. Policy Framework: The model begins with the development of policies, strategies, and guidelines that outline the vision, objectives, and principles for interoperability. These policies are aligned with the EU's interoperability framework, such as the European Interoperability Framework (EIF), which provides guidance on technical, semantic, and organizational interoperability.
2. National Interoperability Framework (NIF): The NIF serves as a comprehensive reference document that defines the technical standards, specifications, and guidelines to be followed by public administrations within the country. It ensures consistency and compatibility of IT systems and services across different government entities, enabling seamless data exchange.
3. Interoperability Governance Body: A dedicated governance body is established to oversee the implementation and enforcement of interoperability standards and guidelines. This body may consist of representatives from various government departments, agencies, and stakeholders. It is responsible for coordinating interoperability initiatives, resolving conflicts, and monitoring compliance.
4. Interoperability Framework Agreements: The governance model facilitates the establishment of agreements between different government entities to ensure interoperability. These agreements define the technical, semantic, and organizational aspects of data exchange, including data formats, protocols, security measures, and data protection requirements.
5. Interoperability Maturity Assessment: Regular assessments are conducted to evaluate the maturity level of interoperability within the country. These assessments help identify gaps, challenges, and areas for improvement. They also provide a basis for benchmarking against other EU member states and aligning with EU-wide interoperability initiatives.
6. Interoperability Training and Support: The governance model includes provisions for training programs and support mechanisms to enhance the capacity of public administration staff in implementing interoperability standards and best practices. This ensures that government employees have the necessary skills and knowledge to effectively utilize interoperable IT systems and services.
7. Stakeholder Engagement: The governance model emphasizes the involvement of relevant stakeholders, including public administrations, industry representatives, academia, and citizens. Regular consultations, workshops, and forums are conducted to gather feedback, address concerns, and foster collaboration in achieving interoperability goals.
8. Compliance and Enforcement: The governance model establishes mechanisms to ensure compliance with interoperability standards and guidelines. This may involve periodic audits, certifications, and penalties for non-compliance. It also encourages the use of open standards and open-source solutions to promote transparency, vendor neutrality, and reusability of IT assets.
Overall, a National Governance Model regarding European IT interoperability aims to create a harmonized and efficient digital ecosystem within a country, aligning with the EU's interoperability objectives. It facilitates seamless data exchange, enhances service delivery, and promotes collaboration among public administrations, ultimately benefiting citizens, businesses, and the overall European digital single market.
Example: One example of the application of national governance models regarding European IT interoperability is the use of national frameworks and standards. Each country within the European Union may have its own governance model for IT interoperability, which includes the development and implementation of national frameworks and standards.
For instance, in Germany, the Federal IT Planning Council (IT-Planungsrat) is responsible for coordinating IT governance across federal, state, and local levels. They have developed the German Interoperability Framework (GIF), which provides guidelines and standards for IT interoperability in the country. This framework ensures that IT systems and services across different government entities can communicate and exchange data effectively.
Similarly, in France, the Agency for Digital Services (Agence du Numérique) is responsible for defining and implementing the national interoperability framework. They have developed the Référentiel Général d'Interopérabilité (RGI), which provides guidelines and standards for IT interoperability in the French public sector. This framework ensures that public administrations can exchange data and services seamlessly, promoting efficiency and collaboration.
These national governance models and frameworks are aligned with the European Interoperability Framework (EIF), which provides a common set of principles, guidelines, and standards for IT interoperability across the European Union. The national governance models ensure that the EIF is implemented effectively at the national level, taking into account specific national requirements and contexts.
Overall, the application of national governance models regarding European IT interoperability ensures that countries within the European Union can effectively exchange data and services, promoting seamless collaboration and efficiency in the digital era.
LOST view: OV-Governance Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/NationalGovernanceModelsContract
ABB name: egovera:NationalGovernanceModelsContract
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/egovera/NationalGovernanceModelsContract
Name: National Governance Models
Interoperability Layer: Organisational
Specialises: http://data.europa.eu/dr8/OrganisationalAgreementContract
Description: OAuth 1.0 is an open standard for authorization that allows users to share their private resources (like photos and videos) stored on one site with another site without having to hand out their credentials, typically username and password. It provides a process for end-users to authorize third-party access to their server resources without sharing their credentials. It uses various signatures to verify the authenticity of the data being transferred, providing a secure method for ensuring that the data is coming from a trusted source.
Additional information: OAuth 1.0 is an open standard for authorization that provides applications the ability for secure designated access. It is used over HTTP and allows applications to access user data from other applications without requiring users to reveal their passwords. OAuth 1.0 was developed in 2007 to provide a standard way for developers to offer their services via an API without forcing their users to expose their passwords (and other credentials).
OAuth 1.0 works by providing the client with a 'token' that can be used to access the specific resources on the server. This token is issued by the server at the request of the client, after successful authentication of the client's identity. The client can then use this token to make requests on behalf of the user, without the need for the user's password.
OAuth 1.0 uses a three-legged model for this process. The three legs are the client, the server, and the user. The client is the application that wants to access the user's account. The server is the application that holds the user's account, and the user is the person who owns the account.
The process starts when the client asks the user for permission to access their account. If the user agrees, the client sends a request to the server, asking for a token. The server then authenticates the client and issues a token. The client can then use this token to make requests on behalf of the user.
OAuth 1.0 provides a method for clients to access server resources on behalf of a resource owner (such as a different client or an end-user). It also provides a process for end-users to authorize third-party access to their server resources without sharing their credentials (typically, a username and password pair), using user-agent redirections.
OAuth 1.0 was later superseded by OAuth 2.0, which offers improved security and a more streamlined workflow. However, some applications still use OAuth 1.0 due to its simplicity and wide adoption at the time of its release.
Example: OAuth 1.0 is an open standard for access delegation, commonly used as a way for Internet users to grant websites or applications access to their information on other websites but without giving them the passwords. Here are some examples of how OAuth 1.0 can be applied:
1. Social Media Integration: OAuth 1.0 is used by social media platforms like Twitter and Facebook to allow third-party apps to access user data without needing the user's password. For example, a user can use a third-party app to post tweets on their Twitter account using OAuth 1.0.
2. Email Clients: OAuth 1.0 can be used by email clients like Outlook or Thunderbird to access a user's email account on a service like Gmail or Yahoo. The user grants the email client permission to access their email account, and the client uses OAuth 1.0 to authenticate with the email service.
3. Mobile Apps: Many mobile apps use OAuth 1.0 to authenticate with web services. For example, a user might use a mobile app to access their Dropbox account. The app uses OAuth 1.0 to authenticate with Dropbox and access the user's files.
4. E-Commerce Websites: OAuth 1.0 can be used by e-commerce websites to allow users to make purchases using their PayPal or Amazon accounts. The website uses OAuth 1.0 to authenticate with PayPal or Amazon and make the purchase on behalf of the user.
5. Cloud Services: Cloud services like Google Cloud or Microsoft Azure use OAuth 1.0 to allow users to authenticate with their services. This allows users to access their cloud resources without having to provide their password each time.
6. API Access: Developers can use OAuth 1.0 to authenticate with APIs and access their resources. For example, a developer might use OAuth 1.0 to authenticate with the Twitter API and access its resources to create a new Twitter client.
Publisher: EIRA team
LOST view: TV-Technical Agreements
Identifier: http://data.europa.eu/dr8/egovera/OAuth10Contract
EIRA traceability: eira:TechnicalInteroperabilityAgreementContract
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-08-03
dct:identifier: http://data.europa.eu/dr8/egovera/OAuth10Contract
dct:title: OAuth 1.0 Contract
Description: The RESTful API specification, also known as Representational State Transfer, is a set of constraints or rules used to build web services. It is a software architectural style that defines a set of constraints to be used for creating web services. These web services, or APIs, allow different software applications to communicate with each other, typically over HTTP. RESTful APIs are stateless, meaning they don't store any information about the client between requests, and they use standard HTTP methods like GET, POST, PUT, DELETE to perform operations. They are designed to take advantage of existing web protocols, are highly scalable, and can return data in different formats like JSON or XML.
Additional information: Representational State Transfer (REST) is an architectural style that defines a set of constraints to be used for creating web services. When a web service adheres to these constraints, it is known as a RESTful API (Application Programming Interface). RESTful APIs are designed to take advantage of existing protocols, and often HTTP specifically.
RESTful APIs are stateless, meaning that each request from a client to a server must contain all the information needed to understand and process the request. The server should not store anything about the latest HTTP request the client made. It should treat each request as if it was brand new. This constraint increases reliability and scalability.
The RESTful API specification is based on the following principles:
1. Client-Server Architecture: The client is responsible for the user interface and user experience, and the server is responsible for processing requests and managing resources. This separation allows both to evolve independently.
2. Stateless Interactions: As mentioned above, each request from a client to a server must contain all the information needed to process the request. The server should not store any session information.
3. Cacheable Data: Clients can cache responses to improve performance. Responses must define themselves as cacheable or non-cacheable to prevent clients from reusing stale or inappropriate data.
4. Uniform Interface: The method of communication between the client and the server should be uniform, simplifying the architecture and improving visibility of interactions. This is typically achieved through the use of resources (URIs), methods (GET, POST, PUT, DELETE), and representations (usually HTML, XML, or JSON).
5. Layered System: The architecture can be composed of multiple layers, each with specific functionality. This allows for flexibility and scalability, as layers can be added, removed, or modified without affecting the system as a whole.
6. Code on Demand (optional): Servers can provide executable code or scripts for clients to run in their context. This is the only optional constraint.
RESTful APIs are commonly used in web applications due to their simplicity, scalability, and performance. They allow different software systems to communicate with each other, even if they use different languages or technologies.
Example: 1. Social Media Applications: RESTful APIs are used extensively in social media platforms like Facebook, Twitter, and Instagram. They use APIs to allow third-party applications to integrate with them, enabling functionalities like login with Facebook, tweet or share something on the user's behalf, fetch user details, etc.
2. E-commerce Websites: Online shopping websites like Amazon, eBay, and Alibaba use RESTful APIs to handle requests from users. These requests can include adding items to a shopping cart, making a payment, checking the status of an order, etc.
3. Weather Forecasting Applications: Apps like Weather.com and AccuWeather use RESTful APIs to fetch real-time weather data from servers. The data is then displayed to the user in a readable format.
4. Google Maps: Google Maps uses RESTful APIs to provide various services like displaying maps, providing directions, showing traffic conditions, etc. Developers can integrate these services into their own applications using the Google Maps API.
5. Mobile Applications: Many mobile apps use RESTful APIs to communicate with a server. For example, a news app might use an API to fetch the latest news articles from the server, or a food delivery app might use an API to send a user's order to the restaurant.
6. Banking Applications: Banks use RESTful APIs to provide services like balance checks, fund transfers, bill payments, etc. These APIs are typically secured using various authentication and authorization mechanisms to ensure the safety of the user's data.
7. Content Management Systems: CMSs like WordPress and Drupal use RESTful APIs to manage the content on the website. This includes creating, reading, updating, and deleting posts, pages, and other types of content.
8. IoT Devices: Internet of Things devices like smart home devices, wearables, etc., use RESTful APIs to communicate with each other and with servers. This allows them to provide various services like home automation, health tracking, etc.
Publisher: EIRA team
LOST view: TV-Technical Agreements
Identifier: http://data.europa.eu/dr8/egovera/RESTfulAPIContract
EIRA traceability: eira:TechnicalInteroperabilityAgreementContract
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-08-03
dct:identifier: http://data.europa.eu/dr8/egovera/RESTfulAPIContract
dct:title: RESTful API Contract
Description: The GraphQL specification is a detailed technical document that defines the rules, syntax, and semantics of GraphQL, an open-source data query and manipulation language for APIs. It outlines how a GraphQL service should expose, validate, and execute a GraphQL request, including the structure of queries, mutations, and subscriptions, as well as the types of data that can be returned. The specification is designed to be platform and language agnostic, meaning it can be implemented in any programming language and run on any platform.
Additional information: The GraphQL specification is a detailed technical document that defines the GraphQL language and its behavior in a precise and implementation-agnostic manner. It serves as the authoritative reference for anyone implementing or using GraphQL. The specification is maintained by the GraphQL Foundation, a project of the Linux Foundation, and is open source, meaning that it is freely available for anyone to use or contribute to.
The specification covers all aspects of GraphQL, including its syntax, type system, query execution, error handling, and more. It describes how a GraphQL service should parse and validate queries, how it should execute them against a data source, and how it should format the results. It also defines a set of rules for how clients and servers should communicate, ensuring interoperability between different implementations.
The GraphQL specification is not a tutorial or a guide to using GraphQL, but rather a formal definition of the language itself. It is intended to be precise and comprehensive, providing a definitive answer to any question about how GraphQL should behave. However, it is also written in a way that is intended to be understandable and useful to developers, not just to computer scientists or language theorists.
The specification is divided into several sections, each covering a different aspect of the language. These include:
1. Language: This section defines the syntax of GraphQL, including its types, fields, arguments, directives, and other constructs. It also describes how queries are parsed and validated.
2. Execution: This section describes how a GraphQL query is executed against a data source. It covers topics like how to resolve fields, how to handle errors, and how to deal with asynchronous operations.
3. Type System: This section defines the GraphQL type system, which is used to describe the shape of the data that a GraphQL service can return. It includes definitions of scalar types, object types, interface types, union types, and more.
4. Introspection: This section describes how clients can query a GraphQL service to learn about its schema, which is the set of types and fields that it supports.
5. Validation: This section describes how a GraphQL query is validated against a schema before it is executed. This includes checks for things like type compatibility, correct use of directives, and more.
6. Response: This section describes the format of a GraphQL response, including how data is serialized and how errors are reported.
The GraphQL specification is continually evolving, with new versions released periodically to incorporate improvements, clarify ambiguities, and add new features. Each version of the specification is fully backwards-compatible with previous versions, ensuring that existing GraphQL services and clients continue to work as expected.
Example: 1. Social Media Applications: GraphQL is used in social media applications like Facebook, Instagram, and Twitter to fetch and update user data, posts, comments, likes, etc. It allows these applications to request specific data and aggregate responses from multiple sources.
2. E-commerce Platforms: E-commerce platforms like Shopify use GraphQL to manage their product catalog, customer data, and shopping cart operations. It allows them to fetch specific product details, update inventory, and manage orders efficiently.
3. Content Management Systems: Content management systems like WordPress use GraphQL to manage their content, user data, and other resources. It allows them to fetch specific content, update content, and manage user roles and permissions.
4. News and Media Websites: News and media websites like The New York Times use GraphQL to manage their news articles, user comments, and other resources. It allows them to fetch specific news articles, update news content, and manage user comments.
5. Travel and Booking Platforms: Travel and booking platforms like Airbnb use GraphQL to manage their property listings, user data, and booking operations. It allows them to fetch specific property details, update property listings, and manage bookings efficiently.
6. Music Streaming Applications: Music streaming applications like Spotify use GraphQL to manage their music catalog, user data, and playlist operations. It allows them to fetch specific song details, update song metadata, and manage playlists.
7. GitHub: GitHub uses GraphQL to power its API v4. This allows developers to selectively request the data they need, making it more efficient than traditional REST APIs.
8. Yelp: Yelp uses GraphQL to power its public API. This allows developers to selectively request data about businesses, reviews, and photos.
Publisher: EIRA team
LOST view: TV-Technical Agreements
Identifier: http://data.europa.eu/dr8/egovera/GraphQLContract
EIRA traceability: eira:TechnicalInteroperabilityAgreementContract
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-08-03
dct:identifier: http://data.europa.eu/dr8/egovera/GraphQLContract
dct:title: GraphQL Contract
Definition: Agreement of the Use on Common Infrastructure ABB is a Contract between multiple parties that outlines the terms and conditions for sharing and utilizing a specific infrastructure or facility. The agreement on the use of common infrastructure typically outlines the rights and responsibilities of each party, the terms and conditions for access and usage, the payment or cost-sharing arrangements, and the procedures for resolving any disputes or issues that may arise. The goal of such agreements is to promote efficient and effective utilization of shared resources and to ensure that all parties are able to benefit from the use of the infrastructure in a fair and equitable manner.
Source: Inspired in the UNECE definition
Source reference: https://unece.org/trade/unece-work-transport/infrastructure/agreements-use-common-infrastructure
Example: The following implementation is an example of how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): With Gaia-X, representatives from business, science and politics on an international level create a proposal for the next generation of data infrastructure: an open, transparent and secure digital ecosystem, where data and services can be made available, collated and shared in an environment of trust. https://www.data-infrastructure.eu/GAIAX/Navigation/EN/Home/home.html
Interoperability Dimension: Governance IoP
LOST view: Organisational view
Interoperability Saliency: Agreement on the use of common infrastructure ABB is salient for governance, organizational and legal interoperability because it comprises the agreements, procedures and rules to elaborate the principles of reference architectures for the public sector.
Identifier: http://data.europa.eu/dr8/AgreementOfTheUseOnCommonInfrastructureContract
ABB name: eira:AgreementOfTheUseOnCommonInfrastructureContract
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/AgreementOfTheUseOnCommonInfrastructureContract
Interoperability Layer: Organisational
Description: JWT Bearer is a method for authentication and authorization where a JSON Web Token (JWT) is used as a bearer token. This means that the client presents the token to the server or resource, and the server uses the information contained in the token to authenticate the client and authorize access. The server does not need to maintain a record or session state for the client, making this method suitable for scalable applications and microservices. The JWT Bearer is often used in OAuth 2.0 and OpenID Connect protocols.
Additional information: JWT Bearer is a method of authentication that involves the use of JSON Web Tokens (JWTs) as bearer tokens. A bearer token is a type of access token that is given to the user after they have authenticated themselves, and it allows the user to access specific resources on a server. The term "bearer" implies that the person or application holding the token is the one that is authenticated.
JWTs are a compact, URL-safe means of representing claims to be transferred between two parties. The claims in a JWT are encoded as a JSON object that is digitally signed using JSON Web Signature (JWS). They can also be encrypted using JSON Web Encryption (JWE) for additional security.
In the context of JWT Bearer, the JWTs are used as the bearer tokens. When a user or application wants to access certain resources, they must include the JWT in the authorization header of the HTTP request. The server will then validate the JWT, and if it's valid, the server will process the request.
The JWT Bearer is often used in the context of OAuth 2.0, an authorization framework that enables a third-party application to obtain limited access to an HTTP service. In OAuth 2.0, the JWT Bearer can be used as a method for client authentication to the token endpoint or as a means of application-level authorization.
One of the main advantages of using JWT Bearer is that the tokens are self-contained. This means they contain all the necessary information about the user or application, so the server doesn't need to query a database to validate the token. This can lead to more efficient and scalable systems. However, it also means that the tokens can be quite large, especially if they contain a lot of claims.
Example: 1. User Authentication: JWT Bearer is commonly used in user authentication. When a user logs in with their credentials, the server generates a JWT that is signed with a secret key and sends it back to the client. The client then includes this JWT in the header of each subsequent request to the server. The server verifies the JWT and if it's valid, allows access to the protected resources.
2. API Authentication: JWT Bearer can be used to authenticate API requests. For example, a mobile app might use a JWT to authenticate requests to a backend API. The app requests a JWT from the server, includes it in the header of each API request, and the server verifies the JWT before processing the request.
3. Single Sign-On (SSO): JWT Bearer can be used to implement SSO across multiple domains or services. When a user logs into one service, a JWT is generated and can be used to authenticate the user on other services without requiring them to log in again.
4. Microservices: In a microservices architecture, JWT Bearer can be used to authenticate requests between services. Each service can generate and verify JWTs, allowing them to securely authenticate requests from other services.
5. IoT Devices: JWT Bearer can be used to authenticate requests from IoT devices. For example, a smart home device might use a JWT to authenticate requests to a cloud-based service. The device requests a JWT from the server, includes it in the header of each request, and the server verifies the JWT before processing the request.
Publisher: EIRA team
LOST view: TV-Technical Agreements
Identifier: http://data.europa.eu/dr8/egovera/JWTBearerContract
EIRA traceability: eira:TechnicalInteroperabilityAgreementContract
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-08-03
dct:identifier: http://data.europa.eu/dr8/egovera/JWTBearerContract
dct:title: JWT Bearer Contract
Definition: National Legal Interoperability Agreement ABB is a Contract formalizing governance rules enabling collaboration amongst different levels of administrations in a State.
Source: Based on the definition in the EIF about Legal Interoperability Agreement, the National Interoperability Framework Observatory (see Joinup NIFO) and existing national legal interoperability agreements.
Source reference: https://ec.europa.eu/isa2/sites/isa/files/eif_brochure_final.pdf#page=27
Additional information: The National Legal Interoperability Agreement ABB is a specialisation of the Legal Interoperability Agreement. It is considered a Shared Legal Content because it enables interoperability between different digital public services of one or multiple Public Administrations within a State.
Example: The following implementation is an example of how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): Agreement to pass the policy of e-Signture and Certificates for the interoperability between the digital public services of the Spanish Central Administration (https://www.boe.es/diario_boe/txt.php?id=BOE-A-2012-15066)
Interoperability Dimension: Governance IoP
LOST view: Legal view
Interoperability Saliency: The European Legal Interoperability Agreement ABB is salient for the governance of interoperability because it lays the European framework between public administration to enable the interoperability between public services. The European Legal Interoperability Agreement ABB is also salient for the legal interoperability due to the legal foundations and requirements that enable the seamless exchange of data, information, and knowledge between European and EEA Member State digital public services. The European Legal Interoperability Agreement ABB is also salient for the organizational interoperability since, as a consequence of the agreement, digital business capabilities can be mapped and subsequently, the process can be aligned between the Member State and EEA Public Administrations and digital public services.
Identifier: http://data.europa.eu/dr8/NationalLegalInteroperabilityAgreementContract
ABB name: eira:NationalLegalInteroperabilityAgreementContract
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/NationalLegalInteroperabilityAgreementContract
Interoperability Layer: Legal
Definition: Technical Interoperability Agreement ABB is a Contract formalizing the technical specifications to ensure organisations operate under different technical frameworks.
Source: EIF
Source reference: https://ec.europa.eu/isa2/sites/isa/files/eif_brochure_final.pdf#page=27
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): ETA - The European Technical Assessment (ETA) is an alternative for construction products not covered by a harmonised standard. It is a document providing information on their performance assessment. The procedure is established in the Construction Products Regulation and offers a way for manufacturers to draw up the Declaration of Performance and affix the CE marking. It contributes to the free movement of construction products and the creation of a strong Single Market. https://ec.europa.eu/growth/sectors/construction/product-regulation/european-assessment_en
IoP Dimension: Governance IoP
LOST view: Technical view - application
Interoperability saliency: The Technical Interoperability Agreement ABB is a key enabler (*) for governance and organizational interoperability by enabling components to ensure data sharing, access and discovery between public services.
Identifier: http://data.europa.eu/dr8/TechnicalInteroperabilityAgreementContract
eira:ID: ABB234
ABB name: eira:TechnicalInteroperabilityAgreementContract
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2022-17-01
Description: Security Assertion Markup Language (SAML) is an open standard for exchanging authentication and authorization data between parties, specifically between an identity provider and a service provider. It is an XML-based markup language for security assertions (statements that service providers use to make access-control decisions). SAML is widely used in enterprise-level applications to allow single sign-on, which means users can log in once and gain access to a wide range of systems.
Additional information: SAML, which stands for Security Assertion Markup Language, is an open standard for exchanging authentication and authorization data between parties. This XML-based framework is used primarily between an identity provider and a service provider. It allows for the secure transmission of authentication credentials from one party, the identity provider, to another party, the service provider.
SAML was developed by the Security Services Technical Committee of the Organization for the Advancement of Structured Information Standards (OASIS). The standard has been around since 2002, but it has become increasingly popular in recent years due to the rise of cloud computing and the need for single sign-on (SSO) solutions.
In a typical SAML use case, a user requests access to a resource or service from the service provider. The service provider requests and obtains an identity assertion from the identity provider and then, on the basis of this assertion, decides whether to grant or deny access to the resource or service.
The identity assertion provided by the identity provider specifies who the user is. It may also include additional information, such as how, when, and where the user was authenticated and any specific attributes related to the user or his/her role.
SAML is a crucial part of many SSO systems that allow users to access multiple services with a single login. It helps to eliminate the need for multiple passwords and enables seamless secure access across numerous applications and platforms.
SAML provides numerous benefits, including improved user productivity and experience, reduced administrative costs, and enhanced security. It is widely used in enterprise settings for web browser single sign-on, cloud identity verification, and various cross-domain web services and applications.
Example: SAML (Security Assertion Markup Language) is an open standard for exchanging authentication and authorization data between parties, in particular, between an identity provider and a service provider. Here are some examples of its application:
1. Single Sign-On (SSO): SAML is often used to implement SSO solutions. For example, a user logs into their company's network and then can access a third-party application (like a cloud-based project management tool) without having to log in again. The company's identity provider sends a SAML assertion to the third-party application, which uses it to authenticate the user.
2. Federated Identity: SAML can be used to establish a federated identity system, where multiple enterprises can share the same identity for a user. For example, a user could have a single identity that is valid across all the different services provided by a group of collaborating libraries.
3. Cloud Security: SAML is used in cloud security to allow users to log in to multiple cloud services using the same credentials. For example, a user could log in to their Google account and then access their Salesforce account without having to log in again.
4. E-commerce: In an e-commerce context, a user could log in to a shopping site, and then be able to access related services such as payment gateways or shipping calculators without having to log in to each one separately.
5. Education: In the education sector, SAML is used to provide students and staff with access to a variety of online resources. For example, a student could log in to their university's system and then access library resources, online journals, and learning management systems without having to log in to each one separately.
6. Government Services: Many government services use SAML to provide citizens with secure access to online services. For example, a citizen could log in to a government portal and then access various services such as tax filing, benefits applications, and license renewals without having to log in to each one separately.
Publisher: EIRA team
LOST view: TV-Technical Agreements
Identifier: http://data.europa.eu/dr8/egovera/SAMLContract
EIRA traceability: eira:TechnicalInteroperabilityAgreementContract
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-08-03
dct:identifier: http://data.europa.eu/dr8/egovera/SAMLContract
dct:title: SAML Contract
Definition: Linked Open Data ABB is a Representation that enables the procedures of publishing structured data enriched with metadata to ensure data understanding, connection, findability and link with informational resources.
Source: EUROPEANA PRO
Source reference: https://pro.europeana.eu/page/linked-open-data
Example: The following implementation is an example of how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): EuropeanaPro https://pro.europeana.eu/page/linked-open-data
Interoperability Dimension: Structural IoP
LOST view: Semantic view
Interoperability Saliency: The Linked Open Data Representation ABB is salient for semantic interoperability because it provides a set of publishing, sharing, and connection methods that allow linking and publishing the data from digital public services, making it more meaningful and increasing the quality and scope of data and services. Moreover, it increases data discoverability and maximises the reuse and exchange of data.
Identifier: http://data.europa.eu/dr8/LinkedOpenDataRepresentation
ABB name: eira:LinkedOpenDataRepresentation
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/LinkedOpenDataRepresentation
Interoperability Layer: Semantic
Definition: Data Representation ABB is a Representation refers to the method or mechanism in which data is encoded and stored in a computer system. It involves transforming data from its original form into a format that can be processed and manipulated by a computer
Source: Inspired in ArchiMate® definition
Source reference: https://pubs.opengroup.org/architecture/archimate3-doc/chap08.html#_Toc10045383
Additional information: (*)DECISION (EU) 2015/2240 OF THE EUROPEAN PARLIAMENT AND OF THE COUNCIL of 25 November 2015 establishing a programme on interoperability solutions and common frameworks for European public administrations, businesses and citizens (ISA2 programme) as a means for modernising the public sector.
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): ESPD data - XML representation: European Single Procurement Document (ESPD) is a self-declaration of the businesses' financial status, abilities and suitability for a public procurement procedure. It is available in all EU languages and used as a preliminary evidence of fulfilment of the conditions required in public procurement procedures across the EU. Thanks to the ESPD, the tenderers no longer have to provide full documentary evidence and different forms previously used in the EU procurement, which means a significant simplification of access to cross-border tendering opportunities. [...] The online form can be filled in, printed and then sent to the buyer together with the rest of the bid. (https://ec.europa.eu/tools/espd/filter?lang=en)
Interoperability Dimension: Structural IoP
LOST view: Semantic view
Viewpoint: Highlevel viewpoint
Interoperability Saliency: The Data Representation ABB is a key interoperability enabler because it ensures a common and unambiguous interpretation of Data (*).
Identifier: http://data.europa.eu/dr8/DataRepresentationRepresentation
ABB name: eira:DataRepresentationRepresentation
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/DataRepresentationRepresentation
Interoperability Layer: Semantic
Description: The Simple Knowledge Organization System (SKOS) is a common data model for sharing and linking knowledge organization systems via the Semantic Web. SKOS-XL defines an extension for the Simple Knowledge Organization System, providing additional support for describing and linking lexical entities.This document provides a brief description of the SKOS-XL vocabulary.
Publisher: W3C
Source: https://www.w3.org/TR/skos-reference/skos-xl.html
LOST view: SV-Functional Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/SKOS-XLRepresentation
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/egovera/SKOS-XLRepresentation
Interoperability Layer: Semantic
Realises: http://data.europa.eu/dr8/DataRepresentation
Description: Genericode is a standardized format for defining and exchanging code lists and reference data. It provides a structured and machine-readable representation of code lists, which are collections of codes and their corresponding meanings or descriptions. Genericode is designed to facilitate interoperability and data exchange between different information systems.
Publisher: Advancement of Structured Information Standards (OASIS)
Source: https://docs.oasis-open.org/codelist/genericode/v1.0/cs02/genericode-v1.0-cs02.html
LOST view: SV-Functional Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/GenericodeRepresentation
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/egovera/GenericodeRepresentation
Interoperability Layer: Semantic
Realises: http://data.europa.eu/dr8/DataRepresentation
Description: CUSDEC is a specific format used for customs declarations. It includes fields and structures for capturing information about import or export shipments, including details about goods, their classification, valuation, origin, and other customs-related information.
Publisher: Progress Software Corporation
Source: https://www.stylusstudio.com/edifact/D96A/CUSDEC.htm#:~:text=This%20Customs%20Declaration%20Message%20%28CUSDEC%29%20permits%20the%20transfer,declaration%20of%20goods%20for%20import%2C%20export%20or%20transit.
LOST view: SV-Customs Data Representation [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/EDIFACTRepresentation
EIRA traceability: eira:DataRepresentation
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-08-21
dct:identifier: http://data.europa.eu/dr8/egovera/EDIFACTRepresentation
Description: The OWL2 (Web Ontology Language) specification is a technical framework that enables computers to understand and reason about structured knowledge. It provides tools for creating ontologies, which define concepts, properties, and relationships in a domain. By using OWL2, computers can accurately interpret data, make logical deductions, and draw new conclusions. This facilitates tasks like information retrieval, data integration, and intelligent data processing. OWL2's standardized approach enhances communication and interoperability between systems, making it easier to share and leverage knowledge effectively.
Publisher: W3C
Source: https://www.w3.org/TR/owl2-syntax/
LOST view: SV-Functional Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/OWL2Representation
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/egovera/OWL2Representation
Interoperability Layer: Semantic
Realises: http://data.europa.eu/dr8/DataRepresentation
Definition: Knowledge ABB is a Representation that refers to a perceptible form of stored information in a human/artificial memory representing the understanding and awareness that a person has about a particular subject, topic, or area of study. Knowledge is generally context related.
Source: FREE DICTIONARY
Source reference: https://encyclopedia2.thefreedictionary.com/knowledge
Example: The following implementation is an example of how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): Core Vocabularies for public administration. https://joinup.ec.europa.eu/collection/semic-support-centre/core-vocabularies
Interoperability Dimension: Structural IoP
LOST view: Semantic view
Viewpoint: Highlevel viewpoint
Identifier: http://data.europa.eu/dr8/KnowledgeRepresentation
ABB name: eira:KnowledgeRepresentation
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/KnowledgeRepresentation
Interoperability Layer: Semantic
Description: GeoJSON is a format for encoding geospatial data in JSON (JavaScript Object Notation). It provides a standard and flexible way to represent geographic features, such as points, lines, and polygons, along with their associated attributes.
Publisher: Internet Engineering Task Force (IETF)
Source: https://tools.ietf.org/html/rfc7946
LOST view: SV-Functional Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/GeoJSONRepresentation
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/egovera/GeoJSONRepresentation
Interoperability Layer: Semantic
Realises: http://data.europa.eu/dr8/DataRepresentation
Description: The Extensible Markup Language (XML) is a subset of SGML that is completely described in this document. Its goal is to enable generic SGML to be served, received, and processed on the Web in the way that is now possible with HTML. XML has been designed for ease of implementation and for interoperability with both SGML and HTML.
Publisher: W3C
Source: https://www.w3.org/TR/2008/REC-xml-20081126/
LOST view: SV-Functional Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/XMLRepresentation
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/egovera/XMLRepresentation
Interoperability Layer: Semantic
Realises: http://data.europa.eu/dr8/DataRepresentation
Description: ISO 8601 is an international standard that specifies the representation of dates, times, and durations. It provides a standardized format for expressing and exchanging date and time-related information in a universally accepted way. The ISO 8601 format follows the YYYY-MM-DD (year-month-day) pattern for dates and the HH:MM:SS (hour-minute-second) pattern for times. It also allows for additional elements such as time zone offsets and durations. ISO 8601 ensures consistency and interoperability in date and time representations, facilitating accurate data exchange, international communication, and proper handling of date and time-related operations across different systems and applications.
Publisher: ISO
LOST view: SV-Functional Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/ISO8601Representation
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/egovera/ISO8601Representation
Interoperability Layer: Semantic
Realises: http://data.europa.eu/dr8/DataRepresentation
Definition: Open Data ABB is a Representation of the information collected, produced or paid for by the public bodies and made freely available for re-use for any purpose
Source: European Comission
Source reference: https://data.europa.eu/en/trening/what-open-data
Example: The following implementation is an example of how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): datos.gob.es https://datos.gob.es/en
Interoperability Dimension: Structural IoP
LOST view: Semantic view
Interoperability Saliency: The Open Data Representation ABB is salient for semantic interoperability because it is the basis for sharing, reusing and making available relevant and public information from public organisations and the digital public services delivery.
Identifier: http://data.europa.eu/dr8/OpenDataRepresentation
ABB name: eira:OpenDataRepresentation
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/OpenDataRepresentation
Interoperability Layer: Semantic
Description: Turtle (Terse RDF Triple Language) is a human-readable serialization format for representing RDF (Resource Description Framework) data. It provides a concise and compact syntax to express triples, which consist of subject-predicate-object statements. Turtle is widely used for creating and sharing RDF data due to its simplicity and readability.
Publisher: W3C
Source: https://www.w3.org/TR/turtle/
LOST view: SV-Functional Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/TurtleRepresentation
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/egovera/TurtleRepresentation
Interoperability Layer: Semantic
Realises: http://data.europa.eu/dr8/DataRepresentation
Description: CSV serves as a convenient and widely adopted data representation method due to its simplicity and compatibility with various applications and programming languages. It allows data to be easily imported, exported, and exchanged between different systems, making it a popular choice for data interchange. By using CSV as a data representation method, one can efficiently represent structured information such as database records, spreadsheets, and tables in a human-readable and machine-readable format. It provides a standardized and flexible approach to store and transmit data, enabling seamless integration and interoperability among different software and platforms.
Publisher: IETF
Source: https://www.rfc-editor.org/rfc/rfc4180
LOST view: SV-Functional Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/CSVRepresentation
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/egovera/CSVRepresentation
Interoperability Layer: Semantic
Realises: http://data.europa.eu/dr8/DataRepresentation
Description: RDF-XML (Resource Description Framework XML) is a syntax format used to represent metadata and structured data in the form of Resource Description Framework (RDF) triples. RDF-XML provides a way to encode and exchange data using XML (eXtensible Markup Language) syntax.
Publisher: W3C
Source: https://www.w3.org/TR/rdf-syntax-grammar/
LOST view: SV-Functional Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/RDF-XMLRepresentation
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/egovera/RDF-XMLRepresentation
Interoperability Layer: Semantic
Realises: http://data.europa.eu/dr8/DataRepresentation
Description: RDF Schema provides a data-modelling vocabulary for RDF data. RDF Schema is an extension of the basic RDF vocabulary.
Publisher: W3C
Source: https://www.w3.org/TR/rdf12-schema/
LOST view: SV-Functional Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/RDF-SRepresentation
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/egovera/RDF-SRepresentation
Interoperability Layer: Semantic
Realises: http://data.europa.eu/dr8/DataRepresentation
Definition: RDF serialization can be defined as the process of encoding RDF (Resource Description Framework) data into a specific format or syntax that enables the storage, transmission, and exchange of structured data in a machine-readable manner. It involves transforming RDF triples into a serialized form, allowing data to be easily parsed, interpreted, and processed by both humans and computer systems.
Source: W3C
Source reference: https://www.w3.org/TR/rdf11-primer/
LOST view: SV-Functional Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/RDFSerialisationsRepresentation
ABB name: egovera:RDFSerialisationsRepresentation
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/egovera/RDFSerialisationsRepresentation
Interoperability Layer: Semantic
Specialises: http://data.europa.eu/dr8/DataRepresentation
Description: The RDF Mapping Language (RML) is a technical specification that provides a standardized approach for transforming structured data from various formats into RDF (Resource Description Framework). RML enables the mapping of data from sources such as databases, spreadsheets, or APIs to RDF, which allows for semantic integration and interoperability. It provides a flexible and extensible mapping language that defines how the source data should be transformed into RDF triples. RML supports complex mappings, allowing for data extraction, transformation, and enrichment during the conversion process. By utilizing RML, technical teams can efficiently convert diverse data sources into RDF, facilitating seamless integration and utilization of structured data within the semantic web and linked data ecosystems.
Publisher: rml.io
Source: https://rml.io/specs/rml/
LOST view: SV-Functional Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/RMLRepresentation
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/egovera/RMLRepresentation
Interoperability Layer: Semantic
Realises: http://data.europa.eu/dr8/DataRepresentation
Description: JSON Lines, also known as newline-delimited JSON, is a text format designed for storing structured data that can be processed one record at a time. It provides a convenient and efficient way to store and exchange data in a format that is compatible with Unix-style text processing tools and shell pipelines.
Publisher: JSON.org
Source: https://jsonlines.org/
LOST view: SV-Functional Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/JSON-LRepresentation
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/egovera/JSON-LRepresentation
Interoperability Layer: Semantic
Realises: http://data.europa.eu/dr8/DataRepresentation
Description: JSON-LD (JSON for Linked Data) is a serialization format that enables the representation of linked data using JSON (JavaScript Object Notation). It allows for the integration of structured data from different sources on the web, facilitating interoperability and knowledge sharing across systems.
Publisher: W3C
Source: https://www.w3.org/TR/json-ld11/
LOST view: SV-Functional Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/JSON-LDRepresentation
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/egovera/JSON-LDRepresentation
Interoperability Layer: Semantic
Realises: http://data.europa.eu/dr8/DataRepresentation
Definition: Linked data ABB is a Representation that enables a set of principles and technologies for publishing, sharing, and connecting structured data on the web.
Source: W3C-Linked Data
Source reference: https://www.w3.org/standards/semanticweb/data
Example: The following implementation is an example of how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): Publications Office Linked Data Repository. https://op.europa.eu/en/linked-data
Interoperability Dimension: Structural IoP
LOST view: Semantic view
Interoperability Saliency: The Linked Data Representation ABB is salient for semantic interoperability because it provides a set of publishing, sharing, and connection methods that allow linking the data from digital public services, making it more meaningful and increasing the quality and scope of data and services.
Identifier: http://data.europa.eu/dr8/LinkedDataRepresentation
ABB name: eira:LinkedDataRepresentation
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/LinkedDataRepresentation
Interoperability Layer: Semantic
Description: RDF (Resource Description Framework) is a standard that enables businesses to represent and connect information in a structured and machine-readable way. It uses triples, which are subject-predicate-object statements, to describe resources and their relationships. RDF facilitates data integration and sharing across domains and systems, providing a common language for businesses to exchange and utilize structured information effectively. It forms the basis for building semantic web applications and supports data interoperability, enabling organizations to leverage and connect their data assets for improved decision-making and collaboration.
Publisher: W3C
Source: https://www.w3.org/RDF/
LOST view: SV-Functional Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/RDFRepresentation
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/egovera/RDFRepresentation
Interoperability Layer: Semantic
Realises: http://data.europa.eu/dr8/DataRepresentation
Description: N3 is a serialization format for representing RDF (Resource Description Framework) data. It is an extension of Turtle (Terse RDF Triple Language) and provides additional features for expressing rules, formulas, and logical statements within RDF graphs. N3 aims to provide a more expressive and flexible syntax for representing RDF data compared to other serialization formats.
Publisher: W3C
Source: https://www.w3.org/TeamSubmission/n3/
LOST view: SV-Functional Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/N3Representation
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/egovera/N3Representation
Interoperability Layer: Semantic
Realises: http://data.europa.eu/dr8/DataRepresentation
Description: SIARD (Software Independent Archival of Relational Databases) is a normative description of an open file format for the long-term archiving of relational databases. SIARD is a nonproprietary, published open standard. The SIARD format is based on open standards, including the ISO standards Unicode, XML, and SQL, the URI Internet standard, and the industry standard ZIP. The aim of employing internationally recognised standards is to ensure the long-term preservation of, and access to, the widely used relational database model, as well as easy exchange of database content, independent of proprietary “dump” formats.
Publisher: The Digital Information LifeCycle Interoperability Standards Board (DILCIS Board)
Source: https://siard.dilcis.eu/
LOST view: SV-Functional Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/SIARD20FormatForDatabasesRepresentation
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/egovera/SIARD20FormatForDatabasesRepresentation
Interoperability Layer: Semantic
Realises: http://data.europa.eu/dr8/DataRepresentation
Definition: Linked Data Event Stream ABB is a Representation of immutable objects that can be publish, consumed and processing in real-time according to the Linked Data principles.
Source: SEMIC
Source reference: https://joinup.ec.europa.eu/collection/semic-support-centre
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): LDES - SEMIC Linked Event Streams pilot for the ERA (European Railway Agency). LDES provides a data publishing alternative based on Linked Data principles, that models dataset changes as a stream of events. This enables opportune data synchronization tasks and access to previous versions of dataset (historic data). In this pilot we aim to establish the foundations and show the benefits of the LDES approach, to power a specific use case required by ERA, namely the infrastructure change alert. https://joinup.ec.europa.eu/collection/semantic-interoperability-community-semic/event/semic-linked-data-event-streams-pilot-era-9th-june
Interoperability Dimension: Structural IoP
LOST view: Semantic view
Interoperability Saliency: The Linked Data Event Stream Representation ABB is salient for semantic interoperability because it contributes to secure data consumption and processing ensuring that exchanged data is not modified or altered. The fact of being immutable is relevant to ensure data integrity over time.
Identifier: http://data.europa.eu/dr8/LinkedDataEventStreamRepresentation
ABB name: eira:LinkedDataEventStreamRepresentation
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/LinkedDataEventStreamRepresentation
Interoperability Layer: Semantic
Description: NQuads is a serialization format used for representing RDF (Resource Description Framework) data that extends the capabilities of the N-Triples format. NQuads provides a straightforward and flexible way to express RDF data in a quad format, which includes an additional context or named graph component. This makes it suitable for representing RDF datasets that involve multiple named graphs or contexts.
Publisher: W3C
Source: https://www.w3.org/TR/n-quads/
LOST view: SV-Functional Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/NQadsRepresentation
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/egovera/NQadsRepresentation
Interoperability Layer: Semantic
Realises: http://data.europa.eu/dr8/DataRepresentation
Description: Keyhole Markup Language (KML) is an XML notation for expressing geographic annotation and visualization within two-dimensional maps and three-dimensional Earth browsers. KML was developed for use with Google Earth, which was originally named Keyhole Earth Viewer. It was created by Keyhole, Inc, which was acquired by Google in 2004. KML became an international standard of the Open Geospatial Consortium in 2008. Google Earth was the first program able to view and graphically edit KML files, but other projects such as Marble have added KML support.
Publisher: Keyhole.inc
Source: https://www.bing.com/search?q=keyhole+markup+language&cvid=61ba8b6734a744768bdc79af95473cc8&aqs=edge.1.69i57j0l8j69i11004.7235j0j4&FORM=ANAB01&PC=U531
LOST view: SV-Functional Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/KMLRepresentation
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/egovera/KMLRepresentation
Interoperability Layer: Semantic
Realises: http://data.europa.eu/dr8/DataRepresentation
Description: CDM is an ontology based on the FRBR model (Functional Requirements for Bibliographic Records). CDM uses RDF(S)/OWL technologies, capable of representing relationships between the resource types managed by the Publications Office and their views. All within the scope of the FRBR model and, therefore, in terms of Work, Expression, Manifestation and Item.
Publisher: The Publications Office of the European Union
Source: https://op.europa.eu/en/web/eu-vocabularies/cdm
LOST view: SV-Functional Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/CommonDataModelRepresentation
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/egovera/CommonDataModelRepresentation
Interoperability Layer: Semantic
Realises: http://data.europa.eu/dr8/DataRepresentation
Description: SPARQL is a query language that enables organizations to extract valuable insights and knowledge from their semantic data. It plays a crucial role in the field of linked data and the semantic web, which focus on creating structured and interconnected data ecosystems.
Publisher: W3C
Source: https://www.bing.com/ck/a?!&&p=97d6e35279e66026JmltdHM9MTY4NzM5MjAwMCZpZ3VpZD0wMjYzNjViYy02Y2NlLTY1YzAtMDc1ZS03NzEwNmQ2NjY0NGYmaW5zaWQ9NTIwMA&ptn=3&hsh=3&fclid=026365bc-6cce-65c0-075e-77106d66644f&psq=sparwl*&u=a1aHR0cHM6Ly93d3cudzMub3JnL1RSL3NwYXJxbDExLXF1ZXJ5Lw&ntb=1
LOST view: SV-Functional Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/SPARQLRepresentation
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/egovera/SPARQLRepresentation
Interoperability Layer: Semantic
Realises: http://data.europa.eu/dr8/DataRepresentation
Description: SKOS plays a crucial role in improving information retrieval, data integration, and semantic interoperability, as it provides a standardized approach to representing and exchanging knowledge. By utilizing SKOS, businesses can enhance the discoverability and accessibility of their knowledge resources, leading to more effective search, navigation, and analysis of information within their systems and applications.
Publisher: W3C
Source: https://www.w3.org/2004/02/skos/
LOST view: SV-Functional Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/SKOSRepresentation
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/egovera/SKOSRepresentation
Interoperability Layer: Semantic
Realises: http://data.europa.eu/dr8/DataRepresentation
Description: The SPARQL Results CSV Results Format is a lossy encoding of a table of results. It does not encode all the details of each RDF term in the results but instead just gives a string without indicating the type of the term (IRI, Literal, Literal with datatype, Literal with language, or blank node). This makes it simple to consume data, such as text and numbers, in applications without needing to understand the details of RDF. In some applications, guesses as to which elements are hyperlinks are made pragmatically, for example, guessing that strings starting "http://" are links.
Publisher: W3C
Source: https://www.w3.org/TR/sparql11-results-csv-tsv/
LOST view: SV-Functional Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/SPARQL-CSVRepresentation
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/egovera/SPARQL-CSVRepresentation
Interoperability Layer: Semantic
Realises: http://data.europa.eu/dr8/DataRepresentation
Definition: Legal Act Representation ABB is a Representation manifesting the content of a legal Act in a digital format, thus making possible digital public services to exchange such content.
Source: Based on the IFLA concepts of 'manifestation' and Legal Act.
Source reference: https://repository.ifla.org/handle/123456789/40
Additional information: Legal Act Representation can be human or machine readable. In the context of digital public services they are, either way, digitally supported (i.e., no physical sypports like paper or other that are not bytes are involved in the exchange of data and information).
Example: The following implementation is an example of how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): The XML specification Akoma Ntoso is used to address the need of the public administration and European Institutions to generate draft legislation in the legal XML format Akoma Ntoso (the OASIS TC LegalXMLDocument). This specification is used by LEOS (Legislation Editing Open Software, https://joinup.ec.europa.eu/collection/justice-law-and-security/solution/leos-open-source-software-editing-legislation/release/330).
Interoperability Dimension: Structural IoP
LOST view: Legal view
Viewpoint: Highlevel viewpoint
Interoperability Saliency: The Legal Act Representation ABB is salient for the Behavioural Interoperability because it enables the exchange, reading and processing of Legal Acts. It is also salient for the Structural Interoperability since the content digitally represented can be searched and reused in different domains and for differnt purposes.
Identifier: http://data.europa.eu/dr8/LegalActRepresentationRepresentation
ABB name: eira:LegalActRepresentationRepresentation
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
eira:modelType: Behavioural IoP, Structural IoP
Identifier: http://data.europa.eu/dr8/LegalActRepresentationRepresentation
Interoperability Layer: Legal
Description: A Linked Data Event Stream (LDES) is a new data publishing approach which allows you to publish any dataset as a collection of immutable objects. The focus of an LDES is to allow clients to replicate the history of a dataset and efficiently synchronise with its latest changes.
Publisher: SEMIC (European Commission)
Source: https://semiceu.github.io/LinkedDataEventStreams/
LOST view: SV-Functional Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/LDESRepresentation
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/egovera/LDESRepresentation
Interoperability Layer: Semantic
Realises: http://data.europa.eu/dr8/DataRepresentation
Description: Geography Markup Language (GML) is an XML-based format that is used to encode geographic information, including the geometry and properties of geographic features. It is designed to facilitate the exchange of geographic data between different systems and applications, and is commonly used in domains such as geographic information systems (GIS), web mapping, and location-based services. The Open Geospatial Consortium (OGC) is responsible for maintaining GML, and the latest version of the format is GML 3.2.1, which was released in 2019.
Publisher: Open Geospatial Consortium (OGC)
Source: https://www.ogc.org/standard/gml/
LOST view: SV-Functional Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/GMLRepresentation
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/egovera/GMLRepresentation
Interoperability Layer: Semantic
Realises: http://data.europa.eu/dr8/DataRepresentation
Description: JSON (JavaScript Object Notation) is a lightweight data-interchange format. It is easy for humans to read and write. It is easy for machines to parse and generate. It is based on a subset of the JavaScript Programming Language Standard ECMA-262 3rd Edition - December 1999. JSON is a text format that is completely language independent but uses conventions that are familiar to programmers of the C-family of languages, including C, C++, C#, Java, JavaScript, Perl, Python, and many others. These properties make JSON an ideal data-interchange language.
Publisher: JSON.org
Source: https://www.json.org/json-en.html
LOST view: SV-Functional Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/JSONRepresentation
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/egovera/JSONRepresentation
Interoperability Layer: Semantic
Realises: http://data.europa.eu/dr8/DataRepresentation
Description: The OASIS ebMS 3.0 Standard combined multiple Web Service standards to create a single comprehensive specification for defining the secure and reliable exchange of documents using Web Services. The AS4 profile of the ebMS 3.0 specification was developed in order to bring continuity to the principles and simplicity that made AS2 successful, while adding better compliance to Web Services standards, and features such as message pulling capability and a built-in Receipt mechanism.
Publisher: OASIS
Source: http://docs.oasis-open.org/ebxml-msg/ebms/v3.0/profiles/AS4-profile/v1.0/os/AS4-profile-v1.0-os.html
LOST view: SV-Functional Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/AS4ProfileOfEbMS30V10Representation
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/egovera/AS4ProfileOfEbMS30V10Representation
Interoperability Layer: Semantic
Realises: http://data.europa.eu/dr8/DataRepresentation
Description: TRiG is designed to express RDF data involving multiple named graphs or contexts. It allows the grouping of triples into different graphs, providing a way to differentiate and organize data within an RDF dataset. TRiG syntax is similar to Turtle, but it includes additional features for representing named graphs.
Publisher: W3C
Source: https://www.w3.org/TR/trig/
LOST view: SV-Functional Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/TRiGRepresentation
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/egovera/TRiGRepresentation
Interoperability Layer: Semantic
Realises: http://data.europa.eu/dr8/DataRepresentation
Definition: Artificial Intelligence ABB is an Application Component that enables the implementation of algorithms, machine learning, and deep learning techniques to enable machines to perform tasks that typically require human-like intelligence, such as perception, reasoning, learning, and decision-making
Source: European Comision
Source reference: https://digital-strategy.ec.europa.eu/en/library/definition-artificial-intelligence-main-capabilities-and-scientific-disciplines
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): PyTorch is a machine learning framework based on the Torch library, used for applications such as computer vision and natural language processing, originally developed by Meta AI and now part of the Linux Foundation umbrella. It is free and open-source software released under the modified BSD license. Although the Python interface is more polished and the primary focus of development, PyTorch also has a C++ interface. https://pytorch.org/
Interoperability Dimension: Structural IoP
LOST view: Technical view - application
Interoperability Saliency: The Artificial Intelligence Application Component ABB is salient for technical interoperability because it provides tools and components that are able to perform operations that would require human intervention such as perception, reasoning, learning, and decision-making. By training artificial intelligence components, digital public services could reach an additional level of maturity increasing efficiency and effectiveness on interoperable processes without requiring human intervention.
Identifier: http://data.europa.eu/dr8/ArtificialIntelligenceApplicationComponent
ABB name: eira:ArtificialIntelligenceApplicationComponent
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/ArtificialIntelligenceApplicationComponent
Interoperability Layer: TechnicalApplication
Definition: Metadata Management ABB is an Application Component that enables the implementation of components for the i) creation, ii) storage, iii) categorisation and iv) retrieval of metadata.
Source: DAMA
Source reference: http://www.dama.org/
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): Eurostat SDMX repository: The Euro SDMX Registry is Eurostat’s implementation of an SDMX registry to facilitate the exchange of statistical data and metadata by serving as a metadata repository. It stores the SDMX artefacts needed for the parties to access and interpret the content of the exchanged statistical data and metadata sets. http://ec.europa.eu/eurostat/web/sdmx-infospace/sdmx-it-tools/sdmx-registry
Interoperability Dimension: Structural IoP
LOST view: Technical view - application
Viewpoint: Interoperability Privacy viewpoint
Interoperability Saliency: The Metadata management Component ABB is an application component providing the implementation of the functionalities to manage metadata. EIF recommends to prioritise it: "Put in place an information management strategy at the highest possible level to avoid fragmentation and duplication. Management of metadata, master data and reference data should be prioritised."
Identifier: http://data.europa.eu/dr8/MetadataManagementApplicationComponent
ABB name: eira:MetadataManagementApplicationComponent
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/MetadataManagementApplicationComponent
Interoperability Layer: TechnicalApplication
Definition: Access Management ABB is an Application Component implementing the process of granting rights to users and preventing the access to non-authorised users.
Source: ITIL v3
Source reference: https://wiki.en.it-processmaps.com/index.php/Access_Management
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): OpenIAM Access Manager - OpenIAM Access Management solution is based on a professional open source model. This is a robust, scalable solution built with Service Oriented Architecture. It integrates seamlessly with the OpenIAM Identity Manager product to provide a comprehensive solution that allows to take control of not only who can access the systems, but what they can do once they are in there. Corporate security policy is enforced across multiple points and managed centrally to improve effectiveness and reduce administrative costs.(http://www.openiam.com/products/access-manager/overview/)
Interoperability Dimension: Structural IoP
LOST view: Technical view - application
Viewpoint: Interoperability Security viewpoint
Interoperability Saliency: The Access Management Component ABB is salient for technical interoperability because it provides the implementation the functionality of allowing user to make an authorized and trusted use of IT Services, data and other assets as stated in the EIF: "Public administrations should ensure that a 'data access and authorisation plan’ which determines who has access to what data and under what conditions, to ensure privacy. Unauthorised access and security breaches should be monitored and appropriate actions should be taken to prevent any recurrence of breaches"
Identifier: http://data.europa.eu/dr8/AccessManagementApplicationComponent
ABB name: eira:AccessManagementApplicationComponent
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/AccessManagementApplicationComponent
Interoperability Layer: TechnicalApplication
Definition: Conformance Testing ABB is an Application Component that enables a structural and modular approach for implementing the validation of the application or service to meet the requirements of a standard or specification
Source: NIST
Source reference: https://www.nist.gov/itl/ssd/information-systems-group/conformance-testing
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): Interoperability Testbed - The Test Bed allows users to execute predefined test cases on their systems in order to test the conformance to standards and requirements, simulate a web-service, validate content and test a complete message exchange protocol. The Testbed manages test cases and users, and orchestrates domain-specific components, the domain-specific logic is in separate components that are used via web services. Test results are provided in a standardised, machine-readable format. The Test Bed also offers a test registry and repository (TRR) to store test artefacts (assertions, test cases, validation schemas, etc.) and compile test services (validation services, simulator services, etc.). Please visit the following website for more information: https://ec.europa.eu/isa2/solutions/interoperability-test-bed_en
Interoperability Dimension: Structural IoP
LOST view: Technical view - application
Interoperability Saliency: The Conformance Testing Component ABB is salient for technical interoperability because it enables the validation and verification that several solutions at one or more layers of the interoperability stack and they satisfy certain interoperability requirements.
Identifier: http://data.europa.eu/dr8/ConformanceTestingApplicationComponent
ABB name: eira:ConformanceTestingApplicationComponent
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/ConformanceTestingApplicationComponent
Interoperability Layer: TechnicalApplication
Definition: Data Virtualization ABB is an Application Component that implements the functionality of retrieving and manipulating data without requiring technical details about the data format or location.
Source: Joinup
Source reference: https://joinup.ec.europa.eu/sites/default/files/inline-files/Data%20visualisation%20service%20definition.pdf
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): Virtuoso. Virtuoso Universal Server is modern platform built on existing open standards that harnesses the power of Hyperlinks (functioning as Super Keys) for breaking down data silos that impede both user and enterprise ability. For example, Virtuoso's core SQL & SPARQL powers many Enterprise Knowledge Graph initiatives just as it does DBpedia and a majority of nodes in the Linked Open Data Cloud -- the world's largest publicly accessible Knowledge Graph. https://big-data-test-infrastructure.ec.europa.eu/service-offering/virtuoso_en
Interoperability Dimension: Structural IoP
LOST view: Technical view - application
Interoperability Saliency: The Data Virtualization Component ABB is salient for technical interoperability because it realises the services established and defined by the Data Virtualization Service ABB, collaborating with enabling interoperability between public services that generate, process or consume data.
Identifier: http://data.europa.eu/dr8/DataVirtualizationApplicationComponent
ABB name: eira:DataVirtualizationApplicationComponent
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/DataVirtualizationApplicationComponent
Interoperability Layer: TechnicalApplication
Definition: Shared Platform ABB is an Application Component supporting the reuse and efficiency, enabling organisations to leverage common sets of tools. his approach helps organizations optimize costs, improve resource utilisation, and foster innovation and collaboration. Shared Platforms facilitate better data management and exchange, provide scalability and flexibility, and help maintain consistency and compliance across different applications and services within the enterprise.
Source: Inspired in definitions from referent companies of IT sector
Additional information: This convergence power is based on the instrumental nature and efficiencies of these resources for enabling common problem-solving approaches. The degree of achievement could range from an ideal perfect shared platform (i.e. no interoperability barriers from the technical perspective) to an imperfect or even null shared platform (i.e. some interoperability barriers from the technical perspective). The level of technical interoperability will constrain digital public services cross levels in a public administration, cross public administrations, and cross borders. The shared platform enables: i) structural interoperability with technical resources supporting reusing and/or sharing of digital public services (i.e. service registry service); ii) behavioural interoperability with technical resources supporting exchanging capabilities of data, information or knowledge with internal/external peers (i.e. Technical interfaces); and iii) governance interoperability with technical resources supporting the assurance and control of collaboration with internal/external peers exchanging data, information, and knowledge(i.e. Technical Interoperability Agreements). Shared Platform offers a harmonised repository of business and technological resources that are essential for the dissemination of unique business functionalities. It is the cornerstone of a digital ecosystem, invariably interfacing with constituents through APIs or providing bespoke connectivity solutions like direct data access, thus ensuring that the organisation's digital fabric is both resilient and adaptive.
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): The Commission proposed a framework for a European Digital Identity which will be available to all EU citizens, residents, and businesses in the EU. Citizens will be able to prove their identity and share electronic documents from their European Digital Identity wallets with the click of a button on their phone. They will be able to access online services with their national digital identification, which will be recognised throughout Europe. Very large platforms will be required to accept the use of European Digital Identity wallets upon request of the user, for example to prove their age.(https://ec.europa.eu/commission/presscorner/detail/en/IP_21_2663)
Interoperability Dimension: Structural IoP
LOST view: Technical view - application
Viewpoint: Interoperability Security viewpoint
Interoperability Saliency: The Shared Platform ABB is a key interoperability enabler because it supports to achieve technical interoperability with public policy goals convergence value by all in all enabling i) the provision/consumption of back-office digital public services, ii) the exchange of data, information, and knowledge between digital public services and individuals , and iii) collaboration between digital public services.
Identifier: http://data.europa.eu/dr8/SharedPlatformApplicationComponent
ABB name: eira:SharedPlatformApplicationComponent
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/SharedPlatformApplicationComponent
Interoperability Layer: TechnicalApplication
Definition: Agenda Management Component ABB is an Application Component that enables the implementation of the procedures to create, distribute and manage events and meetings for public administration and services
Source: Inspired in Public Works and Goverment Services Canada
Source reference: https://buyandsell.gc.ca/cds/public/2016/11/23/c7b27e0ac41ad50ffae2f12b0a837875/ABES.PROD.PW_PWZ.B014.E10051.ATTA001.PDF
Example: The following implementation is an example of how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): Innovation Public Procurement Broker (IPPB). https://ec.europa.eu/futurium/en/system/files/ged/action_7_innovation_public_procurement_broker_guideline.pdf
Interoperability Dimension: Structural IoP
LOST view: Technical view - application
Interoperability Saliency: The Agenda Management Application Component ABB is salient for technical interoperability because it implements the orchestration of different events within digital public services within specific platforms but can be reused and extended in a high-level approach to enable interoperability of digital public services and the different delivery models.
Identifier: http://data.europa.eu/dr8/AgendaManagementApplicationComponent
ABB name: eira:AgendaManagementApplicationComponent
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/AgendaManagementApplicationComponent
Interoperability Layer: TechnicalApplication
Definition: Data Quality Component ABB is an Application Component that enables the implementation of verifying that the value of a data item comes from a given set of acceptable values. Data validation may be followed by corrective actions, such as data editing or data imputation. In statistics, imputation is the process of replacing missing data with substituted values.
Source: Eurostat Data Validation
Source reference: http://ec.europa.eu/eurostat/data/data-validation
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): Hibernate Validator - Express validation rules in a standardized way using annotation-based constraints and benefit from transparent integration with a wide variety of frameworks. Application layer agnostic validation: Hibernate Validator allows to express and validate application constraints. The default metadata source are annotations, with the ability to override and extend through the use of XML. It is not tied to a specific application tier or programming model and is available for both server and client application programming. Hibernate Validator presents the following characteristics: • Extendable: Hibernate Validator offers a configurable bootstrap API as well as a range of built-in constraints. The latter can easily be extended by creating custom constraints; • Rich metadata API: Hibernate Validator gives access to constraint configuration via a metadata API facilitating, for example, tooling integration; • Reference implementation: Hibernate Validator 6.x is the reference implementation Bean Validation 2.0; • Added value: Hibernate Validator offers additional value on top of the features required by Bean Validation. For example, a programmatic constraint configuration API as well as an annotation processor which plugs into the build process and raises compilation errors whenever constraint annotations are incorrectly used. http://hibernate.org/validator/
Interoperability Dimension: Structural IoP
LOST view: Technical view - application
Viewpoint: Interoperability Privacy viewpoint
Interoperability Saliency: The Data Quality Component ABB is salient for technical interoperability because it allows the implementation of the functionality to validate if data received (or to be sent) is compliant with common and agreed interoperable formats as stated in the EIF recommendation n° 41: "Establish procedures and processes to integrate the opening of data in your common business processes, working routines, and in the development of new information systems."
Identifier: http://data.europa.eu/dr8/DataQualityApplicationComponent
ABB name: eira:DataQualityApplicationComponent
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/DataQualityApplicationComponent
Interoperability Layer: TechnicalApplication
Definition: Data Analytics ABB is an Application Component that enables the implementation of procedures to analyze data and extract insights that can be used to improve business decision-making, optimize business processes, and drive innovation
Source: Inspired in Data Act
Source reference: https://digital-strategy.ec.europa.eu/en/policies/data-act
Additional information: Data analytics component enable the automation of mechanical processes and algorithms that work over raw data for human consumption.
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): Microsoft Power BI - Power BI is a business analytics service by Microsoft. It aims to provide interactive visualizations and business intelligence capabilities with an interface simple enough for end users to create their own reports and dashboards. It is part of the Microsoft Power Platform.(https://powerbi.microsoft.com/it-it/what-is-power-bi/)
Interoperability Dimension: Structural IoP
LOST view: Technical view - application
Interoperability Saliency: The Data Analytics Component ABB is salient for technical interoperability because it provides the implementation of functionalities for the automation of mechanical processes and algorithms that work over raw data for human consumption.
Identifier: http://data.europa.eu/dr8/DataAnalyticsApplicationComponent
ABB name: eira:DataAnalyticsApplicationComponent
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/DataAnalyticsApplicationComponent
Interoperability Layer: TechnicalApplication
Definition: Knowledge Discovery ABB is an Application Component that enables the implementation of processes where a lot of data manipulation tools with different characteristics have to be used together to reach the goal of previously unknown, potentially useful information extraction.
Source: Inspired in EUROSTAT
Source reference: https://ec.europa.eu/eurostat/statistics-explained/index.php?title=Glossary:Knowledge-intensive_services_(KIS)
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): CELLAR. Cellar metadata is stored in a knowledge graph, and more specifically in a triple store. A SPARQL interface is used to query the metadata. https://op.europa.eu/en/web/cellar/cellar-data/metadata/knowledge-graph
Interoperability Dimension: Structural IoP
LOST view: Technical view - application
Interoperability Saliency: The Knowledge Discovery Application Component ABB is salient for technical interoperability because it contributes to performing a highly complex process where a lot of data manipulation tools with different characteristics have to be used together to reach the goal of previously unknown, potentially useful information extraction.
Identifier: http://data.europa.eu/dr8/KnowledgeDiscoveryApplicationComponent
ABB name: eira:KnowledgeDiscoveryApplicationComponent
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/KnowledgeDiscoveryApplicationComponent
Interoperability Layer: TechnicalApplication
Definition: Data Extraction, Transformation and Loading ABB is an Application Component that enables the implementation of the process of extracting data from various sources, transforming the data to specific data models and loading the data into a target data store.
Source: Inspired in definitions from referent companies of IT sector
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): Eurostat SDMX converter - The SDMX Converter is a tool that converts statistical datasets between different formats. It is a Java application which is actively developed by Eurostat and is published as open source software. http://ec.europa.eu/eurostat/web/sdmx-infospace/sdmx-it-tools/sdmx-converter
Interoperability Dimension: Structural IoP
LOST view: Technical view - application
Viewpoint: Interoperability Privacy viewpoint
Interoperability Saliency: The Data Extraction, Transformation, and Loading Component ABB is salient for technical interoperability because it enables the implementation of the functionalities to transform internal data structures to common and agreed interoperable formats as stated in the EIF recommendation n° 41: "Establish procedures and processes to integrate the opening of data in your common business processes, working routines, and in the development of new information systems."
Identifier: http://data.europa.eu/dr8/DataExtractionTransformationAndLoadingApplicationComponent
ABB name: eira:DataExtractionTransformationAndLoadingApplicationComponent
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/DataExtractionTransformationAndLoadingApplicationComponent
Interoperability Layer: TechnicalApplication
Definition: Schedule Management Component ABB is an Application Component that enables the implementation of the procedures to manage time and events in the achievement of the goals and delivery of public services.
Source: Inspired in Public Works and Goverment Services Canada
Source reference: https://buyandsell.gc.ca/cds/public/2016/11/23/c7b27e0ac41ad50ffae2f12b0a837875/ABES.PROD.PW_PWZ.B014.E10051.ATTA001.PDF
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): Chronos is a replacement for cron. It is a distributed and fault-tolerant scheduler that runs on top of Apache Mesos that can be used for job orchestration. It supports custom Mesos executors as well as the default command executor. Thus by default, Chronos executes sh (on most systems bash) scripts. https://sourceforge.net/projects/chronos.mirror/
Interoperability Dimension: Structural IoP
LOST view: Technical view - application
Interoperability Saliency: The Schedule Management Application Component ABB is salient for technical interoperability because it implements the orchestration of different events within digital public services within specific platforms but can be reused and extended in a high-level approach to enable interoperability of digital public services and the different delivery models.
Identifier: http://data.europa.eu/dr8/ScheduleManagementApplicationComponent
ABB name: eira:ScheduleManagementApplicationComponent
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/ScheduleManagementApplicationComponent
Interoperability Layer: TechnicalApplication
Definition: Trust Service Provisioning ABB is an Application Component that enables the creation, verification, or validation of electronic signatures, time stamps, seals, electronically registered delivery services, and certificates.
Source: eIDAS
Source reference: http://eur-lex.europa.eu/legal-content/EN/TXT/?uri=uriserv%3AOJ.L_.2014.257.01.0073.01.ENG
Additional information: A ‘trust service’ means an electronic service normally provided for remuneration which consists of these functionalities: i) 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; ii) the creation, verification and validation of certificates for website authentication; or; iii) the preservation of electronic signatures, seals or certificates related to those services.
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): e-TrustEx - Open e-TrustEx is a platform offered by the Directorate-General for Informatics of the European Commission to Public Administrations at European, national and regional level to set up secure exchange of natively digital documents from system to system via standardized interfaces. Open e-TrustEx provides a set of generic web services, which Public Administrations can use to connect heterogeneous applications, removing the need for complex point-to-point connections. http://eur-lex.europa.eu/legal-content/DE/TXT/?uri=CELEX%3A52016SC0279
Interoperability Dimension: Structural IoP
LOST view: Technical view - application
Viewpoint: Interoperability Security viewpoint
Interoperability Saliency: The Trust Service Provisioning Component ABB is salient for technical interoperability because it provides the implementation of the functionalities of information exchange between between administrations, businesses and citizens (e-signature and e-seal creation, verification,validation and preservation, timestamping creation, verification and validation, identity management, etc.) as stated in the EIF recommendation n°47: "Use trust services according to the Regulation on eID and Trust Services as mechanisms that ensure secure and protected data exchange in public services."
Identifier: http://data.europa.eu/dr8/TrustServiceProvisioningApplicationComponent
ABB name: eira:TrustServiceProvisioningApplicationComponent
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/TrustServiceProvisioningApplicationComponent
Interoperability Layer: TechnicalApplication
Definition: Data Persistence ABB is an Application Component that enables the implementation of components that are responsible for managing the storage and retrieval of data within an application. It provides an interface for storing and retrieving data from a database, file system, or other storage medium.
Source: Inspired in European Comision Data Strategy
Source reference: https://commission.europa.eu/strategy-and-policy/priorities-2019-2024/europe-fit-digital-age/european-data-strategy_en
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): Context Broker as a CEF Building Block https://ec.europa.eu/digital-building-blocks/wikis/download/attachments/82773424/Context%20Broker%20Brochure.pdf?version=1&modificationDate=1558016168498&api=v2
Interoperability Dimension: Structural IoP
LOST view: Technical view - application
Interoperability Saliency: The Data Persistence Application Component ABB is salient for technical interoperability because it is can be part of a digital public service to store, and retrieve data within specific applications or systems. It is the basis that realises the Data Persistence Service by providing an interface to manage data and then supporting interoperability through public services.
Identifier: http://data.europa.eu/dr8/DataPersistenceApplicationComponent
ABB name: eira:DataPersistenceApplicationComponent
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/DataPersistenceApplicationComponent
Interoperability Layer: TechnicalApplication
Definition: Data Publication ABB is an Application Component that implements the functionality of making data publicly available and discoverable for reuse by other public administration services.
Source: ISA2
Source reference: https://ec.europa.eu/isa2/sites/default/files/docs/publications/isa2-actions-phase2_-_poc_-_wp1_specifications_en.pdf
Example: The following implementation is an example of how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): CKAN - CKAN is a data publication tool that makes data accessible by providing tools to streamline publishing, sharing, finding and using data. This is a tool for making open data websites. It helps you manage and publish collections of data. It is used by national and local governments, research institutions, and other organizations that collect a lot of data. Once your data is published, users can use its faceted search features to browse and find the data they need and preview it using maps, graphs and tables – whether they are developers, journalists, researchers, NGOs, citizens, or even your staff. CKAN is open-source and free software, with an active community of contributors who develop and maintain its core technology. CKAN is modified and extended by an even larger community of developers who contribute to a growing library of CKAN extension. https://ckan.org/
Interoperability Dimension: Structural IoP
LOST view: Technical view - application
Viewpoint: Interoperability Privacy viewpoint
Interoperability Saliency: The Data Pubblication Component ABB is salient for technical interoperability because it provides the implementation of the functionalities to make public data freely available for use and reuse by others unless restriction aoply as stated in the EIF recommendation n.2: "Publish the data you own as open data unless certain restrictions apply."
Identifier: http://data.europa.eu/dr8/DataPublicationApplicationComponent
ABB name: eira:DataPublicationApplicationComponent
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/DataPublicationApplicationComponent
Interoperability Layer: TechnicalApplication
Definition: Identification ABB is an Application Component implementing the process of verifying a user's identity based on one or more authentication factors.
Source: eIDAS - 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.
Source reference: (http://eur-lex.europa.eu/legal-content/EN/TXT/?uri=uriserv%3AOJ.L_.2014.257.01.0073.01.ENG)
Synonym: Authentication Component
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): OpenIAM Identity Manager - The OpenIAM Identity Manager automates the task of managing identities across the various devices and applications used by the enterprise. This includes applications within the enterprise such as Active Directory and Exchange, and cloud based applications such as Google Apps. OpenIAM Identity Manager provides capabilities such as: • Provisioning, De-provisioning, Workflow; • Password Management, Password Policies, Synchronization; • Self-Service, allowing locked users to reset their accounts, manage their profiles, challenge response security questions; • Audit, Attestation, Reporting; • Delegated Administration.(http://www.openiam.com/products/identity-manager/idm-overview/)
Interoperability Dimension: Structural IoP
LOST view: Technical view - application
Viewpoint: Interoperability Security viewpoint
Interoperability Saliency: The Identification Component ABB is salient for technical interoperability because it provides the functionalities of user authentication.
Identifier: http://data.europa.eu/dr8/IdentificationApplicationComponent
ABB name: eira:IdentificationApplicationComponent
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/IdentificationApplicationComponent
Interoperability Layer: TechnicalApplication
Definition: Forms Management ABB is an Application Component that enables the implementation of i) dynamic creation, ii) distribution and ii) analysis of forms and online surveys.
Source: ISA2 - EIA Action
Source reference: https://joinup.ec.europa.eu/taxonomy/term/http_e_f_fdata_ceuropa_ceu_fdr8_fFormsManagementComponent
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): Form Tools - Form Tools is a forms framework written in PHP and MySQL. You download and install the script on your own website. At its heart, Form Tools is a web form creator, processor, data storage and access script. It was originally designed to work with any existing web form, but has since been expanded to create forms automatically as well. Form Tools is extremely versatile in how it integrates with your forms. You can use the bundled Form Builder module to create the forms automatically on your website (no programming or HTML skills necessary); you can use the PHP API to integrate your own custom form with the script; or you can simply POST your form to Form Tools, and just use it to store the form data. Anything goes! You can read about the different integration methods / form creation methods here. Form Tools works by creating custom database tables to store your unique form data. It provides a range of functionality customized to your data set, such as allowing you to view, update, cross-reference and export your submission data, create subsets of your data for viewing/editing by client accounts, data visualizations, and much more. https://formtools.org/
Interoperability Dimension: Structural IoP
LOST view: Technical view - application
Interoperability Saliency: The Forms Management Component ABB is salient for technical interoperability because it provides the implementation of the functionalities of dynamic creation, distribution and analysis of forms and online surveys as stated in the EIF: " Catalogues help others to find reusable resources (e.g. services, data, software, data models). Various types of catalogue exist, e.g. directories of services, libraries of software components, open data portals, registries of base registries, metadata catalogues, catalogues of standards, specifications and guidelines. Commonly agreed descriptions of the services, data, registries and interoperable solutions published in catalogues are needed to enable interoperability between catalogues."
Identifier: http://data.europa.eu/dr8/FormsManagementApplicationComponent
ABB name: eira:FormsManagementApplicationComponent
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/FormsManagementApplicationComponent
Interoperability Layer: TechnicalApplication
Definition: Interoperable Digital Solution ABB is an Application Component that enables the cooperation between public services, systems and data across organisational and national boundaries
Source: ISA2
Source reference: https://ec.europa.eu/isa2/eif_en/
Additional information: This ABB also corresponds to the delivery of a digital public service, in fulfilment of a shared European legislation framework, being managed according a shared governance framework, accessing semantic assets in a shared knowledge base and using digital resources of a shared platform enabling cross-border/cross-organization exchange of data, information, and knowledge indistinctly between public administrations, businesses and citizens in support to the implementation and advancement of an EU, national or local public policy.
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): eDelivery - Supporting secure and reliable exchange of data and documents - eDelivery is a network of nodes for digital communications. It is based on a distributed model where every participant becomes a node using standard transport protocols and security policies. eDelivery helps public administrations to exchange electronic data and documents with other public administrations, businesses and citizens, in an interoperable, secure, reliable and trusted way. eDelivery is one of the building blocks of the European Commission's Connecting Europe Facility (CEF). These building blocks are reusable specifications, software and services that will form part of a wide variety of IT systems in different policy domains of the EU. The CEF eDelivery building block is based on the AS4 messaging protocol, open and free for all, developed by the OASIS standards development organisation. To ease its adoption in Europe, eDelivery uses the AS4 implementation guidelines defined by the Member States in the e-SENS Large Scale Pilot. Organisations must install an Access Point, or use a Service Provider, to exchange information with the AS4 messaging protocol.(https://ec.europa.eu/cefdigital/wiki/display/CEFDIGITAL/eDelivery)
Interoperability Dimension: Structural IoP
LOST view: Technical view - application
Viewpoint: Interoperability Security viewpoint
Interoperability Saliency: The Interoperable Digital Solution Application Component ABB is salient for technical interoperability because it constitutes the digital public service interoperable with other digital public services, across organisations and national boundaries.
Identifier: http://data.europa.eu/dr8/InteroperableDigitalSolutionApplicationComponent
ABB name: eira:InteroperableDigitalSolutionApplicationComponent
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/InteroperableDigitalSolutionApplicationComponent
Interoperability Layer: TechnicalApplication
Definition: Digital Solution Component ABB is an Application Component that enables the encapsulation of a functionality provided by an Interoperable European Solution.
Source: Inspired in ArchiMate® v3
Source reference: http://pubs.opengroup.org/architecture/archimate3-doc/chap09.html
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): EU Login - EU Login is the European Commission's user authentication service. It allows authorised users to access a wide range of Commission web services and websites, using a single email address and password. EU Login implements the single sign-on functionality. https://webgate.ec.europa.eu/cas/help.html
Interoperability Dimension: Structural IoP
LOST view: Technical view - application
Viewpoint: Highlevel viewpoint
Interoperability Saliency: The Digital Solution Component ABB is salient for technical interoperability because it is a central element the EIF's conceptual model for integrated public services. it represents all the functionalities provided by an Interoperable European Solutionas as stated in the EIF: "Technical interoperability the applications and infrastructures linking systems and services."
Identifier: http://data.europa.eu/dr8/DigitalSolutionApplicationComponent
ABB name: eira:DigitalSolutionApplicationComponent
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/DigitalSolutionApplicationComponent
Interoperability Layer: TechnicalApplication
Description: The Once Only Technical System (OOTS) enables the sharing of information between public administrations across borders between EU countries. It is cross-sectorial and can be expanded beyond the current scope of life events set out in the Single Digital Gateway Regulation. It puts into practice the Once-Only Principle, which states that citizens should not be forced to provide information to authorities if another authority already holds that information in electronic format.
Publisher: European Commission
Source: https://ec.europa.eu/digital-building-blocks/wikis/display/DIGITAL/Once+Only+Technical+System
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/egovera/Once-OnlyTechnicalSystemApplicationService
LOST view: TVA-Data Exchange Enablers [Motivation]
EIRA concept: eira:SolutionBuildingBlock
Additional identifier: http://data.europa.eu/dr8/egovera/Once-OnlyTechnicalSystemApplicationService
Title: eDelivery
Realises: http://data.europa.eu/dr8/PublicAdministrationSingleWindowApplicationComponent
Definition: Data Integration ABB is an Application Component that implements the process of combining data from different sources or systems into a unified view, ensuring consistency, accuracy, and accessibility. It involves transforming and merging data from various formats, structures, and locations to provide a comprehensive and integrated data set.
Source: Wikipedia
Source reference: https://en.wikipedia.org/wiki/Data_integration
LOST view: Technical view - application
Identifier: http://data.europa.eu/dr8/egovera/DataIntegrationApplicationComponent
ABB name: egovera:DataIntegrationApplicationComponent
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/egovera/DataIntegrationApplicationComponent
Name: Data Integration Application Service
Interoperability Layer: TechnicalApplication
Specialises: http://data.europa.eu/dr8/DigitalSolutionApplicationComponent
Definition: Data Management ABB is an Application Component that enables the implementation of components to manage their data under the FAIR principles. The FAIR principles are a set of guidelines designed to ensure that scientific data and digital resources are Findable, Accessible, Interoperable, and Reusable.
Source: Inspired in the Data Act
Source reference: https://digital-strategy.ec.europa.eu/en/policies/data-act
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): Oracle Data Exchange - The Data Exchange Service provides several access points to the Event Repository, allowing the user to perform queries on these events: - The Query Subscription Administration Console configures the Data Exchange Service to create queries and periodically deliver query results to designated receivers (HTTP, JMS, and AS2). The Console can also test queries before subscribing, displaying user-readable events in XML format; - A SOAP Web service allows programmatic queries. This SOAP service is based on the technically complete, but not formally ratified as of October 2006, EPCglobal EPC Information Services (EPCIS) Version 1.0 Specification.EPCglobal EPCIS 1.0 Working Draft. https://docs.oracle.com/cd/E13197_01/rfid/enterprise_server/docs20/epcis/data-exchange.html
Interoperability Dimension: Structural IoP
LOST view: Technical view - application
Viewpoint: Interoperability Privacy viewpoint
Interoperability Saliency: The Data Management Component ABB is salient for technical interoperability because it provides and shares the functionality for the share of data: "Legislation requires that decisions and data are stored and can be accessed for a specified time. This means that records and information in electronic form held by public administrations for the purpose of documenting procedures and decisions must be preserved and be converted, where necessary, to new media when old media become obsolete. The goal is to ensure that records and other forms of information keep their legibility, reliability and integrity and can be accessed as long as needed subject to security and privacy provisions."
Identifier: http://data.europa.eu/dr8/DataManagementApplicationComponent
ABB name: eira:DataManagementApplicationComponent
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/DataManagementApplicationComponent
Interoperability Layer: TechnicalApplication
Definition: Machine Translation ABB is an Application Service that enables the implementation of an automated translation of text, metadata and concept classes or nomenclatures
Source: CEF Automated Translation
Source reference: https://ec.europa.eu/digital-single-market/en/news/tools-and-resources-cef-automated-translation
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): "CEF Digital - eTranslation building block: eTranslation is a Connecting Europe Facility (CEF) building block provided by the European Commission (EC). eTranslation provides a web-user interface for direct use by individuals (human-to-machine).(https://ec.europa.eu/cefdigital/wiki/display/CEFDIGITAL/eTranslation)
Interoperability Dimension: Structural IoP
LOST view: Technical view - application
Interoperability Saliency: The Machine Translation Component ABB is salient for technical interoperability because it provides the implementation of functionalities for cross-lingual functionality by providing automated translation of text, metadata and concept classes or nomenclatures as stated in the EIF recommendation n°16: "Use information systems and technical architectures that cater for multilingualism when establishing a European public service. Decide on the level of multilingualism support based on the needs of the expected users."
Identifier: http://data.europa.eu/dr8/MachineTranslationApplicationComponent
ABB name: eira:MachineTranslationApplicationComponent
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/MachineTranslationApplicationComponent
Interoperability Layer: TechnicalApplication
Definition: e-Archiving ABB is an Application Component that enables the implementation of components for the permanent or long-term storage of selected (by an authority) electronic documents or information for preservation purposes like their enduring research value and a memory aid.
Source: ISA2 - EIA Action
Source reference: https://ec.europa.eu/isa2/actions/towards-european-interoperability-architecture_en/
Synonym: Preservation Service
Additional information: 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 proof 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”.
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): CEF eArchiving - eArchiving provides the core specifications, software, training and knowledge to tackle the challenge of short, medium and long-term data management and reuse in a sustainable, authentic, cost-efficient, manageable and interoperable way.(https://ec.europa.eu/cefdigital/wiki/display/CEFDIGITAL/eArchiving)
Interoperability Dimension: Structural IoP
LOST view: Technical view - application
Viewpoint: Interoperability Privacy viewpoint
Interoperability Saliency: The e-Archiving Component ABB is salient for technical interoperability because it provides the implementation of the functionalities for the long-term or permanent preservation of records and information in electronic form in order to ensure their temporal egibility, reliability and integrity as stated in the EIF: "Legislation requires that decisions and data are stored and can be accessed for a specified time. This means that records and information in electronic form held by public administrations for the purpose of documenting procedures and decisions must be preserved and be converted, where necessary, to new media when old media become obsolete. The goal is to ensure that records and other forms of information keep their legibility, reliability and integrity and can be accessed as long as needed subject to security and privacy provisions."
Identifier: http://data.europa.eu/dr8/E-ArchivingApplicationComponent
ABB name: eira:E-ArchivingApplicationComponent
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/E-ArchivingApplicationComponent
Interoperability Layer: TechnicalApplication
Definition: Privacy ABB is an Application Component that enables the implementation of functionalities such as storing, securing, anonymising, pseudonymising, rectifying and erasing personal data.
Source: ePrivacy Regulation
Source reference: https://digital-strategy.ec.europa.eu/en/policies/eprivacy-regulation
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): SOLVIT - Solvit is a mailbox service for the access, rectification or deletion of personal data.(http://ec.europa.eu/solvit/privacy-statement/#maincontentSec8)
Interoperability Dimension: Structural IoP
LOST view: Technical view - application
Viewpoint: Interoperability Privacy viewpoint
Interoperability Saliency: The Privacy Component ABB is salient for interoperability because "security and privacy are primary concerns in the provision of public services" (EIF) and, as stated in EIF Recommendation 15: "Define a common security and privacy framework and establish processes for public services to ensure secure and trustworthy data exchange between public administrations and in interactions with citizens and businesses."
Identifier: http://data.europa.eu/dr8/PrivacyApplicationComponent
ABB name: eira:PrivacyApplicationComponent
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/PrivacyApplicationComponent
Interoperability Layer: TechnicalApplication
Definition: Audit ABB is an Application Component that enables the implementation of the procedural services for monitoring a building block, ensuring security or compliance with standards, regulations and best practices
Source: Inspired in SIMPL
Source reference: https://digital-strategy.ec.europa.eu/en/news/simpl-cloud-edge-federations-and-data-spaces-made-simple
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): Activiti audit feature - The audit feature of Activiti archives all process instances, activity instances, keeps variable values continuously in sync and all form properties that are submitted so that all user interaction through forms is traceable and can be audited. Authenticated users who submitted the forms are accessible in the history as well as for start forms and task forms. https://www.activiti.org/userguide/#historyFormAuditPurposes
Interoperability Dimension: Structural IoP
LOST view: Technical view - application
Viewpoint: Interoperability Security viewpoint
Interoperability Saliency: The Audit Component ABB is salient for technical interoperability because it allows the implementation of audit policies as stated in the EIF: "Public administrations should ensure that a 'data access and authorisation plan’ which determines who has access to what data and under what conditions, to ensure privacy. Unauthorised access and security breaches should be monitored and appropriate actions should be taken to prevent any recurrence of breaches"
Identifier: http://data.europa.eu/dr8/AuditApplicationComponent
ABB name: eira:AuditApplicationComponent
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/AuditApplicationComponent
Interoperability Layer: TechnicalApplication
Definition: API Catalogue ABB is an Application Component that refers to the (open) software interfaces functionalities that are aligned with the implementation structure of the digital services.
Source: Inspired in Archimate©
Source reference: https://pubs.opengroup.org/architecture/archimate3-doc/chap09.html#_Toc10045392
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): RapidAPI - RapidAPI is a collection of predefined APIs that are free to test, specifically updated for 2021. https://rapidapi.com/collection/list-of-free-apis
Interoperability Dimension: Structural IoP
LOST view: Technical view - application
Interoperability Saliency: The API Catalogue Catalogue Application Component ABB is salient for interoperability because the component is relevant for the software interfaces functionalities aligned with the implementation structures of solutions and digital public services. Those features and functionalities enable data consumption, processing and provision between digital public services.
Identifier: http://data.europa.eu/dr8/APICatalogueApplicationComponent
ABB name: eira:APICatalogueApplicationComponent
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/APICatalogueApplicationComponent
Interoperability Layer: TechnicalApplication
Definition: Orchestration ABB is an Application component that enables the coordination and management of the execution of multiple components or services within an application or system.
Source: W3C
Source reference: https://www.w3.org/TR/ws-arch/
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): Activiti - Activiti is an open-source workflow engine written in Java that can execute business processes described in BPMN 2.0. Activiti supports open standards such as BPMN and DMN with open REST APIs for demanding human- and system-centric processes. It provides business intelligence and audit logs features for free. And with building the solution on business processes, Activiti help to structure the software, think about user tasks, external systems and timers that need to be managed, think about transaction boundaries of the application. Building that kind of features becomes easier when structuring an application around a business process. Managing wait states, timers and asynchronous continuations becomes easier. A business process can express that structure more compact than working with the fundamental instruments that the Java platform offers like JDBC and JMS. Activiti also makes possible to link in Java or scripting for jobs. https://www.activiti.org/
Interoperability Dimension: Structural IoP
LOST view: Technical view - application
Interoperability Saliency: The Orchestration Component ABB is salient for technical interoperability because it provides a set of various methods to manage existing business processes or define and establish new ones. BPM components also execute business process documented through accepted modelling techniques, as recommended by the EIF n.28: "Document your business processes using commonly accepted modelling techniques and agree on how these processes should be aligned to deliver a European public service."
Identifier: http://data.europa.eu/dr8/OrchestrationApplicationComponent
ABB name: eira:OrchestrationApplicationComponent
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/OrchestrationApplicationComponent
Interoperability Layer: TechnicalApplication
Definition: Service Registry ABB is an Application Component that enables the registering of system services within a catalogue to facilitate the discovery of services.
Source: ISA2 - EIA Action
Source reference: http://data.europa.eu/eli/dec/2015/2240/oj
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): jUDDI - jUDDI is an open source Java implementation of OASIS Universal Description, Discovery, and Integration (UDDI) specification for (Web) Services. https://juddi.apache.org/
Interoperability Dimension: Structural IoP
LOST view: Technical view - application
Interoperability Saliency: The Service Registry Component ABB is a key interoperability enabler because it supports to achieve technical interoperability by provisioning and consuming back-office services as stated in the EIF recommendation n°44: "Put in place catalogues of public services, public data, and interoperability solutions and use common models for describing them."
Identifier: http://data.europa.eu/dr8/ServiceRegistryApplicationComponent
ABB name: eira:ServiceRegistryApplicationComponent
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/ServiceRegistryApplicationComponent
Interoperability Layer: TechnicalApplication
Definition: Public Administration Single Window Component ABB is an Application Component that enables the implementation of the procedures to submit information and documents with a single entry point to fulfil all regulatory requirements.
Source: United Nations
Source reference: https://tfig.unece.org/contents/single-window-concept.htm
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): Mi Carpeta Ciudadana Carpeta Ciudadana is a personal online space that facilitates your relationship with public administrations. https://carpetaciudadana.gob.es/carpeta/clave.htm
Interoperability Dimension: Behavioral IoP
LOST view: Technical view - application
Interoperability Saliency: The Public Administration Single Window Application Component ABB is salient for technical interoperability because it implements the platform that realises the service, meaning that includes the tool for administrations and stakeholders (citizens and businesses) to share documentation, information or relevant data. As the platform and services must be compliant with all regulatory aspects depending on the domain of the public service, it can enable interoperability between other public services by allowing regulation compliance of the data provided.
Identifier: http://data.europa.eu/dr8/PublicAdministrationSingleWindowApplicationComponent
ABB name: eira:PublicAdministrationSingleWindowApplicationComponent
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/PublicAdministrationSingleWindowApplicationComponent
Interoperability Layer: TechnicalApplication
Definition: Blockchain ABB is an Application Component that implements a set of rules and processes to enable secure and transparent transactions and record-keeping for sharing of information, enabling permanent, immutable, and transparent recording of data and transactions.
Source: Inspired in European Blockchain Strategy
Source reference: https://digital-strategy.ec.europa.eu/en/library/european-blockchain-strategy-brochure
Additional information: In the creation of the Blockchain component, several actors such as developer, user, architect, regulator, operator, membership services, etc. are present in a blockchain that provides a solution to a blockchain-based business network. Each actor and component present in a blockchain plays a major role to make the network more secure and reliable.
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): Fishcoin Project, is a project using Blockchain technologies for seafood traceability. https://fishcoin.co/
Interoperability Dimension: Structural IoP
LOST view: Technical view - application
Interoperability Saliency: The Blockchain Application Component ABB is salient for interoperability because it implements a set of elements needed and used by blockchain services. Those aspects are peer network, smart contracts, membership, events, ledger, system integration, wallet, and system management. All listed components can be part of a digital public service enhancing trustability and enabling interoperability in a secure and reliable way.
Identifier: http://data.europa.eu/dr8/BlockchainApplicationComponent
ABB name: eira:BlockchainApplicationComponent
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/BlockchainApplicationComponent
Interoperability Layer: TechnicalApplication
Definition: Digital Workplace ABB is an Application Component that enables the implementation of the procedures to freely collaborate independently from the location and boundaries while maintaining high-security standards and increasing productivity and efficiency.
Source: European Comission
Source reference: https://ec.europa.eu/info/publications/digital-workplace-strategy_en
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): Set of IT tools used by European Commission officials, workers, etc. There is a new strategy put in place by the Commission to improve the work of the different roles involved. https://europa.eu/digitec/news/digital-workplace-european-commission/
Interoperability Dimension: Behavioral IoP
LOST view: Technical view - application
Interoperability Saliency: The Digital Workplace Application Component ABB is salient for technical interoperability because it provides the components and tools that allow the free collaboration of staffing people while maintaining high-security standards.
Identifier: http://data.europa.eu/dr8/DigitalWorkplaceApplicationComponent
ABB name: eira:DigitalWorkplaceApplicationComponent
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/DigitalWorkplaceApplicationComponent
Interoperability Layer: TechnicalApplication
Definition: Data Exchange ABB is an Application Component that enables the implementation of the procedure to transfer data between different individuals, organizations or systems.
Source: EIFv2
Source reference: http://ec.europa.eu/isa/documents/isa_annex_ii_eif_en.pdf
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): Open e-TrustEx - Open e-TrustEx is a secure document exchange platform. Solution for European public administration that needs to electronically exchange information with other entities in a secure way. Open e-TrustEx is a cross-sector, open source tool that helps administrations to exchange structured and unstructured documents and to connect to pan-European e-delivery infrastructures with reduced investment. For Commission services, DG Informatics operates the e-TrustEx platform for a fee.(https://ec.europa.eu/isa2/solutions/open-e-trustex_en)
Interoperability Dimension: Behavioral IoP
LOST view: Technical view - application
Viewpoint: Interoperability Security viewpoint
Interoperability Saliency: The Data Exchange Component ABB is salient for technical interoperability because it provides the implementation of the functionalities to enable a secure and trustworthy data exchange between different ICT systems as stated in the EIF: "Define a common security and privacy framework and establish processes for public services to ensure secure and trustworthy data exchange between public administrations and in interactions with citizens and businesses."
Identifier: http://data.europa.eu/dr8/DataExchangeApplicationComponent
ABB name: eira:DataExchangeApplicationComponent
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/DataExchangeApplicationComponent
Interoperability Layer: TechnicalApplication
Definition: The eNotification Application service refers to a software application or component that enables the electronic delivery of notifications, alerts, and messages to individuals or organizations. It operates at the application layer in a software architecture, providing the necessary functionality to create, manage, and distribute notifications through various channels
Source: International Journal of Engineering Research & Technology
Source reference: https://www.ijert.org/research/managing-user-notifications-in-enterprise-applications-IJERTV7IS010324.pdf
LOST view: TVA-API Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/ENotificationApplicationInterface
ABB name: egovera:ENotificationApplicationInterface
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/egovera/ENotificationApplicationInterface
Interoperability Layer: TechnicalApplication
Description: ILIADe is a database of the analytical methods initially developed as a shared directory by the Italian Customs Agency and currently hosted by the European Commission. Its main purpose is to improve the effectiveness of customs laboratories by providing them with an easily accessible and up-to-date compilation of analytical methods, they are required to use for customs and excise purposes, as well as for authenticity and quality controls, consumer health protection and environmental controls. The database contains official analytical methods, international standards and in-house developed methods. The methods and contacts are also available to third countries upon special request.
Publisher: European Commission
Source: https://ec.europa.eu/taxation_customs/dds2/ecics/analyticalmethod_consultation.jsp
LOST view: TVA-Customs API Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/ILIADe-InterLaboratoryInventoryOfAnalyticalDeterminationApplicationInterface
EIRA traceability: eira:WebServiceApplicationInterface
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-08-21
dct:identifier: http://data.europa.eu/dr8/egovera/ILIADe-InterLaboratoryInventoryOfAnalyticalDeterminationApplicationInterface
Description: EBTI - European Binding Tariff Information offers economic operators a legally binding decision on the classification of goods for customs purposes. By submitting a request with detailed information about the goods, importers and exporters can receive a ruling on the correct tariff classification from the customs authorities. This information is essential for determining the appropriate customs duties, taxes, and regulations applicable to specific goods. The EBTI service enhances trade predictability and facilitates compliance by providing certainty on the customs classification of goods, promoting efficient customs procedures and trade facilitation within the EU.
Publisher: European Commission
Source: https://ec.europa.eu/taxation_customs/dds2/ebti/ebti_home.jsp?Lang=en
LOST view: TVA-Customs API Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/EBTI-EuropeanBindingTariffInformationApplicationInterface
EIRA traceability: eira:WebServiceApplicationInterface
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-08-21
dct:identifier: http://data.europa.eu/dr8/egovera/EBTI-EuropeanBindingTariffInformationApplicationInterface
Description: CLASS – Classification Information System is a comprehensive system designed to manage and facilitate the classification of goods for customs purposes. The system stores and organizes detailed information about various products and their corresponding customs codes, enabling accurate and consistent classification during import and export processes. CLASS helps customs authorities, businesses, and traders to determine the appropriate customs tariffs, duties, and other regulatory requirements for specific goods. By centralizing and standardizing classification information, CLASS streamlines customs procedures, enhances trade facilitation, and ensures compliance with customs regulations across the European Union.
Publisher: European Commission
Source: https://taxation-customs.ec.europa.eu/online-services/online-services-and-databases-customs/class-classification-information-system_en
LOST view: TVA-Customs API Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/CLASS–ClassificationInformationSystemApplicationInterface
EIRA traceability: eira:WebServiceApplicationInterface
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-08-21
dct:identifier: http://data.europa.eu/dr8/egovera/CLASS–ClassificationInformationSystemApplicationInterface
Definition: The ePayment Application service refers to a digital payment solution that enables secure and convenient electronic transactions between buyers and sellers. It encompasses the electronic processing of financial transactions, such as online purchases, bill payments, and fund transfers, using digital payment methods and platforms.
Source: International Journal of Computer Science and Network Security (IJCSNS)
Source reference: https://ijcsns.org/
LOST view: TVA-API Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/EPaymentApplicationInterface
ABB name: egovera:EPaymentApplicationInterface
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/egovera/EPaymentApplicationInterface
Interoperability Layer: TechnicalApplication
Specialises: http://data.europa.eu/dr8/WebServiceApplicationInterface
Description: EORI - Economic Operators Registration and Identification number provides access to the information related to the Economic Operator Identification and Registration system (EORI) as established by Council Regulation (EEC) No 2913/92 of 12 October 1992, establishing the Community Customs Code, last amended by Regulation (EC) No 648/2005 of European Parliament and of the Council of 13 April 2005.
Publisher: European Commission
Source: https://ec.europa.eu/taxation_customs/dds2/eos/eori_home.jsp?Lang=en
LOST view: TVA-Customs API Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/EORI-EconomicOperatorsRegistrationAndIdentificationNumberApplicationInterface
EIRA traceability: eira:WebServiceApplicationInterface
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-08-21
dct:identifier: http://data.europa.eu/dr8/egovera/EORI-EconomicOperatorsRegistrationAndIdentificationNumberApplicationInterface
Definition: The Supply Chain Management Application Service refers to a digital service that facilitates the planning, coordination, and optimization of activities involved in the end-to-end management of the supply chain. It encompasses the integration of various functions, including procurement, production, inventory management, logistics, and distribution, to ensure efficient and effective movement of goods or services from suppliers to customers. The application service provides functionalities such as demand forecasting, inventory tracking, order management, supplier collaboration, logistics optimization, and performance analytics. It aims to enhance visibility, transparency, and collaboration across the supply chain, enabling organizations to streamline operations, reduce costs, and improve customer satisfaction.
Source: European Supply Chain Institute (ESCI)
LOST view: TVA-Functional Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/SupplyChainManagementApplicationInterface
ABB name: egovera:SupplyChainManagementApplicationInterface
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/egovera/SupplyChainManagementApplicationInterface
Interoperability Layer: TechnicalApplication
Specialises: http://data.europa.eu/dr8/WebServiceApplicationInterface
Description: A digital solution provided by the Tax and Customs Union (TCU) of the European Union. The open interface allows external systems and stakeholders to validate the authenticity and correctness of EORI numbers in real-time. This service ensures that customs declarations, trade documents, and other transactions involving economic operators are accurate and legitimate. By offering this open interface, the TCU aims to promote secure and efficient cross-border trade by enabling seamless data validation and verification, enhancing customs control, and facilitating smooth interactions between economic operators and customs authorities.
Publisher: European Commission
Source: https://ec.europa.eu/taxation_customs/dds2/eos/news/newstar.jsp?Lang=en
LOST view: TVA-Customs API Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/EORI-ValidationOpenInterfaceApplicationInterface
EIRA traceability: eira:WebServiceApplicationInterface
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-08-21
dct:identifier: http://data.europa.eu/dr8/egovera/EORI-ValidationOpenInterfaceApplicationInterface
Description: The EU Customs Trader Portal provides a single access point to the online systems for “Authorised Economic Operators” (AEO), the “European Binding Tariff Information” (EBTI), the Information Sheet on Special Procedures (INF) , and Registered Exporter system (REX). As the aim of this portal is to harmonise the accesses to the different EU customs systems, it is expected that in a near future all other EU customs systems will be connected to this portal.
Publisher: European Commission
Source: https://taxation-customs.ec.europa.eu/online-services/online-services-and-databases-customs/eu-customs-trader-portal_en
LOST view: TVA-Customs API Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/EUCustomsTraderPortalSystemApplicationInterface
EIRA traceability: eira:WebServiceApplicationInterface
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-08-21
dct:identifier: http://data.europa.eu/dr8/egovera/EUCustomsTraderPortalSystemApplicationInterface
Definition: The eProfessional Qualification web service is a specialized application service that enables the management, verification, and processing of professional qualification-related information and services over the internet. It provides a standardized and secure interface for accessing and exchanging data related to professional qualifications, such as certifications, licenses, skills, and credentials. The eProfessional Qualification web service facilitates tasks such as qualification verification, applicant registration and assessment, qualification tracking, and reporting. It allows authorized stakeholders, including individuals, organizations, and regulatory bodies, to interact with the system and access accurate and up-to-date information regarding professional qualifications. The web service follows industry standards, protocols, and security measures to ensure the integrity, privacy, and reliability of the qualification data exchange.
Source: European Qualifications Framework (EQF)
Source reference: https://ec.europa.eu/ploteus/en/content/european-qualifications-framework-eqf
LOST view: TVA-API Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/EProfessionalQualificationApplicationInterface
ABB name: egovera:EProfessionalQualificationApplicationInterface
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/egovera/EProfessionalQualificationApplicationInterface
Interoperability Layer: TechnicalApplication
Specialises: http://data.europa.eu/dr8/WebServiceApplicationInterface
Definition: A Log Management Application Service refers to a web-based service that facilitates the collection, storage, analysis, and monitoring of log data generated by web applications, servers, and other web-based systems. It provides a centralized platform accessible via the web, allowing users to aggregate, search, and visualize log data for troubleshooting, performance monitoring, and security analysis purposes. The service typically includes features such as log ingestion, parsing, indexing, and customizable dashboards, providing users with insights into their web-based systems' operational status, identifying errors, anomalies, and potential security threats.
Source: The Open Web Application Security Project (OWASP)
Source reference: https://owasp.org/www-project-web-security-testing-guide/latest/4-Web_Application_Security_Testing/10-Logging_Testing/02-Log_Management_Best_Practices
LOST view: TVA-API Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/LogManagementApplicationInterface
ABB name: egovera:LogManagementApplicationInterface
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/egovera/LogManagementApplicationInterface
Interoperability Layer: TechnicalApplication
Specialises: http://data.europa.eu/dr8/WebServiceApplicationInterface
Description: ECICS the European Customs Inventory of Chemical Substances is an information tool managed by the European Commission's Directorate General (DG) for Taxation and Customs Union which allows users to: 1. Clearly and easily identify chemicals; 2. Classify them correctly and easily in the Combined Nomenclature; 3. Name them in all EU languages for regulation purposes.
Publisher: European Commission
Source: https://taxation-customs.ec.europa.eu/online-services/online-services-and-databases-customs/ecics-european-customs-inventory-chemical-substances_en
LOST view: TVA-Customs API Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/ECICS-EuropeanCustomsInventoryOfChemicalSubstancesApplicationInterface
EIRA traceability: eira:WebServiceApplicationInterface
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-08-21
dct:identifier: http://data.europa.eu/dr8/egovera/ECICS-EuropeanCustomsInventoryOfChemicalSubstancesApplicationInterface
Definition: The eQualification Application Service refers to a digital service that enables the management and processing of qualifications and certifications in an electronic format. It facilitates the creation, verification, storage, and sharing of qualifications and related documentation electronically. The service provides a secure and efficient platform for individuals, educational institutions, employers, and certification bodies to manage qualifications, track progress, and validate credentials. It may include features such as online qualification submission, document verification, real-time qualification status updates, and integration with educational databases and certification authorities.
Source: European Commission
Source reference: https://ec.europa.eu/education/sites/education/files/2014-11-25-equal-recognition-foreign-qualifications_en.pdf
LOST view: TVA-API Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/EQualificationApplicationInterface
ABB name: egovera:EQualificationApplicationInterface
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/egovera/EQualificationApplicationInterface
Interoperability Layer: TechnicalApplication
Specialises: http://data.europa.eu/dr8/WebServiceApplicationInterface
Definition: eProcurement as a web service is a method of communication and data exchange between different software applications or systems involved in the eProcurement process. It enables interoperability and integration between various eProcurement platforms, systems, or other software solutions. By using standard web protocols, such as HTTP, it allows different components of an eProcurement ecosystem to interact and share information seamlessly. This facilitates efficient and streamlined procurement processes, enabling organizations to connect and exchange data with suppliers, manage procurement workflows, and optimize their procurement activities.
Source: European Commission
Source reference: https://single-market-economy.ec.europa.eu/single-market/public-procurement/digital-procurement_en
LOST view: TVA-Functional Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/EProcurementApplicationInterface
ABB name: egovera:EProcurementApplicationInterface
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/egovera/EProcurementApplicationInterface
Interoperability Layer: TechnicalApplication
Specialises: http://data.europa.eu/dr8/WebServiceApplicationInterface
Publisher: European Commission
Source: https://taxation-customs.ec.europa.eu/customs-4/prohibitions-and-restrictions/counterfeit-piracy-and-other-ipr-violations/defend-your-rights_en
LOST view: TVA-Customs API Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/COPISApplicationInterface
EIRA traceability: eira:WebServiceApplicationInterface
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-08-21
dct:identifier: http://data.europa.eu/dr8/egovera/COPISApplicationInterface
Description: The Surveillance system is used, in line with Article 55 of Implementing Regulation (EU) 2015/2447 (UCC IA), for monitoring purposed. The Member States customs authorities have the legal obligation to apply customs legislation in a correct and uniform manner in order to, amongst others, protect the financial interests of the Union and its Member States and protect the Union from unfair and illegal trade. To monitor transactions and ensure the correct and uniform implementation of the Union Tariff, Surveillance on goods released for free circulation and export was introduced.
Publisher: European Commission
Source: https://ec.europa.eu/taxation_customs/dds2/surv/surv_consultation.jsp?Lang=en
LOST view: TVA-Customs API Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/SurveillanceSystemApplicationInterface
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-08-21
dct:identifier: http://data.europa.eu/dr8/egovera/SurveillanceSystemApplicationInterface
Definition: Human Interface ABB is an Application Interface that enables the exchange of data between stakeholders (individuals, public administration or legal entities) and a service. This ABB is a key interoperability enabler (*) for assessing compatible interfaces.
Source: EIA Action
Source reference: https://ec.europa.eu/isa2/eif_en
Synonym: User interface, UI, Graphical User Interface, GUI
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): GrapesJS - GrapesJS is an open-source, multi-purpose, Web Builder Framework which combines different tools and features with the goal to help you (or users of your application) to build HTML templates without any knowledge of coding. It's a perfect solution to replace the common WYSIWYG editors, which are good for content editing but inappropriate for creating HTML structures. You can see it in action with the official demos, but using its API you're able to build your own editors. https://grapesjs.com/
Interoperability Dimension: Behavioral IoP
LOST view: Technical view - application
Viewpoint: Interoperability Security viewpoint
Interoperability Saliency: The Human Interface ABB is a key interoperability enabler because it supports to achieve technical behavioral interoperability by enabling the exchange of data, information, and knowledge between digital public services and individuals.
Identifier: http://data.europa.eu/dr8/HumanInterfaceApplicationInterface
ABB name: eira:HumanInterfaceApplicationInterface
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/HumanInterfaceApplicationInterface
Interoperability Layer: TechnicalApplication
Definition: eTendering refers to the capability of providing access to specific functionalities related to tendering processes through web-based APIs (Application Programming Interfaces). This allows external systems or applications to interact with the eTendering platform to perform tasks such as retrieving tendering information, submitting bids, or querying tender results.
Source: Publications Office of the European Union
Source reference: https://ted.europa.eu/TED/main/HomePage.do
LOST view: TVA-API Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/ETenderingApplicationInterface
ABB name: egovera:ETenderingApplicationInterface
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/egovera/ETenderingApplicationInterface
Interoperability Layer: TechnicalApplication
Specialises: http://data.europa.eu/dr8/WebServiceApplicationInterface
Description: AEO - Authorised Economic Operator provides access to the information related to Authorised Economic Operators (AEO) as established by the Regulation (EU) No 952/2013 of the European Parliament and of the Council of 9 October 2013 laying down the Union Customs Code.
Publisher: European Commission
Source: https://taxation-customs.ec.europa.eu/online-services/online-services-and-databases-customs_en#:~:text=AEO%20%2D%20Authorised%20Economic%20Operator
LOST view: TVA-Customs API Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/AEO-AuthorisedEconomicOperatorApplicationInterface
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-08-21
dct:identifier: http://data.europa.eu/dr8/egovera/AEO-AuthorisedEconomicOperatorApplicationInterface
Description: The Movement Reference Number (MRN) is a unique identifier assigned to customs declarations when goods are moved between different customs offices or territories within the EU. The MRN follow-up system allows customs authorities and stakeholders to track the movement and status of goods in real-time. It provides visibility and transparency throughout the entire customs clearance process, allowing for efficient monitoring, risk assessment, and coordination between customs offices and economic operators. By leveraging the MRN follow-up system, the TCU aims to streamline customs operations, enhance trade facilitation, and ensure the secure and timely movement of goods across borders within the European Union.
Publisher: European Commission
Source: https://ec.europa.eu/taxation_customs/dds2/ecs/ecs_home.jsp?Lang=en
LOST view: TVA-Customs API Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/MRNFollow-up–MovementReferenceNumberApplicationInterface
EIRA traceability: eira:WebServiceApplicationInterface
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-08-21
dct:identifier: http://data.europa.eu/dr8/egovera/MRNFollow-up–MovementReferenceNumberApplicationInterface
Definition: The Financial Management Application Service refers to a software service that facilitates the management and processing of financial operations and transactions within an organization. It encompasses a range of functionalities, including budgeting, accounting, financial planning, reporting, invoicing, and payment processing. The service streamlines financial processes, ensures accurate recording and tracking of financial data, and provides insights into the organization's financial performance. It may integrate with other systems such as Enterprise Resource Planning (ERP) systems, banking platforms, and payment gateways to enable seamless financial operations
Source: International Journal of Public Administration and Management Research (IJPAMR)
Source reference: https://www.researchgate.net/publication/331892729_The_Role_of_Financial_Management_Information_Systems_in_the_Public_Sector
LOST view: TVA-Functional Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/FinancialManagementApplicationInterface
ABB name: egovera:FinancialManagementApplicationInterface
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/egovera/FinancialManagementApplicationInterface
Interoperability Layer: TechnicalApplication
Specialises: http://data.europa.eu/dr8/WebServiceApplicationInterface
Definition: An Application Interface in an ERP system refers to the set of protocols, methods, and tools that enable communication and interaction between the ERP system and other applications or systems. It allows data and functionalities to be exchanged between the ERP system and external systems, such as CRM (Customer Relationship Management) systems, HR (Human Resources) systems, supply chain management systems, or third-party applications. The Application Interface facilitates seamless integration, data synchronization, and workflow coordination, enabling efficient information flow and process automation across the organization's ecosystem of systems.
Source: Oracle
Source reference: https://www.oracle.com/erp/what-is-erp-integration/
LOST view: TVA-Functional Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/ERPSystemApplicationInterface
ABB name: egovera:ERPSystemApplicationInterface
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/egovera/ERPSystemApplicationInterface
Interoperability Layer: TechnicalApplication
Specialises: http://data.europa.eu/dr8/WebServiceApplicationInterface
Description: The EUROPA webserver provides the data as received from the different IT environments of the different countries. The data provided is for information only and is binding neither for the Commission nor for the National Administrations concerned. For specific enquiries and information regarding the contents, please contact the Customs Administration of the appropriate country.
Publisher: European Commission
Source: https://ec.europa.eu/taxation_customs/dds2/tra/transit_home.jsp?Lang=en
LOST view: TVA-Customs API Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/TRANSIT–TrackingGoodsInTransitApplicationInterface
EIRA traceability: eira:WebServiceApplicationInterface
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-08-21
dct:identifier: http://data.europa.eu/dr8/egovera/TRANSIT–TrackingGoodsInTransitApplicationInterface
Definition: Web Service ABB is an Application Interface that enables interoperability between different applications or systems over the Internet
Source: W3C
Source reference: https://www.w3.org/TR/2004/NOTE-ws-arch-20040211/#relwwwrest
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): Web Services Description Language (WSDL) - WSDL is an XML format for describing network services as a set of endpoints operating on messages containing either document-oriented or procedure-oriented information. The operations and messages are described abstractly, and then bound to a concrete network protocol and message format to define an endpoint. https://www.w3.org/TR/wsdl.html
Interoperability Dimension: Behavioral IoP
LOST view: Technical view - application
Interoperability Saliency: The Web Service Application Interface ABB is salient for interoperability because, from the beginning, Web services can be interoperable by design. By putting in place web services, interoperability can be guaranteed between systems and applications, and therefore, among digital public services.
Identifier: http://data.europa.eu/dr8/WebServiceApplicationInterface
ABB name: eira:WebServiceApplicationInterface
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/WebServiceApplicationInterface
Interoperability Layer: TechnicalApplication
Description: TARIC - EU Customs Tariff is an extensive database that contains detailed information on the customs tariffs and regulations applicable to various goods imported into or exported from the EU. The TARIC system classifies goods using a combination of the Harmonized System (HS) codes and additional EU-specific codes. Economic operators can use TARIC to determine the customs duties, taxes, and other regulatory measures that apply to specific products when trading with EU member states. The TARIC database is regularly updated to reflect changes in customs regulations, ensuring accurate and up-to-date information for customs declarations and trade facilitation within the European Union.
Publisher: European Commission
Source: https://ec.europa.eu/taxation_customs/dds2/taric/taric_consultation.jsp?Lang=en
LOST view: TVA-Customs API Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/TARIC-EUCustomsTariffApplicationInterface
EIRA traceability: eira:WebServiceApplicationInterface
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-08-21
dct:identifier: http://data.europa.eu/dr8/egovera/TARIC-EUCustomsTariffApplicationInterface
Definition: The eInvoicing application service refers to a digital service that enables the electronic creation, exchange, and processing of invoices between businesses or organizations. It leverages web-based technologies and standards to facilitate the seamless and secure transmission of invoices over the internet. The service provides functionalities such as invoice generation, digital signature, data validation, encryption, and integration with existing accounting or enterprise systems. It aims to streamline the invoicing process, reduce manual effort, enhance accuracy, and enable faster payment cycles.
Source: European Commission
Source reference: https://ec.europa.eu/cefdigital/wiki/display/CEFDIGITAL/eInvoicing
LOST view: TVA-API Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/EInvoicingApplicationInterface
ABB name: egovera:EInvoicingApplicationInterface
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/egovera/EInvoicingApplicationInterface
Interoperability Layer: TechnicalApplication
Definition: API ABB is an Application Interface that enables a set of rules and specifications that allow different software components or systems to communicate and exchange data
Source: EPDB
Source reference: http://api.epdb.eu/#:~:text=The%20API%20can%20help%20you%20conduct%20research%2C%20create,access%20to%20meta%20data%20on%20European%20Union%20legislation.
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): RapidAPI - RapidAPI is a collection of predefined APIs that are free to test, specifically updated for 2021. https://rapidapi.com/collection/list-of-free-apis
Interoperability Dimension: Behavioral IoP
LOST view: Technical view - application
Viewpoint: Key Interoperability Enablers viewpoint
Interoperability Saliency: API Application Interface ABB is a key interoperability enabler (*) for behavioural interoperability by enabling rules and specifications for data exchange between systems and digital public services components.
Identifier: http://data.europa.eu/dr8/APIApplicationInterface
ABB name: eira:APIApplicationInterface
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/APIApplicationInterface
Interoperability Layer: TechnicalApplication
Definition: The Geo-localization Application Service is a web service that provides functionality for determining and retrieving the geographic location of a device, user, or point of interest using various data sources and techniques. It enables applications to integrate location-based features and services, such as mapping, routing, proximity search, and geofencing, into their functionality. The Geo-localization Application Service utilizes a combination of technologies, including GPS, IP geolocation, Wi-Fi positioning, cellular network data, and geospatial algorithms, to accurately determine and track the location information. It offers a standardized and accessible interface for developers to query and utilize location data in their applications, allowing for enhanced user experiences, targeted services, and location-aware functionality
Source: European Location Framework (ELF)
Source reference: https://www.elfproject.eu/
LOST view: TVA-Functional Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/Geo-LocalizationApplicationInterface
ABB name: egovera:Geo-LocalizationApplicationInterface
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/egovera/Geo-LocalizationApplicationInterface
Interoperability Layer: TechnicalApplication
Specialises: http://data.europa.eu/dr8/WebServiceApplicationInterface
Description: The CDS is based on an IT architecture with both national and EU common components. 1. The central CDS is to be used for all applications and decisions which may have an impact in more than one Member State, and for any subsequent event which may affect the original application or decision (annulment, suspension, revocation or amendment); 2. Some Member States will use the CDS also to manage their national customs decisions (i.e. which have only a national impact), whilst other Member States will deploy their national CDS.
Publisher: European Commission
Source: https://taxation-customs.ec.europa.eu/online-services/online-services-and-databases-customs/cds-customs-decisions-system_en
LOST view: TVA-Customs API Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/CDS-CustomsDecisionsSystemApplicationInterface
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-08-21
dct:identifier: http://data.europa.eu/dr8/egovera/CDS-CustomsDecisionsSystemApplicationInterface
Definition: Machine to Machine Interface ABB is an Application Interface that enables the exchange of data between a service and other services. This ABB is a key interoperability enabler (*) for assessing compatible interfaces.
Source: EIA Action (*)DECISION (EU) 2015/2240 OF THE EUROPEAN PARLIAMENT AND OF THE COUNCIL of 25 November 2015 establishing a programme on interoperability solutions and common frameworks for European public administrations, businesses and citizens (ISA2 programme) as a means for modernising the public sector.
Source reference: https://ec.europa.eu/isa2/eif_en
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): XMLGate TRACES Businesses (XTB) - Webservices enabling the management of organisations and cities registered in TRACES. https://circabc.europa.eu/sd/a/dc77e52b-dfba-4dcc-aa39-6a54748db01d/XmlGate%20TRACES%20Businesses%20Manual.doc.
Interoperability Dimension: Behavioral IoP
LOST view: Technical view - application
Viewpoint: Interoperability Security viewpoint
Interoperability Saliency: The Machine to Machine Interface ABB is a key interoperability enabler because it supports to achieve technical behavioral interoperability by enabling the exchange of data, information, and knowledge between digital public services as stated in the EIF recommendation n°5: ""Ensure internal visibility and provide external interfaces for European public services" and recommendation n°9:"Ensure data portability, namely that data is easily transferable between systems and applications supporting the implementation and evolution of European public services without unjustified restrictions, if legally possible."
Identifier: http://data.europa.eu/dr8/MachineToMachineInterfaceApplicationInterface
ABB name: eira:MachineToMachineInterfaceApplicationInterface
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/MachineToMachineInterfaceApplicationInterface
Interoperability Layer: TechnicalApplication
Publisher: European Commission
Source: https://ec.europa.eu/taxation_customs/dds2/SAMANCTA/
LOST view: TVA-Customs API Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/SAMANCTA-SamplingManualForCustomsTaxationAuthoritiesApplicationInterface
EIRA traceability: eira:WebServiceApplicationInterface
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-08-21
dct:identifier: http://data.europa.eu/dr8/egovera/SAMANCTA-SamplingManualForCustomsTaxationAuthoritiesApplicationInterface
Definition: Schedule Management Service ABB is an Application Service that enables the procedures to manage time and events in the achievement of the goals and delivery of public services.
Source: Inspired in Public Works and Goverment Services Canada
Source reference: https://buyandsell.gc.ca/cds/public/2016/11/23/c7b27e0ac41ad50ffae2f12b0a837875/ABES.PROD.PW_PWZ.B014.E10051.ATTA001.PDF
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): Chronos is a replacement for cron. It is a distributed and fault-tolerant scheduler that runs on top of Apache Mesos that can be used for job orchestration. It supports custom Mesos executors as well as the default command executor. Thus by default, Chronos executes sh (on most systems bash) scripts. https://sourceforge.net/projects/chronos.mirror/
Interoperability Dimension: Structural IoP
LOST view: Technical view - application
Interoperability Saliency: The Schedule Management Application Service ABB is salient for technical interoperability because it allows managing and orchestrating different events physical and digital ones within a determined workflow according to the delivery model of each digital public service.
Identifier: http://data.europa.eu/dr8/ScheduleManagementApplicationService
ABB name: eira:ScheduleManagementApplicationService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/ScheduleManagementApplicationService
Interoperability Layer: TechnicalApplication
Definition: Authorisation ABB is an Application Service that enables processes to formalise the electronic identification of a natural or legal person, or the origin and integrity of data in the electronic form to be confirmed
Source: Joinup
Source reference: https://joinup.ec.europa.eu/taxonomy/term/http_e_f_fdata_ceuropa_ceu_fdr8_fIdentityManagementService
Example: The following implementation is an example of how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): Users roles are managed and linked to EU Login accounts (https://ec.europa.eu/research/participants/docs/h2020-funding-guide/user-account-and-roles/roles-and-access-rights_en.htm). EU Login is the entry gate to sign in to different European Commission services and/or other systems. EU Login verifies your identity and allows recovering your personal settings, history and access rights in a secure way. You can sign in using social media accounts or the EU Login account.
Interoperability Dimension: Structural IoP
LOST view: Technical view - application
Interoperability Saliency: The Authorisation Application Service ABB is salient for interoperability because it represents the identifications of actors (natural or legal persons) involved in system interactions, ensuring that the service and the data contained are accessed by actors with granted permissions. Additionally, this can be used as part of the data integrity process to identify the origin of certain data. In general, authorisation services allow for the maintenance of control and integrity of the available data, ensuring its quality when exchanged.
Identifier: http://data.europa.eu/dr8/AuthorisationApplicationService
ABB name: eira:AuthorisationApplicationService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/AuthorisationApplicationService
Interoperability Layer: TechnicalApplication
Definition: Data Management ABB is an Application Service that enables the implementation of procedures to manage data effectively. These procedures include the collection, storage, organisation, maintenance, and usage of data resources, reliability and accessibility
Source: Inspired in the Data Act
Source reference: https://digital-strategy.ec.europa.eu/en/policies/data-act
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): Oracle Data Exchange - The Data Exchange Service provides several access points to the Event Repository, allowing the user to perform queries on these events: - The Query Subscription Administration Console configures the Data Exchange Service to create queries and periodically deliver query results to designated receivers (HTTP, JMS, and AS2). The Console can also test queries before subscribing, displaying user-readable events in XML format; - A SOAP Web service allows programmatic queries. This SOAP service is based on the technically complete, but not formally ratified as of October 2006, EPCglobal EPC Information Services (EPCIS) Version 1.0 Specification.EPCglobal EPCIS 1.0 Working Draft. https://docs.oracle.com/cd/E13197_01/rfid/enterprise_server/docs20/epcis/data-exchange.html
Interoperability Dimension: Structural IoP
LOST view: Technical view - application
Viewpoint: Interoperability Privacy viewpoint
Interoperability Saliency: The Data Management Service ABB is salient for technical interoperability because it provides and shares the functionality for the share of data: "Legislation requires that decisions and data are stored and can be accessed for a specified time. This means that records and information in electronic form held by public administrations for the purpose of documenting procedures and decisions must be preserved and be converted, where necessary, to new media when old media become obsolete. The goal is to ensure that records and other forms of information keep their legibility, reliability and integrity and can be accessed as long as needed subject to security and privacy provisions."
Identifier: http://data.europa.eu/dr8/DataManagementApplicationService
ABB name: eira:DataManagementApplicationService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/DataManagementApplicationService
Interoperability Layer: TechnicalApplication
Definition: A distributed ledger is a decentralized database that maintains a continuously growing list of records, called blocks, which are linked and secured using cryptography. Unlike traditional centralized databases, a distributed ledger is replicated and synchronized across multiple nodes or computers in a network, ensuring transparency, immutability, and consensus among participants.
Source: Investopedia
Source reference: https://www.investopedia.com/terms/d/distributed-ledger.asp
Additional information: Distributed ledgers, often based on blockchain technology, enable participants to have a shared view of the database without relying on a central authority. Each participant in the network has a copy of the entire ledger, and any changes or additions to the ledger require consensus among the participants. This distributed and consensus-driven approach enhances security, as altering a single record would require tampering with all copies of the ledger across the network. Distributed ledgers find applications in various industries, including finance, supply chain management, healthcare, and voting systems, where transparency, traceability, and trust are crucial.
Example: One example of a distributed ledger application is cryptocurrency, such as Bitcoin. In the Bitcoin network, transactions are recorded in blocks, which are added to the blockchain by miners. Each participant in the network has a copy of the entire blockchain, ensuring transparency and preventing double-spending. Another example is supply chain management, where distributed ledgers can track the movement of goods from the point of origin to the end consumer, providing transparency and reducing fraud.
LOST view: TVA-Trust Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/DistributedLedgerApplicationService
ABB name: egovera:DistributedLedgerApplicationService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/egovera/DistributedLedgerApplicationService
Name: Distributed Ledger Application Service
Interoperability Layer: TechnicalApplication
Specialises: http://data.europa.eu/dr8/DigitalSolutionApplicationService
Definition: Data space ABB is an Application Service as the virtual space that enables the creation of a single market for data by integrating, transforming and making available such data.
Source: European Comision-Data Act
Source reference: https://digital-strategy.ec.europa.eu/en/policies/strategy-data
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): Mobility Data Space, The Mobility Data Space goes back to a resolution of the Concerted Action Mobility (KAM) of Germany's Federal Government from November 2019. More than 200 German mobility stakeholders from the science, industry and public administration sectors worked on the concept. acatech - the National Academy of Science and Engineering steered and coordinated the process. https://mobility-dataspace.eu/
Interoperability Dimension: Structural IoP
LOST view: TVA-Data Space Enablers [Motivation]
Interoperability Saliency: The Dataspace Application Service ABB is salient for technical interoperability because it appears as a single space where different stakeholders can integrate, transform and make information available for interested parties to reuse. Interested parties can be individuals, components or services consuming or providing data to that single space.
Identifier: http://data.europa.eu/dr8/DataspaceApplicationService
ABB name: eira:DataspaceApplicationService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/DataspaceApplicationService
Interoperability Layer: TechnicalApplication
Definition: e-Timestamp Verification and Validation ABB is an Application Service that enables the verification of timestamps used for establishing evidence that a given piece of data existed at a given point in time.
Source: eIDAS - 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.
Source reference: http://eur-lex.europa.eu/legal-content/EN/TXT/?uri=uriserv%3AOJ.L_.2014.257.01.0073.01.ENG
Additional information: An ‘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.
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): OpenSSL timestamp verification - OpenSSL is an open-source tool that can be used to retrieve and verify digital timestamps. (https://wiki.openssl.org/index.php/Manual:Ts(1)) and https://www.digistamp.com/technical/software-alternatives/using-openssl-to-request-timestamps/
Interoperability Dimension: Structural IoP
LOST view: Technical view - application
Viewpoint: Interoperability Security viewpoint
Interoperability Saliency: The e-Timestamp Verification and Validation Service ABB is salient for technical interoperability because it provides the functionalities required for e-timestamp verification and validation service.
Identifier: http://data.europa.eu/dr8/E-TimestampVerificationAndValidationApplicationService
ABB name: eira:E-TimestampVerificationAndValidationApplicationService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/E-TimestampVerificationAndValidationApplicationService
Interoperability Layer: TechnicalApplication
Definition: Accounting ABB is an Application Service that enables the process of tracking and recording access to resources, facilities and information.
Source: Inspired in Springer (Authentication, Authorization and Accounting article)
Source reference: https://link.springer.com/chapter/10.1007/978-3-030-52829-4_14
Example: The following implementation is an example of how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): BASICAL system was developed by the General Administration Intervention Board to give computer support to operations and information in the basic model of the Accounting Information System for Local Governments, in compliance with Order EHA/404/2004, of 23 November, approving the Basic Local Accounting Model Regulations. https://administracionelectronica.gob.es/ctt/verPestanaGeneralAbstract.htm?idIniciativa=basical#.ZAISY3bMI2w
Interoperability Dimension: Structural IoP
LOST view: Technical view - application
Interoperability Saliency: The Accounting Application Service ABB is salient for interoperability because it can be a mechanism to track and control access to data, applications, and services. This can help to identify when unauthorised changes or accesses have been accepted and data in a digital public servicer has been compromised and whom is the actor involved.
Identifier: http://data.europa.eu/dr8/AccountingApplicationService
ABB name: eira:AccountingApplicationService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/AccountingApplicationService
Interoperability Layer: TechnicalApplication
Definition: Digital Workplace ABB is an Application Service that enables the procedures to freely collaborate independently from the location and boundaries while maintaining high-security standards and increasing productivity and efficiency.
Source: European Comission
Source reference: https://ec.europa.eu/info/publications/digital-workplace-strategy_en
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): Set of IT tools used by European Commission officials, workers, etc. There is a new strategy put in place by the Commission to improve the work of the different roles involved. https://europa.eu/digitec/news/digital-workplace-european-commission/
Interoperability Dimension: Behavioral IoP
LOST view: Technical view - application
Viewpoint: Key Interoperability Enablers viewpoint
Interoperability Saliency: The Digital Workplace Application Service ABB is a key interoperability enabler (*) for behavioural and technical interoperability by enabling components for free collaboration and accessibility to public services, maintaining high-security standards.
Identifier: http://data.europa.eu/dr8/DigitalWorkplaceApplicationService
ABB name: eira:DigitalWorkplaceApplicationService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/DigitalWorkplaceApplicationService
Interoperability Layer: TechnicalApplication
Definition: A message broker is an intermediary software component that facilitates communication between different applications by enabling asynchronous message-based communication. It acts as a central hub where applications can publish messages and subscribe to receive messages based on specific criteria. The message broker ensures reliable delivery of messages, decouples applications from each other, and provides features like message routing, transformation, and filtering.
Source: Techopedia
Source reference: https://www.techopedia.com/definition/28536/message-broker
Additional information: Message brokers play a crucial role in distributed systems and service-oriented architectures, where multiple applications need to exchange information in a scalable and decoupled manner. They provide a reliable and efficient way to handle the communication between applications, allowing them to operate independently and asynchronously. Message brokers can handle various messaging patterns like publish/subscribe, request/reply, and point-to-point, and often support different messaging protocols such as AMQP, MQTT, or JMS.
Example: An example of a message broker is Apache Kafka, a popular distributed streaming platform. In this scenario, multiple producers can publish messages to Kafka topics, and multiple consumers can subscribe to these topics to receive the messages. The message broker ensures that messages are reliably stored and delivered to the appropriate consumers, even if they are offline or experiencing temporary failures. This enables real-time data processing, event-driven architectures, and scalable data streaming applications.
LOST view: TVA-Messaging Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/MessageBrokerApplicationService
EIRA traceability: eira:DigitalSolutionApplicationService
ABB name: egovera:MessageBrokerApplicationService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-07-20
dct:identifier: http://data.europa.eu/dr8/egovera/MessageBrokerApplicationService
dct:title: Message Broker Application Service
Definition: Duties Calculation and payment refers to the automated and accurate determination and processing of customs duties and taxes owed on imported or exported goods. This service leverages digital technologies and algorithms to calculate duties based on factors such as product classification, customs valuation, origin, and applicable trade agreements. The digital solution integrates with customs systems, financial institutions, and payment gateways to facilitate seamless payment processing, enabling importers or exporters to efficiently settle their customs obligations. By automating duties calculation and payment, this service enhances customs efficiency, reduces errors, ensures compliance with customs regulations, and expedites the release of goods, supporting smooth trade operations within the customs environment.
Source: Based on World Customs Organization (WCO)
Example: ABC Importers, a company engaged in international trade, utilizes a digital solution for duties calculation and payment to streamline their customs processes. Upon receiving an import declaration, the system automatically applies the appropriate customs tariff classification, customs valuation methods, and relevant trade agreements to calculate the duties and taxes owed on the imported goods. The digital solution integrates with the customs authority's systems, allowing for seamless transmission of the calculated duties. ABC Importers can electronically submit the payment through secure online platforms linked with financial institutions. The digital solution facilitates accurate and efficient duties calculation, reducing the risk of errors and ensuring compliance with customs regulations. By automating the duties calculation and payment process, ABC Importers accelerates the clearance of their goods, expedites customs procedures, and enhances overall trade efficiency.
eira:iopDimension: Behavioral IoP
LOST view: TVA-Customs Duties and Tariffs Management Enablers [Motivation]
eira:iopSaliency: The Digital Solution Service ABB is salient for technical interoperability because it is a central element the EIF's conceptual model for integrated public services. it represents the generalisation of all application services provided by an Interoperable European Solutionas as stated in the EIF: "Technical interoperability the applications and infrastructures linking systems and services."
Identifier: http://data.europa.eu/dr8/egovera/DutiesCalculationAndPaymentApplicationService
ABB name: eira:DigitalSolutionApplicationService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-20
dct:identifier: http://data.europa.eu/dr8/egovera/DutiesCalculationAndPaymentApplicationService
Definition: e-Timestamp Verification and Validation Service ABB is an Application Service verifing timestamps used for establishing evidence that a give piece of data existed at a given point in time. An ‘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: eIDAS - 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.
Source reference: (http://eur-lex.europa.eu/legal-content/EN/TXT/?uri=uriserv%3AOJ.L_.2014.257.01.0073.01.ENG)
Additional information: This service is often used in the context of digital signatures and data integrity, where it is crucial to establish when a document was signed or when data was created or last modified. The timestamp is created by a trusted third party, known as a Timestamping Authority (TSA), which attests to the time and date the data was presented to it without any alterations. The TSA uses a cryptographic hash function to generate a unique hash of the submitted data, then signs this hash with its private key, creating a timestamp token that can be verified using the TSA's public key. This process ensures non-repudiation, meaning that the parties involved cannot deny the existence of the data at the time it was timestamped.
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): OpenSSL timestamp verification - OpenSSL is an open-source tool that can be used to retrieve and verify digital timestamps.(https://wiki.openssl.org/index.php/Manual:Ts(1)) (https://www.digistamp.com/technical/software-alternatives/using-openssl-to-request-timestamps/)
Interoperability Dimension: Structural IoP
Identifier: http://data.europa.eu/dr8/egovera/DigitalCertificationTimestampApplicationService
ABB name: egovera:DigitalCertificationTimestampApplicationService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/egovera/DigitalCertificationTimestampApplicationService
Name: Digital Certification Timestamp Application Service
Interoperability Layer: TechnicalApplication
Specialises: http://data.europa.eu/dr8/DigitalSolutionApplicationService
Definition: Special Procedure refers to the implementation of digital platforms and systems to streamline and automate the management of customs procedures that deviate from standard import/export processes.
Source: Taxation and Customs Union
Example: In Country XYZ, customs authorities have implemented a digital solution for managing special procedures, such as inward processing, within their customs operations. Traders can electronically submit applications for special procedures through an online platform, providing necessary documentation and details. The digital solution automates the processing and monitoring of these special procedures, enabling customs authorities to track the movement of goods, manage time limits, and generate electronic customs approvals. Traders can receive real-time updates on the status of their special procedure applications, reducing administrative burdens and expediting customs processes. This digital solution enhances transparency, ensures compliance with customs regulations, and streamlines the management of special procedures, ultimately contributing to trade facilitation and efficient customs operations in Country XYZ.
eira:iopDimension: Behavioral IoP
LOST view: TVA-Customs Compliance and Regulatory Requirements Enablers [Motivation]
eira:iopSaliency: The Digital Solution Service ABB is salient for technical interoperability because it is a central element the EIF's conceptual model for integrated public services. it represents the generalisation of all application services provided by an Interoperable European Solutionas as stated in the EIF: "Technical interoperability the applications and infrastructures linking systems and services."
Identifier: http://data.europa.eu/dr8/egovera/SpecialProcedureApplicationService
ABB name: eira:DigitalSolutionApplicationService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-20
dct:identifier: http://data.europa.eu/dr8/egovera/SpecialProcedureApplicationService
Definition: Cooperation between Customs laboratories involves the implementation of digital platforms and systems to facilitate seamless collaboration, information sharing, and data exchange between customs laboratories. This service enables the efficient management and coordination of laboratory testing, sample analysis, and the exchange of scientific data and results. By leveraging digital technologies, such as laboratory information management systems (LIMS) and secure data-sharing protocols, the cooperation between Customs laboratories enhances the interoperability of laboratory operations, improves data accuracy and consistency, and fosters scientific collaboration within the customs environment. This digital solution service promotes the sharing of best practices, harmonization of testing methods, and efficient utilization of resources, ultimately contributing to robust customs control, compliance verification, and trade facilitation.
Source: Based on World Customs Organization (WCO)
Example: In a collaborative effort, Customs authorities of multiple countries have implemented a digital solution to enhance cooperation and information sharing between their respective customs laboratories. The digital platform provides a secure and standardized framework for exchanging scientific data, analysis results, and testing methodologies. Customs laboratories can efficiently share their expertise, harmonize testing methods, and collectively address emerging challenges in areas such as counterfeit detection, hazardous substance analysis, or product safety compliance. The digital solution fosters collaboration, reduces redundant testing efforts, and facilitates the timely sharing of scientific insights, leading to more effective customs control, improved compliance verification, and enhanced trade facilitation across borders.
eira:iopDimension: Behavioral IoP
LOST view: TVA-Customs Trade Facilitation and Collaboration Enablers [Motivation]
eira:iopSaliency: The Digital Solution Service ABB is salient for technical interoperability because it is a central element the EIF's conceptual model for integrated public services. it represents the generalisation of all application services provided by an Interoperable European Solutionas as stated in the EIF: "Technical interoperability the applications and infrastructures linking systems and services."
Identifier: http://data.europa.eu/dr8/egovera/CooperationBetweenCustomsLaboratoriesApplicationService
ABB name: eira:DigitalSolutionApplicationService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-20
dct:identifier: http://data.europa.eu/dr8/egovera/CooperationBetweenCustomsLaboratoriesApplicationService
Description: Talend Open Studio for Data Integration is an open-source software tool used for designing, developing, and deploying data integration processes. It provides a graphical interface that allows users to create data integration workflows, extract, transform, and load (ETL) data from various sources, and automate data integration tasks. The tool supports a wide range of data formats and connectivity options, enabling seamless integration with databases, cloud services, and other systems.
Additional information: Talend Open Studio for Data Integration is a comprehensive and flexible solution for managing data integration projects. It offers a user-friendly interface with drag-and-drop functionality, making it easy to design complex data integration workflows. The tool supports various data transformation operations, including filtering, sorting, aggregating, and joining data, allowing users to manipulate and cleanse data as per their requirements. It also provides extensive connectivity options, enabling integration with a wide range of data sources and targets. Talend Open Studio for Data Integration supports both batch and real-time data processing, making it suitable for a variety of use cases, such as data warehousing, business intelligence, and data migration. With its open-source nature, the tool benefits from a vibrant community of users and developers, ensuring continuous improvement and support.
Example: An example of using Talend Open Studio for Data Integration is in a retail company's data integration project. The company needs to extract data from multiple sources, such as their e-commerce platform, inventory management system, and customer relationship management (CRM) software. They can use Talend Open Studio to design a workflow that pulls data from these sources, performs data transformations to standardize formats and remove duplicates, and loads the cleansed data into a central data warehouse. This integrated data can then be used for generating reports, analyzing customer behavior, and making data-driven business decisions.
Publisher: Talend
Source: https://www.talend.com/products/data-integration/
LOST view: TVA-Data Management Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/TalendOpenStudioForDataIntegrationApplicationService
EIRA traceability: eira:DigitalSolutionApplicationService
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-07-20
dct:identifier: http://data.europa.eu/dr8/egovera/TalendOpenStudioForDataIntegrationApplicationService
dct:title: Talend Open Studio for Data Integration Application Service
Definition: Agenda Management Service ABB is an Application Service that enables the procedures to create, distribute and manage events and meetings for public administration and services
Source: Inspired in Public Works and Goverment Services Canada
Source reference: https://buyandsell.gc.ca/cds/public/2016/11/23/c7b27e0ac41ad50ffae2f12b0a837875/ABES.PROD.PW_PWZ.B014.E10051.ATTA001.PDF
Example: The following implementation is an example of how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): Innovation Public Procurement Broker (IPPB). https://ec.europa.eu/futurium/en/system/files/ged/action_7_innovation_public_procurement_broker_guideline.pdf
Interoperability Dimension: Structural IoP
LOST view: Technical view - application
Interoperability Saliency: The Agenda Management Application Service ABB is salient for technical interoperability because it allows managing and orchestrating different events physical and digital ones within a determined workflow according to the delivery model of each digital public service.
Identifier: http://data.europa.eu/dr8/AgendaManagementApplicationService
ABB name: eira:AgendaManagementApplicationService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/AgendaManagementApplicationService
Interoperability Layer: TechnicalApplication
Description: Apache Camel is an open-source integration framework that provides a rule-based routing and mediation engine. It allows developers to easily connect different systems and applications using various protocols and data formats. Camel simplifies the integration process by providing a set of predefined components and a powerful Domain Specific Language (DSL) for creating integration routes.
Additional information: Apache Camel enables the creation of enterprise integration patterns (EIPs) by offering a wide range of connectors and transformers. It supports a vast number of protocols and data formats, making it highly flexible and adaptable to different integration scenarios. With Camel, developers can define routes that specify the source, transformation, and destination of messages, allowing seamless communication between disparate systems. The framework also provides features like error handling, message filtering, and content-based routing, enhancing the reliability and efficiency of integration solutions.
Example: An example of Apache Camel's application is in an e-commerce system where it needs to integrate with multiple external systems. Using Camel, developers can easily define routes to fetch product information from a database, transform it into a specific format, and send it to an external inventory management system via a REST API. Similarly, Camel can be used to integrate with payment gateways, shipping providers, and other systems involved in the e-commerce process, simplifying the overall integration effort and ensuring smooth data flow between different components.
Publisher: Apache Camel Documentation
Source: https://camel.apache.org/
LOST view: TVA-Data Management Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/ApacheCamelApplicationService
EIRA traceability: eira:DigitalSolutionApplicationService
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-07-20
dct:identifier: http://data.europa.eu/dr8/egovera/ApacheCamelApplicationService
dct:title: Apache Camel Application Service
Definition: Centralized Identity Management is an IT concept that refers to the practice of managing and controlling user identities and access rights in a centralized manner. It involves the consolidation of user authentication, authorization, and user profile management into a single system or platform.
Source: Techopedia
Source reference: https://www.techopedia.com/definition/31395/centralized-identity-management-cidm
Additional information: In a centralized identity management system, all user identities and access privileges are stored and managed in a central repository. This allows organizations to streamline user provisioning, authentication, and authorization processes, ensuring consistent and secure access to resources across various applications and systems. Centralized identity management enables administrators to efficiently manage user accounts, assign roles and permissions, and enforce security policies from a single point of control. It also simplifies user onboarding and offboarding processes, enhances security by enforcing strong authentication measures, and provides auditing and reporting capabilities for compliance purposes.
Example: An example of centralized identity management is an organization implementing a single sign-on (SSO) solution. With SSO, users can authenticate themselves once and gain access to multiple applications and systems without the need to provide credentials repeatedly. The centralized identity management system handles the authentication process and grants appropriate access based on the user's role and permissions. This improves user experience, reduces the risk of password-related security breaches, and allows administrators to manage user access centrally.
LOST view: TVA-Identification and Access Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/CentralizedIdentityManagementApplicationService
ABB name: egovera:CentralizedIdentityManagementApplicationService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/egovera/CentralizedIdentityManagementApplicationService
Name: Centralized Identity Management Application Service
Interoperability Layer: TechnicalApplication
Specialises: http://data.europa.eu/dr8/DigitalSolutionApplicationService
Definition: A Large Language Model (LLM) digital service refers to a software-based platform that utilizes advanced machine learning models, specifically large-scale language models, to understand, generate, and manipulate human language. These services can perform a variety of language-related tasks such as translation, summarization, question answering, and content creation.
Source: EIRA team
Source reference: N/A
Additional information: Large Language Models like GPT (Generative Pre-trained Transformer) and BERT (Bidirectional Encoder Representations from Transformers) are trained on vast amounts of text data. They use deep learning techniques to capture the nuances of human language, enabling them to generate coherent and contextually relevant text. These models have transformer architectures that allow them to consider the full context of a word by looking at the words that come before and after it. This results in a more nuanced understanding and generation of language. LLMs are continually evolving, with newer models being trained on ever-larger datasets and with more sophisticated algorithms, pushing the boundaries of what artificial intelligence can achieve in natural language processing.
Example: LLMs can be used to generate articles, stories, or even poetry that mimic human writing styles.
Businesses employ LLMs to power chatbots and virtual assistants that can handle customer inquiries and provide support 24/7.
LLMs offer real-time translation services across various languages, breaking down communication barriers in international contexts.
Educational platforms use LLMs to create personalized learning materials and to provide tutoring or homework assistance.
Developers leverage LLMs to generate code snippets, debug programs, or even explain complex code structures in human-readable language.
Identifier: http://data.europa.eu/dr8/egovera/LargeLanguageModelApplicationService
ABB name: egovera:LargeLanguageModelApplicationService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/egovera/LargeLanguageModelApplicationService
Name: Large Language Model (LLM) Application Service
Interoperability Layer: TechnicalApplication
Specialises: http://data.europa.eu/dr8/DigitalSolutionApplicationService
Description: Keycloak is an open-source access management system that enables organizations to manage user authentication, authorization, and identity management for their applications and services. It provides a centralized platform for secure user authentication, single sign-on (SSO), and identity federation across multiple applications and systems.
Publisher: Keycloak
Source: https://www.keycloak.org/
LOST view: TVA-Identification and Access Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/KeycloakApplicationService
EIRA traceability: eira:IdentityMangementApplicationService
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-08-20
dct:identifier: http://data.europa.eu/dr8/egovera/KeycloakApplicationService
Description: The main objective of the INF SP System is to make all INF data available and to streamline the processes of INF data management. For this purpose, the European Commission has designed an EU centralised INF SP System.
Publisher: European Commission
Source: https://taxation-customs.ec.europa.eu/online-services/online-services-and-databases-customs/central-system-standardised-exchange-information_en
LOST view: TVA-Customs Data Exchange Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/CentralSystemForTheStandardisedExchangeOfInformationApplicationService
EIRA traceability: eira:DataExchangeApplicationService
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-08-20
dct:identifier: http://data.europa.eu/dr8/egovera/CentralSystemForTheStandardisedExchangeOfInformationApplicationService
Definition: Cooperation between Customs and Postal Operators involves the implementation of digital platforms and systems to facilitate seamless collaboration, information exchange, and data sharing between customs authorities and postal operators. This service enables the automation of customs procedures, such as electronic customs declarations, risk assessment, and customs clearance for postal shipments. It allows customs and postal operators to exchange shipment data, track packages in real-time, and share relevant information electronically. By leveraging digital technologies, such as electronic data interchange (EDI) and data analytics, the cooperation between customs and postal operators enhances efficiency, transparency, and security in cross-border postal operations. This digital solution service promotes trade facilitation, ensures compliance with customs regulations, and expedites the clearance and delivery of postal shipments within the customs environment.
Source: Based on World Customs Organization (WCO)
Example: In Country XYZ, customs authorities and postal operators have implemented a digital solution to enhance cooperation and streamline cross-border postal operations. The digital platform enables customs and postal operators to exchange electronic shipment data, including customs declarations and tracking information, in real-time. Customs authorities can conduct risk assessments and customs clearances based on the digital data received from postal operators. The platform facilitates seamless collaboration and communication, reducing manual paperwork and delays. It improves the visibility and traceability of postal shipments, allowing both customs authorities and postal operators to monitor the movement of packages more effectively. This digital solution enhances trade facilitation, ensures compliance with customs regulations, and expedites the clearance and delivery of postal shipments, benefiting both customs authorities and postal operators in Country XYZ.
eira:iopDimension: Behavioral IoP
LOST view: TVA-Customs Trade Facilitation and Collaboration Enablers [Motivation]
eira:iopSaliency: The Digital Solution Service ABB is salient for technical interoperability because it is a central element the EIF's conceptual model for integrated public services. it represents the generalisation of all application services provided by an Interoperable European Solutionas as stated in the EIF: "Technical interoperability the applications and infrastructures linking systems and services."
Identifier: http://data.europa.eu/dr8/egovera/CooperationBetweenCustomsAndPostalOperatorsApplicationService
ABB name: eira:DigitalSolutionApplicationService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-20
dct:identifier: http://data.europa.eu/dr8/egovera/CooperationBetweenCustomsAndPostalOperatorsApplicationService
Description: The FIWARE TRUE Connector is a software module that facilitates the exchange of data between FIWARE and the International Data Space (IDS) ecosystem. It provides a secure and reliable way to share data between different organizations, while ensuring that the data remains compliant with IDS standards.
Additional information: The FIWARE TRUE Connector is a key enabler for the IDS ecosystem, as it allows organizations to share data in a secure and compliant way. It is currently used by a number of organizations, including the European Commission and the City of Barcelona.
Example: The FIWARE TRUE Connector can be used to share data between different smart city applications. For example, it could be used to share data about traffic congestion between a traffic management system and a public transport app.
Publisher: FIWARE Foundation
Source: https://fiware-true-connector.readthedocs.io/en/latest/
LOST view: TVA-Data Space Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/FIWARETRUEConnectorApplicationService
EIRA traceability: eira:DigitalSolutionApplicationService
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-07-20
dct:identifier: http://data.europa.eu/dr8/egovera/FIWARETRUEConnectorApplicationService
dct:title: FIWARE TRUE Connector Application Service
Definition: e-Signature Preservation ABB is an Application Service extending the trustworthiness of the qualified electronic signature beyond the technological validity period.
Source: eIDAS - 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.
Source reference: http://eur-lex.europa.eu/legal-content/EN/TXT/?uri=uriserv%3AOJ.L_.2014.257.01.0073.01.ENG
Additional information: 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.
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): Namirial Spa Long term archiving solution - Namirial is a Trust Service Provider, focused on addressing the fast growing market of Digital Transaction Management (DTM), which includes legally compliant electronic signatures, managing and tracking documents flows, conducting secure transactions and ensuring secure storage of data. It provides a long term archiving: • Protect and preserve all documents generated while performing digital business transactions; • Make those documents easily searchable; • Accredited for Long-Term Archiving/Digital Preservation Services; • SaaS, high-availability, multi-company solution built to archive large volumes of documents. https://www.xyzmo.com/digital-signature/e-signature-products
Interoperability Dimension: Structural IoP
LOST view: Technical view - application
Viewpoint: Interoperability Security viewpoint
Interoperability Saliency: The e-Signature Preservation Service ABB is salient for technical interoperability because it provides the functionalities required for e-signature preservation service.
Identifier: http://data.europa.eu/dr8/E-SignaturePreservationApplicationService
ABB name: eira:E-SignaturePreservationApplicationService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/E-SignaturePreservationApplicationService
Interoperability Layer: TechnicalApplication
Definition: Privacy Impact Assessments (PIAs) are a systematic process used to identify and evaluate the potential privacy risks and impacts of a project, system, or initiative. It involves assessing the collection, use, disclosure, and retention of personal information, and determining the necessary measures to mitigate privacy risks and ensure compliance with privacy laws and regulations.
Source: Office of the Privacy Commissioner of Canada
Source reference: https://www.priv.gc.ca/en/privacy-topics/privacy-impact-assessments/02_05_d_15_pia/
Additional information: PIAs are conducted to ensure that privacy considerations are integrated into the design and implementation of IT systems or projects. They help organizations identify and address privacy risks, protect individuals' personal information, and enhance transparency and accountability. PIAs typically involve a comprehensive analysis of the data flows, data handling practices, security measures, and legal requirements associated with the project. The assessment results in recommendations and strategies to minimize privacy risks, such as implementing privacy-enhancing technologies, adopting privacy policies, or obtaining individuals' consent for data processing.
Example: An example of applying PIAs is when a government agency plans to implement a new online portal for citizens to access public services. Before launching the portal, a PIA is conducted to assess the potential privacy risks associated with the collection and storage of personal information. The assessment may identify the need for encryption of data in transit and at rest, secure user authentication mechanisms, and clear privacy notices. By conducting a PIA, the agency can ensure that privacy protections are built into the portal's design and that individuals' personal information is handled in compliance with privacy laws.
LOST view: TVA-Privacy Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/PrivacyImpactAssessmentsApplicationService
ABB name: egovera:PrivacyImpactAssessmentsApplicationService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/egovera/PrivacyImpactAssessmentsApplicationService
Name: Privacy Impact Assessments Application Service
Interoperability Layer: TechnicalApplication
Specialises: http://data.europa.eu/dr8/DigitalSolutionApplicationService
Description: Micrometer is an open-source dimensional metrics instrumentation library for microservices and other applications. It provides a simple and consistent API for collecting application metrics, such as response times, error rates, and throughput, from various monitoring systems. Micrometer supports a wide range of monitoring systems, including Prometheus, Graphite, InfluxDB, and more, allowing developers to choose the system that best fits their needs.
Additional information: Micrometer simplifies the process of instrumenting code to collect metrics, making it easier to monitor and analyze the performance and behavior of applications. It offers a vendor-neutral abstraction layer that decouples the application code from the underlying monitoring system. This allows developers to switch between monitoring systems without modifying their code. Micrometer provides a rich set of features, including support for timers, counters, gauges, histograms, and distribution summaries. It also offers advanced capabilities like dimensional metrics, which enable tagging and filtering of metrics based on custom dimensions. By using Micrometer, developers can gain valuable insights into their applications' performance, identify bottlenecks, and make data-driven decisions to optimize their systems.
Example: An example of using Micrometer is to instrument a microservice to collect response time metrics. By adding a few lines of code, developers can measure the time taken by different parts of the service, such as database queries, external API calls, or specific methods. These metrics can then be visualized and analyzed using a monitoring system like Prometheus or Graphite. This helps in identifying slow-performing components, detecting anomalies, and optimizing the overall system performance.
Publisher: Micrometer GitHub Repository
Source: https://github.com/micrometer-metrics/micrometer
LOST view: TVA-Observability and Monitoring Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/MicrometerApplicationService
EIRA traceability: eira:DigitalSolutionApplicationService
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-07-20
dct:identifier: http://data.europa.eu/dr8/egovera/MicrometerApplicationService
dct:title: Micrometer Application Service
Definition: Conformance Testing ABB is an Application Service that enables the activities and rules to determine whether a tool, platform or service faithfully meets the requirements of a standard or specification
Source: NIST
Source reference: https://www.nist.gov/itl/ssd/information-systems-group/conformance-testing
Additional information: The logistics of interoperability testing is usually more costly (time, coordination, interoperability), and interoperability testing is no substitute for a conformance test suite. Experience shows that interoperability testing is more successful and less costly when conformance of implementations has been tested first.
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): Interoperability Testbed - The Test Bed allows users to execute predefined test cases on their systems in order to test the conformance to standards and requirements, simulate a web-service, validate content and test a complete message exchange protocol. The Testbed manages test cases and users, and orchestrates domain-specific components, the domain-specific logic is in separate components that are used via web services. Test results are provided in a standardised, machine-readable format. The Test Bed also offers a test registry and repository (TRR) to store test artefacts (assertions, test cases, validation schemas, etc.) and compile test services (validation services, simulator services, etc.). Please visit the following website for more information: https://ec.europa.eu/isa2/solutions/interoperability-test-bed_en
Interoperability Dimension: Structural IoP
LOST view: Technical view - application
Interoperability Saliency: The Conformance Testing Services ABB is salient for technical interoperability because it enables the validation and verification that several solutions at one or more layers of the interoperability stack and they satisfy certain interoperability requirements.
Identifier: http://data.europa.eu/dr8/ConformanceTestingApplicationService
ABB name: eira:ConformanceTestingApplicationService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/ConformanceTestingApplicationService
Interoperability Layer: TechnicalApplication
Definition: Data Integration is the process of combining data from multiple sources into a unified and consistent view, enabling organizations to have a comprehensive understanding of their data. It involves extracting, transforming, and loading (ETL) data from various systems, databases, or files, and merging it into a single, coherent dataset.
Source: Techopedia
Source reference: https://www.techopedia.com/definition/1277/data-integration
Additional information: Data Integration plays a crucial role in enabling businesses to make informed decisions by providing a holistic view of their data. It eliminates data silos and ensures data consistency, accuracy, and reliability. The process involves identifying relevant data sources, mapping data elements, applying data transformations, and resolving any inconsistencies or conflicts. Data Integration can be achieved through various methods like manual coding, middleware tools, or specialized data integration platforms.
Example: An example of data integration is a retail company that combines data from its point-of-sale systems, customer relationship management (CRM) software, and inventory management system. By integrating this data, the company can gain insights into customer buying patterns, optimize inventory levels, and personalize marketing campaigns based on customer preferences.
LOST view: TVA-Data Management Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/DataIntegrationApplicationService
ABB name: egovera:DataIntegrationApplicationService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/egovera/DataIntegrationApplicationService
Name: Data Integration Application Service
Interoperability Layer: TechnicalApplication
Specialises: http://data.europa.eu/dr8/DigitalSolutionApplicationService
Definition: Integrity Verification ABB is an Application Service that enables the procedures to ensure that information has not been altered in an unauthorized manner since it was created, transmitted or stored.
Source: CSRC
Source reference: https://csrc.nist.gov/glossary/term/integrity_verification
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): WITDOM’s Integrity and Consistency Verification component protects the integrity and consistency of data outsourced to an untrusted remote storage. https://www.cyberwatching.eu/projects/1006/witdom/products/witdom-integrity-and-consistency-verification
Interoperability Dimension: Structural IoP
LOST view: Technical view - application
Viewpoint: Interoperability Security viewpoint
Interoperability Saliency: The Integrity Verification Application Service ABB is salient for interoperability because is a key service to ensure data integrity, it can perform checks on: changes on the data, if changes are authorised or not, and when those changes have been performed. By ensuring this, digital public services can provide additional trust in the data and information provided to stakeholders.
Identifier: http://data.europa.eu/dr8/IntegrityVerificationApplicationService
ABB name: eira:IntegrityVerificationApplicationService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/IntegrityVerificationApplicationService
Interoperability Layer: TechnicalApplication
Description: Docker Compose is a tool that allows defining and running multi-container Docker applications. It uses a YAML file to configure the services, networks, and volumes required for the application, enabling easy deployment and management of complex containerized environments.
Additional information: Docker Compose simplifies the process of orchestrating multiple Docker containers by providing a declarative way to define the desired state of the application stack. The YAML file specifies the services, their dependencies, network connections, and storage volumes required for the application. Docker Compose then takes care of creating and managing the necessary containers, networks, and volumes, ensuring the defined services can communicate with each other. It allows developers to define the entire application stack as code, making it easy to reproduce and share the environment across different development stages or deployment environments. Docker Compose is particularly useful for development and testing scenarios where multiple services need to work together.
Example: An example of using Docker Compose is a web application that consists of a frontend service, a backend API service, and a database service. The Docker Compose file would define these services along with their configurations, dependencies, and network connections. By running a single command, Docker Compose would create and manage the necessary containers, networks, and volumes, setting up the complete application stack. This allows developers to easily spin up the entire environment on their local machines for development or testing purposes, ensuring all services are properly connected and functioning as expected.
Publisher: Docker Documentation
Source: https://docs.docker.com/compose/
LOST view: TVA-Containerization Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/DockerComposeApplicationService
EIRA traceability: eira:DigitalSolutionApplicationService
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-07-20
dct:identifier: http://data.europa.eu/dr8/egovera/DockerComposeApplicationService
dct:title: Docker Compose Application Service
Definition: Decentralized Identity Management is a concept where individuals have control over their digital identities without relying on a central authority. It enables users to manage their personal information, authentication, and authorization across various online services and platforms.
Source: Wikipedia
Source reference: https://en.wikipedia.org/wiki/Decentralized_identity
Additional information: In decentralized identity management, individuals have the ability to create and control their digital identities using blockchain or distributed ledger technology. This approach eliminates the need for centralized identity providers, reducing the risk of data breaches and identity theft. Users can selectively share their personal information with different service providers, maintaining privacy and control over their data. Decentralized identity management also allows for interoperability between different systems, enabling seamless authentication and authorization across multiple platforms. It empowers individuals to have a self-sovereign identity, giving them the freedom to manage and protect their digital presence.
Example: An example of decentralized identity management is the use of blockchain-based digital wallets. These wallets store an individual's personal information and cryptographic keys securely on the blockchain. When accessing online services, the individual can authenticate themselves using their wallet, eliminating the need for usernames and passwords. The wallet can selectively share relevant information with the service provider, ensuring privacy and reducing the risk of data breaches. Additionally, the individual can use the same wallet across different platforms, enabling seamless authentication and personalized experiences.
LOST view: TVA-Identification and Access Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/DecentralizedIdentityManagementApplicationService
ABB name: egovera:DecentralizedIdentityManagementApplicationService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/egovera/DecentralizedIdentityManagementApplicationService
Name: Decentralized Identity Management Application Service
Interoperability Layer: TechnicalApplication
Specialises: http://data.europa.eu/dr8/DigitalSolutionApplicationService
Definition: Transit procedure refers to the implementation of digital platforms and systems to facilitate the smooth movement of goods under customs control from one customs territory to another.
Source: Based on World Customs Organization (WCO)
Example: A digital solution for transit procedures has been implemented between neighboring customs authorities to streamline cross-border trade. Traders submit electronic transit declarations through a centralized platform, enabling real-time data exchange and shared visibility. The digital solution automates risk assessments, simplifies document verification, and expedites customs clearances. It reduces transit times, eliminates paperwork, and enhances the security and efficiency of cross-border trade within the customs environment.
eira:iopDimension: Behavioral IoP
LOST view: TVA-Customs Compliance and Regulatory Requirements Enablers [Motivation]
eira:iopSaliency: The Digital Solution Service ABB is salient for technical interoperability because it is a central element the EIF's conceptual model for integrated public services. it represents the generalisation of all application services provided by an Interoperable European Solutionas as stated in the EIF: "Technical interoperability the applications and infrastructures linking systems and services."
Identifier: http://data.europa.eu/dr8/egovera/TransitProcedureApplicationService
ABB name: eira:DigitalSolutionApplicationService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-20
dct:identifier: http://data.europa.eu/dr8/egovera/TransitProcedureApplicationService
Definition: MS' Customs organization management involves the implementation of digital platforms and systems to effectively manage and oversee the operations of customs organizations within a specific country or region. This service enables the digitalization of customs processes, including customs declarations, risk assessment, inspection management, and trade data analysis. The digital solution provides customs authorities with tools for workforce planning, resource allocation, performance monitoring, and reporting. It facilitates centralized management of customs operations, enhances coordination between customs offices, improves decision-making based on real-time data, and supports the enforcement of customs regulations and trade facilitation initiatives. By leveraging digital technologies, Member State Customs organization management enhances efficiency, transparency, and effectiveness in customs operations, contributing to secure and efficient cross-border trade.
Source: Based on World Customs Organization (WCO)
Example: In Country ABC, the customs authority has implemented a digital solution for Member State Customs organization management to streamline customs operations and enhance organizational efficiency. The digital platform integrates various systems and databases to enable centralized management of customs processes, including customs declarations, risk assessment, and inspection management. Customs officers have access to real-time dashboards and analytics tools, allowing them to monitor performance, allocate resources effectively, and make data-driven decisions. The digital solution facilitates coordination and collaboration between customs offices across the country, enhancing communication, information sharing, and standardization of procedures. By leveraging this digital solution, Country ABC's customs authority improves operational efficiency, strengthens customs control, and supports trade facilitation initiatives, contributing to secure and efficient cross-border trade within the country.
eira:iopDimension: Behavioral IoP
LOST view: TVA-Customs Trade Facilitation and Collaboration Enablers [Motivation]
eira:iopSaliency: The Digital Solution Service ABB is salient for technical interoperability because it is a central element the EIF's conceptual model for integrated public services. it represents the generalisation of all application services provided by an Interoperable European Solutionas as stated in the EIF: "Technical interoperability the applications and infrastructures linking systems and services."
Identifier: http://data.europa.eu/dr8/egovera/MSCustomsOrganizationManagementApplicationService
ABB name: eira:DigitalSolutionApplicationService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-20
dct:identifier: http://data.europa.eu/dr8/egovera/MSCustomsOrganizationManagementApplicationService
Definition: Open Data Management refers to the practice of making data freely available, accessible, and usable by the public, without restrictive copyright or other controls, to encourage transparency, innovation, and collaboration.
Source: Open Knowledge Foundation
Source reference: https://okfn.org/opendata/
Example: Data.gov
The U.S. government's open data portal that provides public access to high value, machine-readable datasets generated by the Executive Branch of the Federal Government.
European Union Open Data Portal
Provides access to data from the institutions and other bodies of the European Union. The data covers various topics such as the economy, employment, science, environment, and education.
CKAN
An open-source data portal platform used by governments, organizations, and communities worldwide to publish and share data. It provides tools to streamline publishing, sharing, finding, and using data.
Identifier: http://data.europa.eu/dr8/egovera/OpenDataManagementApplicationService
ABB name: egovera:OpenDataManagementApplicationService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/egovera/OpenDataManagementApplicationService
Name: Open Data Management Application Service
Interoperability Layer: TechnicalApplication
Specialises: http://data.europa.eu/dr8/DigitalSolutionApplicationService
Definition: Registration Service ABB is an Application Service that enables users to sign-up for a service, application or platform through unique personal identification data.
Source: eIDAS - 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.
Source reference: http://eur-lex.europa.eu/legal-content/EN/TXT/?uri=uriserv%3AOJ.L_.2014.257.01.0073.01.ENG
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): BE:Trusted - BE:Trusted list including information related to the qualified trust service providers which are supervised by the issuing Member State, together with information related to the qualified trust services provided by them, in accordance with the relevant provisions laid down in 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. https://tsl.belgium.be/archive/TSL-BE-2016-T3_vi5_sn27%20SPF%20Economie_signed.pdf
Interoperability Dimension: Structural IoP
LOST view: Technical view - application
Viewpoint: Interoperability Security viewpoint
Interoperability Saliency: The Registration Service ABB is salient for technical interoperability because it provides the functionalities of the discovery of essential information about accredited service providers.
Identifier: http://data.europa.eu/dr8/RegistrationApplicationService
ABB name: eira:RegistrationApplicationService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/RegistrationApplicationService
Interoperability Layer: TechnicalApplication
Definition: Identity Management ABB is an Application Service that enables the set of processes, policies and technologies used to manage and secure digital entities of individuals, devices and applications.
Source: Inspired in eIDAS
Source reference: https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=CELEX:32014R0910&from=EN
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): EU Login - EU Login is the European Commission's user authentication service. It allows authorised users to access a wide range of Commission web services. EU Login is the entry gate to sign in to different European Commission services and/or other systems. EU Login verifies your identity and allows recovering your personal settings, history and access rights in a secure way. You can sign in using social media accounts or the EU Login account. EU Login supports a variety of verification methods: • Password; • ECAS Mobile App PIN code; • ECAS Mobile App QR code; • On mobile authentication; • Mobile phone + SMS; • Token and Token CRAM. https://webgate.ec.europa.eu/cas/manuals/EU_Login_Tutorial_1.1.pdf
Interoperability Dimension: Structural IoP
LOST view: TVA-Identification and Access Enablers [Motivation]
Interoperability Saliency: The Identity Management Application Service is salient for interoperability because it can help in the management of digital identities for individuals, devices and applications, ensuring and enabling that information on digital public services is available under the proper conditions and to the specific target. This can ensure and enhance the quality of data meant to be exchanged through interoperable systems, applications and digital public services.
Identifier: http://data.europa.eu/dr8/IdentityManagementApplicationService
ABB name: eira:IdentityManagementApplicationService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/IdentityManagementApplicationService
Interoperability Layer: TechnicalApplication
Definition: e-Seal Verification and Validation Service ABB is an Application Service enabling the functionality of the verification of documents that are signed electronically. 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: eIDAS - 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.
Source reference: (http://eur-lex.europa.eu/legal-content/EN/TXT/?uri=uriserv%3AOJ.L_.2014.257.01.0073.01.ENG)
Additional information: The Digital Certification eSeal is a technology based on the European Union's eIDAS (Electronic Identification, Authentication and Trust Services) Regulation, which provides a standardized level of security for electronic transactions across EU member states. An eSeal is the digital equivalent of a company's stamp or seal, providing a legal assurance about the origin and integrity of the document it is attached to. It is used by organizations to certify the authenticity and integrity of electronic documents and to ensure they have not been altered since being sealed. The eSeal contains information about the legal entity that applied it, the date and time of sealing, and uses digital signatures to protect the document. It is particularly useful for automating document processing while maintaining compliance with legal requirements.
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): CEF eSignature DSS - DSS (Digital Signature Services) is an open-source software library for electronic signature creation and validation. DSS supports the creation and verification of interoperable and secure electronic signatures in line with European legislation. In particular, DSS aims to follow the eIDAS Regulation and related standards closely. DSS can be re-used in an IT solution for electronic signatures to ensure that signatures are created and verified in line with European legislation and standards. DSS allows re-use in a variety of different ways: in an applet, in a stand-alone application or in a server application. DSS can also be used as a reference implementation for IT solutions which do not directly re-use it. CEF eSignature's DSS open-source library delivers the following benefits to its users: • Open-source software under LGPL 2.1, a non-viral open source license; • Interoperability of the e-signatures; • Supports both e-signatures and e-seals; • Validation of countersignatures and multiple signatures; • Alignment with the eIDAS Regulation and related standards; • Supports EU standards on: o Signature formats and packaging methods; o Signature validation procedures; • Validation relying on Member States' trusted lists: o Status of trust service providers/trust service, compensation of information, path validation.(https://ec.europa.eu/cefdigital/wiki/display/CEFDIGITAL/eSignaturefile:///C:/Users/bocquilp/Downloads/DSS(ServiceOfferingDescription)%20(v0.03)%20(5).pdf)
Interoperability Dimension: Structural IoP
Identifier: http://data.europa.eu/dr8/egovera/DigitalCertificationESealApplicationService
ABB name: egovera:DigitalCertificationESealApplicationService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/egovera/DigitalCertificationESealApplicationService
Name: Digital Certification ESeal Application Service
Interoperability Layer: TechnicalApplication
Specialises: http://data.europa.eu/dr8/DigitalSolutionApplicationService
Definition: The Identification Service ABB is essential for technical interoperability, providing user authentication functionalities. In alignment with the eIDAS regulation, it ensures secure access to system resources by verifying user identities, thus maintaining system integrity and security.
Source: eIDAS - 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.
Source reference: http://eur-lex.europa.eu/legal-content/EN/TXT/?uri=uriserv%3AOJ.L_.2014.257.01.0073.01.ENG
Example: The following implementation is an example of how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): The EUDI Wallet (European Digital Identity Wallet) serves as a practical implementation of the Identification Service ABB. As a Solution Building Block (SBB), the EUDI Wallet exemplifies the integration of user authentication functionalities compliant with the eIDAS regulation.
Interoperability Dimension: Structural IoP
LOST view: Technical view - application
Interoperability Saliency: The Identification Service ABB is salient for technical interoperability because it ensures secure user authentication across different systems and platforms. By providing standardized and reliable methods for verifying user identities, it enables seamless access to services and data exchange between disparate systems. This interoperability is crucial for maintaining the integrity, security, and efficiency of digital interactions within and across organizational and national boundaries.
Identifier: http://data.europa.eu/dr8/IdentificationApplicationService
ABB name: eira:IdentificationApplicationService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-07-25
Identifier: http://data.europa.eu/dr8/IdentificationApplicationService
Interoperability Layer: TechnicalApplication
Definition: Data Virtualization ABB is an Application Service that enables the access and manipulation of data from various sources without the need for physical data integration.
Source: Joinup
Source reference: https://joinup.ec.europa.eu/sites/default/files/inline-files/Data%20visualisation%20service%20definition.pdf
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): Virtuoso. Virtuoso Universal Server is modern platform built on existing open standards that harnesses the power of Hyperlinks (functioning as Super Keys) for breaking down data silos that impede both user and enterprise ability. For example, Virtuoso's core SQL & SPARQL powers many Enterprise Knowledge Graph initiatives just as it does DBpedia and a majority of nodes in the Linked Open Data Cloud -- the world's largest publicly accessible Knowledge Graph. https://big-data-test-infrastructure.ec.europa.eu/service-offering/virtuoso_en
Interoperability Dimension: Structural IoP
LOST view: Technical view - application
Interoperability Saliency: The Data Virtualization Application Service ABB is salient for technical interoperability because provides the tools for visualising datasets in a graphical way. These services can enable to visualise data and information from different sources, and public services, in a manner that can be better processed, understood, and therefore, interoperability can be achieved.
Identifier: http://data.europa.eu/dr8/DataVirtualizationApplicationService
ABB name: eira:DataVirtualizationApplicationService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/DataVirtualizationApplicationService
Interoperability Layer: TechnicalApplication
Description: The EBSI Wallet for Verifiers is tailored to meet the needs of organizations, such as companies, universities, and other entities, that require a reliable and efficient method to verify the authenticity of Verifiable Credentials (VCs) presented by holders. Under the EBSI (European Blockchain Services Infrastructure) Verifiable Credentials exchange framework, this wallet type ensures that credentials are valid, trustworthy, and compliant with established standards.
Example: The following narrative is ficticius example that can help to understand how EUDI Wallet can be used: Maria, an EU citizen, needs to access healthcare services in another EU country. Using her EUDI Wallet, she logs in with her secure credentials. The healthcare provider requests her health insurance information, and Maria consents to share it through the wallet. The EUDI Wallet securely transmits her insurance details, allowing the provider to validate and authorize her access to services. This seamless process ensures that Maria receives the necessary healthcare without any physical paperwork, showcasing the EUDI Wallet's efficiency in managing identity verification, secure data sharing, and cross-border access.
Publisher: European Commission
Source: EBSI
LOST view: TVA-Identification and Access Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/EUDIWalletForVerifiersApplicationService
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/egovera/EUDIWalletForVerifiersApplicationService
Name: EUDI Wallet For Verifiers
Interoperability Layer: TechnicalApplication
Realises: http://data.europa.eu/dr8/IdentificationApplicationService
Definition: Observability is a concept in IT that refers to the ability to gain insights into the internal state and behavior of a system by analyzing its external outputs. It involves collecting and analyzing various metrics, logs, traces, and other data points to understand the system's performance, health, and potential issues.
Source: Observability in Distributed Systems
Source reference: https://www.oreilly.com/library/view/observability-in-distributed/9781492033431/
Additional information: Observability goes beyond traditional monitoring by providing a holistic view of a system's internal workings. It focuses on capturing and analyzing data that can help in troubleshooting, debugging, and optimizing the system's performance. By collecting and correlating data from different sources, such as application logs, infrastructure metrics, and distributed traces, observability enables IT teams to gain deep insights into the system's behavior and identify patterns or anomalies that may impact its performance or reliability. It helps in understanding the cause and effect relationships within the system, making it easier to diagnose and resolve issues.
Example: An example of observability in practice is the monitoring of a cloud-based application. By collecting metrics on response times, error rates, and resource utilization, along with analyzing logs and distributed traces, IT teams can gain a comprehensive understanding of the application's performance. They can identify bottlenecks, pinpoint the root cause of issues, and make informed decisions to optimize the application's architecture or infrastructure. Observability enables proactive monitoring and troubleshooting, leading to improved system reliability and better user experiences.
LOST view: TVA-Observability and Monitoring Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/ObservabilityApplicationService
EIRA traceability: eira:DigitalSolutionApplicationService
ABB name: egovera:ObservabilityApplicationService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-07-20
dct:identifier: http://data.europa.eu/dr8/egovera/ObservabilityApplicationService
dct:title: Observability Application Service
Definition: The Training and Learning Management building block is an application service that helps organizations efficiently plan, administer, deliver, and track training and learning activities. It provides a comprehensive platform for managing courses, registrations, content delivery, assessments, certifications, and reporting. This application service supports both traditional and online training, offering features like content authoring, learner management, progress tracking, assessments, and analytics. It plays a vital role in promoting employee development, knowledge acquisition, and skill enhancement, allowing organizations to deliver effective training programs in a scalable and streamlined manner.
Source: Gartner
Source reference: https://www.gartner.com/en/documents/3985042
LOST view: TVA-Functional Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/TrainingAndLearningManagementApplicationService
ABB name: egovera:TrainingAndLearningManagementApplicationService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/egovera/TrainingAndLearningManagementApplicationService
Interoperability Layer: TechnicalApplication
Specialises: http://data.europa.eu/dr8/DigitalWorkplaceApplicationService
Definition: Artificial Intelligence ABB is an Application Service that enables the procedures to display intelligent behaviour by analysing their environment and taking actions with some degree of autonomy to achieve specific objectives.
Source: European Comision
Source reference: https://digital-strategy.ec.europa.eu/en/library/definition-artificial-intelligence-main-capabilities-and-scientific-disciplines
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): PyTorch is a machine learning framework based on the Torch library, used for applications such as computer vision and natural language processing, originally developed by Meta AI and now part of the Linux Foundation umbrella. It is free and open-source software released under the modified BSD license. Although the Python interface is more polished and the primary focus of development, PyTorch also has a C++ interface. https://pytorch.org/
Interoperability Dimension: Structural IoP
LOST view: Technical view - application
Interoperability Saliency: The Artificial Intelligence Application Service ABB is salient for technical interoperability because it refers to applications services that are able to analyse data, analysing the environment to take some automated actions for reaching objectives. Those services can enable digital public services to interact between them, exchanging data, and promoting interoperability of services.
Identifier: http://data.europa.eu/dr8/ArtificialIntelligenceApplicationService
ABB name: eira:ArtificialIntelligenceApplicationService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/ArtificialIntelligenceApplicationService
Interoperability Layer: TechnicalApplication
Definition: Data Persistence ABB is an application service that enables the procedures that allow data to be stored and retrieved over an extended period of time.
Source: Inspired in European Comision Data Strategy
Source reference: https://commission.europa.eu/strategy-and-policy/priorities-2019-2024/europe-fit-digital-age/european-data-strategy_en
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): Context Broker as a CEF Building Block. https://ec.europa.eu/digital-building-blocks/wikis/download/attachments/82773424/Context%20Broker%20Brochure.pdf?version=1&modificationDate=1558016168498&api=v2
Interoperability Dimension: Structural IoP
LOST view: Technical view - application
Interoperability Saliency: The Data Persistence Application Service ABB is salient for technical interoperability because it implements the ability to retrieve and store data in a long-term approach. This is relevant for interoperability as it can extend the period in which data can be used, retrieved, and exchanged improving the quality and range of data that can be exchanged, and therefore, is a key element for digital public services interoperability.
Identifier: http://data.europa.eu/dr8/DataPersistenceApplicationService
ABB name: eira:DataPersistenceApplicationService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/DataPersistenceApplicationService
Interoperability Layer: TechnicalApplication
Description: Apache NiFi is an open-source data integration and data flow automation tool that provides a visual interface to easily manage and control the movement of data between different systems. It allows users to design, build, and execute data flows, known as data pipelines, using a web-based graphical user interface (GUI). NiFi supports a wide range of data sources, destinations, and processors, enabling efficient data ingestion, transformation, routing, and monitoring.
Additional information: Apache NiFi is designed to handle real-time data streaming and batch processing, making it suitable for use cases such as IoT data collection, log aggregation, data migration, and data transformation. It provides a scalable and reliable platform for managing data flows across various systems, including databases, cloud storage, messaging systems, and more. NiFi's GUI allows users to visually create and modify data pipelines, making it accessible to both technical and non-technical users. It offers features like data provenance, security, data lineage, and extensive monitoring capabilities. NiFi also supports data governance and compliance requirements through features like data encryption, access control, and auditing.
Example: An example application of Apache NiFi is in a data lake architecture. NiFi can be used to ingest data from various sources like sensors, social media feeds, and databases into a centralized data lake. It can then perform data transformations, filtering, and enrichment before storing the processed data in a suitable format for downstream analytics. NiFi's visual interface makes it easy to design and manage complex data flows, ensuring efficient and reliable data movement within the data lake ecosystem.
Publisher: Apache NiFi - Official Website
Source: https://nifi.apache.org/
LOST view: TVA-Data Management Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/ApacheNiFiApplicationService
EIRA traceability: eira:DigitalSolutionApplicationService
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-07-20
dct:identifier: http://data.europa.eu/dr8/egovera/ApacheNiFiApplicationService
dct:title: Apache NiFi Application Service
Definition: Tariffs registry management refers to the systematic and automated management of customs tariffs and related information. This service involves the digitalization and centralization of tariff schedules, rates, and updates within a digital registry or database. The digital solution enables customs authorities to efficiently maintain, update, and disseminate tariff information, ensuring accurate and consistent application of tariffs during customs processes. It allows for easy access and searchability of tariff data, facilitates tariff classification, and supports customs compliance. By automating tariffs registry management, this service enhances transparency, reduces manual errors, improves trade facilitation, and enables efficient tariff determination and assessment within the customs environment.
Source: Based on World Customs Organization (WCO)
Example: In the customs authority of Country XYZ, a digital solution for tariffs registry management has been implemented to streamline the management and dissemination of tariff information. The system digitalizes and centralizes the country's tariff schedules, rates, and updates into a comprehensive digital registry. Customs officers and traders can easily access the digital registry to determine the applicable tariff rates for goods being imported or exported. The solution automates the maintenance of tariff data, ensuring that the latest tariff changes and amendments are accurately recorded and readily available. This digital solution enhances transparency, reduces manual errors, and facilitates efficient tariff classification, promoting smoother customs processes and trade facilitation for both customs officers and traders in Country XYZ.
eira:iopDimension: Behavioral IoP
LOST view: TVA-Customs Duties and Tariffs Management Enablers [Motivation]
eira:iopSaliency: The Digital Solution Service ABB is salient for technical interoperability because it is a central element the EIF's conceptual model for integrated public services. it represents the generalisation of all application services provided by an Interoperable European Solutionas as stated in the EIF: "Technical interoperability the applications and infrastructures linking systems and services."
Identifier: http://data.europa.eu/dr8/egovera/TariffsRegistryManagementApplicationService
ABB name: eira:DigitalSolutionApplicationService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-20
dct:identifier: http://data.europa.eu/dr8/egovera/TariffsRegistryManagementApplicationService
Definition: Privacy ABB is an Application Service enabling the share of functionalities such as storing, securing, anonymising, pseudonymising, rectifying and erasing personal data.
Source: ePrivacy Regulation
Source reference: https://digital-strategy.ec.europa.eu/en/policies/eprivacy-regulation
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): SOLVIT - Solvit is a mailbox service for the access, rectification or deletion of personal data.(http://ec.europa.eu/solvit/privacy-statement/#maincontentSec8)
Interoperability Dimension: Structural IoP
LOST view: Technical view - application
Viewpoint: Interoperability Privacy viewpoint
Interoperability Saliency: The Privacy Service ABB is salient for interoperability because "security and privacy are primary concerns in the provision of public services" (EIF) and, as stated in EIF Recommendation 15: "Define a common security and privacy framework and establish processes for public services to ensure secure and trustworthy data exchange between public administrations and in interactions with citizens and businesses."
Identifier: http://data.europa.eu/dr8/PrivacyApplicationService
ABB name: eira:PrivacyApplicationService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/PrivacyApplicationService
Interoperability Layer: TechnicalApplication
Description: Apache Atlas is an open-source metadata management and governance framework for enterprises. It provides a scalable platform to capture, manage, and govern metadata about data assets across various systems in an organization. By enabling metadata management, Apache Atlas helps organizations gain insights into their data assets, ensure data quality, and enforce data governance policies.
Additional information: Apache Atlas allows organizations to create a centralized repository of metadata that describes their data assets, such as databases, tables, columns, and relationships between them. It supports a wide range of data platforms and technologies, including Hadoop, relational databases, cloud storage, and more. With Apache Atlas, organizations can define and enforce data governance policies, such as data classification, access controls, and data lineage. It provides a comprehensive set of features for data discovery, data lineage tracking, data quality monitoring, and metadata search. Apache Atlas also integrates with other data management and governance tools, enabling seamless interoperability in the data ecosystem.
Example: An organization can use Apache Atlas to track the lineage of a specific data asset, such as a customer's personal information stored in a database. It can capture metadata about the source of the data, the transformations applied to it, and the systems that consume this data. This allows organizations to understand the origin and usage of data, ensuring compliance with regulations like GDPR. Additionally, Apache Atlas can be used to classify sensitive data, apply access controls, and monitor data quality, providing a holistic view of data assets and enabling effective data governance.
Publisher: Apache Atlas Documentation
Source: https://atlas.apache.org/
LOST view: TVA-Data Management Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/ApacheAtlasApplicationService
EIRA traceability: eira:DigitalSolutionApplicationService
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-07-20
dct:identifier: http://data.europa.eu/dr8/egovera/ApacheAtlasApplicationService
dct:title: Apache Atlas Application Service
Definition: The Vocabulary Hub is an IT concept that refers to a centralized repository or platform designed to store, manage, and provide access to a wide range of vocabularies or terminologies used in various domains. It serves as a comprehensive and standardized source of terms, definitions, and relationships between concepts, enabling efficient data integration, interoperability, and semantic understanding across different systems and applications.
Source: W3C
Source reference: https://www.w3.org/TR/vocab-hub/
Additional information: The Vocabulary Hub acts as a central hub for vocabularies, offering a unified and consistent way to define and organize terms. It provides a common framework for describing concepts, their properties, and relationships, facilitating data sharing and integration between different systems and applications. The hub typically supports various standard formats and protocols for vocabulary representation and exchange, such as RDF, SKOS, and SPARQL, ensuring compatibility and interoperability. It also offers functionalities like versioning, access control, and search capabilities, making it easier for users to discover, reuse, and maintain vocabularies.
Example: An example of the Vocabulary Hub in action is a healthcare system that integrates data from multiple sources, such as electronic health records, medical devices, and research databases. By utilizing the Vocabulary Hub, the system can harmonize and align the terminologies used in these disparate sources, enabling accurate and meaningful data exchange. This allows healthcare professionals to access comprehensive patient information, perform advanced analytics, and improve decision-making processes. Additionally, the Vocabulary Hub facilitates the development of innovative applications and services that leverage the shared vocabulary knowledge, promoting collaboration and interoperability within the healthcare ecosystem.
LOST view: TVA-Knowledge Discovery Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/VocabularyHubApplicationService
ABB name: egovera:VocabularyHubApplicationService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/egovera/VocabularyHubApplicationService
Name: Vocabulary Hub Application Service
Interoperability Layer: TechnicalApplication
Specialises: http://data.europa.eu/dr8/DigitalSolutionApplicationService
Definition: Data encryption is the process of converting plain text or data into a coded form known as ciphertext, to prevent unauthorized access during transmission or storage. It uses cryptographic algorithms and keys to transform the data into an unreadable format, which can only be decrypted using the corresponding decryption key.
Source: Techopedia
Source reference: https://www.techopedia.com/definition/24880/data-encryption
Additional information: Data encryption is a fundamental technique used in information security to protect sensitive data from unauthorized disclosure. It ensures that even if an attacker gains access to the encrypted data, they cannot understand or use it without the decryption key. Encryption provides confidentiality, integrity, and authenticity of data, making it an essential component in securing data at rest, in transit, or in use. Various encryption algorithms such as AES, RSA, and DES are used in different scenarios based on the required level of security.
Example: An example of data encryption is when a user sends a confidential email using a secure email service. The email content is encrypted before transmission, and only the intended recipient possessing the decryption key can decipher and read the message. Similarly, when storing sensitive data on a cloud storage service, encryption can be applied to ensure that even if the data is compromised, it remains unreadable without the appropriate decryption key.
LOST view: TVA-Privacy Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/DataEncryptionApplicationService
ABB name: egovera:DataEncryptionApplicationService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/egovera/DataEncryptionApplicationService
Name: Data Encryption Application Service
Interoperability Layer: TechnicalApplication
Specialises: http://data.europa.eu/dr8/DigitalSolutionApplicationService
Description: Apache Kafka Streams is a client library for building real-time streaming applications and microservices. It allows developers to process and analyze data in real-time as it flows through Kafka topics, enabling the creation of scalable and fault-tolerant stream processing applications.
Additional information: Apache Kafka Streams provides a high-level API that simplifies the development of stream processing applications. It allows developers to write stream processing logic using familiar programming constructs like Java or Scala, making it easier to build and maintain real-time data processing pipelines. Kafka Streams leverages the distributed nature of Apache Kafka, providing fault-tolerance, scalability, and durability out of the box. It supports various operations such as filtering, transforming, aggregating, and joining streams of data, enabling complex data processing tasks. With Kafka Streams, developers can build applications that react to events in real-time, perform continuous computations, and generate real-time analytics.
Example: An example of using Apache Kafka Streams is in a real-time analytics application. Suppose a company wants to analyze customer behavior on their e-commerce platform. They can use Kafka Streams to process and analyze the stream of events generated by customer interactions, such as page views, clicks, and purchases. The application can perform various operations like filtering out irrelevant events, aggregating data to calculate metrics like conversion rates or average session duration, and joining streams to correlate customer behavior. The processed data can then be used to generate real-time dashboards, trigger alerts, or feed into machine learning models for personalized recommendations.
Publisher: Confluent
Source: https://www.confluent.io/what-is-apache-kafka-streams/
LOST view: TVA-Messaging Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/ApacheKafkaStreamsApplicationService
EIRA traceability: eira:DigitalSolutionApplicationService
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-07-20
dct:identifier: http://data.europa.eu/dr8/egovera/ApacheKafkaStreamsApplicationService
dct:title: Apache Kafka Streams Application Service
Description: Docker is an open-source platform that enables developers to automate the deployment and scaling of applications using containerization. Containers are lightweight, isolated environments that package an application and its dependencies, allowing it to run consistently across different computing environments. Docker provides a standardized way to build, distribute, and run containers, making it easier to develop, deploy, and manage applications in a highly efficient and portable manner.
Additional information: Docker simplifies the process of creating and managing application environments by abstracting away the underlying infrastructure. It allows developers to package their applications along with all the necessary dependencies into a container image, which can then be deployed on any system running Docker. Containers provide a consistent and reproducible environment, ensuring that the application behaves the same way regardless of the host system. Docker also offers features like container orchestration, networking, and storage management, making it a powerful tool for building and deploying distributed applications.
Example: An example of using Docker is when a developer wants to deploy a web application. They can create a Dockerfile, which defines the application's dependencies and configuration. Using this Dockerfile, they can build a container image that encapsulates the application and its dependencies. This image can then be distributed and run on any system with Docker installed, ensuring consistent behavior across different environments. Docker also allows for easy scaling of the application by running multiple instances of the container, making it suitable for deployment in cloud environments.
Publisher: Docker Documentation
Source: https://docs.docker.com/get-started/overview/
LOST view: TVA-Containerization Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/DockerApplicationService
EIRA traceability: eira:DigitalSolutionApplicationService
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-07-20
dct:identifier: http://data.europa.eu/dr8/egovera/DockerApplicationService
dct:title: Docker Application Service
Description: The European Digital Identity (EUDI) Wallet is a secure digital tool designed to be available to all EU citizens, residents, and businesses, enabling them to access a variety of public and private digital services across the EU. Users have full control over their identity data and certificates, deciding what information to share. It ensures privacy and facilitates secure, interoperable digital interactions within the EU. The framework is developed with input from EU Member States, adhering to common standards and technical specifications to ensure consistency and reliability.
Example: The following narrative is ficticius example that can help to understand how EUDI Wallet can be used: Maria, an EU citizen, needs to access healthcare services in another EU country. Using her EUDI Wallet, she logs in with her secure credentials. The healthcare provider requests her health insurance information, and Maria consents to share it through the wallet. The EUDI Wallet securely transmits her insurance details, allowing the provider to validate and authorize her access to services. This seamless process ensures that Maria receives the necessary healthcare without any physical paperwork, showcasing the EUDI Wallet's efficiency in managing identity verification, secure data sharing, and cross-border access.
Publisher: European Commission
LOST view: TVA-Identification and Access Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/EUDIWalletApplicationService
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/egovera/EUDIWalletApplicationService
Name: EUDI Wallet
Interoperability Layer: TechnicalApplication
Realises: http://data.europa.eu/dr8/IdentificationApplicationService
Definition: A container is a lightweight and portable software package that includes everything needed to run an application, including the code, runtime, system tools, libraries, and settings. Containers provide a consistent and isolated environment for applications to run, ensuring that they can run reliably across different computing environments.
Source: Techopedia
Source reference: https://www.techopedia.com/definition/28536/container
Additional information: Containers are based on the concept of virtualization but differ in their approach. While traditional virtualization involves running multiple operating systems on a single physical machine, containers share the host operating system kernel and only isolate the application processes. This makes containers more lightweight, faster to start, and more efficient in terms of resource utilization. Containers are commonly used in modern IT infrastructure, enabling developers to package applications with their dependencies and deploy them consistently across different environments, such as development, testing, and production.
Example: An example of container usage is in microservices architecture, where an application is broken down into smaller, loosely coupled services. Each service can be packaged as a container, allowing for independent development, scaling, and deployment. Containers also find applications in cloud computing, where they enable efficient resource utilization and easy migration of applications between different cloud providers.
LOST view: TVA-Containerization Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/ContainerApplicationService
EIRA traceability: eira:DigitalSolutionApplicationService
ABB name: egovera:ContainerApplicationService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-07-20
dct:identifier: http://data.europa.eu/dr8/egovera/ContainerApplicationService
dct:title: Container Application Service
Definition: Software Component Discovery and Catalogue Service ABB is an Application Service containing information about software products and serves as an index during software scans to automatically identify the software products installed on a monitored computer but also getting knowledge on units of composition with contractually specified interfaces and explicit context dependencies.
Source: Dictionary
Source reference: (https://www.dictionary.com/browse/catalog)
LOST view: Technical view - application
Identifier: http://data.europa.eu/dr8/SoftwareComponentDiscoveryandCatalogueApplicationService
eira:ID: ABB525
ABB name: eira:SoftwareComponentDiscoveryandCatalogueApplicationService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2022-18-01
Definition: Blockchain ABB is an Application Service that enables secure, transparent, and immutable record-keeping and transaction processing shared by all participants in a network.
Source: Inspired in European Comission-Blockchain Strategy
Source reference: https://digital-strategy.ec.europa.eu/en/policies/blockchain-strategy
Additional information: Specifically, Blockchain stores records that contain a time stamp and reference links to previous transactions. With this information, anyone with access rights can trace back a transactional event, at any point in its history, belonging to any participant. A blockchain is one architectural design of the broader concept of distributed ledgers.
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): Fishcoin Project, is a project using Blockchain technologies for seafood traceability. https://fishcoin.co/
Interoperability Dimension: Structural IoP
LOST view: Technical view - application
Interoperability Saliency: The Blockchain Application Service ABB is salient for interoperability because as a ledger technology application service can contribute to the trustability of digital public services. It can enable the register and list of irrevocable transactional data being exchanged between digital public services. To that extent, a blockchain service can be enhancing digital public services by establishing a mechanism to track data, and the process applied to it.
Identifier: http://data.europa.eu/dr8/BlockchainApplicationService
ABB name: eira:BlockchainApplicationService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/BlockchainApplicationService
Interoperability Layer: TechnicalApplication
Description: eDelivery is a network of nodes for digital communications. It is based on a distributed model where every participant becomes a node using standard transport protocols and security policies. eDelivery helps public administrations to exchange electronic data and documents with other public administrations, businesses and citizens, in an interoperable, secure, reliable and trusted way.
Publisher: European Commission
Source: https://ec.europa.eu/digital-building-blocks/sites/display/DIGITAL/Documentation+eDelivery
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/eDeliveryApplicationService
LOST view: Technical view - application
EIRA concept: eira:SolutionBuildingBlock
ABB name: eira:eDeliveryApplicationService
Additional information: eDelivery is one of the building blocks of Digital Europe. These building blocks are reusable specifications, software and services that will form part of a wide variety of IT systems in different policy domains of the EU. eDelivery is based on the AS4 messaging protocol, open and free for all, developed by the OASIS standards development organisation. To ease its adoption in Europe, eDelivery uses the AS4 implementation guidelines defined by the Member States in the e-SENS Large Scale Pilot. Organisations must install an Access Point, or use a Service Provider, to exchange information with the AS4 messaging protocol.
Interoperability Dimension: Behavioral IoP
Viewpoint: Interoperability Privacy viewpoint
Additional identifier: http://data.europa.eu/dr8/eDeliveryApplicationService
EIF Layer: TechnicalApplication
Realises: eira:DataExchangeApplicationService
Definition: e-Seal Verification and Validation ABB is an Application Service that enables the functionality of the verification of documents that are signed electronically.
Source: eIDAS - 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.
Source reference: http://eur-lex.europa.eu/legal-content/EN/TXT/?uri=uriserv%3AOJ.L_.2014.257.01.0073.01.ENG
Additional information: 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.
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): CEF eSignature DSS - DSS (Digital Signature Services) is an open-source software library for electronic signature creation and validation. DSS supports the creation and verification of interoperable and secure electronic signatures in line with European legislation. In particular, DSS aims to follow the eIDAS Regulation and related standards closely. DSS can be re-used in an IT solution for electronic signatures to ensure that signatures are created and verified in line with European legislation and standards. DSS allows re-use in a variety of different ways: in an applet, in a stand-alone application or in a server application. DSS can also be used as a reference implementation for IT solutions which do not directly re-use it. CEF eSignature's DSS open-source library delivers the following benefits to its users: • Open-source software under LGPL 2.1, a non-viral open source license; • Interoperability of the e-signatures; • Supports both e-signatures and e-seals; • Validation of countersignatures and multiple signatures; • Alignment with the eIDAS Regulation and related standards; • Supports EU standards on: o Signature formats and packaging methods; o Signature validation procedures; • Validation relying on Member States' trusted lists: o Status of trust service providers/trust service, compensation of information, path validation. https://ec.europa.eu/cefdigital/wiki/display/CEFDIGITAL/eSignaturefile:///C:/Users/bocquilp/Downloads/DSS(ServiceOfferingDescription)%20(v0.03)%20(5).pdf
Interoperability Dimension: Structural IoP
LOST view: Technical view - application
Viewpoint: Interoperability Security viewpoint
Interoperability Saliency: The e-Seal Verification and Validation Service ABB is salient for technical interoperability because it provides the functionalities required for e-seal verification and validation service.
Identifier: http://data.europa.eu/dr8/E-SealVerificationAndValidationApplicationService
ABB name: eira:E-SealVerificationAndValidationApplicationService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/E-SealVerificationAndValidationApplicationService
Interoperability Layer: TechnicalApplication
Definition: e-Signature Creation ABB is an Application Service that enables the process of signing data, in electronic form by a natural person
Source: eIDAS - 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.
Source reference: http://eur-lex.europa.eu/legal-content/EN/TXT/?uri=uriserv%3AOJ.L_.2014.257.01.0073.01.ENG
Additional information: 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.
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): CEF eSignature DSS - DSS (Digital Signature Services) is an open-source software library for electronic signature creation and validation. DSS supports the creation and verification of interoperable and secure electronic signatures in line with European legislation. In particular, DSS aims to follow the eIDAS Regulation and related standards closely. DSS can be re-used in an IT solution for electronic signatures to ensure that signatures are created and verified in line with European legislation and standards. DSS allows re-use in a variety of different ways: in an applet, in a stand-alone application or in a server application. DSS can also be used as a reference implementation for IT solutions which do not directly re-use it. CEF eSignature's DSS open-source library delivers the following benefits to its users: • Open-source software under LGPL 2.1, a non-viral open source license; • Interoperability of the e-signatures; • Supports both e-signatures and e-seals; • Validation of countersignatures and multiple signatures; • Alignment with the eIDAS Regulation and related standards; • Supports EU standards on: o Signature formats and packaging methods; o Signature validation procedures; • Validation relying on Member States' trusted lists: o Status of trust service providers/trust service, compensation of information, path validation. https://ec.europa.eu/cefdigital/wiki/display/CEFDIGITAL/eSignaturefile:///C:/Users/bocquilp/Downloads/DSS(ServiceOfferingDescription)%20(v0.03)%20(5).pdf
Interoperability Dimension: Structural IoP
LOST view: Technical view - application
Viewpoint: Interoperability Security viewpoint
Interoperability Saliency: The e-Signature Creation Service ABB is salient for technical interoperability because it provides the functionalities required for e-signature creation service.
Identifier: http://data.europa.eu/dr8/E-SignatureCreationApplicationService
ABB name: eira:E-SignatureCreationApplicationService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/E-SignatureCreationApplicationService
Interoperability Layer: TechnicalApplication
Definition: Authorisation ABB is an Application Service that enables processes to formalise the electronic identification of a natural or legal person, or the origin and integrity of data in the electronic form to be confirmed
Source: Joinup
Source reference: https://joinup.ec.europa.eu/taxonomy/term/http_e_f_fdata_ceuropa_ceu_fdr8_fIdentityManagementService
Example: The following implementation is an example of how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): Users roles are managed and linked to EU Login accounts (https://ec.europa.eu/research/participants/docs/h2020-funding-guide/user-account-and-roles/roles-and-access-rights_en.htm). EU Login is the entry gate to sign in to different European Commission services and/or other systems. EU Login verifies your identity and allows recovering your personal settings, history and access rights in a secure way. You can sign in using social media accounts or the EU Login account.
eira:iopDimension: Behavioral IoP
LOST view: TVA-Customs Identification and Access Enablers [Motivation]
eira:iopSaliency: The Authorisation Application Service ABB is salient for interoperability because it represents the identifications of actors (natural or legal persons) involved in system interactions, ensuring that the service and the data contained are accessed by actors with granted permissions. Additionally, this can be used as part of the data integrity process to identify the origin of certain data. In general, authorisation services allow for the maintenance of control and integrity of the available data, ensuring its quality when exchanged.
Identifier: http://data.europa.eu/dr8/AuthorisationApplicationService
ABB name: eira:AuthorisationApplicationService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2022-01-18
dct:identifier: http://data.europa.eu/dr8/AuthorisationApplicationService
Description: An eIDAS-Service operated by the Sending Member State and providing personal identification data. The eIDAS Service enables individuals and businesses to use their electronic identities (eIDs) to access online services, sign electronic documents, and authenticate themselves in digital transactions. It ensures that electronic identities are reliable, secure, and interoperable across EU member states
Publisher: European Commission
LOST view: TVA-Identification and Access Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/EIDAS-Proxy-ServiceApplicationService
EIRA traceability: eira:IdentityManagementApplicationService
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-08-20
dct:identifier: http://data.europa.eu/dr8/egovera/EIDAS-Proxy-ServiceApplicationService
Description: RabbitMQ is an open-source message broker software that enables communication between different software systems by implementing the Advanced Message Queuing Protocol (AMQP). It acts as a mediator, receiving messages from producers and delivering them to consumers, ensuring reliable and asynchronous communication. RabbitMQ provides a flexible and scalable solution for decoupling components of distributed systems, allowing them to communicate efficiently and reliably.
Additional information: RabbitMQ operates based on the concept of message queues, where producers send messages to specific queues, and consumers retrieve messages from those queues. It supports various messaging patterns like point-to-point, publish-subscribe, request-reply, and more. RabbitMQ provides features like message persistence, acknowledgments, routing, and filtering, making it suitable for building robust and fault-tolerant systems. It can be integrated with different programming languages and platforms, making it a versatile choice for implementing distributed systems.
Example: An example of RabbitMQ's application is in a microservices architecture, where different services need to communicate with each other asynchronously. Each microservice can act as a producer, sending messages to RabbitMQ queues, and other microservices can act as consumers, retrieving and processing those messages. This decoupled communication allows each service to operate independently and scale horizontally, ensuring fault tolerance and high availability.
Publisher: RabbitMQ Official Documentation
Source: https://www.rabbitmq.com/
LOST view: TVA-Messaging Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/RabbitMQApplicationService
EIRA traceability: eira:DigitalSolutionApplicationService
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-07-20
dct:identifier: http://data.europa.eu/dr8/egovera/RabbitMQApplicationService
dct:title: RabbitMQ Application Service
Description: Docker Swarm is a native clustering and orchestration solution for Docker containers. It allows users to create and manage a swarm of Docker nodes, turning them into a single virtual Docker host. Swarm enables the deployment and scaling of containerized applications across multiple hosts, providing high availability and fault tolerance.
Additional information: Docker Swarm simplifies the management of containerized applications by abstracting the underlying infrastructure. It provides a declarative approach to define services, networks, and volumes, allowing users to easily deploy and scale applications across a cluster of Docker nodes. Swarm uses a leader-follower model, where one node acts as the manager and others as workers. The manager node handles orchestration, scheduling, and service discovery, while the worker nodes execute the tasks assigned by the manager. Swarm also supports load balancing, rolling updates, and automatic service recovery, ensuring the continuous availability of applications. It integrates seamlessly with Docker CLI and Compose, making it easy to adopt for existing Docker users.
Example: An example of using Docker Swarm is deploying a microservices-based application across a cluster of Docker nodes. By defining the desired state of the application using a Docker Compose file, Swarm can automatically distribute the services across the available nodes, ensuring load balancing and fault tolerance. As the application scales, Swarm can dynamically adjust the number of replicas for each service, distributing the workload efficiently. If a node fails, Swarm automatically reschedules the affected tasks on healthy nodes, maintaining the application's availability. Docker Swarm provides a robust and scalable solution for managing containerized applications in a clustered environment.
Publisher: Docker Documentation
Source: https://docs.docker.com/engine/swarm/
LOST view: TVA-Containerization Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/DockerSwarmApplicationService
EIRA traceability: eira:DigitalSolutionApplicationService
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-07-20
dct:identifier: http://data.europa.eu/dr8/egovera/DockerSwarmApplicationService
dct:title: Docker Swarm Application Service
Description: ActiveMQ is an open-source message broker that enables the exchange of messages between different applications or components in a distributed system. It provides reliable and scalable messaging functionality, allowing applications to communicate asynchronously and decoupling the sender and receiver. ActiveMQ supports various messaging patterns like point-to-point, publish-subscribe, and request-response.
Additional information: ActiveMQ is built on the Java Message Service (JMS) API and supports multiple protocols such as AMQP, MQTT, and STOMP. It offers features like message persistence, message filtering, priority-based message delivery, and message acknowledgment. ActiveMQ can be used in various scenarios, including enterprise messaging, real-time data streaming, event-driven architectures, and integration of heterogeneous systems. It provides reliable messaging infrastructure for applications that require asynchronous communication, loose coupling, and scalability.
Example: An example of using ActiveMQ is in a microservices architecture, where different microservices need to communicate with each other. Each microservice can publish messages to specific topics, and other microservices interested in those topics can subscribe to receive the messages. This allows the microservices to communicate asynchronously, reducing dependencies and enabling scalability. ActiveMQ ensures reliable delivery of messages even in the presence of network failures or high message volumes.
Publisher: Apache ActiveMQ
Source: https://activemq.apache.org/
LOST view: TVA-Messaging Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/ActiveMQApplicationService
EIRA traceability: eira:DigitalSolutionApplicationService
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-07-20
dct:identifier: http://data.europa.eu/dr8/egovera/ActiveMQApplicationService
dct:title: ActiveMQ Application Service
Description: Apache Storm is an open-source distributed real-time computation system. It provides a scalable and fault-tolerant platform for processing large streams of data in real-time, enabling organizations to analyze and react to data as it arrives. Storm allows users to define complex data processing workflows, known as topologies, which can handle high volumes of data with low latency.
Additional information: Apache Storm is designed to process data in a distributed and fault-tolerant manner, making it highly reliable for mission-critical applications. It uses a master-worker architecture where a cluster of machines collaboratively processes the data streams. Storm provides guaranteed message processing, fault recovery, and scalability, making it suitable for applications requiring real-time analytics, continuous computation, and stream processing. It integrates with various data sources and sinks, allowing seamless integration with existing data infrastructure. Storm's flexibility and extensibility make it a popular choice for building real-time data processing systems.
Example: One example of Apache Storm's application is in the financial industry, where it can be used for real-time fraud detection. By processing incoming transaction data in real-time, Storm can identify suspicious patterns or anomalies and trigger immediate actions to prevent fraudulent activities. Another example is in social media analytics, where Storm can process streams of social media data to perform sentiment analysis, trending topic detection, and real-time recommendation systems.
Publisher: Apache Software Foundation
Source: https://storm.apache.org/
LOST view: TVA-Data Management Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/ApacheStormApplicationService
EIRA traceability: eira:DigitalSolutionApplicationService
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-07-20
dct:identifier: http://data.europa.eu/dr8/egovera/ApacheStormApplicationService
dct:title: Apache Storm Application Service
Definition: Laboratories management refers to the implementation of digital tools and systems to efficiently manage and oversee customs laboratories' operations. This service involves the automation and optimization of laboratory processes, such as sample tracking, test management, result analysis, and quality assurance. By leveraging digital technologies like laboratory information management systems (LIMS), electronic data capture, and data analytics, laboratories management solutions enhance the accuracy, traceability, and efficiency of laboratory testing and analysis within the customs environment. This digital solution service streamlines laboratory workflows, improves data integrity, enables effective resource allocation, and facilitates timely reporting, contributing to robust customs control and compliance.
Source: Based on World Customs Organization (WCO)
Example: In a customs laboratory, XYZ Customs implements a digital solution for laboratories management to enhance their testing and analysis operations. The system utilizes a Laboratory Information Management System (LIMS) to automate sample tracking, test management, and result analysis. With the digital solution, XYZ Customs can efficiently manage their laboratory workflows, ensuring proper handling of samples, tracking test progress, and recording analysis results. The LIMS enables seamless data capture, storage, and retrieval, improving data integrity and traceability. Quality control measures are integrated, ensuring compliance with international standards and regulatory requirements. Through this digital solution, XYZ Customs optimizes their laboratory processes, streamlines reporting, and facilitates effective resource allocation, resulting in improved customs control, accurate analysis, and efficient customs operations.
eira:iopDimension: Behavioral IoP
LOST view: TVA-Customs Data Management Enablers [Motivation]
eira:iopSaliency: The Digital Solution Service ABB is salient for technical interoperability because it is a central element the EIF's conceptual model for integrated public services. it represents the generalisation of all application services provided by an Interoperable European Solutionas as stated in the EIF: "Technical interoperability the applications and infrastructures linking systems and services."
Identifier: http://data.europa.eu/dr8/egovera/LaboratoriesManagementApplicationService
ABB name: eira:DigitalSolutionApplicationService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-20
dct:identifier: http://data.europa.eu/dr8/egovera/LaboratoriesManagementApplicationService
Definition: e-Seal Preservation ABB is an Application Service that enables the procedures to extend the trustworthiness of the qualified electronic signature beyond the technological validity period.
Source: eIDAS - 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.
Source reference: http://eur-lex.europa.eu/legal-content/EN/TXT/?uri=uriserv%3AOJ.L_.2014.257.01.0073.01.ENG
Additional information: 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.
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): CEF eSignature DSS - DSS (Digital Signature Services) is an open-source software library for electronic signature creation and validation. DSS supports the creation and verification of interoperable and secure electronic signatures in line with European legislation. In particular, DSS aims to follow the eIDAS Regulation and related standards closely. DSS can be re-used in an IT solution for electronic signatures to ensure that signatures are created and verified in line with European legislation and standards. DSS allows re-use in a variety of different ways: in an applet, in a stand-alone application or in a server application. DSS can also be used as a reference implementation for IT solutions which do not directly re-use it. CEF eSignature's DSS open-source library delivers the following benefits to its users: • Open-source software under LGPL 2.1, a non-viral open source license; • Interoperability of the e-signatures; • Supports both e-signatures and e-seals; • Validation of countersignatures and multiple signatures; • Alignment with the eIDAS Regulation and related standards; • Supports EU standards on: o Signature formats and packaging methods; o Signature validation procedures; • Validation relying on Member States' trusted lists: o Status of trust service providers/trust service, compensation of information, path validation. https://ec.europa.eu/cefdigital/wiki/display/CEFDIGITAL/eSignaturefile:///C:/Users/bocquilp/Downloads/DSS(ServiceOfferingDescription)%20(v0.03)%20(5).pdf
Interoperability Dimension: Structural IoP
LOST view: Technical view - application
Viewpoint: Interoperability Security viewpoint
Interoperability Saliency: The e-Seal Preservation Service ABB is salient for technical interoperability because it provides the functionalities required for e-seal preservation service.
Identifier: http://data.europa.eu/dr8/E-SealPreservationApplicationService
ABB name: eira:E-SealPreservationApplicationService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/E-SealPreservationApplicationService
Interoperability Layer: TechnicalApplication
Definition: Business Intelligence (BI) is a technology-driven process for analyzing data and presenting actionable information to help executives, managers and other corporate end users make informed business decisions.
Source: TechTarget
Source reference: https://searchbusinessanalytics.techtarget.com/definition/business-intelligence-BI
Additional information: Business Intelligence encompasses a wide variety of tools, applications and methodologies that enable organizations to collect data from internal systems and external sources, prepare it for analysis, develop and run queries against the data, and create reports, dashboards and data visualizations to make the analytical results available to corporate decision-makers. BI can include data mining, online analytical processing, querying and reporting. Companies use BI to improve decision making, cut costs and identify new business opportunities. BI is more than just corporate reporting and more than a set of tools to coax data out of enterprise systems.
Example: A retail company could use BI to track customer buying habits and use that data to develop new marketing strategies. This could involve analyzing the demographics and purchasing habits of customers to identify trends, manage inventory and increase sales.
A healthcare organization could use BI to track patient satisfaction levels, efficiency of care, and then implement changes for improvement based on these metrics.
A financial institution could use BI to detect fraudulent credit card transactions and monitor customer data to assess risk and manage customer relationships more effectively.
LOST view: TVA-Analytics Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/BusinessIntelligenceApplicationService
ABB name: egovera:BusinessIntelligenceApplicationService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/egovera/BusinessIntelligenceApplicationService
Name: Business Intelligence Application Service
Interoperability Layer: TechnicalApplication
Specialises: http://data.europa.eu/dr8/DigitalSolutionApplicationService
Definition: Registered Electronic Delivery ABB is an Application Service that enables the procedures to transmit sensitive or confidential documents and messages between parties.
Source: eIDAS - 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.
Source reference: http://eur-lex.europa.eu/legal-content/EN/TXT/?uri=uriserv%3AOJ.L_.2014.257.01.0073.01.ENG
Additional information: A registered Electronic Delivery shares functionalities that i) makes it possible to transmit data between third parties by electronic means and ii) provides evidence relating to the handling of the transmitted data, including proof of sending and receiving the data, and iii) that protects transmitted data against the risk of loss, theft, damage or any unauthorised alterations;
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): Qualified electronic registered delivery services listed with CEF Trusted List Browser tool Qualified electronic registered delivery services are listed on https://webgate.ec.europa.eu/tl-browser/#/search/1 and https://webgate.ec.europa.eu/tl-browser/#/search/1
Interoperability Dimension: Structural IoP
LOST view: Technical view - application
Viewpoint: Interoperability Security viewpoint
Interoperability Saliency: The Registered Electronic Delivery Service ABB is salient for technical interoperability because it provides the functionalities related to the handling of data transmission.
Identifier: http://data.europa.eu/dr8/RegisteredElectronicDeliveryApplicationService
ABB name: eira:RegisteredElectronicDeliveryApplicationService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/RegisteredElectronicDeliveryApplicationService
Interoperability Layer: TechnicalApplication
Definition: A Consent Management Application Service refers to a software solution or service that enables organizations to manage and track user consent for the collection, use, and processing of personal data. It provides a centralized platform for obtaining, recording, and managing consent preferences in compliance with privacy regulations and data protection requirements. The Consent Management Application Service typically includes features such as consent capture, storage, consent preference management, and consent lifecycle tracking.
Source: Gartner
Additional information: Consent Management plays a crucial role in ensuring compliance with data protection regulations, such as the General Data Protection Regulation (GDPR). It requires organizations to implement mechanisms that enable individuals to easily give, withdraw, or modify their consent preferences. This involves providing clear and concise consent requests, offering granular choices for different processing activities, and maintaining an auditable record of consent. Consent Management systems often include features like consent forms, preference centers, and consent lifecycle management to facilitate the effective management of user consent.
Example: An example of Consent Management in practice is a website that presents users with a cookie banner upon their first visit. The banner provides clear information about the types of cookies used, their purposes, and the option to accept or decline their use. The user's choice is recorded and respected throughout their browsing session. Additionally, the website offers a preference center where users can review and modify their consent preferences at any time. This ensures that the website is transparent, respects user choices, and complies with applicable data protection regulations.
LOST view: TVA-Privacy Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/ConsentManagementApplicationService
ABB name: egovera:ConsentManagementApplicationService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/egovera/ConsentManagementApplicationService
Name: Consent Management Application Service
Interoperability Layer: TechnicalApplication
Specialises: http://data.europa.eu/dr8/DigitalSolutionApplicationService
Definition: Data Analytics ABB is an Application Service that enables the use of procedures to analyze data and extract insights that can be used to improve business decision-making, optimize business processes, and drive innovation
Source: Inspired in Data Act
Source reference: https://digital-strategy.ec.europa.eu/en/policies/data-act
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): Microsoft Power BI - Power BI is a business analytics service by Microsoft. It aims to provide interactive visualizations and business intelligence capabilities with an interface simple enough for end users to create their own reports and dashboards. It is part of the Microsoft Power Platform.(https://powerbi.microsoft.com/it-it/what-is-power-bi/)
Interoperability Dimension: Structural IoP
LOST view: Technical view - application
Interoperability Saliency: The Data Analytics Service ABB is salient for technical interoperability because it enables the automated processing and analysis of different data source.
Identifier: http://data.europa.eu/dr8/DataAnalyticsApplicationService
ABB name: eira:DataAnalyticsApplicationService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/DataAnalyticsApplicationService
Interoperability Layer: TechnicalApplication
Definition: Data Publication ABB is an Application Service that enables the processes of making data available through the adoption of discoverable, accessible, and reusable mechanisms.
Source: ISA2
Source reference: https://ec.europa.eu/isa2/sites/default/files/docs/publications/isa2-actions-phase2_-_poc_-_wp1_specifications_en.pdf
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): European Data Portal - The European Data Portal harvests the metadata of Public Sector Information available on public data portals across European countries. Information regarding the provision of data and the benefits of re-using data is also included. What is Open Data? - Open (Government) Data refers to the information collected, produced or paid for by the public bodies (also referred to as Public Sector Information) and made freely available for re-use for any purpose. The licence will specify the terms of use; - Public sector information is information held by the public sector. The Directive on the re-use of public sector information provides a common legal framework for a European market for government-held data. It is built around the key pillars of the internal market: free flow of data, transparency and fair competition. It is important to note that not all of the public sector information is Open Data. Within the Portal, sections are dedicated to: - Searching datasets: Categories have been established to structure the metadata harvested from the various countries. These categories follow the revision of the DCAT Application Profile and have been mapped against the Eurovoc Thesaurus; - Providing Data: This section gives an insight into understanding Open Data from the perspective of a data provider. In addition, instructions are offered for those who wish their data portal to be harvested by the European Data Portal; - Using Data: How Open Data is being used, as well as the economic benefits of Open Data are detailed in this section; - Training and Library: eLearning modules about Open Data as well as training guides and a knowledge base referencing publications around Open Data and featured projects; - Portals can be national, regional, local or domain specific. They cover the 28 EU Member States, EEA, countries involved in the EU's neighbourhood policy and Switzerland. https://www.europeandataportal.eu/
Interoperability Dimension: Structural IoP
LOST view: Technical view - application
Viewpoint: Interoperability Privacy viewpoint
Interoperability Saliency: The Data Pubblication Service ABB is salient for technical interoperability because it provides the functionalities to make public data freely available for use and reuse by others unless restriction aoply as stated in the EIF recommendation n.2: "Publish the data you own as open data unless certain restrictions apply."
Identifier: http://data.europa.eu/dr8/DataPublicationApplicationService
ABB name: eira:DataPublicationApplicationService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/DataPublicationApplicationService
Interoperability Layer: TechnicalApplication
Description: An OAuth2/OpenID Connect server for IoT devices which use their private keys to request OAuth2 access tokens in order to access protected resources and websites or apps which retrieve user attributes.
Additional information: Omejdn is a lightweight server that can be easily deployed on a Raspberry Pi or other small device. It is designed to be easy to use and configure, and it provides a secure way for IoT devices to access protected resources.
Example: Omejdn can be used to enable IoT devices to access cloud-based services, such as data storage or data analytics. It can also be used to enable IoT devices to communicate with each other securely.
Publisher: Fraunhofer AISEC
Source: https://github.com/Fraunhofer-AISEC/omejdn-server
LOST view: TVA-Identification and Access Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/FraunhoferOmejdnServerApplicationService
EIRA traceability: eira:IdentityMangementApplicationService
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-07-21
dct:identifier: http://data.europa.eu/dr8/egovera/FraunhoferOmejdnServerApplicationService
dct:title: Fraunhofer Omejdn Server Application Service
Description: WSO2 Identity Server is an open-source, extensible, and standards-based identity and access management (IAM) solution. It provides a comprehensive set of features to manage user identities, secure access to resources, and enable single sign-on (SSO) across multiple applications and systems.
Additional information: The WSO2 Identity Server allows organizations to centrally manage user identities, roles, and permissions. It supports various authentication mechanisms such as username/password, social logins, and multi-factor authentication. The server enables secure access to resources through fine-grained authorization policies, including role-based access control (RBAC) and attribute-based access control (ABAC). It also supports federation protocols like SAML, OAuth, and OpenID Connect, facilitating SSO and seamless integration with external identity providers. The WSO2 Identity Server is highly customizable and can be extended to meet specific IAM requirements of organizations.
Example: An example of using the WSO2 Identity Server is in a large enterprise where multiple applications and systems need to authenticate and authorize users. The server can be deployed to provide a centralized IAM solution, allowing users to have a single set of credentials for accessing various resources. It enables SSO, eliminating the need for users to log in multiple times. The server also ensures secure access by enforcing access control policies based on user roles and attributes. Additionally, it supports integration with external identity providers, enabling seamless authentication and authorization across different systems.
Publisher: WSO2 Documentation
Source: https://docs.wso2.com/display/IS570/WSO2+Identity+Server+Documentation
LOST view: TVA-Identification and Access Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/WSO2IdentityServerApplicationService
EIRA traceability: eira:IdentityMangementApplicationService
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-07-21
dct:identifier: http://data.europa.eu/dr8/egovera/WSO2IdentityServerApplicationService
dct:title: WSO2 Identity Server Application Service
Definition: The Digital Certification eSignature Service enables users to securely sign electronic documents using digital certificates. It leverages cryptographic techniques to ensure the integrity, authenticity, and non-repudiation of digitally signed documents. This service provides a user-friendly interface accessible via the web, allowing users to upload their documents, apply their digital signature, and generate a digitally signed version. It utilizes digital certificate authorities to issue and manage digital certificates, providing a trusted framework for electronic signatures. The Digital Certification eSignature Service enhances document security, eliminates the need for physical signatures, and supports the digital transformation of business processes.
Source: ETSI
Source reference: https://www.etsi.org/deliver/etsi_ts/102700_102799/10277801/01.01.01_60/ts_10277801v010101p.pdf
Interoperability Dimension: Structural IoP
LOST view: TVA-Trust Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/DigitalCertificationESignatureServiceApplicationService
ABB name: egovera:DigitalCertificationESignatureServiceApplicationService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/egovera/DigitalCertificationESignatureServiceApplicationService
Interoperability Layer: TechnicalApplication
Specialises: http://data.europa.eu/dr8/E-SignatureVerificationAndValidationApplicationService
Definition: A Submission Service is a web-based application service that allows users to upload, validate, and publish their data for sharing and dissemination. It provides an intuitive web interface for users to submit their datasets, metadata, and related information in standard formats. The service verifies the submitted data against predefined standards and guidelines to ensure compliance. By enabling seamless data publication, it empowers users to contribute to data repositories or portals, making the data more discoverable and accessible to a wider audience. Additional features of the Submission Service may include data versioning, access control, and integration with metadata standards.
Source: Research Data Alliance
LOST view: TVA-Functional Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/SubmissionServiceApplicationService
ABB name: egovera:SubmissionServiceApplicationService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/egovera/SubmissionServiceApplicationService
Interoperability Layer: TechnicalApplication
Specialises: http://data.europa.eu/dr8/DataPublicationApplicationService
Description: The International Data Space Connector (IDSC) is an IT concept that enables secure and trusted data exchange between organizations in a decentralized manner. It provides a framework for establishing data sovereignty and control, allowing organizations to share and collaborate on data while maintaining ownership and privacy. The IDSC facilitates the seamless integration of data from various sources, ensuring interoperability and enabling the creation of data ecosystems.
Additional information: The International Data Space Connector is a software component that acts as a mediator between data providers and data consumers. It ensures secure and trusted data exchange by implementing authentication, authorization, and encryption mechanisms. The IDSC enables organizations to define and enforce access control policies, ensuring that data is only shared with authorized parties. It also supports data discovery and metadata management, allowing organizations to easily find and understand available data resources. The IDSC promotes data sovereignty by enabling organizations to retain control over their data, even when sharing it with external partners. It provides a scalable and flexible solution for data exchange, supporting various data formats and communication protocols. The IDSC is a key enabler for the creation of data ecosystems, where organizations can collaborate and innovate based on shared data resources.
Example: An example of the International Data Space Connector in action is in the manufacturing industry. Multiple organizations, such as suppliers, manufacturers, and logistics providers, can securely exchange data related to production processes, quality control, and supply chain management. By using the IDSC, these organizations can collaborate and optimize their operations based on real-time data insights. For instance, a manufacturer can securely share production data with a supplier, allowing them to adjust their inventory levels based on demand forecasts. This seamless data exchange facilitated by the IDSC leads to improved efficiency, reduced costs, and enhanced decision-making across the entire value chain.
Publisher: International Data Spaces Association
Source: https://www.internationaldataspaces.org/
LOST view: TVA-Data Space Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/InternationalDataSpaceConnectorApplicationService
EIRA traceability: eira:DigitalSolutionApplicationService
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-07-20
dct:identifier: http://data.europa.eu/dr8/egovera/InternationalDataSpaceConnectorApplicationService
dct:title: International Data Space Connector Application Service
Definition: Transaction Management refers to a web service that enables the efficient and reliable processing of data transactions in a distributed system. It facilitates the coordination and execution of multiple data operations as a single atomic unit, ensuring data integrity and consistency. The Transaction Management service provides mechanisms for transaction initiation, execution, and completion, including features such as concurrency control, isolation, and transactional rollback in case of failures or errors. It enables applications to perform complex data operations while maintaining data integrity and ensuring that changes are either committed in their entirety or rolled back.
Source: EU Open Data Portal
Source reference: https://data.europa.eu/euodp/en/data/handbook
LOST view: TVA-Functional Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/TransactionManagementApplicationService
ABB name: egovera:TransactionManagementApplicationService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/egovera/TransactionManagementApplicationService
Interoperability Layer: TechnicalApplication
Specialises: http://data.europa.eu/dr8/DataManagementApplicationService
Definition: An online platform that provides a centralized and user-friendly interface for traders, customs authorities, and other stakeholders to access and exchange trade-related information and services. This portal offers functionalities such as electronic submission of trade documents, real-time tracking of shipments, automated customs processes, online payment options, and access to relevant trade regulations and guidelines. By leveraging digital technologies, the Trade Facilitation Portal enhances transparency, simplifies procedures, reduces paperwork, and promotes efficiency in cross-border trade, fostering collaboration and communication between traders and customs authorities, ultimately facilitating smoother and faster trade transactions within the customs environment.
Source: Based on World Customs Organization (WCO)
Example: Country ABC has implemented a Trade Facilitation Portal as a digital solution to streamline trade processes and enhance collaboration between traders and customs authorities. The portal provides a user-friendly interface where traders can electronically submit trade documents, such as import/export declarations, certificates of origin, and invoices. Customs authorities can efficiently process and review the submitted documents, reducing paperwork and manual interventions. The portal also enables real-time tracking of shipments, allowing traders to monitor the status and location of their goods. It provides access to up-to-date trade regulations, guidelines, and customs procedures, ensuring compliance and facilitating self-service by traders. Online payment options are integrated into the portal, enabling secure and convenient settlement of customs duties and fees. This Trade Facilitation Portal improves transparency, expedites customs processes, and fosters collaboration and efficiency in cross-border trade, benefiting both traders and customs authorities in Country ABC.
eira:iopDimension: Behavioral IoP
LOST view: TVA-Customs Trade Facilitation and Collaboration Enablers [Motivation]
eira:iopSaliency: The Digital Solution Service ABB is salient for technical interoperability because it is a central element the EIF's conceptual model for integrated public services. it represents the generalisation of all application services provided by an Interoperable European Solutionas as stated in the EIF: "Technical interoperability the applications and infrastructures linking systems and services."
Identifier: http://data.europa.eu/dr8/egovera/TradeFacilitationPortalApplicationService
ABB name: eira:DigitalSolutionApplicationService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-20
dct:identifier: http://data.europa.eu/dr8/egovera/TradeFacilitationPortalApplicationService
Description: The “Trusted IoT Connector”, developed by Fraunhofer AISEC allows for a secure usage of the Internet of Things even for critical processes. It ensures that only trustworthy and non-manipulated devices are used for crucial decisions. A secure execution environment, based on containers, enables the pre-processing of data by apps in the “Connector” itself. Through the enforcement of usage control, it is guaranteed that the data is only used for its designated purpose. In this way, new business models can securely be enabled within the Internet of Things.
Additional information: The Trusted Connector can be used to build secure embedded edge devices with or without hardware trust anchors, or as a cloud-based service for hosting demanding data analysis applications. It was designed with typical IIoT security requirements in mind, and offers a variety of features to protect data and ensure its integrity.
Example: The Trusted Connector could be used to secure a factory floor by ensuring that only trusted devices are allowed to connect to the network. It could also be used to protect sensitive data from unauthorized access, or to ensure that data is processed in compliance with regulations such as GDPR.
Publisher: Fraunhofer AISEC
Source: https://www.aisec.fraunhofer.de/content/dam/aisec/Dokumente/Flyer/Flyer_Trusted_IoT_Connector_engl.pdf
LOST view: TVA-Data Space Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/FraunhoferAISECTrustedConnectorApplicationService
EIRA traceability: eira:DigitalSolutionApplicationService
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-07-20
dct:identifier: http://data.europa.eu/dr8/egovera/FraunhoferAISECTrustedConnectorApplicationService
dct:title: Fraunhofer AISEC Trusted Connector Application Service
Description: Kubernetes is an open-source container orchestration platform that automates the deployment, scaling, and management of containerized applications. It provides a highly scalable and flexible environment for running, managing, and scaling applications across a cluster of machines.
Additional information: Kubernetes simplifies the management of containerized applications by abstracting away the underlying infrastructure complexities. It allows developers to define their application's desired state and Kubernetes takes care of deploying and maintaining that state. It provides features like automatic scaling, load balancing, self-healing, and rolling updates, ensuring high availability and fault tolerance. Kubernetes also enables efficient resource utilization by intelligently scheduling containers across the cluster based on resource requirements. It supports various container runtimes and can be deployed on-premises, in the cloud, or in hybrid environments.
Example: For example, a company running a microservices-based architecture can use Kubernetes to deploy and manage their containerized services. They can define the desired number of replicas for each service, specify resource requirements, and set up health checks. Kubernetes will then ensure that the desired state is maintained, automatically scaling the services based on demand, distributing traffic across replicas, and restarting failed containers. It provides a centralized control plane to monitor and manage the entire application infrastructure, making it easier to scale and update the system without downtime.
Publisher: Kubernetes.io
Source: https://kubernetes.io/docs/concepts/overview/what-is-kubernetes/
LOST view: TVA-Containerization Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/KubernetesApplicationService
EIRA traceability: eira:DigitalSolutionApplicationService
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-07-20
dct:identifier: http://data.europa.eu/dr8/egovera/KubernetesApplicationService
dct:title: Kubernetes Application Service
Description: An open source software for sovereign data exchange. It provides a set of modular components that can be used to connect different data spaces, support different transfer protocols, and manage data sharing and sovereignty.
Additional information: The Eclipse Dataspace Connector is a modular platform that can be used to build a variety of data exchange applications. It can be used to connect different data spaces, support different transfer protocols, and manage data sharing and sovereignty.
Example: For example, the Eclipse Dataspace Connector could be used to build an application that allows users to share data from different IoT devices. The application could use the Eclipse Dataspace Connector to connect to the different data spaces, transfer the data between the spaces, and manage the data sharing and sovereignty.
Publisher: Eclipse Foundation
Source: https://www.eclipse.org/dataspaceconnector/
LOST view: TVA-Data Space Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/EclipseDataspaceConnectorApplicationService
EIRA traceability: eira:DigitalSolutionApplicationService
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-07-20
dct:identifier: http://data.europa.eu/dr8/egovera/EclipseDataspaceConnectorApplicationService
dct:title: Eclipse Dataspace Connector Application Service
Definition: Data Governance is the overall management of the availability, usability, integrity, and security of data within an organization. It encompasses the people, processes, and technologies required to ensure that data is properly managed throughout its lifecycle, from creation or acquisition to deletion or archival.
Source: Techopedia
Source reference: https://www.techopedia.com/definition/12797/data-governance
Additional information: Data Governance involves establishing and enforcing policies, procedures, and standards to ensure that data is accurate, consistent, and reliable. It aims to provide a framework for decision-making, accountability, and responsibility related to data management. This concept ensures that data is treated as a valuable asset and is used effectively to support business objectives, regulatory compliance, and data privacy requirements. Data Governance also involves defining roles and responsibilities, implementing data quality controls, and establishing data stewardship practices.
Example: An example of Data Governance in action is when an organization implements a data governance framework to ensure that all employees follow standardized data entry procedures, adhere to data classification policies, and comply with data protection regulations. This framework may include data governance committees, data stewards, data quality assessments, and data access controls to ensure that data is managed consistently and securely across the organization.
LOST view: TVA-Data Management Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/DataGovernanceApplicationService
ABB name: egovera:DataGovernanceApplicationService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/egovera/DataGovernanceApplicationService
Name: Data Governance Application Service
Interoperability Layer: TechnicalApplication
Specialises: http://data.europa.eu/dr8/DigitalSolutionApplicationService
Definition: A Service Metadata Publisher is a service that allows users to create, publish, and manage metadata associated with services or resources. It provides a user-friendly interface accessible via the web, enabling users to input relevant information about their services, such as descriptions, capabilities, access policies, and quality metrics. The Service Metadata Publisher facilitates the documentation and dissemination of metadata, ensuring that service providers can effectively communicate the details and characteristics of their offerings to potential users. It may support various metadata standards and provide features for metadata editing, versioning, and publication.
Source: OASIS
LOST view: TVA-Functional Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/ServiceMetadataPublisherApplicationService
ABB name: egovera:ServiceMetadataPublisherApplicationService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/egovera/ServiceMetadataPublisherApplicationService
Interoperability Layer: TechnicalApplication
Specialises: http://data.europa.eu/dr8/DataPublicationApplicationService
Definition: Service Discovery and Registry ABB is an Application Service that enables the process of automatically locating network services within distributed digital systems.
Source: Inspired in INSPIRE
Source reference: https://inspire.ec.europa.eu/glossary/DiscoveryService
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): ZooKeeper - ZooKeeper is a centralized service registry for maintaining configuration information, naming, providing distributed synchronization, and providing group services. All of these kinds of services are used in some form or another by distributed applications. Each time they are implemented there is a lot of work that goes into fixing the bugs and race conditions that are inevitable. Because of the difficulty of implementing these kinds of services, applications initially usually skimp on them, which make them brittle in the presence of change and difficult to manage. Even when done correctly, different implementations of these services lead to management complexity when the applications are deployed. https://zookeeper.apache.org/
Interoperability Dimension: Structural IoP
LOST view: Technical view - application
Viewpoint: Key Interoperability Enablers viewpoint
Interoperability Saliency: Service Discovery and Registry Service ABB is a key interoperability enabler (*) for structural and behavioural interoperability by enabling access rights for data that is necessary for accessing public administration components to target fast and easy communication and data exchange.
Identifier: http://data.europa.eu/dr8/ServiceDiscoveryAndRegistryApplicationService
ABB name: eira:ServiceDiscoveryAndRegistryApplicationService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/ServiceDiscoveryAndRegistryApplicationService
Interoperability Layer: TechnicalApplication
Definition: Export procedure refers to the implementation of digital platforms and systems to streamline and automate the process of exporting goods. This service enables traders to electronically submit export declarations, relevant documentation, and trade data through a centralized online platform. The digital solution automates customs processes such as document verification, risk assessment, and export clearance. It facilitates electronic communication and data exchange between traders and customs authorities, reducing paperwork, improving accuracy, and expediting export procedures. By leveraging digital technologies, the Export procedure digital solution enhances trade facilitation, ensures compliance with customs regulations, and promotes efficient and secure cross-border trade within the customs environment.
Source: Based on World Customs Organization (WCO)
Example: In Country XYZ, a digital solution for export procedures has been implemented to streamline the export process and enhance trade facilitation. Traders now submit export declarations, required documentation, and trade data electronically through a centralized online platform. The digital solution automates customs processes such as document verification, risk assessment, and export clearance. It enables real-time communication and data exchange between traders and customs authorities, reducing paperwork, improving data accuracy, and expediting export procedures. This digital solution enhances transparency, ensures compliance with customs regulations, and promotes efficient and secure cross-border trade for exporters in Country XYZ.
eira:iopDimension: Behavioral IoP
LOST view: TVA-Customs Compliance and Regulatory Requirements Enablers [Motivation]
eira:iopSaliency: The Digital Solution Service ABB is salient for technical interoperability because it is a central element the EIF's conceptual model for integrated public services. it represents the generalisation of all application services provided by an Interoperable European Solutionas as stated in the EIF: "Technical interoperability the applications and infrastructures linking systems and services."
Identifier: http://data.europa.eu/dr8/egovera/ExportProcedureApplicationService
ABB name: eira:DigitalSolutionApplicationService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-20
dct:identifier: http://data.europa.eu/dr8/egovera/ExportProcedureApplicationService
Definition: Natural-Language Processing (NLP) is a field of artificial intelligence that focuses on the interaction between computers and humans through natural language. The ultimate objective of NLP is to enable computers to understand, interpret, and generate human language in a valuable way.
Source: TechTarget
Source reference: https://www.techtarget.com/searchenterpriseai/definition/natural-language-processing-NLP
Additional information: NLP encompasses a range of computational techniques that work together to allow computers to process and analyze large amounts of natural language data. The challenges in NLP involve speech recognition, natural language understanding, and natural language generation. NLP uses algorithms to identify and extract the rules such that the unstructured language data is converted into a form that computers can understand. When the data is structured, NLP can perform a variety of tasks, including translation, sentiment analysis, relationship extraction, recognition of named entities, and topic segmentation. Advances in machine learning and deep learning have significantly improved the effectiveness of NLP, enabling more complex applications and improving accuracy.
Example: Services like Google Translate and DeepL use NLP to provide real-time translation between languages.
Siri, Alexa, and Google Assistant use NLP to understand and respond to voice commands.
Businesses use NLP to analyze customer feedback on social media to determine overall sentiment towards products or services.
Websites often feature chatbots that use NLP to understand and respond to customer inquiries without human intervention.
NLP is used to automatically generate summaries of long documents, saving time for readers who need to quickly understand the main points.
Identifier: http://data.europa.eu/dr8/egovera/Natural-LanguageProcessingApplicationService
ABB name: egovera:Natural-LanguageProcessingApplicationService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/egovera/Natural-LanguageProcessingApplicationService
Name: Natural-Language Processing (NLP) Application Service
Interoperability Layer: TechnicalApplication
Specialises: http://data.europa.eu/dr8/DigitalSolutionApplicationService
Definition: Data Space Connector Consumer ABB is an Application Service that enables data gathering and accessibility over available data sources and data in terms of content, structure quality, actuality and other attributes.
Source: IDSA
Source reference: https://internationaldataspaces.org/offers/ids-components/
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): The Dataspace Connector from the International Data Spaces Association. https://international-data-spaces-association.github.io/DataspaceConnector/
Interoperability Dimension: Behavioral IoP
LOST view: TVA-Functional Architecture Principles
Interoperability Saliency: The Data Space Connector Consumer Application Service ABB is salient for technical interoperability because is the service that discovers and gather source for retrieving data. It is not just data, but the data space connector consumer service checks different characteristics and attributes from data such as content, and quality of the structure amongst others. This can be a clear and relevant role in the achievement of interoperability.
Identifier: http://data.europa.eu/dr8/DataspaceConnectorConsumerApplicationService
ABB name: eira:DataspaceConnectorConsumerApplicationService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/DataspaceConnectorConsumerApplicationService
Interoperability Layer: TechnicalApplication
Definition: Import procedure refers to the implementation of digital platforms and systems to streamline and automate the process of importing goods. This service enables traders to electronically submit import declarations, required documentation, and trade data through a centralized online platform. The digital solution automates customs processes such as document verification, risk assessment, and import clearance. It facilitates electronic communication and data exchange between traders and customs authorities, reducing paperwork, improving accuracy, and expediting import procedures. By leveraging digital technologies, the Import procedure digital solution enhances trade facilitation, ensures compliance with customs regulations, and promotes efficient and secure cross-border trade within the customs environment.
Source: Based on World Customs Organization (WCO)
Example: In Country XYZ, a digital solution was implemented to streamline import procedures and enhance trade facilitation. Traders were able to electronically submit import declarations, required documentation, and trade data through a centralized online platform. The digital solution automated customs processes such as document verification, risk assessment, and import clearance. It facilitated real-time communication and data exchange between traders and customs authorities, reducing paperwork, improving data accuracy, and expediting import procedures. This digital solution improved transparency, ensured compliance with customs regulations, and promoted efficient and secure cross-border trade for importers in Country XYZ.
eira:iopDimension: Behavioral IoP
LOST view: TVA-Customs Compliance and Regulatory Requirements Enablers [Motivation]
eira:iopSaliency: The Digital Solution Service ABB is salient for technical interoperability because it is a central element the EIF's conceptual model for integrated public services. it represents the generalisation of all application services provided by an Interoperable European Solutionas as stated in the EIF: "Technical interoperability the applications and infrastructures linking systems and services."
Identifier: http://data.europa.eu/dr8/egovera/ImportProcedureApplicationService
ABB name: eira:DigitalSolutionApplicationService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-20
dct:identifier: http://data.europa.eu/dr8/egovera/ImportProcedureApplicationService
Definition: An Anonymization Application Service refers to a software solution or service that enables the anonymization of sensitive or personally identifiable information (PII) within datasets. It applies techniques to transform or remove identifiable information while preserving the usability and integrity of the data. The purpose of the Anonymization Application Service is to protect privacy, comply with data protection regulations, and enable the secure use and sharing of data for analysis or research purposes.
Source: IEEE Software
Source reference: https://ieeexplore.ieee.org/document/8484865
LOST view: TVA-Privacy Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/AnonymisationApplicationService
ABB name: egovera:AnonymisationApplicationService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/egovera/AnonymisationApplicationService
Interoperability Layer: TechnicalApplication
Specialises: http://data.europa.eu/dr8/egovera/AnonymisationServiceApplicationService
Definition: UX Management Service ABB is Application Service managing user experience design-related activities inside an organization to create growth and good management practices. Typical UX management activities are to define an organization’s UX design language and strategy and manage the work processes around UX design.
Source: Interaction design
Source reference: (https://www.interaction-design.org/literature/topics/ux-management)
LOST view: Technical view - application
Identifier: http://data.europa.eu/dr8/UXManagementService
Identifier: http://data.europa.eu/dr8/UXManagementApplicationService
eira:ID: ABB484
ABB name: eira:UXManagementApplicationService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2022-23-01
Definition: CRM (Customer Relationship Management) as a web service refers to a set of APIs (Application Programming Interfaces) that enable the integration and utilization of CRM functionality within external applications or systems. It provides developers with the means to access and interact with CRM capabilities, such as customer data retrieval, data update, customer interaction tracking, and more. By exposing CRM functionality as a web service, organizations can achieve seamless interoperability and enhance customer engagement by integrating CRM features into various channels, platforms, and services.
Source: IEEE Xplore
LOST view: TVA-Functional Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/CRMApplicationService
ABB name: egovera:CRMApplicationService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/egovera/CRMApplicationService
Interoperability Layer: TechnicalApplication
Specialises: http://data.europa.eu/dr8/DataManagementApplicationService
Definition: Request Validation ABB is an Application Service that enables the process of verifying that the data sent to a web server from a client is safe and meets the expected format and standards.
Source: Inspired in CORS
Source reference: https://ec.europa.eu/eurostat/cros/content/validation-levels_en
Example: The following implementation is an example of how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): HORIZON 2020 Organisation's validation service https://ec.europa.eu/research/participants/docs/h2020-funding-guide/grants/applying-for-funding/register-an-organisation/validation-of-organisation_en.htm
Interoperability Dimension: Structural IoP
LOST view: Technical view - application
Viewpoint: Interoperability Security viewpoint
Interoperability Saliency: The Request Validation Application Service ABB is salient for interoperability because as a web service, it can ensure and validate if exchanged data is secured and meets the standards and specifications required. The validation can play a relevant role to ensure the health of systems and services and also the quality of information being exchanged between interoperable services.
Identifier: http://data.europa.eu/dr8/RequestValidationApplicationService
ABB name: eira:RequestValidationApplicationService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/RequestValidationApplicationService
Interoperability Layer: TechnicalApplication
Description: Red Hat OpenShift is a container application platform that enables developers to build, deploy, and manage applications across various cloud environments. It provides a consistent and secure foundation for developing and scaling applications, allowing teams to focus on delivering value rather than managing infrastructure. OpenShift utilizes Kubernetes orchestration to automate the deployment, scaling, and management of containerized applications.
Additional information: Red Hat OpenShift simplifies the process of developing, deploying, and scaling applications by providing a comprehensive platform that abstracts away the underlying infrastructure complexities. It offers a self-service environment for developers to easily create and deploy applications using containers, which encapsulate the application and its dependencies. OpenShift provides features like automated scaling, load balancing, and continuous integration/continuous deployment (CI/CD) pipelines, enabling teams to rapidly iterate and deliver software. It also offers built-in security features, such as role-based access control (RBAC) and image scanning, to ensure the integrity and compliance of applications. With its support for multiple cloud providers and on-premises environments, OpenShift offers flexibility and portability for applications across different infrastructures.
Example: An example of using Red Hat OpenShift is a development team building a microservices-based application. They can leverage OpenShift to create and manage containers for each microservice, allowing independent development and scaling of individual components. OpenShift's built-in CI/CD capabilities enable automated testing and deployment of new versions, ensuring a streamlined development process. The team can easily scale the application horizontally by adding more container instances as needed, and OpenShift's load balancing features distribute the traffic efficiently. With OpenShift's portability, the team can seamlessly deploy the application across different cloud providers or on-premises environments, adapting to changing business needs.
Publisher: Red Hat
Source: https://www.redhat.com/en/technologies/cloud-computing/openshift
LOST view: TVA-Containerization Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/RedHatOpenShiftApplicationService
EIRA traceability: eira:DigitalSolutionApplicationService
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-07-20
dct:identifier: http://data.europa.eu/dr8/egovera/RedHatOpenShiftApplicationService
dct:title: Red Hat OpenShift Application Service
Definition: e-Timestamp Creation ABB is an Application Service that enables the recording of the date and time when a specific electronic document, data or transaction is created or modified. This ABB verifies the existence, integrity, and authenticity of an electronic document, data or transaction.
Source: eIDAS - 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.
Source reference: http://eur-lex.europa.eu/legal-content/EN/TXT/?uri=uriserv%3AOJ.L_.2014.257.01.0073.01.ENG
Additional information: An ‘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.
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): DigiStamp eTimeStamp® - DigiStamp eTimeStamp® protects the intellectual property in any computer file: • Use Desktop and Web applications for on-demand protection; • Plug the Timestamp Authority into the automated systems. Plug-in rigorous implementation of US & EU standards: • Secure, reliable, RFC 3161 timestamp cloud service; • Archiving and Hash Chaining keyless security; • Elliptic Curve Upgrade; Implementation of the Internet Engineering Task Force's RFC 3161 means DigiStamp timestamps are understood by data validation systems the world over: • Implementation of ANSI X9.95 further increases the compatibility of our timestamps; • Compliance with IETF RFC 3628 gives credence to the trustworthiness of our Time Stamp Authorities.; • Conformance to IETF RFC 3126 makes our timestamps usable for long-term, legally binding agreements. https://www.digistamp.com/
Interoperability Dimension: Structural IoP
LOST view: Technical view - application
Viewpoint: Interoperability Security viewpoint
Interoperability Saliency: The e-Timestamp Creation Service ABB is salient for technical interoperability because it provides the functionalities required for e-Timestamp creation service.
Identifier: http://data.europa.eu/dr8/E-TimestampCreationApplicationService
ABB name: eira:E-TimestampCreationApplicationService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/E-TimestampCreationApplicationService
Interoperability Layer: TechnicalApplication
Definition: e-Archiving ABB is an Application Service enabling the permanent or long-term storage of selected (by an authority) electronic documents or information for preservation purposes like their enduring research value and memory aid.
Source: ISA2 - EIA Action
Source reference: https://ec.europa.eu/isa2/actions/towards-european-interoperability-architecture_en/
Synonym: Preservation Service
Additional information: The EIRA(c) 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 proof 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”.
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): CEF eArchiving: eArchiving provides the core specifications, software, training and knowledge to tackle the challenge of short, medium and long-term data management and reuse in a sustainable, authentic, cost-efficient, manageable and interoperable way. https://ec.europa.eu/cefdigital/wiki/display/CEFDIGITAL/eArchiving
Interoperability Dimension: Structural IoP
LOST view: Technical view - application
Viewpoint: Interoperability Privacy viewpoint
Interoperability Saliency: The e-Archiving Service ABB is salient for technical interoperability because it provides and shares the functionality for the long-term or permanent preservation of records and information in electronic form in order to ensure their temporal egibility, reliability and integrity as stated in the EIF: "Legislation requires that decisions and data are stored and can be accessed for a specified time. This means that records and information in electronic form held by public administrations for the purpose of documenting procedures and decisions must be preserved and be converted, where necessary, to new media when old media become obsolete. The goal is to ensure that records and other forms of information keep their legibility, reliability and integrity and can be accessed as long as needed subject to security and privacy provisions."
Identifier: http://data.europa.eu/dr8/E-ArchivingApplicationService
ABB name: eira:E-ArchivingApplicationService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/E-ArchivingApplicationService
Interoperability Layer: TechnicalApplication
Definition: The Data Integration Plugins Manager is a software component that facilitates the management and integration of various plugins within a data integration system. It provides a centralized platform for installing, configuring, and maintaining plugins, allowing users to easily extend the functionality of their data integration workflows.
Source: Techopedia
Source reference: https://www.techopedia.com/definition/32662/data-integration
Additional information: The Data Integration Plugins Manager acts as a repository for plugins, which are software modules that enhance the capabilities of the data integration system. It allows users to discover, install, and update plugins seamlessly, eliminating the need for manual installation and configuration. The manager provides a user-friendly interface to browse available plugins, view their descriptions, and manage their settings. It also ensures compatibility between plugins and the data integration system, preventing conflicts and ensuring smooth integration. The Data Integration Plugins Manager simplifies the process of extending the functionality of a data integration system, enabling users to tailor their workflows to specific requirements and integrate with a wide range of data sources and systems.
Example: An example of the Data Integration Plugins Manager in action is a data integration platform used by a marketing team. The manager allows the team to easily add plugins for social media data extraction, CRM integration, and email campaign automation. They can browse the available plugins, select the ones that suit their needs, and install them with a few clicks. The manager ensures that the plugins are compatible with the data integration platform and provides options to configure their settings. With the Data Integration Plugins Manager, the marketing team can quickly enhance their data integration workflows, streamline their processes, and gain valuable insights from various data sources.
LOST view: TVA-Data Management Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/DataIntegrationPluginsManagerApplicationService
ABB name: egovera:DataIntegrationPluginsManagerApplicationService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/egovera/DataIntegrationPluginsManagerApplicationService
Name: Data Integration Plugins Manager Application Service
Interoperability Layer: TechnicalApplication
Specialises: http://data.europa.eu/dr8/DigitalSolutionApplicationService
Description: The Intel IONOS Orbiter Connector is an implementation of the Eclipse Dataspace Connector (EDC) specification. It is designed to be interoperable with other EDC-compliant connectors, allowing for the secure and federated sharing of data across different data spaces.
Additional information: It is based on the Eclipse Dataspace Connector (EDC) specification, which is an open standard for connecting data spaces. It is designed to be interoperable with other EDC-compliant connectors, allowing for the secure and federated sharing of data across different data spaces.It is implemented in Java and can be deployed on a variety of platforms, including on-premises servers, cloud platforms, and edge devices. It is available as a free and open source software project. The Intel IONOS Orbiter Connector is a valuable tool for organizations that need to share data securely and efficiently across different data spaces. It is easy to use and deploy, and it is compatible with a wide range of platforms.
Example: The Intel IONOS Orbiter Connector could be used to connect a data space for automotive data with a data space for energy data. This would allow for the sharing of data about vehicle emissions and energy consumption, which could be used to improve the efficiency of transportation systems.
Publisher: Intel
Source: https://www.intel.com/content/www/us/en/homepage.html
LOST view: TVA-Data Space Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/IntelIONOSOrbiterConnectorApplicationService
EIRA traceability: eira:DigitalSolutionApplicationService
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-07-20
dct:identifier: http://data.europa.eu/dr8/egovera/IntelIONOSOrbiterConnectorApplicationService
dct:title: Intel IONOS Orbiter Connector Application Service
eira:iopDimension: Behavioral IoP
LOST view: TVA-Customs Compliance and Regulatory Requirements Enablers [Motivation]
eira:iopSaliency: The Digital Solution Service ABB is salient for technical interoperability because it is a central element the EIF's conceptual model for integrated public services. it represents the generalisation of all application services provided by an Interoperable European Solutionas as stated in the EIF: "Technical interoperability the applications and infrastructures linking systems and services."
Identifier: http://data.europa.eu/dr8/egovera/ComplianceRequirementsChecksApplicationService
ABB name: eira:DigitalSolutionApplicationService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-20
dct:identifier: http://data.europa.eu/dr8/egovera/ComplianceRequirementsChecksApplicationService
Definition: Machine Translation ABB is an Application Service that enables the procedures for automated translation of text, metadata and concept classes or nomenclatures
Source: CEF Automated Translation
Source reference: https://ec.europa.eu/digital-single-market/en/news/tools-and-resources-cef-automated-translation
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): CEF Digital - eTranslation building block: eTranslation is a Connecting Europe Facility (CEF) building block provided by the European Commission (EC). eTranslation provides an online machine translation service.(https://ec.europa.eu/cefdigital/wiki/display/CEFDIGITAL/eTranslation)
Interoperability Dimension: Structural IoP
LOST view: Technical view - application
Interoperability Saliency: The Machine Translation Service ABB is salient for technical interoperability because it enables cross-lingual functionality by providing automated translation of text, metadata and concept classes or nomenclatures as stated in the EIF recommendation n°16: "Use information systems and technical architectures that cater for multilingualism when establishing a European public service. Decide on the level of multilingualism support based on the needs of the expected users."
Identifier: http://data.europa.eu/dr8/MachineTranslationApplicationService
ABB name: eira:MachineTranslationApplicationService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/MachineTranslationApplicationService
Interoperability Layer: TechnicalApplication
Definition: e-Signature Verification and Validation Service ABB is an Application Service that enables the process of verifying and confirming that an electronic signature or a seal is valid.
Source: eIDAS - 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.
Source reference: http://eur-lex.europa.eu/legal-content/EN/TXT/?uri=uriserv%3AOJ.L_.2014.257.01.0073.01.ENG
Additional information: 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. ‘Validation’ means the process of verifying and confirming that an electronic signature or a seal is valid.
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): CEF eSignature DSS - DSS (Digital Signature Services) is an open-source software library for electronic signature creation and validation. DSS supports the creation and verification of interoperable and secure electronic signatures in line with European legislation. In particular, DSS aims to follow the eIDAS Regulation and related standards closely. DSS can be re-used in an IT solution for electronic signatures to ensure that signatures are created and verified in line with European legislation and standards. DSS allows re-use in a variety of different ways: in an applet, in a stand-alone application or in a server application. DSS can also be used as a reference implementation for IT solutions which do not directly re-use it. CEF eSignature's DSS open-source library delivers the following benefits to its users: • Open-source software under LGPL 2.1, a non-viral open source license; • Interoperability of the e-signatures; • Supports both e-signatures and e-seals; • Validation of countersignatures and multiple signatures; • Alignment with the eIDAS Regulation and related standards; • Supports EU standards on: o Signature formats and packaging methods; o Signature validation procedures; • Validation relying on Member States' trusted lists: o Status of trust service providers/trust service, compensation of information, path validation. https://ec.europa.eu/cefdigital/wiki/display/CEFDIGITAL/eSignaturefile:///C:/Users/bocquilp/Downloads/DSS(ServiceOfferingDescription)%20(v0.03)%20(5).pdf
Interoperability Dimension: Structural IoP
LOST view: Technical view - application
Viewpoint: Interoperability Security viewpoint
Interoperability Saliency: The e-Signature Verification and Validation Service ABB is salient for technical interoperability because it provides the functionalities required for e-signature verification and validation service.
Identifier: http://data.europa.eu/dr8/E-SignatureVerificationAndValidationApplicationService
ABB name: eira:E-SignatureVerificationAndValidationApplicationService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/E-SignatureVerificationAndValidationApplicationService
Interoperability Layer: TechnicalApplication
Description: The Interoperability Test Bed is a service offered by the European Commission’s DIGIT to facilitate the conformance testing of IT systems. The Test Bed is itself a software system that can be both downloaded and installed locally, but also reused through a shared online installation operated by DIGIT. It offers an intuitive web user interface that allows administrators to define their project’s overall testing setup as well as users to connect and run tests.
Publisher: DIGIT, Interoperable Europe Initiative
Source: https://joinup.ec.europa.eu/collection/interoperability-test-bed-repository/solution/interoperability-test-bed/about#:~:text=The%20Interoperability%20Test%20Bed%20is%20a%20service%20offered,through%20a%20shared%20online%20installation%20operated%20by%20DIGIT.
LOST view: TVA-Test Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/EuropeanInteroperabilityTestBedApplicationService
EIRA traceability: eira:ConformanceTestingApplicationService
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2022-01-18
dct:identifier: http://data.europa.eu/dr8/ConformanceTestingApplicationService
Definition: Data Extraction, Transformation, and Loading ABB is an Application Service that enables the processes to extract data from various sources, transform the data to specific data models and load the data into a target data store.
Source: Inspired in definitions from referent companies of IT sector
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): Eurostat transformation service - The transformation service allows datasets to be converted from one file format to another, optionally performing additional tasks, such as mapping and transcoding. The service is operational but is currently only available for internal consumption within Eurostat. However, the source code of both web service and software component is available in the SDMX webspace: http://ec.europa.eu/eurostat/web/sdmx-infospace/validation-transformation/transformation-services
Interoperability Dimension: Structural IoP
LOST view: Technical view - application
Viewpoint: Interoperability Privacy viewpoint
Interoperability Saliency: The Data Extraction, Transformation, and Loading Service ABB is salient for technical interoperability because it provides the functionalities to transform internal data structures to common and agreed interoperable formats as stated in the EIF recommendation n° 41: "Establish procedures and processes to integrate the opening of data in your common business processes, working routines, and in the development of new information systems."
Identifier: http://data.europa.eu/dr8/DataExtractionTransformationAndLoadingApplicationService
ABB name: eira:DataExtractionTransformationAndLoadingApplicationService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/DataExtractionTransformationAndLoadingApplicationService
Interoperability Layer: TechnicalApplication
Definition: Containers Orchestrator is a software tool or platform that automates the deployment, management, and scaling of containerized applications. It provides a centralized control plane to efficiently manage and coordinate the deployment and operation of containers across a cluster of machines or nodes.
Source: Wikipedia
Source reference: https://en.wikipedia.org/wiki/Container_orchestration
Additional information: Containers Orchestrator simplifies the management of containerized applications by abstracting away the underlying infrastructure complexities. It enables efficient resource utilization, load balancing, high availability, and fault tolerance. The orchestrator handles tasks such as container scheduling, service discovery, networking, storage management, and health monitoring. It allows developers to focus on application development and deployment, while ensuring scalability, resilience, and ease of management.
Example: One popular example of a Containers Orchestrator is Kubernetes. It provides a robust and scalable platform for managing containerized applications. With Kubernetes, developers can define the desired state of their application using declarative configuration files, and the orchestrator takes care of deploying and managing the containers accordingly. It offers features like automatic scaling, rolling updates, service discovery, and load balancing, making it easier to deploy and manage applications in a distributed environment.
LOST view: TVA-Containerization Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/ContainersOrchestratorApplicationService
EIRA traceability: eira:DigitalSolutionApplicationService
ABB name: egovera:ContainersOrchestratorApplicationService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-07-20
dct:identifier: http://data.europa.eu/dr8/egovera/ContainersOrchestratorApplicationService
dct:title: Containers Orchestrator Application Service
Definition: A Knowledge Management Application Service is a software application or service that supports the processes of capturing, organizing, storing, retrieving, and sharing knowledge within an organization. It provides functionalities and tools to facilitate knowledge creation, acquisition, categorization, search, collaboration, and dissemination. The Knowledge Management Application Service typically includes features such as knowledge repositories, document management, collaboration platforms, content categorization, search capabilities, expertise location, and best practice sharing. It enables employees or users to access and leverage the organization's knowledge assets effectively, fostering innovation, decision-making, and continuous learning.
Source: International Journal of Computer Science Issues (IJCSI)
Source reference: http://ijcsi.org/papers/IJCSI-8-2-1-179-186.pdf
LOST view: TVA-Knowledge Discovery Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/KnowledgeManagementApplicationService
ABB name: egovera:KnowledgeManagementApplicationService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/egovera/KnowledgeManagementApplicationService
Interoperability Layer: TechnicalApplication
Specialises: http://data.europa.eu/dr8/DataManagementApplicationService
Definition: A Workflow Management Application Service, also known as Orchestration Application Service, refers to a software solution or service that enables the design, execution, and coordination of workflows within an organization. It provides a centralized platform for modeling, automating, and monitoring business processes, ensuring efficient and effective workflow execution. The Workflow Management Application Service typically includes features such as workflow design and modeling, task assignment and tracking, process monitoring and optimization, exception handling, and integration with other systems and applications.
Source: Gartner
Source reference: https://www.gartner.com/en/information-technology/glossary/workflow-orchestration
LOST view: TVA-Orchestration Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/WorkflowManagementApplicationService
ABB name: egovera:WorkflowManagementApplicationService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/egovera/WorkflowManagementApplicationService
Interoperability Layer: TechnicalApplication
Specialises: http://data.europa.eu/dr8/OrchestrationApplicationService
Definition: Trusted Digital Repositories refer to specialized eArchiving application services that are designed to preserve and provide long-term access to digital objects, such as documents, datasets, multimedia files, and other forms of digital content. These repositories follow established standards, best practices, and guidelines to ensure the integrity, authenticity, and usability of the archived materials over time. They employ robust storage, metadata management, and preservation strategies to safeguard the long-term viability and accessibility of digital assets. Trusted Digital Repositories play a crucial role in the preservation and curation of digital heritage, research data, and other valuable digital resources.
Source: ISO
LOST view: TVA-Functional Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/TrustedDigitalRepositoriesApplicationService
ABB name: egovera:TrustedDigitalRepositoriesApplicationService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/egovera/TrustedDigitalRepositoriesApplicationService
Interoperability Layer: TechnicalApplication
Specialises: http://data.europa.eu/dr8/E-ArchivingApplicationService
Description: Apache Beam is an open-source unified programming model and set of tools for building batch and streaming data processing pipelines. It provides a high-level API that allows developers to write data processing logic once and execute it on various distributed processing backends, such as Apache Flink, Apache Spark, and Google Cloud Dataflow. Beam's model allows for both batch and streaming data processing, enabling developers to handle real-time data as well as large-scale batch data in a consistent manner.
Additional information: Apache Beam simplifies the development of data processing pipelines by providing a portable and expressive programming model. It allows developers to focus on the logic of their data transformations without worrying about the underlying execution engine. Beam's model supports a wide range of data processing patterns, including filtering, aggregating, joining, and transforming data. It also provides built-in support for windowing, allowing developers to handle time-based computations efficiently. With its ability to run on multiple execution engines, Apache Beam offers flexibility and scalability for processing data at any scale.
Example: An example of using Apache Beam is to process a stream of user activity data in real-time. The pipeline can read the incoming data, apply transformations such as filtering and aggregating, and then write the results to a database or generate alerts based on certain conditions. Another example is processing a large batch of log files to extract relevant information, perform analytics, and store the results in a data warehouse. Apache Beam's unified programming model allows developers to write these pipelines once and run them on different execution engines, making it easier to switch between batch and streaming processing or migrate to a different backend without rewriting the entire pipeline.
Publisher: Apache Beam Documentation
Source: https://beam.apache.org/documentation/
LOST view: TVA-Orchestration Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/ApacheBeamApplicationService
EIRA traceability: eira:DigitalSolutionApplicationService
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-07-20
dct:identifier: http://data.europa.eu/dr8/egovera/ApacheBeamApplicationService
dct:title: Apache Beam Application Service
Definition: Expeditions controls refers to the use of digital tools and technologies to enhance the monitoring, tracking, and control of goods throughout the transportation and logistics process. This service involves the implementation of digital systems, such as Electronic Data Interchange (EDI), Global Positioning System (GPS), and Internet of Things (IoT) devices, to enable real-time visibility and management of expeditions. The digital solution provides customs authorities with accurate and timely information on the movement, location, and condition of goods, facilitating efficient risk assessment, inspection prioritization, and trade facilitation. By automating expeditions controls, this service improves supply chain security, reduces transit times, enhances customs compliance, and ensures the smooth flow of goods across borders within the customs environment.
Source: Based on World Customs Organization (WCO)
Example: In the customs department of Country ABC, a digital solution for expeditions controls has been implemented to enhance the monitoring and tracking of goods during transportation. IoT devices are attached to shipments, providing real-time location tracking and environmental condition monitoring. The system integrates with customs databases and utilizes advanced analytics to analyze the data collected from the IoT devices. Customs officers can access a centralized dashboard that displays real-time information on the movement, status, and compliance of goods in transit. By automating expeditions controls, this digital solution improves customs risk assessment capabilities, enables targeted inspections, reduces transit times, and enhances trade facilitation. It enhances supply chain visibility, strengthens security measures, and ensures the efficient and compliant movement of goods across borders in Country ABC.
eira:iopDimension: Behavioral IoP
LOST view: TVA-Customs Process Streamlining and Efficiency Enablers [Motivation]
eira:iopSaliency: The Digital Solution Service ABB is salient for technical interoperability because it is a central element the EIF's conceptual model for integrated public services. it represents the generalisation of all application services provided by an Interoperable European Solutionas as stated in the EIF: "Technical interoperability the applications and infrastructures linking systems and services."
Identifier: http://data.europa.eu/dr8/egovera/ExpeditionsControlsApplicationService
ABB name: eira:DigitalSolutionApplicationService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-20
dct:identifier: http://data.europa.eu/dr8/egovera/ExpeditionsControlsApplicationService
Definition: Metadata Management ABB is an Application Service that enables functionalities for the i) creation, ii) storage, iii) categorisation and iv) retrieval of metadata.
Source: DAMA
Source reference: http://www.dama.org/
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): Eurostat SDMX repository: The Euro SDMX Registry is Eurostat’s implementation of an SDMX registry to facilitate the exchange of statistical data and metadata by serving as a metadata repository. It stores the SDMX artefacts needed for the parties to access and interpret the content of the exchanged statistical data and metadata sets. http://ec.europa.eu/eurostat/web/sdmx-infospace/sdmx-it-tools/sdmx-registry
Interoperability Dimension: Structural IoP
LOST view: Technical view - application
Viewpoint: Interoperability Privacy viewpoint
Interoperability Saliency: The Metadata management Service ABB is salient for interoperability because it provides and shares the functionalities to manage metadata. EIF recommends to prioritise it: "Put in place an information management strategy at the highest possible level to avoid fragmentation and duplication. Management of metadata, master data and reference data should be prioritised".
Identifier: http://data.europa.eu/dr8/MetadataManagementApplicationService
ABB name: eira:MetadataManagementApplicationService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/MetadataManagementApplicationService
Interoperability Layer: TechnicalApplication
Definition: A Big Data Analytics Application service refers to a software application or platform that leverages advanced analytics techniques to process and analyze large and complex datasets, commonly known as big data. It enables organizations to derive valuable insights, identify patterns, trends, and correlations, and make data-driven decisions. The service typically includes data ingestion, storage, processing, and visualization capabilities, as well as advanced analytics techniques such as machine learning, natural language processing, and predictive modeling.
Source: NIST
LOST view: TVA-Analytics Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/BigDataAnalyticsApplicationService
ABB name: egovera:BigDataAnalyticsApplicationService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/egovera/BigDataAnalyticsApplicationService
Interoperability Layer: TechnicalApplication
Specialises: http://data.europa.eu/dr8/DataAnalyticsApplicationService
Definition: A Data Policy Engine is an IT concept that refers to a software component or system responsible for enforcing data policies and rules within an organization. It acts as a centralized control point for managing and governing data access, usage, and security based on predefined policies.
Source: Techopedia
Source reference: https://www.techopedia.com/definition/32545/data-policy-engine-dpe
Additional information: The Data Policy Engine enables organizations to define and enforce data policies consistently across various data sources, applications, and user roles. It provides a flexible framework to create and manage policies related to data privacy, data sharing, data retention, data classification, and more. The engine evaluates incoming data requests against the defined policies and applies appropriate actions or restrictions. It helps organizations ensure compliance with regulatory requirements, maintain data integrity, and mitigate risks associated with unauthorized data access or misuse.
Example: An example of the application of a Data Policy Engine is in a healthcare organization. The engine can be used to enforce policies that restrict access to patient medical records based on the user's role and the sensitivity of the data. It can also enforce policies related to data anonymization when sharing data with external research organizations. The Data Policy Engine ensures that only authorized individuals can access and use patient data, and it provides an audit trail for monitoring and reporting data access activities.
LOST view: TVA-Data Management Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/DataPolicyEngineApplicationService
ABB name: egovera:DataPolicyEngineApplicationService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/egovera/DataPolicyEngineApplicationService
Name: Data Policy Engine Application Service
Interoperability Layer: TechnicalApplication
Specialises: http://data.europa.eu/dr8/DigitalSolutionApplicationService
Description: The eIDAS-Node software is a sample implementation of the eID eIDAS Profile. It was developed by the European Commission with the help of Member States collaborating in the technical sub-committee of the eIDAS Expert Group. The eIDAS-Node software contains the necessary modules to help Member States to communicate with other eIDAS-compliant counterparts in a centralised or distributed fashion.
Publisher: European Commission
Source: https://ec.europa.eu/digital-building-blocks/wikis/display/DIGITAL/eIDAS-Node+version+2.6
LOST view: TVA-Identification and Access Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/EIDAS-NodeApplicationService
EIRA traceability: eira:IdentityMangementApplicationService
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-08-20
dct:identifier: http://data.europa.eu/dr8/egovera/EIDAS-NodeApplicationService
Definition: API Discovery and Catalogue Service ABB is an Application Service that enables the discovery and/or maintenance of the API Catalogue ABB.
Source: Inspired in Gartner
Source reference: https://www.gartner.com/en/information-technology/glossary/application-programming-interface
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): RapidAPI - RapidAPI is a collection of predefined APIs that are free to test, specifically updated for 2021. https://rapidapi.com/collection/list-of-free-apis
Interoperability Dimension: Structural IoP
LOST view: Technical view - application
Viewpoint: Key Interoperability Enablers viewpoint
Interoperability Saliency: API Discovery and Catalogue Application Service ABB is a key interoperability enabler (*) for structural and behavioural interoperability by enabling and maintaining API Catalogues for public administration services. This is a key aspect enabling interoperability as it contributes to the discovery of APIs through catalogues.
Identifier: http://data.europa.eu/dr8/APIDiscoveryAndCatalogueApplicationService
ABB name: eira:APIDiscoveryAndCatalogueApplicationService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/APIDiscoveryAndCatalogueApplicationService
Interoperability Layer: TechnicalApplication
Definition: Knowledge Discovery ABB is an Application Service that enables a highly complex process where a lot of data manipulation tools with different characteristics have to be used together to reach the goal of previously unknown, potentially useful information extraction.
Source: Inspired in EUROSTAT
Source reference: https://ec.europa.eu/eurostat/statistics-explained/index.php?title=Glossary:Knowledge-intensive_services_(KIS)
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): CELLAR. Cellar metadata is stored in a knowledge graph, and more specifically in a triple store. A SPARQL interface is used to query the metadata. https://op.europa.eu/en/web/cellar/cellar-data/metadata/knowledge-graph
Interoperability Dimension: Structural IoP
LOST view: Technical view - application
Interoperability Saliency: The Knowledge Discovery Application Service ABB is salient for technical interoperability because it performs a series of complex processes that incorporate multiple data channels, formats and characteristics that are processed to extract relevant information to be used by other digital public services.
Identifier: http://data.europa.eu/dr8/KnowledgeDiscoveryApplicationService
ABB name: eira:KnowledgeDiscoveryApplicationService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/KnowledgeDiscoveryApplicationService
Interoperability Layer: TechnicalApplication
Description: The European Blockchain Services Infrastructure (EBSI) is an IT concept that aims to provide a secure and scalable infrastructure for blockchain-based services across Europe. It is a network of distributed nodes that enables the interoperability of different blockchain platforms and facilitates the development and deployment of blockchain applications in various domains.
Additional information: The EBSI is being developed by the European Commission in collaboration with member states and industry partners. It aims to promote the adoption of blockchain technology in the public sector by providing a trusted and efficient infrastructure. The EBSI leverages blockchain's decentralized and immutable nature to enhance transparency, security, and trust in digital transactions. It enables the creation of smart contracts, digital identity management, supply chain traceability, and other applications that require secure and tamper-proof data exchange. The EBSI also supports the integration of existing systems and services, ensuring seamless interoperability between different blockchain networks.
Example: One example of the application of the EBSI is in the field of public procurement. By utilizing blockchain technology, the EBSI can enable transparent and auditable procurement processes, reducing fraud and increasing efficiency. It can provide a secure and tamper-proof record of all transactions, ensuring the integrity of the procurement process. Additionally, the EBSI can facilitate cross-border transactions, allowing suppliers from different countries to participate in procurement procedures without the need for complex paperwork and intermediaries.
Publisher: European Commission
Source: https://ec.europa.eu/cefdigital/wiki/display/CEFDIGITAL/European+Blockchain+Services+Infrastructure
LOST view: TVA-Trust Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/EuropeanBlockchainServicesInfrastructureApplicationService
EIRA traceability: eira:DigitalSolutionApplicationService
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-07-25
dct:identifier: http://data.europa.eu/dr8/egovera/EuropeanBlockchainServicesInfrastructureApplicationService
dct:title: European Blockchain Services Infrastructure Application Service
Definition: e-Seal Creation ABB is an Application Service that enables to sign of data in electronic forms on behalf of a legal person
Source: eIDAS - 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.
Source reference: http://eur-lex.europa.eu/legal-content/EN/TXT/?uri=uriserv%3AOJ.L_.2014.257.01.0073.01.ENG
Additional information: 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.
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): CEF eSignature DSS - DSS (Digital Signature Services) is an open-source software library for electronic signature creation and validation. DSS supports the creation and verification of interoperable and secure electronic signatures in line with European legislation. In particular, DSS aims to follow the eIDAS Regulation and related standards closely. DSS can be re-used in an IT solution for electronic signatures to ensure that signatures are created and verified in line with European legislation and standards. DSS allows re-use in a variety of different ways: in an applet, in a stand-alone application or in a server application. DSS can also be used as a reference implementation for IT solutions which do not directly re-use it. CEF eSignature's DSS open-source library delivers the following benefits to its users: • Open-source software under LGPL 2.1, a non-viral open source license; • Interoperability of the e-signatures; • Supports both e-signatures and e-seals; • Validation of countersignatures and multiple signatures; • Alignment with the eIDAS Regulation and related standards; • Supports EU standards on: o Signature formats and packaging methods; o Signature validation procedures; • Validation relying on Member States' trusted lists: o Status of trust service providers/trust service, compensation of information, path validation. https://ec.europa.eu/cefdigital/wiki/display/CEFDIGITAL/eSignaturefile:///C:/Users/bocquilp/Downloads/DSS(ServiceOfferingDescription)%20(v0.03)%20(5).pdf
Interoperability Dimension: Structural IoP
LOST view: Technical view - application
Viewpoint: Interoperability Security viewpoint
Interoperability Saliency: The e-Seal Creation Service ABB is salient for technical interoperability because it provides the functionalities required for e-seal creation service.
Identifier: http://data.europa.eu/dr8/E-SealCreationApplicationService
ABB name: eira:E-SealCreationApplicationService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/E-SealCreationApplicationService
Interoperability Layer: TechnicalApplication
Definition: A Learning Platform System is a software application service that provides a comprehensive platform for managing and delivering learning content and experiences. It enables organizations to create, manage, and deliver various types of learning materials, such as courses, training modules, assessments, and educational resources. The Learning Platform System typically includes features such as content authoring, learner management, progress tracking, assessment tools, discussion forums, and collaboration capabilities. It supports both self-paced and instructor-led learning, fostering employee or user development, knowledge acquisition, and skill enhancement. The Learning Platform System application service facilitates efficient and effective learning experiences, enabling organizations to deliver training and educational programs in a centralized and scalable manner.
Source: Gartner
Source reference: https://www.gartner.com/en/documents/4002299
LOST view: TVA-Functional Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/LearningPlatformSystemApplicationService
ABB name: egovera:LearningPlatformSystemApplicationService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/egovera/LearningPlatformSystemApplicationService
Interoperability Layer: TechnicalApplication
Specialises: http://data.europa.eu/dr8/DigitalWorkplaceApplicationService
Definition: Dataspace Connector ABB is an Application Service that enables the easy and trustworthy procedure to share data and work collaboratively with other research institutions.
Source: IDSA
Source reference: https://international-data-spaces-association.github.io/DataspaceConnector/
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): The Dataspace Connector from the International Data Spaces Association. https://international-data-spaces-association.github.io/DataspaceConnector/
Interoperability Dimension: Behavioral IoP
LOST view: TVA-Data Space Enablers [Motivation]
Interoperability Saliency: The Dataspace Connector Application Service ABB is salient for technical interoperability because it provides the way or method, the procedure for different parties (public services, public organisations, etc) to exchange data in a collaborative method.
Identifier: http://data.europa.eu/dr8/DataspaceConnectorApplicationService
ABB name: eira:DataspaceConnectorApplicationService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/DataspaceConnectorApplicationService
Interoperability Layer: TechnicalApplication
Definition: Multimedia Distribution refers to a data management application service that facilitates the efficient and scalable distribution of multimedia content, such as audio, video, images, and other multimedia formats. It encompasses the storage, retrieval, and delivery of multimedia assets to end-users or target systems. This service typically involves the use of network infrastructure, content delivery networks (CDNs), and streaming technologies to ensure fast and reliable delivery of multimedia content across various devices and platforms. Multimedia Distribution services play a crucial role in enabling widespread access to multimedia content, supporting entertainment, education, communication, and other domains.
Source: International Telecommunication Union (ITU)
LOST view: TVA-Functional Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/MultimediaDistributionApplicationService
ABB name: egovera:MultimediaDistributionApplicationService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/egovera/MultimediaDistributionApplicationService
Interoperability Layer: TechnicalApplication
Specialises: http://data.europa.eu/dr8/DataManagementApplicationService
Definition: Machine Learning is an application service within the field of Artificial Intelligence that enables systems to automatically learn and improve from experience without being explicitly programmed. It involves the development and deployment of algorithms and models that can analyze large volumes of data, identify patterns, and make predictions or decisions based on the learned patterns.
Source: Journal of Machine Learning Research
LOST view: TVA-Artificial Intelligence Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/MachineLearningApplicationService
ABB name: egovera:MachineLearningApplicationService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/egovera/MachineLearningApplicationService
Interoperability Layer: TechnicalApplication
Specialises: http://data.europa.eu/dr8/ArtificialIntelligenceApplicationService
Description: OpenPeppol is a non-profit international association that manages the development and maintenance of the PEPPOL Network. PEPPOL is a set of standards for exchanging electronic business documents, such as invoices, orders, and delivery notes. The PEPPOL Network is a global network of organizations that provide access to PEPPOL services.
Additional information: OpenPeppol is a non-profit organization that oversees the PEPPOL network, a global network that allows organizations to exchange business documents electronically. The PEPPOL network is based on a set of standards that facilitate the exchange of documents such as invoices, orders, and delivery notes. OpenPeppol's role is to manage the development and maintenance of this network, ensuring its smooth operation and continuous improvement.
Example: A company can use the PEPPOL network to send an electronic invoice to a customer in another country. The invoice is sent through the network, which ensures that it is delivered in a format that the customer's system can process. This eliminates the need for manual data entry and reduces the risk of errors. Similarly, a supplier can send an electronic delivery note to a customer, who can then automatically update their inventory management system.
Publisher: OpenPeppol Official Website
Source: https://peppol.eu/
LOST view: TVA-Tax Management Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/OpenPeppolApplicationService
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2024-01-17
Identifier: http://data.europa.eu/dr8/egovera/OpenPeppolApplicationService
Name: OpenPeppol Application Service
Interoperability Layer: TechnicalApplication
eira:businessDomain: taxes
Realises: http://data.europa.eu/dr8/DigitalSolutionApplicationService
Definition: People and skill allocation and distribution refers to the utilization of digital tools and platforms to efficiently allocate, manage, and distribute human resources and skills within the customs organization. This service involves the implementation of digital workforce management systems that enable customs authorities to streamline resource allocation, monitor staff availability, assign tasks, and track skill sets and competencies. The digital solution optimizes personnel deployment, enhances operational efficiency, and ensures the right people with the required skills are assigned to the appropriate tasks or projects. By automating people and skill allocation and distribution, this service improves workforce planning, minimizes resource gaps, enhances productivity, and supports effective customs operations within the customs environment.
Source: Based on World Customs Organization (WCO)
Example: In the customs department of a country, a digital solution for people and skill allocation and distribution has been implemented to optimize workforce management. The system integrates employee data, skills inventory, and task assignments, allowing customs authorities to efficiently allocate personnel based on their expertise, availability, and workload. The digital solution provides a centralized platform where supervisors can monitor staff availability, track skill sets and competencies, and assign tasks accordingly. It ensures that the right people with the required skills are allocated to specific customs operations, such as inspections, audits, or trade facilitation initiatives. By automating people and skill allocation and distribution, this digital solution enhances workforce planning, maximizes resource utilization, improves productivity, and enables effective customs operations within the customs environment.
eira:iopDimension: Behavioral IoP
LOST view: TVA-Customs Process Streamlining and Efficiency Enablers [Motivation]
eira:iopSaliency: The Digital Solution Service ABB is salient for technical interoperability because it is a central element the EIF's conceptual model for integrated public services. it represents the generalisation of all application services provided by an Interoperable European Solutionas as stated in the EIF: "Technical interoperability the applications and infrastructures linking systems and services."
Identifier: http://data.europa.eu/dr8/egovera/PeopleAndSkillAllocationAndDistributionApplicationService
ABB name: eira:DigitalSolutionApplicationService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-20
dct:identifier: http://data.europa.eu/dr8/egovera/PeopleAndSkillAllocationAndDistributionApplicationService
Definition: Orchestration Service ABB is an Application Service that enables the definition of the sequence and conditions in which one service invokes other services to realize some useful function.
Source: W3C
Source reference: https://www.w3.org/TR/ws-arch/
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): Apache ODE - Apache ODE (Orchestration Director Engine) software executes business processes written following the WS-BPEL standard. It talks to web services, sending and receiving messages, handling data manipulation and error recovery as described by your process definition. It supports both long and short living process executions to orchestrate all the services that are part of your application. http://ode.apache.org/
Interoperability Dimension: Structural IoP
LOST view: Technical view - application
Interoperability Saliency: The Orchestration Service ABB is salient for technical interoperability because it provides the functionality of "automated" business processes coordination. The EIF's Conceptual model for integrated EU public services foresees the concept a Coordination for Integrated Service Delivery. The Model comprises an "integrated service delivery" is based on a "coordination function", which is related to SOA principles such as choreography and orchestration, to manage internal business processes in order to remove complexity for the end-user, as stated in the EIF: "The coordination function ensures that needs are identified and appropriate services are invoked and orchestrated to provide a European public service. This function should select the appropriate sources and services and integrate them. Coordination can be automated or manual."
Identifier: http://data.europa.eu/dr8/OrchestrationApplicationService
ABB name: eira:OrchestrationApplicationService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/OrchestrationApplicationService
Interoperability Layer: TechnicalApplication
Definition: A Contact Management Digital Service is a software solution designed to store, organize, and manage contact information for individuals and organizations. It facilitates the collection, tracking, and utilization of contact details, communication preferences, and interaction history to enhance communication and relationship management.
Source: Techopedia
Source reference: https://www.techopedia.com/definition/2453/contact-management-software-cms
Additional information: Contact Management Digital Services are essential tools for businesses and professionals who need to maintain a large network of contacts. These services often include features such as contact databases, search and filter capabilities, integration with email and calendar applications, task management, interaction tracking, and reporting functions. Advanced systems may also offer automation of communication processes, social media integration, and customer relationship management (CRM) features. The goal of contact management is to streamline the process of maintaining up-to-date contact information, improving the efficiency of communication, and fostering strong relationships with clients, customers, and partners.
Example: Individuals using a contact management app to keep track of friends, family, and professional contacts, syncing across multiple devices and integrating with social media platforms.
A sales team using a CRM platform that includes contact management features to track interactions with potential clients, set reminders for follow-up, and record notes from meetings and calls.
A nonprofit organization utilizing contact management software to manage donor information, send out newsletters, and organize fundraising events.
Identifier: http://data.europa.eu/dr8/egovera/ContactManagementApplicationService
ABB name: egovera:ContactManagementApplicationService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/egovera/ContactManagementApplicationService
Name: Contact Management Application Service
Interoperability Layer: TechnicalApplication
Specialises: http://data.europa.eu/dr8/DigitalSolutionApplicationService
eira:iopDimension: Behavioral IoP
LOST view: TVA-Customs Compliance and Regulatory Requirements Enablers [Motivation]
eira:iopSaliency: The Digital Solution Service ABB is salient for technical interoperability because it is a central element the EIF's conceptual model for integrated public services. it represents the generalisation of all application services provided by an Interoperable European Solutionas as stated in the EIF: "Technical interoperability the applications and infrastructures linking systems and services."
Identifier: http://data.europa.eu/dr8/egovera/AuthorisedEconomicOperatorAccreditationApplicationService
ABB name: eira:DigitalSolutionApplicationService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-20
dct:identifier: http://data.europa.eu/dr8/egovera/AuthorisedEconomicOperatorAccreditationApplicationService
Definition: Audit ABB is an Application Service that enables the implementation of comprehensive procedural services capable of receiving inputs from different building blocks to ensure their correct behaviour, security or compliance with standards, regulations and best practices.
Source: Inspired in SIMPL
Source reference: https://digital-strategy.ec.europa.eu/en/news/simpl-cloud-edge-federations-and-data-spaces-made-simple
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): OpenIAM audit service - OpenIAM Auditing Service ensures that detailed information about events and activities associated with identities or resources are logged into a centralized repository and be tracked. It offers the following features: • Sign-on, Sign-off, • User: create, update, delete or disable accounts, • Role: create, update, delete or disable accounts, • Resource: create, update, delete or disable accounts, • Password changes, resets, challenge response questions changes, • Synchronization events, • Reconciliation events. Several reporting templates are provided for a BIRT report writer for use in an Eclipse designer. Organizations can also generate their own reports in BIRT with SQL. https://www.openiam.com/products/identity-manager/features/audit-compliance/
Interoperability Dimension: Structural IoP
LOST view: Technical view - application
Viewpoint: Interoperability Security viewpoint
Interoperability Saliency: The Audit Service ABB is salient for technical interoperability because it defines the elements of an information system which need to be traced, for example to assure traceability of user actions as stated in the EIF: "Public administrations should ensure that a 'data access and authorisation plan’ which determines who has access to what data and under what conditions, to ensure privacy. Unauthorised access and security breaches should be monitored and appropriate actions should be taken to prevent any recurrence of breaches"
Identifier: http://data.europa.eu/dr8/AuditApplicationService
ABB name: eira:AuditApplicationService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/AuditApplicationService
Interoperability Layer: TechnicalApplication
Description: Apache Airflow is an open-source platform used for programmatically authoring, scheduling, and monitoring workflows. It provides a way to define complex workflows as code, allowing users to easily manage and orchestrate tasks across different systems and technologies. Airflow uses Directed Acyclic Graphs (DAGs) to represent workflows, where each task is a node in the graph and the dependencies between tasks are represented by edges. It offers a rich set of operators to perform various tasks, such as running scripts, executing SQL queries, transferring data, and more. Airflow also provides a web-based user interface for visualizing and monitoring workflow execution.
Additional information: Apache Airflow is designed to be highly scalable, fault-tolerant, and extensible. It allows users to define workflows using Python code, making it flexible and customizable. Airflow supports various integrations with popular technologies like databases, cloud platforms, message queues, and more, enabling seamless integration with existing systems. It provides features like task retries, task dependencies, parallel execution, and monitoring capabilities, making it suitable for managing complex data pipelines, ETL processes, and batch processing workflows. With its modular architecture and active community support, Apache Airflow has become a popular choice for workflow management in the IT industry.
Example: An example of using Apache Airflow is to create a data pipeline for processing and analyzing customer data. The workflow can include tasks like extracting data from multiple sources, transforming and cleaning the data, loading it into a database, running machine learning models, and generating reports. By defining this workflow in Airflow, it becomes easy to schedule and monitor the execution of each task, handle failures, and ensure the overall data pipeline runs smoothly. The web-based UI of Airflow provides a visual representation of the workflow, allowing users to track the progress, view logs, and troubleshoot any issues that may arise during execution.
Publisher: Apache Airflow Documentation
Source: https://airflow.apache.org/docs/
LOST view: TVA-Orchestration Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/ApacheAirflowApplicationService
EIRA traceability: eira:DigitalSolutionApplicationService
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-07-20
dct:identifier: http://data.europa.eu/dr8/egovera/ApacheAirflowApplicationService
dct:title: Apache Airflow Application Service
Definition: Forms Management ABB is an Application Service that enables the procedures for i) dynamic creation, ii) distribution and ii) analysis of forms and online surveys.
Source: ISA2 - EIA Action
Source reference: https://joinup.ec.europa.eu/taxonomy/term/http_e_f_fdata_ceuropa_ceu_fdr8_fFormsManagementComponent
Synonym: e-Forms Service
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): EACEA e-Forms - Electronic Application Forms - eForms: This page contains the resources and information required by applicants who wish to complete and submit an electronic application form (eForm) for a funding opportunity or for an accreditation. The programmes and actions are listed for which electronic application forms are currently available. The Application eForm homepage is where applicants for funding and applicants for accreditation must follow a series of steps in order to create their new application. https://eacea.ec.europa.eu/about-eacea/electronic-application-forms-eforms_en
Interoperability Dimension: Structural IoP
LOST view: Technical view - application
Interoperability Saliency: The Forms Management Service ABB is salient for technical interoperability because it provides and shares the functionalities of dynamic creation, distribution and analysis of forms and online surveys as stated in the EIF: " Catalogues help others to find reusable resources (e.g. services, data, software, data models). Various types of catalogue exist, e.g. directories of services, libraries of software components, open data portals, registries of base registries, metadata catalogues, catalogues of standards, specifications and guidelines. Commonly agreed descriptions of the services, data, registries and interoperable solutions published in catalogues are needed to enable interoperability between catalogues."
Identifier: http://data.europa.eu/dr8/FormsManagementApplicationService
ABB name: eira:FormsManagementApplicationService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/FormsManagementApplicationService
Interoperability Layer: TechnicalApplication
Description: Podman is an open-source container engine that enables users to manage and run containers on Linux-based systems. It provides a command-line interface (CLI) for creating, managing, and interacting with containers, pods, and container images. Podman offers a lightweight and secure alternative to traditional container runtimes by utilizing the user's existing Linux kernel without requiring a separate daemon process.
Additional information: Podman is designed to be compatible with the Open Container Initiative (OCI) standards and can be used as a drop-in replacement for Docker. It allows users to create and manage individual containers or groups of containers called pods, which can be used to orchestrate multiple containers that need to work together. Podman provides features like container networking, storage management, and resource isolation. It also supports rootless containers, allowing non-root users to run containers securely. With its focus on security, performance, and compatibility, Podman is becoming increasingly popular in the containerization ecosystem.
Example: An example of using Podman is to create a pod consisting of multiple containers, such as a web server container, a database container, and a caching container. By using Podman's pod management capabilities, these containers can be easily orchestrated and managed as a single unit. This simplifies the deployment and management of complex applications that require multiple interconnected containers.
Publisher: Red Hat
Source: https://www.redhat.com/sysadmin/podman-containers-linux
LOST view: TVA-Containerization Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/PodmanApplicationService
EIRA traceability: eira:DigitalSolutionApplicationService
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-07-20
dct:identifier: http://data.europa.eu/dr8/egovera/PodmanApplicationService
dct:title: Podman Application Service
Definition: Digital Solution ABB is an Application Service that enables the implementation of public digital services or exposes an application behaviour.
Source: Inspired in EIF
Source reference: https://ec.europa.eu/isa2/sites/default/files/eif_brochure_final.pdf
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): EU Login - EU Login is the European Commission's user authentication service. It allows authorised users to access a wide range of Commission web services and websites, using a single email address and password. EU Login implements the single sign-on functionality. https://webgate.ec.europa.eu/cas/help.html
Interoperability Dimension: Structural IoP
LOST view: Technical view - application
Viewpoint: Highlevel viewpoint
Interoperability Saliency: The Digital Solution Service ABB is salient for technical interoperability because it is a central element the EIF's conceptual model for integrated public services. it represents the generalisation of all application services provided by an Interoperable European Solutionas as stated in the EIF: "Technical interoperability the applications and infrastructures linking systems and services."
Identifier: http://data.europa.eu/dr8/DigitalSolutionApplicationService
ABB name: eira:DigitalSolutionApplicationService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/DigitalSolutionApplicationService
Interoperability Layer: TechnicalApplication
Description: System for EU traders to manage authorisation assignments (delegations).
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): Belgian Federal Public Service Policy and Support - Role Management service: The Role Management service gives access managers the possibility to manage roles. A role gives access to an online government application. Characteristics: • A federal access management platform for public e-gov applications; • Three separate contexts: Businesses, Officials and Independent; • Roles that can only be attributed by a specific group of managers for a specific application within one of the three contexts; • Two different security levels of the application depending on the sensitivity of the information: user name, password and token; and electronic identity card with associated PIN code; • Authentication when connecting to an application; • Support with the implementation of the service; • Support while the service is being used. Users: All public services and institutions that want a secure access management for their applications: federal public services and institutions; Communities and Regions; Provinces, municipalities and local public social welfare centres; businesses or persons implementing government contracts. Requirements: application with Fedict Service Desk and signing up to a user agreement.(http://www.fedict.belgium.be/en/identificatie_beveiliging/rollenbeheer)
Publisher: European Commission
Source: https://customs.ec.europa.eu/taxud/uumds/cas/uumds-wayf/wayf?loginRequestId=ECAS_LR-193584-258Fl07XfLmYyzzHX2rK3khhqNEtMklzwgIruOTFab4XyqzYbchrdnwDSOQ1rugzd0NAtuU0dn0EAGP7qtzzUiD8-CiDsmZJBYJefjYF6zkDKeZ-WGzzKrUu7XVyGeYNhZx3rifPMIgxScy7XuhJEMgsPkC6qkJ5pYYWpmkzNqeO1D5W2uKKnzrokbY51O8azU15rfS
LOST view: TVA-Customs Identification and Access Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/CentralUniformUserManagementAndDigitalSignatureSystemApplicationService
EIRA traceability: eira:AccessManagementApplicationService
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-08-20
dct:identifier: http://data.europa.eu/dr8/egovera/CentralUniformUserManagementAndDigitalSignatureSystemApplicationService
Description: The EBSI Wallet for Holders is designed to empower users by allowing them to manage their Verifiable Credentials (VCs) efficiently and securely. Under the EBSI (European Blockchain Services Infrastructure) Verifiable Credentials exchange framework, the Wallet for Holders offers a suite of functionalities that cater specifically to the needs of credential holders. Request Issuance of Verifiable Credentials: Users can initiate requests for the issuance of VCs from trusted issuers. This functionality ensures that individuals can easily obtain credentials that validate their identity, qualifications, or other attributes.
Example: The following narrative is ficticius example that can help to understand how EUDI Wallet can be used: Maria, an EU citizen, needs to access healthcare services in another EU country. Using her EUDI Wallet, she logs in with her secure credentials. The healthcare provider requests her health insurance information, and Maria consents to share it through the wallet. The EUDI Wallet securely transmits her insurance details, allowing the provider to validate and authorize her access to services. This seamless process ensures that Maria receives the necessary healthcare without any physical paperwork, showcasing the EUDI Wallet's efficiency in managing identity verification, secure data sharing, and cross-border access.
Publisher: European Commission
Source: EBSI
LOST view: TVA-Identification and Access Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/EUDIWalletForHoldersApplicationService
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/egovera/EUDIWalletForHoldersApplicationService
Name: EUDI Wallet For Holders
Interoperability Layer: TechnicalApplication
Realises: http://data.europa.eu/dr8/IdentificationApplicationService
Definition: A software application service that enables individuals or teams to collaborate and communicate effectively, regardless of their physical locations. It provides tools and features such as video conferencing, instant messaging, document sharing, and virtual whiteboards to support real-time or asynchronous interactions. The Remote Collaboration and Communication application service bridges geographical and temporal gaps, facilitating seamless collaboration and communication in remote or distributed work environments.
Source: Gartner
Source reference: https://www.gartner.com/smarterwithgartner/the-future-of-work-collaboration-tools-and-technologies/
LOST view: TVA-Functional Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/RemoteCollaborationAndCommunicationApplicationService
ABB name: egovera:RemoteCollaborationAndCommunicationApplicationService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/egovera/RemoteCollaborationAndCommunicationApplicationService
Interoperability Layer: TechnicalApplication
Specialises: http://data.europa.eu/dr8/DigitalWorkplaceApplicationService
Definition: Digital collaboration refers to the use of digital tools and platforms to work together with others in a virtual environment. It involves the sharing of information, ideas, and resources to achieve common goals or complete tasks, regardless of the physical location of the participants.
Source: Techopedia
Source reference: https://www.techopedia.com/definition/3805/collaboration
Additional information: Digital collaboration encompasses a wide range of technologies and practices, including but not limited to, video conferencing, cloud-based document and file sharing, project management applications, instant messaging, and collaborative software suites that integrate multiple functions. These tools enable individuals and teams to communicate in real-time or asynchronously, enhancing productivity and facilitating the exchange of knowledge. Effective digital collaboration requires not only the right tools but also a culture that promotes open communication, trust, and the willingness to share expertise. As remote work and distributed teams become more prevalent, digital collaboration is increasingly critical for maintaining team cohesion and ensuring successful project outcomes.
Example: Using Zoom or Microsoft Teams to hold virtual meetings with team members located in different cities or countries.
Utilizing Google Docs or Microsoft OneDrive to collaboratively edit documents in real-time, allowing multiple users to make changes simultaneously.
Employing tools like Asana, Trello, or Jira to track project progress, assign tasks, and manage deadlines across a team.
Leveraging Slack or Microsoft Teams for quick communication and to facilitate discussions in dedicated channels for different topics or projects.
Using Office 365 or G Suite to access a comprehensive set of tools that support various aspects of collaboration, including email, calendaring, file storage, and more.
Identifier: http://data.europa.eu/dr8/egovera/DigitalCollaborationApplicationService
ABB name: egovera:DigitalCollaborationApplicationService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/egovera/DigitalCollaborationApplicationService
Name: Digital Collaboration Application Service
Interoperability Layer: TechnicalApplication
Specialises: http://data.europa.eu/dr8/DigitalSolutionApplicationService
Definition: Content Management ABB is an Application Service to enable the procedures to create, manage, and publish digital content, such as text, images, videos, and documents
Source: EUI
Source reference: https://www.eui.eu/ServicesAndAdmin/CommunicationsService/WebUnit/Web-CMS
Additional information: Content Management ABB is an Application Service being responsible for: - developing Website templates and functionalities; - assigning appropriate user permissions and workflows; - providing trainings to the web working group; - developing tools and web controls to speed up and facilitate the work of the web working group; - giving support and advice to the web working group; - ensuring continuity of service and performance; - ensuring security and accessibility on the website; - ensuring disaster recovery processes and backup procedures; - setting up the website information architecture within the CMS; - setting up alert procedures and analytics on usage of the platform.
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): FPFIS-CMS: "The European Commission announced in the Commission Internet strategy plans to transform the EUROPA web site from a source of one-way information into a tool for communication and interaction (i.e. provide modern interactive web sites for the citizens and stakeholders). Web sites are a key tool for external communications. They are the institution's business card. Websites are a very cost-effective and efficient means of communication. EUROPA now hosts over 460 websites. EUROPA would benefit from fewer and better sites to respond to user needs. To address the shortcomings, as part of the Commission's IT governance process, the College on 30 November 2011, instructed Commission departments to rationalise the Institution's web presence. Reduce the cost (human, financial, technical) of the Commission's web presence via exploiting economies of scale and eliminating redundancies by building corporate solutions. The European Commission should offer a corporate service which optimizes and harmonizes the use of different website tools, which speeds up the creation of new external dynamic and social websites (i.e. in days or weeks and not months) and which provides a common solid modern shared infrastructure to support the rapid deployment of these sites". https://webgate.ec.europa.eu/fpfis/mwikis/thinktank/index.php/Content_Management_System_of_the_Flexible_Platform
Interoperability Dimension: Structural IoP
LOST view: Technical view - application
Interoperability Saliency: The Content Management Service ABB is salient for technical interoperability because it provides and shares the functionalities of dynamic creation, distribution and analysis of contents (images, videos, etc.) as stated in the EIF: " Catalogues help others to find reusable resources (e.g. services, data, software, data models). Various types of catalogue exist, e.g. directories of services, libraries of software components, open data portals, registries of base registries, metadata catalogues, catalogues of standards, specifications and guidelines. Commonly agreed descriptions of the services, data, registries and interoperable solutions published in catalogues are needed to enable interoperability between catalogues."
Identifier: http://data.europa.eu/dr8/ContentManagementApplicationService
ABB name: eira:ContentManagementApplicationService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/ContentManagementApplicationService
Interoperability Layer: TechnicalApplication
Description: eTranslation is a state-of-the-art neural machine translation service offered by the European Commission. It enables users to automatically translate text and documents between multiple languages with high accuracy and speed.
Additional information: The eTranslation digital service utilizes advanced neural machine translation technology to provide efficient and reliable translation capabilities. It supports translation between 27 European languages, as well as numerous non-European languages. The service is designed to cater to various needs, including individuals, businesses, public administrations, and organizations. It offers a user-friendly web interface and a robust API for seamless integration into different applications and workflows. eTranslation ensures data privacy and security, as all translations are processed securely within the European Union. The service continuously improves its translation quality through machine learning techniques and user feedback. It plays a crucial role in promoting multilingualism, facilitating cross-border communication, and fostering digital transformation across Europe.
Example: eTranslation can be used by a business to translate product descriptions, customer reviews, and marketing materials to target international markets. It can assist a public administration in translating official documents, regulations, and public communications to ensure accessibility and inclusivity. Additionally, it can aid individuals in translating personal documents, emails, or websites to overcome language barriers and enhance communication in a globalized world.
Publisher: European Commission
Source: https://ec.europa.eu/info/research-and-innovation/research-area/digital-transformation_en
LOST view: TVA-Translation Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/ETranslationApplicationService
EIRA traceability: eira:MachineTranslationApplicationService
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-07-25
dct:identifier: http://data.europa.eu/dr8/egovera/ETranslationApplicationService
dct:title: eTranslation Application Service
Definition: Archival Information Packages (AIPs) refer to standardized packages of digital content and associated metadata that are created for long-term preservation and access in the context of eArchiving. AIPs encapsulate the essential components of digital objects, including their content, structure, and contextual information, ensuring their authenticity, integrity, and usability over time. AIPs typically adhere to established archival standards and formats, facilitating interoperability and long-term preservation strategies. The service of managing AIPs involves activities such as ingestion, storage, metadata management, preservation planning, and retrieval.
Source: OASIS
Source reference: https://public.ccsds.org/Pubs/650x0m2.pdf
LOST view: TVA-Data Management Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/ArchivalInformationPackagesApplicationService
ABB name: egovera:ArchivalInformationPackagesApplicationService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/egovera/ArchivalInformationPackagesApplicationService
Interoperability Layer: TechnicalApplication
Specialises: http://data.europa.eu/dr8/E-ArchivingApplicationService
Definition: Identity Management ABB is an Application Service that enables the set of processes, policies and technologies used to manage and secure digital entities of individuals, devices and applications.
Source: Inspired in eIDAS
Source reference: https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=CELEX:32014R0910&from=EN
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): EU Login - EU Login is the European Commission's user authentication service. It allows authorised users to access a wide range of Commission web services. EU Login is the entry gate to sign in to different European Commission services and/or other systems. EU Login verifies your identity and allows recovering your personal settings, history and access rights in a secure way. You can sign in using social media accounts or the EU Login account. EU Login supports a variety of verification methods: • Password; • ECAS Mobile App PIN code; • ECAS Mobile App QR code; • On mobile authentication; • Mobile phone + SMS; • Token and Token CRAM. https://webgate.ec.europa.eu/cas/manuals/EU_Login_Tutorial_1.1.pdf
eira:iopDimension: Behavioral IoP
LOST view: TVA-Customs Identification and Access Enablers [Motivation]
eira:iopSaliency: The Identity Management Application Service is salient for interoperability because it can help in the management of digital identities for individuals, devices and applications, ensuring and enabling that information on digital public services is available under the proper conditions and to the specific target. This can ensure and enhance the quality of data meant to be exchanged through interoperable systems, applications and digital public services.
Identifier: http://data.europa.eu/dr8/IdentityMangementApplicationService
ABB name: eira:IdentityMangementApplicationService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2022-01-18
dct:identifier: http://data.europa.eu/dr8/IdentityMangementApplicationService
Definition: Public Administration Single Window Service ABB is an Application that enables the processes to submit information and documents with a single entry point to fulfil all regulatory requirements.
Source: United Nations
Source reference: https://tfig.unece.org/contents/single-window-concept.htm
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): Mi Carpeta Ciudadana Carpeta Ciudadana is a personal online space that facilitates your relationship with public administrations. https://carpetaciudadana.gob.es/carpeta/clave.htm
Interoperability Dimension: Behavioral IoP
LOST view: Technical view - application
Interoperability Saliency: The Public Administration Single Window Application Service ABB is salient for technical interoperability because it acts as a single entry point for the provision and exchange of data between stakeholders and public organisations. This can improve not only the user experience but interoperability due to the standardised methods for data sharing.
Identifier: http://data.europa.eu/dr8/PublicAdministrationSingleWindowApplicationService
ABB name: eira:PublicAdministrationSingleWindowApplicationService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/PublicAdministrationSingleWindowApplicationService
Interoperability Layer: TechnicalApplication
Description: LXC (Linux Containers) is an operating system-level virtualization method that allows multiple isolated Linux systems, known as containers, to run on a single host. Each container shares the host's kernel but operates in a separate user space, providing lightweight and efficient virtualization. LXC provides a way to create and manage these containers, offering a flexible and secure environment for deploying applications.
Additional information: LXC provides a lightweight alternative to traditional virtualization technologies by leveraging the Linux kernel's cgroups and namespaces features. Containers created using LXC offer resource isolation, process-level separation, and filesystem-level isolation, allowing applications to run in an environment that closely resembles a full-fledged Linux system. LXC enables efficient utilization of hardware resources, faster startup times, and lower overhead compared to traditional virtual machines. It is widely used in various scenarios, including server consolidation, application sandboxing, development environments, and microservices architecture.
Example: An example of LXC's application is in cloud computing platforms where multiple containers can be deployed on a single physical server, each running its own isolated application stack. This allows for efficient resource utilization and scalability, as containers can be easily provisioned, managed, and scaled independently. LXC also finds use in development environments, where developers can create lightweight containers to replicate production environments, ensuring consistent testing and development workflows.
Publisher: Linux Containers (LXC) - Linux Containers Documentation
Source: https://linuxcontainers.org/lxc/introduction/
LOST view: TVA-Containerization Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/LXCApplicationService
EIRA traceability: eira:DigitalSolutionApplicationService
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-07-20
dct:identifier: http://data.europa.eu/dr8/egovera/LXCApplicationService
dct:title: LXC Application Service
Definition: Dataspace Connector Provider ABB is an Application Service that enables maintenance control over the data and sets the conditions for its use in the data space ecosystem.
Source: IDSA
Source reference: https://internationaldataspaces.org/offers/ids-components/
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): The Dataspace Connector from the International Data Spaces Association. https://international-data-spaces-association.github.io/DataspaceConnector/
Interoperability Dimension: Behavioral IoP
LOST view: TVA-Functional Architecture Principles
Interoperability Saliency: The Dataspace Connector Provider Application Service ABB is salient for technical interoperability because is a key element in the data spaces environment and interoperability, as this service sets the conditions for the consumption of data by other services or parties.
Identifier: http://data.europa.eu/dr8/DataspaceConnectorProviderApplicationService
ABB name: eira:DataspaceConnectorProviderApplicationService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/DataspaceConnectorProviderApplicationService
Interoperability Layer: TechnicalApplication
Description: Apache Mesos is an open-source distributed systems kernel that provides resource management and scheduling capabilities for running applications across a cluster of machines. It abstracts the underlying hardware and allows multiple applications to efficiently share resources, improving utilization and scalability. Mesos provides a flexible and scalable framework for managing and deploying applications, making it easier to build and operate large-scale distributed systems.
Additional information: Mesos acts as a middle layer between the operating system and the applications, enabling efficient sharing of resources across multiple applications. It provides a unified interface for managing and scheduling tasks, allowing developers to focus on building applications without worrying about the underlying infrastructure. Mesos also supports dynamic allocation and isolation of resources, allowing applications to scale up or down based on demand. It offers fault-tolerance and high availability, ensuring that applications continue to run even in the presence of failures. Mesos is widely used in large-scale distributed systems, cloud computing, and container orchestration platforms.
Example: One example of using Apache Mesos is in a data center environment where multiple applications need to be run on a cluster of machines. Mesos can efficiently allocate resources such as CPU, memory, and storage to each application based on their requirements. For instance, a data processing application may require more CPU resources, while a storage-intensive application may need more disk space. Mesos ensures that these applications coexist and share resources effectively, maximizing the utilization of the cluster. This allows organizations to achieve better resource utilization, cost savings, and improved scalability.
Publisher: Apache Mesos Documentation
Source: https://mesos.apache.org/documentation/
LOST view: TVA-Containerization Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/ApacheMesosApplicationService
EIRA traceability: eira:DigitalSolutionApplicationService
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-07-20
dct:identifier: http://data.europa.eu/dr8/egovera/ApacheMesosApplicationService
dct:title: Apache Mesos Application Service
Description: The ELK Stack is a collection of three open-source tools: Elasticsearch, Logstash, and Kibana, used for centralized logging and log analysis. Elasticsearch is a distributed search and analytics engine that stores and indexes data, providing fast and scalable search capabilities. Logstash is a data processing pipeline that ingests, transforms, and sends data to Elasticsearch. Kibana is a data visualization and exploration platform that allows users to interact with the data stored in Elasticsearch, creating real-time dashboards, charts, and graphs.
Additional information: The ELK Stack is widely used for log management and analysis in various industries and organizations. It enables the collection, storage, and analysis of large volumes of log data from different sources, such as servers, applications, and network devices. By centralizing logs in Elasticsearch, it becomes easier to search, monitor, and gain insights from the data. Logstash provides a flexible and extensible platform for data ingestion, allowing users to parse, filter, and transform logs before sending them to Elasticsearch. Kibana complements Elasticsearch by providing a user-friendly interface to visualize and explore the data, enabling users to create custom dashboards and perform ad-hoc queries. The ELK Stack is highly scalable and can handle massive amounts of data, making it a powerful tool for log analysis and troubleshooting.
Example: An example of using the ELK Stack is in a web application environment. Logs generated by web servers, load balancers, and application servers can be collected by Logstash, which processes and sends them to Elasticsearch for indexing. Kibana can then be used to create real-time dashboards that display metrics such as response times, error rates, and user activity. This allows developers and system administrators to monitor the application's performance, identify issues, and troubleshoot effectively.
Publisher: Elastic
Source: https://www.elastic.co/what-is/elk-stack
LOST view: TVA-Observability and Monitoring Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/ELKStackApplicationService
EIRA traceability: eira:DigitalSolutionApplicationService
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-07-20
dct:identifier: http://data.europa.eu/dr8/egovera/ELKStackApplicationService
dct:title: ELK Stack Application Service
Definition: Access Management ABB is an Application Service aimed to grant authorized users the right to use a service, while preventing access to non-authorized users
Source: ITIL v3
Source reference: https://wiki.en.it-processmaps.com/index.php/Access_Management
Additional information: Access management helps to protect the confidentiality, integrity and availability of assets by ensuring that only authorized users are able to access or modify the assets.
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): Belgian Federal Public Service Policy and Support - Role Management service: The Role Management service gives access managers the possibility to manage roles. A role gives access to an online government application. Characteristics: • A federal access management platform for public e-gov applications; • Three separate contexts: Businesses, Officials and Independent; • Roles that can only be attributed by a specific group of managers for a specific application within one of the three contexts; • Two different security levels of the application depending on the sensitivity of the information: user name, password and token; and electronic identity card with associated PIN code; • Authentication when connecting to an application; • Support with the implementation of the service; • Support while the service is being used. Users: All public services and institutions that want a secure access management for their applications: federal public services and institutions; Communities and Regions; Provinces, municipalities and local public social welfare centres; businesses or persons implementing government contracts. Requirements: application with Fedict Service Desk and signing up to a user agreement.(http://www.fedict.belgium.be/en/identificatie_beveiliging/rollenbeheer)
Interoperability Dimension: Structural IoP
LOST view: Technical view - application
Viewpoint: Interoperability Security viewpoint
Interoperability Saliency: The Access Management Service ABB is salient for technical interoperability because it provides the functionality of allowing user to make an authorized and trusted use of IT Services, data and other assets as stated in the EIF: "Public administrations should ensure that a 'data access and authorisation plan’ which determines who has access to what data and under what conditions, to ensure privacy. Unauthorised access and security breaches should be monitored and appropriate actions should be taken to prevent any recurrence of breaches"
Identifier: http://data.europa.eu/dr8/AccessManagementApplicationService
ABB name: eira:AccessManagementApplicationService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/AccessManagementApplicationService
Interoperability Layer: TechnicalApplication
Definition: A Service Metadata Locator is a digital service that enables the discovery and retrieval of metadata about other services within a distributed system or across the internet.
Source: Techopedia
Source reference: https://www.techopedia.com/definition/24559/service-metadata-locator
Additional information: The Service Metadata Locator is a crucial component in service-oriented architectures (SOA) and microservices architectures, where services are loosely coupled and can be dynamically discovered and integrated. It acts as a directory or registry that holds information about the services available within a system, such as service endpoints, interfaces, protocols, and policies. This information is essential for service consumers to understand how to interact with the services. The locator often provides an API or interface through which services can register their metadata and through which consumers can query for services that meet certain criteria. This enables automation in service discovery and integration, which is vital for scalability and flexibility in complex systems.
Example: Web Services Discovery
In a web services environment, a Service Metadata Locator can be used to store and provide access to WSDL (Web Services Description Language) files. Clients can query the locator to find the appropriate WSDL for a web service they wish to consume, enabling them to dynamically generate client stubs and interact with the service.
Microservices Architecture
In a microservices architecture, a Service Metadata Locator can be used by individual microservices to register their availability and by others to discover these services. For example, when a new microservice is deployed, it registers its metadata with the locator. Other microservices or service gateways can query the locator to route requests or compose services.
Identifier: http://data.europa.eu/dr8/egovera/ServiceMetadataLocatorApplicationService
ABB name: egovera:ServiceMetadataLocatorApplicationService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/egovera/ServiceMetadataLocatorApplicationService
Name: Service Metadata Locator Application Service
Interoperability Layer: TechnicalApplication
Specialises: http://data.europa.eu/dr8/DigitalSolutionApplicationService
Definition: Refers to the systematic assessment and evaluation of potential risks associated with trade transactions and customs operations. It involves leveraging data analytics, algorithms, and risk management methodologies to identify patterns, anomalies, and potential risks in real-time. By analyzing factors such as shipment details, trader profiles, country of origin, and historical data, risk analysis enables customs authorities to prioritize inspections, allocate resources effectively, and mitigate risks related to smuggling, fraud, security threats, and non-compliance. This digital solution service enhances customs efficiency, facilitates secure trade, and supports informed decision-making to ensure effective risk management within the customs domain.
Source: World Customs Organization (WCO)
Example: In the context of customs, risk analysis involves utilizing data analytics and automated algorithms to assess and identify potential risks associated with trade transactions. By analyzing factors such as the country of origin, importer's profile, commodity type, and historical data, customs authorities can assign risk scores to declarations, enabling the effective allocation of inspection resources. High-risk declarations can be flagged for further scrutiny, while low-risk ones can proceed with minimal intervention. Risk analysis enhances border security, combats illicit activities, and streamlines trade by prioritizing resources and focusing on high-risk transactions. It ensures operational efficiency, adaptability to evolving threats, and continuous improvement in risk assessment models for more accurate and effective risk management.
eira:iopDimension: Behavioral IoP
LOST view: TVA-Customs Risk Analysis Enablers [Motivation]
eira:iopSaliency: The Digital Solution Service ABB is salient for technical interoperability because it is a central element the EIF's conceptual model for integrated public services. it represents the generalisation of all application services provided by an Interoperable European Solutionas as stated in the EIF: "Technical interoperability the applications and infrastructures linking systems and services."
Identifier: http://data.europa.eu/dr8/egovera/RiskAnalysisApplicationService
ABB name: eira:DigitalSolutionApplicationService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-20
dct:identifier: http://data.europa.eu/dr8/egovera/RiskAnalysisApplicationService
Definition: Authentication ABB is an Application Service that enables the functionality of grating users to access the platforms or the services.
Source: eIDAS - 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.
Source reference: http://eur-lex.europa.eu/legal-content/EN/TXT/?uri=uriserv%3AOJ.L_.2014.257.01.0073.01.ENG
Additional information: ‘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;
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): EU Login - EU Login is the European Commission's user authentication service. It allows authorised users to access a wide range of Commission web services. EU Login is the entry gate to sign in to different European Commission services and/or other systems. EU Login verifies your identity and allows recovering your personal settings, history and access rights in a secure way. You can sign in using social media accounts or the EU Login account. EU Login supports a variety of verification methods: • Password; • ECAS Mobile App PIN code; • ECAS Mobile App QR code; • On mobile authentication; • Mobile phone + SMS; • Token and Token CRAM. https://webgate.ec.europa.eu/cas/about.html
Interoperability Dimension: Structural IoP
LOST view: Technical view - application
Viewpoint: Interoperability Security viewpoint
Interoperability Saliency: The Authentication Service ABB is salient for technical interoperability because it provides the functionalities of user authentication.
Identifier: http://data.europa.eu/dr8/AuthenticationApplicationService
ABB name: eira:AuthenticationApplicationService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/AuthenticationApplicationService
Interoperability Layer: TechnicalApplication
Description: Vault is an open-source tool designed for securely storing and accessing sensitive information such as passwords, API keys, and encryption keys. It provides a centralized system for managing secrets and ensures their secure distribution across applications and systems.
Additional information: Vault offers a secure and scalable solution for managing secrets in modern IT environments. It employs a client-server architecture where the Vault server acts as a central repository for secrets, while clients interact with the server to retrieve or store secrets. Vault provides various authentication methods, access control policies, and encryption mechanisms to ensure the confidentiality and integrity of stored secrets. It also supports dynamic secrets, which are short-lived credentials generated on-demand, further enhancing security. Vault integrates with popular cloud platforms and can be seamlessly integrated into existing infrastructure.
Example: An example of Vault's application is in a microservices architecture where multiple services require access to sensitive information. Instead of hardcoding credentials within each service, Vault can be used to securely store and distribute these secrets. Services can authenticate with Vault and retrieve the required secrets dynamically, reducing the risk of exposure and simplifying secret management across the system.
Publisher: HashiCorp
Source: https://www.vaultproject.io/
LOST view: TVA-Privacy Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/HashiCorpVaultApplicationService
EIRA traceability: eira:DigitalSolutionApplicationService
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-08-20
dct:identifier: http://data.europa.eu/dr8/egovera/HashiCorpVaultApplicationService
dct:title: Vault Application Service
Description: EU Login is an authentication service provided by the European Commission that allows users to securely access a wide range of European Union (EU) online services and applications. It provides a single sign-on mechanism, enabling users to use a single set of credentials to access multiple EU services.
Additional information: EU Login, formerly known as ECAS (European Commission Authentication Service), is a centralized authentication system used by various EU institutions, agencies, and other online services. It ensures secure access to sensitive information and services by verifying the identity of users through a username and password combination or other authentication methods. EU Login supports multi-factor authentication, allowing users to enhance the security of their accounts by using additional verification methods such as mobile app-based codes or hardware tokens. It also provides features like password recovery, account management, and user profile settings. EU Login simplifies the user experience by eliminating the need for separate credentials for each EU service, reducing the administrative burden for both users and service providers.
Example: An example of EU Login in action is when a user wants to access the European Commission's online portal to submit a funding application. Instead of creating a new account, the user can simply use their existing EU Login credentials to authenticate themselves and gain access to the application submission system. This streamlines the process for the user and ensures the security and integrity of the application data.
Publisher: European Commission
Source: https://webgate.ec.europa.eu/cas/help.html
LOST view: TVA-Identification and Access Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/EULoginApplicationService
EIRA traceability: eira:IdentityMangementApplicationService
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-07-21
dct:identifier: http://data.europa.eu/dr8/egovera/EULoginApplicationService
dct:title: EU Login Application Service
Definition: Data Exchange ABB is an Application Service enabling the secure exchange of messages, records, forms and other kinds of data between different individuals, organizations or systems. This includes data routing, except endpoint discovery.
Source: EIFv2
Source reference: http://ec.europa.eu/isa/documents/isa_annex_ii_eif_en.pdf
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): XMLGate - XMLGate is a Web service application used to validate an XML instance against a well-defined schema. The XML flow is submitted either via a PDF form or by uploading the XML file.(https://webgate.ec.europa.eu/sanco-xmlgate/Login.jsp;jsessionid=2MPn_N5Wg9Dar4_W2-yVL_Xg-VlW3kn47PLVbNise9X5Kycx1yLI!-25226473)
Interoperability Dimension: Behavioral IoP
LOST view: Technical view - application
Viewpoint: Interoperability Security viewpoint
Interoperability Saliency: The Data Exchange Service ABB is a key interoperability enabler (*) for behavioural and technical interoperability because it provides secure and trustworthy data exchange between different ICT systems as stated in the EIF: "Define a common security and privacy framework and establish processes for public services to ensure secure and trustworthy data exchange between public administrations and in interactions with citizens and businesses."
Identifier: http://data.europa.eu/dr8/DataExchangeApplicationService
ABB name: eira:DataExchangeApplicationService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/DataExchangeApplicationService
Interoperability Layer: TechnicalApplication
Definition: Guarantee refers to the electronic management and administration of customs guarantees provided by traders or financial institutions to ensure compliance with customs requirements. This service involves the implementation of digital platforms and systems that enable efficient guarantee management, such as tracking guarantee amounts, issuing and processing electronic guarantee certificates, and automating guarantee-related processes. The digital solution provides customs authorities with real-time visibility into the status and validity of guarantees, streamlining customs operations and facilitating trade facilitation. By automating guarantee management, this service enhances transparency, reduces administrative burdens, improves compliance verification, and ensures efficient handling of financial obligations within the customs environment.
Source: Based on World Customs Organization (WCO)
Example: In the customs department of Country XYZ, a digital solution for guarantee management has been implemented to streamline the administration and tracking of customs guarantees. Traders or financial institutions provide electronic guarantee certificates, which are securely stored and managed within a centralized system. The digital solution automates processes such as guarantee issuance, modification, and release. Customs authorities can efficiently verify the validity and coverage of guarantees in real-time, ensuring compliance with customs requirements and mitigating risk. By automating guarantee management, this digital solution improves transparency, reduces paperwork, accelerates customs clearance, and facilitates trade facilitation for both customs authorities and traders in Country XYZ.
eira:iopDimension: Behavioral IoP
LOST view: TVA-Customs Process Streamlining and Efficiency Enablers [Motivation]
eira:iopSaliency: The Digital Solution Service ABB is salient for technical interoperability because it is a central element the EIF's conceptual model for integrated public services. it represents the generalisation of all application services provided by an Interoperable European Solutionas as stated in the EIF: "Technical interoperability the applications and infrastructures linking systems and services."
Identifier: http://data.europa.eu/dr8/egovera/GuaranteeApplicationService
ABB name: eira:DigitalSolutionApplicationService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-20
dct:identifier: http://data.europa.eu/dr8/egovera/GuaranteeApplicationService
Description: The EBSI Wallet for Issuers is designed to enable organizations, such as universities, ministries, and other credential-issuing bodies, to manage and issue Verifiable Credentials (VCs) securely on the blockchain ledger. Under the EBSI (European Blockchain Services Infrastructure) Verifiable Credentials exchange framework, this wallet provides a robust platform for issuing and managing accreditations.
Additional information: Key functionalities of the EBSI Wallet for Issuers include: (1) Manage Accreditations: Organizations can efficiently manage their accreditation processes on the blockchain ledger, ensuring that all issued credentials are secure, verifiable, and tamper-proof. (2) Issue Verifiable Credentials: The wallet allows issuers to create and distribute VCs to holders. These credentials can validate a wide range of information, from educational qualifications to professional certifications. (3) Blockchain Integration: By utilizing blockchain technology, the wallet ensures the integrity and authenticity of the credentials, providing a transparent and immutable record of all issued documents. These functionalities ensure that credentials issued via the EBSI Wallet for Issuers are trusted, interoperable, and easily verifiable across different systems and platforms. This wallet supports the broader EBSI goals of enhancing trust, security, and interoperability in digital services across Europe.
Example: The following narrative is ficticius example that can help to understand how EUDI Wallet can be used: Maria, an EU citizen, needs to access healthcare services in another EU country. Using her EUDI Wallet, she logs in with her secure credentials. The healthcare provider requests her health insurance information, and Maria consents to share it through the wallet. The EUDI Wallet securely transmits her insurance details, allowing the provider to validate and authorize her access to services. This seamless process ensures that Maria receives the necessary healthcare without any physical paperwork, showcasing the EUDI Wallet's efficiency in managing identity verification, secure data sharing, and cross-border access.
Publisher: European Commission
Source: EBSI
LOST view: TVA-Identification and Access Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/EUDIWalletForIssuersApplicationService
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/egovera/EUDIWalletForIssuersApplicationService
Name: EUDI Wallet For Issuers
Interoperability Layer: TechnicalApplication
Realises: http://data.europa.eu/dr8/IdentificationApplicationService
Definition: Federated Data Catalogue Management refers to the practice of centrally managing and organizing metadata about data assets across multiple data catalogues within an organization. It involves creating a unified view of data assets, their attributes, and relationships, while allowing decentralized control and ownership of individual catalogues.
Source: Techopedia
Source reference: https://www.techopedia.com/definition/33133/federated-data-catalog-management
Additional information: In a federated data catalogue management approach, each data catalogue retains its autonomy and maintains its own metadata, but a central management system is responsible for aggregating and harmonizing the metadata from all catalogues. This allows users to search, discover, and understand data assets across different catalogues, promoting data sharing, collaboration, and governance. The federated approach enables organizations to leverage existing catalogues, avoid data duplication, and maintain data lineage and provenance. It also facilitates compliance with data regulations and standards by providing a comprehensive view of data assets.
Example: An organization with multiple business units may have separate data catalogues for each unit. With federated data catalogue management, a central system can integrate metadata from all catalogues, enabling users to search and discover data assets across units. For example, a data analyst in one business unit can easily find and access relevant datasets from another unit's catalogue without needing direct access to that catalogue. This promotes cross-functional collaboration, reduces data silos, and improves overall data governance and utilization.
LOST view: TVA-Data Management Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/FederatedDataCatalogueManagementApplicationService
ABB name: egovera:FederatedDataCatalogueManagementApplicationService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/egovera/FederatedDataCatalogueManagementApplicationService
Name: Federated Data Catalogue Management Application Service
Interoperability Layer: TechnicalApplication
Specialises: http://data.europa.eu/dr8/DigitalSolutionApplicationService
Definition: Data Quality ABB is an Application Service that enables the procedures to ensure the data is accurate, complete, consistent, and up-to-date
Source: Eurostat Data Validation
Source reference: http://ec.europa.eu/eurostat/data/data-validation
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): Eurostat Struval - The Structural Validation service (called STRUVAL) performs structural validation of statistical data files following the SDMX Information Model for a given data flow. It ensures that a data file respects the following key elements: • SDMX compliance in terms of checks on file format and completeness in terms of mandatory fields; • SDMX compliance in terms of the structure and coding defined by the Data Structure Definition (DSD); • The constraints defined for respective data flows. The STRUVAL service returns a response containing a machine-readable message that is processed by the process manager. The invoker of the service receives a validation report, regardless of the result of the process (in case of no failures the reports hold no records). http://ec.europa.eu/eurostat/web/sdmx-infospace/validation-transformation/structural-validation
Interoperability Dimension: Structural IoP
LOST view: Technical view - application
Viewpoint: Interoperability Privacy viewpoint
Interoperability Saliency: The Data Quality Service ABB is salient for technical interoperability because it shares the functionality to validate if data received (or to be sent) is compliant with common and agreed interoperable formats as stated in the EIF recommendation n° 41: "Establish procedures and processes to integrate the opening of data in your common business processes, working routines, and in the development of new information systems."
Identifier: http://data.europa.eu/dr8/DataQualityApplicationService
ABB name: eira:DataQualityApplicationService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/DataQualityApplicationService
Interoperability Layer: TechnicalApplication
Description: DSS (Digital Signature Services) is an open-source software library for digital signature creation, validation, and extension, designed to help digital solutions achieve compliance with the eIDAS Regulation.
Publisher: European Commission
Source: https://ec.europa.eu/digital-building-blocks/wikis/display/DIGITAL/Digital+Signature+Service+-++DSS
LOST view: TVA-Trust Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/DigitalEuropeESignaturesDSSOpen-sourceLibraryApplicationService
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/egovera/DigitalEuropeESignaturesDSSOpen-sourceLibraryApplicationService
Interoperability Layer: TechnicalApplication
Realises: http://data.europa.eu/dr8/E-SignatureCreationApplicationService
Description: Apache Kafka is an open-source distributed event streaming platform that is designed to handle high-throughput, fault-tolerant, and scalable real-time data streaming. It provides a publish-subscribe model where producers publish data to topics, and consumers subscribe to those topics to receive the data. Kafka stores the data in a fault-tolerant and durable manner, allowing it to be processed and consumed by multiple applications and systems.
Additional information: Apache Kafka is widely used in modern data architectures as a messaging system, enabling real-time data integration, streaming analytics, and event-driven architectures. It is built to handle massive amounts of data and provides low-latency, high-throughput, and fault-tolerant data streaming capabilities. Kafka's distributed nature allows it to scale horizontally across multiple servers, ensuring high availability and reliability. It provides strong durability guarantees by persisting data to disk, making it suitable for mission-critical applications. Kafka's flexible architecture allows seamless integration with various data systems, making it a popular choice for building data pipelines and streaming applications.
Example: One example of Apache Kafka's application is in a real-time analytics platform. Multiple data sources, such as web servers, mobile apps, and IoT devices, can publish events to Kafka topics. These events can then be consumed by analytics applications in real-time, allowing businesses to gain insights and make data-driven decisions instantly. Another example is its use in building scalable microservices architectures, where Kafka acts as a reliable communication layer between different microservices, ensuring data consistency and fault tolerance.
Publisher: Confluent
Source: https://www.confluent.io/what-is-apache-kafka/
LOST view: TVA-Messaging Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/ApacheKafkaApplicationService
EIRA traceability: eira:DigitalSolutionApplicationService
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-07-20
dct:identifier: http://data.europa.eu/dr8/egovera/ApacheKafkaApplicationService
dct:title: Apache Kafka Application Service
Description: A software component that enables data sharing and data sovereignty based on the EDC framework and the IDS standard.
Additional information: The Sovity Dataspace Connector is an extension of the EDC Connector, which provides a framework for sovereign, inter-organizational data exchange. Sovity adds features such as easy access, automated integration, simple usage, fully managed services, and data space expertise to offer enterprise-ready solutions for data sharing. Sovity also provides different editions of the connector, such as the Community Edition, which contains pre-configured open source extensions.
Example: An example of the Sovity Dataspace Connector in action is a consortium of healthcare providers sharing patient data securely and efficiently. The connector enables the seamless exchange of patient records, medical images, and diagnostic reports between hospitals, clinics, and research institutions. It ensures that sensitive patient information is protected and accessed only by authorized entities, while allowing healthcare professionals to collaborate and make informed decisions based on comprehensive and up-to-date patient data. The connector also facilitates the integration of data from wearable devices, remote monitoring systems, and electronic health records, enabling a holistic view of patient health and supporting personalized medicine initiatives.
Publisher: Sovity
Source: https://sovity.de/
LOST view: TVA-Data Space Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/SovityDataspaceConnectorApplicationService
EIRA traceability: eira:DigitalSolutionApplicationService
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-07-20
dct:identifier: http://data.europa.eu/dr8/egovera/SovityDataspaceConnectorApplicationService
dct:title: Sovity Dataspace Connector Application Service
Definition: A Knowledge Exchange Digital Service is an online platform that facilitates the sharing of information, expertise, and insights among individuals, organizations, or communities. It often includes features such as forums, document repositories, collaborative workspaces, and social networking capabilities to enhance communication and collaboration.
Source: Techopedia
Source reference: https://www.techopedia.com/definition/26558/knowledge-exchange
Additional information: The Knowledge Exchange Digital Service is designed to support the dissemination and collaborative use of knowledge across various domains. It can be tailored to specific industries or areas of interest, such as academia, healthcare, technology, or government. The service typically includes mechanisms for content management, user authentication, and access control to ensure that information is shared securely and with the appropriate audience. Advanced services may incorporate artificial intelligence and machine learning to curate and recommend content to users based on their interests and past interactions. The goal of such a service is to foster innovation, improve decision-making, and enable users to learn from each other's experiences and expertise.
Example: A university may use a Knowledge Exchange Digital Service to connect researchers across different disciplines, allowing them to share data, research findings, and methodologies, which can lead to interdisciplinary collaborations and advancements in research.
A digital platform for healthcare professionals where they can exchange clinical case studies, best practices, and the latest research findings to improve patient care and stay updated with medical advancements.
A government-initiated service that allows policymakers, experts, and stakeholders to discuss and refine policy proposals, share empirical evidence, and access a repository of historical policy documents and their outcomes.
Identifier: http://data.europa.eu/dr8/egovera/KnowledgeExchangeApplicationService
ABB name: egovera:KnowledgeExchangeApplicationService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/egovera/KnowledgeExchangeApplicationService
Name: Knowledge Exchange Application Service
Interoperability Layer: TechnicalApplication
Specialises: http://data.europa.eu/dr8/DigitalSolutionApplicationService
Definition: Data Catalogue Management is the process of organizing, categorizing, and managing metadata about data assets within an organization. It involves creating a centralized repository or catalog that provides a comprehensive view of available data resources, including their structure, location, quality, and usage. This enables data users to easily discover, understand, and access relevant data assets, promoting data governance, collaboration, and informed decision-making.
Source: Techopedia
Source reference: https://www.techopedia.com/definition/32705/data-catalog
Additional information: Data Catalogue Management plays a crucial role in data-driven organizations by facilitating the discovery and understanding of data assets. It involves capturing and maintaining metadata, such as data source, format, schema, and lineage, in a structured manner. The catalog serves as a central hub for data stakeholders to search, explore, and evaluate available data resources. It helps in identifying data dependencies, assessing data quality, and ensuring compliance with data governance policies. Data Catalogue Management enhances data collaboration and enables self-service analytics, as users can easily find and access the data they need. It also promotes data reuse, as the catalog provides visibility into existing data assets, reducing redundancy and improving efficiency. Overall, effective Data Catalogue Management improves data discoverability, accessibility, and usability, leading to better decision-making and insights.
Example: An example of Data Catalogue Management in practice is a large financial institution that maintains a data catalog to manage its vast amount of financial data. The catalog includes metadata about various data sources, such as transactional databases, market data feeds, and customer data repositories. It provides detailed information about each dataset, including its structure, data types, and data quality metrics. Data analysts and business users can search the catalog to find relevant data for their analysis or reporting needs. They can also view the lineage of a dataset to understand its origin and transformations. The data catalog ensures that users have a clear understanding of available data assets, enabling them to make informed decisions and perform accurate analysis.
LOST view: TVA-Data Management Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/DataCatalogueManagementApplicationService
ABB name: egovera:DataCatalogueManagementApplicationService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/egovera/DataCatalogueManagementApplicationService
Name: Data Catalogue Management Application Service
Interoperability Layer: TechnicalApplication
Specialises: http://data.europa.eu/dr8/DigitalSolutionApplicationService
Description: Ethereum is an open-source blockchain-based platform that enables the development and execution of decentralized applications (DApps) and smart contracts. It provides a decentralized virtual machine, called the Ethereum Virtual Machine (EVM), which allows developers to build and deploy applications on the Ethereum network. Ethereum utilizes its native cryptocurrency called Ether (ETH) as a means of value exchange within the network.
Additional information: Ethereum revolutionized the blockchain industry by introducing smart contracts, which are self-executing contracts with predefined rules and conditions. These contracts automatically execute when the conditions are met, eliminating the need for intermediaries and enhancing transparency and efficiency. Ethereum's decentralized nature ensures that applications built on its platform are resistant to censorship, fraud, and downtime. It has become a popular choice for developers and organizations looking to create decentralized applications, tokenized assets, and decentralized finance (DeFi) solutions.
Example: One example of Ethereum's application is in the field of decentralized finance (DeFi). DeFi platforms built on Ethereum enable users to access financial services without relying on traditional intermediaries, such as banks. Users can lend, borrow, trade, and earn interest on their cryptocurrencies directly through smart contracts, eliminating the need for a centralized authority. This opens up opportunities for financial inclusion and innovation, allowing individuals worldwide to participate in the global financial system.
Publisher: Ethereum.org
Source: https://ethereum.org/
LOST view: TVA-Trust Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/EthereumApplicationService
EIRA traceability: eira:DigitalSolutionApplicationService
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-07-25
dct:identifier: http://data.europa.eu/dr8/egovera/EthereumApplicationService
dct:title: Ethereum Application Service
Definition: Monitoring in IT refers to the process of observing and tracking the performance, availability, and health of various systems, networks, applications, and services. It involves collecting data, analyzing it in real-time, and generating alerts or reports to ensure that everything is functioning optimally. Monitoring helps identify issues, troubleshoot problems, and make informed decisions to improve the overall performance and reliability of IT infrastructure.
Source: Techopedia
Source reference: https://www.techopedia.com/definition/24560/monitoring
Additional information: Monitoring is a critical aspect of IT management as it allows organizations to proactively identify and address potential issues before they escalate. It involves the use of specialized tools and technologies to continuously collect and analyze data from various sources such as servers, databases, network devices, and applications. This data is then used to generate real-time alerts, performance reports, and visualizations that provide insights into the health and performance of the IT environment. Monitoring can encompass various aspects, including system availability, resource utilization, network traffic, security events, application performance, and user experience.
Example: An example of monitoring in practice is the monitoring of a web server. By continuously monitoring metrics such as CPU usage, memory utilization, network traffic, and response times, IT administrators can identify potential bottlenecks or performance issues. They can set up alerts to be notified if any of these metrics exceed predefined thresholds. Monitoring can also help track website availability and response times from different geographical locations, ensuring a positive user experience. Additionally, monitoring can provide valuable insights into user behavior, allowing organizations to optimize their websites or applications based on usage patterns and trends.
LOST view: TVA-Observability and Monitoring Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/MonitoringApplicationService
EIRA traceability: eira:DigitalSolutionApplicationService
ABB name: egovera:MonitoringApplicationService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-07-20
dct:identifier: http://data.europa.eu/dr8/egovera/MonitoringApplicationService
dct:title: Monitoring Application Service
Description: A digital wallet in the context of EBSI is a type of online storage that lets you securely keep track of your digital assets and information, like digital certificates and digital identity information. It's like a traditional wallet but storing digital information.
Publisher: European Commission
Source: EBSI
LOST view: TVA-Identification and Access Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/EBSIWalletApplicationService
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/egovera/EBSIWalletApplicationService
Name: EBSI Wallet
Interoperability Layer: TechnicalApplication
Realises: http://data.europa.eu/dr8/IdentificationApplicationService
Definition: Smart Queue Management is a digital service that uses advanced algorithms and data analysis to manage and optimize the flow of customers or users in a queue. This service can be used in various sectors such as retail, healthcare, and transportation to improve efficiency and customer satisfaction.
Source: Techopedia
Source reference: https://www.techopedia.com/definition/31575/queue-management-system
Additional information: Smart Queue Management is a technology-driven solution that helps businesses manage customer flow effectively. It uses real-time data and predictive analytics to estimate waiting times, streamline the queuing process, and improve service efficiency. This system can be integrated with digital signage to display queue information and wait times, enhancing the customer experience. It can also provide valuable insights into customer behavior and peak times, enabling businesses to allocate resources more effectively. Moreover, it can reduce physical queues, making it particularly useful in the context of social distancing measures.
Example: In a retail setting, a smart queue management system can be used to manage queues at checkouts, reducing wait times and improving customer satisfaction. It can also provide data on peak times, helping the store to allocate staff more effectively.
In a healthcare setting, such as a hospital or clinic, smart queue management can be used to manage patient flow, reducing wait times and improving patient satisfaction. It can also provide data on peak times, helping the hospital to allocate staff and resources more effectively.
In a transportation setting, such as an airport or train station, smart queue management can be used to manage passenger flow, reducing wait times and improving passenger satisfaction. It can also provide data on peak times, helping the airport or station to allocate staff and resources more effectively.
LOST view: TVA-Analytics Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/SmartQueueManagementApplicationService
ABB name: egovera:SmartQueueManagementApplicationService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/egovera/SmartQueueManagementApplicationService
Name: Smart Queue Management Application Service
Interoperability Layer: TechnicalApplication
Specialises: http://data.europa.eu/dr8/DigitalSolutionApplicationService
Definition: An eFiles Management Digital Service is an electronic system designed to store, manage, and track electronic documents and other media files. It enables users to create, share, organize, and find documents in a centralized digital environment, often providing tools for version control, access permissions, and collaboration.
Source: Techopedia
Source reference: https://www.techopedia.com/definition/23759/electronic-file-management-system
Additional information: The eFiles Management Digital Service is a comprehensive solution that helps organizations transition from paper-based file management systems to digital ones. It encompasses a range of functionalities including document scanning and digitization, metadata tagging for easy search and retrieval, secure access controls to ensure data privacy and compliance with regulations, and audit trails for tracking document history. The service often integrates with other enterprise applications such as email, customer relationship management (CRM) systems, and enterprise resource planning (ERP) systems to streamline workflows and improve productivity. Additionally, it may offer features like automated workflows, electronic signatures, and mobile access to facilitate remote work and collaboration among team members.
Example: Human Resources Document Management
An HR department uses an eFiles Management Digital Service to securely store employee records, including contracts, performance reviews, and personal information. The system allows HR staff to quickly retrieve documents for reference or auditing purposes and ensures that sensitive information is protected with appropriate access controls.
Legal Case File Organization
A law firm implements an eFiles Management Digital Service to manage case files. The system allows lawyers to access case-related documents from anywhere, collaborate on documents with version control, and ensure that all changes are tracked for legal compliance and accountability.
Educational Content Repository
A university uses an eFiles Management Digital Service to manage a repository of educational materials, including lecture notes, research papers, and multimedia content. Professors and students can access and contribute to the repository, which is organized by course and subject matter for ease of use.
Identifier: http://data.europa.eu/dr8/egovera/EFilesManagementApplicationService
ABB name: egovera:EFilesManagementApplicationService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/egovera/EFilesManagementApplicationService
Name: EFiles Management Application Service
Interoperability Layer: TechnicalApplication
Specialises: http://data.europa.eu/dr8/DigitalSolutionApplicationService
Description: ETSI Centre for Testing and Interoperability (CTI) provides a free online tool that performs numerous checkings in order to verify the conformity of the ETSI Advanced Electronic Signatures.
Publisher: ETSI
Source: https://signatures-conformance-checker.etsi.org/pub/index.php
LOST view: TVA-Test Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/ETSISignatureConformanceCheckerApplicationService
EIRA traceability: eira:E-SignatureVerificationAndValidationService
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-08-20
dct:identifier: http://data.europa.eu/dr8/egovera/ETSISignatureConformanceCheckerApplicationService
Definition: Preservation of cargo information refers to the secure and systematic management of data related to the movement and handling of goods during customs processes. This service involves the digital capture, storage, and retrieval of cargo-related information, such as shipping details, transport documents, customs declarations, and inspection reports. By leveraging digital technologies, including data management systems, document repositories, and secure data transmission protocols, the preservation of cargo information ensures the integrity, traceability, and accessibility of critical data throughout the customs clearance process. This service enhances data visibility, facilitates compliance verification, and supports efficient customs operations by providing a centralized, organized, and secure repository for cargo-related information.
Source: Based on World Customs Organization (WCO)
Example: A global logistics company, ABC Logistics, involved in international trade. To comply with customs requirements and streamline their operations, they implement a digital solution for the preservation of cargo information. When receiving a shipment, they capture relevant data such as product descriptions, quantities, and associated documents using barcode scanning. This information is securely stored in a centralized cloud-based system, ensuring easy access and preservation. Customs-related documents like bills of lading and packing lists are organized, version-controlled, and readily available for customs inspections. The digital solution enables secure data transmission to customs authorities, ensuring confidentiality and integrity. ABC Logistics benefits from reduced paperwork, increased data accuracy, improved customs compliance, and efficient information retrieval during audits. The preservation of cargo information digital solution enhances their customs operations, ensuring seamless access to critical cargo data and facilitating smooth trade transactions.
eira:iopDimension: Behavioral IoP
LOST view: TVA-Customs Data Management Enablers [Motivation]
eira:iopSaliency: The Digital Solution Service ABB is salient for technical interoperability because it is a central element the EIF's conceptual model for integrated public services. it represents the generalisation of all application services provided by an Interoperable European Solutionas as stated in the EIF: "Technical interoperability the applications and infrastructures linking systems and services."
Identifier: http://data.europa.eu/dr8/egovera/PreservationOfCargoInformationApplicationService
ABB name: eira:DigitalSolutionApplicationService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-20
dct:identifier: http://data.europa.eu/dr8/egovera/PreservationOfCargoInformationApplicationService
Definition: Accounting ABB is an Application Service that enables the process of tracking and recording access to resources, facilities and information.
Source: Inspired in Springer (Authentication, Authorization and Accounting article)
Source reference: https://link.springer.com/chapter/10.1007/978-3-030-52829-4_14
Example: The following implementation is an example of how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): BASICAL system was developed by the General Administration Intervention Board to give computer support to operations and information in the basic model of the Accounting Information System for Local Governments, in compliance with Order EHA/404/2004, of 23 November, approving the Basic Local Accounting Model Regulations. https://administracionelectronica.gob.es/ctt/verPestanaGeneralAbstract.htm?idIniciativa=basical#.ZAISY3bMI2w
eira:iopDimension: Behavioral IoP
LOST view: TVA-Customs Identification and Access Enablers [Motivation]
eira:iopSaliency: The Accounting Application Service ABB is salient for interoperability because it can be a mechanism to track and control access to data, applications, and services. This can help to identify when unauthorised changes or accesses have been accepted and data in a digital public servicer has been compromised and whom is the actor involved.
Identifier: http://data.europa.eu/dr8/AccountingApplicationService
ABB name: eira:AccountingApplicationService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2022-01-18
dct:identifier: http://data.europa.eu/dr8/AccountingApplicationService
Definition: Virtual Dataset ABB is a Data Object that enables a dynamic and logical representation of data that aggregates, integrates, or transforms data from multiple sources into a single view
Source: H5PY
Source reference: https://docs.h5py.org/en/stable/vds.html
Example: The following implementation is an example of how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): Virtual Datasets (VDS) is an example of a distribution for the creation of virtual datasets. https://docs.h5py.org/en/stable/vds.html
Interoperability Dimension: Structural IoP
LOST view: Semantic view
Viewpoint: Interoperability Privacy viewpoint
Interoperability Saliency: The Virtual Dataset Data Object ABB is salient for semantic interoperability due to its position on and capability for transforming data from different and multiple channels to a single view allowing and increasing the reuse and shareability of data across organisations and digital public services.
Identifier: http://data.europa.eu/dr8/VirtualDatasetDataObject
ABB name: eira:VirtualDatasetDataObject
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/VirtualDatasetDataObject
Interoperability Layer: Semantic
Definition: Goods Metadata ABB is a DataSet Data Object that encapsulates detailed information about goods or products within an organization's system. This metadata typically includes data attributes such as product name, SKU (Stock Keeping Unit), manufacturer details, specifications, pricing, availability, and relevant classifications. It serves as a crucial element for effective management of product information, enabling accurate tracking, inventory management, and seamless integration with various business processes like sales, procurement, and supply chain operations. This data object is instrumental in enhancing data consistency, facilitating efficient retrieval and analysis of product information, and ensuring that business decisions are informed by comprehensive and up-to-date product details.
Source: European Commission
Source reference: https://data.europa.eu/data/datasets/combined-nomenclature-2023?locale=en
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/egovera/GoodsMetadataDataObject
EIRA traceability: eira:DataSetCatalogueDataObject
EIRA concept: eira:ArchitectureBuildingBlock
Additional identifier: http://data.europa.eu/dr8/egovera/GoodsMetadataDataObject
ABB name: egovera:GoodsMetadataDataObject
Example: The Combined Nomenclature (CN) is an integral part of the EU's system of tariff and statistical nomenclature and is used for the customs tariff and for external trade statistics. It provides a basis for the collection and analysis of trade data, customs tariffs, and for trade negotiations.
eira:eifLayer: Semantic
Definition: Translation Item Metadata refers to structured information that provides descriptive and contextual details about a translation item or unit of content in a translation process. It includes attributes such as the item's source language, target language, content type, translation status, translator information, and any additional metadata that helps define its characteristics and supports the translation workflow. Translation Item Metadata enables efficient management, tracking, and quality control of translation tasks, ensuring accuracy and consistency across multilingual content.
Source: Based on relevant standards for translation services
LOST view: SV-Business Agnostic Metadata
Identifier: http://data.europa.eu/dr8/egovera/TranslationItemMetadataDataObject
ABB name: egovera:TranslationItemMetadataDataObject
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/egovera/TranslationItemMetadataDataObject
Interoperability Layer: Semantic
Specialises: http://data.europa.eu/dr8/DataSetDataObject
Description: The Asset Description Metadata Schema (ADMS) is a standard metadata specification developed by the European Commission's ISA² program (Interoperability Solutions for European Public Administrations). ADMS is designed to facilitate the description and discovery of digital assets, particularly in the context of public administration.
Publisher: W3C
Source: https://www.w3.org/TR/vocab-adms/
LOST view: SV-Agnostic Ontologies
Identifier: http://data.europa.eu/dr8/egovera/ADMSDataObject
EIRA traceability: eira:ControlledVocabularyDataObject
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-08-20
dct:identifier: http://data.europa.eu/dr8/egovera/ADMSDataObject
Definition: Data ABB is a Data Object that enables the implementation of digital or non-digital information that is collected, stored, or processed by a computer system or other information technology infrastructure. This information can take many forms, including text, numbers, images, video, audio, and more.
Source: ISO-IEC-2382-1 * 1993 *
Source reference: https://www.iso.org/obp/ui/#iso:std:iso-iec:2382:ed-1:v1:en
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): https://www.eea.europa.eu/data-and-maps/dashboards/emissions-trading-viewer-1
Interoperability Dimension: Structural IoP
LOST view: Semantic view
Viewpoint: Interoperability Privacy viewpoint
Interoperability Saliency: The Data ABB is salient for semantic interoperability because it represents the most important mean of interaction between ICT systems of organisations in order to ensure interoperability as stated in the EIF recommendation n° 30: "Perceive data and information as a public asset that should be appropriately generated, collected, managed, shared, protected and preserved."
Identifier: http://data.europa.eu/dr8/DataDataObject
ABB name: eira:DataDataObject
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/DataDataObject
Interoperability Layer: Semantic
Definition: A High Value Dataset refers to a collection of data that is deemed to be of significant value to a wide range of users, including the public, researchers, and policy makers, due to its potential to contribute to economic growth, transparency, and societal advancements.
Source: Open Data Handbook
Source reference: http://opendatahandbook.org/glossary/en/terms/high-value-dataset/
Additional information: The concept of a High Value Dataset typically encompasses datasets that are frequently requested by users or have the potential to be leveraged for high-impact applications. These datasets are often characterized by their quality, completeness, timeliness, and ease of access. Governments and organizations prioritize the release of such datasets to foster innovation, improve government transparency, and enable data-driven decision-making. Criteria for determining a dataset's 'high value' can include its relevance to public interest, contribution to the improvement of government services, support for economic growth, and enhancement of public knowledge.
Example: Examples of High Value Datasets include national health statistics, which can inform public health policy and research; real-time public transportation data, which can improve urban mobility and planning; and government expenditure data, which promotes transparency and accountability in public finance. Another example is geospatial data, which is crucial for a wide range of applications such as environmental monitoring, urban planning, and disaster response.
Interoperability Dimension: Structural IoP
Identifier: http://data.europa.eu/dr8/egovera/HighValueDatasetDataObject
ABB name: egovera:HighValueDatasetDataObject
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/egovera/HighValueDatasetDataObject
Name: High Value Dataset
Interoperability Layer: Semantic
Description: To support an effective Single Market, the Commission encourages suppliers and contracting authorities/entities to adopt best practice and use electronic communication and information technology to provide all the relevant information, so as to ensure best value for money in public procurement.
Interoperability Dimension: Structural IoP
Publisher: Eurostat
Source: https://ec.europa.eu/eurostat/web/regions-and-cities/overview
LOST view: SV-Agnostic Reference Data
Identifier: http://data.europa.eu/dr8/egovera/NUTSDataObject
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/egovera/NUTSDataObject
Interoperability Layer: Semantic
Realises: http://data.europa.eu/dr8/ReferenceData
Description: Ontology Engineer IngGroup
Interoperability Dimension: Structural IoP
Publisher: Linked Open Vocabularies (LOV) is a comprehensive and curated collection of vocabularies or ontologies that are openly available on the web and interconnected through semantic links. LOV serves as a resource for the Semantic Web community, providing a repository of vocabularies that can be used to describe and annotate data in a standardized and interoperable manner.
Source: https://lov.linkeddata.es/dataset/lov/
LOST view: SV-Agnostic Ontology Catalogue
Identifier: http://data.europa.eu/dr8/egovera/LinkedOpenVocabulariesDataObject
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/egovera/LinkedOpenVocabulariesDataObject
Interoperability Layer: Semantic
Realises: http://data.europa.eu/dr8/OntologiesCatalogueDataObject
Definition: Controlled Vocabulary ABB is a Data Object that enables a carefully curated set of terms used to describe concepts or objects in a specific field or domain. It is a standardized list of terms that are used to ensure consistency and accuracy in the indexing, searching, and retrieval of information
Source: Joinup
Source reference: https://joinup.ec.europa.eu/collection/catalogue-services/document/controlled-vocabularies
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): EuroVoc - EuroVoc is a multilingual, multidisciplinary thesaurus covering the activities of the EU, the European Parliament in particular. It contains terms in 23 EU languages (Bulgarian, Croatian, Czech, Danish, Dutch, English, Estonian, Finnish, French, German, Greek, Hungarian, Italian, Latvian, Lithuanian, Maltese, Polish, Portuguese, Romanian, Slovak, Slovenian, Spanish and Swedish), plus in three languages of countries which are candidates for EU accession: македонски (mk), shqip (sq) and cрпски (sr). (https://op.europa.eu/en/web/eu-vocabularies/th-dataset/-/resource/dataset/eurovoc)
Interoperability Dimension: Structural IoP
LOST view: Semantic view
Interoperability Saliency: The Controlled Vocabulary ABB is salient for semantic interoperability because it ensures compatible interpretations of words and phrases used to index content and/or to retrieve content through browsing or searching.
Identifier: http://data.europa.eu/dr8/ControlledVocabularyDataObject
ABB name: eira:ControlledVocabularyDataObject
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/ControlledVocabularyDataObject
Interoperability Layer: Semantic
Definition: Forms Structure ABB is a Data Object that enables the implementation of the layout and organization of the fields, labels and controls on a form used to collect or display data.
Source: Inspired in Science Direct
Source reference: https://www.sciencedirect.com/topics/computer-science/formal-structure
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): Standard forms for public procurement - o help you publish EU public procurement data in the Official Journal, the European Commission has created standard forms aligned with each of the EU legal bases in place for publishing this data, namely: - TED schema forms set out in Regulation (EU) 2015/1986; - eForms set out in Regulation (EU) 2019/1780. https://simap.ted.europa.eu/standard-forms-for-public-procurement
Interoperability Dimension: Structural IoP
LOST view: Semantic view
Interoperability Saliency: The Forms Structure Data Object ABB is salient for semantic interoperability because the harmonisation of forms structures can contribute to data accessibility and reuse.
Identifier: http://data.europa.eu/dr8/FormsStructureDataObject
ABB name: eira:FormsStructureDataObject
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/FormsStructureDataObject
Interoperability Layer: Semantic
Definition: Refers to a specialized classification framework developed and implemented by a specific country's customs authority. This taxonomy is tailored to categorize and organize customs-related data, regulations, and procedures unique to that nation's trade and customs environment. It provides a standardized structure that aids in consistent data classification, harmonization of customs processes, and effective management of customs-related information within the country's customs ecosystem. This taxonomy enables efficient customs operations, enhances trade facilitation, and supports accurate reporting and analysis while catering to the specific requirements and nuances of the national customs context.
Source: Based on European Commission Sources
LOST view: SV-Customs Controlled Vocabularies [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/NationalCustomsSpecificTaxonomyDataObject
EIRA traceability: eira:ControlledVocabularyDataObject
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-20
dct:identifier: http://data.europa.eu/dr8/egovera/NationalCustomsSpecificTaxonomyDataObject
Definition: Data Mapping Catalogue ABB is a Data Object aiming to index an inventory of rules or procedures on how data from different sources and domains can be linked and integrated.
Source: European Comision
Source reference: https://digital-strategy.ec.europa.eu/en/library/staff-working-document-data-spaces
Additional information: A data Mapping Catalogue stores the data mappings with comprehensiveness and trustiness value. This ABB is a key interoperability enabler (*) for sharing/PROVISIONING and reusing/CONSUMING Data.
Example: CEMS Rapid Mapping - JRC - The Joint Research Centre (JRC) is the European Commission's science and knowledge service which employs scientists to carry out research in order to provide independent scientific advice and support to EU policy. Rapid Mapping is one of the two on-demand mapping services under the Copernicus Emergency Management Service (CEMS). Rapid Mapping delivers geospatial information (in different vector and raster formats) in the midst of or immediately after catastrophic events or humanitarian crises. It is available 24/7/365. Supported disaster types range from natural hazards such as floods, fires, storms, tsunamis, volcanic eruptions, landslides, and earthquakes to industrial accidents and humanitarian crises. (https://data.jrc.ec.europa.eu/collection/id-0072)
Interoperability Dimension: Structural IoP
LOST view: Semantic view
Viewpoint: Key Interoperability Enablers viewpoint
Interoperability Saliency: The Data Mapping Catalogue ABB is a key interoperability enabler (*) for structural interoperability by ensuring the mapping of data by digital public services.
Identifier: http://data.europa.eu/dr8/DataMappingCatalogueDataObject
ABB name: eira:DataMappingCatalogueDataObject
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/DataMappingCatalogueDataObject
Interoperability Layer: Semantic
Description: CDM is an ontology based on the FRBR model (Functional Requirements for Bibliographic Records). CDM uses RDF(S)/OWL technologies, capable of representing relationships between the resource types managed by the Publications Office and their views. All within the scope of the FRBR model and, therefore, in terms of Work, Expression, Manifestation and Item.
Publisher: The Publications Office of the European Union
Source: https://op.europa.eu/en/web/eu-vocabularies/cdm
LOST view: SV-Business Agnostic Data Models
Identifier: http://data.europa.eu/dr8/egovera/CommonDataModelDataObject
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/egovera/CommonDataModelDataObject
Interoperability Layer: Semantic
Realises: http://data.europa.eu/dr8/DataModelDataObject
Definition: Dataset Catalogue ABB is a Data Object aimed at indexing a collection (inventory) of datasets in a systematic manner.
Source: W3C-Data Catalogue Vocabulary
Source reference: https://www.w3.org/TR/vocab-dcat/#class-catalog
Additional information: (*)DECISION (EU) 2015/2240 OF THE EUROPEAN PARLIAMENT AND OF THE COUNCIL of 25 November 2015 establishing a programme on interoperability solutions and common frameworks for European public administrations, businesses and citizens (ISA2 programme) as a means for modernising the public sector.
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): Agricultural and Vegetable Catalogue - The seed of varieties of agricultural and plant species and varieties of vegetable species that are published in the EU level common catalogue is subject to no marketing restrictions with the Community. Publication in the catalogue must be approved as fulfilling minimum requirements laid down in legislation. Data is published on the contents of the catalogues for agricultural and vegetal species and maintainers with details of the reference list.(https://data.europa.eu/euodp/data/dataset/7A98oEqVa83q6L7tHQ)
Interoperability Dimension: Structural IoP
LOST view: Semantic view
Viewpoint: Key Interoperability Enablers viewpoint
Interoperability Saliency: The Dataset catalogue ABB is a key interoperability enabler (*) for semantic and structural interoperability by ensuring the provision/consumption of data by digital public services.
Identifier: http://data.europa.eu/dr8/DatasetCatalogueDataObject
ABB name: eira:DatasetCatalogueDataObject
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/DatasetCatalogueDataObject
Interoperability Layer: Semantic
Definition: Data Format ABB is a Data Object that enables the methods and structures in which data is organized and structured within a file or dataset
Source: Inspired in Common European Research Forma
Source reference: https://joinup.ec.europa.eu/collection/eu-semantic-interoperability-catalogue/solution/common-european-research-information-format/about
Example: The following implementation is an example of how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): European Data Format, a simple and flexible format for the exchange and storage of multichannel biological and physical signals. It was developed by a few European 'medical' engineers who first met at the 1987 international Sleep Congress in Copenhagen. https://www.edfplus.info/). CSV is also a data format https://www.loc.gov/preservation/digital/formats/fdd/fdd000323.shtml
Interoperability Dimension: Structural IoP
LOST view: Semantic view
Interoperability Saliency: The Data Format Data Object ABB is a key interoperability enabler and salient for semantic interoperability because it provides a common and structured method to organise data, ensuring data quality and successful data exchanges between public administrations and digital public services
Identifier: http://data.europa.eu/dr8/DataFormatDataObject
ABB name: eira:DataFormatDataObject
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/DataFormatDataObject
Interoperability Layer: Semantic
Description: The Asset Description Metadata Schema (ADMS) is a standard metadata specification developed by the European Commission's ISA² program (Interoperability Solutions for European Public Administrations). ADMS is designed to facilitate the description and discovery of digital assets, particularly in the context of public administration.
Publisher: European Commission
Source: https://joinup.ec.europa.eu/collection/support-centre/solution/asset-description-metadata-schema-adms/about
LOST view: SV-Agnostic Ontologies
Identifier: http://data.europa.eu/dr8/egovera/ADMS-APDataObject
EIRA traceability: eira:ControlledVocabularyDataObject
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-08-20
dct:identifier: http://data.europa.eu/dr8/egovera/ADMS-APDataObject
Definition: Tender Item Metadata refers to structured information that provides details about specific items or products included in a tender or procurement process. It encompasses attributes such as item name, description, quantity, unit of measure, pricing, specifications, and any additional metadata relevant to the tender item. Tender Item Metadata helps in accurately describing and categorizing items, facilitating the procurement process, comparing bids, and ensuring transparency and fairness in tender evaluations.
Source: European Single Procurement Document (ESPD)
LOST view: SV-Business Agnostic Metadata
Identifier: http://data.europa.eu/dr8/egovera/TenderItemMetadataDataObject
ABB name: egovera:TenderItemMetadataDataObject
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/egovera/TenderItemMetadataDataObject
Interoperability Layer: Semantic
Specialises: http://data.europa.eu/dr8/DataSetDataObject
Description: The Core Vocabularies can be used by public administrations to attain a minimum level of semantic interoperability for e-Government systems. The Handbook explains how to (a) design new data models that extend the Core Vocabularies; and (b) map existing data models to the Core Vocabularies.
Publisher: European Comission
Source: https://joinup.ec.europa.eu/collection/semic-support-centre/core-vocabularies
LOST view: Semantic view
Identifier: http://data.europa.eu/dr8/egovera/SEMICCoreVocabulariesDataObject
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/egovera/SEMICCoreVocabulariesDataObject
Interoperability Layer: Semantic
Realises: http://data.europa.eu/dr8/ControlledVocabularyDataObject
Description: The Digital Europa Thesaurus (DET) is a multilingual thesaurus covering the main subject matters of the European Commission's public communications.
Interoperability Dimension: Structural IoP
Publisher: Publications Office of the European Union
Source: https://op.europa.eu/en/web/eu-vocabularies/det
LOST view: SV-Agnostic Reference Data
Identifier: http://data.europa.eu/dr8/egovera/DigitalEuropeThesaurusDataObject
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/egovera/DigitalEuropeThesaurusDataObject
Interoperability Layer: Semantic
Realises: http://data.europa.eu/dr8/ReferenceData
Description: This dataspace comprise INSPIRE themes, reference parcels, and agricultural parcels
Publisher: European Comission- Directive 2019/1024
Source: https://eur-lex.europa.eu/legal-content/EN/TXT/PDF/?uri=CELEX:32019L1024
LOST view: SV-Business Agnostic High Value Dataset
Identifier: http://data.europa.eu/dr8/egovera/GeospatialHighValueDatasetDataObject
EIRA traceability: eira:DataSetCatalogueDataObject
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-08-20
dct:identifier: http://data.europa.eu/dr8/egovera/GeospatialHighValueDatasetDataObject
Description: The ISO country codes are internationally recognized codes that designate every country and most of the dependent areas a two-letter combination or a three-letter combination; it is like an acronym, that stands for a country or a state. The country code is in use for example for the two-letter suffixes such as .us (United States), .fr (France) or .de (Germany) in top-level domains (for countries) on the Internet. The three letter code is also often used at events with international participants from various countries like sports meetings or song contests, where you can see abbreviations like CAN (for Canada), DNK (for Denmark), AUS (for Australia). Below is a list of two-letter codes (ISO alpha-2), and the three letter codes (ISO alpha-3), as well as the United Nations, used numerical code M49 for countries, dependencies, and other areas. (Dependencies marked in Italic writing)
Publisher: ISO
Source: https://www.nationsonline.org/oneworld/country_code_list.htm
LOST view: SV-Reference Data [Motivation]
Identifier: http://data.europa.eu/dr8/ReferenceDataObject
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-01-16
dct:identifier: http://data.europa.eu/dr8/egovera/
Definition: Laboratories Testing Metadata ABB is a DataSet Data Object that encompasses all the detailed information related to tests and analyses conducted in laboratories. It includes data such as the type of test, test results, date and time of testing, sample information, laboratory equipment used, technician details, and any relevant standards or protocols followed. Laboratories Testing Metadata is crucial for ensuring the accuracy and traceability of test results, compliance with quality standards, and effective management of laboratory operations.
Source: European Commission
Source reference: https://taxation-customs.ec.europa.eu/customs-4/customs-laboratories_en
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/egovera/LaboratoriesTestingMetadataDataObject
EIRA traceability: eira:DataSetDataObject
LOST view: SV-Customs Datasets [Motivation]
EIRA concept: eira:ArchitectureBuildingBlock
ABB name: egovera:LaboratoriesTestingMetadataDataObject
Additional identifier: http://data.europa.eu/dr8/egovera/LaboratoriesTestingMetadataDataObject
eira:eifLayer: Semantic
Description: This dataspace comprise INSPIRE themes, environmental information according to the environmental information directive, and datasets related to select legal acts.
Publisher: European Comission- Directive 2019/1024
Source: https://eur-lex.europa.eu/legal-content/EN/TXT/PDF/?uri=CELEX:32019L1024
LOST view: SV-Business Agnostic High Value Dataset
Identifier: http://data.europa.eu/dr8/egovera/EarthObservationDataHighValueDatasetDataObject
EIRA traceability: eira:DataSetCatalogueDataObject
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-08-20
dct:identifier: http://data.europa.eu/dr8/egovera/EarthObservationDataHighValueDatasetDataObject
Definition: Ontologies Catalogue ABB is a Data Object aiming at indexing the collection of ontologies with comprehensiveness and trustiness value
Source: Joinup
Source reference: https://joinup.ec.europa.eu/taxonomy/term/http_e_f_fdata_ceuropa_ceu_fdr8_fOntologiesCatalogue
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): BioPortal - BioPortal is a repository of over 300 biomedical ontologies and includes tools for working with these ontologies. Holds most widely used Biomedical ontologies. Allows ontologies to be browsed, searched, and reviewed. Allows uses to create notes on ontologies terms. Allows arbitrary text to be annotated with ontology terms. Also supports search of biomedical resources (e.g. PubMed) for combinations of terms from ontologies. Allows programmatic access to ontologies through a REST interface.(http://bioportal.bioontology.org/)
Interoperability Dimension: Structural IoP
LOST view: Semantic view
Viewpoint: Key Interoperability Enablers viewpoint
Interoperability Saliency: The Ontologies catalogue ABB is a key interoperability enabler (*) for structural interoperability because it ensures the provision/consumption of ontologies by digital public services.
Identifier: http://data.europa.eu/dr8/OntologiesCatalogueDataObject
ABB name: eira:OntologiesCatalogueDataObject
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/OntologiesCatalogueDataObject
Interoperability Layer: Semantic
Description: AEO stands for Authorized Economic Operator. It is a status granted to businesses by customs administrations in the European Union (EU) and many other countries worldwide. The AEO program aims to enhance international supply chain security and facilitate trade by recognizing businesses that meet certain criteria and demonstrate compliance with customs regulations and security standards.
Publisher: European Commission
Source: https://ec.europa.eu/taxation_customs/dds2/eos/aeo_home.jsp?Lang=en
LOST view: SV-Customs Base Registries [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/AEO-AuthorisedEconomicOperatorDataObject
EIRA traceability: eira:BaseRegistryDataObject
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-08-20
dct:identifier: http://data.europa.eu/dr8/egovera/AEO-AuthorisedEconomicOperatorDataObject
Description: The database contains information on regulated professions, statistics on migrating professionals, contact points and competent authorities, as provided by EU Member States, EEA countries, the UK and Switzerland.
Interoperability Dimension: Structural IoP
Publisher: European Commission
Source: https://ec.europa.eu/growth/tools-databases/regprof/home
LOST view: SV-Agnostic Reference Data
Identifier: http://data.europa.eu/dr8/egovera/RegulatedProfessionsDBDataObject
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/egovera/RegulatedProfessionsDBDataObject
Interoperability Layer: Semantic
Realises: http://data.europa.eu/dr8/ReferenceData
Definition: A Data Policy, within the realm of taxation regulations, refers to a set of guidelines and rules that govern the collection, processing, storage, and dissemination of data related to tax matters. This policy ensures that tax-related data is handled in a manner that is compliant with legal requirements, protects taxpayer confidentiality, and maintains data integrity and security. It outlines the responsibilities of tax authorities and other stakeholders in managing tax data, and includes provisions for data sharing, data retention periods, and the use of data for compliance, enforcement, and analytical purposes. The policy is designed to balance the need for effective tax administration with the rights of individuals and organizations to have their personal and financial information protected.
Source: EIRA team
Additional information: A Data Policy in the context of European Tax Regulation is a comprehensive framework that outlines the principles, legal requirements, and best practices for the collection, processing, storage, sharing, and protection of data, particularly personal and financial information, within the realm of taxation. This policy is designed to ensure that all data handling activities comply with relevant tax laws and regulations, such as the General Data Protection Regulation (GDPR), and other specific tax-related directives and legislation.
The Data Policy encompasses various aspects of data governance, including:
1. Data Collection: The policy defines what types of data can be collected for tax purposes, the lawful basis for its collection, and the methods by which it is obtained. It ensures that only necessary data is collected, and that taxpayers are informed about the reasons for data collection and their rights regarding their personal data.
2. Data Processing: It sets out the conditions under which data can be processed, ensuring that processing is done lawfully, fairly, and transparently. The policy stipulates that data processing should be relevant to and not excessive for tax administration purposes, and that it should be kept accurate and up-to-date.
3. Data Storage: The policy details the security measures that must be in place to protect data during storage, including encryption, access controls, and regular audits. It also specifies retention periods, after which personal data should be securely deleted or anonymized, in accordance with legal requirements and the principle of data minimization.
4. Data Sharing: It outlines the circumstances under which data can be shared with other tax authorities, government agencies, or third parties, including international data transfers. The policy ensures that data sharing is compliant with data protection laws and that appropriate safeguards are in place to maintain the confidentiality and integrity of the data.
5. Data Protection: The policy mandates the implementation of technical and organizational measures to safeguard data against unauthorized access, accidental loss, destruction, or damage. It includes requirements for data breach notification procedures and the prompt reporting of any data security incidents to the relevant supervisory authorities and affected individuals.
6. Data Subject Rights: The policy enshrines the rights of individuals with respect to their data, such as the right to access, rectify, erase, or port their data, and the right to object to its processing. It provides mechanisms for individuals to exercise these rights and ensures that requests are handled within the legal timeframes.
7. Compliance and Enforcement: The policy includes provisions for monitoring compliance with data protection laws, conducting regular assessments and audits, and addressing any identified gaps or weaknesses. It also describes the penalties and enforcement actions that can be taken against entities that fail to comply with the data policy.
8. Accountability and Training: It establishes the roles and responsibilities of those involved in data handling, including the appointment of a Data Protection Officer (DPO) where required. The policy mandates ongoing training and awareness programs for staff to ensure they understand their obligations under the data policy and the importance of protecting taxpayer data.
Overall, the Data Policy serves as a critical tool for tax authorities and related entities to manage tax-related data responsibly and ethically, fostering trust and compliance among taxpayers while meeting the stringent requirements of European tax laws and data protection regulations.
Example: Data policies in the context of taxation often encompass the following elements:
1. **Data Collection and Processing**: The policy outlines what types of personal and financial data are collected from taxpayers, such as income, expenses, investments, and other relevant financial information. It also details the methods of data collection, whether through tax filings, third-party reporting, or automatic exchange of information between countries.
2. **Data Accuracy and Retention**: This aspect of the policy mandates the accuracy of the data collected and sets forth the duration for which the data must be retained. It ensures that taxpayers' data is up-to-date and stored securely for a period that complies with legal requirements, often several years.
3. **Data Sharing and Confidentiality**: The policy defines the circumstances under which tax-related data can be shared with other governmental agencies, international bodies, or third parties. It also includes provisions to protect the confidentiality of personal and financial data, preventing unauthorized access and disclosure.
4. **Data Security**: Security measures are specified to protect data from breaches, loss, or corruption. This includes encryption, access controls, and regular audits to ensure that data is handled securely throughout its lifecycle.
5. **Compliance with Legal Obligations**: The policy ensures that data handling practices are in compliance with relevant laws and regulations, such as the General Data Protection Regulation (GDPR), which governs the processing of personal data within the European Union.
6. **Data Subject Rights**: Taxpayers are granted rights in relation to their data, including the right to access their data, request corrections, object to processing, and in some cases, the right to data portability or the right to be forgotten.
7. **Data Use for Tax Compliance and Enforcement**: The policy may specify how data is used to ensure tax compliance, including the application of data analytics for risk assessment, identifying non-compliance or fraud, and supporting tax audits and investigations.
8. **International Data Exchange**: Provisions for the automatic exchange of information with other countries for tax purposes, in accordance with international agreements and standards, such as the Common Reporting Standard (CRS).
9. **Data Reporting by Third Parties**: Requirements for financial institutions and other third parties to report financial information to tax authorities, which is critical for the accurate assessment of taxes owed.
10. **Oversight and Governance**: The establishment of a governance structure to oversee data management practices, including roles and responsibilities for data protection officers and other relevant personnel.
These examples of data policy elements ensure that tax authorities collect, process, and manage taxpayer data responsibly and in accordance with legal requirements, while also safeguarding taxpayer privacy and promoting efficient tax administration.
Identifier: http://data.europa.eu/dr8/egovera/DataPolicyDataObject
ABB name: egovera:DataPolicyDataObject
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/egovera/DataPolicyDataObject
Name: Data Policy Data-object
Interoperability Layer: Semantic
Specialises: http://data.europa.eu/dr8/DataPolicyBusinessObject
Definition: Service Registry ABB is a Data Object that enables the implementation of a central repository of information that contains metadata about the available digital services.
Source: Redhat
Source reference: https://www.redhat.com/en/topics/integration/what-is-a-service-registry
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): ZooKeeper - ZooKeeper is a centralized service registry for maintaining configuration information, naming, providing distributed synchronization, and providing group services. All of these kinds of services are used in some form or another by distributed applications. Each time they are implemented there is a lot of work that goes into fixing the bugs and race conditions that are inevitable. Because of the difficulty of implementing these kinds of services, applications initially usually skimp on them, which make them brittle in the presence of change and difficult to manage. Even when done correctly, different implementations of these services lead to management complexity when the applications are deployed. https://zookeeper.apache.org/
Interoperability Dimension: Structural IoP
LOST view: Technical view - application
Interoperability Saliency: The Service Registry ABB is a key interoperability enabler because it provides access to software systems over the Internet using standard protocols. In the most basic scenario there is a Web Service Provider that publishes a service and a Web Service Consumer that uses this service.
Identifier: http://data.europa.eu/dr8/ServiceRegistryDataObject
ABB name: eira:ServiceRegistryDataObject
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/ServiceRegistryDataObject
Interoperability Layer: TechnicalApplication
Definition: Ontology ABB is a Data Object that defines a set of representational primitives with which to model a domain of knowledge or discourse
Source: Formal definiion of Tom Gruber
Source reference: https://tomgruber.org/writing/definition-of-ontology
Additional information: Ontology ABB is a Data Object aiming to be a formal description of knowledge, as a set of concepts, within a domain and the axioms connecting concepts and allowing for logic inferences. When speaking about an ontology, we do not refer only to the terminology (or T-Box) but also to all the “assertions” about the concepts and roles (the A-Box), i.e. all the individuals or instances of concepts and roles of the terminology and as important, the rules for logic inference: the semantics “part".
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): Medical Dictionary for Regulatory Activities Terminology (MedDRA) - The university ontology includes classes, e.g., :Staff, :Students, :Department or :Course. These classes denote natural concepts that are shared or at least understood by users familiar with universities all over the world. Universities ontologies can be view in university portals.(http://bioportal.bioontology.org/ontologies/MEDDRA)
Interoperability Dimension: Structural IoP
LOST view: Semantic view
Viewpoint: Interoperability Privacy viewpoint
Interoperability Saliency: The Ontology ABB is salient for semantic interoperability because it defined as a simplified, reusable and extensible data model that capture the fundamental characteristics of a data entity in a context-neutral and syntax-neutral fashion.
Identifier: http://data.europa.eu/dr8/OntologyDataObject
ABB name: eira:OntologyDataObject
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/OntologyDataObject
Interoperability Layer: Semantic
Description: The Combined Nomenclature (CN) is a tool for classifying goods, set up to meet the requirements both of the Common Customs TariffEN••• and of the EU's external trade statistics. The CN is also used in intra-EU trade statistics. It is a further development (with special EU-specific subdivisions) of the World Customs Organization'sHarmonized System nomenclature. This is a systematic list of commodities applied by most trading nations (and also used for international trade negotiations).
Publisher: European Commission
Source: https://eur-lex.europa.eu/legal-content/EN/TXT/PDF/?uri=OJ:L:2022:282:FULL&from=EN
LOST view: SV-Customs Controlled Vocabularies [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/CombinedNomenclatureDataObject
EIRA traceability: eira:ControlledVocabularyDataObject
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2022-17-01
Description: The EUROSTAT data catalogue is a comprehensive repository of statistical data and indicators maintained by EUROSTAT, the statistical office of the European Union (EU). It serves as a central platform for accessing a wide range of statistical information about the EU and its member states. The catalogue provides a structured and organized collection of datasets covering various domains such as economy, population, employment, agriculture, trade, and many others.
Publisher: Eurostat
Source: https://ec.europa.eu/eurostat/web/main/home
LOST view: SV-Datasets Catalogue Solutions
Identifier: http://data.europa.eu/dr8/egovera/EurostatDataCatalogueDataObject
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/egovera/EurostatDataCatalogueDataObject
Interoperability Layer: Semantic
Realises: http://data.europa.eu/dr8/DataSetCatalogueDataObject
Definition: API Catalogue ABB is a Data Object that corresponds to a collection of (open) software interfaces that allow data consumption by a specific digital solution
Source: Inspired in JRC
Source reference: https://data.jrc.ec.europa.eu/dataset/5a431f38-1e2c-449a-898e-34f2a3234c3b
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): RapidAPI - RapidAPI is a collection of predefined APIs that are free to test, specifically updated for 2021. https://rapidapi.com/collection/list-of-free-apis
Interoperability Dimension: Structural IoP
LOST view: Technical view - application
Interoperability Saliency: The API Catalogue Data Object ABB is salient for interoperability as it is a collection of software interfaces that allows data consumption between solutions and services.
Identifier: http://data.europa.eu/dr8/APICatalogueDataObject
ABB name: eira:APICatalogueDataObject
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/APICatalogueDataObject
Interoperability Layer: TechnicalApplication
Description: EuroVoc is the EU's multilingual and multidisciplinary thesaurus. It contains keywords, organized in 21 domains and 127 sub-domains, which are used to describe the content of documents in EUR-Lex.
Publisher: Publications Office
Source: https://op.europa.eu/en/web/eu-vocabularies/dataset/-/resource?uri=http://publications.europa.eu/resource/dataset/eurovoc
LOST view: SV-Agnostic Vocabularies
Identifier: http://data.europa.eu/dr8/egovera/EuroVocDataObject
EIRA traceability: eira:ControlledVocabularyDataObject
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-08-20
dct:identifier: http://data.europa.eu/dr8/egovera/EuroVocDataObject
Definition: Authorised Payment Methods Metadata refers to structured information that provides details about the various payment methods that are accepted and authorized by a system or platform for financial transactions. It includes attributes such as payment method type, supported currencies, transaction limits, authentication requirements, and any additional metadata that helps define the characteristics and specifications of each payment method. Authorised Payment Methods Metadata enables seamless integration and processing of different payment methods, ensuring secure and efficient financial transactions.
Source: OpenAPI Specification (OAS)
Source reference: https://www.openapis.org/
LOST view: SV-Business Agnostic Metadata
Identifier: http://data.europa.eu/dr8/egovera/AuthorisedPaymentMethodsMetadataDataObject
EIRA traceability: eira:DataSetDataObject
ABB name: egovera:AuthorisedPaymentMethodsMetadataDataObject
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2022-01-16
Definition: Applications and Requests Metadata ABB is a data object that contains comprehensive details about various applications and requests processed within an organization. It encompasses information such as application types (e.g., customer requests, service applications, permit requests), applicant details, processing stages, required documents, decision outcomes, and timelines. Applications and Requests Metadata is essential for streamlining process workflows, enhancing customer service, and providing transparency and accountability in application processing and decision-making.
Source: European Commission
Source reference: https://taxation-customs.ec.europa.eu/online-services/online-services-and-databases-customs/eu-customs-trader-portal_en
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/egovera/ApplicationsAndRequestsMetadataDataObject
EIRA traceability: eira:DataSetDataObject
LOST view: SV-Customs Datasets [Motivation]
EIRA concept: eira:ArchitectureBuildingBlock
ABB name: egovera:ApplicationsAndRequestsMetadataDataObject
Additional identifier: http://data.europa.eu/dr8/egovera/ApplicationsAndRequestsMetadataDataObject
EIF Layer: Semantic
Definition: Goods taxonomy metadata ABB is DataSet Data Object that provides a structured and detailed classification system for categorizing various goods or products within an enterprise. It includes comprehensive classifications such as categories, subcategories, attributes, product codes, and descriptions, facilitating efficient organization, retrieval, and standardization of product information. This metadata is integral to supply chain management, effective data analysis, compliance, reporting, and seamless integration with other enterprise systems like ERP and CRM, thereby enhancing overall operational efficiency and decision-making processes.
Source: European Commission
Source reference: https://data.europa.eu/data/datasets/combined-nomenclature-2023?locale=en
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/egovera/GoodsTaxonomyMetadataDataObject
EIRA traceability: eira:DataSetDataObject
LOST view: SV-Customs Datasets [Motivation]
EIRA concept: eira:ArchitectureBuildingBlock
ABB name: egovera:GoodsTaxonomyMetadataDataObject
Additional identifier: http://data.europa.eu/dr8/egovera/GoodsTaxonomyMetadataDataObject
eira:eifLayer: Semantic
Description: The BTI application form is used to request an official binding decision from customs authorities regarding the classification of specific goods under the Harmonized System (HS). The form collects information about the applicant, including their details and supporting documentation about the goods, such as their description, technical specifications, and intended use. The applicant suggests an HS code and provides a reason for seeking the binding decision. The completed form is submitted to the customs authority for review, and once a determination is made, the binding tariff information is communicated to the applicant, providing legal certainty for the goods' tariff classification.
Publisher: European Commission
LOST view: SV-Customs Form Structure [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/BTIApplicationFormDataObject
EIRA traceability: eira:FormsStructureDataObject
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2022-01-17
dct:identifier: http://data.europa.eu/dr8/egovera/BTIApplicationFormDataObject
Description: The Unified Code for Units of Measure (UCUM) is a code system intended to include all units of measures being contemporarily used in international science, engineering, and business. The purpose is to facilitate unambiguous electronic communication of quantities together with their units. The focus is on electronic communication, as opposed to communication between humans. A typical application of The Unified Code for Units of Measure are electronic data interchange (EDI) protocols, but there is nothing that prevents it from being used in other types of machine communication.
Publisher: Regenstrief Institute
Source: https://ucum.org/ucum
LOST view: SV-Reference Data [Motivation]
Identifier: http://data.europa.eu/dr8/ReferenceDataObject
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-01-16
dct:identifier: http://data.europa.eu/dr8/egovera/
Description: The Core Assessment Vocabulary represents and defines what an “Assessment” of “assets” is and how to perform the assessment based on “Criteria”. It is a domain-agnostic vocabulary, meaning that it can be used to assess any type of assets.
Publisher: European Commission
Source: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/solution/core-assessment-vocabulary-cav/
LOST view: SV-Agnostic Vocabularies
Identifier: http://data.europa.eu/dr8/egovera/CoreAssessmentVocabularyDataObject
EIRA traceability: eira:ControlledVocabularyDataObject
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-08-20
dct:identifier: http://data.europa.eu/dr8/egovera/CoreAssessmentVocabularyDataObject
Definition: Dataset ABB is a Data Object representing a collection of related data that is organized and presented in a structured format
Source: Inpired in the Open Data and Re-use of public sector inforamtion directive
Source reference: https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=CELEX:32019L1024&from=EN#d1e1012-56-1
Additional information: It is useful to remember that when a common interconnecting infrastructure for base registries is available, legislation is used to force its use. The use of interconnecting infrastructure prevents the proliferation of pointto-point interconnections. Stakeholders should be involved in developing the legislation and be given enough time to prepare for implementation.
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): European Union Data Portal - The European Union Open Data Portal (EU ODP) gives you access to open data published by EU institutions and bodies. All the data you can find via this catalogue are free to use and reuse for commercial or non-commercial purposes. (https://data.europa.eu/euodp/data/dataset)
Interoperability Dimension: Structural IoP
LOST view: Semantic view
Viewpoint: Interoperability Privacy viewpoint
Interoperability Saliency: The Data Set ABB is salient for semantic interoperability because it provides a collection of data to be shared or exchanged between ICT systmes as stated in the EIF recommendation n° 30: "Perceive data and information as a public asset that should be appropriately generated, collected, managed, shared, protected and preserved."
Identifier: http://data.europa.eu/dr8/DatasetDataObject
ABB name: eira:DatasetDataObject
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/DatasetDataObject
Interoperability Layer: Semantic
LOST view: SV-Forms Structure
Identifier: http://data.europa.eu/dr8/egovera/OrderFormDataObject
EIRA traceability: eira:FormsStructureDataObject
ABB name: egovera:OrderFormDataObject
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2022-01-17
Description: The European Single Procurement Document (ESPD) is a standardized form used in public procurement processes within the European Union (EU). As a data object, the ESPD represents a structured document that contains essential information about a supplier or contractor. It includes details such as the company's identification, financial standing, technical and professional abilities, and any legal grounds for exclusion. The ESPD serves as a preliminary self-declaration by suppliers, allowing them to demonstrate their eligibility and suitability to participate in public procurement procedures across EU member states.
Interoperability Dimension: Structural IoP
Publisher: The Publications Office of the European Union
Source: https://docs.ted.europa.eu/ESPD-EDM/latest/index.html
LOST view: SV-Business Agnostic Data Models
Identifier: http://data.europa.eu/dr8/egovera/ESPD-EDMDataObject
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/egovera/ESPD-EDMDataObject
Interoperability Layer: Semantic
Realises: http://data.europa.eu/dr8/DataModelDataObject
Definition: Log Metadata refers to structured information that captures details and contextual information about log events generated by software applications, systems, or devices. It includes attributes such as log entry timestamp, log level, source or origin of the log event, log message, and any additional metadata associated with the log event. Log Metadata helps in understanding and analyzing system behavior, diagnosing issues, and monitoring application or system performance.
Source: W3C Logging Specification
LOST view: SV-Business Agnostic Metadata
Identifier: http://data.europa.eu/dr8/egovera/LogMetadataDataObject
EIRA traceability: eira:DataSetDataObject
ABB name: egovera:LogMetadataDataObject
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2022-01-16
Definition: Data Model ABB is a Data Object aiming to be a collection of entities, their properties and the relationships among them, which focus at formally representing a domain, a concept or a real-world thing.
Source: ISA2 - SEMIC Action
Source reference: https://joinup.ec.europa.eu/sites/default/files/methodology_and_tools_for_metadata_governance_and_management_for_eu_institutions.pdf
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): ESPD - Exchange data model - The ESPD Exchange Data Model was designed to implement the data requirements expressed in the Annex 2 of the COMMISSION IMPLEMENTING REGULATION (EU) 2016/7 of 5 January 2016 (from now on "the Annex to the Regulation 2016/7"), establishing the standard form for the European Single Document. Additionally to these requirements, the model took also into account the Information Requirements Model specified by the CEN/BII-Workshops.[3] (namely Workshop 3), and the latest developments relating to the Virtual Company Dossier (VCD) in e-Sens.[4].
Interoperability Dimension: Structural IoP
LOST view: Semantic view
Interoperability Saliency: The Data Model ABB is salient for semantic interoperability because it ensures compatible interpretations of data exchange as specified in the document "Methodology and tools for metadata governance and management for EU Institutions", developed under the SEMIC action of the ISA Programme: "Whilst technological developments offer various means to automate the exchange of information, technological developments alone cannot guarantee a greater interoperability between information systems. A fundamental aspect is the need for common data standards: primarily data models and reference data [...]".
Identifier: http://data.europa.eu/dr8/DataModelDataObject
ABB name: eira:DataModelDataObject
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/DataModelDataObject
Interoperability Layer: Semantic
LOST view: SV-Forms Structure
Identifier: http://data.europa.eu/dr8/egovera/ContactFormDataObject
EIRA traceability: eira:FormsStructureDataObject
ABB name: egovera:ContactFormDataObject
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2022-01-17
Description: This document describes RML, a generic mapping language, based on and extending [R2RML]. The RDF Mapping language (RML) is a mapping language defined to express customized mapping rules from heterogeneous data structures and serializations to the RDF [RDF-CONCEPTS] data model. RML is defined as a superset of the W3C-standardized mapping language [R2RML], aiming to extend its applicability and broaden its scope, adding support for data in other structured formats. [R2RML] is the W3C standard to express customized mappings from relational databases to RDF. RML follows exactly the same syntax as R2RML; therefore, RML mappings are themselves RDF graphs. The present document describes the RML language and its concepts through definitions and examples.
Interoperability Dimension: Structural IoP
Publisher: IDLab Ghent University
Source: https://rml.io/specs/rml/
LOST view: SV-Data Mapping
Identifier: http://data.europa.eu/dr8/egovera/RDFMappingLanguageDataObject
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/egovera/RDFMappingLanguageDataObject
Interoperability Layer: Semantic
Realises: http://data.europa.eu/dr8/DataMappingDataObject
Definition: "Golden Record" refers to a single, authoritative, and complete version of a data entity or a set of data that serves as the reference source for all other copies or instances of that data
Source: Eurpean Comission Data Management
Source reference: https://ec.europa.eu/research/participants/docs/h2020-funding-guide/cross-cutting-issues/open-access-data-management/open-access_en.htm
Example: The following implementation is an example of how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): EU-ERS: Master Data Register. https://circabc.europa.eu/ui/group/3cc8c417-0f2a-4eb4-8ff7-10d60638446a/information
eira:iopDimension: Structural IoP
LOST view: Semantic view - Motivation
eira:iopSaliency: The Master Data ABB is a key interoperable enabler for semantic interoperability because it is a core element for digital public services enabling the reuse of relevant data such as identifiers for parties, or locations.
Identifier: http://data.europa.eu/dr8/MasterDataObject
ABB name: eira:GoldenRecord
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2022-01-26
dct:identifier: http://data.europa.eu/dr8/MasterDataObject
Description: VIES is a system that enables businesses to verify the validity of VAT (Value Added Tax) numbers of their trading partners within the EU. It assists in the administration and control of intra-community transactions.
Publisher: European Commission
Source: https://europa.eu/youreurope/business/taxation/vat/check-vat-number-vies/index_en.htm#shortcut-0
LOST view: SV-Customs Base Registries [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/VATInformationExchangeSystemDataObject
EIRA traceability: eira:BaseRegistryDataObject
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-08-20
dct:identifier: http://data.europa.eu/dr8/egovera/VATInformationExchangeSystemDataObject
Description: The Registered Exporter system (the REX system) is a system of certification of origin of goods based on a principle of self-certification.The origin of goods is declared by economic operators themselves by means of so-called statements on origin. To be entitled to make out a statement on origin, an economic operator has to be registered in a database by his competent authorities. The economic operator becomes a "registered exporter". The REX system is the term used to designate the system of certification of origin as a whole, and not only the underlying IT system which is used for the registration of exporters.
Additional information: The REX IT system has been developed by the European Commission and is made available to the Member States of the EU, to the GSP beneficiary countries and to the OCTs. It takes the form of a Web application accessed with a username and a password as a website through Internet. The only technical requirement is then to use a device connected to Internet to be able to use the REX system.
Publisher: European Commission
Source: https://taxation-customs.ec.europa.eu/online-services/online-services-and-databases-customs/rex-registered-exporter-system_en
LOST view: SV-Customs Base Registries [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/REX–RegisteredExporterSystemDataObject
EIRA traceability: eira:BaseRegistryDataObject
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-08-20
dct:identifier: http://data.europa.eu/dr8/egovera/REX–RegisteredExporterSystemDataObject
Description: This dataspace comprise INSPIRE themes and River Information Services data.
Publisher: European Comission- Directive 2019/1024
Source: https://eur-lex.europa.eu/legal-content/EN/TXT/PDF/?uri=CELEX:32019L1024
LOST view: SV-Business Agnostic High Value Dataset
Identifier: http://data.europa.eu/dr8/egovera/MobilityHighValueDatasetDataObject
EIRA traceability: eira:DataSetCatalogueDataObject
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-08-20
dct:identifier: http://data.europa.eu/dr8/egovera/MobilityHighValueDatasetDataObject
Definition: Knowledge Triplestore ABB is a Data Object that enables storage, management and retrieval of data in the form of triples, data entities composed of subject-predicate-object.
Source: W3C
Source reference: https://www.w3.org/2001/sw/Europe/events/20031113-storage/positions/rusher.html
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): CELLAR. Cellar metadata is stored in a knowledge graph, and more specifically in a triple store. A SPARQL interface is used to query the metadata. https://op.europa.eu/en/web/cellar/cellar-data/metadata/knowledge-graph
Interoperability Dimension: Structural IoP
LOST view: Technical view - application
Interoperability Saliency: The Knowledge Triplestore Data Object ABB is salient for technical interoperability because it represents the different data objects such as databases storing data, allowing to manage and retrieve of data from different sources and digital public services.
Identifier: http://data.europa.eu/dr8/KnowledgeTriplestoreDataObject
ABB name: eira:KnowledgeTriplestoreDataObject
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/KnowledgeTriplestoreDataObject
Interoperability Layer: TechnicalApplication
Definition: Software Components Catalogue ABB is a Data Object aiming to index information about collaborative spaces that offfers eGoverment solutions and best practices.
Source: Joinup
Source reference: https://joinup.ec.europa.eu/topic/ict/reusable-software-components
Example: The following implementation is an example of how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): Software ReUse Catalogue (Belgium) https://joinup.ec.europa.eu/collection/belgian-interoperability-catalogue/solution/ict-reuse/about
Interoperability Dimension: Structural IoP
LOST view: Semantic view
Interoperability Saliency: The Software Components Catalogue Data Object ABB is salient for semantic interoperability because it can act as a repository with descriptive data about digital solutions and interoperable solutions and best practices. This can contribute to expanding and enabling the reuse of artefacts, solutions, and services to implement new digital public services without starting from scratch. The reuse of such elements can infer knowledge and best practices from the collaboration between parties.
Identifier: http://data.europa.eu/dr8/SoftwareComponentsCatalogueDataObject
ABB name: eira:SoftwareComponentsCatalogueDataObject
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/SoftwareComponentsCatalogueDataObject
Interoperability Layer: Semantic
Definition: Transaction Metadata refers to structured information that captures details and contextual information about a specific transaction. It includes attributes such as transaction ID, date and time, parties involved, transaction type, transaction status, and any additional metadata relevant to the transaction. Transaction Metadata provides a comprehensive view of the transaction, enabling data analysis, auditing, tracking, and reporting.
Source: ISO
LOST view: SV-Business Agnostic Metadata
Identifier: http://data.europa.eu/dr8/egovera/TransactionMetadataDataObject
EIRA traceability: eira:DataSetDataObject
ABB name: egovera:TransactionMetadataDataObject
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2022-01-16
Description: This dataspace comprise observation measurement data (weather stations), climate data, weather warnings, radar data, NWP model data.
Publisher: European Comission- Directive 2019/1024
Source: https://eur-lex.europa.eu/legal-content/EN/TXT/PDF/?uri=CELEX:32019L1024
LOST view: SV-Business Agnostic High Value Dataset
Identifier: http://data.europa.eu/dr8/egovera/MetereologyHighValueDatasetDataObject
EIRA traceability: eira:DataSetCatalogueDataObject
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-08-20
dct:identifier: http://data.europa.eu/dr8/egovera/MetereologyHighValueDatasetDataObject
Definition: Hash Code ABB is a Data Object that enables the implementation of a numeric or alphanumeric string obtained by the application of an algorithm that turns a variable amount of data into a small, fixed-length value
Source: Inspired in CROS
Source reference: https://ec.europa.eu/eurostat/cros/content/data-hashing_en
Example: The following implementation is an example of how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): The hash code is a relevant tool used, for instance, in the personal data pseudonymisation technique. https://edps.europa.eu/sites/edp/files/publication/19-10-30_aepd-edps_paper_hash_final_en.pdf
Interoperability Dimension: Structural IoP
LOST view: Semantic view
Interoperability Saliency: The Hash Code Data Object ABB is salient for semantic interoperability because it supports semantic interoperability by providing alphanumeric strings comprising a variable amount of data. This enables and supports interoperability by reducing data and changing from comprehensible data to anonymised strings.
Identifier: http://data.europa.eu/dr8/HashCodeDataObject
ABB name: eira:HashCodeDataObject
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/HashCodeDataObject
Interoperability Layer: Semantic
Description: An EORI number is mandatory for customs clearance in the customs territory of the European Union. That relates to all types of customs operations such as export, import and transit. EORI uniquely identifies economic operators and other persons. At a certain point in time, a person can be assigned only one valid EORI number. A person must communicate the number to customs authorities in the Member States for customs operations. By having one common type of identification number across the EU both economic operators and customs authorities benefit from more efficiency in customs clearance, statistical and security purposes.
Publisher: European Commission
Source: https://taxation-customs.ec.europa.eu/online-services/online-services-and-databases-customs_en
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/egovera/EORIMetadataDataObject
EIRA traceability: eira:DataSetDataObject
LOST view: SV-Customs Datasets [Motivation]
EIRA concept: eira:SolutionBuildingBlock
Additional identifier: http://data.europa.eu/dr8/egovera/EORIMetadataDataObject
EIF Layer: Semantic
Description: The Shapes Constraint Language (SHACL) is a language and framework for describing and validating the structure and constraints of RDF (Resource Description Framework) graphs. RDF is a standard for representing data in a graph format, widely used in the Semantic Web.
Publisher: W3C
Source: https://www.w3.org/TR/shacl/
LOST view: SV-Agnostic Ontologies
Identifier: http://data.europa.eu/dr8/egovera/W3CShapesConstraintLanguageDataObject
EIRA traceability: eira:Ontology
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-08-20
dct:identifier: http://data.europa.eu/dr8/egovera/W3CShapesConstraintLanguageDataObject
Definition: Master Data ABB is a Data Object that enables the implementation of non-transactional information to play a key role in the core operation of a business in public administrations and re-used for multiple purposes
Source: European Medicines Agency
Source reference: https://www.ema.europa.eu/en/glossary/master-data#:~:text=Master%20data%20Any%20non-transactional%20information%20considered%20to%20play,product%2C%20organisation%20and%20referential%20%28SPOR%29%20master%20data%20%27.
Example: The following implementation is an example of how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): EU-ERS: Master Data Register. https://circabc.europa.eu/ui/group/3cc8c417-0f2a-4eb4-8ff7-10d60638446a/information
Interoperability Dimension: Structural IoP
LOST view: Semantic view
Interoperability Saliency: The Master Data ABB is a key interoperable enabler for semantic interoperability because it is a core element for digital public services enabling the reuse of relevant data such as identifiers for parties, or locations.
Identifier: http://data.europa.eu/dr8/MasterDataDataObject
ABB name: eira:MasterDataDataObject
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/MasterDataDataObject
Interoperability Layer: Semantic
Definition: Metadata ABB is a Data Object providing information about one or more aspects of the data
Source: W3C
Source reference: www.w3.org/Metadata/
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): https://data.europa.eu/en
Interoperability Dimension: Behavioral IoP
LOST view: Semantic view
Viewpoint: Key Interoperability Enablers viewpoint
Interoperability Saliency: The Metadata ABB is a key interoperability enabler (*) for behavioural interoperability by enabling data discoverability and reuse enhancing the delivery and collaboration between digital public services.
Identifier: http://data.europa.eu/dr8/MetadataDataObject
ABB name: eira:MetadataDataObject
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/MetadataDataObject
Interoperability Layer: Semantic
Definition: Distributed Ledger ABB is a Data Object that enables the sharing and recording of encrypted data across multiple sites, countries, or institutions.
Source: Regulation of a pilot regime for market infrastructures based on distributed ledger technology
Source reference: https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=CELEX:52020PC0594&from=EN
Example: The following implementation is an example of how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): TOLAR (https://tolar.io/)is a tool implemented as the outcome of the Seduproject, Hashnet is in the process of evaluation by the European Blockchain Partnership to become one of the pilot protocols for European Blockchain Service Infrastructure. https://www.seedeuproject.eu/partners/hashnet/
Interoperability Dimension: Structural IoP
LOST view: Semantic view
Interoperability Saliency: The Distributed Ledger ABB is salient for semantic interoperability due to its capacity to exchange encrypted data amongst digital public services. It is also salient because it can be used across borders to ensure secure and trustworthy data exchange. Additionally, it is also relevant for new technologies incorporating blockchain technology.
Identifier: http://data.europa.eu/dr8/DistributedLedgerDataObject
ABB name: eira:DistributedLedgerDataObject
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/DistributedLedgerDataObject
Interoperability Layer: Semantic
Description: The PROV Ontology (PROV-O) expresses the PROV Data Model [PROV-DM] using the OWL2 Web Ontology Language (OWL2) [OWL2-OVERVIEW]. It provides a set of classes, properties, and restrictions that can be used to represent and interchange provenance information generated in different systems and under different contexts. It can also be specialized to create new classes and properties to model provenance information for different applications and domains. The PROV Document Overview describes the overall state of PROV, and should be read before other PROV documents.
Publisher: W3C
Source: https://www.w3.org/TR/prov-o/
LOST view: SV-Agnostic Ontologies
Identifier: http://data.europa.eu/dr8/egovera/PROV-ODataObject
EIRA traceability: eira:Ontology
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-08-20
dct:identifier: http://data.europa.eu/dr8/egovera/PROV-ODataObject
Description: The ‘Reference Data & Customs Office List’ pages provide information on the Reference Data (RD) and the Customs Office List (COL) used by the national customs applications. The Reference Data part is maintained by the Commission. The Customs Office List published on this site is based on the data provided and maintained by the national customs administrations. Those data are provided for information only and is binding neither for the Commission nor for the National Administrations concerned. For specific enquiries and information regarding the customs offices, please contact the Customs Administration of the appropriate country
Publisher: European Commission
Source: https://ec.europa.eu/taxation_customs/dds2/rd/rd_home.jsp?Lang=en
LOST view: SV-Reference Data [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/ReferenceDataCustomsOfficesListDataObject
EIRA traceability: eira:ReferenceData
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-08-20
dct:identifier: http://data.europa.eu/dr8/egovera/ReferenceDataCustomsOfficesListDataObject
Definition: Procedures Metadata ABB is a DataSet Data Object that refers to structured information that outlines various standard operating procedures, workflows, or protocols within an organization. This includes step-by-step process descriptions, involved roles and responsibilities, required resources, timeframes, and compliance requirements. This data object is essential for ensuring operational consistency, efficiency, and adherence to regulatory and quality standards across the organization.
Source: European Commission
Source reference: https://taxation-customs.ec.europa.eu/customs-4/customs-procedures-import-and-export-0_en
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/egovera/ProceduresMetadataDataObject
EIRA traceability: eira:DataSetDataObject
LOST view: SV-Customs Datasets [Motivation]
EIRA concept: eira:ArchitectureBuildingBlock
ABB name: egovera:ProceduresMetadataDataObject
Additional identifier: http://data.europa.eu/dr8/egovera/ProceduresMetadataDataObject
eira:eifLayer: Semantic
Description: The portal is a central point of access to European open data from international, European Union, national, regional, local and geodata portals.
Publisher: The Publications Office of the European Union
Source: https://data.europa.eu/en
LOST view: SV-Metadata Catalogue
Identifier: http://data.europa.eu/dr8/egovera/OfficialPortalForEuropeanDataDataObject
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/egovera/OfficialPortalForEuropeanDataDataObject
Interoperability Layer: Semantic
Realises: http://data.europa.eu/dr8/DataSetCatalogueDataObject
Description: The Profiles Vocabulary is an RDF vocabulary created to allow the machine-readable description of profiles of specifications for information resources. It can be used to describe profile hierarchies wherein profiles of specifications may themselves have profiles indicated. It can also link multiple profile resources that make up a profile - guidelines, validation tools, schemas, term lists and so on - to it and allows for those profile resources to be described with formats, roles, and digital artifacts.
Publisher: W3C
Source: https://www.w3.org/TR/dx-prof/
LOST view: SV-Agnostic Vocabularies
Identifier: http://data.europa.eu/dr8/egovera/W3CProfilesVocabularyDataObject
EIRA traceability: eira:ControlledVocabularyDataObject
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-08-20
dct:identifier: http://data.europa.eu/dr8/egovera/W3CProfilesVocabularyDataObject
Description: The FOAF project is based around the use of machine readable Web homepages for people, groups, companies and other kinds of thing. To achieve this we use the "FOAF vocabulary" to provide a collection of basic terms that can be used in these Web pages. At the heart of the FOAF project is a set of definitions designed to serve as a dictionary of terms that can be used to express claims about the world. The initial focus of FOAF has been on the description of people, since people are the things that link together most of the other kinds of things we describe in the Web: they make documents, attend meetings, are depicted in photos, and so on.
Publisher: Dan Brickley
Source: http://xmlns.com/foaf/0.1/
LOST view: SV-Agnostic Ontologies
Identifier: http://data.europa.eu/dr8/egovera/FOAFDataObject
EIRA traceability: eira:ControlledVocabularyDataObject
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-08-20
dct:identifier: http://data.europa.eu/dr8/egovera/FOAFDataObject
Description: The ESCO classification identifies and categorises skills, competences, and occupations relevant for the EU labour market and education and training. It systematically shows the relationships between the different concepts.
Interoperability Dimension: Structural IoP
Publisher: European Commission
Source: https://esco.ec.europa.eu/en
LOST view: SV-Agnostic Reference Data
Identifier: http://data.europa.eu/dr8/egovera/ESCODataObject
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/egovera/ESCODataObject
Interoperability Layer: Semantic
Realises: http://data.europa.eu/dr8/ReferenceData
Description: The HS codes are an internationally standardized system for classifying products and goods. These codes determine the customs duties, taxes, and regulations applicable to specific products during import or export.
Publisher: World Customs Organization
Source: https://www.wcoomd.org/en/topics/nomenclature/instrument-and-tools/hs-nomenclature-2022-edition/hs-nomenclature-2022-edition.aspx
LOST view: SV-Reference Data [Motivation]
Identifier: http://data.europa.eu/dr8/ReferenceDataObject
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-01-16
dct:identifier: http://data.europa.eu/dr8/egovera/
Definition: Exchange Item Metadata refers to the structured information that provides descriptive and contextual details about an exchange item in a data exchange or integration process. It includes attributes such as the item's name, description, format, source, destination, and any additional metadata that helps define its characteristics and usage. Exchange Item Metadata serves as a standardized representation of the item's properties, enabling effective data integration, interoperability, and understanding across different systems and applications.
Source: W3C
Source reference: https://www.w3.org/standards/
LOST view: SV-Business Agnostic Metadata
Identifier: http://data.europa.eu/dr8/egovera/ExchangeItemMetadataDataObject
EIRA traceability: eira:DataSetDataObject
ABB name: egovera:ExchangeItemMetadataDataObject
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2022-01-16
Description: The DCAT Application Profile for data portals in Europe (DCAT-AP) is a specification based on the Data Catalogue Vocabulary (DCAT) developed by W3C. This application profile is a specification for metadata records to meet the specific application needs of data portals in Europe while providing semantic interoperability with other applications on the basis of reuse of established controlled vocabularies (e.g. EuroVoc) and mappings to existing metadata vocabularies (e.g. Dublin Core, SDMX, INSPIRE metadata, etc.).
Publisher: European Commission
Source: https://joinup.ec.europa.eu/collection/semantic-interoperability-community-semic/solution/dcat-application-profile-data-portals-europe/about
LOST view: SV-Agnostic Ontologies
Identifier: http://data.europa.eu/dr8/egovera/DCAT-APDataObject
EIRA traceability: eira:ControlledVocabularyDataObject
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-08-20
dct:identifier: http://data.europa.eu/dr8/egovera/DCAT-APDataObject
Description: This resource is a distinct reference data asset (like authority table, taxonomy, thesaurus, ontology, …) maintained by an organisation like the EU vocabularies. The nature of the asset can be described by concepts from the AT dataset type.
Interoperability Dimension: Structural IoP
Publisher: Publications Office of the European Union
LOST view: SV-Agnostic Reference Data
Identifier: http://data.europa.eu/dr8/egovera/ReferenceDataAssetDataObject
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/egovera/ReferenceDataAssetDataObject
Interoperability Layer: Semantic
Realises: http://data.europa.eu/dr8/ReferenceData
Description: The CSSV is the vocabulary used for the information exchange related to standards and specifications amongst software solutions, and also for the description of themselves like EIRA, CPSV, IMAPS, amongst other specifications. The CSSV is the key element for the development of the EIRA Library of Interoperability Specifications (ELIS).
Publisher: European Commission
Source: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/solution/core-standards-and-specifications-vocabulary-cssv/about
LOST view: SV-Agnostic Vocabularies
Identifier: http://data.europa.eu/dr8/egovera/CoreStandardsAndSpecificationsVocabularyDataObject
EIRA traceability: eira:ControlledVocabularyDataObject
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-08-20
dct:identifier: http://data.europa.eu/dr8/egovera/CoreStandardsAndSpecificationsVocabularyDataObject
Definition: Notifications Metadata ABB is a data object that refers to structured data regarding various types of notifications generated within an enterprise system. This includes notification types (e.g., system alerts, transaction confirmations, regulatory notices), recipients, timing, delivery methods, and response requirements or actions taken. It plays a vital role in ensuring effective communication, operational efficiency, and compliance with procedural or regulatory requirements within an organization.
Source: European Commission
Source reference: https://taxation-customs.ec.europa.eu/customs-4/union-customs-code/eu-customs-data-model-eucdm_en
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/egovera/NotificationsMetadataDataObject
EIRA traceability: eira:DataSetDataObject
LOST view: SV-Customs Datasets [Motivation]
EIRA concept: eira:ArchitectureBuildingBlock
ABB name: egovera:NotificationsMetadataDataObject
Additional identifier: http://data.europa.eu/dr8/egovera/NotificationsMetadataDataObject
eira:eifLayer: Semantic
Description: The Organization Ontology is a standardized representation of organizational structures, roles, and relationships within the field of Linked Data and the Semantic Web. It provides a framework for describing and modeling various aspects of organizations, such as their hierarchy, departments, employees, and roles.
Publisher: W3C
Source: https://www.w3.org/TR/vocab-org/
LOST view: Semantic view
Identifier: http://data.europa.eu/dr8/egovera/ODRLDataObject
EIRA traceability: eira:Ontology
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-08-20
dct:identifier: http://data.europa.eu/dr8/egovera/ODRLDataObject
Description: Authority tables (also known as Named Authority Lists or NALs are used to harmonise and standardise the codes and associated labels used in various environments (web platforms, systems and applications) and in facilitating data exchanges between the institutions involved in decision-making process and not only.
Interoperability Dimension: Structural IoP
Publisher: Publications Office of the European Union
Source: https://op.europa.eu/en/web/eu-vocabularies/authority-tables
LOST view: SV-Agnostic Reference Data
Identifier: http://data.europa.eu/dr8/egovera/AuthorityTablesDataObject
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/egovera/AuthorityTablesDataObject
Interoperability Layer: Semantic
Realises: http://data.europa.eu/dr8/ReferenceData
Definition: Data mapping ABB is a Data Object aiming to bring equivalence in a relationship between two data items with ontological value.
Source: Inspired in "Data Mapping for Data Warehouse Design" book
Source reference: https://www.sciencedirect.com/book/9780128051856/data-mapping-for-data-warehouse-design
Additional information: Data mapping is used for a wide variety of tasks, including: - Data mediation between a data source and a destination; - Data transformation; - Identification of data relationships as part of data lineage analysis; - Discovery of hidden sensitive data such as the last four digits of a social security number hidden in another user id as part of a data masking or de-identification project; - Consolidation of multiple databases into a single database and identifying redundant columns of data for consolidation or elimination.
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): Microsoft Dynamics CRM Mapping Schema - Microsoft Dynamics CRM contains several data sets which comprise of different objects, such as Leads, Opportunities, and Competitors. Each of these data sets has several fields like Name, Account Owner, City, Country, Job Title, and more. The application has a defined schema along with attributes, enumerations, and mapping rules. Therefore, if a new record is to be added to the schema of a data object, a data map needs to be created from the data source to the Microsoft Dynamics CRM account.
Interoperability Dimension: Structural IoP
LOST view: Semantic view
Viewpoint: Interoperability Privacy viewpoint
Interoperability Saliency: The Data Mapping ABB is a key interoperability enabler because it supports to achieve legal behavioral interoperability by enabling the exchange of data, information, and knowledge between digital public services.
Identifier: http://data.europa.eu/dr8/DataMappingDataObject
ABB name: eira:DataMappingDataObject
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/DataMappingDataObject
Interoperability Layer: Semantic
Definition: Laboratory Reports Index ABB is a data object that acts as a centralized and organized repository for all laboratory reports within an organization. It includes essential metadata such as report identification, date, type of analysis, subject details, and key findings. This index is integral for efficient data management, ensuring seamless integration with other enterprise systems, maintaining regulatory compliance and traceability, and supporting analytical and decision-making processes by providing structured access to comprehensive laboratory data.
Source: European Commission
Source reference: https://taxation-customs.ec.europa.eu/customs-4/customs-laboratories_en
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/egovera/LaboratoryReportsIndexDataObject
EIRA traceability: eira:DataSetDataObject
LOST view: SV-Customs Datasets [Motivation]
EIRA concept: eira:ArchitectureBuildingBlock
ABB name: egovera:LaboratoryReportsIndexDataObject
Additional identifier: http://data.europa.eu/dr8/egovera/LaboratoryReportsIndexDataObject
eira:eifLayer: Semantic
Description: The Organization Ontology is a standardized representation of organizational structures, roles, and relationships within the field of Linked Data and the Semantic Web. It provides a framework for describing and modeling various aspects of organizations, such as their hierarchy, departments, employees, and roles.
Publisher: W3C
Source: https://www.w3.org/TR/vocab-org/
LOST view: SV-Agnostic Ontologies
Identifier: http://data.europa.eu/dr8/egovera/W3COrganizationDataObject
EIRA traceability: eira:Ontology
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-08-20
dct:identifier: http://data.europa.eu/dr8/egovera/W3COrganizationDataObject
Definition: Metadata Catalogue ABB is a Data Object that represents the collection of of descriptive information about data, resources or information objects related to public services.
Source: INSPIRE
Source reference: https://inspire.ec.europa.eu/training/metadata-and-catalogue-services
Example: The following implementation is an example of how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): CESSDA Data Catalogue https://www.cessda.eu/Tools/Data-Catalogue
Interoperability Dimension: Structural IoP
LOST view: Semantic view
Interoperability Saliency: The Metadata Catalogue ABB is a key interoperability enabler supporting semantic interoperability because metadata catalogue is a collection of descriptive information about data and information related to digital public services. The usage of standardised methods can enable successful data discoverability and reuse supporting the implementation of digital public services across borders.
Identifier: http://data.europa.eu/dr8/MetadataCatalogueDataObject
ABB name: eira:MetadataCatalogueDataObject
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/MetadataCatalogueDataObject
Interoperability Layer: Semantic
LOST view: SV-Forms Structure
Identifier: http://data.europa.eu/dr8/egovera/SurveyFormDataObject
EIRA traceability: eira:FormsStructureDataObject
ABB name: egovera:SurveyFormDataObject
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2022-01-17
Description: This dataspace comprise basic company information, records, and financial statements.
Publisher: European Comission- Directive 2019/1024
Source: https://eur-lex.europa.eu/legal-content/EN/TXT/PDF/?uri=CELEX:32019L1024
LOST view: SV-Business Agnostic High Value Dataset
Identifier: http://data.europa.eu/dr8/egovera/Business-relatedDataHighValueDatasetDataObject
EIRA traceability: eira:DataSetCatalogueDataObject
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-08-20
dct:identifier: http://data.europa.eu/dr8/egovera/Business-relatedDataHighValueDatasetDataObject
Description: DCAT enables a publisher to describe datasets and data services in a catalog using a standard model and vocabulary that facilitates the consumption and aggregation of metadata from multiple catalogs. This can increase the discoverability of datasets and data services.
Publisher: W3C
Source: https://www.w3.org/TR/vocab-dcat-2/
LOST view: SV-Agnostic Ontologies
Identifier: http://data.europa.eu/dr8/egovera/DCATDataObject
EIRA traceability: eira:ControlledVocabularyDataObject
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-08-20
dct:identifier: http://data.europa.eu/dr8/egovera/DCATDataObject
Definition: Cargo Metadata ABB is DataSet Data Object that encapsulates all essential details and attributes related to cargo or freight managed by an organization. This metadata includes information such as cargo type, size, weight, packaging details, origin, destination, transportation mode, shipment dates, consignor and consignee information, customs declarations, and any applicable handling instructions or safety requirements. In the realm of Enterprise Architecture, Cargo Metadata plays a crucial role in optimizing logistics and supply chain management, ensuring compliance with transportation and customs regulations, facilitating efficient cargo tracking and monitoring, and enhancing overall operational effectiveness in cargo handling and distribution processes.
Source: European Commission
Source reference: https://taxation-customs.ec.europa.eu/online-services/online-services-and-databases-customs_en
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/egovera/CargoMetadataDataObject
EIRA traceability: eira:DataSetDataObject
LOST view: SV-Customs Datasets [Motivation]
EIRA concept: eira:ArchitectureBuildingBlock
ABB name: egovera:CargoMetadataDataObject
Additional identifier: http://data.europa.eu/dr8/egovera/CargoMetadataDataObject
eira:eifLayer: Semantic
Definition: Origins Metadata ABB is a data object that encapsulates comprehensive details about the origin and initial context of various entities, items, or data within an organization. This metadata includes information on geographical origin, source system, creation date, original creator, and initial conditions of creation. It plays a critical role in ensuring traceability and provenance, assessing data quality, complying with regulatory requirements, facilitating effective data integration and management, and enhancing decision-making processes by providing essential context about the sources and history of organizational data.
Source: European Commission
Source reference: https://taxation-customs.ec.europa.eu/customs-4/international-affairs/origin-goods_en
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/egovera/OriginsMetadataDataObject
EIRA traceability: eira:DataSetDataObject
LOST view: SV-Customs Datasets [Motivation]
EIRA concept: eira:ArchitectureBuildingBlock
ABB name: egovera:OriginsMetadataDataObject
Additional identifier: http://data.europa.eu/dr8/egovera/OriginsMetadataDataObject
eira:eifLayer: Semantic
Description: The e-Government Core Vocabularies are simplified, re-usable and extensible data models that capture the fundamental characteristics of a data entity in a context-neutral fashion.
Publisher: SEMIC
Source: https://joinup.ec.europa.eu/collection/semantic-interoperability-community-semic/solution/e-government-core-vocabularies/about
LOST view: SV-Agnostic Vocabularies
Identifier: http://data.europa.eu/dr8/egovera/EGovernmentCoreVocabulariesDataObject
EIRA traceability: eira:ControlledVocabularyDataObject
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-08-20
dct:identifier: http://data.europa.eu/dr8/egovera/EGovernmentCoreVocabulariesDataObject
Description: Cellar is the common data repository of the Publications Office of the European Union. Digital publications and metadata are stored in and disseminated via Cellar, in order to be used by humans and machines. Aiming to transparently serve users, Cellar stores multilingual publications and metadata, it is open to all EU citizens and provides machine-readable data.
Publisher: The Publications Office of the European Union
Source: https://op.europa.eu/en/web/cellar/cellar-data/metadata/knowledge-graph
LOST view: SV-Datasets Catalogue Solutions
Identifier: http://data.europa.eu/dr8/egovera/CELLARDataObject
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/egovera/CELLARDataObject
Interoperability Layer: Semantic
Realises: http://data.europa.eu/dr8/DataSetCatalogueDataObject
Definition: Data Syntax ABB is a Data Object defining the way in which data is put together with appropriate identifiers, delimiters, separator character(s), and other non-data characters to form messages.
Source: ISO
Source reference: https://www.iso.org/obp/ui/#iso:std:iso:14817:-1:ed-1:v1:en:term:4.59
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): XML syntax - XML syntax refers to the rules that determine how an XML application can be written. The XML syntax is very straight forward, and this makes XML very easy to learn. Below are the main points to remember when creating XML documents.(https://www.quackit.com/xml/tutorial/xml_syntax.cfm)
Interoperability Dimension: Structural IoP
LOST view: Semantic view
Interoperability Saliency: The Data Syntax ABB is salient for semantic interoperability because it provides the rules establishing how data have to to be written.
Identifier: http://data.europa.eu/dr8/DataSyntaxDataObject
ABB name: eira:DataSyntaxDataObject
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/DataSyntaxDataObject
Interoperability Layer: Semantic
Definition: Data Syntax Mapping Catalogue ABB is an Data Object bridging the differences between two systems, or data models, so that when data is moved from a source, it is accurate and usable at the destination.
Source: Inspired in Digital Strategy Europe
Source reference: https://digital-strategy.ec.europa.eu/en/library/study-mapping-data-flows
LOST view: Semantic view
Identifier: http://data.europa.eu/dr8/DataSyntaxMappingCatalogueDataObject
eira:ID: ABB445
ABB name: eira:DataSyntaxMappingCatalogueDataObject
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2022-20-01
Definition: Reference data ABB is a Data Object that enables the definition of a set of values or codes that are used to categorize, classify, or describe data elements in a consistent and standardized way
Source: Inspired in the book "Managing Reference Data in Enterprise Datavases"
Source reference: ISBN1558606971
Example: The following implementation is an example of how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): GISCO - the Geographic Information System of the COmmission reference data https://ec.europa.eu/eurostat/web/gisco/geodata/reference-data
Interoperability Dimension: Structural IoP
LOST view: Semantic view
Interoperability Saliency: The Reference Data ABB is a key interoperability enabler because it contributes to data standardisation and provides values and mechanisms to ensure and enable the proper, agreed and successful data exchange between parties and digital public services. Reference Data is a key element for reaching and maintaining data quality.
Identifier: http://data.europa.eu/dr8/ReferenceDataDataObject
ABB name: eira:ReferenceDataDataObject
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/ReferenceDataDataObject
Interoperability Layer: Semantic
Definition: Intra-EU Purchases and Sales Metadata is a Data Object that refers to the collection and organization of detailed information pertaining to the buying and selling of goods and services within the European Union. It includes transaction details such as the nature of the goods or services, transaction values, dates, involved parties (buyer and seller details), VAT (Value Added Tax) information, and any relevant trade or regulatory compliance data. This metadata is key for ensuring compliance with EU trade regulations, facilitating accurate financial reporting, and enabling efficient cross-border transaction management.
Source: European Commission
Source reference: https://taxation-customs.ec.europa.eu/online-services/online-services-and-databases-customs_en
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/egovera/Intra-EUPurchasesAndSalesMetadataDataObject
EIRA traceability: eira:DataSetDataObject
LOST view: SV-Customs Datasets [Motivation]
EIRA concept: eira:ArchitectureBuildingBlock
ABB name: egovera:Intra-EUPurchasesAndSalesMetadataDataObject
Additional identifier: http://data.europa.eu/dr8/egovera/Intra-EUPurchasesAndSalesMetadataDataObject
eira:eifLayer: Semantic
Description: Economic Operators Information refers to the metadata related to businesses or individuals who are involved in the supply chain of goods and services. This information can include details about their legal status, financial capacity, abilities, qualifications, and reliability. It is often used in procurement processes to assess the suitability of potential suppliers, contractors, or service providers. In the context of information systems, it can be a critical component for decision-making, risk assessment, and compliance checks.
Publisher: Based on Publications Office Datasets definitions
Last modification: 2024-01-10
Identifier: http://data.europa.eu/dr8/egovera/EconomicOperatorsMetadataDataObject
EIRA traceability: eira:DataSetDataObject
LOST view: SV-Customs Datasets [Motivation]
EIRA concept: eira:SolutionBuildingBlock
Additional identifier: http://data.europa.eu/dr8/egovera/EconomicOperatorsMetadataDataObject
EIF Layer: Semantic
Description: The Currency authority table is a controlled vocabulary that lists concepts associated with currencies and currency subunits. The concepts included are correlated with the ISO 4217 international standard. The Currency authority table is updated based on the stakeholders’ needs. Contributions to it are accepted following a review made by EU Vocabularies team of the Publications Office of the EU. The Currency authority table is maintained by the Publications Office of the European Union on the EU Vocabularies website.
Publisher: Publications Office of the European Union
Source: https://op.europa.eu/en/web/eu-vocabularies/dataset/-/resource?uri=http://publications.europa.eu/resource/dataset/currency
LOST view: SV-Reference Data [Motivation]
Identifier: http://data.europa.eu/dr8/ReferenceDataObject
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-01-16
dct:identifier: http://data.europa.eu/dr8/egovera/
Definition: Base Registry ABB is a Data Object that refers to reliable sources of basic information that permits an efficient, secure, and transarent exchange of the data.
Source: EIF
Source reference: https://eur-lex.europa.eu/resource.html?uri=cellar:2c2f2554-0faf-11e7-8a35-01aa75ed71a1.0017.02/DOC_3&format=PDF
Example: The following implementation is an example of how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): Business Registry - Registradores de España https://sede.registradores.org/site/mercantil?lang=en_EN
Interoperability Dimension: Structural IoP
LOST view: Semantic view
Interoperability Saliency: The Base Registry Data Object ABB is salient for semantic interoperability because it provides a mechanism or method to ensure reliability of data, fostering secure data exchanges between public administrations and digital public services delivery.
Identifier: http://data.europa.eu/dr8/BaseRegistryDataObject
ABB name: eira:BaseRegistryDataObject
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/BaseRegistryDataObject
Interoperability Layer: Semantic
Description: The Registered Organization Vocabularies, as outlined in the W3C specification, provide a standardized set of terms and concepts for representing and describing registered organizations. It includes elements such as organization identifiers, names, types, statuses, addresses, contacts, and affiliations. By utilizing these standardized vocabularies, developers and data publishers can achieve a consistent and interoperable representation of registered organizations, enabling seamless integration, exchange, and discovery of organization-related data across diverse applications and systems.
Publisher: European Commission
Source: https://www.w3.org/TR/vocab-regorg/
LOST view: SV-Customs Controlled Vocabularies [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/RegisteredOrganisationVocabularyDataObject
EIRA traceability: eira:ControlledVocabularyDataObject
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-08-20
dct:identifier: http://data.europa.eu/dr8/egovera/RegisteredOrganisationVocabularyDataObject
LOST view: SV-Forms Structure
Identifier: http://data.europa.eu/dr8/egovera/RegistrationFormDataObject
EIRA traceability: eira:FormsStructureDataObject
ABB name: egovera:RegistrationFormDataObject
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2022-01-17
Description: This dataspace comprise statistical data on select legal acts.
Publisher: European Comission- Directive 2019/1024
Source: https://eur-lex.europa.eu/legal-content/EN/TXT/PDF/?uri=CELEX:32019L1024
LOST view: SV-Business Agnostic High Value Dataset
Identifier: http://data.europa.eu/dr8/egovera/StatisticsHighValueDatasetDataObject
EIRA traceability: eira:DataSetCatalogueDataObject
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-08-20
dct:identifier: http://data.europa.eu/dr8/egovera/StatisticsHighValueDatasetDataObject
Description: The EUR.1 Movement Certificate is a specific form that needs to be completed to certify the origin of goods and claim preferential treatment in international trade.
Publisher: European Commission
LOST view: SV-Customs Form Structure [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/EUR1MovementCertificateDataObject
EIRA traceability: eira:FormsStructureDataObject
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2022-01-17
dct:identifier: http://data.europa.eu/dr8/egovera/EUR1MovementCertificateDataObject
Description: The EORI system is used to assign a unique identification number to economic operators involved in customs activities within the EU. It enables customs authorities to track and monitor traders engaged in import/export operations and simplifies customs procedures.
Publisher: European Commission
Source: https://ec.europa.eu/taxation_customs/dds2/eos/eori_home.jsp?Lang=en
LOST view: SV-Customs Base Registries [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/EORI-EconomicOperatorsRegistrationAndIdentificationNumberDataObject
EIRA traceability: eira:BaseRegistryDataObject
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-08-20
dct:identifier: http://data.europa.eu/dr8/egovera/EORI-EconomicOperatorsRegistrationAndIdentificationNumberDataObject
Definition: References to relevant customs laws, regulations, and guidelines are essential for ensuring compliance with customs requirements and procedures.
Source: Inspired on EUR-Lex references
LOST view: SV-Reference Data [Motivation]
Identifier: http://data.europa.eu/dr8/ReferenceDataObject
ABB name: eira:ReferenceDataObject
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-01-16
dct:identifier: http://data.europa.eu/dr8/egovera/
Description: Customs valuation is a customs procedure applied to determine the customs value of imported goods. If the rate of duty is ad valorem, the customs value is essential to determine the duty to be paid on an imported good.
Publisher: World Trade Organisation
Source: https://www.wto.org/english/tratop_e/cusval_e/cusval_info_e.htm
LOST view: SV-Reference Data [Motivation]
Identifier: http://data.europa.eu/dr8/ReferenceDataObject
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-01-16
dct:identifier: http://data.europa.eu/dr8/egovera/
Definition: Declarations Metadata ABB is a DataSet Data Object that refers to the detailed information encompassed in various formal statements or disclosures required by regulatory, legal, or administrative processes. This can include data from customs declarations, financial disclosures, regulatory compliance statements, and other official declarations. It contains elements like declaration types, dates, entities involved, items or matters declared, and compliance or verification status. This metadata is crucial for maintaining transparency, ensuring compliance with legal and regulatory requirements, and supporting effective record-keeping and reporting practices.
Source: European Commission
Source reference: https://taxation-customs.ec.europa.eu/customs-4/customs-procedures-import-and-export-0/customs-procedures/customs-declaration_en
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/egovera/DeclarationsMetadataDataObject
EIRA traceability: eira:DataSetDataObject
LOST view: SV-Customs Datasets [Motivation]
EIRA concept: eira:ArchitectureBuildingBlock
ABB name: egovera:DeclarationsMetadataDataObject
Additional identifier: http://data.europa.eu/dr8/egovera/DeclarationsMetadataDataObject
eira:eifLayer: Semantic
Description: OntologyDesignPatterns.org is a Semantic Web portal dedicated to ontology design patterns (ODPs)
Interoperability Dimension: Structural IoP
Publisher: Association for Ontology Design & Patterns (ODPA)
Source: http://ontologydesignpatterns.org/wiki/Main_Page
LOST view: SV-Agnostic Ontology Catalogue
Identifier: http://data.europa.eu/dr8/egovera/ODPDataObject
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/egovera/ODPDataObject
Interoperability Layer: Semantic
Realises: http://data.europa.eu/dr8/OntologiesCatalogueDataObject
Definition: Customs Statistical Metadata on Goods Imported ABB is a data object encompassing comprehensive descriptors and classifications of imported goods for customs purposes. This metadata includes detailed information such as the type, quantity, valuation, origin, and destination of goods, which is essential for ensuring legal compliance, facilitating trade policy analysis, and optimizing operational processes in customs management. It is a critical component for data-driven decision-making, enabling efficient customs operations and effective integration with other enterprise systems related to import activities.
Source: World Customs Organisation
Source reference: https://www.wcoomd.org/
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/egovera/CustomsStatisticalMetadataOnGoodsImportedDataObject
EIRA traceability: eira:DataSetDataObject
LOST view: SV-Customs Datasets [Motivation]
EIRA concept: eira:ArchitectureBuildingBlock
ABB name: egovera:CustomsStatisticalMetadataOnGoodsImportedDataObject
Additional identifier: http://data.europa.eu/dr8/egovera/CustomsStatisticalMetadataOnGoodsImportedDataObject
eira:eifLayer: Semantic
Description: The Joint Research Center (JRC) Data Catalogue is a collection of metadata records that provides information about datasets produced by the Joint Research Centre (JRC) in accordance with its Data Policy. The JRC, as the European Commission's in-house science service, conducts research to provide independent scientific advice and support to the policies of the European Union.
Publisher: Joint Research Center (JRC)
Source: https://data.jrc.ec.europa.eu/
LOST view: SV-Metadata Catalogue
Identifier: http://data.europa.eu/dr8/egovera/JRCDataCatalogueDataObject
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/egovera/JRCDataCatalogueDataObject
Interoperability Layer: Semantic
Realises: http://data.europa.eu/dr8/MetadataCatalogueDataObject
Definition: Customs Statistical Metadata on Goods exported ABB is a data object that details and categorizes all aspects of goods being exported from a country. This metadata encompasses critical information such as the types, quantities, values, destinations, and origins of exported goods. Essential for adhering to export regulations and guidelines, it aids in trade policy analysis and streamlines export-related processes in customs management. This data object is instrumental in facilitating informed decision-making, ensuring efficient customs operations, and integrating effectively with wider business systems associated with export activities.
Source: World Customs Organisation
Source reference: https://www.wcoomd.org/
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/egovera/CustomsStatisticalMetadataOnGoodsExportedDataObject
EIRA traceability: eira:DataSetDataObject
LOST view: SV-Customs Datasets [Motivation]
EIRA concept: eira:ArchitectureBuildingBlock
ABB name: egovera:CustomsStatisticalMetadataOnGoodsExportedDataObject
Additional identifier: http://data.europa.eu/dr8/egovera/CustomsStatisticalMetadataOnGoodsExportedDataObject
eira:eifLayer: Semantic
Description: TARIC is an integrated tariff database that contains information on customs tariffs, import and export formalities, and applicable measures such as quotas, duties, and restrictions. It provides details on the classification of goods and determines the customs duties and trade policies associated with specific products.
Publisher: European Commission
Source: https://ec.europa.eu/taxation_customs/dds2/taric/taric_consultation.jsp?Lang=en
LOST view: SV-Customs Base Registries [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/TARICDataObject
EIRA traceability: eira:BaseRegistryDataObject
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-16-01
Definition: Tariffs Metadata ABB is a DataSet Data Object that contains information about the tariffs applied to goods and services. It includes tariff rates, descriptions of goods or services to which they apply, relevant tariff classification codes, and any associated regulations or trade agreements. This metadata is key for managing international trade operations, ensuring compliance with customs regulations, and facilitating accurate and efficient tariff application and trade reporting.
Source: European Commission
Source reference: https://taxation-customs.ec.europa.eu/customs-4/calculation-customs-duties/customs-tariff/eu-customs-tariff-taric_en
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/egovera/TariffsMetadataDataObject
EIRA traceability: eira:DataSetDataObject
LOST view: SV-Customs Datasets [Motivation]
EIRA concept: eira:ArchitectureBuildingBlock
ABB name: egovera:TariffsMetadataDataObject
Additional identifier: http://data.europa.eu/dr8/egovera/TariffsMetadataDataObject
eira:eifLayer: Semantic
Description: A smart data model includes three elements: The schema, or technical representation of the model defining the technical data types and structure, the specification of a written document for human readers, and the examples of the payloads for NGSIv2 and NGSI-LD versions.
Publisher: Fiware Foundation
Source: https://www.fiware.org/smart-data-models/
LOST view: Semantic view
Identifier: http://data.europa.eu/dr8/egovera/SmartDataModelsDataObject
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/egovera/SmartDataModelsDataObject
Interoperability Layer: Semantic
Realises: http://data.europa.eu/dr8/MetadataCatalogueDataObject
Definition: A Data Contract, within the realm of European tax regulations, refers to a formal agreement that stipulates the terms and conditions under which personal and financial data is collected, processed, shared, and stored by entities such as businesses, tax authorities, and financial institutions. This contract ensures compliance with data protection laws, such as the General Data Protection Regulation (GDPR), by establishing clear guidelines on data handling practices, the rights of individuals whose data is being processed, and the obligations of the data processors and controllers. The aim is to safeguard taxpayer information, maintain privacy, and ensure the integrity and security of data exchanges, particularly in cross-border transactions where multiple jurisdictions are involved.
Source: EIRA team
Identifier: http://data.europa.eu/dr8/egovera/DataContractDataObject
ABB name: egovera:DataContractDataObject
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/egovera/DataContractDataObject
Name: Data Contract Data-object
Interoperability Layer: Semantic
Specialises: http://data.europa.eu/dr8/DataPolicyBusinessObject
Definition: Risk Metadata ABB is a Data Object that encompasses data that identifies, assesses, and categorizes various risks associated with an organization's operations or processes. This includes information on the nature of the risk, probability of occurrence, potential impact, risk mitigation measures, and monitoring strategies. This data object is crucial for effective risk management, aiding in decision-making processes, and ensuring the organization's resilience and compliance with regulatory standards.
Source: European Commission
Source reference: https://taxation-customs.ec.europa.eu/customs-4/customs-risk-management_en
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/egovera/RiskMetadataDataObject
EIRA traceability: eira:DataSetDataObject
LOST view: SV-Customs Datasets [Motivation]
EIRA concept: eira:ArchitectureBuildingBlock
ABB name: egovera:RiskMetadataDataObject
Additional identifier: http://data.europa.eu/dr8/egovera/RiskMetadataDataObject
eira:eifLayer: Semantic
Definition: Multimedia Object Metadata refers to structured information that describes and provides context to multimedia assets such as images, videos, audio files, and other multimedia content. It includes attributes such as title, creator, date, format, resolution, duration, keywords, and other descriptive information that helps identify, organize, and retrieve multimedia assets. Multimedia Object Metadata plays a crucial role in enabling efficient search, discovery, and management of multimedia content in various applications and systems.
Source: W3C
Source reference: https://www.w3.org/standards/
LOST view: SV-Business Agnostic Metadata
Identifier: http://data.europa.eu/dr8/egovera/MultimediaObjectMetadataDataObject
EIRA traceability: eira:DataSetDataObject
ABB name: egovera:MultimediaObjectMetadataDataObject
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2022-01-16
Description: The ICS is an EU system designed to enhance customs control over goods entering the EU. It involves the submission of advanced electronic entry summary declarations by carriers or their representatives before the goods arrive in the EU. The ICS helps customs authorities identify high-risk consignments and streamline import procedures.
Publisher: European Commission
Source: http://www.ics-import-control-system.net/#:~:text=ICS%20%28Import%20Control%20System%29%20is%20the%20electronic%20security,within%20the%20scope%20of%20the%20EU%20eCUSTOMS%20programme.
LOST view: SV-Customs Base Registries [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/ICSDataObject
EIRA traceability: eira:BaseRegistryDataObject
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-16-01
LOST view: SV-Forms Structure
Identifier: http://data.europa.eu/dr8/egovera/FeedbackFormDataObject
EIRA traceability: eira:FormsStructureDataObject
ABB name: egovera:FeedbackFormDataObject
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2022-01-17
Description: The single administrative document (SAD) is a form used for customs declarations in the EU, Switzerland, Norway, Iceland, Turkey, the Republic of North Macedonia and Serbia. It is composed of a set of eight copies each with a different function. Using one single document reduces the administrative burden and increases the standardisation and harmonisation of data collected on trade.
Publisher: European Commission
LOST view: SV-Customs Form Structure [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/SingleAdministrativeDocumentDataObject
EIRA traceability: eira:FormsStructureDataObject
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-08-20
dct:identifier: http://data.europa.eu/dr8/egovera/SingleAdministrativeDocumentDataObject
Definition: Solution Building Block ABB is an Artifact that corresponds to a piece of data, produced software or deployment/operation of IT system that permit to implement one or more EIRA Architecture Building Blocks of an European Public Service.
Source: ISA2
Source reference: https://ec.europa.eu/isa2/sites/default/files/e-government_core_vocabularies_handbook.pdf
Additional information: Solution Builsing Block ABB is formulated as an agreed normative statement in design terms on a legal, organisational, semantic, or technical attribute of an European Public Service. On the technical view, a Solution Building Block is a specific software component that it might be either procured or developed of a To-Be Interoperable European Solution or that it is integrated in an As-Is Interoperable European Solution
Interoperability saliency: The Solution Building Block ABB is salient for the technical interoperability due to establishing the technical aspects related to the definition of architecture and public service architectural principles to support public administration in the service delivery.
Identifier: http://data.europa.eu/dr8/SolutionBuildingBlockArtifact
eira:ID: ABB610
ABB name: eira:SolutionBuildingBlockArtifact
Description: Common Communication Network 2 (CCN 2) is a pan-European telecommunications network that provides a secure and reliable platform for the exchange of information between the European Commission, EU Member States, and other participating parties.
Additional information: CCN 2 is a high-speed network that supports the exchange of information for various applications and services related to the European Union's policies and activities. It is a key component of the EU's digital infrastructure, enabling the secure and efficient transmission of data across borders. The network is managed by the European Commission's Directorate-General for Taxation and Customs Union (DG TAXUD). It is used for a wide range of applications, including customs, taxation, and agricultural policy, among others. The network is designed to ensure the confidentiality, integrity, and availability of the data it transmits, using advanced security measures and protocols.
Example: Examples of applications that use the CCN 2 network include the New Computerised Transit System (NCTS), which manages the movement of goods across EU borders, and the Excise Movement and Control System (EMCS), which monitors the movement of excise goods within the EU. Another example is the Integrated Administration and Control System (IACS), which supports the management of agricultural subsidies.
Publisher: Register of the Data Protection Officer (DPO)
Source: https://ec.europa.eu/dpo-register/detail/DPR-EC-01106.1
LOST view: TVI-Wide Area Networking [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/CommonCommunicationNetwork2CommunicationNetwork
EIRA traceability: eira:SecurePublicCommunicationNetwork
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-08-21
dct:identifier: http://data.europa.eu/dr8/egovera/CommonCommunicationNetwork2CommunicationNetwork
dct:title: Common Communication Network 2 (CCN 2) Communication Network
Definition: Local Area Network ABB is a Communication Network that enables the connection of devices and computers within a limited area.
Source: Networkbits
Source reference: https://web.archive.org/web/20201026082752/http://networkbits.net/lan-components/local-area-network-lan-basic-components/
Example: The following implementation is an example of how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): European Commission. https://ec.europa.eu/commission/presscorner/detail/en/MEMO_05_256
LOST view: Technical view - Infrastructure
Interoperability saliency: The Local Area Network ABB is salient for technical interoperability as the infrastructure that can connect devices and tools within a limited area of the public administration.
Identifier: http://data.europa.eu/dr8/LocalAreaCommunicationNetwork
eira:ID: http://data.europa.eu/dr8/LocalAreaCommunicationNetwork
ABB name: eira:LocalAreaCommunicationNetwork
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2022-31-01
Definition: Public Network ABB is a Communication Network that enables access to 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.
Source: ISA2 - EIA Action
Source reference: https://digital-strategy.ec.europa.eu/en/news/isa2-interoperability-solutions-european-public-administrations-first-work-programme-adopted
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): World-Wide-Web (WWW) - The WorldWideWeb (W3) is a wide-area hypermedia information retrieval initiative aiming to give universal access to a large universe of documents.
LOST view: Technical view - Infrastructure
Interoperability saliency: The Public Network ABB is salient for technical interoperability due to it provides the network infrastructure to facilitate access to the public administration digital service to the general public.
Identifier: http://data.europa.eu/dr8/PublicCommunicationNetwork
eira:ID: http://data.europa.eu/dr8/PublicCommunicationNetwork
ABB name: eira:PublicCommunicationNetwork
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2022-31-01
Definition: Private Network ABB is a Communication Network that enables the implementation of a network used for realising the physical communication among Interoperable European Solution (e.g. sTESTA), and cannot be accessed by the public.
Source: ISA2 - EIA Action
Source reference: https://ec.europa.eu/isa2/actions/towards-european-interoperability-architecture_en/
Example: The following implementation is an example of how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): ECC Report 301. https://docdb.cept.org/download/1395
Interoperability Dimension: Structural IoP
LOST view: Technical view - infrastructure
Interoperability Saliency: Private Network ABB is salient for technical interoperability because it implements and establishes the basis of the network of the public administration private area for exchanging, storing and sharing information at the internal level.
Identifier: http://data.europa.eu/dr8/PrivateNetworkCommunicationNetwork
ABB name: eira:PrivateNetworkCommunicationNetwork
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/PrivateNetworkCommunicationNetwork
Interoperability Layer: TechnicalInfrastructure
Definition: Cloud Private Network ABB is a Communication Network that enables a virtual network that connects resources and services within a cloud computing environment.
Source: Inspired in referent cloud service providers definitions
Example: The following implementation is an example of how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): JRC- Development of the EU Green Public Procurement (GPP)- Criteria for Data Centres, Server Rooms and Cloud Services. https://ec.europa.eu/environment/gpp/pdf/jrc118558_2020_0605_data_centres_technical_report_jrc_clean_with_id.pdf
LOST view: Technical view - Infrastructure
Interoperability saliency: The Cloud Private Network ABB is salient for technical interoperability because it provides the needed infrastructure connection between cloud service providers to a specific group of people, organizations or systems.
Identifier: http://data.europa.eu/dr8/CloudPrivateCommunicationNetwork
eira:ID: http://data.europa.eu/dr8/CloudPrivateCommunicationNetwork
ABB name: eira:CloudPrivateCommunicationNetwork
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2022-31-01
Description: Common Communication Network (CCN) is a standardized system for transmitting and receiving data between different systems or devices. It is often used in industries such as telecommunications, computing, and networking to facilitate seamless communication and data exchange.
Additional information: CCN is a critical component in modern digital communication, enabling different systems and devices to communicate effectively. It provides a common platform for data transmission, ensuring that all systems can understand and interpret the data being sent. CCN can be used in various settings, including local area networks (LANs), wide area networks (WANs), and even the internet. It is designed to handle different types of data, including text, images, audio, and video, making it a versatile solution for many different applications.
Example: Examples of CCN application include its use in telecommunications where it allows for seamless data transmission between different devices, such as phones, computers, and servers. In computing, it can be used to facilitate communication between different systems, such as in a cloud computing environment where data needs to be shared between different servers. In networking, it can be used to connect different networks, allowing them to communicate and share data.
Publisher: Register of the Data Protection Officer (DPO)
Source: https://ec.europa.eu/dpo-register/detail/DPR-EC-04049.1
LOST view: TVI-Wide Area Networking [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/CommonCommunicationNetworkCommunicationNetwork
EIRA traceability: eira:SecurePublicCommunicationNetwork
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-08-21
dct:identifier: http://data.europa.eu/dr8/egovera/CommonCommunicationNetworkCommunicationNetwork
dct:title: Common Communication Network (CCN) Communication Network
Definition: Secure Public Network ABB is a Communication Network that enables access to the public, but is designed and configured to protect against unauthorized access and cyber threats
Source: ISA2 - EIA Action
Source reference: https://digital-strategy.ec.europa.eu/en/news/isa2-interoperability-solutions-european-public-administrations-first-work-programme-adopted
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): World-Wide-Web (WWW) - The WorldWideWeb (W3) is a wide-area hypermedia information retrieval initiative aiming to give universal access to a large universe of documents.
LOST view: Technical view - Infrastructure
Interoperability saliency: Secure Public Network ABB is salient for technical interoperability because it set up the network infrastructure to establish secure communications with the public administration services.
Identifier: http://data.europa.eu/dr8/SecurePublicCommunicationNetwork
eira:ID: http://data.europa.eu/dr8/SecurePublicCommunicationNetwork
ABB name: eira:SecurePublicCommunicationNetwork
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2022-31-01
Definition: Private Subnetwork ABB is a Communication Network that enables the implementation of a subset of a larger network that is isolated and only accessible to a specific group of devices or users
Source: ISA2 - EIA Action
Source reference: https://ec.europa.eu/isa2/actions/towards-european-interoperability-architecture_en/
Example: The following implementation is an example of how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): ECC Report 301. https://docdb.cept.org/download/1395
Interoperability Dimension: Structural IoP
LOST view: Technical view - infrastructure
Interoperability Saliency: The private subnetwork ABB is salient for technical interoperability because it provides custom private areas to share internal information about specific public administration internal services. These areas are only accessible by a restricted number of people and/or devices.
Identifier: http://data.europa.eu/dr8/PrivateSubnetworkCommunicationNetwork
ABB name: eira:PrivateSubnetworkCommunicationNetwork
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/PrivateSubnetworkCommunicationNetwork
Interoperability Layer: TechnicalInfrastructure
Definition: Desktop Computer ABB is a Device in which the main unit is in a permanent location and is not designed for portability and is designed for use with an external display and external peripherals such as a keyboard and mouse.
Source: European Comission
Source reference: https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32013R0617
LOST view: Technical view - Infrastructure
Interoperability saliency: The Desktop Computer ABB is salient for technical interoperability because it provides the physical element to communicate with public services.
Identifier: http://data.europa.eu/dr8/DesktopComputerDevice
eira:ID: http://data.europa.eu/dr8/DesktopComputerDevice
ABB name: eira:DesktopComputerDevice
EIRA concept: eira:ArchitectureBuildingBlock
Definition: Remote Desktop Client ABB is a Device that enables access, control and interaction with a remote computer located anywhere through the internet or internal network.
Source: Inspired in Gartner
Source reference: https://www.gartner.com/en/information-technology/glossary/remote-access
LOST view: Technical view - Infrastructure
Interoperability saliency: The Remote Desktop Client ABB is salient for technical interoperability because it provides the physical element to remotely connect to shared workspaces to access public services.
Identifier: http://data.europa.eu/dr8/RemoteDesktopClientDevice
eira:ID: http://data.europa.eu/dr8/RemoteDesktopClientDevice
ABB name: eira:RemoteDesktopClientDevice
EIRA concept: eira:ArchitectureBuildingBlock
Definition: Sensor ABB is a Device that that detects and responds to events or changes in the physical environment.
Source: Inspired in SAREF
Source reference: https://saref.etsi.org/core/Sensor
Additional information: Sensors convert physical inputs into electrical signals that can be processed and analyzed by electronic systems or software
LOST view: Technical view - Infrastructure
Interoperability saliency: The Sensor ABB is salient for technical interoperability because it provides needed observational elements to measure specific elements that serve to improve eGovernance services.
Identifier: http://data.europa.eu/dr8/SensorDevice
eira:ID: http://data.europa.eu/dr8/SensorDevice
ABB name: eira:SensorDevice
Definition: Smart Device ABB is a Device that can operate interactively and autonomously, connected to other devices or networks through different communication protocols.
Source: European Comission
Source reference: https://digital-strategy.ec.europa.eu/en/policies/internet-things-policy
Synonym:
Additional information: Smart devices typically incorporate sensors, processors, and connectivity technology, such as Wi-Fi or Bluetooth, that allow them to collect and exchange data
IoP Dimension:
LOST view: Technical view - Infrastructure
Interoperability saliency: The Smart Device ABB is salient for technical interoperability because it provides the physical element to exchange information and events with the public administration digital services.
Identifier: http://data.europa.eu/dr8/SmartDevice
eira:ID: http://data.europa.eu/dr8/SmartDevice
ABB name: eira:SmartDevice
EIRA concept: eira:ArchitectureBuildingBlock
Last modification:
Definition: The Physical Computing Infrastructure ABB is an Equipment that enables the processing, storage, and transmission of data in a computing environment.
Source: Inspired on relevant IT infrastructure providers
LOST view: Technical view - Infrastructure
Interoperability saliency: The Physical Computing Infrastructure ABB is salient for technical interoperability because it establishes the infrastructure to analyse a large amount of information.
Identifier: http://data.europa.eu/dr8/PhysicalComputingInfrastructureEquipment
ABB name: eira:PhysicalComputingInfrastructureEquipment
EIRA concept: eira:ArchitectureBuildingBlock
eira:ID : http://data.europa.eu/dr8/PhysicalComputingInfrastructure
Definition: The Physical Network Infrastructure ABB is an Equipment that enables connectivity and communication between users, devices, apps and the Internet.
Source: Inspired on relevant Physical Network Infrastructure providers
LOST view: Technical view - Infrastructure
Interoperability saliency: The Physical Network Infrastructure ABB is salient for technical interoperability because it provides the infrastructure to facilitate the hosting and execution of public administration services.
Identifier: http://data.europa.eu/dr8/PhysicalNetworkInfrastructureEquipment
eira:ID: http://data.europa.eu/dr8/PhysicalNetworkInfrastructureEquipment
ABB name: eira:PhysicalNetworkInfrastructureEquipment
EIRA concept: eira:ArchitectureBuildingBlock
Definition: Physical Power Supply Infrastructure ABB is Equipment that enables reliable and uninterrupted electrical power to support the operation of public administration systems.
Source: Inspired in Lawinsider
Source reference: https://www.lawinsider.com/dictionary/power-supply-infrastructure
LOST view: Technical view - Infrastructure
Interoperability saliency: The Physical Power Supply Infrastructure ABB is salient for the technical interoperability due to it provides electrical supply to the public administration systems for ensuring their availability according to the service level agreements.
Identifier: http://data.europa.eu/dr8/PhysicalPowerSupplyInfrastructureEquipment
ABB name: eira:PhysicalPowerSupplyInfrastructureEquipment
EIRA concept: eira:ArchitectureBuildingBlock
eira:ID : http://data.europa.eu/dr8/PhysicalPowerSupplyInfrastructure
Definition: The Physical Communication Infrastructure ABB is an Equipment that enables components to exchange data.
Source: Law Insider
Source reference: https://www.lawinsider.com/dictionary/communication-infrastructure
Additional information: The Physical Communication Infrastructure includes but is not limited to fixed links, radio communication transmitters, fibre/copper cable, towers, switches, base stations. Customer premise equipment is not included.
LOST view: Technical view - Infrastructure
Interoperability saliency: The Physical Communication Infrastructure ABB is salient for technical interoperability because it provides the infrastructure in charge of bringing the data exchange and communication between public administration services.
Identifier: http://data.europa.eu/dr8/PhysicalCommunicationInfrastructureEquipment
ABB name: eira:PhysicalCommunicationInfrastructureEquipment
EIRA concept: eira:ArchitectureBuildingBlock
eira:ID : http://data.europa.eu/dr8/PhysicalCommunicationInfrastructure
Definition: Physical Security Infrastructure ABB is Equipment that enables the protection of facilities and assets from actions and events that could cause damage or losses.
Source: Inspired in Gartner
Source reference: https://www.gartner.com/en/information-technology/glossary/physical-security
LOST view: Technical view - Infrastructure
Interoperability saliency: The Physical Security Infrastructure ABB is salient for technical interoperability because it provides the infrastructure capable of providing functionalities of data protection and privacy.
Identifier: http://data.europa.eu/dr8/PhysicalSecurityInfrastructureEquipment
ABB name: eira:PhysicalSecurityInfrastructureEquipment
EIRA concept: eira:ArchitectureBuildingBlock
eira:ID : http://data.europa.eu/dr8/PhysicalSecurityInfrastructure
Definition: On Premise Facility ABB is a Facility referring to to a physical location, such as an office or data center, that is owned and managed by a business or organization
Source: Inspired in The Free Dictionary
Source reference: https://encyclopedia2.thefreedictionary.com/Facility
Example: The following implementation is an example of how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): JRC- Development of the EU Green Public Procurement (GPP)- Critaria for Data Centres, Server Rooms and Cloud Services. https://ec.europa.eu/environment/gpp/pdf/jrc118558_2020_0605_data_centres_technical_report_jrc_clean_with_id.pdf
Interoperability Dimension: Structural IoP
LOST view: Technical view - infrastructure
Viewpoint: Interoperability Security viewpoint
Interoperability Saliency: The On Premise Facility ABB is salient for organizational interoperability because it establishes the business rules and responsibilities to place the public administration ICT infrastructure in a custom location.
Identifier: http://data.europa.eu/dr8/OnPremiseFacilityFacility
ABB name: eira:OnPremiseFacilityFacility
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/OnPremiseFacilityFacility
Interoperability Layer: TechnicalInfrastructure
Definition: Hosting Facility ABB is a Facility that enables components and services to make public services available on the Internet for their use.
Source: Law Insider
Source reference: https://www.lawinsider.com/dictionary/hosting-facility#:~:text=Hosting%20Facility%20means%20a%20third,for%20use%20by%20End%20Users.
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): DIGIT/C Hosting Facility - DIGIT/C offers a high availability and high-performance hosting infrastructure that is comprised, among other elements, of back-end web server instances and application servers for hosting and serving both static and dynamic sites. The dynamic sites supported by the standard Apache web servers are mainly sites based on Coldfusion and in some cases also sites using CGI scripts. Dynamic sites based on particular technologies (i.e. Weblogic) are being hosted on individual application servers and are being integrated with the other related sites using reverse proxy mappings. Direct HTTP access to the back-end web servers hosting the static sites is denied by the standard web server configuration. http://ec.europa.eu/ipg/build/infrastructure/index_en.htm
Interoperability Dimension: Structural IoP
LOST view: Technical view - infrastructure
Viewpoint: Interoperability Security viewpoint
Interoperability Saliency: Hosting Facility ABB is salient for the technical interoperability because it establish the set up of IT systems to deliver the different public administration digital services and architectures that permit to integrate data from different infrastructure and remove existing IT silos in public administration.
Identifier: http://data.europa.eu/dr8/HostingFacilityFacility
ABB name: eira:HostingFacilityFacility
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/HostingFacilityFacility
Interoperability Layer: TechnicalInfrastructure
Definition: Private Cloud Computing Facility ABB is a Facility that enables a cloud infrastructure that is exclusively dedicated to a single organization or user.
Source: Inspired in Redhat
Source reference: https://www.redhat.com/en/topics/cloud-computing/public-cloud-vs-private-cloud-and-hybrid-cloud
Example: The following implementation is an example of how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): JRC- Development of the EU Green Public Procurement (GPP)- Critaria for Data Centres, Server Rooms and Cloud Services. https://ec.europa.eu/environment/gpp/pdf/jrc118558_2020_0605_data_centres_technical_report_jrc_clean_with_id.pdf
Interoperability Dimension: Structural IoP
LOST view: Technical view - infrastructure
Viewpoint: Interoperability Security viewpoint
Interoperability Saliency: Private Cloud Facilities ABB is salient for organizational and technical interoperability because it establishes the business rules and responsibilities to expose public digital services that are restricted for the use of custom organizations, users or devices.
Identifier: http://data.europa.eu/dr8/PrivateCloudComputingFacilityFacility
ABB name: eira:PrivateCloudComputingFacilityFacility
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/PrivateCloudComputingFacilityFacility
Interoperability Layer: TechnicalInfrastructure
Definition: Hybrid Cloud Facility ABB is a Facility that enables a mix of cloud computing services combining at least one private cloud and one public cloud working together.
Source: Inspired in referent cloud service providers
Example: The following implementation is an example of how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): JRC- Development of the EU Green Public Procurement (GPP)- Criteria for Data Centres, Server Rooms and Cloud Services. https://ec.europa.eu/environment/gpp/pdf/jrc118558_2020_0605_data_centres_technical_report_jrc_clean_with_id.pdf
Interoperability Dimension: Structural IoP
LOST view: Technical view - infrastructure
Interoperability Saliency: The Hybrid Cloud Facility ABB is salient for organizational and technical interoperability because it provides a set of business rules and responsibilities to the administration of public administration services. Moreover, it also provides the needed infrastructure to manage private and public services remotely.
Identifier: http://data.europa.eu/dr8/HybridCloudFacilityFacility
ABB name: eira:HybridCloudFacilityFacility
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/HybridCloudFacilityFacility
Interoperability Layer: TechnicalInfrastructure
Definition: Cloud Computing Facility ABB is a Facility that enables the storage, processing and use of data on remotely located devices accessed over the internet
Source: European Comission-Unleashing the Potential of Cloud Computing in Europe
Source reference: https://eur-lex.europa.eu/LexUriServ/LexUriServ.do?uri=COM:2012:0529:FIN:en:PDF
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): FENIX is an infrastructure research project that incorporates cloud computing facilities from ICT Solutions for Brilliant Minds. https://fenix-ri.eu/about-fenix/project-partners
Interoperability Dimension: Structural IoP
LOST view: Technical view - infrastructure
Interoperability Saliency: The Cloud Computing Facility ABB is salient for organizational interoperability due to it provides the business rules and responsibilities to publish and manage the public administration services.
Identifier: http://data.europa.eu/dr8/CloudComputingFacilityFacility
ABB name: eira:CloudComputingFacilityFacility
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/CloudComputingFacilityFacility
Interoperability Layer: TechnicalInfrastructure
Definition: Public Cloud Computing Facility ABB is a Facility that enables a cloud infrastructure that is shared among multiple users and organizations and is typically managed by a third-party service provider
Source: Inpired in Redhat
Source reference: https://www.redhat.com/en/topics/cloud-computing/public-cloud-vs-private-cloud-and-hybrid-cloud
Example: The following implementation is an example of how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): JRC- Development of the EU Green Public Procurement (GPP)- Critaria for Data Centres, Server Rooms and Cloud Services. https://ec.europa.eu/environment/gpp/pdf/jrc118558_2020_0605_data_centres_technical_report_jrc_clean_with_id.pdf
Interoperability Dimension: Structural IoP
LOST view: Technical view - infrastructure
Viewpoint: Interoperability Security viewpoint
Interoperability Saliency: Public Cloud Facilities ABB is salient for organizational and technical interoperability because it establishes the business rules and responsibilities to deploy and deliver public administration services remotely.
Identifier: http://data.europa.eu/dr8/PublicCloudComputingFacilityFacility
ABB name: eira:PublicCloudComputingFacilityFacility
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/PublicCloudComputingFacilityFacility
Interoperability Layer: TechnicalInfrastructure
Definition: External Facility ABB is a Facility that enables a physical location or infrastructure that is owned or operated by a third-party organization and used by another organization or individual. These facilities may include office buildings, data centres, warehouses, manufacture
Source: ISA2-EIA
Source reference: https://ec.europa.eu/isa2/actions/towards-european-interoperability-architecture_en/
LOST view: Technical view - Infrastructure
Interoperability saliency: The External Facility ABB is saliency for organizational and technical interoperability because it establishes the business rules and responsibilities to share infrastructures for the use of public administrations. The ABB also provides the application of open specifications and solutions to make interoperable public administration solutions.
Identifier: http://data.europa.eu/dr8/ExternalFacility
eira:ID: http://data.europa.eu/dr8/ExternalFacility
ABB name: eira:ExternalFacility
EIRA concept: eira:ArchitectureBuildingBlock
Definition: Server ABB is a Node that enables access to resources or services to other computers or devices on a network
Source: Gartner
Source reference: https://www.gartner.com/en/information-technology/glossary/clientserver
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): DIGIT/C Hosting Service - DIGIT/C offers a high availability and high performance hosting infrastructure that is being comprised, among other elements, of back-end web server instances and application servers for hosting and serving both static and dynamic sites. http://ec.europa.eu/ipg/build/infrastructure/index_en.htm
LOST view: Technical view - Infrastructure
Interoperability saliency: The Server ABB is salient for technical interoperability because it provides the capabilities to host public administration services at both levels, internally and externally.
Identifier: http://data.europa.eu/dr8/ServerNode
eira:ID: http://data.europa.eu/dr8/ServerNode
ABB name: eira:ServerNode
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2022-31-01
Definition: Virtual Machine ABB is a Node that enables the emulation of a physical computer to run programs and deploy applications.
Source: Inspired in Redhat
Source reference: https://www.redhat.com/en/topics/virtualization/what-is-a-virtual-machine
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): Redhat Virtualization: Built on Red Hat Enterprise Linux® and KVM and fully maintained by Red Hat, Red Hat® Virtualization is an enterprise virtualization platform that supports core virtualization workloads, including resource-intensive and important applications. With a solid foundation for a cloud-native and containerized future, virtualize your resources, workflows, and software applications. Additionally compatible with platforms like Microsoft Exchange and the Oracle database is Red Hat Enterprise Virtualization. https://www.redhat.com/en/technologies/virtualization/enterprise-virtualization
LOST view: Technical view - Infrastructure
Interoperability saliency: The Virtual Machine ABB is salient for technical interoperability because it provides needed tools to emulate the public administration services under controlled environments.
Identifier: http://data.europa.eu/dr8/VirtualMachineNode
eira:ID: http://data.europa.eu/dr8/VirtualMachineNode
ABB name: eira:VirtualMachineNode
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2022-31-01
Definition: Container ABB is a Technology Service that implements an executable unit of software in which application code is packaged, along with its libraries and dependencies, in common ways so that it can be run anywhere, whether it be on a desktop, traditional IT, or the cloud
Source: Inspired in referent cloud service providers
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): Docker. Docker is a containerization technology that works with the Kubernetes platform, with many adopting it to create an app that runs across multiple containers. https://www.docker.com/
Interoperability Dimension: Structural IoP
LOST view: Technical view - infrastructure
Interoperability Saliency: Container ABB is salient for technical interoperability because it provides the packaged software that contains or nurtures the functionalities of public services.
Identifier: http://data.europa.eu/dr8/ContainerSystemSoftware
ABB name: eira:ContainerSystemSoftware
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/ContainerSystemSoftware
Interoperability Layer: TechnicalInfrastructure
Definition: Edge Computing ABB is a Technology Collaboration that enables the procedures to implement a distributed computing topology where information processing is located close to the edge, where things and people produce or consume that information
Source: Gartner
Source reference: https://www.gartner.com/en/information-technology/glossary/edge-computing
Synonym:
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): SovereignEDGE.eu https://sovereignedge.eu/
Interoperability Dimension: Structural IoP
LOST view: Technical view - infrastructure
Interoperability Saliency: The Edge Computing ABB is salient for technical interoperability because it provides needed computational elements and tools to perform data analytics in specific devices that can nurture public administration digital services (e.g. mobiles from citizens).
Identifier: http://data.europa.eu/dr8/EdgeComputingTechnologyCollaboration
ABB name: eira:EdgeComputingTechnologyCollaboration
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/EdgeComputingTechnologyCollaboration
Interoperability Layer: TechnicalInfrastructure
Definition: Technology Interface ABB is an archimate Technology Interface that represents a point of access where technology services offered by a technology internal active structure element can be accessed.
Source: Inspired in Archimate
Source reference: https://pubs.opengroup.org/architecture/archimate3-doc/chap10.html
Synonym:
Additional information: A technology interface specifies how the technology services of a technology internal active structure element can be accessed by other elements. A technology interface exposes a technology service to the environment. The same service may be exposed through different interfaces.
Interoperability Dimension: Behavioral IoP
LOST view: Technical view - infrastructure
Viewpoint: Key Interoperability Enablers viewpoint
Interoperability Saliency: Technology Interface ABB is a key interoperability enabler (*) for behavioural, technical and semantic interoperability by enabling interfaces and access points to the architectures for infrastructure-to-infrastructure data exchange.
Identifier: http://data.europa.eu/dr8/TechnologyInterfaceTechnologyInterface
ABB name: eira:TechnologyInterfaceTechnologyInterface
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/TechnologyInterfaceTechnologyInterface
Interoperability Layer: TechnicalInfrastructure
Definition: Streaming Server ABB is a Technology Service that implements the behaviour of specialised computer server designed to stream digital multimedia content to client devices over the Internet or a local network
Source: Inspired in Gartner
Source reference: https://www.gartner.com/en/information-technology/glossary/streaming
Example: The following implementation is an example of how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): Study of use Open Source Software in the Public Sector. http://softlibre.unizar.es/manuales/legal/oss-fact-sheet.pdf
Interoperability Dimension: Behavioral IoP
LOST view: Technical view - infrastructure
Identifier: http://data.europa.eu/dr8/StreamingServerTechnologyService
ABB name: eira:StreamingServerTechnologyService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/StreamingServerTechnologyService
Interoperability Layer: TechnicalInfrastructure
Definition: Blockchain Ledger ABB is a Technology Service that enables the procedures to record, share, and synchronize transactions in the respective electronic ledger.
Source: World Bank
Source reference: https://www.worldbank.org/en/topic/financialsector/brief/blockchain-dlt
Additional information: Electronic Ledgers means the electronic master records of all contracts of the Sellers or the Issuer similar to and including the Contracts
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): OpenCHAIN is an open-source blockchain platform with distributed ledger technology. This blockchain company is suitable for organizations managing digital assets in secure and robust ways. Blockchain technology does not require fees for mining and the Bitcoin blockchain is significant for its immutability. https://www.openchainproject.org/
Interoperability Dimension: Structural IoP
LOST view: Technical view - infrastructure
Interoperability Saliency: Blockchain Ledger ABB is salient for technical interoperability because it established the elements to publish public services and subsequent information securely across a trustworthy network.
Identifier: http://data.europa.eu/dr8/BlockchainLedgerTechnologyService
ABB name: eira:BlockchainLedgerTechnologyService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/BlockchainLedgerTechnologyService
Interoperability Layer: TechnicalInfrastructure
Definition: Logger ABB is a Technology Service that enables the procedures recording events or messages that occur within a system or application
Source: Inspired in Gartner
Source reference: https://www.gartner.com/en/information-technology/glossary/event-fault-and-log-management
Example: The following implementation is an example of how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): OECD-OPSI- Quality of Public Administrations - A toolbox for practicioners. https://oecd-opsi.org/toolkits/quality-of-public-administration-a-toolbox-for-practitioners/
Interoperability Dimension: Structural IoP
LOST view: Technical view - infrastructure
Interoperability Saliency: Logger ABB is salient for semantic and technical interoperability due to it defines the mechanisms to manage messages from the applications to enhance their behavioural understanding in the execution or when unexpected behaviours occur. These mechanisms are based on open specifications for messaging representation and exchange.
Identifier: http://data.europa.eu/dr8/LoggerTechnologyService
ABB name: eira:LoggerTechnologyService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/LoggerTechnologyService
Interoperability Layer: TechnicalInfrastructure
Definition: SaaS ABB is a Technology Service that enables the procedures for delivering software that is owned and managed remotely by one or more providers. The provider delivers software based on one set of common code and data definitions that is consumed in a one-to-many model by all contracted customers at any time on a pay-for-use basis or as a subscription based on use metrics.
Source: Gartner
Source reference: https://www.gartner.com/en/information-technology/glossary/software-as-a-service-saas
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): Drupal is content management software. It's used to make many of the websites and applications you use every day. Drupal has great standard features, like easy content authoring, reliable performance, and excellent security. But what sets it apart is its flexibility; modularity is one of its core principles. Its tools help you build the versatile, structured content that dynamic web experiences need. https://www.drupal.org/about
Interoperability Dimension: Structural IoP
LOST view: Technical view - infrastructure
Interoperability Saliency: The SaaS ABB is salient for organizational, semantic and technical and technical interoperability due to it provides the needed infrastructure to deliver public administration services on demand. Also, SaaS provides the functionalities of common data models and definitions to support the internal communication between software components. Finally, SaaS provides also the set up of business rules to ensure the correct performance of the software modules.
Identifier: http://data.europa.eu/dr8/SaasTechnologyService
ABB name: eira:SaasTechnologyService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/SaasTechnologyService
Interoperability Layer: TechnicalInfrastructure
Definition: Backup ABB is a is a Technology Service that implements the behaviour of a software tool that create a copy of important data or information to ensure that it can be recovered in case of data loss, corruption, or system failure
Source: Gartner
Source reference: https://www.gartner.com/en/information-technology/glossary/backup-server
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): Backup Archiving Recovery Open Sourced (bareos) is a set of computer programs that permits you (or the system administrator) to manage backup, recovery, and verification of computer data across a network of computers of different kinds. In technical terms, it is a network Client/Server based backup program. Bareos is relatively easy to use and efficient, while offering many advanced storage management features that make it easy to find and recover lost or damaged files. Due to its modular design, Bareos is scalable from small single computer systems to systems consisting of hundreds of computers located over a large network.. https://www.bareos.com/
Interoperability Dimension: Structural IoP
LOST view: Technical view - infrastructure
Interoperability Saliency: Backup System ABB is salient for technical interoperability because it provides a secure mechanism to recover important information in case of unexpected behaviour of public administration services.
Identifier: http://data.europa.eu/dr8/BackupTechnologyService
ABB name: eira:BackupTechnologyService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/BackupTechnologyService
Interoperability Layer: TechnicalInfrastructure
Definition: Containers Orchestration ABB is a Technology Service that enables the procedures to automate the deployment, management, scaling, and networking of containers
Source: Red Hat
Source reference: https://www.redhat.com/en/topics/containers/what-is-container-orchestration
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): OpenSHIFT is a secure and an enterprise-grade cloud-based container orchestration system with Kubernetes at the backend. It can be used both as a Red Hat Container Orchestration Engine and Platform-as-a-Service (PaaS). https://github.com/openshift/origin
Interoperability Dimension: Structural IoP
LOST view: Technical view - infrastructure
Interoperability Saliency: Containers Orchestrator ABB is salient for technical interoperability due to it provides the mechanism and networks to organize virtual public services and tools to facilitate the deployment and publication of public digital services.
Identifier: http://data.europa.eu/dr8/ContainersOrchestratorTechnologyService
ABB name: eira:ContainersOrchestratorTechnologyService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/ContainersOrchestratorTechnologyService
Interoperability Layer: TechnicalInfrastructure
Definition: Business Process Manager ABB is a Technology Service that implements the behaviour of coordinates the behavior of people, systems, information and things to produce business outcomes in support of a business strategy
Source: Gartner
Source reference: https://www.gartner.com/en/information-technology/glossary/business-process-management-bpm
Example: The following implementation is an example of how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): UNDP- Business Process Re-engineering Manual. https://www.undp.org/sites/g/files/zskgke326/files/migration/uz/BPR-Manual_designed---Eng---final.pdf
Interoperability Dimension: Structural IoP
LOST view: Technical view - infrastructure
Interoperability Saliency: Business Process Manager ABB is salient for organizational interoperability due to it implements and defines business procedures related to public administration services.
Identifier: http://data.europa.eu/dr8/BusinessProcessManagerTechnologyService
ABB name: eira:BusinessProcessManagerTechnologyService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/BusinessProcessManagerTechnologyService
Interoperability Layer: TechnicalInfrastructure
Definition: Distributed File System is a Technology Service that implements the behaviour of a software tool that allows access to files from multiple computers in a distributed network
Source: Inspired in Gartner
Source reference: https://www.gartner.com/reviews/market/distributed-file-systems-and-object-storage
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): MooseFS is a Fault-tolerant, Highly available, Highly performing, Scaling-out, Network distributed file system. It spreads data over several physical commodity servers, which are visible to the user as one virtual disk. It is POSIX compliant and acts like any other Unix-like file system supporting: -Hierarchical structure: Files and Folders, -File attributes, -Special files: Pipes, Sockets, Block and Character devices, -Symbolic and Hard links, -Security attributes and ACLs. https://moosefs.com/
Interoperability Dimension: Structural IoP
LOST view: Technical view - infrastructure
Identifier: http://data.europa.eu/dr8/DistributedFileSystemTechnologyService
ABB name: eira:DistributedFileSystemTechnologyService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/DistributedFileSystemTechnologyService
Interoperability Layer: TechnicalInfrastructure
Definition: Business Intelligence ABB is a Technology Service that enables the procedure of collecting, storing, and analysing the data produced by the public administration to improve and optimise decisions and performance.
Source: Inspired in Gartner
Source reference: https://www.gartner.com/en/information-technology/glossary/business-intelligence-bi
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): Central banks increasingly need to use business intelligence (BI) systems to collect, manage and analyse data in order to inform policy decisions. This report presents the results of a survey conducted by the BIS’s Irving Fisher Committee on Central Bank Statistics (IFC) in 2019. The following link gives access to a report on the use of BI in Central Banks. https://www.bis.org/ifc/publ/ifc_report_bi_1910.pdf
Interoperability Dimension: Structural IoP
LOST view: Technical view - infrastructure
Interoperability Saliency: Business Intelligence ABB is salient for semantic interoperability because it provides visual and data understanding functionalities to be provided to the users in form of reports and other king of visual diagrams.
Identifier: http://data.europa.eu/dr8/BusinessIntelligenceTechnologyService
ABB name: eira:BusinessIntelligenceTechnologyService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/BusinessIntelligenceTechnologyService
Interoperability Layer: TechnicalInfrastructure
Definition: Router ABB is a Technology Service that enables the implementation of a component to connect multiple networks and directs traffic between them
Source: ISO 35.110
Source reference: https://www.iso.org/ics/35.110/x/
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): Turris Omnia Open Source Router, https://opensource.com/article/22/1/turris-omnia-open-source-router
Interoperability Dimension: Structural IoP
LOST view: Technical view - infrastructure
Interoperability Saliency: Router ABB is salient for technical interoperability due to it physically establishes the rules for distributing the information into a network.
Identifier: http://data.europa.eu/dr8/RouterTechnologyService
ABB name: eira:RouterTechnologyService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/RouterTechnologyService
Interoperability Layer: TechnicalInfrastructure
Definition: Containers Manager ABB is a Technology Service that implements the process of organizing, adding or replacing large numbers of software containers
Source: Inspired in referent cloud service providers
Source reference:
Synonym:
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): OpenSHIFT is a secure and an enterprise-grade cloud-based container orchestration system with Kubernetes at the backend. It can be used both as a Red Hat Container Orchestration Engine and Platform-as-a-Service (PaaS). https://github.com/openshift/origin
Interoperability Dimension: Structural IoP
LOST view: Technical view - infrastructure
Interoperability Saliency: Containers Manager ABB is salient for technical interoperability due to its setting up the software tool to manage virtual public services and tools.
Identifier: http://data.europa.eu/dr8/ContainersManagerTechnologyService
ABB name: eira:ContainersManagerTechnologyService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/ContainersManagerTechnologyService
Interoperability Layer: TechnicalInfrastructure
Definition: Event Manager ABB is a Technology Service that implements the behaviour of collecting, analyzing, and responding to events or alerts generated by various digital platforms, including servers, applications, network devices, and security appliances
Source: Inspired in the definition provided by relebant cloud service organizations.
Example: The following implementation is an example of how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): Apache Kafka (https://kafka.apache.org/)
Interoperability Dimension: Structural IoP
LOST view: Technical view - infrastructure
Interoperability Saliency: Event Manager ABB is salient for semantic and technical interoperability due to its establish mechanism to promote event and stream data sharing using existing open standards and commonly agreed metadata.
Identifier: http://data.europa.eu/dr8/EventManagerTechnologyService
ABB name: eira:EventManagerTechnologyService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/EventManagerTechnologyService
Interoperability Layer: TechnicalInfrastructure
Definition: IaaS ABB is a Technology Service that enables the procedures to implement a standardized, highly automated offering in which computing resources owned by a service provider, complemented by storage and networking capabilities, are offered to customers on demand. Resources are scalable and elastic in near real-time and metered by use. Self-service interfaces, including an API and a graphical user interface (GUI), are exposed directly to customers. Resources may be single-tenant or multitenant and are hosted by the service provider or on-premises in a customer’s data centre.
Source: Gartner
Source reference: https://www.gartner.com/en/information-technology/glossary/infrastructure-as-a-service-iaas
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): EBSI, the European Blockchain Service Infrastructure. lockchain Services Infrastructure (EBSI) aims to leverage the power of blockchain for the public good. EBSI is an initiative of the European Commission and the European Blockchain Partnership. what are databricks
Interoperability Dimension: Structural IoP
LOST view: Technical view - infrastructure
Interoperability Saliency: The IaaS ABB is salient for technical interoperability because it provides the needed infrastructure to store information and virtualize software tools related to public administration.
Identifier: http://data.europa.eu/dr8/IaaSTechnologyService
ABB name: eira:IaaSTechnologyService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/IaaSTechnologyService
Interoperability Layer: TechnicalInfrastructure
Definition: Identity provider ABB is a Technology Service that enables the authentication of users and provides them with a secure means of accessing online resources and applications
Source: Inpired in eIDAS
Source reference: https://digital-strategy.ec.europa.eu/en/policies/eidas-regulation
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): EU Login is the European Commission's user authentication service. It allows authorised users to access a wide range of Commission web services. EU Login is the entry gate to sign in to different European Commission services and/or other systems. EU Login verifies your identity and allows recovering your personal settings, history and access rights in a secure way. You can sign in using social media accounts or the EU Login account. https://webgate.ec.europa.eu/cas/about.html
Interoperability Dimension: Structural IoP
LOST view: Technical view - infrastructure
Interoperability Saliency: Identity Provider ABB is salient for technical and semantic interoperability because it provides mechanisms to ensure the identification of stakeholders (organizations or individuals) across multiple platforms around Europe. Thus, it permits: (i) making interoperable identities across the public service platforms, and (ii) secure identification to the public services.
Identifier: http://data.europa.eu/dr8/IdentityProviderTechnologyService
ABB name: eira:IdentityProviderTechnologyService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/IdentityProviderTechnologyService
Interoperability Layer: TechnicalInfrastructure
Definition: API Gateway ABB is a Technology Service that implements the behaviour of acting as a single entry point for multiple APIs (Application Programming Interfaces)
Source: Inspired in Joinup
Source reference: https://joinup.ec.europa.eu/collection/api4dt/about
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): API Gateway Authentication Bundle. It authenticates requests from European Commission service API Gateway. https://joinup.ec.europa.eu/collection/ecphp/solution/api-gw-authentication-php/about
Interoperability Dimension: Structural IoP
LOST view: Technical view - infrastructure
Interoperability Saliency: API Gateway ABB is salient for semantic interoperability due to its setting up the rules to share multiple public administration digital services to facilitate their accessibility, discovery and sharing across platforms (catalogue of APIs). These rules follow up existing standards and common practices in the API documentation and accessibility (Open APIs description).
Identifier: http://data.europa.eu/dr8/APIGatewayTechnologyService
ABB name: eira:APIGatewayTechnologyService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/APIGatewayTechnologyService
Interoperability Layer: TechnicalInfrastructure
Definition: Relational Database Manager ABB is a Technology Service that implements the behaviour of a software system that provides access to and management of relational databases
Source: Inspired in Gartner
Source reference: https://www.gartner.com/en/information-technology/glossary/rdbms-relational-database-management-system
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): MySQL manager, an SQL for MySQL. https://www.sqlmanager.net/products/mysql/manager
Interoperability Dimension: Structural IoP
LOST view: Technical view - infrastructure
Interoperability Saliency: Relational Database Manager ABB is salient for semantic interoperability because it establishes a common mechanism to query structured data and share the information using common data exchange models
Identifier: http://data.europa.eu/dr8/RelationalDatabaseManagerTechnologyService
ABB name: eira:RelationalDatabaseManagerTechnologyService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/RelationalDatabaseManagerTechnologyService
Interoperability Layer: TechnicalInfrastructure
Definition: NoSQL Database Manager ABB is a Technology Service that enables the behaviour of a system that provides access to non-relational databases.
Source: Inspired in the definition provided by relebant noSQL vendors
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): NoSQL Manager by mongodb. User friendly interface and Shell power. Intuitive interface and high performance of the desktop application save time for beginners and professional database developers and administrators. https://www.mongodbmanager.com/
Interoperability Dimension: Structural IoP
LOST view: Technical view - infrastructure
Interoperability Saliency: NoSQL Database Manager ABB is salient for semantic interoperability due to its implements mechanism to manipulate NoSQL databases and share data using common data exchange models (e.g. JSON)
Identifier: http://data.europa.eu/dr8/NoSQLDatabaseManagerTechnologyService
ABB name: eira:NoSQLDatabaseManagerTechnologyService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/NoSQLDatabaseManagerTechnologyService
Interoperability Layer: TechnicalInfrastructure
Definition: Load Balancer ABB is a Technology Service that enables the implementation of a component that distributes incoming network traffic across multiple servers or network resources
Source: Inspired in referent cloud service providers definitions
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): DIGIT/C Hosting Service - DIGIT/C offers a high availability and high performance hosting infrastructure that is being comprised, among other elements, of back-end web server instances and application servers for hosting and serving both static and dynamic sites. http://ec.europa.eu/ipg/build/infrastructure/index_en.htm
Interoperability Dimension: Structural IoP
LOST view: Technical view - infrastructure
Interoperability Saliency: The Load Balancer ABB is salient for technical interoperability because it provides the functionalities to maintain the traffic to the public administration digital services accordingly with a load that can permit their correct performance.
Identifier: http://data.europa.eu/dr8/LoadBalancerTechnologyService
ABB name: eira:LoadBalancerTechnologyService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/LoadBalancerTechnologyService
Interoperability Layer: TechnicalInfrastructure
Definition: Data Catalog ABB is a Technology Service that enables the procedures of a centralised metadata repository to provide information about the data assets in a public administration
Source: Inspired in JRC
Source reference: https://data.jrc.ec.europa.eu/about
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): Jount Research Centre Data Catalogue. https://data.jrc.ec.europa.eu/
Interoperability Dimension: Structural IoP
LOST view: Technical view - infrastructure
Interoperability Saliency: Data Catalog ABB is salient for semantic interoperability because it provides grouped datasets of information enhanced with metadata to promote their discovery, sharing and understanding for other digital services and public administrations
Identifier: http://data.europa.eu/dr8/DataCatalogTechnologyService
ABB name: eira:DataCatalogTechnologyService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/DataCatalogTechnologyService
Interoperability Layer: TechnicalInfrastructure
Definition: PKI Certificate Manager ABB is a Technology Service that enables the procedures to issue, maintain and revoke public key certificates
Source: NIST
Source reference: https://csrc.nist.gov/glossary/term/public_key_infrastructure
Example: The following implementation is an example of how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): eDelivery - PKI Service. https://ec.europa.eu/digital-building-blocks/wikis/display/DIGITAL/PKI+Service
Interoperability Dimension: Structural IoP
LOST view: Technical view - infrastructure
Interoperability Saliency: PKI Certificate Manager ABB is salient for technical interoperability because permits the public services to exchange information through the use of digital certificates that permit the accessibility to such service.
Identifier: http://data.europa.eu/dr8/PKICertificateManagerTechnologyService
ABB name: eira:PKICertificateManagerTechnologyService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/PKICertificateManagerTechnologyService
Interoperability Layer: TechnicalInfrastructure
Definition: Block Storage ABB is an Application Component that enables the behaviour of breaking data into separate pieces (blocks) and storing them with a unique identifier.
Source: Inspired in referent cloud service providers
Example: The following implementation is an example of how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): Kibana at EU. https://big-data-test-infrastructure.ec.europa.eu/service-offering/kibana_en
Interoperability Dimension: Structural IoP
LOST view: Technical view - infrastructure
Interoperability Saliency: Block Storage ABB is salient for technical interoperability because it set up data storage and integration in fixed-sized blocks under a hierarchical infrastructure that permits ensuring their integrity through time.
Identifier: http://data.europa.eu/dr8/BlockStorageTechnologyService
ABB name: eira:BlockStorageTechnologyService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/BlockStorageTechnologyService
Interoperability Layer: TechnicalInfrastructure
Definition: Gateway ABB is a Technology Service that enables the implementation of a component that converts information, data or other communications from one protocol or format to another
Source: Gartner
Source reference: https://www.gartner.com/en/information-technology/glossary/gateway
Synonym:
Additional information:
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): The Single Digital Gateway from the European Commission is implemented via Your Europe Portal. This portal allows searching and exchanging information from businesses at the European and national level. information from EU and member states. https://europa.eu/youreurope/index_en.htm
Interoperability Dimension: Structural IoP
LOST view: Technical view - infrastructure
Interoperability Saliency: Gateway ABB is salient for technical interoperability because it physically transforms information, data and other communications from one protocol or format into another standard protocol format.
Identifier: http://data.europa.eu/dr8/GatewayTechnologyService
ABB name: eira:GatewayTechnologyService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/GatewayTechnologyService
Interoperability Layer: TechnicalInfrastructure
Definition: GraphQL ABB is a Technology Service that implements the behaviour of a server-side runtime that execute queries using a type system you define for your data
Source: GraphQL
Source reference: https://graphql.org/learn/
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): Github is using GraphQL Server and API to allow users retreive the required data without having additional information that is not relevant for its purpose. https://docs.github.com/es/graphql
Interoperability Dimension: Structural IoP
LOST view: Technical view - infrastructure
Interoperability Saliency: GraphQL Server ABB contributes to the semantic and technical interoperability because it set up the API that permits (i) access to the public administration information using semantics, (ii) exposes API following up common specifications related to GraphQL language.
Identifier: http://data.europa.eu/dr8/GraphQLServerTechnologyService
ABB name: eira:GraphQLServerTechnologyService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/GraphQLServerTechnologyService
Interoperability Layer: TechnicalInfrastructure
Definition: Immutable Database Manager ABB is a Technology Service that enables the procedure to manage data that cannot be (or shouldn't be) deleted or modified.
Source: ODBMS
Source reference: https://www.odbms.org/2015/10/the-rise-of-immutable-data-stores/
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): immubd is a database written in Go, but unlike other databases, it is immutable: history is preserved and can't be changed without clients noticing. immudb can be used both as a key-value store, or as a relational database (SQL). immudb can be run as full database server with replicas or easily embedded as a lightweight database into application. https://docs.immudb.io/master/
Interoperability Dimension: Structural IoP
LOST view: Technical view - infrastructure
Interoperability Saliency: Immutable Database Manager ABB is salient for technical interoperability because it establishes the mechanism to store information and also, manages that the stored information is cannot be deleted or modified.
Identifier: http://data.europa.eu/dr8/InmutableDatabaseManagerTechnologyService
ABB name: eira:InmutableDatabaseManagerTechnologyService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/InmutableDatabaseManagerTechnologyService
Interoperability Layer: TechnicalInfrastructure
Definition: Audit Manager ABB is a Technology Service that enables the procedures of managing audits and workflows, tracking audit progress, and ensuring compliance with regulations and standards
Source: Inspired in the definition provided by relebant cloud service organizations.
Example: The following implementation is an example of how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): Design Principles for Data Spaces -Position Paper. https://design-principles-for-data-spaces.org/
Interoperability Dimension: Structural IoP
LOST view: Technical view - infrastructure
Interoperability Saliency: Audit Manager ABB is salient for the technical interoperability due to it implements the rules to assess business workflows of public administration services to ensure compliance with the regulation and open standards.
Identifier: http://data.europa.eu/dr8/AuditManagerTechnologyService
ABB name: eira:AuditManagerTechnologyService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/AuditManagerTechnologyService
Interoperability Layer: TechnicalInfrastructure
Definition: Application Server ABB is a Technology Service that implements the behaviour of system software that resides between the operating system (OS) on one side, the external resources (such as a database management system [DBMS], communications and Internet services) on another side and the users’ applications on the third side.
Source: Gartner
Source reference: https://www.gartner.com/en/information-technology/glossary/application-server
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): DIGIT/C Hosting Service - DIGIT/C offers a high availability and high performance hosting infrastructure that is being comprised, among other elements, of back-end web server instances and application servers for hosting and serving both static and dynamic sites. http://ec.europa.eu/ipg/build/infrastructure/index_en.htm
Interoperability Dimension: Structural IoP
LOST view: Technical view - infrastructure
Interoperability Saliency: Application Server ABB is salient for semantic and technical interoperability because it implements the mechanism to expose access to applications using metadata. This exposition of application contributes to the integration of legacy systems and siloed information to expose to the different public service consumers.
Identifier: http://data.europa.eu/dr8/ApplicationServerTechnologyService
ABB name: eira:ApplicationServerTechnologyService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/ApplicationServerTechnologyService
Interoperability Layer: TechnicalInfrastructure
Definition: Containers Registry ABB is a Technology Service that enables the procedures to elaborate a repository of a collection of registries used to store and access container images
Source: Redhat
Source reference: https://www.redhat.com/en/topics/cloud-native-apps/what-is-a-container-registry
Additional information:
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): Project QUAY, Quay is a container image registry that enables you to build, organize, distribute, and deploy containers. Quay gives you security over your repositories with image vulnerability scanning and robust access controls. Project Quay provides a scalable open source platform to host container images across any size organization. https://www.projectquay.io/
Interoperability Dimension: Structural IoP
LOST view: Technical view - infrastructure
Interoperability Saliency: Container Registry ABB is salient for semantic interoperability due to it establishing a catalogue of registries of virtual public services and tools to be deployed and executed.
Identifier: http://data.europa.eu/dr8/ContainerRegistryTechnologyService
ABB name: eira:ContainerRegistryTechnologyService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/ContainerRegistryTechnologyService
Interoperability Layer: TechnicalInfrastructure
Definition: Firewall ABB is a technology Service that enables the implementation of a network security component that monitors and controls the incoming and outgoing network traffic based on predetermined security rules
Source: Inspired in referent cloud service providers definitions
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): pfSense® software is a free, open source customized distribution of FreeBSD specifically tailored for use as a firewall and router that is entirely managed via web interface. In addition to being a powerful, flexible firewalling and routing platform, it includes a long list of related features and a package system allowing further expandability without adding bloat and potential security vulnerabilities to the base distribution. https://www.pfsense.org/about-pfsense/
Interoperability Dimension: Structural IoP
LOST view: Technical view - infrastructure
Interoperability Saliency: The Firewall ABB is salient for technical interoperability because it permits control of the traffic between the public administration and the different information providers and information consumers.
Identifier: http://data.europa.eu/dr8/FirewallTechnologyService
ABB name: eira:FirewallTechnologyService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/FirewallTechnologyService
Interoperability Layer: TechnicalInfrastructure
Definition: Virtual Private Network ABB is a Technology Service that enables the procedures to implement a protected information system link utilizing tunnelling, security controls, and endpoint address translation giving the impression of a dedicated line
Source: NIST
Source reference: https://csrc.nist.gov/glossary/term/virtual_private_network
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): Virtual Private Network service for accessing European Commission servers out of the Commission. https://wikis.ec.europa.eu/display/WEBGUIDE/01.+Access+to+servers+from+outside+the+European+Commission
Interoperability Dimension: Structural IoP
LOST view: Technical view - infrastructure
Interoperability Saliency: Virtual Private Network ABB is salient for technical interoperability because it implements standard methods to build a secure network to exchange information in public administration
Identifier: http://data.europa.eu/dr8/VirtualPrivateNetworkTechnologyService
ABB name: eira:VirtualPrivateNetworkTechnologyService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/VirtualPrivateNetworkTechnologyService
Interoperability Layer: TechnicalInfrastructure
Definition: PaaS ABB is a Technology Service that enables the procedures for delivering application infrastructure (middleware) capabilities as a service. There are multiple types of PaaS (xPaaS), including, among many more, application platform as a service (aPaaS), integration PaaS (iPaaS), API management PaaS (apimPaaS), function PaaS (fPaaS), business analytics PaaS (baPaaS), IoT PaaS and database PaaS (dbPaaS). PaaS capability can be delivered as provider-managed or self-managed, multitenant or dedicated.
Source: Gartner
Source reference: https://www.gartner.com/en/information-technology/glossary/platform-as-a-service-paas
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): OpenSHIFT is a secure and an enterprise-grade cloud-based container orchestration system with Kubernetes at the backend. It can be used both as a Red Hat Container Orchestration Engine and Platform-as-a-Service (PaaS). https://github.com/openshift/origin
Interoperability Dimension: Structural IoP
LOST view: Technical view - infrastructure
Interoperability Saliency: The PaaS ABB is salient for technical interoperability because it provides the mechanism to deploy and publish public administration services and make them accessible through the provided remote infrastructure.
Identifier: http://data.europa.eu/dr8/PaaSTechnologyService
ABB name: eira:PaaSTechnologyService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/PaaSTechnologyService
Interoperability Layer: TechnicalInfrastructure
Definition: External Service ABB is a Technology Service that enables the procedures to offer services that are delivered by a third-party organization or vendor.
Source: Inspired in Gartner
Source reference: https://www.gartner.com/en/information-technology/glossary/esp-external-services-provider
LOST view: Technical view - Infrastructure
Interoperability saliency: The External Service ABB is salient for organizational and semantic interoperability because it establishes the business rules and responsibilities to share digital services on the use of the public administration to complement the existing ones. This ABB also provides standardised data exchange models to share the information provided by external services.
Identifier: http://data.europa.eu/dr8/ExternalTechnologyService
eira:ID: http://data.europa.eu/dr8/ExternalTechnologyService
ABB name: eira:ExternalTechnologyService
EIRA concept: eira:ArchitectureBuildingBlock
Definition: Lightweight Directory Access ABB is a Technology Service that enables compliance with an open, vendor-neutral, industry-standard application protocol for accessing and maintaining distributed directory information services over an Internet Protocol (IP) network.
Source: CAMSS
Source reference: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): Lightweight Directory Access Protocol can be implemented in multiple platforms or systems, allowing to integrating an organisatio'n LDAP-enabled identity management service to other platforms such as Drupal. https://www.drupal.org/docs/contributed-modules/lightweight-directory-access-protocol-ldap
Interoperability Dimension: Structural IoP
LOST view: Technical view - infrastructure
Interoperability Saliency: Lightweight Directory Access ABB is salient for technical and semantic interoperability because it provides the needed software mechanism and the LDAP data exchange model to manage user authentication, user provisioning and access to public services.
Identifier: http://data.europa.eu/dr8/LightweightDirectoryAccessProtocolTechnologyService
ABB name: eira:LightweightDirectoryAccessProtocolTechnologyService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/LightweightDirectoryAccessProtocolTechnologyService
Interoperability Layer: TechnicalInfrastructure
Definition: Data Lake Storage ABB is a Technology Service that implements the behaviour of a storage repository that allows organizations to store large amounts of structured, semi-structured, and unstructured data at any scale
Source: Inspired in Forbes
Source reference: https://www.forbes.com/sites/ciocentral/2011/07/21/big-data-requires-a-big-new-architecture/?sh=5be8fb361157
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): Smart Data Lake. https://smartdatalake.eu/
Interoperability Dimension: Structural IoP
LOST view: Technical view - infrastructure
Interoperability Saliency: Data Lake storage ABB is salient for semantic and technical interoperability because it provides the data architecture to store and share multiple sources of data under a common framework. This ABB also provides FAIR data through the application of data curation pipelines that maximise the data quality returned to the public service consumers.
Identifier: http://data.europa.eu/dr8/DataLakeStorageTechnologyService
ABB name: eira:DataLakeStorageTechnologyService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/DataLakeStorageTechnologyService
Interoperability Layer: TechnicalInfrastructure
Definition: API Manager ABB is a Technology Service that implements the behaviour of safely and securely publish APIs, either internally or externally
Source: Gartner
Source reference: https://www.gartner.com/en/information-technology/glossary/api-management
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): API Manager, WSO2 API Manager is a complete platform for building, integrating, and exposing your digital services as managed APIs in the cloud, on-premise, and hybrid architectures to drive your digital transformation strategy. https://apim.docs.wso2.com/en/latest/
Interoperability Dimension: Structural IoP
LOST view: Technical view - infrastructure
Interoperability Saliency: API Manager ABB is salient for semantic interoperability due to its setting up the rules to share public administration digital services to facilitate their accessibility, discovery and sharing across platforms. These rules follow up existing standards and common practices in the API documentation and accessibility (Open APIs description).
Identifier: http://data.europa.eu/dr8/APIManagerTechnologyService
ABB name: eira:APIManagerTechnologyService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/APIManagerTechnologyService
Interoperability Layer: TechnicalInfrastructure
Definition: Enterprise Service Bus ABB is a Technology Service that enables integration between applications by acting as a centralized component to perform the transformation in data models, handle connectivity, perform message routing, convert communication protocols and manage the composition of multiple requests.
Source: Gartner
Source reference: https://www.gartner.com/en/documents/1405237
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): eXTra Enterprise Service Bus (eESB), eESB is an Enterprise Service Bus for exchanging data between the institutes of the German pension insurance. To connect the services within one institute EJB-Technology is used. The communication with external partners and between the different institutes of the German pension insurance is based on SOAP-WebServices. As data structure for the general communication the eXTra-Standard is used to address the responsible service applications. https://joinup.ec.europa.eu/collection/egovernment/solution/extra-enterprise-service-bus-eesb/about
Interoperability Dimension: Structural IoP
LOST view: Technical view - infrastructure
Interoperability Saliency: Enterprise Service Bus ABB is salient for semantic and technical interoperability due to it ensuring (i) data sharing across different public service applications and infrastructures using specific enhanced datasets with metadata, and (ii) providing data sharing mechanism using open specifications and open data standards.
Identifier: http://data.europa.eu/dr8/EnterpriseServiceBusTechnologyService
ABB name: eira:EnterpriseServiceBusTechnologyService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/EnterpriseServiceBusTechnologyService
Interoperability Layer: TechnicalInfrastructure
Definition: Federated Identity Provider ABB is a Technology Service that enables users to access multiple applications and services across different organizations or domains using a single set of credentials
Source: Inpired in eIDAS
Source reference: https://digital-strategy.ec.europa.eu/en/policies/eidas-regulation
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): Federated Identity can be achieved by implementing the OpenID Connect Federation specification. https://openid.net/specs/openid-connect-federation-1_0.html
Interoperability Dimension: Structural IoP
LOST view: Technical view - infrastructure
Interoperability Saliency: Federated Identity Provider ABB is salient for technical interoperability because it conforms to the network of identity provider systems to distribute the transference and identification of stakeholders to access and make use of public services.
Identifier: http://data.europa.eu/dr8/FederatedIdentityProviderTechnologyService
ABB name: eira:FederatedIdentityProviderTechnologyService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/FederatedIdentityProviderTechnologyService
Interoperability Layer: TechnicalInfrastructure
Definition: Telemetry ABB is a Technology Service that enables the procedures to automatically measure and analyse information about public administration services and IT platforms to track performance and identify issues.
Source: EEA
Source reference: https://www.eea.europa.eu/help/glossary/gemet-environmental-thesaurus/telemetry
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): Telemetry is a clear example of use in computers integrated in spacecrafts. https://www.esa.int/Enabling_Support/Space_Engineering_Technology/Onboard_Computers_and_Data_Handling/Telemetry_Telecommand
Interoperability Dimension: Structural IoP
LOST view: Technical view - infrastructure
Interoperability Saliency: Telemetry is salient for semantic and technical interoperability because it sets up the mechanisms to monitor a specific ICT system to (i) collect behavioural information, and (ii) understand the ICT system's behaviour during its execution.
Identifier: http://data.europa.eu/dr8/TelemetryTechnologyService
ABB name: eira:TelemetryTechnologyService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/TelemetryTechnologyService
Interoperability Layer: TechnicalInfrastructure
Definition: Remote Desktop ABB is a Technology Service that enables the procedures to grant users to access and control a computer or device from a remote location using a network connection
Source: Inspired in Gartner
Source reference: https://www.gartner.com/en/information-technology/glossary/remote-access
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): PSI Remote Desktop Service from the European Open Science Cloud https://marketplace.eosc-portal.eu/services/remote-desktop-service?from_recommendation_panel=true&fromc=access-physical-einfrastructures
Interoperability Dimension: Structural IoP
LOST view: Technical view - infrastructure
Interoperability Saliency: Remote Desktop ABB is salient for technical interoperability because it refers to the sharing of a workspace to share or access public administration applications remotely. This contributes to establishing European public services with remote accessibility.
Identifier: http://data.europa.eu/dr8/RemoteDesktopTechnologyService
ABB name: eira:RemoteDesktopTechnologyService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/RemoteDesktopTechnologyService
Interoperability Layer: TechnicalInfrastructure
Definition: Computing Hosting, Networking, and Data Hosting Infrastructure ABB are a Technology Service that enables the functionalities for i) hosting Interoperable European Solutions and ii) providing the necessary networks for operating these solutions.
Source: ISA2 - EIA Action
Source reference: https://digital-strategy.ec.europa.eu/en/news/isa2-interoperability-solutions-european-public-administrations-first-work-programme-adopted
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB):DIGIT Hosting and Networking Infrastructure Service
IoP Dimension: Structural IoP
LOST view: Technical view - Infrastructure
Interoperability saliency: The Computing Hosting, Networking and Data Hosting Infrastructure ABB is a key enabler interoperability enabler (*) for structural interoperability by enabling all the functionalities to host the Interoperable European Solutions (high availability and high-performance hosting infrastructure) and the network that can operate these solutions (a public and private network). Hosting and networking represent the lower level of the technical layer, but to be considered when designing an interoperable solution, as they can create interoperability barriers. Interoperability technical specifications need to be used at this level to ensure interoperability of the levels above.
Identifier: http://data.europa.eu/dr8/ComputingHosting,Networking,andDataHostingInfrastructureTechnologyService
eira:ID: ABB439
ABB name: eira:ComputingHosting,Networking,andDataHostingInfrastructureTechnologyService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2022-31-01
Definition: Domain Name Service ABB is a Technology Service that enables the implementation of a directory which translates numeric IP addresses into Domain Names to identify users on the Internet
Source: LAWINSIDER
Source reference: https://www.lawinsider.com/dictionary/domain-name-service
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): Europe Registry, Europe Registry is a trusted domain expert with over twenty years experience in the domain industry. We have multiple ICANN Accreditations and provide domain registration for country code top level domains (ccTLDs). https://www.europeregistry.com/
Interoperability Dimension: Structural IoP
LOST view: Technical view - infrastructure
Interoperability Saliency: Domain Name Service ABB is salient for semantic interoperability because it implements a catalogue of internet addresses associated with the corresponding names to facilitate accessibility to public administration services.
Identifier: http://data.europa.eu/dr8/DomainNameServiceTechnologyService
ABB name: eira:DomainNameServiceTechnologyService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/DomainNameServiceTechnologyService
Interoperability Layer: TechnicalInfrastructure
Definition: Databriks ABB is a Technology Service that enables the procedures of a collaborative workspace to process large amounts of public administration data
Source: Inspired in Databriks
Source reference: https://docs.databricks.com/introduction/index.html
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): IOStack is an H2020 funded by the European Commission that implemented Databricks as the tool for processing large amounts of data. https://ec.europa.eu/research/participants/documents/downloadPublic?documentIds=080166e5ae65ba9a&appId=PPGMS
Interoperability Dimension: Structural IoP
LOST view: Technical view - infrastructure
Interoperability Saliency: Databriks ABB is salient for semantic interoperability because it permits to break of public administration siloes through the construction of shared spaces to process and analyse data from different sources and domains.
Identifier: http://data.europa.eu/dr8/DatabricksTechnologyService
ABB name: eira:DatabricksTechnologyService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/DatabricksTechnologyService
Interoperability Layer: TechnicalInfrastructure
Definition: Machine Learning ABB is a Technology service that enables the procedures for implementing algorithms and models that can learn from and make predictions on data
Source: European Comision-White paper on AI
Source reference: https://commission.europa.eu/system/files/2020-02/commission-white-paper-artificial-intelligence-feb2020_en.pdf
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): AI Whatch Artificial Intelligence in public administrations. https://publications.jrc.ec.europa.eu/repository/bitstream/JRC120399/jrc120399_misuraca-ai-watch_public-services_30062020_def.pdf
Interoperability Dimension: Structural IoP
LOST view: Technical view - infrastructure
Interoperability Saliency: Machine Learning ABB is salient for semantic interoperability because it refers to the generation of newer insights (knowledge) from public data to generate (i) new curated datasets and/or (ii) new public data assets based on the combination of other public data.
Identifier: http://data.europa.eu/dr8/MachineLearningTechnologyService
ABB name: eira:MachineLearningTechnologyService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/MachineLearningTechnologyService
Interoperability Layer: TechnicalInfrastructure
Definition: Serveless Orchestration ABB is a Technology Service that implements the behaviour of coordinating and managing individual functions are deployed as separate, independent units of code that can be executed in response to specific events or triggers.
Source: inspired in RedHat
Source reference: https://www.redhat.com/en/topics/cloud-native-apps/what-is-serverless
Example: The following implementation is an example of how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): Architecture of Orchestration for serverless computing. https://ec.europa.eu/research/participants/documents/downloadPublic?documentIds=080166e5d0f56561&appId=PPGMS
Interoperability Dimension: Structural IoP
LOST view: Technical view - infrastructure
Interoperability Saliency: Serverless Orchestrator ABB is salient for technical interoperability because it establishes the events and individual functions to combine information from legacy and public administrations service to respond to the applications and stakeholders that consume its information.
Identifier: http://data.europa.eu/dr8/ServerlessOrchestratorTechnologyService
ABB name: eira:ServerlessOrchestratorTechnologyService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/ServerlessOrchestratorTechnologyService
Interoperability Layer: TechnicalInfrastructure
Definition: Analytics ABB is a Technology service that enables the procedures of analysing a great amount of raw data to make conclusions about specific information.
Source: Inspired in Data Act
Source reference: https://digital-strategy.ec.europa.eu/en/policies/data-act
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): Europa Analytics is the corporate service that monitors and evaluates the effectiveness and efficiency of the European Commission's websites on Europa. https://commission.europa.eu/europa-analytics_en
Interoperability Dimension: Structural IoP
LOST view: Technical view - infrastructure
Interoperability Saliency: Analytics ABB is salient for technical and semantic interoperability in because it provides all functionalities to analyze huge amount of information by indicating inputs and outputs for the analytical services. Thus, semantic interoperability between analytical services can be provided as an interlink between processes and establish a common framework to map business processes in public administrations.
Identifier: http://data.europa.eu/dr8/AnalyticsTechnologyService
ABB name: eira:AnalyticsTechnologyService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/AnalyticsTechnologyService
Interoperability Layer: TechnicalInfrastructure
Definition: Web Server ABB is a Technology Service that implements the behaviour of a type of server software that handles HTTP (Hypertext Transfer Protocol) requests sent by clients, typically web browsers, and delivers web content back to the client in response
Source: Inspired in ISA2-EIF
Source reference: https://eur-lex.europa.eu/resource.html?uri=cellar:2c2f2554-0faf-11e7-8a35-01aa75ed71a1.0017.02/DOC_1&format=PDF
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): DIGIT/C Hosting Service - DIGIT/C offers a high availability and high performance hosting infrastructure that is being comprised, among other elements, of back-end web server instances and application servers for hosting and serving both static and dynamic sites. http://ec.europa.eu/ipg/build/infrastructure/index_en.htm
Interoperability Dimension: Structural IoP
LOST view: Technical view - infrastructure
Interoperability Saliency: Streaming Server is salient for semantic technical interoperability because it provides ICT systems to manage data streams related to public digital services. This ABB provides real-time interaction with the data following up streaming open specifications and metadata (if needed).
Identifier: http://data.europa.eu/dr8/WebServerTechnologyService
ABB name: eira:WebServerTechnologyService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/WebServerTechnologyService
Interoperability Layer: TechnicalInfrastructure
Definition: Distributed Blockchain Network ABB is a Technology Service that enables the implementation procedures to manage tokens that may be utilised and/or exchanged, as communicated by the Company to the Token holders from time to time
Source: World Bank
Source reference: https://www.worldbank.org/en/topic/financialsector/brief/blockchain-dlt
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): Oasis Network, The Oasis Network is a Layer 1 decentralized blockchain network designed to be uniquely scalable, privacy-first and versatile. The Network has two main architectural components, the consensus layer and the ParaTime layer: 1. The consensus layer is a scalable, high-throughput, secure, proof-of-stake consensus run by a decentralized set of validator nodes; 2. The ParaTime layer hosts many parallel runtimes (ParaTimes), each representing a replicated compute environment with shared state. https://docs.oasis.io/general/oasis-network/
Interoperability Dimension: Structural IoP
LOST view: Technical view - infrastructure
Interoperability Saliency: Distributed Blockchain Network ABB is salient for technical interoperability because it establishes the infrastructure to share information and also makes the information consistent under distributed data stores.
Identifier: http://data.europa.eu/dr8/DistributedBlockchainNetworkTechnologyService
ABB name: eira:DistributedBlockchainNetworkTechnologyService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/DistributedBlockchainNetworkTechnologyService
Interoperability Layer: TechnicalInfrastructure
Definition: Database Cache Manager ABB is a Technology Service that implements the behaviour of a software system that manages the caching of frequently accessed data in memory
Source: Inspired in the definition provided by relebant database vendors
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): Redis, The open source, in-memory data store used by millions of developers as a database, cache, streaming engine, and message broker. https://redis.io/
Interoperability Dimension: Structural IoP
LOST view: Technical view - infrastructure
Interoperability Saliency: Database Cache Manager ABB is salient for semantic interoperability due to implementing a mechanism to manage data in memory to provide to the public administration consumers efficiently and in a short time response. It also facilitates data sharing and reuse using common data exchange models and serialisations.
Identifier: http://data.europa.eu/dr8/DatabaseCacheManagerTechnologyService
ABB name: eira:DatabaseCacheManagerTechnologyService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/DatabaseCacheManagerTechnologyService
Interoperability Layer: TechnicalInfrastructure
Definition: Management Console ABB is a Technology Service that enables the procedures to elaborate a centralised interface to manage and monitor digital platforms.
Source: Inspired in the definition provided by relebant cloud service organizations.
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): Open e-TrustEx. https://joinup.ec.europa.eu/collection/e-trustex/solution/open-e-trustex/about
Interoperability Dimension: Structural IoP
LOST view: Technical view - infrastructure
Interoperability Saliency: Management Console ABB is salient for technical interoperability due to it contributes to consolidating the management and monitoring of public digital services to ensure their availability according to the service level agreements established.
Identifier: http://data.europa.eu/dr8/ManagementConsoleTechnologyService
ABB name: eira:ManagementConsoleTechnologyService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/ManagementConsoleTechnologyService
Interoperability Layer: TechnicalInfrastructure
Definition: Graph Database manager ABB is a Technology Service that implements the behaviour of a software system that manages and manipulates data stores in the form of nodes, edges, and properties, which are represented as a graph
Source: Inspired in the definition provided by relebant Graph database vendors
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): neo4j Graph Database management. https://neo4j.com/docs/graph-data-science/current/management-ops/
Interoperability Dimension: Structural IoP
LOST view: Technical view - infrastructure
Identifier: http://data.europa.eu/dr8/GraphDatabaseManagerTechnologyService
ABB name: eira:GraphDatabaseManagerTechnologyService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/GraphDatabaseManagerTechnologyService
Interoperability Layer: TechnicalInfrastructure
Definition: Object Oriented Database Manager ABB is a Technology Service that implements the behaviour of a software system that applies concepts of object-oriented programming, and applies them to the management of persistent objects on behalf of multiple users, with capabilities for security, integrity, recovery and contention management
Source: Gartner
Source reference: https://www.gartner.com/en/information-technology/glossary/oodbms-object-oriented-database-management-system
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): PostgreSQL is an open source object-relational database system that has an edge over other relational databases as the software supports user-defined objects and their behaviors including operators, data types, domains, and indexes. This makes the database software more flexible and robust. https://www.postgresql.org/
Interoperability Dimension: Behavioral IoP
LOST view: Technical view - infrastructure
Interoperability Saliency: Object Oriented DatabaseManager ABB is salient for semantic interoperability because it implements data management using object-oriented specifications and their corresponding data representation to share the information with different public administration services.
Identifier: http://data.europa.eu/dr8/Object-OrientedDatabaseManagerTechnologyService
ABB name: eira:Object-OrientedDatabaseManagerTechnologyService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/Object-OrientedDatabaseManagerTechnologyService
Interoperability Layer: TechnicalInfrastructure
Definition: Active Directory ABB is a Technology Service that enables the procedures to work with interconnected, complex and different network resources in a unified manner
Source: Inspired in CAMSS
Source reference: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): OpenLDAP highly flexible, scalable, and focused on providing core directory services to resources that leverage the LDAP protocol. https://www.openldap.org/
Interoperability Dimension: Structural IoP
LOST view: Technical view - infrastructure
Interoperability Saliency: The Active Directory ABB is salient for technical interoperability because it is the store container about the public administration services and information that permit (i) establishing policies for the access and use of public services, (ii) deploying programs inside the public administration, and (iii) holistically manage software updates.
Identifier: http://data.europa.eu/dr8/ActiveDirectoryTechnologyService
ABB name: eira:ActiveDirectoryTechnologyService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/ActiveDirectoryTechnologyService
Interoperability Layer: TechnicalInfrastructure
Definition: File storage ABB is a Technology Service that implements the behaviour of a software tool that refers to the process of storing and organizing digital files in a secure and efficient manner
Source: Inspired in the definition provided by relebant database vendors
Example: The following implementation is an example of how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): GARTNER- Distributed File Systems and Objects Storage Reviews and Ratings. https://www.gartner.com/reviews/market/distributed-file-systems-and-object-storage
Interoperability Dimension: Structural IoP
LOST view: Technical view - infrastructure
Interoperability Saliency: File Storage ABB is salient for technical interoperability because it set up the data integration mechanism based on different files. This kind of file storage permit also ensures data provenance of the information considering file modification and creation.
Identifier: http://data.europa.eu/dr8/FileStorageTechnologyService
ABB name: eira:FileStorageTechnologyService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/FileStorageTechnologyService
Interoperability Layer: TechnicalInfrastructure
Definition: The Granularity of Legral requirements ABB is an Assessment that refers to the degree to which laws and regulations are broken down into specific requirements and standards that must be met.
Source: Scientific Foundations of Digital Governance and Transformation
Source reference: https://books.google.gr/books?id=IB5iEAAAQBAJ&pg=PA298&lpg=PA298&dq=Delegation+of+Powers+Provisioning+Digital+Public+Services&source=bl&ots=jyuzPhj0Q8&sig=ACfU3U1-hD4udfrf3Ye_7Ywly0FATpCu6Q&hl=el&sa=X&ved=2ahUKEwjHhuyQ-KT3AhUEt6QKHTNbCCwQ6AF6BAgPEAM#v=onepage&q=Delegation%20of%20Powers%20Provisioning%20Digital%20Public%20Services&f=false
Example: The following implementation is an example of how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): Study of use Open Source Software in the Public Sector. http://softlibre.unizar.es/manuales/legal/oss-fact-sheet.pdf
Interoperability Dimension: Structural IoP
LOST view: Legal view
Viewpoint: Highlevel viewpoint
Interoperability Saliency: The Granularity on Legal Requirements ABB is salient for governance and legal interoperability because it sets the rules and requirements devoted to i) reuse and elaborate public sector digital services; ii) data sharing rules to enable the exchange of data across different countries.
Identifier: http://data.europa.eu/dr8/GranularityOfLegalRequirementsAssessment
ABB name: eira:GranularityOfLegalRequirementsAssessment
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/GranularityOfLegalRequirementsAssessment
Interoperability Layer: Legal
Definition: Delegation of Powers Provisioning Digital Public Services ABB is an Assessment representing the extent to which the digital public service delivery is delegated to lower public administrative tiers or to private organisations acting on behalf of the public administration.
Source: Scientific Foundations of Digital Governance and Transformation
Source reference: https://books.google.gr/books?id=IB5iEAAAQBAJ&pg=PA298&lpg=PA298&dq=Delegation+of+Powers+Provisioning+Digital+Public+Services&source=bl&ots=jyuzPhj0Q8&sig=ACfU3U1-hD4udfrf3Ye_7Ywly0FATpCu6Q&hl=el&sa=X&ved=2ahUKEwjHhuyQ-KT3AhUEt6QKHTNbCCwQ6AF6BAgPEAM#v=onepage&q=Delegation%20of%20Powers%20Provisioning%20Digital%20Public%20Services&f=false
Example: The following implementation is an example of how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): OECD Designing and Delivering public services in the digital age (https://goingdigital.oecd.org/data/notes/No22_ToolkitNote_DigitalGovernment.pdf)
Interoperability Dimension: Structural IoP
LOST view: Legal view
Viewpoint: Highlevel viewpoint
Interoperability Saliency: The Delegation of Powers provisioning Digital Public Services ABB is salient for the legal interoperability due to it enables (i) the delegation of powers to local authorities to implement rules and metrics to monitor the digital public services; and (ii) the establishment of rules to balance the digital public services consumption.
Identifier: http://data.europa.eu/dr8/DelegationOfPowersProvisioningDigitalPublicServicesAssessment
ABB name: eira:DelegationOfPowersProvisioningDigitalPublicServicesAssessment
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/DelegationOfPowersProvisioningDigitalPublicServicesAssessment
Interoperability Layer: Legal
Definition: Digital Solution Assumption ABB is a Constraint that refers to the factor that limits the realization of the exchange and sharing of data across different platforms
Source: ISA2-EIF
Source reference: https://ec.europa.eu/isa2/eif_en/
LOST view: Enterprise Architecture Framework alignment guidelines view
Identifier: http://data.europa.eu/dr8/DigitalSolutionAssumptionConstraint
ABB name: eira:DigitalSolutionAssumptionConstraint
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2022-01-23
dct:identifier: http://data.europa.eu/dr8/DigitalSolutionAssumptionConstraint
Definition: Interoperable Digital Public Service Implementation Orientation ABB is a Constraint that implements the approach that a digital public service owner has to follow to implement their digital public services.
Source: European Interoperability Framework (EIF)
Source reference: http://eur-lex.europa.eu/resource.html?uri=cellar:2c2f2554-0faf-11e7-8a35-01aa75ed71a1.0017.02/DOC_3&format=PDF
Additional information: Studying the implementation orientation facilitate Member States in understanding the implementation impacts on the interoperability and the functioning of the digital public services from different perspectives.
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): The four implementation orientations identified in IDPSIO, integration, technology, governance, and legal (see the Joinup IDPSIO solution home page: https://joinup.ec.europa.eu/collection/european-interoperability-reference-architecture-eira/solution/egovera/release/v210).
IoP Dimension: Governance IoP
LOST view: Organisational view
Interoperability saliency: Interoperable Digital Public Service Implementation Orientation ABB is salient for governance interoperability because it supports digital public service owners in deciding the approach to follow to implement their digital public services.
Identifier: http://data.europa.eu/dr8/InteroperableDigitalPublicServiceImplementationOrientationConstraint
eira:ID: ABB491
ABB name: eira:InteroperableDigitalPublicServiceImplementationOrientationConstraint
EIRA concept: EIRA_ONTOLOGY_CLASS
Last modification: 2022-12-01
Definition: Public Policy Constraint ABB is a Constraint that imposes one or more restrictions on the way the Public Policy operates or may be realized.
Source: Based on policy-making literature (e.g., Theory of Policy Constraint: https://www.synchronix.com/toc_exploit_subordinate_elevate.htm) as well as the definition of what a constraint is according to Archimate language.
Source reference: https://pubs.opengroup.org/architecture/archimate3-doc/chap06.html
Synonym: Public Policy Restriction
Additional information: Cfr. https://ec.europa.eu/commission/presscorner/detail/en/ip_22_4503 for more information on the Path to the Digital Decade.
Example: The following implementation is an example of how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): Transparency: EIF Transparency Principle refers to: 1. Enabling visibility inside the administrative environment of a public administration. This is about allowing other public administrations, citizens and businesses to view and understand administrative rules, processes, data, services and decision-making. 2. Ensuring availability of interfaces with internal information systems. Public administrations operate a large number of what are often heterogeneous and disparate information systems in support of their internal processes. Interoperability depends on ensuring the availability of interfaces to these systems and the data they handle. In turn, interoperability facilitates reuse of systems and data, and enables these to be integrated into larger systems. 3. Securing the right to the protection of personal data, by respecting the applicable legal framework for the large volumes of personal data of citizens, held and managed by Public administrations.(https://ec.europa.eu/isa2/sites/default/files/eif_brochure_final.pdf)
eira:iopDimension: Governance IoP
LOST view: High Level view
eira:iopSaliency: The Public Policy Constraint ABB is salient for the governance interoperability because it imposes conditions on the implementation of the system (e.g., specific technology that is to be used), a restriction on the implementation process (e.g., time or budget constraints), or a restriction on the functioning of the system (e.g., legal constraints).
Identifier: http://data.europa.eu/dr8/PublicPolicyConstraint
ABB name: eira:PublicPolicyConstraint
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-10-1
dct:identifier: http://data.europa.eu/dr8/PublicPolicyConstraint
Definition: Public Policy Context ABB is a Constraint that describes the background against which policy decisions are made, policy processes take place and stakeholders or actors engage with the policy.
Source: Based on policy-making literature as well as the explanations provided by the European Commission when describing Public Policies.
Source reference: https://onlinelibrary.wiley.com/doi/abs/10.1111/1468-0009.12026
Additional information: Public Policy Context is a specialisation of Public Policy Constraint. As such, Public Policy Context(s) provides the limits for the realisation of goals. In contrast to requirements, a Public Policy Constraint does not prescribe some intended functionality of the system to be realized but might impose restrictions on the implementation of the system (e.g., specific technology that is to be used, such as the usage of open source software), a restriction on the implementation process (e.g., time or budget constraints), or a restriction on the functioning of the system (e.g., legal constraints).
Example: The following implementation is an example of how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): The European Cybersecurity Strategy has won a relevant role in the European IT environment since Ukraine's was started. Cybersecurity attacks have become a regular war method. Therefore, the context for the strength and increasing efforts by the Commission is this singular event. The following link illustrates the state of the art: Russia's war on Ukraine: Timeline of cyber-attacks. https://www.europarl.europa.eu/thinktank/en/document/EPRS_BRI(2022)733549
eira:iopDimension: Governance IoP
LOST view: High Level view
eira:iopSaliency: The Public Policy Context ABB is salient for the governance interoperability because it provides further limits and specifications used for the implementing of legal instruments; e.g., for its in recitals of Regulations, Directives, Implementing Acts and other legal instruments.
Identifier: http://data.europa.eu/dr8/PublicPolicyContextConstraint
ABB name: eira:PublicPolicyContextConstraint
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-10-1
dct:identifier: http://data.europa.eu/dr8/PublicPolicyContextConstraint
Definition: Digital Solution Constraint ABB is a Constraint that refers to the factor that limits the realization of the exchange and sharing of data across different platforms
Source: ISA2-EIF
Source reference: https://ec.europa.eu/isa2/eif_en/
eira:iopDimension: Governance IoP
LOST view: Enterprise Architecture Framework alignment guidelines view
Identifier: http://data.europa.eu/dr8/DigitalSolutionConstraintConstraint
ABB name: eira:DigitalSolutionConstraintConstraint
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2022-01-23
dct:identifier: http://data.europa.eu/dr8/DigitalSolutionConstraintConstraint
Definition: Means for Public Policy Objectives Convergence Assurance and Control ABB is a Constraint formalising the mechanisms that are to be used to assure union or uniformity regarding Public Policy Objectives.
Source: Europarl
Source reference: https://www.europarl.europa.eu/RegData/etudes/IDAN/2018/614502/IPOL_IDA(2018)614502_EN.pdf
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): Policy Risk Management approaches and tools for public policy convergence assurance and control, as suggested in studies like the "Explaining Policy Convergence and Divergence through Policy Paradigm Shifts: A Comparative Analysis of Agricultural Risk Governance in OECD Countries" (https://www.tandfonline.com/doi/full/10.1080/13876988.2019.1674623) or in the abundant literature on Public Policy Convergence (see, for example, "Introduction: Cross-National Policy Convergence: Concepts, Approaches, and Explanatory Factors", https://www.researchgate.net/publication/30015252_Introduction_Cross-National_Policy_Convergence_Concepts_Approaches_and_Explanatory_Factors)
eira:iopDimension: Governance IoP
LOST view: OV-Data Spaces
eira:iopSaliency: Means for Public Policy Objectives Convergence Assurance an Control ABB is relevant for the governance of the interoperability because it provides solution(s) to compare, analyse, measure and correct the gaps between what is actually being provided by the public digital services and what were the intended cross public policy objectives.
Identifier: http://data.europa.eu/dr8/MeansForPublicPolicyObjectivesConvergenceAssuranceAndControlConstraint
ABB name: eira:MeansForPublicPolicyObjectivesConvergenceAssuranceAndControlConstraint
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2022-01-13
dct:identifier: http://data.europa.eu/dr8/MeansForPublicPolicyObjectivesConvergenceAssuranceAndControlConstraint
Definition: The Creation of Interoperable European Solutions Driver represents an external or internal condition that motivates the public organisation to define its goals and implement the changes necessary to create Digital Public Services.
Source: ArchiMate
Source reference: https://pubs.opengroup.org/architecture/archimate3-doc/index.html
IoP Dimension: Structural IoP
LOST view: Interoperability Motivation View
Identifier: http://data.europa.eu/dr8/CreationOfInteroperableEuropeanSolutionsDriver
eira:ID: http://data.europa.eu/dr8/CreationOfInteroperableEuropeanSolutionsDriver
ABB name: eira:CreationOfInteroperableEuropeanSolutionsDriver
Definition: Architecture Decision Record from where you should specialise the ADR SBBs regarding the Vertical Scaling
Source: ISO/IEC/IEEE 42010:2022
Source reference: https://www.iso.org/standard/74393.html
Additional information: Vertical scaling, also known as scaling up or scaling vertically, is a method of increasing the capacity and capabilities of a single server or machine by adding more resources to it. This is typically achieved by upgrading the hardware components, such as increasing the processing power, memory, storage capacity, or network bandwidth of the server.
Example: Title: Vertical Scaling Architecture Decision Record (ADR)
LOST view: Digital Solution Architecture Decisions Catalogue view
Identifier: http://data.europa.eu/dr8/egovera/VerticalScalingGoal
EIRA traceability: eira:DigitalSolutionArchitectureDecisionGoal
ABB name: egovera:VerticalScalingGoal
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-07-06
dct:identifier: ADR-20230606091024769
dct:title: Architecture Decision Record about Vertical Scaling
eira:adr_context: The context explains why we need to make a decision. It also describes the alternatives along with the pros and cons.
eira:adr_decision: The decision describes the justification for why the particular solution was accepted. It has more emphasis on the why rather than the how.
eira:adr_status: [Proposed (under review)|Accepted (approved and ready for implementation)|Superseded (superseded by another decision)]
eira:adr_consecuences: The consequences section contains information about the overall impact of an architectural decision. Every decision has trade-offs. That’s why it’s crucial to include the analysis to provide a clear picture.
Definition: Architecture Decision Record from where you should specialise the ADR SBBs regarding the Use GNU GPL as License
Source: ISO/IEC/IEEE 42010:2022
Source reference: https://www.iso.org/standard/74393.html
Additional information: The decision to use GNU GPL as a license concept is a strategic choice made by companies and organizations that want to promote the use and distribution of open-source software. The GNU GPL license allows users to modify and distribute the software freely if they also make their modifications available under the same license. This creates a collaborative environment where developers can work together to improve the software and build upon each other's work. Additionally, the GNU GPL license ensures that the software remains open-source and free for all to use, preventing any one entity from monopolizing the technology.
Example: Internationalization and Localization:
Decision: Chosen option: "GNU GPL", because this license supports a strong copyleft model.
Rationale: Everything needs to be licensed, otherwise the default copyright laws apply. For instance, in Germany that means users may not alter anything without explicitly asking for permission. For more information see https://help.github.com/articles/licensing-a-repository/.
We want to have all source code related to Operate First to be used without any hassle and as free as possible, so that users can just execute and enjoy the four freedoms.
LOST view: Digital Solution Architecture Decisions Catalogue view
Identifier: http://data.europa.eu/dr8/egovera/UseGNUGPLAsLicenseGoal
EIRA traceability: eira:DigitalSolutionArchitectureDecisionGoal
ABB name: egovera:UseGNUGPLAsLicenseGoal
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-06-15
dct:identifier: ADR-20230515180947412
dct:title: Architecture Decision Record about Use GNU GPL as License
eira:adr_context: The context explains why we need to make a decision. It also describes the alternatives along with the pros and cons.
eira:adr_decision: The decision describes the justification for why the particular solution was accepted. It has more emphasis on the why rather than the how.
eira:adr_status: [Proposed (under review)|Accepted (approved and ready for implementation)|Superseded (superseded by another decision)]
eira:adr_consecuences: The consequences section contains information about the overall impact of an architectural decision. Every decision has trade-offs. That’s why it’s crucial to include the analysis to provide a clear picture.
Definition: Architecture Decision Record from where you should specialise the ADR SBBs regarding the Retention and Data Deletion
Source: ISO/IEC/IEEE 42010:2022
Source reference: https://www.iso.org/standard/74393.html
Additional information: Retention and Data Deletion is a critical concept in IT architecture that deals with the management of data throughout its lifecycle. It involves the decision-making process of how long data should be kept, where it should be stored, and when it should be deleted. The concept is essential for organizations to comply with legal and regulatory requirements, protect sensitive information, and optimize storage resources. The retention and data deletion policy should be well-defined, communicated, and enforced to ensure data is managed effectively and efficiently. The policy should also consider the potential risks associated with data breaches, data loss, and unauthorized access.
Example: Retention and Data Deletion:
Decision: Implementing data retention policies and mechanisms for secure data deletion when no longer required.
Rationale: Data retention and deletion policies ensure compliance with regulations governing the storage and retention of data, minimizing the risk of unauthorized access to obsolete or unnecessary data.
LOST view: Digital Solution Architecture Decisions Catalogue view
Identifier: http://data.europa.eu/dr8/egovera/RetentionAndDataDeletionGoal
EIRA traceability: eira:DigitalSolutionArchitectureDecisionGoal
ABB name: egovera:RetentionAndDataDeletionGoal
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-06-15
dct:identifier: ADR-20230515180947804
dct:title: Architecture Decision Record about Retention and Data Deletion
eira:adr_context: The context explains why we need to make a decision. It also describes the alternatives along with the pros and cons.
eira:adr_decision: The decision describes the justification for why the particular solution was accepted. It has more emphasis on the why rather than the how.
eira:adr_status: [Proposed (under review)|Accepted (approved and ready for implementation)|Superseded (superseded by another decision)]
eira:adr_consecuences: The consequences section contains information about the overall impact of an architectural decision. Every decision has trade-offs. That’s why it’s crucial to include the analysis to provide a clear picture.
Definition: Architecture Decision Record from where you should specialise the ADR SBBs regarding the Data Protection Measures
Source: ISO/IEC/IEEE 42010:2022
Source reference: https://www.iso.org/standard/74393.html
Additional information: Data Protection Measures refer to the set of policies, procedures, and technologies that are implemented to safeguard sensitive information from unauthorized access, use, disclosure, disruption, modification, or destruction. These measures are designed to ensure the confidentiality, integrity, and availability of data, and to comply with regulatory requirements and industry standards. Examples of data protection measures include encryption, access controls, firewalls, intrusion detection and prevention systems, backup and recovery systems, and disaster recovery plans. The selection and implementation of data protection measures depend on the nature and sensitivity of the data, the risks and threats to the data, and the cost and feasibility of the measures.
Example: Data Protection Measures:
Decision: Implementing data encryption at rest and in transit to protect sensitive data.
Rationale: Data encryption helps safeguard sensitive information from unauthorized access, ensuring compliance with data protection regulations and industry best practices.
LOST view: Digital Solution Architecture Decisions Catalogue view
Identifier: http://data.europa.eu/dr8/egovera/DataProtectionMeasuresGoal
EIRA traceability: eira:DigitalSolutionArchitectureDecisionGoal
ABB name: egovera:DataProtectionMeasuresGoal
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-06-15
dct:identifier: ADR-20230515180947498
dct:title: Architecture Decision Record about Data Protection Measures
eira:adr_context: The context explains why we need to make a decision. It also describes the alternatives along with the pros and cons.
eira:adr_decision: The decision describes the justification for why the particular solution was accepted. It has more emphasis on the why rather than the how.
eira:adr_status: [Proposed (under review)|Accepted (approved and ready for implementation)|Superseded (superseded by another decision)]
eira:adr_consecuences: The consequences section contains information about the overall impact of an architectural decision. Every decision has trade-offs. That’s why it’s crucial to include the analysis to provide a clear picture.
Definition: Architecture Decision Record from where you should specialise the ADR SBBs regarding the Semantic Capability
Source: ISO/IEC/IEEE 42010:2022
Source reference: https://www.iso.org/standard/74393.html
Additional information: The Semantic Capability concept in IT architecture refers to the ability of a system or application to understand and interpret the meaning of data and information. This involves the use of semantic technologies such as ontologies, taxonomies, and metadata to provide context and structure to data, enabling better search, retrieval, and analysis. Semantic Capability is important in enabling interoperability between different systems and applications, as well as in supporting advanced analytics and decision-making processes. It is also a key enabler of the semantic interoperability, which aims to make data more accessible and useful by adding meaning and context to it.
Example: Decision: The semantics heterogeneity of Evidence across Data Consumer’s and Data Provider’s is managed
Consequence: New Capability: Evidence Semantic Management, including Semantic Mapping
LOST view: Digital Solution Architecture Decisions Catalogue view
Identifier: http://data.europa.eu/dr8/egovera/SemanticCapabilityGoal
EIRA traceability: eira:DigitalSolutionArchitectureDecisionGoal
ABB name: egovera:SemanticCapabilityGoal
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-06-15
dct:identifier: ADR-20230515180947488
dct:title: Architecture Decision Record about Semantic Capability
eira:adr_context: The context explains why we need to make a decision. It also describes the alternatives along with the pros and cons.
eira:adr_decision: The decision describes the justification for why the particular solution was accepted. It has more emphasis on the why rather than the how.
eira:adr_status: [Proposed (under review)|Accepted (approved and ready for implementation)|Superseded (superseded by another decision)]
eira:adr_consecuences: The consequences section contains information about the overall impact of an architectural decision. Every decision has trade-offs. That’s why it’s crucial to include the analysis to provide a clear picture.
Definition: Architecture Decision Record from where you should specialise the ADR SBBs regarding the Database Sharding
Source: ISO/IEC/IEEE 42010:2022
Source reference: https://www.iso.org/standard/74393.html
Additional information: Database sharding ADR is a decision to choose the technique used in distributed databases to improve scalability and performance. It involves partitioning a large database into smaller, more manageable pieces called shards, which are distributed across multiple servers. Each shard contains a subset of the data, and queries are routed to the appropriate shard based on a predefined sharding key. This allows for faster query processing and reduces the risk of data loss or downtime in the event of a server failure. However, implementing database sharding requires careful planning and coordination to ensure data consistency and availability.
Example: Database Sharding:
Decision: Implementing database sharding to distribute data across multiple database instances.
Rationale: Sharding allows for horizontal scaling of the database by splitting data into smaller partitions and distributing them across multiple database servers, improving performance and accommodating increased data volume.
LOST view: Digital Solution Architecture Decisions Catalogue view
Identifier: http://data.europa.eu/dr8/egovera/DatabaseShardingGoal
EIRA traceability: eira:DigitalSolutionArchitectureDecisionGoal
ABB name: egovera:DatabaseShardingGoal
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-06-15
dct:identifier: ADR-20230515180947693
dct:title: Architecture Decision Record about Database Sharding
eira:adr_context: The context explains why we need to make a decision. It also describes the alternatives along with the pros and cons.
eira:adr_decision: The decision describes the justification for why the particular solution was accepted. It has more emphasis on the why rather than the how.
eira:adr_status: [Proposed (under review)|Accepted (approved and ready for implementation)|Superseded (superseded by another decision)]
eira:adr_consecuences: The consequences section contains information about the overall impact of an architectural decision. Every decision has trade-offs. That’s why it’s crucial to include the analysis to provide a clear picture.
Definition: Architecture Decision Record from where you should specialise the ADR SBBs regarding the Data Notification Deployment
Source: ISO/IEC/IEEE 42010:2022
Source reference: https://www.iso.org/standard/74393.html
Additional information: The Data Notification Deployment ADR is a decision made in IT architecture that involves the deployment of notifications related to data. This concept is used to ensure that users are informed about changes or updates to data that they are interested in. The notifications can be sent via email, SMS, or other communication channels. The purpose of this concept is to improve data management and ensure that users are aware of any changes that may affect their work. This concept is particularly important in organizations that deal with large amounts of data and have many users accessing that data. By deploying data notifications, organizations can improve data security, reduce errors, and increase productivity.
Example: Decision: Data Notification capability is operated by the Data Exchanger (shared resources).
Consequence: Data Subscription required
LOST view: Digital Solution Architecture Decisions Catalogue view
Identifier: http://data.europa.eu/dr8/egovera/DataNotificationDeploymentGoal
EIRA traceability: eira:DigitalSolutionArchitectureDecisionGoal
ABB name: egovera:DataNotificationDeploymentGoal
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-06-15
dct:identifier: ADR-20230515180947459
dct:title: Architecture Decision Record about Data Notification Deployment
eira:adr_context: The context explains why we need to make a decision. It also describes the alternatives along with the pros and cons.
eira:adr_decision: The decision describes the justification for why the particular solution was accepted. It has more emphasis on the why rather than the how.
eira:adr_status: [Proposed (under review)|Accepted (approved and ready for implementation)|Superseded (superseded by another decision)]
eira:adr_consecuences: The consequences section contains information about the overall impact of an architectural decision. Every decision has trade-offs. That’s why it’s crucial to include the analysis to provide a clear picture.
Definition: Architecture Decision Record from where you should specialise the ADR SBBs regarding the Containerization and Orchestration
Source: ISO/IEC/IEEE 42010:2022
Source reference: https://www.iso.org/standard/74393.html
Additional information: Containerization and orchestration are two concepts that are closely related to each other in the field of IT architecture. Containerization refers to the process of packaging an application and its dependencies into a single container that can be easily deployed across different environments. On the other hand, orchestration refers to the process of managing and coordinating multiple containers that are running in a distributed environment. This involves tasks such as scaling containers up or down, monitoring their health, and ensuring that they are communicating with each other correctly.
Example: Containerization and Orchestration:
Decision: Using containerization technologies, such as Docker, and container orchestration platforms, such as Kubernetes, for scalable deployment and management of system components.
Rationale: Containerization provides a lightweight and consistent deployment mechanism, while orchestration platforms enable efficient management, scaling, and load balancing of containerized services.
LOST view: Digital Solution Architecture Decisions Catalogue view
Identifier: http://data.europa.eu/dr8/egovera/ContainerizationAndOrchestrationGoal
EIRA traceability: eira:DigitalSolutionArchitectureDecisionGoal
ABB name: egovera:ContainerizationAndOrchestrationGoal
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-06-15
dct:identifier: ADR-20230515180947565
dct:title: Architecture Decision Record about Containerization and Orchestration
eira:adr_context: The context explains why we need to make a decision. It also describes the alternatives along with the pros and cons.
eira:adr_decision: The decision describes the justification for why the particular solution was accepted. It has more emphasis on the why rather than the how.
eira:adr_status: [Proposed (under review)|Accepted (approved and ready for implementation)|Superseded (superseded by another decision)]
eira:adr_consecuences: The consequences section contains information about the overall impact of an architectural decision. Every decision has trade-offs. That’s why it’s crucial to include the analysis to provide a clear picture.
Definition: Architecture Decision Record from where you should specialise the ADR SBBs regarding the Data Exchange Deployment
Source: ISO/IEC/IEEE 42010:2022
Source reference: https://www.iso.org/standard/74393.html
Additional information: The Data Exchange Deployment ADR is a decision that refers to the process of establishing a system for exchanging data between different applications, systems, or organizations. It involves defining the data exchange requirements, selecting appropriate data exchange protocols, and implementing the necessary infrastructure to support the exchange of data. The goal of Data Exchange Deployment is to ensure that data is shared efficiently and securely, enabling organizations to make better decisions and improve their operations. This concept is particularly important in today's interconnected world, where data is generated and consumed by a wide range of applications and systems.
Example: Decision: Data Exchange Management is operated by the Data Exchanger.
Consequence: Capability assigned to Data Exchanger
LOST view: Digital Solution Architecture Decisions Catalogue view
Identifier: http://data.europa.eu/dr8/egovera/DataExchangeDeploymentGoal
EIRA traceability: eira:DigitalSolutionArchitectureDecisionGoal
ABB name: egovera:DataExchangeDeploymentGoal
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-06-15
dct:identifier: ADR-20230515180947856
dct:title: Architecture Decision Record about Data Exchange Deployment
eira:adr_context: The context explains why we need to make a decision. It also describes the alternatives along with the pros and cons.
eira:adr_decision: The decision describes the justification for why the particular solution was accepted. It has more emphasis on the why rather than the how.
eira:adr_status: [Proposed (under review)|Accepted (approved and ready for implementation)|Superseded (superseded by another decision)]
eira:adr_consecuences: The consequences section contains information about the overall impact of an architectural decision. Every decision has trade-offs. That’s why it’s crucial to include the analysis to provide a clear picture.
Definition: Architecture Decision Record from where you should specialise the ADR SBBs regarding the Application of Service Monitoring Tools
Source: ISO/IEC/IEEE 42010:2022
Source reference: https://www.iso.org/standard/74393.html
Additional information: The application of service monitoring tools is a decision in IT architecture that involves the use of software tools to monitor and manage the performance of IT services. These tools are designed to provide real-time visibility into the performance of IT systems, applications, and infrastructure, allowing IT teams to quickly identify and resolve issues before they impact end-users. Service monitoring tools typically include features such as performance monitoring, event management, and alerting, which enable IT teams to proactively manage and optimize IT services. By using these tools, IT teams can improve service availability, reduce downtime, and enhance the overall user experience. The decision to implement service monitoring tools requires careful consideration of factors such as the organization's IT infrastructure, the complexity of its IT services, and the level of support required. It also involves selecting the right tools that are compatible with the organization's existing IT systems and can provide the necessary level of visibility and control.
Example: Network Optimization:
Decision: Set-up a monitoring tool (like Prometheus or similar).
Rationale: Since there will be multiple services deployed in the Operate First environment (ex. Jupyterhub, Argo, Superset, Observatorium, etc) distributed over various namespaces, we need to be able to monitor them.
LOST view: Digital Solution Architecture Decisions Catalogue view
Identifier: http://data.europa.eu/dr8/egovera/ApplicationOfServiceMonitoringToolsGoal
EIRA traceability: eira:DigitalSolutionArchitectureDecisionGoal
ABB name: egovera:ApplicationOfServiceMonitoringToolsGoal
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-06-15
dct:identifier: ADR-20230515180947825
dct:title: Architecture Decision Record about Application of Service Monitoring Tools
eira:adr_context: The context explains why we need to make a decision. It also describes the alternatives along with the pros and cons.
eira:adr_decision: The decision describes the justification for why the particular solution was accepted. It has more emphasis on the why rather than the how.
eira:adr_status: [Proposed (under review)|Accepted (approved and ready for implementation)|Superseded (superseded by another decision)]
eira:adr_consecuences: The consequences section contains information about the overall impact of an architectural decision. Every decision has trade-offs. That’s why it’s crucial to include the analysis to provide a clear picture.
Definition: Architecture Decision Record from where you should specialise the ADR SBBs regarding the Provisioning Capability Publication
Source: ISO/IEC/IEEE 42010:2022
Source reference: https://www.iso.org/standard/74393.html
Additional information: The Provisioning Capability Publication ADR is a part of IT architecture decision-making process that involves the publication of information about the provisioning capabilities of a system or application. This information can include details about the resources available, such as storage, memory, and processing power, as well as information about the system's performance and availability. The goal of this ADR is to provide users with the information they need to make informed decisions about how to use the system or application, and to ensure that the system is being used in the most efficient and effective way possible. By publishing this information, IT teams can also identify areas where improvements can be made to the system or application and make changes to optimize its performance.
Example: Decision: The Data Provider has the capability to publish to the Data Exchanger its capabilities to provision Data.
Consequence: New capability: Provisioning Capability Publication, part of Provisioning Capability Management
LOST view: Digital Solution Architecture Decisions Catalogue view
Identifier: http://data.europa.eu/dr8/egovera/ProvisioningCapabilityPublicationGoal
EIRA traceability: eira:DigitalSolutionArchitectureDecisionGoal
ABB name: egovera:ProvisioningCapabilityPublicationGoal
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-06-15
dct:identifier: ADR-20230515180947526
dct:title: Architecture Decision Record about Provisioning Capability Publication
eira:adr_context: The context explains why we need to make a decision. It also describes the alternatives along with the pros and cons.
eira:adr_decision: The decision describes the justification for why the particular solution was accepted. It has more emphasis on the why rather than the how.
eira:adr_status: [Proposed (under review)|Accepted (approved and ready for implementation)|Superseded (superseded by another decision)]
eira:adr_consecuences: The consequences section contains information about the overall impact of an architectural decision. Every decision has trade-offs. That’s why it’s crucial to include the analysis to provide a clear picture.
Definition: Architecture Decision Record from where you should specialise the ADR SBBs regarding the Data Subscription Deployment
Source: ISO/IEC/IEEE 42010:2022
Source reference: https://www.iso.org/standard/74393.html
Additional information: The Data Subscription Deployment ADR is a decision made in IT architecture that involves the deployment of data subscriptions to enable real-time data access and analysis. This concept involves the use of data subscriptions to provide a continuous stream of data to applications, which can be used to make informed decisions in real-time. The deployment of data subscriptions can be done through various methods, including API integration, webhooks, and other data integration tools. This concept is particularly useful in industries such as finance, healthcare, and retail, where real-time data analysis is critical for decision-making. The Data Subscription Deployment concept can help organizations to improve their operational efficiency, reduce costs, and enhance customer experience by providing real-time insights into their business operations.
Example: Decision: The Data Exchanger operates the Data Consumer Data Subscription capability
Consequence: --
LOST view: Digital Solution Architecture Decisions Catalogue view
Identifier: http://data.europa.eu/dr8/egovera/DataSubscriptionDeploymentGoal
EIRA traceability: eira:DigitalSolutionArchitectureDecisionGoal
ABB name: egovera:DataSubscriptionDeploymentGoal
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-06-15
dct:identifier: ADR-20230515180947764
dct:title: Architecture Decision Record about Data Subscription Deployment
eira:adr_context: The context explains why we need to make a decision. It also describes the alternatives along with the pros and cons.
eira:adr_decision: The decision describes the justification for why the particular solution was accepted. It has more emphasis on the why rather than the how.
eira:adr_status: [Proposed (under review)|Accepted (approved and ready for implementation)|Superseded (superseded by another decision)]
eira:adr_consecuences: The consequences section contains information about the overall impact of an architectural decision. Every decision has trade-offs. That’s why it’s crucial to include the analysis to provide a clear picture.
Definition: Architecture Decision Record from where you should specialise the ADR SBBs regarding the Cross-Border Semantic Data Management
Source: ISO/IEC/IEEE 42010:2022
Source reference: https://www.iso.org/standard/74393.html
Additional information: Cross-border Semantic Data Management is a concept that refers to the management of data across different countries or regions, with a focus on ensuring that the data is consistent and understandable across all borders. This involves the use of semantic technologies, which allow for the creation of a common language or vocabulary that can be used to describe data in a way that is easily understood by all parties involved. The goal of cross-border semantic data management is to improve the efficiency and effectiveness of data sharing and collaboration across different regions, while also ensuring that the data remains secure and protected. This concept is particularly important in today's globalized economy, where businesses and organizations often need to work together across borders to achieve their goals.
Example: Decision: Data provider discovery and (semantic) data management capabilities are both operated by the same entity, with the role of Cross-Border Data Exchange.
Consequence: Cross-Border Data Management is a new business role.
LOST view: Digital Solution Architecture Decisions Catalogue view
Identifier: http://data.europa.eu/dr8/egovera/Cross-BorderSemanticDataManagementGoal
EIRA traceability: eira:DigitalSolutionArchitectureDecisionGoal
ABB name: egovera:Cross-BorderSemanticDataManagementGoal
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-06-15
dct:identifier: ADR-20230515180947395
dct:title: Architecture Decision Record about Cross-Border Semantic Data Management
eira:adr_context: The context explains why we need to make a decision. It also describes the alternatives along with the pros and cons.
eira:adr_decision: The decision describes the justification for why the particular solution was accepted. It has more emphasis on the why rather than the how.
eira:adr_status: [Proposed (under review)|Accepted (approved and ready for implementation)|Superseded (superseded by another decision)]
eira:adr_consecuences: The consequences section contains information about the overall impact of an architectural decision. Every decision has trade-offs. That’s why it’s crucial to include the analysis to provide a clear picture.
Definition: Architecture Decision Record from where you should specialise the ADR SBBs regarding the Event-Driven Architecture
Source: ISO/IEC/IEEE 42010:2022
Source reference: https://www.iso.org/standard/74393.html
Additional information: In a monolithic architecture, the entire application is built as a single, self-contained unit. All components of the application are tightly coupled, and any changes or updates require modifying the entire system. This architecture is straightforward to develop and deploy but can become complex and difficult to scale or maintain as the application grows.
Example: Title: Monolithic Architecture Decision Record (ADR)
LOST view: Digital Solution Architecture Decisions Catalogue view
Identifier: http://data.europa.eu/dr8/egovera/MonolithicArchitectureGoal
EIRA traceability: eira:DigitalSolutionArchitectureDecisionGoal
ABB name: egovera:MonolithicArchitectureGoal
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-07-06
dct:identifier: ADR-20230606091024763
dct:title: Architecture Decision Record about Monolithic Architecture
eira:adr_context: The context explains why we need to make a decision. It also describes the alternatives along with the pros and cons.
eira:adr_decision: The decision describes the justification for why the particular solution was accepted. It has more emphasis on the why rather than the how.
eira:adr_status: [Proposed (under review)|Accepted (approved and ready for implementation)|Superseded (superseded by another decision)]
eira:adr_consecuences: The consequences section contains information about the overall impact of an architectural decision. Every decision has trade-offs. That’s why it’s crucial to include the analysis to provide a clear picture.
Definition: Architecture Decision Record from where you should specialise the ADR SBBs regarding the Compliance Monitoring and Auditing
Source: ISO/IEC/IEEE 42010:2022
Source reference: https://www.iso.org/standard/74393.html
Additional information: Compliance monitoring and auditing is a concept in IT architecture that ensures that an organization's IT systems and processes comply with relevant laws, regulations, and industry standards. This concept involves the continuous monitoring of IT systems and processes to identify any potential compliance issues and the implementation of corrective actions to address them. Compliance monitoring and auditing also involves regular audits to assess the effectiveness of an organization's compliance program and identify areas for improvement. By implementing a robust compliance monitoring and auditing program, organizations can ensure that they are operating within legal and regulatory boundaries, protecting their reputation, and avoiding costly fines and penalties.
Example: Compliance Monitoring and Auditing:
Decision: Implementing mechanisms for continuous compliance monitoring, internal auditing, and vulnerability assessments.
Rationale: Regular monitoring, auditing, and vulnerability assessments help identify compliance gaps, ensure ongoing adherence to regulations, and proactively address potential security risks.
LOST view: Digital Solution Architecture Decisions Catalogue view
Identifier: http://data.europa.eu/dr8/egovera/ComplianceMonitoringAndAuditingGoal
EIRA traceability: eira:DigitalSolutionArchitectureDecisionGoal
ABB name: egovera:ComplianceMonitoringAndAuditingGoal
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-06-15
dct:identifier: ADR-20230515180947604
dct:title: Architecture Decision Record about Compliance Monitoring and Auditing
eira:adr_context: The context explains why we need to make a decision. It also describes the alternatives along with the pros and cons.
eira:adr_decision: The decision describes the justification for why the particular solution was accepted. It has more emphasis on the why rather than the how.
eira:adr_status: [Proposed (under review)|Accepted (approved and ready for implementation)|Superseded (superseded by another decision)]
eira:adr_consecuences: The consequences section contains information about the overall impact of an architectural decision. Every decision has trade-offs. That’s why it’s crucial to include the analysis to provide a clear picture.
Definition: Architecture Decision Record from where you should specialise the ADR SBBs regarding the Scalability for Growth
Source: ISO/IEC/IEEE 42010:2022
Source reference: https://www.iso.org/standard/74393.html
Additional information: Scalability for Growth is a decision that refers to the ability of a system or application to handle an increasing amount of workload or traffic without compromising its performance or stability. This concept is essential for businesses that are looking to expand their operations and need to ensure that their IT infrastructure can support their growth. Scalability can be achieved through various techniques such as horizontal scaling, vertical scaling, load balancing, and caching. By designing an IT architecture that is scalable, businesses can ensure that their systems can handle increased demand and provide a seamless user experience.
Example: Scalability for Growth:
Decision: Designing the software system with scalability in mind to support future business growth.
Rationale: Scalability ensures that the system can handle increasing user demands, accommodate higher data volumes, and support business expansion without significant re-architecture or performance issues.
LOST view: Digital Solution Architecture Decisions Catalogue view
Identifier: http://data.europa.eu/dr8/egovera/ScalabilityForGrowthGoal
EIRA traceability: eira:DigitalSolutionArchitectureDecisionGoal
ABB name: egovera:ScalabilityForGrowthGoal
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-06-15
dct:identifier: ADR-20230515180947555
dct:title: Architecture Decision Record about Scalability for Growth
eira:adr_context: The context explains why we need to make a decision. It also describes the alternatives along with the pros and cons.
eira:adr_decision: The decision describes the justification for why the particular solution was accepted. It has more emphasis on the why rather than the how.
eira:adr_status: [Proposed (under review)|Accepted (approved and ready for implementation)|Superseded (superseded by another decision)]
eira:adr_consecuences: The consequences section contains information about the overall impact of an architectural decision. Every decision has trade-offs. That’s why it’s crucial to include the analysis to provide a clear picture.
Definition: Architecture Decision Record from where you should specialise the ADR SBBs regarding the Operability
Source: ISO/IEC/IEEE 42010:2022
Source reference: https://www.iso.org/standard/74393.html
Additional information: operability refers to the ease with which users can operate and interact with a software system to achieve their desired goals efficiently and effectively. It focuses on designing interfaces, workflows, and interactions that facilitate user understanding, control, and seamless navigation within the system.
Example: Title: Operability Architecture Decision Record (ADR)
LOST view: Digital Solution Architecture Decisions Catalogue view
Identifier: http://data.europa.eu/dr8/egovera/OperabilityGoal
EIRA traceability: eira:DigitalSolutionArchitectureDecisionGoal
ABB name: egovera:OperabilityGoal
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-07-06
dct:identifier: ADR-20230606091024733
dct:title: Architecture Decision Record about Operability
eira:adr_context: The context explains why we need to make a decision. It also describes the alternatives along with the pros and cons.
eira:adr_decision: The decision describes the justification for why the particular solution was accepted. It has more emphasis on the why rather than the how.
eira:adr_status: [Proposed (under review)|Accepted (approved and ready for implementation)|Superseded (superseded by another decision)]
eira:adr_consecuences: The consequences section contains information about the overall impact of an architectural decision. Every decision has trade-offs. That’s why it’s crucial to include the analysis to provide a clear picture.
Definition: Architecture Decision Record from where you should specialise the ADR SBBs regarding the Integration Thrid-Party Systems
Source: ISO/IEC/IEEE 42010:2022
Source reference: https://www.iso.org/standard/74393.html
Additional information: Integration of third-party systems is a decision that involves the integration of external systems with the organization's existing IT infrastructure. This decision is essential to ensure that the organization's systems can communicate and share data with external systems, such as vendors, partners, and customers. The integration of third-party systems can improve the efficiency of business processes, reduce costs, and enhance the overall customer experience. However, it also requires careful planning and consideration of security, data privacy, and compliance requirements. The IT architecture team must evaluate the compatibility of the third-party systems with the existing infrastructure, assess the risks associated with the integration, and develop a robust integration strategy that aligns with the organization's business goals and objectives.
Example: Integration with Third-Party Systems:
Decision: Integrating the software system with popular customer relationship management (CRM) platforms.
Rationale: Integrating with widely used CRM systems allows for seamless data exchange, better customer insights, and improved customer relationship management for the organization.
LOST view: Digital Solution Architecture Decisions Catalogue view
Identifier: http://data.europa.eu/dr8/egovera/IntegrationThrid-PartySystemsGoal
EIRA traceability: eira:DigitalSolutionArchitectureDecisionGoal
ABB name: egovera:IntegrationThrid-PartySystemsGoal
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-06-15
dct:identifier: ADR-20230515180947744
dct:title: Architecture Decision Record about Integration Thrid-Party Systems
eira:adr_context: The context explains why we need to make a decision. It also describes the alternatives along with the pros and cons.
eira:adr_decision: The decision describes the justification for why the particular solution was accepted. It has more emphasis on the why rather than the how.
eira:adr_status: [Proposed (under review)|Accepted (approved and ready for implementation)|Superseded (superseded by another decision)]
eira:adr_consecuences: The consequences section contains information about the overall impact of an architectural decision. Every decision has trade-offs. That’s why it’s crucial to include the analysis to provide a clear picture.
Definition: Architecture Decision Record from where you should specialise the ADR SBBs regarding the Data Exchanger Operations
Source: ISO/IEC/IEEE 42010:2022
Source reference: https://www.iso.org/standard/74393.html
Additional information: The Data Exchanger Operations concept refers to the process of exchanging data between different systems or applications within an organization. This can involve transferring data from one database to another, integrating data from multiple sources, or sharing data between different departments or teams. The goal of Data Exchanger Operations is to ensure that data is accurate, up-to-date, and accessible to those who need it, while also maintaining data security and compliance with relevant regulations. This concept is an important part of IT architecture, as it helps to ensure that data is effectively managed and utilized throughout an organization.
Example: Decision: The Data Exchanger role is operated by a separate entity than Data Consumer and Data Provider.
Consequence: New entity potentially operating the Data Exchange responsibilities for both Data Consumers and Data Providers
LOST view: Digital Solution Architecture Decisions Catalogue view
Identifier: http://data.europa.eu/dr8/egovera/DataExchangerOperationsGoal
EIRA traceability: eira:DigitalSolutionArchitectureDecisionGoal
ABB name: egovera:DataExchangerOperationsGoal
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-06-15
dct:identifier: ADR-20230515180947517
dct:title: Architecture Decision Record about Data Exchanger Operations
eira:adr_context: The context explains why we need to make a decision. It also describes the alternatives along with the pros and cons.
eira:adr_decision: The decision describes the justification for why the particular solution was accepted. It has more emphasis on the why rather than the how.
eira:adr_status: [Proposed (under review)|Accepted (approved and ready for implementation)|Superseded (superseded by another decision)]
eira:adr_consecuences: The consequences section contains information about the overall impact of an architectural decision. Every decision has trade-offs. That’s why it’s crucial to include the analysis to provide a clear picture.
Definition: Architecture Decision Record from where you should specialise the ADR SBBs regarding the Data Subscription Capability
Source: ISO/IEC/IEEE 42010:2022
Source reference: https://www.iso.org/standard/74393.html
Additional information: The Data Subscription Capability ADR is a decision made in IT architecture that allows users to subscribe to specific data sets or streams. This capability enables users to receive real-time updates and notifications when new data is available, without having to constantly check for updates manually. This concept is particularly useful for businesses that rely on real-time data for decision-making, such as financial institutions or stock traders. By subscribing to specific data sets, users can stay informed and make informed decisions quickly and efficiently. Additionally, the Data Subscription Capability ADR can help reduce data overload by allowing users to filter out irrelevant data and focus on the information that is most important to them.
Example: Decision: The Data Consumer controls the notification through a subscription to Data changes
Consequence: New capability: Data Consumer Data Subscription
LOST view: Digital Solution Architecture Decisions Catalogue view
Identifier: http://data.europa.eu/dr8/egovera/DataSubscriptionCapabilityGoal
EIRA traceability: eira:DigitalSolutionArchitectureDecisionGoal
ABB name: egovera:DataSubscriptionCapabilityGoal
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-06-15
dct:identifier: ADR-20230515180947846
dct:title: Architecture Decision Record about Data Subscription Capability
eira:adr_context: The context explains why we need to make a decision. It also describes the alternatives along with the pros and cons.
eira:adr_decision: The decision describes the justification for why the particular solution was accepted. It has more emphasis on the why rather than the how.
eira:adr_status: [Proposed (under review)|Accepted (approved and ready for implementation)|Superseded (superseded by another decision)]
eira:adr_consecuences: The consequences section contains information about the overall impact of an architectural decision. Every decision has trade-offs. That’s why it’s crucial to include the analysis to provide a clear picture.
DEFINITION:
Achieve Organisational Interoperability ABB is Goal. For the purpose of the EIF, interoperability is the ability of organisations to interact towards mutually beneficial goals, involving the sharing of information and knowledge between these organisations, through the business processes they support, by means of the exchange of data between their ICT systems.
The interoperability model which is applicable to all digital public services and may also be considered as an integral element of the interoperability-by-design paradigm. It includes: four layers of interoperability: legal, organisational, semantic and technical.
Organisational interoperability refers to the way in which public administrations align their business processes, responsibilities and expectations to achieve commonly agreed and mutually beneficial goals. In practice, organisational interoperability means documenting and integrating or aligning business processes and relevant information exchanged. Organisational interoperability also aims to meet the requirements of the user community by making services available, easily identifiable, accessible and user-focused.
Source: EIF
(https://ec.europa.eu/isa2/sites/isa/files/eif_brochure_final.pdf)
EXAMPLES:
The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB):
Definition: Architecture Decision Record from where you should specialise the ADR SBBs regarding the Internazionalization and Localization
Source: ISO/IEC/IEEE 42010:2022
Source reference: https://www.iso.org/standard/74393.html
Additional information: The decision of internationalization and localization in IT architecture refers to the process of designing software applications that can be adapted to different languages, cultures, and regions. Internationalization involves creating software that can handle different character sets, date and time formats, and other cultural differences. Localization involves adapting the software to a specific language and culture, including translating text, adjusting graphics, and modifying functionality to meet local requirements. This concept is important for companies that operate in multiple countries and need to provide software that can be used by people with different backgrounds and languages.
Example: Internationalization and Localization:
Decision: Building support for multiple languages and cultural adaptations into the software system.
Rationale: Internationalization and localization enable the organization to reach a broader global market, cater to diverse customer preferences, and provide a localized user experience, leading to increased customer satisfaction and market penetration.
LOST view: Digital Solution Architecture Decisions Catalogue view
Identifier: http://data.europa.eu/dr8/egovera/InternazionalizationAndLocalizationGoal
EIRA traceability: eira:DigitalSolutionArchitectureDecisionGoal
ABB name: egovera:InternazionalizationAndLocalizationGoal
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-06-15
dct:identifier: ADR-20230515180947623
dct:title: Architecture Decision Record about Internazionalization and Localization
eira:adr_context: The context explains why we need to make a decision. It also describes the alternatives along with the pros and cons.
eira:adr_decision: The decision describes the justification for why the particular solution was accepted. It has more emphasis on the why rather than the how.
eira:adr_status: [Proposed (under review)|Accepted (approved and ready for implementation)|Superseded (superseded by another decision)]
eira:adr_consecuences: The consequences section contains information about the overall impact of an architectural decision. Every decision has trade-offs. That’s why it’s crucial to include the analysis to provide a clear picture.
Definition: Architecture Decision Record from where you should specialise the ADR SBBs regarding the Access Control Policy
Source: ISO/IEC/IEEE 42010:2022
Source reference: https://www.iso.org/standard/74393.html
Additional information: Access Control Policy is a critical concept in IT architecture that defines the rules and guidelines for controlling access to resources and data within an organization's network. It outlines the procedures and protocols that must be followed to ensure that only authorized users can access sensitive information and resources. The policy includes guidelines for user authentication, authorization, and access management, and it helps organizations to maintain the confidentiality, integrity, and availability of their data. The Access Control Policy is a crucial component of any IT security program, and it is essential for protecting against unauthorized access, data breaches, and cyber attacks.
Example: Access Control Policies:
Decision: Enforcing role-based access control (RBAC) and implementing strict access control policies for government systems.
Rationale: RBAC provides a structured approach to managing user access based on predefined roles and responsibilities, reducing the risk of unauthorized access to sensitive information.
LOST view: Digital Solution Architecture Decisions Catalogue view
Identifier: http://data.europa.eu/dr8/egovera/AccessControlPolicyGoal
EIRA traceability: eira:DigitalSolutionArchitectureDecisionGoal
ABB name: egovera:AccessControlPolicyGoal
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-06-15
dct:identifier: ADR-20230515180947653
dct:title: Architecture Decision Record about Access Control Policy
eira:adr_context: The context explains why we need to make a decision. It also describes the alternatives along with the pros and cons.
eira:adr_decision: The decision describes the justification for why the particular solution was accepted. It has more emphasis on the why rather than the how.
eira:adr_status: [Proposed (under review)|Accepted (approved and ready for implementation)|Superseded (superseded by another decision)]
eira:adr_consecuences: The consequences section contains information about the overall impact of an architectural decision. Every decision has trade-offs. That’s why it’s crucial to include the analysis to provide a clear picture.
Definition: Architecture Decision Record from where you should specialise the ADR SBBs regarding the Managing Self-Description Schemas in the Federated Catalogue
Source: ISO/IEC/IEEE 42010:2022
Source reference: https://www.iso.org/standard/74393.html
Additional information: The concept of Managing Self-description Schemas in the Federated Catalogue involves the creation and management of metadata that describes the data and services available in a federated environment. This metadata is used to enable discovery, understanding, and use of the data and services by users and applications. The self-description schemas provide a standardized way of describing the data and services, which makes it easier for users to find and use them. The federated catalogue is a central repository that stores the metadata and provides a search interface for users to discover the data and services. Effective management of self-description schemas in the federated catalogue is essential for ensuring that the data and services are discoverable, understandable, and usable by users and applications.
Example: Decision: Self-Descriptions refer to one or several schemas via a "isA" relation.
Every schema consists of classes and classes define attributes and relations to other Self-Descriptions.
Only attributes from a class can be used for the Self-Descriptions.
The Self-Description classes form an extensible inheritance hierarchy.
For example geo-location for some Nodes.
The Self-Description classes are versioned according to the Semantic Versioning conventions.
GAIA-X provides and maintains a set of core Self-Description classes.
The schema hierarchy can be extended with specialized classes, for example for a domain-specific ecosystem.
GAIA-X defines requirements and processes to accept and distribute new Self-Description classes and updates thereof.
- Option 1: Central repo by the GAIA-X Foundation for schemas
- Option 2: Ecosystems / private catalogues can have additional schema sources
RDF and SHACL are selected as technologies for schema description and enforcement.
- RDF: Data model "behind" JSON-LD
- SHACL: Validation of RDF against a schema independently from the serialization technology
Rationale: For the purpose of validating Self-Descriptions, the Federated Catalogue needs to know the Schema to validate against.
Gaia-X develops an extensible hierarchy of Schemas that define the terms used in Self-Descriptions.
Some Schemas are standardized by the Gaia-X AISBL and must be supported by any Catalogue, but it should be possible to create additional ones specific to an application domain, an Ecosystem, Participants in it, or Assets offered by these Participants.
Schemas have the same format as Self-Descriptions, i.e., they are graphs in the RDF data model, serialized as JSON-LD.
A Schema may define terms (classes, their attributes, and their relationships to other classes) in an Ontology.
If it does, it must also define Shapes to validate instances of the Ontology against.
A Schema may also introduce a Controlled Vocabulary of attribute values intended to be reused.
LOST view: Digital Solution Architecture Decisions Catalogue view
Identifier: http://data.europa.eu/dr8/egovera/ManagingSelf-DescriptionSchemasInTheFederatedCatalogueGoal
EIRA traceability: eira:DigitalSolutionArchitectureDecisionGoal
ABB name: egovera:ManagingSelf-DescriptionSchemasInTheFederatedCatalogueGoal
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-06-15
dct:identifier: ADR-20230515180947835
dct:title: Architecture Decision Record about Managing Self-Description Schemas in the Federated Catalogue
eira:adr_context: The context explains why we need to make a decision. It also describes the alternatives along with the pros and cons.
eira:adr_decision: The decision describes the justification for why the particular solution was accepted. It has more emphasis on the why rather than the how.
eira:adr_status: [Proposed (under review)|Accepted (approved and ready for implementation)|Superseded (superseded by another decision)]
eira:adr_consecuences: The consequences section contains information about the overall impact of an architectural decision. Every decision has trade-offs. That’s why it’s crucial to include the analysis to provide a clear picture.
Definition: Architecture Decision Record from where you should specialise the ADR SBBs regarding the Big-Data Architecture
Source: ISO/IEC/IEEE 42010:2022
Source reference: https://www.iso.org/standard/74393.html
Additional information: Big Data Architecture is a framework or blueprint that outlines the design, components, and processes required to handle and analyze large volumes of data. It encompasses the infrastructure, tools, and methodologies used to capture, store, process, and analyze diverse and complex data sets in a scalable and efficient manner.
Example: Title: Big Data Architecture Decision Record (ADR)
LOST view: Digital Solution Architecture Decisions Catalogue view
Identifier: http://data.europa.eu/dr8/egovera/Big-DataArchitectureGoal
EIRA traceability: eira:DigitalSolutionArchitectureDecisionGoal
ABB name: egovera:Big-DataArchitectureGoal
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-20
dct:identifier: http://data.europa.eu/dr8/egovera/Big-DataArchitectureGoal
dct:title: Architecture Decision Record about Big-Data Architecture
eira:adr_context: The context explains why we need to make a decision. It also describes the alternatives along with the pros and cons.
eira:adr_decision: The decision describes the justification for why the particular solution was accepted. It has more emphasis on the why rather than the how.
eira:adr_status: [Proposed (under review)|Accepted (approved and ready for implementation)|Superseded (superseded by another decision)]
eira:adr_consecuences: The consequences section contains information about the overall impact of an architectural decision. Every decision has trade-offs. That’s why it’s crucial to include the analysis to provide a clear picture.
Definition: Architecture Decision Record from where you should specialise the ADR SBBs regarding the Security Incident Response Plan
Source: ISO/IEC/IEEE 42010:2022
Source reference: https://www.iso.org/standard/74393.html
Additional information: The Security Incident Response Plan is a concept that outlines the procedures and protocols that must be followed in the event of a security breach or incident. The plan typically includes steps for identifying the incident, containing the damage, investigating the cause, and restoring normal operations. It also includes guidelines for communication with stakeholders, such as customers, employees, and regulatory bodies. A well-designed Security Incident Response Plan can help minimize the impact of a security incident and reduce the risk of future incidents.
Example: Security Incident Response Plan:
Decision: Establishing a security incident response plan to handle and respond to security breaches or incidents promptly and effectively.
Rationale: A well-defined incident response plan helps mitigate the impact of security incidents, comply with incident reporting requirements, and facilitate the recovery and restoration of systems and data.
LOST view: Digital Solution Architecture Decisions Catalogue view
Identifier: http://data.europa.eu/dr8/egovera/SecurityIncidentResponsePlanGoal
EIRA traceability: eira:DigitalSolutionArchitectureDecisionGoal
ABB name: egovera:SecurityIncidentResponsePlanGoal
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-06-15
dct:identifier: ADR-20230515180947794
dct:title: Architecture Decision Record about Security Incident Response Plan
eira:adr_context: The context explains why we need to make a decision. It also describes the alternatives along with the pros and cons.
eira:adr_decision: The decision describes the justification for why the particular solution was accepted. It has more emphasis on the why rather than the how.
eira:adr_status: [Proposed (under review)|Accepted (approved and ready for implementation)|Superseded (superseded by another decision)]
eira:adr_consecuences: The consequences section contains information about the overall impact of an architectural decision. Every decision has trade-offs. That’s why it’s crucial to include the analysis to provide a clear picture.
Definition: Architecture Decision Record from where you should specialise the ADR SBBs regarding the Documentation
Source: ISO/IEC/IEEE 42010:2022
Source reference: https://www.iso.org/standard/74393.html
Additional information: This ADR documents decisions regarding the documentation practices for the software system. It includes decisions on the types of documentation to be maintained (e.g., system architecture, API documentation, user guides), tools to be used for documentation, and guidelines for keeping documentation up to date.
Example: Title: Documentation Architecture Decision Record (ADR)
LOST view: Digital Solution Architecture Decisions Catalogue view
Identifier: http://data.europa.eu/dr8/egovera/DocumentationGoal
EIRA traceability: eira:DigitalSolutionArchitectureDecisionGoal
ABB name: egovera:DocumentationGoal
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-07-06
dct:identifier: ADR-20230606091024761
dct:title: Architecture Decision Record about Documentation
eira:adr_context: The context explains why we need to make a decision. It also describes the alternatives along with the pros and cons.
eira:adr_decision: The decision describes the justification for why the particular solution was accepted. It has more emphasis on the why rather than the how.
eira:adr_status: [Proposed (under review)|Accepted (approved and ready for implementation)|Superseded (superseded by another decision)]
eira:adr_consecuences: The consequences section contains information about the overall impact of an architectural decision. Every decision has trade-offs. That’s why it’s crucial to include the analysis to provide a clear picture.
Definition: An Architectural Decision Record (ADR) is a document that captures the key decisions made during the architectural design and development of a software system. It is used to record the rationale, alternatives considered, and trade-offs made during the decision-making process, as well as the context and implications of each decision.
Source: Architectural Decision Records
Source reference: https://adr.github.io/
IoP Dimension: Governance IoP
LOST view: Interoperability Motivation View
Identifier: http://data.europa.eu/dr8/DigitalSolutionArchitectureDecisionGoal
eira:ID: http://data.europa.eu/dr8/DigitalSolutionArchitectureDecisionGoal
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 24-04-2023
dct:identifier: A unique increasing number and date that usually follows the ADR-nnnn pattern to help sort them from old to new (ADR-20230412180800). The format to use is ADR-[YYYYMMDDHHmmSS].
dct:title: The title contains a short phrase describing the architectural decisions.
dct:description: The description contains a full description of the architectural decisions.
adr:context: The context explains why we need to make a decision. It also describes the alternatives along with the pros and cons.
adr:decision: The decision describes the justification for why the particular solution was accepted. It has more emphasis on the why rather than the how.
adr:status: [Proposed (under review)|Accepted (approved and ready for implementation)|Superseded (superseded by another decision)]
adr:consecuences: The consequences section contains information about the overall impact of an architectural decision. Every decision has trade-offs. That’s why it’s crucial to include the analysis to provide a clear picture.
Definition: Architecture Decision Record from where you should specialise the ADR SBBs regarding the Security Incident Response
Source: ISO/IEC/IEEE 42010:2022
Source reference: https://www.iso.org/standard/74393.html
Additional information: The Security Incident Response concept involves the development of a comprehensive plan to detect, respond to, and recover from security incidents that may occur within an organization's information systems. The plan should include procedures for identifying and assessing potential threats, as well as protocols for containing and mitigating the impact of any incidents that do occur. The goal of the Security Incident Response concept is to minimize the risk of data loss, system downtime, and other negative consequences that can result from security breaches. Effective implementation of this concept requires ongoing monitoring and testing of security measures, as well as regular training and awareness programs for employees.
Example: Security Incident Response:
Decision: Establishing an incident response plan to handle security breaches and incidents.
Rationale: Having a well-defined incident response plan enables a quick and coordinated response to security incidents, minimizing potential damage, and facilitating the recovery and restoration of normal operations.
LOST view: Digital Solution Architecture Decisions Catalogue view
Identifier: http://data.europa.eu/dr8/egovera/SecurityIncidentResponseGoal
EIRA traceability: eira:DigitalSolutionArchitectureDecisionGoal
ABB name: egovera:SecurityIncidentResponseGoal
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-06-15
dct:identifier: ADR-20230515180947632
dct:title: Architecture Decision Record about Security Incident Response
eira:adr_context: The context explains why we need to make a decision. It also describes the alternatives along with the pros and cons.
eira:adr_decision: The decision describes the justification for why the particular solution was accepted. It has more emphasis on the why rather than the how.
eira:adr_status: [Proposed (under review)|Accepted (approved and ready for implementation)|Superseded (superseded by another decision)]
eira:adr_consecuences: The consequences section contains information about the overall impact of an architectural decision. Every decision has trade-offs. That’s why it’s crucial to include the analysis to provide a clear picture.
Definition: Architecture Decision Record from where you should specialise the ADR SBBs regarding the Learning
Source: ISO/IEC/IEEE 42010:2022
Source reference: https://www.iso.org/standard/74393.html
Additional information: User learning, in the context of usability, refers to the process by which users acquire the knowledge and skills necessary to effectively and efficiently interact with a software system. It involves understanding the system's functionality, features, and workflows, as well as learning how to navigate interfaces and perform tasks.
Example: Title: User Learning Architecture Decision Record (ADR)
LOST view: Digital Solution Architecture Decisions Catalogue view
Identifier: http://data.europa.eu/dr8/egovera/LearningGoal
EIRA traceability: eira:DigitalSolutionArchitectureDecisionGoal
ABB name: egovera:LearningGoal
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-07-06
dct:identifier: ADR-20230606091024693
dct:title: Architecture Decision Record about Learning
eira:adr_context: The context explains why we need to make a decision. It also describes the alternatives along with the pros and cons.
eira:adr_decision: The decision describes the justification for why the particular solution was accepted. It has more emphasis on the why rather than the how.
eira:adr_status: [Proposed (under review)|Accepted (approved and ready for implementation)|Superseded (superseded by another decision)]
eira:adr_consecuences: The consequences section contains information about the overall impact of an architectural decision. Every decision has trade-offs. That’s why it’s crucial to include the analysis to provide a clear picture.
Definition: Interoperability Strategy ABB is a Goal that enables the ability of disparate and diverse organisations to interact towards mutually beneficial and agreed common goals, involving the sharing of information and knowledge between the organisations, through the business processes they support, by means of the exchange of data between their respective ICT systems.
Source: EIF
Source reference: http://eur-lex.europa.eu/resource.html?uri=cellar:2c2f2554-0faf-11e7-8a35-01aa75ed71a1.0017.02/DOC_3&format=PDF
Example: The following implementation is an example of how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): The vision laying down in the Interoperable Europe Act (see recitals) and additional information in https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A52022PC0720, and in https://www.europarl.europa.eu/legislative-train/theme-a-europe-fit-for-the-digital-age/file-eu-digital-interoperabilioty-strategy.
IoP Dimension: Governance IoP
LOST view: Organisational view
Interoperability saliency: The Interoperability Strategy ABB is salient for governance interoperability because it helps governments and public administrations to cooperate, share information and deliver public services seamlessly across borders, sectors and organizational boundaries. Thus, for example, the Interoperable Europe Act supports public sector innovation and public-private 'GovTech' projects. It sets up a new cooperation framework for interoperability in the public sector.
Identifier: http://data.europa.eu/dr8/InteroperabilityStrategyGoal
eira:ID: ABB489
ABB name: eira:InteroperabilityStrategyGoal
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2022-12-01
Definition: Architecture Decision Record from where you should specialise the ADR SBBs regarding the Role-Based Access Control (RBAC)
Source: ISO/IEC/IEEE 42010:2022
Source reference: https://www.iso.org/standard/74393.html
Additional information: Role-Based Access Control (RBAC) is a concept in IT architecture that provides a method for controlling access to resources based on the roles of individual users within an organization. This approach is designed to simplify the process of managing access to sensitive data and systems by assigning permissions based on job responsibilities rather than individual identities. With RBAC, administrators can create roles that define specific access privileges and then assign those roles to users based on their job functions. This helps to ensure that users only have access to the resources they need to perform their duties, reducing the risk of unauthorized access and data breaches. RBAC is widely used in enterprise environments and is considered a best practice for access control in IT security.
Example: Role-Based Access Control (RBAC):
Decision: Implementing RBAC to enforce fine-grained access controls based on user roles and permissions.
Rationale: RBAC provides a structured and manageable approach to access control, ensuring that users have appropriate privileges based on their roles within the system, minimizing the risk of unauthorized actions.
LOST view: Digital Solution Architecture Decisions Catalogue view
Identifier: http://data.europa.eu/dr8/egovera/Role-BasedAccessControlGoal
EIRA traceability: eira:DigitalSolutionArchitectureDecisionGoal
ABB name: egovera:Role-BasedAccessControlGoal
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-06-15
dct:identifier: ADR-20230515180947403
dct:title: Architecture Decision Record about Role-Based Access Control (RBAC)
eira:adr_context: The context explains why we need to make a decision. It also describes the alternatives along with the pros and cons.
eira:adr_decision: The decision describes the justification for why the particular solution was accepted. It has more emphasis on the why rather than the how.
eira:adr_status: [Proposed (under review)|Accepted (approved and ready for implementation)|Superseded (superseded by another decision)]
eira:adr_consecuences: The consequences section contains information about the overall impact of an architectural decision. Every decision has trade-offs. That’s why it’s crucial to include the analysis to provide a clear picture.
Definition: Architecture Decision Record from where you should specialise the ADR SBBs regarding the Installability
Source: ISO/IEC/IEEE 42010:2022
Source reference: https://www.iso.org/standard/74393.html
Additional information: Installability in software architecture refers to the design and characteristics of a software system that enable easy and efficient installation, configuration, and deployment onto target environments. An installable software architecture aims to simplify the installation process for end-users or system administrators, reducing the time, effort, and potential errors involved in setting up and configuring the system.
Example: Title: Installability Architecture Decision Record (ADR)
LOST view: Digital Solution Architecture Decisions Catalogue view
Identifier: http://data.europa.eu/dr8/egovera/InstallabilityGoal
EIRA traceability: eira:DigitalSolutionArchitectureDecisionGoal
ABB name: egovera:InstallabilityGoal
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-07-06
dct:identifier: ADR-20230606091024766
dct:title: Architecture Decision Record about Installability
eira:adr_context: The context explains why we need to make a decision. It also describes the alternatives along with the pros and cons.
eira:adr_decision: The decision describes the justification for why the particular solution was accepted. It has more emphasis on the why rather than the how.
eira:adr_status: [Proposed (under review)|Accepted (approved and ready for implementation)|Superseded (superseded by another decision)]
eira:adr_consecuences: The consequences section contains information about the overall impact of an architectural decision. Every decision has trade-offs. That’s why it’s crucial to include the analysis to provide a clear picture.
Definition: Architecture Decision Record from where you should specialise the ADR SBBs regarding the Adequacy Recognition
Source: ISO/IEC/IEEE 42010:2022
Source reference: https://www.iso.org/standard/74393.html
Additional information: Adequacy recognition refers to the degree to which the process of evaluating the suitability, completeness, and reliability of data or information within a software system is user-friendly, intuitive, and efficient. It encompasses the design and implementation of interfaces, workflows, and feedback mechanisms that enable users to easily and effectively perform adequacy recognition tasks.
Example: Title: Adequacy Recognition Architecture Decision Record (ADR)
LOST view: Digital Solution Architecture Decisions Catalogue view
Identifier: http://data.europa.eu/dr8/egovera/AdequacyRecognitionGoal
EIRA traceability: eira:DigitalSolutionArchitectureDecisionGoal
ABB name: egovera:AdequacyRecognitionGoal
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-07-06
dct:identifier: ADR-20230606091024719
dct:title: Architecture Decision Record about Adequacy Recognition
eira:adr_context: The context explains why we need to make a decision. It also describes the alternatives along with the pros and cons.
eira:adr_decision: The decision describes the justification for why the particular solution was accepted. It has more emphasis on the why rather than the how.
eira:adr_status: [Proposed (under review)|Accepted (approved and ready for implementation)|Superseded (superseded by another decision)]
eira:adr_consecuences: The consequences section contains information about the overall impact of an architectural decision. Every decision has trade-offs. That’s why it’s crucial to include the analysis to provide a clear picture.
Definition: Architecture Decision Record from where you should specialise the ADR SBBs regarding the Disaster Recovery Plan
Source: ISO
Source reference: https://www.iso.org/standard/75106.html
Additional information: A Disaster Recovery Plan (DRP) is a documented and structured approach that outlines the strategies, processes, and procedures to be followed in the event of a disaster or significant disruption that impacts an organization's IT infrastructure, systems, and data. The primary goal of a DRP is to minimize the impact of the disaster, recover critical systems and data, and restore normal operations as quickly and efficiently as possible.
Example: Title: Disaster Recovery Plan Architecture Decision Record (ADR)
LOST view: Digital Solution Architecture Decisions Catalogue view
Identifier: http://data.europa.eu/dr8/egovera/DisasterRecoveryPlanGoal
EIRA traceability: eira:DigitalSolutionArchitectureDecisionGoal
ABB name: egovera:DisasterRecoveryPlanGoal
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-07-06
dct:identifier: ADR-20230606091024730
dct:title: Architecture Decision Record about Application of Disaster Recovery Plan
eira:adr_context: The context explains why we need to make a decision. It also describes the alternatives along with the pros and cons.
eira:adr_decision: The decision describes the justification for why the particular solution was accepted. It has more emphasis on the why rather than the how.
eira:adr_status: [Proposed (under review)|Accepted (approved and ready for implementation)|Superseded (superseded by another decision)]
eira:adr_consecuences: The consequences section contains information about the overall impact of an architectural decision. Every decision has trade-offs. That’s why it’s crucial to include the analysis to provide a clear picture.
Definition: Public Policy Objective ABB is a Goal allowing public authorities to set the path towards the implementation of a public strategy.
Source: EuroVoc
Source reference: 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
Additional information: Public Policy Objectives are usually formalized in the legislation. Thus, the EU data strategy is supported by a catalogue of legislation comprising the Data Act (https://digital-strategy.ec.europa.eu/en/policies/data-act), the Data Governance Act (https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:52020PC0767), the Interoperable Europe Act (https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A52022PC0720), and other ancillary binding legal instruments like the GDPR, eIDAS, the framework for the flow of non-personal data, as well as by non-binding instruments like the Communication of the Commission on a European data space (https://eur-lex.europa.eu/legal-content/en/ALL/?uri=CELEX%3A52018DC0232)
Example: The following implementation is an example of how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): In 2021-2027 EU cohesion policy has set a shorter, modern menu of 5 policy objectives supporting growth for the period 2021-2027. The Joint Action Plan includes actions on: 1. a more competitive and smarter Europe; 2. a greener, low carbon transitioning towards a net zero carbon economy; 3. a more connected Europe by enhancing mobility; 4. a more social and inclusive Europe; 5. Europe closer to citizens by fostering the sustainable and integrated development of all types of territories (https://ec.europa.eu/regional_policy/2021-2027_en)
Interoperability Dimension: Structural IoP
LOST view: Legal view
Viewpoint: Enterprise Architecture Framework alignment guidelines viewpoint
Interoperability Saliency: The Public Policy Objective ABB is salient for the governance of interoperability because it sets the path toward the definition of courses of action and frameworks that facilitates data sharing across EU countries. This ABB also is salient for legal interoperability due to it will drive the specification of legal requirements for the enablement of interoperability.
Identifier: http://data.europa.eu/dr8/PublicPolicyObjectiveGoal
ABB name: eira:PublicPolicyObjectiveGoal
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/PublicPolicyObjectiveGoal
Interoperability Layer: Legal
Definition: Architecture Decision Record from where you should specialise the ADR SBBs regarding the Continous Security Monitoring
Source: ISO/IEC/IEEE 42010:2022
Source reference: https://www.iso.org/standard/74393.html
Additional information: Continuous Security Monitoring is a concept in IT architecture that involves the continuous monitoring of an organization's IT infrastructure to detect and respond to security threats in real-time. This approach involves the use of automated tools and processes to monitor network traffic, system logs, and other data sources for signs of suspicious activity. The goal of continuous security monitoring is to identify potential security incidents as early as possible, so that they can be addressed before they can cause significant damage to the organization. This approach is becoming increasingly important as the number and complexity of security threats continue to grow, and as organizations become more reliant on technology to support their operations.
Example: Continuous Security Monitoring:
Decision: Implementing security monitoring tools and processes to continuously monitor and detect security incidents and vulnerabilities.
Rationale: Continuous security monitoring helps identify and respond to security threats promptly, reducing the risk of unauthorized access, data breaches, or service disruptions.
LOST view: Digital Solution Architecture Decisions Catalogue view
Identifier: http://data.europa.eu/dr8/egovera/ContinousSecurityMonitoringGoal
EIRA traceability: eira:DigitalSolutionArchitectureDecisionGoal
ABB name: egovera:ContinousSecurityMonitoringGoal
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-06-15
dct:identifier: ADR-20230515180947683
dct:title: Architecture Decision Record about Continous Security Monitoring
eira:adr_context: The context explains why we need to make a decision. It also describes the alternatives along with the pros and cons.
eira:adr_decision: The decision describes the justification for why the particular solution was accepted. It has more emphasis on the why rather than the how.
eira:adr_status: [Proposed (under review)|Accepted (approved and ready for implementation)|Superseded (superseded by another decision)]
eira:adr_consecuences: The consequences section contains information about the overall impact of an architectural decision. Every decision has trade-offs. That’s why it’s crucial to include the analysis to provide a clear picture.
Definition: Architecture Decision Record from where you should specialise the ADR SBBs regarding the Coding Standards
Source: ISO/IEC/IEEE 42010:2022
Source reference: https://www.iso.org/standard/74393.html
Additional information: This ADR documents decisions regarding the coding standards and guidelines that developers should follow during software development. It includes decisions related to code formatting, naming conventions, and best practices to ensure consistency and improve code quality.
Example: Title: Coding Standards Architecture Decision Record (ADR)
LOST view: Digital Solution Architecture Decisions Catalogue view
Identifier: http://data.europa.eu/dr8/egovera/CodingStandardsGoal
EIRA traceability: eira:DigitalSolutionArchitectureDecisionGoal
ABB name: egovera:CodingStandardsGoal
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-07-06
dct:identifier: ADR-20230606091024690
dct:title: Architecture Decision Record about Coding Standards
eira:adr_context: The context explains why we need to make a decision. It also describes the alternatives along with the pros and cons.
eira:adr_decision: The decision describes the justification for why the particular solution was accepted. It has more emphasis on the why rather than the how.
eira:adr_status: [Proposed (under review)|Accepted (approved and ready for implementation)|Superseded (superseded by another decision)]
eira:adr_consecuences: The consequences section contains information about the overall impact of an architectural decision. Every decision has trade-offs. That’s why it’s crucial to include the analysis to provide a clear picture.
Definition: Architecture Decision Record from where you should specialise the ADR SBBs regarding the Security Testing
Source: ISO/IEC/IEEE 42010:2022
Source reference: https://www.iso.org/standard/74393.html
Additional information: Security testing is a critical aspect of IT architecture decision-making. It involves the evaluation of a system's security measures to identify vulnerabilities and potential threats. The goal of security testing is to ensure that the system is secure and protected from unauthorized access, data breaches, and other security risks. The testing process involves a range of techniques, including penetration testing, vulnerability scanning, and risk assessment. By conducting security testing, IT architects can identify weaknesses in the system and take steps to address them, thereby improving the overall security posture of the organization.
Example: Security Testing:
Decision: Conducting regular penetration testing and vulnerability assessments on the system.
Rationale: Regular security testing helps identify and address vulnerabilities and weaknesses in the system, reducing the risk of exploitation by attackers. It ensures the ongoing security and resilience of the system.
LOST view: Digital Solution Architecture Decisions Catalogue view
Identifier: http://data.europa.eu/dr8/egovera/SecurityTestingGoal
EIRA traceability: eira:DigitalSolutionArchitectureDecisionGoal
ABB name: egovera:SecurityTestingGoal
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-06-15
dct:identifier: ADR-20230515180947450
dct:title: Architecture Decision Record about Security Testing
eira:adr_context: The context explains why we need to make a decision. It also describes the alternatives along with the pros and cons.
eira:adr_decision: The decision describes the justification for why the particular solution was accepted. It has more emphasis on the why rather than the how.
eira:adr_status: [Proposed (under review)|Accepted (approved and ready for implementation)|Superseded (superseded by another decision)]
eira:adr_consecuences: The consequences section contains information about the overall impact of an architectural decision. Every decision has trade-offs. That’s why it’s crucial to include the analysis to provide a clear picture.
DEFINITION:
Achieve Legal Interoperability ABB is a Goal. For the purpose of the EIF, interoperability is the ability of organisations to interact towards mutually beneficial goals, involving the sharing of information and knowledge between these organisations, through the business processes they support, by means of the exchange of data between their ICT systems.
The interoperability model which is applicable to all digital public services and may also be considered as an integral element of the interoperability-by-design paradigm. It includes: four layers of interoperability: legal, organisational, semantic and technical.
Legal interoperability is about ensuring that organisations operating under different legal frameworks, policies and strategies are able to work together.
Source: EIF
(https://ec.europa.eu/isa2/sites/isa/files/eif_brochure_final.pdf)
EXAMPLES:
The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB):
Definition: Architecture Decision Record from where you should specialise the ADR SBBs regarding the Application of Service Monitoring Tools Configuration
Source: ISO/IEC/IEEE 42010:2022
Source reference: https://www.iso.org/standard/74393.html
Additional information: The Application of Service Monitoring Tools Configuration concept refers to the process of configuring service monitoring tools to ensure that they can effectively monitor and manage the performance of IT services. This involves setting up the tools to collect data on key performance indicators (KPIs) such as response time, availability, and throughput, and configuring alerts and notifications to ensure that IT teams are alerted to any issues that arise. The goal of this concept is to enable IT teams to proactively identify and address issues before they impact end-users, thereby improving the overall performance and reliability of IT services.
Example: Network Optimization:
Decision: The GitHub alertmanager receiver can easily be configured and operated to function with Prometheus alerts. It automatically creates issues in GitHub repositories for any active alerts being fired, making it visible for any user to track
All communication/updates/concerns related to the incident can be easily handled by adding comments in the issues created by the GitHub receiver
Unlike Option 1, there is no additional cost involved
There is no requirement for using JIRA/Slack for incident tracking, which are the only supported options in some of the tools listed in Option 2 (such as Dispatch and Response) In any case that such a requirement surfaces, we can use GitHub bots for different platforms such as GitHub for Slack and Google Chat to notify us of the issues immediately
It is actively being maintained and supported compared to some of the tools in Option 1 (such as Cabot and OpenDuty) which lack community support
Rationale: As we have multiple services/applications deployed and monitored in the Operate First environment (ex. Jupyterhub, Argo, Superset, Observatorium, Project Thoth, AICoE CI pipelines etc), we need to implement an incident reporting setup for handling outages/incidents related to these services.
LOST view: Digital Solution Architecture Decisions Catalogue view
Identifier: http://data.europa.eu/dr8/egovera/ApplicationOfServiceMonitoringToolsConfigurationGoal
EIRA traceability: eira:DigitalSolutionArchitectureDecisionGoal
ABB name: egovera:ApplicationOfServiceMonitoringToolsConfigurationGoal
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-06-15
dct:identifier: ADR-20230515180947662
dct:title: Architecture Decision Record about Application of Service Monitoring Tools Configuration
eira:adr_context: The context explains why we need to make a decision. It also describes the alternatives along with the pros and cons.
eira:adr_decision: The decision describes the justification for why the particular solution was accepted. It has more emphasis on the why rather than the how.
eira:adr_status: [Proposed (under review)|Accepted (approved and ready for implementation)|Superseded (superseded by another decision)]
eira:adr_consecuences: The consequences section contains information about the overall impact of an architectural decision. Every decision has trade-offs. That’s why it’s crucial to include the analysis to provide a clear picture.
Definition: Architecture Decision Record from where you should specialise the ADR SBBs regarding the Technology Stack Selection
Source: ISO/IEC/IEEE 42010:2022
Source reference: https://www.iso.org/standard/74393.html
Additional information: Technology Stack Selection SBB is a crucial decision in IT architecture that involves choosing the appropriate set of technologies, frameworks, and tools to build a software application. The technological stack selection process involves evaluating various factors such as scalability, performance, security, ease of maintenance, and cost-effectiveness. The technology stack includes the programming language, database, web server, operating system, and other software components required to build the application. The right technology stack selection can significantly impact the success of the software application (or architecture), as it can affect the development time, cost, and overall quality of the product.
Example: Technology Stack Selection:
Decision: Selecting Node.js and React.js as the primary technologies for a web application.
Rationale: Node.js provides a lightweight and scalable runtime environment for the backend, while React.js offers a component-based approach for building responsive and interactive user interfaces.
LOST view: Digital Solution Architecture Decisions Catalogue view
Identifier: http://data.europa.eu/dr8/egovera/TechnologyStackSelectionGoal
EIRA traceability: eira:DigitalSolutionArchitectureDecisionGoal
ABB name: egovera:TechnologyStackSelectionGoal
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-06-15
dct:identifier: ADR-20230515180947724
dct:title: Architecture Decision Record about Technology Stack Selection
eira:adr_context: The context explains why we need to make a decision. It also describes the alternatives along with the pros and cons.
eira:adr_decision: The decision describes the justification for why the particular solution was accepted. It has more emphasis on the why rather than the how.
eira:adr_status: [Proposed (under review)|Accepted (approved and ready for implementation)|Superseded (superseded by another decision)]
eira:adr_consecuences: The consequences section contains information about the overall impact of an architectural decision. Every decision has trade-offs. That’s why it’s crucial to include the analysis to provide a clear picture.
DEFINITION:
Achieve Semantic Interoperability ABB is a Goal. For the purpose of the EIF, interoperability is the ability of organisations to interact towards mutually beneficial goals, involving the sharing of information and knowledge between these organisations, through the business processes they support, by means of the exchange of data between their ICT systems.
The interoperability model which is applicable to all digital public services and may also be considered as an integral element of the interoperability-by-design paradigm. It includes: four layers of interoperability: legal, organisational, semantic and technical.
Semantic interoperability ensures that the precise format and meaning of exchanged data and information is preserved and understood throughout exchanges between parties, in other words ‘what is sent is what is understood’. In the EIF, semantic interoperability covers both semantic and syntactic aspects.
Source: EIF
(https://ec.europa.eu/isa2/sites/isa/files/eif_brochure_final.pdf)
EXAMPLES:
The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB):
DEFINITION:
Achieve Technical Interoperability ABB is a Goal. For the purpose of the EIF, interoperability is the ability of organisations to interact towards mutually beneficial goals, involving the sharing of information and knowledge between these organisations, through the business processes they support, by means of the exchange of data between their ICT systems.
The interoperability model which is applicable to all digital public services and may also be considered as an integral element of the interoperability-by-design paradigm. It includes: four layers of interoperability: legal, organisational, semantic and technical.
Technical interoperability covers the applications and infrastructures linking systems and services. Aspects of technical interoperability include interface specifications, interconnection services, data integration services, data presentation and exchange, and secure communication protocols
Source: EIF
(https://ec.europa.eu/isa2/sites/isa/files/eif_brochure_final.pdf)
EXAMPLES:
The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB):
Definition: Architecture Decision Record from where you should specialise the ADR SBBs regarding the Caching Strategy
Source: ISO/IEC/IEEE 42010:2022
Source reference: https://www.iso.org/standard/74393.html
Additional information: Caching strategy is a concept in IT architecture that involves the use of caching mechanisms to improve the performance of applications and systems. Caching involves storing frequently accessed data in a cache, which is a temporary storage area that is closer to the application or system than the original data source. This reduces the time it takes to access the data, thereby improving the overall performance of the application or system.
Example: Caching Mechanism:
Decision: Implementing a distributed caching mechanism, such as Redis or Memcached, to improve response times and reduce database load.
Rationale: Caching frequently accessed data in memory reduces the need for repeated database queries, resulting in faster response times, improved scalability, and reduced strain on the database infrastructure.
LOST view: Digital Solution Architecture Decisions Catalogue view
Identifier: http://data.europa.eu/dr8/egovera/CachingStrategyGoal
EIRA traceability: eira:DigitalSolutionArchitectureDecisionGoal
ABB name: egovera:CachingStrategyGoal
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-06-15
dct:identifier: ADR-20230515180947584
dct:title: Architecture Decision Record about Caching Strategy
eira:adr_context: The context explains why we need to make a decision. It also describes the alternatives along with the pros and cons.
eira:adr_decision: The decision describes the justification for why the particular solution was accepted. It has more emphasis on the why rather than the how.
eira:adr_status: [Proposed (under review)|Accepted (approved and ready for implementation)|Superseded (superseded by another decision)]
eira:adr_consecuences: The consequences section contains information about the overall impact of an architectural decision. Every decision has trade-offs. That’s why it’s crucial to include the analysis to provide a clear picture.
Definition: Architecture Decision Record from where you should specialise the ADR SBBs regarding the Encryption Standards
Source: ISO/IEC/IEEE 42010:2022
Source reference: https://www.iso.org/standard/74393.html
Additional information: Encryption standards refer to the set of protocols and algorithms used to secure data and information. These standards ensure that sensitive information is protected from unauthorized access, theft, or manipulation. The choice of encryption standards is critical in IT architecture decisions as it determines the level of security and protection that the system can provide. The most used encryption standards include AES, RSA, and SHA, among others. The selection of encryption standards depends on the specific needs of the organization, the type of data being protected, and the level of security required. The implementation of encryption standards requires careful planning and management to ensure that the system is secure and effective.
Example: Encryption Standards:
Decision: Using Advanced Encryption Standard (AES) with a key length of 256 bits for data encryption at rest.
Rationale: AES-256 is a widely accepted and secure encryption algorithm, providing strong protection for sensitive data stored on disk or in databases.
LOST view: Digital Solution Architecture Decisions Catalogue view
Identifier: http://data.europa.eu/dr8/egovera/EncryptionStandardsGoal
EIRA traceability: eira:DigitalSolutionArchitectureDecisionGoal
ABB name: egovera:EncryptionStandardsGoal
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-06-15
dct:identifier: ADR-20230515180947536
dct:title: Architecture Decision Record about Encryption Standards
eira:adr_context: The context explains why we need to make a decision. It also describes the alternatives along with the pros and cons.
eira:adr_decision: The decision describes the justification for why the particular solution was accepted. It has more emphasis on the why rather than the how.
eira:adr_status: [Proposed (under review)|Accepted (approved and ready for implementation)|Superseded (superseded by another decision)]
eira:adr_consecuences: The consequences section contains information about the overall impact of an architectural decision. Every decision has trade-offs. That’s why it’s crucial to include the analysis to provide a clear picture.
Definition: Architecture Decision Record from where you should specialise the ADR SBBs regarding the UserInterface
Source: ISO/IEC/IEEE 42010:2022
Source reference: https://www.iso.org/standard/74393.html
Additional information: Accessibility in the context of usability refers to the design and implementation of a software system that ensures equal access and usability for all users, including those with disabilities or impairments. It focuses on creating an inclusive user experience by removing barriers and providing accommodations to enable individuals with disabilities to perceive, understand, navigate, and interact with the system effectively.
Example: Title: Accessibility Architecture Decision Record (ADR)
LOST view: Digital Solution Architecture Decisions Catalogue view
Identifier: http://data.europa.eu/dr8/egovera/AccessibilityGoal
EIRA traceability: eira:DigitalSolutionArchitectureDecisionGoal
ABB name: egovera:AccessibilityGoal
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-07-06
dct:identifier: ADR-20230606091024752
dct:title: Architecture Decision Record about UserInterface
eira:adr_context: The context explains why we need to make a decision. It also describes the alternatives along with the pros and cons.
eira:adr_decision: The decision describes the justification for why the particular solution was accepted. It has more emphasis on the why rather than the how.
eira:adr_status: [Proposed (under review)|Accepted (approved and ready for implementation)|Superseded (superseded by another decision)]
eira:adr_consecuences: The consequences section contains information about the overall impact of an architectural decision. Every decision has trade-offs. That’s why it’s crucial to include the analysis to provide a clear picture.
Definition: Architecture Decision Record from where you should specialise the ADR SBBs regarding the UserInterface
Source: ISO/IEC/IEEE 42010:2022
Source reference: https://www.iso.org/standard/74393.html
Additional information: the user interface (UI) refers to the visual and interactive elements of a software system that allow users to interact with and control the system. It encompasses the design and presentation of screens, menus, buttons, forms, and other visual components that users engage with to perform tasks and access information within the system.
Example: Title: User Interface Architecture Decision Record (ADR)
LOST view: Digital Solution Architecture Decisions Catalogue view
Identifier: http://data.europa.eu/dr8/egovera/UserInterfaceGoal
EIRA traceability: eira:DigitalSolutionArchitectureDecisionGoal
ABB name: egovera:UserInterfaceGoal
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-07-06
dct:identifier: ADR-20230606091024717
dct:title: Architecture Decision Record about UserInterface
eira:adr_context: The context explains why we need to make a decision. It also describes the alternatives along with the pros and cons.
eira:adr_decision: The decision describes the justification for why the particular solution was accepted. It has more emphasis on the why rather than the how.
eira:adr_status: [Proposed (under review)|Accepted (approved and ready for implementation)|Superseded (superseded by another decision)]
eira:adr_consecuences: The consequences section contains information about the overall impact of an architectural decision. Every decision has trade-offs. That’s why it’s crucial to include the analysis to provide a clear picture.
Definition: Architecture Decision Record from where you should specialise the ADR SBBs regarding the Version Control
Source: ISO/IEC/IEEE 42010:2022
Source reference: https://www.iso.org/standard/74393.html
Additional information: This ADR focuses on decisions related to version control systems and practices. It includes decisions on the selection and configuration of version control tools (e.g., Git, SVN), branching strategies, and guidelines for effective collaboration among developers.
Example: Title: Version Control Architecture Decision Record (ADR)
LOST view: Digital Solution Architecture Decisions Catalogue view
Identifier: http://data.europa.eu/dr8/egovera/VersionControlGoal
EIRA traceability: eira:DigitalSolutionArchitectureDecisionGoal
ABB name: egovera:VersionControlGoal
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-07-06
dct:identifier: ADR-20230606091024749
dct:title: Architecture Decision Record about Version Control
eira:adr_context: The context explains why we need to make a decision. It also describes the alternatives along with the pros and cons.
eira:adr_decision: The decision describes the justification for why the particular solution was accepted. It has more emphasis on the why rather than the how.
eira:adr_status: [Proposed (under review)|Accepted (approved and ready for implementation)|Superseded (superseded by another decision)]
eira:adr_consecuences: The consequences section contains information about the overall impact of an architectural decision. Every decision has trade-offs. That’s why it’s crucial to include the analysis to provide a clear picture.
Definition: Architecture Decision Record from where you should specialise the ADR SBBs regarding the Monetization Strategy
Source: ISO/IEC/IEEE 42010:2022
Source reference: https://www.iso.org/standard/74393.html
Additional information: Monetization strategy is a decision in IT architecture that determines how a company will generate revenue from its digital products or services. It involves identifying the target audience, understanding their needs and preferences, and developing a pricing model that aligns with the value proposition of the product or service. The monetization strategy can be based on various models such as subscription-based, pay-per-use, freemium, or advertising-based. The choice of the model depends on the nature of the product or service, the market demand, and the competitive landscape. A well-defined monetization strategy can help a company to maximize its revenue potential, build customer loyalty, and sustain long-term growth.
Example: Decision: Implementing a subscription-based pricing model for a software-as-a-service (SaaS) product.
Rationale: A subscription-based model provides recurring revenue and aligns with the target market's willingness to pay for ongoing access to the product's features and services.
LOST view: Digital Solution Architecture Decisions Catalogue view
Identifier: http://data.europa.eu/dr8/egovera/MonetizationStrategyGoal
EIRA traceability: eira:DigitalSolutionArchitectureDecisionGoal
ABB name: egovera:MonetizationStrategyGoal
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-06-15
dct:identifier: ADR-20230515180947575
dct:title: Architecture Decision Record about Monetization Strategy
eira:adr_context: The context explains why we need to make a decision. It also describes the alternatives along with the pros and cons.
eira:adr_decision: The decision describes the justification for why the particular solution was accepted. It has more emphasis on the why rather than the how.
eira:adr_status: [Proposed (under review)|Accepted (approved and ready for implementation)|Superseded (superseded by another decision)]
eira:adr_consecuences: The consequences section contains information about the overall impact of an architectural decision. Every decision has trade-offs. That’s why it’s crucial to include the analysis to provide a clear picture.
Definition: Architecture Decision Record from where you should specialise the ADR SBBs regarding the Network Optimization
Source: ISO/IEC/IEEE 42010:2022
Source reference: https://www.iso.org/standard/74393.html
Additional information: Network optimization is a concept in IT architecture that involves improving the performance and efficiency of a computer network. This can be achieved through various techniques such as reducing network congestion, optimizing routing protocols, improving bandwidth utilization, and implementing load balancing. The goal of network optimization is to ensure that the network can handle the increasing demands of data traffic and provide a seamless user experience. It is an important consideration for organizations that rely heavily on their network infrastructure to support their business operations.
Example: Network Optimization:
Decision: Implementing network optimization techniques, such as compression, caching, and minimizing network round trips, to reduce latency and improve data transmission efficiency.
Rationale: Optimizing network communication improves system performance by reducing the time required to transfer data and improving the utilization of network resources.
LOST view: Digital Solution Architecture Decisions Catalogue view
Identifier: http://data.europa.eu/dr8/egovera/NetworkOptimizationGoal
EIRA traceability: eira:DigitalSolutionArchitectureDecisionGoal
ABB name: egovera:NetworkOptimizationGoal
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-06-15
dct:identifier: ADR-20230515180947421
dct:title: Architecture Decision Record about Network Optimization
eira:adr_context: The context explains why we need to make a decision. It also describes the alternatives along with the pros and cons.
eira:adr_decision: The decision describes the justification for why the particular solution was accepted. It has more emphasis on the why rather than the how.
eira:adr_status: [Proposed (under review)|Accepted (approved and ready for implementation)|Superseded (superseded by another decision)]
eira:adr_consecuences: The consequences section contains information about the overall impact of an architectural decision. Every decision has trade-offs. That’s why it’s crucial to include the analysis to provide a clear picture.
Definition: Architecture Decision Record from where you should specialise the ADR SBBs regarding the Elastic Cloud Infrastructure
Source: ISO/IEC/IEEE 42010:2022
Source reference: https://www.iso.org/standard/74393.html
Additional information: Elastic Cloud Infrastructure (ECI) is a concept in IT architecture that refers to a cloud-based infrastructure that can dynamically scale up or down based on the needs of the application or workload. This means that resources such as computing power, storage, and network bandwidth can be added or removed as required, allowing for greater flexibility and cost-effectiveness. ECI is often used in conjunction with containerization technologies such as Docker and Kubernetes, which allow applications to be packaged and deployed in a consistent and portable manner. ECI can also help to improve application performance and availability by distributing workloads across multiple servers or data centers.
Example: Elastic Cloud Infrastructure:
Decision: Utilizing cloud infrastructure services to dynamically adjust resources based on demand.
Rationale: Cloud-based auto scaling enables the system to automatically add or remove compute resources in response to changes in workload, ensuring optimal resource allocation and scalability.
LOST view: Digital Solution Architecture Decisions Catalogue view
Identifier: http://data.europa.eu/dr8/egovera/ElasticCloudInfrastructureGoal
EIRA traceability: eira:DigitalSolutionArchitectureDecisionGoal
ABB name: egovera:ElasticCloudInfrastructureGoal
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-06-15
dct:identifier: ADR-20230515180947866
dct:title: Architecture Decision Record about Elastic Cloud Infrastructure
eira:adr_context: The context explains why we need to make a decision. It also describes the alternatives along with the pros and cons.
eira:adr_decision: The decision describes the justification for why the particular solution was accepted. It has more emphasis on the why rather than the how.
eira:adr_status: [Proposed (under review)|Accepted (approved and ready for implementation)|Superseded (superseded by another decision)]
eira:adr_consecuences: The consequences section contains information about the overall impact of an architectural decision. Every decision has trade-offs. That’s why it’s crucial to include the analysis to provide a clear picture.
Definition: Achieve Interoperability ABB is a Goal. For the purpose of the EIF, interoperability is the ability of organisations to interact towards mutually beneficial goals, involving the sharing of information and knowledge between these organisations, through the business processes they support, by means of the exchange of data between their ICT systems.
Source: EIF
Source reference: https://ec.europa.eu/isa2/sites/isa/files/eif_brochure_final.pdf
Additional information: The interoperability model which is applicable to all digital public services and may also be considered as an integral element of the interoperability-by-design paradigm. It includes: four layers of interoperability: legal, organisational, semantic and technical.
eira:iopDimension: Behavioral IoP
LOST view: Enterprise Architecture Framework alignment guidelines view
Identifier: http://data.europa.eu/dr8/AchieveInteroperabilityGoal
ABB name: eira:AchieveInteroperabilityGoal
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-04-18
dct:identifier: http://data.europa.eu/dr8/AchieveInteroperabilityGoal
Definition: Architecture Decision Record from where you should specialise the ADR SBBs regarding the Content Delivery Network
Source: ISO/IEC/IEEE 42010:2022
Source reference: https://www.iso.org/standard/74393.html
Additional information: A Content Delivery Network (CDN) is a distributed network of servers that work together to deliver content to end-users. The concept of a CDN is to reduce the latency and improve the performance of websites and applications by caching content closer to the end-users. This is achieved by replicating the content across multiple servers in different geographic locations, allowing users to access the content from the server closest to them. CDNs are commonly used for delivering static content such as images, videos, and other media files. They can also be used for dynamic content such as web applications and APIs. CDNs can improve website performance, reduce server load, and provide better user experience.
Example: Content Delivery Network (CDN):
Decision: Utilizing a CDN to distribute static content and media files closer to end-users.
Rationale: A CDN improves performance by caching and delivering content from edge servers located in various geographic regions, reducing latency and improving the overall user experience.
LOST view: Digital Solution Architecture Decisions Catalogue view
Identifier: http://data.europa.eu/dr8/egovera/ContentDeliveryNetworkGoal
EIRA traceability: eira:DigitalSolutionArchitectureDecisionGoal
ABB name: egovera:ContentDeliveryNetworkGoal
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-06-15
dct:identifier: ADR-20230515180947430
dct:title: Architecture Decision Record about Content Delivery Network
eira:adr_context: The context explains why we need to make a decision. It also describes the alternatives along with the pros and cons.
eira:adr_decision: The decision describes the justification for why the particular solution was accepted. It has more emphasis on the why rather than the how.
eira:adr_status: [Proposed (under review)|Accepted (approved and ready for implementation)|Superseded (superseded by another decision)]
eira:adr_consecuences: The consequences section contains information about the overall impact of an architectural decision. Every decision has trade-offs. That’s why it’s crucial to include the analysis to provide a clear picture.
Definition: Architecture Decision Record from where you should specialise the ADR SBBs regarding the Serveless Architecture
Source: ISO/IEC/IEEE 42010:2022
Source reference: https://www.iso.org/standard/74393.html
Additional information: Serverless architecture, also known as Function-as-a-Service (FaaS), allows developers to focus on writing and deploying individual functions or microservices without managing the underlying infrastructure. Functions are triggered by events and run in ephemeral containers managed by a cloud provider. This architecture eliminates the need for provisioning or managing servers, enabling scalability and cost optimization.
Example: Title: Serverless Architecture Decision Record (ADR)
LOST view: Digital Solution Architecture Decisions Catalogue view
Identifier: http://data.europa.eu/dr8/egovera/ServelessArchitectureGoal
EIRA traceability: eira:DigitalSolutionArchitectureDecisionGoal
ABB name: egovera:ServelessArchitectureGoal
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-07-06
dct:identifier: ADR-20230606091024695
dct:title: Architecture Decision Record about Serveless Architecture
eira:adr_context: The context explains why we need to make a decision. It also describes the alternatives along with the pros and cons.
eira:adr_decision: The decision describes the justification for why the particular solution was accepted. It has more emphasis on the why rather than the how.
eira:adr_status: [Proposed (under review)|Accepted (approved and ready for implementation)|Superseded (superseded by another decision)]
eira:adr_consecuences: The consequences section contains information about the overall impact of an architectural decision. Every decision has trade-offs. That’s why it’s crucial to include the analysis to provide a clear picture.
Definition: Architecture Decision Record from where you should specialise the ADR SBBs regarding the Horizontal Scaling
Source: ISO/IEC/IEEE 42010:2022
Source reference: https://www.iso.org/standard/74393.html
Additional information: Horizontal scaling is a decision in IT architecture that involves adding more servers or nodes to a system to increase its capacity and performance. This approach is often used in distributed systems, where workloads can be spread across multiple servers to improve efficiency and reduce the risk of downtime. Horizontal scaling can be achieved through various techniques, such as load balancing, clustering, and sharding, and it can help organizations to scale their IT infrastructure in a cost-effective and flexible manner. However, horizontal scaling also requires careful planning and management to ensure that the system remains reliable and secure as it grows.
Example: Horizontal Scaling:
Decision: Adopting a microservices architecture to enable horizontal scaling of system components.
Rationale: A microservices architecture allows for independent scaling of individual services based on demand, providing flexibility and the ability to allocate resources where they are most needed.
LOST view: Digital Solution Architecture Decisions Catalogue view
Identifier: http://data.europa.eu/dr8/egovera/HorizontalScalingGoal
EIRA traceability: eira:DigitalSolutionArchitectureDecisionGoal
ABB name: egovera:HorizontalScalingGoal
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-06-15
dct:identifier: ADR-20230515180947594
dct:title: Architecture Decision Record about Horizontal Scaling
eira:adr_context: The context explains why we need to make a decision. It also describes the alternatives along with the pros and cons.
eira:adr_decision: The decision describes the justification for why the particular solution was accepted. It has more emphasis on the why rather than the how.
eira:adr_status: [Proposed (under review)|Accepted (approved and ready for implementation)|Superseded (superseded by another decision)]
eira:adr_consecuences: The consequences section contains information about the overall impact of an architectural decision. Every decision has trade-offs. That’s why it’s crucial to include the analysis to provide a clear picture.
Definition: Architecture Decision Record from where you should specialise the ADR SBBs regarding the Adaptability
Source: ISO/IEC/IEEE 42010:2022
Source reference: https://www.iso.org/standard/74393.html
Additional information: Adaptability in software architecture refers to the design and characteristics of a software system that allow it to easily and efficiently respond to changing requirements, technologies, and environmental conditions. An adaptable software architecture enables the system to evolve and adapt over time, facilitating seamless updates and modifications without significant disruption.
Example: Title: Adaptability Architecture Decision Record (ADR)
LOST view: Digital Solution Architecture Decisions Catalogue view
Identifier: http://data.europa.eu/dr8/egovera/AdaptabilityGoal
EIRA traceability: eira:DigitalSolutionArchitectureDecisionGoal
ABB name: egovera:AdaptabilityGoal
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-07-06
dct:identifier: ADR-20230606091024687
dct:title: Architecture Decision Record about Adaptability
eira:adr_context: The context explains why we need to make a decision. It also describes the alternatives along with the pros and cons.
eira:adr_decision: The decision describes the justification for why the particular solution was accepted. It has more emphasis on the why rather than the how.
eira:adr_status: [Proposed (under review)|Accepted (approved and ready for implementation)|Superseded (superseded by another decision)]
eira:adr_consecuences: The consequences section contains information about the overall impact of an architectural decision. Every decision has trade-offs. That’s why it’s crucial to include the analysis to provide a clear picture.
Definition: Architecture Decision Record from where you should specialise the ADR SBBs regarding the Secure Communications
Source: ISO/IEC/IEEE 42010:2022
Source reference: https://www.iso.org/standard/74393.html
Additional information: The Secure Communications concept in IT architecture decision-making refers to the implementation of measures that ensure the confidentiality, integrity, and availability of data transmitted between different systems or devices. This includes the use of encryption, digital signatures, and secure protocols such as SSL/TLS to protect data in transit from unauthorized access, interception, or modification. The Secure Communications concept is critical in ensuring the security of sensitive information such as financial transactions, personal data, and intellectual property. It is also essential for compliance with regulatory requirements such as HIPAA, PCI DSS, and GDPR.
Example: Secure Communications:
Decision: Enforcing Transport Layer Security (TLS) for secure communication over the network.
Rationale: TLS ensures that data transmitted between client and server is encrypted, preventing eavesdropping, tampering, and unauthorized interception of sensitive information.
LOST view: Digital Solution Architecture Decisions Catalogue view
Identifier: http://data.europa.eu/dr8/egovera/SecureCommunicationsGoal
EIRA traceability: eira:DigitalSolutionArchitectureDecisionGoal
ABB name: egovera:SecureCommunicationsGoal
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-06-15
dct:identifier: ADR-20230515180947469
dct:title: Architecture Decision Record about Secure Communications
eira:adr_context: The context explains why we need to make a decision. It also describes the alternatives along with the pros and cons.
eira:adr_decision: The decision describes the justification for why the particular solution was accepted. It has more emphasis on the why rather than the how.
eira:adr_status: [Proposed (under review)|Accepted (approved and ready for implementation)|Superseded (superseded by another decision)]
eira:adr_consecuences: The consequences section contains information about the overall impact of an architectural decision. Every decision has trade-offs. That’s why it’s crucial to include the analysis to provide a clear picture.
Definition: Architecture Decision Record from where you should specialise the ADR SBBs regarding the Dynamic Location of Data provider
Source: ISO/IEC/IEEE 42010:2022
Source reference: https://www.iso.org/standard/74393.html
Additional information: The concept of Dynamic Location of Data Provider in IT architecture refers to the ability of a system to automatically determine the best location for data storage and retrieval based on various factors such as network latency, availability of resources, and user location. This approach allows for more efficient use of resources and faster access to data, as the system can dynamically adjust to changing conditions and optimize performance. Additionally, it can help to reduce costs by minimizing the need for manual intervention and maintenance. Overall, the dynamic location of data provider concept is an important consideration in modern IT architecture design, particularly for systems that require high levels of performance and scalability.
Example: Decision: The Data Provider capable of providing the required evidence is dynamically located.
Consequence: New Capability: Data Provider Capability Management, including Data Provider Discovery
LOST view: Digital Solution Architecture Decisions Catalogue view
Identifier: http://data.europa.eu/dr8/egovera/DynamicLocationOfDataProviderGoal
EIRA traceability: eira:DigitalSolutionArchitectureDecisionGoal
ABB name: egovera:DynamicLocationOfDataProviderGoal
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-06-15
dct:identifier: ADR-20230515180947784
dct:title: Architecture Decision Record about Dynamic Location of Data provider
eira:adr_context: The context explains why we need to make a decision. It also describes the alternatives along with the pros and cons.
eira:adr_decision: The decision describes the justification for why the particular solution was accepted. It has more emphasis on the why rather than the how.
eira:adr_status: [Proposed (under review)|Accepted (approved and ready for implementation)|Superseded (superseded by another decision)]
eira:adr_consecuences: The consequences section contains information about the overall impact of an architectural decision. Every decision has trade-offs. That’s why it’s crucial to include the analysis to provide a clear picture.
Definition: Architecture Decision Record from where you should specialise the ADR SBBs regarding the Compliance with Data Privacy Regulations
Source: ISO/IEC/IEEE 42010:2022
Source reference: https://www.iso.org/standard/74393.html
Additional information: Compliance with data privacy regulations is a decision that ensures that an organization's data management practices align with the legal and regulatory requirements of the jurisdictions in which it operates. This decision involves implementing appropriate data protection measures, such as encryption, access controls, and data retention policies, to safeguard sensitive information from unauthorized access, use, or disclosure. Compliance with data privacy regulations also involves establishing clear policies and procedures for data handling, including data collection, storage, sharing, and disposal, to ensure that personal data is processed lawfully, fairly, and transparently. Failure to comply with data privacy regulations can result in severe legal and financial consequences, including fines, legal action, and reputational damage. Therefore, IT architecture decisions must prioritize compliance with data privacy regulations to protect the organization's data and reputation.
Example: Compliance with Data Privacy Regulations:
Decision: Ensuring compliance with the General Data Protection Regulation (GDPR) for handling customer data.
Rationale: Compliance with GDPR builds trust with customers, reduces the risk of legal consequences, and enhances the organization's reputation in terms of data privacy and security.
LOST view: Digital Solution Architecture Decisions Catalogue view
Identifier: http://data.europa.eu/dr8/egovera/ComplianceWithDataPrivacyRegulationsGoal
EIRA traceability: eira:DigitalSolutionArchitectureDecisionGoal
ABB name: egovera:ComplianceWithDataPrivacyRegulationsGoal
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-06-15
dct:identifier: ADR-20230515180947734
dct:title: Architecture Decision Record about Compliance with Data Privacy Regulations
eira:adr_context: The context explains why we need to make a decision. It also describes the alternatives along with the pros and cons.
eira:adr_decision: The decision describes the justification for why the particular solution was accepted. It has more emphasis on the why rather than the how.
eira:adr_status: [Proposed (under review)|Accepted (approved and ready for implementation)|Superseded (superseded by another decision)]
eira:adr_consecuences: The consequences section contains information about the overall impact of an architectural decision. Every decision has trade-offs. That’s why it’s crucial to include the analysis to provide a clear picture.
Definition: Architecture Decision Record from where you should specialise the ADR SBBs regarding the Cross-border User Authentication Operations
Source: ISO/IEC/IEEE 42010:2022
Source reference: https://www.iso.org/standard/74393.html
Additional information: Cross-border User Authentication Operations concept refers to the process of verifying the identity of users who are accessing digital services across different countries. It involves the use of various authentication methods such as biometrics, passwords, and tokens to ensure that only authorized users can access the services. It helps to enhance security, reduce fraud, and ensure compliance with regulatory requirements. The implementation of cross-border user authentication operations requires careful consideration of various factors such as legal and regulatory requirements, technical capabilities, and user experience.
Example: Decision: The Identity Provider operates the cross-border authentication of the User.
Consequence: Identity Provider is a new role in business ops
LOST view: Digital Solution Architecture Decisions Catalogue view
Identifier: http://data.europa.eu/dr8/egovera/Cross-borderUserAuthenticationOperationsGoal
EIRA traceability: eira:DigitalSolutionArchitectureDecisionGoal
ABB name: egovera:Cross-borderUserAuthenticationOperationsGoal
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-06-15
dct:identifier: ADR-20230515180947814
dct:title: Architecture Decision Record about Cross-border User Authentication Operations
eira:adr_context: The context explains why we need to make a decision. It also describes the alternatives along with the pros and cons.
eira:adr_decision: The decision describes the justification for why the particular solution was accepted. It has more emphasis on the why rather than the how.
eira:adr_status: [Proposed (under review)|Accepted (approved and ready for implementation)|Superseded (superseded by another decision)]
eira:adr_consecuences: The consequences section contains information about the overall impact of an architectural decision. Every decision has trade-offs. That’s why it’s crucial to include the analysis to provide a clear picture.
Definition: Architecture Decision Record from where you should specialise the ADR SBBs regarding the Authentication Mechanism
Source: ISO/IEC/IEEE 42010:2022
Source reference: https://www.iso.org/standard/74393.html
Additional information: Authentication Mechanism is a crucial concept in IT architecture that refers to the process of verifying the identity of a user or system before granting access to resources or services. It involves the use of various methods such as passwords, biometric identification, smart cards, and tokens to ensure that only authorized users can access sensitive information or perform critical operations. The choice of authentication mechanism depends on the level of security required, the complexity of the system, and the user experience. A well-designed authentication mechanism can prevent unauthorized access, protect against cyber threats, and enhance the overall security of the IT infrastructure.
Example: Authentication Mechanism:
Decision: Implementing multi-factor authentication (MFA) using time-based one-time passwords (TOTP).
Rationale: MFA adds an extra layer of security by requiring users to provide a second form of authentication, reducing the risk of unauthorized access even if credentials are compromised. TOTP is a widely supported and secure method for generating one-time passwords.
LOST view: Digital Solution Architecture Decisions Catalogue view
Identifier: http://data.europa.eu/dr8/egovera/AuthenticationMechanismGoal
EIRA traceability: eira:DigitalSolutionArchitectureDecisionGoal
ABB name: egovera:AuthenticationMechanismGoal
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-06-15
dct:identifier: ADR-20230515180947643
dct:title: Architecture Decision Record about Authentication Mechanism
eira:adr_context: The context explains why we need to make a decision. It also describes the alternatives along with the pros and cons.
eira:adr_decision: The decision describes the justification for why the particular solution was accepted. It has more emphasis on the why rather than the how.
eira:adr_status: [Proposed (under review)|Accepted (approved and ready for implementation)|Superseded (superseded by another decision)]
eira:adr_consecuences: The consequences section contains information about the overall impact of an architectural decision. Every decision has trade-offs. That’s why it’s crucial to include the analysis to provide a clear picture.
Definition: Architecture Decision Record from where you should specialise the ADR SBBs regarding the Microservices Architecture
Source: ISO/IEC/IEEE 42010:2022
Source reference: https://www.iso.org/standard/74393.html
Additional information: Microservices architecture decomposes an application into smaller, loosely coupled services. Each service is responsible for a specific functionality and can be developed, deployed, and scaled independently. Services communicate with each other through lightweight APIs or messaging protocols. This architecture enables flexibility, scalability, and easier maintenance, but it introduces complexities in managing distributed systems.
Example: Title: Microservices Architecture Decision Record (ADR)
LOST view: Digital Solution Architecture Decisions Catalogue view
Identifier: http://data.europa.eu/dr8/egovera/MicroserviceArchitectureGoal
EIRA traceability: eira:DigitalSolutionArchitectureDecisionGoal
ABB name: egovera:MicroserviceArchitectureGoal
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-20
dct:identifier: http://data.europa.eu/dr8/egovera/MicroserviceArchitectureGoal
dct:title: Architecture Decision Record about Microservices Architecture
eira:adr_context: The context explains why we need to make a decision. It also describes the alternatives along with the pros and cons.
eira:adr_decision: The decision describes the justification for why the particular solution was accepted. It has more emphasis on the why rather than the how.
eira:adr_status: [Proposed (under review)|Accepted (approved and ready for implementation)|Superseded (superseded by another decision)]
eira:adr_consecuences: The consequences section contains information about the overall impact of an architectural decision. Every decision has trade-offs. That’s why it’s crucial to include the analysis to provide a clear picture.
Definition: Digital Agenda ABB is a Goal that describes all the measures required or planned in a systematic way to support public policy in adopting the digital transformation.
Source: Inspired on the contents of the EU Digital Agenda
Source reference: https://www.europarl.europa.eu/factsheets/en/sheet/64/digital-agenda-for-europe
Additional information: Do not confuse Digital Agenda with Digitalisation Roadmap. An Agenda focuses on goals and priorities, e.g. protecting citizens and freedoms, developing a strong and vibrant economic base, building a climate-neutral, green, fair and social Europe, promoting European interests and values on the global stage, etc. A Roadmap focuses on the actions and deadlines that need to be executed to realise the Agenda.
Example: The following implementation is an example of how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): The Digital Agenda for Europe. See https://www.europarl.europa.eu/factsheets/en/sheet/64/digital-agenda-for-europe. The widespread, rapid and extensive development of digital service platforms, as well as debates on public data spaces and new technologies such as artificial intelligence, affect all areas of our society. Many new ways to communicate, shop or access information online have been integrated into our daily lives and are constantly evolving. The European digital agenda for the decade 2020-2030 addresses these issues by focusing on creating secure digital spaces and services, creating a level playing field in digital markets with large platforms and strengthening Europe’s digital sovereignty, while contributing to the European goal of climate neutrality by 2050.
IoP Dimension: Governance IoP
LOST view: Organisational view
Interoperability saliency: The Digital Agenda ABB is salient for governance interoperability since it establishes the main goals and priorities that the digital public services are expected to support (e.g., the overall aim of the Digital Agenda is to deliver sustainable economic and social benefits from a digital single market based on fast and ultra-fast internet and interoperable applications).
Identifier: http://data.europa.eu/dr8/DigitalAgendaGoal
eira:ID: ABB442
ABB name: eira:DigitalAgendaGoal
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2022-12-01
Definition: Architecture Decision Record from where you should specialise the ADR SBBs regarding the Replaceability
Source: ISO/IEC/IEEE 42010:2022
Source reference: https://www.iso.org/standard/74393.html
Additional information: Replaceability in software architecture refers to the design and characteristics of a software system that enable individual components or modules to be easily replaced or substituted without significant impact on the overall functionality or integrity of the system. An architecture that supports replaceability allows for seamless replacement of components to accommodate evolving requirements, technology advancements, or business needs.
Example: Title: Replaceability Architecture Decision Record (ADR)
LOST view: Digital Solution Architecture Decisions Catalogue view
Identifier: http://data.europa.eu/dr8/egovera/ReplaceabilityGoal
EIRA traceability: eira:DigitalSolutionArchitectureDecisionGoal
ABB name: egovera:ReplaceabilityGoal
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-07-06
dct:identifier: ADR-20230606091024772
dct:title: Architecture Decision Record about Replaceability
eira:adr_context: The context explains why we need to make a decision. It also describes the alternatives along with the pros and cons.
eira:adr_decision: The decision describes the justification for why the particular solution was accepted. It has more emphasis on the why rather than the how.
eira:adr_status: [Proposed (under review)|Accepted (approved and ready for implementation)|Superseded (superseded by another decision)]
eira:adr_consecuences: The consequences section contains information about the overall impact of an architectural decision. Every decision has trade-offs. That’s why it’s crucial to include the analysis to provide a clear picture.
Definition: Architecture Decision Record from where you should specialise the ADR SBBs regarding the Asynchronous Procesing
Source: ISO/IEC/IEEE 42010:2022
Source reference: https://www.iso.org/standard/74393.html
Additional information: Asynchronous Processing is a concept in IT architecture that involves executing tasks or processes independently of each other, without waiting for the completion of one task before starting another. This approach allows for greater efficiency and scalability, as multiple tasks can be executed simultaneously without causing delays or bottlenecks. Asynchronous processing is commonly used in web applications, where multiple users may be accessing the same system at the same time, and in distributed systems, where tasks may be spread across multiple servers or nodes. It is also used in event-driven architectures, where processes are triggered by specific events or messages. Overall, asynchronous processing is a key component of modern IT architectures, enabling faster, more efficient, and more scalable systems.
Example: Decision: Integrating Apache Kafka and Apache Spark for processing large volumes of data in near real-time.
Rationale: Kafka allows for the ingestion of high-volume data streams, while Spark provides a distributed processing framework for performing complex analytics and transformations on the data.
LOST view: Digital Solution Architecture Decisions Catalogue view
Identifier: http://data.europa.eu/dr8/egovera/AsynchronousProcesingGoal
EIRA traceability: eira:DigitalSolutionArchitectureDecisionGoal
ABB name: egovera:AsynchronousProcesingGoal
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-06-15
dct:identifier: ADR-20230515180947673
dct:title: Architecture Decision Record about Asynchronous Procesing
eira:adr_context: The context explains why we need to make a decision. It also describes the alternatives along with the pros and cons.
eira:adr_decision: The decision describes the justification for why the particular solution was accepted. It has more emphasis on the why rather than the how.
eira:adr_status: [Proposed (under review)|Accepted (approved and ready for implementation)|Superseded (superseded by another decision)]
eira:adr_consecuences: The consequences section contains information about the overall impact of an architectural decision. Every decision has trade-offs. That’s why it’s crucial to include the analysis to provide a clear picture.
Definition: Architecture Decision Record from where you should specialise the ADR SBBs regarding the Provide a Service Catalog
Source: ISO/IEC/IEEE 42010:2022
Source reference: https://www.iso.org/standard/74393.html
Additional information: The concept of Provide a Service Catalog in IT architecture decision-making involves creating a comprehensive list of all the services that an organization offers to its customers or clients. This catalog provides a clear and concise description of each service, including its features, benefits, and pricing. By having a service catalog, customers can easily find the services they need and understand what they are getting. It also helps organizations to manage their services more efficiently, prioritize their resources, and make informed decisions about service offerings. The service catalog can be made available online or in print, and it can be updated regularly to reflect changes in the organization's services.
Example: Decision: Chosen option: "Backstage", because we don't want to reimplement the tooling, we want something opensource and Backstage is now a CNCF project.
Rationale: As a transparent and open cloud we need a simple yet complete way of displaying services that are available on our platform, their current status, support path etc.
LOST view: Digital Solution Architecture Decisions Catalogue view
Identifier: http://data.europa.eu/dr8/egovera/ProvideAServiceCatalogGoal
EIRA traceability: eira:DigitalSolutionArchitectureDecisionGoal
ABB name: egovera:ProvideAServiceCatalogGoal
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-06-15
dct:identifier: ADR-20230515180947704
dct:title: Architecture Decision Record about Provide a Service Catalog
eira:adr_context: The context explains why we need to make a decision. It also describes the alternatives along with the pros and cons.
eira:adr_decision: The decision describes the justification for why the particular solution was accepted. It has more emphasis on the why rather than the how.
eira:adr_status: [Proposed (under review)|Accepted (approved and ready for implementation)|Superseded (superseded by another decision)]
eira:adr_consecuences: The consequences section contains information about the overall impact of an architectural decision. Every decision has trade-offs. That’s why it’s crucial to include the analysis to provide a clear picture.
Definition: Architecture Decision Record from where you should specialise the ADR SBBs regarding the Performance Testing and Tuning
Source: ISO/IEC/IEEE 42010:2022
Source reference: https://www.iso.org/standard/74393.html
Additional information: Performance testing and tuning is a decision of IT architecture that involves assessing the behavior of a system or application under different conditions and identifying areas where improvements can be made. This process helps to ensure that the system or application can handle the expected workload and provide a satisfactory user experience. Performance testing and tuning can involve a range of techniques, including load testing, stress testing, and capacity planning. It is an ongoing process that requires regular monitoring and adjustment to ensure optimal performance.
Example: Performance Testing and Tuning:
Decision: Conducting performance testing and tuning exercises regularly to identify bottlenecks and optimize system performance.
Rationale: Performance testing helps uncover performance issues and provides insights into system limitations, enabling public administrations to make informed decisions on infrastructure scaling, code optimization, and configuration adjustments to enhance performance.
LOST view: Digital Solution Architecture Decisions Catalogue view
Identifier: http://data.europa.eu/dr8/egovera/PerformanceTestingAndTuningGoal
EIRA traceability: eira:DigitalSolutionArchitectureDecisionGoal
ABB name: egovera:PerformanceTestingAndTuningGoal
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-06-15
dct:identifier: ADR-20230515180947440
dct:title: Architecture Decision Record about Performance Testing and Tuning
eira:adr_context: The context explains why we need to make a decision. It also describes the alternatives along with the pros and cons.
eira:adr_decision: The decision describes the justification for why the particular solution was accepted. It has more emphasis on the why rather than the how.
eira:adr_status: [Proposed (under review)|Accepted (approved and ready for implementation)|Superseded (superseded by another decision)]
eira:adr_consecuences: The consequences section contains information about the overall impact of an architectural decision. Every decision has trade-offs. That’s why it’s crucial to include the analysis to provide a clear picture.
Definition: Architecture Decision Record from where you should specialise the ADR SBBs regarding the Service-Oriented Architecture
Source: ISO/IEC/IEEE 42010:2022
Source reference: https://www.iso.org/standard/74393.html
Additional information: SOA is an architecture that focuses on organizing software systems as a collection of reusable services. These services are well-defined, self-contained modules that communicate with each other using standardized interfaces. SOA promotes interoperability, flexibility, and reusability of services across multiple applications.
Example: Title: Service-Oriented Architecture Decision Record (ADR)
LOST view: Digital Solution Architecture Decisions Catalogue view
Identifier: http://data.europa.eu/dr8/egovera/Service-OrientedArchitectureGoal
EIRA traceability: eira:DigitalSolutionArchitectureDecisionGoal
ABB name: egovera:Service-OrientedArchitectureGoal
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-20
dct:identifier: http://data.europa.eu/dr8/egovera/Service-OrientedArchitectureGoal
dct:title: Architecture Decision Record about Service-Oriented Architecture
eira:adr_context: The context explains why we need to make a decision. It also describes the alternatives along with the pros and cons.
eira:adr_decision: The decision describes the justification for why the particular solution was accepted. It has more emphasis on the why rather than the how.
eira:adr_status: [Proposed (under review)|Accepted (approved and ready for implementation)|Superseded (superseded by another decision)]
eira:adr_consecuences: The consequences section contains information about the overall impact of an architectural decision. Every decision has trade-offs. That’s why it’s crucial to include the analysis to provide a clear picture.
Definition: Architecture Decision Record from where you should specialise the ADR SBBs regarding the Event-Driven Architecture
Source: ISO/IEC/IEEE 42010:2022
Source reference: https://www.iso.org/standard/74393.html
Additional information: Event-Driven Architecture (EDA) is a software architecture pattern that emphasizes the production, detection, consumption, and reaction to events that occur within a system. It is a distributed computing model that allows for the creation of loosely coupled systems, where components can communicate with each other without the need for direct integration. EDA is particularly useful in systems that require real-time processing and decision-making, such as financial trading systems, sensor networks, and IoT applications. The key benefits of EDA include scalability, flexibility, and agility, as well as the ability to respond quickly to changing business requirements.
Example: Event-Driven Architecture:
Decision: Implementing an event-driven architecture using Apache Kafka for asynchronous communication between microservices.
Rationale: Event-driven architectures enable loose coupling, scalability, and fault tolerance. Kafka provides a distributed messaging system with high throughput and fault-tolerant message persistence.
LOST view: Digital Solution Architecture Decisions Catalogue view
Identifier: http://data.europa.eu/dr8/egovera/Event-DrivenArchitectureGoal
EIRA traceability: eira:DigitalSolutionArchitectureDecisionGoal
ABB name: egovera:Event-DrivenArchitectureGoal
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-06-15
dct:identifier: ADR-20230515180947546
dct:title: Architecture Decision Record about Event-Driven Architecture
eira:adr_context: The context explains why we need to make a decision. It also describes the alternatives along with the pros and cons.
eira:adr_decision: The decision describes the justification for why the particular solution was accepted. It has more emphasis on the why rather than the how.
eira:adr_status: [Proposed (under review)|Accepted (approved and ready for implementation)|Superseded (superseded by another decision)]
eira:adr_consecuences: The consequences section contains information about the overall impact of an architectural decision. Every decision has trade-offs. That’s why it’s crucial to include the analysis to provide a clear picture.
Definition: Architecture Decision Record from where you should specialise the ADR SBBs regarding the API Design
Source: ISO/IEC/IEEE 42010:2022
Source reference: https://www.iso.org/standard/74393.html
Additional information: API design is a crucial aspect of IT architecture decision-making, as it determines how different software systems and applications communicate with each other. A well-designed API can improve the efficiency and effectiveness of software development, as it allows developers to easily integrate different systems and functionalities. On the other hand, a poorly designed API can lead to compatibility issues, security vulnerabilities, and other problems that can hinder the development process. Therefore, IT architects must carefully consider the design of APIs when making decisions about software development and integration. This includes factors such as the format and structure of the API, the security measures in place, and the ease of use for developers.
Example: One example of the application of the Directive 2014/24/EU is in the procurement of construction services for a new public building. The directive requires that the procurement process be open, transparent, and non-discriminatory, with equal opportunities for all potential bidders. The contracting authority must publish a notice of the procurement in the Official Journal of the European Union, and provide all relevant information to interested parties. The directive also requires that the contracting authority evaluate bids based on objective criteria, and award the contract to the most economically advantageous tender. This ensures that public funds are used efficiently and effectively, and that the public receives high-quality services at a fair price.
LOST view: Digital Solution Architecture Decisions Catalogue view
Identifier: http://data.europa.eu/dr8/egovera/APIDesignGoal
EIRA traceability: eira:DigitalSolutionArchitectureDecisionGoal
ABB name: egovera:APIDesignGoal
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-06-15
dct:identifier: ADR-20230515180947613
dct:title: Architecture Decision Record about API Design
eira:adr_context: The context explains why we need to make a decision. It also describes the alternatives along with the pros and cons.
eira:adr_decision: The decision describes the justification for why the particular solution was accepted. It has more emphasis on the why rather than the how.
eira:adr_status: [Proposed (under review)|Accepted (approved and ready for implementation)|Superseded (superseded by another decision)]
eira:adr_consecuences: The consequences section contains information about the overall impact of an architectural decision. Every decision has trade-offs. That’s why it’s crucial to include the analysis to provide a clear picture.
Definition: Architecture Decision Record from where you should specialise the ADR SBBs regarding the Cloud-Native Architecture
Source: ISO/IEC/IEEE 42010:2022
Source reference: https://www.iso.org/standard/74393.html
Additional information: Cloud-native architecture is designed specifically for cloud environments, leveraging cloud computing capabilities and services. It emphasizes scalability, fault tolerance, and the use of containerization and orchestration tools like Docker and Kubernetes. Cloud-native applications are typically built using microservices and take advantage of cloud services such as storage, databases, and messaging queues.
Example: Title: Cloud-Native Architecture Decision Record (ADR)
LOST view: Digital Solution Architecture Decisions Catalogue view
Identifier: http://data.europa.eu/dr8/egovera/Cloud-NativeArchitectureGoal
EIRA traceability: eira:DigitalSolutionArchitectureDecisionGoal
ABB name: egovera:Cloud-NativeArchitectureGoal
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-20
dct:identifier: http://data.europa.eu/dr8/egovera/Cloud-NativeArchitectureGoal
dct:title: Architecture Decision Record about Cloud-Native Architecture
eira:adr_context: The context explains why we need to make a decision. It also describes the alternatives along with the pros and cons.
eira:adr_decision: The decision describes the justification for why the particular solution was accepted. It has more emphasis on the why rather than the how.
eira:adr_status: [Proposed (under review)|Accepted (approved and ready for implementation)|Superseded (superseded by another decision)]
eira:adr_consecuences: The consequences section contains information about the overall impact of an architectural decision. Every decision has trade-offs. That’s why it’s crucial to include the analysis to provide a clear picture.
Definition: Architecture Decision Record from where you should specialise the ADR SBBs regarding the Cross-Border Data Exchange
Source: ISO/IEC/IEEE 42010:2022
Source reference: https://www.iso.org/standard/74393.html
Additional information: Cross-border data exchange is a concept that refers to the transfer of data between different countries or regions. This can be done for various reasons, such as sharing information between businesses, governments, or individuals. The concept of cross-border data exchange is becoming increasingly important in today's globalized world, as more and more organizations are operating across borders and need to share information with partners and customers in different countries. However, there are also challenges associated with cross-border data exchange, such as data privacy and security concerns, legal and regulatory issues, and technical compatibility issues. Therefore, it is important for organizations to carefully consider the IT architecture decisions related to cross-border data exchange and ensure that they have appropriate policies, procedures, and technologies in place to manage these challenges effectively.
Example: Decision: The Data Consumer and Data Provider rely on the Data Exchange Manager capability.
Consequence: New capability: Evidence Data Management
LOST view: Digital Solution Architecture Decisions Catalogue view
Identifier: http://data.europa.eu/dr8/egovera/Cross-BorderDataExchangeGoal
EIRA traceability: eira:DigitalSolutionArchitectureDecisionGoal
ABB name: egovera:Cross-BorderDataExchangeGoal
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-06-15
dct:identifier: ADR-20230515180947774
dct:title: Architecture Decision Record about Cross-Border Data Exchange
eira:adr_context: The context explains why we need to make a decision. It also describes the alternatives along with the pros and cons.
eira:adr_decision: The decision describes the justification for why the particular solution was accepted. It has more emphasis on the why rather than the how.
eira:adr_status: [Proposed (under review)|Accepted (approved and ready for implementation)|Superseded (superseded by another decision)]
eira:adr_consecuences: The consequences section contains information about the overall impact of an architectural decision. Every decision has trade-offs. That’s why it’s crucial to include the analysis to provide a clear picture.
Definition: Architecture Decision Record from where you should specialise the ADR SBBs regarding the Cross-Border Identification Business
Source: ISO/IEC/IEEE 42010:2022
Source reference: https://www.iso.org/standard/74393.html
Additional information: The Cross-Border Identification Business concept refers to the process of identifying individuals across different countries or regions. This is particularly important in industries such as finance, healthcare, and travel, where individuals may need to be identified and verified across borders. The IT architecture decision for this concept involves selecting the appropriate technologies and systems to enable secure and efficient cross-border identification, such as biometric identification, digital identity verification, and blockchain-based identity management systems. The decision also involves considering regulatory and legal requirements for cross-border identification, as well as privacy and data protection concerns.
Example: Rationale: As a transparent and open cloud we need a simple yet complete way of displaying services that are available on our platform, their current status, support path etc.
LOST view: Digital Solution Architecture Decisions Catalogue view
Identifier: http://data.europa.eu/dr8/egovera/Cross-BorderIdentificationBusinessGoal
EIRA traceability: eira:DigitalSolutionArchitectureDecisionGoal
ABB name: egovera:Cross-BorderIdentificationBusinessGoal
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-06-15
dct:identifier: ADR-20230515180947478
dct:title: Architecture Decision Record about Cross-Border Identification Business
eira:adr_context: The context explains why we need to make a decision. It also describes the alternatives along with the pros and cons.
eira:adr_decision: The decision describes the justification for why the particular solution was accepted. It has more emphasis on the why rather than the how.
eira:adr_status: [Proposed (under review)|Accepted (approved and ready for implementation)|Superseded (superseded by another decision)]
eira:adr_consecuences: The consequences section contains information about the overall impact of an architectural decision. Every decision has trade-offs. That’s why it’s crucial to include the analysis to provide a clear picture.
Definition: Architecture Decision Record from where you should specialise the ADR SBBs regarding the Database Schema Design
Source: ISO/IEC/IEEE 42010:2022
Source reference: https://www.iso.org/standard/74393.html
Additional information: Database Schema Design is an important decision in IT architecture that involves creating a logical representation of the database structure. It involves defining the tables, columns, relationships, and constraints that make up the database. The schema design should be optimized for the specific needs of the application and should be flexible enough to accommodate future changes. A well-designed schema can improve performance, reduce data redundancy, and ensure data integrity. It is important to consider factors such as scalability, security, and data access when making database schema design decisions.
Example: Database Schema Design:
Decision: Utilizing a denormalized schema design for a reporting database to optimize query performance.
Rationale: Denormalizing the schema reduces the need for joins and improves query performance for reporting and analytics use cases, at the expense of increased data redundancy.
LOST view: Digital Solution Architecture Decisions Catalogue view
Identifier: http://data.europa.eu/dr8/egovera/DatabaseSchemaDesignGoal
EIRA traceability: eira:DigitalSolutionArchitectureDecisionGoal
ABB name: egovera:DatabaseSchemaDesignGoal
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-06-15
dct:identifier: ADR-20230515180947754
dct:title: Architecture Decision Record about Database Schema Design
eira:adr_context: The context explains why we need to make a decision. It also describes the alternatives along with the pros and cons.
eira:adr_decision: The decision describes the justification for why the particular solution was accepted. It has more emphasis on the why rather than the how.
eira:adr_status: [Proposed (under review)|Accepted (approved and ready for implementation)|Superseded (superseded by another decision)]
eira:adr_consecuences: The consequences section contains information about the overall impact of an architectural decision. Every decision has trade-offs. That’s why it’s crucial to include the analysis to provide a clear picture.
Definition: Architecture Decision Record from where you should specialise the ADR SBBs regarding the Load Balancing Strategy
Source: ISO/IEC/IEEE 42010:2022
Source reference: https://www.iso.org/standard/74393.html
Additional information: Load balancing strategy is a decision in IT architecture that involves distributing network traffic across multiple servers to ensure optimal performance, availability, and scalability. The strategy involves selecting the appropriate load balancing algorithm, such as round-robin, least connections, or IP hash, based on the specific needs of the application and infrastructure. The load balancer acts as a traffic cop, directing incoming requests to the most available and responsive server, reducing downtime, and improving user experience. The load balancing strategy also involves monitoring and analyzing traffic patterns, adjusting server capacity, and implementing failover mechanisms to ensure high availability and fault tolerance.
Example: Load Balancing Strategy:
Decision: Implementing a load balancing mechanism, such as round-robin or dynamic load balancing, to distribute incoming traffic across multiple servers.
Rationale: Load balancing ensures that incoming requests are evenly distributed among servers, preventing any single server from becoming overwhelmed and maintaining consistent performance under high loads.
LOST view: Digital Solution Architecture Decisions Catalogue view
Identifier: http://data.europa.eu/dr8/egovera/LoadBalancingStrategyGoal
EIRA traceability: eira:DigitalSolutionArchitectureDecisionGoal
ABB name: egovera:LoadBalancingStrategyGoal
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-06-15
dct:identifier: ADR-20230515180947508
dct:title: Architecture Decision Record about Load Balancing Strategy
eira:adr_context: The context explains why we need to make a decision. It also describes the alternatives along with the pros and cons.
eira:adr_decision: The decision describes the justification for why the particular solution was accepted. It has more emphasis on the why rather than the how.
eira:adr_status: [Proposed (under review)|Accepted (approved and ready for implementation)|Superseded (superseded by another decision)]
eira:adr_consecuences: The consequences section contains information about the overall impact of an architectural decision. Every decision has trade-offs. That’s why it’s crucial to include the analysis to provide a clear picture.
Definition: Interoperable Digital Solution ABB is a Goal that refers to a digital public service that can work seamlessly with other public services, systems and data across organisational and national boundaries
Source: ISA2
Source reference: https://ec.europa.eu/isa2/eif_en/
eira:iopDimension: Structural IoP
LOST view: Enterprise Architecture Framework alignment guidelines view
Identifier: http://data.europa.eu/dr8/InteroperableEuropeanSolutionGoal
ABB name: eira:InteroperableEuropeanSolutionGoal
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-04-24
dct:identifier: http://data.europa.eu/dr8/InteroperableEuropeanSolutionGoal
Definition: The European Data Sharing Principles are a set of guidelines established by the European Union to promote the responsible and secure sharing of data among organizations. These principles aim to foster innovation, maximize the value of data, and ensure privacy and data protection.
Source: European Commission
Source reference: https://ec.europa.eu/
Additional information: The European Data Sharing Principles were developed in alignment with the General Data Protection Regulation (GDPR) and other relevant data protection laws. They emphasize the importance of transparency, legal compliance, and accountability when sharing data. The principles encourage organizations to adopt fair and non-discriminatory data sharing practices, implement appropriate security measures, and establish clear governance frameworks for data sharing initiatives. By following these principles, the European Union seeks to create a data-sharing ecosystem that benefits both businesses and individuals while maintaining high standards of data protection.
Example: An example application of the European Data Sharing Principles is a consortium of healthcare providers sharing anonymized patient data for medical research purposes. The principles ensure that the data is handled securely and in compliance with data protection laws. The healthcare providers implement technical measures to de-identify the data, establish data access controls, and define data usage agreements. Researchers can then access the shared data for scientific studies while protecting patient privacy and maintaining the trust of the individuals whose data is being shared.
eira:iopDimension: Governance IoP
LOST view: Architecture Principles view
eira:iopSaliency: Interoperability is a key aspect of the European Data Sharing Principles. It ensures that data can be effectively shared and utilized across different systems, organizations, and sectors. By promoting interoperability, the principles aim to break down data silos, facilitate data exchange, and foster collaboration. This interoperability saliency enables seamless integration and analysis of diverse datasets, leading to enhanced decision-making, innovation, and societal benefits.
Identifier: http://data.europa.eu/dr8/egovera/EuropeanDataSharingPrinciplesPrinciple
ABB name: egovera:EuropeanDataSharingPrinciplesPrinciple
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-07-07
dct:identifier: http://data.europa.eu/dr8/egovera/EuropeanDataSharingPrinciplesPrinciple
Description: The European Data Sharing principle of consumer protection aims to safeguard the rights and interests of individuals when their personal data is shared. It ensures that individuals have control over their data, are informed about how it will be used, and have the ability to exercise their rights regarding data protection.
Additional information: Consumer protection is a fundamental aspect of data sharing in the European Union. It is based on the principles outlined in the General Data Protection Regulation (GDPR) and other relevant legislation. The principle emphasizes the importance of transparency, consent, purpose limitation, data minimization, accuracy, storage limitation, integrity, and confidentiality in protecting the rights of individuals. It also highlights the need for organizations to implement appropriate security measures and provide individuals with mechanisms to exercise their rights, such as the right to access, rectify, and erase their personal data.
Example: An example of the application of consumer protection in data sharing is when a company collects personal data from its customers for marketing purposes. The company must inform the customers about the specific purposes for which their data will be used, obtain their explicit consent, and provide them with the option to opt-out of such data sharing. Additionally, the company must ensure the security and confidentiality of the data and allow customers to access, correct, or delete their personal information upon request.
Publisher: European Union
Source: https://edpb.europa.eu/
LOST view: Architecture Principles view
Identifier: http://data.europa.eu/dr8/egovera/ConsumerProtectionPrinciple
EIRA traceability: eira:ArchitecturePrinciple
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-07-07
dct:identifier: http://data.europa.eu/dr8/egovera/ConsumerProtectionPrinciple
dct:title: Consumer protection
Description: The subsidiarity principle requires EU decisions to be taken as closely as possible by the citizen.
Publisher: ELAP
Source: Subsidiarity and proportionality Underlying Principle (1) of the European Interoperability Framework (EIF)
Last modification: 2024-01-11
Identifier: http://data.europa.eu/2sa/elap/subsidiarity-and-proportionality
EIRA traceability: eira:EuropeanLibraryofArchitecturePrinciplesPrinciple
EIRA concept: eira:SolutionBuildingBlock
Additional identifier: elap:SubsidiarityAndProportionalityPrinciple
Title: Subsidiarity and proportionality
EIF Layer: N/A
Description: The principle of Fair Competition in European Data Sharing ensures that all participants have equal opportunities and are subject to the same rules and regulations when accessing and utilizing shared data. It promotes a level playing field for businesses and organizations, preventing unfair advantages or monopolistic practices.
Additional information: Fair Competition is a fundamental principle in the European Data Sharing framework, aiming to foster innovation, encourage market diversity, and prevent anti-competitive behavior. It ensures that data sharing practices do not lead to the creation of monopolies or unfair market advantages for certain entities. By promoting fair competition, the European Union aims to create an environment that benefits both businesses and consumers, fostering economic growth and innovation.
Example: An example of the application of Fair Competition in European Data Sharing is when a data-sharing platform provides equal access to all participants, regardless of their size or market position. This ensures that startups and smaller businesses have the same opportunities as larger corporations to utilize shared data for product development, market analysis, or improving their services. Additionally, Fair Competition principles may include regulations to prevent data monopolies or anti-competitive behavior, such as prohibiting exclusive data-sharing agreements that limit access for certain competitors.
Publisher: European Commission
Source: https://ec.europa.eu/info/strategy/priorities-2019-2024/europe-fit-digital-age/european-data-strategy_en
LOST view: Architecture Principles view
Identifier: http://data.europa.eu/dr8/egovera/FairCompetitionPrinciple
EIRA traceability: eira:ArchitecturePrinciple
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-07-07
dct:identifier: http://data.europa.eu/dr8/egovera/FairCompetitionPrinciple
dct:title: Fair Competition
Description: Ensuring availability of interfaces with internal information systems.
Publisher: ELAP
Source: Transparency Underlying Principle (3) of the European Interoperability Framework (EIF)
Last modification: 2023-11-20
Identifier: http://data.europa.eu/2sa/elap/transparency-of-internal-information-systems
EIRA traceability: eira:EuropeanLibraryofArchitecturePrinciplesPrinciple
LOST view: TVA-Functional Architecture Principles
EIRA concept: eira:SolutionBuildingBlock
Additional identifier: elap:transparency-of-internal-information-systems
Title: Transparency of internal information systems
Additional information: Public administrations operate a large number of what are often heterogeneous and disparate information systems in support of their internal processes. Interoperability depends on ensuring the availability of interfaces to these systems and the data they handle. In turn, interoperability facilitates the reuse of systems and data and enables these to be integrated into larger systems.
The European Interoperability Framework is part of the Communication (COM(2017)134) from the European Commission adopted on 23 March 2017. The framework gives specific guidance on how to set up interoperable digital public services.
EIF Layer: N/A
Description: Data and metadata availability through standardised mechanism and ensure its long-term availability
Publisher: ELAP
Source: FAIR Principles
Last modification: 2023-11-20
Identifier: http://data.europa.eu/2sa/elap/data-accessibility
EIRA traceability: eira:EuropeanLibraryofArchitecturePrinciplesPrinciple
LOST view: TVA-Functional Architecture Principles
EIRA concept: eira:SolutionBuildingBlock
Additional identifier: elap:data-accessibility
Title: Data Accessibility
EIF Layer: N/A
Definition: Security by design refers to one of the prime principles found in any standard and in any practice throughout the whole of IT.
Source: https://joinup.ec.europa.eu/collection/nifo-national-interoperability-framework-observatory/2-underlying-principles-european-public-services#2.4
Additional information: Security by design encompasses the protection of valuable assets, by securing them safely within the boundaries of organizations, taking into account the ownership of the assets. This means that in any circumstance, one has to attend to the valuable property, being 'data' and 'technology' as a whole, both by securing access to (data)assets and by securing the proliferation of data(assets) outside the boundaries, for which one is responsible.
Security by design (or secure by design), sometimes abbreviated “SbD,” is a new industry term for a range of security practices built on one fundamental idea — that security should be built into a product by design, instead of being added on later by third-party products and services.
The European Interoperability Framework is part of the Communication (COM(2017)134) from the European Commission adopted on 23 March 2017. The framework gives specific guidance on how to set up interoperable digital public services.
LOST view: TVA-Functional Architecture Principles
Identifier: http://data.europa.eu/2sa/elap/security-design
ABB name: elap:security-design
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-17
Name: Security by Design
Interoperability Layer: N/A
Specialises: http://data.europa.eu/dr8/EuropeanLibraryofArchitecturePrinciplesPrinciple
Description: Data Altruism is a principle of European Data Sharing that promotes the voluntary sharing of data for the common good. It encourages individuals and organizations to share their data with the aim of benefiting society as a whole, rather than for personal or commercial gain.
Additional information: Data Altruism emphasizes the importance of sharing data in a responsible and ethical manner. It encourages data owners to consider the potential societal impact of their data and make it available for research, innovation, and public interest purposes. By promoting data altruism, the European Union aims to foster collaboration, innovation, and the development of data-driven solutions to address societal challenges.
Example: An example of data altruism is when a healthcare organization shares anonymized patient data with researchers to improve medical treatments and find new cures. By voluntarily sharing this data, the organization contributes to the advancement of medical knowledge and benefits society as a whole.
Publisher: European Commission
Source: https://ec.europa.eu/info/strategy/priorities-2019-2024/europe-fit-digital-age/european-data-strategy_en
LOST view: Architecture Principles view
Identifier: http://data.europa.eu/dr8/egovera/DataAltruismPrinciple
EIRA traceability: eira:ArchitecturePrinciple
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-07-07
dct:identifier: http://data.europa.eu/dr8/egovera/DataAltruismPrinciple
dct:title: Data Altruism
Definition: Architecture Principle ABB is a Principle that enables general rules and guidelines for the use and deployment of all IT resources and assets across the enterprise.
Source: TOGAF 9.2 The Open Group
Source reference: https://pubs.opengroup.org/architecture/togaf9-doc/arch/chap20.html#:~:text=Architecture%20Principles%20define%20the%20underlying,for%20making%20future%20IT%20decisions
Additional information: The architecture Principle reflects the level of consensus among the various elements of the enterprise, and form the basis for making future IT decisions.
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): The European Innovation Partnership on Smart Cities and Communities (EIP SCC) is a stakeholder driven initiative stimulated and supported by the European Commission. The EIP SCC has defined key priority areas which will be addressed including the architecture principle of Capabilities. Capabilities are the center element of the architectures to ensure that a common ground is easy to be found.(https://ec.europa.eu/research/participants/documents/downloadPublic?documentIds=080166e5b9a18c76&appId=PPGMS)
eira:iopDimension: Governance IoP
LOST view: OV-Data Spaces
eira:iopSaliency: The Architecture Principle ABB is salient for governance interoperability due to it lays the architectural framework to elaborate public services. Also, the Architecture Principle ABB is salient for organizational interoperability due to it establishes the requirements to sustain the business processes for enabling public services to exchange data.
Identifier: http://data.europa.eu/dr8/ArchitecturePrinciple
ABB name: eira:ArchitecturePrinciple
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2022-01-23
dct:identifier: http://data.europa.eu/dr8/ArchitecturePrinciple
Description: Organisations are loosely coupled with other organisations.
Publisher: ELAP
Source: Organizations Social Systems Conducting Experiments
Last modification: 2023-11-20
Identifier: http://data.europa.eu/2sa/elap/loosely-coupled-integration
EIRA traceability: eira:EuropeanLibraryofArchitecturePrinciplesPrinciple
LOST view: TVA-Functional Architecture Principles
EIRA concept: eira:SolutionBuildingBlock
Additional identifier: elap:loosely-coupled-integration
Title: Loosely coupled integration
EIF Layer: N/A
Description: Decide early on the type of deployment: On-premise, vs. Cloud-native and sourcing models IaaS, PaaS, SaaS, etc
Publisher: ELAP
Source: EUROPEAN COMMISSION CLOUD STRATEGY Cloud as an enabler for the European Commission Digital Strategy
Last modification: 2023-11-20
Identifier: http://data.europa.eu/2sa/elap/deployment-fit-cloud-first-approach
EIRA traceability: eira:EuropeanLibraryofArchitecturePrinciplesPrinciple
LOST view: Architecture Principles view
EIRA concept: eira:SolutionBuildingBlock
Additional identifier: elap:deployment-fit-cloud-first-approach
Title: Deployment fit (Cloud-first approach)
Additional information: It is relevant for the success of Digital Public Services to select the deployment methodologies that fit the needs of the administration and stakeholders (citizens and businesses).
European Commission cloud strategy: "Cloud-first with a secure hybrid multi-cloud service offering". Cloud-first means that systems should rather be conceived in such a way that they can benefit from the advantages of cloud based delivery models, which exist both on premise and in the public cloud. The choice of architecture, especially of on premise and/or public cloud, will depend on the advantages, constraints and risks for a specific system. So it does not mean that all systems should go to the public cloud.
EIF Layer: N/A
Description: Ensure the evolution of society and eGovernment by implementing means for the achievement of the purpose, specifically for inclusion and equitative public service, resilience towards crises and efficient and effective innovation.
Publisher: ELAP
Source: \"The neo-Weberian state: From ideal type model to reality?\" by UCL Institute for Innovation and Public Purpose
Last modification: 2023-11-20
Identifier: http://data.europa.eu/2sa/elap/neo-weberian-state-approach
EIRA traceability: eira:EuropeanLibraryofArchitecturePrinciplesPrinciple
LOST view: TVA-Governance Architecture Principles
EIRA concept: eira:SolutionBuildingBlock
Additional identifier: elap:neo-weberian-state-approach
Title: Neo-Weberian-State approach (NWS)
Additional information: NWS is a hierarchy-driven system within a hierarchy-market-network space. This NWS (based and driven by hierarchy) then moved to one of the normative reform models.
The Neo-Weberian-State approach is focused an aimed to ensure three main core principles, that are specifically relevant to the development of eGovernment and societies: inclusive and equitable service delivery, resilient crises governance, and effective innovation for government and society.
The application of the principle or the work towards the approach is a key enabler for digital and healthy societies, where users and the overall society is taken into account, and put on the focus on the development of Digital Public Services.
The UCL Institute for Innovation and Public Purpose is focused on the development and research of how digital platforms and services can improve societies.
EIF Layer: N/A
Description: The principle of self-determination in European Data Sharing emphasizes the individual's right to control their personal data and make informed decisions about its collection, use, and disclosure. It recognizes that individuals should have the autonomy to determine how their data is shared and used by others.
Additional information: Self-determination is a fundamental aspect of data protection and privacy rights. It ensures that individuals have the ability to exercise control over their personal data, including the right to provide or withhold consent for data processing activities. This principle is enshrined in various European data protection laws, such as the General Data Protection Regulation (GDPR), which grants individuals the right to be informed, access, rectify, and erase their personal data. Self-determination also includes the right to object to data processing, restrict processing, and the right to data portability.
Example: An example of self-determination in practice is when an individual is presented with clear and understandable choices regarding the collection and use of their personal data. For instance, a website may provide options for users to opt-in or opt-out of certain data processing activities, such as targeted advertising or sharing data with third parties. By giving individuals the ability to exercise their self-determination, they can make informed decisions about their data and protect their privacy.
Publisher: European Union
Source: https://edpb.europa.eu/
LOST view: Architecture Principles view
Identifier: http://data.europa.eu/dr8/egovera/SelfDeterminationPrinciple
EIRA traceability: eira:ArchitecturePrinciple
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-07-07
dct:identifier: http://data.europa.eu/dr8/egovera/SelfDeterminationPrinciple
dct:title: Self Determination
Description: The implementation of digital public services has a focus on integration, technology, governance or legal.
Publisher: ELAP
Source: COM(2017) 134 final ANNEX 2 COMMUNICATION FROM THE COMMISSION TO THE EUROPEAN PARLIAMENT, THE COUNCIL, THE EUROPEAN ECONOMIC AND SOCIAL COMMITTEE AND THE COMMITTEE OF THE REGIONS European Interoperability Framework - Implementation Strategy
Last modification: 2023-11-20
Identifier: http://data.europa.eu/2sa/elap/best-fit-public-service-implementation-orientation
EIRA traceability: eira:EuropeanLibraryofArchitecturePrinciplesPrinciple
LOST view: OV-Governance Architecture Principles
EIRA concept: eira:SolutionBuildingBlock
Additional identifier: elap:best-fit-public-service-implementation-orientation
Title: Best fit Public Service Implementation Orientation
Additional information: Experience shows that a focused approach is a critical success factor in the implementation of digital public services.
EUR-Lex is your online gateway to EU Law. It provides the official and most comprehensive access to EU legal documents. It is available in all of the EU’s 24 official languages and is updated daily
EIF Layer: N/A
Description: Accessibility ensures that people with disabilities, the elderly and other disadvantaged groups can use public services at service levels comparable to those provided to other citizens.
Publisher: ELAP
Source: https://joinup.ec.europa.eu/collection/nifo-national-interoperability-framework-observatory/glossary/term/inclusion-and-accessibility
Last modification: 2024-01-11
Identifier: http://data.europa.eu/2sa/elap/accessibility
EIRA traceability: eira:EuropeanLibraryofArchitecturePrinciplesPrinciple
EIRA concept: eira:SolutionBuildingBlock
Additional identifier: elap:AccessibilityPrinciple
Title: Accessibility
EIF Layer: N/A
Description: Enabling visibility inside the administrative environment of a public administration.
Publisher: ELAP
Source: Transparency Underlying Principle (3) of the European Interoperability Framework (EIF)
Last modification: 2023-11-20
Identifier: http://data.europa.eu/2sa/elap/transparency-of-the-administrative-environment
EIRA traceability: eira:EuropeanLibraryofArchitecturePrinciplesPrinciple
LOST view: SV-Functional Architecture Principles
EIRA concept: eira:SolutionBuildingBlock
Additional identifier: elap:transparency-of-the-administrative-environment
Title: Transparency of the administrative environment
EIF Layer: N/A
Definition: EU Localisation Framework compliance refers to digital public services being compliant and implementing the INSPIRE directive and the different requirements stated in the regulation. The EU Localisation Framework concept consists of a package of case studies, specifications, guidelines, training materials, recommendations and actions required by public administrations and stakeholder communities to facilitate the implementation, use and expansion of INSPIRE in an e-government context. Public Administrations and stakeholders need to follow the different guidelines, implement the specifications and foster training for the understanding of INSPIRE directive.
Source: European Union Location Framework (EULF)
Source reference: https://inspire.ec.europa.eu/eulf/31
LOST view: TVA-Functional Architecture Principles
Identifier: http://data.europa.eu/2sa/elap/eu-localisation-framework-compliance
ABB name: elap:eu-localisation-framework-compliance
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-17
Name: EU Localisation Framework compliance
Interoperability Layer: N/A
Specialises: eira:EuropeanLibraryofArchitecturePrinciplesPrinciple
Description: Signifies the agreement to the processing of personal data related to an individual
Additional information: Privacy refers to any freely given, specific, informed and unambiguous indication of the data subject's wishes by which he or she, by a statement or by clear affirmative action, signifies agreement to the processing of personal data relating to him or her.
Additionally, it refers to ensuring that the vast amounts of citizens' personal data held and processed by public bodies are protected by complying with the applicable legal framework.
A relevant aspect to consider when focusing on the application of privacy is full compliance with GDPR Regulation.
The European Interoperability Framework is part of the Communication (COM(2017)134) from the European Commission adopted on 23 March 2017. The framework gives specific guidance on how to set up interoperable digital public services.
Publisher: ELAP
Source: https://joinup.ec.europa.eu/collection/nifo-national-interoperability-framework-observatory/2-underlying-principles-european-public-services#2.4
LOST view: TVA-Functional Architecture Principles
Identifier: http://data.europa.eu/2sa/elap/privacy
EIRA traceability: eira:EuropeanLibraryofArchitecturePrinciplesPrinciple
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-06-27
dct:identifier: elap:privacy
dct:title: Privacy
Description: European digital public services are multilingual."@en, "European public services can potentially be used by anyone in any Member State. So multilingualism needs to be carefully considered when designing them. Citizens across Europe often have problems accessing and using digital public services if these are not available in the languages they speak.
Publisher: ELAP
Source: Multilingualism Underlying Principle (9) of the European Interoperability Framework (EIF)
Last modification: 2024-01-11
Identifier: http://data.europa.eu/2sa/elap/multilingualism
EIRA traceability: eira:EuropeanLibraryofArchitecturePrinciplesPrinciple
EIRA concept: eira:SolutionBuildingBlock
Additional identifier: elap:MultilingualismPrinciple
Title: Multilingualism
EIF Layer: N/A
Definition: Records are preserved and made long-term accessible. Legislation requires that decisions and data are stored and can be accessed for a specified time. This includes all data and information in the electronic form held by public administrations for the purpose of documenting procedures and decisions. The goal is to ensure that records and other forms of information keep their legibility, reliability and integrity and can be accessed as long as needed subject to security and privacy provisions.
Source: Preservation of information Underlying Principle (12) of the European Interoperability Framework (EIF)
Source reference: https://joinup.ec.europa.eu/collection/nifo-national-interoperability-framework-observatory/2-underlying-principles-european-public-services#2.12
Identifier: http://data.europa.eu/2sa/elap/preservation-information
ABB name: elap:PreservationOfInformationPrinciple
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-17
Name: Preservation of information
Interoperability Layer: N/A
Specialises: eira:EuropeanLibraryofArchitecturePrinciplesPrinciple
Description: The design and implementation of sufficient mechanisms to attain full visibility on the effective realisation of public services, based on public policies, by putting in place processes and procedures that provide accountability to stakeholders.
Publisher: ELAP
Source: Assessment of Effectiveness and Efficiency Underlying Principle (12) of the European Interoperability Framework (EIF)
Last modification: 2024-01-11
Identifier: http://data.europa.eu/2sa/elap/convergence-control-public-policy-goals-attainment
EIRA traceability: eira:EuropeanLibraryofArchitecturePrinciplesPrinciple
EIRA concept: eira:SolutionBuildingBlock
Additional identifier: elap:ConvergenceControlOnPublicPolicyGoalsAttainmentPrinciple
Title: Convergence control on public policy goals attainment
EIF Layer: N/A
Definition: EIF Principle ABB is a Principle analysing European Public Services by driving the identification and formulation of interoperability requirements with higher levels of granularity and used to design European public services by driving the identification and formulation of interoperability specifications
Source: EIF
Source reference: https://ec.europa.eu/isa2/eif_en
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): Transparency: EIF Transparency Principle refers to: 1. Enabling visibility inside the administrative environment of a public administration. This is about allowing other public administrations, citizens and businesses to view and understand administrative rules, processes, data, services and decision-making. 2. Ensuring availability of interfaces with internal information systems. Public administrations operate a large number of what are often heterogeneous and disparate information systems in support of their internal processes. Interoperability depends on ensuring the availability of interfaces to these systems and the data they handle. In turn, interoperability facilitates reuse of systems and data, and enables these to be integrated into larger systems. 3. Securing the right to the protection of personal data, by respecting the applicable legal framework for the large volumes of personal data of citizens, held and managed by Public administrations.(https://ec.europa.eu/isa2/sites/default/files/eif_brochure_final.pdf)
LOST view: Architecture Principle View
Identifier: http://data.europa.eu/dr8/EifPrinciple
eira:ID: ABB300
ABB name: eira:EifPrinciple
Last modification: 2022-23-01
Description: Users have an integrated experience of digital public services
Publisher: ELAP
Source: eID Building Block of DIGITAL Europe
Last modification: 2024-01-11
Identifier: http://data.europa.eu/2sa/elap/integrated-horizontal-user-experience
EIRA traceability: eira:EuropeanLibraryofArchitecturePrinciplesPrinciple
EIRA concept: eira:SolutionBuildingBlock
Additional identifier: elap:IntegratedHorizontalUserExperiencePrinciple
Title: Integrated Horizontal User Experience
EIF Layer: N/A
Description: The assessment of the effective realisation of public services, based on public policies, by evaluating various technological solutions when striving to ensure the effectiveness and efficiency of European public services.
Publisher: ELAP
Source: Assessment of Effectiveness and Efficiency Underlying Principle (12) of the European Interoperability Framework (EIF)
Last modification: 2024-01-11
Identifier: http://data.europa.eu/2sa/elap/convergence-assurance-public-policy-goals-attainment
EIRA traceability: eira:EuropeanLibraryofArchitecturePrinciplesPrinciple
EIRA concept: eira:SolutionBuildingBlock
Additional identifier: elap:ConvergenceAssuranceOnPublicPolicyGoalsAttainmentPrinciple
Title: Convergence assurance on public policy goals attainment
EIF Layer: N/A
Description: EU Legislation Compliance is the property of (national/local) legislation to be coherent or to implement European legislation.
Publisher: ELAP
Source: COM(2017) 134 final ANNEX 2 COMMUNICATION FROM THE COMMISSION TO THE EUROPEAN PARLIAMENT, THE COUNCIL, THE EUROPEAN ECONOMIC AND SOCIAL COMMITTEE AND THE COMMITTEE OF THE REGIONS European Interoperability Framework - Implementation Strategy
Last modification: 2024-01-11
Identifier: http://data.europa.eu/2sa/elap/eu-legislation-compliance
EIRA traceability: eira:EuropeanLibraryofArchitecturePrinciplesPrinciple
EIRA concept: eira:SolutionBuildingBlock
Additional identifier: elap:EULegislationCompliancePrinciple
Title: EU Legislation Compliance
EIF Layer: N/A
Description: In the context of interoperable public services, the concept of openness mainly relates to data, specifications and software.
Publisher: ELAP
Source: Openness Underlying Principle (2) of the European Interoperability Framework (EIF)
Last modification: 2024-01-11
Identifier: http://data.europa.eu/2sa/elap/openness
EIRA traceability: eira:EuropeanLibraryofArchitecturePrinciplesPrinciple
EIRA concept: eira:SolutionBuildingBlock
Additional identifier: elap:OpennessPrinciple
Title: Openness
EIF Layer: N/A
Description: The European Commission's digital transformation must be based on the identification of cross-organisational needs and the development of internal partnerships.
Publisher: ELAP
Source: C(2022) 4388 final COMMUNICATION TO THE COMMISSION European Commission digital strategy Next generation digital Commission
Last modification: 2023-11-20
Identifier: http://data.europa.eu/2sa/elap/digital-partnership
EIRA traceability: eira:EuropeanLibraryofArchitecturePrinciplesPrinciple
LOST view: TVA-Functional Architecture Principles
EIRA concept: eira:SolutionBuildingBlock
Additional identifier: elap:digital-partnership
Title: Digital Partnership
Additional information: Strong and reliable relationships with other EU institutions and beyond, should be fostered in order to share resources and remain at the forefront of the latest technological trends. Specific approaches in technology such as user-centric, data-driven and agile trends must be pursued.
The Digital Strategy sets a new vision, addressing digital transformation opportunities of a post-pandemic scenario, and supporting the delivery of the EU’s strategic priorities by 2030.
EIF Layer: N/A
Description: A full life cycle cost of ownership (including retirement costs) should form part of the business case.
Publisher: ELAP
Source: How the EU wants to achieve a circular economy by 2050 in News European Parliament
Last modification: 2023-11-20
Identifier: http://data.europa.eu/2sa/elap/care-cradle-grave
EIRA traceability: eira:EuropeanLibraryofArchitecturePrinciplesPrinciple
LOST view: OV-Governance Architecture Principles
EIRA concept: eira:SolutionBuildingBlock
Additional identifier: elap:care-cradle-grave
Title: Care from cradle to grave
Additional information: At a critical stage for sustainable development in terms of climate change, and excess use of resources (economic, natural resources, etc), there is a need for the public administrations to use and establish relevant policies that help the reduction of general waste.
Public administrations are the first link of the chain and need to be the example for society and businesses on taking care of the whole life cycle for technology products. Therefore, when planning and designing public services, this aspect needs to be included (from the design and implementation to the retirement)
How the EU wants to achieve a circular economy by 2050
EIF Layer: N/A
Definition: European Library of Architecture principles ABB is a Principle that aim to support interoperability and standardization in eGoverment across the EU.
Source: ELAP
Source reference: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/solution/elap
Additional information: The European Library of Architecture Principles (ELAP) ABB is a principle intended to direct government organizations in initiating changes and implementing IT projects. Particularly when designing new or modified services, it is necessary to make visible how the principles are implemented and which considerations are made in this regard. The apply-or-explain principle applies here, whereby deviations are permitted provided that they are substantiated and recorded with good arguments so that they can be revisited at a later stage. This prevents important matters from being overlooked.
Interoperability saliency: The European Library of Architecture Principles ABB is salient for governance interoperability due to it establishes the principles and framework to ensure interoperability at the European level. Also, the European Library of Architecture Principles ABB is salient for organizational interoperability due to it establishes requirements and business processes to enable interoperability between public services.
Identifier: http://data.europa.eu/dr8/EuropeanLibraryofArchitecturePrinciplesPrinciple
eira:ID: ABB617
ABB name: eira:EuropeanLibraryofArchitecturePrinciplesPrinciple
Last modification: 2022-23-01
Description: Data Sovereignty refers to the ability of stakeholders involved in the delivery of public services to have full control over the shared data.
Publisher: ELAP
Source: \"Towards a Reference Enterprise Architecture to enforce Digital Sovereignty in International Data Spaces\". University of Twente
Last modification: 2023-11-20
Identifier: http://data.europa.eu/2sa/elap/data-sovereignty
EIRA traceability: eira:EuropeanLibraryofArchitecturePrinciplesPrinciple
LOST view: TVA-Functional Architecture Principles
EIRA concept: eira:SolutionBuildingBlock
Additional identifier: elap:data-sovereignty
Title: Data Sovereignty
Additional information: The concept of data sovereignty is becoming more and more relevant while digital transformation advances. Digital Sovereignty is relevant in the context of digital public services because allows the control of which data is shared between parties.
Under an environment compliant with data sovereignty, all stakeholders can manage the data they aim to provide. Therefore, when planning and designing public services, data sovereignty is a pillar to guarantee the rights and obligations of the different parties.
Nowadays, data spaces are gaining relevance and public administrations are putting efforts to focus on interoperability through the establishment of domain-specific data spaces. In this field, data sovereignty is specifically relevant and needs to be taken into account.
The University of Twente, specifically its Faculty of Behavioural, Management and Social Science is leading working groups and investigations on how e-Government can leverage new data paradigms can help to enhance the digital transformation and the relevance of digital public services by implementing Data Spaces.
EIF Layer: N/A
Definition: Citizens and businesses provide public administrations data only once Requesting the data multiple times leads to an unnecessary administrative burden for citizens and businesses. It also leads to multiple administrations of the same data, with a high risk of inconsistency and low data quality. It is essential that the data that public administrations use is of good quality, in order to prevent errors and delays in processes and provide high-quality services. There is a central metadata administration of all the datasets that public administration bodies have available for reuse.Public administration bodies first determine whether specific data elements are available for reuse before they decide to collect them.Data that can be reused from other public administrations are not requested from citizens or businesses but simply referred to.""
Source: Once Only Principle of DIGITAL Europe
Source reference: https://ec.europa.eu/cefdigital/wiki/display/CEFDIGITAL/Once+Only+Principle
Identifier: http://data.europa.eu/2sa/elap/once-only
ABB name: elap:OnceOnlyPrinciple
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-17
Name: Once Only
Interoperability Layer: N/A
Specialises: eira:EuropeanLibraryofArchitecturePrinciplesPrinciple
Description: The European Data Sharing principle of Fundamental Rights ensures that data sharing practices respect and protect the fundamental rights of individuals within the European Union. It emphasizes the importance of upholding privacy, data protection, and other fundamental rights while sharing data.
Additional information: The principle of Fundamental Rights is based on the understanding that data sharing should not compromise the rights of individuals, including their right to privacy, protection of personal data, freedom of expression, non-discrimination, and other fundamental rights enshrined in the European Union's Charter of Fundamental Rights. It aims to strike a balance between the benefits of data sharing and the protection of individual rights.
Example: An example of applying the Fundamental Rights principle is when a company shares customer data with a third-party service provider. The company must ensure that the data sharing agreement respects the privacy rights of its customers, complies with data protection regulations, and safeguards against any potential discrimination or misuse of the shared data.
Publisher: European Commission
Source: https://ec.europa.eu/info/strategy/priorities-2019-2024/europe-fit-digital-age/european-data-strategy_en
LOST view: Architecture Principles view
Identifier: http://data.europa.eu/dr8/egovera/FundamentalRightsPrinciple
EIRA traceability: eira:ArchitecturePrinciple
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-07-07
dct:identifier: http://data.europa.eu/dr8/egovera/FundamentalRightsPrinciple
dct:title: Fundamental Rights
Description: Code of ethics compliance refers to the expression of important values and standards that are also to be found in the law, but not only aspects related to legally-binding issues.
Publisher: ELAP
Source: European Ombudsman
Last modification: 2024-01-11
Identifier: http://data.europa.eu/2sa/elap/code-ethics-compliance
EIRA traceability: eira:EuropeanLibraryofArchitecturePrinciplesPrinciple
EIRA concept: eira:SolutionBuildingBlock
Additional identifier: elap:CodeOfEthicsCompliancePrinciple
Title: Code of ethics compliance
EIF Layer: N/A
Definition: Datasets metadata machine-readable format, vocabularies reused, and reference to other datasets and their metadata. Data format should be readable for machines without the need for specialised or ad hoc algorithms, translators, or mappings. Data does not exist in isolation but is highly dependent upon other data that is available from other parties. Data should also be reused, when possible, to prevent collecting the same data twice and introducing duplication, with the risk of inconsistency. Controlled vocabularies define the terms in a specific domain, standardising their interpretation. These concepts are the foundation for data, providing definitions and meaning to them. It is important for users of data to have access to these definitions, so they can correctly interpret the data. The usage of standardised methods for the representation of metadata (RDF, OWL, DAM+OIL, JSON LD). In the metadata of datasets, references are made to the metadata of other datasets that the dataset depends upon. The data model of the dataset refers to the data model and the specific data elements and definitions that are reused from other datasets. The data itself includes identifiers to data in other datasets that the data depends upon.Relevant controlled vocabularies that exist for the domain that is covered by a specific dataset are determined. Important terms that are not defined by existing controlled vocabularies are defined in a new controlled vocabulary. The controlled vocabulary is published in a standardized format in a location that can easly be found by the target audience. The controlled vocabulary and the concepts that it describes have globally unique and persistent identifiers, so they can easily be referred to.""
Source: FAIR principles
Source reference: https://www.go-fair.org/fair-principles/
LOST view: TVA-Functional Architecture Principles
Identifier: http://data.europa.eu/2sa/elap/data-interoperability
ABB name: elap:data-interoperability
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-17
Name: Data Interoperability
Interoperability Layer: N/A
Specialises: eira:EuropeanLibraryofArchitecturePrinciplesPrinciple
Description: Citizen Participation is a principle of European Data Sharing that emphasizes the involvement of citizens in decision-making processes related to data sharing. It recognizes the importance of including citizens in discussions, consultations, and collaborations to ensure transparency, accountability, and democratic governance in data sharing initiatives.
Additional information: Citizen Participation promotes the active engagement of individuals, communities, and civil society organizations in shaping data sharing policies, frameworks, and practices. It aims to foster trust, promote inclusivity, and empower citizens to have a say in how their data is collected, used, and shared. By involving citizens, data sharing initiatives can better address societal needs, protect privacy rights, and ensure that data-driven decisions align with public interests.
Example: An example of Citizen Participation in practice is when a city government initiates a public consultation process to gather input from residents on the use of data collected through smart city sensors. Citizens are invited to provide feedback, express concerns, and suggest potential uses for the data. This participatory approach allows the city to make informed decisions that reflect the needs and preferences of its citizens, ensuring that data sharing initiatives are transparent, accountable, and beneficial to the community as a whole.
Publisher: European Commission
Source: https://ec.europa.eu/info/strategy/priorities-2019-2024/europe-fit-digital-age/european-data-strategy_en
LOST view: Architecture Principles view
Identifier: http://data.europa.eu/dr8/egovera/CitizenParticipationPrinciple
EIRA traceability: eira:ArchitecturePrinciple
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-07-07
dct:identifier: http://data.europa.eu/dr8/egovera/CitizenParticipationPrinciple
dct:title: Citizen Participation
Description: Laws and regulations are technology neutral
Publisher: ELAP
Source: Technological neutrality and data portability Underlying Principle (5) of the European Interoperability Framework (EIF)
Last modification: 2024-01-11
Identifier: http://data.europa.eu/2sa/elap/technology-neutrality
EIRA traceability: eira:EuropeanLibraryofArchitecturePrinciplesPrinciple
EIRA concept: eira:SolutionBuildingBlock
Additional identifier: elap:TechnologyNeutralityPrinciple
Title: Technology Neutrality
EIF Layer: N/A
Description: Service orientation is a way of thinking in terms of services and service-based development and the outcomes of services.
Publisher: ELAP
Source: Open Group
Last modification: 2024-01-11
Identifier: http://data.europa.eu/2sa/elap/service-orientation
EIRA traceability: eira:EuropeanLibraryofArchitecturePrinciplesPrinciple
EIRA concept: eira:SolutionBuildingBlock
Additional identifier: elap:ServiceOrientationPrinciple
Title: Service Orientation
EIF Layer: N/A
Definition: Data portability is ensured. The functioning of the digital single market requires data to be easily transferable among different systems to avoid lock-in and support the frthe movement of data. This requirement relates to data portability - the ability to move and reuse data easily among different applications and systems, which becomes even more challenging in cross-border scenarios.
Source: Technological neutrality and data portability Underlying Principle (5) of the European Interoperability Framework (EIF)
Source reference: https://joinup.ec.europa.eu/collection/nifo-national-interoperability-framework-observatory/glossary/term/technological-neutrality-and-data-portability
LOST view: TVA-Functional Architecture Principles
Identifier: http://data.europa.eu/2sa/elap/data-portability
ABB name: elap:data-portability
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-03-17
Name: Data portability
Interoperability Layer: N/A
Specialises: eira:EuropeanLibraryofArchitecturePrinciplesPrinciple
Description: Digital public services enable accountability of public administrations
Publisher: ELAP
Source: Public Administration Review (Yale School of Management)
Last modification: 2024-01-11
Identifier: http://data.europa.eu/2sa/elap/accountability
EIRA traceability: eira:EuropeanLibraryofArchitecturePrinciplesPrinciple
EIRA concept: eira:SolutionBuildingBlock
Additional identifier: elap:AccountabilityPrinciple
Title: Accountability
EIF Layer: N/A
Description: Innovation entails rethinking organisations and processes and changing behaviour so that public services are delivered more efficiently to people.
Publisher: ELAP
Source: OPEN EUROPE Policies, Reforms and Achievements in EI Science and Innovation 2014-2019
Last modification: 2024-01-11
Identifier: http://data.europa.eu/2sa/elap/innovation
EIRA traceability: eira:EuropeanLibraryofArchitecturePrinciplesPrinciple
EIRA concept: eira:SolutionBuildingBlock
Additional identifier: elap:InnovationPrinciple
Title: Innovation
EIF Layer: N/A
Description: Metadata and data should be easy to find for both humans and computers
Publisher: ELAP
Source: FAIR Principles
Last modification: 2023-11-20
Identifier: http://data.europa.eu/2sa/elap/data-findability
EIRA traceability: eira:EuropeanLibraryofArchitecturePrinciplesPrinciple
LOST view: TVA-Functional Architecture Principles
EIRA concept: eira:SolutionBuildingBlock
Additional identifier: elap:data-findability
Title: Data Findability
EIF Layer: N/A
Description: Proactiveness refers to proactive services, which are public services that a public institution delivers following its own initiatives.
Publisher: ELAP
Source: Joinup
Last modification: 2024-01-11
Identifier: http://data.europa.eu/2sa/elap/proactiveness
EIRA traceability: eira:EuropeanLibraryofArchitecturePrinciplesPrinciple
EIRA concept: eira:SolutionBuildingBlock
Additional identifier: elap:ProactivenessPrinciple
Title: Proactiveness
EIF Layer: N/A
Description: The European Data Sharing principle of Inclusion emphasizes the importance of ensuring that all individuals and organizations have equal access to shared data resources. It promotes the idea that data should be made available to a wide range of stakeholders, including citizens, businesses, researchers, and public sector entities, without any discrimination or exclusion based on factors such as nationality, location, or organizational affiliation.
Additional information: Inclusion in data sharing is crucial for fostering innovation, enabling fair competition, and driving societal benefits. It ensures that data is not monopolized by a few entities and encourages collaboration and participation from diverse stakeholders. By promoting inclusivity, the European Data Sharing principle aims to create a level playing field and empower all actors to leverage data for economic growth, scientific advancements, and evidence-based decision-making.
Example: An example of the application of the Inclusion principle is the creation of open data portals by governments, where they make various datasets available to the public, researchers, and businesses. These portals ensure that data is accessible to anyone interested, enabling the development of innovative applications, research studies, and informed policy-making. Additionally, initiatives promoting data sharing among different organizations, such as public-private partnerships, adhere to the principle of inclusion by allowing equal participation and access to shared data resources.
Publisher: European Commission
Source: https://ec.europa.eu/info/strategy/priorities-2019-2024/europe-fit-digital-age/european-data-strategy_en
LOST view: Architecture Principles view
Identifier: http://data.europa.eu/dr8/egovera/InclusionPrinciple
EIRA traceability: eira:ArchitecturePrinciple
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-07-07
dct:identifier: http://data.europa.eu/dr8/egovera/InclusionPrinciple
dct:title: Inclusion
Definition: Digital Public Services, the organisations behind them and the data managed need to incorporate the relevant mechanism to ensure overall trustworthiness. Trust entails citizens reliance on trustworthy and verifiable digital government applications and services, which fully conform to high-security standards and respond to user needs. Fundamental rights and security should be integrated into all policies with a digital dimension. To foster trust in digital interactions with the public sector, suitable regulatory frameworks that ensure transparency, predictability, security-by-design and, where necessary, reinforcement or adjustment of existing provisions must be provided. The principle has a horizontal approach, where it affects the adoption of legal measures, organisational mechanisms, and technical means to ensure services are part of a network of trustworthiness interactions. At the legal level, relevant and binding legislation needs to be put in place to ensure legal interoperability and guarantee that trust is the base of data interactions (exchange, processing, etc amongst digital public services).At the technical level, mechanisms, tools and standards should be part of processes certification that data exchange involving all stakeholders, is saved, with integrity and trustable. ""
Source: Digital trust, from Shaping Europe’s digital future
Source reference: https://digital-strategy.ec.europa.eu/en/policies/trust
Identifier: http://data.europa.eu/2sa/elap/trust
ABB name: elap:TrustPrinciple
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-17
Name: Trust
Interoperability Layer: N/A
Specialises: eira:EuropeanLibraryofArchitecturePrinciplesPrinciple
Description: Where possible, public administrations should seek to streamline and simplify their administrative processes by improving them or eliminating any that do not provide public value.
Publisher: ELAP
Source: Administrative Simplification Underlying Principle (10) of the European Interoperability Framework (EIF)
Last modification: 2023-11-20
Identifier: http://data.europa.eu/2sa/elap/administrative-simplification
EIRA traceability: eira:EuropeanLibraryofArchitecturePrinciplesPrinciple
LOST view: TVA-Functional Architecture Principles
EIRA concept: eira:SolutionBuildingBlock
Additional identifier: elap:administrative-simplification
Title: Administrative Simplification
EIF Layer: N/A
Description: Digital sovereignty means digital infrastructures, products and services that safeguard European security, strategic assets and interests while respecting European values and requirements.
Publisher: ELAP
Source: C(2022) 4388 final COMMUNICATION TO THE COMMISSION European Commission digital strategy Next generation digital Commission
Last modification: 2023-11-20
Identifier: http://data.europa.eu/2sa/elap/digital-sovereignty-and-autonomy
EIRA traceability: eira:EuropeanLibraryofArchitecturePrinciplesPrinciple
LOST view: TVA-Functional Architecture Principles
EIRA concept: eira:SolutionBuildingBlock
Additional identifier: elap:digital-sovereignty-and-autonomy
Title: Digital sovereignty and autonomy
Additional information: European Institutions and Administrations are representing citizens and businesses and respond to and ensuring the proper development of European society in its most holistic manner. Therefore, there is a need of preventing to spend and depending on external stakeholders to foster the monopoly and vendor lock-in making non-efficient solutions and subject to external agents' desires.
The Digital Strategy sets a new vision, addressing digital transformation opportunities of a post-pandemic scenario, and supporting the delivery of the EU’s strategic priorities by 2030.
EIF Layer: N/A
Description: The sustainability principle in European Data Sharing emphasizes the long-term viability and environmental impact of data sharing practices. It promotes the responsible use of data resources to ensure their availability for future generations while minimizing any negative ecological consequences.
Additional information: Sustainability in data sharing involves adopting practices that prioritize the preservation and efficient utilization of data resources. This principle encourages organizations to consider the environmental impact of their data sharing activities, such as minimizing energy consumption, reducing carbon emissions, and promoting the use of renewable energy sources. It also emphasizes the importance of long-term data preservation, ensuring that data remains accessible and usable for future generations. By integrating sustainability into data sharing practices, organizations can contribute to a more environmentally conscious and resilient digital ecosystem.
Example: An example of applying the sustainability principle in data sharing is the implementation of energy-efficient data centers that utilize renewable energy sources. By reducing energy consumption and carbon emissions associated with data storage and processing, organizations can contribute to a more sustainable data infrastructure. Additionally, adopting data preservation strategies, such as long-term archiving and data lifecycle management, ensures the availability and usability of valuable data resources for future research and innovation.
Publisher: European Commission
Source: https://ec.europa.eu/info/strategy/priorities-2019-2024/europe-fit-digital-age/european-data-strategy_en
LOST view: Architecture Principles view
Identifier: http://data.europa.eu/dr8/egovera/SustainabilityPrinciple
EIRA traceability: eira:ArchitecturePrinciple
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-07-07
dct:identifier: http://data.europa.eu/dr8/egovera/SustainabilityPrinciple
dct:title: Sustainability
Description: Every solution must support sustainability. The sourcing, operation and decommissioning of IT equipment should not indirectly or directly negatively affect economic, social and environmental aspects.
Publisher: ELAP
Source: The European Parliament’s carbon footprint Towards carbon neutrality
Last modification: 2023-11-20
Identifier: http://data.europa.eu/2sa/elap/carbon-dioxide-e-footprint-impact-awareness
EIRA traceability: eira:EuropeanLibraryofArchitecturePrinciplesPrinciple
LOST view: OV-Governance Architecture Principles
EIRA concept: eira:SolutionBuildingBlock
Additional identifier: elap:carbon-dioxide-e-footprint-impact-awareness
Title: Carbon-dioxide e-footprint impact awareness
Additional information: Climate change is one of society's challenges for the upcoming decades, and public administrations shall be aware of and consider it when planning or implementing digital public services. Therefore, administrations and bodies in charge of developing public services according to public policies, need to consider the proper agreements that allow the reusing of existing services components and infrastructure to reduce the Carbon-dioxide e-footprint impact.
Towards carbon neutrality - European Parliament: The study analyses the European Parliament’s (EP) carbon footprint in the context of the recent EP resolutions, in which it declared a climate emergency in Europe and requested the development of a strategy to become itself carbon-neutral by 2030.
EIF Layer: N/A
Description: Public services are transformed into digital public services
Publisher: ELAP
Source: C(2022) 4388 final COMMUNICATION TO THE COMMISSION European Commission digital strategy Next generation digital Commission
Last modification: 2023-11-20
Identifier: http://data.europa.eu/2sa/elap/digital-first
EIRA traceability: eira:EuropeanLibraryofArchitecturePrinciplesPrinciple
LOST view: TVA-Functional Architecture Principles
EIRA concept: eira:SolutionBuildingBlock
Additional identifier: elap:digital-first
Title: Digital First
EIF Layer: N/A
Description: Social participation refers to Promoting Civic Participation and Transparency of Government Decision-Making Processes covering policies concerning ICT.
Publisher: ELAP
Source: Digital Democracy of European Citizen Action Service (ECAS)
Last modification: 2024-01-11
Identifier: http://data.europa.eu/2sa/elap/social-participation
EIRA traceability: eira:EuropeanLibraryofArchitecturePrinciplesPrinciple
EIRA concept: eira:SolutionBuildingBlock
Additional identifier: elap:SocialParticipationPrinciple
Title: Social participation
EIF Layer: N/A
Definition: Metadata and data should be well-described so that they can be replicated and/or combined in different settings. Reusability is the central goal of FAIR and is usually the trigger for the introduction of data management and FAIR in companies. In principle, achieving F, A and I should achieve most of R - but there is another important aspect of the reusability principle that needs to be resolved. When designing data collection processes, reusability beyond the original purpose must be considered. It is usually extremely difficult to make data that is not FAIR reusable after the fact. Data reusability must be in place from the beginning, i.e. context and tacit knowledge must be built in from the start. Otherwise, there is a risk that datasets will be found and analysed under false assumptions, leading to a disruption of projects and sometimes a reluctance of researchers to share their data with others. Data reusability must be in place from the beginning, i.e. context and tacit knowledge must be built in from the start. Otherwise, there is a risk that datasets will be found and analysed under false assumptions, leading to a disruption of projects and sometimes a reluctance of researchers to share their data with others.Mechanisms that ensure the data can be reused by other stakeholders are relevant, for this, two aspects to take into account are well-documented and clear licence and provenance information. ""
Source: FAIR Principles
Source reference: https://www.go-fair.org/fair-principles/
Publisher: ELAP
LOST view: TVA-Functional Architecture Principles
Identifier: http://data.europa.eu/2sa/elap/data-reusability
ABB name: elap:data-reusability
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-17
Name: Data Reusability
Interoperability Layer: N/A
Specialises: eira:EuropeanLibraryofArchitecturePrinciplesPrinciple
Description: Evidence-based Public Policies are policies designed and periodically reviewed looking at experimental evidences and incontrovertible data.
Publisher: ELAP
Source: Evidence-based policy (EBP)
Last modification: 2024-01-11
Identifier: http://data.europa.eu/2sa/elap/evidence-based-public-policy
EIRA traceability: eira:EuropeanLibraryofArchitecturePrinciplesPrinciple
EIRA concept: eira:SolutionBuildingBlock
Additional identifier: elap:EvidenceBasedPublicPolicyPrinciple
Title: Evidence based Public Policy
EIF Layer: N/A
Description: The design of digital public services is centred around their users.
Publisher: ELAP
Source: User-Centricity Underlying Principle (6) of the European Interoperability Framework (EIF)
Last modification: 2024-01-11
Identifier: http://data.europa.eu/2sa/elap/user-centricity
EIRA traceability: eira:EuropeanLibraryofArchitecturePrinciplesPrinciple
EIRA concept: eira:SolutionBuildingBlock
Additional identifier: elap:User-centricityPrinciple
Title: User-centricity
EIF Layer: N/A
Definition: Existing IT systems are reused, before deciding upon buying or even building them. Taxpayers money can only be spent once. Reusing existing systems is a lot cheaper that buying new systems or even building them. In most cases, the requirements of public administrations are not very specific, and existing systems are sufficient to support the processes. It may seem that the costs of building new IT systems can be acceptable, but the costs of the maintenance and support of these systems are often forgotten and are much higher than the cost related to the initial development. When requirements for IT support arise, it is first determined whether systems that provide similar functionality are already available in the organization or otherwise in the market.Requirements that are not supported by existing systems are critically analyzed to determine whether they are really essential.Processes are adapted to existing systems or standard systems that are available in the market, when possible and acceptable.Building new IT systems is only considered a last resort when no existing systems exist or cannot fulfil essential requirements.""
Source: Reusability Underlying Principle (4) of the European Interoperability Framework (EIF)
Source reference: https://joinup.ec.europa.eu/collection/nifo-national-interoperability-framework-observatory/glossary/term/reusability
LOST view: TVA-Functional Architecture Principles
Identifier: http://data.europa.eu/2sa/elap/reuse-buy-build
ABB name: elap:reuse-buy-build
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-17
Name: Reuse, before buy, before build
Interoperability Layer: N/A
Specialises: eira:EuropeanLibraryofArchitecturePrinciplesPrinciple
Description: Regulation (EU) 2018/1724, also known as the Single Digital Gateway Regulation, aims to establish a unified digital gateway that provides easy access to information, procedures, and assistance services for citizens and businesses across the European Union. The regulation seeks to simplify and streamline the process of accessing public services and information online, making it more user-friendly and efficient. It also amends the existing Regulation (EU) No 1024/2012 to align with the new provisions. The Single Digital Gateway is an important step towards creating a more digital and interconnected Europe.
Publisher: EUR-Lex
Source: http://data.europa.eu/eli/reg/2018/1724/oj
Last modification: 26/06/2023
EIRA traceability: eira:BindingInstrumentRequirement
LOST view: Legal view - Binding Power and Jurisdiction
EIRA concept: eira:SolutionBuildingBlock
Additional identifier: http://data.europa.eu/eli/reg/2018/1724/oj
Title: Regulation (EU) 2018/1724 of the European Parliament and of the Council of 2 October 2018 establishing a single digital gateway to provide access to information, to procedures and to assistance and problem-solving services and amending Regulation (EU) No 1024/2012 (Text with EEA relevance.)
Description: Regulation (EU) 2022/2065, also known as the Digital Service Act (DSA), updates the European Union's legal framework for illegal content on intermediaries, in particular by modernising the e-Commerce Directive adopted in 2000. In doing so, the DSA aims to harmonise different national laws in the European Union that have emerged at national level to address illegal content.
Publisher: EUR-Lex
Source: http://data.europa.eu/eli/reg/2022/2065/oj
Last modification: 26/06/2023
EIRA traceability: eira:BindingInstrumentRequirement
LOST view: Legal view - Binding Power and Jurisdiction
EIRA concept: eira:SolutionBuildingBlock
Additional identifier: http://data.europa.eu/eli/reg/2022/2065/oj
Title: Regulation (EU) 2022/2065 of the European Parliament and of the Council of 19 October 2022 on a Single Market For Digital Services and amending Directive 2000/31/EC (Digital Services Act) (Text with EEA relevance)
Description: The Regulation (EU) 2021/1230 aims to improve the efficiency and transparency of cross-border payments within the European Union (EU). It requires that cross-border payments in euro or other EU currencies must be treated the same as domestic payments, with no additional fees or charges. The regulation also mandates that payment service providers must disclose all fees and exchange rates upfront to consumers, and ensure that payments are processed within a certain timeframe. Additionally, the regulation promotes the use of innovative payment technologies and encourages competition among payment service providers. Overall, the regulation seeks to create a more integrated and competitive payments market within the EU, benefiting consumers and businesses alike.
Publisher: EUR-Lex
Source: http://data.europa.eu/eli/reg/2021/1230/oj
Last modification: 26/06/2023
EIRA traceability: eira:BindingInstrumentRequirement
LOST view: Legal view - Binding Power and Jurisdiction
EIRA concept: eira:SolutionBuildingBlock
Additional identifier: http://data.europa.eu/eli/reg/2021/1230/oj
Title: Regulation (EU) 2021/1230 of the European Parliament and of the Council of 14 July 2021 on cross-border payments in the Union
Definition: Disaster recovery is an IT non-functional requirement that ensures that a system can recover from any catastrophic event or disaster, such as natural disasters, power outages, or cyber-attacks. This requirement involves creating a plan and implementing strategies to minimize the impact of such events on the system's functionality and data. The disaster recovery plan should include backup and recovery procedures, redundant systems, and failover mechanisms to ensure that the system can quickly and efficiently recover from any disaster. The goal of disaster recovery is to minimize downtime, data loss, and ensure business continuity.
Source: TOGAF
Source reference: https://pubs.opengroup.org/architecture/togaf9-doc/arch/chap03.html
Additional information: According to the TOGAF specification, Disaster Recovery is a non-functional requirement that refers to the ability of an IT system to recover from a catastrophic event or disaster. This requirement is essential for ensuring the continuity of business operations and minimizing the impact of disruptions on the organization.
The Disaster Recovery requirement includes the following elements:
1. Recovery Time Objective (RTO): This refers to the maximum amount of time that the IT system can be down before it must be restored to full functionality. The RTO is typically measured in hours or days and is determined by the criticality of the system to the business.
2. Recovery Point Objective (RPO): This refers to the maximum amount of data loss that the organization can tolerate in the event of a disaster. The RPO is typically measured in minutes or hours and is determined by the criticality of the data to the business.
3. Backup and Recovery Procedures: This refers to the processes and procedures that are in place to backup and restore the IT system in the event of a disaster. These procedures must be tested regularly to ensure that they are effective and can be executed quickly and efficiently.
4. Disaster Recovery Plan: This refers to the overall plan that outlines the steps that must be taken to recover the IT system in the event of a disaster. The plan must be comprehensive and include all necessary information, such as contact information for key personnel, backup and recovery procedures, and communication protocols.
5. Testing and Maintenance: This refers to the ongoing testing and maintenance of the Disaster Recovery plan and procedures to ensure that they remain effective and up-to-date. Testing must be conducted regularly to identify any weaknesses or gaps in the plan and to ensure that all personnel are familiar with their roles and responsibilities.
Overall, the Disaster Recovery requirement is critical for ensuring the continuity of business operations in the event of a catastrophic event or disaster. Organizations must ensure that they have a comprehensive plan in place that includes backup and recovery procedures, testing and maintenance, and clear communication protocols to minimize the impact of disruptions on the organization.
Example: In the event of a natural disaster or system failure, the system must be able to recover all data and functionality within 24 hours with minimal data loss.
LOST view: Digital Solution Non-Functional Requirements Catalogue view
Identifier: http://data.europa.eu/dr8/egovera/DisasterRecoveryRequirement
EIRA traceability: eira:DigitalSolutionNonFunctionalRequirementRequirement
ABB name: egovera:DisasterRecoveryRequirement
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-05-16
dct:identifier: http://data.europa.eu/dr8/egovera/DisasterrecoveryRequirement
dct:title: Disaster recovery Non-Functional Requirement
Definition: Consistency is an important non-functional requirement in IT systems that refers to the uniformity and coherence of data and processes across different components of the system. It ensures that the system behaves predictably and reliably, and that users can trust the accuracy and completeness of the information they receive. Consistency can be achieved through the use of standardized formats, protocols, and interfaces, as well as through rigorous testing and quality assurance procedures. It is particularly important in distributed systems, where data and processes may be spread across multiple servers or networks.
Source: TOGAF
Source reference: https://pubs.opengroup.org/architecture/togaf9-doc/arch/chap03.html
Additional information: According to the TOGAF specification, guidelines, and documentation, the non-functional requirement of 'Consistency' refers to the need for the IT system to maintain a uniform and coherent approach to its operations, data, and interfaces. This consistency should be maintained across all components of the system, including hardware, software, and network infrastructure.
Consistency is essential for ensuring that the system operates smoothly and efficiently, without any unexpected or unpredictable behavior. It also helps to ensure that users can easily navigate and interact with the system, without encountering any confusing or conflicting information.
To achieve consistency, the IT system should adhere to established standards and best practices, such as those defined by industry bodies or regulatory agencies. It should also use a common set of data definitions and formats, and ensure that all interfaces and interactions are designed and implemented in a consistent manner.
In addition, the IT system should be designed and tested to ensure that it can maintain consistency even under varying conditions, such as changes in workload, network traffic, or hardware failures. This may involve implementing redundancy or failover mechanisms, or using load balancing techniques to distribute workload across multiple servers.
Overall, the non-functional requirement of 'Consistency' is critical for ensuring that the IT system operates reliably and predictably, and provides a consistent and seamless experience for users.
Example: One example of the IT non-functional requirement 'Consistency' could be ensuring that all user interfaces across a software application have a consistent look and feel, including font sizes, colors, and button placements. This can help to improve user experience and reduce confusion or frustration when navigating the application.
LOST view: Digital Solution Non-Functional Requirements Catalogue view
Identifier: http://data.europa.eu/dr8/egovera/ConsistencyRequirement
EIRA traceability: eira:DigitalSolutionNonFunctionalRequirementRequirement
ABB name: egovera:ConsistencyRequirement
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-05-16
dct:identifier: http://data.europa.eu/dr8/egovera/ConsistencyRequirement
dct:title: Consistency Non-Functional Requirement
Definition: Alerts and monitoring are non-functional requirements that ensure that the system can detect and reporting any issues or anomalies that may arise during its operation. This includes the ability to monitor system performance, detect errors, and notify relevant stakeholders in real-time. The alerts and monitoring system should be designed to provide timely and accurate information to enable quick and effective decision-making, as well as to ensure that the system is always available and performing optimally. This requirement is critical for ensuring the reliability, availability, and performance of the system.
Source: TOGAF
Source reference: https://pubs.opengroup.org/architecture/togaf9-doc/arch/chap03.html
Additional information: According to the TOGAF specification, 'Alerts and monitoring' is a non-functional requirement that pertains to the system's ability to detect and report errors, failures, and other critical events. This requirement is essential for ensuring the system's reliability, availability, and performance.
To meet this requirement, the system must be equipped with monitoring tools and mechanisms that can track and analyze various system metrics, such as CPU usage, memory utilization, network traffic, and disk space. These tools should be able to generate alerts and notifications when predefined thresholds are exceeded or when specific events occur.
The alerts and notifications should be sent to the appropriate stakeholders, such as system administrators, support teams, or business users, depending on the severity and impact of the event. The alerts should provide sufficient information to enable the stakeholders to take appropriate actions, such as investigating the root cause of the problem, applying corrective measures, or escalating the issue to higher levels of management.
The monitoring tools should also be able to generate reports and dashboards that provide insights into the system's performance and health. These reports should be customizable and configurable to meet the specific needs of different stakeholders.
Overall, the 'Alerts and monitoring' non-functional requirement is critical for ensuring the system's reliability, availability, and performance. By providing real-time visibility into the system's health and performance, the monitoring tools enable stakeholders to proactively identify and resolve issues before they escalate into major problems.
Example: One example of the IT non-functional requirement 'Alerts and monitoring' could be for a financial institution's online banking system to have real-time monitoring of all transactions and user activity, with alerts triggered for any suspicious or potentially fraudulent activity. This would help ensure the security and integrity of the system and protect both the institution and its customers from potential financial losses.
LOST view: Digital Solution Non-Functional Requirements Catalogue view
Identifier: http://data.europa.eu/dr8/egovera/AlertsAndMonitoringRequirement
EIRA traceability: eira:DigitalSolutionNonFunctionalRequirementRequirement
ABB name: egovera:AlertsAndMonitoringRequirement
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-05-16
dct:identifier: http://data.europa.eu/dr8/egovera/AlertsandmonitoringRequirement
dct:title: Alerts and monitoring Non-Functional Requirement
Description: The Digital Europe Programme (DIGITAL) is an EU funding programme focused on bringing digital technology to businesses, citizens and public administrations. It provides strategic funding supporting projects in five key capacity areas: in supercomputing, artificial intelligence, cybersecurity, advanced digital skills, and ensuring a wide use of digital technologies across the economy and society, including through Digital Innovation Hubs. It aims to accelerate the economic recovery and shape the digital transformation of Europe’s society and economy, bringing benefits to everyone, but in particular to small and medium-sized enterprises.
Publisher: EUR-Lex
Source: http://data.europa.eu/eli/reg/2021/694/oj
Last modification: 26/06/2023
EIRA traceability: eira:Non-bindingInstrumentRequirement
LOST view: Legal view - Binding Power and Jurisdiction
EIRA concept: eira:SolutionBuildingBlock
Additional identifier: http://data.europa.eu/eli/reg/2021/694/oj
Title: Regulation (EU) 2021/694 of the European Parliament and of the Council of 29 April 2021 establishing the Digital Europe Programme and repealing Decision (EU) 2015/2240 (Text with EEA relevance)
Definition: Modularity and reusability are non-functional requirements that refer to the ability of a software system to be broken down into smaller, independent components that can be easily reused in other parts of the system or in other systems altogether. This requirement is important because it allows for greater flexibility and scalability in software development, as well as reducing the amount of time and effort required to develop new software applications. By designing software with modularity and reusability in mind, developers can create more efficient and effective systems that are easier to maintain and update over time.
Source: TOGAF
Source reference: https://pubs.opengroup.org/architecture/togaf9-doc/arch/chap03.html
Additional information: Modularity and reusability are non-functional requirements that are essential for the development of robust and scalable IT systems. According to the TOGAF specification, guidelines, and documentation, modularity refers to the ability of a system to be broken down into smaller, independent components or modules. These modules can be developed, tested, and maintained separately, which makes it easier to modify or replace them without affecting the rest of the system.
Reusability, on the other hand, refers to the ability of a system or its components to be used in different contexts or applications. This means that the system or its components should be designed in a way that they can be easily adapted or extended to meet the requirements of different users or applications.
To achieve modularity and reusability, the TOGAF framework recommends the use of standard interfaces and protocols that allow different components to communicate with each other. This can be achieved through the use of service-oriented architecture (SOA) or microservices, which provide a modular and flexible approach to system design.
In addition, the TOGAF framework recommends the use of design patterns and best practices that promote modularity and reusability. These include the use of abstraction, encapsulation, and inheritance to create modular and reusable components that can be easily extended or modified.
Overall, modularity and reusability are critical non-functional requirements that should be considered throughout the entire system development lifecycle. By following the TOGAF framework and best practices, IT systems can be designed to be more flexible, scalable, and adaptable to changing business needs.
Example: One example of the IT non-functional requirement 'Modularity and reusability' could be the development of a software application that can be easily integrated with other systems and components. This means that the application should be designed in a modular way, with clear interfaces and well-defined APIs, so that it can be easily reused and adapted to different environments and use cases. Additionally, the application should be built using standard technologies and programming languages, so that it can be easily maintained and updated over time. This requirement is important for organizations that need to integrate multiple systems and applications, as it helps to reduce development time and costs, and improves overall system performance and reliability.
LOST view: Digital Solution Non-Functional Requirements Catalogue view
Identifier: http://data.europa.eu/dr8/egovera/ModularityAndReusabilityRequirement
EIRA traceability: eira:DigitalSolutionNonFunctionalRequirementRequirement
ABB name: egovera:ModularityAndReusabilityRequirement
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-05-16
dct:identifier: http://data.europa.eu/dr8/egovera/ModularityandreusabilityRequirement
dct:title: Modularity and reusability Non-Functional Requirement
Definition: Non-binding Instrument ABB is a Business Object, involving no obligation, which are available to the European institutions to carry out their tasks.
Source: EUR-Lex
Source reference: http://ec.europa.eu/eurostat/data/data-validation
Example: The following implementation is an example of how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): Opinion of the European Economic and Social Committee on Next Generation SME Strategy — Enhancing Effective and Swift Delivery (own-initiative opinion). https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A52021IE3668&qid=1664779252884
Interoperability Dimension: Structural IoP
LOST view: Legal view
Interoperability Saliency: The Non-binding Instrument ABB is a key salient for the legal and governance interoperability enabler as a specialisation of the Legal Act, it makes the recommendation of implementation of the policies and rules.
Identifier: http://data.europa.eu/dr8/Non-bindingInstrumentRequirement
ABB name: eira:Non-bindingInstrumentRequirement
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/Non-bindingInstrumentRequirement
Interoperability Layer: Legal
Definition: Auditability is an IT non-functional requirement that refers to the ability of a system to provide a complete and accurate record of all activities and transactions that occur within it. This includes the ability to track changes made to data, monitor user access and permissions, and generate reports that can be used for compliance, regulatory, or legal purposes. The audit trail should be secure, tamper-proof, and easily accessible to authorized personnel. The purpose of auditability is to ensure accountability, transparency, and integrity of the system's operations.
Source: TOGAF
Source reference: https://pubs.opengroup.org/architecture/togaf9-doc/arch/chap03.html
Additional information: According to the TOGAF specification, Auditability is a non-functional requirement that refers to the ability of a system to provide a complete and accurate record of all transactions and activities that occur within the system. This includes the ability to track and record all user actions, system events, and data changes, as well as the ability to generate reports and alerts based on this information.
The Auditability requirement is important for ensuring the integrity and security of a system, as well as for compliance with regulatory and legal requirements. It also helps to identify and investigate any potential security breaches or fraudulent activities.
To meet the Auditability requirement, a system must have the following capabilities:
1. Logging and tracking: The system must be able to log and track all user actions, system events, and data changes, including the date, time, and user responsible for each action.
2. Reporting and analysis: The system must be able to generate reports and alerts based on the logged information, allowing administrators to identify and investigate any suspicious activity.
3. Security and access control: The system must have robust security and access control mechanisms in place to prevent unauthorized access to the audit logs and to ensure the integrity of the logged information.
4. Retention and archiving: The system must be able to retain and archive audit logs for a specified period of time, in accordance with regulatory and legal requirements.
Overall, the Auditability requirement is an essential aspect of any system design, ensuring that the system is secure, compliant, and transparent in its operations.
Example: One example of the IT non-functional requirement 'Auditability' could be for a financial management system to track and record all changes made to financial data, including who made the change, when it was made, and what the previous and new values were. This would allow for auditing and compliance purposes, as well as ensuring the accuracy and integrity of financial data.
LOST view: Digital Solution Non-Functional Requirements Catalogue view
Identifier: http://data.europa.eu/dr8/egovera/AuditabilityRequirement
EIRA traceability: eira:DigitalSolutionNonFunctionalRequirementRequirement
ABB name: egovera:AuditabilityRequirement
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-05-16
dct:identifier: http://data.europa.eu/dr8/egovera/AuditabilityRequirement
dct:title: Auditability Non-Functional Requirement
Description: Regulation 2018/389 is a European Union regulation that aims to establish a framework for cooperation and information exchange between member states in the field of cybersecurity. It sets out rules and procedures for the sharing of information on cyber threats and incidents, as well as the coordination of response measures. The regulation also establishes a European Cybersecurity Certification Framework to ensure the security and trustworthiness of products and services in the digital market. Overall, the regulation seeks to enhance the EU's cybersecurity capabilities and strengthen the resilience of its digital infrastructure.
Publisher: EUR-Lex
Source: http://data.europa.eu/eli/reg_del/2018/389/oj
Last modification: 26/06/2023
EIRA traceability: eira:Non-bindingInstrumentRequirement
LOST view: Legal view - Binding Power and Jurisdiction
EIRA concept: eira:SolutionBuildingBlock
Additional identifier: http://data.europa.eu/eli/reg_del/2018/389/oj
Title: Commission Delegated Regulation (EU) 2018/389 of 27 November 2017 supplementing Directive (EU) 2015/2366 of the European Parliament and of the Council with regard to regulatory technical standards for strong customer authentication and common and secure open standards of communication
Example: Regulation 2018/389, also known as the "Regulation on the establishment of a framework for interoperability between EU information systems," has several applications in various areas. Here are a few examples:
Description: Regulation 2014/910, also known as eIDAS (Electronic Identification, Authentication and Trust Services), is a European Union regulation that aims to establish a framework for electronic identification and trust services in the internal market. It provides a legal framework for electronic signatures, electronic seals, electronic time stamps, electronic documents, and electronic registered delivery services, ensuring their legal validity and cross-border recognition within the EU. The regulation aims to enhance the security and reliability of electronic transactions, promote the use of electronic identification, and facilitate the digital single market within the European Union.
Publisher: EUR-Lex
Source: https://eur-lex.europa.eu/eli/reg/2014/910/oj
Last modification: 26/06/2023
EIRA traceability: eira:BindingInstrumentRequirement
LOST view: Legal view - Binding Power and Jurisdiction
EIRA concept: eira:SolutionBuildingBlock
Additional identifier: https://eur-lex.europa.eu/eli/reg/2014/910/oj
Title: 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
Definition: Geodes is a non-functional requirement that refers to the ability of a system to accurately determine the location of a user or device. This requirement is important for systems that rely on location-based services, such as navigation apps or emergency response systems. Geodes involves the use of GPS or other location tracking technologies to provide precise location data, which can be used to improve the functionality and usability of the system. The accuracy and reliability of geodes is critical, as errors or inaccuracies can lead to serious consequences in certain applications.
Source: TOGAF
Source reference: https://pubs.opengroup.org/architecture/togaf9-doc/arch/chap03.html
Additional information: According to the TOGAF specification, Geodes can be classified as a non-functional requirement related to the performance and scalability of the IT system. Geodes refer to the ability of the system to handle and process large volumes of data and transactions in a timely and efficient manner. This requirement is critical for systems that deal with geospatial data, such as mapping and navigation applications.
To meet the Geodes requirement, the IT system must be designed to handle large amounts of data and transactions without compromising performance or scalability. This can be achieved through the use of distributed computing architectures, such as cloud computing or grid computing, which allow for the processing of data across multiple nodes or servers.
Additionally, the IT system must be designed to optimize the use of resources, such as memory and processing power, to ensure that performance is not impacted by the volume of data being processed. This can be achieved through the use of caching mechanisms, data compression, and other optimization techniques.
Overall, the Geodes requirement is critical for systems that deal with geospatial data and must be carefully considered during the design and implementation of the IT system to ensure that performance and scalability are not compromised.
Example: One example of an IT non-functional requirement for geodes could be that the system must be able to accurately track and display the location of assets or vehicles in real-time, with a margin of error no greater than 10 meters. This requirement would ensure that the system is reliable and precise enough to be used for applications such as fleet management or logistics tracking.
LOST view: Digital Solution Non-Functional Requirements Catalogue view
Identifier: http://data.europa.eu/dr8/egovera/GeodesRequirement
EIRA traceability: eira:DigitalSolutionNonFunctionalRequirementRequirement
ABB name: egovera:GeodesRequirement
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-05-16
dct:identifier: http://data.europa.eu/dr8/egovera/GeodesRequirement
dct:title: Geodes Non-Functional Requirement
Description: The proposal for a regulation aims to establish horizontal cybersecurity requirements for products with digital elements in the European Union. It seeks to ensure a high level of cybersecurity for all products with digital components, including software, firmware, and hardware. The regulation will apply to all economic operators involved in the production, distribution, and sale of these products, and it will establish a framework for conformity assessment and market surveillance. The proposal also amends Regulation (EU) 2019/1020 to include cybersecurity as one of the essential requirements for products.
Publisher: EUR-Lex
Source: https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=celex%3A52022PC0454
Last modification: 26/06/2023
EIRA traceability: eira:BindingInstrumentRequirement
LOST view: Legal view - Binding Power and Jurisdiction
EIRA concept: eira:SolutionBuildingBlock
Additional identifier: https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=celex%3A52022PC0454
Title: Proposal for a REGULATION OF THE EUROPEAN PARLIAMENT AND OF THE COUNCIL on horizontal cybersecurity requirements for products with digital elements and amending Regulation (EU) 2019/1020
Definition: Pluggability is an IT non-functional requirement that refers to the ability of a system to easily integrate with other systems or components without requiring significant modifications to the existing codebase. This requirement ensures that the system can be easily extended or customized by adding or removing components, modules, or plugins, without affecting the overall functionality of the system. Pluggability is essential for systems that need to be scalable, flexible, and adaptable to changing business requirements, as it allows for easy integration with third-party tools and technologies.
Source: TOGAF
Source reference: https://pubs.opengroup.org/architecture/togaf9-doc/arch/chap03.html
Additional information: According to the TOGAF specification, Pluggability is a non-functional requirement that refers to the ability of a system or application to easily integrate with other systems or components without requiring significant modifications to the existing architecture. This requirement is closely related to the concept of interoperability, which is the ability of different systems to work together seamlessly.
Pluggability is an important non-functional requirement for modern IT systems, as it allows organizations to easily integrate new technologies and components into their existing infrastructure. This can help to reduce costs, improve efficiency, and enhance the overall functionality of the system.
To achieve pluggability, IT systems must be designed with a modular architecture that allows for easy integration of new components. This can be achieved through the use of standard interfaces, protocols, and APIs that enable different systems to communicate with each other.
In addition, pluggability requires that IT systems be designed with a high degree of flexibility and scalability. This means that the system must be able to adapt to changing requirements and accommodate new components as they are added.
Overall, pluggability is an important non-functional requirement for IT systems that enables organizations to easily integrate new technologies and components into their existing infrastructure. By designing systems with a modular architecture and a high degree of flexibility, organizations can achieve pluggability and reap the benefits of a more efficient and effective IT infrastructure.
Example: One example of the IT non-functional requirement 'Pluggability' could be the ability of a software application to seamlessly integrate with third-party plugins or modules. For instance, a content management system (CMS) should be able to support various plugins for search engine optimization (SEO), social media integration, and e-commerce functionality. The pluggability requirement ensures that the software can be easily extended and customized to meet the specific needs of the users without requiring significant modifications to the core codebase.
LOST view: Digital Solution Non-Functional Requirements Catalogue view
Identifier: http://data.europa.eu/dr8/egovera/PluggabilityRequirement
EIRA traceability: eira:DigitalSolutionNonFunctionalRequirementRequirement
ABB name: egovera:PluggabilityRequirement
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-05-16
dct:identifier: http://data.europa.eu/dr8/egovera/PluggabilityRequirement
dct:title: Pluggability Non-Functional Requirement
Description: The proposal aims to strengthen the European Union's ability to detect, prepare for, and respond to cybersecurity threats and incidents. It outlines measures that member states must take to improve their cybersecurity capabilities, including establishing national cybersecurity centers and developing incident response plans. The proposal also establishes a European Cybersecurity Competence Center to coordinate research and development efforts and promote cybersecurity skills and knowledge across the EU. The regulation emphasizes the importance of cooperation and information sharing between member states and with the private sector to enhance the EU's overall cybersecurity resilience.
Publisher: EUR-Lex
Source: https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:52023PC0209
Last modification: 26/06/2023
EIRA traceability: eira:BindingInstrumentRequirement
LOST view: Legal view - Binding Power and Jurisdiction
EIRA concept: eira:SolutionBuildingBlock
Additional identifier: https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:52023PC0209
Title: Proposal for a REGULATION OF THE EUROPEAN PARLIAMENT AND OF THE COUNCIL laying down measures to strengthen solidarity and capacities in the Union to detect, prepare for and respond to cybersecurity threats and incidents
Definition: Accountability is an IT non-functional requirement that refers to the ability of a system to track and record the actions of users and processes. This requirement ensures that all activities within the system can be traced back to their source, allowing for transparency and responsibility. Accountability is essential for compliance with regulations and standards, as well as for detecting and preventing fraudulent or malicious activities. It also helps to build trust and confidence in the system by providing a clear audit trail of all actions taken.
Source: TOGAF
Source reference: https://pubs.opengroup.org/architecture/togaf9-doc/arch/chap03.html
Additional information: According to the TOGAF specification, Accountability is a non-functional requirement that refers to the ability to trace and audit the actions and decisions made by a system or its users. This requirement ensures that the system can be held responsible for its actions and that there is a clear record of who made what decision and when.
To meet this requirement, the system must have the ability to log and track all user actions and system events. This includes the ability to record user login and logout times, the actions taken by users while logged in, and any system events that occur during operation. The system must also be able to generate reports and audit trails that can be used to trace the actions and decisions made by the system and its users.
In addition, the system must provide mechanisms for controlling access to sensitive data and functionality. This includes the ability to restrict access to certain features or data based on user roles and permissions. The system must also provide mechanisms for enforcing data privacy and security policies to ensure that sensitive data is protected from unauthorized access or disclosure.
Overall, the Accountability non-functional requirement is critical for ensuring that the system is transparent and can be held responsible for its actions. By providing the ability to trace and audit user actions and system events, the system can be used with confidence and trust.
Example: One example of the IT non-functional requirement 'Accountability' could be ensuring that all actions taken by users on a system are logged and traceable to the individual user. This would allow for accountability in the event of any unauthorized or malicious activity on the system.
LOST view: Digital Solution Non-Functional Requirements Catalogue view
Identifier: http://data.europa.eu/dr8/egovera/AccountabilityRequirement
EIRA traceability: eira:DigitalSolutionNonFunctionalRequirementRequirement
ABB name: egovera:AccountabilityRequirement
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-05-16
dct:identifier: http://data.europa.eu/dr8/egovera/AccountabilityRequirement
dct:title: Accountability Non-Functional Requirement
Definition: Legality is an IT non-functional requirement that ensures that the software or system complies with all applicable laws, regulations, and standards. It is important to ensure that the system does not violate any legal or regulatory requirements, such as data privacy laws, copyright laws, or industry-specific regulations. Failure to comply with these requirements can result in legal and financial consequences for the organization. Therefore, it is crucial to ensure that the system is designed and developed in accordance with all applicable legal and regulatory requirements.
Source: TOGAF
Source reference: https://pubs.opengroup.org/architecture/togaf9-doc/arch/chap03.html
Additional information: According to the TOGAF specification, guidelines, and documentation, the non-functional requirement of 'Legality' refers to the compliance of the IT system with legal and regulatory requirements. This requirement ensures that the system adheres to all applicable laws, regulations, and standards, including data protection laws, intellectual property laws, and industry-specific regulations.
The Legality requirement also includes the need for the system to be auditable and transparent, allowing for regulatory compliance checks and audits. The system must also provide appropriate documentation and reporting capabilities to demonstrate compliance with legal and regulatory requirements.
In addition, the Legality requirement also encompasses the need for the system to be secure and protect sensitive data from unauthorized access or disclosure. This includes the implementation of appropriate security measures, such as encryption, access controls, and monitoring, to ensure that the system meets legal and regulatory requirements for data protection.
Overall, the Legality requirement is critical for ensuring that the IT system operates within the boundaries of the law and meets all applicable legal and regulatory requirements. Failure to meet this requirement can result in legal and financial penalties, reputational damage, and loss of customer trust.
Example: One example of an IT non-functional requirement related to legality could be ensuring compliance with data privacy laws such as GDPR or CCPA. This could include requirements for data encryption, user consent for data collection and processing, and data retention policies.
LOST view: Digital Solution Non-Functional Requirements Catalogue view
Identifier: http://data.europa.eu/dr8/egovera/LegalityRequirement
EIRA traceability: eira:DigitalSolutionNonFunctionalRequirementRequirement
ABB name: egovera:LegalityRequirement
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-05-16
dct:identifier: http://data.europa.eu/dr8/egovera/LegalityRequirement
dct:title: Legality Non-Functional Requirement
Description: The European Code of Conduct relating to electronic payment is a set of guidelines and principles established by the European Commission to ensure fair and transparent practices in electronic payment services. It aims to protect consumers by promoting secure and efficient payment systems, enhancing competition, and preventing fraud and abuse. The code encourages payment service providers to provide clear information to consumers regarding fees, charges, and terms of service, as well as ensuring the security and privacy of personal data. It also promotes interoperability and accessibility of payment systems across the European Union.
Publisher: EUR-Lex
Source: http://data.europa.eu/eli/reco/1987/598/oj
Last modification: 26/06/2023
EIRA traceability: eira:Non-bindingInstrumentRequirement
LOST view: Legal view - Binding Power and Jurisdiction
EIRA concept: eira:SolutionBuildingBlock
Additional identifier: http://data.europa.eu/eli/reco/1987/598/oj
Title: 87/598/EEC: Commission Recommendation of 8 December 1987 on a European Code of Conduct relating to electronic payment (Relations between financial institutions, traders and service establishments, and consumers)
Example: The European Code of Conduct relating to electronic payment is a set of guidelines and principles that aim to ensure the security, transparency, and efficiency of electronic payment services within the European Union. Here are some examples of its application:
Definition: Durability is an IT non-functional requirement that refers to the ability of a system or application to withstand and recover from failures, errors, or disruptions. It ensures that the system can maintain its functionality and data integrity even in the face of unexpected events such as power outages, hardware failures, or network disruptions. Durability is critical for systems that handle sensitive or mission-critical data, as any loss or corruption of data can have severe consequences. To achieve durability, systems may use techniques such as data replication, backup and recovery, and fault tolerance.
Source: TOGAF
Source reference: https://pubs.opengroup.org/architecture/togaf9-doc/arch/chap03.html
Additional information: Durability is a non-functional requirement that refers to the ability of a system to maintain its functionality and performance over time, even in the face of adverse conditions such as hardware failures, power outages, or other disruptions. This requirement is important for systems that are critical to the operation of an organization or that handle sensitive or valuable data.
According to the TOGAF specification, durability is one of the key quality attributes that must be considered when designing and implementing an enterprise architecture. This requirement is closely related to other non-functional requirements such as reliability, availability, and maintainability, which together form the basis of a system's overall performance and effectiveness.
To ensure that a system meets the durability requirement, architects and designers must consider a range of factors, including the robustness of hardware components, the resilience of software applications, and the effectiveness of backup and recovery procedures. They must also consider the impact of environmental factors such as temperature, humidity, and power fluctuations, and design systems that can withstand these conditions without compromising performance or functionality.
In addition to these technical considerations, architects and designers must also consider the organizational and operational factors that can affect durability. This includes factors such as training and support for system users, maintenance and repair procedures, and disaster recovery planning.
Overall, the durability requirement is a critical aspect of enterprise architecture design, and must be carefully considered and addressed in order to ensure the long-term success and effectiveness of a system.
Example: One example of the IT non-functional requirement 'Durability' could be for a database system to maintain data integrity and availability even in the event of hardware failures or power outages. This means that the system should be able to recover quickly and efficiently from any disruptions or failures without losing any data or causing any downtime for users. The durability requirement ensures that the system can handle unexpected events and maintain its functionality over time.
LOST view: Digital Solution Non-Functional Requirements Catalogue view
Identifier: http://data.europa.eu/dr8/egovera/DurabilityRequirement
EIRA traceability: eira:DigitalSolutionNonFunctionalRequirementRequirement
ABB name: egovera:DurabilityRequirement
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-05-16
dct:identifier: http://data.europa.eu/dr8/egovera/DurabilityRequirement
dct:title: Durability Non-Functional Requirement
Definition: Agility is an IT non-functional requirement that refers to the ability of a system to adapt quickly and easily to changing business needs or market conditions. It involves the system's ability to respond to new requirements, integrate with other systems, and scale up or down as needed. An agile system is one that can be easily modified or updated without disrupting the overall functionality of the system. This requirement is important for businesses that need to stay competitive and responsive to changing market conditions.
Source: TOGAF
Source reference: https://pubs.opengroup.org/architecture/togaf9-doc/arch/chap03.html
Additional information: According to the TOGAF specification, Agility is a non-functional requirement that refers to the ability of an IT system to respond quickly and effectively to changing business needs and market conditions. This requirement is closely related to the concept of flexibility, which involves the ability to adapt to new situations and requirements.
To meet the Agility requirement, an IT system must be designed with a high degree of modularity, scalability, and interoperability. It should be able to integrate easily with other systems and technologies, and should be able to support a wide range of business processes and workflows.
In addition, an Agile IT system should be designed with a focus on continuous improvement and innovation. This means that it should be able to evolve and adapt over time, incorporating new features and functionality as needed to meet changing business needs.
To achieve these goals, an Agile IT system should be built using modern software development methodologies such as Agile or DevOps. It should also be designed with a high degree of automation, including automated testing, deployment, and monitoring.
Overall, the Agility requirement is an important consideration for any IT system, as it can help to ensure that the system remains relevant and effective in the face of changing business needs and market conditions. By following the TOGAF guidelines and documentation, IT architects and designers can create systems that are both flexible and adaptable, and that can support the evolving needs of the organization over time.
Example: One example of an IT non-functional requirement for agility could be the ability for a software system to quickly adapt to changing business requirements or market conditions. This could involve the ability to easily add or modify features, integrate with new technologies, or scale up or down as needed. The system should also be able to respond quickly to user feedback and incorporate changes into future releases.
LOST view: Digital Solution Non-Functional Requirements Catalogue view
Identifier: http://data.europa.eu/dr8/egovera/AgilityRequirement
EIRA traceability: eira:DigitalSolutionNonFunctionalRequirementRequirement
ABB name: egovera:AgilityRequirement
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-05-16
dct:identifier: http://data.europa.eu/dr8/egovera/AgilityRequirement
dct:title: Agility Non-Functional Requirement
Description: Directive (EU) 2018/1972, also known as the European Electronic Communications Code, is a directive established by the European Parliament and Council in December 2018. It aims to modernize and harmonize the regulatory framework for electronic communications across the European Union. The code sets out rules and obligations for electronic communications services, networks, and infrastructure providers, with the goal of promoting competition, investment, and innovation in the sector. It also addresses issues such as consumer rights, spectrum management, and access to emergency services. The code replaces the previous regulatory framework established in 2002 and is expected to facilitate the development of a single European digital market.
Publisher: EUR-Lex
Source: http://data.europa.eu/eli/dir/2018/1972/oj
Last modification: 26/06/2023
EIRA traceability: eira:BindingInstrumentRequirement
LOST view: Legal view - Binding Power and Jurisdiction
EIRA concept: eira:SolutionBuildingBlock
Additional identifier: http://data.europa.eu/eli/dir/2018/1972/oj
Title: Directive (EU) 2018/1972 of the European Parliament and of the Council of 11 December 2018 establishing the European Electronic Communications Code (Recast)Text with EEA relevance.
Description: Directive (EU) 2019/1024, also known as the Open Data Directive, stipulates minimum requirements for EU member states regarding making public sector information available for re-use. This directive provides a common legislative framework for this area. The Directive is an attempt to remove barriers that hinder the re-use of public sector information throughout the Union.
Publisher: EUR-Lex
Source: http://data.europa.eu/eli/dir/2019/1024/oj
Last modification: 26/06/2023
EIRA traceability: eira:BindingInstrumentRequirement
LOST view: Legal view - Binding Power and Jurisdiction
EIRA concept: eira:SolutionBuildingBlock
Additional identifier: http://data.europa.eu/eli/dir/2019/1024/oj
Title: Directive (EU) 2019/1024 of the European Parliament and of the Council of 20 June 2019 on open data and the re-use of public sector information
Description: The Data Governance Act is a regulation enacted by the European Parliament and Council that aims to establish a framework for the governance of data in the European Union. It seeks to facilitate the sharing of data across sectors and borders while ensuring the protection of individuals' rights and promoting fair competition. The act introduces rules for data intermediaries and data-sharing service providers, promoting transparency, accountability, and trust in data sharing. It also includes provisions for the creation of data spaces and the development of codes of conduct for data sharing. Additionally, the act amends the existing Regulation (EU) 2018/1724 to align it with the new data governance framework.
Publisher: EUR-Lex
Source: http://data.europa.eu/eli/reg/2022/868/oj
Last modification: 26/06/2023
EIRA traceability: eira:BindingInstrumentRequirement
LOST view: Legal view - Binding Power and Jurisdiction
EIRA concept: eira:SolutionBuildingBlock
Additional identifier: http://data.europa.eu/eli/reg/2022/868/oj
Title: Regulation (EU) 2022/868 of the European Parliament and of the Council of 30 May 2022 on European data governance and amending Regulation (EU) 2018/1724 (Data Governance Act) (Text with EEA relevance)
Description: Directive 2014/24/EU is a European Union legislation that governs public procurement processes within member states. It was adopted on 26 February 2014 and replaces Directive 2004/18/EC. The directive aims to promote transparency, competition, and value for money in public procurement by setting out rules and procedures that must be followed by public authorities when awarding contracts for goods, services, and works. It also introduces measures to simplify and streamline the procurement process, encourage the participation of small and medium-sized enterprises, and promote sustainable and socially responsible procurement practices.
Publisher: EUR-Lex
Source: http://data.europa.eu/eli/dir/2014/24/oj
Last modification: 26/06/2023
EIRA traceability: eira:BindingInstrumentRequirement
LOST view: Legal view - Binding Power and Jurisdiction
EIRA concept: eira:SolutionBuildingBlock
Additional identifier: http://data.europa.eu/eli/dir/2014/24/oj
Title: Directive 2014/24/EU of the European Parliament and of the Council of 26 February 2014 on public procurement and repealing Directive 2004/18/EC Text with EEA relevance
Example: Directive 2014/24/EU on public procurement is a European Union law that sets out the rules and procedures for the procurement of goods, services, and works by public authorities in the EU. Here are some examples of its application:
Definition: Deployment stamps are a non-functional requirement that refers to the need for a system to have a timestamp or version number associated with each deployment. This allows for easy tracking and identification of different versions of the system, as well as the ability to roll back to a previous version if necessary. Deployment stamps are important for ensuring the stability and reliability of a system, as well as for facilitating efficient and effective maintenance and troubleshooting.
Source: TOGAF
Source reference: https://pubs.opengroup.org/architecture/togaf9-doc/arch/chap03.html
Additional information: According to the TOGAF specification, Deployment stamps are a non-functional requirement that pertains to the deployment of software applications. This requirement specifies that each deployment of the software application must be stamped with a unique identifier that indicates the version of the application that has been deployed.
The purpose of this requirement is to ensure that the deployment process is traceable and auditable. By having a unique identifier for each deployment, it becomes easier to track changes and identify any issues that may arise during the deployment process.
The deployment stamp should be generated automatically by the deployment tool or system and should be stored in a central repository. This repository should be accessible to authorized personnel who need to track the deployment process.
In addition to the unique identifier, the deployment stamp should also include information such as the date and time of the deployment, the environment in which the application was deployed, and any other relevant information that may be useful for tracking and auditing purposes.
Overall, the Deployment stamps non-functional requirement is an important aspect of ensuring that the deployment process is traceable and auditable, which is essential for maintaining the integrity and reliability of software applications.
Example: Deployment stamps refer to the requirement that each version of the software being deployed must have a unique identifier or timestamp associated with it. This helps to ensure that the correct version of the software is being deployed and that any issues can be traced back to a specific version. For example, a banking application may require deployment stamps to ensure that the correct version of the software is being used to process financial transactions.
LOST view: Digital Solution Non-Functional Requirements Catalogue view
Identifier: http://data.europa.eu/dr8/egovera/DeploymentStampsRequirement
EIRA traceability: eira:DigitalSolutionNonFunctionalRequirementRequirement
ABB name: egovera:DeploymentStampsRequirement
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-05-16
dct:identifier: http://data.europa.eu/dr8/egovera/DeploymentstampsRequirement
dct:title: Deployment stamps Non-Functional Requirement
Definition: Nonrepudiation is an IT non-functional requirement that ensures that the sender and the receiver cannot deny the sending or reception of a message. It is a security measure that provides proof of the authenticity and integrity of a message, ensuring that it cannot be altered or tampered with during transmission. Nonrepudiation is essential in situations where legal or financial transactions are involved, as it provides evidence that can be used to resolve disputes or prove compliance with regulations.
Source: TOGAF
Source reference: https://pubs.opengroup.org/architecture/togaf9-doc/arch/chap03.html
Additional information: Nonrepudiation is an IT non-functional requirement that ensures that the sender of a message cannot deny sending it and the receiver cannot deny receiving it. This requirement is essential in situations where there is a need to establish accountability and traceability of communication between parties.
According to the TOGAF specification, nonrepudiation is a security requirement that is achieved through the use of digital signatures, timestamps, and other cryptographic techniques. These techniques ensure that messages are tamper-proof and that their origin and integrity can be verified.
Nonrepudiation is an important requirement in many industries, including finance, healthcare, and legal services. It helps to prevent fraud, disputes, and other legal issues that may arise from disputes over the authenticity of messages.
To ensure nonrepudiation, IT systems must be designed with security in mind. This includes implementing strong authentication and access controls, using encryption to protect data in transit and at rest, and monitoring systems for suspicious activity. Additionally, organizations must have policies and procedures in place to ensure that nonrepudiation requirements are met and that any violations are addressed promptly.
Overall, nonrepudiation is a critical IT non-functional requirement that helps to ensure the integrity and accountability of communication between parties. By following the TOGAF guidelines and documentation, organizations can design and implement systems that meet this requirement and provide a secure and reliable platform for communication and collaboration.
Example: Nonrepudiation is an IT non-functional requirement that ensures that a user cannot deny having performed a particular action or transaction. For example, in an online banking system, nonrepudiation ensures that a user cannot deny having made a particular transaction, such as transferring funds to another account. This is achieved through the use of digital signatures and other cryptographic techniques that provide evidence of the user's identity and the authenticity of the transaction.
LOST view: Digital Solution Non-Functional Requirements Catalogue view
Identifier: http://data.europa.eu/dr8/egovera/NonrepudiationRequirement
EIRA traceability: eira:DigitalSolutionNonFunctionalRequirementRequirement
ABB name: egovera:NonrepudiationRequirement
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-05-16
dct:identifier: http://data.europa.eu/dr8/egovera/NonrepudiationRequirement
dct:title: Nonrepudiation Non-Functional Requirement
Description: Directive 2019/770 is a legislation enacted by the European Parliament and Council on 20 May 2019 that focuses on specific aspects related to contracts for the provision of digital content and digital services. The directive aims to harmonize and strengthen consumer rights in the digital market by establishing clear rules and obligations for suppliers of digital content and services. It covers various aspects such as the conformity of digital content and services, remedies for non-conformity, the right to updates and upgrades, and the protection of personal data. The directive seeks to enhance consumer trust and confidence in the digital marketplace while promoting fair competition and innovation.
Publisher: EUR-Lex
Source: http://data.europa.eu/eli/dir/2019/770/oj
Last modification: 26/06/2023
EIRA traceability: eira:BindingInstrumentRequirement
LOST view: Legal view - Binding Power and Jurisdiction
EIRA concept: eira:SolutionBuildingBlock
Additional identifier: http://data.europa.eu/eli/dir/2019/770/oj
Title: Directive (EU) 2019/770 of the European Parliament and of the Council of 20 May 2019 on certain aspects concerning contracts for the supply of digital content and digital services.
Definition: Traffic pattern is an IT non-functional requirement that refers to the expected volume and frequency of user traffic on a system or application. It includes factors such as peak usage times, the number of concurrent users, and the expected growth rate of traffic over time. The traffic pattern requirement is critical in ensuring that the system can handle the expected load without experiencing performance issues such as slow response times or crashes. It also helps in determining the appropriate infrastructure and resources needed to support the system.
Source: TOGAF
Source reference: https://pubs.opengroup.org/architecture/togaf9-doc/arch/chap03.html
Additional information: According to the TOGAF specification, the non-functional requirement 'Traffic pattern' refers to the expected behavior of the system under different levels of traffic. This requirement is concerned with the system's ability to handle varying levels of user activity, data volume, and transaction processing.
The Traffic pattern non-functional requirement is important for ensuring that the system can perform optimally under different traffic conditions. This requirement should be defined in terms of the expected traffic patterns, such as peak usage times, expected user activity levels, and the expected volume of data transactions.
To meet this requirement, the system should be designed to handle the expected traffic patterns efficiently. This may involve the use of load balancing techniques, caching mechanisms, and other performance optimization strategies. The system should also be able to scale up or down as needed to accommodate changes in traffic patterns.
In addition, the Traffic pattern non-functional requirement should be tested to ensure that the system can perform as expected under different traffic conditions. This may involve load testing, stress testing, and other performance testing techniques to simulate different traffic scenarios and measure the system's response.
Overall, the Traffic pattern non-functional requirement is critical for ensuring that the system can handle varying levels of traffic and perform optimally under different usage scenarios.
Example: One example of an IT non-functional requirement for 'Traffic pattern' could be for a website or application that needs to handle a high volume of traffic during peak hours, such as during a major sale event or a product launch. The requirement could specify that the system must be able to handle a certain number of concurrent users without experiencing any significant slowdowns or crashes. Additionally, it may require that the system be able to scale up or down as needed to accommodate fluctuations in traffic patterns.
LOST view: Digital Solution Non-Functional Requirements Catalogue view
Identifier: http://data.europa.eu/dr8/egovera/TrafficPatternRequirement
EIRA traceability: eira:DigitalSolutionNonFunctionalRequirementRequirement
ABB name: egovera:TrafficPatternRequirement
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-05-16
dct:identifier: http://data.europa.eu/dr8/egovera/TrafficpatternRequirement
dct:title: Traffic pattern Non-Functional Requirement
Definition: Archivability is an IT non-functional requirement that refers to the ability of a system to store and retrieve data or information over a long period of time. This requirement is important for systems that deal with critical data or information that needs to be preserved for legal, regulatory, or historical purposes. Archivability ensures that data is stored in a format that can be accessed and retrieved easily, even after a long period of time, and that the data remains accurate and complete. It also ensures that the system can handle large amounts of data and that the data is stored securely to prevent unauthorized access or tampering.
Source: TOGAF
Source reference: https://pubs.opengroup.org/architecture/togaf9-doc/arch/chap03.html
Additional information: Archivability is a non-functional requirement that pertains to the ability of a system to store and preserve data for future reference or use. According to the TOGAF specification, guidelines, and documentation, archivability is a critical aspect of enterprise architecture, particularly in the context of data management and governance.
The archivability non-functional requirement is closely related to other requirements such as data retention, data integrity, and data security. It involves ensuring that data is stored in a format that is easily retrievable and accessible, and that it remains intact and uncorrupted over time. This requirement is particularly important for organizations that are required to comply with regulatory or legal requirements, as it ensures that data can be retrieved and presented as evidence if necessary.
To meet the archivability non-functional requirement, enterprise architects must consider a range of factors, including the type of data being stored, the format in which it is stored, the storage medium used, and the length of time for which the data needs to be retained. They must also consider the potential risks associated with data loss or corruption, and implement appropriate measures to mitigate these risks.
In practice, meeting the archivability non-functional requirement may involve implementing a range of technologies and processes, such as data backup and recovery systems, data archiving solutions, and data retention policies. It may also involve working closely with stakeholders across the organization to ensure that data is managed and stored in a way that meets their needs and requirements.
Overall, the archivability non-functional requirement is a critical aspect of enterprise architecture, and one that must be carefully considered and managed to ensure the long-term viability and success of an organization.
Example: Archivability: The system must be able to store and retrieve data for a minimum of 10 years, with the ability to export data in a standard format for long-term storage and retrieval.
LOST view: Digital Solution Non-Functional Requirements Catalogue view
Identifier: http://data.europa.eu/dr8/egovera/ArchivabilityRequirement
EIRA traceability: eira:DigitalSolutionNonFunctionalRequirementRequirement
ABB name: egovera:ArchivabilityRequirement
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-05-16
dct:identifier: http://data.europa.eu/dr8/egovera/ArchivabilityRequirement
dct:title: Archivability Non-Functional Requirement
Publisher: EUR-Lex
Source: https://eur-lex.europa.eu/procedure/EN/2021_106
Last modification: 26/06/2023
EIRA traceability: eira:BindingInstrumentRequirement
LOST view: Legal view - Binding Power and Jurisdiction
EIRA concept: eira:SolutionBuildingBlock
Additional identifier: https://eur-lex.europa.eu/procedure/EN/2021_106
Title: Proposal for a REGULATION OF THE EUROPEAN PARLIAMENT AND OF THE COUNCIL LAYING DOWN HARMONISED RULES ON ARTIFICIAL INTELLIGENCE (ARTIFICIAL INTELLIGENCE ACT) AND AMENDING CERTAIN UNION LEGISLATIVE ACTS
Definition: Observability is a non-functional requirement in IT that refers to the ability to monitor and analyze the behavior of a system or application in real-time. It involves collecting and analyzing data from various sources, such as logs, metrics, and traces, to gain insights into the system's performance, availability, and reliability. Observability helps IT teams identify and troubleshoot issues quickly, improve system performance, and ensure that the system meets the desired level of service. It is an essential requirement for complex and distributed systems that require constant monitoring and analysis to ensure optimal performance.
Source: TOGAF
Source reference: https://pubs.opengroup.org/architecture/togaf9-doc/arch/chap03.html
Additional information: Observability is a non-functional requirement that refers to the ability of a system to be monitored and analyzed in order to detect and diagnose issues. According to the TOGAF specification, observability is a key aspect of system performance and reliability, as it allows for proactive identification and resolution of problems before they impact users.
To achieve observability, a system must be designed with the ability to collect and analyze data from various sources, including logs, metrics, and traces. This data must be made available to monitoring and analysis tools, which can then provide insights into system behavior and performance.
The TOGAF guidelines recommend that observability be considered throughout the entire system development lifecycle, from initial design through to deployment and ongoing maintenance. This includes defining clear metrics and logging requirements, as well as selecting appropriate monitoring and analysis tools.
In addition, the TOGAF documentation emphasizes the importance of ensuring that observability is integrated into the overall system architecture, rather than being treated as an afterthought. This requires careful consideration of factors such as data collection and storage, data processing and analysis, and user access to monitoring and analysis tools.
Overall, observability is a critical non-functional requirement for any system that requires high levels of performance and reliability. By following the TOGAF guidelines and best practices, organizations can ensure that their systems are designed with observability in mind, and are able to proactively identify and resolve issues before they impact users.
Example: One example of the IT non-functional requirement 'Observability' could be the ability to monitor and track system performance metrics such as CPU usage, memory usage, network traffic, and response times. This would allow IT teams to quickly identify and troubleshoot any issues that may arise, ensuring that the system remains reliable and available to users. Additionally, observability could also include the ability to log and analyze user behavior, allowing for insights into how the system is being used and how it can be improved.
LOST view: Digital Solution Non-Functional Requirements Catalogue view
Identifier: http://data.europa.eu/dr8/egovera/ObservabilityRequirement
EIRA traceability: eira:DigitalSolutionNonFunctionalRequirementRequirement
ABB name: egovera:ObservabilityRequirement
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-05-16
dct:identifier: http://data.europa.eu/dr8/egovera/ObservabilityRequirement
dct:title: Observability Non-Functional Requirement
Definition: Integrity is an IT non-functional requirement that ensures the accuracy, consistency, and reliability of data throughout its lifecycle. It involves maintaining the correctness and completeness of data, preventing unauthorized access or modification, and ensuring that data is not lost or corrupted due to system failures or errors. Integrity is critical for ensuring the trustworthiness of data and maintaining the credibility of the system that uses it. It is often achieved through the use of data validation, error checking, access controls, and backup and recovery mechanisms.
Source: TOGAF
Source reference: https://pubs.opengroup.org/architecture/togaf9-doc/arch/chap03.html
Additional information: According to the TOGAF specification, Integrity is a non-functional requirement that refers to the accuracy, consistency, and reliability of data and information within a system. It ensures that the data is protected from unauthorized access, modification, or deletion, and that it remains consistent and reliable throughout its lifecycle.
Integrity is an essential requirement for any system that deals with sensitive or critical data, such as financial transactions, personal information, or medical records. It ensures that the data is not compromised or corrupted, and that it can be trusted by the users and stakeholders.
To achieve integrity, the system must have appropriate security measures in place, such as access controls, authentication, encryption, and auditing. It must also have mechanisms to detect and prevent data tampering, such as checksums, digital signatures, or version control.
Integrity is closely related to other non-functional requirements, such as availability, reliability, and performance. A system that lacks integrity may also suffer from data loss, downtime, or poor performance, which can have severe consequences for the users and the organization.
Overall, integrity is a critical non-functional requirement that ensures the trustworthiness and reliability of data and information within a system. It must be carefully considered and implemented to ensure the security and effectiveness of the system.
Example: One example of the IT non-functional requirement 'Integrity' is ensuring that data is not altered or modified during transmission or storage. This can be achieved through the use of encryption, checksums, and other security measures to prevent unauthorized access or tampering. Additionally, data backups and disaster recovery plans can help ensure that data remains intact and accessible in the event of a system failure or other disruption.
LOST view: Digital Solution Non-Functional Requirements Catalogue view
Identifier: http://data.europa.eu/dr8/egovera/IntegrityRequirement
EIRA traceability: eira:DigitalSolutionNonFunctionalRequirementRequirement
ABB name: egovera:IntegrityRequirement
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-05-16
dct:identifier: http://data.europa.eu/dr8/egovera/IntegrityRequirement
dct:title: Integrity Non-Functional Requirement
Definition: Compliance is an IT non-functional requirement that refers to the ability of a system or application to adhere to legal, regulatory, and industry standards. This requirement ensures that the system or application meets the necessary security, privacy, and data protection standards, as well as any other relevant regulations. Compliance is critical for organizations that handle sensitive data, such as financial institutions, healthcare providers, and government agencies, as it helps to mitigate risks and avoid legal and financial penalties.
Source: TOGAF
Source reference: https://pubs.opengroup.org/architecture/togaf9-doc/arch/chap03.html
Additional information: According to the TOGAF specification, Compliance is a non-functional requirement that refers to the ability of an IT system to adhere to legal, regulatory, and industry standards. Compliance requirements are often imposed by external entities, such as government agencies or industry associations, and failure to comply can result in legal or financial penalties.
To ensure compliance, IT systems must be designed and implemented in accordance with relevant standards and regulations. This may involve incorporating specific security measures, data protection protocols, or other controls to meet compliance requirements.
Compliance is an important consideration for organizations in many industries, particularly those that handle sensitive data or operate in highly regulated environments. By ensuring compliance, organizations can minimize the risk of legal or financial penalties, protect their reputation, and demonstrate their commitment to ethical and responsible business practices.
Overall, compliance is a critical non-functional requirement that must be carefully considered and addressed in the design and implementation of IT systems.
Example: One example of an IT non-functional requirement for compliance could be ensuring that the system meets all relevant regulatory requirements, such as HIPAA for healthcare data or PCI DSS for credit card information. This could include implementing appropriate security measures, maintaining audit logs, and regularly conducting vulnerability assessments.
LOST view: Digital Solution Non-Functional Requirements Catalogue view
Identifier: http://data.europa.eu/dr8/egovera/ComplianceRequirement
EIRA traceability: eira:DigitalSolutionNonFunctionalRequirementRequirement
ABB name: egovera:ComplianceRequirement
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-05-16
dct:identifier: http://data.europa.eu/dr8/egovera/ComplianceRequirement
dct:title: Compliance Non-Functional Requirement
Definition: Confidentiality is a non-functional requirement that ensures that sensitive information is protected from unauthorized access, disclosure, or modification. It is essential for maintaining the privacy and security of data, especially in industries such as healthcare, finance, and government. Confidentiality can be achieved through various measures, such as encryption, access controls, and secure communication channels. It is crucial to ensure that confidential information is only accessible to authorized personnel and is not compromised in any way.
Source: TOGAF
Source reference: https://pubs.opengroup.org/architecture/togaf9-doc/arch/chap03.html
Additional information: According to the TOGAF specification, confidentiality is a non-functional requirement that refers to the protection of sensitive information from unauthorized access, disclosure, or modification. This requirement is critical for ensuring the privacy and security of data, particularly in systems that handle sensitive or confidential information.
To achieve confidentiality, the system must have appropriate security controls in place, such as access controls, encryption, and authentication mechanisms. These controls should be designed to prevent unauthorized access to data, both in transit and at rest, and to ensure that only authorized users can view or modify sensitive information.
In addition, the system should be designed to detect and respond to security breaches or incidents that could compromise confidentiality. This may involve implementing intrusion detection and prevention systems, monitoring access logs, and conducting regular security audits and assessments.
Overall, confidentiality is a key non-functional requirement that must be carefully considered and addressed in any system that handles sensitive or confidential information. By implementing appropriate security controls and monitoring mechanisms, organizations can ensure that their data remains secure and protected from unauthorized access or disclosure.
Example: In a healthcare system, patient medical records must be kept confidential and only accessible to authorized personnel.
LOST view: Digital Solution Non-Functional Requirements Catalogue view
Identifier: http://data.europa.eu/dr8/egovera/ConfidentialityRequirement
EIRA traceability: eira:DigitalSolutionNonFunctionalRequirementRequirement
ABB name: egovera:ConfidentialityRequirement
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-05-16
dct:identifier: http://data.europa.eu/dr8/egovera/ConfidentialityRequirement
dct:title: Confidentiality Non-Functional Requirement
Definition: An API contract is a non-functional requirement that specifies the rules and guidelines for how an application programming interface (API) should behave. It defines the expected behavior of the API, including the input and output formats, error handling, security, and performance. The API contract ensures that the API is consistent and predictable, making it easier for developers to use and integrate with other systems. It also helps to ensure that the API is reliable, scalable, and maintainable over time.
Source: TOGAF
Source reference: https://pubs.opengroup.org/architecture/togaf9-doc/arch/chap03.html
Additional information: According to the TOGAF specification, an API contract is a non-functional requirement that defines the terms and conditions for using an application programming interface (API). It specifies the rules and guidelines that must be followed by both the API provider and the API consumer to ensure that the API functions as intended and meets the required quality attributes.
The API contract includes details such as the API's input and output parameters, error handling procedures, security requirements, performance expectations, and other technical specifications. It also outlines the expected behavior of the API under different scenarios and usage patterns.
The API contract is a critical component of the API design process, as it helps to ensure that the API is reliable, scalable, and maintainable. It also helps to minimize the risk of errors and inconsistencies in the API implementation, which can lead to security vulnerabilities, performance issues, and other problems.
To create an effective API contract, it is important to involve all stakeholders, including the API provider, API consumer, and any other relevant parties. The contract should be clear, concise, and easy to understand, and should be regularly reviewed and updated as needed to reflect changes in the API or its usage patterns.
Example: One example of an IT non-functional requirement for an API contract could be that the API must have a clearly defined and documented interface that specifies the expected inputs, outputs, and behavior of the API. This interface should be consistent and stable over time, so that clients can rely on it and build their own applications around it. Additionally, the API should be designed to be scalable and performant, so that it can handle large volumes of requests and respond quickly to user actions. Finally, the API should be secure and protected against unauthorized access, with appropriate authentication and authorization mechanisms in place to ensure that only authorized users can access the API and its data.
LOST view: Digital Solution Non-Functional Requirements Catalogue view
Identifier: http://data.europa.eu/dr8/egovera/APIContractRequirement
EIRA traceability: eira:DigitalSolutionNonFunctionalRequirementRequirement
ABB name: egovera:APIContractRequirement
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-05-16
dct:identifier: http://data.europa.eu/dr8/egovera/APIcontractRequirement
dct:title: API contract Non-Functional Requirement
Description: Directive 2000/31/EC, known also as the Electronic Commerce Directive, is a legislation enacted by the European Parliament and Council on June 8, 2000. It focuses on the legal aspects of information society services, specifically electronic commerce, within the Internal Market of the European Union. The directive aims to establish a harmonized legal framework for online businesses, ensuring the free movement of electronic services and promoting consumer confidence in online transactions. It covers various aspects such as electronic contracts, liability of intermediaries, and rules for online advertising and commercial communications.
Publisher: EUR-Lex
Source: http://data.europa.eu/eli/dir/2000/31/oj
Last modification: 26/06/2023
EIRA traceability: eira:BindingInstrumentRequirement
LOST view: Legal view - Binding Power and Jurisdiction
EIRA concept: eira:SolutionBuildingBlock
Additional identifier: http://data.europa.eu/eli/dir/2000/31/oj
Title: Directive 2000/31/EC of the European Parliament and of the Council of 8 June 2000 on certain legal aspects of information society services, in particular electronic commerce, in the Internal Market ('Directive on electronic commerce')
Example: The Electronic Commerce Directive (ECD) is a European Union directive that provides legal guidelines for electronic commerce activities within the EU. Here are some examples of its application:
Definition: Elasticity is an IT non-functional requirement that refers to the ability of a system to scale up or down in response to changes in demand. This means that the system should be able to handle increased traffic or workload without compromising its performance or stability. Elasticity is important for systems that experience unpredictable or fluctuating demand, as it allows them to maintain optimal performance and avoid downtime. It also helps organizations to optimize their resource utilization and reduce costs by scaling down when demand decreases.
Source: TOGAF
Source reference: https://pubs.opengroup.org/architecture/togaf9-doc/arch/chap03.html
Additional information: According to the TOGAF specification, Elasticity is a non-functional requirement that refers to the ability of a system to scale up or down its resources in response to changing demands. This requirement is closely related to the concept of scalability, which refers to the ability of a system to handle increasing workloads without compromising its performance.
Elasticity is an important requirement for systems that are expected to handle varying levels of traffic or workload. For example, a web application that experiences a sudden surge in traffic due to a marketing campaign or a news event should be able to scale up its resources to handle the increased demand. Similarly, a system that experiences a decrease in traffic during off-peak hours should be able to scale down its resources to save costs.
To achieve elasticity, a system should be designed with the following characteristics:
1. Modularity: The system should be composed of independent modules that can be scaled up or down independently.
2. Automation: The scaling process should be automated to minimize human intervention and reduce the risk of errors.
3. Monitoring: The system should be monitored continuously to detect changes in demand and trigger the scaling process.
4. Resilience: The system should be able to handle failures and recover quickly from them.
5. Flexibility: The system should be able to adapt to different types of workloads and resource requirements.
Overall, elasticity is an important non-functional requirement that can help ensure that a system is able to handle changing demands and provide a consistent level of performance.
Example: An example of the IT non-functional requirement 'Elasticity' could be the ability of a cloud-based application to automatically scale up or down its computing resources based on the current demand. This means that the application should be able to handle sudden spikes in traffic without crashing or slowing down, while also being able to reduce its resource usage during periods of low activity to save costs.
LOST view: Digital Solution Non-Functional Requirements Catalogue view
Identifier: http://data.europa.eu/dr8/egovera/ElasticityRequirement
EIRA traceability: eira:DigitalSolutionNonFunctionalRequirementRequirement
ABB name: egovera:ElasticityRequirement
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-05-16
dct:identifier: http://data.europa.eu/dr8/egovera/ElasticityRequirement
dct:title: Elasticity Non-Functional Requirement
Definition: This ABB is a Business Agnostic National Legal Act which lays down rules regulating the electronic identification of citizens and businesses.
LOST view: LV-Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/NationalSchemaOnEIdentificationRequirement
ABB name: egovera:NationalSchemaOnEIdentificationRequirement
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-11-20
Name: National Schema in eIdentification
Identifier: egovera:NationalSchemaOnEIdentificationRequirement
Interoperability Layer: Legal
Specialises: http://data.europa.eu/dr8/BindingInstrumentRequirement
Definition: European Legal Act ABB is a Requirement enabling the adoption of laws by the Institutions of the European Union in order to exercise the powers given to them by the EU Treaties. They come in five forms: regulations, directives, decisions, recommendations and opinions.
Source: Eur-Lex
Source reference: https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=LEGISSUM:ai0032
Example: The following implementation is an example of how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): TOLAR (https://tolar.io/)is a tool implemented as the outcome of the Seduproject, Hashnet is in the process of evaluation by the European Blockchain Partnership to become one of the pilot protocols for European Blockchain Service Infrastructure. https://www.seedeuproject.eu/partners/hashnet/
Interoperability Dimension: Structural IoP
LOST view: Legal view
Interoperability Saliency: European Legal Act ABB is salient for legal interoperability because it helps to achieve European legal and juridical certainty in the exchange of information
Identifier: http://data.europa.eu/dr8/EuropeanLegalActRequirement
ABB name: eira:EuropeanLegalActRequirement
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/EuropeanLegalActRequirement
Interoperability Layer: Legal
Definition: Usability is a non-functional requirement that refers to the ease of use and learnability of a software system. It encompasses factors such as user interface design, navigation, and accessibility, and aims to ensure that the system is intuitive and efficient for users to interact with. Usability is important for ensuring user satisfaction, reducing errors and frustration, and ultimately improving the overall user experience.
Source: TOGAF
Source reference: https://pubs.opengroup.org/architecture/togaf9-doc/arch/chap03.html
Additional information: According to the TOGAF specification, Usability is a non-functional requirement that refers to the ease of use and learnability of a system or application. It encompasses various aspects such as user interface design, navigation, and user experience.
Usability is an important consideration for any system or application as it directly impacts user satisfaction and productivity. A system that is difficult to use or navigate can lead to frustration and errors, which can ultimately result in decreased productivity and user adoption.
To ensure that a system meets the usability requirement, it is important to consider the needs and expectations of the users. This can be achieved through user research and testing, as well as incorporating user feedback throughout the development process.
Usability can also be measured through various metrics such as task completion time, error rates, and user satisfaction surveys. These metrics can help identify areas for improvement and ensure that the system is meeting the needs of its users.
Overall, the usability non-functional requirement is an important consideration for any system or application and should be addressed throughout the development process to ensure user satisfaction and productivity.
Example: One example of the IT non-functional requirement 'Usability' could be that the software application should have a clear and intuitive user interface that is easy to navigate and understand, even for users who are not technically proficient. This could include features such as clear labeling of buttons and menus, consistent design elements throughout the application, and the ability to customize the interface to suit individual user preferences. Additionally, the application should be responsive and fast, with minimal lag or delays when performing tasks or loading data.
LOST view: Digital Solution Non-Functional Requirements Catalogue view
Identifier: http://data.europa.eu/dr8/egovera/UsabilityRequirement
EIRA traceability: eira:DigitalSolutionNonFunctionalRequirementRequirement
ABB name: egovera:UsabilityRequirement
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-05-16
dct:identifier: http://data.europa.eu/dr8/egovera/UsabilityRequirement
dct:title: Usability Non-Functional Requirement
Description: Regulation (EU) 2018/302, also known as the Geo-blocking Regulation, is a legislation passed by the European Parliament and Council in February 2018. The regulation aims to address unjustified geo-blocking and other forms of discrimination based on customers' nationality, place of residence, or place of establishment within the internal market. It amends existing regulations and directives to ensure that consumers can access and purchase goods and services online without facing discrimination or restrictions based on their location. The regulation seeks to create a more unified and fair internal market within the European Union.
Publisher: EUR-Lex
Source: http://data.europa.eu/eli/reg/2018/302/oj
Last modification: 26/06/2023
EIRA traceability: eira:BindingInstrumentRequirement
LOST view: Legal view - Binding Power and Jurisdiction
EIRA concept: eira:SolutionBuildingBlock
Additional identifier: http://data.europa.eu/eli/reg/2018/302/oj
Title: Regulation (EU) 2018/302 of the European Parliament and of the Council of 28 February 2018 on addressing unjustified geo-blocking and other forms of discrimination based on customers' nationality, place of residence or place of establishment within the internal market and amending Regulations (EC) No 2006/2004 and (EU) 2017/2394 and Directive 2009/22/EC
Example: Regulation 2018/302, also known as the Geo-blocking Regulation, aims to eliminate unjustified geo-blocking and other forms of discrimination based on customers' nationality, place of residence, or place of establishment within the European Union's internal market. Here are some examples of its application:
Definition: Security is a non-functional requirement that refers to the ability of a system to protect itself against unauthorized access, data breaches, and other malicious activities. It involves implementing measures such as encryption, access controls, firewalls, and intrusion detection systems to safeguard the system and its data. Security is essential for any system that handles sensitive information or performs critical functions, as a breach can result in significant financial, legal, and reputational damage. Therefore, security must be a top priority in the design, development, and deployment of any IT system.
Source: TOGAF
Source reference: https://pubs.opengroup.org/architecture/togaf9-doc/arch/chap03.html
Additional information: According to the TOGAF specification, guidelines, and documentation, the non-functional requirement of "Security" refers to the ability of a system to protect against unauthorized access, modification, or destruction of data. This requirement encompasses a range of security measures, including authentication, authorization, encryption, and auditing.
To meet the Security requirement, a system must be designed to ensure that only authorized users can access sensitive data or perform certain actions. This may involve implementing strong passwords, multi-factor authentication, or other access control mechanisms. Additionally, the system must be able to detect and prevent unauthorized access attempts, such as through intrusion detection systems or firewalls.
Another aspect of the Security requirement is data protection. This involves ensuring that data is encrypted both in transit and at rest, and that appropriate measures are in place to prevent data loss or corruption. The system must also be able to recover from security incidents, such as by restoring data from backups or rolling back transactions.
Finally, the Security requirement includes auditing and monitoring capabilities. The system must be able to track user activity and generate audit logs, which can be used to investigate security incidents or comply with regulatory requirements. This may involve implementing logging and monitoring tools, as well as establishing policies and procedures for reviewing and analyzing audit data.
Example: One example of an IT non-functional requirement for security could be that the system must have a secure login process that includes multi-factor authentication and password complexity requirements to prevent unauthorized access.
LOST view: Digital Solution Non-Functional Requirements Catalogue view
Identifier: http://data.europa.eu/dr8/egovera/SecurityRequirement
EIRA traceability: eira:DigitalSolutionNonFunctionalRequirementRequirement
ABB name: egovera:SecurityRequirement
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-05-16
dct:identifier: http://data.europa.eu/dr8/egovera/SecurityRequirement
dct:title: Security Non-Functional Requirement
Definition: Logging is an IT non-functional requirement that involves the recording of events and activities within a system or application. This includes capturing information such as user actions, system errors, and performance metrics. The purpose of logging is to provide a detailed record of system behavior that can be used for troubleshooting, auditing, and analysis. Logging is essential for ensuring the security and reliability of IT systems, as it enables administrators to identify and address issues quickly and effectively. Additionally, logging can help organizations meet regulatory compliance requirements by providing a comprehensive record of system activity.
Source: TOGAF
Source reference: https://pubs.opengroup.org/architecture/togaf9-doc/arch/chap03.html
Additional information: According to the TOGAF specification, guidelines, and documentation, the non-functional requirement of 'Logging' refers to the ability of a system to record and store information about its activities and events in a structured and organized manner. This information can be used for various purposes, such as troubleshooting, auditing, compliance, and performance analysis.
The logging requirement should specify the types of events that need to be logged, the format and structure of the log data, the storage location and retention period, and the access control and security measures for the log files. The logging mechanism should be reliable, efficient, and scalable, and should not impact the performance or availability of the system.
The logging requirement should also consider the legal and regulatory requirements for data privacy, protection, and disclosure. The log data should be encrypted, anonymized, or masked if necessary, and should only be accessible to authorized personnel with a legitimate need to know.
The logging requirement should be documented in the system architecture and design, and should be tested and validated during the system development and deployment phases. The logging mechanism should be monitored and maintained throughout the system lifecycle, and should be updated or improved as needed to meet changing business and technical requirements.
Example: One example of the IT non-functional requirement 'Logging' could be for a financial application to log all user activity and transactions for auditing and compliance purposes. This would include logging user login and logout times, as well as any changes made to account balances or transactions. The logs would need to be secure and tamper-proof, with access restricted to authorized personnel only. The system would also need to be able to generate reports based on the logged data, such as transaction histories or user activity summaries.
LOST view: Digital Solution Non-Functional Requirements Catalogue view
Identifier: http://data.europa.eu/dr8/egovera/LoggingRequirement
EIRA traceability: eira:DigitalSolutionNonFunctionalRequirementRequirement
ABB name: egovera:LoggingRequirement
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-05-16
dct:identifier: http://data.europa.eu/dr8/egovera/LoggingRequirement
dct:title: Logging Non-Functional Requirement
Definition: Maintainability is an important non-functional requirement in IT that refers to the ease with which a software system can be modified, updated, or repaired. A maintainable system is one that can be easily understood, tested, and modified without causing any unintended consequences or errors. This requirement is critical for ensuring that the system can be adapted to changing business needs or technological advancements, and that it can be maintained over time without incurring excessive costs or downtime. Factors that contribute to maintainability include clear documentation, modular design, and adherence to coding standards and best practices.
Source: TOGAF
Source reference: https://pubs.opengroup.org/architecture/togaf9-doc/arch/chap03.html
Additional information: According to the TOGAF specification, Maintainability is a non-functional requirement that refers to the ease with which a system can be modified, updated, or repaired. This requirement is important because it ensures that the system can be adapted to changing business needs and technological advancements without incurring excessive costs or downtime.
To achieve Maintainability, the system should be designed with modularity, scalability, and flexibility in mind. This means that the system should be composed of independent components that can be easily replaced or upgraded without affecting the rest of the system. Additionally, the system should be able to handle increased usage or data volumes without requiring significant changes to the underlying architecture.
To ensure Maintainability, the system should also be well-documented and adhere to established coding standards and best practices. This will make it easier for developers to understand and modify the system as needed. Additionally, the system should be tested thoroughly to ensure that any changes or updates do not introduce new bugs or issues.
Overall, Maintainability is an important non-functional requirement that ensures the long-term viability and adaptability of a system. By designing with Maintainability in mind, organizations can ensure that their systems remain effective and efficient in the face of changing business needs and technological advancements.
Example: The software system should be designed in a way that allows for easy maintenance and updates to be made without disrupting the overall functionality of the system. This includes clear and concise documentation, modular code structure, and the ability to easily identify and fix bugs or errors.
LOST view: Digital Solution Non-Functional Requirements Catalogue view
Identifier: http://data.europa.eu/dr8/egovera/MaintainabilityRequirement
EIRA traceability: eira:DigitalSolutionNonFunctionalRequirementRequirement
ABB name: egovera:MaintainabilityRequirement
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-05-16
dct:identifier: http://data.europa.eu/dr8/egovera/MaintainabilityRequirement
dct:title: Maintainability Non-Functional Requirement
Definition: Extensibility is an IT non-functional requirement that refers to the ability of a system to easily accommodate future changes or additions without requiring significant modifications to the existing system. This means that the system should be designed in a way that allows for new features, functionalities, and technologies to be added seamlessly, without disrupting the existing system's performance or stability. Extensibility is important for ensuring that the system remains relevant and adaptable to changing business needs and technological advancements. It also helps to reduce the cost and effort required for future upgrades and maintenance.
Source: TOGAF
Source reference: https://pubs.opengroup.org/architecture/togaf9-doc/arch/chap03.html
Additional information: According to the TOGAF specification, Extensibility is a non-functional requirement that refers to the ability of a system or application to be easily extended or modified without affecting its existing functionality. This requirement is important for organizations that need to adapt to changing business requirements or technological advancements.
The Extensibility requirement can be achieved through the use of modular and scalable architectures that allow for the addition of new components or features. This can be achieved through the use of open standards, APIs, and other integration mechanisms that enable the integration of new functionality into the existing system.
To ensure that the Extensibility requirement is met, it is important to establish clear guidelines and standards for the development and integration of new components. This includes defining the interfaces and protocols that will be used for communication between different components, as well as establishing testing and validation procedures to ensure that new components are compatible with the existing system.
In addition, it is important to consider the impact of extensibility on system performance and scalability. This may require the use of distributed architectures, load balancing mechanisms, and other techniques to ensure that the system can handle the increased load and complexity that comes with the addition of new components.
Overall, the Extensibility requirement is an important consideration for organizations that need to adapt to changing business requirements and technological advancements. By following the TOGAF guidelines and documentation, organizations can ensure that their systems are designed to be easily extended and modified, while maintaining their existing functionality and performance.
Example: An example of the IT non-functional requirement 'Extensibility' could be that the software system should be designed in such a way that it can easily accommodate new features and functionalities in the future without requiring significant changes to the existing codebase. This means that the system should be modular, with clear separation of concerns and well-defined interfaces between different components, so that new modules can be added or existing ones can be modified without affecting the rest of the system. Additionally, the system should be designed with scalability in mind, so that it can handle increased load and data volumes as the user base grows.
LOST view: Digital Solution Non-Functional Requirements Catalogue view
Identifier: http://data.europa.eu/dr8/egovera/ExtensibilityRequirement
EIRA traceability: eira:DigitalSolutionNonFunctionalRequirementRequirement
ABB name: egovera:ExtensibilityRequirement
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-05-16
dct:identifier: http://data.europa.eu/dr8/egovera/ExtensibilityRequirement
dct:title: Extensibility Non-Functional Requirement
Definition: National Legal Act ABB is a Requirement enabling the adoption of laws on a national level.
Source: Eur-Lex
Source reference: https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=LEGISSUM:ai0032
Example: he following implementation is an example of how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): Real Decreto 4/2010, de 8 de enero, por el que se regula el Esquema Nacional de Interoperabilidad en el ámbito de la Administración Electrónica. https://www.boe.es/eli/es/rd/2010/01/08/4. The example provider is a National Regulation from Spanish National Government regulating the Interoperability Scheme.
Interoperability Dimension: Structural IoP
LOST view: Legal view
Interoperability Saliency: National Legal Act ABB is salient for legal interoperability because it helps to achieve different EU member states legal and juridical certainty in the exchange of information for public services.
Identifier: http://data.europa.eu/dr8/NationalLegalActRequirement
ABB name: eira:NationalLegalActRequirement
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/NationalLegalActRequirement
Interoperability Layer: Legal
Definition: Configurability is an IT non-functional requirement that refers to the ability of a system or software to be easily customized or modified to meet the specific needs or preferences of different users or organizations. This includes the ability to change settings, parameters, and other aspects of the system without requiring extensive programming or technical knowledge. Configurability is important for ensuring that the system can adapt to changing requirements and environments, and can be tailored to meet the unique needs of different users or organizations.
Source: TOGAF
Source reference: https://pubs.opengroup.org/architecture/togaf9-doc/arch/chap03.html
Additional information: According to the TOGAF specification, configurability is a non-functional requirement that refers to the ability of a system or application to be easily configured or customized to meet the specific needs of different users or organizations. This includes the ability to modify settings, parameters, and other configuration options without requiring significant changes to the underlying code or architecture of the system.
Configurability is an important non-functional requirement for many systems, particularly those that are used by multiple organizations or users with different requirements. By providing a high degree of configurability, these systems can be adapted to meet the specific needs of each user or organization, without requiring significant customization or development efforts.
To meet the configurability requirement, systems should provide a range of configuration options that are easy to access and modify. These options should be well-documented and clearly explained, so that users can understand how to make the necessary changes. Additionally, systems should be designed in a modular and flexible way, so that changes to one part of the system do not require significant changes to other parts.
Overall, configurability is an important non-functional requirement that can help to ensure that systems are adaptable and flexible enough to meet the needs of different users and organizations. By following the TOGAF guidelines and best practices for configurability, organizations can ensure that their systems are well-designed and easy to use, while also providing the necessary flexibility and customization options to meet the needs of their users.
Example: One example of the IT non-functional requirement 'Configurability' could be the ability for a software application to be easily customized and adapted to meet the specific needs and requirements of different users or organizations. This could include features such as the ability to modify user interface elements, configure system settings and preferences, and integrate with other software systems or platforms. By providing a high degree of configurability, the application can be more easily tailored to meet the unique needs of different users, improving overall usability and user satisfaction.
LOST view: Digital Solution Non-Functional Requirements Catalogue view
Identifier: http://data.europa.eu/dr8/egovera/ConfigurabilityRequirement
EIRA traceability: eira:DigitalSolutionNonFunctionalRequirementRequirement
ABB name: egovera:ConfigurabilityRequirement
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-05-16
dct:identifier: http://data.europa.eu/dr8/egovera/ConfigurabilityRequirement
dct:title: Configurability Non-Functional Requirement
Definition: Legal clauses ABB is a Requirement that refers to specific points or topics that permit to specify a legal document.
Source: European Comision
Source reference: https://commission.europa.eu/law/law-making-process/types-eu-law_en
Example: The following implementation is an example of how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): Clause 6 - Description of the transfer(s): The details of the transfer(s), and in particular the categories of personal data that are transferred and the purpose(s) for which they are transferred, are specified in Annex I.B. (http://data.europa.eu/eli/dec_impl/2021/914/oj)
Interoperability Dimension: Structural IoP
LOST view: Legal view
Identifier: http://data.europa.eu/dr8/LegalClausesRequirement
ABB name: eira:LegalClausesRequirement
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/LegalClausesRequirement
Interoperability Layer: Legal
Description: The European Interoperability Framework (EIF) is a communication from the European Commission to various European institutions, including the European Parliament and the Council. It outlines the implementation strategy for achieving interoperability across European public administrations. The framework aims to promote the seamless exchange of information and services between different public administrations, enabling efficient and effective governance. It provides guidelines and principles for the development and implementation of interoperable digital solutions, emphasizing the use of open standards and specifications. The EIF seeks to enhance collaboration and cooperation among European public administrations, ultimately improving the delivery of public services to citizens and businesses.
Publisher: EUR-Lex
Source: https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=COM%3A2017%3A134%3AFIN
Last modification: 26/06/2023
EIRA traceability: eira:Non-bindingInstrumentRequirement
LOST view: Legal view - Binding Power and Jurisdiction
EIRA concept: eira:SolutionBuildingBlock
Additional identifier: https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=COM%3A2017%3A134%3AFIN
Title: COMMUNICATION FROM THE COMMISSION TO THE EUROPEAN PARLIAMENT, THE COUNCIL, THE EUROPEAN ECONOMIC AND SOCIAL COMMITTEE AND THE COMMITTEE OF THE REGIONS European Interoperability Framework – Implementation Strategy
Example: The European Interoperability Framework (EIF) is a set of guidelines and recommendations for promoting interoperability in the European Union (EU). The implementation strategy of the EIF provides specific examples of how the framework can be applied in various domains. Here are some examples:\n\n1. eGovernment Services: The EIF promotes the development of interoperable eGovernment services across EU member states. For example, it encourages the use of common data formats and standards to ensure that citizens can access and use public services seamlessly, regardless of their location. This could include services such as online tax filing, healthcare access, or business registration.\n\n2. Cross-Border Data Exchange: The EIF facilitates the exchange of data between different public administrations and agencies across borders. For instance, it encourages the use of common data models and protocols to enable the seamless sharing of information between law enforcement agencies, customs authorities, or healthcare providers. This ensures efficient collaboration and improves the effectiveness of cross-border operations.\n\n3. Public Procurement: The EIF promotes interoperability in public procurement processes. It encourages the use of common standards and specifications for electronic procurement systems, making it easier for businesses to participate in public tenders across different member states. This reduces administrative burden and increases transparency and competition in the procurement process.\n\n4. Health Information Systems: The EIF supports the development of interoperable health information systems. It promotes the use of common data models and standards to enable the exchange of patient data between healthcare providers, ensuring continuity of care and improving patient safety. This could include electronic health records, telemedicine services, or interoperable prescription systems.\n\n5. Smart Cities: The EIF can be applied to promote interoperability in smart city initiatives. It encourages the use of common data formats and interfaces to enable the integration of various urban services, such as transportation, energy management, or waste management. This allows cities to optimize resource allocation, improve citizen services, and enhance sustainability.\n\nThese examples demonstrate how the European Interoperability Framework can be applied in various domains to promote seamless information exchange, collaboration, and service delivery across the EU. By adopting common standards and practices, the EIF aims to enhance efficiency, reduce costs, and improve the user experience for citizens, businesses, and public administrations.
Description: Directive (EU) 2016/2102, also known as the Web Accessibility Directive, is a directive issued by the European Parliament and Council in October 2016. It aims to improve the accessibility of websites and mobile applications of public sector bodies within the European Union. The directive requires these entities to ensure that their digital platforms are accessible to all individuals, including those with disabilities. This includes making content perceivable, operable, understandable, and robust, as well as providing alternative formats and assistive technologies. The directive aims to promote equal access to information and services online for all citizens.
Publisher: EUR-Lex
Source: https://eur-lex.europa.eu/eli/dir/2016/2102/oj
Last modification: 26/06/2023
EIRA traceability: eira:BindingInstrumentRequirement
LOST view: Legal view - Binding Power and Jurisdiction
EIRA concept: eira:SolutionBuildingBlock
Additional identifier: https://eur-lex.europa.eu/eli/dir/2016/2102/oj
Title: Directive (EU) 2016/2102 of the European Parliament and of the Council of 26 October 2016 on the accessibility of the websites and mobile applications of public sector bodies
Example: The Web Accessibility Directive aims to ensure that websites and mobile applications of public sector bodies in the European Union are accessible to all users, including those with disabilities. Here are some examples of how this directive can be applied:
Definition: Privacy is an important non-functional requirement in IT systems that ensures the protection of sensitive information from unauthorized access, use, or disclosure. It involves implementing security measures such as encryption, access controls, and data masking to safeguard personal and confidential data. Privacy also includes compliance with legal and regulatory requirements such as GDPR, HIPAA, and CCPA. Maintaining privacy in IT systems is crucial for building trust with users and protecting their personal information from potential threats.
Source: TOGAF
Source reference: https://pubs.opengroup.org/architecture/togaf9-doc/arch/chap03.html
Additional information: According to the TOGAF specification, guidelines, and documentation, the non-functional requirement of 'Privacy' refers to the ability of a system to protect the confidentiality, integrity, and availability of personal information. This requirement is essential for ensuring that sensitive data is not disclosed to unauthorized parties, and that individuals have control over how their personal information is collected, used, and shared.
To meet the Privacy requirement, the system must comply with relevant laws, regulations, and industry standards related to data protection and privacy. This includes implementing appropriate security measures such as encryption, access controls, and data masking to prevent unauthorized access, modification, or disclosure of personal information.
The system must also provide users with clear and concise privacy policies that explain how their personal information is collected, used, and shared. Users must be given the option to opt-out of data collection or sharing, and their consent must be obtained before any personal information is collected or used.
In addition, the system must have mechanisms in place to detect and respond to privacy breaches. This includes monitoring for unauthorized access or use of personal information, and taking appropriate action to mitigate any potential harm to affected individuals.
Overall, the Privacy non-functional requirement is critical for ensuring that personal information is protected and that individuals have control over their data. By meeting this requirement, the system can build trust with users and stakeholders, and avoid potential legal or reputational risks associated with privacy breaches.
Example: One example of the IT non-functional requirement 'Privacy' could be that the system must ensure that all user data is encrypted and stored securely to prevent unauthorized access or data breaches.
LOST view: Digital Solution Non-Functional Requirements Catalogue view
Identifier: http://data.europa.eu/dr8/egovera/PrivacyRequirement
EIRA traceability: eira:DigitalSolutionNonFunctionalRequirementRequirement
ABB name: egovera:PrivacyRequirement
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-05-16
dct:identifier: http://data.europa.eu/dr8/egovera/PrivacyRequirement
dct:title: Privacy Non-Functional Requirement
Definition: Authentication is a non-functional requirement that ensures that only authorized users can access a system or application. It involves verifying the identity of the user through various means such as passwords, biometric identification, or security tokens. Authentication is crucial for maintaining the security and integrity of a system, as it prevents unauthorized access and protects sensitive information from being compromised. It also helps to ensure accountability and traceability by keeping a record of user activities.
Source: TOGAF
Source reference: https://pubs.opengroup.org/architecture/togaf9-doc/arch/chap03.html
Additional information: According to the TOGAF specification, Authentication is a non-functional requirement that refers to the process of verifying the identity of a user or system. It is a critical aspect of security and is necessary to ensure that only authorized users or systems can access the system or application.
The Authentication non-functional requirement can be further broken down into several sub-requirements, including:
1. Identification - The process of identifying a user or system based on a unique identifier such as a username, email address, or IP address.
2. Authentication Mechanisms - The methods used to verify the identity of a user or system, such as passwords, biometric authentication, or two-factor authentication.
3. Authorization - The process of granting or denying access to specific resources or functions based on the authenticated user's permissions.
4. Audit Trail - The ability to track and record all authentication attempts and actions taken by authenticated users or systems.
5. Security - The requirement to ensure that authentication mechanisms are secure and cannot be easily bypassed or compromised.
Overall, the Authentication non-functional requirement is critical to ensuring the security and integrity of a system or application and should be carefully considered and implemented in accordance with industry best practices and standards.
Example: An example of the IT non-functional requirement 'Authentication' could be that a user must provide a valid username and password to access a secure system or application. This ensures that only authorized users are able to access sensitive information or perform certain actions within the system. Additionally, the system may require multi-factor authentication, such as a security token or biometric verification, to further enhance security and prevent unauthorized access.
LOST view: Digital Solution Non-Functional Requirements Catalogue view
Identifier: http://data.europa.eu/dr8/egovera/AuthenticationRequirement
EIRA traceability: eira:DigitalSolutionNonFunctionalRequirementRequirement
ABB name: egovera:AuthenticationRequirement
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-05-16
dct:identifier: http://data.europa.eu/dr8/egovera/AuthenticationRequirement
dct:title: Authentication Non-Functional Requirement
Definition: Compatibility is an IT non-functional requirement that refers to the ability of a system or software to function properly with other systems, software, hardware, or environments. It ensures that the system can operate seamlessly with other systems, without any compatibility issues or conflicts. Compatibility is essential for ensuring that the system can integrate with other systems and can be used by a wide range of users, regardless of their hardware or software configurations. It also ensures that the system can be easily upgraded or migrated to newer versions without any compatibility issues.
Source: TOGAF
Source reference: https://pubs.opengroup.org/architecture/togaf9-doc/arch/chap03.html
Additional information: According to the TOGAF specification, Compatibility is an IT non-functional requirement that refers to the ability of a system or application to operate in conjunction with other systems or applications. This requirement ensures that the system or application can integrate seamlessly with other systems or applications without causing any disruption or compatibility issues.
Compatibility can be achieved through adherence to industry standards, protocols, and interfaces. The system or application must be designed to work with different operating systems, hardware, and software configurations. It should also be able to communicate with other systems or applications using standard communication protocols.
The compatibility requirement also includes backward compatibility, which ensures that the system or application can work with older versions of software or hardware. This is important to ensure that users can continue to use the system or application even if they have not upgraded their hardware or software.
To ensure compatibility, it is important to conduct thorough testing and validation of the system or application. This includes testing for interoperability with other systems or applications, as well as testing for compatibility with different hardware and software configurations.
Overall, the compatibility requirement is critical to ensure that the system or application can work seamlessly with other systems or applications, and that users can continue to use the system or application without any disruption or compatibility issues.
Example: One example of the IT non-functional requirement 'Compatibility' could be ensuring that a software application is compatible with multiple operating systems such as Windows, Mac, and Linux. This would ensure that the application can be used by a wider range of users regardless of their preferred operating system.
LOST view: Digital Solution Non-Functional Requirements Catalogue view
Identifier: http://data.europa.eu/dr8/egovera/CompatibilityRequirement
EIRA traceability: eira:DigitalSolutionNonFunctionalRequirementRequirement
ABB name: egovera:CompatibilityRequirement
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-05-16
dct:identifier: http://data.europa.eu/dr8/egovera/CompatibilityRequirement
dct:title: Compatibility Non-Functional Requirement
Definition: Replication is an IT non-functional requirement that refers to the ability of a system to duplicate or copy data or processes across multiple servers or locations. This is important for ensuring high availability and reliability of the system, as well as for disaster recovery purposes. Replication can be achieved through various techniques such as database replication, file replication, or server replication. The system should be able to handle replication in a seamless and efficient manner, without compromising performance or security.
Source: TOGAF
Source reference: https://pubs.opengroup.org/architecture/togaf9-doc/arch/chap03.html
Additional information: According to the TOGAF specification, Replication is a non-functional requirement that refers to the ability of a system to duplicate or copy data, processes, or services across multiple locations or instances. This requirement is important for ensuring high availability, fault tolerance, and disaster recovery capabilities.
The Replication requirement can be further broken down into several sub-requirements, including:
1. Data Replication: This refers to the ability of a system to replicate data across multiple locations or instances. This can be achieved through various techniques such as database replication, file replication, or object replication.
2. Process Replication: This refers to the ability of a system to replicate processes or services across multiple locations or instances. This can be achieved through techniques such as load balancing, clustering, or virtualization.
3. Synchronization: This refers to the ability of a system to ensure that replicated data, processes, or services are kept in sync across all instances. This can be achieved through techniques such as data synchronization, process synchronization, or service synchronization.
4. Performance: This refers to the ability of a system to maintain performance levels even when replicating data, processes, or services across multiple locations or instances. This can be achieved through techniques such as caching, compression, or optimization.
Overall, the Replication requirement is critical for ensuring that a system can provide high availability, fault tolerance, and disaster recovery capabilities. It is important to carefully consider the specific sub-requirements and techniques that will be used to achieve this requirement in order to ensure that the system is able to meet its performance and reliability goals.
Example: One example of the IT non-functional requirement 'Replication' is in a database system where data needs to be replicated across multiple servers for redundancy and fault tolerance. This ensures that if one server fails, the data can still be accessed from another server without any disruption to the system. The replication process should be seamless and transparent to the end-users, ensuring that they can access the data without any delay or interruption. Additionally, the replication process should be efficient and scalable, allowing for easy addition of new servers as the system grows.
LOST view: Digital Solution Non-Functional Requirements Catalogue view
Identifier: http://data.europa.eu/dr8/egovera/ReplicationRequirement
EIRA traceability: eira:DigitalSolutionNonFunctionalRequirementRequirement
ABB name: egovera:ReplicationRequirement
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-05-16
dct:identifier: http://data.europa.eu/dr8/egovera/ReplicationRequirement
dct:title: Replication Non-Functional Requirement
Definition: Authenticity is an IT non-functional requirement that ensures that the information or data presented is genuine and trustworthy. It is essential to maintain the integrity of the system and prevent unauthorized access or tampering of data. Authenticity can be achieved through various methods such as encryption, digital signatures, and access control mechanisms. It is crucial for systems that handle sensitive information, such as financial transactions, medical records, or legal documents, to ensure authenticity to maintain the trust of users and stakeholders.
Source: TOGAF
Source reference: https://pubs.opengroup.org/architecture/togaf9-doc/arch/chap03.html
Additional information: According to the TOGAF specification, Authenticity is a non-functional requirement that refers to the ability of a system to ensure that the information or data being processed or transmitted is genuine and has not been tampered with or altered in any way. This requirement is essential for systems that deal with sensitive or confidential information, such as financial transactions, personal data, or medical records.
To meet the Authenticity requirement, the system must implement appropriate security measures, such as encryption, digital signatures, or access controls, to prevent unauthorized access, modification, or deletion of data. The system must also ensure that the data is accurate, complete, and consistent, and that it can be traced back to its original source.
Furthermore, the system must provide mechanisms for detecting and reporting any attempts to tamper with the data, such as intrusion detection systems or audit logs. It must also have procedures in place for responding to security incidents, such as notifying the appropriate authorities or taking corrective actions to prevent further damage.
Overall, the Authenticity requirement is critical for ensuring the integrity and trustworthiness of the system and the data it processes. It is a key component of a comprehensive security strategy and must be carefully considered and implemented to meet the needs of the organization and its stakeholders.
Example: One example of the IT non-functional requirement 'Authenticity' could be ensuring that only authorized users have access to sensitive data or systems. This can be achieved through various authentication methods such as passwords, biometrics, or two-factor authentication. The system should also be able to detect and prevent unauthorized access attempts.
LOST view: Digital Solution Non-Functional Requirements Catalogue view
Identifier: http://data.europa.eu/dr8/egovera/AuthenticityRequirement
EIRA traceability: eira:DigitalSolutionNonFunctionalRequirementRequirement
ABB name: egovera:AuthenticityRequirement
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-05-16
dct:identifier: http://data.europa.eu/dr8/egovera/AuthenticityRequirement
dct:title: Authenticity Non-Functional Requirement
Definition: Scalability is an important non-functional requirement for any IT system, which refers to the ability of the system to handle increasing amounts of workload or users without compromising its performance or stability. A scalable system should be able to accommodate growth in data volume, traffic, and user base, by adding more resources or nodes to the system, without causing any downtime or degradation in response time. Scalability is critical for ensuring that the system can meet the demands of the business, adapt to changing requirements, and provide a seamless user experience.
Source: TOGAF
Source reference: https://pubs.opengroup.org/architecture/togaf9-doc/arch/chap03.html
Additional information: According to the TOGAF specification, scalability is a non-functional requirement that refers to the ability of a system to handle increasing amounts of work or traffic without experiencing a decrease in performance or stability. This requirement is important for systems that are expected to grow or expand over time, as it ensures that the system can handle the increased workload without compromising its functionality or reliability.
Scalability can be achieved through a variety of techniques, including horizontal scaling (adding more servers or nodes to distribute the workload), vertical scaling (adding more resources to a single server or node), and load balancing (distributing the workload across multiple servers or nodes). It is important to consider scalability early in the design process, as it can impact the overall architecture and infrastructure of the system.
To ensure that scalability is achieved, it is important to establish performance metrics and benchmarks, and to regularly test and monitor the system to identify any bottlenecks or areas for improvement. Additionally, the system should be designed with modularity and flexibility in mind, so that it can be easily adapted and expanded as needed.
Overall, scalability is a critical non-functional requirement for any system that is expected to grow or evolve over time, and should be carefully considered and addressed in the design and implementation phases of the system development lifecycle.
Example: An example of the IT non-functional requirement 'Scalability' could be a web application that needs to handle a large number of concurrent users. The application should be able to scale up or down based on the number of users accessing it at any given time. This means that the application should be able to handle a sudden surge in traffic without crashing or slowing down. Additionally, the application should be able to add more resources such as servers or storage as needed to accommodate the increased traffic.
LOST view: Digital Solution Non-Functional Requirements Catalogue view
Identifier: http://data.europa.eu/dr8/egovera/ScalabilityRequirement
EIRA traceability: eira:DigitalSolutionNonFunctionalRequirementRequirement
ABB name: egovera:ScalabilityRequirement
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-05-16
dct:identifier: http://data.europa.eu/dr8/egovera/ScalabilityRequirement
dct:title: Scalability Non-Functional Requirement
Definition: Legal Act ABB is a Business Object formalising a set of rules on a subject potentially including requirements concerning digital public services.
Source: European Union Law
Source reference: https://eur-lex.europa.eu/summary/glossary/legislative_acts.html
Synonym: Legal Instrument
Additional information: The granularity of the requirements might be of high level or detail level. Requirements of high-level granularity contain generic/abstract functional requirements like principles and/or recommendations with considerable degrees for transposition/execution and of not binding nature. On the other side, requirements of detail-level granularity imply a limited degree for transposition/execution and they contain specific/concrete functionalities, solution components, data, procedures, and/or technical specifications or standards to be used. EU legal acts are legislative or non-legislative acts adopted by the European institutions (Article 288 TFEU). With the entry into force of the Treaty of Lisbon on 1 December 2009. The names "European Union" or "EU" have replaced "European Community", "Community" or "EC".
Example: The following implementation is an example of how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): The COMMISSION REGULATION (EU) 2018/1881 of 3 December 2018 amending Regulation (EC) No 1907/2006 of the European Parliament and of the Council on the Registration, Evaluation, Authorisation and Restriction of Chemicals (REACH) as regards Annexes I, III,VI, VII, VIII, IX, X, XI, and XII to address nanoforms of substances (https://eur-lex.europa.eu/legal-content/EN/TXT/?qid=1544102387245&uri=CELEX:32018R1881) is an example of an SBB implementing a Legal Act ABB.
Interoperability Dimension: Structural IoP
LOST view: Legal view
Viewpoint: Interoperability Privacy viewpoint
Interoperability Saliency: The Legal Act ABB is salient for legal interoperability because it helps establish legal rules by ensuring compatible legal/juridical certainty in the exchange of information.
Identifier: http://data.europa.eu/dr8/LegalActRequirement
ABB name: eira:LegalActRequirement
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/LegalActRequirement
Interoperability Layer: Legal
Description: Regulation 2018/644, also known as the Regulation on cross-border parcel delivery services, is a legislation enacted by the European Parliament and Council on 18 April 2018. The regulation aims to improve the transparency, affordability, and quality of cross-border parcel delivery services within the European Union. It introduces measures to enhance price transparency, increase competition, and provide consumers with more information about delivery options and prices. The regulation also establishes a regulatory framework to address issues related to access to essential facilities and the resolution of disputes between service providers. Overall, it seeks to promote a more efficient and competitive market for cross-border parcel delivery services in the EU.
Publisher: EUR-Lex
Source: http://data.europa.eu/eli/reg/2018/644/oj
Last modification: 26/06/2023
EIRA traceability: eira:BindingInstrumentRequirement
LOST view: Legal view - Binding Power and Jurisdiction
EIRA concept: eira:SolutionBuildingBlock
Additional identifier: http://data.europa.eu/eli/reg/2018/644/oj
Title: Regulation (EU) 2018/644 of the European Parliament and of the Council of 18 April 2018 on cross-border parcel delivery services (Text with EEA relevance)
Example: Regulation 2018/644, also known as the Regulation on cross-border parcel delivery services, aims to improve the transparency and affordability of cross-border parcel delivery within the European Union. Here are some examples of its application:
Definition: Resiliency is an IT non-functional requirement that refers to the ability of a system to recover quickly and efficiently from unexpected events or failures. This includes the ability to maintain availability, performance, and data integrity in the face of disruptions such as hardware failures, network outages, or cyber attacks. A resilient system is designed to minimize downtime, prevent data loss, and ensure business continuity, even in the face of adverse conditions. This requirement is critical for any system that needs to operate reliably and consistently, particularly in mission-critical applications such as financial services, healthcare, or emergency response.
Source: TOGAF
Source reference: https://pubs.opengroup.org/architecture/togaf9-doc/arch/chap03.html
Additional information: According to the TOGAF specification, Resiliency is a non-functional requirement that refers to the ability of an IT system to recover from failures or disruptions and continue to function as intended. This requirement is essential for ensuring that the system can withstand unexpected events such as hardware failures, power outages, or cyber-attacks.
To meet the Resiliency requirement, IT systems must be designed with redundancy and fault-tolerant mechanisms that enable them to continue operating even when one or more components fail. This may involve the use of backup systems, redundant hardware, or failover mechanisms that automatically switch to a backup system when the primary system fails.
In addition to technical measures, Resiliency also requires the implementation of robust disaster recovery and business continuity plans that outline procedures for responding to disruptions and restoring normal operations as quickly as possible. These plans should be regularly tested and updated to ensure that they remain effective in the face of changing threats and circumstances.
Overall, Resiliency is a critical non-functional requirement for IT systems that must be carefully considered and addressed throughout the entire system development lifecycle. By ensuring that systems are designed with Resiliency in mind, organizations can minimize the risk of downtime and data loss, and maintain the continuity of their operations even in the face of unexpected events.
Example: One example of the IT non-functional requirement 'Resiliency' could be that the system should be able to recover from hardware or software failures within a specified time frame, without losing any data or causing significant downtime. This could involve implementing redundancy measures such as backup servers, failover mechanisms, and data replication to ensure that the system can continue to operate even in the event of a failure. Additionally, the system should be able to handle high levels of traffic or usage without becoming overwhelmed or crashing, and should be able to scale up or down as needed to accommodate changing demands.
LOST view: Digital Solution Non-Functional Requirements Catalogue view
Identifier: http://data.europa.eu/dr8/egovera/ResiliencyRequirement
EIRA traceability: eira:DigitalSolutionNonFunctionalRequirementRequirement
ABB name: egovera:ResiliencyRequirement
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-05-16
dct:identifier: http://data.europa.eu/dr8/egovera/ResiliencyRequirement
dct:title: Resiliency Non-Functional Requirement
Definition: Authorization is a non-functional requirement in IT that refers to the process of granting or denying access to specific resources or functionalities within a system. It involves verifying the identity of a user and determining their level of access based on their role or permissions. Authorization is essential for ensuring the security and integrity of a system, as it prevents unauthorized users from accessing sensitive information or performing actions that could compromise the system. It also helps to maintain accountability by tracking user activity and ensuring that actions are performed by authorized individuals.
Source: TOGAF
Source reference: https://pubs.opengroup.org/architecture/togaf9-doc/arch/chap03.html
Additional information: Authorization is a non-functional requirement that is related to the security aspect of an IT system. It refers to the process of granting or denying access to resources or functionalities based on the identity and privileges of the user or entity requesting access.
According to the TOGAF specification, Authorization is a key aspect of security architecture and should be designed to ensure that only authorized users or entities can access the system or its resources. The authorization process should be based on a well-defined set of policies and rules that are consistent with the organization's security policies and regulatory requirements.
The TOGAF guidelines recommend that the authorization process should be implemented using a combination of authentication, authorization, and access control mechanisms. Authentication is the process of verifying the identity of the user or entity requesting access, while authorization is the process of determining whether the user or entity has the necessary privileges to access the requested resource. Access control is the process of enforcing the authorization decisions by controlling the actual access to the resource.
To ensure that the authorization process is effective, the TOGAF documentation recommends that the security architecture should include mechanisms for monitoring and auditing the authorization process. This will help to detect and prevent unauthorized access attempts and ensure that the system is compliant with the organization's security policies and regulatory requirements.
In summary, Authorization is a non-functional requirement that is critical for ensuring the security of an IT system. It should be designed based on a well-defined set of policies and rules, and implemented using a combination of authentication, authorization, and access control mechanisms. The authorization process should be monitored and audited to ensure that it is effective and compliant with the organization's security policies and regulatory requirements.
Example: One example of an IT non-functional requirement for Authorization could be that only users with specific roles or permissions are able to access certain features or data within a software application. This could include restrictions on who can create, edit, or delete certain types of content, or who can view sensitive information such as financial data or personal information. The authorization system should also be secure and reliable, ensuring that unauthorized users cannot gain access to restricted areas or data.
LOST view: Digital Solution Non-Functional Requirements Catalogue view
Identifier: http://data.europa.eu/dr8/egovera/AuthorizationRequirement
EIRA traceability: eira:DigitalSolutionNonFunctionalRequirementRequirement
ABB name: egovera:AuthorizationRequirement
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-05-16
dct:identifier: http://data.europa.eu/dr8/egovera/AuthorizationRequirement
dct:title: Authorization Non-Functional Requirement
Definition: Recoverability is an important non-functional requirement in IT that refers to the ability of a system to solve failures or errors and come-back to its normal functioning. This includes the ability to recover data, configurations, and settings after a system crash or other disruptions. Recoverability is critical for ensuring system availability and minimizing downtime, as well as for protecting against data loss and corruption. It involves implementing backup and recovery mechanisms, such as data replication, redundancy, and failover, to ensure that the system can quickly and reliably recover from any failures or errors.
Source: TOGAF
Source reference: https://pubs.opengroup.org/architecture/togaf9-doc/arch/chap03.html
Additional information: According to the TOGAF specification, Recoverability is a non-functional requirement that refers to the ability of a system to recover from failures or disasters. It is a critical aspect of system design and architecture, as it ensures that the system can continue to operate even in the event of unexpected events.
Recoverability includes a range of features and capabilities that enable a system to recover from failures, including backup and restore capabilities, fault tolerance, and disaster recovery planning. These features are designed to ensure that the system can quickly and efficiently recover from any type of failure, whether it is a hardware failure, software failure, or a natural disaster.
To achieve recoverability, system architects and designers must consider a range of factors, including the system's overall architecture, the types of failures that are most likely to occur, and the impact of those failures on the system's operations. They must also consider the cost and complexity of implementing recoverability features, as well as the potential impact on system performance and availability.
Overall, recoverability is a critical non-functional requirement that must be carefully considered and designed into any system architecture. By ensuring that a system can recover quickly and efficiently from failures, organizations can minimize downtime, reduce costs, and ensure that critical business operations can continue uninterrupted.
Example: In a banking application, the recoverability non-functional requirement would ensure that in case of a system failure or crash, the system can recover all the data and transactions that were in progress before the failure occurred. This would ensure that no data is lost and the system can resume normal operations without any major disruptions.
LOST view: Digital Solution Non-Functional Requirements Catalogue view
Identifier: http://data.europa.eu/dr8/egovera/RecoverabilityRequirement
EIRA traceability: eira:DigitalSolutionNonFunctionalRequirementRequirement
ABB name: egovera:RecoverabilityRequirement
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-05-16
dct:identifier: http://data.europa.eu/dr8/egovera/RecoverabilityRequirement
dct:title: Recoverability Non-Functional Requirement
Description: The Interoperable Europe Act is a proposal for a regulation that aims to establish a high level of public sector interoperability across the European Union. The regulation seeks to promote the seamless exchange of data and information between public sector entities, including national, regional, and local authorities, as well as public service providers. The proposal outlines a framework for achieving interoperability, including the development of common standards, the use of open data, and the establishment of a European Interoperability Framework. The regulation also includes provisions for ensuring data protection and privacy, as well as measures to promote transparency and accountability in the use of public sector data. Overall, the Interoperable Europe Act aims to improve the efficiency and effectiveness of public services across the EU by facilitating the exchange of information and data between different public sector entities.
Publisher: EUR-Lex
Source: https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A52022PC0720
Last modification: 26/06/2023
EIRA traceability: eira:BindingInstrumentRequirement
LOST view: Legal view - Binding Power and Jurisdiction
EIRA concept: eira:SolutionBuildingBlock
Additional identifier: https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A52022PC0720
Title: Proposal for a REGULATION OF THE EUROPEAN PARLIAMENT AND OF THE COUNCIL laying down measures for a high level of public sector interoperability across the Union (Interoperable Europe Act)
Example: The Interoperable Europe Act aims to improve the interoperability of public sector services across the European Union. Here are some examples of how this regulation could be applied:
Description: Directive (EU) 2022/2555, also known as the NIS2 Directive, is the EU-wide legislation on cybersecurity. It provides legal measures to boost the overall level of cybersecurity in the EU.
Publisher: EUR-Lex
Source: http://data.europa.eu/eli/dir/2022/2555/oj
Last modification: 26/06/2023
EIRA traceability: eira:BindingInstrumentRequirement
LOST view: Legal view - Binding Power and Jurisdiction
EIRA concept: eira:SolutionBuildingBlock
Additional identifier: http://data.europa.eu/eli/dir/2022/2555/oj
Title: Directive (EU) 2022/2555 of the European Parliament and of the Council of 14 December 2022 on measures for a high common level of cybersecurity across the Union, amending Regulation (EU) No 910/2014 and Directive (EU) 2018/1972, and repealing Directive (EU) 2016/1148 (NIS 2 Directive) (Text with EEA relevance)or a REGULATION OF THE EUROPEAN PARLIAMENT AND OF THE COUNCIL laying down measures to strengthen solidarity and capacities in the Union to detect, prepare for and respond to cybersecurity threats and incidents
Description: Regulation 2018/1807, also known as the "Regulation on the free flow of non-personal data in the European Union," was adopted by the European Parliament and Council on November 14, 2018. The regulation aims to establish a framework that enables the free movement of non-personal data across EU member states and prohibits unjustified data localization requirements. It seeks to promote the development of the digital economy by facilitating data sharing and portability, ensuring fair competition, and fostering innovation. The regulation also includes provisions for data protection and security, ensuring that the free flow of data does not compromise privacy or cybersecurity.
Publisher: EUR-Lex
Source: http://data.europa.eu/eli/reg/2018/1807/oj
Last modification: 26/06/2023
EIRA traceability: eira:BindingInstrumentRequirement
LOST view: Legal view - Binding Power and Jurisdiction
EIRA concept: eira:SolutionBuildingBlock
Additional identifier: http://data.europa.eu/eli/reg/2018/1807/oj
Title: Regulation (EU) 2018/1807 of the European Parliament and of the Council of 14 November 2018 on a framework for the free flow of non-personal data in the European Union
Description: The General Data Protection Regulation (GDPR) is a regulation enacted by the European Union in 2016 to protect the privacy and personal data of individuals within the EU. It establishes rules and guidelines for the processing of personal data by organizations, including the collection, storage, and transfer of such data. The GDPR aims to give individuals more control over their personal information and requires organizations to implement measures to ensure the security and confidentiality of the data they handle. It also introduces stricter penalties for non-compliance with the regulation. The GDPR replaces the previous Data Protection Directive and applies to all EU member states.
Publisher: EUR-Lex
Source: http://data.europa.eu/eli/reg/2016/679/2016-05-04
Last modification: 26/06/2023
EIRA traceability: eira:BindingInstrumentRequirement
LOST view: Legal view - Binding Power and Jurisdiction
EIRA concept: eira:SolutionBuildingBlock
Additional identifier: http://data.europa.eu/eli/reg/2016/679/2016-05-04
Title: Regulation (EU) 2016/679 of the European Parliament and of the Council of 27 April 2016 on the protection of natural persons with regard to the processing of personal data and on the free movement of such data, and repealing Directive 95/46/EC (General Data Protection Regulation)
Example: 1. Consent management: Under the GDPR, organizations are required to obtain explicit and informed consent from individuals before collecting and processing their personal data. This means that companies need to clearly explain why they are collecting the data, how it will be used, and give individuals the option to opt out or withdraw their consent at any time.
Definition: Deployability is an IT non-functional requirement that refers to the ease and efficiency with which software applications can be deployed and installed on different platforms and environments. It involves ensuring that the software can be easily installed, configured, and updated without causing any disruption to the existing system. Deployability is critical for ensuring that software can be quickly and easily rolled out to users, reducing downtime, and minimizing the risk of errors or conflicts. It also helps to ensure that the software can be easily maintained and updated over time, ensuring that it remains secure and up to date with the latest features and functionality.
Source: TOGAF
Source reference: https://pubs.opengroup.org/architecture/togaf9-doc/arch/chap03.html
Additional information: According to the TOGAF specification, guidelines, and documentation, the non-functional requirement of Deployability refers to the ease with which a system or application can be deployed into a production environment. This requirement encompasses a range of factors, including the ease of installation, configuration, and maintenance of the system, as well as the ability to scale the system to meet changing demands.
To meet the Deployability requirement, the system must be designed with a focus on ease of deployment. This can include the use of standard deployment tools and processes, such as automated deployment scripts and configuration management tools. The system must also be designed to be easily configurable, with clear documentation and support for common configuration scenarios.
In addition, the system must be designed to be easily maintainable, with clear documentation and support for common maintenance tasks. This can include the use of automated monitoring and alerting tools, as well as the ability to easily diagnose and resolve issues.
Finally, the system must be designed to be scalable, with the ability to easily add or remove resources as needed to meet changing demands. This can include the use of cloud-based infrastructure, as well as the ability to easily add or remove servers or other resources as needed.
Overall, the Deployability requirement is critical to ensuring that a system or application can be easily and reliably deployed into a production environment, and that it can be easily maintained and scaled to meet changing demands.
Example: One example of the IT non-functional requirement 'Deployability' could be the ability of a software application to be easily installed and configured on different operating systems and hardware configurations without requiring extensive technical knowledge or expertise. This could include features such as automated installation scripts, clear documentation and user guides, and compatibility with common deployment tools and platforms. The goal of this requirement is to ensure that the application can be quickly and efficiently deployed in a variety of environments, reducing the time and effort required for IT teams to set up and maintain the software.
LOST view: Digital Solution Non-Functional Requirements Catalogue view
Identifier: http://data.europa.eu/dr8/egovera/DeployabilityRequirement
EIRA traceability: eira:DigitalSolutionNonFunctionalRequirementRequirement
ABB name: egovera:DeployabilityRequirement
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-05-16
dct:identifier: http://data.europa.eu/dr8/egovera/DeployabilityRequirement
dct:title: Deployability Non-Functional Requirement
Definition: This ABB is a Business Agnostic National Legal Act which lays down rules regulating the provision and use of electronic delivery services to ensure a transparent and secure data exchange.
LOST view: LV-Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/NationalSchemaOnEDeliveryRequirement
ABB name: egovera:NationalSchemaOnEDeliveryRequirement
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-11-20
Name: National Schema on eDelivery
Identifier: egovera:NationalSchemaOnEDeliveryRequirement
Interoperability Layer: Legal
Specialises: http://data.europa.eu/dr8/BindingInstrumentRequirement
Definition: The National Schema on Cybersecurity is a comprehensive framework developed by a country's government to address and mitigate cyber threats and risks. It outlines a set of guidelines, best practices, and standards that organizations and individuals should follow to protect their digital assets and information from cyberattacks. The schema covers various aspects of cybersecurity, including risk assessment, incident response, data protection, network security, and employee awareness and training. It serves as a reference document for organizations to develop their cybersecurity strategies and ensure a consistent and coordinated approach to cybersecurity across the nation.
Example: The National Schema on Cybersecurity is a framework developed by governments to provide guidance and best practices for organizations to enhance their cybersecurity posture. Here are a few examples of how the National Schema on Cybersecurity can be applied:
LOST view: LV-Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/NationalSchemaOnCybersecurityRequirement
ABB name: egovera:NationalSchemaOnCybersecurityRequirement
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-11-20
Name: National Schema on Cybersecurity
Identifier: egovera:NationalSchemaOnCybersecurityRequirement
Interoperability Layer: Legal
Specialises: http://data.europa.eu/dr8/BindingInstrumentRequirement
Definition: Accessibility is an IT non-functional requirement that ensures the system or application can be used by people with disabilities or impairments. This includes providing features such as screen readers, keyboard navigation, and alternative text for images. The goal of accessibility is to make sure that everyone, regardless of their abilities, can access and use the system or application. This requirement is important for compliance with accessibility laws and regulations, as well as for creating an inclusive and user-friendly experience for all users.
Source: TOGAF
Source reference: https://pubs.opengroup.org/architecture/togaf9-doc/arch/chap03.html
Additional information: According to the TOGAF specification, Accessibility is a non-functional requirement that refers to the ability of a system or application to be used by people with disabilities. This includes individuals with visual, auditory, physical, or cognitive impairments.
Accessibility is an important consideration for any system or application, as it ensures that all users can access and use the system or application effectively. This requirement is particularly important for systems or applications that are used by the public, as they must comply with accessibility standards and guidelines set by regulatory bodies.
To meet the Accessibility non-functional requirement, the system or application must be designed and developed with accessibility in mind. This includes providing alternative ways of accessing information, such as text-to-speech or screen readers for visually impaired users, and ensuring that the system or application is navigable using only a keyboard for users with physical impairments.
The system or application must also comply with accessibility standards and guidelines, such as the Web Content Accessibility Guidelines (WCAG) and the Americans with Disabilities Act (ADA). Compliance with these standards and guidelines ensures that the system or application is accessible to all users, regardless of their abilities.
In summary, the Accessibility non-functional requirement requires that the system or application be designed and developed with accessibility in mind, and comply with accessibility standards and guidelines to ensure that all users can access and use the system or application effectively.
Example: One example of an IT non-functional requirement for accessibility could be that the website or application must be designed to be compatible with screen readers and other assistive technologies commonly used by people with disabilities. This could include ensuring that all images have alt text descriptions, using clear and concise language, and providing keyboard shortcuts for navigation. Additionally, the website or application should be designed with a high contrast color scheme and large, easy-to-read fonts to accommodate users with visual impairments.
LOST view: Digital Solution Non-Functional Requirements Catalogue view
Identifier: http://data.europa.eu/dr8/egovera/AccessibilityRequirement
EIRA traceability: eira:DigitalSolutionNonFunctionalRequirementRequirement
ABB name: egovera:AccessibilityRequirement
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-05-16
dct:identifier: http://data.europa.eu/dr8/egovera/AccessibilityRequirement
dct:title: Accessibility Non-Functional Requirement
Definition: Learnability is an important non-functional requirement in IT that refers to the capability to learn and understand how to use a system or application. It is a measure of how quickly and efficiently users can become proficient in using the system, without requiring extensive training or support. Learnability is essential for ensuring user satisfaction and productivity, as well as reducing the risk of errors and mistakes. A system with good learnability should have clear and intuitive interfaces, consistent design patterns, and well-organized documentation and help resources.
Source: TOGAF
Source reference: https://pubs.opengroup.org/architecture/togaf9-doc/arch/chap03.html
Additional information: According to the TOGAF specification, Learnability is a non-functional requirement that refers to the ease with which users can learn to use a system or application. This requirement is essential for ensuring that users can quickly and easily understand how to use the system, reducing the need for extensive training and support.
The Learnability requirement is typically addressed during the design and development phases of a project, with a focus on creating user-friendly interfaces, clear and concise documentation, and intuitive navigation. This requirement is closely related to other non-functional requirements, such as Usability, Accessibility, and User Experience (UX), which all contribute to the overall ease of use and satisfaction of the system.
To ensure that the Learnability requirement is met, the TOGAF documentation recommends conducting user testing and feedback sessions throughout the development process. This allows developers to gather feedback from users and make adjustments to the system as needed to improve its ease of use and learnability.
Overall, the Learnability requirement is critical for ensuring that users can quickly and easily learn to use a system or application, reducing the need for extensive training and support and improving overall user satisfaction.
Example: One example of the IT non-functional requirement 'Learnability' could be for a new software application to have a user-friendly interface that is easy to navigate and understand, allowing users to quickly learn how to use the application without requiring extensive training or support. This could include clear and concise instructions, intuitive design elements, and helpful tooltips or pop-ups to guide users through the application's features and functionality. The goal of this requirement would be to minimize the learning curve for users and increase overall adoption and satisfaction with the software.
LOST view: Digital Solution Non-Functional Requirements Catalogue view
Identifier: http://data.europa.eu/dr8/egovera/LearnabilityRequirement
EIRA traceability: eira:DigitalSolutionNonFunctionalRequirementRequirement
ABB name: egovera:LearnabilityRequirement
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-05-16
dct:identifier: http://data.europa.eu/dr8/egovera/LearnabilityRequirement
dct:title: Learnability Non-Functional Requirement
Description: The Digital Services Act is a regulation passed by the European Parliament and Council that aims to create a single market for digital services in the European Union. The act amends Directive 2000/31/EC and introduces new rules for online platforms, including requirements for transparency, accountability, and content moderation. It also establishes a new regulatory framework for digital services, including provisions for data protection, cybersecurity, and consumer protection. The act is designed to promote innovation and competition in the digital economy while ensuring that online platforms operate in a responsible and accountable manner.
Publisher: EUR-Lex
Source: https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:52022PC0068
Last modification: 26/06/2023
EIRA traceability: eira:BindingInstrumentRequirement
LOST view: Legal view - Binding Power and Jurisdiction
EIRA concept: eira:SolutionBuildingBlock
Additional identifier: https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:52022PC0068
Title: Proposal for a REGULATION OF THE EUROPEAN PARLIAMENT AND OF THE COUNCIL on harmonised rules on fair access to and use of data (Data Act)
Definition: Tiered levels of support is an IT non-functional requirement that refers to the different levels of technical support that are available to users of a system or application. This requirement specifies that the support should be provided in a hierarchical manner, with higher levels of support being available to users who require more advanced technical assistance. The purpose of this requirement is to ensure that users can receive the appropriate level of support based on their needs, and that technical issues can be resolved quickly and efficiently. This can help to minimize downtime and ensure that users are able to use the system or application effectively.
Source: TOGAF
Source reference: https://pubs.opengroup.org/architecture/togaf9-doc/arch/chap03.html
Additional information: According to the TOGAF specification, guidelines, and documentation, the non-functional requirement 'Tiered levels of support' refers to the need for a system or application to provide different levels of support based on the severity of the issue or problem. This requirement is typically associated with the availability and reliability of the system, as well as the ability to quickly resolve issues and minimize downtime.
The tiered levels of support typically include three or more levels, with each level providing a different level of support and response time. The first level of support is typically a help desk or support team that provides basic troubleshooting and triage. The second level of support is typically a more specialized team that can provide more in-depth technical support and problem resolution. The third level of support is typically a team of experts who can provide advanced technical support and problem resolution.
The tiered levels of support should be clearly defined and documented, with specific service level agreements (SLAs) for each level. The SLAs should include response times, resolution times, and escalation procedures. The system or application should also provide clear communication channels for users to report issues and receive updates on the status of their support requests.
Overall, the 'Tiered levels of support' non-functional requirement is critical for ensuring the availability and reliability of a system or application, as well as providing users with timely and effective support when issues arise.
Example: One example of the IT non-functional requirement 'Tiered levels of support' could be for a software application used by a large corporation. The requirement would specify that there must be multiple levels of support available to users, depending on the severity of the issue they are experiencing. For example, a user with a critical issue that is preventing them from completing their work would have access to a higher level of support than a user with a minor issue that can wait. This would ensure that the most urgent issues are addressed quickly and efficiently, while less urgent issues are still resolved in a timely manner.
LOST view: Digital Solution Non-Functional Requirements Catalogue view
Identifier: http://data.europa.eu/dr8/egovera/TieredLevelsOfSupportRequirement
EIRA traceability: eira:DigitalSolutionNonFunctionalRequirementRequirement
ABB name: egovera:TieredLevelsOfSupportRequirement
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-05-16
dct:identifier: http://data.europa.eu/dr8/egovera/TieredlevelsofsupportRequirement
dct:title: Tiered levels of support Non-Functional Requirement
Description: Directive (EU) 2015/2366, also known as the Payment Services Directive (PSD), is a European Union directive that was adopted in 2015 to regulate payment services within the internal market of the EU. It aims to create a single market for payment services by harmonizing rules and regulations across member states. The directive provides a legal framework for payment service providers, including banks and other financial institutions, and sets out rules for payment transactions, consumer rights, and the security of electronic payments. The PSD is an evolution of the initial Directive 2007/64/EC to adapt to technological advancements and changes in the payment industry.
Publisher: EUR-Lex
Source: http://data.europa.eu/eli/dir/2015/2366/2015-12-23
Last modification: 26/06/2023
EIRA traceability: eira:BindingInstrumentRequirement
LOST view: Legal view - Binding Power and Jurisdiction
EIRA concept: eira:SolutionBuildingBlock
Additional identifier: http://data.europa.eu/eli/dir/2015/2366/2015-12-23
Title: Directive (EU) 2015/2366 of the European Parliament and of the Council of 25 November 2015 on payment services in the internal market, amending Directives 2002/65/EC, 2009/110/EC and 2013/36/EU and Regulation (EU) No 1093/2010, and repealing Directive 2007/64/EC
Definition: Fault tolerance is an IT non-functional requirement that refers to the ability of a system to continue functioning even in the event of hardware or software failures. This means that the system should be able to detect and recover from errors or failures without causing any disruption to the user experience. Fault tolerance is important for critical systems that cannot afford to fail, such as those used in healthcare, finance, and transportation. It involves redundancy, backup systems, and failover mechanisms to ensure that the system remains operational even in the face of unexpected events.
Source: TOGAF
Source reference: https://pubs.opengroup.org/architecture/togaf9-doc/arch/chap03.html
Additional information: According to the TOGAF specification, fault tolerance is a non-functional requirement that refers to the ability of a system to continue operating in the event of a failure or error. This means that the system should be able to detect and recover from faults or errors without causing any disruption to the overall performance or availability of the system.
To achieve fault tolerance, the system should be designed with redundancy and failover mechanisms that can automatically switch to backup components or systems in the event of a failure. This can include redundant hardware components, such as servers, storage devices, and network connections, as well as software components, such as load balancers, clustering, and replication.
In addition, the system should be able to detect faults and errors in real-time, using monitoring and alerting mechanisms that can notify system administrators or operators of any issues. This can include automated monitoring tools that can detect performance issues, security breaches, or other types of errors that can impact the system's availability or performance.
Overall, fault tolerance is a critical non-functional requirement for any system that requires high availability and reliability, such as mission-critical applications, financial systems, or healthcare systems. By designing systems with fault tolerance in mind, organizations can ensure that their systems can continue operating even in the face of unexpected failures or errors, minimizing downtime and ensuring business continuity.
Example: One example of the IT non-functional requirement 'Fault tolerance' is in the aviation industry. The flight control systems of an aircraft must be designed to be fault-tolerant, meaning that they can continue to operate even if one or more components fail. This is critical for ensuring the safety of passengers and crew in the event of a system failure. The system must be able to detect and isolate faults, and then continue to operate using redundant components or backup systems.
LOST view: Digital Solution Non-Functional Requirements Catalogue view
Identifier: http://data.europa.eu/dr8/egovera/FaultToleranceRequirement
EIRA traceability: eira:DigitalSolutionNonFunctionalRequirementRequirement
ABB name: egovera:FaultToleranceRequirement
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-05-16
dct:identifier: http://data.europa.eu/dr8/egovera/FaulttoleranceRequirement
dct:title: Fault tolerance Non-Functional Requirement
Definition: Latency is a non-functional requirement that refers to the time delay between the initiation of a request and the response received. It is a critical factor in determining the overall performance of a system, particularly in real-time applications such as online gaming, video conferencing, and financial trading. Low latency is desirable as it ensures that the system responds quickly to user requests, providing a seamless and efficient user experience. High latency, on the other hand, can lead to frustration and decreased productivity, making it essential to ensure that latency is kept to a minimum in any IT system.
Source: TOGAF
Source reference: https://pubs.opengroup.org/architecture/togaf9-doc/arch/chap03.html
Additional information: According to the TOGAF specification, Latency is a non-functional requirement that refers to the time delay between the initiation of a request and the response received. It is a measure of the time taken for data to travel from one point to another, and is typically measured in milliseconds (ms).
Latency is an important consideration for IT systems that require real-time or near-real-time responses, such as financial trading systems, online gaming platforms, and video conferencing applications. High latency can result in delays, lag, and poor user experience, which can negatively impact the performance and usability of the system.
To ensure that latency requirements are met, IT architects must consider a range of factors, including network bandwidth, server processing power, and data storage capacity. They must also design systems that are optimized for low latency, using techniques such as caching, load balancing, and content delivery networks (CDNs).
In addition, IT architects must work closely with stakeholders to define latency requirements and establish appropriate performance metrics. This may involve conducting performance testing and benchmarking to identify areas for improvement and ensure that the system meets the required latency targets.
Overall, latency is a critical non-functional requirement that must be carefully considered and managed throughout the IT system development lifecycle to ensure optimal performance and user experience.
Example: An example of the IT non-functional requirement 'Latency' could be for a video conferencing application to have a maximum latency of 100 milliseconds to ensure smooth and real-time communication between participants.
LOST view: Digital Solution Non-Functional Requirements Catalogue view
Identifier: http://data.europa.eu/dr8/egovera/LatencyRequirement
EIRA traceability: eira:DigitalSolutionNonFunctionalRequirementRequirement
ABB name: egovera:LatencyRequirement
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-05-16
dct:identifier: http://data.europa.eu/dr8/egovera/LatencyRequirement
dct:title: Latency Non-Functional Requirement
Definition: Availability is a non-functional requirement that refers to the ability of a system or application to be accessible and operational at all times. It is a measure of the system's reliability and the ability to provide uninterrupted service to users. This requirement is critical for systems that are used in mission-critical environments, such as healthcare, finance, and transportation. High availability is achieved through redundancy, fault tolerance, and disaster recovery mechanisms that ensure that the system can continue to function even in the event of hardware or software failures.
Source: TOGAF
Source reference: https://pubs.opengroup.org/architecture/togaf9-doc/arch/chap03.html
Additional information: According to the TOGAF specification, Availability is a non-functional requirement that refers to the ability of a system or application to be accessible and usable by authorized users at all times. This requirement is critical for ensuring that the system or application is always available for use, regardless of any potential disruptions or failures.
To meet the Availability requirement, the system or application must be designed and implemented with a high degree of resilience, fault tolerance, and redundancy. This may involve the use of redundant hardware, software, and network components, as well as the implementation of backup and recovery procedures to ensure that data is not lost in the event of a failure.
Additionally, the system or application must be designed to handle high levels of traffic and usage, without experiencing performance degradation or downtime. This may involve the use of load balancing and other performance optimization techniques to ensure that the system can handle peak loads without impacting availability.
Overall, the Availability requirement is critical for ensuring that the system or application is always accessible and usable by authorized users, and must be carefully considered and addressed during the design and implementation phases of the project.
Example: One example of an IT non-functional requirement for availability could be for a banking system to have a 99.99% uptime, meaning that the system should be available for use by customers 99.99% of the time. This requirement ensures that customers can access their accounts and perform transactions at any time without experiencing downtime or system failures.
LOST view: Digital Solution Non-Functional Requirements Catalogue view
Identifier: http://data.europa.eu/dr8/egovera/AvailabilityRequirement
EIRA traceability: eira:DigitalSolutionNonFunctionalRequirementRequirement
ABB name: egovera:AvailabilityRequirement
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-05-16
dct:identifier: http://data.europa.eu/dr8/egovera/AvailabilityRequirement
dct:title: Availability Non-Functional Requirement
Description: Directive 2014/55/EU, also known as the Directive on electronic invoicing in public procurement, is a legislation enacted by the European Parliament and Council on 16 April 2014. The directive aims to establish a common framework for the use of electronic invoicing in public procurement across the European Union. It sets out the requirements for the format, content, and transmission of electronic invoices, with the goal of promoting efficiency, cost savings, and interoperability in public procurement processes. The directive also encourages the use of electronic invoicing by public authorities and promotes the adoption of standardized electronic invoicing solutions.
Publisher: EUR-Lex
Source: https://eur-lex.europa.eu/eli/dir/2014/55/oj
Last modification: 26/06/2023
EIRA traceability: eira:BindingInstrumentRequirement
LOST view: Legal view - Binding Power and Jurisdiction
EIRA concept: eira:SolutionBuildingBlock
Additional identifier: https://eur-lex.europa.eu/eli/dir/2014/55/oj
Title: Directive 2014/55/EU of the European Parliament and of the Council of 16 April 2014 on electronic invoicing in public procurement
Description: Directive (EU) 2016/97, also known as the Insurance Distribution Directive (IDD), is a European Union directive that aims to harmonize the rules and regulations governing the distribution of insurance products across member states. The directive sets out requirements for insurance distributors, including insurance intermediaries and insurance undertakings, in terms of their professional knowledge, conduct, and transparency towards customers. It also introduces new rules on product oversight and governance, disclosure of information, and the handling of complaints. The IDD seeks to enhance consumer protection, promote fair competition, and ensure a level playing field for insurance distributors operating within the EU.
Publisher: EUR-Lex
Source: http://data.europa.eu/eli/dir/2016/97/2020-06-12
Last modification: 26/06/2023
EIRA traceability: eira:BindingInstrumentRequirement
LOST view: Legal view - Binding Power and Jurisdiction
EIRA concept: eira:SolutionBuildingBlock
Additional identifier: http://data.europa.eu/eli/dir/2016/97/2020-06-12
Title: Directive (EU) 2016/97 of the European Parliament and of the Council of 20 January 2016 on insurance distribution (recast)
Definition: This ABB is a Business Agnostic National Legal Act which lays down rules regulating the use and access to national base registries for the reuse of data.
LOST view: LV-Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/NationalSchemaOnTheAccessToBaseRegistriesRequirement
ABB name: egovera:NationalSchemaOnTheAccessToBaseRegistriesRequirement
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-11-20
Name: National Schema on the access to Base Registries
Identifier: egovera:NationalSchemaOnTheAccessToBaseRegistriesRequirement
Interoperability Layer: Legal
Specialises: http://data.europa.eu/dr8/BindingInstrumentRequirement
Description: This regulation refers to the national laws enacted by individual member states of the European Union to implement and enforce the EU's customs cooperation regulations. These laws are designed to ensure the smooth operation of the EU's customs union, which involves the free movement of goods between member states and a common external tariff for goods entering the union. They cover areas such as customs procedures, duties and tariffs, and cooperation between national customs authorities.
Publisher: Individual Member States of the European Union
Source: https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=LEGISSUM%3Al11010
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/egovera/NationalLegalActOnCustomCooperationBetweenDifferentMemberStatesRequirement
EIRA traceability: eira:BindingInstrumentRequirement
LOST view: LV-Architecture Principles
EIRA concept: eira:ArchitectureBuildingBlock
Administration level: National
Additional identifier: http://data.europa.eu/dr8/egovera/NationalLegalActOnCustomCooperationBetweenDifferentMemberStatesRequirement
Title: National legal act on custom cooperation between different member states
Example: For instance, the UK's Customs (Cooperation with the European Union) Regulations 2020 were enacted to implement EU customs cooperation regulations in the UK. They provide for the sharing of information between UK and EU customs authorities, mutual assistance in customs matters, and the enforcement of EU customs regulations in the UK.
Additional information: The regulation is crucial for the functioning of the EU's single market and customs union. It ensures that customs duties are applied uniformly across the union, prevents smuggling and fraud, and facilitates trade between member states. Each member state is responsible for implementing and enforcing these regulations within its own territory.
ABB name: egovera:NationalLegalActOnCustomCooperationBetweenDifferentMemberStatesRequirement
eira:eifLayer: Legal
Definition: Binding Instrument ABB is a Business Object involving an obligation, which is available to the European institutions to carry out their tasks.
Source: Eur-Lex
Source reference: http://eur-lex.europa.eu/summary/glossary/community_legal_instruments.html
Additional information: Additional Information: The European binding instruments listed in Article 288 of the Treaty on the Functioning of the European Union are: The European binding instruments listed in Article 288 of the Treaty on the Functioning of the European Union are: - regulations: these are binding in their entirety and directly applicable in all EU countries; - directives: these bind the EU countries as to the results to be achieved; they have to be transposed into the national legal framework and thus leave margin for manoeuvre as to the form and means of implementation; - decisions: these are fully binding on those to whom they are addressed; - recommendations and opinions: these are non-binding, declaratory instruments.
Example: The following implementation is an example of how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): Directive (EU) 2019/790 of the European Parliament and of the Council of 17 April 2019 on copyright and related rights in the Digital Single Market and amending Directives 96/9/EC and 2001/29/EC (Text with EEA relevance.). http://data.europa.eu/eli/dir/2019/790/oj
Interoperability Dimension: Structural IoP
LOST view: Legal view
Interoperability Saliency: The Binding Instrument ABB is relevant for legal and governance interoperability as, by being a specialisation of the Legal Act, it makes mandatory the implementation of the policy (and therefore the underlying interoperability implications).
Identifier: http://data.europa.eu/dr8/BindingInstrumentRequirement
ABB name: eira:BindingInstrumentRequirement
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/BindingInstrumentRequirement
Interoperability Layer: Legal
Definition: Organization ABB is a Stakeholder that corresponds to a collection of people organized together into a community or other social, commercial or political structure. The group has some common purpose or reason for existence which goes beyond the set of people belonging to it and can act as an Agent. Organizations are often decomposable into hierarchical structures.
Source: SEMIC-CPOV
Source reference: https://semiceu.github.io/CPOV/releases/2.1.0/#Organization
Example: The following implementation is an example of how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): Any instance of an organisation with a legal personality, e.g. a Business, a Public Organisation, a Consortium, an NGO, etc.
Interoperability Dimension: Structural IoP
LOST view: Organisational view
Viewpoint: Interoperability Privacy viewpoint
Interoperability Saliency: The Organization ABB is relevant for behavioural and organizational interoperability because it permits the identification of procedures, stakeholders and intra-company frameworks that facilitate the exchange of data, information and knowledge between digital public services.
Identifier: http://data.europa.eu/dr8/OrganisationStakeholder
ABB name: eira:OrganisationStakeholder
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/OrganisationStakeholder
Interoperability Layer: Organisational
Definition: Individual ABB is a Stakeholder that is a human being who may be dead or alive, but not imaginary.
Source: SEMIC-CPV
Source reference: https://semiceu.github.io/Core-Person-Vocabulary/releases/2.00/#Person
Synonym: Person
Example: The following implementation is an example of how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): Any instance of a person, for instance, Ursula von der Leyen, President of the European Commission. https://ec.europa.eu/commission/commissioners/2019-2024/president_en
Interoperability Dimension: Structural IoP
LOST view: Organisational view
Viewpoint: Interoperability Privacy viewpoint
Interoperability Saliency: The Individual ABB is salient for organizational and behavioural interoperability because it permits the identification of procedures and business rules related to this stakeholder that facilitates the exchange of data, information and knowledge between digital public services and individuals (and vice versa).
Identifier: http://data.europa.eu/dr8/IndividualStakeholder
ABB name: eira:IndividualStakeholder
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/IndividualStakeholder
Interoperability Layer: Organisational
Definition: Public Administration ABB is a Stakeholder that corresponds to an Organization that is defined as being part of the public sector by a legal framework at any level. In this scope, there are in charge of implementing public policy
Source: SEMIC-CPOV
Source reference: https://semiceu.github.io/CPOV/releases/2.1.0/#Public%20Organisation
Additional information: The provision of digital public services are Public Administration's means of implementing e-Government. Certain countries make the difference between e-Government (policy implementation management) and e-Administration (administrative procedure management using electronic means). For these countries, the case of the SDG would fall under the e-Administration umbrella.
Example: The following implementation is an example of how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): The European Commission; the central, regional or local executive arm of a MS.
Interoperability Dimension: Structural IoP
LOST view: Organisational view
Viewpoint: Interoperability Privacy viewpoint
Interoperability Saliency: The Public Administration ABB is salient for behavioural and organizational interoperability because it represents the specific authority in charge of supporting the definition of procedures and business rules to publish digital business capabilities. It also allows the security assurance and control configuration associated with this authority or public entity, the discovery of data types that it can provide, as well as other aspects necessary to assure, monitor and control the exchange of data between this public entity and the digital public services providing to or consuming data from this stakeholder.
Identifier: http://data.europa.eu/dr8/PublicAdministrationStakeholder
ABB name: eira:PublicAdministrationStakeholder
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/PublicAdministrationStakeholder
Interoperability Layer: Organisational
Definition: Legal Entity ABB is a Stakeholder that is a self-empoyed person, company, or organization that has legal rights and obligations.
Source: SEMIC-CBV
Source reference: https://semiceu.github.io/Core-Business-Vocabulary/releases/2.00/#Legal%20Entity
Example: The following implementation is an example of how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): Any instance of Business, Public Administration with legal personality or a Natural person. https://commission.europa.eu/publications/legal-entities_en
Interoperability Dimension: Structural IoP
LOST view: Organisational view
Interoperability Saliency: The Legal Entity ABB is salient for organizational and behavioural interoperability because it permits the identification of procedures and business rules related to this stakeholder that facilitates the exchange of data, information and knowledge between digital public services.
Identifier: http://data.europa.eu/dr8/LegalEntityStakeholder
ABB name: eira:LegalEntityStakeholder
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/LegalEntityStakeholder
Interoperability Layer: Organisational
Definition: Business ABB is a Stakeholder that correspond to an individual, group, or organization that has an interest or stake in the success or failure of a particular product or service. Indeed, they focus on making, buying or selling goods or even, providing services in pursuing a benefit.
Source: Inspired in definition provided by relevant consultancy services
Source reference: https://www.gartner.com/en/information-technology/glossary/business-process-as-a-service-bpaas
Example: The following implementation is an example of how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): The instance of an Economic Operator that is using a digital public service to submit a tender.
Interoperability Dimension: Structural IoP
LOST view: Organisational view
Viewpoint: Interoperability Privacy viewpoint
Interoperability Saliency: The Business ABB is salient for behavioural and organizational interoperability because it permits the identification of a specific stakeholder, which in turn allows the identification of its rights, permissions, and digital business capabilities. It also allows the security assurance and control configuration associated with this stakeholder, the discovery of data types that it can provide, as well as other aspects necessary to assure, monitor and control the exchange of data between this stakeholder and the digital public services providing to or consuming data from this stakeholder.
Identifier: http://data.europa.eu/dr8/BusinessStakeholder
ABB name: eira:BusinessStakeholder
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/BusinessStakeholder
Interoperability Layer: Organisational
Definition: The Analytical Capacity Value ABB refers to the ability of public administrations to gather, analyse, and utilize data and evidence in decision-making processes. It involves having the skills, tools, and institutional arrangements to collect, interpret, and apply data to inform policy development, program design, and performance monitoring.
Source: Public Administration Reform: A Comparative Analysis
eira:iopDimension: Governance IoP
LOST view: Enterprise Architecture Framework alignment guidelines view
Identifier: http://data.europa.eu/dr8/AnalyticalCapacityValue
ABB name: eira:AnalyticalCapacityValue
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-05-25
dct:identifier: http://data.europa.eu/dr8/AnalyticalCapacityValue
Definition: The Regulatory Capacity Value ABB relates to a government's ability to develop, implement, and enforce regulations and rules effectively. It involves having the necessary resources, expertise, and mechanisms in place to establish and enforce regulatory frameworks that protect public interests, promote compliance, and achieve desired outcomes.
Source: Public Administration Reform: A Comparative Analysis
eira:iopDimension: Governance IoP
LOST view: Enterprise Architecture Framework alignment guidelines view
Identifier: http://data.europa.eu/dr8/RegulatoryCapacityValue
ABB name: eira:RegulatoryCapacityValue
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-05-25
dct:identifier: http://data.europa.eu/dr8/RegulatoryCapacityValue
Definition: The Coordination Capacity Value ABB refers to mediating and bringing different administrative units and dispersed actors to work together to achieve joint actions. It is not only about vertical coordination by hierarchy but also about facilitating horizontal coordination across policy areas and organizations at the same administrative level.
Source: Administrative coordination capacity; does the wickedness of policy areas matter?
Source reference: https://www.duo.uio.no/bitstream/handle/10852/76072/10-108014494035-2019-1584147.pdf?sequence=4&isAllowed=y
eira:iopDimension: Governance IoP
LOST view: Enterprise Architecture Framework alignment guidelines view
Identifier: http://data.europa.eu/dr8/CoordinationCapacityValue
ABB name: eira:CoordinationCapacityValue
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-05-25
dct:identifier: http://data.europa.eu/dr8/CoordinationCapacityValue
Definition: The Delivery Capacity Value ABB refers to the ability of public administrations to deliver public services, programs, and policies effectively and efficiently to citizens and stakeholders. It encompasses the overall performance, effectiveness, and responsiveness of public administration in meeting the needs and expectations of the public.
Source: Public Administration Reform: A Comparative Analysis
eira:iopDimension: Governance IoP
LOST view: Enterprise Architecture Framework alignment guidelines view
Identifier: http://data.europa.eu/dr8/DeliveryCapacityValue
ABB name: eira:DeliveryCapacityValue
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-05-25
dct:identifier: http://data.europa.eu/dr8/DeliveryCapacityValue
Definition: Digitaliation Roadmap ABB is a Work Package that corresponds to a high-level vision and strategy referring to long-term business goal an organization wants to achieve, including digital initiatives and goals the organization will drive.
Source: Inspired in referent consultancy companies and IEEE
Source reference: https://roadmaps.ieee.org/guide-to-technology-roadmaps
Example: The following implementation is an example of how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): Digital roadmap for organising mobility authorities (OMAs). (https://cerre.eu/publications/mobility-as-a-service-maas-digital-roadmap-public-transport-authorities/)
IoP Dimension: Governance IoP
LOST view: Organisational view
Interoperability saliency: Digitalization Roadmap ABB is salient for the governance, semantic and technical interoperability because it commonly offers (i) a transversal vision of existing reusable standards applied in the digitalization of the public sector, (ii) actions to ensure data exchange between digital services; (iii) technological software and assets that should be included in the digitalization of public administrations.
Identifier: http://data.europa.eu/dr8/DigitalisationRoadmapWorkPackage
eira:ID: ABB490
ABB name: eira:DigitalisationRoadmapWorkPackage
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2022-12-01
Definition: Customs Legislation on Governance Interoperability (NBI) is a grouping that covers the national legal acts related to customs cooperation with private businesses and between different member states. It is a collection of elements that define the legal framework for customs operations and cooperation at a national level, aiming to enhance interoperability and efficiency in customs governance.
Source: EIRA Team Research
Additional information: The Customs Legislation on Governance Interoperability (NBI) is a catalogue of elements that includes national legal acts on customs cooperation with private businesses and between different member states. These elements provide the legal basis for customs operations and cooperation, aiming to ensure smooth and efficient customs processes. The first element pertains to the legal framework for cooperation between customs authorities and private businesses, while the second element refers to the legal framework for cooperation between customs authorities of different member states. These elements are crucial for ensuring interoperability in customs governance, which is key for facilitating international trade and ensuring compliance with customs regulations.
Example: An example of the application of the 'National legal act on custom cooperation with private businesses' could be a legislation that outlines the responsibilities and obligations of private businesses in customs processes, such as the declaration of goods for import or export. An example of the 'National legal act on custom cooperation between different member states' could be an agreement between two countries to share information and collaborate on customs enforcement to prevent smuggling and fraud.
LOST view: LV-Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/CustomsLegislationOnGovernanceInteroperabilityGrouping
ABB name: egovera:CustomsLegislationOnGovernanceInteroperabilityGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-20
dct:identifier: http://data.europa.eu/dr8/egovera/CustomsLegislationOnGovernanceInteroperabilityGrouping
dct:title: Customs Legislation On Governance Interoperability (NBI)
Definition: Customs Legislation on Behavioural Interoperability (NNBI) ABB is a grouping that covers the rules, regulations, and procedures that govern the interaction and exchange of information between different customs systems. It aims to ensure seamless communication and cooperation between these systems, regardless of their individual characteristics or the countries they belong to.
Source: EIRA Team Research
Additional information: The NNBI ABB is crucial in the context of international trade, as it facilitates the smooth flow of goods across borders by standardizing the way customs systems interact with each other. It covers a wide range of elements, including data exchange protocols, system compatibility requirements, and behavioural guidelines for system users. The goal is to create an environment where all customs systems can work together effectively, regardless of their individual characteristics or the countries they belong to. This not only simplifies the process of importing and exporting goods, but also helps to prevent issues such as smuggling and tax evasion.
Example: An example of the application of the NNBI ABB would be the implementation of a new data exchange protocol between the customs systems of two countries. This protocol would be designed in accordance with the principles of behavioural interoperability, ensuring that both systems can communicate effectively with each other. Another example would be the creation of a set of behavioural guidelines for users of a customs system, designed to ensure that their actions do not disrupt the interoperability of the system with others.
LOST view: LV-Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/CustomsLegislationOnBehaviouralInteroperabilityGrouping
ABB name: egovera:CustomsLegislationOnBehaviouralInteroperabilityGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-20
dct:identifier: http://data.europa.eu/dr8/egovera/CustomsLegislationOnBehaviouralInteroperabilityGrouping
dct:title: Customs Legislation On Behavioural Interoperability (NNBI)
Definition: Shared Knowledge Content ABB is a Grouping setting semantic (re)usable resources, with convergence power, in relation to public policy goals attainment, enabling common understanding from existing information across public administrations, and borders.
Source: Atlassian
Source reference: https://www.atlassian.com/itsm/knowledge-management/what-is-a-knowledge-base
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/SharedKnowledgeContentGrouping
LOST view: Semantic view
EIRA concept: eira:ArchitectureBuildingBlock
ABB name: eira:SharedKnowledgeContentGrouping
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): Eur-Lex (stylized EUR-Lex) is an official website of European Union law and other public documents of the European Union (EU), published in 24 official languages of the EU. The Official Journal (OJ) of the European Union is also published on Eur-Lex. Users can access Eur-Lex free of charge and also register for a free account, which offers extra features. https://eur-lex.europa.eu/homepage.html?locale=en
Interoperability Saliency: The Shared Knowledge Content ABB is a key interoperability enabler (*) for governance, behavioural and structural interoperability. This ABB is salient for semantic interoperability with public policy goals convergence value by enabling i) the provision/consumption of data by public services, ii) the exchange of data, information, and knowledge between digital public services, and iii) collaboration between digital public services
Additional information: This convergence power is based on the enabling sense-making nature of these resources influencing the enactment of common understanding from the existing organisational information. The degree of achievement could range from an ideal perfect shared knowledge base (i.e. no interoperability barriers from the semantic perspective) to an imperfect or even null shared knowledge base (i.e. some interoperability barriers from the semantic perspective). The level of semantic interoperability will constrain digital public services cross levels in a public administration, cross public administrations, and cross borders. The shared knowledge base enables: i) structural interoperability with semantic resources supporting reusing and/or sharing of digital public services (i.e. data set catalogue); ii) behavioural interoperability with semantic resources supporting exchanging capabilities of data, information or knowledge with internal/external peers (i.e. Metadata mappings); and iii) governance interoperability with semantic resources supporting the assurance and control of collaboration with internal/external peers exchanging data, information, and knowledge cross legal jurisdictions (i.e. Sematic Interoperability Agreements).
Interoperability Dimension: Structural IoP
Viewpoint: Highlevel viewpoint
Additional identifier: http://data.europa.eu/dr8/SharedKnowledgeContentGrouping
EIF Layer: Semantic
Definition: Customs Legislation on Behavioural Interoperability (EBI) is a grouping that covers a variety of regulations and legislations related to customs and trade within the European Union. These regulations govern various aspects of customs procedures, including tariff and statistical nomenclature, temporary storage of goods, import of cultural goods, enforcement of intellectual property rights, payment of import or export duty, customs status of goods, application for the status of AEO, simplification of customs procedures, declaration of particulars relating to customs value, and formalities to be carried out by the shipping company.
Source: EIRA Team Research
Additional information: The EBI catalogue includes a variety of regulations and legislations that govern customs procedures within the European Union. These regulations are designed to ensure the smooth operation of trade within the EU, and cover a wide range of topics, from the tariff and statistical nomenclature used in trade, to the enforcement of intellectual property rights, to the procedures for applying for the status of Authorized Economic Operator (AEO). Each regulation in the catalogue is accompanied by a detailed description, providing further information on its purpose and application.
Example: For instance, 'Regulation (EEC) No 2658/87 - the tariff and statistical nomenclature and the Common Customs Tariff' is a regulation that establishes the tariff and statistical nomenclature to be used in trade within the EU, as well as the Common Customs Tariff. Another example, 'Regulation (EU) No 952/2013 of the European Parliament and of the Council of 9 October 2013 laying down the Union Customs Code Articles 108 to 113', governs the payment of import or export duty within the EU.
LOST view: LV-Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/CustomsLegislationOnBehaviouralInteroperabilityGrouping
ABB name: egovera:CustomsLegislationOnBehaviouralInteroperabilityGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-20
dct:identifier: http://data.europa.eu/dr8/egovera/CustomsLegislationOnBehaviouralInteroperabilityGrouping
dct:title: Customs Legislation On Behavioural Interoperability (EBI)
Definition: Business Agnostic Data Space Participant Digital Public Service Catalog (ABB) is a grouping that covers a range of digital public services that are essential for the operation and management of data in a business-agnostic manner. These services include data extraction, transformation and loading, content management, open data management, workflow management, data exchange, eArchiving, anonymisation, and secure access control.
Source: EIRA Team Research
Additional information: The Business Agnostic Data Space Participant Digital Public Service Catalog ABB is a comprehensive catalog that encompasses various digital public services that are not specific to any business or industry. These services are crucial for the efficient handling and management of data. 'Data Extraction, Transformation and Loading' refers to the process of extracting data from different sources, transforming it into a usable format, and loading it into a database. 'Content Management' involves the creation, management, and modification of digital content. 'Open Data Management' is about managing data that is freely available to everyone to use and republish. 'Workflow Management' is the coordination of tasks that make up a work process. 'Data Exchange' is the process of transferring data from one system to another. 'eArchiving' is the storage of digital data for long-term preservation. 'Anonymisation' is the process of removing personally identifiable information from data sets. 'Secure Access Control' is about managing access to resources in a computing environment.
Example: Examples of application include a government agency using the 'Open Data Management' service to manage and share public data, a healthcare organization using 'Anonymisation' service to protect patient data, or a corporation using 'Workflow Management' to streamline its business processes.
LOST view: OV-Data Spaces
Identifier: http://data.europa.eu/dr8/egovera/BusinessAgnosticDataSpaceParticipantDigitalPublicServiceCatalogGrouping
ABB name: egovera:BusinessAgnosticDataSpaceParticipantDigitalPublicServiceCatalogGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-17
dct:identifier: http://data.europa.eu/dr8/egovera/BusinessAgnosticDataSpaceParticipantDigitalPublicServiceCatalogGrouping
dct:title: Business Agnostic Data Space Participant Digital Public Service Catalog Catalogue
Definition: Shared Application Content ABB is a Grouping setting application (re)usable resources, with convergence power, for the enhancement of interoperability across digital platforms. It enables the sharing and integration of software tools and services, fostering collaborative functionality within and across applications to support the attainment of public policy goals.
Source: Inspired in referent cloud service providers definitions
Last modification: 2024-01-08
Identifier: http://data.europa.eu/dr8/SharedApplicationContentGrouping
LOST view: Technical view - application
EIRA concept: eira:ArchitectureBuildingBlock
ABB name: eira:SharedApplicationContentGrouping
Interoperability Saliency: The Shared Application Content ABB is a key interoperability enabler (*) for governance, behavioural and structural interoperability because it aggregates components to enable knowledge sharing across public administration to achieve their public policy goals.
Interoperability Dimension: Governance IoP
Viewpoint: Highlevel viewpoint
Additional identifier: http://data.europa.eu/dr8/SharedApplicationContentGrouping
EIF Layer: TechnicalApplication
Definition: Business Agnostic Data Models Solutions ABB is a grouping that covers a set of data models that are universally applicable across various business domains. This catalogue includes the Common Data Model (CDM) and the eProcurement Data Model, both of which are designed to standardize and streamline data management processes in their respective fields.
Source: EIRA Team Research
Additional information: The Common Data Model (CDM) is an ontology based on the FRBR model (Functional Requirements for Bibliographic Records) and uses RDF(S)/OWL technologies. It is capable of representing relationships between the resource types managed by the Publications Office and their views, all within the scope of the FRBR model. On the other hand, the eProcurement Data Model covers essential elements related to public procurement processes within the European Union, including the European Single Procurement Document (ESPD) as a key component. The ESPD is a standardized form used in these processes, representing a structured document that contains essential information about a supplier or contractor.
Example: For instance, the Common Data Model can be used by a publishing company to manage and organize its various resources, such as books, articles, and authors, in a structured and standardized manner. The eProcurement Data Model, particularly the ESPD component, can be utilized by government agencies to streamline their public procurement processes, ensuring that all suppliers or contractors meet the necessary eligibility and suitability criteria.
LOST view: SV-Business Agnostic Data Models
Identifier: http://data.europa.eu/dr8/egovera/BusinessAgnosticDataModelsSolutionsGrouping
ABB name: egovera:BusinessAgnosticDataModelsSolutionsGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/egovera/BusinessAgnosticDataModelsSolutionsGrouping
Name: Business Agnostic Data Models Solutions Catalogue
Interoperability Layer: Semantic
Definition: Extensibility Requirements Catalogue ABB is a grouping that covers a set of non-functional requirements that pertain to the adaptability and scalability of a software system. It includes elements such as modularity and reusability, and pluggability, which are crucial for creating flexible, efficient, and effective software systems that can be easily maintained, updated, and integrated with other systems or components.
Source: EIRA Team Research
Additional information: The Extensibility Requirements Catalogue ABB is a comprehensive collection of non-functional requirements that are essential for the development of scalable and adaptable software systems. The catalogue includes 'Modularity and reusability', which refers to the ability of a software system to be broken down into smaller, independent components that can be reused in other parts of the system or in other systems. This requirement is crucial for reducing development time and effort, and for creating more efficient systems. The catalogue also includes 'Pluggability', which refers to the ability of a system to easily integrate with other systems or components without requiring significant code modifications. This requirement is vital for systems that need to be scalable and adaptable to changing business requirements.
Example: An example of the application of the Extensibility Requirements Catalogue ABB could be in the development of a large-scale enterprise software system. The system could be designed with modularity and reusability in mind, allowing for the easy reuse of components across different parts of the system. Additionally, the system could be designed to be pluggable, enabling easy integration with third-party tools and technologies, and allowing for easy customization and extension of the system's functionality as business requirements change over time.
LOST view: Digital Solution Non-Functional Requirements Catalogue view
Identifier: http://data.europa.eu/dr8/egovera/ExtensibilityRequirementsCatalogueGrouping
ABB name: egovera:ExtensibilityRequirementsCatalogueGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-17
dct:identifier: http://data.europa.eu/dr8/egovera/ExtensibilityRequirementsCatalogueGrouping
dct:title: Extensibility Requirements Catalogue Catalogue
Definition: Legislation on Governance Interoperability (NBI) is a grouping that covers a broad range of legal and regulatory frameworks, policies, and guidelines that aim to facilitate the interaction between different governance systems. It encompasses all the elements that ensure seamless and efficient communication, data exchange, and cooperation between various governance entities, while adhering to the principles of transparency, accountability, and public participation.
Source: EIRA Team Research
Additional information: The Legislation on Governance Interoperability (NBI) catalogue is a comprehensive collection of legal and regulatory instruments that are designed to promote interoperability in governance. It includes laws, regulations, policies, and guidelines that define the standards, protocols, and procedures for data exchange, communication, and cooperation between different governance systems. The catalogue is intended to serve as a reference for policymakers, regulators, and governance professionals, providing them with a clear understanding of the legal and regulatory landscape for governance interoperability. It is also designed to facilitate the development and implementation of interoperable governance systems, promoting efficiency, transparency, and public participation.
Example: Examples of application for the Legislation on Governance Interoperability (NBI) can include the creation of a unified data exchange protocol for different government agencies, the development of a common communication platform for public participation in policy-making, or the establishment of a regulatory framework for cross-border cooperation between different governance systems.
LOST view: LV-Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/LegislationOnGovernanceInteroperabilityGrouping
ABB name: egovera:LegislationOnGovernanceInteroperabilityGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-20
dct:identifier: http://data.europa.eu/dr8/egovera/LegislationOnGovernanceInteroperabilityGrouping
dct:title: Legislation On Governance Interoperability (NBI) Catalogue
Definition: Networking Infrastructure Enablers ABB is a Grouping of components and services that facilitate the creation and operation of computer networks. These enablers can include both hardware and software technologies and are essential for building and maintaining modern networks
Source: ISA2 - EIA Action
Source reference: https://ec.europa.eu/isa2/actions/towards-european-interoperability-architecture_en/
Synonym:
Additional information:
Example: The following implementation is an example of how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): ECC Report 301. https://docdb.cept.org/download/1395
Interoperability Dimension: Structural IoP
LOST view: Technical view - infrastructure
Interoperability Saliency: The Networking Infrastructure Enablers ABB is salient for the organizational and technical interoperability due to it provides (i) the set up of rules for establishing the correct communication in the public administration considering both public and private, (ii) establish the physical elements to balance the traffic and ensure the correct behaviour of the communication considering the system performance.
Identifier: http://data.europa.eu/dr8/NetworkingInfrastructureEnablersGrouping
ABB name: eira:NetworkingInfrastructureEnablersGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/NetworkingInfrastructureEnablersGrouping
Interoperability Layer: TechnicalInfrastructure
Definition: Jurisdiction ABB is a Grouping that refers to the limits or territory within which authority may be exercised.
Source: CPV
Source reference: https://semiceu.github.io/Core-Person-Vocabulary/releases/2.00/#Jurisdiction
Definition: Schedule Management Enablers ABB is a Grouping that enables the implementation of components and services to create, distribute and manage events at different scales inside a cloud platform.
Source: Inspired in Redhat
Source reference: https://www.redhat.com/en/topics/cloud-computing/what-is-cloud-management
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): Chronos is a replacement for cron. It is a distributed and fault-tolerant scheduler that runs on top of Apache Mesos that can be used for job orchestration. It supports custom Mesos executors as well as the default command executor. Thus by default, Chronos executes sh (on most systems bash) scripts. https://sourceforge.net/projects/chronos.mirror/
Interoperability Dimension: Structural IoP
LOST view: Technical view - application
Interoperability Saliency: The Schedule Management Enablers Grouping ABB is salient for technical interoperability because it comprises the different services and tools that allow to organise and manage events within a platform for the delivery of a digital public service. It enables interoperability by allowing the management of events through a single point of access (for users and administrations) and the reuse of such information to an overall relationship between public administration and stakeholders.
Identifier: http://data.europa.eu/dr8/ScheduleManagementEnablersGrouping
ABB name: eira:ScheduleManagementEnablersGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/ScheduleManagementEnablersGrouping
Interoperability Layer: TechnicalApplication
Definition: eProcurement Data Model Solutions ABB is a Grouping that covers the elements related to the data models used in electronic procurement (eProcurement) processes. These elements are designed to standardize and streamline the procurement processes, particularly in the public sector within the European Union (EU). The primary element in this grouping is the European Single Procurement Document (ESPD), a standardized form used in public procurement processes within the EU.
Source: EIRA Team Research
Additional information: The eProcurement Data Model Solutions ABB focuses on the ESPD-EDM element. The European Single Procurement Document (ESPD) is a structured document that contains essential information about a supplier or contractor, including company identification, financial standing, technical and professional abilities, and any legal grounds for exclusion. The ESPD serves as a preliminary self-declaration by suppliers, allowing them to demonstrate their eligibility and suitability to participate in public procurement procedures across EU member states. As a data model, it helps to standardize and streamline the procurement processes, making them more efficient and transparent.
Example: An example of the application of the eProcurement Data Model Solutions ABB is in public procurement processes within the EU. When a public sector organization is seeking to procure goods or services, suppliers or contractors can use the ESPD to provide essential information about their company and demonstrate their eligibility and suitability to participate in the procurement process. The standardized format of the ESPD makes it easier for the procuring organization to compare and evaluate the suppliers or contractors.
LOST view: SV-Data Model [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/EProcurementDataModelSolutionsGrouping
ABB name: egovera:EProcurementDataModelSolutionsGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-21
dct:identifier: http://data.europa.eu/dr8/egovera/EProcurementDataModelSolutionsGrouping
dct:title: EProcurement Data Model Solutions
Definition: Constraints, Assumptions and Decisions ABB is a Grouping that covers a broad range of information entities that are crucial in the planning, execution, and evaluation of any project or process. These elements help in understanding the limitations, preconditions, and choices made during the lifecycle of a project or process.
Source: EIRA Team Research
Additional information: The Constraints, Assumptions and Decisions ABB catalogue is a comprehensive collection of elements that are integral to any project or process. 'Constraints' refer to the limitations or restrictions that may affect the execution or outcome of a project. 'Assumptions' are the conditions or facts that are assumed to be true in the planning and execution of a project. 'Decisions' are the choices made during the project lifecycle, which can significantly influence the project's direction and outcome. These elements are crucial as they help in identifying potential risks, planning for contingencies, and making informed decisions. They also provide a framework for evaluating the project's success and learning for future projects.
Example: [object Object]
[object Object]
[object Object]
LOST view: OV-Data Spaces
Identifier: http://data.europa.eu/dr8/egovera/ConstraintsAssumptionsAndDecisionsGrouping
ABB name: egovera:ConstraintsAssumptionsAndDecisionsGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-17
dct:identifier: http://data.europa.eu/dr8/egovera/ConstraintsAssumptionsAndDecisionsGrouping
dct:title: Constraints, Assumptions And Decisions Catalogue
Definition: Business Agnostic Organisational Agreement Catalogue ABB is a grouping that refers to the actual catalogue of specifications, agreements and/or contracts that facilitates the establishment and implementation of national governance models. It serves as a repository of the necessary documents that guide the coordination and collaboration among various government agencies, departments, and stakeholders in developing and implementing common standards, policies, and guidelines for IT interoperability within the European Union.
Source: EIRA Team Research
Additional information: The Business Agnostic Organisational Agreement Catalogue ABB is a critical tool in promoting seamless interoperability, data security, and efficient digital services within a country. It contains the necessary specifications, agreements, and contracts that define the framework and processes for IT interoperability. This includes the roles and responsibilities of different stakeholders, the standards and policies to be followed, and the guidelines for data exchange and sharing. The catalogue is 'business agnostic', meaning it is applicable regardless of the specific business or industry involved. It aligns with the broader European IT interoperability framework, facilitating cross-border data exchange and cooperation.
Example: An example of the application of the Business Agnostic Organisational Agreement Catalogue ABB could be a country developing its National Governance Model for IT interoperability. The country would refer to the catalogue to understand the necessary specifications, agreements, and contracts to be established. This could include agreements on data sharing between government departments, contracts with IT service providers to ensure they adhere to the required standards, and specifications for the IT systems to be used. The catalogue would guide the country in ensuring its National Governance Model aligns with the broader European IT interoperability framework.
LOST view: OV-Governance Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/BusinessAgnosticOrganisationalAgreementCatalogueGrouping
ABB name: egovera:BusinessAgnosticOrganisationalAgreementCatalogueGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/egovera/BusinessAgnosticOrganisationalAgreementCatalogueGrouping
Name: Business Agnostic Organisational Agreement Catalogue Catalogue
Interoperability Layer: Organisational
Specialises: http://data.europa.eu/dr8/TechnicalAgreementContract
Definition: Customs Vocabularies ABB is a grouping that covers a collection of standardized terminologies and classification systems used in the customs and trade sector. It includes elements such as the Registered Organization Vocabulary, National Customs Specific Taxonomy, and the Combined Nomenclature. These vocabularies provide a consistent and interoperable representation of customs-related data, enabling seamless integration, exchange, and discovery of data across diverse applications and systems.
Source: EIRA Team Research
Additional information: The Customs Vocabularies ABB includes the Registered Organization Vocabulary, which provides a standardized set of terms for representing registered organizations. It also includes the National Customs Specific Taxonomy, a specialized classification framework developed by a specific country's customs authority for organizing customs-related data. The Combined Nomenclature is another element, a tool for classifying goods to meet the requirements of the Common Customs Tariff and the EU external trade statistics. These vocabularies are essential for achieving a consistent and interoperable representation of customs-related data, facilitating efficient customs operations, enhancing trade facilitation, and supporting accurate reporting and analysis.
Example: Registered Organisation Vocabulary
A global company uses the Registered Organization Vocabulary to standardize the representation of its various branches across the world, enabling seamless data integration and discovery across its diverse systems and applications.
National Customs Specific Taxonomy
A country's customs authority implements the National Customs Specific Taxonomy to categorize and organize customs-related data, enhancing the efficiency of its customs operations and facilitating trade.
Combined Nomenclature
An international trading company uses the Combined Nomenclature to classify goods for customs and trade purposes, ensuring compliance with the Common Customs Tariff and EU external trade statistics.
LOST view: SV-Customs Controlled Vocabularies [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/CustomsVocabulariesGrouping
ABB name: egovera:CustomsVocabulariesGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-20
dct:identifier: http://data.europa.eu/dr8/egovera/CustomsVocabulariesGrouping
dct:title: Customs Vocabularies
Definition: Storage Infrastructure Enablers ABB is a Grouping of a set of tools and digital services that facilitate the efficient and effective storage of data
Source: TECHNOPEDIA
Source reference: https://www.techopedia.com/definition/30476/storage-infrastructure
Example: The following implementation is an example of how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): GARTNER- Distributed File Systems and Objects Storage Reviews and Ratings. https://www.gartner.com/reviews/market/distributed-file-systems-and-object-storage
Interoperability Dimension: Structural IoP
LOST view: Technical view - infrastructure
Interoperability Saliency: Storage Infrastructure Enablers ABB is salient for technical interoperability because it establishes the mechanism to (i) ensure the correct management of the information across single or multiple infrastructures, and (ii) minimize the effects of data loss in case of unexpected behaviour of public services through data recovery strategies.
Identifier: http://data.europa.eu/dr8/StorageInfrastructureEnablersGrouping
ABB name: eira:StorageInfrastructureEnablersGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/StorageInfrastructureEnablersGrouping
Interoperability Layer: TechnicalInfrastructure
Definition: Software Architect Data Spaces Concerns ABB is a Grouping that covers the processes, roles, and relationships a software architect should follow to read, assess, and understand an eGovERA model for the purpose of understanding and developing a Data Spaces solution or architecture. It includes elements such as 'Technical view - application' and 'Semantic view'.
Source: EIRA Team Research
Additional information: The Software Architect Data Spaces Concerns ABB is a comprehensive catalogue of elements that a software architect needs to consider when working with an eGovERA model to develop a Data Spaces solution or architecture. It includes the 'Technical view - application', which refers to the technical aspects of the application, and the 'Semantic view', which refers to the meaning and interpretation of the data. These elements are crucial in understanding the model and developing an effective solution.
Example: For example, a software architect might need to understand the technical infrastructure of the application, such as the programming languages used, the database management systems in place, and the server architecture.
For instance, the software architect might need to understand the semantics of the data, such as the meaning of different data fields, the relationships between different data entities, and the rules and constraints that govern the data.
LOST view: [A] How to read the model
Identifier: http://data.europa.eu/dr8/egovera/SoftwareArchitectDataSpacesConcernsGrouping
ABB name: egovera:SoftwareArchitectDataSpacesConcernsGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-18
dct:identifier: http://data.europa.eu/dr8/egovera/SoftwareArchitectDataSpacesConcernsGrouping
dct:title: Software Architect Data Spaces Concerns Catalogue
Definition: Containerization Enablers ABB is a Grouping that refers to components and services that facilitate the packaging of applications into standardized units for development, shipment and deployment. This grouping includes two main elements: the Container and the Containers Orchestrator.
Source: EIRA Team Research
Source reference: N/A
Additional information: Containerization Enablers ABB is a crucial component in modern software development and deployment processes. It includes the '[Container]' and '[Containers Orchestrator]' elements. The '[Container]' is a lightweight and portable software package that includes everything needed to run an application, ensuring a consistent and isolated environment for applications to run across different computing environments. The '[Containers Orchestrator]' is a software tool or platform that automates the deployment, management, and scaling of containerized applications, providing a centralized control plane to efficiently manage and coordinate the deployment and operation of containers across a cluster of machines or nodes.
Example: An example of Containerization Enablers ABB in action is the use of Docker as a container platform to package an application and its dependencies into a single object, and Kubernetes as a container orchestrator to manage the deployment and scaling of the Docker containers across a cluster of servers in a cloud environment. This allows for efficient, reliable, and scalable deployment of applications.
LOST view: TVA-Containerization Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/ContainerizationEnablersGrouping
ABB name: egovera:ContainerizationEnablersGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-16
dct:identifier: http://data.europa.eu/dr8/egovera/ContainerizationEnablersGrouping
dct:title: Containerization EnablersGrouping
Definition: Data Space Enablers ABB is a Grouping that refers to components and services that support the creation and management of a dataspace.
Source: Inspired in IDSA
Source reference: https://internationaldataspaces.org/why/data-spaces/
Interoperability Dimension: Structural IoP
LOST view: Technical view - application
Interoperability Saliency: The Data Spaces Enablers Grouping ABB is salient for technical interoperability because it comprises the core elements, components, and services required to set up Data Spaces that are interoperable between them. Data Spaces can be part of the environment for the implementation and delivery of interoperable digital public services.
Identifier: http://data.europa.eu/dr8/DataspaceEnablersGrouping
ABB name: eira:DataspaceEnablersGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/DataspaceEnablersGrouping
Interoperability Layer: TechnicalApplication
Description: Bussiness Agnostic Identity Management Solutions (BAIMS) is a grouping that refers to actual solutions that facilitate the management of user identities across various business models and industries. These solutions are designed to be flexible and adaptable, allowing businesses of any type or size to effectively manage user access, authentication, and security.
Additional information: BAIMS are crucial in today's digital age where security and privacy are of utmost importance. They provide a comprehensive approach to managing the identities of users in an organization, regardless of the nature of the business. They are designed to handle tasks such as user authentication, authorization, roles and access management, password management, policy enforcement, and audit and reporting. These solutions are not tied to a specific business model or industry, making them versatile and adaptable. They can be integrated with various systems and platforms, providing a seamless user experience while ensuring security and compliance.
Example: Examples of application of BAIMS include: 1) In a healthcare setting, these solutions can be used to manage the identities of doctors, nurses, and patients, ensuring that only authorized individuals have access to sensitive patient data. 2) In a retail business, they can be used to manage the identities of customers and employees, facilitating secure transactions and protecting customer information. 3) In a financial institution, they can be used to manage the identities of account holders and employees, ensuring secure access to financial data and systems.
Publisher: EIRA Team Research
LOST view: TVA-Identification and Access Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/BusinessAgnosticIdentityManagementSolutionsGrouping
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/egovera/BusinessAgnosticIdentityManagementSolutionsGrouping
Name: Bussiness Agnostic Identity Management SolutionsGrouping
Interoperability Layer: TechnicalApplication
Realises: http://data.europa.eu/dr8/DigitalSolutionApplicationService
Definition: Customs Dataset Catalogue ABB is a Grouping that covers a wide range of metadata and indices related to customs operations and procedures. It includes elements such as EORI metadata, customs statistical metadata on goods imported and exported, applications and requests metadata, laboratory reports index, tariffs metadata, risk metadata, economic operators metadata, origins metadata, cargo metadata, declarations metadata, intra-EU purchases and sales metadata, goods taxonomy metadata, notifications metadata, procedures metadata, goods metadata, and laboratories testing metadata.
Source: EIRA Team Research
Additional information: The Customs Dataset Catalogue ABB is a comprehensive collection of metadata and indices that are crucial for customs operations and procedures. These elements cover a wide range of areas including but not limited to, information about economic operators (EORI metadata), statistical data on goods imported and exported, metadata related to customs applications and requests, indices of laboratory reports, metadata on customs tariffs and risks, information on the origins of goods, cargo details, customs declarations, intra-EU purchases and sales, taxonomy of goods, customs notifications and procedures, and metadata on goods and laboratory testing. This catalogue is a valuable resource for customs authorities, traders, and other stakeholders in the customs and trade sector.
Example: For instance, the 'EORI metadata' element can be used by customs authorities to verify the identity of economic operators. The 'Customs statistical metadata on goods imported' and 'Customs statistical metadata on goods exported' elements provide valuable data for trade analysis and policy-making. The 'Applications and Requests metadata' element can be used to track and manage customs applications and requests. The 'Laboratory reports index' and 'Laboratories testing metadata' elements provide information on laboratory tests conducted on goods for customs purposes.
LOST view: SV-Customs Datasets [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/CustomsDatasetCatalogueGrouping
ABB name: egovera:CustomsDatasetCatalogueGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-20
dct:identifier: http://data.europa.eu/dr8/egovera/CustomsDatasetCatalogueGrouping
dct:title: Customs Dataset Catalogue
Definition: Bussiness Agnostic Digital Workplace Enablers ABB is a Grouping that covers a range of software application services designed to enhance productivity, collaboration, and learning in a digital workplace. These services are business-agnostic, meaning they can be applied across various industries and business types. They include Training and Learning Management, Learning Platform System, Remote Collaboration and Communication, and Digital Collaboration.
Source: EIRA Team Research
Additional information: The Bussiness Agnostic Digital Workplace Enablers ABB includes four key elements. The 'Training and Learning Management' element is an application service that helps organizations efficiently plan, administer, deliver, and track training and learning activities. The 'Learning Platform System' is a software application service that provides a comprehensive platform for managing and delivering learning content and experiences. The 'Remote Collaboration and Communication' is a software application service that enables individuals or teams to collaborate and communicate effectively, regardless of their physical locations. Lastly, the 'Digital Collaboration' is a broad term that encompasses various tools and strategies used to facilitate collaboration in a digital environment.
Example: Examples of application of these elements could include a multinational corporation using a Learning Platform System to deliver standardized training to employees around the world, a remote team using Remote Collaboration and Communication tools to work together on a project, or an organization using a Training and Learning Management system to track employee progress and certifications.
LOST view: TVA-Digital Workplace Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/BusinessAgnosticDigitalWorkplaceEnablersGrouping
ABB name: egovera:BusinessAgnosticDigitalWorkplaceEnablersGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-21
dct:identifier: http://data.europa.eu/dr8/egovera/BusinessAgnosticDigitalWorkplaceEnablersGrouping
dct:title: Bussiness Agnostic Digital Workplace Enablers
Definition: Digital Exchange Enablers ABB is a Grouping that refers to tools or components that facilitate the exchange of data between systems or applications
Source: EIFv2
Source reference: http://ec.europa.eu/isa/documents/isa_annex_ii_eif_en.pdf
Example: The Data Exchange Service ABB is salient for technical interoperability because it provides secure and trustworthy data exchange between different ICT systems as stated in the EIF: "Define a common security and privacy framework and establish processes for public services to ensure secure and trustworthy data exchange between public administrations and in interactions with citizens and businesses."
Interoperability Dimension: Behavioral IoP
LOST view: Technical view - application
Interoperability Saliency: The Data Exchange Enablers Grouping ABB is salient for technical interoperability because it provides secure and trustworthy data exchange between different ICT systems as stated in the EIF: "Define a common security and privacy framework and establish processes for public services to ensure secure and trustworthy data exchange between public administrations and in interactions with citizens and businesses."
Identifier: http://data.europa.eu/dr8/DataExchangeEnablersGrouping
ABB name: eira:DataExchangeEnablersGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/DataExchangeEnablersGrouping
Interoperability Layer: TechnicalApplication
Description: Privacy Solutions ABB is a grouping that refers to actual solutions that facilitate the secure storage, management, and distribution of sensitive information such as passwords, API keys, and encryption keys across various applications and systems. It is designed to ensure the privacy and security of data in a digital environment.
Additional information: Privacy Solutions ABB is a collection of digital services solutions that are primarily focused on providing secure and private storage and access to sensitive data. The group includes tools like HashiCorp Vault, an open-source tool designed for securely storing and accessing sensitive information. Vault provides a centralized system for managing secrets and ensures their secure distribution across applications and systems. The primary purpose of these solutions is to ensure that sensitive data, such as passwords, API keys, and encryption keys, are securely stored and only accessible to authorized entities. These solutions are critical in maintaining data privacy and security in various digital environments, including cloud-based systems, mobile applications, and other digital platforms.
Example: An example of Privacy Solutions ABB in action is the use of HashiCorp Vault in a cloud-based application. The application may need to store and access various sensitive data, such as user passwords and API keys. Instead of storing this data directly in the application, which could be vulnerable to attacks, the application uses Vault. Vault securely stores the sensitive data and only provides access to it when the application needs it. This ensures that the sensitive data is securely stored and managed, reducing the risk of data breaches and unauthorized access.
Publisher: EIRA Team Research
LOST view: TVA-Privacy Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/BusinessAgnosticPrivacySolutionsGrouping
EIRA traceability: eira:DigitalSolutionApplicationService
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-08-20
dct:identifier: http://data.europa.eu/dr8/egovera/BusinessAgnosticPrivacySolutionsGrouping
dct:title: Privacy Solutions Catalogue
Definition: Resiliency Requirements Catalogue ABB is a grouping that covers a set of non-functional IT requirements that are designed to ensure that a system can withstand and recover from various types of disruptions, including catastrophic events, system failures, and errors. The catalogue includes elements such as 'Disaster Recovery' and 'Recoverability', which outline the strategies and mechanisms needed to minimize the impact of such events on system functionality and data, and to ensure system availability and business continuity.
Source: EIRA Team Research
Additional information: The Resiliency Requirements Catalogue ABB is a comprehensive collection of non-functional IT requirements that focus on the system's ability to bounce back from disruptions. The 'Disaster Recovery' element refers to the strategies and procedures that need to be in place to recover from catastrophic events, such as natural disasters, power outages, or cyber-attacks. This includes backup and recovery procedures, redundant systems, and failover mechanisms. The 'Recoverability' element, on the other hand, refers to the system's ability to recover from failures or errors and return to its normal functioning. This involves implementing backup and recovery mechanisms, such as data replication, redundancy, and failover.
Example: An example of the application of the Resiliency Requirements Catalogue ABB could be in the development of a cloud-based data storage system. The 'Disaster Recovery' element would involve creating a detailed plan for how the system would recover from a catastrophic event, such as a major power outage or a cyber-attack. This could include strategies such as regular data backups, the use of redundant systems, and the implementation of failover mechanisms. The 'Recoverability' element would involve ensuring that the system has the ability to recover data, configurations, and settings after a system crash or other disruptions. This could involve the use of data replication, redundancy, and failover mechanisms.
LOST view: Digital Solution Non-Functional Requirements Catalogue view
Identifier: http://data.europa.eu/dr8/egovera/ResiliencyRequirementsCatalogueGrouping
ABB name: egovera:ResiliencyRequirementsCatalogueGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-17
dct:identifier: http://data.europa.eu/dr8/egovera/ResiliencyRequirementsCatalogueGrouping
dct:title: Resiliency Requirements Catalogue Catalogue
Definition: Business Agnostic Dataset Catalogue Solutions (ABB) is a grouping that covers a range of comprehensive data repositories and catalogues that provide access to a wide array of statistical and open data. These catalogues, which include the Eurostat Data Catalogue, the Official Portal for European Data, and CELLAR, serve as central platforms for accessing diverse datasets and metadata across various domains and geographical scopes. They are designed to be business agnostic, meaning they can be utilized across different industries and sectors.
Source: EIRA Team Research
Additional information: The elements contained in the Business Agnostic Dataset Catalogue Solutions are primarily focused on providing access to European data. The Eurostat Data Catalogue is a comprehensive repository of statistical data and indicators maintained by EUROSTAT, the statistical office of the European Union (EU). It provides a structured and organized collection of datasets covering various domains such as economy, population, employment, agriculture, trade, and many others. The Official Portal for European Data serves as a central point of access to European open data from international, European Union, national, regional, local and geodata portals. CELLAR, on the other hand, is the common data repository of the Publications Office of the European Union, storing digital publications and metadata for use by humans and machines. These catalogues are designed to be business agnostic, meaning they can be utilized across different industries and sectors, providing valuable insights and information for decision-making and strategy development.
Example: Examples of application for the Business Agnostic Dataset Catalogue Solutions could include a business analyst in the agriculture sector using the Eurostat Data Catalogue to access data on crop yields across the EU for comparative analysis, a data scientist using the Official Portal for European Data to gather data for a machine learning model predicting economic trends, or a researcher using CELLAR to access digital publications and metadata for a study on EU policy impacts.
LOST view: SV-Datasets Catalogue Solutions
Identifier: http://data.europa.eu/dr8/egovera/BusinessAgnosticDatasetCatalogueSolutionsGrouping
ABB name: egovera:BusinessAgnosticDatasetCatalogueSolutionsGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/egovera/BusinessAgnosticDatasetCatalogueSolutionsGrouping
Name: Business Agnostic Dataset Catalogue Solutions Catalogue
Interoperability Layer: Semantic
Definition: Workflow Orchestration Infrastructure Enablers ABB is a Grouping that refers to components and services that enable the coordination and automation of components through workflows across multiple systems, applications, and organizations.
Source: Inspired in Redhat
Source reference: https://www.redhat.com/en/topics/automation/what-is-orchestration
Example: The following implementation is an example of how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): UNDP- Business Process Re-engineering Manual. https://www.undp.org/sites/g/files/zskgke326/files/migration/uz/BPR-Manual_designed---Eng---final.pdf
Interoperability Dimension: Structural IoP
LOST view: Technical view - infrastructure
Interoperability Saliency: Process Orchestration Infrastructure Enablers ABB is salient for organizational interoperability because it implements and defines the rules to manage different public administration services and matchmake the processes to provide effective responses to the public administration consumers.
Identifier: http://data.europa.eu/dr8/WorkflowOrchestrationInfrastructureEnablersGrouping
ABB name: eira:WorkflowOrchestrationInfrastructureEnablersGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/WorkflowOrchestrationInfrastructureEnablersGrouping
Interoperability Layer: TechnicalInfrastructure
Definition: Digital Solution Maintainability & Quality Architecture Decision Catalogue ABB is a grouping that covers the technical architectural decisions related to the maintainability and quality of digital solutions. It includes decisions about version control, coding standards, and documentation, which are crucial for the development, maintenance, and quality assurance of software systems.
Source: EIRA Team Research
Additional information: The Digital Solution Maintainability & Quality Architecture Decision Catalogue ABB is a collection of architectural decision records (ADRs) that document the decisions made regarding the technical aspects of a software system's architecture. These decisions typically involve choosing specific technologies, frameworks, protocols, or design patterns. The catalogue includes decisions about version control, which is crucial for tracking changes in the software and facilitating collaboration among developers; coding standards, which ensure consistency and readability in the code; and documentation, which provides necessary information about the software to developers, users, and other stakeholders.
Example: [object Object]
[object Object]
[object Object]
LOST view: Digital Solution Architecture Decisions Catalogue view
Identifier: http://data.europa.eu/dr8/egovera/DigitalSolutionMaintenabilityQualityArchitectureDecisionCatalogueGrouping
ABB name: egovera:DigitalSolutionMaintenabilityQualityArchitectureDecisionCatalogueGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-18
dct:identifier: http://data.europa.eu/dr8/egovera/DigitalSolutionMaintenabilityQualityArchitectureDecisionCatalogueGrouping
dct:title: Digital Solution Maintenability & Quality Architecture Decision Catalogue Catalogue
Definition: Orchestration Enablers ABB is a Grouping Component that refers to the components and practices that support the development and deployment of orchestration applications.
Source: ETSI Network Functions Virtualisation Standard
Source reference: https://portal.etsi.org/NFV/NFV_White_Paper2.pdf
Interoperability Dimension: Structural IoP
LOST view: Technical view - application
Interoperability Saliency: The Orchestration Enablers Grouping ABB is salient for interoperability because it contains both, application services and components, that can enable the deployment and development of orchestration services. By enabling and promoting orchestration, the grouping can contribute to the creation and functioning of an interoperable ecosystem that can foster the digital public services interoperability
Identifier: http://data.europa.eu/dr8/OrchestrationEnablersGrouping
ABB name: eira:OrchestrationEnablersGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/OrchestrationEnablersGrouping
Interoperability Layer: TechnicalApplication
Definition: Identity and Access Management Technical Interoperability Agreement Catalogue ABB is a grouping that refers to the actual catalogue of specifications, agreements and/or contracts that facilitates the implementation of security measures in digital systems. This catalogue is designed to provide a framework for the integration of various security measures, such as Multi-Factor Authentication (MFA), to ensure the protection of data and resources.
Source: EIRA Team Research
Additional information: The Identity and Access Management Technical Interoperability Agreement Catalogue ABB is a comprehensive collection of technical specifications, agreements, and contracts that serve as a guide for implementing security measures in digital systems. One of the key elements in this catalogue is the Multi-Factor Authentication (MFA). MFA is a security measure that requires users to provide two or more verification factors to gain access to a resource such as an application, online account, or a VPN. It is designed to provide an additional layer of protection, minimizing the risk of security breaches and data theft. The factors used in MFA could include something you know (like a password), something you have (like a hardware token or a smartphone), or something you are (like a fingerprint or other biometric method). This catalogue serves to standardize the implementation of such measures across different systems and platforms, ensuring a uniform level of security.
Example: An example of the application of the Identity and Access Management Technical Interoperability Agreement Catalogue ABB would be a company implementing MFA in their digital systems. The company would refer to the catalogue for the technical specifications and agreements related to MFA, ensuring that the implementation is in line with the standardized guidelines. This would involve setting up the system to require users to provide two or more verification factors, which could include a password, a hardware token, or a biometric method.
LOST view: TVA-Governance Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/IdentityAndAccessManagementTechnicalInteroperabilityAgreementCatalogueGrouping
EIRA traceability: eira:TechnicalAgreementContract
ABB name: egovera:IdentityAndAccessManagementTechnicalInteroperabilityAgreementCatalogueGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-17
dct:identifier: http://data.europa.eu/dr8/egovera/IdentityAndAccessManagementTechnicalInteroperabilityAgreementCatalogueGrouping
dct:title: Identity And Access Management Technical Interoperability Agreement Catalogue Catalogue
Definition: Customs Legislation on Behavioural Interoperability (NBI) is a grouping that covers national legal acts related to the processing of statistical data, classification, labelling and packaging of goods, and excise goods. These acts are designed to ensure the smooth and efficient exchange of information and cooperation between different customs authorities and other relevant entities.
Source: EIRA Team Research
Additional information: The Customs Legislation on Behavioural Interoperability (NBI) encompasses various national legal acts that are crucial for the functioning of customs operations. These include the processing of statistical data, which is essential for understanding trade patterns and making informed policy decisions; the classification, labelling and packaging of goods, which ensures that goods are correctly identified and handled during customs procedures; and the regulation of excise goods, which involves the taxation of certain goods. The NBI aims to promote interoperability, or the ability of different systems and organizations to work together, in these areas.
Example: For instance, the 'National legal act on the processing of statistical data' would cover the rules and regulations on how customs authorities collect, process, and share trade data. The 'National legal act on Classification, labelling and packaging of goods' would detail the standards and procedures for classifying, labelling, and packaging goods for customs purposes. The 'National legal act on excise goods' would outline the tax rates and regulations for goods subject to excise duties.
LOST view: LV-Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/CustomsLegislationOnBehaviouralInteroperabilityGrouping
ABB name: egovera:CustomsLegislationOnBehaviouralInteroperabilityGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-20
dct:identifier: http://data.europa.eu/dr8/egovera/CustomsLegislationOnBehaviouralInteroperabilityGrouping
dct:title: Customs Legislation On Behavioural Interoperability (NBI)
Definition: Infrastructure Architect Concerns ABB is a Grouping that covers the key areas of focus for an infrastructure architect in the context of an eGovERA model. It includes the technical view of infrastructure and application, which are essential for understanding and assessing the model.
Source: EIRA Team Research
Additional information: The Infrastructure Architect Concerns ABB grouping is designed to help infrastructure architects navigate the eGovERA model. It includes two main elements: the technical view of infrastructure and the technical view of application. The technical view of infrastructure element covers the physical and technical aspects of the model, including hardware, networks, and other physical resources. The technical view of application element, on the other hand, focuses on the software and application aspects of the model. Both elements are crucial for infrastructure architects to understand and assess the model, and to understand how their role interacts with other roles in the model.
Example: An example of this might be an infrastructure architect assessing the network requirements of the eGovERA model, including bandwidth, latency, and redundancy needs.
An example of this might be an infrastructure architect evaluating the software requirements of the eGovERA model, including operating systems, databases, and application servers.
LOST view: [A] How to read the model
Identifier: http://data.europa.eu/dr8/egovera/InfrastructureArchitectConcernsGrouping
ABB name: egovera:InfrastructureArchitectConcernsGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-18
dct:identifier: http://data.europa.eu/dr8/egovera/InfrastructureArchitectConcernsGrouping
dct:title: Infrastructure Architect Concerns Catalogue
Definition: National Non-Binding Instruments (NNBI) is a grouping that covers a range of legislative catalogues related to interoperability. These catalogues are non-binding in nature, meaning they provide guidelines rather than mandatory rules. The NNBI includes legislation on structural, behavioural, and governance interoperability.
Source: EIRA Team Research
Additional information: The National Non-Binding Instruments (NNBI) is a comprehensive catalogue of legislative documents that provide guidelines on various aspects of interoperability. Interoperability, in this context, refers to the ability of different information systems, devices, or applications to access, exchange, integrate, and cooperatively use data in a coordinated manner, within and across organizational, regional, and national boundaries, to provide timely and seamless portability of information and optimize the health of individuals and populations. The NNBI covers three main areas: structural interoperability, which is about the data exchange and the ensuring that the data exchanged by systems is interpretable; behavioural interoperability, which is about the operation and interaction of systems; and governance interoperability, which is about the policies and agreements that define how systems interact.
Example: [object Object]
[object Object]
[object Object]
LOST view: LV-Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/NationalNon-BindingInstrumentsGrouping
ABB name: egovera:NationalNon-BindingInstrumentsGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-17
dct:identifier: http://data.europa.eu/dr8/egovera/NationalNon-BindingInstrumentsGrouping
dct:title: National Non-Binding Instruments Catalogue
Definition: Wide Area Networking ABB is a Grouping of different of networks to enables communication and data exchange across geographically dispersed locations
Source: Gartner
Source reference: https://www.gartner.com/en/information-technology/glossary/wan-wide-area-network
Definition: Legislation on Behavioural Interoperability (NNBI) is a grouping that covers a range of legal and regulatory frameworks, policies, and guidelines that aim to facilitate and govern the interaction and exchange of information between different systems, applications, and components in a way that they can operate together effectively and efficiently. This catalogue does not contain any specific elements as indicated by the provided JSON.
Source: EIRA Team Research
Additional information: The Legislation on Behavioural Interoperability (NNBI) is a theoretical catalogue that would encompass various laws, regulations, and guidelines that are designed to ensure the smooth interaction and exchange of information between different systems, applications, and components. These laws and regulations would aim to ensure that these different entities can work together in a seamless and efficient manner, without any barriers or obstacles. This would involve setting standards for data exchange, defining protocols for communication, and establishing guidelines for system design and operation. However, the provided JSON indicates that this catalogue does not currently contain any specific elements.
Example: An example of a legislation that could be included in the Legislation on Behavioural Interoperability (NNBI) is a law that sets standards for data exchange between different healthcare systems, ensuring that patient information can be shared seamlessly and securely between different healthcare providers. Another example could be a regulation that defines the protocols for communication between different components of a smart city, ensuring that they can work together to optimize city operations and services.
LOST view: LV-Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/LegislationOnBehaviouralInteroperabilityGrouping
ABB name: egovera:LegislationOnBehaviouralInteroperabilityGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-20
dct:identifier: http://data.europa.eu/dr8/egovera/LegislationOnBehaviouralInteroperabilityGrouping
dct:title: Legislation On Behavioural Interoperability (NNBI) Catalogue
Definition: Digital Solution Security, Privacy and Compliance Architecture Decision Catalogue ABB is a grouping that covers a range of elements focused on security-related decisions made during the architectural design process. These elements document choices related to authentication mechanisms, encryption methods, access control, and other security considerations.
Source: EIRA Team Research
Additional information: The catalogue includes elements such as 'Authentication Mechanism', 'Encryption Standards', 'Secure Communications', 'Role-Based Access Control', 'Security Testing', 'Security Incident Response', 'Access Control Policy', 'Continuous Security Monitoring', 'Retention and Data Deletion', 'Security Incident Response Plan', 'Compliance Monitoring and Auditing', and 'Data Protection Measures'. Each of these elements represents a specific decision made in the architectural design process, with a focus on ensuring the security, privacy, and compliance of the digital solution. The decisions made in these areas can have significant impacts on the overall security posture of the solution, and as such, they are carefully documented and monitored.
Example: Authentication Mechanism
This could involve a decision to use multi-factor authentication for all user logins, to enhance the security of the system.
Encryption Standards
This might involve a decision to use a specific encryption standard, such as AES-256, for all data at rest and in transit.
Secure Communications
This could involve a decision to use secure communication protocols, such as HTTPS and SSL/TLS, to protect data during transmission.
Role-Based Access Control
This might involve a decision to implement role-based access control, to ensure that users only have access to the data and functions that they need for their role.
LOST view: Digital Solution Architecture Decisions Catalogue view
Identifier: http://data.europa.eu/dr8/egovera/DigitalSolutionSecurityPrivacyAndComplianceArchitectureDecisionCatalogueGrouping
ABB name: egovera:DigitalSolutionSecurityPrivacyAndComplianceArchitectureDecisionCatalogueGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-18
dct:identifier: http://data.europa.eu/dr8/egovera/DigitalSolutionSecurityPrivacyAndComplianceArchitectureDecisionCatalogueGrouping
dct:title: Digital Solution Security, Privacy And Compliance Architecture Decision Catalogue Catalogue
Definition: Digital Solution Technical Architecture Decision Catalogue ABB is a Grouping that covers a range of elements related to the technical architectural decisions made during the development of a software system. These decisions typically involve the selection of specific technologies, frameworks, protocols, or design patterns that are best suited to the system's requirements and objectives.
Source: EIRA Team Research
Additional information: The catalogue includes elements such as 'Technology Stack Selection', 'API Design', 'Event-Driven Architecture', 'Database Schema Design', 'Asynchronous Processing', 'Provide a Service Catalog', 'Managing Self-Description Schemas in the Federated Catalogue', 'Monolithic Architecture', 'Microservice Architecture', 'Serveless Architecture', 'Cloud-Native Architecture', 'Big-Data Architecture', and 'Service-Oriented Architecture'. Each of these elements represents a specific architectural decision that needs to be made during the development of a software system. These decisions are critical as they determine the overall structure and functionality of the system, as well as its ability to meet the needs of its users and to adapt to changes in technology and business requirements.
Example: For instance, the 'Technology Stack Selection' element involves deciding on the specific technologies to be used in the system, such as the programming languages, databases, server technologies, and other tools. The 'API Design' element involves deciding on the structure and functionality of the APIs that the system will provide, which can affect its interoperability with other systems. The 'Event-Driven Architecture' element involves deciding on the use of events to drive the system's behavior, which can affect its responsiveness and scalability.
LOST view: Digital Solution Architecture Decisions Catalogue view
Identifier: http://data.europa.eu/dr8/egovera/DigitalSolutionTechnicalArchitectureDecisionCatalogueGrouping
ABB name: egovera:DigitalSolutionTechnicalArchitectureDecisionCatalogueGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-18
dct:identifier: http://data.europa.eu/dr8/egovera/DigitalSolutionTechnicalArchitectureDecisionCatalogueGrouping
dct:title: Digital Solution Technical Architecture Decision Catalogue Catalogue
Description: Data Governance Solutions ABB is a grouping that refers to actual solutions that facilitate the management, usability, availability, integrity, and security of data in an organization. These solutions provide a comprehensive approach to managing an organization's data and information, ensuring that it meets regulatory compliance, data privacy, and business requirements.
Additional information: Data Governance Solutions ABB encompasses a set of processes, roles, policies, standards, and metrics that ensure the effective and efficient use of information in enabling an organization to achieve its goals. It includes data quality management, data architecture, data privacy, data security, and business intelligence. These solutions help organizations to manage their data assets, improve data quality, ensure data privacy and security, and comply with regulations and standards. They also enable organizations to make data-driven decisions, improve operational efficiency, and gain a competitive advantage.
Example: Examples of Data Governance Solutions ABB include data governance software like Informatica Axon, Collibra, and Alation. These tools provide capabilities such as data cataloging, data lineage, data quality management, and data privacy management. They help organizations to understand their data landscape, ensure data quality, protect sensitive data, and comply with data regulations. For instance, a healthcare organization can use these solutions to manage patient data, ensure data privacy and security, comply with HIPAA regulations, and improve patient care.
Publisher: EIRA Team Research
LOST view: TVA-Data Management Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/BusinessAgnosticDataGovernanceSolutionsGrouping
EIRA traceability: eira:DigitalSolutionApplicationService
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-08-20
dct:identifier: http://data.europa.eu/dr8/egovera/BusinessAgnosticDataGovernanceSolutionsGrouping
dct:title: Data Governance SolutionsGrouping
Definition: Artificial Intelligence Infrastructure Enablers ABB is a Grouping that refers to a set of components that facilitate the development and deployment of artificial intelligence applications
Source: European Comission
Source reference: https://digital-strategy.ec.europa.eu/en/library/definition-artificial-intelligence-main-capabilities-and-scientific-disciplines
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): AI Whatch Artificial Intelligence in public administrations. https://publications.jrc.ec.europa.eu/repository/bitstream/JRC120399/jrc120399_misuraca-ai-watch_public-services_30062020_def.pdf
Interoperability Dimension: Structural IoP
LOST view: Technical view - infrastructure
Interoperability Saliency: Artificial Intelligence Infrastructure Enablers ABB is salient for semantic interoperability because it refers to the generation of newer insights (knowledge) from public data to generate (i) new curated datasets and/or (ii) new public data assets based on the combination of other public data.
Identifier: http://data.europa.eu/dr8/ArtificialIntelligenceInfrastructureEnablersGrouping
ABB name: eira:ArtificialIntelligenceInfrastructureEnablersGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/ArtificialIntelligenceInfrastructureEnablersGrouping
Interoperability Layer: TechnicalInfrastructure
Definition: Customs Forms Structure is a grouping that covers a range of forms used in international trade and customs procedures. These forms are essential for the classification, declaration, and certification of goods, ensuring compliance with customs regulations and facilitating the smooth flow of international trade.
Source: EIRA Team Research
Additional information: The Customs Forms Structure includes the BTI Application Form, the EUR.1 Movement Certificate, and the Single Administrative Document (SAD). The BTI Application Form is used to request a binding decision from customs authorities on the classification of specific goods under the Harmonized System (HS). The EUR.1 Movement Certificate certifies the origin of goods and is used to claim preferential treatment in international trade. The Single Administrative Document (SAD) is a form used for customs declarations in the EU and several other countries, aiming to reduce administrative burden and standardize data collected on trade.
Example: For instance, a company importing electronic devices into the EU would need to fill out a BTI Application Form to get a binding decision on the tariff classification of their goods. They would also need to complete a EUR.1 Movement Certificate if they are claiming preferential treatment due to the origin of their goods. Finally, they would need to submit a Single Administrative Document (SAD) to declare their goods to customs authorities.
LOST view: SV-Customs Form Structure [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/CustomsFormsStructureGrouping
ABB name: egovera:CustomsFormsStructureGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-20
dct:identifier: http://data.europa.eu/dr8/egovera/CustomsFormsStructureGrouping
dct:title: Customs Forms Structure
Definition: Shared Organisational Content ABB is a Grouping setting organizational (re)usable resources with convergence power, to public policy goals attainment, enabling to reuse and share digital public services across public administrations and borders.
Source: EUR-LEX
Source reference: (https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32021R0695&qid=1646736486403)
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/SharedOrganisationalContentGrouping
LOST view: Organisational view
EIRA concept: eira:ArchitectureBuildingBlock
ABB name: eira:SharedOrganisationalContentGrouping
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): The recent economic and financial crisis revealed weaknesses in the EU's economic governance. The EU responded by taking a wide range of measures to strengthen its governance and to facilitate a return to sustainable economic growth, job creation, financial stability and sound public finances.(https://ec.europa.eu/info/sites/default/files/eu-economic-governance-explained.pdf)
Interoperability Saliency: The Shared Organisational Content ABB is a key interoperability enabler (*) for the governance, behavioural and structural enablers. This ABB is salient for legal interoperability because it defines the public policy goals that enable enabling i) sharing/provisioning/reusing/consumption of legislation on digital public services, ii) the exchange of data, information, and knowledge between digital public services, and iii) collaboration between digital public services
Additional information: This convergence power is based on the enabling communication and harmonization nature of these resources influencing collaboration cross levels in a public administration, cross public administrations, and cross borders. The degree of achievement could range from an ideal perfect shared governance framework (i.e. no interoperability barriers from the organisational perspective) to an imperfect or even null shared governance framework (i.e. some interoperability barriers from the organizational perspective). The level of organizational interoperability will constrain digital public services cross levels in a public administration, cross public administrations, and cross borders. The shared governance framework enables: i) structural interoperability with organisational resources supporting reusing and/or sharing of digital public services (i.e. public services catalogues); ii) behavioural interoperability with organisational resources supporting exchanging capabilities of data, information or knowledge with internal/external peers (i.e. user experience patterns and service delivery mode); and iii) governance interoperability with governance resources supporting the assurance and control of collaboration with internal/external peers exchanging data, information, and knowledge (i.e. Organisational Interoperability Agreements).
Interoperability Dimension: Structural IoP
Viewpoint: Highlevel viewpoint
Additional identifier: http://data.europa.eu/dr8/SharedOrganisationalContentGrouping
EIF Layer: Organisational
Definition: Business Agnostic EU Vocabularies Reference Data Solutions (BAEUV RDS) is a grouping that covers a range of information entities designed to support and enhance the efficiency of the Single Market. It includes elements such as NUTS, Reference Data Asset, Authority Tables, and the Digital Europe Thesaurus. These elements aim to standardize and harmonize codes, labels, and other forms of data across various platforms and systems, facilitating effective communication and data exchange.
Source: EIRA Team Research
Additional information: The BAEUV RDS is a comprehensive catalogue of information entities that serve a critical role in the functioning of the Single Market. 'NUTS' is an element that encourages the use of electronic communication and information technology in public procurement to ensure value for money. 'Reference Data Asset' refers to distinct reference data assets like authority tables, taxonomies, thesauri, ontologies, etc., maintained by organizations like the EU vocabularies. 'Authority Tables' or Named Authority Lists (NALs) are used to standardize and harmonize the codes and labels used across various platforms and systems, facilitating data exchanges. 'Digital Europe Thesaurus' is a multilingual thesaurus covering the main subject matters of the European Commission public communications.
Example: An example of the application of BAEUV RDS could be in the public procurement process where NUTS is used to provide relevant information electronically to ensure best value for money. Another example could be the use of the Digital Europe Thesaurus in the European Commission's public communications to ensure consistency and clarity of information across different languages.
LOST view: SV-Agnostic Reference Data
Identifier: http://data.europa.eu/dr8/egovera/BusinessAgnosticEUVocabulariesReferenceDataSolutionsGrouping
ABB name: egovera:BusinessAgnosticEUVocabulariesReferenceDataSolutionsGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/egovera/BusinessAgnosticEUVocabulariesReferenceDataSolutionsGrouping
Name: Business Agnostic EU Vocabularies Reference Data Solutions Catalogue
Interoperability Layer: Semantic
Definition: Business Agnostic Ontology Solutions (BAOS) is a grouping that covers a range of standardized representations and frameworks for describing, modeling, validating, and interchanging data and metadata in various contexts. These solutions are designed to facilitate semantic interoperability, data discoverability, and the description of organizational structures, roles, relationships, and digital assets, particularly in the field of Linked Data and the Semantic Web.
Source: EIRA Team Research
Additional information: The elements of BAOS include W3C Organization, W3C Shapes Constraint Language (SHACL), PROV-O, FOAF, DCAT-AP, ADMS, ADMS-AP, DCAT, and ODRL. These elements provide a set of classes, properties, and restrictions that can be used to represent and interchange provenance information generated in different systems and under different contexts. They also provide a language and framework for describing and validating the structure and constraints of RDF graphs, a collection of basic terms for machine-readable Web homepages, and a specification for metadata records to meet the specific application needs of data portals in Europe.
Example: For example, the W3C Organization Ontology can be used to model the hierarchy, departments, employees, and roles of an organization in a standardized way. The SHACL can be used to validate the structure and constraints of RDF graphs. The PROV-O can be used to represent and interchange provenance information generated in different systems. The FOAF project can be used to create machine-readable Web homepages for people, groups, companies, and other kinds of things. The DCAT-AP can be used to provide semantic interoperability for data portals in Europe. The ADMS and ADMS-AP can be used to facilitate the description and discovery of digital assets in the context of public administration. The DCAT can be used to describe datasets and data services in a catalog. The ODRL can be used to describe and model various aspects of organizations.
LOST view: SV-Ontology [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/BusinessAgnosticOntologySolutionsGrouping
ABB name: egovera:BusinessAgnosticOntologySolutionsGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-20
dct:identifier: http://data.europa.eu/dr8/egovera/BusinessAgnosticOntologySolutionsGrouping
dct:title: Business Agnostic Ontology Solutions
Description: Business Agnostic Identity and Access Management Technical Interoperability Agreement Solutions (BAIAMTIAS) is a grouping that refers to actual solutions that facilitate the management of digital identities and access rights across different business environments. These solutions are based on various open standards and protocols that ensure secure and efficient authentication, authorization, and exchange of security assertions between different systems and applications.
Additional information: The BAIAMTIAS includes a variety of protocols and standards such as OpenID, SAML, NTLM, OAuth 2.0, OAuth 1.0, Basic Auth, Bearer Token, JWT Bearer, Hawk Authentication, and Digest Auth. These elements provide a range of functionalities from decentralized authentication (OpenID), exchanging authentication and authorization data (SAML), providing authentication, integrity, and confidentiality to users (NTLM), to enabling applications to obtain limited access to user accounts on an HTTP service (OAuth 2.0 and 1.0). They also include methods for a web browser or application to provide a username and password when making a request (Basic Auth), using a type of access token for user authentication (Bearer Token), using a JSON Web Token as a bearer token (JWT Bearer), making HTTP requests authenticated using a Message Authentication Code (MAC) algorithm (Hawk Authentication), and authenticating a user and verifying their access rights to a system or server (Digest Auth).
Example: Examples of application of BAIAMTIAS include: a user logging into multiple unrelated websites using a single identity and password through OpenID; an enterprise-level application allowing single sign-on using SAML; a Windows operating system using NTLM for authentication in various network protocols; a web application obtaining limited access to a user's Facebook account through OAuth 2.0; a web browser providing a username and password when making a request using Basic Auth; a server generating a Bearer Token in response to a login request for user authentication; a scalable application using JWT Bearer for client authentication and authorization; a RESTful API making HTTP requests authenticated using Hawk Authentication; and a system verifying a user's access rights using Digest Auth.
Publisher: EIRA Team Research
LOST view: TV-Technical Agreements
Identifier: http://data.europa.eu/dr8/egovera/BusinessAgnosticIdentityAndAccessManagementTechnicalInteroperabilityAgreementSolutionsGrouping
EIRA traceability: eira:TechnicalInteroperabilityAgreementContract
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-08-17
dct:identifier: http://data.europa.eu/dr8/egovera/BusinessAgnosticIdentityAndAccessManagementTechnicalInteroperabilityAgreementSolutionsGrouping
dct:title: Business Agnostic Identity And Access Management Technical Interoperability Agreement Solutions Catalogue
Definition: Security Enablers ABB is a Grouping that refers to components that enable the implementation and management of security controls and measures, and enable organizations to protect their digital assets and information from a wide range of cyber threats
Source: Inspired n Cyber Resilience Act
Source reference: https://digital-strategy.ec.europa.eu/en/library/cyber-resilience-act
Interoperability Dimension: Structural IoP
LOST view: Technical view - application
Interoperability Saliency: The Security Enablers Grouping ABB is salient for interoperability because it aggregates the set of services and components that allow to secure systems and protect them from cyber threats. In this sense, security can play a relevant role, making systems safe and as consequence, ensuring their integrity. All these aspects can contribute to the development of an interoperable and secure environment of digital public services.
Identifier: http://data.europa.eu/dr8/SecurityEnablersGrouping
ABB name: eira:SecurityEnablersGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/SecurityEnablersGrouping
Interoperability Layer: TechnicalApplication
Definition: Customs Web Services Solutions ABB is a Grouping that covers a range of digital solutions and systems designed to streamline and facilitate customs procedures, trade facilitation, and regulatory compliance within the European Union. These solutions provide comprehensive information and tools for customs authorities, businesses, and traders to manage and facilitate the classification of goods, track goods in transit, validate EORI numbers, monitor customs transactions, and more.
Source: EIRA Team Research
Additional information: The elements within the Customs Web Services Solutions ABB include CLASS - Classification Information System, EU Customs Trader Portal system, ECICS - European Customs Inventory of Chemical Substances, TRANSIT - Tracking goods in transit, EORI - Economic Operators Registration and Identification number, SAMANCTA - Sampling manual for customs taxation authorities, ILIADe - Inter Laboratory Inventory of Analytical Determination, EORI - validation open interface, MRN follow-up - Movement Reference Number, Surveillance System, TARIC - EU Customs Tariff, AEO - Authorised Economic Operator, CDS - Customs Decisions System, COPIS (COunterfeit and anti-Piracy Information System), and EBTI - European Binding Tariff Information. Each of these elements serves a specific purpose in the customs and trade process, providing essential information, tools, and services to facilitate efficient, secure, and compliant cross-border trade within the EU.
Example: For instance, the CLASS - Classification Information System stores and organizes detailed information about various products and their corresponding customs codes, enabling accurate and consistent classification during import and export processes. The EU Customs Trader Portal system provides a single access point to the online systems for 'Authorised Economic Operators' (AEO), the 'European Binding Tariff Information' (EBTI), the Information Sheet on Special Procedures (INF), and Registered Exporter system (REX). The EORI - validation open interface allows external systems and stakeholders to validate the authenticity and correctness of EORI numbers in real-time, ensuring that customs declarations, trade documents, and other transactions involving economic operators are accurate and legitimate.
LOST view: TVA-Customs API Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/CustomsWebServicesSolutionsGrouping
ABB name: egovera:CustomsWebServicesSolutionsGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-20
dct:identifier: http://data.europa.eu/dr8/egovera/CustomsWebServicesSolutionsGrouping
dct:title: Customs Web Services Solutions
Definition: Governance Analyst Concerns ABB is a Grouping that covers the processes a governance analyst should follow, and the relation/influence of process related with other roles' processes, to read/assess/understand an eGovERA model. It includes elements such as the Organisational view and Legal view.
Source: EIRA Team Research
Additional information: The Governance Analyst Concerns ABB is a comprehensive catalogue of elements that a governance analyst needs to consider when assessing an eGovERA model. It includes the Organisational view, which pertains to the understanding of the structure, roles, and responsibilities within the organization. The Legal view, on the other hand, deals with the legal aspects, regulations, and compliance requirements that the organization needs to adhere to. These elements are crucial in providing a holistic understanding of the eGovERA model and its implications on the organization's governance.
Example: For instance, a governance analyst may use the Organisational view to understand the hierarchy within the organization, the roles of different stakeholders, and how decisions are made and implemented.
In the Legal view, the analyst may assess the legal compliance of the organization, understanding the laws and regulations it needs to follow, and ensuring that the organization's processes are in line with these legal requirements.
LOST view: [A] How to read the model
Identifier: http://data.europa.eu/dr8/egovera/GovernanceAnalystConcernsGrouping
ABB name: egovera:GovernanceAnalystConcernsGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-18
dct:identifier: http://data.europa.eu/dr8/egovera/GovernanceAnalystConcernsGrouping
dct:title: Governance Analyst Concerns Catalogue
Definition: European Binding Instruments (EBI) is a grouping that covers a wide range of legislative and regulatory instruments enacted by the European Union (EU) to govern various aspects of interoperability within the digital single market. These instruments aim to harmonize rules and regulations across EU member states, promote fair competition and innovation, protect consumer rights, and ensure the security and privacy of electronic transactions. The EBI includes directives, regulations, and proposals that address issues related to governance, behavioural, and structural interoperability.
Source: EIRA Team Research
Additional information: The European Binding Instruments (EBI) catalogue includes a variety of legislative and regulatory instruments that govern different aspects of interoperability within the digital single market of the European Union. These instruments are grouped into three categories: Legislation on Governance Interoperability, Legislation on Behavioural Interoperability, and Legislation on Structural Interoperability. Each category includes a number of specific instruments, such as directives and regulations, that address specific issues related to electronic communications, digital content and services, public procurement, insurance distribution, payment services, cross-border parcel delivery services, geo-blocking, electronic commerce, open data, data protection, free flow of non-personal data, web accessibility, electronic invoicing, cybersecurity, and electronic identification and trust services.
Example: An example of a European Binding Instrument is the Directive (EU) 2018/1972, also known as the European Electronic Communications Code. This directive aims to modernize and harmonize the regulatory framework for electronic communications across the European Union. It sets out rules and obligations for electronic communications services, networks, and infrastructure providers, with the goal of promoting competition, investment, and innovation in the sector. Another example is the General Data Protection Regulation (GDPR), which is a regulation enacted by the European Union in 2016 to protect the privacy and personal data of individuals within the EU. It establishes rules and guidelines for the processing of personal data by organizations, including the collection, storage, and transfer of such data.
LOST view: LV-Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/EuropeanBindingInstrumentsGrouping
ABB name: egovera:EuropeanBindingInstrumentsGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-17
dct:identifier: http://data.europa.eu/dr8/egovera/EuropeanBindingInstrumentsGrouping
dct:title: European Binding Instruments Catalogue
Definition: Business Agnostic Data Model Solutions ABB is a Grouping that covers a range of data model solutions that are applicable across various business domains. These solutions include the Common Data Model (CDM) and eProcurement Data Model Solutions, which are designed to standardize and structure data for efficient use and interoperability.
Source: EIRA Team Research
Additional information: The Business Agnostic Data Model Solutions ABB includes the Common Data Model (CDM), an ontology based on the FRBR model (Functional Requirements for Bibliographic Records) that uses RDF(S)/OWL technologies to represent relationships between resource types. This model is particularly useful in the Publications Office, where it can represent various views of resources within the scope of the FRBR model. Another key element of this grouping is the eProcurement Data Model Solutions, which includes the European Single Procurement Document (ESPD). The ESPD is a standardized form used in public procurement processes within the European Union (EU) that serves as a preliminary self-declaration by suppliers, demonstrating their eligibility and suitability to participate in public procurement procedures across EU member states.
Example: For example, the Common Data Model can be used by a Publications Office to manage and represent relationships between various resource types, such as books, articles, and other publications. On the other hand, the eProcurement Data Model Solutions, particularly the ESPD, can be used by suppliers and contractors to provide essential information about their company, including identification, financial standing, technical and professional abilities, and any legal grounds for exclusion, during public procurement processes within the EU.
LOST view: SV-Data Model [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/BusinessAgnosticDataModelSolutionsGrouping
ABB name: egovera:BusinessAgnosticDataModelSolutionsGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-21
dct:identifier: http://data.europa.eu/dr8/egovera/BusinessAgnosticDataModelSolutionsGrouping
dct:title: Business Agnostic Data Model Solutions
Definition: Software Architect Concerns ABB is a Grouping that covers the processes a software architect should follow, and the relation/influence of process related with other roles' processes, to read/assess/understand an eGovERA model. It includes elements such as 'Technical view - application' and 'Semantic view'.
Source: EIRA Team Research
Additional information: The Software Architect Concerns ABB grouping is designed to guide software architects in understanding and assessing an eGovERA model. It includes elements like 'Technical view - application', which focuses on the technical aspects of the application, and 'Semantic view', which deals with the meaning and interpretation of the data and information in the model. These elements help the software architect to understand the technical and semantic aspects of the eGovERA model, and how they relate to and influence the processes of other roles.
Example: This element might involve understanding the technical architecture of the application, including the software and hardware requirements, the data structures, the interfaces, and the algorithms used in the application.
This element might involve understanding the semantics of the data and information in the eGovERA model, including the meaning of the data, the relationships between different data elements, and the rules and constraints that govern the data.
LOST view: [A] How to read the model
Identifier: http://data.europa.eu/dr8/egovera/SoftwareArchitectConcernsGrouping
ABB name: egovera:SoftwareArchitectConcernsGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-18
dct:identifier: http://data.europa.eu/dr8/egovera/SoftwareArchitectConcernsGrouping
dct:title: Software Architect Concerns Catalogue
Definition: Observability Requirements Catalogue ABB is a grouping that covers non-functional requirements related to system monitoring, logging, and tiered levels of support. These requirements are critical for ensuring the reliability, availability, performance, security, and effective use of IT systems and applications.
Source: EIRA Team Research
Additional information: The Observability Requirements Catalogue ABB includes three main elements: Alerts and Monitoring, Logging, and Tiered Levels of Support. Alerts and Monitoring refer to the system's ability to detect and report issues or anomalies in real-time, ensuring optimal performance and availability. Logging involves recording events and activities within a system or application, providing a detailed record of system behavior for troubleshooting, auditing, and analysis. Tiered Levels of Support refers to the hierarchical provision of technical support to users based on their needs, ensuring quick and efficient resolution of technical issues. These requirements are essential for maintaining the security and reliability of IT systems, meeting regulatory compliance requirements, minimizing downtime, and enabling effective use of the system or application.
Example: Examples of application for the Observability Requirements Catalogue ABB include: a cloud-based software application implementing real-time alerts and monitoring to detect and report system errors, a banking system implementing logging to record user actions and system errors for auditing and analysis, and a customer support center implementing tiered levels of support to provide appropriate technical assistance to users based on their needs.
LOST view: Digital Solution Non-Functional Requirements Catalogue view
Identifier: http://data.europa.eu/dr8/egovera/ObservabilityRequirementsCatalogueGrouping
ABB name: egovera:ObservabilityRequirementsCatalogueGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-17
dct:identifier: http://data.europa.eu/dr8/egovera/ObservabilityRequirementsCatalogueGrouping
dct:title: Observability Requirements Catalogue Catalogue
Definition: BlockChain Technical Interoperability Agreement Catalogue ABB is a grouping that refers to the actual catalogue of specifications, agreements and/or contracts that facilitates the interoperability of blockchain technology among European member states and private companies. It includes agreements and governance models that aim to standardize the use, development, and maintenance of blockchain technology, ensuring secure and transparent data exchange and collaboration.
Source: EIRA Team Research
Additional information: The BlockChain Technical Interoperability Agreement Catalogue ABB includes elements such as the Blockchain IoP Agreement, Blockchain Governance, Hybrid Blockchain Governance, Public Blockchain Governance (permissionless), and Private Blockchain Governance (permissioned). Each of these elements plays a crucial role in establishing a standardized framework for the use of blockchain technology within the European Union. They aim to promote transparency, security, and trust in blockchain-based systems, enabling seamless data exchange and interoperability between member states and private entities. They also address issues such as data privacy, regulatory compliance, and dispute resolution, ensuring a harmonized approach to blockchain implementation and utilization across Europe.
Example: For instance, the Blockchain IoP Agreement ensures that different IT systems can work together efficiently, promoting seamless communication and data exchange. Blockchain Governance establishes rules, standards, and protocols that govern the use of blockchain technology. Hybrid Blockchain Governance combines elements of both centralized and decentralized governance models to ensure efficient and secure data exchange. Public Blockchain Governance (permissionless) allows for open participation and consensus among all stakeholders, fostering trust and enabling seamless interoperability. Lastly, Private Blockchain Governance (permissioned) restricts access to the blockchain to a select group of participants, facilitating secure and efficient data exchange and collaboration.
LOST view: TVA-Governance Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/BlockChainTechnicalInteroperabilityAgreementCatalogueGrouping
EIRA traceability: eira:TechnicalAgreementContract
ABB name: egovera:BlockChainTechnicalInteroperabilityAgreementCatalogueGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-17
dct:identifier: http://data.europa.eu/dr8/egovera/BlockChainTechnicalInteroperabilityAgreementCatalogueGrouping
dct:title: BlockChain Technical Interoperability Agreement Catalogue Catalogue
Definition: Customs Legislation on Structural Interoperability (NNBI) ABB is a grouping that covers the legal, technical, and procedural aspects of customs operations that ensure seamless and efficient exchange of information between different systems, platforms, and applications. This includes laws, regulations, and standards that govern the interoperability of customs systems and processes.
Source: EIRA Team Research
Additional information: The Customs Legislation on Structural Interoperability (NNBI) ABB is a comprehensive catalogue of elements that encompass the legal, technical, and procedural aspects of customs operations to ensure seamless and efficient exchange of information between different systems, platforms, and applications. This includes, but is not limited to, laws, regulations, standards, protocols, and guidelines that govern the interoperability of customs systems and processes. The aim of this catalogue is to provide a structured framework that facilitates the harmonization of customs operations, promotes efficiency, and enhances compliance with international customs standards and regulations.
Example: Examples of application include the use of the NNBI ABB in the development of customs software systems that ensure seamless data exchange between different customs authorities, the application of NNBI ABB in the formulation of customs laws and regulations that promote interoperability, and the use of NNBI ABB in the design of customs procedures that facilitate efficient and seamless operations.
LOST view: LV-Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/CustomsLegislationOnStructuralInteroperabilityGrouping
ABB name: egovera:CustomsLegislationOnStructuralInteroperabilityGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-20
dct:identifier: http://data.europa.eu/dr8/egovera/CustomsLegislationOnStructuralInteroperabilityGrouping
dct:title: Customs Legislation On Structural Interoperability (NNBI)
Definition: Technical Governance Content ABB is a Grouping that refers to formal decisions on technical frameworks, institutional arrangements, organisational structures, roles and responsibilities, policies, agreements and other aspects of ensuring and monitoring public services at national and EU levels
Source: Inspired in EIF
Source reference: https://ec.europa.eu/isa2/sites/default/files/eif_brochure_final.pdf
Identifier: http://data.europa.eu/dr8/TechnicalGovernanceContentGrouping
eira:ID: http://data.europa.eu/dr8/TechnicalGovernanceContentGrouping
ABB name: eira:TechnicalGovernanceContentGrouping
Definition: Customs Dataset Solutions ABB is a Grouping that covers the collection, organization, and management of data related to customs operations. It includes elements such as EORI metadata and Economic operators metadata, which are crucial for the smooth functioning of customs procedures and operations.
Source: EIRA Team Research
Additional information: The Customs Dataset Solutions ABB is a comprehensive collection of data solutions designed to streamline and enhance customs operations. It includes elements like 'EORI metadata', which refers to data related to the Economic Operators Registration and Identification number, a unique ID assigned to businesses that interact with customs authorities. Another element is 'Economic operators metadata', which pertains to data about economic operators involved in customs operations. These elements are crucial for ensuring efficient customs procedures, facilitating international trade, and ensuring compliance with customs regulations.
Example: For instance, the EORI metadata could be used to quickly identify and verify the details of a business involved in importing or exporting goods. The Economic operators metadata, on the other hand, could provide valuable insights into the operations of economic operators, helping customs authorities to monitor and regulate trade activities more effectively.
LOST view: SV-Customs Datasets [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/CustomsDatasetSolutionsGrouping
ABB name: egovera:CustomsDatasetSolutionsGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-21
dct:identifier: http://data.europa.eu/dr8/egovera/CustomsDatasetSolutionsGrouping
dct:title: Customs Dataset Solutions
Definition: Customs Identification and Access Solutions ABB is a Grouping that covers a range of systems and services designed to manage and secure the digital identities of individuals, devices, and applications involved in EU customs processes. These solutions facilitate the management of authorisation assignments, the formalisation of electronic identification, and the tracking and recording of access to resources, facilities, and information.
Source: EIRA Team Research
Additional information: The Customs Identification and Access Solutions ABB includes elements such as the Central Uniform User Management and Digital Signature System (UUMDS), which allows EU traders to manage authorisation assignments. It also includes the TAXUD Identity Management Service, an Application Service that manages and secures digital entities. The TAXUD Authorisation Service is another element, enabling processes to confirm the electronic identification of a natural or legal person, or the origin and integrity of data in electronic form. Lastly, the TAXUD Accounting Service is included, enabling the process of tracking and recording access to resources, facilities, and information.
Example: For example, an EU trader could use the Central Uniform User Management and Digital Signature System (UUMDS) to delegate authorisation to a colleague. They could also use the TAXUD Identity Management Service to secure their digital identity, the TAXUD Authorisation Service to confirm their electronic identification, and the TAXUD Accounting Service to track and record their access to relevant resources.
LOST view: TVA-Customs Identification and Access Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/CustomsIdentificationAndAccessSolutionsGrouping
ABB name: egovera:CustomsIdentificationAndAccessSolutionsGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-20
dct:identifier: http://data.europa.eu/dr8/egovera/CustomsIdentificationAndAccessSolutionsGrouping
dct:title: Customs Identification And Access Solutions
Definition: Secure Public Network Solutions ABB is a Grouping that covers a range of network solutions designed to ensure secure and reliable communication in public networks. These solutions include the Common Communication Network (CCN) and Common Communication Network 2 (CCN 2), both of which are designed to facilitate secure and efficient communication across public networks.
Source: EIRA Team Research
Additional information: The Secure Public Network Solutions ABB is a comprehensive catalogue of network solutions that are designed to enhance the security and reliability of communication in public networks. The catalogue includes the Common Communication Network (CCN) and Common Communication Network 2 (CCN 2). The CCN is a communication network that is commonly used for secure and reliable communication in public networks. Similarly, the CCN 2 is an upgraded version of the CCN that offers enhanced features and capabilities for secure and efficient communication in public networks. Both these solutions are designed with advanced security features to protect against potential threats and vulnerabilities in public networks.
Example: Examples of application of the Secure Public Network Solutions ABB include public institutions like government agencies and organizations that require secure and reliable communication networks. These solutions can also be used in industries such as telecommunications, finance, and healthcare where secure and efficient communication is critical.
LOST view: TVI-Wide Area Networking [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/SecurePublicNetworkSolutionsGrouping
ABB name: egovera:SecurePublicNetworkSolutionsGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-21
dct:identifier: http://data.europa.eu/dr8/egovera/SecurePublicNetworkSolutionsGrouping
dct:title: Secure Public Network Solutions
Definition: Artificial Intelligence Enablers ABB is a Grouping that refers to components and services that provide the necessary infrastructure and resources for AI developers to build intelligent systems that can perform tasks that typically require human-like intelligence, such as perception, reasoning, learning, and decision-making
Source: European Comision
Source reference: https://digital-strategy.ec.europa.eu/en/library/definition-artificial-intelligence-main-capabilities-and-scientific-disciplines
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): PyTorch is a machine learning framework based on the Torch library, used for applications such as computer vision and natural language processing, originally developed by Meta AI and now part of the Linux Foundation umbrella. It is free and open-source software released under the modified BSD license. Although the Python interface is more polished and the primary focus of development, PyTorch also has a C++ interface. https://pytorch.org/
Interoperability Dimension: Structural IoP
LOST view: Technical view - application
Interoperability Saliency: The Artificial Intelligence Enablers Grouping ABB is salient for technical interoperability because it comprises tools and services that provide the necessary infrastructure and resources for AI developers to build intelligent systems that can perform tasks that typically require human-like intelligence, such as perception, reasoning, learning, and decision-making. This can contribute to enabling and creating cutting-edge digital public services interoperable with others.
Identifier: http://data.europa.eu/dr8/ArtificialIntelligenceEnablersGrouping
ABB name: eira:ArtificialIntelligenceEnablersGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/ArtificialIntelligenceEnablersGrouping
Interoperability Layer: TechnicalApplication
Definition: Security Requirements Catalogue ABB is a grouping that covers a range of non-functional IT requirements that are critical for ensuring the security, integrity, and reliability of a system or application. These requirements include confidentiality, integrity, nonrepudiation, accountability, authenticity, auditability, authentication, authorization, legality, compliance, and privacy. Each of these elements plays a crucial role in protecting sensitive information, preventing unauthorized access or modification, ensuring compliance with laws and regulations, and maintaining the trustworthiness and credibility of the system.
Source: EIRA Team Research
Additional information: The Security Requirements Catalogue ABB is a comprehensive collection of IT security requirements that are essential for any system or application that handles sensitive data. These requirements are designed to protect the data from unauthorized access, ensure its accuracy and consistency, provide proof of transactions, track user activities, verify user identities, grant appropriate access levels, comply with legal and regulatory standards, and safeguard privacy. Failure to meet these requirements can result in security breaches, loss of data integrity, legal penalties, and loss of trust among users and stakeholders.
Example: For example, a healthcare application would need to meet the requirements of confidentiality to protect patient data, integrity to ensure the accuracy of medical records, nonrepudiation to provide proof of medical orders, accountability to track user activities, authenticity to verify the genuineness of data, auditability to provide a record of transactions, authentication to verify user identities, authorization to grant appropriate access levels, legality to comply with healthcare regulations, compliance to adhere to data protection standards, and privacy to safeguard patient privacy.
LOST view: Digital Solution Non-Functional Requirements Catalogue view
Identifier: http://data.europa.eu/dr8/egovera/SecurityRequirementsCatalogueGrouping
ABB name: egovera:SecurityRequirementsCatalogueGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-17
dct:identifier: http://data.europa.eu/dr8/egovera/SecurityRequirementsCatalogueGrouping
dct:title: Security Requirements Catalogue Catalogue
Definition: Geo-spatial Data Format is a grouping that covers various formats used for encoding, storing, and exchanging geospatial data. These formats include GeoJSON, KML, and GML, each of which serves a unique purpose and is used in different applications. They provide a standardized and flexible way to represent geographic features and their associated attributes, facilitating the exchange of geographic data between different systems and applications.
Source: EIRA Team Research
Additional information: GeoJSON is a format for encoding geospatial data in JSON (JavaScript Object Notation), providing a standard and flexible way to represent geographic features, such as points, lines, and polygons, along with their associated attributes. Keyhole Markup Language (KML) is an XML notation for expressing geographic annotation and visualization within two-dimensional maps and three-dimensional Earth browsers, developed for use with Google Earth. Geography Markup Language (GML) is an XML-based format used to encode geographic information, including the geometry and properties of geographic features, facilitating the exchange of geographic data between different systems and applications.
Example: GeoJSON is often used in web applications that need to visualize geographic data, such as interactive maps. KML is commonly used to create and share geographic data with Google Earth and other Earth browsers. GML is used in a variety of domains, including geographic information systems (GIS), web mapping, and location-based services.
LOST view: SV-Functional Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/Geo-spatialDataFormatSolutionsGrouping
ABB name: egovera:Geo-spatialDataFormatSolutionsGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/egovera/Geo-spatialDataFormatSolutionsGrouping
Name: Geo-spatial Data Format Catalogue
Interoperability Layer: Semantic
Definition: Analytics Infrastructure Enablers ABB is a Grouping that refers to the set of components and services that support the development and deployment of data analytics solutions
Source: Inspired in CROS
Source reference: https://ec.europa.eu/eurostat/cros/content/36-strategy-european-data-infrastructure_en
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): Central banks increasingly need to use business intelligence (BI) systems to collect, manage and analyse data in order to inform policy decisions. This report presents the results of a survey conducted by the BIS’s Irving Fisher Committee on Central Bank Statistics (IFC) in 2019. The following link gives access to a report on the use of BI in Central Banks. https://www.bis.org/ifc/publ/ifc_report_bi_1910.pdf
Interoperability Dimension: Behavioral IoP
LOST view: Technical view - infrastructure
Interoperability Saliency: Analytics Infrastructure Enablers ABB is salient for the semantic and organizational interoperability because it sets the analytical environments that relate to (i) data processing of a large amount of data, (ii) data visualization and interaction, and (iii) catalogues discovery and data sharing across multiple workspaces.
Identifier: http://data.europa.eu/dr8/AnalyticsInfrastructureEnablersGrouping
ABB name: eira:AnalyticsInfrastructureEnablersGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/AnalyticsInfrastructureEnablersGrouping
Interoperability Layer: TechnicalInfrastructure
Definition: Customs Duties and Tariffs Management Enablers ABB is a Grouping that covers the digital and automated management of customs tariffs and duties. This includes the systematic management of tariff registries and the accurate calculation and payment of customs duties. These services leverage digital technologies to enhance efficiency, reduce errors, ensure compliance, and support smooth trade operations within the customs environment.
Source: EIRA Team Research
Additional information: The Customs Duties and Tariffs Management Enablers ABB includes two main elements: Tariffs Registry Management and Duties Calculation and Payment. Tariffs Registry Management refers to the digitalization and centralization of tariff schedules, rates, and updates within a digital registry or database. This service allows customs authorities to efficiently maintain, update, and disseminate tariff information, facilitating tariff classification and supporting customs compliance. Duties Calculation and Payment, on the other hand, refers to the automated and accurate determination and processing of customs duties and taxes owed on imported or exported goods. This service integrates with customs systems, financial institutions, and payment gateways to facilitate seamless payment processing, enabling importers or exporters to efficiently settle their customs obligations.
Example: For instance, a customs authority could use the Tariffs Registry Management service to maintain and update its tariff schedules, ensuring accurate and consistent application of tariffs during customs processes. An importer or exporter could use the Duties Calculation and Payment service to calculate and pay the customs duties and taxes owed on their goods, expediting the release of their goods and ensuring compliance with customs regulations.
LOST view: TVA-Customs Duties and Tariffs Management Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/CustomsDutiesAndTariffsManagementEnablersGrouping
ABB name: egovera:CustomsDutiesAndTariffsManagementEnablersGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-20
dct:identifier: http://data.europa.eu/dr8/egovera/CustomsDutiesAndTariffsManagementEnablersGrouping
dct:title: Customs Duties And Tariffs Management Enablers
Definition: Customs Trade Facilitation and Collaboration Enablers ABB is a Grouping that covers a range of digital platforms and systems designed to streamline and enhance the efficiency of customs operations, promote collaboration and information exchange between customs authorities, traders, and other stakeholders, and facilitate cross-border trade. The elements within this grouping include the Trade Facilitation Portal, Cooperation between Customs laboratories, Cooperation between Customs and Postal Operators, and MS' Customs organization management.
Source: EIRA Team Research
Additional information: The elements within the Customs Trade Facilitation and Collaboration Enablers ABB grouping are digital solutions that leverage technologies such as electronic data interchange (EDI), data analytics, and laboratory information management systems (LIMS) to automate customs procedures, enhance transparency and security, improve data accuracy and consistency, and promote efficiency in cross-border trade. These digital platforms and systems provide functionalities such as electronic submission of trade documents, real-time tracking of shipments, automated customs processes, online payment options, and access to relevant trade regulations and guidelines. They also facilitate seamless collaboration, information sharing, and data exchange between customs authorities, traders, postal operators, and customs laboratories.
Example: Trade Facilitation Portal
An online platform that provides a centralized and user-friendly interface for traders, customs authorities, and other stakeholders to access and exchange trade-related information and services.
Cooperation between Customs laboratories
The implementation of digital platforms and systems to facilitate seamless collaboration, information sharing, and data exchange between customs laboratories.
Cooperation between Customs and Postal Operators
The implementation of digital platforms and systems to facilitate seamless collaboration, information exchange, and data sharing between customs authorities and postal operators.
MS' Customs organization management
The implementation of digital platforms and systems to effectively manage and oversee the operations of customs organizations within a specific country or region.
LOST view: TVA-Customs Trade Facilitation and Collaboration Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/CustomsTradeFacilitationAndCollaborationEnablersGrouping
ABB name: egovera:CustomsTradeFacilitationAndCollaborationEnablersGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-20
dct:identifier: http://data.europa.eu/dr8/egovera/CustomsTradeFacilitationAndCollaborationEnablersGrouping
dct:title: Customs Trade Facilitation And Collaboration Enablers
Definition: Business Agnostic Data Policy Catalogue ABB is a grouping that covers a range of policies and guidelines designed to manage and control data assets within an organization. These policies ensure seamless interoperability between different systems, maintain data quality, govern data usage, and manage data within a blockchain network. The catalogue is business agnostic, meaning it can be applied across various industries and business models.
Source: EIRA Team Research
Additional information: The Business Agnostic Data Policy Catalogue ABB includes four main elements: Interoperability Policy, Data Quality Framework, Data Governance Guidelines, and Blockchain Policy. The Interoperability Policy ensures that different systems and data within an organization or across entities can work together seamlessly. The Data Quality Framework provides a structured approach to assess, measure, and improve data quality. The Data Governance Guidelines provide direction for managing and controlling data assets, ensuring data quality, integrity, privacy, security, and compliance. Lastly, the Blockchain Policy governs the management, access, and utilization of data within a blockchain network, ensuring integrity, immutability, and transparency.
Example: For instance, a healthcare organization can use the Interoperability Policy to ensure that its various systems, such as electronic health records and billing systems, can communicate effectively. The Data Quality Framework can be used to ensure that the data collected from patients is accurate and reliable. The Data Governance Guidelines can help the organization manage its data assets, ensuring privacy and compliance with regulations like HIPAA. The Blockchain Policy can be used if the organization decides to use blockchain technology for secure and transparent data storage and transactions.
LOST view: SV-Governance Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/BusinessAgnosticDataPolicyCatalogueGrouping
ABB name: egovera:BusinessAgnosticDataPolicyCatalogueGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/egovera/BusinessAgnosticDataPolicyCatalogueGrouping
Name: Business Agnostic Data Policy Catalogue Catalogue
Interoperability Layer: Semantic
Definition: Messaging Enablers ABB is a Grouping that refers to components and services that facilitate asynchronous message-based communication between different applications. This is achieved through the use of intermediary software components such as a Message Broker, which acts as a central hub for the publishing and receiving of messages based on specific criteria. The Messaging Enablers ensure reliable delivery of messages, decoupling of applications from each other, and provide features like message routing, transformation, and filtering.
Source: EIRA Team Research
Source reference: N/A
Additional information: Messaging Enablers are crucial in modern software architecture, especially in microservices architecture where different services need to communicate with each other. They provide a way for these services to communicate asynchronously, which means that the sender and receiver do not need to interact with the message queue at the same time. This decoupling allows for greater flexibility and scalability. The Message Broker, a key component of the Messaging Enablers, ensures that messages are delivered reliably, even if the receiver is not available at the time the message is sent. It also provides features like message routing, which directs messages based on their content or other criteria; transformation, which converts messages to a format the receiver can understand; and filtering, which controls which messages a receiver gets based on specific criteria.
Example: An example of Messaging Enablers in use could be an e-commerce platform. When a customer places an order, the order service publishes a message to the message broker. The inventory service, which is subscribed to these types of messages, receives the message and updates the inventory. The shipping service, also subscribed to these messages, receives the message and arranges for the order to be shipped. In this scenario, the Message Broker enables these different services to communicate and coordinate with each other to fulfill the order.
LOST view: TVA-Messaging Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/MessagingEnablersGrouping
ABB name: egovera:MessagingEnablersGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-17
dct:identifier: http://data.europa.eu/dr8/egovera/MessagingEnablersGrouping
dct:title: Messaging EnablersGrouping
Definition: Business Agnostic Ontologies Catalogue Solutions (ABB) is a grouping that covers a range of ontology resources and tools that are applicable across various business domains. The catalogue includes Linked Open Vocabularies (LOV) and Ontology Design Patterns (ODP), both of which are instrumental in ontology engineering and semantic web portal design respectively.
Source: EIRA Team Research
Additional information: The Business Agnostic Ontologies Catalogue Solutions (ABB) is a comprehensive collection of ontology resources that are not specific to any business domain, hence the term 'agnostic'. It includes Linked Open Vocabularies (LOV), a tool used by Ontology Engineers for creating, managing and utilizing ontologies. LOV provides a wide range of vocabularies that can be linked and utilized in various contexts. Another key component of the catalogue is OntologyDesignPatterns.org (ODP), a dedicated portal for ontology design patterns. ODP provides resources and tools for designing and implementing ontologies in a semantic web context. Both LOV and ODP are crucial for ontology engineering and semantic web design, making the catalogue a valuable resource for businesses operating in diverse domains.
Example: For instance, a healthcare organization can use the LOV tool from the Business Agnostic Ontologies Catalogue Solutions to create a medical ontology linking various medical terms and concepts. Similarly, an e-commerce business can use the ODP resources to design a product ontology for their semantic web portal, linking various product categories and attributes.
LOST view: SV-Agnostic Ontology Catalogue
Identifier: http://data.europa.eu/dr8/egovera/BusinessAgnosticOntologiesCatalogueSolutionsGrouping
ABB name: egovera:BusinessAgnosticOntologiesCatalogueSolutionsGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/egovera/BusinessAgnosticOntologiesCatalogueSolutionsGrouping
Name: Business Agnostic Ontologies Catalogue Solutions Catalogue
Interoperability Layer: Semantic
Definition: eProcurement Data Model ABB is a grouping that covers essential elements related to public procurement processes within the European Union. It specifically includes the European Single Procurement Document (ESPD) as a key component, which is a standardized form used in these processes.
Source: EIRA Team Research
Additional information: The eProcurement Data Model ABB is a catalogue of information entities that are crucial for the execution of public procurement processes in the EU. The primary element in this model is the ESPD, a data object that represents a structured document containing vital information about a supplier or contractor. This includes details such as company identification, financial standing, technical and professional abilities, and any legal grounds for exclusion. The ESPD serves as a preliminary self-declaration by suppliers, allowing them to demonstrate their eligibility and suitability to participate in public procurement procedures across EU member states. The eProcurement Data Model ABB, therefore, provides a structured approach to managing and utilizing procurement data, ensuring transparency, efficiency, and compliance with EU regulations.
Example: For instance, a public institution in the EU planning to award a contract for a construction project would use the eProcurement Data Model ABB to manage the procurement process. They would request ESPDs from interested contractors, who would fill out these forms with their company details, financial status, technical capabilities, and any legal issues. The institution could then use the data from these ESPDs, structured according to the eProcurement Data Model ABB, to assess the eligibility and suitability of each contractor for the project.
LOST view: SV-Business Agnostic Data Models
Identifier: http://data.europa.eu/dr8/egovera/EProcurementDataModelGrouping
ABB name: egovera:EProcurementDataModelGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/egovera/EProcurementDataModelGrouping
Name: EProcurement Data Model Catalogue
Interoperability Layer: Semantic
Definition: Usability Requirements Catalogue ABB is a grouping that covers a range of non-functional IT requirements that are crucial for ensuring the usability and accessibility of a system or application. This includes requirements related to accessibility, learnability, and API contracts. Each of these elements plays a key role in ensuring that the system or application is user-friendly, inclusive, and efficient, and that it complies with relevant laws and regulations.
Source: EIRA Team Research
Additional information: The Usability Requirements Catalogue ABB is a comprehensive collection of non-functional requirements that are essential for the development of user-friendly and accessible IT systems and applications. The catalogue includes 'Accessibility', which ensures that the system can be used by people with disabilities or impairments; 'Learnability', which measures how quickly and efficiently users can learn to use the system; and 'API contract', which specifies the rules and guidelines for how an API should behave. By adhering to these requirements, developers can create systems and applications that are inclusive, efficient, and compliant with relevant laws and regulations.
Example: For instance, when developing a new web application, a developer might refer to the Usability Requirements Catalogue ABB to ensure that the application is accessible to users with disabilities. This could involve implementing features such as screen readers, keyboard navigation, and alternative text for images. The developer might also use the catalogue to ensure that the application is easy to learn and use, by creating clear and intuitive interfaces and providing well-organized documentation and help resources. Finally, the developer might refer to the 'API contract' requirement to ensure that the application's API is consistent, predictable, and easy to integrate with other systems.
LOST view: Digital Solution Non-Functional Requirements Catalogue view
Identifier: http://data.europa.eu/dr8/egovera/UsabilityRequirementsCatalogueGrouping
ABB name: egovera:UsabilityRequirementsCatalogueGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-17
dct:identifier: http://data.europa.eu/dr8/egovera/UsabilityRequirementsCatalogueGrouping
dct:title: Usability Requirements Catalogue Catalogue
Definition: Customs Legislation on Structural Interoperability (EBI) ABB is a grouping that covers the legal and regulatory framework for the movement of goods into the customs territory of the European Union. It specifically refers to the Commission Implementing Regulation (EU) 2015/2447 Articles 137, which outlines the rules and procedures for the place where goods are brought into the customs territory of the Union.
Source: EIRA Team Research
Additional information: The Customs Legislation on Structural Interoperability (EBI) ABB is a comprehensive collection of legal provisions and regulations that govern the import and export of goods within the European Union. It is designed to ensure that all member states follow a uniform set of rules and procedures for customs operations, thereby facilitating seamless trade and commerce across borders. The Commission Implementing Regulation (EU) 2015/2447 Articles 137 is a key component of this legislative framework, providing specific guidelines on the place where goods are to be brought into the customs territory of the Union.
Example: For instance, a company importing goods into the European Union would need to adhere to the provisions of the Commission Implementing Regulation (EU) 2015/2447 Articles 137. This would involve bringing the goods into the customs territory of the Union at a designated place, as stipulated by the regulation.
LOST view: LV-Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/CustomsLegislationOnStructuralInteroperabilityGrouping
ABB name: egovera:CustomsLegislationOnStructuralInteroperabilityGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-20
dct:identifier: http://data.europa.eu/dr8/egovera/CustomsLegislationOnStructuralInteroperabilityGrouping
dct:title: Customs Legislation On Structural Interoperability (EBI)
Definition: Information Architect Concerns ABB is a Grouping that covers the processes an information architect should follow, and the relation/influence of process related with other roles' processes, to read/assess/understand an eGovERA model. It includes elements such as 'Semantic view' and 'Organisational view'.
Source: EIRA Team Research
Additional information: The Information Architect Concerns ABB is a crucial component in the eGovERA model, providing a structured approach for information architects to understand and assess the model. It includes elements like 'Semantic view', which refers to the process of understanding the meaning and interpretation of the information in the model, and 'Organisational view', which refers to the process of understanding the organizational structure and roles in the model. These elements help the information architect to understand the model from different perspectives and to ensure that the model is accurately interpreted and implemented.
Example: For instance, an information architect might start by examining the 'Semantic view' to understand the meaning of the information in the eGovERA model. They might then move on to the 'Organisational view' to understand how the roles and responsibilities are distributed in the model. This comprehensive approach ensures that the architect has a thorough understanding of the model and can effectively guide its implementation.
LOST view: [A] How to read the model
Identifier: http://data.europa.eu/dr8/egovera/InformationArchitectConcernsGrouping
ABB name: egovera:InformationArchitectConcernsGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-18
dct:identifier: http://data.europa.eu/dr8/egovera/InformationArchitectConcernsGrouping
dct:title: Information Architect Concerns Catalogue
Definition: European Non-Binding Instruments (ENBI) is a grouping that covers a range of legislative documents and recommendations that aim to guide and influence the development and implementation of interoperability in various sectors across Europe. These instruments, while not legally binding, provide a framework for cooperation and coordination among European institutions, member states, and other stakeholders.
Source: EIRA Team Research
Additional information: The ENBI catalogue is divided into three main categories: Governance, Structural, and Behavioural Interoperability. The Governance Interoperability category includes instruments such as the Commission Recommendation 87/598/EEC and Regulation (EU) 2021/694. The Structural Interoperability category includes instruments like the European Interoperability Framework - Implementation Strategy COM/2017/0134 final and the Strengthened Code of Practice on Disinformation. The Behavioural Interoperability category, while currently empty, is intended to house future instruments related to the behavioural aspects of interoperability. These instruments provide guidance on a wide range of issues, from electronic payments and digital programs to disinformation and digital identity frameworks.
Example: Commission Recommendation 87/598/EEC of 8 December 1987
This recommendation provides a code of conduct for electronic payments, outlining the relationships between financial institutions, traders, service establishments, and consumers.
Regulation (EU) 2021/694 of the European Parliament and of the Council of 29 April 2021
This regulation establishes the Digital Europe Programme and repeals Decision (EU) 2015/2240. It is relevant to the European Economic Area.
European Interoperability Framework - Implementation Strategy COM/2017/0134 final
This communication from the Commission outlines the implementation strategy for the European Interoperability Framework.
Strengthened Code of Practice on Disinformation
This 2022 code of practice provides strengthened guidelines for tackling disinformation.
LOST view: LV-Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/EuropeanNon-BindingInstrumentsGrouping
ABB name: egovera:EuropeanNon-BindingInstrumentsGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-17
dct:identifier: http://data.europa.eu/dr8/egovera/EuropeanNon-BindingInstrumentsGrouping
dct:title: European Non-Binding Instruments Catalogue
Definition: Customs Legislation on Governance Interoperability (EBI) is a grouping that covers various regulations and directives issued by the European Union. These regulations pertain to mutual recognition of protection measures in civil matters, the Union Customs Code, and market surveillance and compliance of products.
Source: EIRA Team Research
Additional information: The Customs Legislation on Governance Interoperability (EBI) includes key regulations such as Regulation (EU) No 606/2013, which deals with mutual recognition of protection measures in civil matters. It also includes Regulation (EU) No 952/2013, which lays down the Union Customs Code. Another important regulation in this grouping is Regulation (EU) 2019/1020, which pertains to market surveillance and compliance of products. These regulations are crucial for ensuring smooth and compliant trade within the European Union.
Example: Regulation (EU) No 606/2013 of the European Parliament and of the Council of 12 June 2013 on mutual recognition of protection measures in civil matters
This regulation ensures that protection measures taken in one EU country are recognized and maintained in any other EU countries to which a person moves or travels.
Regulation (EU) No 952/2013 of the European Parliament and of the Council of 9 October 2013 laying down the Union Customs Code
This regulation provides a framework for customs rules and procedures in the EU customs territory, adapted to modern trade realities and modern communication tools.
Regulation (EU) 2019/1020 on market surveillance and compliance of products Article 4
This regulation outlines the tasks of economic operators regarding products subject to certain Union harmonisation legislation.
LOST view: LV-Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/CustomsLegislationOnGovernanceInteroperabilityGrouping
ABB name: egovera:CustomsLegislationOnGovernanceInteroperabilityGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-20
dct:identifier: http://data.europa.eu/dr8/egovera/CustomsLegislationOnGovernanceInteroperabilityGrouping
dct:title: Customs Legislation On Governance Interoperability (EBI)
Definition: Customs Legislation on Structural Interoperability (ENBI) ABB is a grouping that covers the legal, technical, and procedural elements that facilitate the exchange of information and data between different customs systems. It includes the laws, regulations, standards, and protocols that ensure seamless communication and data exchange between disparate customs systems, thereby promoting efficient customs operations and compliance with international trade laws.
Source: EIRA Team Research
Additional information: The ENBI ABB is crucial in the context of international trade as it ensures that different customs systems can effectively communicate and exchange data. This is particularly important given the increasing digitalization of customs operations and the growing complexity of international trade laws. The ENBI ABB covers a wide range of elements, including legal provisions that govern data exchange between customs systems, technical standards that ensure the compatibility of different systems, and procedural guidelines that facilitate efficient data exchange. By promoting structural interoperability, the ENBI ABB contributes to the overall efficiency and effectiveness of customs operations.
Example: An example of application of the ENBI ABB could be the implementation of a new data exchange protocol between two countries' customs systems. This would involve not only the technical aspects of establishing the data link, but also the legal and procedural elements, such as ensuring compliance with data protection laws and establishing procedures for data verification and validation.
LOST view: LV-Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/CustomsLegislationOnStructuralInteroperabilityGrouping
ABB name: egovera:CustomsLegislationOnStructuralInteroperabilityGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-20
dct:identifier: http://data.europa.eu/dr8/egovera/CustomsLegislationOnStructuralInteroperabilityGrouping
dct:title: Customs Legislation On Structural Interoperability (ENBI)
Definition: Legislation on Governance Interoperability (EBI) is a grouping that covers a range of directives and regulations enacted by the European Parliament and Council. These legislative instruments aim to harmonize and modernize various sectors including electronic communications, digital content and services, public procurement, insurance distribution, payment services, cross-border parcel delivery services, cross-border payments, geo-blocking, and electronic commerce within the European Union (EU). The purpose of these legislations is to promote transparency, competition, innovation, consumer protection, and fair trade practices across the EU's internal market.
Source: EIRA Team Research
Additional information: The EBI catalogue includes various directives and regulations that govern different sectors within the EU. These legislative instruments have been enacted with the aim of harmonizing rules and regulations across member states, promoting competition and innovation, protecting consumer rights, and ensuring fair trade practices. They cover a wide range of areas including electronic communications, digital content and services, public procurement, insurance distribution, payment services, cross-border parcel delivery services, cross-border payments, geo-blocking, and electronic commerce. Each legislation has specific objectives and requirements that must be adhered to by the relevant stakeholders.
Example: For instance, Directive (EU) 2018/1972, also known as the European Electronic Communications Code, modernizes and harmonizes the regulatory framework for electronic communications across the EU. On the other hand, Directive (EU) 2019/770 focuses on contracts for the provision of digital content and digital services, aiming to strengthen consumer rights in the digital market. Similarly, Regulation (EU) 2018/302, known as the Geo-blocking Regulation, addresses unjustified geo-blocking and other forms of discrimination based on customers' nationality or location within the internal market.
LOST view: LV-Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/LegislationOnGovernanceInteroperabilityGrouping
ABB name: egovera:LegislationOnGovernanceInteroperabilityGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-20
dct:identifier: http://data.europa.eu/dr8/egovera/LegislationOnGovernanceInteroperabilityGrouping
dct:title: Legislation On Governance Interoperability (EBI) Catalogue
Description: Messaging Solutions ABB is a grouping that refers to actual solutions that facilitate the exchange of information through digital messages. These solutions can include email, SMS, instant messaging, push notifications, and other forms of digital communication. They are designed to streamline and simplify the process of sending, receiving, and managing messages in a digital environment.
Additional information: Messaging solutions are an integral part of modern communication, especially in business environments. They can be used for a variety of purposes, including customer service, marketing, internal communication, and more. These solutions often include features like automation, personalization, analytics, and integration with other systems. They can be used to send messages to individuals or groups, and can support various types of content, including text, images, videos, and links. Messaging solutions can also include security features to protect the privacy and integrity of the messages.
Example: Examples of messaging solutions include email marketing platforms like MailChimp, customer service chatbots, internal communication tools like Slack, and SMS marketing services. These solutions can be used in a variety of contexts. For example, a business might use an email marketing platform to send promotional messages to customers, a chatbot to answer customer inquiries, and an internal communication tool to facilitate communication among employees.
Publisher: EIRA Team Research
LOST view: TVA-Messaging Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/BusinessAgnosticMessagingSolutionsGrouping
EIRA traceability: eira:DigitalSolutionApplicationService
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-08-20
dct:identifier: http://data.europa.eu/dr8/egovera/BusinessAgnosticMessagingSolutionsGrouping
dct:title: Messaging SolutionsGrouping
Definition: API Enablers ABB is a Grouping that refers to components and frameworks that support the implementation and cataloguing of (open) software interfaces
Source: European Comission
Source reference: https://digital-strategy.ec.europa.eu/en/library/apis-enablers-digital-transformation-governments
Interoperability Dimension: Structural IoP
LOST view: Technical view - application
Interoperability Saliency: The API Enablers Grouping ABB is salient for technical interoperability because this grouping composition of the different technologies that can implement software interfaces used to consume and provide data from public services. Implementing those technologies can enable interoperability throughout public services.
Identifier: http://data.europa.eu/dr8/APIEnablersGrouping
ABB name: eira:APIEnablersGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/APIEnablersGrouping
Interoperability Layer: TechnicalApplication
Description: Bussiness Agnostic Identity Management Solutions (BAIMS) is a grouping that refers to actual solutions that facilitate the management of user identities across various business models and industries. These solutions are designed to be flexible and adaptable, allowing businesses of any type or size to effectively manage user access, authentication, and security.
Additional information: BAIMS are crucial in today's digital age where security and privacy are of utmost importance. They provide a comprehensive approach to managing the identities of users in an organization, regardless of the nature of the business. They are designed to handle tasks such as user authentication, authorization, roles and access management, password management, policy enforcement, and audit and reporting. These solutions are not tied to a specific business model or industry, making them versatile and adaptable. They can be integrated with various systems and platforms, providing a seamless user experience while ensuring security and compliance.
Example: Examples of application of BAIMS include: 1) In a healthcare setting, these solutions can be used to manage the identities of doctors, nurses, and patients, ensuring that only authorized individuals have access to sensitive patient data. 2) In a retail business, they can be used to manage the identities of customers and employees, facilitating secure transactions and protecting customer information. 3) In a financial institution, they can be used to manage the identities of account holders and employees, ensuring secure access to financial data and systems.
Publisher: EIRA Team Research
LOST view: TVA-Identification and Access Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/BusinessAgnosticIdentityManagementSolutionsGrouping
EIRA traceability: eira:DigitalSolutionApplicationService
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-08-20
dct:identifier: http://data.europa.eu/dr8/egovera/BusinessAgnosticIdentityManagementSolutionsGrouping
dct:title: Bussiness Agnostic Identity Management SolutionsGrouping
Definition: Legislation on Behavioural Interoperability (NBI) is a grouping that covers a set of laws, regulations, and guidelines aimed at ensuring the seamless interaction of different systems, applications, and services. It focuses on the behavior of systems when they interact, ensuring that they operate together effectively and efficiently. The NBI legislation is designed to facilitate the exchange of information and services among different systems, promoting interoperability and integration.
Source: EIRA Team Research
Additional information: The Legislation on Behavioural Interoperability (NBI) is an important aspect of information technology and telecommunications. It is concerned with the ability of different systems, applications, and services to work together seamlessly. This involves not only the technical aspects of interoperability but also the legal and regulatory aspects. The NBI legislation provides a framework for ensuring that systems behave in a predictable and consistent manner when they interact, facilitating the exchange of information and services. It covers a wide range of areas, including data exchange standards, communication protocols, interface specifications, and service level agreements.
Example: An example of the application of the Legislation on Behavioural Interoperability (NBI) is in the healthcare sector. Here, different systems such as electronic health records, hospital information systems, and telemedicine applications need to interact seamlessly to provide effective and efficient healthcare services. The NBI legislation ensures that these systems can exchange information and services in a predictable and consistent manner, promoting interoperability and integration.
LOST view: LV-Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/LegislationOnBehaviouralInteroperabilityGrouping
ABB name: egovera:LegislationOnBehaviouralInteroperabilityGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-20
dct:identifier: http://data.europa.eu/dr8/egovera/LegislationOnBehaviouralInteroperabilityGrouping
dct:title: Legislation On Behavioural Interoperability (NBI) Catalogue
Definition: Customs Reference Data is a grouping that covers a comprehensive set of elements related to customs procedures and regulations. It includes information on customs offices, product classification codes, country codes, currency codes, units of measure, legal references, and customs valuation methods. These elements are essential for ensuring compliance with customs requirements and procedures, facilitating international trade, and enabling unambiguous electronic communication of quantities together with their units.
Source: EIRA Team Research
Additional information: The Customs Reference Data catalogue includes elements such as the Reference Data Customs Offices List, which provides information on the Reference Data (RD) and the Customs Office List (COL) used by national customs applications. It also includes the Harmonized System (HS) Codes, an internationally standardized system for classifying products and goods. The ISO Country Codes, which are internationally recognized codes that designate every country and most of the dependent areas, are also part of this catalogue. The catalogue also includes the Currency Code List, the Unified Code for Units of Measure (UCUM), Legal and Regulatory References, and Customs Valuation Methods.
Example: For instance, the Harmonized System (HS) Codes are used to determine the customs duties, taxes, and regulations applicable to specific products during import or export. Similarly, the ISO Country Codes are used in top-level domains on the Internet and at international events. The Currency Code List is used to list concepts associated with currencies and currency subunits, while the Unified Code for Units of Measure (UCUM) is used to facilitate unambiguous electronic communication of quantities together with their units.
LOST view: SV-Reference Data [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/CustomsReferenceDataGrouping
ABB name: egovera:CustomsReferenceDataGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-20
dct:identifier: http://data.europa.eu/dr8/egovera/CustomsReferenceDataGrouping
dct:title: Customs Reference Data
Narrative:
The "Semantic view - Business Agnostic Datasets" viewpoint extends organizational view and provides a comprehensive framework for managing and utilizing business agnostic datasets within the digital ecosystem. This view associates the Agnostic Datasets with the Business Information Base and Digital Public Services from the application layer.
Within this view, Agnostic Datasets represent standardized collections of data that are independent of specific business domains. These datasets adhere to common data structures, formats, and semantics, enabling interoperability, data integration, and efficient data exchange across different digital services and applications.
The Business Information Base, as part of the application layer, serves as a repository of business-related information that utilizes the Agnostic Datasets. It stores and manages domain-specific data within the standardized dataset structures, facilitating data consistency, accessibility, and sharing.
Digital Public Services leverage the Agnostic Datasets to ensure uniformity and coherence in data representation and utilization. These services align their data models, operations, and interactions with the agnostic datasets, enabling seamless integration, data consistency, and semantic interoperability among different digital public services.
By associating the Agnostic Datasets with the Business Information Base and Digital Public Services, the "Semantic view - Business Agnostic Datasets" promotes standardized data management practices and efficient data utilization within the digital ecosystem. This view supports data integration, semantic interoperability, and advanced functionalities for digital public services.
The agnostic nature of the datasets allows for flexibility and adaptability across different business domains and digital public services. It enables reusability of data structures, reduces data duplication, and promotes consistent data representation and exchange.
Definition: NARRATIVE:The 'Business Agnostic Metadata Catalogue' in ArchiMate is a grouping that organizes various elements based on their concerns or responsibilities. In the provided JSON, there are three main elements: [JRC Data Catalogue], [SV-Metadata Catalogue], and [Smart Data Models]. 1. [JRC Data Catalogue]: This is a Data Object SBB type element. It represents the Joint Research Center (JRC) Data Catalogue, which is a collection of metadata records providing information about datasets produced by the JRC. The JRC, as the European Commission's in-house science service, conducts research to provide independent scientific advice and support to the policies of the European Union. This element does not contain any sub-elements.2. [SV-Metadata Catalogue]: This is an Archimate Diagram-model ABB type element. The description is not provided in the JSON, but based on its type, it can be inferred that this element represents a metadata catalogue in the form of an ArchiMate diagram model. This element also does not contain any sub-elements.3. [Smart Data Models]: This is another Data Object SBB type element. It represents a smart data model, which includes three elements: the schema (technical representation of the model defining the technical data types and structure), the specification (a written document for human readers), and the examples of the payloads for NGSIv2 and NGSI-LD versions. This element also does not contain any sub-elements.In the context of ArchiMate's grouping, these elements are catalogued in the 'Business Agnostic Metadata Catalogue' based on their responsibilities or concerns, which revolve around data and metadata management, research, and policy support.
Source: EIRA Team Research
Additional information: The BAMS catalogue includes the JRC Data Catalogue, a collection of metadata records detailing datasets produced by the Joint Research Centre (JRC) in line with its Data Policy. The JRC, the European Commission's in-house science service, conducts research to provide independent scientific advice and support to EU policies. Another key element in the catalogue is Smart Data Models. These models include a schema (technical representation of the model defining the technical data types and structure), a specification (written document for human readers), and examples of the payloads for NGSIv2 and NGSI-LD versions. These models are 'smart' because they are designed to be easily understood and used by both humans and machines, facilitating more effective data management and utilization.
Example: An example of the application of the JRC Data Catalogue could be a research institution using the catalogue to access and utilize JRC's datasets for a study on EU policy impact. Similarly, a tech company could use the Smart Data Models in the development of a new software product, leveraging the models to ensure that their data is structured and managed in a standardized, efficient manner.
LOST view: SV-Metadata Catalogue
Identifier: http://data.europa.eu/dr8/egovera/BusinessAgnosticMetadataCatalogueSolutionsGrouping
ABB name: egovera:BusinessAgnosticMetadataCatalogueSolutionsGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/egovera/BusinessAgnosticMetadataCatalogueSolutionsGrouping
Name: Business Agnostic Metadata Solutions Catalogue
Interoperability Layer: Semantic
Definition: Data Analytics Enablers ABB is a Grouping that refers to components and services that serve any current or future Digital Service Infrastructure (DSI) requiring data analysis capabilities.
Source: Inspired in Data Act
Source reference: https://digital-strategy.ec.europa.eu/en/policies/data-act
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): Microsoft Power BI - Power BI is a business analytics service by Microsoft. It aims to provide interactive visualizations and business intelligence capabilities with an interface simple enough for end users to create their own reports and dashboards. It is part of the Microsoft Power Platform.(https://powerbi.microsoft.com/it-it/what-is-power-bi/)
Interoperability Dimension: Structural IoP
LOST view: Technical view - application
Interoperability Saliency: The Analytics Enablers Grouping ABB is salient for technical Interoperability because it comprises tools and services that serve to digital service infrastructure of current or future digital services.
Identifier: http://data.europa.eu/dr8/AnalyticsEnablersGrouping
ABB name: eira:AnalyticsEnablersGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/AnalyticsEnablersGrouping
Interoperability Layer: TechnicalApplication
Definition: Customs Legislation on Behavioural Interoperability (ENBI) ABB is a grouping that covers the set of rules, regulations, and standards that govern the interaction of different systems and processes in the customs domain. It aims to ensure seamless and efficient communication and data exchange between various customs systems and stakeholders.
Source: EIRA Team Research
Additional information: The ENBI catalogue is designed to facilitate the interoperability of customs systems at a behavioural level. It encompasses all the legislative elements that dictate how these systems should interact, communicate, and exchange data. This includes, but is not limited to, laws, regulations, standards, and guidelines. The purpose of this catalogue is to ensure that all customs systems, regardless of their individual characteristics or the country in which they operate, can work together seamlessly and efficiently. This is crucial for facilitating international trade, preventing customs fraud, and ensuring the security of international supply chains.
Example: Examples of application for the ENBI catalogue could include the standardization of data formats for customs declarations, the development of common protocols for the exchange of customs data between different countries, or the establishment of guidelines for the integration of new technologies into existing customs systems.
LOST view: LV-Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/CustomsLegislationOnBehaviouralInteroperabilityGrouping
ABB name: egovera:CustomsLegislationOnBehaviouralInteroperabilityGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-20
dct:identifier: http://data.europa.eu/dr8/egovera/CustomsLegislationOnBehaviouralInteroperabilityGrouping
dct:title: Customs Legislation On Behavioural Interoperability (ENBI)
Definition: Data Space Policies and Contracts ABB is a grouping that covers two primary elements: Data Policy and Data Contract. These elements are integral to the management and governance of data within an organization or system, outlining the rules, regulations, and agreements that dictate how data is handled, shared, and used.
Source: EIRA Team Research
Additional information: The Data Policy element within this grouping refers to the set of rules and guidelines established by an organization or system to manage its data, ensuring its quality, accessibility, and protection. This includes policies on data collection, storage, processing, distribution, and disposal. On the other hand, the Data Contract element refers to the formal agreement between parties on the terms and conditions of data sharing and usage. This includes the rights and responsibilities of each party, the scope of data to be shared, the purpose of data sharing, and the measures for data security and privacy. Together, these elements form the foundation of a robust data governance framework, enabling organizations to effectively manage their data assets while ensuring compliance with relevant laws and regulations.
Example: An example of a Data Policy could be a company's policy on data privacy, which outlines the measures it takes to protect the personal data of its customers, such as encryption and anonymization techniques. An example of a Data Contract could be an agreement between a healthcare provider and a research institution, where the provider agrees to share patient data for research purposes, under the condition that the data is de-identified to protect patient privacy.
LOST view: SV-Agnostic Data Policies and Contracts- Data Space
Identifier: http://data.europa.eu/dr8/egovera/DataSpacePoliciesAndContractsGrouping
ABB name: egovera:DataSpacePoliciesAndContractsGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-17
dct:identifier: http://data.europa.eu/dr8/egovera/DataSpacePoliciesAndContractsGrouping
dct:title: Data Space Policies And Contracts Catalogue
Definition: Test Enablers ABB is a Grouping that refers to the applications and services that support the development and deployment of conformance testing and validation.
Source: Inspired in European Comision
Source reference: https://digital-strategy.ec.europa.eu/en/faqs/testing-and-experimentation-facilities-tefs-questions-and-answers
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): Interoperability Testbed - The Test Bed allows users to execute predefined test cases on their systems in order to test the conformance to standards and requirements, simulate a web-service, validate content and test a complete message exchange protocol. The Testbed manages test cases and users, and orchestrates domain-specific components, the domain-specific logic is in separate components that are used via web services. Test results are provided in a standardised, machine-readable format. The Test Bed also offers a test registry and repository (TRR) to store test artefacts (assertions, test cases, validation schemas, etc.) and compile test services (validation services, simulator services, etc.). Please visit the following website for more information: https://ec.europa.eu/isa2/solutions/interoperability-test-bed_en
Interoperability Dimension: Governance IoP
LOST view: Technical view - application
Interoperability Saliency: The Test Enablers Grouping ABB is salient for interoperability because testing and validation solutions services are relevant aspects to ensure that they are conformant to relevant standards enabling interoperability.
Identifier: http://data.europa.eu/dr8/TestEnablersGrouping
ABB name: eira:TestEnablersGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/TestEnablersGrouping
Interoperability Layer: TechnicalApplication
Definition: Business Agnostic Digital Business Capabilities Catalogue ABB is a Grouping that refers to the actual catalogue of digital business capabilities (DBC) that puts together a range of capabilities related to various digital business operations. These capabilities are crucial for organizations to effectively and efficiently manage their digital operations, gain valuable insights, make informed decisions, ensure data quality, security, and compliance, and generate value and revenue.
Source: EIRA Team Research
Additional information: The catalogue includes a wide range of capabilities such as Electronic Identification, Qualification Management, Digital Payments, Digital Procurement, Digital Communication, Digital Exchange, Digital Invoicing, Data Management, Multimedia Management, Contact Management, Case and Workflow Management, Knowledge Management, Digital Twin, Artificial Intelligence, and Business Agnostic Data Management Digital Business Capability Catalogue. Each of these capabilities has a specific role and function in the digital business operations of an organization. For instance, Electronic Identification ensures secure access to online services, Digital Payments enables the purchase of goods or services via digital modes, and Data Management is responsible for the development, execution, and supervision of plans, policies, programs, and practices that deliver, control, protect, and enhance the value of data and information assets throughout their lifecycles.
Example: An example of the application of these capabilities can be seen in a digital business operation where Electronic Identification is used to ensure secure access to online services, Digital Payments are used to facilitate the purchase of goods or services, Digital Communication is used for virtual collaboration, and Data Management is used to manage and enhance the value of data and information assets. Similarly, in the Business Agnostic Data Management Digital Business Capability Catalogue, capabilities such as Data Discovery, Data Analytics, Data Monetization, Data Governance, Data Ethics, Data Interoperability, Data Sharing, Data Quality, Data Security, and Data Lineage are used to effectively and efficiently manage data assets, gain valuable insights, make informed decisions, ensure data quality, security, and compliance, and generate value and revenue.
LOST view: OV-Data Spaces
Identifier: http://data.europa.eu/dr8/egovera/BusinessAgnosticDigitalBusinessCapabilitiesCatalogueGrouping
EIRA traceability: eira:DigitalBusinessCapability
ABB name: egovera:BusinessAgnosticDigitalBusinessCapabilitiesCatalogueGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-17
dct:identifier: http://data.europa.eu/dr8/egovera/BusinessAgnosticDigitalBusinessCapabilitiesCatalogueGrouping
dct:title: Business Agnostic Digital Business Capabilities Catalogue
Definition: Business Agnostic Business Information Base (ABB) is a grouping that refers to the actual catalogue of information entities that covers a wide range of business-related elements. These elements include payments, transactions, identification, qualifications, audit trails, access rights, profiles, messages, availability, digital signatures, documents, security measures, locations, invoices, contracting authorities, economic operators, digital assets, credentials, data quality, and distribution lists.
Source: EIRA Team Research
Additional information: The Business Agnostic Business Information Base (ABB) is a comprehensive catalogue of information entities that are applicable across various business domains. It includes elements such as 'Payment' which refers to the voluntary tendering of money or its equivalent, 'Transaction' which is an interaction of individuals/entities with outside entities, 'Identification' which is data that could potentially be used to identify a particular person or entity, and 'Qualification' which is something that could potentially be used to qualify a particular person or entity. Other elements like 'Audit trail', 'Access rights', 'Profile', 'Message', 'Availability', 'Digital Signature', 'Document', 'Security Measure', 'Location', 'Invoice', 'Contracting authority', 'Economic operator', 'Digital Asset', 'Credential', 'Data Quality', and 'Distribution list' are also part of this catalogue, each with its own specific definition and purpose.
Example: For instance, in a financial institution, the 'Payment' element would refer to the transactions made by customers, 'Identification' would refer to the customer's personal information, 'Access rights' would determine what information a customer or employee can view, 'Digital Signature' would be used to verify the authenticity of digital messages or documents, and 'Data Quality' would refer to the state of qualitative or quantitative pieces of information within the institution.
LOST view: OV-Functional Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/BusinessAgnosticBusinessInformationBaseGrouping
ABB name: egovera:BusinessAgnosticBusinessInformationBaseGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/egovera/BusinessAgnosticBusinessInformationBaseGrouping
Name: Business Agnostic Business Information Base Catalogue
Interoperability Layer: Organisational
Specialises: http://data.europa.eu/dr8/InformationBusinessObject
Definition: Containers Infrastructure Enabler ABB is a Grouping of components and services enabling a virtual packaging code and isolated applications for deployment of public services.
Source: Inspired in referent cloud service providers
Source reference:
Synonym:
Additional information:
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): OpenSHIFT is a secure and an enterprise-grade cloud-based container orchestration system with Kubernetes at the backend. It can be used both as a Red Hat Container Orchestration Engine and Platform-as-a-Service (PaaS). https://github.com/openshift/origin
Interoperability Dimension: Structural IoP
LOST view: Technical view - infrastructure
Interoperability Saliency: Containers Infrastructure Enablers ABB is salient for organizational interoperability due to setting up the rules and business process to establish and manage the virtual tools that permit determining the functionality of the public digital services.
Identifier: http://data.europa.eu/dr8/ContainersInfrastructureEnablersGrouping
ABB name: eira:ContainersInfrastructureEnablersGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/ContainersInfrastructureEnablersGrouping
Interoperability Layer: TechnicalInfrastructure
Definition: Customs Risk Management and Analysis Enablers ABB is a Grouping that covers digital solutions and methodologies used in the systematic assessment and evaluation of potential risks associated with trade transactions and customs operations. It involves the use of data analytics, algorithms, and risk management methodologies to identify patterns, anomalies, and potential risks in real-time.
Source: EIRA Team Research
Additional information: The elements within this grouping are designed to enhance the efficiency of customs authorities by enabling them to prioritize inspections, allocate resources effectively, and mitigate risks related to smuggling, fraud, security threats, and non-compliance. They leverage factors such as shipment details, trader profiles, country of origin, and historical data to provide a comprehensive risk analysis. This supports informed decision-making and ensures effective risk management within the customs domain.
Example: Risk analysis
Risk analysis is a key element within the Customs Risk Management and Analysis Enablers grouping. It refers to the systematic assessment and evaluation of potential risks associated with trade transactions and customs operations. By analyzing factors such as shipment details, trader profiles, country of origin, and historical data, risk analysis enables customs authorities to prioritize inspections, allocate resources effectively, and mitigate risks related to smuggling, fraud, security threats, and non-compliance. This digital solution service enhances customs efficiency, facilitates secure trade, and supports informed decision-making to ensure effective risk management within the customs domain.
LOST view: TVA-Customs Risk Analysis Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/CustomsRiskManagementAndAnalysisEnablersGrouping
ABB name: egovera:CustomsRiskManagementAndAnalysisEnablersGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-20
dct:identifier: http://data.europa.eu/dr8/egovera/CustomsRiskManagementAndAnalysisEnablersGrouping
dct:title: Customs Risk Management And Analysis Enablers
Definition: Shared Legal Content ABB is a Grouping setting legal (re)usable resources with convergence power, to public policy goals attainment, enabling to reuse and share legislations cross-legal jurisdictions through exchange of data, information, and knowledge.
Source: EUR-LEX
Source reference: (https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32021R0695&qid=1646736486403)
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/SharedLegalContentGrouping
LOST view: Legal view
EIRA concept: eira:ArchitectureBuildingBlock
ABB name: eira:SharedLegalContentGrouping
Synonym: ABC
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): The past years have seen an extraordinary proliferation of sharing economy platforms, and the largest platforms have fast become global enterprises with market capitalisations that exceed competitors with “traditional” business concepts. These developments call into question a number of regulatory matters and pose new questions for national and European-level regulators. (https://www.intereconomics.eu/contents/year/2017/number/1/article/regulating-the-european-sharing-economy-state-of-play-and-challenges.html).
Interoperability Saliency: The Shared Legal Content ABB is a key interoperability enabler (*) for governance, behavioural and structural interoperability because it supports to achieve of it with public policy goals convergence value by enabling i) sharing/provisioning/reusing/consumption of legislation on digital public services, ii) the exchange of data, information, and knowledge between digital public services, and iii) collaboration between digital public services.
Additional information: The degree of achievement could range from an ideal perfect shared legal framework (i.e. no interoperability barriers from the legal perspective) to an imperfect or even null shared legal framework (i.e. some interoperability barriers from the legal perspective). The level of legal interoperability will constrain digital public services cross-legal jurisdictions.
Interoperability Dimension: Structural IoP
Viewpoint: Highlevel viewpoint
Additional identifier: http://data.europa.eu/dr8/SharedLegalContentGrouping
EIF Layer: Legal
Definition: Interoperability Non-Functional Requirements Catalogue ABB is a Grouping of technical specifications and capabilities that enable different systems, applications, or devices to exchange information and work together seamlessly
Source: EIRA Team Research
Additional information: The Digital Solution Non-Functional Requirements Catalogue ABB includes various elements such as Extensibility, Observability, Security, Agility, Resiliency, Consistency, Scalability, Availability, Usability, and Durability. Each of these elements has a specific role and importance in the overall system design and operation. For instance, Extensibility refers to the system's ability to accommodate future changes or additions seamlessly, while Observability refers to the system's ability to monitor and analyze its behavior in real-time. Similarly, Security refers to the system's ability to protect itself against unauthorized access and data breaches, while Agility refers to the system's ability to adapt quickly to changing business needs or market conditions. The catalogue also includes various sub-elements under each main element, providing a comprehensive list of non-functional requirements for digital solutions.
Example: An example of applying the Digital Solution Non-Functional Requirements Catalogue ABB could be during the design and development of a new digital banking application. The developers would need to consider various non-functional requirements such as Security (to protect users' financial information), Availability (to ensure the app is always accessible), Usability (to ensure the app is user-friendly), Scalability (to handle increasing number of users), and Extensibility (to easily add new features in the future). Additionally, they would also need to consider sub-elements such as Confidentiality and Integrity under Security, Accessibility and Learnability under Usability, and Disaster Recovery and Recoverability under Resiliency.
LOST view: Digital Solution Non-Functional Requirements Catalogue view
Identifier: http://data.europa.eu/dr8/egovera/DigitalSolutionNon-FunctionalRequirementsCatalogueGrouping
ABB name: egovera:DigitalSolutionNon-FunctionalRequirementsCatalogueGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-17
dct:identifier: http://data.europa.eu/dr8/egovera/DigitalSolutionNon-FunctionalRequirementsCatalogueGrouping
dct:title: Digital Solution Non-Functional Requirements Catalogue Catalogue
Definition: Privacy Data Policy Catalogue ABB is a grouping that covers a range of policies and guidelines implemented by an organization to ensure the privacy and protection of personal data. The catalogue includes elements such as the Anonymisation Policy, which outlines the rules and procedures for anonymizing sensitive data in compliance with privacy regulations.
Source: EIRA Team Research
Additional information: The Privacy Data Policy Catalogue ABB is a comprehensive collection of policies and guidelines that an organization uses to safeguard personal data. It includes elements like the Anonymisation Policy, which is a formal document outlining the methods, techniques, and criteria used to transform personally identifiable information (PII) into a form that can no longer be linked to an individual. This policy ensures compliance with privacy regulations and helps mitigate the risk of unauthorized disclosure or misuse of personal data. It includes considerations for data anonymization processes, such as data masking, aggregation, or encryption, to protect individuals' privacy while still allowing data to be used for legitimate business purposes.
Example: An example of an element in the Privacy Data Policy Catalogue ABB is the Anonymisation Policy. This policy could state that all customer data used for internal analytics must first be anonymized through a process of data masking. This would involve replacing identifiable data fields with artificial identifiers or pseudonyms to prevent the identification of individuals. The policy might also specify the use of encryption for data storage and transmission to further protect personal data from unauthorized access or disclosure.
LOST view: SV-Governance Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/PrivacyDataPolicyCatalogueGrouping
ABB name: egovera:PrivacyDataPolicyCatalogueGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/egovera/PrivacyDataPolicyCatalogueGrouping
Name: Privacy Data Policy Catalogue Catalogue
Interoperability Layer: Semantic
Definition: Customs Data Format, Representation and Syntax Solutions ABB is a grouping that covers the specific formats and syntax solutions used for customs declarations. This includes the structures and fields used to capture information about import or export shipments, such as details about goods, their classification, valuation, origin, and other customs-related information.
Source: EIRA Team Research
Additional information: The Customs Data Format, Representation and Syntax Solutions ABB is a comprehensive catalogue of elements that are used in the customs declaration process. These elements are designed to standardize the way information is captured and represented, ensuring that all necessary details are accurately and consistently recorded. This includes information about the goods being imported or exported, their classification according to customs regulations, their valuation, their origin, and any other information that may be relevant to the customs process. The elements in this catalogue are used in various customs declaration formats, including the EDIFACT CUSDEC format.
Example: [object Object]
LOST view: SV-Customs Data Representation [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/CustomsDataFormatRepresentationAndSyntaxSolutionsGrouping
ABB name: egovera:CustomsDataFormatRepresentationAndSyntaxSolutionsGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-20
dct:identifier: http://data.europa.eu/dr8/egovera/CustomsDataFormatRepresentationAndSyntaxSolutionsGrouping
dct:title: Customs Data Format, Representation And Syntax Solutions
Definition: Agility Requirements Catalogue ABB is a grouping that covers a set of IT non-functional requirements that contribute to the agility of a software or system. These requirements, including configurability, compatibility, maintainability, and deployability, are crucial for ensuring that the system can adapt to changing needs and environments, can function seamlessly with other systems, can be easily modified and maintained, and can be efficiently deployed and installed.
Source: EIRA Team Research
Additional information: The Agility Requirements Catalogue ABB comprises of four key elements: Configurability, Compatibility, Maintainability, and Deployability. Configurability refers to the system's ability to be easily customized or modified to meet specific needs, without requiring extensive programming knowledge. Compatibility ensures that the system can function properly with other systems, hardware, or environments, and can be easily upgraded or migrated. Maintainability refers to the ease with which the system can be modified, updated, or repaired, contributing to its long-term sustainability. Deployability involves the ease and efficiency with which the software can be deployed and installed on different platforms, reducing downtime and minimizing risk of errors.
Example: An example of the application of the Agility Requirements Catalogue ABB could be in the development of a new software system. The developers would need to ensure that the system is configurable, allowing users to easily customize it to their needs. They would also need to ensure that it is compatible with a range of other systems, software, and hardware to ensure wide usability. The system should be maintainable, with clear documentation and a modular design to allow for easy updates and repairs. Finally, the system should be easily deployable, with a straightforward installation process that minimizes disruption to the existing system.
LOST view: Digital Solution Non-Functional Requirements Catalogue view
Identifier: http://data.europa.eu/dr8/egovera/AgilityRequirementsCatalogueGrouping
ABB name: egovera:AgilityRequirementsCatalogueGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-17
dct:identifier: http://data.europa.eu/dr8/egovera/AgilityRequirementsCatalogueGrouping
dct:title: Agility Requirements Catalogue Catalogue
Definition: Digital Public Service Improvement Principle Catalogue ABB is a grouping that covers the principles, guidelines, and strategies aimed at enhancing the delivery of public services through digital platforms. The catalogue primarily focuses on the principle of 'Innovation', which is a key driver in the modernization and improvement of public services.
Source: EIRA Team Research
Additional information: The Digital Public Service Improvement Principle Catalogue ABB is an essential tool for public service organizations seeking to leverage digital technologies to improve their service delivery. The catalogue's main element is 'Innovation', which refers to the application of new ideas, methods, or technologies to enhance public service delivery. Innovation in this context can involve the development of new digital services, the improvement of existing services through digital technologies, or the use of digital technologies to create new ways of engaging with the public. The catalogue provides a framework for understanding and applying the principle of innovation in the context of digital public service improvement.
Example: An example of the application of the Digital Public Service Improvement Principle Catalogue ABB could be a local government agency using it as a guide to develop a new online service for residents to report issues in their community. The agency could use the principle of 'Innovation' to explore new ways of receiving and responding to reports, such as through a mobile app or a chatbot, thereby improving the efficiency and accessibility of their service.
LOST view: Architecture Principles view
Identifier: http://data.europa.eu/dr8/egovera/DigitalPublicServiceImprovementPrincipleCatalogueGrouping
ABB name: egovera:DigitalPublicServiceImprovementPrincipleCatalogueGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-18
dct:identifier: http://data.europa.eu/dr8/egovera/DigitalPublicServiceImprovementPrincipleCatalogueGrouping
dct:title: Digital Public Service Improvement Principle Catalogue Catalogue
Definition: Customs Compliance and Regulatory Requirements Enablers ABB is a Grouping that covers a range of digital platforms and systems designed to streamline, automate, and facilitate the management of customs procedures. These include special, export, transit, and import procedures, as well as the accreditation of Authorised Economic Operators and compliance requirements checks. These systems are aimed at enhancing trade facilitation, ensuring compliance with customs regulations, and promoting efficient and secure cross-border trade within the customs environment.
Source: EIRA Team Research
Additional information: The elements within the Customs Compliance and Regulatory Requirements Enablers ABB are digital solutions that automate various customs processes such as document verification, risk assessment, and clearance for export and import procedures. They also facilitate electronic communication and data exchange between traders and customs authorities, reducing paperwork, improving accuracy, and expediting procedures. The special procedure element refers to systems managing customs procedures that deviate from standard import/export processes. The transit procedure element refers to systems facilitating the movement of goods under customs control from one customs territory to another. The Authorised Economic Operator accreditation and compliance requirements checks elements, although not described in the provided JSON, likely refer to systems managing the accreditation process for economic operators and ensuring compliance with regulatory requirements.
Example: An example of the application of these elements could be a company using the Export procedure digital solution to electronically submit export declarations and relevant documentation through a centralized online platform. The system would then automate the document verification, risk assessment, and export clearance processes, facilitating electronic communication and data exchange between the company and customs authorities. This would reduce paperwork, improve accuracy, and expedite the export procedure, ensuring compliance with customs regulations and promoting efficient and secure cross-border trade.
LOST view: TVA-Customs Compliance and Regulatory Requirements Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/CustomsComplianceAndRegulatoryRequirementsEnablersGrouping
ABB name: egovera:CustomsComplianceAndRegulatoryRequirementsEnablersGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-20
dct:identifier: http://data.europa.eu/dr8/egovera/CustomsComplianceAndRegulatoryRequirementsEnablersGrouping
dct:title: Customs Compliance And Regulatory Requirements Enablers
Definition: Blockchain Enablers ABB is a Grouping that refers to components and services that facilitate the development, deployment, and management of ledger technology applications
Source: Inspired in European Blockchain Strategy
Source reference: https://digital-strategy.ec.europa.eu/en/library/european-blockchain-strategy-brochure
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): Fishcoin Project, is a project using Blockchain technologies for seafood traceability. https://fishcoin.co/
Interoperability Dimension: Structural IoP
LOST view: Technical view - application
Interoperability Saliency: The Blockchain Enablers Grouping ABB is salient for interoperability because it comprises the tools, applications and services relevant to implement and deploying ledger technologies into digital public services.
Identifier: http://data.europa.eu/dr8/BlockchainEnablersGrouping
ABB name: eira:BlockchainEnablersGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/BlockchainEnablersGrouping
Interoperability Layer: TechnicalApplication
Definition: Customs Information Base ABB is a Grouping that covers a wide range of elements related to customs procedures, regulations, and operations. It includes information on economic operators, customs partners, duties calculation, classification of goods, and more. This information base is crucial for the smooth functioning of customs operations and for ensuring compliance with international trade laws and regulations.
Source: EIRA Team Research
Additional information: The Customs Information Base ABB includes elements such as Economic Operators Registration and Identification number (EORI), free circulation requirement information, laboratories information, threats and fraudulent actions information, duties calculation information, imports information, combined nomenclature, workforce information, classification of goods information, temporary storage information, exports information, special procedures information, binding tariffs information, guarantee information, economic operators information, customs partners information, economic value information, internal logistic information, and origin of goods information. Each of these elements plays a critical role in customs operations, from identifying and registering economic operators to calculating duties and classifying goods. This information base is essential for ensuring that all customs procedures are carried out correctly and efficiently.
Example: For instance, the 'Economic Operators Registration and Identification number (EORI)' element contains information about the EORI, which is a unique identification number that businesses need to import or export goods. The 'Free circulation requirement information' element provides details about the requirements for goods to move freely within a certain area. The 'Laboratories information' element includes data about the laboratories that test the goods for compliance with safety and quality standards. The 'Duties calculation Information' element contains information on how duties on goods are calculated.
LOST view: OV-Customs Functional Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/CustomsInformationBaseGrouping
ABB name: egovera:CustomsInformationBaseGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-20
dct:identifier: http://data.europa.eu/dr8/egovera/CustomsInformationBaseGrouping
dct:title: Customs Information Base
Definition: Customs Digital Public Services Catalogue ABB is a Grouping that covers a wide range of digital public services related to customs operations and management. These services include, but are not limited to, Economic Operators Registry management, EU Customs Trader Portal, Analysis Management, Customs logistics management, Centralised Clearance for Import, Determination of the economic value of goods declared for importation, Tariff Registry management, and many others.
Source: EIRA Team Research
Additional information: The Customs Digital Public Services Catalogue ABB encompasses a comprehensive list of digital services that facilitate various customs operations. These services range from managing registries of economic operators and tariffs, to handling customs declarations and duties calculation. They also include digital platforms like the EU Customs Trader Portal, and systems for managing internal customs logistics. Furthermore, the catalogue includes services for compliance verification, partner authorization, and procedure automation. All these services aim to streamline and digitalize customs processes, making them more efficient and accessible.
Example: An example of a service in the Customs Digital Public Services Catalogue is the 'Economic Operators Registry management'. This digital public service is responsible for managing the registry of economic operators. Another example is the 'EU Customs Trader Portal', a digital platform that provides traders with access to various EU customs services. 'Duties calculation and payment' is another service that facilitates the calculation and payment of customs duties.
LOST view: OV-Customs Functional Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/CustomsDigitalPublicServicesCatalogueGrouping
ABB name: egovera:CustomsDigitalPublicServicesCatalogueGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-20
dct:identifier: http://data.europa.eu/dr8/egovera/CustomsDigitalPublicServicesCatalogueGrouping
dct:title: Customs Digital Public Services Catalogue
Definition: Machine Translation Enablers ABB is a Groping that refers to tools or components that facilitate the translation of text from one language to another using machine learning techniques
Source: Inspired in eTranslation
Source reference: https://commission.europa.eu/resources-partners/etranslation_en
Interoperability Dimension: Structural IoP
LOST view: Technical view - application
Interoperability Saliency: The Translation Enablers Grouping ABB is salient for technical interoperability because it comprises a set of tools and components that ensure the translation of digital public services to different languages in the European Union by using machine learning techniques.
Identifier: http://data.europa.eu/dr8/TranslationEnablersGrouping
ABB name: eira:TranslationEnablersGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/TranslationEnablersGrouping
Interoperability Layer: TechnicalApplication
Definition: Business Agnostic Data Mapping Solutions (BADS) is a grouping that covers a range of solutions designed to facilitate the mapping of data from various heterogeneous data structures and serializations to the RDF data model. These solutions are not specific to any particular business or industry, making them versatile and adaptable across different contexts. The key element in this grouping is the RDF Mapping Language (RML), a generic mapping language that extends the W3C-standardized mapping language, R2RML.
Source: EIRA Team Research
Additional information: The Business Agnostic Data Mapping Solutions catalogue primarily includes the RDF Mapping Language (RML), a mapping language that allows for the expression of customized mapping rules from various data structures and serializations to the RDF data model. RML is a superset of R2RML, the W3C standard for expressing customized mappings from relational databases to RDF. As such, RML follows the same syntax as R2RML and extends its applicability and scope by adding support for data in other structured formats. RML mappings are themselves RDF graphs, and this document provides a comprehensive description of the RML language and its concepts through definitions and examples.
Example: An example of the application of Business Agnostic Data Mapping Solutions would be in a scenario where a business needs to map data from a relational database to RDF. Using RML, the business can express customized mapping rules to convert the data from the relational database into the RDF data model. This allows for greater interoperability and flexibility in data management and usage.
LOST view: SV-Data Mapping
Identifier: http://data.europa.eu/dr8/egovera/BusinessAgnosticDataMappingSolutionsGrouping
ABB name: egovera:BusinessAgnosticDataMappingSolutionsGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/egovera/BusinessAgnosticDataMappingSolutionsGrouping
Name: Business Agnostic Data Mapping Solutions Catalogue
Interoperability Layer: Semantic
Definition: Digital Public Service Operation Principle Catalogue ABB is a grouping that covers a range of principles and guidelines that are essential for the operation of digital public services. These principles include convergence control on public policy goals attainment, data accessibility, data findability, data interoperability, data reusability, preservation of information, security by design, and trust.
Source: EIRA Team Research
Additional information: The Digital Public Service Operation Principle Catalogue ABB is a comprehensive collection of principles that guide the operation of digital public services. 'Convergence control on public policy goals attainment' refers to the alignment of digital services with public policy goals. 'Data Accessibility' and 'Data Findability' pertain to the ease of access and discovery of data respectively. 'Data Interoperability' and 'Data Reusability' concern the ability of systems to work together and the potential for data to be reused. 'Preservation of information' is about maintaining and protecting data, while 'Security by Design' is a principle that emphasizes the importance of incorporating security measures from the onset of system design. Lastly, 'Trust' refers to the confidence and reliability in digital public services.
Example: An example of the application of these principles can be seen in a digital public service like an online tax filing system. The system should be designed with 'Security by Design', ensuring that user data is protected. The data collected should be 'Accessible' and 'Findable' for users, and 'Interoperable' to allow for seamless interaction with other systems. The system should also allow for 'Data Reusability', enabling data to be used for multiple purposes. The 'Preservation of Information' is crucial to maintain historical tax records. The system should also align with the 'Convergence control on public policy goals attainment' by facilitating the efficient collection of taxes. Lastly, the system should foster 'Trust' among users by being reliable and secure.
LOST view: Architecture Principles view
Identifier: http://data.europa.eu/dr8/egovera/DigitalPublicServiceOperationPrincipleCatalogueGrouping
ABB name: egovera:DigitalPublicServiceOperationPrincipleCatalogueGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-18
dct:identifier: http://data.europa.eu/dr8/egovera/DigitalPublicServiceOperationPrincipleCatalogueGrouping
dct:title: Digital Public Service Operation Principle Catalogue Catalogue
Definition: User Experience Management Enablers ABB is a Grouping that refers to components and services that track, measure, analyze and improve any interaction people have with the organization
Source: Inpired in referece business and cloud provider compabies
Source reference: https://www.vmware.com/topics/glossary/content/experience-management.html
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): Mi Carpeta Ciudadana Carpeta Ciudadana is a personal online space that facilitates your relationship with public administrations. https://carpetaciudadana.gob.es/carpeta/clave.htm
Interoperability Dimension: Behavioral IoP
LOST view: Technical view - application
Interoperability Saliency: The User Experience Management Enablers Grouping ABB is salient for technical interoperability because it comprises services and components that allow different parties involved in the use and delivery o public services, to exchange and provide data or information.
Identifier: http://data.europa.eu/dr8/UserExperienceManagementEnablersGrouping
ABB name: eira:UserExperienceManagementEnablersGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/UserExperienceManagementEnablersGrouping
Interoperability Layer: TechnicalApplication
Definition: Data Lake Infrastructure Enablers ABB is a Grouping of a set of tools and digital services hat help organizations build and maintain a robust data lake infrastructure
Source: Inspired in Forbes
Source reference: https://www.forbes.com/sites/ciocentral/2011/07/21/big-data-requires-a-big-new-architecture/?sh=5be8fb361157
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): Smart Data Lake. https://smartdatalake.eu/
Interoperability Dimension: Structural IoP
LOST view: Technical view - infrastructure
Interoperability Saliency: Data Lake Infrastructure Enabers ABB is salient for semantic and technical interoperability because it determines the needed infrastructure to host data management considering multiple data sources. This ABB also implements analytical services for ensuring data quality of the stored information.
Identifier: http://data.europa.eu/dr8/DataLakeInfrastructureEnablersGrouping
ABB name: eira:DataLakeInfrastructureEnablersGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/DataLakeInfrastructureEnablersGrouping
Interoperability Layer: TechnicalInfrastructure
Definition: National Binding Instruments (NBI) is a grouping that covers a broad range of legislative and regulatory frameworks related to interoperability in various domains. This includes structural, behavioural, and governance interoperability. The NBI provides a structured approach to the implementation and management of these frameworks, ensuring that they are in line with national and international standards and best practices.
Source: EIRA Team Research
Additional information: The National Binding Instruments (NBI) catalogue is a comprehensive repository of legislative and regulatory frameworks that govern interoperability in various domains. It includes the Legislation on Structural Interoperability (NBI), which covers the National Schema on eIdentification, Cybersecurity, eDelivery, and access to Base Registries. It also includes the Legislation on Behavioural Interoperability (NBI) and the Legislation on Governance Interoperability (NBI). Each of these categories contains specific elements that provide detailed information on the respective legislative and regulatory frameworks. The NBI catalogue is designed to facilitate the implementation and management of these frameworks, ensuring compliance with national and international standards and best practices.
Example: For instance, under the Legislation on Structural Interoperability (NBI), there are specific elements such as the National Schema on eIdentification which provides guidelines on electronic identification processes. Similarly, the National Schema on Cybersecurity outlines the legislative framework for managing cybersecurity risks. The National Schema on eDelivery provides the regulatory framework for electronic delivery services, while the National Schema on the access to Base Registries outlines the guidelines for accessing base registries. These elements provide a structured approach to implementing and managing interoperability in their respective domains.
LOST view: LV-Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/NationalBindingInstrumentsGrouping
ABB name: egovera:NationalBindingInstrumentsGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-17
dct:identifier: http://data.europa.eu/dr8/egovera/NationalBindingInstrumentsGrouping
dct:title: National Binding Instruments Catalogue
Definition: Legislation on Governance Interoperability (NNBI) is a grouping that covers a comprehensive catalogue of information entities related to laws, regulations, and policies that facilitate the interaction between different governance systems. This catalogue is empty as indicated by the JSON provided, but it is intended to house elements that define and describe the legal and regulatory framework that enables interoperability in governance.
Source: EIRA Team Research
Additional information: The Legislation on Governance Interoperability (NNBI) catalogue is designed to be a repository of information entities that detail the legal and regulatory aspects of governance interoperability. Interoperability in this context refers to the ability of different governance systems to work together, exchange information and function effectively. The catalogue is currently empty, but it is intended to include elements such as specific laws, regulations, policies, guidelines, and standards that facilitate interoperability in governance. Each element in the catalogue will have a name and a description, providing a clear understanding of the element's role and relevance in promoting governance interoperability.
Example: An example of an element that might be included in the Legislation on Governance Interoperability (NNBI) catalogue could be a law like the 'Data Sharing and Governance Act'. The name of the element would be 'Data Sharing and Governance Act' and the description might detail how this law facilitates the sharing of data between different governmental departments, thereby promoting interoperability.
LOST view: LV-Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/LegislationOnGovernanceInteroperabilityGrouping
ABB name: egovera:LegislationOnGovernanceInteroperabilityGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-20
dct:identifier: http://data.europa.eu/dr8/egovera/LegislationOnGovernanceInteroperabilityGrouping
dct:title: Legislation On Governance Interoperability (NNBI) Catalogue
Definition: Customs Privacy Data Policy Catalogue ABB is a grouping that covers the elements related to the protection of sensitive and proprietary data within a business or organization. It includes measures and policies that ensure the confidentiality of business information, preventing unauthorized access, use, or disclosure.
Source: EIRA Team Research
Additional information: The Customs Privacy Data Policy Catalogue ABB is a comprehensive collection of elements that pertain to the confidentiality of business information. This includes, but is not limited to, trade secrets, financial data, client lists, and marketing strategies. The catalogue emphasizes the importance of implementing appropriate security measures, access controls, non-disclosure agreements, and policies to maintain the confidentiality of business information. The aim is to prevent unauthorized access, use, or disclosure of such information, which could compromise the competitive advantage, reputation, or legal standing of the business.
Example: An example of an element in the Customs Privacy Data Policy Catalogue ABB is 'Confidentiality of Business Information'. This element refers to the protection of sensitive and proprietary data belonging to a business or organization. It involves ensuring that confidential information remains secure and is accessible only to authorized individuals within the organization. Confidentiality safeguards aim to prevent unauthorized access, use, or disclosure of such information.
LOST view: SV-Governance Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/CustomsPrivacyDataPolicyCatalogueGrouping
ABB name: egovera:CustomsPrivacyDataPolicyCatalogueGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-20
dct:identifier: http://data.europa.eu/dr8/egovera/CustomsPrivacyDataPolicyCatalogueGrouping
dct:title: Customs Privacy Data Policy Catalogue
Definition: Legislation on Structural Interoperability (EBI) ABB is a grouping that covers key regulations issued by the European Union to establish a framework for electronic identification, trust services, and cybersecurity in the internal market. It includes regulations that aim to enhance the security and reliability of electronic transactions, promote the use of electronic identification, facilitate the digital single market, and strengthen the resilience of the EU's digital infrastructure.
Source: EIRA Team Research
Additional information: The Legislation on Structural Interoperability (EBI) ABB includes two key regulations. The first, Regulation 2014910, also known as eIDAS, provides a legal framework for electronic signatures, seals, time stamps, documents, and registered delivery services, ensuring their legal validity and cross-border recognition within the EU. The second, Regulation 2018389, establishes a framework for cooperation and information exchange in the field of cybersecurity, setting out rules for sharing information on cyber threats and incidents, coordinating response measures, and establishing a European Cybersecurity Certification Framework.
Example: An example of the application of the Legislation on Structural Interoperability (EBI) ABB is the use of electronic signatures in cross-border transactions within the EU. Under Regulation 2014910 (eIDAS), these signatures are legally valid and recognized across member states, facilitating electronic transactions and promoting the digital single market. Another example is the sharing of information on cyber threats and incidents between member states under Regulation 2018389, which enhances EU cybersecurity capabilities and strengthens the resilience of its digital infrastructure.
LOST view: LV-Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/LegislationOnStructuralInteroperabilityGrouping
ABB name: egovera:LegislationOnStructuralInteroperabilityGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-20
dct:identifier: http://data.europa.eu/dr8/egovera/LegislationOnStructuralInteroperabilityGrouping
dct:title: Legislation On Structural Interoperability (EBI) Catalogue
Definition: Business Agnostic High Value Dataset Solutions (BAHVDS) is a grouping that covers a wide range of high-value datasets that are not specific to any particular business sector. These datasets include Geospatial, Business-related data, Metereology, Mobility, Statistics, and Earth Observation Data. Each of these datasets comprises different types of data, such as INSPIRE themes, reference parcels, agricultural parcels, company information, records, financial statements, weather data, river information services data, statistical data, and environmental information.
Source: EIRA Team Research
Additional information: The BAHVDS is a comprehensive catalogue of high-value datasets that are applicable across various business sectors. The Geospatial High Value Dataset includes INSPIRE themes, reference parcels, and agricultural parcels. The Business-related data High Value Dataset includes basic company information, records, and financial statements. The Metereology High Value Dataset includes observation measurement data (weather stations), climate data, weather warnings, radar data, NWP model data. The Mobility High Value Dataset includes INSPIRE themes and River Information Services data. The Statistics High Value Dataset includes statistical data on select legal acts. The Earth Observation Data High Value Dataset includes INSPIRE themes, environmental information according to the environmental information directive, and datasets related to select legal acts.
Example: Examples of application of these datasets could be in various sectors such as agriculture, where the Geospatial High Value Dataset could be used for land management and planning. The Business-related data High Value Dataset could be used by financial institutions for risk assessment and credit scoring. The Metereology High Value Dataset could be used by weather forecasting agencies for accurate weather prediction. The Mobility High Value Dataset could be used for transportation planning and management. The Statistics High Value Dataset could be used by government agencies for policy making. The Earth Observation Data High Value Dataset could be used for environmental monitoring and conservation.
LOST view: SV-Business Agnostic High Value Dataset
Identifier: http://data.europa.eu/dr8/egovera/BusinessAgnosticHighValueDatasetSolutionsGrouping
ABB name: egovera:BusinessAgnosticHighValueDatasetSolutionsGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-17
dct:identifier: http://data.europa.eu/dr8/egovera/BusinessAgnosticHighValueDatasetSolutionsGrouping
dct:title: Business Agnostic High Value Dataset Solutions Catalogue
Definition: Scalability Requirements Catalogue ABB is a grouping that covers a range of non-functional IT requirements that are critical for ensuring the scalability, performance, and efficiency of a system or application. It includes elements such as Traffic Pattern, Elasticity, and Latency, each of which plays a key role in determining how well a system can handle user traffic and respond to changes in demand.
Source: EIRA Team Research
Additional information: The Scalability Requirements Catalogue ABB is a comprehensive collection of non-functional requirements that are essential for the design and operation of scalable IT systems. The 'Traffic Pattern' element refers to the expected volume and frequency of user traffic, which helps in planning the necessary infrastructure and resources. 'Elasticity' refers to the system's ability to scale up or down based on demand, ensuring optimal performance and cost-efficiency. 'Latency', on the other hand, refers to the time delay between a request and response, which is a crucial factor in the overall user experience. By considering these elements, IT professionals can design systems that are robust, scalable, and efficient, meeting the needs of users while optimizing resource utilization.
Example: For instance, a video streaming service needs to consider all these elements in their system design. The 'Traffic Pattern' would help them prepare for peak viewing times and ensure the system can handle the load. 'Elasticity' would allow the service to scale up during popular live events and scale down during off-peak hours, optimizing resource use. Lastly, 'Latency' is critical for providing a smooth viewing experience, as high latency could lead to buffering and lagging issues.
LOST view: Digital Solution Non-Functional Requirements Catalogue view
Identifier: http://data.europa.eu/dr8/egovera/ScalabilityRequirementsCatalogueGrouping
ABB name: egovera:ScalabilityRequirementsCatalogueGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-17
dct:identifier: http://data.europa.eu/dr8/egovera/ScalabilityRequirementsCatalogueGrouping
dct:title: Scalability Requirements Catalogue Catalogue
Definition: Digital Workplace Enablers is a Grouping that refers to components or services that enable the collaboration of work aspects while security and privacy are ensured.
Source: European Comission
Source reference: https://ec.europa.eu/info/publications/digital-workplace-strategy_en
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): Set of IT tools used by European Commission officials, workers, etc. There is a new strategy put in place by the Commission to improve the work of the different roles involved. https://europa.eu/digitec/news/digital-workplace-european-commission/
Interoperability Dimension: Behavioral IoP
LOST view: Technical view - application
Interoperability Saliency: The Digital Workplace Enablers Grouping ABB is salient for technical interoperability because it tools, components or services that allow the free collaboration of work aspects while security and privacy are ensured. The free collaboration is relevant for interoperability because allows to enable and maintain digital public services without the need of being at the Organisation responsible for digital public services head quarters
Identifier: http://data.europa.eu/dr8/DigitalWorkplaceEnablersGrouping
ABB name: eira:DigitalWorkplaceEnablersGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/DigitalWorkplaceEnablersGrouping
Interoperability Layer: TechnicalApplication
Description: Containers Orchestrator Solutions ABB is a Grouping that refers to actual solutions that facilitate the management, scaling, networking, and deployment of containerized applications. These solutions provide an automated framework for running and coordinating containers within and across different environments.
Additional information: Container orchestrator solutions are essential in modern application development and deployment, especially in cloud-based and microservices architectures. They handle the lifecycle of containers, from provisioning and deployment to networking, scaling, and load balancing. They also ensure the health and availability of containers, restarting failed containers, and replacing and rescheduling containers when nodes die. Some of the most popular container orchestrator solutions include Kubernetes, Docker Swarm, and Apache Mesos.
Example: 1. Kubernetes is a widely used container orchestrator solution that automates the deployment, scaling, and management of containerized applications. 2. Docker Swarm is another example, which allows for the management of a cluster of Docker nodes as a single virtual system. 3. Apache Mesos is a project that manages computer clusters and provides efficient resource isolation and sharing across distributed applications or frameworks.
Publisher: EIRA Team Research
LOST view: TVA-Containerization Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/BusinessAgnosticContainersOrchestratorSolutionsGrouping
EIRA traceability: eira:DigitalSolutionApplicationService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-20
dct:identifier: http://data.europa.eu/dr8/egovera/BusinessAgnosticContainersOrchestratorSolutionsGrouping
dct:title: Containers Orchestrator SolutionsGrouping
Description: Blockchain Solutions ABB is a grouping that refers to actual solutions that facilitate the use of blockchain technology in various industries. These solutions are designed to leverage the unique features of blockchain such as decentralization, transparency, security, and immutability to improve business processes, enhance trust, and reduce operational costs.
Additional information: Blockchain Solutions ABB encompasses a wide range of services and applications that utilize blockchain technology. These solutions can be tailored to meet the specific needs of different industries, including finance, supply chain, healthcare, and more. They can be used to create secure and transparent transaction networks, track and verify the authenticity of goods, manage digital identities, and much more. Blockchain Solutions ABB can also include consulting services to help businesses understand and implement blockchain technology effectively.
Example: Examples of Blockchain Solutions ABB include blockchain-based supply chain management systems that provide end-to-end visibility and traceability of goods, blockchain-based financial systems that enable secure and transparent transactions, and blockchain-based healthcare systems that ensure the security and privacy of patient data. Another example is the use of blockchain for energy trading, where ABB has developed a solution that allows for peer-to-peer energy transactions, improving efficiency and reducing costs.
Publisher: EIRA Team Research
LOST view: TVA-Trust Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/BusinessAgnosticBlockchainSolutionsGrouping
EIRA traceability: eira:DigitalSolutionApplicationService
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-08-20
dct:identifier: http://data.europa.eu/dr8/egovera/BusinessAgnosticBlockchainSolutionsGrouping
dct:title: Blockchain SolutionsGrouping
Definition: Legislation on Structural Interoperability (NNBI) ABB is a grouping that covers the legal and regulatory framework related to the structural interoperability of systems, networks, and services. It includes laws, regulations, directives, and other legal instruments that govern the design, implementation, and operation of interoperable systems and services.
Source: EIRA Team Research
Additional information: The NNBI ABB is a comprehensive catalogue of legal and regulatory instruments that are relevant to structural interoperability. It provides a structured and systematic approach to understanding and navigating the complex legal landscape of interoperability. The catalogue includes a wide range of elements, each with a specific name and description. These elements represent different aspects of the legal and regulatory framework for interoperability, including specific laws and regulations, overarching legal principles, regulatory authorities and their roles, compliance requirements, and enforcement mechanisms. The NNBI ABB is an essential resource for policymakers, regulators, industry professionals, and other stakeholders involved in the design, implementation, and operation of interoperable systems and services.
Example: Examples of application of the Legislation on Structural Interoperability (NNBI) ABB could include the development of a new digital communication network that needs to comply with specific interoperability standards, or a public administration implementing a new e-government service that needs to be compatible with existing systems and services. In these cases, the NNBI ABB would provide a comprehensive overview of the relevant legal and regulatory requirements, helping to ensure compliance and avoid potential legal and regulatory pitfalls.
LOST view: LV-Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/LegislationOnStructuralInteroperabilityGrouping
ABB name: egovera:LegislationOnStructuralInteroperabilityGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-20
dct:identifier: http://data.europa.eu/dr8/egovera/LegislationOnStructuralInteroperabilityGrouping
dct:title: Legislation On Structural Interoperability (NNBI) Catalogue
Definition: Semantic Governance Content ABB is a Grouping that refers to the concepts and terms to support the elaboration of rules and mechanims to enhance the availability, integrity, interoperability and security of data while respecting data protection and ethical rules
Source: EUR-LEX
Source reference: https://eur-lex.europa.eu/legal-content/EN/TXT/PDF/?uri=CELEX:52020PC0767
Identifier: http://data.europa.eu/dr8/SemanticGovernanceContentGrouping
eira:ID: http://data.europa.eu/dr8/SemanticGovernanceContentGrouping
ABB name: eira:SemanticGovernanceContentGrouping
Definition: Trust Infrastructure Enablers ABB is a Grouping of a set of components and services devoted to creating and managing public keys for encryption, which is a common method of securing data transfers on the internet
Source: ENISA
Source reference: https://www.enisa.europa.eu/topics/incident-response/glossary/public-key-infrastructure-pki
Synonym:
Additional information:
Example: The following implementation is an example of how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): eDelivery - PKI Service. https://ec.europa.eu/digital-building-blocks/wikis/display/DIGITAL/PKI+Service
Interoperability Dimension: Structural IoP
LOST view: Technical view - infrastructure
Interoperability Saliency: Trust Infrastructure Enablers ABB is salient for organizational interoperability because it defines the rules and methodologies to ensure the secure and trustworthy exchange of information between public services.
Identifier: http://data.europa.eu/dr8/TrustInfrastructureEnablersGrouping
ABB name: eira:TrustInfrastructureEnablersGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/TrustInfrastructureEnablersGrouping
Interoperability Layer: TechnicalInfrastructure
Definition: Solution Architect Concerns ABB is a Grouping that covers the processes a solution architect should follow, and the relation/influence of process related with other roles' processes, to read/assess/understand an eGovERA model. It includes the journeys of various roles such as Public Policy Officer, Governance Analyst, Information Architect, Software Architect, and Infrastructure Architect.
Source: EIRA Team Research
Additional information: The Solution Architect Concerns ABB is a comprehensive catalogue that outlines the key concerns and processes that a solution architect should consider when working with an eGovERA model. It includes the journeys of various roles, providing a detailed roadmap for each. The Public Policy Officer Journey, for instance, outlines the steps a public policy officer would take in the context of the eGovERA model. Similarly, the Governance Analyst Journey, Information Architect Journey, Software Architect Journey, and Infrastructure Architect Journey provide a step-by-step guide for these roles. Each journey is designed to help the solution architect understand the processes, responsibilities, and concerns of these roles, thereby enabling them to better assess and understand the eGovERA model.
Example: For instance, the 'Public Policy Officer Journey' might include steps like 'Identify Policy Needs', 'Develop Policy Proposal', 'Implement Policy', and 'Evaluate Policy Impact'. Similarly, the 'Software Architect Journey' might include steps like 'Define Software Requirements', 'Design Software Architecture', 'Implement Software', and 'Test and Validate Software'. By understanding these journeys, a solution architect can better understand how each role interacts with the eGovERA model and can therefore design more effective solutions.
LOST view: [A] How to read the model
Identifier: http://data.europa.eu/dr8/egovera/SolutionArchitectConcernsGrouping
ABB name: egovera:SolutionArchitectConcernsGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-18
dct:identifier: http://data.europa.eu/dr8/egovera/SolutionArchitectConcernsGrouping
dct:title: Solution Architect Concerns Catalogue
Definition: Organisational Governance Frameworks Catalogue ABB is a grouping that covers a set of business objects that enable the protection, confidentiality, and interoperability of data, information, and knowledge assets and the organizational resources handling them. It includes the Security Framework, Privacy Framework, and Interoperability Framework.
Source: EIRA Team Research
Additional information: The Organisational Governance Frameworks Catalogue ABB is a comprehensive collection of frameworks that are designed to guide organizations in managing and protecting their data and information assets. The Security Framework focuses on the protection of these assets and the resources handling them. The Privacy Framework, on the other hand, emphasizes the confidentiality aspects of these assets and resources. Lastly, the Interoperability Framework is designed to enable organizations to collaborate effectively towards the joint delivery of public services. It does this by specifying a set of common elements such as vocabulary, concepts, principles, guidelines, and recommendations.
Example: An example of the application of the Organisational Governance Frameworks Catalogue ABB could be a public service organization that needs to ensure the security and privacy of its data while also needing to collaborate with other organizations. The Security Framework would guide the organization in protecting its data and resources. The Privacy Framework would help ensure the confidentiality of the data. The Interoperability Framework would provide the necessary guidelines and recommendations for effective collaboration with other organizations.
LOST view: OV-Governance Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/BusinessAgnosticOrganisationalGovernanceFrameworksCatalogueGrouping
ABB name: egovera:BusinessAgnosticOrganisationalGovernanceFrameworksCatalogueGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-20
dct:identifier: http://data.europa.eu/dr8/egovera/BusinessAgnosticOrganisationalGovernanceFrameworksCatalogueGrouping
dct:title: Organisational Governance Frameworks Catalogue Catalogue
Definition: Privacy Enablers ABB is a Grouping that refers to components and services that facilitate the implementation of privacy-related functionality within an application or system
Source: ePrivacy Regulation
Source reference: https://digital-strategy.ec.europa.eu/en/policies/eprivacy-regulation
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): SOLVIT - Solvit is a mailbox service for the access, rectification or deletion of personal data.(http://ec.europa.eu/solvit/privacy-statement/#maincontentSec8)
Interoperability Dimension: Structural IoP
LOST view: Technical view - application
Interoperability Saliency: The Privacy Enablers Grouping ABB is salient for technical interoperability because it comprises tools and components that facilitate the implementation of privacy-related functionality within an application or system. This is relevant for the implementation and deployment of digital public services.
Identifier: http://data.europa.eu/dr8/PrivacyEnablersGrouping
ABB name: eira:PrivacyEnablersGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/PrivacyEnablersGrouping
Interoperability Layer: TechnicalApplication
Definition: Identification and Access Enablers ABB is a Grouping that refers to components to enable the secure identification and authentication of users, systems and services into a platform.
Source: World Bank
Source reference: https://id4d.worldbank.org/guide/enablers
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): EU Login - EU Login is the European Commission's user authentication service. It allows authorised users to access a wide range of Commission web services. EU Login is the entry gate to sign in to different European Commission services and/or other systems. EU Login verifies your identity and allows recovering your personal settings, history and access rights in a secure way. You can sign in using social media accounts or the EU Login account. EU Login supports a variety of verification methods: • Password; • ECAS Mobile App PIN code; • ECAS Mobile App QR code; • On mobile authentication; • Mobile phone + SMS; • Token and Token CRAM. https://webgate.ec.europa.eu/cas/about.html
Interoperability Dimension: Structural IoP
LOST view: Technical view - application
Interoperability Saliency: The Identification and Access Enablers Grouping ABB is salient for interoperability because it is composed of the different tools, mechanisms and platforms that can ensure the access rights, and the confidentiality of data. In general terms, identification and authentication are relevant aspects that can enable trustworthy data exchanges or harm data in interoperable digital services.
Identifier: http://data.europa.eu/dr8/IdentificationAndAccessEnablersGrouping
ABB name: eira:IdentificationAndAccessEnablersGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/IdentificationAndAccessEnablersGrouping
Interoperability Layer: TechnicalApplication
Definition: Legislation on Behavioural Interoperability (ENBI) ABB is a grouping that covers the legal and regulatory aspects related to the interaction between different systems and software applications. It includes the rules, standards, and protocols that govern how these systems communicate and exchange data, ensuring that they can work together effectively and efficiently.
Source: EIRA Team Research
Additional information: The ENBI ABB does not contain any specific elements as indicated by the provided JSON. However, in a broader context, it would typically encompass elements such as data exchange protocols, communication standards, security regulations, privacy laws, and other legal requirements related to interoperability. These elements are crucial in ensuring that different systems can interact with each other without any issues, while also maintaining the security and privacy of the data being exchanged. The ENBI ABB would be applicable in various fields, including IT, telecommunications, healthcare, and more.
Example: An example of application could be in the healthcare sector, where different systems need to exchange patient data. The ENBI ABB would cover the legal requirements for this data exchange, such as the need for patient consent, the standards for data encryption, and the protocols for data transmission. This ensures that the systems can interact effectively, while also protecting the privacy and security of the patient data.
LOST view: LV-Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/LegislationOnBehaviouralInteroperabilityGrouping
ABB name: egovera:LegislationOnBehaviouralInteroperabilityGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-20
dct:identifier: http://data.europa.eu/dr8/egovera/LegislationOnBehaviouralInteroperabilityGrouping
dct:title: Legislation On Behavioural Interoperability (ENBI) Catalogue
Description: Observability and Monitoring Solutions ABB is a grouping that refers to actual solutions that facilitate the collection, processing, storage, indexing, and visualization of data from various sources, particularly in the context of microservices and other applications. This grouping includes tools for centralized logging and log analysis, as well as metrics instrumentation for monitoring system performance.
Additional information: The Observability and Monitoring Solutions ABB grouping includes tools such as the ELK Stack and Micrometer. The ELK Stack is a collection of three open-source tools: Elasticsearch, Logstash, and Kibana. Elasticsearch is a distributed search and analytics engine that stores and indexes data, providing fast and scalable search capabilities. Logstash is a data processing pipeline that ingests, transforms, and sends data to Elasticsearch. Kibana is a data visualization and exploration platform that allows users to interact with the data stored in Elasticsearch, creating real-time dashboards, charts, and graphs. On the other hand, Micrometer is an open-source dimensional metrics instrumentation library for microservices and other applications. It provides a simple and consistent API for collecting application metrics, such as response times, error rates, and throughput, from various monitoring systems. Micrometer supports a wide range of monitoring systems, including Prometheus, Graphite, InfluxDB, and more, allowing developers to choose the system that best fits their needs.
Example: For example, a company could use the ELK Stack to centralize logging from various sources, making it easier to analyze and visualize data in real time. They could also use Micrometer to collect metrics from their microservices, helping them monitor system performance and identify potential issues before they become major problems.
Publisher: EIRA Team Research
LOST view: TVA-Observability and Monitoring Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/BusinessAgnosticObservabilityAndMonitoringSolutionsGrouping
EIRA traceability: eira:DigitalSolutionApplicationService
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-08-20
dct:identifier: http://data.europa.eu/dr8/egovera/BusinessAgnosticObservabilityAndMonitoringSolutionsGrouping
dct:title: Observability And Monitoring SolutionsGrouping
Definition: Customs Legislation on Governance Interoperability (ENBI) ABB is a Grouping that covers the set of rules, regulations, and standards that facilitate the exchange and mutual understanding of information between different customs governance systems. It aims to ensure seamless and efficient communication and cooperation between various customs authorities and stakeholders, thereby enhancing the effectiveness and efficiency of customs operations.
Source: EIRA Team Research
Additional information: ENBI is crucial in the modern global trade environment where customs operations involve multiple jurisdictions and numerous stakeholders. It covers aspects such as data exchange standards, communication protocols, security measures, and legal frameworks that enable interoperability. It aims to ensure that different customs systems can work together seamlessly, reducing delays and costs, and enhancing the security and efficiency of international trade. The elements contained within ENBI can vary widely, including technical standards, legal agreements, operational procedures, and more.
Example: An example of ENBI application could be the implementation of a common data exchange standard across different customs systems, allowing them to share and understand the same information. Another example could be the establishment of a legal framework that enables the mutual recognition of customs controls and procedures, reducing the need for duplicate checks and speeding up the customs process.
LOST view: LV-Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/CustomsLegislationOnGovernanceInteroperabilityGrouping
ABB name: egovera:CustomsLegislationOnGovernanceInteroperabilityGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-20
dct:identifier: http://data.europa.eu/dr8/egovera/CustomsLegislationOnGovernanceInteroperabilityGrouping
dct:title: Customs Legislation On Governance Interoperability (ENBI)
Definition: Customs Base Registry ABB is a Grouping that covers a range of systems and identifiers used in the regulation and facilitation of international trade. These elements include the Registered Exporter system (REX), Economic Operators Registration and Identification number (EORI), Import Control System (ICS), Integrated Tariff of the European Union (TARIC), VAT Information Exchange System (VIES), and the Authorized Economic Operator (AEO) status.
Source: EIRA Team Research
Additional information: The Customs Base Registry is a comprehensive catalogue of systems and identifiers used in international trade. The REX system allows for self-certification of goods' origin by registered exporters. The EORI system assigns unique identification numbers to economic operators involved in customs activities within the EU. The ICS is an EU system designed to enhance customs control over goods entering the EU. TARIC is an integrated tariff database that contains information on customs tariffs, import and export formalities, and applicable measures. VIES is a system that enables businesses to verify the validity of VAT numbers of their trading partners within the EU. AEO is a status granted to businesses by customs administrations in the EU and many other countries worldwide, recognizing businesses that meet certain criteria and demonstrate compliance with customs regulations and security standards.
Example: For example, a business exporting goods from the EU would need to register in the REX system to self-certify the origin of their goods. They would also need an EORI number for identification in customs activities. If they are importing goods into the EU, they would need to submit advanced electronic entry summary declarations through the ICS. They could use TARIC to determine the customs duties and trade policies associated with their products, and VIES to verify the VAT numbers of their trading partners. If they meet certain criteria, they could also apply for AEO status to enhance their supply chain security and facilitate their trade operations.
LOST view: SV-Customs Base Registries [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/CustomsBaseRegistryGrouping
ABB name: egovera:CustomsBaseRegistryGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-20
dct:identifier: http://data.europa.eu/dr8/egovera/CustomsBaseRegistryGrouping
dct:title: Customs Base Registry
Definition: Customs Process Streamlining and Efficiency Enablers ABB is a Grouping that covers a range of digital tools and technologies designed to enhance the efficiency and effectiveness of customs operations. These include systems for expeditions controls, people and skill allocation and distribution, and guarantee management. These digital solutions provide customs authorities with real-time visibility and control over various aspects of the customs process, from the movement and condition of goods to the allocation of human resources and the management of customs guarantees.
Source: EIRA Team Research
Additional information: The elements within the Customs Process Streamlining and Efficiency Enablers ABB are designed to automate and streamline various aspects of the customs process. Expeditions controls involve the use of digital systems to monitor, track, and control goods throughout the transportation and logistics process. People and skill allocation and distribution refers to digital workforce management systems that optimize personnel deployment and task assignment. Guarantee management involves the electronic administration of customs guarantees to ensure compliance with customs requirements. These digital solutions enhance supply chain security, improve workforce planning, reduce administrative burdens, and facilitate trade facilitation.
Example: Examples of application for the elements within the Customs Process Streamlining and Efficiency Enablers ABB include the use of Electronic Data Interchange (EDI), Global Positioning System (GPS), and Internet of Things (IoT) devices for expeditions controls; digital workforce management systems for people and skill allocation and distribution; and digital platforms for the management and administration of customs guarantees.
LOST view: TVA-Customs Process Streamlining and Efficiency Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/CustomsProcessStreamliningAndEfficiencyEnablersGrouping
ABB name: egovera:CustomsProcessStreamliningAndEfficiencyEnablersGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-20
dct:identifier: http://data.europa.eu/dr8/egovera/CustomsProcessStreamliningAndEfficiencyEnablersGrouping
dct:title: Customs Process Streamlining And Efficiency Enablers
Definition: Governance Analyst Data Spaces Concerns ABB is a Grouping that covers the processes a governance analyst should follow, and the relation/influence of process related with other roles' processes, to read/assess/understand an eGovERA model in order to understand/develop a Data Spaces solution/architecture. It includes elements such as Organisational view and Legal view.
Source: EIRA Team Research
Additional information: The 'Governance Analyst Data Spaces Concerns ABB' is a comprehensive catalogue of elements that a governance analyst needs to consider when developing a Data Spaces solution or architecture. It includes the 'Organisational view', which pertains to understanding the structure, roles, and responsibilities within the organization, and the 'Legal view', which involves understanding the legal and regulatory requirements that the solution or architecture must comply with. These elements are crucial in ensuring that the solution or architecture is not only technically sound but also aligns with the organization's goals and complies with all relevant laws and regulations.
Example: For instance, when developing a Data Spaces solution for a government agency, the governance analyst would first look at the 'Organisational view' to understand the agency's structure, roles, and responsibilities. This could involve analyzing the agency's organizational chart, job descriptions, and other relevant documents. Next, the analyst would consider the 'Legal view' to ensure that the solution complies with all relevant laws and regulations. This could involve reviewing the agency's legal and regulatory compliance policies, consulting with legal experts, and conducting a legal risk assessment.
LOST view: [A] How to read the model
Identifier: http://data.europa.eu/dr8/egovera/GovernanceAnalystDataSpacesConcernsGrouping
ABB name: egovera:GovernanceAnalystDataSpacesConcernsGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-18
dct:identifier: http://data.europa.eu/dr8/egovera/GovernanceAnalystDataSpacesConcernsGrouping
dct:title: Governance Analyst Data Spaces Concerns Catalogue
Definition: Semantic Web Data Formats (SWDF) is a grouping that covers a range of technical specifications and standards designed to facilitate the creation, integration, and utilization of structured data on the web. These formats provide the necessary tools for businesses and organizations to represent, connect, and share information in a machine-readable way, enabling the development of semantic web applications and promoting data interoperability.
Source: EIRA Team Research
Additional information: The Semantic Web Data Formats encompass various elements including LDES, RDF, RDF-S, OWL2, RML, SPARQL*, RDF*, and SPARQL. Each of these elements serves a specific purpose in the realm of semantic web and linked data. For instance, LDES allows for the publishing of datasets as a collection of immutable objects. RDF and RDF-S provide a standard for representing and connecting information, with RDF-S extending the basic RDF vocabulary. OWL2 is a technical framework for creating ontologies and enabling computers to understand and reason about structured knowledge. RML provides a standardized approach for transforming structured data into RDF. RDF* extends RDF with the ability to make statements about other statements. Lastly, SPARQL and SPARQL* are query languages that enable the extraction of insights from semantic data.
Example: An example of application of these formats could be a large corporation using RDF to represent their complex business data in a structured and machine-readable way. They could then use RML to transform data from various sources into RDF, ensuring semantic integration and interoperability. The corporation could also use OWL2 to create ontologies that define concepts, properties, and relationships within their business domain. This would enable their computers to accurately interpret data, make logical deductions, and draw new conclusions. Finally, they could use SPARQL to query their semantic data and extract valuable insights for decision-making.
LOST view: SV-Functional Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/SemanticWebDataFormatsSolutionsGrouping
ABB name: egovera:SemanticWebDataFormatsSolutionsGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/egovera/SemanticWebDataFormatsSolutionsGrouping
Name: Semantic Web Data Formats Catalogue
Interoperability Layer: Semantic
Definition: Business Agnostic Data Space Digital Public Services Catalogue ABB is a grouping that covers a range of digital public services that are not specific to any business sector. These services include eSignature, eNotification, Log Management, Audit, eIdentification, Digital Collaboration and a sub-catalogue of services for Business Agnostic Data Space Participants.
Source: EIRA Team Research
Additional information: The catalogue is a comprehensive collection of digital public services that are designed to be applicable across various business sectors. These services include eSignature, which provides digital signature services; eNotification, which provides digital notification services; Log Management, which provides digital log management services; Audit, which provides digital audit services; eIdentification, which provides digital identification services; and Digital Collaboration, which provides digital collaboration services. The catalogue also includes a sub-catalogue of services specifically for Business Agnostic Data Space Participants, which includes services such as Data Extraction, Transformation and Loading; Content Management; Open Data Management; Workflow Management; Data Exchange; eArchiving; Anonymisation; and Secure Access Control.
Example: For instance, a business in the healthcare sector could use the eSignature service to digitally sign documents, the eNotification service to send digital notifications to patients, the Log Management service to manage digital logs of patient records, the Audit service to conduct digital audits of their operations, the eIdentification service to digitally identify patients, and the Digital Collaboration service to collaborate digitally with other healthcare providers. They could also use the services in the Business Agnostic Data Space Participant sub-catalogue to manage their data and workflows.
LOST view: OV-Data Spaces
Identifier: http://data.europa.eu/dr8/egovera/BusinessAgnosticDataSpaceDigitalPublicServicesCatalogueGrouping
ABB name: egovera:BusinessAgnosticDataSpaceDigitalPublicServicesCatalogueGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-17
dct:identifier: http://data.europa.eu/dr8/egovera/BusinessAgnosticDataSpaceDigitalPublicServicesCatalogueGrouping
dct:title: Business Agnostic Data Space Digital Public Services Catalogue Catalogue
Definition: Digital Solution High Availability and Resilience Architecture Decision Catalogue ABB is a grouping that covers a range of decisions related to optimizing the performance of a system. These decisions may include choices regarding caching strategies, load balancing techniques, database optimizations, or any other performance-related considerations. The catalogue includes elements such as Caching Strategy, Content Delivery Network, Performance Testing and Tuning, Network Optimization, Application of Service Monitoring Tools, Application of Service Monitoring Tools Configuration, and Disaster Recovery Plan.
Source: EIRA Team Research
Additional information: The Digital Solution High Availability and Resilience Architecture Decision Catalogue ABB is a comprehensive collection of elements that capture decisions related to optimizing the performance of a system. Each element in the catalogue represents a specific decision area, with a focus on strategies and techniques that can enhance system performance, ensure high availability, and build resilience. The elements are described in the form of Architecture Decision Records (ADRs), which provide a detailed account of the decision-making process, the options considered, the decision taken, and the reasons behind the decision.
Example: For instance, the 'Caching Strategy' element in the catalogue might detail the decision to use a distributed caching system to improve the performance of a data-intensive application. The 'Content Delivery Network' element might describe the decision to use a global CDN to ensure fast and reliable content delivery to users worldwide. The 'Performance Testing and Tuning' element might outline the decision to implement a rigorous performance testing regime and a continuous tuning process to maintain optimal system performance. Similarly, the 'Network Optimization', 'Application of Service Monitoring Tools', 'Application of Service Monitoring Tools Configuration', and 'Disaster Recovery Plan' elements would detail decisions in their respective areas.
LOST view: Digital Solution Architecture Decisions Catalogue view
Identifier: http://data.europa.eu/dr8/egovera/DigitalSolutionHighAvailabilityAndResilienceArchitectureDecisionCatalogueGrouping
ABB name: egovera:DigitalSolutionHighAvailabilityAndResilienceArchitectureDecisionCatalogueGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-18
dct:identifier: http://data.europa.eu/dr8/egovera/DigitalSolutionHighAvailabilityAndResilienceArchitectureDecisionCatalogueGrouping
dct:title: Digital Solution High Availability And Resilience Architecture Decision Catalogue Catalogue
Definition: Knowledge discovery Enablers ABB is a Grouping that refers to components and services that facilitate the process of discovering insights and knowledge from data
Source: European Comission-Open Science
Source reference: https://research-and-innovation.ec.europa.eu/strategy/strategy-2020-2024/our-digital-future/open-science_en
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): CELLAR. Cellar metadata is stored in a knowledge graph, and more specifically in a triple store. A SPARQL interface is used to query the metadata. https://op.europa.eu/en/web/cellar/cellar-data/metadata/knowledge-graph
Interoperability Dimension: Structural IoP
LOST view: Technical view - application
Interoperability Saliency: The Knowledge Discovery Enablers Grouping ABB is salient for technical interoperability because it comprises tools, data services and components that enable and enhance the knowledge discovery process from data and information.
Identifier: http://data.europa.eu/dr8/KnowledgeDiscoveryEnablersGrouping
ABB name: eira:KnowledgeDiscoveryEnablersGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/KnowledgeDiscoveryEnablersGrouping
Interoperability Layer: TechnicalApplication
Definition: Public Policy Officer Concerns ABB is a Grouping that covers the legal aspects and perspectives that a public policy officer needs to consider when interpreting an eGovERA model. This includes understanding the legal implications of policy decisions, the legal framework surrounding the policy area, and how these legal factors interact with other elements of the policy process.
Source: EIRA Team Research
Additional information: The Public Policy Officer Concerns ABB grouping is crucial for public policy officers as it provides a structured approach to understanding and interpreting the legal aspects of an eGovERA model. This includes not only understanding the legal implications of policy decisions, but also how these legal factors interact with other elements of the policy process. This grouping is particularly important for public policy officers who are tasked with designing and implementing policies within a specific legal framework, as it provides them with the tools and knowledge necessary to navigate this complex landscape.
Example: For instance, a public policy officer working on data privacy policies would use the 'Legal view' element of the Public Policy Officer Concerns ABB to understand the legal framework surrounding data privacy, the legal implications of different policy decisions, and how these legal factors interact with other elements of the policy process such as technological capabilities or public opinion.
LOST view: [A] How to read the model
Identifier: http://data.europa.eu/dr8/egovera/PublicPolicyOfficerConcernsGrouping
ABB name: egovera:PublicPolicyOfficerConcernsGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-18
dct:identifier: http://data.europa.eu/dr8/egovera/PublicPolicyOfficerConcernsGrouping
dct:title: Public Policy Officer Concerns Catalogue
Definition: Binding power ABB is a Requirement that to the legal authority or force of a law or decision that requires compliance by those who are subject to it.
Source: Inspired in ILO
Source reference: https://www.ilo.org/global/topics/labour-migration/publications/WCMS_385582/lang--en/index.htm
Definition: Trust Enablers ABB is a Grouping that refers to components and services that facilitate the establishment and maintenance of secure-cross borders transactions and interactions.
Source: Inspired in eIDAS
Source reference: http://eur-lex.europa.eu/legal-content/EN/TXT/?uri=uriserv%3AOJ.L_.2014.257.01.0073.01.ENG
Interoperability Dimension: Structural IoP
LOST view: Technical view - application
Interoperability Saliency: The Trust Enablers Grouping is salient for interoperability because it comprises the set of tools, services and applications that allow to secure the digital public services across borders. Trust enablers are focused on transactions and interactions between parties (services, platforms, individuals) related to services. By applying those mechanisms identities, and timestamps (amongst other aspects) can be guaranteed and ensure the trustworthy data exchange
Identifier: http://data.europa.eu/dr8/TrustEnablersGrouping
ABB name: eira:TrustEnablersGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/TrustEnablersGrouping
Interoperability Layer: TechnicalApplication
Definition: European Data Sharing Principles Catalogue (EDSPC) is a grouping that covers a range of principles related to data sharing within the European context. These principles include Self Determination, Inclusion, Fundamental Rights, Consumer Protection, Fair Competition, Citizen Participation, Sustainability, and Data Altruism. Each principle represents a key aspect of data sharing and management in Europe, reflecting the region's commitment to privacy, inclusivity, and sustainability.
Source: EIRA Team Research
Additional information: The European Data Sharing Principles Catalogue is a comprehensive list of principles that guide data sharing practices in Europe. 'Self Determination' refers to the ability of individuals or organizations to control their own data. 'Inclusion' ensures that all individuals and organizations have equal access to data resources. 'Fundamental Rights' protect the basic rights of individuals in relation to data, such as privacy and freedom of expression. 'Consumer Protection' safeguards consumers from harmful data practices. 'Fair Competition' promotes a level playing field in the data market. 'Citizen Participation' encourages public involvement in data-related decisions. 'Sustainability' emphasizes the long-term viability of data practices. Finally, 'Data Altruism' encourages the voluntary sharing of data for the common good.
Example: An example of the application of these principles can be seen in the European Union's General Data Protection Regulation (GDPR). This regulation embodies principles such as Self Determination, Fundamental Rights, and Consumer Protection by giving individuals control over their personal data and protecting them from harmful data practices. Similarly, initiatives that promote open data or data philanthropy reflect the principles of Inclusion, Citizen Participation, and Data Altruism.
LOST view: Architecture Principles view
Identifier: http://data.europa.eu/dr8/egovera/EuropeanDataSharingPrinciplesCatalogueGrouping
ABB name: egovera:EuropeanDataSharingPrinciplesCatalogueGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-18
dct:identifier: http://data.europa.eu/dr8/egovera/EuropeanDataSharingPrinciplesCatalogueGrouping
dct:title: European Data Sharing Principles Catalogue Catalogue
Definition: Customs Digital Business Capabilities Map (DBC) is a grouping that covers a range of elements related to the digital operations and procedures of customs. These elements include compliance requirements checks, customs cooperation, import and export procedures, guarantee, tariffs registry management, preservation of cargo information, cooperation between customs and postal operators, transit procedure, authorised economic operator accreditation, risk analysis, cooperation between customs laboratories, special procedure, laboratories management, MS' customs organization management, duties calculation and payment, and expeditions controls.
Source: EIRA Team Research
Additional information: The Customs Digital Business Capabilities Map (DBC) is a comprehensive catalogue of elements that pertain to the digital functionalities and operations of customs. It includes a wide array of elements, each with a specific role and purpose in the customs digital business landscape. These elements range from compliance checks and cooperation between customs and other entities, to specific procedures such as import, export, transit, and special procedures. It also covers areas such as tariffs registry management, preservation of cargo information, risk analysis, and duties calculation and payment. The DBC is a crucial tool for understanding and managing the digital aspects of customs operations.
Example: For instance, 'Compliance requirements checks' is an element that ensures all customs procedures and operations adhere to the necessary regulations and standards. 'Customs cooperation' refers to the collaboration between different customs entities to ensure efficient and effective operations. 'Import procedure' and 'Export procedure' are elements that detail the digital processes involved in importing and exporting goods. 'Risk analysis' is an element that involves assessing potential risks in customs operations to prevent any issues or disruptions.
LOST view: OV-Customs DBCs, DPSs and Information [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/CustomsDigitalBusinessCapabilitiesMapGrouping
ABB name: egovera:CustomsDigitalBusinessCapabilitiesMapGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-20
dct:identifier: http://data.europa.eu/dr8/egovera/CustomsDigitalBusinessCapabilitiesMapGrouping
dct:title: Customs Digital Business Capabilities Map
Definition: Customs Legislation on Governance Interoperability (NNBI) ABB is a grouping that covers the legal, regulatory, and policy framework that facilitates the exchange of information and cooperation between different governance systems in the context of customs operations. It encompasses the rules and procedures that ensure seamless interaction between various customs systems, promoting efficiency and effectiveness in customs administration.
Source: EIRA Team Research
Additional information: The NNBI ABB is a critical component in the modernization of customs operations. It provides a structured approach to managing the interactions between different governance systems, reducing the potential for conflicts and inconsistencies. This includes the harmonization of data standards, the development of common protocols for information exchange, and the establishment of mechanisms for dispute resolution. The NNBI ABB also addresses issues related to data privacy and security, ensuring that the exchange of information complies with relevant laws and regulations. It is a dynamic framework, evolving in response to technological advancements and changes in the customs environment.
Example: An example of the application of the NNBI ABB is the development of a common data model for the exchange of customs information between countries participating in a regional economic community. This involves the harmonization of data standards, the establishment of protocols for data exchange, and the implementation of measures to ensure data privacy and security. Another example is the establishment of a dispute resolution mechanism to address conflicts that may arise in the course of information exchange.
LOST view: LV-Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/CustomsLegislationOnGovernanceInteroperabilityGrouping
ABB name: egovera:CustomsLegislationOnGovernanceInteroperabilityGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-20
dct:identifier: http://data.europa.eu/dr8/egovera/CustomsLegislationOnGovernanceInteroperabilityGrouping
dct:title: Customs Legislation On Governance Interoperability (NNBI)
Definition: Digital Workplace Infrastructure Enablers ABB is a Grouping that enables the set of components and services that enable organizations to create and manage virtual workplaces environments and facilitate their access remotely.
Source: Inspired in Gartner
Source reference: https://www.gartner.com/en/information-technology/glossary/remote-access
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): PSI Remote Desktop Service from the European Open Science Cloud https://marketplace.eosc-portal.eu/services/remote-desktop-service?from_recommendation_panel=true&fromc=access-physical-einfrastructures
Interoperability Dimension: Structural IoP
LOST view: Technical view - infrastructure
Interoperability Saliency: Digital Workplace Infrastructure Enablers ABB is salient for technical interoperability due to it refers to setting up the workplace ecosystem to establish access to European public services remotely to access applications using open specifications and interfaces.
Identifier: http://data.europa.eu/dr8/DigitalWorkplaceInfrastructureEnablersGrouping
ABB name: eira:DigitalWorkplaceInfrastructureEnablersGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/DigitalWorkplaceInfrastructureEnablersGrouping
Interoperability Layer: TechnicalInfrastructure
Definition: Legislation on Behavioural Interoperability (EBI) is a grouping that covers a variety of legislative and regulatory measures enacted by the European Union (EU) to promote interoperability, data sharing, and data protection across member states. These measures aim to facilitate the exchange of information and services between public sector entities, enhance cybersecurity, ensure the protection of personal data, and promote fair competition in the digital economy.
Source: EIRA Team Research
Additional information: The EBI catalogue includes various directives, regulations, and proposals that address different aspects of behavioural interoperability. These include the Open Data Directive, the General Data Protection Regulation (GDPR), the Regulation on the free flow of non-personal data, the Single Digital Gateway Regulation, the Web Accessibility Directive, the Directive on electronic invoicing in public procurement, the Cyber Solidarity Act Proposal, the NIS2 Directive, the Digital Services Act, the Interoperable Europe Act Proposal, the Artificial Intelligence Act Proposal, the Digital Service Act (DSA), the Cyber Resilience Act Proposal, the Data Governance Act, the Implementing Act on High-Value Datasets, and the Digital Markets Act. Each of these measures contributes to the overall goal of promoting interoperability, data sharing, and data protection across the EU.
Example: For instance, the Open Data Directive sets minimum requirements for making public sector information available for re-use, while the GDPR establishes rules for the processing of personal data. The Regulation on the free flow of non-personal data promotes data sharing and portability, and the Single Digital Gateway Regulation aims to simplify access to public services and information online. The Web Accessibility Directive ensures that digital platforms are accessible to all individuals, including those with disabilities, and the Directive on electronic invoicing in public procurement promotes efficiency and interoperability in public procurement processes. The Cyber Solidarity Act Proposal strengthens the EU's ability to respond to cybersecurity threats, and the NIS2 Directive boosts the overall level of cybersecurity in the EU. The Digital Services Act creates a single market for digital services, the Interoperable Europe Act Proposal promotes the seamless exchange of data and information between public sector entities, and the Artificial Intelligence Act Proposal regulates the use of AI in the EU. The Digital Service Act (DSA) updates the EU's legal framework for illegal content on intermediaries, the Cyber Resilience Act Proposal establishes cybersecurity requirements for products with digital elements, the Data Governance Act establishes a framework for the governance of data, the Implementing Act on High-Value Datasets describes datasets held by the public sector, and the Digital Markets Act ensures fair and contestable markets in the digital sector.
LOST view: LV-Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/LegislationOnBehaviouralInteroperabilityGrouping
ABB name: egovera:LegislationOnBehaviouralInteroperabilityGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-20
dct:identifier: http://data.europa.eu/dr8/egovera/LegislationOnBehaviouralInteroperabilityGrouping
dct:title: Legislation On Behavioural Interoperability (EBI) Catalogue
Definition: Digital Solution Scalability Architecture Decision Catalogue ABB is a grouping that covers a range of Architecture Decision Records (ADRs) that are designed to ensure that a system can effectively scale to handle increased workload or user demands. This includes decisions related to horizontal scaling, database sharding, elastic cloud infrastructure, containerization and orchestration, vertical scaling, load balancing strategy, and scalability for growth.
Source: EIRA Team Research
Additional information: The Digital Solution Scalability Architecture Decision Catalogue ABB is a comprehensive collection of ADRs that address various aspects of system scalability. 'Horizontal Scaling' refers to the ability to increase capacity by connecting multiple hardware or software entities to work as a single logical unit. 'Database Sharding' is a type of database partitioning that separates very large databases into smaller, faster, more easily managed parts called data shards. 'Elastic Cloud Infrastructure' refers to the provision of IT infrastructure through the internet on an on-demand, pay-per-use basis. 'Containerization and Orchestration' involves encapsulating or packaging up software code and all its dependencies so that it can run uniformly and consistently on any infrastructure. 'Vertical Scaling' involves adding more resources such as computing power or memory to a server, or replacing one server with a more powerful one. 'Load Balancing Strategy' involves distributing network traffic across multiple servers to ensure no single server becomes overwhelmed with traffic. 'Scalability for Growth' involves designing the system in such a way that it can handle increased workload or user demands in the future.
Example: For instance, a company might decide to adopt a horizontal scaling strategy to handle increased user demands during peak times. This might involve adding more servers to their system to distribute the load more evenly. Similarly, a company with a large, complex database might decide to implement database sharding to improve performance and make the database more manageable. On the other hand, a company expecting rapid growth might decide to adopt an elastic cloud infrastructure to easily scale up or down based on demand.
LOST view: Digital Solution Architecture Decisions Catalogue view
Identifier: http://data.europa.eu/dr8/egovera/DigitalSolutionScalabilityArchitectureDecisionCatalogueGrouping
ABB name: egovera:DigitalSolutionScalabilityArchitectureDecisionCatalogueGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-18
dct:identifier: http://data.europa.eu/dr8/egovera/DigitalSolutionScalabilityArchitectureDecisionCatalogueGrouping
dct:title: Digital Solution Scalability Architecture Decision Catalogue Catalogue
Description: Orchestration Solutions ABB is a grouping that refers to actual solutions that facilitate the management, scheduling, and monitoring of complex workflows and data processing pipelines. These solutions are primarily used for orchestrating tasks across different systems and technologies, and for building both batch and streaming data processing pipelines.
Additional information: Orchestration Solutions ABB includes tools like Apache Airflow and Apache Beam. Apache Airflow is an open-source platform used for authoring, scheduling, and monitoring workflows. It allows users to define complex workflows as code, making it easier to manage and orchestrate tasks across different systems and technologies. Apache Beam, on the other hand, is an open-source unified programming model and set of tools for building batch and streaming data processing pipelines. It provides a high-level API that allows developers to write data processing logic once and execute it on various distributed processing backends.
Example: Examples of application for Orchestration Solutions ABB include using Apache Airflow to automate the execution of SQL queries and data transfers, or using Apache Beam to build a data processing pipeline that can handle both real-time and batch data.
Publisher: EIRA Team Research
LOST view: TVA-Orchestration Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/BusinessAgnosticOrchestrationSolutionsGrouping
EIRA traceability: eira:DigitalSolutionApplicationService
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-08-20
dct:identifier: http://data.europa.eu/dr8/egovera/BusinessAgnosticOrchestrationSolutionsGrouping
dct:title: Orchestration Solutions Catalogue
Definition: Customs Data Management Enablers ABB is a Grouping that covers a range of digital solutions and services designed to enhance the management, preservation, and accessibility of data related to customs processes. These solutions leverage advanced digital technologies to ensure the integrity, traceability, and efficiency of customs operations, from the handling and storage of cargo information to the management of customs laboratories.
Source: EIRA Team Research
Additional information: The Customs Data Management Enablers ABB includes two key elements: Preservation of cargo information and Laboratories management. The former refers to the digital capture, storage, and retrieval of cargo-related information, such as shipping details, transport documents, customs declarations, and inspection reports. This service ensures the integrity, traceability, and accessibility of critical data throughout the customs clearance process. The latter refers to the implementation of digital tools and systems to manage and oversee customs laboratories' operations, enhancing the accuracy, traceability, and efficiency of laboratory testing and analysis within the customs environment.
Example: Examples of application for the Customs Data Management Enablers ABB include a digital platform for the capture and storage of cargo information, which can be accessed by customs officers for verification and compliance checks. Another example is a laboratory information management system (LIMS) that automates and optimizes laboratory processes, such as sample tracking, test management, result analysis, and quality assurance, within the customs environment.
LOST view: TVA-Customs Data Management Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/CustomsDataManagementEnablersGrouping
ABB name: egovera:CustomsDataManagementEnablersGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-20
dct:identifier: http://data.europa.eu/dr8/egovera/CustomsDataManagementEnablersGrouping
dct:title: Customs Data Management Enablers
Definition: Business Agnostic Forms Structure Catalogue ABB is a grouping that covers a variety of form structures that are applicable across different business domains. These form structures are designed to be versatile and adaptable to various business needs, regardless of the industry or sector. The catalogue includes forms such as Contact Form, Feedback Form, Survey Form, Registration Form, and Order Form.
Source: EIRA Team Research
Additional information: The Business Agnostic Forms Structure Catalogue ABB is a comprehensive collection of form structures that are not specific to any business or industry. These forms are designed to be adaptable and versatile, allowing them to be used in a variety of different business contexts. The Contact Form is used for collecting basic information about a person or entity, the Feedback Form is used for gathering feedback or opinions, the Survey Form is used for conducting surveys or polls, the Registration Form is used for registering users or participants, and the Order Form is used for placing orders or making purchases. Each form structure can be customized to suit the specific needs of the business, making this catalogue a valuable resource for any business.
Example: Examples of application for the Business Agnostic Forms Structure Catalogue ABB could be a retail business using the Order Form for customers to place orders, a research institution using the Survey Form to conduct a study, a service provider using the Feedback Form to gather customer feedback, an event organizer using the Registration Form to register participants, or a company using the Contact Form on their website for visitors to get in touch.
LOST view: SV-Forms Structure
Identifier: http://data.europa.eu/dr8/egovera/BusinessAgnosticFormsStructureCatalogueGrouping
ABB name: egovera:BusinessAgnosticFormsStructureCatalogueGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-17
dct:identifier: http://data.europa.eu/dr8/egovera/BusinessAgnosticFormsStructureCatalogueGrouping
dct:title: Business Agnostic Forms Structure Catalogue Catalogue
Definition: Information Architect Data Spaces Concerns ABB is a Grouping that covers the processes an information architect should follow, and the relation/influence of process related with other roles' processes, to read/assess/understand an eGovERA model in order to understand/develop a Data Spaces solution/architecture. It includes elements such as Semantic view and Organisational view.
Source: EIRA Team Research
Additional information: The Information Architect Data Spaces Concerns ABB is a crucial tool for information architects working on Data Spaces solutions or architectures. It provides a structured approach to understanding and developing these solutions, taking into account the interplay between different roles and processes. The Semantic view element refers to the understanding and interpretation of the data, its meaning and relationships. The Organisational view element, on the other hand, pertains to the understanding of the organizational structure, roles, responsibilities, and processes that are involved in the management and use of the data.
Example: For instance, when developing a Data Spaces solution for a government agency, an information architect would use the Semantic view to understand the meaning and relationships of the data that the agency handles. They would use the Organisational view to understand the agency's structure, roles, and processes, and how these factors would influence the management and use of the data in the Data Spaces solution.
LOST view: [A] How to read the model
Identifier: http://data.europa.eu/dr8/egovera/InformationArchitectDataSpacesConcernsGrouping
ABB name: egovera:InformationArchitectDataSpacesConcernsGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-18
dct:identifier: http://data.europa.eu/dr8/egovera/InformationArchitectDataSpacesConcernsGrouping
dct:title: Information Architect Data Spaces Concerns Catalogue
Description: Translation Solutions ABB is a grouping that refers to actual solutions that facilitate the automatic translation of text and documents between multiple languages with high accuracy and speed. It leverages state-of-the-art neural machine translation services to enable users to overcome language barriers and communicate effectively in different languages.
Additional information: Translation Solutions ABB primarily includes eTranslation, a neural machine translation service offered by the European Commission. This service uses advanced artificial intelligence algorithms to understand the context and nuances of the original text and translate it into the target language while maintaining the original meaning and tone. It supports multiple languages, making it a versatile tool for global communication. The high accuracy and speed of eTranslation make it a reliable solution for translating official documents, web content, and other types of text.
Example: Examples of application for Translation Solutions ABB include translating official documents for international organizations, enabling multilingual communication on websites, and facilitating cross-border e-commerce transactions. For instance, a European Union agency can use eTranslation to translate policy documents into all EU languages. Similarly, an e-commerce platform can use this service to translate product descriptions and customer reviews into different languages, helping customers from different countries understand the product details and make informed purchase decisions.
Publisher: EIRA Team Research
LOST view: TVA-Translation Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/BusinessAgnosticTranslationSolutionsGrouping
EIRA traceability: eira:DigitalSolutionApplicationService
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-08-20
dct:identifier: http://data.europa.eu/dr8/egovera/BusinessAgnosticTranslationSolutionsGrouping
dct:title: Translation Solutions Catalogue
Definition: Infrastructure Architect Data Spaces Concerns ABB is a Grouping that covers the processes an infrastructure architect should follow, and the relation/influence of process related with other roles' processes, to read/assess/understand an eGovERA model in order to understand/develop a Data Spaces solution/architecture. This includes the technical view of both infrastructure and application.
Source: EIRA Team Research
Additional information: The Infrastructure Architect Data Spaces Concerns ABB is a comprehensive catalogue that includes the technical view of infrastructure and application. It is designed to guide infrastructure architects in understanding and developing a Data Spaces solution or architecture. The catalogue provides a structured approach to understanding the eGovERA model, which is crucial in the development of Data Spaces solutions. It also highlights the interplay between the processes of the infrastructure architect and those of other roles, fostering a more integrated and holistic approach to solution development.
Example: For instance, the 'Technical view - infrastructure' element in the catalogue could guide an infrastructure architect in understanding the underlying infrastructure requirements of a Data Spaces solution. This could involve assessing the current state of the infrastructure, identifying gaps, and developing strategies to bridge these gaps. On the other hand, the 'Technical view - application' element could guide the architect in understanding the application requirements of the solution, including the necessary software and interfaces.
LOST view: [A] How to read the model
Identifier: http://data.europa.eu/dr8/egovera/InfrastructureArchitectDataSpacesConcernsGrouping
ABB name: egovera:InfrastructureArchitectDataSpacesConcernsGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-18
dct:identifier: http://data.europa.eu/dr8/egovera/InfrastructureArchitectDataSpacesConcernsGrouping
dct:title: Infrastructure Architect Data Spaces Concerns Catalogue
Definition: Digital Solution Portability and Scalability Architecture Decision Catalogue ABB is a grouping that covers a range of technical architectural decisions related to the portability and scalability of digital solutions. These decisions are documented in the form of Architecture Decision Records (ADRs) and typically involve choosing specific technologies, frameworks, protocols, or design patterns to ensure the solution's adaptability, installability, replaceability, and its ability to manage and exchange data across borders.
Source: EIRA Team Research
Additional information: The catalogue includes decisions about Semantic Capability, Cross-Border Semantic Data Management, Cross-Border Data Exchange, Data Exchange Deployment, Data Exchanger Operations, Adaptability, Installability, and Replaceability. Each decision record provides a detailed description of the decision, the context in which it was made, the factors considered, and the implications of the decision. These decisions are crucial for ensuring that the digital solution can be easily installed, replaced, and adapted to changing requirements, and that it can effectively manage and exchange data across borders.
Example: For instance, the 'Semantic Capability' decision might involve choosing a specific semantic technology to ensure that the digital solution can understand and interpret the meaning of the data it processes. The 'Cross-Border Data Exchange' decision might involve selecting a specific data exchange protocol to ensure that the solution can effectively exchange data with systems in other countries. The 'Adaptability' decision might involve choosing a modular design pattern to ensure that the solution can be easily adapted to changing requirements.
LOST view: Digital Solution Architecture Decisions Catalogue view
Identifier: http://data.europa.eu/dr8/egovera/DigitalSolutionPortabilityAndScalabilityArchitectureDecisionCatalogueGrouping
ABB name: egovera:DigitalSolutionPortabilityAndScalabilityArchitectureDecisionCatalogueGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-18
dct:identifier: http://data.europa.eu/dr8/egovera/DigitalSolutionPortabilityAndScalabilityArchitectureDecisionCatalogueGrouping
dct:title: Digital Solution Portability And Scalability Architecture Decision Catalogue Catalogue
Definition: Digital Solution Architecture Decision Catalogue ABB is a Grouping that covers a comprehensive collection of architecture decisions related to digital solutions. It includes decisions about technical architecture, business architecture, security, privacy and compliance, high availability and resilience, scalability, portability, maintainability, quality, and usability. Each decision is documented in an Architecture Decision Record (ADR) that describes the context, decision, and consequences.
Source: EIRA Team Research
Additional information: The catalogue is divided into several categories, each focusing on a specific aspect of digital solution architecture. For example, the 'Digital Solution Technical Architecture Decision Catalogue' includes decisions about technology stack selection, API design, event-driven architecture, database schema design, and more. Similarly, the 'Digital Solution Business Architecture Decision Catalogue' includes decisions about cross-border identification business, dynamic location of data provider, data notification deployment, and others. Each decision is documented in an ADR, providing a record of why and how decisions were made, aiding in future understanding and decision-making.
Example: An example of an element in the catalogue is 'Technology Stack Selection'. This is an ADR that documents the decision-making process for selecting the technology stack for a digital solution. It would include the context (why the decision was needed), the decision (what was decided), and the consequences (the impact of the decision).
LOST view: Digital Solution Architecture Decisions Catalogue view
Identifier: http://data.europa.eu/dr8/egovera/DigitalSolutionArchitectureDecisionCatalogueGrouping
ABB name: egovera:DigitalSolutionArchitectureDecisionCatalogueGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-18
dct:identifier: http://data.europa.eu/dr8/egovera/DigitalSolutionArchitectureDecisionCatalogueGrouping
dct:title: Digital Solution Architecture Decision Catalogue Catalogue
Definition: Legislation on Structural Interoperability (ENBI) ABB is a grouping that covers a range of legislative documents and recommendations from the European Union. These documents aim to guide and regulate the implementation of interoperability within the digital space, addressing issues such as disinformation, digital rights and principles, and the creation of a secure European e-ID.
Source: EIRA Team Research
Additional information: The ENBI catalogue includes key documents such as the 'European Interoperability Framework - Implementation Strategy', which outlines the Commission's strategy for implementing interoperability across the EU. It also includes the 'Strengthened Code of Practice on Disinformation', a document aimed at combating the spread of false information online. The 'Declaration for the Future of Internet' and 'Declaration on Digital Rights and Principles' set out the EU's vision for a free, open and secure internet, while the 'Recommendation on Building a Joint Cyber Unit' and 'Recommendation on a trusted and secure European e-ID' provide specific recommendations for enhancing cybersecurity and digital identity within the EU.
Example: An example of the application of the ENBI catalogue could be a European digital service provider looking to ensure their services are in line with EU regulations and recommendations. They could consult the 'European Interoperability Framework - Implementation Strategy' for guidance on implementing interoperable systems, and the 'Recommendation on a trusted and secure European e-ID' for advice on creating secure digital identities for their users.
LOST view: LV-Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/LegislationOnStructuralInteroperabilityGrouping
ABB name: egovera:LegislationOnStructuralInteroperabilityGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-20
dct:identifier: http://data.europa.eu/dr8/egovera/LegislationOnStructuralInteroperabilityGrouping
dct:title: Legislation On Structural Interoperability (ENBI) Catalogue
Definition: Problem Statement Grouping refers to the set of elements needed for the detailed description of the issues, goals, constraints, and context influencing the creation and implementation of digital public services. It includes defining strategic goals, identifying regulatory and technical constraints, ensuring alignment with public policy objectives, providing guidelines for service implementation, understanding the context of policy decisions, and recognizing technical barriers and underlying assumptions. This problem statement serves as a framework to address interoperability challenges in digital public services, aligning solutions with public policy goals and relevant constraints.
Source: EIRA Team
LOST view: Semantic view
Viewpoint: EIRA Ontology viewpoint
Identifier: http://data.europa.eu/dr8/ProblemStatementGrouping
ABB name: eira:ProblemStatementGrouping
EIRA concept: eira:ArchitectureBuildingBlock
eira:identifier: http://data.europa.eu/dr8/ProblemStatementGrouping
Definition: Data Management Enablers ABB is a Grouping that refers to components and services that support effective data management practices and procedures.
Source: Inspired in European Comision- Data Governance and data policies at the European Comission
Source reference: https://commission.europa.eu/publications/data-governance-and-data-policies-european-commission_en
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): Context Broker as a CEF Building Block. https://ec.europa.eu/digital-building-blocks/wikis/download/attachments/82773424/Context%20Broker%20Brochure.pdf?version=1&modificationDate=1558016168498&api=v2
Interoperability Dimension: Structural IoP
LOST view: Technical view - application
Interoperability Saliency: The Data Management Enablers Grouping ABB is salient for technical interoperability because it comprises the tools, components and services related to data management. Data Management Enablers are relevant as they support effective and efficient data management, ensuring that interoperability can be achieved between digital public services.
Identifier: http://data.europa.eu/dr8/DataManagementEnablersGrouping
ABB name: eira:DataManagementEnablersGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/DataManagementEnablersGrouping
Interoperability Layer: TechnicalApplication
Definition: The description contains a full description of the architectural decisions.
Source: EIRA Team Research
Additional information: The Digital Solution Business Architecture Decision Catalogue ABB is a structured collection of architectural decisions made for digital business solutions. Each element in the catalogue represents a specific decision, such as 'Cross-Border Identification Business' or 'Data Subscription Capability'. These decisions are recorded in an Architecture Decision Record (ADR), which provides a detailed description of the decision, the context in which it was made, the contributing factors, and the consequences. The catalogue serves as a reference for understanding the architectural design of the digital solution and can be used to guide future decision-making.
LOST view: Digital Solution Architecture Decisions Catalogue view
Identifier: http://data.europa.eu/dr8/egovera/DigitalSolutionBusinessArchitectureDecisionCatalogueGrouping
ABB name: egovera:DigitalSolutionBusinessArchitectureDecisionCatalogueGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-18
dct:identifier: http://data.europa.eu/dr8/egovera/DigitalSolutionBusinessArchitectureDecisionCatalogueGrouping
dct:title: Digital Solution Business Architecture Decision Catalogue Catalogue
Description: Business Agnostic API Technical Interoperability Agreement Solutions (ABB) is a grouping that refers to actual solutions that facilitate the design, development, documentation, and consumption of APIs (Application Programming Interfaces) across different systems and platforms. These solutions are built upon various specifications and protocols such as OpenAPI, RESTful API, GraphQL, gRPC, JSON-RPC, SOAP, and OData, which provide a standard, language-agnostic interface for APIs, enabling interoperability between different systems.
Additional information: The Business Agnostic API Technical Interoperability Agreement Solutions (ABB) is a comprehensive suite of solutions that leverage various API specifications and protocols to ensure seamless interaction between different systems and platforms. These solutions are built upon OpenAPI, RESTful API, GraphQL, gRPC, JSON-RPC, SOAP, and OData specifications, each offering unique features and capabilities. OpenAPI is used for designing, building, documenting, and consuming REST APIs. RESTful API is a set of rules for building web services, while GraphQL is a data query and manipulation language for APIs. gRPC is a high-performance framework for service communication, JSON-RPC is a protocol for data exchange, SOAP is a messaging protocol for program communication over the internet, and OData is a protocol for building and consuming RESTful APIs.
Example: Examples of application for the Business Agnostic API Technical Interoperability Agreement Solutions include designing and building APIs for a multi-language system using OpenAPI and gRPC, creating web services using RESTful API, querying and manipulating data using GraphQL, exchanging data between a client and a server using JSON-RPC, communicating between programs running on different operating systems using SOAP, and building and consuming RESTful APIs using OData.
Publisher: EIRA Team Research
LOST view: TV-Technical Agreements
Identifier: http://data.europa.eu/dr8/egovera/BusinessAgnosticAPITechnicalInteroperabilityAgreementSolutionsGrouping
EIRA traceability: eira:TechnicalInteroperabilityAgreementContract
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-08-17
dct:identifier: http://data.europa.eu/dr8/egovera/BusinessAgnosticAPITechnicalInteroperabilityAgreementSolutionsGrouping
dct:title: Business Agnostic API Technical Interoperability Agreement Solutions Catalogue
Description: Bussiness Agnostic Conformance Solutions ABB is a grouping that refers to actual solutions that facilitate the alignment of business processes, regardless of the industry or sector, with the necessary regulatory and compliance requirements. These solutions are designed to be adaptable and flexible, allowing businesses from different sectors to conform to the same set of standards or regulations.
Additional information: These solutions are typically software or digital services that provide tools and features to help businesses manage and monitor their compliance with various regulations. They may include features for risk management, audit trails, reporting, and more. The 'agnostic' aspect refers to the fact that these solutions are not tied to any specific business or industry - they can be used by any type of business that needs to comply with certain regulations. This makes them highly versatile and useful for businesses operating in highly regulated industries, such as finance, healthcare, and more.
Example: Examples of Business Agnostic Conformance Solutions could include compliance management software like LogicGate or Onspring. These platforms provide tools for risk management, compliance, audit management, and more, and can be used by businesses in any industry. Another example could be a digital service that provides a platform for businesses to manage and monitor their GDPR compliance, which would be applicable to any business that handles personal data of EU citizens.
Publisher: EIRA Team Research
LOST view: TVA-Test Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/BusinessAgnosticConformanceSolutionsGrouping
EIRA traceability: eira:DigitalSolutionApplicationService
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-08-20
dct:identifier: http://data.europa.eu/dr8/egovera/BusinessAgnosticConformanceSolutionsGrouping
dct:title: Bussiness Agnostic Conformance SolutionsGrouping
Definition: Management Infrastructure Enablers ABB is a Grouping that refers to the set of components and services to manage a public administration IT platforms efficiently and efficiency.
Source: Inspired in PMI
Source reference: https://www.pmi.org/learning/library/project-management-infrastructure-4647
Example: The following implementation is an example of how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): Design Principles for Data Spaces -Position Paper. https://design-principles-for-data-spaces.org/
Interoperability Dimension: Structural IoP
LOST view: Technical view - infrastructure
Interoperability Saliency: Management Infrastructure Enablers ABB is salient for technical interoperability due to its set-up the implementation for managing and monitoring the public administration digital services to (i) ensure their correct behaviour, (ii) ensure the correct provision of resources, and (iii) guarantee the assessment of standards and regulations (including SLAs)
Identifier: http://data.europa.eu/dr8/ManagementInfrastructureEnablersGrouping
ABB name: eira:ManagementInfrastructureEnablersGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/ManagementInfrastructureEnablersGrouping
Interoperability Layer: TechnicalInfrastructure
Definition: Durability Requirements Catalogue ABB is a grouping that covers a set of non-functional IT requirements that ensure the long-term reliability, stability, and accessibility of a system. These requirements include replication, fault tolerance, and archivability, each of which plays a crucial role in maintaining the system's performance, security, and data integrity over time.
Source: EIRA Team Research
Additional information: The Durability Requirements Catalogue ABB is a comprehensive collection of non-functional requirements that are essential for the long-term operation of a system. 'Replication' refers to the system's ability to duplicate data or processes across multiple servers or locations, ensuring high availability and reliability. 'Fault tolerance' is the system's ability to continue functioning despite hardware or software failures, involving redundancy, backup systems, and failover mechanisms. 'Archivability' refers to the system's ability to store and retrieve data over a long period of time, ensuring that the data remains accurate, complete, and secure. Each of these elements is critical for systems that handle sensitive or critical data, such as those used in healthcare, finance, and transportation.
Example: An example of the application of the Durability Requirements Catalogue ABB could be a healthcare system. The system would need to replicate patient data across multiple servers to ensure it is always available when needed. It would also need to be fault-tolerant, so that in the event of a hardware or software failure, the system could continue to function without disruption. Lastly, the system would need to be archivable, storing patient data securely and in a retrievable format for many years, in compliance with regulatory requirements.
LOST view: Digital Solution Non-Functional Requirements Catalogue view
Identifier: http://data.europa.eu/dr8/egovera/DurabilityRequirementsCatalogueGrouping
ABB name: egovera:DurabilityRequirementsCatalogueGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-17
dct:identifier: http://data.europa.eu/dr8/egovera/DurabilityRequirementsCatalogueGrouping
dct:title: Durability Requirements Catalogue Catalogue
Definition: Enterprise Architecture Framework (EAF) alignment guidelines ABB is a Grouping that covers the process of establishing a harmonious relationship between the European Interoperability Reference Architecture (EIRA) model and any given Enterprise Architecture Framework (EAF). The aim is to make the EIRA model fully compliant with the chosen EAF, promoting uniformity across the architectural ecosystem.
Source: EIRA Team Research
Additional information: The EAF alignment guidelines serve as an integral part of the process, aiming to establish a harmonious relationship between the European Interoperability Reference Architecture (EIRA) model and any given Enterprise Architecture Framework (EAF). The ultimate goal is to make the EIRA model fully compliant with the chosen EAF, promoting uniformity across the architectural ecosystem. The elements contained within these guidelines include Interoperable European Solution, Achieve Interoperability, Creation of Interoperable European Solutions, European Interoperability Reference Architecture, Coordination Capacity, Regulatory Capacity, Delivery Capacity, Analytical Capacity, EIRA Ontology, Public Administration, Architecture Principle, Constraints, Assumptions and Decisions, Shared Legal Content, Shared Organisational Content, Digital Solution Requirement, Iternational Data Spaces Reference Architecture Model (IDS-RAM), Data Spaces Business Alliance, Eclipse Dataspace Components, JRC Data Spaces Knowledge Base, FIWARE for Data Spaces, Gaia-X Data Spaces Community.
Example: An example of the application of the EAF alignment guidelines could be the process of aligning a national public administration's enterprise architecture with the EIRA model. This would involve assessing the current architecture, identifying gaps and areas of non-compliance, and implementing changes to achieve alignment. The guidelines would provide a roadmap for this process, outlining the necessary steps and considerations.
LOST view: Enterprise Architecture Framework alignment guidelines view
Identifier: http://data.europa.eu/dr8/egovera/EnterpriseArchitectureFrameworkAlignmentGuidelinesGrouping
ABB name: egovera:EnterpriseArchitectureFrameworkAlignmentGuidelinesGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-20
dct:identifier: http://data.europa.eu/dr8/egovera/EnterpriseArchitectureFrameworkAlignmentGuidelinesGrouping
dct:title: Enterprise Architecture Framework (EAF) Alignment Guidelines Catalogue
Definition: Application Presentation Enablers ABB is a Grouping that enables the implementation of visually appealing and interactive user interfaces for software applications
Source: Inspired in Redhat
Source reference: https://www.redhat.com/architect/5-essential-patterns-software-architecture
Interoperability Dimension: Behavioral IoP
LOST view: Technical view - application
Viewpoint: Highlevel viewpoint
Interoperability Saliency: The Application Presentation Enablers Grouping ABB is salient for interoperability because is composed of the Human Interface Application Interface which is a key interoperability enabler that facilitates the data exchange between parties using the digital public service. In addition, this is relevant for interoperability because the ABBs included can work as a tool through which to assess compatible interfaces.
Identifier: http://data.europa.eu/dr8/ApplicationPresentationEnablersGrouping
ABB name: eira:ApplicationPresentationEnablersGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/ApplicationPresentationEnablersGrouping
Interoperability Layer: TechnicalApplication
Definition: Business Agnostic Trust Solutions (ABB) is a grouping that covers a range of solutions designed to establish and enhance trust in digital business environments. These solutions are agnostic, meaning they can be applied across various business sectors and are not limited to a specific industry or type of business. The elements within this grouping are geared towards ensuring compliance with digital trust regulations, enhancing security, and promoting transparency in digital transactions.
Source: EIRA Team Research
Additional information: The Business Agnostic Trust Solutions grouping includes elements such as the Digital Europe eSignature DSS open-source library. This is a software library for digital signature creation, validation, and extension. It is designed to help digital solutions achieve compliance with the eIDAS Regulation, which sets out the rules for electronic identification and trust services for electronic transactions in the European Single Market. The DSS library is a key tool for businesses looking to enhance the security and trustworthiness of their digital transactions, regardless of their specific industry or sector.
Example: An example of a Business Agnostic Trust Solution is the use of the Digital Europe eSignature DSS open-source library by an e-commerce company. The company can use the DSS library to create and validate digital signatures for online transactions, ensuring compliance with eIDAS Regulation and enhancing the security and trustworthiness of their business operations.
LOST view: TVA-Trust Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/BusinessAgnosticTrustSolutionsGrouping
ABB name: egovera:BusinessAgnosticTrustSolutionsGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-21
dct:identifier: http://data.europa.eu/dr8/egovera/BusinessAgnosticTrustSolutionsGrouping
dct:title: Business Agnostic Trust Solutions
Definition: Semantic Functional Content ABB is a Grouping that refers to the procedures and mechanims to structure and organise the information to convey meaning and functionality.
Source: Inspired in "Semantic Content" article
Source reference: https://philpapers.org/rec/STOSC-2
Identifier: http://data.europa.eu/dr8/SemanticFunctionalContentGrouping
eira:ID: http://data.europa.eu/dr8/SemanticFunctionalContentGrouping
ABB name: eira:SemanticFunctionalContentGrouping
Definition: Business Agnostic Reference Data Solutions (ABB) is a grouping that covers a range of information entities designed to support and enhance the efficiency of the Single Market. It includes elements such as ESCO, Regulated Professions DB, and Business Agnostic EU Vocabularies Reference Data Solutions. These elements aim to standardize and harmonize codes, labels, and other forms of data across various platforms and systems, facilitating effective communication and data exchange.
Source: EIRA Team Research
Additional information: The Business Agnostic Reference Data Solutions includes the ESCO classification which identifies and categorises skills, competences, and occupations relevant for the EU labour market and education and training. It also includes the Regulated Professions DB which contains information on regulated professions, statistics on migrating professionals, contact points and competent authorities, as provided by EU Member States, EEA countries, the UK and Switzerland. Furthermore, it includes the Business Agnostic EU Vocabularies Reference Data Solutions (BAEUV RDS) which is a grouping that covers a range of information entities such as NUTS, Reference Data Asset, Authority Tables, and the Digital Europe Thesaurus. These elements aim to standardize and harmonize codes, labels, and other forms of data across various platforms and systems, facilitating effective communication and data exchange.
Example: For instance, the ESCO classification can be used by job search platforms to standardize job titles and skills across the EU. The Regulated Professions DB can be used by professionals moving to another EU country to understand the regulations and requirements of their profession in the new country. The BAEUV RDS can be used by public authorities and businesses to ensure they are using the same codes and labels when exchanging data.
LOST view: SV-Agnostic Reference Data
Identifier: http://data.europa.eu/dr8/egovera/BusinessAgnosticReferenceDataSolutionsGrouping
ABB name: egovera:BusinessAgnosticReferenceDataSolutionsGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/egovera/BusinessAgnosticReferenceDataSolutionsGrouping
Name: Business Agnostic Reference Data Solutions Catalogue
Interoperability Layer: Semantic
Definition: Business Agnostic Data Management Digital Business Capability Catalogue ABB is a Grouping that refers to the actual catalogue of digital business capabilities (DBC) that puts together a range of capabilities related to data management. These capabilities are crucial for organizations to effectively and efficiently manage their data assets, gain valuable insights, make informed decisions, ensure data quality, security, and compliance, and generate value and revenue. The catalogue includes capabilities such as Data Discovery, Data Analytics, Data Monetization, Data Governance, Data Ethics, Data Interoperability, Data Sharing, Data Quality, Data Security, and Data Lineage.
Source: EIRA Team Research
Additional information: The Business Agnostic Data Management Digital Business Capability Catalogue ABB is a comprehensive catalogue that encompasses various aspects of data management. Each capability in the catalogue has a specific role and purpose in the overall data management strategy of an organization. For instance, Data Discovery and Data Analytics capabilities enable organizations to discover, analyze, and interpret large volumes of data to gain valuable insights and make informed decisions. Data Monetization capability allows organizations to generate value and revenue from their data assets. Data Governance and Data Ethics capabilities ensure the effective management, governance, and ethical use of data. Data Interoperability and Data Sharing capabilities facilitate seamless data exchange and integration across different systems and platforms. Data Quality and Data Security capabilities ensure the accuracy, integrity, and security of data. Lastly, Data Lineage capability enables organizations to track and trace the origin, movement, and transformation of data throughout its lifecycle.
Example: An example of the application of the Business Agnostic Data Management Digital Business Capability Catalogue ABB could be a large corporation implementing a data-driven strategy. The corporation could leverage the Data Discovery and Data Analytics capabilities to analyze customer data and gain insights into customer behavior and preferences. They could use the Data Monetization capability to create new revenue streams by selling these insights or using them to develop new products or services. The corporation could implement Data Governance and Data Ethics policies to ensure the ethical use of customer data and compliance with data protection regulations. They could use Data Interoperability and Data Sharing capabilities to integrate customer data from different systems and share it with relevant departments. The corporation could ensure the accuracy and security of the customer data by implementing Data Quality and Data Security measures. Finally, they could use the Data Lineage capability to track the origin and movement of the customer data across different systems and processes.
LOST view: OV-Data Spaces [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/BusinessAgnosticDataManagementDigitalBusinessCapabilityCatalogueGrouping
EIRA traceability: eira:DigitalBusinessCapability
ABB name: egovera:BusinessAgnosticDataManagementDigitalBusinessCapabilityCatalogueGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-17
dct:identifier: http://data.europa.eu/dr8/egovera/BusinessAgnosticDataManagementDigitalBusinessCapabilityCatalogueGrouping
dct:title: Business Agnostic Data Management Digital Business Capability Catalogue
Definition: Not Implemented Architecture Principles Catalogue ABB is a grouping that covers the collection of architecture principles that have not been implemented in a specific solution architecture. It serves as a repository for documenting these omissions, providing transparency and understanding of the architectural choices made.
Source: EIRA Team Research
Additional information: Despite the vital role architecture principles play, there are situations where certain principles may not be employed within a specific solution architecture. The Not Implemented Architecture Principles Catalogue ABB serves as a repository for documenting such cases. Including explanatory notes alongside each omitted principle is crucial. These notes should provide a clear rationale for the exclusion, explaining the context, constraints, or trade-offs that led to the decision. The catalogue facilitates knowledge sharing among architects by capturing the context and rationale behind each omitted principle. It also helps ensure that architectural decisions align with organizational governance frameworks and compliance requirements. Furthermore, it enables architects to proactively address potential risks and develop mitigation strategies. The documentation of omitted principles promotes a culture of continuous improvement, encouraging architects to revisit decisions, reassess trade-offs, and learn from past experiences.
Example: For instance, an architecture principle related to the use of open standards may not be implemented in a solution architecture due to vendor lock-in or specific business requirements. This omission would be documented in the Not Implemented Architecture Principles Catalogue ABB, along with an explanation of the reasons for the deviation. This documentation would then serve as a reference for future architects, helping them understand the trade-offs made and informing their decision-making process.
LOST view: Architecture Principles view
Identifier: http://data.europa.eu/dr8/egovera/NotImplementedArchitecturePrinciplesCatalogueGrouping
ABB name: egovera:NotImplementedArchitecturePrinciplesCatalogueGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-18
dct:identifier: http://data.europa.eu/dr8/egovera/NotImplementedArchitecturePrinciplesCatalogueGrouping
dct:title: Not Implemented Architecture Principles Catalogue Catalogue
Definition: Availability Requirements Catalogue ABB is a grouping that covers a range of non-functional requirements that are critical for the operation, maintenance, and usability of a system. This includes elements such as 'Deployment Stamps' and 'Geodes', which refer to the need for a system to have a timestamp or version number associated with each deployment, and the ability of a system to accurately determine the location of a user or device, respectively.
Source: EIRA Team Research
Additional information: The Availability Requirements Catalogue ABB is a comprehensive collection of non-functional requirements that are essential for the effective operation and maintenance of a system. 'Deployment Stamps' are crucial for tracking and identifying different versions of the system, enabling easy rollback to a previous version if necessary, and ensuring system stability and reliability. 'Geodes', on the other hand, refers to the system's ability to accurately pinpoint the location of a user or device, which is critical for systems that rely on location-based services. The accuracy and reliability of geodes can significantly impact the functionality and usability of the system, and in certain applications, can have serious consequences.
Example: Examples of application for the elements in the Availability Requirements Catalogue ABB include software development projects where 'Deployment Stamps' would be used to track different versions of the software, and navigation or emergency response systems where 'Geodes' would be used to provide precise location data.
LOST view: Digital Solution Non-Functional Requirements Catalogue view
Identifier: http://data.europa.eu/dr8/egovera/AvailabilityRequirementsCatalogueGrouping
ABB name: egovera:AvailabilityRequirementsCatalogueGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-17
dct:identifier: http://data.europa.eu/dr8/egovera/AvailabilityRequirementsCatalogueGrouping
dct:title: Availability Requirements Catalogue Catalogue
Definition: Legislation on Governance Interoperability (ENBI) is a grouping that covers various legislative documents and regulations that aim to establish and regulate the interoperability of governance systems, particularly in the digital realm. It includes legislation such as the Commission Recommendation 87/598/EEC of 8 December 1987 and Regulation (EU) 2021/694 of the European Parliament and of the Council of 29 April 2021.
Source: EIRA Team Research
Additional information: The ENBI catalogue includes legislative documents that aim to establish a framework for interoperability in governance. This includes the Commission Recommendation 87/598/EEC of 8 December 1987, which relates to a European Code of Conduct for electronic payment, establishing relations between financial institutions, traders, service establishments, and consumers. It also includes Regulation (EU) 2021/694 of the European Parliament and of the Council of 29 April 2021, which establishes the Digital Europe Programme and repeals Decision (EU) 2015/2240. This regulation is particularly relevant to the digital transformation of governance systems and has EEA relevance.
Example: An example of the application of the ENBI catalogue would be in the development of digital governance systems. The legislation contained within the catalogue would provide a legal framework for the interoperability of these systems, ensuring that they can work together efficiently and effectively. This could include, for example, the development of a digital payment system that complies with the Commission Recommendation 87/598/EEC, or the implementation of a digital governance project under the Digital Europe Programme established by Regulation (EU) 2021/694.
LOST view: LV-Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/LegislationOnGovernanceInteroperabilityGrouping
ABB name: egovera:LegislationOnGovernanceInteroperabilityGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-20
dct:identifier: http://data.europa.eu/dr8/egovera/LegislationOnGovernanceInteroperabilityGrouping
dct:title: Legislation On Governance Interoperability (ENBI) Catalogue
Definition: Dataspace Solutions ABB is a grouping that refers to actual solutions that facilitate the management, integration, and utilization of data in a secure and efficient manner. These solutions provide a platform for data sharing, collaboration, and analytics, enabling businesses to make data-driven decisions and gain competitive advantage.
Source: EIRA Team Research
LOST view: TVA-Data Space Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/BusinessAgnosticDataspaceSolutionsGrouping
ABB name: egovera:BusinessAgnosticDataspaceSolutionsGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-20
dct:identifier: http://data.europa.eu/dr8/egovera/BusinessAgnosticDataspaceSolutionsGrouping
dct:title: Dataspace SolutionsGrouping
Description: Business Agnostic Container Enablers ABB is a Grouping that refers to components and services that facilitate the creation, management, and deployment of applications using containerization. This includes open-source platforms and container engines like Docker, Podman, and LXC, which provide standardized, efficient, and secure methods for automating the deployment and scaling of applications across different computing environments.
Additional information: The Business Agnostic Container Enablers ABB includes Docker, an open-source platform that automates the deployment and scaling of applications using containerization. Containers are lightweight, isolated environments that package an application and its dependencies, allowing it to run consistently across different computing environments. It also includes Podman, an open-source container engine that enables users to manage and run containers on Linux-based systems. Lastly, it includes LXC (Linux Containers), an operating system-level virtualization method that allows multiple isolated Linux systems, known as containers, to run on a single host.
Example: Examples of application include using Docker to package an application and its dependencies into a container for consistent deployment across different computing environments, using Podman to manage and run containers on Linux-based systems, and using LXC to create and manage multiple isolated Linux systems on a single host.
Publisher: EIRA Team Research
LOST view: TVA-Containerization Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/BusinessAgnosticContainerSolutionsGrouping
EIRA traceability: eira:DigitalSolutionApplicationService
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-20
dct:identifier: http://data.europa.eu/dr8/egovera/BusinessAgnosticContainerSolutionsGrouping
dct:title: Container SolutionsGrouping
Definition: Observability and Monitoring Enablers ABB is a Grouping that refers to components and services that facilitate the collection, analysis, and interpretation of data to gain insights into the performance, health, and potential issues of various systems, networks, applications, and services. It includes the concepts of Observability and Monitoring, which involve tracking and understanding the internal state and behavior of a system through its external outputs, and observing and tracking the performance and health of IT infrastructure, respectively.
Source: EIRA Team Research
Source reference: N/A
Additional information: Observability and Monitoring Enablers ABB is a crucial aspect of IT operations, as it allows for the proactive identification and resolution of issues, ensuring optimal performance and reliability of IT infrastructure. Observability involves the collection and analysis of various metrics, logs, traces, and other data points, providing insights into the system's performance, health, and potential issues. On the other hand, Monitoring involves observing and tracking the performance, availability, and health of systems, networks, applications, and services, generating alerts or reports to facilitate informed decision-making and troubleshooting.
Example: Examples of Observability and Monitoring Enablers ABB in action include the use of application performance monitoring (APM) tools to track and analyze the performance of software applications, network monitoring tools to observe and manage network performance and reliability, and log management solutions to collect, analyze, and visualize log data for insights into system behavior and potential issues.
LOST view: TVA-Observability and Monitoring Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/ObservabilityAndMonitoringEnablersGrouping
ABB name: egovera:ObservabilityAndMonitoringEnablersGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-17
dct:identifier: http://data.europa.eu/dr8/egovera/ObservabilityAndMonitoringEnablersGrouping
dct:title: Observability And Monitoring EnablersGrouping
Description: Data Integration Solutions ABB is a grouping that refers to actual solutions that facilitate the process of combining data from different sources into a single, unified view. These solutions help organizations to effectively manage, govern, and integrate their data to improve efficiency, decision-making, and strategic planning.
Additional information: Data Integration Solutions ABB includes a wide range of digital services and solutions such as data warehousing, data migration, data consolidation, data synchronization, and data transformation. These solutions enable organizations to integrate data from various sources, including databases, applications, and systems, both within and outside the organization. They help in ensuring data consistency, accuracy, and accessibility, thereby improving data quality and reliability. Furthermore, they support real-time data integration, allowing organizations to make timely and informed decisions.
Example: Examples of application of Data Integration Solutions ABB include integrating data from different departments in a large organization to provide a unified view of the organization's operations, consolidating customer data from various channels in a retail business to improve customer service and personalization, and synchronizing data between an organization's on-premise systems and cloud-based applications to enhance data accessibility and scalability.
Publisher: EIRA Team Research
LOST view: TVA-Data Management Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/BusinessAgnosticDataIntegrationSolutionsGrouping
EIRA traceability: eira:DigitalSolutionApplicationService
EIRA concept: eira:SolutionBuildingBlock
Last modification: 2023-08-20
dct:identifier: http://data.europa.eu/dr8/egovera/BusinessAgnosticDataIntegrationSolutionsGrouping
dct:title: Data Integration SolutionsGrouping
Definition: Business Agnostic Data Format, Representation and Syntax Solutions (ABB) is a grouping that covers a wide range of technical specifications, standards, and formats designed to facilitate the representation, storage, and exchange of structured data in a machine-readable manner. These solutions are independent of specific business domains, making them applicable across various industries and use cases. They provide the necessary tools for businesses to create, integrate, and utilize structured data, promoting data interoperability and enabling the development of data-driven applications.
Source: EIRA Team Research
Additional information: The elements contained within this grouping include various data models, markup languages, data representation methods, and data interchange formats, among others. They cover a broad spectrum of data-related aspects, including data modeling (Common Data Model), data representation (XML, CSV, JSON), date and time representation (ISO 8601), secure and reliable document exchange (AS4 Profile of ebMS 3.0 v1.0), database archiving (SIARD 2.0 format for databases), RDF serialization (RDF Serialisations, Turtle, RDF-XML, N3, NQuads, TRiG), knowledge organization (SKOS, SKOS-XL), linked data representation (JSON-LD, JSON-L), semantic web data formats (LDES, RDF, RDF-S, OWL2, RML, SPARQL*, RDF*, SPARQL), geospatial data formats (geoJSON, KML, GML), code list definition and exchange (Genericode), and SPARQL results representation (SPARQL-CSV).
Example: Examples of application of these solutions include: creating and sharing RDF data using Turtle format, representing and exchanging geospatial data using GeoJSON or KML, defining and exchanging code lists using Genericode, representing date and time information in a standardized format using ISO 8601, archiving relational databases using SIARD 2.0 format, and querying semantic data using SPARQL.
LOST view: SV-Functional Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/BusinessAgnosticDataFormatRepresentationAndSyntaxSolutionsGrouping
ABB name: egovera:BusinessAgnosticDataFormatRepresentationAndSyntaxSolutionsGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/egovera/BusinessAgnosticDataFormatRepresentationAndSyntaxSolutionsGrouping
Name: Business Agnostic Data Format, Representation And Syntax Solutions Catalogue
Interoperability Layer: Semantic
Definition: Business Agnostic Digital Public Services Catalogue ABB is a grouping that refers to the actual catalogue of digital public services that facilitates the seamless integration and interoperability of various IT systems and services provided by the European Commission. It encompasses a wide range of elements, each with a specific role in enhancing the efficiency, accessibility, and user experience of digital public services, while promoting interoperability across different platforms and systems.
Source: EIRA Team Research
Additional information: The Business Agnostic Digital Public Services Catalogue ABB includes elements such as ePayment, Audit, eArchiving, eDelivery, eQualification, eTranslation, Data Extraction, Transformation and Loading, Data Analytics, Delegation of Power, Workflow Management, Knowledge Management, eNotification, eIdentification, Digital Collaboration, Waiting list Management, Open Data Management, Anonymisation, eSignature, Secure Access Control, Content Management, Log Management, eInvoicing, eTendering, Contact Management, Forms Management, Data Exchange, Digital Inmutability, Business Intelligence, Compliance Testing, Data Space, Data Space Participant, and Digital Asset Management. Each of these elements plays a crucial role in ensuring the smooth functioning and interoperability of digital public services within the European Commission.
Example: For instance, ePayment allows users to make secure and convenient electronic payments for various services provided by the Commission. Similarly, eArchiving ensures the preservation and maintenance of digital information in a standardized and accessible manner. On the other hand, Data Analytics enables the Commission to analyze and interpret large volumes of data to gain valuable insights and make informed decisions. Meanwhile, Secure Access Control ensures authorized and secure access to digital resources and services. These are just a few examples of how the elements within the Business Agnostic Digital Public Services Catalogue ABB contribute to the overall efficiency and effectiveness of digital public services within the European Commission.
LOST view: TVA-Data Space Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/BusinessAgnosticDigitalPublicServicesCatalogueGrouping
EIRA traceability: eira:DigitalPublicServiceCatalogueBusinessObject
ABB name: egovera:BusinessAgnosticDigitalPublicServicesCatalogueGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-17
dct:identifier: http://data.europa.eu/dr8/egovera/BusinessAgnosticDigitalPublicServicesCatalogueGrouping
dct:title: Business Agnostic Digital Public Services Catalogue Catalogue
Definition: Digital Solution Usability Architecture Decision Catalogue (DSUADC) is a grouping that covers a collection of architectural decision records (ADRs) that focus on the usability aspects of a digital solution's architecture. These decisions involve considerations about adequacy recognition, learning, operability, user interface, and accessibility.
Source: EIRA Team Research
Additional information: The DSUADC is a comprehensive catalogue that documents crucial decisions made about the usability aspects of a digital solution's architecture. Each element in the catalogue represents a specific area of focus. 'Adequacy Recognition' refers to decisions about how well the solution meets user needs and expectations. 'Learning' covers decisions about how users learn to use the solution. 'Operability' involves decisions about the ease of operating the solution. 'User Interface' refers to decisions about the design and functionality of the user interface. 'Accessibility' covers decisions about making the solution accessible to all users, including those with disabilities.
Example: For instance, an ADR under 'Adequacy Recognition' might document the decision to use a particular user feedback system to ensure the solution meets user needs. An ADR under 'Learning' might cover the decision to include interactive tutorials to help new users learn how to use the solution. An ADR under 'Operability' might document the decision to use a specific technology to ensure smooth operation of the solution. An ADR under 'User Interface' could cover the decision to use a specific design pattern for the user interface. Lastly, an ADR under 'Accessibility' might document the decision to follow specific accessibility standards to make the solution usable by people with disabilities.
LOST view: Digital Solution Architecture Decisions Catalogue view
Identifier: http://data.europa.eu/dr8/egovera/DigitalSolutionUsabilityArchitectureDecisionCatalogueGrouping
ABB name: egovera:DigitalSolutionUsabilityArchitectureDecisionCatalogueGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-18
dct:identifier: http://data.europa.eu/dr8/egovera/DigitalSolutionUsabilityArchitectureDecisionCatalogueGrouping
dct:title: Digital Solution Usability Architecture Decision Catalogue Catalogue
Definition: Blockchain Infrastructure Enablers ABB is a Grouping of a set of components and services that permit building a digital ledger infrastructure of interconnected nodes to facilitate a trustworthy environment to share data.
Source: European Comission
Source reference: https://digital-strategy.ec.europa.eu/en/policies/european-blockchain-services-infrastructure
Synonym:
Additional information:
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): OpenCHAIN is an open-source blockchain platform with distributed ledger technology. This blockchain company is suitable for organizations managing digital assets in secure and robust ways. Blockchain technology does not require fees for mining and the Bitcoin blockchain is significant for its immutability. https://www.openchainproject.org/
Interoperability Dimension: Structural IoP
LOST view: Technical view - infrastructure
Interoperability Saliency: Blockchain Infrastructure Enablers ABB is salient for organizational interoperability due to it setting up the rules for generating a trustworthy network that permits (i) sharing information related to public services securely and privately, and (ii) ensuring the public information is consistent in time.
Identifier: http://data.europa.eu/dr8/BlockchainInfrastructureEnablersGrouping
ABB name: eira:BlockchainInfrastructureEnablersGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/BlockchainInfrastructureEnablersGrouping
Interoperability Layer: TechnicalInfrastructure
Definition: Shared Infrastructure Content ABB is a Grouping setting infrastructure (re)usable resources, with convergence power, aimed at consolidating the IT framework to support public policy objectives. It provides a shared IT environment, including hardware, software, and associated processes, ensuring secure and efficient resource utilization across multiple stakeholders while maintaining strict data and operational separation.
Source: Joinup
Source reference: https://joinup.ec.europa.eu/collection/nifo-national-interoperability-framework-observatory/glossary/term/shared-infrastructure
Last modification: 2024-01-08
Identifier: http://data.europa.eu/dr8/SharedInfrastructureContentGrouping
LOST view: Technical view - infrastructure
EIRA concept: eira:ArchitectureBuildingBlock
ABB name: eira:SharedInfrastructureContentGrouping
Interoperability Saliency: Shared Infrastructure Content ABB is a key interoperability enabler (*) for structural, behavioural and governance interoperability. It is salient for technical interoperability because it determines the tools and services that can be used by stakeholders or other digital services to interconnect services and data. This ABB also technically establish security standards compliance to deliver such public services.
Interoperability Dimension: Structural IoP
Viewpoint: Highlevel viewpoint
Additional identifier: http://data.europa.eu/dr8/SharedInfrastructureContentGrouping
EIF Layer: TechnicalInfrastructure
Definition: Security Data Policy Catalogue ABB is a grouping that covers a range of policies and guidelines related to the security and management of data within an organization. The catalogue includes elements such as 'Permission Policy', which are designed to govern the authorization and access rights granted to individuals or roles within a system or organization.
Source: EIRA Team Research
Additional information: The Security Data Policy Catalogue ABB is a comprehensive collection of data security policies, each with its own specific purpose and application. For instance, the 'Permission Policy' is a set of rules, guidelines, and controls that dictate the specific permissions and privileges assigned to different entities within an organization. This policy is crucial in ensuring appropriate access control and maintaining the confidentiality, integrity, and availability of resources or information. The catalogue serves as a reference and guide for organizations to establish, implement, and manage their data security policies effectively.
Example: An example of an application of the Security Data Policy Catalogue ABB is in the management of user permissions within an organization. The 'Permission Policy' element of the catalogue would be used to define the access rights of different roles within the organization, ensuring that each individual has the appropriate level of access to the system and its resources. This could include specifying that only certain roles have the ability to view, edit, or delete specific data, thereby protecting the integrity and confidentiality of the data.
LOST view: SV-Governance Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/SecurityDataPolicyCatalogueGrouping
ABB name: egovera:SecurityDataPolicyCatalogueGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-11-20
Identifier: http://data.europa.eu/dr8/egovera/SecurityDataPolicyCatalogueGrouping
Name: Security Data Policy Catalogue Catalogue
Interoperability Layer: Semantic
Definition: Business Agnostic Organisational Agreement Solutions (BAOAS) is a grouping that refers to the actual catalogue of specifications, agreements and/or contracts that facilitates the establishment of standardised business practices across various industries. This catalogue includes a variety of elements, such as codes of conduct, guidelines, and best practices, which are designed to improve operational efficiency, promote ethical business practices, and enhance environmental sustainability.
Source: EIRA Team Research
Additional information: The elements contained within the BAOAS catalogue are diverse and cater to different aspects of business operations. For instance, it includes the 'Code of Conduct for Energy Efficiency in Data Centres', a voluntary code developed by the European Commission's Joint Research Centre. This code aims to improve the energy efficiency and environmental sustainability of data centres by providing guidelines and best practices for data centre operators to reduce their environmental impact. The BAOAS catalogue is designed to be business agnostic, meaning it can be applied across various industries and business models. It serves as a valuable resource for organisations seeking to adopt standardised, ethical, and sustainable business practices.
Example: An example of the application of BAOAS could be a data centre operator utilising the 'Code of Conduct for Energy Efficiency in Data Centres' to improve their energy efficiency. They could implement the guidelines and best practices outlined in the code, such as optimising cooling systems or using energy-efficient hardware, to reduce their environmental impact. Similarly, a company in a different industry could use other elements within the BAOAS catalogue to standardise their business practices and enhance their operational efficiency.
LOST view: Organisational view
Identifier: http://data.europa.eu/dr8/egovera/BusinessAgnosticOrganisationalAgreementSolutionsGrouping
EIRA traceability: eira:TechnicalAgreementContract
ABB name: egovera:BusinessAgnosticOrganisationalAgreementSolutionsGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-17
dct:identifier: http://data.europa.eu/dr8/egovera/BusinessAgnosticOrganisationalAgreementSolutionsGrouping
dct:title: Business Agnostic Organisational Agreement Solutions
Definition: Customs Legislation on Structural Interoperability (NBI) ABB is a grouping that covers the legal and regulatory framework that governs the exchange of data and information between different systems, platforms, and applications within the customs environment. This includes laws, regulations, and guidelines that ensure seamless integration and interaction between different systems for efficient customs operations.
Source: EIRA Team Research
Additional information: The Customs Legislation on Structural Interoperability (NBI) ABB is crucial in facilitating international trade. It ensures that different systems can effectively communicate and exchange data, thereby enhancing efficiency, reducing errors, and promoting transparency in customs operations. This legislation covers various aspects including data formats, communication protocols, security standards, and data integrity checks among others. It is applicable to all stakeholders involved in customs operations including customs authorities, traders, freight forwarders, and other government agencies.
Example: An example of application of the Customs Legislation on Structural Interoperability (NBI) ABB is in the implementation of a Single Window system. This system allows traders to submit all required documents and data for customs clearance through a single entry point. The legislation ensures that the Single Window system can seamlessly interact with other systems such as the traders' systems, freight forwarders' systems, and other government agencies' systems to facilitate efficient data exchange and processing.
LOST view: LV-Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/CustomsLegislationOnStructuralInteroperabilityGrouping
ABB name: egovera:CustomsLegislationOnStructuralInteroperabilityGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-20
dct:identifier: http://data.europa.eu/dr8/egovera/CustomsLegislationOnStructuralInteroperabilityGrouping
dct:title: Customs Legislation On Structural Interoperability (NBI)
Definition: Legislation on Structural Interoperability (NBI) is a grouping that covers national schemas on eIdentification, cybersecurity, eDelivery, and access to base registries. These schemas provide a framework for the implementation of digital services and security measures in a national context.
Source: EIRA Team Research
Additional information: The Legislation on Structural Interoperability (NBI) is a comprehensive catalogue of information entities that provide the legal and structural framework for the implementation of digital services and security measures at a national level. It includes the National Schema on eIdentification, which outlines the standards and protocols for digital identification processes. The National Schema on Cybersecurity provides the guidelines for implementing cybersecurity measures and protocols. The National Schema on eDelivery outlines the framework for electronic delivery of services, while the National Schema on the access to Base Registries provides the guidelines for accessing base registries in a digital environment.
Example: For example, a country implementing a new digital identification system would refer to the National Schema on eIdentification within the Legislation on Structural Interoperability (NBI) to ensure they are following the correct standards and protocols. Similarly, if a country is looking to enhance its cybersecurity measures, it would refer to the National Schema on Cybersecurity for guidance.
LOST view: LV-Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/LegislationOnStructuralInteroperabilityGrouping
ABB name: egovera:LegislationOnStructuralInteroperabilityGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-20
dct:identifier: http://data.europa.eu/dr8/egovera/LegislationOnStructuralInteroperabilityGrouping
dct:title: Legislation On Structural Interoperability (NBI) Catalogue
Definition: Content Delivery Infrastructure Enablers ABB is a Grouping that refers to the set of components and services that enable the delivery of digital content such as web pages, videos, images, and audio files to end-users
Source: Inspired in the definition provided by relebant cloud service organizations.
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): DIGIT/C Hosting Service - DIGIT/C offers a high availability and high performance hosting infrastructure that is being comprised, among other elements, of back-end web server instances and application servers for hosting and serving both static and dynamic sites. http://ec.europa.eu/ipg/build/infrastructure/index_en.htm
Interoperability Dimension: Structural IoP
LOST view: Technical view - infrastructure
Interoperability Saliency: Content Delivery Infrastructure Enablers ABB is salient for semantic and technical interoperability because it provides ICT systems to manipulate, reuse and share batch and streaming data related to public administration services.
Identifier: http://data.europa.eu/dr8/ContentDeliveryInfrastructureEnablersGrouping
ABB name: eira:ContentDeliveryInfrastructureEnablersGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/ContentDeliveryInfrastructureEnablersGrouping
Interoperability Layer: TechnicalInfrastructure
Definition: Computing Infrastructure Enablers ABB is a Grouping that refers to components and services that provide the development, deployment, and management of virtual and computing infrastructure
Source: Inspired in Redhat
Source reference: https://www.redhat.com/en/topics/virtualization/what-is-a-virtual-machine
Synonym:
Additional information:
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): DIGIT/C Hosting Service - DIGIT/C offers a high availability and high performance hosting infrastructure that is being comprised, among other elements, of back-end web server instances and application servers for hosting and serving both static and dynamic sites. http://ec.europa.eu/ipg/build/infrastructure/index_en.htm
IoP Dimension:
LOST view: Technical view - Infrastructure
Interoperability saliency: The Computing Infrastructure Enablers ABB is salient for organizational and technical interoperability due to it providing (i) mechanisms to ensure the correct publication of public administration digital services, and (ii) physical elements that permit to host of public administration services in a standardised manner.
Identifier: http://data.europa.eu/dr8/ComputingInfrastructureEnablers
eira:ID: http://data.europa.eu/dr8/ComputingInfrastructureEnablers
ABB name: eira:ComputingInfrastructureEnablers
EIRA concept: eira:ArchitectureBuildingBlock
Last modification:
Definition: Business Agnostic Technical Governance Catalogue (ABB) is a grouping that covers the various forms of blockchain governance. These forms include Hybrid Blockchain Governance, Public Blockchain Governance (permissionless), Private Blockchain Governance (permissioned), and Blockchain Governance in general.
Source: EIRA Team Research
Additional information: The Business Agnostic Technical Governance Catalogue is a comprehensive collection of different types of blockchain governance. It includes Hybrid Blockchain Governance, which combines aspects of both public and private blockchains. Public Blockchain Governance (permissionless) is a type of blockchain where anyone can join and participate in the decision-making process. Private Blockchain Governance (permissioned) is a type of blockchain where only selected entities are allowed to participate in the consensus process. Lastly, Blockchain Governance in general refers to the system of rules and procedures that regulate the operation and maintenance of a blockchain network.
Example: An example of Hybrid Blockchain Governance is the Ripple network, which combines aspects of both public and private blockchains. It allows certain nodes to participate in the consensus process, while also allowing anyone to hold and transfer its native cryptocurrency, XRP.
Bitcoin is a prime example of Public Blockchain Governance (permissionless). Anyone can join the network, participate in the mining process, and have a say in the decision-making process.
An example of Private Blockchain Governance (permissioned) is the Hyperledger Fabric, where only selected entities are allowed to participate in the consensus process.
Ethereum is an example of Blockchain Governance. It has a system of rules and procedures that regulate the operation and maintenance of the network, including the process of decision-making and the implementation of changes to the protocol.
LOST view: TVI-Governance Architecture Principles
Identifier: http://data.europa.eu/dr8/egovera/BusinessAgnosticTechnicalGovernanceCatalogueGrouping
ABB name: egovera:BusinessAgnosticTechnicalGovernanceCatalogueGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-20
dct:identifier: http://data.europa.eu/dr8/egovera/BusinessAgnosticTechnicalGovernanceCatalogueGrouping
dct:title: Business Agnostic Technical Governance Catalogue
Definition: Application Integration Infrastructure Enablers ABB is a Grouping that refers to the set of components and services facilitating the integration of disparate applications and systems within an organization
Source: Inspired in European Alliance for Industrial Data, Edge and Cloud
Source reference: https://digital-strategy.ec.europa.eu/en/policies/cloud-alliance
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): API Manager, WSO2 API Manager is a complete platform for building, integrating, and exposing your digital services as managed APIs in the cloud, on-premise, and hybrid architectures to drive your digital transformation strategy. https://apim.docs.wso2.com/en/latest/
Interoperability Dimension: Structural IoP
LOST view: Technical view - infrastructure
Interoperability Saliency: Application Integration Infrastructure Enablers ABB is salient for semantic and technical interoperability because it provides mechanisms and assets to expose open APIs regarding public services that permit machines to discover and understand available public services. Also, this ABB facilitates data consumption and sharing through these public services exposed.
Identifier: http://data.europa.eu/dr8/ApplicationIntegrationInfrastructureEnablersGrouping
ABB name: eira:ApplicationIntegrationInfrastructureEnablersGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/ApplicationIntegrationInfrastructureEnablersGrouping
Interoperability Layer: TechnicalInfrastructure
Definition: Customs Data Exchange Solutions ABB is a Grouping that covers a range of solutions designed to facilitate the exchange of customs data between different entities. The main objective of these solutions is to streamline the processes of data management and make all relevant information readily available. The European Commission has designed a centralised system for this purpose, known as the INF SP System.
Source: EIRA Team Research
Additional information: Customs Data Exchange Solutions ABB includes the 'Central system for the standardised exchange of information', also known as the INF SP System. This system is designed to standardise the exchange of information and streamline the processes of data management. It aims to make all INF data available in a centralised manner, thereby improving efficiency and reducing the potential for errors. The system is designed by the European Commission and is part of their efforts to improve customs procedures across the EU.
Example: An example of the application of the Customs Data Exchange Solutions ABB is the use of the INF SP System by customs authorities across the EU. This system allows for the standardised exchange of information, making it easier for these authorities to access and manage the data they need. This can help to speed up customs procedures and improve the accuracy of the data being used.
LOST view: TVA-Customs Data Exchange Enablers [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/CustomsDataExchangeSolutionsGrouping
ABB name: egovera:CustomsDataExchangeSolutionsGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-20
dct:identifier: http://data.europa.eu/dr8/egovera/CustomsDataExchangeSolutionsGrouping
dct:title: Customs Data Exchange Solutions
Definition: Digital Public Service Strategy (Public Policy Cycle) Principle Catalogue ABB is a grouping that covers a range of principles and strategies related to the implementation and management of digital public services. These principles include accessibility, accountability, best fit public service implementation orientation, care from cradle to grave, data sovereignty, deployment fit (Cloud-first approach), digital first, digital partnership, digital sovereignty and autonomy, evidence-based public policy, social participation, transparency of internal information systems, and transparency of the administrative environment.
Source: EIRA Team Research
Additional information: The catalogue is a comprehensive collection of principles and strategies that guide the implementation, management, and evolution of digital public services. 'Accessibility' ensures services are available to all citizens, 'Accountability' ensures responsible use of resources and power, 'Best fit Public Service Implementation Orientation' guides the implementation process, 'Care from cradle to grave' ensures lifelong support for citizens, 'Data Sovereignty' ensures citizens' data rights, 'Deployment fit (Cloud-first approach)' guides the deployment of services, 'Digital First' prioritizes digital solutions, 'Digital Partnership' encourages collaboration, 'Digital sovereignty and autonomy' ensures digital independence, 'Evidence based Public Policy' ensures policies are based on factual data, 'Social participation' encourages citizen involvement, 'Transparency of internal information systems' ensures openness about system operations, and 'Transparency of the administrative environment' ensures openness about administrative processes.
Example: An example of 'Accessibility' could be a government website that is designed to be user-friendly for all citizens, including those with disabilities. An example of 'Accountability' could be a public service agency that regularly publishes reports on its spending and activities. An example of 'Best fit Public Service Implementation Orientation' could be a government agency that carefully selects the most suitable software for its needs, rather than simply choosing the most popular or cheapest option. An example of 'Care from cradle to grave' could be a government health service that provides care for citizens from birth to old age.
LOST view: Architecture Principles view
Identifier: http://data.europa.eu/dr8/egovera/DigitalPublicServiceStrategyPrincipleCatalogueGrouping
ABB name: egovera:DigitalPublicServiceStrategyPrincipleCatalogueGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-20
dct:identifier: http://data.europa.eu/dr8/egovera/DigitalPublicServiceStrategyPrincipleCatalogueGrouping
dct:title: Digital Public Service Strategy (Public Policy Cycle) Principle Catalogue Catalogue
Definition: Business Agnostic Controlled Vocabulary Solutions (BACVS) is a grouping that covers a range of vocabularies and models designed to standardize and simplify data and information exchange across various domains. These vocabularies are context-neutral, reusable, and extensible, making them applicable across different business environments and sectors.
Source: EIRA Team Research
Additional information: The BACVS includes elements such as the eGovernment Core Vocabularies, Core Assessment Vocabulary, Core Standards and Specifications Vocabulary, W3C Profiles Vocabulary, and EuroVoc. These vocabularies are designed to capture the fundamental characteristics of a data entity, define assessments of assets, facilitate information exchange related to software standards and specifications, allow machine-readable descriptions of profiles of specifications for information resources, and provide a multilingual and multidisciplinary thesaurus for the EU, respectively. They are all domain-agnostic, meaning they can be applied across various business sectors and environments.
Example: These vocabularies can be used by government agencies to standardize data exchange and communication, ensuring consistency and interoperability across different systems and platforms.
This vocabulary can be used by businesses to assess various types of assets based on specific criteria, ensuring a standardized and comprehensive assessment process.
Software developers can use this vocabulary to facilitate information exchange related to software standards and specifications, promoting interoperability and standardization.
This vocabulary can be used by organizations to create machine-readable descriptions of profiles of specifications for information resources, promoting transparency and accessibility.
EU institutions can use EuroVoc to describe the content of documents in EUR-Lex, promoting consistency and clarity in document classification and retrieval.
LOST view: SV-Controlled Vocabulary [Motivation]
Identifier: http://data.europa.eu/dr8/egovera/BusinessAgnosticControlledVocabularySolutionsGrouping
ABB name: egovera:BusinessAgnosticControlledVocabularySolutionsGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-20
dct:identifier: http://data.europa.eu/dr8/egovera/BusinessAgnosticControlledVocabularySolutionsGrouping
dct:title: Business Agnostic Controlled Vocabulary Solutions
Definition: Database Infrastructure Enablers ABB is a Groping that enables the tools and technology services for efficient management and operation of data under a storage system.
Source: Inspired in Gartner
Source reference: https://www.gartner.com/en/information-technology/glossary/dbms-database-management-system
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): MySQL manager, an SQL for MySQL. https://www.sqlmanager.net/products/mysql/manager
Interoperability Dimension: Structural IoP
LOST view: Technical view - infrastructure
Interoperability Saliency: Database Infrastructure Enablers ABB is salient for semantic and organization interoperability because it set up (i) tools to manage and manipulate data considering different types of data stores, (ii) establishes a data exchange mechanism to facilitate data understanding, (iii) manage data provenance through the public services interaction with the heterogeneous datastores.
Identifier: http://data.europa.eu/dr8/DatabaseInfrastructureEnablersGrouping
ABB name: eira:DatabaseInfrastructureEnablersGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/DatabaseInfrastructureEnablersGrouping
Interoperability Layer: TechnicalInfrastructure
Definition: Digital Public Service Design Principle Catalogue ABB is a grouping that covers a range of principles and guidelines aimed at shaping the design and implementation of digital public services. These principles encompass various aspects including administrative simplification, carbon-dioxide e-footprint impact awareness, code of ethics compliance, data portability, EU legislation compliance, integrated user experience, multilingualism, privacy, proactiveness, service orientation, technology neutrality, and user-centricity among others.
Source: EIRA Team Research
Additional information: The Digital Public Service Design Principle Catalogue ABB is a comprehensive collection of principles that guide the design and delivery of digital public services. These principles are aimed at ensuring that digital services are user-centric, efficient, ethical, and compliant with relevant legislation. They cover a broad spectrum of considerations from administrative simplification which aims to reduce bureaucratic processes and make public services more accessible, to carbon-dioxide e-footprint impact awareness which encourages the design of digital services that are environmentally friendly. Other principles like data portability and privacy ensure that users' data is handled responsibly and securely. The catalogue also includes principles like multilingualism and integrated user experience which aim to make digital services more inclusive and user-friendly.
Example: An example of application of these principles can be seen in the design of a digital public service like an online tax filing system. The system would need to be designed with user-centricity in mind, ensuring it is easy to use for all citizens. It would also need to comply with EU legislation and a code of ethics, ensuring data is handled securely and responsibly. The system should also be designed with an awareness of its carbon-dioxide e-footprint, aiming to minimise its environmental impact. Furthermore, the principle of administrative simplification would be applied to make the tax filing process as straightforward and efficient as possible.
LOST view: Architecture Principles view
Identifier: http://data.europa.eu/dr8/egovera/DigitalPublicServiceDesignPrincipleCatalogueGrouping
ABB name: egovera:DigitalPublicServiceDesignPrincipleCatalogueGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-18
dct:identifier: http://data.europa.eu/dr8/egovera/DigitalPublicServiceDesignPrincipleCatalogueGrouping
dct:title: Digital Public Service Design Principle Catalogue Catalogue
Definition: Identity and Access Infrastructure Enablers ABB is a Grouìng of a set of components and services that provide the underlying functionality to implement identity and access management solutions
Source: Inspired in CAMSS
Source reference: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss
Example: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): Lightweight Directory Access Protocol can be implemented in multiple platforms or systems, allowing to integrating an organisatio'n LDAP-enabled identity management service to other platforms such as Drupal. https://www.drupal.org/docs/contributed-modules/lightweight-directory-access-protocol-ldap
Interoperability Dimension: Structural IoP
LOST view: Technical view - infrastructure
Interoperability Saliency: Identity and Access Infrastructure Enablers ABB is Salient for the technical, organizational and semantic interoperability because it provides (i) the setup and implementation of rules to access public services, (ii) the tools and mechanism to identify unequivocally organizations or individuals, (iii) the tools and mechanisms to facilitate the access and use of the public services
Identifier: http://data.europa.eu/dr8/IdentityAndAccessInfrastructureEnablersGrouping
ABB name: eira:IdentityAndAccessInfrastructureEnablersGrouping
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2024-01-28
Identifier: http://data.europa.eu/dr8/IdentityAndAccessInfrastructureEnablersGrouping
Interoperability Layer: TechnicalInfrastructure
Definition: Facility Location ABB is a Location conceptual or physical place or position where a bussiness organization is placed.
Source: Inspired in Archimate
Source reference: https://pubs.opengroup.org/architecture/archimate3-doc/chap04.html
LOST view: Technical view - Infrastructure
Interoperability saliency: Facility Location ABB is salient for the organizational and technical interoperability because of (i) it determines the interlink between public administration business process removing existing barriers; (ii) set up needed mechanism between IT systems to remove fragmentation in service delivery.
Identifier: http://data.europa.eu/dr8/FacilityLocation
eira:ID: http://data.europa.eu/dr8/FacilityLocation
ABB name: eira:FacilityLocation
EIRA concept: eira:ArchitectureBuildingBlock
This relationship has been converted from "aggregation" to "association"
This relationship has been converted from "composition" to "association"
This relationship has been converted from "realization" to "association"
A [Public Service Catalogue] documents a [Public Service]
a [Data Policy] influences [Data]
A [Representation] represents [Data]
This relationship has been converted from "composition" to "association"
This relationship has been converted from "aggregation" to "association"
A [Public Service] implements a [Public Policy]
NARRATIVE:
The TVA-Analytics Enablers [Motivation] view extends Technical view - application and provides a comprehensive framework for leveraging the Business Agnostic Digital Public Services Catalogue and the Analytics Enablers.
The Business Agnostic Digital Public Services Catalogue is a Diagram Model-group ABB that encompasses the Data Analytics Business Service ABB. This service provides digital public services related to data analytics.
The Analytics Enablers is a Grouping ABB that refers to components and services that serve any current or future Digital Service Infrastructure (DSI) requiring data analysis capabilities. This grouping includes several Application Service ABBs: Big Data Analytics, Data Analytics, Business Intelligence, and Smart Queue Management.
The Big Data Analytics Application Service refers to a software application or platform that leverages advanced analytics techniques to process and analyze large and complex datasets, commonly known as big data. It enables organizations to derive valuable insights, identify patterns, trends, and correlations, and make data-driven decisions. The service typically includes data ingestion, storage, processing, and visualization capabilities, as well as advanced analytics techniques such as machine learning, natural language processing, and predictive modeling.
The Data Analytics ABB is an Application Service that enables the use of procedures to analyze data and extract insights that can be used to improve business decision-making, optimize business processes, and drive innovation.
The Business Intelligence Application Service ABB is another component of the Analytics Enablers, providing business intelligence capabilities.
Lastly, the Smart Queue Management Application Service ABB is part of the Analytics Enablers, providing smart queue management capabilities.
The motivation behind this view is to provide a comprehensive framework that leverages the capabilities of the Business Agnostic Digital Public Services Catalogue and the Analytics Enablers to enhance data analysis capabilities and support data-driven decision-making in the organization.
NARRATIVE:
The TVA-Knowledge Discovery Enablers [Motivation] view extends Technical view - application and provides a comprehensive framework for leveraging the elements of the JSON provided. The view is primarily composed of two main elements: the 'Business Agnostic Knowledge Discovery Service' and the 'Knowledge Discovery Enablers'.
The 'Business Agnostic Knowledge Discovery Service' is a Diagram Model-group ABB that encapsulates the 'Knowledge Management' Business Service ABB. This service is described as a digital public service that is dedicated to the management of knowledge. However, the JSON does not provide any sub-elements or further details about this service.
The 'Knowledge Discovery Enablers' is a Grouping ABB that refers to components and services that facilitate the process of discovering insights and knowledge from data. This group includes four Application Service ABBs: 'Knowledge Discovery', 'Knowledge Management', 'Knowledge Exchange', and 'Vocabulary Hub'.
The 'Knowledge Discovery' service is described as a highly complex process where a lot of data manipulation tools with different characteristics have to be used together to reach the goal of previously unknown, potentially useful information extraction.
The 'Knowledge Management' service is a software application or service that supports the processes of capturing, organizing, storing, retrieving, and sharing knowledge within an organization. It provides functionalities and tools to facilitate knowledge creation, acquisition, categorization, search, collaboration, and dissemination. This service enables employees or users to access and leverage the organization's knowledge assets effectively, fostering innovation, decision-making, and continuous learning.
The 'Knowledge Exchange' service is not described in detail in the JSON, but it can be inferred that it is related to the exchange or sharing of knowledge.
The 'Vocabulary Hub' service is also not described in detail in the JSON. However, it can be inferred that it is a service related to managing and providing access to a vocabulary or set of terminologies used within the organization or system.
In summary, the TVA-Knowledge Discovery Enablers [Motivation] view provides a comprehensive framework for leveraging various services and components that enable the discovery, management, exchange, and use of knowledge in an organization.
NARRATIVE:
The TVA-Customs Risk Analysis Enablers [Motivation] view extends Technical view - application and provides a comprehensive framework for leveraging the capabilities of the 'Customs Risk Management and Analysis Enablers' and 'Customs Digital Public Services'.
The 'Customs Risk Management and Analysis Enablers' is a Grouping ABB that encapsulates the 'Risk analysis' Application Service ABB. This service refers to the systematic assessment and evaluation of potential risks associated with trade transactions and customs operations. It involves leveraging data analytics, algorithms, and risk management methodologies to identify patterns, anomalies, and potential risks in real-time. By analyzing factors such as shipment details, trader profiles, country of origin, and historical data, risk analysis enables customs authorities to prioritize inspections, allocate resources effectively, and mitigate risks related to smuggling, fraud, security threats, and non-compliance. This digital solution service enhances customs efficiency, facilitates secure trade, and supports informed decision-making to ensure effective risk management within the customs domain.
The 'Customs Digital Public Services' is a Diagram Model-group ABB that includes the 'Risk analysis' Business Service ABB. This service is a digital public service that is part of the customs digital public services.
The relationship between these two elements is that the 'Risk analysis' Application Service ABB under 'Customs Risk Management and Analysis Enablers' is the technical enabler for the 'Risk analysis' Business Service ABB under 'Customs Digital Public Services'. This means that the application service provides the necessary technical capabilities and functionalities that enable the business service to deliver its intended value to the users.
The motivation for this arrangement is to ensure that the customs authorities can effectively manage and mitigate risks associated with trade transactions and customs operations by leveraging advanced data analytics and risk management methodologies. This not only enhances customs efficiency and facilitates secure trade but also supports informed decision-making.
NARRATIVE:
The TVA-Customs Data Management Enablers [Motivation] view extends Technical view - application and provides a comprehensive framework for leveraging digital technologies to enhance the management and oversight of customs processes. This view is divided into two main elements: "Customs Data Management Enablers" and "Customs Digital Public Services".
The "Customs Data Management Enablers" group comprises two application services: "Preservation of cargo information" and "Laboratories management". The "Preservation of cargo information" service refers to the secure and systematic management of data related to the movement and handling of goods during customs processes. This service involves the digital capture, storage, and retrieval of cargo-related information, such as shipping details, transport documents, customs declarations, and inspection reports. By leveraging digital technologies, including data management systems, document repositories, and secure data transmission protocols, this service ensures the integrity, traceability, and accessibility of critical data throughout the customs clearance process.
The second service, "Laboratories management", refers to the implementation of digital tools and systems to efficiently manage and oversee customs laboratories' operations. This service involves the automation and optimization of laboratory processes, such as sample tracking, test management, result analysis, and quality assurance. By leveraging digital technologies like laboratory information management systems (LIMS), electronic data capture, and data analytics, this service enhances the accuracy, traceability, and efficiency of laboratory testing and analysis within the customs environment.
The "Customs Digital Public Services" group includes two business services: "Preservation of cargo control" and "Laboratories registry management". These services represent the digital public services provided by the customs department to facilitate cargo control and manage laboratories registry. The exact nature and functionality of these services are not detailed in the provided JSON.
In summary, the TVA-Customs Data Management Enablers [Motivation] view presents a framework that leverages digital technologies to enhance customs processes. It highlights the importance of data management and digital tools in ensuring efficient and effective customs operations.
not clear about the 2nd and 3rd.
NARRATIVE:
The TVA-Customs Process Streamlining and Efficiency Enablers [Motivation] view extends Technical view - application and provides a comprehensive framework for leveraging digital tools and technologies to enhance customs operations and facilitate trade. This view is composed of two main elements: 'Customs Process Streamlining and Efficiency Enablers' and 'Customs Digital Public Services'.
The 'Customs Process Streamlining and Efficiency Enablers' is a Grouping ABB that encompasses three Application Service ABBs: 'Expeditions controls', 'People and skill allocation and distribution', and 'Guarantee'.
'Expeditions controls' refers to the use of digital tools and technologies to enhance the monitoring, tracking, and control of goods throughout the transportation and logistics process. This service involves the implementation of digital systems, such as Electronic Data Interchange (EDI), Global Positioning System (GPS), and Internet of Things (IoT) devices, to enable real-time visibility and management of expeditions.
'People and skill allocation and distribution' refers to the utilization of digital tools and platforms to efficiently allocate, manage, and distribute human resources and skills within the customs organization. This service involves the implementation of digital workforce management systems that enable customs authorities to streamline resource allocation, monitor staff availability, assign tasks, and track skill sets and competencies.
'Guarantee' refers to the electronic management and administration of customs guarantees provided by traders or financial institutions to ensure compliance with customs requirements. This service involves the implementation of digital platforms and systems that enable efficient guarantee management, such as tracking guarantee amounts, issuing and processing electronic guarantee certificates, and automating guarantee-related processes.
The 'Customs Digital Public Services' is a Diagram Model-group ABB that includes the 'Procedure Automation System' as a Business Service ABB. The 'Procedure Automation System' represents a digital public service that automates customs procedures.
The relations between these elements and their motivations are not explicitly defined in the provided JSON. However, it can be inferred that the 'Customs Process Streamlining and Efficiency Enablers' are intended to support the 'Customs Digital Public Services' by providing the necessary digital tools and technologies. The ultimate motivation behind these elements is to enhance customs operations, facilitate trade, and improve the overall efficiency and effectiveness of the customs environment.
NARRATIVE:
The TVA-Customs API Enablers [Motivation] view extends the Technical view - application and provides a comprehensive framework for leveraging web services and application interfaces to facilitate customs operations and trade facilitation within the European Union. This view is composed of two main groups: 'Customs Web Services Solutions' and 'Business Agnostic Web Services'.
The 'Customs Web Services Solutions' group consists of several Application Interface SBBs, each representing a specific system or service designed to support customs operations. These systems include CLASS, the EU Customs Trader Portal system, ECICS, TRANSIT, EORI, SAMANCTA, ILIADe, EORI - validation open interface, MRN follow-up, Surveillance System, TARIC, AEO, CDS, COPIS, and EBTI. Each system provides specific functionalities and data to facilitate customs procedures, enhance trade facilitation, and ensure compliance with customs regulations across the European Union.
The 'Business Agnostic Web Services' group consists of several Application Interface ABBs, each representing a generic service that can be utilized across different business contexts. These services include ERP System, eNotification, Financial Management, ePayment, eQualification, eInvoicing, Supply Chain Management, eTendering, eProcurement, eProfessional Qualification, Geo-Localization, and Log Management. Each service provides specific functionalities and data to support various business operations and processes.
The 'Web Service' element, an Application Interface ABB, represents a generic interface that enables interoperability between different applications or systems over the Internet. This element serves as a foundational component for both the 'Customs Web Services Solutions' and 'Business Agnostic Web Services' groups, enabling seamless integration and data exchange between the various systems and services.
The motivation behind this view is to provide a comprehensive framework for leveraging web services and application interfaces to streamline customs operations, enhance trade facilitation, and ensure compliance with customs regulations. By centralizing and standardizing classification information, streamlining customs procedures, and enabling real-time data validation and verification, this view aims to promote secure and efficient cross-border trade within the European Union.
NARRATIVE:
The TVA-Data Exchange Enablers [Motivation] view extends Technical view - application and provides a comprehensive framework for leveraging the Business Agnostic Data Exchange Business Service and Data Exchange Enablers.
The Business Agnostic Data Exchange Business Service, as depicted in the Diagram Model-group ABB, is a crucial element in this view. It is further detailed by the Data Exchange element, which is a Business Service ABB. The Data Exchange Digital Public Service is designed to facilitate the exchange of data in a business-agnostic manner, meaning it can be used across various business domains.
The Data Exchange Enablers, represented as a Grouping ABB, are essential components that facilitate the exchange of data between systems or applications. This grouping includes two Application Service ABBs: the Once-Only Technical System and the Data Exchange.
The Once-Only Technical System (OOTS) is a cross-sectorial service that enables the sharing of information between public administrations across borders between EU countries. It can be expanded beyond the current scope of life events set out in the Single Digital Gateway Regulation. The OOTS puts into practice the Once-Only Principle, which states that citizens should not be forced to provide information to authorities if another authority already holds that information in electronic format.
The Data Exchange is another Application Service ABB within the Data Exchange Enablers grouping. This service enables the secure exchange of messages, records, forms, and other kinds of data between different individuals, organizations, or systems. This includes data routing, except endpoint discovery.
In summary, the TVA-Data Exchange Enablers [Motivation] view provides a comprehensive framework that leverages the Business Agnostic Data Exchange Business Service and Data Exchange Enablers to facilitate secure and efficient data exchange across different systems, applications, and borders.
NARRATIVE:
The TVA-Customs Duties and Tariffs Management Enablers [Motivation] view extends Technical view - application and provides a comprehensive framework for leveraging digital technologies and services to enhance the management of customs duties and tariffs.
This view is composed of two main elements: 'Customs Duties and Tariffs Management Enablers' and 'Customs Digital Public Services'.
The 'Customs Duties and Tariffs Management Enablers' is a Grouping ABB that encompasses two Application Service ABBs: 'Tariffs registry management' and 'Duties Calculation and payment'.
'Tariffs registry management' refers to the systematic and automated management of customs tariffs and related information. This service involves the digitalization and centralization of tariff schedules, rates, and updates within a digital registry or database. It enhances transparency, reduces manual errors, improves trade facilitation, and enables efficient tariff determination and assessment within the customs environment.
'Duties Calculation and payment' refers to the automated and accurate determination and processing of customs duties and taxes owed on imported or exported goods. This service leverages digital technologies and algorithms to calculate duties based on factors such as product classification, customs valuation, origin, and applicable trade agreements. It enhances customs efficiency, reduces errors, ensures compliance with customs regulations, and expedites the release of goods, supporting smooth trade operations within the customs environment.
The 'Customs Digital Public Services' is a Diagram Model-group ABB that includes four Business Service ABBs: 'Tariff Registry management', 'Tariff Suspensions', 'Duties calculation and payment', and 'Duties guarantee management'. These services represent the digital public services provided by the customs authorities to facilitate the management of tariffs and duties.
'Tariff Registry management' and 'Duties calculation and payment' Business Service ABBs align with their corresponding Application Service ABBs in the 'Customs Duties and Tariffs Management Enablers' group, indicating that these digital public services are enabled by the underlying application services.
'Tariff Suspensions' and 'Duties guarantee management' represent additional digital public services provided by the customs authorities to manage tariff suspensions and duties guarantees respectively.
Overall, the TVA-Customs Duties and Tariffs Management Enablers [Motivation] view provides a holistic perspective on the digital enablers and services that support efficient and effective management of customs duties and tariffs.
NARRATIVE:
The TVA-Observability and Monitoring Enablers [Motivation] view extends Technical view - application and provides a comprehensive framework for leveraging the elements of 'Observability and Monitoring Enablers' and 'Business Agnostic Observability and Monitoring Solutions'.
The 'Observability and Monitoring Enablers' is a Grouping ABB (Architecture Building Block) that encapsulates two key elements: 'Observability' and 'Monitoring'. Both of these elements are Application Service ABBs, which are essential services in the architecture. The 'Observability' service is responsible for making the system's internal states externally visible for diagnostic purposes. On the other hand, the 'Monitoring' service is responsible for overseeing the system's operation to ensure it is functioning as expected.
The 'Business Agnostic Observability and Monitoring Solutions' is a Grouping SBB (Solution Building Block) that encompasses two application services: 'ELK Stack' and 'Micrometer'. These are specific solutions that are used to implement the observability and monitoring functionality in a business-agnostic manner. The 'ELK Stack' is an Application Service SBB that provides a powerful platform for searching, analyzing, and visualizing data in real time. The 'Micrometer' is another Application Service SBB that provides a simple facade over the instrumentation clients for the most popular monitoring systems, allowing for dimensional-style metrics collection.
The relationship between these elements is that the 'Observability and Monitoring Enablers' provide the overarching services that are necessary for system diagnostics and operation oversight. These services are then implemented using the specific solutions provided by the 'Business Agnostic Observability and Monitoring Solutions' group. This structure allows for a flexible and adaptable approach to system observability and monitoring, as different solutions can be used depending on the specific needs of the business. The motivation behind this structure is to ensure that the system is always functioning optimally and any issues can be quickly identified and addressed.
NARRATIVE:
The TVA-Digital Workplace Enablers [Motivation] view extends Technical view - application and provides a comprehensive framework for leveraging the elements of the Business Agnostic Digital Workplace Business Services and Digital Workplace Enablers.
The Business Agnostic Digital Workplace Business Services is a Diagram Model-group ABB. It is designed to be universally applicable across various business domains. Within this model group, there is a Business Service ABB named Digital Collaboration. This service is described as a Digital Collaboration Digital Public Service, indicating its role in facilitating digital interaction and cooperation in the public sector.
On the other hand, the Digital Workplace Enablers is a Grouping ABB. This grouping refers to components or services that enable the collaboration of work aspects while ensuring security and privacy. Within this grouping, there is an Application Service ABB also named Digital Collaboration. This service, while sharing the same name as the one in the Business Agnostic Digital Workplace Business Services, is distinct in its function and application.
The relationship between these elements is that they are all part of the overarching TVA-Digital Workplace Enablers [Motivation] view. They are interconnected in their shared goal of enabling digital collaboration in the workplace, albeit through different means and in different contexts. The motivation behind these elements and their relationships is to create a comprehensive framework that leverages digital technologies to enhance collaboration and productivity in the workplace, while also ensuring the security and privacy of all involved.
NARRATIVE:
The TVA-Customs Data Exchange Enablers [Motivation] view extends Technical view - application and provides a comprehensive framework for leveraging digital tools and components that facilitate the exchange of data between systems or applications. This view is primarily composed of two main elements: 'Data Exchange Enablers' and 'Customs Data Exchange Solutions'.
The 'Data Exchange Enablers' is a Grouping ABB that refers to tools or components that facilitate the exchange of data between systems or applications. Within this grouping, there are two key elements: 'Data Exchange' as an Application Component ABB and 'Data Exchange' as an Application Service ABB. The 'Data Exchange' Application Component ABB enables the implementation of the procedure to transfer data between different individuals, organizations, or systems. On the other hand, the 'Data Exchange' Application Service ABB enables the secure exchange of messages, records, forms, and other kinds of data between different individuals, organizations, or systems. This includes data routing, except endpoint discovery.
The second main element is the 'Customs Data Exchange Solutions', another Grouping ABB. This grouping contains a key element named 'Central system for the standardized exchange of information', which is an Application Service SBB. The main objective of this system is to make all INF data available and to streamline the processes of INF data management. For this purpose, the European Commission has designed an EU centralized INF SP System.
Additionally, there is an 'Once-Only Technical System', an Application Service ABB, which enables the sharing of information between public administrations across borders between EU countries. It is cross-sectorial and can be expanded beyond the current scope of life events set out in the Single Digital Gateway Regulation. It puts into practice the Once-Only Principle, which states that citizens should not be forced to provide information to authorities if another authority already holds that information in electronic format.
In summary, the TVA-Customs Data Exchange Enablers [Motivation] view provides a detailed framework for data exchange enablers and customs data exchange solutions, highlighting the importance of efficient and secure data exchange between different entities and systems.
NARRATIVE:
The TVA-API Enablers [Motivation] view extends Technical view - application and provides a comprehensive framework for leveraging Business Agnostic API Business Services and API Enablers.
The Business Agnostic API Business Services is a Diagram Model-group ABB that includes several Business Service ABBs, namely Log Management, eTendering, eNotification, ePayment, eQualification, and eInvoicing. These services are digital public services that cater to various business needs.
Log Management is a service that deals with the management of digital logs. eTendering is a service that handles digital tendering processes. eNotification is a service that manages digital notifications. ePayment is a service that facilitates digital payments. eQualification is a service that deals with digital qualification processes. eInvoicing is a service that handles digital invoicing.
The API Enablers is a Grouping ABB that refers to components and frameworks that support the implementation and cataloguing of (open) software interfaces. This includes several Application Interface ABBs, namely Web Service, ePayment, eInvoicing, eTendering, eProfessional Qualification, eQualification, eNotification, and Log Management.
Web Service is an Application Interface that enables interoperability between different applications or systems over the Internet. ePayment is an Application Interface that refers to a digital payment solution that enables secure and convenient electronic transactions between buyers and sellers. eInvoicing is an Application Interface that enables the electronic creation, exchange, and processing of invoices between businesses or organizations. eTendering is an Application Interface that provides access to specific functionalities related to tendering processes through web-based APIs. eProfessional Qualification is an Application Interface that enables the management, verification, and processing of professional qualification-related information and services over the internet. eQualification is an Application Interface that enables the management and processing of qualifications and certifications in an electronic format. eNotification is an Application Interface that enables the electronic delivery of notifications, alerts, and messages to individuals or organizations. Log Management is an Application Interface that facilitates the collection, storage, analysis, and monitoring of log data generated by web applications, servers, and other web-based systems.
The motivation behind this view is to provide a comprehensive framework that leverages these services and interfaces to enhance business processes, improve interoperability between different systems, and facilitate secure and efficient digital transactions.
EUDI WALLET has to be included here as a SBB for the moment. The logic is that if a high-level model is included in the IoP Arch environment, it should be something developed in co-creation mode with the EUDI WALLET initiative or DIGIT Responsible.
NARRATIVE:
The TVA-Identification and Access Enablers [Motivation] view extends Technical view - application and provides a comprehensive framework for leveraging the secure identification and authentication of users, systems, and services into a platform. This view is composed of three main elements: Identification and Access Enablers, Business Agnostic Identity Management Solutions, and Business Agnostic Authentication Solutions.
The Identification and Access Enablers is a Grouping ABB that refers to components enabling the secure identification and authentication of users, systems, and services into a platform. It includes several Application Service ABBs and Application Component ABBs, such as Authentication, Registration, Identification, Access Management, Identity Management, Authorisation, Accounting, Request Validation, Centralized Identity Management, and Decentralized Identity Management. Each of these components plays a crucial role in the process of identification and access enabling, from the registration of users to the management of their identities and access rights.
The Business Agnostic Identity Management Solutions is a Grouping SBB that includes several Application Service SBBs, such as eIDAS-Node, eIDAS-Proxy-Service, Keycloak, EU Login, WSO2 Identity Server, and Fraunhofer Omejdn Server. These solutions provide a range of identity management services, from the provision of personal identification data to the management of user authentication and authorization.
The Business Agnostic Authentication Solutions is another Grouping SBB that includes several Application Service SBBs, such as EU Login Identification, EU Login Authentication, EU Login Request Validation, and EU Login Registration. These solutions provide a range of authentication services, from user identification to request validation and registration.
The motivation behind this view is to provide a comprehensive framework for the secure identification and authentication of users, systems, and services into a platform. This is achieved through a combination of various components and solutions, each playing a specific role in the process. The ultimate goal is to ensure that only authorized users have access to the platform and its services, thereby enhancing the security and integrity of the platform.
NARRATIVE:
The TVA-Data Space Enablers [Motivation] view extends Technical view - application and provides a comprehensive framework for leveraging various components and services that support the creation and management of a dataspace. This view is divided into three main elements: Dataspace Enablers, Business Agnostic Digital Public Services Catalogue, and Business Agnostic Dataspace Solutions.
The Dataspace Enablers, a Grouping ABB, refers to components and services that support the creation and management of a dataspace. Within this grouping, there are two Application Service ABBs: Dataspace and Dataspace Connector. The Dataspace is the virtual space that enables the creation of a single market for data by integrating, transforming, and making available such data. The Dataspace Connector enables the easy and trustworthy procedure to share data and work collaboratively with other research institutions.
The Business Agnostic Digital Public Services Catalogue is another Grouping ABB that includes two Business Service ABBs: Data Space and Data Space Participant. These services are part of the digital public service offerings related to the dataspace.
The third element, Business Agnostic Dataspace Solutions, is a Grouping ABB that includes several Application Service SBBs. These are specific solutions for the dataspace, including the Eclipse Dataspace Connector, International Data Space Connector, FIWARE TRUE Connector, Sovity Dataspace Connector, Intel IONOS Orbiter Connector, and Fraunhofer AISEC Trusted Connector. Each of these services provides specific functionalities and capabilities within the dataspace.
The motivation behind this view is to provide a comprehensive overview of the various components, services, and solutions that enable the creation, management, and utilization of a dataspace. This view helps in understanding the technical and business aspects of the dataspace and how they interact with each other. It also helps in identifying potential opportunities for improvement and innovation within the dataspace.
NARRATIVE:
The TVA-Privacy Enablers [Motivation] view extends Technical view - application and provides a comprehensive framework for leveraging various elements that facilitate privacy-related functionality within an application or system.
The view consists of three main elements: 'Business Agnostic Privacy Business Service', 'Privacy Enablers', and 'Business Agnostic Privacy Solutions'.
The 'Business Agnostic Privacy Business Service' is a Diagram Model-group ABB that includes a 'Business Service ABB' named 'Anonymisation'. This service refers to a digital public service that provides anonymisation capabilities, which is a crucial aspect of privacy protection.
The 'Privacy Enablers' is a Grouping ABB that refers to components and services that facilitate the implementation of privacy-related functionality within an application or system. It includes several 'Application Service ABBs' such as 'Privacy', 'Anonymisation', 'Consent Management', 'Data Encryption', and 'Privacy Impact Assessments'.
The 'Privacy' service enables the sharing of functionalities such as storing, securing, anonymising, pseudonymising, rectifying, and erasing personal data. The 'Anonymisation' service refers to a software solution that enables the anonymisation of sensitive or personally identifiable information (PII) within datasets. The 'Consent Management' service, 'Data Encryption' service, and 'Privacy Impact Assessments' service are also part of the 'Privacy Enablers' group, each providing specific functionalities related to privacy protection.
The 'Business Agnostic Privacy Solutions' is a Grouping SBB that serves as a catalogue for privacy solutions. It includes an 'Application Service SBB' named 'HashiCorp Vault', which is a specific application service related to privacy protection.
The motivation behind these elements and their relations is to provide a comprehensive framework for implementing privacy-related functionalities in an application or system. This is crucial in today's digital age, where data protection and privacy are of utmost importance.
NARRATIVE:
The TVA-Customs Trade Facilitation and Collaboration Enablers [Motivation] view extends Technical view - application and provides a comprehensive framework for leveraging digital technologies to enhance efficiency, transparency, and collaboration in customs operations and cross-border trade.
The view is divided into two main groups: 'Customs Trade Facilitation and Collaboration Enablers' and 'Customs Digital Public Services'.
The first group, 'Customs Trade Facilitation and Collaboration Enablers', consists of four application services. The first service, 'Trade Facilitation Portal', is an online platform that simplifies trade procedures and promotes efficiency in cross-border trade. The second service, 'Cooperation between Customs laboratories', involves the use of digital platforms to facilitate collaboration and data exchange between customs laboratories. The third service, 'Cooperation between Customs and Postal Operators', involves the use of digital platforms to facilitate collaboration and data sharing between customs authorities and postal operators. The fourth service, 'MS' Customs organization management', involves the use of digital platforms to manage and oversee the operations of customs organizations within a specific country or region.
The second group, 'Customs Digital Public Services', consists of three business services. The first service, 'Customs organizational structure management', is a digital public service for managing the organizational structure of customs. The second service, 'Laboratories registry management', is a digital public service for managing the registry of laboratories. The third service, 'EU Customs Trader Portal', is a digital public service for traders in the EU customs environment.
These services and platforms are designed to enhance the interoperability of customs operations, improve data accuracy and consistency, foster scientific collaboration, promote trade facilitation, ensure compliance with customs regulations, expedite the clearance and delivery of postal shipments, and contribute to secure and efficient cross-border trade. By leveraging digital technologies, these services and platforms aim to provide a comprehensive framework for customs trade facilitation and collaboration.
NARRATIVE:
The TVA-Translation Enablers [Motivation] view extends Technical view - application and provides a comprehensive framework for leveraging various elements related to translation services and solutions. This view is composed of three main elements: 'Business Agnostic eTranslation Services', 'Translation Enablers', and 'Business Agnostic Translation Solutions'.
The 'Business Agnostic eTranslation Services' is a Diagram Model-group ABB that encapsulates the business services related to eTranslation. It includes the 'eTranslation' Business Service ABB, which represents the digital public service for eTranslation. This service is business-agnostic, meaning it can be applied across various business domains.
The 'Translation Enablers' is a Grouping ABB that refers to tools or components that facilitate the translation of text from one language to another using machine learning techniques. It includes the 'Machine Translation' Application Service ABB, which enables the procedures for automated translation of text, metadata, and concept classes or nomenclatures. This application service is a key enabler for the translation process, leveraging machine learning techniques to automate and streamline the translation tasks.
The 'Business Agnostic Translation Solutions' is a Grouping SBB that represents a catalogue of translation solutions. It includes the 'eTranslation' Application Service SBB, which represents the application service for eTranslation. This service is part of the translation solutions that are business-agnostic, meaning they can be applied across various business domains.
In terms of relations, the 'Business Agnostic eTranslation Services' and 'Business Agnostic Translation Solutions' are related as they both provide business-agnostic services and solutions for translation. The 'Translation Enablers' is related to both as it provides the necessary tools and components that enable the translation services and solutions. The motivation behind these elements is to provide comprehensive and versatile translation services and solutions that can be applied across various business domains, leveraging machine learning techniques to automate and streamline the translation tasks.
NARRATIVE:
The TVA-Orchestration Enablers [Motivation] view extends Technical view - application and provides a comprehensive framework for leveraging various elements that facilitate business agnostic orchestration.
The first element is the "Business Agnostic Orchestration Business Service," which is a Diagram Model-group ABB. This element encapsulates the "Workflow Management" service, a Business Service ABB that provides a digital public service for managing workflows.
The second element is the "Orchestration Enablers," a Grouping ABB that refers to the components and practices supporting the development and deployment of orchestration applications. This group includes three sub-elements: "Orchestration" as an Application Service ABB, "Orchestration" as an Application Component ABB, and "Workflow Management" as an Application Service ABB. The "Orchestration" Application Service ABB enables the definition of the sequence and conditions in which one service invokes other services to realize some useful function. The "Orchestration" Application Component ABB enables the coordination and management of the execution of multiple components or services within an application or system. The "Workflow Management" Application Service ABB, also known as Orchestration Application Service, refers to a software solution or service that enables the design, execution, and coordination of workflows within an organization.
The third element is the "Business Agnostic Orchestration Solutions," a Grouping SBB that serves as a catalogue for orchestration solutions. This group includes two sub-elements: "Apache Airflow" and "Apache Beam," both of which are Application Service SBBs. These services represent specific orchestration solutions that can be utilized in the orchestration process.
The motivation behind this view is to provide a comprehensive understanding of the various elements and their interrelations that enable effective orchestration in a business-agnostic manner. This includes the services, components, and specific solutions that can be leveraged to design, execute, and manage workflows and orchestration processes within an organization.
NARRATIVE:
The TVA-Containerization Enablers [Motivation] view extends Technical view - application and provides a comprehensive framework for leveraging various elements that enable containerization. This view is divided into three main groupings: Containerization Enablers, Business Agnostic Containers Orchestrator Solutions, and Business Agnostic Container Solutions.
The first grouping, Containerization Enablers, is an Architectural Building Block (ABB) that includes two Application Service ABBs: Container and Containers Orchestrator. The Container Application Service represents the basic unit of software that packages up code and all its dependencies so the application runs quickly and reliably from one computing environment to another. The Containers Orchestrator Application Service, on the other hand, is responsible for managing the lifecycles of containers, including deployment, scaling, networking, and availability.
The second grouping, Business Agnostic Containers Orchestrator Solutions, is a Solution Building Block (SBB) that includes five Application Service SBBs: Kubernetes, Docker Compose, Docker Swarm, Apache Mesos, and Red Hat OpenShift. These represent various solutions that can be used to manage and orchestrate containers in a business-agnostic manner, meaning they can be used across different business domains and applications.
The third grouping, Business Agnostic Container Solutions, is also an SBB that includes three Application Service SBBs: Docker, Podman, and LXC. These represent different solutions for creating and managing containers that are also business-agnostic.
The relationships between these elements are defined by their grouping. The Container and Containers Orchestrator are part of the Containerization Enablers, which are necessary for the operation of the Business Agnostic Containers Orchestrator Solutions and the Business Agnostic Container Solutions. These solutions, in turn, provide the tools and services necessary to implement and manage containerization in a business environment. The motivation behind this view is to provide a comprehensive overview of the elements and solutions that enable containerization, allowing for a better understanding and implementation of this technology.
NARRATIVE:
The TVA-Messaging Enablers [Motivation] view extends Technical view - application and provides a comprehensive framework for leveraging various elements to facilitate effective messaging. This view is composed of two main elements: 'Messaging Enablers' and 'Business Agnostic Messaging Solutions'.
The 'Messaging Enablers' is a Grouping ABB (Architecture Building Block) that encapsulates the elements that enable messaging. Within this grouping, there is an Application Service ABB named 'Message Broker'. The 'Message Broker' is a crucial component that facilitates the exchange of messages between different applications, acting as an intermediary to ensure smooth communication.
On the other hand, 'Business Agnostic Messaging Solutions' is a Grouping SBB (Solution Building Block) that contains a set of Application Service SBBs. These are 'ActiveMQ', 'Apache Kafka', 'Apache Kafka Streams', and 'RabbitMQ'. These services are independent of any specific business context and can be used across various business scenarios.
'ActiveMQ' is an open-source messaging and Integration Patterns server, which can handle communication from more than one client or server. 'Apache Kafka' is a distributed streaming platform that is designed to handle real-time data feeds. 'Apache Kafka Streams' is a client library for building applications and microservices, where the input and output data are stored in Kafka clusters. 'RabbitMQ' is an open-source message broker software that implements the Advanced Message Queuing Protocol (AMQP).
The relationship between these elements is that the 'Message Broker' in the 'Messaging Enablers' grouping facilitates the communication between the different 'Business Agnostic Messaging Solutions'. These solutions, in turn, provide the necessary services to handle various messaging requirements in a business-agnostic manner. The motivation behind this arrangement is to provide a flexible and robust messaging framework that can cater to diverse business needs.
NARRATIVE:
The TVA-Trust Enablers [Motivation] view extends Technical view - application and provides a comprehensive framework for leveraging various elements that facilitate secure cross-border transactions and interactions.
The view includes three main groups: Business Agnostic Trust Business Services, Business Agnostic Blockchain Business Service, and Trust Enablers.
The Business Agnostic Trust Business Services group includes the eSignature service, which is a digital public service that enables the signing of data in electronic form by a natural person.
The Business Agnostic Blockchain Business Service group includes the Digital Immutability service, which is a digital public service that ensures the integrity, authenticity, and non-repudiation of digitally signed documents.
The Trust Enablers group refers to components and services that facilitate the establishment and maintenance of secure cross-border transactions and interactions. This group includes various application services such as e-Seal Preservation, e-Timestamp Verification and Validation, Registered Electronic Delivery, e-Seal Verification and Validation, e-Signature Creation, e-Signature Preservation, e-Signature Verification and Validation, e-Seal Creation, e-Timestamp Creation, and Trust Service Provisioning.
These services enable various procedures such as extending the trustworthiness of the qualified electronic signature beyond the technological validity period, verifying timestamps used for establishing evidence that a given piece of data existed at a given point in time, transmitting sensitive or confidential documents and messages between parties, verifying documents that are signed electronically, signing data in electronic form by a natural person, and creating, verifying, or validating electronic signatures, time stamps, seals, electronically registered delivery services, and certificates.
The Trust Enablers group also includes the Blockchain Enablers, which refers to components and services that facilitate the development, deployment, and management of ledger technology applications. This includes the Blockchain and Distributed Ledger application services, which enable secure, transparent, and immutable record-keeping and transaction processing shared by all participants in a network.
The view also includes the Business Agnostic Blockchain Solutions group, which includes the Ethereum and European Blockchain Services Infrastructure application services. These services facilitate the development, deployment, and management of blockchain technology applications.
In addition, the view includes various application services such as Digital Certification Timestamp, Digital Certification eSeal, Digital Certification eSignature Service, Digital Europe eSignature DSS open-source library, and Integrity Verification. These services enable various procedures such as verifying timestamps used for establishing evidence that a given piece of data existed at a given point in time, verifying documents that are signed electronically, securely signing electronic documents using digital certificates, and ensuring that information has not been altered in an unauthorized manner since it was created, transmitted, or stored.
NARRATIVE:
The TVA-Data Management Enablers [Motivation] view extends Technical view - application and provides a comprehensive framework for leveraging various elements that facilitate effective data management practices and procedures.
The view is composed of three main groups: Business Agnostic Data Management Business Service, Data Management Enablers, and Business Agnostic Data Governance and Data Integration Solutions.
The Business Agnostic Data Management Business Service group includes six Business Service ABBs: Forms Management, Open Data Management, Data Extraction, Transformation and Loading, Content Management, eArchiving, and Contact Management. These services represent the digital public services that are necessary for managing business-agnostic data.
The Data Management Enablers group refers to components and services that support effective data management practices and procedures. This group includes thirteen Application Service ABBs: Content Management, e-Archiving, Archival Information Packages, Forms Management, Data Extraction, Transformation and Loading, Open Data Management, Contact Management, Data Management, Data Governance, Data Policy Engine, Data Catalogue Management, Federated Data Catalogue Management, Data Integration, and Data Integration Plugins Manager. These services enable various procedures related to data management, such as the creation, management, and publishing of digital content, long-term storage of electronic documents, management of standardized packages of digital content, dynamic creation, distribution and analysis of forms and online surveys, extraction, transformation, and loading of data, and the implementation of procedures to manage data effectively.
The Business Agnostic Data Governance Solutions group includes one Application Service SBB, Apache Atlas, which is a data governance application service. The Business Agnostic Data Integration Solutions group includes four Application Service SBBs: Apache Camel, Apache NiFi, Apache Storm, and Talend Open Studio for Data Integration. These services represent specific solutions for data governance and data integration.
The motivation behind this view is to provide a comprehensive framework that supports effective data management practices and procedures. This is achieved by leveraging various services and components that enable the necessary procedures for managing business-agnostic data, as well as specific solutions for data governance and data integration.
NARRATIVE:
The TVA-Artificial Intelligence Enablers [Motivation] view extends Technical view - application and provides a comprehensive framework for leveraging artificial intelligence (AI) in a business context. This view is composed of two main elements: "Business Agnostic Artificial Intelligence Business Service" and "Artificial Intelligence Enablers".
The "Business Agnostic Artificial Intelligence Business Service" is a Diagram Model-group ABB that represents a business service that is independent of any specific business context. It contains a single element, "Business Intelligence", which is a Business Service ABB that provides a digital public service related to business intelligence.
The "Artificial Intelligence Enablers" is a Grouping ABB that refers to components and services that provide the necessary infrastructure and resources for AI developers to build intelligent systems. These systems are capable of performing tasks that typically require human-like intelligence, such as perception, reasoning, learning, and decision-making. This grouping contains four elements: "Artificial Intelligence", "Machine Learning", "Artificial Intelligence Engine", and "Natural-Language Processing (NLP)".
"Artificial Intelligence" is an Application Service ABB that enables procedures to display intelligent behaviour by analysing their environment and taking actions with some degree of autonomy to achieve specific objectives.
"Machine Learning" is an Application Service ABB within the field of AI that enables systems to automatically learn and improve from experience without being explicitly programmed. It involves the development and deployment of algorithms and models that can analyze large volumes of data, identify patterns, and make predictions or decisions based on the learned patterns.
"Artificial Intelligence Engine" is an Application Service ABB that refers to a software component or service that encompasses the core capabilities of an AI system. It provides a set of algorithms, models, and tools that enable the development, deployment, and execution of AI applications. The AI engine acts as the brain behind AI-powered systems, enabling tasks such as data processing, pattern recognition, prediction, decision-making, and learning.
"Natural-Language Processing (NLP)" is an Application Service ABB that deals with the interaction between computers and humans using natural language. The ultimate objective of NLP is to read, decipher, understand, and make sense of the human language in a valuable way.
In summary, the TVA-Artificial Intelligence Enablers [Motivation] view provides a comprehensive framework for leveraging AI in a business context, including the necessary infrastructure, resources, and services to enable the development and deployment of intelligent systems.
NARRATIVE:
The TVA-Test Enablers [Motivation] view extends Technical view - application and provides a comprehensive framework for leveraging various elements related to testing and conformance. This view includes elements such as Business Agnostic Testing Business Service, Test Enablers, and Business Agnostic Conformance Solutions.
The Business Agnostic Testing Business Service is a Diagram Model-group ABB that encapsulates the Compliance Testing service. This service is a Business Service ABB that is responsible for the Compliance Testing Digital Public Service.
The Test Enablers is a Grouping ABB that refers to the applications and services that support the development and deployment of conformance testing and validation. It includes elements such as Conformance Testing Application Service ABB, Conformance Testing Application Component ABB, and Conformance Test Scenario Business Object ABB. The Conformance Testing Application Service ABB enables the activities and rules to determine whether a tool, platform, or service faithfully meets the requirements of a standard or specification. The Conformance Testing Application Component ABB enables a structural and modular approach for implementing the validation of the application or service to meet the requirements of a standard or specification. The Conformance Test Scenario Business Object ABB specifies a sequence of actions for the execution of a test, also known as a test script or manual test script.
The Business Agnostic Conformance Solutions is a Grouping SBB that includes elements such as the European Interoperability TestBed and the ETSI Signature Conformance Checker. The European Interoperability TestBed is an Application Service SBB offered by the European Commission's DIGIT to facilitate the conformance testing of IT systems. The TestBed is a software system that can be both downloaded and installed locally, but also reused through a shared online installation operated by DIGIT. The ETSI Signature Conformance Checker is another Application Service SBB provided by ETSI Centre for Testing and Interoperability (CTI) that performs numerous checkings to verify the conformity of the ETSI Advanced Electronic Signatures.
These elements and their relationships provide a comprehensive framework for leveraging the development and deployment of conformance testing and validation.
NARRATIVE:
The TVA-Customs Identification and Access Enablers [Motivation] view extends Technical view - application and provides a comprehensive framework for leveraging various application services and components to facilitate secure identification and access within the customs domain.
The view is divided into three main elements: 'Customs Identification and Access Solutions', 'Identification and Access Enablers', and 'EU Login' services.
The 'Customs Identification and Access Solutions' element is a Grouping ABB that encompasses four Application Service ABBs: 'Central Uniform User Management and Digital Signature System (UUMDS)', 'TAXUD Identity Management Service', 'TAXUD Authorisation Service', and 'TAXUD Accounting Service'. These services provide functionalities such as managing authorisation assignments, managing and securing digital identities, confirming electronic identification, and tracking and recording access to resources, respectively.
The 'Identification and Access Enablers' element is another Grouping ABB that includes a range of Application Service ABBs and Application Component ABBs. These include 'Authentication', 'Registration', 'Identification', 'Access Management' (both as a service and a component), 'Identity management', 'Authorisation', 'Accounting', and 'Request Validation'. These services and components enable secure identification, authentication, registration, access management, and request validation for users, systems, and services.
The 'EU Login' services include 'EU Login Identification', 'EU Login Authentication', 'EU Login Request Validation', and 'EU Login Registration'. These services, classified as Application Component SBB and Application Service SBB, provide a point for user authentication to a wide range of Commission information systems.
The motivation behind this view is to provide a comprehensive framework that enables secure identification and access within the customs domain. This is achieved through the use of various application services and components that manage and secure digital identities, confirm electronic identification, track and record access to resources, and enable secure identification, authentication, registration, access management, and request validation.
NARRATIVE:
The TVA-Customs Compliance and Regulatory Requirements Enablers [Motivation] view extends Technical view - application and provides a comprehensive framework for leveraging digital technologies to streamline and automate customs procedures, ensuring compliance with regulatory requirements.
The view is divided into two main groups: "Customs Compliance and Regulatory Requirements Enablers" and "Customs Digital Public Services".
The first group, "Customs Compliance and Regulatory Requirements Enablers", consists of six Application Service ABBs: "Special procedure", "Export procedure", "Transit procedure", "Import procedure", "Authorised Economic Operator accreditation", and "Compliance requirements checks". These services represent the implementation of digital platforms and systems designed to automate and streamline various customs procedures, ranging from special procedures that deviate from standard import/export processes to the management of compliance requirements checks.
For example, the "Export procedure" and "Import procedure" services enable traders to electronically submit export and import declarations, relevant documentation, and trade data through a centralized online platform. These digital solutions automate customs processes such as document verification, risk assessment, and export or import clearance, facilitating electronic communication and data exchange between traders and customs authorities.
The second group, "Customs Digital Public Services", includes six Business Service ABBs: "Economic Operator management and accreditation", "Economic Operators Registry management", "Compliance verification management", "Procedure Automation System", "Procedures registry management", and "Computerised Transit". These services represent various digital public services provided by customs, such as the management and accreditation of economic operators, the management of compliance verification, and the automation of procedures.
The motivation behind this view is to leverage digital technologies to enhance trade facilitation, ensure compliance with customs regulations, and promote efficient and secure cross-border trade within the customs environment. By reducing paperwork, improving accuracy, and expediting procedures, these digital solutions contribute to a more efficient and effective customs environment.
The view that relates Architecture principles to application layer view functional components is crucial in solutions architecture. This view focuses on how architecture principles influence the design and implementation of functional components within the application layer.
By aligning architecture principles with application layer view functional components, solutions architects ensure consistency, enhance performance and scalability, promote reusability and maintainability, and support regulatory compliance. This alignment leads to the creation of robust and efficient applications within the application layer, enabling seamless integration, optimal user experience, reduced maintenance effort, and adherence to legal and industry standards.
In summary, aligning Architecture principles with application layer view functional components ensures consistency, enhances performance and scalability, promotes reusability and maintainability, and supports regulatory compliance. By following these principles, solutions architects can design robust and efficient applications within the application layer.
The view that relates Architecture principles to application layer view functional components is crucial in solutions architecture. This view focuses on how architecture principles influence the design and implementation of functional components within the application layer.
By aligning architecture principles with application layer view functional components, solutions architects ensure consistency, enhance performance and scalability, promote reusability and maintainability, and support regulatory compliance. This alignment leads to the creation of robust and efficient applications within the application layer, enabling seamless integration, optimal user experience, reduced maintenance effort, and adherence to legal and industry standards.
In summary, aligning Architecture principles with application layer view functional components ensures consistency, enhances performance and scalability, promotes reusability and maintainability, and supports regulatory compliance. By following these principles, solutions architects can design robust and efficient applications within the application layer.
The view connects Architecture principles to technical view and the governance components. It is a relevant aspect of solutions architecture. This view specifically examines how architecture principles influence the design and implementation of governance structures within the application layer of a solution.
Firstly, it establishes effective governance within the application layer. Architecture principles provide guidance on defining governance structures, policies, and processes for application and infrastructure development and management. By aligning governance components with these principles, solutions architects design a robust governance framework that promotes compliance, transparency, and accountability in application development, configuration, and operations. This alignment ensures proper control and management of applications, reducing risks and enhancing overall governance practices.
Secondly, aligning architecture principles with governance components supports optimized application development and deployment. Architecture principles often emphasize best practices for application design, scalability, and performance optimization. By incorporating these principles into the design and implementation of governance components, solutions architects establish mechanisms for enforcing design patterns, scalability approaches, and performance monitoring.
NARRATIVE:
The [TV-Technical Agreements] view extends technical view application and provides a comprehensive framework for leveraging various types of agreements, contracts, and specifications to ensure interoperability, collaboration, and service quality across different systems and organizations.
The view includes four types of Technical Agreements: Contract ABB, Grouping ABB, and Business Object ABB. The Contract ABB type includes the Technical Agreement, Technical Interoperability Agreement, and Service Level Agreement. These agreements formalize the framework for strategic and technological collaboration, ensure organizations operate under different technical frameworks, and outline the level of service provided and the metrics used to measure service quality, respectively.
The Grouping ABB type includes the API Technical Interoperability Agreement Solutions, BlockChain Technical Interoperability Agreement Catalogue, and Identity and Access Management Technical Interoperability Agreement Solutions. These groupings provide a collection of technical specifications and standards for building and consuming APIs, ensuring interoperability using blockchain technology, and managing identity and access, respectively.
The Business Object ABB type includes the BlockChain Governance, Hybrid Blockchain Governance, Public BlockChain Governance (permissionless), and Private BlockChain Governance (permissioned). These objects provide the framework and mechanisms for effective collaboration and interoperability using blockchain technology.
The elements within these agreements, contracts, and specifications have relationships with each other based on their function and purpose. For example, the API Technical Interoperability Agreement Solutions grouping includes various Contract ABB elements like OpenAPI, RESTful API, GraphQL, gRPC, JSON-RPC, Simple Object Access Protocol, and OData. These elements provide the technical specifications for building and consuming APIs, enabling interoperability between different systems.
Similarly, the BlockChain Technical Interoperability Agreement Catalogue grouping includes the BlockChain IoP Agreement Contract ABB and the BlockChain Governance, Hybrid Blockchain Governance, Public BlockChain Governance (permissionless), and Private BlockChain Governance (permissioned) Business Object ABB elements. These elements provide the framework and mechanisms for ensuring interoperability using blockchain technology.
The motivation behind these elements and their relationships is to provide a comprehensive framework for leveraging technical agreements, contracts, and specifications to ensure interoperability, collaboration, and service quality across different systems and organizations. This framework enables organizations to identify common interests, prioritize policy dialogue, and develop the necessary tools for strategic and technological collaboration.
NARRATIVE:
The EIRA approach for Data Spaces emphasises a decentralised model where no centralised elements, such as data lakes or data warehouses, are used to process or store the data. Instead, data is maintained and managed by the participants within the data space itself. This approach ensures that control over the data remains with the original data owners, fostering trust, data sovereignty, and compliance with data protection regulations. Through the EIRA/eGovERA Data Space approach, participants share data, allowing for collaboration without the need for centralised storage or processing hubs, thereby promoting a more distributed and flexible data management ecosystem.
The [TVA-Dataspace Enablers] view extends technical view application and provides a comprehensive framework for leveraging various elements and their relationships to enable data integration, management, and usage. This view is composed of several Diagram Model-group ABBs, each containing multiple Application Service ABBs, and a Grouping ABB named [Dataspace Enablers].
The [App Store / Extensions / User Workflows] group includes three services: [Data Integration], [Data Integration Plugins Manager], and [Data Extraction, Transformation and Loading]. These services facilitate the process of combining data from multiple sources into a unified view, managing plugins within a data integration system, and extracting, transforming, and loading data into a target data store.
The [Event Driven / NRT] group contains the [Message Broker] service, which acts as an intermediary for asynchronous message-based communication between different applications.
The [Vocabulary Management] group includes the [Vocabulary Hub] service, a centralized repository for managing and providing access to a wide range of vocabularies or terminologies.
The [Trust] group contains the [Privacy] service, which enables functionalities such as storing, securing, anonymising, pseudonymising, rectifying and erasing personal data.
The [Identity Provider] group includes three services: [Centralized Identity Management], [Decentralized Identity Management], and [Identity Management]. These services manage and control user identities and access rights in both centralized and decentralized manners.
The [Monitoring] group contains the [Observability] service, which provides insights into the internal state and behavior of a system by analyzing its external outputs.
The [Dataspace Enablers] group includes the [Dataspace], [Dataspace Connector], [Dataspace Connector Provider], and [Dataspace Connector Consumer] services. These services support the creation and management of a dataspace, a virtual space for integrating, transforming, and making available data.
The [Contract Negotiation] group includes the [Data Contract], [Data Policy], and [Data Governance] services, which manage the availability, usability, integrity, and security of data within an organization.
The [Service Discovery and Registry], [Service Registry], [Data Catalogue Management], [Dataset Catalogue], and [Federated Data Catalogue Management] services enable the implementation of public digital services, organize metadata about data assets, and manage data catalogues.
The [Data Analytics and Quality] group includes the [Data Analytics] and [Data Quality] services, which analyze data and ensure its accuracy, completeness, consistency, and up-to-dateness.
The view also includes several Archimate Diagram-model ABBs that represent the motivation behind various elements, and Diagram Model-connection ABBs that represent the relationships between these elements.
The Organizational-Functional Architecture Principles view is a crucial aspect of solutions architecture, as it directly influences the implementation of solutions within an organization's functional layers. This view focuses on aligning the design and implementation of solutions with the goals, requirements, and processes of the organization.
Aligning the Organizational-Functional Architecture Principles view with the organizational building blocks brings several benefits. Firstly, it ensures consistency and coherence across different functional areas within the organization. By defining and adhering to architecture principles, solutions architects establish a standardized approach that allows for seamless integration and interoperability between various building blocks. This consistency fosters effective communication and collaboration among departments and teams, promoting efficient business processes and operations.
Secondly, aligning the Organizational-Functional Architecture Principles view supports the scalability and adaptability of solutions. The architecture principles provide guidelines for designing modular, flexible, and reusable solutions. By considering the specific requirements and characteristics of each organizational building block, solutions architects can design solutions that can easily accommodate future changes and expansions. This scalability and adaptability enable the organization to respond to evolving business needs, reducing the time and resources required for future modifications.
Furthermore, aligning the Organizational-Functional Architecture Principles view enhances governance and decision-making processes within the organization. The architecture principles serve as a reference for making design decisions, ensuring that solutions align with the strategic objectives and priorities of the organization. By considering the unique characteristics and requirements of each building block, solutions architects can make informed choices that optimize resource utilization and support the overall organizational strategy.
The Organizational Governance Architecture Principles view focuses on the relationship between the building blocks for governance at the organizational layer and the principles that influence them. This view is crucial in solutions architecture as it ensures that the design and implementation of governance structures within an organization align with the guiding principles and goals of the organization.
Aligning the Organizational Governance Architecture Principles view with the governance building blocks brings several benefits. Firstly, it establishes a strong governance framework that ensures compliance, accountability, and transparency throughout the organization. By defining and adhering to architecture principles, solutions architects can design governance structures that reflect the organization's values, policies, and legal requirements. This alignment promotes consistent decision-making, risk management, and regulatory compliance, ultimately enhancing the organization's overall governance practices.
Secondly, aligning the Organizational Governance Architecture Principles view supports effective communication and collaboration among stakeholders. The architecture principles provide guidelines for structuring roles, responsibilities, and decision-making processes within the governance building blocks. By considering the principles that influence these building blocks, solutions architects can design governance structures that facilitate clear lines of authority, information flow, and decision rights. This alignment fosters better coordination, accountability, and efficiency in governance activities across the organization.
The Organizational-Functional Architecture Principles view is a crucial aspect of solutions architecture, as it directly influences the implementation of solutions within an organization's functional layers. This view focuses on aligning the design and implementation of solutions with the goals, requirements, and processes of the organization.
Aligning the Organizational-Functional Architecture Principles view with the organizational building blocks brings several benefits. Firstly, it ensures consistency and coherence across different functional areas within the organization. By defining and adhering to architecture principles, solutions architects establish a standardized approach that allows for seamless integration and interoperability between various building blocks. This consistency fosters effective communication and collaboration among departments and teams, promoting efficient business processes and operations.
Secondly, aligning the Organizational-Functional Architecture Principles view supports the scalability and adaptability of solutions. The architecture principles provide guidelines for designing modular, flexible, and reusable solutions. By considering the specific requirements and characteristics of each organizational building block, solutions architects can design solutions that can easily accommodate future changes and expansions. This scalability and adaptability enable the organization to respond to evolving business needs, reducing the time and resources required for future modifications.
Furthermore, aligning the Organizational-Functional Architecture Principles view enhances governance and decision-making processes within the organization. The architecture principles serve as a reference for making design decisions, ensuring that solutions align with the strategic objectives and priorities of the organization. By considering the unique characteristics and requirements of each building block, solutions architects can make informed choices that optimize resource utilization and support the overall organizational strategy.
NARRATIVE:
The OV-Duties Calculation and payment [Motivation] view extends the Organisational view and provides a comprehensive framework for leveraging the elements involved in the process of duties calculation and payment. This view is represented by the Diagram Model-group ABB named "Duties Calculation and payment".
The main capability of this model is the "Duties Calculation and payment" (DBC), which is a Capability SBB. This capability is supported by various Business Service ABBs, which include "Economic Operators Registry management", "Determination of the economic value of goods declared for importation", "Origin Registry management", "Customs declarations", "Classification of goods", "EU Customs Trader Portal", "Customs Decisions system", "Procedure Automation System", "Tariff Suspensions", "Goods flow analysis and simulations", "Intra-EU purchases and sales", "Duties calculation and payment", and "Duties guarantee management". These services represent the digital public services that facilitate the duties calculation and payment process.
The information required for these services is represented by Business Object ABBs, which include "Imports information", "Combined nomenclature", "Exports information", "Economic value Information", "Binding Tariffs Information", "Classification of goods Information", "Guarantee Information", "Origin of goods Information", "Economic Operators Information", and "Duties calculation Information". These objects provide the necessary data for the services to function effectively.
The motivation behind this view is to provide a clear and detailed representation of the elements involved in the duties calculation and payment process. This includes the capabilities, services, and information required to facilitate this process. By understanding these elements and their relationships, organizations can better manage and optimize the duties calculation and payment process.
NARRATIVE:
The OV-Export procedure [Motivation] view extends the Organisational view and provides a comprehensive framework for leveraging the Export Procedure, which is a Diagram Model-group ABB. This procedure consists of various Business Service ABBs and Business Object ABBs that work together to manage and facilitate the export process.
The Business Service ABBs include Economic Operators Registry management, Origin Registry management, Customs declarations, Classification of goods, EU Customs information exchange, Goods flow analysis and simulations, Duties calculation and payment, and Duties guarantee management. These services are digital public services that handle different aspects of the export procedure, from managing registries and declarations to classifying goods and calculating duties.
The Business Object ABBs include Duties calculation Information, Economic Operators Information, Threads and fraudulent actions Information, Classification of goods Information, Guarantee Information, Origin of goods Information, Internal logistic Information, Binding Tariffs Information, Workforce information, Economic value Information, Special Procedures Information, Combined nomenclature, Customs partners Information, Imports information, and Economic Operators Registration and Identification number (EORI). These objects represent different types of information that are used and produced during the export procedure.
The Export Procedure capability SBB represents the ability to carry out the export procedure. This capability is crucial for the functioning of the export process and is supported by the various services and information objects mentioned above.
The relationships between these elements are not explicitly stated in the JSON, but it can be inferred that the Business Service ABBs use the Business Object ABBs to carry out their functions. For example, the Duties calculation and payment service might use the Duties calculation Information object to calculate the duties for a particular export. Similarly, the Economic Operators Registry management service might use the Economic Operators Information object to manage the registry of economic operators. The Export Procedure capability SBB, in turn, relies on all these services and information objects to carry out the export procedure.
The motivation behind this view is to provide a comprehensive understanding of the export procedure and the various elements involved in it. This understanding can help in identifying potential improvements and efficiencies in the export process.
NARRATIVE:
The OV-Transit procedure [Motivation] view extends the Organisational view and provides a comprehensive framework for leveraging the transit procedure. This view is represented by a Diagram Model-group ABB named "Transit procedure".
The Transit procedure is further broken down into several capabilities and services. The primary capability is also named "Transit procedure" and is represented as a Capability SBB. This capability is the driving force behind the transit procedure and serves as the main motivation for the other elements in the view.
Several Business Service ABBs are also part of the Transit procedure. These include "Determination of the economic value of goods declared for importation", "Origin Registry management", "Analysis Management", "Duties calculation and payment", "Duties guarantee management", "Computerised Transit", "Customs declarations", "Procedure Automation System", and "Classification of goods". Each of these services plays a crucial role in the transit procedure and contributes to its overall functionality.
The Transit procedure also involves several Business Object ABBs. These include "Duties calculation Information", "Imports information", "Exports information", "Special Procedures Information", "Economic value Information", "Origin of goods Information", "Combined nomenclature", "Classification of goods Information", and "Economic Operators Information". These objects represent the various types of information that are processed and managed during the transit procedure.
The relationships between these elements are crucial for the functioning of the Transit procedure. The Capability SBB motivates the Business Service ABBs, which in turn manage and process the Business Object ABBs. This interconnectedness ensures the smooth operation of the transit procedure and allows for efficient management of goods transit.
Narrative: The ‘Organisational view – DBCs, DPS and Information” viewpoint extends the organisational view and encompasses the realization of digital business capabilities through the deployment of digital public services that interact with specific information bases. Digital business capabilities represent the technological functions and capacities required to deliver services in a digital environment. These capabilities are leveraged by digital public services, which are designed and implemented to facilitate the delivery of services to users in a digital format. These digital public services rely on accessing and utilizing specific information bases to retrieve and process relevant data. By integrating digital business capabilities, digital public services, and information access, organizations can effectively harness technology to enhance service delivery, streamline processes, and meet the needs of users in the digital realm.
NARRATIVE:
The OV-Cooperation between Customs laboratories [Motivation] view extends the Organisational view and provides a comprehensive framework for leveraging cooperation between customs laboratories. This view is represented by a Diagram Model-group ABB named "Cooperation between Customs laboratories".
The Cooperation between Customs laboratories contains several elements that are crucial for its operation. These elements include Business Services ABBs, Business Objects ABBs, and a Capability SBB.
The Business Services ABBs include "Laboratories registry management", "Determination of the economic value of goods declared for importation", "Classification of goods", and "Goods flow analysis and simulations". These services represent the digital public services provided by the customs laboratories.
The Business Objects ABBs include "Combined nomenclature", "Economic Operators Information", "Classification of goods Information", and "Laboratories information". These objects represent the information that is managed and used by the customs laboratories.
The Capability SBB is "Cooperation between Customs laboratories", which represents the ability of the customs laboratories to cooperate and work together.
The motivation behind this view is to provide a comprehensive framework that enables effective cooperation between customs laboratories. This is achieved by clearly defining the services provided by the laboratories, the information they manage and use, and their capability to cooperate. This framework is crucial for ensuring that the customs laboratories can effectively carry out their duties and responsibilities.
In terms of relations, the Business Services ABBs and Business Objects ABBs are related to the Capability SBB. This means that the services provided by the laboratories and the information they manage and use are directly linked to their ability to cooperate. This relationship is crucial for ensuring effective cooperation between the customs laboratories.
NARRATIVE:
The OV-Compliance requirements checks [Motivation] view extends the Organisational view and provides a comprehensive framework for leveraging the compliance requirements checks in a digital public service context. This view is represented by a Diagram Model-group ABB named "Compliance requirements checks".
Within this model, there is a Capability SBB also named "Compliance requirements checks". This capability is responsible for ensuring the compliance of various business services and business objects.
The business services include "Origin Registry management", "Customs declarations", "Classification of goods", "Customs Decisions system", "Compliance verification management", "Duties calculation and payment", and "Duties guarantee management". These services represent different aspects of the digital public service that are subject to compliance checks.
The business objects include "Economic value Information", "Special Procedures Information", "Binding Tariffs Information", "Guarantee Information", "Classification of goods Information", "Origin of goods Information", "Economic Operators Information", "Duties calculation Information", "Exports information", "Imports information", and "Combined nomenclature". These objects represent different types of information that are used in the digital public service and are subject to compliance checks.
The motivation behind this view is to ensure that all aspects of the digital public service, from the services provided to the information used, are compliant with the necessary regulations and standards. This is achieved through the "Compliance requirements checks" capability, which checks the compliance of the business services and business objects. This ensures the integrity and reliability of the digital public service, and helps to maintain trust and confidence in the service.
NARRATIVE:
The OV-MS' Customs organization management [Motivation] view extends the Organisational view and provides a comprehensive framework for leveraging the capabilities and services of the MS' Customs organization management. This view is represented by a Diagram Model-group ABB, which encapsulates the various elements of the MS' Customs organization management.
The MS' Customs organization management is a Capability SBB, which is responsible for managing the customs organization. This capability is supported by various Business Service ABBs, which provide digital public services related to customs operations. These services include Economic Operators Registry management, Determination of the economic value of goods declared for importation, Origin Registry management, EU Customs Trader Portal, Customs declarations, Tariff Registry management, Customs Decisions system, Procedure Automation System, Classification of goods, Tariff Suspensions, Goods flow analysis and simulations, Intra-EU purchases and sales, Duties calculation and payment, Notification of Arrival, Presentation Notification and Temporary Storage, and Duties guarantee management.
These services are underpinned by various Business Object ABBs, which represent the information entities that are manipulated by the services. These objects include Origin of goods Information, Internal logistic Information, Binding Tariffs Information, Workforce information, Laboratories information, Guarantee Information, Classification of goods Information, Threads and fraudulent actions Information, Economic Operators Information, Economic value Information, Special Procedures Information, Temporary storage Information, Duties calculation Information, Free circulation requirement information, Combined nomenclature, Customs partners Information, Exports information, Imports information, and Economic Operators Registration and Identification number (EORI).
The motivation behind this view is to provide a comprehensive understanding of the MS' Customs organization management's capabilities and services, and the information entities they manipulate. This understanding can be used to identify opportunities for improvement, streamline operations, and enhance the effectiveness and efficiency of the customs organization.
NARRATIVE:
The OV-Guarantee [Motivation] view extends the Organisational view and provides a comprehensive framework for leveraging the Guarantee diagram model-group ABB. This model-group is composed of several elements, each with a specific role and purpose.
The first element is the Guarantee capability SBB, which is described as the Guarantee (DBC). This capability is the core of the model-group and serves as the primary function that the other elements revolve around.
The model-group also includes several business services ABBs, each providing a unique service. These services include the determination of the economic value of goods declared for importation, customs declarations, EU customs information exchange, goods flow analysis and simulations, duties calculation and payment, and duties guarantee management. Each of these services is a digital public service, indicating that they are provided electronically to the public.
In addition to these services, the model-group also contains several business object ABBs, which represent various types of information. These include imports information, exports information, economic value information, guarantee information, origin of goods information, and duties calculation information. These business objects serve as the data that the business services use to perform their functions.
The relationships between these elements are crucial to the functioning of the Guarantee model-group. The Guarantee capability SBB is the central element that the other elements revolve around. The business services use the business objects as data to perform their functions. For example, the duties calculation and payment service might use the duties calculation information to calculate the duties owed on an import. Similarly, the determination of the economic value of goods declared for importation service might use the economic value information to determine the value of the goods.
The motivation behind this model-group is to provide a comprehensive framework for managing guarantees. By having a clear structure and defined roles for each element, the model-group can effectively manage guarantees and ensure that all necessary services are provided.
NARRATIVE:
The OV-Tariffs registry management [Motivation] view extends Organisational view and provides a comprehensive framework for leveraging various elements related to tariff management. The elements in this view are grouped under the "Tariff Management" Diagram Model-group ABB, which is described as the overarching theme of this view.
One of the key elements in this view is the "Tariffs registry management" Capability SBB. This capability is responsible for managing the tariffs registry, as indicated by its description "Tariffs registry management (DBC)". However, the JSON does not provide any sub-elements or further details about this capability.
The view also includes several Business Service ABBs, which represent digital public services related to tariff management. These services include "Tariff Suspensions", "Customs declarations", "Tariff Registry management", and "Determination of the economic value of goods declared for importation". Each of these services plays a unique role in the tariff management process, from suspending tariffs and managing the tariff registry to declaring customs and determining the economic value of imported goods.
In addition, the view contains several Business Object ABBs, which represent different types of information used in tariff management. These objects include "Imports information", "Classification of goods Information", "Exports information", and "Economic value Information". These objects provide the necessary data for the aforementioned services to function effectively.
The relationships between these elements are not explicitly defined in the JSON, but it can be inferred that the Business Service ABBs rely on the Capability SBB and the Business Object ABBs to perform their functions. For example, the "Tariff Registry management" service likely uses the "Tariffs registry management" capability to manage the tariff registry, and it may use the "Imports information" and "Exports information" objects to inform its operations.
The motivation behind this view is to provide a clear and comprehensive overview of the elements involved in tariff management, and to illustrate how these elements interact to support the overall process. By understanding these elements and their relationships, organizations can better manage their tariffs and improve their tariff-related operations.
NARRATIVE:
The OV-Laboratories management [Motivation] view extends the Organisational view and provides a comprehensive framework for leveraging the capabilities and services of the Laboratories management system. This view is represented by a Diagram Model-group ABB named "Laboratories management", which is described as the overarching management system for laboratories.
Within this management system, there is a Capability SBB also named "Laboratories management", which is described as the core capability of managing laboratories (DBC). This capability is the fundamental ability of the system to manage and control the operations of laboratories.
The system also provides a Business Service ABB named "Laboratories registry management", which is described as a digital public service for managing the registry of laboratories. This service is responsible for maintaining and updating the registry of all laboratories.
The system also contains several Business Object ABBs, which represent the different types of information managed by the system. These include "Combined nomenclature Information", "Economic Operators Information", "Classification of goods Information", and "Laboratories information". These objects represent the different types of data that the system manages and processes.
The system also provides several other Business Service ABBs, which represent the different services provided by the system. These include "Determination of the economic value of goods declared for importation", "Classification of goods", and "Goods flow analysis and simulations". These services represent the different operations that the system can perform, such as determining the economic value of imported goods, classifying goods, and analyzing and simulating the flow of goods.
The motivation behind this view is to provide a comprehensive framework for managing laboratories, which includes the ability to manage and control the operations of laboratories, maintain and update the registry of laboratories, manage and process different types of information, and perform various operations such as determining the economic value of imported goods, classifying goods, and analyzing and simulating the flow of goods.
NARRATIVE:
The 'OV-Cooperation between Customs and Postal Operators [Motivation] view extends the Organisational view and provides a comprehensive framework for leveraging the cooperation between customs and postal operators. This view is represented by a Diagram Model-group ABB named 'Cooperation between Customs and Postal Operators'.
This model group includes various Business Service ABBs and Business Object ABBs. The Business Service ABBs represent the different services provided in the cooperation, including 'Centralised Clearance for Import', 'Duties guarantee management', 'Partner authorization', 'Duties calculation and payment', 'Compliance verification management', 'Economic Operator management and accreditation', 'Tariff Suspensions', 'Economic Operators Registry management', 'Determination of the economic value of goods declared for importation', 'Tariff Registry management', 'Origin Registry management', 'Customs declarations', 'Procedure Automation System', 'Classification of goods', 'Procedures registry management', 'Preservation of cargo control', and 'Goods flow analysis and simulations'.
These services are supported by various Business Object ABBs, which represent the different types of information used in the cooperation. These include 'Economic Operators Information', 'Duties calculation Information', 'Origin of goods Information', 'Guarantee Information', 'Workforce information', 'Classification of goods Information', 'Binding Tariffs Information', 'Economic value Information', 'Special Procedures Information', 'Combined nomenclature', 'Customs partners Information', 'Exports information', 'Imports information', and 'Economic Operators Registration and Identification number (EORI)'.
The model group also includes a Capability SBB named 'Cooperation between Customs and Postal Operators', which represents the overall capability to cooperate between customs and postal operators.
The relations and motivations among these elements are not explicitly provided in the JSON. However, it can be inferred that the Business Service ABBs are motivated by the need to provide efficient and effective services in the cooperation between customs and postal operators. These services are supported by the Business Object ABBs, which provide the necessary information for the services. The overall capability to cooperate is a key motivation for the existence of all these elements.
NARRATIVE:
The OV-Special procedure [Motivation] view extends the Organisational view and provides a comprehensive framework for leveraging the special procedure in the context of customs and trade. This view is represented by a Diagram Model-group ABB named "Special procedure".
The "Special procedure" is a Capability SBB, which is described as a special procedure (DBC). This capability is supported by several Business Service ABBs, including "Economic Operators Registry management", "Origin Registry management", "Customs declarations", "Classification of goods", "EU Customs information exchange", "Goods flow analysis and simulations", "Duties calculation and payment", and "Duties guarantee management". These services are all described as Digital Public Services, indicating their role in facilitating digital interactions in the customs and trade domain.
The "Special procedure" capability also interacts with a range of Business Object ABBs, which represent different types of information that are relevant to the special procedure. These include "Duties calculation Information", "Economic Operators Information", "Threads and fraudulent actions Information", "Classification of goods Information", "Guarantee Information", "Origin of goods Information", "Internal logistic Information", "Binding Tariffs Information", "Workforce information", "Economic value Information", "Special Procedures Information", "Combined nomenclature", "Customs partners Information", "Imports information", and "Economic Operators Registration and Identification number (EORI) Information".
These Business Object ABBs provide the necessary data and information for the execution of the "Special procedure" capability and the associated Business Service ABBs. The relationships between these elements indicate the flow of information and the dependencies between the different services and the capability.
The motivation behind this view is to provide a clear and comprehensive representation of the special procedure in the customs and trade context, highlighting the key services and information elements involved. This can support strategic planning and decision-making, as well as operational efficiency and effectiveness.
NARRATIVE:
The OV-Risk Analysis [Motivation] view extends the Organisational view and provides a comprehensive framework for leveraging various elements related to risk analysis in an organization. The primary element in this view is the 'Risk Analysis' which is a Diagram Model-group ABB. This element encapsulates all other elements in the JSON.
The 'Risk Analysis' element includes a 'Risk analysis' capability SBB, which is the ability to conduct risk analysis. This capability is crucial for the organization to identify, assess, and prioritize risks.
The 'Risk Analysis' element also includes several Business Service ABBs, which represent the various services provided by the organization. These services include 'Economic Operators Registry management', 'Origin Registry management', 'Analysis Management', 'Duties calculation and payment', 'Goods flow analysis and simulations', 'Economic Operator management and accreditation', 'Risk analysis', and 'Duties guarantee management'. These services are essential for the organization's operations and are likely to be influenced by the results of the risk analysis.
The 'Risk Analysis' element also includes several Business Object ABBs, which represent the various types of information that the organization deals with. These include 'Imports information', 'Exports information', 'Free circulation requirement information', 'Combined nomenclature', 'Customs partners Information', 'Economic value Information', 'Binding Tariffs Information', 'Origin of goods Information', 'Guarantee Information', 'Classification of goods Information', 'Economic Operators Information', and 'Duties calculation Information'. These types of information are likely to be used in the risk analysis process and may also be affected by the outcomes of the risk analysis.
In terms of relations, the 'Risk analysis' capability SBB is likely to be related to all the Business Service ABBs, as it is the capability that enables these services. Similarly, the Business Service ABBs are likely to be related to the Business Object ABBs, as these services use the information represented by these objects.
The motivation for these elements and their relations is to enable the organization to conduct effective risk analysis. This is crucial for the organization to identify potential risks, assess their impact, and take appropriate actions to mitigate them. By doing so, the organization can ensure its continued operation and success.
NARRATIVE:
The OV-Import procedure [Motivation] view extends the Organisational view and provides a comprehensive framework for leveraging various elements related to the import procedure. The primary element in this view is the "Import Procedure", which is a Diagram Model-group ABB. This element encapsulates the entire import procedure.
Within the Import Procedure, there are several sub-elements, each representing a specific capability or service. The "Import procedure" is a Capability SBB, which is the core capability of the entire process.
The "Economic Operators Registry management", "Origin Registry management", "Customs declarations", "Classification of goods", "EU Customs information exchange", "Goods flow analysis and simulations", "Duties calculation and payment", and "Duties guarantee management" are all Business Service ABBs. These services represent the various activities involved in the import procedure, from managing registries and declarations to calculating and paying duties.
The Import Procedure also involves several Business Object ABBs, which represent the information used and produced during the process. These include "Economic Operators Registration and Identification number (EORI)", "Imports information", "Customs partners Information", "Combined nomenclature", "Special Procedures Information", "Economic value Information", "Workforce information", "Binding Tariffs Information", "Internal logistic Information", "Origin of goods Information", "Guarantee Information", "Classification of goods Information", "Threads and fraudulent actions Information", "Economic Operators Information", and "Duties calculation Information".
These Business Object ABBs are crucial for the operation of the import procedure, as they provide the necessary information for the execution of the various services. For example, the "Economic Operators Registration and Identification number (EORI)" provides the identification information for the economic operators involved in the import procedure, while the "Imports information" provides details about the goods being imported.
The relationships between these elements are not explicitly defined in the JSON, but it can be inferred that the Business Service ABBs use the information provided by the Business Object ABBs to execute their functions. For instance, the "Duties calculation and payment" service would use the "Duties calculation Information" to calculate the duties owed for the imported goods.
The motivation behind this view is to provide a comprehensive understanding of the import procedure, including the various services involved and the information they require. This can help in identifying potential improvements or optimizations in the process, ultimately leading to more efficient and effective import procedures.
NARRATIVE:
The 'OV-Customs DBCs, DPSs and Information [Motivation] view extends the Organisational view and provides a comprehensive framework for leveraging various elements related to customs digital business capabilities, digital public services, and information base.
The view is divided into three main groupings: 'Customs Digital Public Services Catalogue', 'Customs Digital Business Capabilities Map', and 'Customs Information Base'.
The 'Customs Digital Public Services Catalogue' grouping contains various business service ABBs such as 'Economic Operators Registry management', 'EU Customs Trader Portal', 'Analysis Management', and 'Centralised Clearance for Import' among others. These services represent different digital public services provided by the customs department.
The 'Customs Digital Business Capabilities Map' grouping includes capability SBBs like 'Compliance requirements checks', 'Customs cooperation', 'Import procedure', and 'Guarantee' among others. These capabilities represent the digital business capabilities of the customs department.
The 'Customs Information Base' grouping consists of business object ABBs such as 'Economic Operators Registration and Identification number (EORI)', 'Free circulation requirement information', 'Laboratories information', and 'Threads and fraudulent actions Information' among others. These objects represent the information base of the customs department.
The view also includes several 'Diagram Model-connection ABB' elements, which are not described in the JSON but presumably represent the relationships and interactions between the different elements in the view.
The motivation behind this view is to provide a comprehensive overview of the customs department's digital public services, digital business capabilities, and information base. This can help in understanding the department's operations, identifying areas for improvement, and developing strategies for digital transformation.
NARRATIVE:
The OV-Authorised Economic Operator accreditation [Motivation] view extends the Organisational view and provides a comprehensive framework for leveraging strategic planning and decision-making processes in the context of achieving the Authorized Economic Operator (AEO) accreditation. However, the provided JSON does not contain any elements, which means there are no specific entities, relationships, or motivations to describe within this view.
In a typical scenario, the elements in the JSON could include various stakeholders, goals, requirements, constraints, principles, and drivers related to the AEO accreditation process. These elements would be interconnected, illustrating how different components of the organization are motivated and aligned towards achieving the AEO accreditation.
For instance, stakeholders could be the organization's management team, employees, and regulatory authorities. Goals could include achieving AEO accreditation, enhancing customs efficiency, and improving supply chain security. Requirements might involve meeting specific customs compliance standards, implementing necessary security measures, and demonstrating financial solvency. Constraints could be budget limitations, timeframes, and regulatory restrictions. Principles could guide the approach towards achieving the AEO accreditation, and drivers could be factors prompting the organization to seek the accreditation.
The relationships between these elements would illustrate the cause-and-effect dynamics within the organization's strategic planning towards the AEO accreditation. For example, the management team (stakeholder) could be driven by the need to enhance customs efficiency (driver) and therefore sets a goal to achieve the AEO accreditation. To achieve this goal, they would need to meet specific customs compliance standards (requirement), guided by certain principles and within certain constraints.
The motivation aspect of the view would highlight why certain decisions are made, what goals are set, and how different elements are prioritized. It would provide insights into the underlying reasons behind the organization's strategic direction towards achieving the AEO accreditation.
NARRATIVE:
The OV-Customs cooperation [Motivation] view extends the Organisational view and provides a comprehensive framework for leveraging the elements of the Customs Cooperation model. This model is a Diagram Model-group ABB type, which includes a variety of elements that are crucial for the functioning of customs cooperation.
The model includes a Capability SBB type element named "Customs cooperation" which is described as Customs cooperation (DBC). This capability is the core of the model and it is the driving force behind all other elements.
The model also includes several Business Service ABB type elements that are essential for the functioning of customs cooperation. These include "Economic Operators Registry management", "Determination of the economic value of goods declared for importation", "Tariff Registry management", "Origin Registry management", "Customs declarations", "Procedure Automation System", "Procedures registry management", "Classification of goods", "Preservation of cargo control", "Goods flow analysis and simulations", "Tariff Suspensions", "Economic Operator management and accreditation", "Duties calculation and payment", "Compliance verification management", "Partner authorization", "Duties guarantee management", and "Centralised Clearance for Import". Each of these services plays a unique role in the customs cooperation process and contributes to the overall functioning of the system.
The model also includes several Business Object ABB type elements that provide the necessary information for the functioning of the customs cooperation. These include "Economic Operators Registration and Identification number (EORI)", "Imports information", "Exports information", "Customs partners Information", "Combined nomenclature", "Special Procedures Information", "Economic value Information", "Binding Tariffs Information", "Workforce information", "Classification of goods Information", "Guarantee Information", "Origin of goods Information", "Duties calculation Information", and "Economic Operators Information". Each of these objects provides a specific type of information that is crucial for the functioning of the customs cooperation.
The relationships between these elements are not explicitly defined in the JSON, but it can be inferred that the Capability SBB type element "Customs cooperation" is the driving force behind all other elements. The Business Service ABB type elements are likely to be the services that are provided as part of the customs cooperation, and the Business Object ABB type elements are likely to be the information that is used and produced by these services. The motivation behind these elements and their relationships is to ensure the smooth and efficient functioning of customs cooperation.
NARRATIVE:
The 'OV-Preservation of cargo information [Motivation] view extends the Organisational view and provides a comprehensive framework for leveraging the preservation of cargo information. This view is represented by a Diagram Model-group ABB named 'Preservation of cargo information'.
The 'Preservation of cargo information' is a Capability SBB that is responsible for preserving cargo information (DBC). This capability is supported by several Business Service ABBs, including 'Economic Operators Registry management', 'EU Customs Trader Portal', 'Tariff Registry management', 'Analysis Management', 'Customs declarations', 'Classification of goods', 'Preservation of cargo control', 'Intra-EU purchases and sales', 'Duties calculation and payment', and 'Duties guarantee management'. These services are all digital public services that contribute to the preservation of cargo information.
The 'Preservation of cargo information' capability also interacts with several Business Object ABBs, which represent different types of information that are crucial for the preservation of cargo information. These include 'Imports information', 'Exports information', 'Special Procedures Information', 'Binding Tariffs Information', 'Economic value Information', 'Origin of goods Information', 'Guarantee Information', 'Economic Operators Information', 'Duties calculation Information', 'Combined nomenclature', and 'Classification of goods Information'.
The relationships between the Capability SBB, Business Service ABBs, and Business Object ABBs in this view are crucial for the preservation of cargo information. The Business Service ABBs provide the necessary services to support the Capability SBB, while the Business Object ABBs provide the necessary information for these services. Together, these elements form a comprehensive framework for preserving cargo information.
Narrative: The ‘Organisational view – DBCs, DPS and Information” viewpoint extends the organisational view and encompasses the realization of digital business capabilities through the deployment of digital public services that interact with specific information bases. Digital business capabilities represent the technological functions and capacities required to deliver services in a digital environment. These capabilities are leveraged by digital public services, which are designed and implemented to facilitate the delivery of services to users in a digital format. These digital public services rely on accessing and utilizing specific information bases to retrieve and process relevant data. By integrating digital business capabilities, digital public services, and information access, organizations can effectively harness technology to enhance service delivery, streamline processes, and meet the needs of users in the digital realm.
NARRATIVE:
The OV-Expeditions controls [Motivation] view extends the Organisational view and provides a comprehensive framework for leveraging various elements related to expeditions controls. The view is primarily composed of a Diagram Model-group ABB named "Expeditions controls", which encapsulates a Capability SBB of the same name and a multitude of Business Service ABBs and Business Object ABBs.
The Capability SBB, "Expeditions controls", represents the ability of the organization to manage and control expeditions. This capability is crucial for the organization's operations and is the central element of the view.
The Business Service ABBs represent various digital public services related to expeditions controls. These include "Economic Operators Registry management", "Determination of the economic value of goods declared for importation", "Origin Registry management", "EU Customs Trader Portal", "Customs declarations", "Tariff Registry management", "Customs Decisions system", "Procedure Automation System", "Classification of goods", "Tariff Suspensions", "Goods flow analysis and simulations", "Intra-EU purchases and sales", "Duties calculation and payment", "Notification of Arrival, Presentation Notification and Temporary Storage", and "Duties guarantee management". Each of these services plays a specific role in the overall expeditions control process, contributing to the organization's ability to effectively manage and control expeditions.
The Business Object ABBs represent various types of information that are crucial for the expeditions control process. These include "Origin of goods Information", "Internal logistic Information", "Binding Tariffs Information", "Workforce information", "Laboratories information", "Guarantee Information", "Classification of goods Information", "Threads and fraudulent actions Information", "Economic Operators Information", "Economic value Information", "Special Procedures Information", "Temporary storage Information", "Duties calculation Information", "Free circulation requirement information", "Combined nomenclature", "Customs partners Information", "Exports information", "Imports information", and "Economic Operators Registration and Identification number (EORI)". Each of these information types provides valuable insights that enable the organization to effectively manage and control expeditions.
The relationships between these elements are not explicitly defined in the JSON, but it can be inferred that the Capability SBB is supported by the various Business Service ABBs, which in turn utilize the Business Object ABBs to perform their functions. The motivation behind this arrangement is to create a comprehensive and effective system for managing and controlling expeditions, leveraging digital public services and various types of information to achieve this goal.
NARRATIVE:
The OV-Information Base view extends Organisational view and provides a comprehensive framework for leveraging business objects and grouping ABBs to support the delivery of digital public services.
The view consists of two main elements: 'Information' and 'Business Agnostic Business Information Base'. 'Information' is a Business Object ABB that describes business facts, assets, or opinions that are exchanged in the context of a digital public service to support its delivery. This information is enacted via interpretation rules (expressed in an ontology) of data and considering knowledge of a given context. Examples include an invoice, a medical prescription, a driving license.
The 'Business Agnostic Business Information Base' is a Grouping ABB that serves as a catalogue for various Business Object ABBs. These include 'Payment', 'Transaction', 'Identification', 'Qualification', 'Audit trail', 'Access rights', 'Profile', 'Message', 'Availability', 'Digital Signature', 'Document', 'Security Measure', 'Location', 'Invoice', 'Contracting authority', 'Economic operator', 'Digital Asset', 'Credential', 'Data Quality', and 'Distribution list'. Each of these represents a specific type of business information that is essential for the functioning of the digital public service.
The view also includes a 'Customs Information Base', which is another Grouping ABB. This base contains specific Business Object ABBs related to customs operations, such as 'Economic Operators Registration and Identification number (EORI)', 'Free circulation requirement information', 'Laboratories information', 'Threads and fraudulent actions Information', 'Duties calculation Information', 'Imports information', 'Combined nomenclature', 'Workforce information', 'Classification of goods Information', 'Temporary storage Information', 'Exports information', 'Special Procedures Information', 'Binding Tariffs Information', 'Guarantee Information', 'Economic Operators Information', 'Customs partners Information', 'Economic value Information', 'Internal logistic Information', and 'Origin of goods Information'.
The relations between these elements are not explicitly defined in the JSON, but it can be inferred that the 'Business Agnostic Business Information Base' and 'Customs Information Base' are subsets of the 'Information' element, as they provide specific types of information needed for the digital public service. The motivation behind this structure is to provide a comprehensive and organized view of all the information elements involved in the service, facilitating their management and utilization.
NARRATIVE:
The OV-Digital Business Capabilities Catalogue view extends Organisational view and provides a comprehensive framework for leveraging digital capabilities in public administration. This view is composed of two main elements: "Digital Business Capability" and two Grouping ABBs - "Business Agnostic Digital Business Capabilities Map" and "Customs Digital Business Capabilities Map".
The "Digital Business Capability" is a Capability ABB that corresponds to an ability implemented in a system to enable public administrations to perform an administrative function. This capability does not contain any sub-elements.
The "Business Agnostic Digital Business Capabilities Map" is a Grouping ABB that encompasses a set of Capability SBBs. These capabilities include "Electronic Identification", "Qualification Management", "Digital Payments", "Digital Procurement", "Digital Communication", "Digital Exchange", "Digital Invoicing", "Data Management", "Multimedia Management", "Contact Management", "Case and Workflow Management", "Knowledge Management", "Digital Twin", and "Artificial Intelligence". Each of these capabilities represents a specific digital business capability that can be leveraged by public administrations.
The "Customs Digital Business Capabilities Map" is another Grouping ABB that includes a set of Capability SBBs related to customs operations. These capabilities include "Compliance requirements checks", "Customs cooperation", "Import procedure", "Guarantee", "Tariffs registry management", "Preservation of cargo information", "Cooperation between Customs and Postal Operators", "Transit procedure", "Authorised Economic Operator accreditation", "Risk analysis", "Cooperation between Customs laboratories", "Special procedure", "Laboratories management", "MS' Customs organization management", "Export procedure", and "Duties Calculation and payment", and "Expeditions controls". Each of these capabilities represents a specific digital business capability that can be leveraged by customs administrations.
The relationships between these elements are not explicitly defined in the JSON data, but it can be inferred that the Capability SBBs within each Grouping ABB are related in that they contribute to the overall digital business capabilities of public or customs administrations. The motivation for these elements and their relationships is to provide a comprehensive framework for leveraging digital capabilities in public administration, enabling more efficient and effective operations.
NARRATIVE:
The OV-Digital Public Services Catalogue view extends Organisational view and provides a comprehensive framework for leveraging the digital transformation of public services. The view is composed of two main elements: the "Digital Public Service Catalogue" and the "Business Agnostic Digital Public Services Catalogue".
The "Digital Public Service Catalogue" is a Business Object ABB that enables the index of active digital public services, and their descriptions, provided by a public administration. This ABB is a key interoperability enabler for sharing and provisioning, as well as reusing and consuming of front-office public services.
The "Business Agnostic Digital Public Services Catalogue" is a Grouping ABB that includes a variety of Business Service ABBs. These services range from ePayment, Audit, eArchiving, eDelivery, eQualification, eTranslation, Data Extraction, Transformation and Loading, Data Analytics, Delegation of Power, Workflow Management, Knowledge Management, eNotification, eIdentification, Digital Collaboration, Waiting list Management, Open Data Management, Anonymisation, eSignature, Secure Access Control, Content Management, Log Management, eInvoicing, eTendering, Contact Management, Forms Management, Data Exchange, Digital Inmutability, Business Intelligence, Compliance Testing, Data Space, to Data Space Participant. Each of these services represents a specific digital public service provided by the public administration.
The view also includes a "Customs Digital Public Services Catalogue", which is another Grouping ABB. This catalogue includes Business Service ABBs that are specific to customs operations, such as Economic Operators Registry management, EU Customs Trader Portal, Analysis Management, (Internal) Customs logistics management, Centralised Clearance for Import, Determination of the economic value of goods declared for importation, Tariff Registry management, Applications and Requests, Compliance verification management, Duties guarantee management, Origin Registry management, Customs Decisions system, Customs organizational structure management, Duties calculation and payment, Partner authorization, Customs declarations, Procedure Automation System, Preservation of cargo control, Intra-EU purchases and sales, Notification of Arrival, Presentation Notification and Temporary Storage, Classification of goods, Procedures registry management, Tariff Suspensions, Computerised Transit, Risk analysis, Laboratories registry management, EU Customs information exchange, Goods flow analysis and simulations, and Economic Operator management and accreditation.
In summary, the OV-Digital Public Services Catalogue view provides a comprehensive framework for understanding and managing the digital transformation of public services, with a particular focus on interoperability and the sharing and reusing of services.
The Organisational view models the most salient Architecture Building Blocks and Solution Building blocks that shall be considered in order to support organisational interoperability among providers and users of a public service.
Narrative: The delivery of public services involves various organizations playing different roles within the ecosystem. Public service providers, acting as suppliers, offer public services to citizens, businesses, and public administrations, who act as consumers of these services. The specific public services are documented in public service catalogues, which serve as a reference for service portfolio management. Public service providers can delegate the delivery of these services to public service delivery agents who act on their behalf. To ensure effective service delivery, public service providers can enter into interoperability agreements that define the agreed-upon approach to delivering public services to users.
The delivery of public services relies on the utilization of business capabilities and the exchange of business information. Business capabilities represent the operational functions required to deliver the services, while the exchange of business information facilitates the transfer of relevant data between the involved parties. The exchanged business information is specific to each instance and is governed by business rules derived from organizational interoperability enablers such as organizational structures, procedures, policies, and skills.
Interoperability governance is overseen by the interoperability organizational authority, responsible for establishing and enforcing governance practices. This authority influences the interoperability strategy, which in turn implements the interoperability framework. Interoperability skills, a specialized form of organizational skills, enable organizations to excel in interoperability and effectively participate in the ecosystem.
Security also plays a crucial role in the delivery of digital public services. A security framework, which is a specific form of a security policy, addresses the organization's security-related aspects, ensuring the protection of sensitive information and adherence to security standards.
To support the design and implementation of digital public services, additional solution building blocks are extended. These include organizational agreements, a digital governance plan, a digital public service catalogue, information management, and digital business capabilities. These building blocks provide specific functionalities and capabilities to enhance the development and deployment of digital public services, aligning them with the overarching organizational framework.
Overall, the organizational layer of the solution architecture template outlines the roles, agreements, processes, and governance mechanisms necessary for effective delivery of public services. It emphasizes the importance of interoperability, security, and specialized skills, while incorporating additional solution building blocks to enable the design and implementation of digital public services.
NARRATIVE:
The OV-Organisational Agreements view extends Organisational view and provides a comprehensive framework for leveraging various elements that are crucial for the functioning of an organisation. This view is designed to provide a detailed understanding of the organisational agreements and their associated elements.
The first element is the "Organisational Agreement", which is of the type "Contract ABB". The Organisational Agreement ABB is a Contract that enables any agreement to which the Organisation or any Restricted Subsidiary is a party pursuant. This implies that this contract is a binding agreement that the organisation or its restricted subsidiaries must adhere to.
The second element is the "Business Agnostic Organisational Agreement Catalogue", which is of the type "Grouping ABB". This catalogue is a collection of organisational agreements that are business-agnostic, meaning they are applicable regardless of the specific business context or industry. This catalogue includes a sub-element named "National Governance Models", which is of the type "Contract ABB". The National Governance Models are contracts that define the governance models at a national level.
The third element is the "Business Agnostic Organisational Agreement Solutions", which is also of the type "Grouping ABB". This element represents a collection of solutions that are business-agnostic and pertain to organisational agreements. This includes a sub-element named "Code of Conduct for Energy Efficiency in Data Centres", which is of the type "Contract SBB". This contract outlines the code of conduct for maintaining energy efficiency in data centres.
The relationships between these elements are defined by their hierarchical structure. The Organisational Agreement is a standalone element, while the Business Agnostic Organisational Agreement Catalogue and Business Agnostic Organisational Agreement Solutions are groupings that contain specific contracts. These contracts, namely the National Governance Models and the Code of Conduct for Energy Efficiency in Data Centres, are part of their respective groupings and contribute to the overall organisational agreements framework.
The motivation for this structure is to provide a comprehensive and structured view of the organisational agreements, allowing for a clear understanding of the various contracts and their implications. This helps in ensuring compliance and effective governance within the organisation.
NARRATIVE:
The SV-Customs Data Representation [Motivation] view extends Semantic view and provides a comprehensive framework for leveraging the elements of data representation and customs data format, representation, and syntax solutions.
The first element, named 'Data Representation', is of the type 'Representation ABB'. It describes the perceptible configuration of business information or a legal act. Representations can be classified in various ways, such as by medium (e.g., electronic or paper documents, audio, etc.) or format (HTML, ASCII, PDF, RTF, etc.). This element does not contain any sub-elements.
The second element, named 'Customs Data Format, Representation and Syntax Solutions', is of the type 'Grouping ABB'. This element groups together solutions related to customs data format, representation, and syntax. Within this grouping, there is a sub-element named 'EDIFACT', which is of the type 'Representation SBB'. EDIFACT, or 'CUSDEC', is a specific format used for customs declarations. It includes fields and structures for capturing information about import or export shipments, including details about goods, their classification, valuation, origin, and other customs-related information.
The relationship between the 'Data Representation' and 'Customs Data Format, Representation and Syntax Solutions' elements is not explicitly defined in the JSON. However, it can be inferred that 'Customs Data Format, Representation and Syntax Solutions' is a specific application of the general 'Data Representation' concept. The 'EDIFACT' sub-element, in turn, is a specific instance of the 'Customs Data Format, Representation and Syntax Solutions' grouping.
The motivation behind this view is to provide a structured way of representing and organizing data related to customs declarations, thereby facilitating more efficient and accurate data processing and decision-making.
Narrative:
The "Semantic view - Agnostic Ontology Catalogue" viewpoint extends the semantic view and provides a comprehensive framework for organizing and managing agnostic ontologies within the digital ecosystem. This view associates the Business Agnostic Ontologies Catalogue with Digital Public Services and the Business Information Base from the application layer.
Within this view, the Business Agnostic Ontologies Catalogue serves as a centralized repository for storing and categorizing a collection of agnostic ontologies. It acts as a catalogue of standardized concepts, relationships, and rules that are independent of specific business domains. The catalogue ensures that ontologies are easily discoverable, accessible, and reusable across different digital services and applications.
The Digital Public Services, as part of the application layer, leverage the ontologies within the Business Agnostic Ontologies Catalogue to ensure consistent and meaningful representation of information and functionalities. These services align with the ontological concepts and relationships to enable seamless interactions, data exchange, and semantic interoperability among various digital public services.
Furthermore, the Business Information Base complements the Business Agnostic Ontologies Catalogue by providing a structured repository of business-related information. It serves as a valuable resource for storing and accessing domain-specific data, supporting decision-making processes, and enabling the enrichment of ontologies within the catalogue.
By associating the Business Agnostic Ontologies Catalogue with Digital Public Services and the Business Information Base, the "Semantic view - Agnostic Ontology Catalogue" facilitates the discovery, retrieval, and reuse of agnostic ontologies within the digital ecosystem. This view promotes the standardization and consistency of ontological concepts and relationships, allowing for effective semantic interoperability, data integration, and advanced functionalities such as semantic search and intelligent data processing.
The agnostic nature of the ontologies within the catalogue allows for flexibility and adaptability across different business domains and digital public services. It enables organizations to leverage existing ontologies and avoid duplication of efforts, reducing complexity and promoting the consistency of information representation.
Narrative:
The "Semantic view - Business Agnostic Data Models" viewpoint extends the semantic view provides a comprehensive framework for organizing and utilizing business agnostic data models within the digital ecosystem. This view associates the Agnostic Data Models with Digital Public Services from the application layer.
Within this view, Agnostic Data Models represent standardized and domain-independent structures for organizing and representing data. These models define the entities, attributes, relationships, and rules that are applicable across different business domains, ensuring consistency and interoperability in data representation and exchange.
Digital Public Services, as part of the application layer, leverage the Agnostic Data Models to ensure uniformity and coherence in data organization and management. These services align their data structures, operations, and interactions with the agnostic data models, enabling seamless integration, data consistency, and semantic interoperability among different digital public services.
By associating the Agnostic Data Models with Digital Public Services, the "Semantic view - Business Agnostic Data Models" facilitates standardized data modeling and data management practices. This view supports effective data integration, semantic interoperability, and advanced functionalities within the digital ecosystem.
The agnostic nature of the data models allows for flexibility and adaptability across different business domains and digital public services. It promotes reusability, reduces redundancy, and supports consistent and efficient data representation and exchange.
NARRATIVE:
The SV-Data Syntax Mapping Catalogue [Motivation] view extends Semantic view and provides a comprehensive framework for leveraging the elements in the given JSON. This view is designed to bridge the gap between different systems or data models, ensuring that data remains accurate and usable when transferred from a source to a destination.
The JSON contains two main elements: "Business Agnostic Business Information Base" and "Data Syntax Mapping Catalogue".
The "Business Agnostic Business Information Base" is a Diagram Model-group ABB. It is a business-agnostic model that serves as a base for business information. This base includes a sub-element named "Availability", which is a Business Object ABB. The "Availability" object represents availability information, and it does not contain any sub-elements.
The second main element in the JSON is the "Data Syntax Mapping Catalogue", which is a Data Object ABB. The description indicates that this catalogue serves as a bridge between two systems or data models. It is designed to ensure that data remains accurate and usable when it is moved from a source to a destination. This element does not contain any sub-elements.
The relationship between these two main elements is not explicitly defined in the JSON. However, based on the descriptions, it can be inferred that the "Data Syntax Mapping Catalogue" may use the "Business Agnostic Business Information Base" to ensure the accuracy and usability of data during transfer. The motivation behind this relationship is to facilitate efficient data transfer between different systems or data models, thereby enhancing the overall data management process.
NARRATIVE:
The SV-Data Mapping Catalogue [Motivation] view extends Semantic view and provides a comprehensive framework for leveraging the business agnostic business information base and the data mapping catalogue.
The first element in this view is the 'Business Agnostic Business Information Base', which is a Diagram Model-group ABB. This base is a general-purpose business information base that is not tied to any specific business context or domain. It contains two sub-elements: 'Availability' and 'Digital Asset', both of which are Business Object ABBs.
'Availability' is a business object that represents the availability information. This could include data about the availability of resources, services, or any other business elements. The 'Digital Asset' business object represents the digital asset information. This could include data about digital resources such as software, digital media, or any other digital assets.
The second main element in this view is the 'Data Mapping Catalogue', which is a Data Object ABB. This catalogue is a data object that aims to index an inventory of rules or procedures on how data from different sources and domains can be linked and integrated. This could include mapping rules, transformation rules, integration procedures, or any other relevant information.
The relationship between these elements is that the 'Data Mapping Catalogue' uses the data from the 'Business Agnostic Business Information Base' to create a comprehensive and integrated view of the business data. This allows for a more effective and efficient use of the data, as it can be easily linked and integrated across different sources and domains.
The motivation behind this view is to provide a comprehensive framework for leveraging business data. By using a business agnostic business information base and a data mapping catalogue, businesses can effectively manage their data and use it to drive business decisions and actions. This can lead to improved business performance and competitiveness.
Not clear if it is an SBB in itself. It seems to be a broad description for Authority Tables and other asstets managed by the Publications Office
Narrative:
The "Semantic view - Agnostic Reference Data" viewpoint extends the semantic view and provides a comprehensive framework for managing and leveraging agnostic reference data within the digital ecosystem. This view associates the Agnostic Reference Data with Digital Public Services and the Business Information Base from the application layer.
Within this view, the Agnostic Reference Data acts as a centralized repository for standardized and commonly used reference data across different business domains. It includes data elements such as codes, classifications, and identifiers that are independent of specific contexts. The agnostic nature of the reference data ensures consistency and interoperability across various digital services and applications.
The Digital Public Services, as part of the application layer, rely on the Agnostic Reference Data to ensure uniformity and accuracy in data representation and exchange. These services align their data structures and operations with the reference data, enabling seamless integration, data consistency, and semantic interoperability among different digital public services.
Furthermore, the Business Information Base complements the Agnostic Reference Data by providing a repository of business-related information that relies on the reference data. It serves as a valuable resource for storing and accessing domain-specific data, facilitating decision-making processes, and enabling the enrichment of reference data within the digital ecosystem.
By associating the Agnostic Reference Data with Digital Public Services and the Business Information Base, the "Semantic view - Agnostic Reference Data" promotes the standardization and consistency of reference data within the digital ecosystem. This view ensures the availability and accessibility of accurate and up-to-date reference data, enabling effective data integration, semantic interoperability, and advanced functionalities in digital public services.
The use of agnostic reference data allows for flexibility and adaptability across different business domains and digital public services. It facilitates data harmonization, reduces redundancy, and enables consistent data interpretation and exchange across applications and systems.
NARRATIVE:
The SV-High Value Datasets [Motivation] view extends Semantic view and provides a comprehensive framework for leveraging high-value datasets and business information. This view is composed of several elements, each with unique characteristics and relationships.
The first element, "Business Agnostic High Value Dataset Solutions," is a Grouping ABB that serves as a catalogue for various high-value datasets. These datasets are divided into six Data Object SBBs: "Geospatial High Value Dataset," "Business-related data High Value Dataset," "Metereology High Value Dataset," "Mobility High Value Dataset," "Statistics High Value Dataset," and "Earth Observation Data High Value Dataset." Each of these datasets contains specific data related to their respective fields, such as INSPIRE themes, reference parcels, agricultural parcels, basic company information, records, financial statements, weather data, river information services data, statistical data on select legal acts, and environmental information.
The second element, "Business Agnostic Business Information Base," is a Diagram Model-group ABB that contains three Business Object ABBs: "Availability," "Data Quality," and "Document." These objects provide information on the availability of the datasets, the quality of the data, and any related documents.
The third element, "Dataset," is a Data Object ABB that represents a collection of related data organized and presented in a structured format. This element serves as a foundation for the high-value datasets.
The final element, "High Value Dataset," is a Data Object ABB that represents datasets with the potential to generate significant socio-economic or environmental benefits, innovative services, assist in generating revenues, and be combined with other datasets. This element highlights the value and potential benefits of the datasets.
The relationships between these elements are crucial for understanding the motivation behind the SV-High Value Datasets [Motivation] view. The high-value datasets are grouped under the "Business Agnostic High Value Dataset Solutions" and are supported by the "Business Agnostic Business Information Base," which provides necessary information about the datasets. The "Dataset" and "High Value Dataset" elements further emphasize the importance and value of these datasets.
Narrative:
The "Semantic view - Forms Structure" extends semantic view and provides a comprehensive framework for designing and managing the structure of forms within the digital ecosystem. This view associates the Forms Structure with the Business Information Base and Digital Public Services from the application layer.
Within this view, the Forms Structure defines the organization, layout, and components of digital forms used for data collection and input. It ensures a consistent and standardized approach to form design, enhancing user experience, and enabling efficient data capture.
The Business Information Base, as part of the application layer, relies on the Forms Structure to ensure effective data collection and management. It utilizes the defined forms structure to design and implement forms that capture domain-specific data accurately and comprehensively.
Digital Public Services leverage the Forms Structure to ensure consistent form design and data collection across different services. These services align their data models, operations, and interactions with the defined forms structure, enhancing user engagement and facilitating accurate data entry within the digital ecosystem.
By associating the Forms Structure with the Business Information Base and Digital Public Services, the "Semantic view - Forms Structure" promotes standardized form design and enables efficient data capture and management. This view ensures consistency in form layout and components, improves data quality, and enhances user satisfaction within the context of digital public services.
The defined forms structure allows for streamlined data collection, reducing errors, and ensuring data completeness. It provides a user-friendly interface for capturing data, guiding users through the necessary fields and data entry requirements.
NARRATIVE:
The SV-Customs Controlled Vocabularies [Motivation] view extends Semantic view and provides a comprehensive framework for leveraging standardized vocabularies and taxonomies in the context of customs operations and trade facilitation. This view is composed of three main elements: 'Customs Vocabularies', 'Customs Information Base', and 'Controlled Vocabulary'.
The 'Customs Vocabularies' element is a Grouping ABB that encompasses three Data Objects: 'Registered Organisation Vocabulary', 'National Customs Specific Taxonomy', and 'Combined Nomenclature'. These vocabularies provide a standardized set of terms and concepts for representing and describing registered organizations, customs-related data, regulations, and procedures unique to a nation's trade and customs environment, and a tool for classifying goods to meet the requirements of the Common Customs TariffEN and of the EU external trade statistics.
The 'Customs Information Base' is a Diagram Model-group ABB that includes a variety of Business Objects such as 'Economic Operators Information', 'Free circulation requirement information', 'Imports information', 'Laboratories information', 'Combined nomenclature', 'Exports information', 'Customs partners Information', 'Economic value Information', 'Origin of goods Information', and 'Workforce information'. These Business Objects represent different types of information that are crucial for customs operations and trade facilitation.
The 'Controlled Vocabulary' is a Data Object ABB that represents a carefully curated set of terms used to describe concepts or objects in the customs and trade domain. This standardized list of terms is used to ensure consistency and accuracy in the indexing, searching, and retrieval of information.
The relationship between these elements is such that the 'Customs Vocabularies' and 'Controlled Vocabulary' provide the standardized terms and concepts that are used in the 'Customs Information Base' to ensure consistent and accurate representation of customs-related information. This facilitates efficient customs operations, enhances trade facilitation, and supports accurate reporting and analysis.
Narrative:
The "semantic view - Agnostic Ontologies" viewpoint extends the semantic view and provides a comprehensive framework for representing and organizing knowledge within the digital ecosystem. This view associates the Business Agnostic Ontologies with Digital Public Services and the Business Information Base from the application layer.
Within this view, the Business Agnostic Ontologies serve as foundational structures for representing and defining common concepts, relationships, and rules that are independent of specific business domains. These ontologies provide a shared understanding and semantic framework that enables interoperability, data integration, and semantic reasoning across different digital services and applications.
The Digital Public Services, as part of the application layer, leverage the Business Agnostic Ontologies to ensure consistent and meaningful representation of information and functionalities. These services align with the ontological concepts and relationships to enable seamless interactions, data exchange, and interoperability among various digital public services.
Furthermore, the Business Information Base complements the Business Agnostic Ontologies by providing a structured repository of business-related information. It serves as a valuable resource for storing and accessing domain-specific data, facilitating data sharing, and supporting decision-making processes within digital public services.
By associating the Business Agnostic Ontologies with Digital Public Services and the Business Information Base, the "semantic view - Agnostic Ontologies" enables a standardized and coherent representation of knowledge and information within the digital ecosystem. This view promotes semantic interoperability, enhances data integration, and supports advanced functionalities such as semantic search, intelligent recommendations, and context-aware decision-making.
NARRATIVE:
The SV-Data Space Policies and Contracts [Motivation] view extends Semantic view and provides a comprehensive framework for leveraging the elements of Data Space Policies and Contracts and Business Agnostic Business Information Base.
The Data Space Policies and Contracts is a Grouping ABB that serves as a catalogue for the elements it contains. This catalogue includes two Data Object ABBs: Data Policy and Data Contract. The Data Policy is a standalone element with no sub-elements, and it represents the policies that govern the data in the data space. The Data Contract, also a standalone element, represents the contracts that dictate the terms and conditions of data usage within the data space.
The Business Agnostic Business Information Base is a Diagram Model-group ABB that contains a collection of Business Object ABBs. These objects include Availability, Digital Asset, Credential, Access rights, and Transaction. Each of these elements represents different types of information that are business-agnostic, meaning they are not specific to any one business or industry.
The Availability object represents information about the availability of data or services. The Digital Asset object represents information about digital assets, which could include digital files, software, or other digital resources. The Credential object represents information about credentials, which could include usernames, passwords, or other forms of identification. The Access rights object represents information about access rights, which dictate who can access certain data or services. Lastly, the Transaction object represents information about transactions, which could include financial transactions, data transactions, or other types of exchanges.
The relationships between these elements are not explicitly defined in the JSON, but it can be inferred that the Data Space Policies and Contracts catalogue governs the data represented by the Business Object ABBs in the Business Agnostic Business Information Base. This governance could include setting policies for how the data is used (Data Policy) and establishing contracts for data usage (Data Contract). The motivation behind this structure is to provide a comprehensive framework for managing data in a way that is not specific to any one business or industry, allowing for flexibility and adaptability.
NARRATIVE:
The SV-Data Model [Motivation] view extends Semantic view and provides a comprehensive framework for leveraging the elements in the JSON data. The JSON data contains three main elements: "Business Agnostic Data Model Solutions", "Business Agnostic Business Information Base", and "Data Model".
The "Business Agnostic Data Model Solutions" is a Grouping ABB type element that encompasses two sub-elements: "Common Data Model" and "eProcurement Data Model Solutions". The "Common Data Model" is a Data Object SBB type element that represents an ontology based on the FRBR model (Functional Requirements for Bibliographic Records) using RDF(S)/OWL technologies. It is capable of representing relationships between the resource types managed by the Publications Office and their views, all within the scope of the FRBR model.
The "eProcurement Data Model Solutions" is another Grouping ABB type element that includes the "ESPD-EDM" as a sub-element. The "ESPD-EDM" is a Data Object SBB type element representing the European Single Procurement Document (ESPD), a standardized form used in public procurement processes within the European Union (EU). It serves as a preliminary self-declaration by suppliers, demonstrating their eligibility and suitability to participate in public procurement procedures across EU member states.
The "Business Agnostic Business Information Base" is a Diagram Model-group ABB type element that includes three sub-elements: "Message", "Document", and "Data Quality". Each of these sub-elements is a Business Object ABB type element representing different types of business information.
Finally, the "Data Model" is a Data Object ABB type element that aims to be a collection of entities, their properties, and the relationships among them. It focuses on formally representing a domain, a concept, or a real-world thing.
The relationships among these elements are defined by their hierarchical structure in the JSON data. The motivation behind this structure is to provide a comprehensive and structured representation of different types of data models and business information, facilitating their use in various business contexts.
NARRATIVE:
The SV-Customs Form Structure [Motivation] view extends Semantic view and provides a comprehensive framework for leveraging the structure and organization of customs forms and the information base related to customs.
The view is composed of three main elements: "Customs Forms Structure", "Customs Information Base", and "Forms Structure".
The "Customs Forms Structure" is a Grouping ABB that encompasses three Data Object SBBs: "BTI Application Form", "EUR.1 Movement Certificate", and "Single Administrative Document (SAD)". Each of these forms serves a specific purpose in the customs process, collecting and providing necessary information for customs authorities to make decisions regarding the classification, origin, and movement of goods.
The "BTI Application Form" is used to request an official binding decision from customs authorities regarding the classification of specific goods under the Harmonized System (HS). The "EUR.1 Movement Certificate" certifies the origin of goods and claims preferential treatment in international trade. The "Single Administrative Document (SAD)" is a form used for customs declarations in the EU and other countries, aiming to reduce the administrative burden and increase the standardisation and harmonisation of data collected on trade.
The "Customs Information Base" is a Diagram Model-group ABB that contains nine Business Object ABBs. These objects represent various types of information related to customs, including "Origin of goods Information", "Imports information", "Classification of goods Information", "Exports information", "Economic value Information", "Combined nomenclature", "Free circulation requirement information", "Economic Operators Registration and Identification number (EORI)", and "Economic Operators Information". Each of these objects provides crucial data for the customs process, contributing to the overall efficiency and effectiveness of customs operations.
The "Forms Structure" is a Data Object ABB that enables the implementation of the layout and organization of the fields, labels, and controls on a form used to collect or display data. This object plays a crucial role in ensuring the usability and functionality of the customs forms.
In terms of relations, the "Customs Forms Structure" and "Customs Information Base" are related in that the forms collect and provide the information represented by the Business Object ABBs in the information base. The "Forms Structure" is related to the "Customs Forms Structure" as it defines the layout and organization of the forms. The motivation behind this view is to provide a comprehensive and structured framework for managing and leveraging customs forms and related information, thereby enhancing the efficiency and effectiveness of customs operations.
Narrative:
The "Semantic view - Data Mapping" viewpoint extends semantic view and provides a comprehensive framework for managing and aligning data mappings within the digital ecosystem. This view associates the Data Mapping with the Business Information Base and Digital Public Services from the application layer.
Within this view, Data Mapping involves the translation and transformation of data representations between different formats, structures, and systems. It enables seamless data integration, interoperability, and efficient data exchange across various applications and services.
The Business Information Base, as part of the application layer, serves as a repository of business-related information that relies on data mappings. It stores and manages data using mappings that ensure data consistency and compatibility, facilitating data sharing and decision-making processes.
Digital Public Services leverage Data Mapping to ensure accurate and meaningful data exchange and integration. These services align their data models, operations, and interactions with the defined data mappings, enabling seamless integration, data consistency, and interoperability among different digital public services.
By associating the Data Mapping with the Business Information Base and Digital Public Services, the "Semantic view - Data Mapping" promotes standardized data mappings, facilitating efficient data integration and interoperability within the digital ecosystem. This view supports effective data exchange, consistent data representation, and advanced functionalities for digital public services.
NARRATIVE:
The SV-Controlled Vocabulary [Motivation] view extends Semantic view and provides a comprehensive framework for leveraging controlled vocabulary solutions in a business-agnostic manner. This view is composed of three main elements: Business Agnostic Controlled Vocabulary Solutions, Business Agnostic Business Information Base, and Controlled Vocabulary.
The Business Agnostic Controlled Vocabulary Solutions is a Grouping ABB that encompasses several Data Object SBBs. These include eGovernment Core Vocabularies, Core Assessment Vocabulary, Core Standards and Specifications Vocabulary, W3C Profiles Vocabulary, and EuroVoc. Each of these data objects represents a specific set of vocabularies or standards used for information exchange, assessment, and description of various data entities in a context-neutral manner. For instance, the eGovernment Core Vocabularies are simplified, reusable, and extensible data models that capture the fundamental characteristics of a data entity. Similarly, the Core Assessment Vocabulary defines what an 'Assessment' of 'assets' is and how to perform the assessment based on 'Criteria'.
The Business Agnostic Business Information Base is a Diagram Model-group ABB that includes two Business Object ABBs: Data Quality and Availability. These objects represent the quality and availability of the business information, respectively.
The Controlled Vocabulary is a Data Object ABB that enables a carefully curated set of terms used to describe concepts or objects in a specific field or domain. It is a standardized list of terms that are used to ensure consistency and accuracy in the indexing, searching, and retrieval of information.
The motivation behind this view is to provide a comprehensive and standardized framework for the use of controlled vocabularies in a business-agnostic manner. This ensures consistency and accuracy in the description, indexing, and retrieval of information across different business domains. It also facilitates the exchange of information and interoperability among various software solutions.
NARRATIVE:
The SV-Customs Base Registries [Motivation] view extends Semantic view and provides a comprehensive framework for leveraging data objects and business objects related to customs activities. This view is divided into three main elements: the Customs Base Registry, the Customs Information Base, and the Base Registry.
The Customs Base Registry is a Grouping ABB that encompasses six Data Object SBBs, each representing a different system or database used in customs activities. These include the REX - Registered Exporter system, EORI - Economic Operators Registration and Identification number, ICS (Import Control System), TARIC (Integrated Tariff of the European Union), VAT Information Exchange System (VIES), and AEO - Authorised Economic Operator. Each of these systems or databases serves a unique purpose in the customs process, from certifying the origin of goods and assigning unique identification numbers to economic operators, to enhancing customs control, providing tariff information, verifying VAT numbers, and recognizing businesses that meet certain criteria and demonstrate compliance with customs regulations and security standards.
The Customs Information Base is a Diagram Model-group ABB that includes nine Business Object ABBs, each representing a different type of information used in customs activities. These include Exports information, Imports information, Origin of goods Information, Economic value Information, Customs partners Information, Binding Tariffs Information, Economic Operators Registration and Identification number (EORI), Economic Operators Information, and Workforce information. These business objects provide essential information for customs activities, such as details about exports and imports, the origin of goods, economic value, customs partners, binding tariffs, registration and identification numbers for economic operators, information about economic operators, and workforce information.
The Base Registry is a Data Object ABB that refers to reliable sources of basic information that permits an efficient, secure, and transparent exchange of the data. This registry serves as a foundational element in the SV-Customs Base Registries [Motivation] view, providing the underlying data that supports the other elements in the view.
In summary, the SV-Customs Base Registries [Motivation] view provides a comprehensive framework for managing and leveraging data and information related to customs activities. It integrates various systems and databases, each serving a unique purpose in the customs process, and provides a wide range of essential information for customs activities. The Base Registry serves as the foundation for this view, providing reliable sources of basic information that enable efficient, secure, and transparent data exchange.
Narartive:
The "Semantic view - Business Agnostic Datasets" viewpoint extends semantic view and provides a comprehensive framework for managing and utilizing business agnostic datasets within the digital ecosystem. This view associates the Agnostic Datasets with the Business Information Base and Digital Public Services from the application layer.
Within this view, Agnostic Datasets represent standardized collections of data that are independent of specific business domains. These datasets adhere to common data structures, formats, and semantics, enabling interoperability, data integration, and efficient data exchange across different digital services and applications.
The Business Information Base, as part of the application layer, serves as a repository of business-related information that utilizes the Agnostic Datasets. It stores and manages domain-specific data within the standardized dataset structures, facilitating data consistency, accessibility, and sharing.
Digital Public Services leverage the Agnostic Datasets to ensure uniformity and coherence in data representation and utilization. These services align their data models, operations, and interactions with the agnostic datasets, enabling seamless integration, data consistency, and semantic interoperability among different digital public services.
By associating the Agnostic Datasets with the Business Information Base and Digital Public Services, the "Semantic view - Business Agnostic Datasets" promotes standardized data management practices and efficient data utilization within the digital ecosystem. This view supports data integration, semantic interoperability, and advanced functionalities for digital public services.
The agnostic nature of the datasets allows for flexibility and adaptability across different business domains and digital public services. It enables reusability of data structures, reduces data duplication, and promotes consistent data representation and exchange.
NARRATIVE:
The SV-Dataset [Motivation] view extends Semantic view and provides a comprehensive framework for leveraging various types of data objects and their associated metadata. This view is primarily composed of three main elements: the Business Agnostic Dataset Catalogue, the Business Agnostic Business Information Base, and the Data Objects ABBs.
The Business Agnostic Dataset Catalogue is a Grouping ABB that contains several Data Object ABBs, each representing a specific type of metadata. These include Multimedia Object Metadata, Log Metadata, Translation Item Metadata, Transaction Metadata, Exchange Item Metadata, Tender Item Metadata, and Authorised Payment Methods Metadata. Each of these metadata types provides structured information about a specific aspect of data, such as multimedia assets, log events, translation items, transactions, exchange items, tender items, and authorized payment methods. The metadata helps in identifying, organizing, retrieving, analyzing, and managing the corresponding data assets, thereby enabling efficient data operations.
The Business Agnostic Business Information Base is a Diagram Model-group ABB that contains several Business Object ABBs. These represent various types of business information, including Location, Data Quality, Payment, Transaction, Message, Document, Audit Trail, and Availability. Each of these business objects provides specific business-related information, which is crucial for the operation and management of business activities.
The Data Objects ABBs include Dataset, Reference Data, and Master Data. The Dataset ABB represents a collection of related data organized in a structured format. The Reference Data ABB enables the definition of a set of values or codes used to categorize, classify, or describe data elements in a consistent and standardized way. The Master Data ABB enables the implementation of non-transactional information that plays a key role in the core operation of a business in public administrations and is re-used for multiple purposes.
The relationships among these elements are defined by their hierarchical structure in the JSON. The Business Agnostic Dataset Catalogue and the Business Agnostic Business Information Base are at the top level, each containing several sub-elements. The Data Objects ABBs are at the same level as these two main elements, indicating their independent but equally important roles in the data architecture. The motivation behind this structure is to provide a comprehensive and flexible framework for managing a wide range of data types and their associated metadata, thereby supporting efficient data operations and business activities.
NARRATIVE:
The SV-Customs Data Models [Motivation] view extends Semantic view and provides a comprehensive framework for leveraging the customs data models. This view is composed of three main elements: the "Customs Information Base", the "Customs Data model", and the "Data Model".
The "Customs Information Base" is a Diagram Model-group ABB that encapsulates various Business Object ABBs. These include "Workforce information", "Origin of goods Information", "Internal logistic Information", "Special Procedures Information", "Economic value Information", "Customs partners Information", "Exports information", "Imports information", "Free circulation requirement information", and "Laboratories information". Each of these business objects represents a specific type of information that is crucial for customs operations.
The "Customs Data model" is a Grouping ABB that contains two Data Object SBBs: the "EU Customs Data Model" and the "WCO Data Model". The "EU Customs Data Model" is a standardized framework developed by the European Union for harmonizing and structuring data exchange in customs operations. It promotes data consistency, simplifies data integration, and supports the automation of customs procedures within the EU customs environment. On the other hand, the "WCO Data Model" has been the data foundation for global trade interoperability for over two decades. It provides a universal language for cross-border data exchange, enabling the implementation of Single Window systems and fueling Data Analytics.
Lastly, the "Data Model" is a Data Object ABB that aims to be a collection of entities, their properties, and the relationships among them. It focuses on formally representing a domain, a concept, or a real-world thing.
The motivation behind this view is to provide a comprehensive and structured framework for managing and leveraging customs data. By standardizing and harmonizing the data models, it facilitates interoperability between different customs systems and stakeholders, promotes data consistency, simplifies data integration, and supports the automation of customs procedures. This ultimately leads to reduced costs and improved efficiencies for customs operations.
Narrative:
The "Semantic view - Metadata Catalogue" extends semantic viewpoint and provides a comprehensive framework for organizing and managing metadata within the digital ecosystem. This view associates the Metadata Catalogue with the Business Information Base and Digital Public Services from the application layer.
Within this view, the Metadata Catalogue serves as a centralized repository for storing and categorizing metadata associated with digital assets, resources, and information. It enables efficient discovery, access, and management of metadata, providing essential information about the characteristics, properties, and relationships of digital entities.
The Business Information Base, as part of the application layer, relies on the Metadata Catalogue to ensure accurate and meaningful metadata integration and utilization. It utilizes the defined metadata standards and structures to enrich and describe business-related information, supporting data discovery, analysis, and decision-making processes.
Digital Public Services leverage the Metadata Catalogue to ensure consistent metadata representation and interoperability among different services. These services align their data models, operations, and interactions with the catalogued metadata, enabling efficient data exchange, integration, and discoverability within the digital ecosystem.
By associating the Metadata Catalogue with the Business Information Base and Digital Public Services, the "Semantic view - Metadata Catalogue" promotes standardized metadata management and facilitates its discoverability and reuse. This view ensures consistent metadata representation, improves data quality, and enhances interoperability within the context of digital public services.
The catalogued metadata allows for efficient search and retrieval of relevant information, supporting data discovery and analysis. It provides valuable context and insights into the digital assets, facilitating data integration, sharing, and collaboration among different applications and services.
NARRATIVE:
The SV-Customs Datasets [Motivation] view extends Semantic view and provides a comprehensive framework for leveraging various elements related to customs data. This view is composed of four main elements: "Customs Dataset Catalogue", "Customs Information Base", "Dataset", and "Customs Dataset Solutions".
The "Customs Dataset Catalogue" is a Grouping ABB that consists of multiple Data Object ABBs. These include "Customs statistical metadata on goods imported", "Applications and Requests metadata", "Laboratory reports index", "Tariffs metadata", "Risk metadata", "Origins metadata", "Cargo metadata", "Declarations metadata", "Intra-EU purchases and sales metadata", "Goods taxonomy metadata", "Notifications metadata", "Procedures metadata", "Customs statistical metadata on goods exported", "Goods metadata", and "Laboratories testing metadata". Each of these data objects represents a specific type of metadata related to customs operations.
The "Customs Information Base" is a Diagram Model-group ABB that contains various Business Object ABBs. These include "Economic Operators Registration and Identification number (EORI)", "Free circulation requirement information", "Laboratories information", "Imports information", "Combined nomenclature", "Special Procedures Information", "Customs partners Information", "Exports information", "Binding Tariffs Information", "Workforce information", "Economic value Information", "Internal logistic Information", "Origin of goods Information", "Guarantee Information", "Classification of goods Information", "Threads and fraudulent actions Information", "Economic Operators Information", "Temporary storage Information", and "Duties calculation Information". Each of these business objects represents a specific type of information related to customs operations.
The "Dataset" is a Data Object ABB that represents a collection of related data organized and presented in a structured format. This element provides a general representation of datasets in the context of customs operations.
The "Customs Dataset Solutions" is a Grouping ABB that includes two Data Object SBBs: "EORI metadata" and "Economic operators metadata". These data objects represent specific types of metadata related to customs dataset solutions.
The relationships between these elements are not explicitly defined in the JSON. However, it can be inferred that the "Customs Dataset Catalogue" and "Customs Dataset Solutions" are related to the "Dataset" as they provide specific types of metadata for datasets. Similarly, the "Customs Information Base" can be related to the "Dataset" as it provides specific types of information that can be included in datasets. The motivation behind these elements and their relationships is to provide a comprehensive and structured representation of customs data, which can be leveraged for various customs operations and solutions.
Narrative:
The "Semantic view - Datasets Catalogues" viewpoint extends semantic view and provides a comprehensive framework for organizing and managing datasets catalogues within the digital ecosystem. This view associates the Dataset Catalogues with the Business Information Base and Digital Public Services from the application layer.
Within this view, Dataset Catalogues act as centralized repositories for organizing and categorizing datasets. They enable efficient discovery, access, and management of datasets across different domains and applications. The catalogues ensure that datasets are easily searchable, accessible, and reusable, promoting data sharing and fostering collaboration.
The Business Information Base, as part of the application layer, relies on the Dataset Catalogues to ensure accurate and meaningful data integration and utilization. It utilizes the catalogued datasets to store and manage domain-specific data, enabling informed decision-making processes and supporting business operations.
Digital Public Services leverage the Dataset Catalogues to ensure seamless integration, data consistency, and interoperability among different services. These services align their data models, operations, and interactions with the catalogued datasets, facilitating data exchange and integration within the digital ecosystem.
By associating the Dataset Catalogues with the Business Information Base and Digital Public Services, the "Semantic view - Datasets Catalogues" promotes standardized dataset organization and facilitates dataset discovery and reuse. This view ensures efficient data management, improves data quality, and enhances interoperability within the context of digital public services.
The catalogued datasets allow for easy access and retrieval of relevant data, promoting data sharing and collaboration among different applications and services. They enable efficient data integration, reduce redundancy, and support consistent data representation and interpretation.
The view that relates Architecture principles to semantic view functional components is a relevant aspect of solutions architecture. This view focuses on how architecture principles influence the design and implementation of functional components within the semantic layer of a solution.
By aligning architecture principles with semantic view functional components, solutions architects ensure that the design and implementation of these components adhere to established guidelines and best practices. This alignment brings several benefits to the overall solution.
Firstly, it promotes consistency and coherence in the design of functional components. Architecture principles provide guidelines for designing semantic components that ensure a standardized approach and facilitate seamless integration and interoperability. By aligning functional components with these principles, solutions architects ensure that the semantics and data structures across the solution remain consistent, enabling efficient data exchange and integration.
Secondly, aligning architecture principles with semantic view functional components supports data integrity and quality. Architecture principles often emphasize data governance, data security, and data management practices. By incorporating these principles into the design and implementation of semantic components, solutions architects can enforce data governance policies, ensure data security measures, and maintain data quality standards. This alignment enhances the reliability and trustworthiness of the solution's data, leading to more accurate and informed decision-making.
Furthermore, aligning architecture principles with semantic view functional components improves the understandability and maintainability of the solution. Architecture principles provide guidelines for organizing and structuring functional components, making them easier to comprehend and manage. By aligning functional components with these principles, solutions architects facilitate future enhancements, updates, and maintenance of the solution, reducing the complexity and effort required for managing the semantic layer.
The view that relates Architecture principles to semantic view governance components is an essential aspect of solutions architecture. This view specifically focuses on how architecture principles influence the design and implementation of governance structures and processes within the semantic layer of a solution.
Aligning architecture principles with semantic view governance components brings several benefits to the overall solution.
Firstly, it ensures effective governance practices within the semantic layer. Architecture principles provide guidance on establishing governance structures, policies, and processes that govern the management and usage of data. By aligning governance components with these principles, solutions architects can design a robust governance framework that ensures compliance, transparency, and accountability in data management, access control, and data quality. This alignment promotes proper oversight and control over the semantic layer, facilitating efficient and secure data governance practices.
Secondly, aligning architecture principles with semantic view governance components supports data integrity and quality. Architecture principles often emphasize data governance, security, and management best practices. By incorporating these principles into the design and implementation of governance components, solutions architects can establish mechanisms for enforcing data governance policies, implementing security measures, and monitoring data quality. This alignment enhances the reliability and accuracy of data within the semantic layer, contributing to more informed decision-making and reliable business insights.
NARRATIVE:
The SV-Privacy Policy Catalogue view extends Semantic view and provides a comprehensive framework for leveraging the elements of privacy policy within an organization. This view is composed of several elements, each with a specific role and purpose.
The first element is the 'Privacy Policy', a Business Object ABB. This object regulates the personal data of any customer, client, or employee information. It sets the rules and guidelines for how personal data should be handled, stored, and processed within the organization. It is the cornerstone of the organization's privacy framework, ensuring compliance with data protection laws and regulations.
Nested within the 'Privacy Policy' are two Grouping ABBs: 'Privacy Data Policy Catalogue' and 'Customs Privacy Data Policy Catalogue'. These groupings categorize specific policies related to privacy and data protection.
The 'Privacy Data Policy Catalogue' contains the 'Anonymisation Policy', another Business Object ABB. This policy is a formal document that outlines the rules and procedures for anonymizing sensitive data. It defines the methods, techniques, and criteria used to transform personally identifiable information (PII) into a form that can no longer be linked to an individual. The policy ensures compliance with privacy regulations and helps mitigate the risk of unauthorized disclosure or misuse of personal data. It includes considerations for data anonymization processes, such as data masking, aggregation, or encryption, to protect individuals' privacy while still allowing data to be used for legitimate business purposes.
The 'Customs Privacy Data Policy Catalogue' includes the 'Confidentiality of Business Information', another Business Object ABB. This policy refers to the protection of sensitive and proprietary data belonging to a business or organization. It involves ensuring that confidential information, such as trade secrets, financial data, client lists, and marketing strategies, remains secure and is accessible only to authorized individuals within the organization. Confidentiality safeguards aim to prevent unauthorized access, use, or disclosure of such information, which could compromise the competitive advantage, reputation, or legal standing of the business.
In summary, the SV-Privacy Policy Catalogue view provides a structured and comprehensive framework for managing and implementing privacy policies within an organization. It ensures that all aspects of data privacy, from anonymization to confidentiality, are adequately addressed, thereby safeguarding the organization's data and maintaining compliance with relevant regulations.
NARRATIVE:
The SV-Data Policy Catalogue view extends Semantic view and provides a comprehensive framework for leveraging the Business Agnostic Data Policy Catalogue, which is a Grouping ABB. This catalogue includes several Business Object ABBs, each with its own specific purpose and description.
The first Business Object ABB within the Business Agnostic Data Policy Catalogue is the Interoperability Policy. This policy is a set of guidelines that ensure different systems and data within an organization or across entities work together seamlessly. It promotes the use of open standards and best practices to facilitate smooth communication and integration between various systems, applications, and stakeholders.
The second Business Object ABB is the Data Quality Framework. This framework is a structured approach or set of guidelines that organizations use to assess, measure, and improve the quality of their data. It provides a systematic framework for managing data quality throughout its lifecycle, from data collection to data analysis and decision-making.
The third Business Object ABB is the Data Governance Guidelines. These guidelines are a set of principles, rules, and practices that provide direction and guidance for managing and controlling data assets within an organization. They outline the framework for ensuring data quality, integrity, privacy, security, and compliance throughout the data lifecycle.
The fourth Business Object ABB is the Blockchain policy. This policy is a set of rules, guidelines, and controls that govern the management, access, and utilization of data within a blockchain network or ecosystem. It outlines the specific protocols, procedures, and requirements for storing, validating, and securing data on the blockchain.
Lastly, the Data Policy is a standalone Business Object ABB that aims to form the guiding framework in which data management can operate. This policy is crucial in setting the direction and standards for all data-related activities within an organization.
In summary, the SV-Data Policy Catalogue view provides a comprehensive framework that includes various policies and guidelines to ensure effective data management, interoperability, quality, governance, and security. Each of these elements plays a critical role in managing and controlling data assets, promoting data integrity, privacy, and compliance, and facilitating effective data sharing and collaboration.
A non-functional requirements catalog for a digital solution includes a set of criteria and characteristics that describe how the solution should perform, rather than what it should do.
These requirements focus on aspects such as performance, security, usability, reliability, and other quality attributes that determine the overall effectiveness and user experience of the solution.
Here are some common categories of non-functional requirements that are often included in such a catalog:
+ Performance: Defines the speed, responsiveness, scalability, and efficiency of the solution under varying conditions, such as user load, data volume, or network latency.
+ Usability: Specifies the ease of use, intuitiveness, and accessibility of the solution, ensuring that it meets the needs and expectations of its intended users.
+ Reliability: Addresses the solution's ability to consistently perform its functions accurately and reliably over time, minimizing downtime and data loss.
+ Security: Covers the protection of data, information, and system resources against unauthorized access, tampering, or breaches. It may include aspects such as authentication, encryption, and compliance with relevant security standards.
+ Availability: Describes the solution's uptime requirements, including its ability to remain accessible and operational during scheduled maintenance or unexpected outages.
+ Scalability: Defines the solution's ability to handle increasing workload or user demand by efficiently utilizing resources and adapting to changing circumstances.
+ Maintainability: Refers to the ease of maintaining and modifying the solution, including aspects such as code maintainability, documentation, and the availability of development and debugging tools.
+ Interoperability: Specifies the solution's ability to integrate and communicate with other systems or components, often through the use of standardized protocols or interfaces.
+ Compliance: Ensures that the solution adheres to relevant laws, regulations, and industry standards, such as data protection regulations or accessibility guidelines.
+ Performance Efficiency: Focuses on optimizing resource usage, minimizing energy consumption, and maximizing the efficiency of the solution's operations.
+ Testability: Defines the ease with which the solution can be tested to ensure that it meets its functional and non-functional requirements, often through the use of automated testing tools and techniques.
+ Internationalization and Localization: Addresses the solution's ability to support multiple languages, regions, and cultural conventions to cater to a global user base.
These are just some examples of non-functional requirements that may be included in a catalog for a digital solution. The specific requirements will depend on the nature of the solution, its intended use, and the stakeholders' needs.
The Enterprise Architecture Framework (EAF) alignment guidelines viewpoint serves as an integral part of the process, aiming to establish a harmonious relationship between the European Interoperability Reference Architecture (EIRA) model and any given Enterprise Architecture Framework (EAF). The ultimate goal is to make the EIRA model fully compliant with the chosen EAF, promoting uniformity across the architectural ecosystem.
In this alignment diagram, each Architectural Building Block (ABB) carries a specific connection to the EIRA's Legal, Organisational, Semantic, and Technical (LOST) views that it belongs to. Each ABB forms a critical component of the architecture, representing distinct facets of the EIRA in the broader context of the selected EAF. This viewpoint connects different layers of the enterprise architecture, creating a comprehensive picture of the interoperability landscape.
The intricate ties between each ABB and their corresponding LOST views can be thoroughly explored on the [Properties] sheet under the [Analysis] tab of Archi, a visual modelling and management tool for enterprise architecture. Here, users can investigate each ABB, understanding its role, its relationship with the LOST views, and its part in securing compliance with the EAF.
The EAF alignment guidelines viewpoint allows organizations to align with industry standards, facilitates interoperability, and bridges the EIRA model with the selected EAF. It assists an organization in effectively detailing their enterprise architecture in line with their specific needs while maintaining alignment with larger industry frameworks.
The viewpoint provides a structured layout, enhancing strategic decision-making, facilitating effective communication, and aiding the integration of different architectural elements. This organized alignment fortifies the architecture's robustness and provides a pathway for strategic expansion and evolution.
The IT Architecture Decision Records (ADRs) catalogue of a digital solution refers to a collection of documents that capture and document important architectural decisions made during the development and evolution of the solution.
These records serve as a valuable reference for the project team, stakeholders, and future developers, providing insights into the rationale behind key design choices and the impact of those decisions.
The ADR catalogue typically includes the following elements:
+ Title/Identifier: Each ADR is assigned a unique title or identifier to enable easy identification and retrieval.
+ Context: This section provides a brief overview of the background and context that led to the architectural decision. It may include factors such as business requirements, technical constraints, or market considerations.
+ Decision: This section outlines the specific decision made, describing the chosen solution or approach in detail. It should clearly articulate the problem being addressed and the solution chosen.
+ Alternatives Considered: It is essential to document alternative solutions or approaches that were evaluated before settling on the chosen decision. This helps to understand the reasoning behind the selected option.
+ Rationale: The rationale section explains the reasoning behind the decision. It may include factors such as performance, scalability, security, cost, maintainability, compatibility, or other relevant considerations.
+ Implications: This section discusses the potential impact of the decision on the system, including any anticipated benefits, drawbacks, risks, or dependencies introduced by the chosen approach.
+ Related ADRs: If the decision has dependencies or relationships with other ADRs, those connections should be documented in this section. It helps in establishing the traceability and understanding the interconnectedness of decisions.
+ Status and Date: Each ADR should include the current status (e.g., proposed, accepted, rejected, superseded) and the date when the decision was made or recorded.
By maintaining a comprehensive ADR catalogue, organizations can foster transparency, facilitate collaboration, and ensure consistency in architectural decision-making across teams and projects.
It serves as a knowledge repository and assists in understanding the evolution and reasoning behind the architecture of a digital solution.
The European Interoperability Framework underlying principles view models the motivation of the EIRA© in terms of goals to be achieved and the principles to be followed in order to achieve interoperability in public services.
The interoperability principles are fundamental behavioural aspects to drive interoperable public services. They describe the context in which European public services are designed and implemented.
The twelve underlying principles of the EIF are grouped into four categories:
1. Principle setting the context for EU actions on interoperability (Subsidiarity and proportionality);
2. Core interoperability principles (Openness, Transparency, Reusability, Technological neutrality and data portability);
3. Principles related to generic user needs and expectations (User-centricity, Inclusion and accessibility, Security and privacy, Multilingualism);
4. Foundation principles for cooperation among public administrations (Administrative simplification, Preservation of information, Assessment of Effectiveness and Efficiency).
The "Not Implemented Architecture Principles Catalogue":
Despite the vital role architecture principles play, there are situations where certain principles may not be employed within a specific solution architecture. It is important to maintain transparency and ensure that these omissions are duly noted and communicated. The "Not Implemented Architecture Principles Catalogue" serves as a repository for documenting such cases.
Including explanatory notes alongside each omitted principle is crucial. These notes should provide a clear rationale for the exclusion, explaining the context, constraints, or trade-offs that led to the decision. By doing so, the documentation acts as a reference for future architects, fostering a deeper understanding of the architectural choices made and promoting informed decision-making.
Benefits of Documenting Omitted Principles:
Knowledge Sharing: The catalogue facilitates knowledge sharing among architects by capturing the context and rationale behind each omitted principle. This ensures that valuable insights are not lost, enabling future architects to make informed decisions based on prior experiences.
Governance and Compliance: The documentation of omitted principles helps ensure that architectural decisions align with organizational governance frameworks and compliance requirements. It provides visibility into the reasons behind deviations from standard architectural practices, allowing stakeholders to assess risks and make informed judgments.
Risk Management: Identifying and acknowledging the absence of certain architecture principles helps uncover potential risks and trade-offs associated with the solution architecture. It enables architects to proactively address these risks and develop mitigation strategies.
Continuous Improvement: The documentation of omitted principles promotes a culture of continuous improvement. It encourages architects to revisit decisions, reassess trade-offs, and learn from past experiences, ultimately refining their approach to solution architecture.
The European Interoperability Framework underlying principles view models the motivation of the EIRA© in terms of goals to be achieved and the principles to be followed in order to achieve interoperability in public services.
The interoperability principles are fundamental behavioural aspects to drive interoperable public services. They describe the context in which European public services are designed and implemented.
The twelve underlying principles of the EIF are grouped into four categories:
1. Principle setting the context for EU actions on interoperability (Subsidiarity and proportionality);
2. Core interoperability principles (Openness, Transparency, Reusability, Technological neutrality and data portability);
3. Principles related to generic user needs and expectations (User-centricity, Inclusion and accessibility, Security and privacy, Multilingualism);
4. Foundation principles for cooperation among public administrations (Administrative simplification, Preservation of information, Assessment of Effectiveness and Efficiency).
Narrative: The twelve interoperability principles of the New EIF ([Subsidiarity and proportionality], [Openness], [Transparency], [Transparency], [Technological neutrality and data portability], [User-centricity], [Inclusion and accessibility], [Security and privacy], [Multilingualism], [Administrative simplification], [Preservation of information] and [Assessment of Effectiveness and Efficiency]) together fulfil the goals of achieving interoperability: [Achieve Legal Interoperability], [Achieve Organisational Interoperability], [Achieve Semantic Interoperability] and [Achieve Technical Interoperability].
Source: The New EIF. https://ec.europa.eu/isa2/eif_en
The new European Interoperability Framework (EIF) is part of the Communication (COM(2017)134) from the European Commission adopted on 23 March 2017. The framework gives specific guidance on how to set up interoperable digital public services.
The view that relates Architecture principles to infrastructure layer view functional components is crucial in solutions architecture. This view focuses on how architecture principles influence the design and implementation of functional components within the technical layer.
By aligning architecture principles with technical layer view functional components, solutions architects ensure consistency, enhance performance and scalability, promote reusability and maintainability, and support regulatory compliance. This alignment leads to the creation of robust and efficient applications within the technology layer, enabling seamless integration, optimal user experience, reduced maintenance effort, and adherence to legal and industry standards.
In summary, aligning Architecture principles with technical layer view functional components ensures consistency, enhances performance and scalability, promotes reusability and maintainability, and supports regulatory compliance. By following these principles, solutions architects can design robust and efficient applications within the technical layer.
The view connects Architecture principles to technical view and the governance components. It is a relevant aspect of solutions architecture. This view specifically examines how architecture principles influence the design and implementation of governance structures within the application layer of a solution.
Firstly, it establishes effective governance within the application layer. Architecture principles provide guidance on defining governance structures, policies, and processes for application and infrastructure development and management. By aligning governance components with these principles, solutions architects design a robust governance framework that promotes compliance, transparency, and accountability in application development, configuration, and operations. This alignment ensures proper control and management of applications, reducing risks and enhancing overall governance practices.
Secondly, aligning architecture principles with governance components supports optimized application development and deployment. Architecture principles often emphasize best practices for application design, scalability, and performance optimization. By incorporating these principles into the design and implementation of governance components, solutions architects establish mechanisms for enforcing design patterns, scalability approaches, and performance monitoring.
Narrative:
The Orchestration Infrastructure Enablers view provides insights into the relationship between the infrastructure enablers for orchestration and the orchestration enablers at the application level. This view highlights the importance of a robust and efficient infrastructure to support the seamless coordination and automation of business processes.
At the infrastructure layer, several elements are involved in enabling orchestration. The Management Infrastructure Enablers play a vital role in providing the necessary tools and capabilities for managing and monitoring the orchestration processes. These enablers include components such as logger technology services, audit manager technology services, telemetry technology services, and management console technology services. They enable organizations to effectively manage and control the execution of orchestrated workflows.
Additionally, the Workflow Orchestration Infrastructure Enablers provide the foundational components for modelling, executing, and monitoring complex business workflows. These enablers encompass workflow engines, service buses, event managers, and process managers. They are designed to support the seamless execution and coordination of business processes across different systems and services.
Furthermore, the Containers Infrastructure Enablers play a crucial role in providing the necessary runtime environment for orchestrating and deploying containerized applications. These enablers include container orchestrator technology services, container manager technology services, container registry technology services, and containers themselves. They enable organizations to encapsulate and manage their applications in lightweight, isolated containers, facilitating easy deployment and scalability.
The orchestration enablers at the application level work in collaboration with the infrastructure enablers to facilitate the seamless automation of business processes. These enablers include components and services that support activities such as process modelling, integration, event handling, and service orchestration. They empower organizations to define and automate their business workflows, integrating disparate systems and services into cohesive end-to-end processes.
The synergy between the orchestration infrastructure enablers and the orchestration enablers at the application level is essential for the success of process automation initiatives. The infrastructure enablers provide the necessary runtime environment, management capabilities, and containerization support to execute orchestrated processes, while the orchestration enablers empower organizations to design and configure complex business workflows.
By establishing a strong connection between the orchestration infrastructure enablers and the orchestration enablers at the application level, organizations can achieve streamlined and efficient business operations. This enables organizations to automate repetitive tasks, improve process visibility and control, and enhance overall operational efficiency.
NARRATIVE:
The TVI-Analytics Infrastructure Enablers [Motivation] view extends Technical view - infrastructure and provides a comprehensive framework for leveraging the elements of the Analytics Infrastructure Enablers and Analytics Enablers.
The Analytics Infrastructure Enablers is a Grouping ABB that refers to the set of components and services that support the development and deployment of data analytics solutions. This group includes four Technology Service ABBs: Analytics, Business Intelligence, Databricks, and Data Catalog.
The Analytics ABB is a Technology service that enables the procedures of analysing a great amount of raw data to make conclusions about specific information. The Business Intelligence ABB is a Technology Service that enables the procedure of collecting, storing, and analysing the data produced by the public administration to improve and optimise decisions and performance. The Databricks ABB is a Technology Service that enables the procedures of a collaborative workspace to process large amounts of public administration data. The Data Catalog ABB is a Technology Service that enables the procedures of a centralised metadata repository to provide information about the data assets in a public administration.
The Analytics Enablers is another Grouping ABB that refers to components and services that serve any current or future Digital Service Infrastructure (DSI) requiring data analysis capabilities. This group includes five Application Component and Service ABBs: Data Analytics, Big Data Analytics, Data Analytics, Business Intelligence, and Smart queue management.
The Data Analytics ABB is an Application Component that enables the implementation of procedures to analyze data and extract insights that can be used to improve business decision-making, optimize business processes, and drive innovation. The Big Data Analytics Application service refers to a software application or platform that leverages advanced analytics techniques to process and analyze large and complex datasets, commonly known as big data. It enables organizations to derive valuable insights, identify patterns, trends, and correlations, and make data-driven decisions. The service typically includes data ingestion, storage, processing, and visualization capabilities, as well as advanced analytics techniques such as machine learning, natural language processing, and predictive modeling. The Data Analytics ABB is an Application Service that enables the use of procedures to analyze data and extract insights that can be used to improve business decision-making, optimize business processes, and drive innovation. The Business Intelligence and Smart Queue Management are both Application Services with unspecified descriptions in this context.
The motivation behind these elements and their relations is to provide a comprehensive framework that supports the development, deployment, and enhancement of data analytics solutions, enabling better decision-making, business process optimization, and innovation within the public administration.
NARRATIVE:
The TVI-Trust Infrastructure Enablers [Motivation] view extends Technical view - infrastructure and provides a comprehensive framework for leveraging various components and services to build a secure and trustworthy environment for data sharing and transactions.
The view consists of several elements grouped into four main categories: Blockchain Infrastructure Enablers, Trust Infrastructure Enablers, Trust Enablers, and Dataspace Enablers.
Blockchain Infrastructure Enablers ABB is a grouping of components and services that allow for the construction of a digital ledger infrastructure of interconnected nodes. This includes the Immutable Database Manager ABB, Blockchain Ledger ABB, and Distributed Blockchain Network ABB. These technology services enable the management of immutable data, recording and sharing of transactions in an electronic ledger, and the implementation of tokens in a blockchain network, respectively.
Trust Infrastructure Enablers ABB is a grouping devoted to creating and managing public keys for encryption, a common method of securing data transfers on the internet. This includes the PKI Certificate Manager ABB, a technology service that enables the issuance, maintenance, and revocation of public key certificates.
Trust Enablers ABB is a grouping that facilitates the establishment and maintenance of secure cross-border transactions and interactions. It includes several application services such as e-Seal Preservation, e-Timestamp Verification and Validation, Registered Electronic Delivery, e-Seal Verification and Validation, e-Signature Creation, e-Signature Preservation, e-Signature Verification and Validation, e-Seal Creation, and e-Timestamp Creation. These services enable various procedures related to electronic signatures, timestamps, and seals, extending their trustworthiness and verifying their validity.
Dataspace Enablers ABB is a grouping that supports the creation and management of a dataspace. It includes the Dataspace, Dataspace Connector, Dataspace Connector Consumer, and Dataspace Connector Provider application services. These services enable the creation of a single market for data, easy and trustworthy data sharing, data gathering and accessibility, and control over data use in the dataspace ecosystem, respectively.
The motivation behind these groupings and services is to provide a secure and trustworthy environment for data sharing and transactions, leveraging blockchain technology, trust infrastructure, and dataspace capabilities. This view provides a comprehensive framework for understanding and implementing these elements in a cohesive and effective manner.
NARRATIVE:
The TVI-Digital Workplace Infrastructure Enablers [Motivation] view extends Technical view - infrastructure and provides a comprehensive framework for leveraging the capabilities of digital workplace infrastructure enablers and digital workplace enablers.
The Digital Workplace Infrastructure Enablers ABB is a Grouping that enables the set of components and services that enable organizations to create and manage virtual workplaces environments and facilitate their access remotely. This grouping includes the Remote Desktop ABB, a Technology Service that enables the procedures to grant users to access and control a computer or device from a remote location using a network connection.
The Digital Workplace Enablers is another Grouping that refers to components or services that enable the collaboration of work aspects while security and privacy are ensured. This grouping includes several Application Services and an Application Component.
The Digital Workplace ABB is both an Application Service and an Application Component that enables the procedures to freely collaborate independently from the location and boundaries while maintaining high-security standards and increasing productivity and efficiency.
The Training and Learning Management building block is an application service that helps organizations efficiently plan, administer, deliver, and track training and learning activities. It provides a comprehensive platform for managing courses, registrations, content delivery, assessments, certifications, and reporting.
The Digital Collaboration is an Application Service that facilitates digital collaboration among team members.
The Learning Platform System is a software application service that provides a comprehensive platform for managing and delivering learning content and experiences. It enables organizations to create, manage, and deliver various types of learning materials, such as courses, training modules, assessments, and educational resources.
The Remote Collaboration and Communication is a software application service that enables individuals or teams to collaborate and communicate effectively, regardless of their physical locations. It provides tools and features such as video conferencing, instant messaging, document sharing, and virtual whiteboards to support real-time or asynchronous interactions.
These elements are interconnected and work together to enable a digital workplace that is secure, efficient, and productive. The motivation behind this view is to leverage technology to facilitate remote work and collaboration, enhance learning and development, and improve organizational efficiency and productivity.
For eGovera, there were 3 motivational views related to the management Infrastructure Enablers. We created the unique motivational access.
NARRATIVE:
The TVI-Management Infrastructure Enablers [Motivation] view extends Technical view - infrastructure and provides a comprehensive framework for leveraging various elements that enable the management of IT platforms, data spaces, security, privacy, and orchestration in a public administration context.
The view is divided into several groupings, each containing elements that contribute to the overall management infrastructure. The first grouping, API Enablers, includes components and frameworks that support the implementation and cataloguing of open software interfaces. This includes elements like the Service Registry, which enables the registering of system services, and the API Catalogue, which is a collection of open software interfaces.
The second grouping, Management Infrastructure Enablers, refers to the set of components and services that manage a public administration's IT platforms efficiently. This includes elements like the Logger, which records events within a system, and the Management Console, which provides a centralised interface for managing and monitoring digital platforms.
The third grouping, Dataspace Enablers, refers to components and services that support the creation and management of a dataspace. This includes elements like the Dataspace, which is a virtual space for integrating and making data available, and the Dataspace Connector, which enables easy and trustworthy data sharing.
The fourth grouping, Security Enablers, includes components that enable the implementation and management of security controls and measures. This includes elements like the Audit, which ensures the correct behaviour, security, and compliance of different building blocks.
The fifth grouping, Privacy Enablers, refers to components and services that facilitate the implementation of privacy-related functionality. This includes elements like the Privacy service, which enables functionalities such as storing, securing, and anonymising personal data.
The final grouping, Orchestration Enablers, refers to the components and practices that support the development and deployment of orchestration applications. This includes elements like the Orchestration service, which defines the sequence and conditions in which one service invokes other services.
Overall, the TVI-Management Infrastructure Enablers [Motivation] view provides a comprehensive framework for leveraging various elements to enable efficient and effective management of IT platforms, data spaces, security, privacy, and orchestration in a public administration context.
NARRATIVE:
The TVI-Data Management and Knowledge Discovery Infrastructure Enablers [Motivation] view extends Technical view - infrastructure and provides a comprehensive framework for leveraging various elements related to data management and knowledge discovery.
The view consists of several Grouping ABBs, each containing multiple elements. The first Grouping ABB is "Database Infrastructure Enablers", which enables tools and technology services for efficient data management and operation under a storage system. It includes Technology Service ABBs such as "Relational Database Manager", "Object-Oriented Database Manager", "NoSQL Database Manager", "Graph Database Manager", and "Database Cache Manager". These services implement the behavior of various software systems that manage and manipulate different types of databases.
The second Grouping ABB is "Storage Infrastructure Enablers", which facilitates efficient and effective data storage. It includes Technology Service ABBs like "File Storage", "Block Storage", "Distributed File System", and "Backup". These services implement the behavior of software tools that manage data storage in various forms.
The third Grouping ABB is "Data Lake Infrastructure Enablers", which helps organizations build and maintain a robust data lake infrastructure. It includes a Technology Service ABB called "Data Lake Storage", which implements the behavior of a storage repository that allows organizations to store large amounts of structured, semi-structured, and unstructured data at any scale.
The fourth Grouping ABB is "Data Management Enablers", which supports effective data management practices and procedures. It includes Application Component ABBs and Application Service ABBs such as "Data Publication", "Forms Management", "Content Management", "Data Management", "e-Archiving", "Metadata Management", "Data Quality", "Data Extraction, Transformation, and Loading", "Data Persistence", "Data Virtualization", "Multimedia distribution", "Submission Service", "Transaction Management", "Archival Information Packages", "Trusted Digital Repositories", "Service Metadata Publisher", "CRM", "Data Publication", "Forms Management", "Data Extraction, Transformation and Loading", "Data Virtualization", "eFiles Management", "Service Metadata Locator", "Open Data Management", and "Contact Management". These services and components enable various functionalities related to data management.
The fifth Grouping ABB is "Knowledge Discovery Enablers", which facilitates the process of discovering insights and knowledge from data. It includes an Application Component ABB called "Knowledge Discovery" and a Data Object ABB called "Knowledge Triplestore", which enable the extraction of previously unknown, potentially useful information from data.
The final Grouping ABB is "Dataspace Enablers", which supports the creation and management of a dataspace. It includes Application Service ABBs such as "Dataspace", "Dataspace Connector", "Dataspace Connector Consumer", and "Dataspace Connector Provider". These services enable the creation of a single market for data by integrating, transforming, and making available such data.
The motivation behind this view is to provide a comprehensive framework for leveraging various elements related to data management and knowledge discovery, enabling organizations to effectively manage their data and extract valuable insights from it.
NARRATIVE:
The TVI-Application Integration Infrastructure Enablers [Motivation] view extends Technical view - infrastructure and provides a comprehensive framework for leveraging various elements that facilitate the integration of disparate applications and systems within an organization.
The view is divided into several groupings, each containing elements that serve specific functions. The first grouping is the "Application Integration Infrastructure Enablers", which includes technology services such as the Enterprise Service Bus, API Manager, GraphQL Server, Serverless Orchestrator, Application Server, Event Manager, and API Gateway. These services enable the integration between applications by performing various tasks such as data transformation, connectivity handling, message routing, communication protocol conversion, and managing the composition of multiple requests.
The second grouping is "API Enablers", which refers to components and frameworks that support the implementation and cataloguing of software interfaces. This includes application components like the Service Registry and API Catalogue, and application interfaces such as Web Service, API, ePayment, eInvoicing, eTendering, eProfessional Qualification, Geo-Localization, eProcurement, Supply Chain Management, eQualification, eNotification, ERP System, Financial Management, Log Management, Service Discovery and Registry, API Discovery and Catalogue, and Service Registry.
The third grouping is "Content Delivery Infrastructure Enablers", which includes technology services like the Web Server and Streaming Server. These services enable the delivery of digital content such as web pages, videos, images, and audio files to end-users.
The fourth grouping is "Management Infrastructure Enablers", which includes technology services like Logger, Audit Manager, Telemetry, and Management Console. These services enable the efficient management of a public administration's IT platforms.
The final grouping is "Dataspace Enablers", which includes application services like Dataspace, Dataspace Connector, Dataspace Connector Consumer, and Dataspace Connector Provider. These services support the creation and management of a dataspace, enabling the integration, transformation, and availability of data.
Each of these elements plays a crucial role in the overall application integration infrastructure, contributing to the efficient and effective functioning of an organization's IT systems. The motivation behind this view is to provide a comprehensive framework that facilitates the integration of disparate applications and systems, thereby enhancing the organization's operational efficiency and effectiveness.
NARRATIVE:
The TVI-Wide Area Networking [Motivation] view extends Technical view - infrastructure and provides a comprehensive framework for leveraging different types of networks to enable communication and data exchange across geographically dispersed locations. This view is primarily composed of two main elements: 'Wide Area Networking' and 'Secure Public Network Solutions'.
The 'Wide Area Networking' is a Grouping ABB that encompasses different networks to facilitate communication and data exchange. Within this grouping, there are two Communication Network ABBs: 'Public Network' and 'Secure Public Network'. The 'Public Network' is a communication network that allows access to the public, including public administrations, businesses, and citizens, without specific authorisations. Interoperable European Solutions can rely on these Public Networks, such as the Internet, to realise the physical communication between nodes. On the other hand, the 'Secure Public Network' is a communication network that also enables public access but is specifically designed and configured to protect against unauthorized access and cyber threats.
The second main element in this view is the 'Secure Public Network Solutions', another Grouping ABB. This grouping includes two Communication Network SBBs: 'Common Communication Network (CCN)' and 'Common Communication Network 2 (CCN 2)'. Both of these networks are part of the Secure Public Network Solutions, indicating that they are designed to provide secure communication channels.
In terms of relations and motivations, the 'Wide Area Networking' grouping is motivated by the need to enable communication and data exchange across geographically dispersed locations. The inclusion of both 'Public Network' and 'Secure Public Network' within this grouping suggests a motivation to cater to different levels of security requirements. Similarly, the 'Secure Public Network Solutions' grouping, including the 'CCN' and 'CCN 2' networks, is motivated by the need for secure communication solutions. The presence of these two networks indicates a motivation to provide options for secure communication, catering to different needs or contexts.
NARRATIVE:
The TVI-Workflow Orchestration and Containers Infrastructure Enablers [Motivation] view extends Technical view - infrastructure and provides a comprehensive framework for leveraging different components and services that enable the coordination and automation of workflows across multiple systems, applications, and organizations.
The view is divided into four main elements: Workflow Orchestration Infrastructure Enablers, Orchestration Enablers, Management Infrastructure Enablers, and Containers Infrastructure Enablers.
The Workflow Orchestration Infrastructure Enablers group includes the Business Process Manager, a technology service that coordinates the behavior of people, systems, information, and things to produce business outcomes in support of a business strategy.
The Orchestration Enablers group refers to the components and practices that support the development and deployment of orchestration applications. It includes the Orchestration Service, an application service that defines the sequence and conditions in which one service invokes other services to realize some useful function. It also includes the Orchestration Application Component, which enables the coordination and management of the execution of multiple components or services within an application or system. Lastly, it includes the Workflow Management Application Service, a software solution or service that enables the design, execution, and coordination of workflows within an organization.
The Management Infrastructure Enablers group refers to the set of components and services to manage a public administration IT platforms efficiently and efficiently. It includes the Logger, a technology service that records events or messages within a system or application. It also includes the Audit Manager, a technology service that manages audits and workflows, tracks audit progress, and ensures compliance with regulations and standards. Additionally, it includes the Telemetry, a technology service that measures and analyses information about public administration services and IT platforms to track performance and identify issues. Lastly, it includes the Management Console, a technology service that provides a centralized interface to manage and monitor digital platforms.
The Containers Infrastructure Enablers group includes components and services enabling a virtual packaging code and isolated applications for deployment of public services. It includes the Containers Manager, a technology service that organizes, adds, or replaces large numbers of software containers. It also includes the Containers Orchestrator, a technology service that automates the deployment, management, scaling, and networking of containers. Additionally, it includes the Container Registry, a technology service that stores and accesses container images. Lastly, it includes the Container, a system software that packages application code, along with its libraries and dependencies, in common ways so that it can be run anywhere, whether it be on a desktop, traditional IT, or the cloud.
This relation needs a revision due to it is transversal to all shared services.
NARRATIVE:
The TVI-Networking Infrastructure Enablers [Motivation] view extends Technical view - infrastructure and provides a comprehensive framework for leveraging various components and services that facilitate the creation and operation of computer networks. This view is divided into two main elements: Networking Infrastructure Enablers and Shared Platform.
The Networking Infrastructure Enablers ABB is a grouping of components and services that include both hardware and software technologies essential for building and maintaining modern networks. It consists of several elements such as Private Network, Firewall, Load Balancer, Router, Private Subnetwork, Domain Name Service, Virtual Private Network, and Gateway. These elements enable the implementation of various network functionalities such as physical communication, network security, traffic distribution, network connection, IP address translation, and protocol conversion.
The Shared Platform ABB is an application component that sets technical reusable resources with convergence power, enabling interoperability from a technical perspective across levels in a public administration, cross public administrations, and cross borders. It includes several groupings such as API Enablers, Orchestration Enablers, Security Enablers, Test Enablers, Trust Enablers, Data Exchange Enablers, Data Management Enablers, Privacy Enablers, Knowledge Discovery Enablers, Analytics Enablers, Translation Enablers, Digital Workplace Enablers, Artificial Intelligence Enablers, Dataspace Enablers, Schedule Management Enablers, Messaging Enablers, Observability and Monitoring Enablers, and Containerization Enablers. These groupings refer to components and services that support various functionalities such as software interfaces, orchestration applications, security controls, conformance testing, secure-cross borders transactions, data exchange, data management, privacy-related functionality, knowledge discovery, data analysis, language translation, digital workplace, artificial intelligence, dataspace creation, schedule management, messaging, observability and monitoring, and containerization.
The motivation behind this view is to provide a comprehensive framework that leverages various components and services to facilitate the creation and operation of computer networks. This framework aims to enable interoperability from a technical perspective across levels in a public administration, cross public administrations, and cross borders. It also supports various functionalities such as software interfaces, orchestration applications, security controls, conformance testing, secure-cross borders transactions, data exchange, data management, privacy-related functionality, knowledge discovery, data analysis, language translation, digital workplace, artificial intelligence, dataspace creation, schedule management, messaging, observability and monitoring, and containerization.
Populate with elegible Applications and Infrastructure Enablers based on the deployment model
NARRATIVE:
The TVI-Artificial Intelligence Infrastructure Enablers [Motivation] view extends Technical view - infrastructure and provides a comprehensive framework for leveraging the capabilities of artificial intelligence (AI) in an organization. This view is composed of two main groupings: Artificial Intelligence Infrastructure Enablers and Artificial Intelligence Enablers.
The Artificial Intelligence Infrastructure Enablers grouping refers to a set of components that facilitate the development and deployment of artificial intelligence applications. Within this grouping, there is a Technology Service ABB named Machine Learning. This service enables the procedures for implementing algorithms and models that can learn from and make predictions on data. The Machine Learning service is a critical component of the AI infrastructure, providing the necessary tools and capabilities for data analysis and predictive modeling.
The Artificial Intelligence Enablers grouping refers to components and services that provide the necessary infrastructure and resources for AI developers to build intelligent systems. These systems can perform tasks that typically require human-like intelligence, such as perception, reasoning, learning, and decision-making. Within this grouping, there are several elements:
1. Artificial Intelligence as an Application Service ABB: This service enables the procedures to display intelligent behavior by analyzing their environment and taking actions with some degree of autonomy to achieve specific objectives.
2. Artificial Intelligence as an Application Component ABB: This component enables the implementation of algorithms, machine learning, and deep learning techniques to enable machines to perform tasks that typically require human-like intelligence.
3. Machine Learning as an Application Service ABB: This service enables systems to automatically learn and improve from experience without being explicitly programmed. It involves the development and deployment of algorithms and models that can analyze large volumes of data, identify patterns, and make predictions or decisions based on the learned patterns.
4. Artificial Intelligence Engine as an Application Service ABB: This service refers to a software component or service that encompasses the core capabilities of an AI system. It provides a set of algorithms, models, and tools that enable the development, deployment, and execution of AI applications.
5. Natural-Language Processing (NLP) as an Application Service ABB: This service enables the understanding, interpretation, and generation of human language in a valuable way.
The motivation behind this view is to provide a comprehensive framework for leveraging AI capabilities, facilitating the development and deployment of AI applications, and providing the necessary infrastructure for AI developers to build intelligent systems.
NARRATIVE:
The TVI-Identity and Access Infrastructure Enablers [Motivation] view extends Technical view - infrastructure and provides a comprehensive framework for leveraging various components and services that facilitate identity and access management solutions, security controls, and privacy-related functionality within an application or system.
The view is divided into four main groupings: Identity and Access Infrastructure Enablers, Security Enablers, Management Infrastructure Enablers, and Privacy Enablers.
The Identity and Access Infrastructure Enablers grouping includes Technology Service ABBs like Identity Provider, Federated Identity Provider, Active Directory, and Lightweight Directory Access Protocol. These services provide the underlying functionality to implement identity and access management solutions, including user authentication, access to online resources, and maintaining distributed directory information services over an IP network.
The Security Enablers grouping includes Application Service ABBs and Application Component ABBs such as Audit, Authentication, Registration, Identification, Access Management, Identity Management, Authorisation, Accounting, and Request Validation. These components enable the implementation and management of security controls and measures, ensuring the correct behaviour, security, and compliance of different building blocks.
The Management Infrastructure Enablers grouping includes Technology Service ABBs like Logger, Audit Manager, Telemetry, and Management Console. These services enable efficient management of public administration IT platforms, including recording system events, managing audits, tracking performance, and identifying issues.
The Privacy Enablers grouping includes Application Service ABB and Application Component ABB named Privacy. These components facilitate the implementation of privacy-related functionality within an application or system, such as storing, securing, anonymising, pseudonymising, rectifying, and erasing personal data.
The motivation behind this view is to provide a comprehensive framework that leverages various components and services to ensure secure and efficient identity and access management, security controls, and privacy-related functionality within an application or system.
Narrative:
The Identity Access Infrastructure focuses on managing user identities and their access privileges. It encompasses the [Identity Provider Technology Service], which enables the secure identification and authentication of users, and the [Federated Identity Provider Technology Service], which allows seamless integration with external identity providers. Additionally, the [Lightweight Directory Access Technology Service] facilitates efficient storage and retrieval of user and access information.
To strengthen security and privacy within the technical view, the access and identity infrastructure relates to various security application services. These services include robust encryption mechanisms, secure communication protocols, and threat detection and prevention systems. By integrating these security application services, the access and identity infrastructure ensures the confidentiality, integrity, and availability of sensitive data and resources.
Moreover, privacy enablers are incorporated into the access and identity infrastructure to comply with privacy regulations and protect user data. These enablers encompass mechanisms for data anonymization, consent management, and data retention policies. By implementing these privacy enablers, organizations can demonstrate their commitment to privacy protection and establish trust with their users.
By extending the narrative to include the Technical view - access and identity infrastructure, organizations can establish a secure and privacy-conscious foundation for their digital solutions. This view leverages the Management Infrastructure Enablers and Identity Access Infrastructure, while integrating security application services and privacy enablers to safeguard sensitive information, ensure proper user authentication and authorization, and adhere to privacy regulations. By doing so, organizations can provide a trusted and secure environment for their users while maintaining compliance with relevant security and privacy standards.
NARRATIVE:
The TVI-Computing Infrastructure Enablers [Motivation] view extends Technical view - infrastructure and provides a comprehensive framework for leveraging various components and services that facilitate the development, deployment, and management of virtual and computing infrastructure. This view is divided into several groups, each containing different elements that contribute to the overall computing infrastructure.
The first group, "Computing Infrastructure Enablers", includes two Node ABBs: "Virtual Machine" and "Server". The Virtual Machine ABB enables the emulation of a physical computer to run programs and deploy applications, while the Server ABB enables access to resources or services to other computers or devices on a network.
The second group, "Artificial Intelligence Enablers", contains several Application Service ABBs and Application Component ABBs that provide the necessary infrastructure and resources for AI developers to build intelligent systems. These include "Artificial Intelligence", "Machine learning", "Artificial Intelligence Engine", and "Natural-Language Processing (NLP)".
The third group, "Analytics Enablers", refers to components and services that serve any current or future Digital Service Infrastructure (DSI) requiring data analysis capabilities. This group includes "Data Analytics", "Big Data Analytics", "Business Intelligence", and "Smart queue management".
The fourth group, "Data Management Enablers", refers to components and services that support effective data management practices and procedures. This group includes "Data Publication", "Forms Management", "Content Management", "Data Management", "e-Archiving", "Metadata Management", "Data Quality", "Data Extraction, Transformation, and Loading", "Data Persistence", "Data Virtualization", "Multimedia distribution", "Submission Service", "Transaction Management", "Archival Information Packages", "Trusted Digital Repositories", "Service Metadata Publisher", "CRM", "Data Publication", "Forms Management", "Data Extraction, Transformation and Loading", "Data Virtualization", "eFiles Management", "Service Metadata Locator", "Open Data Management", "Contact Management".
The fifth group, "Orchestration Enablers", refers to the components and practices that support the development and deployment of orchestration applications. This group includes "Orchestration" and "Workflow Management".
The final group, "Data Exchange Enablers", refers to tools or components that facilitate the exchange of data between systems or applications. This group includes "Data Exchange", "Once-Only Technical System", and "Data Exchange".
Each of these groups and their elements play a crucial role in the overall computing infrastructure, providing the necessary tools and services to facilitate the development, deployment, and management of various applications and systems.
Architecture principles play a vital role in shaping the overall implementation of solutions. These principles provide guidelines and best practices that inform the design decisions made by solutions architects. By considering the legal view alongside architecture principles, solutions architects can ensure that legal requirements are seamlessly integrated into the design and implementation process.
When architecture principles and the legal view are aligned, several benefits arise. First, it enables solutions architects to proactively address legal compliance from the early stages of the project. By incorporating legal requirements into the architectural design, potential legal issues and risks can be identified and mitigated upfront. This proactive approach reduces the likelihood of costly redesigns or legal challenges later in the implementation process.
Second, aligning the legal view with architecture principles helps maintain consistency and coherence in the overall solution. Legal acts often establish specific standards and regulations that must be followed. By integrating these legal requirements into the architectural design, solutions architects ensure that the solution remains aligned with legal obligations throughout its lifecycle. This adherence to legal standards enhances the trust and confidence of stakeholders, including clients, regulators, and end-users.
Furthermore, aligning the legal view with architecture principles promotes transparency and accountability. Legal acts often emphasize data privacy, security, and ethical considerations. By incorporating these aspects into the architecture principles, solutions architects can demonstrate their commitment to protecting sensitive data, ensuring the security of the solution, and upholding ethical practices. This proactive approach enhances the reputation of the solution and the organization behind it.
The ‘Legal view – Binding Power and Jurisdiction’ view presents and describes the legal paradigm and landscape for the development of digital public services. It is done through binding and non-binding instruments at the European and National levels. These instruments, in the form of legal texts, establish the foundation for harmonization, collaboration, and cooperation across various domains within the European Union (EU) member states.
At the highest level, there are European Legal acts, which encompass overarching legislation applicable across all member states. These acts provide a framework for ensuring interoperability and cohesion within the European Union's legal landscape. They serve as the cornerstone of harmonization efforts and facilitate the exchange of information and services across borders. Beneath the European Legal Acts lie National Legal Acts, which are specific to individual member states. These acts reflect the adaptation of European legislation to the national context, addressing unique requirements and considerations. While National Legal acts maintain alignment with European Legal acts, they offer the necessary flexibility to accommodate country-specific needs and nuances.
Legislation on Structural Interoperability establishes the technical standards and protocols necessary for seamless data exchange and integration between systems and applications across member states. Legislation on Behavioural Interoperability focuses on promoting consistent behaviour and responsible conduct among individuals and organizations involved in cross-border operations. It establishes common norms and guidelines to foster trust, transparency, and accountability. Legislation on Governance Interoperability defines the governance structures, processes, and decision-making frameworks that facilitate effective coordination and collaboration among member states and stakeholders, ensuring the successful implementation of interoperability objectives.
Authorization is not mentioned
Certificaciones (PKI)
Certification of participants
Actualizar
The Interoperability Security and Privacy viewpoint models the most salient Architecture Building Blocks related to both security and privacy in the domain of interoperability. Citizens and businesses must be confident that when they interact with public authorities they are doing so in a secure and trustworthy environment and in full compliance with relevant regulations, e.g. the Regulation and Directive on data protection, and the Regulation on electronic identification and trust services. Public administrations must guarantee the citizens’ privacy, and the confidentiality, authenticity, integrity and non-repudiation of information provided by citizens and businesses.
Security and privacy are primary concerns in the provision of public services. When public administrations and other entities exchange official information, the information should be transferred, depending on security requirements, via a secure, harmonised, managed and controlled network. Transfer mechanisms should facilitate information exchanges between administrations, businesses and citizens. Appropriate mechanisms should allow secure exchange of electronically verified messages, records, forms and other kinds of information between the different systems; should handle specific security requirements and electronic identification and trust services such as electronic signatures/seals creation and verification; and should monitor traffic to detect intrusions, changes of data and other type of attacks.
Source: The New EIF
https://ec.europa.eu/isa2/sites/isa/files/eif_brochure_final.pdf
Narrative: This viewpoint selects Architecture Building Blocks from the five different view highlighting the Security and Privacy aspects of the EIRA©:
1. The selected Architecture Building Block of the legal view shows the [Public Policy], which is that mainspring of the solution
2. The selected Architecture Building Block of the organisational view shows the [Security Framework], associated with the [Security Governance] which is that mainspring of the solution.
3. The selected Architecture Building Block of the semantic view shows the [Security Policy], which is that mainspring of the solution.
4. The selected Architecture Building Blocks of the technical view Application shows that a [Interoperable Digital Solution], which considers [Human Interface] and [Machine to Machine Interface] is supported by a [Shared platform] which uses [Trust Enablers], [Application Security Enablers], [Identification and Access Enablers] and [Data Exchange Enablers]. [Trust Enablers] such as [Integrity Verification Service], [e-Signature Creation Service], [e-Seal Creation Service], [e-Timestamp Creation Service], [e-Signature Verification and Validation Service], [e-Seal Verification and Validation Service], [e-Timestamp Verification and Validation Service], [e-Signature Preservation Service], [e-Seal Preservation Service] and [Registered Electronic Delivery Service], are all realised by a [Trust Service Provisioning Component]. [Identification and Access Enablers] is composed of [Authentication Service], [Request Validation Service] and [Registration Service] which are realised by [Identification Component] and that provides access to the [Directory], accessed also by the [Access Management Service], realised by the [Access Management Component]. [Application Security Enablers] is realised of [Firewall Service], composed of [Firewall Component] and [Audit Service], which is realised by an [Audit Component]. [Data Exchange Enablers] composed of Data Exchange Service] realised by the [Data Exchange Component].
5. The selected Architecture Building Blocks of the technical view Infrastructure shows an [Outsourcing Facility] and [On - Premise Facility] composed of [Back End Firewall] and [Extranet Firewall].
5. The selected Architecture Building Blocks of the EIF Underlying Principles view show that [Interoperability Specifications] realises [EIF Principles], the general intended properties used to achieve interoperability, of which the [Security and Privacy] is a specialisation. The interoperability Specifications can be used to define the interoperability aspects for any of the Architecture Building Blocks
.
The Key Interoperability Enablers viewpoint models the most salient key interoperability enablers(*). The viewpoint uses the ArchiMate© motivation extension to assess the structural interoperability readiness, the behavioral interoperability readiness and the governance interoperability readiness of solutions that are necessary to enable the efficient and effective delivery of public services across administrations. European public service provision often requires different public administrations to work together to meet end users’ needs and provide public services in an integrated way. When multiple organizations are involved there is a need for coordination and governance by the authorities with a mandate for planning, implementing and operating European public services. Services should be governed to ensure: collaboration, seamless execution, reuse of services and data, and development of new services and ‘building blocks'.
(*)DECISION (EU) 2015/2240 OF THE EUROPEAN PARLIAMENT AND OF THE COUNCIL of 25 November 2015 establishing a programme on interoperability solutions and common frameworks for European public administrations, businesses and citizens (ISA2 programme) as a means for modernising the public sector.
The Key Interoperability Enablers viewpoint covers all EIF interoperability aspects: legal, organisational, semantic and technical. Ensuring interoperability when preparing legal instruments, organisation business processes, data/information/knowledge exchange, services and components that support European interoperable digital public services is a continuous task, as interoperability is regularly disrupted by changes to the environment, i.e. in legislation, the needs of businesses or citizens, the organisational structure of public administrations, the business processes, and by the emergence of new technologies.
Source: The New EIF
https://ec.europa.eu/isa2/sites/isa/files/eif_brochure_final.pdf
Narrative: This viewpoint selects Architecture Building Blocks of the EIRA© that are key enablers for the interoperability of public services:
1. EIF [Interoperability Principles] are used to realise the overall goal of achieving interoperability.
2. Particularly, the goal of [Achieve Legal Interoperability] is realised by a [Shared Legal Framework] of [re]usable legal resources that enables:
structural interoperability by legal resources supporting reusing and/or sharing legislation (i.e. [Legislation Catalogue] enabling provisioning/consuming legal texts cross public administrations and cross borders);
behavioral interoperability by legal resources supporting exchanging capabilities of data, information or knowledge with internal/external peers (i.e. [Legislation on Data Information and Knowledge Exchange] enabling data/information/knowledge to be provisioned/consumed cross public administrations and cross borders); and
governance interoperability by legislation supporting the collaboration with internal/external peers exchanging data, information or knowledge (i.e. [Legal Interoperability Agreement] on legal terms assuring juridical certainty enabling agreed legal terms/conditions for sharing, reuse and exchange of data/information/knowledge cross public administrations and cross borders).
3. Particularly, the goal of [Achieving Organisational Interoperability] is realised by a [Shared Governance Framework] of [re]usable organisational resources that enables: structural interoperability by organisational resources supporting reusing and/or sharing of digital public services (i.e. [Digital Public Service Catalogue] enabling provisioning/consuming public services cross public administrations and cross borders); behavioural interoperability by organisational resources supporting exchanging capabilities of data, information or knowledge with internal/external peers (i.e. [Digital Public Service Delivery Model], served by [Digital Public Service Delivery] enabling data/information/knowledge to be provisioned/consumed cross public administrations and cross borders); and governance interoperability by governance resources supporting the collaboration with internal/external peers exchanging data, information or knowledge (i.e. [Organisational Interoperability Agreement] on organisational terms/conditions enabling sharing, reuse and exchange of data/information/knowledge cross public administrations and cross borders).
4. Particularly, the goal of [Achieving Semantic Interoperability] is realized by a [Shared Knowledge Base] of usable data, information and knowledge resources that enables: structural interoperability by semantic resources supporting reusing and/or sharing of data, information and knowledge (i.e. [Data Set Catalogue], [Ontologies Catalogue] and [Data Mapping Catalogue] enabling provisioning/consuming data, information and knowledge cross public administrations and cross borders); behavioral interoperability by semantic resources supporting exchanging capabilities of data, information or knowledge with internal/external peers (i.e. [Open Data], [Distributed Ledger] and [Virtual Data Set]; and governance interoperability by semantic resources supporting the collaboration with internal/external peers exchanging data, information or knowledge (i.e. [Semantic Interoperability Agreement] on interpretations enabling sharing, reuse and exchange of data/information/knowledge cross public administrations and cross borders).
5. Particularly, the goal of [Achieving Technical Interoperability] is realised by a [Shared Application Content] and [Shared Infrastructure Content]. The [Shared Application Content] is a Grouping of ICT Resources components that enables structural interoperability by ICT resources supporting the reusing and sharing of data via [Software component Discovery and catalogue Service], [API Discovery and Catalogue Service] and [Service Discovery and Registry Service]; behavioural interoperability by ICT resources supporting communication via [Machine to Machine], [Human Interface], [Data Exchange Service], [UX Management Service] and [Digital Workplace Service], and governance interoperability by ICT resources supporting collaboration via [Technical Interoperability Agreements]. The [Shared Infrastructure Content] is a Grouping of ICT resources that enables structural interoperability by ICT resources supporting reusing and/or sharing of data via [Computing Hosting, Networking, and Data Hosting Infrastructure], behavioural interoperability by ICT resources supporting communication via [Technology Interface]. governance interoperability by ICT resources supports also the collaboration with internal/external peers exchanging data, information or knowledge (i.e. [Technical Interoperability Agreements] on technical terms/conditions enabling provisioning/consuming back-office services cross public administrations and cross borders), and governance interoperability by ICT resources supporting collaboration via [Technical Interoperability Agreements].
The Interoperable European Solution viewpoint models the most salient Architecture Building Blocks related to the modelling of interoperable solutions across europe. Public administrations must consider all the aspects reported within the viewpoint when creating solution that should consider all the aspects specific to interoperability.
Narrative:
[Interoperable Digital Solution] is composed by a [Shared Platform][Machine to Machine Interface] and [Human Interface]. [Machine to Machine Interface] and [Human Interface] are assigned to the [Digital Solution Component] relised by the [Digital Solution component] and associated with the [Shared Knowledge Base]. [Interoperable Digital Solution] is regulated by a [Shared Legal Framework] and associated with [Shared Governance Framework] which is also associated with [Shared Legal Framework] and [Shared Platform]. The [Shared Legal Framework] regulates also the [Shared Platform].
The Interoperability Governance viewpoint models the most salient Architecture Building Blocks that refer to decisions on interoperability frameworks, institutional arrangements, organisational structures, roles and responsibilities, policies, agreements and other aspects of ensuring and monitoring interoperability at national and EU levels. As such, it does not include operational Architecture Building Blocks like interoperability agreements.
Interoperability governance is the key to a holistic approach on interoperability, as it brings together all the instruments needed to apply it.
Source: The New EIF
https://ec.europa.eu/isa2/sites/isa/files/eif_brochure_final.pdf
Narrative: The selected Architecture Building Blocks from the five different views highlight the Architecture Building Blocks of the EIRA that are related to Interoperability Governance:
1. The selected Architecture Building Blocks of the legal view show the [Public Policy Cycle] and the [Legal Interoperability Agreement], which is a specialisation of the [Legal Agreement],
2. The selected Architecture Building Blocks of the organisational view show that [Data Owner] signs [Organisational Agreement] which is a specialisation of the [Organisational Interoperability Agreement] and is composed by the [Framework Agreement] that is a specialisation of the [Specific Agreement] associated with [Means for Public Policy Objectives Convergence assurance]. The [Interoperability Strategy] implements the [Interoperability Framework], which influences the [Security Framework], the [Privacy Framework], the [Interoperable skill] and the [Interoperability governance]. The [Interoperability Governance] is under the responsibility of the [Interoperability Organisational Authority]. [Delegation of powers provisioning Digital Public Services] influences the [Interoperable Digital Public Service Implementation Orientation] which is realised by the [Digitalisation Roadmap] that realises also the [Digital Agenda], that serves the [Interoperability Strategy]. [Digital Agenda] is associated with [Digital Governance], which, in turn, is associated with [Interoperability Framework], [Security Framework] and [Privacy Framework].
3. The selected Architecture Building Block of the semantic view show that [Data Policy] and its specialisation [Descriptive Metadata Policy], [Data Portability Policy], [Open Data Policy], [Master Data Policy], [Base Registry Data Policy] and [Reference Data Policy], together with the [Semantic Interoperability Agreement] are the mainstream of the solution governance at semantic level. Within the [Semantic governance Content] it is also considered that the [Semantic Interoperabilty Agreement] is a specialisation of a [Semantic Agreement].
4. The selected Architecture Building Blocks of the technical view show [Technical Interoperability Agreement], which is a specialisation of the [Technical Agreement], which are the mainspring of the solution governance at technical level.
An Application Processing Enabler is the collection of mediation enablers and decision support enablers.
A Mediation Enabler is a service or component for the routing, transformation, validation and exchange of data.
The Interoperability Privacy viewpoint highlights the EIRA building blocks that are relevant when implementing the EU General Data Protection Regulation (GDPR) or assessing an existing architecture against the GDPR principles. Public administrations must indeed guarantee the citizens’ privacy, and the confidentiality, authenticity, integrity and non-repudiation of information provided by citizens and businesses.
Narrative: The selected Architecture Building Blocks from the five different views highlight the Architecture Building Blocks of the EIRA that are that are relevant with respect to GDPR:
1. The selected Architecture Building Blocks of the legal view show that privacy requirements are coming from a [Public Policy] realised by a [Binding instrument].
2. The selected Architecture Building Blocks of the organisational view show that the [Privacy Framework] applies to the [Digital Public Service] which is assigned by the [Data Owner] and provided by the [Digital Public Service Provider]. The [Digital Public Service] serves the [Digital Public Service Delivery Consumer], assigned to an [Individual] that is associated to the [Information] accessible though the [Organisation] which is a specialissed by [Public Administration] and [Business].
3. The selected Architecture Building Blocks of the semantic view show that [Data] aggregates [Data Set], [Ontology] and [Data Mapping] and that it is subject to the [Data Policy].
4. The selected Architecture Building Blocks of the Technical View shows many service involving data impacted by the privacy regulation, such as
[Data Extraction,Transformation and Loading Service], [Data Quality Service], [e-Archiving Service], [Data Publication Service], [Data Exchange Service] and [Data Management Service]; all the services reported are realised by their specific Application Component. Additionally, a [Privacy Service], realised by a [Privacy Component] implementing GDPR principle can be used to ensure compliance.
5. The selected Architecture Building Block of the EIF Underlying Principles view show the [EIF Principle], the general intended properties used to achieve interoperability, of which the [Security and Privacy] is a specialisation. The interoperability Specifications can be used to define the interoperability aspects for any of the Architecture Building Blocks.
The EIRA© Highlevel viewpoint models an introductory overview of the focal Architecture Building Blocks of each view.
The ABBs included in the high-level viewpoint represent the points that link the EIRA©’s views enabling traceability between their different Architecture Building Blocks. They are not necessarily mandatory but should always be considered by a user of the EIRA© when executing one of its use cases.
The EIRA© with its views provides a set of Architecture Building Blocks, important to facilitate interoperability. Each view, one for each interoperability level, is represented with the Focal Architecture Building Blocks needed to deliver an interoperable solution. These focal Architecture Building Blocks are indicated with an accented colour.
In the high-level are represented the ABBs that link the EIRA©’s views enabling navigation between the different views. As such they should be considered as critical components of any interoperable public service. They are not necessarily mandatory but should always be considered by a user of the EIRA© when executing one of its use cases.
Narrative: This viewpoint selects Architecture Building Blocks from the five different views highlighting the focal building blocks of the EIRA©:
1. The selected Architecture Building Block of the legal view shows the [Public Policy] is realised by [Legal Act] and [Digital Public Service]; these two ABB, referred to the legal view, are aggregated within the [Shared Legal framework]. [Shared legal Framework] influences [Organisational Functional Content], [Semantic Functional Content], [Technical Application Functional Content].
2. The selected Architecture Building Blocks of the organizational view show a [Shared Governance Framework] that aggregates the [Organizational Functional Content] which considers a [Digital Public Service] which can be an aggregation of other [Digital Public Service]. The [Digital Public Service] realises a [Digital Business Capability]. A [Digital Business Capability] describes key functions supporting the [Digital Public Service]. A [Digital Public Service] accesses [Information], which can be an aggregation of other [Information]. At the same time a [Digital Public Service] is assigned by a [Digital Public Service Delivery] which is connected through a serving relation with the [Digital Public Service Delivery Model].
3. The selected Architecture Building Blocks of the semantic view shows the [Shared Knowledge Base] and that the [Semantic Functional Content] is composed of a [Representation], stored as [Data] and the [Ontology].
4. The selected Architecture Building Blocks of the technical views - application shows that a [Interoperable Digital Solution Service] is composed of a [Digital Solution Service] realized by a [Digital Solution Component] and lets consumers access it via [Machine to Machine Interface] and/or [Human Interface], which are part of a [Application Presentation and Access Enablers]. A [Digital Solution] exposes one or more [Digital Solution Service] via its [Machine to Machine Interface] and/or [Human Interface]. The [Digital Solution] uses [Digital Service Infrastructure] which uses a [Computing Hosting, Networking, and Data Hosting Infrastructure].
5. The selected Architecture Building Blocks of the technical views - infrastructure considers the [Computing Hosting, Networking and Data Hosting Infrastructure].
The EIRA© Highlevel viewpoint models an introductory overview of the focal Architecture Building Blocks of each view.
The ABBs included in the high-level viewpoint represent the points that link the EIRA©’s views enabling traceability between their different Architecture Building Blocks. They are not necessarily mandatory but should always be considered by a user of the EIRA© when executing one of its use cases.
The EIRA© with its views provides a set of Architecture Building Blocks, important to facilitate interoperability. Each view, one for each interoperability level, is represented with the Focal Architecture Building Blocks needed to deliver an interoperable solution. These focal Architecture Building Blocks are indicated with an accented colour.
In the high-level are represented the ABBs that link the EIRA©’s views enabling navigation between the different views. As such they should be considered as critical components of any interoperable public service. They are not necessarily mandatory but should always be considered by a user of the EIRA© when executing one of its use cases.
Narrative: This viewpoint selects Architecture Building Blocks from the five different views highlighting the focal building blocks of the EIRA©:
1. The selected Architecture Building Block of the legal view shows the [Public Policy] is realised by [Legal Act] and [Digital Public Service]; these two ABB, referred to the legal view, are aggregated within the [Shared Legal framework]. [Shared legal Framework] influences [Organisational Functional Content], [Semantic Functional Content], [Technical Application Functional Content].
2. The selected Architecture Building Blocks of the organizational view show a [Shared Governance Framework] that aggregates the [Organizational Functional Content] which considers a [Digital Public Service] which can be an aggregation of other [Digital Public Service]. The [Digital Public Service] realises a [Digital Business Capability]. A [Digital Business Capability] describes key functions supporting the [Digital Public Service]. A [Digital Public Service] accesses [Information], which can be an aggregation of other [Information]. At the same time a [Digital Public Service] is assigned by a [Digital Public Service Delivery] which is connected through a serving relation with the [Digital Public Service Delivery Model].
3. The selected Architecture Building Blocks of the semantic view shows the [Shared Knowledge Base] and that the [Semantic Functional Content] is composed of a [Representation], stored as [Data] and the [Ontology].
4. The selected Architecture Building Blocks of the technical views - application shows that a [Interoperable Digital Solution Service] is composed of a [Digital Solution Service] realized by a [Digital Solution Component] and lets consumers access it via [Machine to Machine Interface] and/or [Human Interface], which are part of a [Application Presentation and Access Enablers]. A [Digital Solution] exposes one or more [Digital Solution Service] via its [Machine to Machine Interface] and/or [Human Interface]. The [Digital Solution] uses [Digital Service Infrastructure] which uses a [Computing Hosting, Networking, and Data Hosting Infrastructure].
5. The selected Architecture Building Blocks of the technical views - infrastructure considers the [Computing Hosting, Networking and Data Hosting Infrastructure].
Logic for ABBs and SBBs:
There are three cases:
1. ABBs that are directly from EIRA. They will be the same (name, properties, etc). There is no method or mechanism yet to reference models without including these elements.
2. ABBs under eGovERA name sapce. These ABBs are specialisations from EIRA, that will act as "placeholders". Solution designers should develop the SBB from them. They have specific properties as they are not the same ABBs as EIRA's ones.
3. SBB, with specific properties (harmonized).
This approach will be used for all views.
Specialisation relation between Linked Data/Open Data and Data is not allowed in this model
The Semantic view models the most salient Architecture Building Blocks that should be considered to support semantic aspects for the End-to-End design of interoperable Digital Public Services.
Narrative:
[Data] is serialised using [Data Representation] the treatment and contextualisation, drives [Data] and [Data Representation] into [Knowledge]. [Data] can be grouped into [Dataset], as [Dataset] aggregates [Data]. and can be described and aggregated in [Dataset Catalogue]. [Data] is linked to [Ontology], which can be described and aggregated into [Ontologies Catalogue]. [Data Mapping] aggregates [Data] and is described and aggregated into [Data Mapping Catalogue]. [Data Mapping] is also specialised in [Metadata Catalogue], [Data Syntax Mapping Catalogue], and [Software Components Catalogue]. [Distributed Ledger] is associated to [Data] supporting the sharing and recording of encrypted data across multiple sites, countries, or institutions. [Virtual Dataset] aggregates [Dataset], that can be specialised in [Reference Data] and [Master Data]. [Base Registry] is composed of [Master Data]. [Data] can be represented as [Linked Data] and [Open Data], which are specialisations of [Data]. The representation [Linked Open Data] is a specialisation of both [Open Data] and [Linked Data]. [Linked Data] can be distributed by [Linked Open Event Stream], which is a specialisation of it. [Hash Code] and [Metadata] specialise [Data]. [Metadata] is at the same time, specialised by [Data Model], which is composed of [Forms Structure] and [Data Format], and aggregates [Data Syntax]. [Controlled Vocabulary] is a specialisation of [Data Model]. [Data] has a specific [Data Owner] that is responsible for its management, together with [Digital Public Service Delivery Consumer] and [Digital Public Service Delivery Provider Provider] and all negotiate and reach a [Semantic Agreement] and/or a [Semantic Interoperability Agreement], which is a specialisation of [Semantic Agreement]. [Data] is subject to [Data Policy], which has specific cases that are [Master Data Policy], [Security Policy], [Privacy Policy], [Data Portability Policy], and [Open Data Policy].
These different Architecture Building Blocks define the [Semantic Functional content] and [Semantic Governance Content], both are aggregated with [Semantic Knowledge Content].
The Technical - Application Domain specific view contains the most salient application Architecture Building Blocks that need to be considered to support technical aspects for the End-to-End analysis and design of Digital Solutions. A Digital Solution can support one or more public policies.
Narrative:
[Interoperable Digital Solution] aggregates [Shared Platform], and provides access to data and services. The [Interoperable Digital Solution] includes [Machine to Machine Interface] with [Human Interface], which both realise [Digital Public Service Delivery], which assign [Digital Public Service], which realize [Digital Business Capability]. Also [Machine to Machine Interface] and [Human Interface] assign [Digital Solution Service] which is realised by [Digital Solution Component]. [Interoperable Digital Solution] is influenced by [Technical Agreement], and its specialisation [Tech Interoperability Agreement] and [Service Level Agreement], all three elements constitute [Technical Governance Content].
[Shared Platform] includes [API Enablers] to register the system services in which [Web Service] which is a specialisation of [API], as well as [Machine to Machine Interface]. [API Catalogue Component] realises [API Discovery and Catalogue Service] which associate with [API Catalogue] which associate with [API]. [Service Registry] is associate with (is a) [Web Service] and [Service Discovery and Registry Service] which realized by [Service Registry Component]. Orchestration Enablers in which [Orchestration Component] realises [Orchestration Service]. Security Enablers in which [Audit Component] realises [Audit Service]. [Security Enablers] include a subset of Identification and Access Enablers where [Identification Component] realises [Authentication Service], [Request Validation Service], [Registration Service], and [Access Management Component] realises [Access Management Service] and its specialisations [Identity Management Service], [Authorisation Service], and the [Accounting Service]. [Test Enablers] in which [Conformance Testing Component] accesses [Conformance Test Scenario] and performs [Conformance Testing Service]. Trust between systems is established with Identity management is realised with [Trust Enablers] in which [Trust Service Provisioning Component] realises [e-Signature Creation Service],[e-signature Verification and Validation Service],[e-signature Preservation Service], [e-Seal Creation Service], [e-Seal Verification and Validation Service], [e-Seal Preservation Service], [e-Timestamp Creation Service], [e-Timestamp Verification and Validation Service], [Registered Electronic Delivery Service] and [Integrity Verification Service]. Also [Blockchain Component] realises [Blockchain Service]. In [Data Exchange Enablers] exist [Data Exchange Component] which realises [Data Exchange Service]. In [Data Management Enablers] exist the [Metadata Management Component] realises [Metadata Management Service]. [e-Archiving Component] realises [e-Archiving Service]. [Data Management Component] realises [Data Management Service]. [Forms Management Component] realises [Content Management Service] and [Forms Management Service]. [Data Publication Component] realises [Data Publication Service]. [Data Extraction, Transformation, and Loading Component] realises [Data Extraction, Transformation, and Loading Service]. [Data Quality Component] realises [Data Quality Service]. [Data Persistence Component] realises [Data Persistence Service]. There is also the [Data Virtualization Component] that realises [Data Virtualization Service]. In [Privacy Enablers] exists the [Privacy Component], which realises the [Privacy Service]. In [Knowledge Discovery Enablers] the [Knowledge Discovery Component] realises [Knowledge Discovery Component Service] which is associated with [Knowledge Triple stone]. In [Analytics Enablers] [Data Analytics Component] realises [Data Analytics Service]. In [Artificial Intelligence] the [Artificial Intelligent Component] realises [Artificial Intelligent Service]. [Translation Enablers] enable the possibility to increase the accessibility to public service through [Machine Translation Component] that realises [Machine Translation Service]. In [Users Experience Management Enablers] the [Public Administration Single Window Component] realises [Public Administration Single Window Service]. In [Digital Workplace Enablers] exist [Digital Workplace Component] which realises [Digital Workplace Service]. In [Schedule Management Enablers] the [Schedule Management Component] realises [Schedule Management Service], and the [Agenda Management Component] realises [Agenda Management Service], which is a specialisation of [Schedule Management Service]. The [Data Space Enablers] includes the [Data Space] which aggregates [Data Space Connector], and it has two specialisations, which are the [Data Space Connector Provider] and [Data Space Connector Consumer].
These different Architecture Building Blocks define the [Technical Application Functional content] and [Technical Application Governance content]
The Architecture Building Blocks defined in the [Digital Solution] can have [Interoperability Specification] associated, which is a specialisation of [Solution Specification] and realises [Interoperability Requirement].
The Legal view models the most salient public policy development enablers and implementation instruments that shall be considered to support the End-to-End design of interoperable digital public services.
Narrative:
A [Public Policy] aims at addressing the needs of a group of stakeholders, and it is associated with a [Public Policy Objective]. The policy is formulated and realized with the help of [Legal Act] which has two specializations [European Legal Act] and [National Legal Act] in the form of [Binding Instrument] or [Non-Binding Instrument]. A key type of legislation for behavioural interoperability is the [Legislation on Data Information and Knowledge Exchange], which is a specialization of a legal key enabler for the delivery of digital public services, the [Legislation on Digital Public Services]. Both are contained in [Legislation Catalogue], as they are specialisations. [Legislation Catalogue] include [Legal Act] and the different specialisations [European Legal Act] and [National Legal Act], and the different forms [Binding Instrument], and [Non-Binding Instrument]. The [Legal act] aggregates [Legal Clauses] and is realised by [Public Policy] and linked to the [Granularity of Legal Requirements]. [Public Policy] realises [Digital-ready Policymaking], and the same time [Public Policy Constraint] which is a specialisation of a [Public Policy Context] realises the [Public Policy]. [Public Policy] has associated a [Public Policy Objective] and [Delegation of Powers Provisioning Digital Public Services], which influences [Public Policy Context]. As part of the Legal Governance Content, [Legal Agreement] is specialised by [Legal Interoperability Agreement] focused on formalizing governance rules enabling collaboration between digital public services. [Legal Interoperability Agreement] can be reached at the European level [European Legal Interoperability Agreement] or the National level [National Legal Interoperability Agreement].
These different Architecture Building Blocks define the [Legal Governance Content] and the [Legal Functional Content], which both are aggregated by [Shared Legal Content].
Why is it a Facility?
Where is Location?
To discuss: Infrastructure services, nodes, facilities, etc... are quite abstract and each one can use different mechanism. Maybe GAIA-X or other elements can be reused, but most of the elements (IMHO) will be included as ABBs directly from EIRA.
The Technical - Infrastructure view contains the most salient cross-sectorial infrastructure services that need to be considered to support technical aspects for the infrastructure (i.e. computing hosting, networking, and data hosting) of Digital Solutions regardless the use case considered.
Narrative:
In the same way, as it happens in the Technical Application view, the [Technical Governance Content], the [Technical Agreement], and its specialisations [Tech Interoperability Agreement] and [Service Level Agreement] constitute the [Technical Governance Content] and influence the whole [Technical Infrastructure Functional Content]. Both, [Technical Governance Content] and [Technical Infrastructure Functional Content] are aggregated by the [Shared Infrastructure Content]. The infrastructure is located in a [Facility Location] and hosted using a [Hosting Facility]. [Hosting Facility] is realised by [Computing Hosting, Networking and Data Hosting Infrastructure]. The capabilities of a [Hosting Facility] are supported by a set of physical (in place) elements: [Physical Computing Infrastructure], [Physical Network Infrastructure], [Physical Communication Infrastructure], [Physical Power Supply Infrastructure] and [Physical Security Infrastructure]. [Analytics Infrastructure Enablers] aggregates [Analytics Technology Service], [Business Intelligence Technology Service], [Databricks Technology Service], and [Data Catalog Technology Service]. The [Artificial Intelligence infrastructure Enablers] aggregates [Machine Learning Technology Service]. [Digital Workplace Infrastructure Enablers] aggregates [Remote Desktop Technology Service]. [Management Infrastructure Enablers] includes four elements aggregated [Logger Technology Service], [Audit Manager Technology Service], [Telemetry Technology Service] and [Management Console Technology Service]. [Application Integration Infrastructure Enablers] aggregates a set of technology services to facilitate integration in organisations and are [Enterprise Service Bus Technology Service], [Event Manager Technology Service], [API Manager Technology Service], which is aggregated by an [API Gateway Technology Service], also [Serverless Orchestrator Technology Service], [GraphQL Server Technology Service] and [Application Service]. [Content Delivery Infrastructure Enablers] aggregates [Web Server Technology Service] and [Streaming Server Technology Service]. [Process Orchestration Infrastructure Enablers] aggregates [Business Process Manager Technology Service]. The [Database Infrastructure Enablers] aggregates [Relational Database Manager Technology Service], [Object-Oriented Database Manager Technology Service], [NoSQL Database Manager Technology Service], [Graph Database Manager Technology Service], and [Database Cache Manager Technology Service]. [Storage Infrastructure Enablers] aggregates [File Storage Technology Service], [Block Storage Technology Service], [Backup Technology Service], and [Distributed File System Technology Service]. [Data Lake Infrastructure Enablers] aggregates [Data Lake Storage Technology Service]. The [Identity and Access Infrastructure Enablers] aggregates [Identity Provider Technology Service], [Federated Identity Provider Technology Service], and [Lightweight Directory Access Technology Service]. [Trust Infrastructure Enablers] aggregates [PKI Certificate Manager Technology Service]. [Blockchain Infrastructure Enablers] aggregates [Inmutable Database Manager Technology Service], [Blockchain Ledger Technology Service], and [Distributed Blockchain Network Technology Service]. [Containers Infrastructure Enablers] aggregates [Container Orchestrator Technology Service] is aggregated by [Containers Manager Technology Service], which is associated to [Container Registry Technology Service], and [Container]. [Networking Infrastructure Enablers] aggregates [Virtual Private Network Technology Service], [Gateway Technology Service], [Domain Name Service Technology Service], and a [Router Technology Service] associated to a [Private Network], composed by a [Private Subnetwork], associated to [Firewall], which is associated to [Load Balancer Technology Service]. [Computing Infrastructure Enablers] is composed with [Virtual Machine] node. [Virtual Machine] specialise a [Server] node. [On Premise Facility] and [Cloud Computing Facility] specialise [Computing Hosting, Networking and Data Hosting Infrastructure]. [On Premise Facility] includes [Local Area Network]. [Cloud Computing Facility] is associated with [SaaS], which is composed of [PaaS], and [PaaS] is composed of [IaaS]. The [IaaS] includes [Cloud Private Network]. [Hybrid Cloud Facility] and [Edge Computing] aggregate both [On Premise Facility], and [Cloud Computing Facility]. Also, [On Premise Facility] and [Cloud Computing Facility] are served by [Wide Area Networking], which aggregates [Secure Public Network], specialised by [Public Network]. [Additional Area Networking] includes several associations that can be established with external services, facilities or devices, for instance [External Facility], [External Service], [Desktop Computer], [Smart Device], [Sensor], [Remote Desktop Client].
These different Architecture Building Blocks define the [Technical Infrastructure Functional content] and [Technical Governance content]. The Architecture Building Blocks defined can have any [Interoperability Specification] associated, of which the [Solution Specification] is a specialization.
The Organisational view models the most salient Architecture Building Blocks that shall be considered to support organisational aspects for the End-to-End design of Digital Public Services.
Narrative:
[Digital Public Service] is delivered according to its [Digital Public Service Delivery Model] and realises a [Digital Business Capability] by accessing [Information]. [Digital Public Service] is documented in [Digital Public Service Catalogue] that can be used among others with services portfolio management purposes. The [Digital Public Service Catalogue] aggregates the [Shared Organisational Content] as the [Organisational Agreement] and the [Digital Public Service Delivery Model]. [Digital Public Service Delivery Model] assigns/aggregates [Digital Public Service Delivery Machine Agent] and [Digital Public Service Delivery Human Agent] both serving a role [Agent]. [Agent] is specialised by stakeholders [Individual] and [Legal Entity], which is the specialisation of another stakeholder [Organisation]. [Organisation] is also specialised by stakeholders such as [Business] and [Public Administration]. An [Agent] can serve both relations, as [Digital Public Service Consumer] and [Digital Public Service Provider]. Both roles are assigned with the business function [Digital Public Service Provision]. [Organisational Agreement], which is specialised in [Organisational Interoperability Agreement]. [Digital Governance Plan] is composed by contracts [Agreement on Provision of Digital Public Services], [Agreement on Interoperability Security] which is associated to [Security Framework], the [Agreement on Privacy] associated to [Privacy Framework], the [Agreement on Data Sharing] and [Agreement of the Use on Common Infrastructure] both associated to [Interoperability Framework]. [Digital Governance Plan] realises the [Digital Agenda] that influences the [Interoperability Strategy]. [Digital Agenda] is realised by a [Digitalisation Roadmap], which developing the constraint [Interoperable Digital Public Service Implementation Orientation]. [Data Owner] is a business role that signs or agrees upon [Organisational Agreement] that realises the constraint [Means for Public Policy Objectives Convergence Assurance and Control]. On the delivery of the [Digital Public Service] a [Digital Public Service Delivery] business interface is assigned to the [Digital Public Service], and the business interface can have different modalities such as [Web App], [Mobile App], [Desktop App], [Service App], and [Adaptive Configuration].
These different Architecture Building Blocks define the [Organisational Governance content] and [Organisational Functional content], both aggregated with [Shared Organisational Content]. Each of these Architecture Building Blocks can have any [Interoperability Specification] associated, which is realised by a [Solution Building Block].
This file provides the ArchiMate model of the European Interoperability Reference Architecture (EIRA). The EIRA has been developed in the context of Action of the Interoperability Solutions for European Public Administrations (ISA) Programme. The EIRA is a reference architecture focused on the interoperability of digital public services. It is composed of the most important architecture building blocks needed to promote cross-border and cross-sector interactions between public administrations. It is based on the Service Oriented Architecture style and uses ArchiMate as a modelling notation. The EIRA implements the New European Interoperability Framework (EIF) .
The latest release of the EIRA is available on Joinup: https://joinup.ec.europa.eu/asset/eia/description
The latest release of the new EIF is available here: https://ec.europa.eu/isa2/eif_en