Design documentation and BIM coordination system
The design team combines drawings and static models, records notes and confirms the transmission of documents. Recipients see which version is for their work.
Coordinated editions of disciplines belong to a different stage, reference basis or unverified part of the model. Notes may be raised due to already eliminated difference or overlooking a true discrepancy between each other.
How the solution works
- Participants agree on the purpose, scope and review responsibilities of the transmitted set.
- The preparer provides a clear version as well as its fitness status; models are only connected on an agreed reference basis.
- The note is linked to a specific location or part of the document and a responsible correction.
- An authorized review determines whether the set can be used for an agreed action.
- The validated volume is transmitted to the recipient; the change preserves the previous history and its application limits.
Key challenges
- Discipline models coordinated fragmentarily
- Uncertain versions of solutions
- Design data not ready for construction
Solution capabilities
Version and uses
The drawing or model has a separate edition and a fit state for a specific volume. Uploading a newer file does not automatically replace a valid edition.
Discipline Coordination
For agreed revisions, compatible model editions and their reference data are combined; the note is checked for relevance to the part of the project.
Completion of notes
The question is accompanied by a location in the model or document, the originator responsible and his answer. The reviewer checks the correction and confirms if the question has been resolved.
Release of information
The set is approved by authorized participants according to its purpose. The reason for rejection returns to the organizer with the necessary correction.
Verification of transmission contents
Verify that the recipient receives the agreed documents, model properties and references. Data completeness is separated from technical solution suitability.
Business context
- Discipline models coordinated fragmentarily
- Coordinated editions of disciplines belong to a different stage, reference basis or unverified part of the model. Notes may be raised due to already eliminated difference or overlooking a true discrepancy between each other.
- Uncertain versions of solutions
- A version of the transmitted drawing or pattern does not distinguish between drafting, debugging and permissible use for a specific work scope. The command uses information that has not yet been approved for that action or has already been modified for that scope.
- Design data not ready for construction
- The contents of the transfer set are not checked against the destination agreed upon by the recipient, the required attributes and document connections. The contractor receives files that are insufficient for the intended action and has to refine additional information when already preparing the work.
- The customer sees what is actually aligned
- It is important for the developer of construction to distinguish the version under preparation from documents that can already be worked on. Clear versions and notes facilitate the adoption of solutions. The design team can justify the work done and minimize disputes arising from the use of different information.
Core features
- Version and uses
- Discipline Coordination
- Completion of notes
- Release of information
- Verification of transmission contents
Key integrations
- Design and Modeling Programs
- A document or model is being prepared and its specific permission for review.
- Requirements Management
- The purpose of the transfer, the need for information and a significant change have been confirmed.
- Participant Information Environments
- Agreed version of documents, review notes and endorsement or reason for rejection.
- Project Tasks and Construction Management
- The scope affected, the deadline required and a reference to the set appropriate for that action.
Potential impact (%)
The ranges indicate an illustrative relative change in the metric under the stated assumptions. Results depend on the starting position and actual use of the solution. Percentages for different metrics must not be added together.
Search and reconciliation work for a valid set
16–42%Decreasing
This illustrative scenario assumes that 40-70% of information searches and repeated cross-checks can be addressed. That share is assumed to fall by 40-60%. Company data is needed to verify both the addressable workload and the resulting change.
The active time of employees is compared by finding the right drawing or pattern permission for a similar action.
Reworking due to incorrect version of information
12–36%Decreasing
This illustrative scenario assumes that 30-60% of manual data entry and handover work can be addressed. That share is assumed to fall by 40-60%. Company data is needed to verify both the addressable workload and the resulting change.
Only approved additional work caused by this cause is fixed, separate from the required design change.
Conditional calculation scenarios. The assumptions have not been validated against client measurements.
When this solution is relevant
- The contractor receives the latest file, but it is unclear if it has already been authorized for a specific construction scope.
- The coordination note is linked to the previous edition of the discipline, so the review team repeats the verification that has already been performed.
Implementation requirements
The goals of the environmental design are agreed upon for the information transfer, the responsibilities of the disciplines and the rules for official release. Rejections, corrections and modified drawings must maintain a history of revision using the existing project environment when its capabilities are sufficient.
Further development options
- Inclusion of additional transfer volumes for recipients
- Automation of repeated data checks according to a clearly described information requirement