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.