What is the purpose of ISO 19650 suitability codes?

 When working with ISO 19650 CDE documents, you might wonder: What is the purpose of suitability codes?

The primary purpose of these codes is to provide a progressive framework for quality, intent, and milestone approval. They help ensure the content is developed, reviewed, and approved systematically through the milestone.

Here’s a breakdown of common suitability codes:

  • S1: For coordination — the authoring team develops an iterative solution for integration, inviting collaborative comments. The solution will continue to develop.
  • S3: For review and comment — the authoring team has developed the solution significantly for technical reviews or the pre-milestone quality sign-off process. The contents may undergo interdisciplinary or technical quality reviews, capturing feedback for resolution.
  • S4: For stage authorization — the delivery team confirms the solution is complete and meets the milestone quality thresholds; delivery team quality sign-offs are obtained, and the solution is authorized for client submission.
  • S5: For stage acceptance — the client may review and formally accept the solution. Note: This step is optional and reliant on the client’s submission processes.
  • A1/A2/A3/A4….: Published — Accepted formal milestone submission, meeting the milestone contractual requirements.

Note: Not every document will go through all statuses; however, they must go through an S4 before stage approval.
You may notice that S2 is missing. S2 – is an outlier, typically referring to reference documents generated outside the delivery team, and/or will not have an iterative development approach.



What Does S2 in a CDE Mean?

When exploring the BS EN ISO19650-2 national annex, you'll encounter various shared states, each with specific meanings and uses. But what exactly do they represent, and how should you apply them?

One of the outliers in these suitability codes is S2. Unlike other codes, which typically relate to content developed by a project task team seeking collaborative input or feedback, S2 is different.

 

What does "Suitable for Information/Reference" mean?

S2 refers to content (Information Container) not authored directly by a project task team CDE member. Examples include historical or contextual information, including reference designs created by others, or content defined outside of the team, such as industry standards or guides.

This indicates that the content is intended for informational or reference purposes only. It is valuable for understanding context or standards, but does not have a direct feedback loop to its source within the Common Data Environment (CDE).


Where Can You Find an ISO 19650 Checklist?

 Are you looking for a comprehensive checklist to support the delivery (capital expenditure) stage of the ISO 19650 series?



Section 5 of ISO 19650-2 offers a detailed information management checklist aligned with each delivery sub-stage, including:
  1. Client assessment and needs
  2. Client invitation to tender
  3. Tender responses from parties
  4. Appointment of the successful tenderer
  5. Mobilisation
  6. Collaborative information production
  7. Information model delivery
  8. Project close-out

It’s surprising how many clients recognise the importance of aligning with ISO 19650 but often overlook key line items, particularly at the "Client invitation to tender" phase.

Does ISO 19650 ever identify the CDE as one environment?

When sitting down with a project team, it is common for stakeholders to ask: “What platform are we using as the CDE?” The expectation often is that there is one software solution serving as the CDE.

However, ISO 19650-1 does not specify a single platform for the CDE. In fact, it explicitly states that: “Information container-based collaborative working allows for CDE workflow to be distributed across different computer systems or technology platforms.”

This means: the CDE is realized through a system architecture and workflow that can span multiple systems, rather than relying on a single software platform.

The key questions during project delivery should be:

  1. Where are the “shared” status information containers located?
  2. Where are the “published” (milestone submission) information containers located?

If these questions yield multiple answers within a project, it may indicate that the team needs to reconsider the CDE system architecture to ensure clarity and efficiency.

Of interest, PAS 1192-2:2013 includes a useful diagram illustrating separate CDEs for asset management and project delivery (see below).

Feel free to comment and share.





Ever wondered where those ISO Status Codes S1, S2, S3, etc., come from?

If you're working with ISO 19650, you might have noticed these codes referenced by clients, especially in Australian government projects. But have you checked if they are in the AZ ISO 19650 series? 

Here's the thing: the AZ ISO 19650 series only mentions Work in Progress (WiP), Shared, Published, and Archived status codes. So where do the S0, S1, S2, S3 codes come from? 

The answer lies in the British Standards version of BS EN ISO 19650-2:2018 & Revised NA (2021).

This regional version of the standard includes a UK National Annex with detailed guidance on: 

  • Information container naming structures
  • Revision systems
  • Suitability codes

Pro tip: If your organisation has access, check the British Standards Institution Online site to get the full details. 

Hope this clears up a common confusion! Stay tuned — I’ve got more Digital Engineering and BIM insights coming soon.


