PURI: http://data.europa.eu/2sa/elap/reuse-before-buy-before-build
Category: Digital Public Service Governance
Scope: Business agnostic
Principle: Reuse, before buy, before build
Statement: (Statement) Existing digital systems are reused, before deciding upon buying or even building them.
IoP Layer: Organisational IoP, Semantic IoP, Technical IoP
Principle Source: Reusability Underlying Principle (4) of the European Interoperability Framework (EIF)
About source: 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.
PA Governance: Common
Influence in DPS Implementation life-cycle: Desire
Influence in implemented DPS attribute: Desire
|
|
| elap:PURI | http://data.europa.eu/2sa/elap/reuse-before-buy-before-build |
| dct:title | Reuse, before buy, before build |
| dct:description | (Statement) Existing digital systems are reused, before deciding upon buying or even building them. |
| dct:description | (Rationale) Reusing existing systems, services, and solutions can lead to substantial cost savings, as the expenses associated with developing and maintaining new systems are often much higher than anticipated. This principle ensures that public administrations make efficient use of resources by leveraging existing investments and avoiding unnecessary duplication. Additionally, reusing proven solutions can enhance the reliability and interoperability of public services, as these systems have already been tested and validated in real-world scenarios. By prioritising reuse, public administrations can focus on optimising and integrating existing solutions to meet their needs, fostering innovation and improving service delivery without incurring the high costs and risks associated with building new systems from scratch. |
| dct:description | (Implications) Implementing the principle of ""Reuse, before buy, before build"" requires both business and technical considerations. Public bodies and administrations must conduct thorough assessments of existing systems, services, and solutions to determine their suitability for reuse. This involves evaluating the functionality, scalability, and interoperability of these systems to ensure they can meet current and future requirements. When existing solutions are not sufficient, the next step is to consider purchasing commercial off-the-shelf (COTS) solutions that can be customised to fit specific needs. Building new systems should only be considered as a last resort when no existing solutions can fulfil essential requirements.From a technical perspective, public administrations must establish robust frameworks for evaluating and integrating existing systems. This includes adopting open standards and protocols to ensure interoperability, implementing secure data management practices, and maintaining comprehensive documentation to facilitate the reuse of systems. Additionally, public bodies should promote a culture of collaboration and knowledge sharing, encouraging the reuse of solutions across different departments and agencies. By following these guidelines, public administrations can achieve cost-effective, sustainable, and efficient service delivery, while minimising the risks and costs associated with developing new systems. |
| elap:scope | Business agnostic |
| elap:Category | Digital Public Service Governance |
| dct:source | Reusability Underlying Principle (4) of the European Interoperability Framework (EIF) |
| dct:source | https://interoperable-europe.ec.europa.eu/collection/nifo-national-interoperability-framework-observatory/glossary/term/reusability |
| rdfs:comment | 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. |
| dcat:theme | Organisational IoP, Semantic IoP, Technical IoP |
| elap:paGovernance | Common |
| elap:influenceInDPSLifecycle | Desire |
| elap:influenceInDPSAttribute | Desire |