Virtual Construction Bricks : Overview

Virtual Construction Bricks

As part of the Productization approach, we promote the adoption of Virtual Construction Bricks (VCB) to increase the capitalisation of the knowledge in the AEC Industry. Virtual Construction Bricks combine the modelling of construction know-how and knowledge of construction elements into generative, parametric, associative templates which can be adaptively reused across projects. 

It is important to understand this approach in the context of this technical best practice to identify the key issues relevant to each Brick and ensure an holistic development approach by project phases.

 

 

Productization and Continuous Level of Development (LOD)

Virtual Construction Bricks are implemented in stages to allow users to modify specifications in context. Generative assemblies are built on top of previous stage content as separate Parts meaning both LODs are accessible. Connectivity existing across all scales and LOD meanings that at any point in a project life-cycle a design change can automatically drive change at every scale (e.g. from overall building massing down to the attachment hardware for a façade panel).

 

  • "Preliminary Design" phase: The user of a VCB needs a light weight version of the element in order to give a perspective of the project data specific for construction in order to create simplified deliverables (quantities, location plan) or to provide early feedback about construction feasibility.

 

  • "Detailed Design & Manufacturing" and "Execution & On-Site Assembly" : Capitalisation of the knowledge and know-how of fabrication, construction and operation experience (typically self-performed activities where the contractor is in control of the process involving materials, assets and people)

 

This best practice describes the two types of Virtual Construction Bricks relevant to project phase deliverables: Declarative and Detailed Bricks

  • Declarative VCB for the "Preliminary design" phase.

  • Detailed VCB for the "Detailed design, manufacturing" and "Execution and on site assembly" phases.

 

Declarative VCBs are generally used to add value to a construction element by resolving interfaces and improving reliability and predictability downstream. Declarative Bricks can be used to define the inputs for the Detailed VCBs however this is not always required. Sometimes multiple Declarative VCBs are used as inputs to a single Detailed VCB. 

Examples:

  • The Declarative VCB of a service riser could output the lengths of materials and connection interfaces. 
  • Design documentation: The Declarative VCB is used to subdivide a large wall for detailed manufacture. The subdivisions of the Declarative VCB would be the input for the Detailed VCB

Deliverables

Much like the alignment of BIM LOD with the project deliverables, the specification of Declarative and Detailed VCBs should align with requirements. It is important to reflect on the required deliverables first before planning the VCB content. For example, if the purpose of the 3D model is for costing or coordination (not fabrication), Declarative VCBs would likely be sufficient. Adding manufacturing and construction details (bolts, screws, assembly drawings) takes time to instantiate and may be superfluous.

Brick Definition Process

In this best practice, we focus on the technical implementation (step 11) whose DEFINE is done during the brick engineering step (7,8,9,10)

 

 

The result of these steps will be the company business value model, a building product breakdown structure with a list of strategic Virtual Construction Bricks, and the business KPI/benefits for those VCBs along with the requirements, deliverables, embedded knowledge, rules and product breakdown structure in a technical package ready for coding referred to as Brick Technical Sheets

 

Brick Technical Sheets

Brick Technical Sheets is a generic name for the information required to create the VCB. It is extracted from a business assessment of the design rules, regulations, production know-how, manufacturing constraints and corporate IP that become parameters and metadata in the Virtual Construction Brick.

 

The 3DExperience Platform contains a variety of tools and processes for delivering a customer's desired process of project delivery. The definition of the VCB should consider the process of building up information according to the construction timeline (further described in the implementation of VCB in a Virtual Construction Twin)

 

Interfaces, Behaviours and Logical Architecture

It is critical to define standard interfaces and dimensions to enable modularity. When VCBs are assembled into a Virtual Construction Twin, it is managed behaviour of the input parameters that will determine a successful implementation. Consider the way in which each of the following parameters affects the module below:

 

Each parameter reflects different activities. For example:

  • The bathroom type reflects explicitly define components that will impact the space available and connections to vertical services
  • Module with changes by preset increments up to a limit for transportation
  • Window types will be defined by subcontractor interfaces and specifications.

 

These behaviours are defined in the Brick Definition Process Step 8 : Formalise the Brick Logical Architecture. The logical architecture identifies key interfaces that will ultimately be integrated in the 3DEXPERIENCE Platform and have to be manged between disciplines.

 

 

 

Virtual Construction Brick Implementation Process

While this varies considerably across Project and Customers, the process of VCB implementation should consider the ability for a tailored approach across the development of the project to construction. Where the construction method is clearly defined, it may not be necessary to anticipate customisation at all however the power of the 3DEXPERIENCE Platform provides the ability to do just that.

 

At the initialisation phase, a reference project comes in, gets evaluated for compliance and is processed to establish the details for construction. The Declarative VCBs refine this information while providing the project with 'intermediary deliverables' like cost and schematic drawings. Detailed VCBs instantiate the manufacturing information for production but can still provide opportunities for fine tuning as required.