How to manage a trade construction model establishment?

As soon as you have a project in the early stage of construction, you can quickly get overloaded with models. Design and construction shop models are coming at you, wondering what graphical data does your project team coordinate against and how is the construction model development and approval managed?


There is little on such a process in the public forum and PAS1192-2 and the Penn State BIM Execution Guide are somewhat bare around this area. Below is a proposed theoretical approach, looking at a specific specialist sub-contractor where the Design Intent model is complete before the Construction Shop Modelling has begun.

Have a look at it, pull it apart, and comment below on what you believe works and does not work. If it has legs, it shall be integrated into future release 2.0 Open BIM version of the BIMFix Model Establishment Framework. 


The Problem:
During the construction modeling stage; graphical data will undergo several transitions. The design Intent graphical data may be complete, but changes can still occur, while; the specialist sub-contractor is authoring their Construction Shop Model for approval, and the approved Construction model is undergoing fabrication/construction.
  • Separation into trades: A design intent model (authored by a design consultant), may contain graphical data from several specialist construction trades. For example, the Structural Engineering design intent model may contain the Trades; steelwork, in-situ concrete, and precast concrete. Proposed pre-fabrication and manufacturing graphical data typically goes through a construction modeling process, while in-situ construction graphical data may not, continuing under the design consultant’s governance. To manage each Trade content, the consultant’s design Intent model should be subdivided into design intent trade models, before construction modeling may begin.
  • Duplicate elements: During this transition, a graphical data element could potentially be in two models (i.e.: the design intent model and construction model). This generates a coordination conflict, as the project team does not have a single point of truth for the given element. Thus, a process shall be identified to enable the project team to coordinate with one approved graphical data element.
  • For approval pre-fabrication and manufacturing elements: For approval shop models shall be released to approving project team members only. A separate “For Approval” model shall be engaged. Geometry not yet ready for review, or approved geometry shall not be within the “For Approval” shop model.
  • Fit for construction: Approved Construction model graphical data could be undergoing fabrication, or may have been constructed on site. Due to this different status, they need to be identified separately.
  • As Constructed Elements: BIM projects may have an As-Constructed deliverable. Constructed elements are measured on site, and design/construction graphical data are updated to reflect this within an agreed tolerance.  Due to this different suitability (As Construction Record documentation), they shall be identified separately. For this study, I have left out the As-Constructed Process.




Written Process:
Shortly after the Main Contractor is appointed; they identify the specialist sub-contractors (trades) producing construction models and oversee the management of the below workflow. Process begins:

1. Design Consultant (Design Intent Model Originator):
1.a:  If not partitioned correctly; the design intent model/s are subdivided into distinct Design Intent Trade Models.
1.b:  Remaining graphical data (i.e. elements of trade/s not undertaking construction modeling) shall stay under the governance of the Design Consultant during the construction modeling period. As-build or As-constructed modeling is outside of this study of the process.
1.c:  Following the project appointment of the specialist sub-contractor (Trade) are appointed, the (complete) frozen Design Intent Trade Models and associated drawings/documents are published to the CDE (Common Data Environment), for the purpose of the Trade/s to begin the generation of their construction models and shop drawings.





2. Specialist Sub-Contractor’s Construction Model initial generation:
2.a:  Progressively re-builds a Construction Model from the Design Intent Trade Model (novation agreements may facilitate other construction model generation approaches).
2.b:  Construction Model elements/assemblies ready for the approval process, are released exclusively to the “Shop Drawing Review Team”, along with PDF Shop drawings & relevant documents.




3.  Shop Drawing Review Team gate options:
3.a:  Elements/Assemblies: Fail. – Result: Graphical Data updated by Trade to reflect comments and resubmitted through shop drawing approval process.
3.b:  Elements/Assemblies: Pass. – Result: Graphical Data shall be transferred into the Approved Construction Model.




4.  Specialist Sub-Contractor’s Construction Model following Shop Drawing Approval:
4.a:  On receipt of the first Shop Drawing Approval, the Specialist Sub-contractor Trade now becomes the “Curator” of the Design Intent Trade Model for their package.
4.b:  The approved Construction Model progressively grows of approved merged shop drawing graphical data.
4.c:  The Design Intent Trade Model graphical data which has received shop drawing approval; is trimmed out of the released Design Intent Model by the Curator.  
4.d:  The approved Construction Model & Trimmed Design Intent Trade Model are updated to the CDE simultaneously.
4.e: Above Construction Model process will repeat as required. At no time shall the aggregate Design Intent Trade Model & Construction Approved Model contain duplicate geometry/elements.
4.f:  At the end of the Construction Modelling process, the Design Intent Trade Model will contain no graphical data and shall be obsolete for the purpose of ongoing coordination.




