Model-based layout of reinforcement

The following services support the use case «model-based layout of reinforcement»

Requirements Kickoff:
Hardware, software, training (kickoff process) should have been defined in the tender documentation and later fixed by all parties (e.g. planner, contractor, subcontractor).
Responsibilities and costs should be considered and incorporated into the plan

The model creator(s) and the executor(s) must have coordinated in recurring joint exchanges such that the following artifacts can be finalized based on the designs.

• Model Stages
• Execution instructions
• QM rules
• Buildability requirements
• Model requirements
• Model delivery program
• Training documents

With this foundation, the model of the reinforcement can be created.

Responsibilities over the individual artifacts must be determined in advance. The CDE and the data storage is defined in the use case «Create execution model».

• The geometry must correspond to the real conditions, including the stages. In case of deviations, these must be documented in the execution instructions
• Reinforcement bars must not be exported as individual bars and must be selectable with the entire reinforcement
• Sockets / threads for screw reinforcement should be visible as a geometric element and grouped with the associated bar
• Reinforcement lengths and geometry shall be coordinated with buildaility requirements (max. total length, thigh mass, production requirements)
• Information on which recess sizes (e.g. smaller than 30x30cm) are disregarded for modeling purposes

• Information content according to Exchange Requirements (see separate artifact)
• Staging and concreting section designation must correspond to a logic that is the same over the entire project and goes from the coarse to the fine (floor-stage-concreting section)
• Logic for position numbering should be the same throughout the project and is documented in the execution instruction
• Layers and layer names should be the same for the whole project and will be documented in the execution instruction documented

Following artifacts are needed for process step 1.1 & 1.2 to implement the use case

Model Stages

The model from the use case «Staging and views of models» is to be used as the foundation for the model of the reinforcement. Included in this staged model are: All concrete elements incl.

their stages and concreting sections, both in geometric form and as information in the model.

Execution instructions

They define which points are to be observed during execution in addition to the information in the model, among others:

• Dependencies to other components (e.g. inserts)
• Interfaces to other trades
• Cross-project special features regarding reinforcement
• Clarification of special details
• Supplementary information on special reinforcement

Contents of this document:

• Change record
• General remarks
  • Overlaps
• Stage designations in the model
• Staging scheme
• Position numbering reinforcement models
  • Unique position number
• Model colors
• Examples of staging
• Conflicts
  • In reinforcement model
  • Allowances
  • Voids
  • overlays

Model and document delivery program (delivery milestone)

It defines the time when which documents are needed to meet the construction schedule:

Content:

Work packages form the basis for the delivery of the:

• Latest delivery milestone
  • IFC models of the reinforcement
  • supplementary documents (order lists, etc.)
• Include specifications from suppliers

Definition of work package:

• Summarized elements and stages from use case «Staging and views of models».

The following points, among others, have a significant influence on the delivery time and must be clarified in advance by the contractor:

• normal reinforcement (bars + meshes)
• normal installation parts (backbend connections, cantilever slab connections)
• special reinforcement (bars + meshes)
  • Material (Top 12, Top 700, glass fiber)
  • Attachment parts (anchor plates, sleeves, etc.)
  • special shapes (helix)
• built-in parts (special production)

Structural data

The structural data is required for the creation of the reinforcement models. Ideally, structural engineers and model creators use consistent digital methods for the creation of reinforcement models (e.g., attributes for minimum reinforcement requirements, transfer parts of the reinforcement from structural analysis software to design software, ...). However, this is not mandatory for the use case. The specifications of the structural analysis contain among others

• Minimum basic reinforcement
• Information about allowances
• Material requirements for reinforcement and bolted connections
• Product selection in coordination with the buildability requirements
• Requirements for installation parts (material quality, product types, static properties, ...)

Buildability and production requirements

Modeling guidelines

see last chapter «Modeling Guidelines»

QM Execution

defines what must be observed during the acceptance of the installed reinforcement with regard to the model-based installation. These includes:

• Who accepts the reinforcement? (Executor)
• Have special elements (reinforcement, built-in parts, ...) been installed according to specifications?
• Have the details of the additional documents been correctly implemented -> according to the artifact «Execution instructions»
• Documentation of quality control (tool, contents, pictures?)

Schulungsunterlagen

• Objective: All project participants s have gained process knowledge in the sepcific use case. They are also able to use the tools and devices used for their task.
• At a minimum, all participants are able to:
  • Implement the process according to the requirements
  • Use the software and equipment relevant to their area profitably.

For this purpose, the following issues must be trained respectively the knowledge must be available before starting the work:

• Software
• Application (which application, app, web, ...)
  • Access to the application (login, licensing, ...)
  • Contact person (1. power user in the project team, 2. support?!)
  • Use of the application (where is which data, how is it accessed, how is work done)
  • Implementation of the process with the application (how is the process implemented with the application -> how is the process implemented with the application?
  • How to lay reinforcement, how to retrieve information, ...)
