The aim of this tender is to conclude an interfederally usable framework agreement from which authorities at all federal levels can obtain low-code platforms. The contract is divided into two lots.
The main subject of this tender is the licensing of low-code platform software. Other services to be provided in both batches are operational preparation in the form of establishing operational readiness, setting up a deployment pipeline and training. The subject matter of the contract is also ongoing services in the form of support as well as maintenance and care. The operational operation itself is the responsibility of the call-off persons and is therefore not part of this tender.
The maximum amount that can be called up is fifty million euros for Lot 1 (Development-oriented low-code platforms) and one hundred and fifty million euros for Lot 2 (Transaction-oriented low-code platforms).
Development-centric, low-code platformDevelopment-oriented low-code platforms: advanced low-code application development (cf. Low-Code Application Platforms, LCAPs) with basic operations management skills (cf. Business Process Automation, BPAs). Development-oriented low-code platforms place application development – from simple to highly complex business processes – at the center of their range of functions. They are to be understood as the further development of platforms for application development. For further information, please refer to para. 2.2.1 of Appendix 9 Terms of Service.
Operation-oriented, low-code platformOperation-oriented, low-code platforms: sophisticated operations management (cf. BPA) with low-code application development capabilities (cf. LCAP). In addition to the building block-based low-code application development, which is also inherent in them, process-oriented low-code platforms are characterized in particular by distinctive functionalities in the areas of service and process management. They make it possible to comprehensively model business processes and, where possible, to automate them.
For further information, please refer to para. 2.2.2 of Appendix 9 Terms of Reference.