5.  Late Design Change: If the requested design change is under the management of the Design Consultant:
5.a:  Following change approval, the new and modified geometry solely of the design change is released, (by the designer) to the Curator. The designer will provide detailed information about the scope of the design change, and ideally the element unique identifiers of the geometry to be removed from the former design intent trade model.
5.b:  The Curator, imports design change model geometry into the current Design Intent Trade Model and removes all superseded graphical data. The updated model is released to the CDE for backgrounds and coordination.





Design Intent Trade Model Curator (Curator). 

The role of the Curator begins following the first approval of shop models. The specialist sub-contractor will take on the Design Intent Trade Model Trimming role. Role includes:

  • Removing (hide in export view) graphical data from the design intent trade model which have obtained shop drawing approval.
  • Importing approved design change graphical data, and removing (hide in export view) the superseded graphical data.
  • Re-releasing (That is: exporting the visible graphical data elements in the view,) the updated design intent trade model to the CDE, for coordination and model background purposes only.
Modifying graphical data beyond hiding it in the export view is prohibited by the Design Intent Trade Model Curator. Thus, the Design Intent Trade Model only contains designer’s graphical data which have not yet been superseded by the shop drawing approval.


The Design Intent Model Curator Role debate:

The debate goes to who is best to fit this role, and why does the Originator not do it? Here are some of the challenges on a traditional tender project:

Following design completion:

1. The design consultant (model Originator) does not know the approval status of shop drawing elements/assemblies, other than their own return review comments. Other reviewing disciplines and the contractor's comments/approvals are often not openly available. Thus, if the Originator was to be the Curator, they would require an instruction from the sub-contractor on which elements/assemblies have received approval.

2. When the design stage is complete, the design consultant only has technical review staff on the project, and not modeling staff (due to fee breakdowns, and work scope), thus making it more difficult to trim the model. This type of task is best carried out by a proficient modeler.

3. The updated design intent trade model needs to be released to the CDE at the same time as the updated Construction model: (to avoid confusion and double modeling). Having two separate parties involved in the release process slows it up, and makes the nonperiodic simultaneous release more challenging to achieve.

4. In existing contracts with design consultants, such a Curator role following design completion is outside their typical scope. Introducing a role into a subcontractor's contract is easily achievable within the procurement timeline.

5. With scripting tools, it is possible for the Sub-contractor shop modeler to link Element Identifiers of the designers model to the Construction model, thus making it a semi-automated process for removing the approved elements from the Design Intent Trade Model.



Liability:

The above process is designed “not” to remove any responsibilities or liabilities. All models and documents authored by the design consultant remain in the CDE, with their status and approvals recorded. The process is ensuring approved information is reaching the relevant project participants at the correct time. The combination of the CDE and how easy it is to engage model comparison tools, remove a lack of trust between the designer and Curator.



Practical Engagement:

From model exchange and interoperability, how would this work in the real world? Following a model exchange format agreement, design intent models are exchanged on the CDE in a proprietary file format (e.g. .RVT, .DGN, .DB1), or an Open BIM Format (e.g. .IFC). If the Designer and Curator are engaging the same authoring application, there is no model trimming difficulty.

Proprietary format – Different applications: If the Curator is using a different authoring application they can:

  • natively import the Originator’s format or the
  • or the Curator also has the Originators software and can export the model to the preferred import format. 

Both of the above will enable the Curator to trim the Originators model.

Open BIM format: If the Curator is importing the IFC file format directly into their authoring application. Due to the challenge of round-tripping errors, it is ill-advised for the Curator to export the trimmed design intent model from their authoring application. Instead; engaging an IFC middleware application (such as SimpleBIM,) would allow trimming of the Design Intent Trade Model with no loss of model fidelity.

The industry is starting to understand that when working with IFC files, the use of an IFC middleware is becoming essential, as all BIM Authoring applications have their own quirks in exporting and importing IFC files.



Close:

Please provide your views below. Have you used or seen a comparable process in the past? If this appears a legitimate approach, the next process development step is projects where the construction modeling is occurring concurrently with the design stage and the As-constructed process.