Reuse, before buy, before build
Statement
Existing solutions, services, data and information should be reused whenever appropriate before acquiring or developing new ones, or requesting information that is already available.
Identifier |
|
|---|---|
Category |
|
Interoperability layers |
|
Governance model |
|
Influence on DPS lifecycle |
|
Influence on DPS attributes |
|
Scope |
Business agnostic |
ELAP release |
4.0.0 |
Rationale
Reusing existing assets enables public administrations to make efficient use of available resources and investments while avoiding unnecessary duplication. For software and digital solutions, existing systems, services and components should first be assessed for reuse. Where suitable reusable solutions are not available, existing software products, including Commercial Off-The-Shelf (COTS) solutions, should be considered before developing new solutions from scratch. This can reduce development and maintenance costs, implementation risks and time to deployment, while promoting the use of proven solutions. Reusability also applies to data and information. Information already available within public administrations should, where legally and organisationally permitted, be shared and reused rather than collected repeatedly. This contributes to improved consistency and data quality and supports the once-only approach, reducing the administrative burden on citizens and businesses.
Implications
Public administrations should assess existing assets before acquiring or developing new ones. For software and digital solutions, this assessment should follow a reuse before buy before build approach: existing systems, services, components and other reusable solutions should first be evaluated for fitness for purpose; where these cannot fulfil the requirements, available software products, including COTS solutions, should be considered and evaluated for functionality, interoperability, scalability, security, maintainability, adaptability and integration with the existing architecture. Development of a new solution should be considered where reuse or acquisition cannot adequately satisfy the identified requirements. For data and information, public administrations should determine whether the information required by a service is already available and suitable for reuse before collecting it again. Appropriate catalogues, metadata, interfaces and data-sharing mechanisms should support the discovery, access and reuse of information across organisational boundaries. Where legally and technically possible, information already held by public administrations should be reused instead of being requested again from citizens or businesses. Across both dimensions, reusable assets should be sufficiently documented and should use interoperable standards, interfaces and data models where appropriate. Their reuse must take into account applicable legal, organisational, semantic, security and technical requirements.
Source
Reusability Underlying Principle (4) of the European Interoperability Framework (EIF)
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.