FE 15.0744/2026/LRB - Überprüfung der Bewertungssystematik der regulären Bauwerksprüfung nach DIN 1076 für Brücken

The contract begins when the contractor receives the award letter, and it concludes upon the acceptance of the final report or the complete handover of the research and development (FE) results. The specific project start date is detailed in "Anlage 2.2 Zeitplan und Termine" (Schedule and Dates).

Key milestones and reporting phases include:

• Submission of an intermediate report by XX.XX.XXXX.
• Submission of a status report by XX.XX.XXXX.
• Submission of the draft final report documents by XX.XX.XXXX.
• Submission of the final report documents by XX.XX.XXXX.

The contractor is required to provide a milestone and payment plan ("Meilenstein- und Zahlungsplan") as "Anlage 2.3", which must include the specific timing for achieving each milestone. The final milestone must involve the creation and submission of the final report documents, for which at least 5% of the total offer sum must be allocated.

The total duration of the contract is not explicitly stated as a fixed period.

• Text files in UTF-8 encoding.
• Documentation in PDF format.
• Documentation alternatively in reStructured Text/Sphinx.
• Documentation alternatively in Markdown.
• Documentation alternatively in AsciiDoc.
• Modern development principles.
• Maintainability principles.
• Elementary security principles.
• Installation-specific configurations (paths, URLs, etc.) to be externally configurable from the source code.
• SBOM (Software-Bill-Of-Materials) preferably in CycloneDX-format.
• SBOM (Software-Bill-Of-Materials) alternatively in SPDX-format.
• Package definition files for common package managers (pip).
• Package definition files for common package managers (cargo).
• Package definition files for common package managers (conan).
• Web applications must function with the Gecko browser engine (Firefox).
• Web applications must function with the Blink browser engine (Google Chrome, Microsoft Edge, etc.).
• Web applications must function with the WebKit browser engine (Apple).
• Database models must fulfill the condition of referential integrity.
• Cross-platform development (Windows, Linux, etc.).
• For client applications, Windows as the target platform (if cross-platform development is not feasible).
• For server services, Linux (containerized) as the target platform (if cross-platform development is not feasible).
• Source code submission via BASt-Gitlab installation.
• Compilable code must run without warnings and errors.
• For interpreted code, common linters are to be used.
• Trained AI models in the native format of the development framework (e.g., Keras.keras).
• Trained AI models additionally in the interoperable ONNX-format (.onnx).
• If ONNX is not possible, an equivalent, openly documented format for AI models.
• Data handover electronically.
• Data handover machine-readable.
• Data in open formats: CSV for small tables.
• Data in open formats: SQLite/Spatialite for large data quantities.
• Data in open formats: PostgreSQL/PostGIS for large data quantities.
• Application of suitable methods for scientific processing.
• Use of current, scientifically recognized procedures.
• Adherence to all relevant regulations, methodical standards, and norms.
• Effective quality management.