Official name: Udviklings- og Forenklingsstyrelsen
National registration number: 19 55 21 01
Postal address: Osvald Helmuths Vej 4
Town: Frederiksberg
NUTS code: DK
Postal code: 2000
Country: Denmark
Contact person: Lauge Bruun
E-mail: lauge.bruun@UFST.dk
Telephone: +45 72370861

Internet address(es):

Main address: www.UFST.dk

Address of the buyer profile: https://eu.eu-supply.com/ctm/Company/CompanyInformation/Index/204762

The procurement documents are available for unrestricted and full direct access, free of charge, at: http://eu.eu-supply.com/app/rfq/rwlentrance_s.asp?PID=262757&B=SKATTEMINISTERIET

Additional information can be obtained from the abovementioned address

Ministry or any other national or federal authority, including their regional or local subdivisions

Economic and financial affairs

External Dialog Meeting about ETL-tool

72000000

Services

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.

This contract is divided into lots: no

72200000

72230000

72590000

72240000

72260000

72510000

72222300

72250000

72310000

NUTS code: DK

Main site or place of performance:

2000 Frederiksberg.

The ETL solution should support 3 main functionalities:

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.).

Please note that these are the main functionalities and not a complete list.

The ETL solution should support several ETL-specific as well as cross-functional requirements.

ETL-specific requirements:

— supporting the possibility of generating ETL jobs via external scripts or third-party programmes,

— logging of ETL flows as well as audit logs of ETL flow configuration,

— supporting lineage of data transformations on the platform over time,

— horizontal scalability of the ETL workloads,

— modularisation of configured workflows to support reuse of common patterns,

— possibility to do versioning of ETL workflows in an external versioning tool,

— 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.

Cross-functional requirements:

— supporting the target architecture and design principles (information is accessible via the above link from section I.3),

— coherent and dynamic scalability across all components on the data platform,

— 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,

— rights management

—— supporting role-based rights management;

—— integrating with the Danish Ministry of Taxation’s active directory;

—— user rights/information rights should be inherited from underlying data levels;

—— rights management should be granted on table, file or logical container (directory) level.

— 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),

— supporting monitoring of operational data (for example ETL flows),

— 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.

Please note that these are the main cross-functional requirements and not a complete list.

The ETL solution should integrate with already set technologies on the data platform, including:

— Azure Data Lake,

— Azure SQL Synapse Analytics (data warehouse),

— Azure SQL Database,

— Azure Data Factory,

— Azure Automation,

— Azure DevOps,

— Azure Active Directory.

02/03/2020

The procurement is covered by the Government Procurement Agreement: yes

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.

Meetings will be held on the premises of UFST on 24.2.2020 and 25.2.2020. The meetings will be held in Danish or English.

Due to a time perspective, UFST reserves the right only to invite a limited number of participants. If dialogue meetings should be relevant due to a high number of positive responses, UFST will go through references from prior deliveries, specifications on the proposed technology and numbers of years that the potential vendors have been providing/selling ETL.

UFST will therefore kindly ask you to submit a written confirmation together with a short description of the above-mentioned information of maximum one page no later than 18.2.2020 at 16.00 if you wish to participate in a meeting. The confirmation shall be submitted by email to Lauge.Bruun@UFST.dk. In the subject line of the email, please state ‘Confirmation of participation in ETL solution’. UFST will hereafter revert with further information.

UFST emphasises that this notice is not a call for pre-qualification applications, and participation in the discussions will not be required for pre-qualification in the coming call for tenders. Furthermore, it should be stressed that replies given during the period of discussion will not in any way be part of any later assessment. The purpose of this request for information is solely to give UFST wide background knowledge about the opportunities and challenges in the market.

After completing the market dialogue, UFST will draw up a report in which the proceeding of the dialogue will be summarised. The report will be published on the website: https://www.ufst.dk/om-styrelsen/aktuelle-udbud/

07/02/2020