• Hardware / Devices
  • Provision (which devices, how many, purpose)
  • Use of the devices (how to use the devices correctly)
  • Implementation of the process with the devices (how is the process implemented with the devices)
• Processes
  • How is the process implemented in the project
  • Use of the CDE (document administration, naming conventions, purpose)
  • Progress/status control (how is it ensured that the current status of the work is known)

Ideally, a checklist is used at the beginning to determine whether all project participants have the necessary knowledge – if necessary, the knowledge should be transferred through internal or external training.

In consideration of the coordinated use case and the associated bases / artifacts, the model designer creates or adapts the reinforcement.

Before the reinforcement is transferred as a model (.ifc), the model designer must check the following aspects must be checked against the exchange requirements. This should be implemented automatically.

er_1 Exchange Requirements

• see chapter «er_1 Exchange Requirements»

Quality assurance Exchange Requirements + other documents

The QM rules define which checks are undertaken to ensure that all documents are complete and plausible. These are among others:

• Quality Control er_1 includes, among others :
  • Min: According to ER definitions
  • Project-specific rules (developed in collaboration)
  • Which rules are checked manually / automatically
  • Define test report and procedure in case of non-compliance
  • tools used for testing?
  • Attachments/links with rule sets for checking?
• Control of further process documents (e.g. order lists) etc:
  • According to jointly defined points, e.g.
  • Are all documents complete?
  • Do the documents belong to the defined work package?
  • min-/max- quantities (e.g. 0.1 to 20to per EL, 10 to 50 pcs. built-in parts per list)
  • Special ordered separately from normal elements

Decision whether the quality gate for the exchange requirements has been passed and the model can be delivered.

• Yes, models can be delivered
• No, model must be adapted

The models (.ifc) and the supplementary information must be made available on a CDE (Common Data Environment) to the contractor. The transfer must be communicated to the contractor.

IFC reinforcement models

IFC reinforcement models (and concrete and built -in parts) are supplied by the model designer for each work package The following points, among others, must be considered:

• Models are supplied per stage
• (models are delivered on time according to the model delivery program)
• Reinforcements meet the buildability and production requirements
• Models pass the quality tests according to the Exchange Requirements
• Models comply with the model requirements

--> Reinforcement / Sep. concrete + installation parts as reference

Supplementary information

The supplementary information supplied by the model designer (e.g. order lists, additional

execution instructions) are implemented according to specifications, checked and delivered per work package. The following points are to be considered, among others:

• Structure of the documents per stage or as jointly defined
• Documents in formats as agreed, as PDF, BVBS (.abs)
• QM test successfully passed
• CDE document structure must be adhered to

When receiving the reinforcement, the model (.ifc) must be checked by the contractor against the exchange requirements. This should be implemented automatically.

er_1 Exchange Requirements

see chapter «er_1 Exchange Requirements»

Quality assurance Exchange Requirements + other documents

The QM rules define which checks are undertaken to ensure that all documents are complete and plausible. These are among others:

• Quality Control er_1 includes, among others :
  • min: According to ER definitions
  • Project specific rules (developed together)
  • Which rules are checked manually / automatically
  • Define test report and procedure in case of non-compliance
  • tools used for testing?
  • Attachments/links with rule sets for checking?
• Control of further process documents (e.g. order lists) etc:
  • According to jointly defined points, e.g.
  • Are all documents complete?
  • Do the documents belong to the defined work package?
  • min-/max- quantities (e.g. 0.1 to 20to per EL, 10 to 50 pcs. built-in parts per list)
  • Special ordered separately from normal elements

The reinforcement model shall be checked for buildability and fabrication taking into account the execution instructions, the work preparation department of the executor and the buildability requirements.

Execution instructions

The final version of the execution instructions shall be applied.

Work preparation department of the contractor

Preparing the execution on the construction site from the model.

• Verification of constructability, logic and sequence.
• Verification of Suva (Swiss National Accident Insurance Fund) standards
• Requirements for assembly and sequence
• Prepare views for reinforcement works according to location and position (foreman subcontractor)

Constructability and production requirements

Apply the final version of the constructability and production requirements.

The reinforcement model has been created, tested and delivered and can now be used for the production / placement.

The reinforcement model has been created, tested and delivered and can now be used for the production / placement.

IFC reinforcement model with the supplementary information shall be provided to the manufacturer for timely delivery.

Taking into consideration the execution instructions, the IFC model of the reinforcement must be placed.
Training documents must be observed.

Quality assurance for the installed reinforcement is conducted on the basis of the defined QM rules and the associated responsibilities.

If necessary, the reinforcement must be corrected and finally documented (further use case) so that the reality corresponds to the model.

End of the process. Next stage / section can be implemented.