Everything here is free and needs no account. We built each one because a job needed it and nothing good enough existed.

All tools
ConstructionGermanyTechnical evidence

Digital Deliverables German Infrastructure Bidders Should Show

An infrastructure engineer checking as-built drawings against installed work

A German infrastructure bidder should show how it will produce, check and hand over digital information. Software lists and screenshots do not prove delivery. The useful evidence is a chain from the client's AIA to the bidder's BAP, CDE workflow, models, checks and accepted outputs.

Show examples only when the client permits them and remove project-sensitive information.

Which digital deliverables should an infrastructure bidder show?

Show an AIA compliance matrix, draft BAP structure, BIM use-case workflows, model responsibility matrix, CDE process, exchange and IFC tests, coordination reports, information-quality checks, delivery schedule and handover example.

Evidence item What it proves Bid presentation
AIA matrix Requirements were understood and assigned Requirement, response, owner, output
BAP extract Delivery method is planned Relevant sections, not a generic template
Use-case map Models support project decisions Input, activity, output and reviewer
Responsibility matrix Interfaces and authorship are controlled Discipline, model, milestone and approver
CDE workflow Information states and approvals work Status map plus tested example
Exchange test Native and open formats preserve data Issue log and resolved sample
Quality report Models and properties are checked Rule, result, owner and close-out
Handover sample Final information is usable File, metadata and acceptance record

Digital deliverables matrix for a German infrastructure bid with requirement, method, sample, check and owner columns

Digital deliverables matrix for a German infrastructure bid with requirement, method, sample, check and owner columns.

Respond to the project AIA

Do not attach a standard BIM brochure in place of a response. Extract the project requirements and state how each will be met, clarified or treated as an assumption.

Include:

  • BIM goals and required use cases
  • delivery milestones
  • model, document and data formats
  • information levels and properties
  • coordinate and spatial requirements
  • naming and classification
  • CDE workflow and access
  • checking and acceptance
  • handover and archive

BIM Deutschland explains that the BAP responds to the AIA. Make that relationship visible in the tender.

Use a model responsibility matrix

List each discipline model and information container, author, contributor, reviewer, delivery point and exchange dependency. Add who federates models and who closes coordination issues.

This exposes interface gaps early. It also prevents several firms from assuming another party will author the same information.

Demonstrate the CDE process

Show how information moves through work in progress, shared or reviewed, published or approved, and archived states according to the project requirements. Explain permissions, metadata, naming and revision.

A compact demonstration can include one file uploaded, checked, rejected, revised and accepted. The important evidence is the audit trail and decision, not the interface design of the platform.

Test exchange before the contract milestone

Select a representative sample and exchange native and required open formats. Check geometry, coordinates, classifications, properties, relationships, units and file performance. Record issues and corrective actions.

BIM Deutschland's official downloads include AIA, BAP and use-case material. Its BIM Portal provides templates, properties and checking support. Use the versions named by the procurement documents.

Show quality as a repeatable process

A clash screenshot is not a quality system. State the check, rule, tolerance, frequency, reviewer and close-out evidence.

Check group Example control Output
File and naming Required file name and metadata CDE validation result
Geometry Coordinates, units and model position Model check report
Information Required property, value and classification Rule-based report
Coordination Interface or clearance check Issue with owner and status
Delivery File set and revision completeness Transmittal and acceptance

Protect client and project information

Use anonymised or internally created samples where prior-project material cannot be shared. Never expose infrastructure security detail, access credentials, personal information or a client's controlled model to improve a tender graphic.

State which evidence can be reviewed under the procurement process and who approves access.

Show the people behind the workflow

Name the proposed information manager, discipline leads, model coordinators and assurance roles, with availability for the contract period. Explain who can approve a change to the BAP and who resolves a conflict between model production and contractual information requirements.

Use short role evidence rather than a wall of software certificates: relevant project type, exact responsibility, delivery scale and one lesson that changed the team's method. This connects the digital process to accountable people.

Bid evidence checklist

  • Evidence responds to this AIA
  • Draft BAP is tailored, not copied
  • Use cases show outputs and decisions
  • Model authors and reviewers are named
  • CDE workflow has been tested
  • Exchange sample uses required formats
  • Property and classification checks are visible
  • Issues show assignment and close-out
  • Handover sample includes metadata
  • Prior-project material is approved for use

Creatif Work builds construction websites and bid content that make digital delivery understandable to procurement without oversimplifying the method. Through our website service, BIM consultancies and contractors can publish approved evidence while keeping live project data controlled. Our article on German AIA, CDE and model delivery gives a deeper readiness review.