Public procurement notice: Prior Information Notice Without Call For Competition
Published: 2020-02-11
Buyer: Udviklings- og Forenklingsstyrelsen
Country: DK
Contract type: Services
CPV classification: 72000000 | 72200000 | 72222300: Information technology services | 72230000: Custom software development services | 72240000

Technical requirements: Υπηρεσίες τεχνολογίας των πληροφοριών: παροχή συμβουλών, ανάπτυξη λογισμικού, Διαδίκτυο και υποστήριξη
The IT and Development Agency of the Danish Ministry of Taxation (UFST) is currently in the preparation phase for a tender regarding the acquisition of ETL (Extract, Transform and Load) processes for a data platform. This project is a part of a collaboration on control and risk management in the EU, where customs supervision becomes more data-driven and data is handled intelligently. As part of the preparation, UFST would like to gather information from the market by holding dialogue meetings on 24.2.2020 and 25.2.2020. The purpose of the dialogue meetings is to gather information on how vendors can provide a solution that will fit into our current stack of technologies and how it can be provided within a short period of time due to EU deadlines, and which requirements specifications will be required for an ETL solution. It should be stressed that this notice is not a call for tender, and participation in the dialogue will not be required for participation in a future tender.
1) Extraction of data from the source system(s). As regards our data platform, the source system(s) is (are) based on Azure Data Lake and Azure SQL Database;
2) Data transformation by applying rules or functions to the extracted data (for example data cleansing, data manipulation and joining) before loading data into an end target;
3) Load of data into the end target. As regards our data platform, the end targets are Azure Synapse Analytics (data warehouse), Azure Data Lake and possibly Azure SQL Database. The ETL solution should also be able to support load of data into targets outside the data platform (for example SharePoint, other databases, emails, etc.).
— supporting definition of workflows as code (for example domain-specific language) or configuration files,
— systematic tracking of workflow and workflow step failures/successes which can be exported via common formats or APIs.
— supporting the target architecture and design principles (information is accessible via the above link from section I.3),
— being a part of a unified scheduling and deployment process across all components on the data platform by integrating with third-party tools like Azure Automation and Azure DevOps,
— supporting anonymisation and pseudonymisation (for example by built-in functionalities or by integrating with a third-party tool),
— supporting data quality (for example by built-in functionalities or by integrating with a third-party tool),
— each staged/archived data set should have accompanying metadata describing the origins and processing steps that produced data,
— supporting staging of data at each point where a major transformation has occurred in order to support comparisons with new data to generate change capture records or for reprocessing.
For the dialogue meetings, UFST has prepared descriptions of the initial needs for UFST, information about the target architecture and design principles for the data platform as well as questions that vendors will need for preparation of the dialogue meeting. This information is accessible via the above link from Section I.3). At the dialogue meetings, the potential vendors will be asked to give their opinion on commercial and technical matters.
This is to inform interested vendors of the opportunity to participate in dialogue meetings, and potential vendors are informed that aside from the request for information documents mentioned above, no further information regarding the tender material, documents, conditions or the tender procedure is available prior to the publication of the contract notice.