...
Compliance
Libra CDE is based on the international standard ISO 19650 - Organisation and digitisation of information about buildings and civil engineering works, including Building Information Modelling (BIM).
What is Libra CDE based on?
Naming Convention
The naming convention is crucial for ensuring consistency, clarity, and efficient retrieval of information within the Common Data Environment (CDE). ISO 19650 specifies that each information container should have a unique ID based on an agreed and documented naming convention.
Key Components of the Naming Convention:
- Project Identifier: A unique code representing the project. This ensures that all information containers can be linked back to the specific project they belong to.
- Originator: A code representing the organisation or individual who created the information container. This helps in tracking the source of the information.
- Volume/System: A code representing the volume or system within the project. This is useful for large projects with multiple volumes or systems.
- Level/Location: A code representing the specific level or location within the project. This helps in pinpointing the exact area related to the information.
- Type: A code indicating the type of information container, such as drawings, models, documents, etc.
- Role: A code representing the role of the information, such as design, construction, operation, etc.
- Number: A sequential number to ensure each information container has a unique identifier.
Example of a Naming Convention
Here is an example format for a naming convention:
[ProjectID] - [Originator] - [Volume/System] - [Level/Location] - [Type] - [Role] - [Number]
Example Breakdown:
- ProjectID: P2024
- Originator: COL (Collabrii Limited)
- Volume/System: ZZ
- Level/Location: 01
- Type: DR (Drawing Rendition)
- Role: IM (Information Manager)
- Number: 001
Resulting in:
P2024-COL-ZZ-01-DR-IM-001
Status Codes in Libra CDE
In compliance with ISO 19650, Libra CDE assigns status codes to information containers to indicate their suitability and stage within the Common Data Environment (CDE). The status codes help in identifying the current state of the information and facilitate effective management throughout the project lifecycle.
| Status Code | Description | Revision Type |
|---|---|---|
| S0 | Initial status | Preliminary revision |
| S1 | Suitable for coordination | Preliminary revision |
| S2 | Suitable for information | Preliminary revision |
| S3 | Suitable for review and comment | Preliminary revision |
| S4 | Suitable for stage approval | Preliminary revision |
| S5 | Withdrawn | |
| S6 | Suitable for PIM authorisation | Preliminary revision |
| S7 | Suitable for AIM authorisation | Preliminary revision |
| A1, A2, etc. | Authorised and accepted | Contractual revision |
| B1, B2, etc. | Partial sign-off (with comments) | Preliminary revision |
| CR | As constructed record document | Contractual revision |
By using these status codes, Libra CDE ensures a consistent and transparent process for managing the status of information containers, aligning with the standards set forth by ISO 19650-2.
Revisions in Libra CDE
In compliance with ISO 19650, Libra CDE utilises a structured approach to manage revisions of information containers within our Common Data Environment (CDE). We focus on two main types of revisions:
Preliminary Revisions (P)
Preliminary revisions are used to denote information containers that are still in progress and not yet finalised. These revisions help in tracking the iterative changes during the development and coordination phases.
- P01, P02, etc.: Each preliminary revision is assigned a unique identifier with a "P" followed by a sequential number. This helps in maintaining a clear history of updates and ensures that all stakeholders can access the latest version during the project development stages.
Contractual Revisions (C)
Contractual revisions indicate that the information container has been authorised and accepted. These revisions are considered final and contractual, signifying that the information is ready for use in official project documentation and decision-making.
- C01, C02, etc.: Each contractual revision is assigned a unique identifier with a "C" followed by a sequential number. This ensures a traceable record of finalised information, providing confidence in the accuracy and reliability of the data.
Summary of Revision Codes in Libra CDE:
- P01, P02, etc.: Preliminary revisions for work in progress.
- C01, C02, etc.: Contractual revisions for authorised and accepted information.
By adhering to these revision codes, Libra CDE ensures a consistent and transparent process for managing project information, aligning with the standards set forth by ISO 19650-2.
Classification in Libra CDE
The ISO 19650-2 document specifies that the classification of information within information containers should adhere to the Uniclass 2015 system. This is the UK implementation of ISO 12006-2:2015, which provides a structured framework for classification.
Key Points of Classification:
- Classification System: The classification system used should be Uniclass 2015. This system is designed to cover all aspects of the built environment across various stages of the asset lifecycle.
- Consistency and Standardisation: The use of a standardised classification system ensures that information is organised consistently, making it easier to retrieve, manage, and use across different projects and stakeholders.
- Automatic Classification in Libra CDE: In Libra CDE, the classification process is automated. This ensures that all information containers are consistently classified according to the Uniclass 2015 system without manual intervention, reducing errors and improving efficiency.
Example of Classification Codes
Here is an example format for classification codes using Uniclass 2015:
[Classification System Code] - [Group Code] - [Subgroup Code] - [Section Code]
Example Breakdown:
- Classification System Code: Uniclass
- Group Code: e.g., Co (Complexes)
- Subgroup Code: e.g., Co_20 (Education complexes)
- Section Code: e.g., Co_20_10 (Universities)
Workflows in Libra CDE
Libra CDE provides two main workflows, based on ISO 19650 status codes, to ensure quality and control in the management of 3D models and documents.
S1 Workflow for 3D Models
The S1 workflow, designed for 3D models, begins with users uploading models to the Common Data Environment (CDE). These models are set to "Private" and marked as "Pending Review." The BIM Coordinator conducts a QA review to ensure accuracy and compliance. Approved models are then made "Public" and distributed to stakeholders. If rejected, they are sent back for revision, maintaining a high standard of quality.
S2-S4 Workflow for Drawings and Documents
The S2-S4 workflow handles drawings and documents. Uploaded documents are initially set to "Private" and marked as "Pending Review." The Document Controller performs a QA review. Approved documents are set to "Public" and distributed to key stakeholders for further comments, coordination, and approval. Rejected documents are returned for revision. This process ensures stringent control and high-quality outputs.
These workflows enhance the integrity and reliability of project information, ensuring it meets ISO 19650 standards.
Customisation in Libra CDE
Libra CDE offers extensive customisation options to meet the unique needs and practices of your projects. This flexibility ensures that your project information management aligns with your specific requirements and quality procedures.
Naming Conventions
The naming conventions within Libra CDE can be tailored to match your project's specific requirements. Whether you need to follow a particular standard or create a custom naming system, in Libra CDE we can define and enforce the conventions that best suit your workflow.
Status Codes
Libra CDE supports the customisation of status codes to fit your project’s needs. While it adheres to the ISO 19650 standard, you can modify or add status codes to reflect your internal processes and requirements, ensuring clear communication and effective management of information at every stage.
Revisions
Revisions in Libra CDE are also customisable. You can define how preliminary (P) and contractual (C) revisions are managed, ensuring that the revision process fits seamlessly with your project’s workflow. This flexibility helps maintain a clear and traceable history of changes, enhancing the integrity of your project information.
Workflows
Both the S1 workflow for 3D models and the S2-S4 workflow for drawings and documents can be customised in Libra CDE. We can adjust the workflows to align with your specific practices, quality procedures, and project requirements. Customising workflows at the account level ensures consistency across all projects managed by your organisation.
Security and compliance specs for Cloud Data Hosting
| Category | Details |
|---|---|
| Standards the CDE Complies With | ISO 19650, BIM Standards |
| Name of the Data Host | Google Cloud Platform (GCP) |
| Location of the Data Centre | Worldwide (Regions include the United States, Europe, Asia) |
| Standards the Data Host Complies With | ISO/IEC 27001:2013, ISO/IEC 27017:2015, ISO/IEC 27018:2014, SOC 1, SOC 2, SOC 3, GDPR, CCPA |
| Encryption Standards | AES-256 for data at rest, TLS for data in transit |
| Back-up Frequency | Daily (configurable by the user) |
| Back-up/File Integrity | Redundant storage across multiple locations, regular verification processes |
| Anti-virus Protection | Comprehensive anti-virus and anti-malware measures, regular scanning |
| Firewall Protection | Advanced firewall protection, configurable firewall rules by the user |
| Detection of Security Events | Extensive monitoring and logging, real-time visibility via Google Cloud Security Command Center |
| Management of Security Events | Automated alerts, incident analysis, coordinated response framework |