Building a Digital Workflow in

Practice
March 2019
CONTENT PREVIEW
Digital Workflows and Computational Design Panel
The Institution of Structural Engineers
Building a Digital Workflow in Practice
March 2019
Please note that this content preview may not represent the final published guidance from the Digital Workflows and Computational Design Panel of
the Institution.

The Institution of Structural Engineers and the members who serve in the Digital Workflows and Computational Design Panel that
produced this guide have endeavoured to ensure the accuracy of its contents. However, the guidance and recommendations given
should always be reviewed by those using the report in the light of the facts of their particular case and any specialist advice. No
liability for negligence or otherwise in relation to this guide and its contents in accepted by the Institution, the members of the Digital
Workflows and Computational Design Panel its servants or agents. Any person using this document should pay particular attention
to the provisions of this condition.
Objectives
This page aims to help you:

i. practitioners understand how to begin constructing a digital workflow

ii. practitioners identify where there may be gaps in existing workflows

Constructing a digital workflow

Moving data from one piece of software to another and achieving meaningful output requires a few steps.
Depending on expertise, budget, technical constraints, etc. design practice workflows may differ. It is however,
important to understand how these potentially different workflows can operate successfully together to avoid
some of the time consuming and wasteful consequences of the ‘data dead-ends’ described earlier.

At the inception of any project the overall workflow should be defined. This includes inputs and outputs of
numerous data parameters, some examples of which are shown below.

Analysis parameters Deliverable data parameters Shared parameters

• Material properties • Material properties • Geometry

• Design codes • Specification – materials and
• Loads workmanship
• Load catchment areas • Movements and tolerances
• Releases • Connection forces
• Supports • Pre-stress
• Restraint conditions • Corrosion protection
• Tolerances and imperfections • Fire protection
• Construction sequence • Limiting Temperature
• Pre-stress • Material quantities
• Reinforcement quantities
• Embodied carbon
• Cost

Table 1: Common analysis and output parameters

Once the outputs are established they can be formulated into a flowchart that forms the framework of the project
workflow. Note that when working with external consultants, there should be agreement on both the data to be
provided to them, and (perhaps more importantly) the data format in which that information will be delivered.

The Institution of Structural Engineers Building a Digital Workflow in Practice (Content Preview) 1
 Figure 1 - An example of information flow between architect and structural engineer

Once this flowchart of information has been established, software can be mapped to the various tasks that need
to be undertaken. Note that some software (eg spreadsheets, databases or custom scripts) can be used as a
general-purpose tool with which to manipulate data in various ways, at different stages of the design process.

In Figure 1, the required transfer of data is denoted by arrows straddling boundary lines, representing the
direction data flow. Note that data flows are required by both design processes within structural design, and
coordination with the architect. Thus, the use of a robust data model and digital workflow has benefits not only
for working internally, but for working with other consultants. The more accessible the data, the easier it is it
interrogate and check, making the process easier.

The Institution of Structural Engineers Building a Digital Workflow in Practice (Content Preview) 2
 Figure 2 - Structural design and documentation workflow

To optimise the workflow, it is desirable to reduce the number of programs and formats used, and to adopt a
database approach whereby as much data as possible is shared between the various digital models. This
process of sharing common data using centralised information management and transferable file formats is
encompassed in the term ’interoperability’.

Robust database-driven workflow

Figure 3, in contrast to those shown previously, demonstrates the power of a robust digital workflow.

Figure 3 - Multi-disciplinary database driven workflow

Data is held in a central ‘hub’ where geometry and other data (parametrically defined or otherwise) drives
processes related to the holistic design of the building.

The Institution of Structural Engineers Building a Digital Workflow in Practice (Content Preview) 3
Changes from the structural analysis, testing, construction-staging, fire engineering and architectural
coordination are held centrally in the ‘Central Data Hub’. Changes are not undertaken at the branches, but
instead fed back to those managing the model held in the hub.

The organisation of this workflow is much like a client-server model seen in many IT systems.

The benefit of this method of working is that all changes are synchronised across disciplines and all consultants,
contractors, etc. are working on the most up-to-date and fully federated model which is consistent between all
designers.

Interoperability
Interoperability does not need to be complicated or involve high-end programming or scripting. It can often be as
simple as using a spreadsheet as a container to move data between different software packages. Many
commonly used programs have already developed strong interoperability links, for example between analysis
and documentation/BIM products.

There are often discontinuities in these processes as they are rarely perfect, but there are always work-around
solutions so getting familiar with the software and knowing the limitations is an important part of the process. By
defining workflows and understanding the capabilities of software, an initial investment of time will bring
efficiencies in delivery.

The Institution of Structural Engineers Building a Digital Workflow in Practice (Content Preview) 4