# IDS Compass — full site content for language models > Complete readable text of every public page on idscompass.com. Source of truth: https://idscompass.com > Index version of this file: https://idscompass.com/llms.txt Contact: info@idscompass.com --- ## URL: https://idscompass.com/ Title: IDSCompass — AI workspace for BIM information requirements # Define BIM requirements in plain language . Generate validated IDS files. The AI workspace for turning project briefs into structured information requirements, reusable specifications and standards-compliant IDS files. Private beta · invite-only · free while in beta. ## BIM requirements live in too many places . Scattered across documents, spreadsheets and conversations impossible to align on, impossible to reuse. Every team reads the same brief its own way. Requirements are rewritten from scratch on every project. Gaps surface only when the model is already delivered. ## Describe. Structure. Reuse. Publish. Validate. A single path from a plain-language brief to a validated IFC delivery. Write requirements in plain language. AI extracts entities, properties, types and constraints. Organize requirements into libraries and sets. Export standards-compliant IDS files. Check incoming IFC models against requirements. ## Natural language, precise requirements. Describe what the model must contain. IDSCompass identifies entities, properties, data types and constraints — reviewable and editable. “All pumps in the mechanical plant room must have a manufacturer, model number, serial number and warranty expiry date.” ## Build once. Reuse across projects. Requirements become long-lived organizational knowledge — versioned, discoverable, and shared across every project your team runs. ## One requirement. One source of truth. Owners, information managers, designers and contractors aligned on the same specification — end to end. Defines what information is needed. Structures and standardizes requirements. Delivers information in the model. Checks the IFC model against IDS. Receives reliable, structured information. ## Built on open BIM. Interoperable by design. Every specification is a valid IDS file, every check runs against IFC. ## IDS in Practice . A practical guide to information requirements and checkable IFC deliveries — from first brief to a validated model, with worked examples you can apply on your next project. ## Frequently asked. ## What is IDS? + ### What is IDS? IDS (Information Delivery Specification) is the open buildingSMART standard for expressing BIM information requirements in a machine-readable way, so IFC models can be checked automatically. ## Do I need deep IFC or Revit knowledge? + ### Do I need deep IFC or Revit knowledge? No. You describe requirements in plain language. IDSCompass maps them onto IFC entities, property sets and data types for you — and lets you review or override anything. ## How does the AI work? + ### How does the AI work? The AI extracts entities, properties, data types, values and constraints from your text. Every extraction is transparent and editable — nothing is published without your review. ## Can I edit the requirements manually? + ### Can I edit the requirements manually? Yes. Every field the AI proposes is editable. You can also author requirements from scratch. ## Can I reuse requirements across projects? + ### Can I reuse requirements across projects? Yes. Requirements live in a versioned library and can be composed into requirement sets shared across projects, phases and teams. ## Can I export valid IDS files? + ### Can I export valid IDS files? Yes. IDSCompass emits standards-compliant IDS 1.0 files that work with any downstream IDS checker. ## Can I validate IFC models? + ### Can I validate IFC models? Yes. Point IDSCompass at an incoming IFC and get a pass/fail report against the defined requirements. ## Who is IDSCompass for? + ### Who is IDSCompass for? Primarily BIM and Information Managers. Owners, consultants and contractors use IDSCompass to align on and deliver against the same specifications. ## Is the beta free? + ### Is the beta free? Yes. The private beta is invite-only and free of charge. ## Make BIM information requirements predictable. Join the IDSCompass beta and help shape the future of AI-powered BIM information requirements. Private beta · free while in beta. © 2026 IDSCompass --- ## URL: https://idscompass.com/ids-editor Title: Online IDS Editor for BIM Specifications | IDS Compass # Create and manage IDS specifications for BIM projects IDS Compass is an online IDS editor for teams defining BIM information requirements. Create specifications, organise reusable libraries, and manage the requirements for each project phase and release. Use AI assistance to develop a starting draft, then review the details before sharing it with your project team. Create your first IDS or request a demo — both start with beta access. ## Give each requirement a clear structure A useful requirement identifies the information needed and the objects it applies to. Begin with a familiar task, such as requesting an agreed property on a group of walls, and build a specification your team can discuss and use. Give specifications meaningful names and descriptions. Explain why the information is required and how it will be used. This context helps the person preparing the model understand the purpose of the delivery. New to the format? Read our guide to what IDS means in BIM . ## Reuse specifications across projects Your team should be able to build on requirements it has already reviewed. Organise specifications into libraries and use them as a starting point for future work. Review the assumptions each time you reuse a specification. An asset owner's information needs, the agreed IFC version and the delivery stage may differ between projects. A reusable library is most useful when its scope is clear. ## Organise requirements by project phase and release The information needed for an early design decision may differ from the information needed at handover. IDS Compass lets you organise your work around projects, phases and releases so that the specification set has a clear delivery context. Use meaningful release names and descriptions to explain the purpose of each issue. Make it clear to the receiving team which release should guide its next delivery. ## Use AI assistance to start from plain language Describe the information you need in everyday project language and use AI assistance to develop an initial specification. Review the selected objects, information fields and value rules before accepting the draft. A useful prompt includes the object group, the required information and the purpose of the check. For example: “I need the agreed classification recorded for the wall types included in this design delivery.” The next step is to resolve the project's exact classification system and codes, then test the resulting specification. ## Prepare requirements for the checking workflow Decide how the team will review the specification and check its IFC delivery. Check software support for the IDS and IFC versions being exchanged, and keep the issued requirement set identifiable. Our IDS validation guide explains the checks to plan before using results to assess a delivery. ## Start with one requirement that matters. Bring a requirement from your current project. Structure it, review it, and use the experience to build a specification library your team understands. Private beta · free while in beta. --- ## URL: https://idscompass.com/learn Title: Learn IDS for BIM: Guides and Examples | IDS Compass # Learn IDS for BIM Understand Information Delivery Specifications and put them to work on your next information delivery. These guides explain how to define requirements, structure a specification, and make sense of the results when an IFC model is checked. ## Start with the essentials Learn what an IDS file describes, who uses it, and where it fits in a BIM workflow. Understand the relationship between a model and the requirements used to assess its information. See how model information requirements can support a wider asset handover process. ## Write your first specification Work from a clear project requirement to a specification you can review and test. Explore small examples for property values, naming rules and project information. Learn how to select the right objects and avoid excluding the objects you intended to check. ## Review your delivery workflow Understand the difference between auditing an IDS file and checking an IFC model against it. Explore a practical approach to libraries, project phases and successive releases. A practical guide to ISO 19650, IFC, IDS 1.0 and buildingSMART. ## Put your requirements into practice IDS Compass brings specification authoring, reusable libraries and project organisation into one workspace. Start with a requirement you already need to communicate and build from there. ## Make BIM information requirements predictable. Join the IDS Compass beta and start authoring standards-compliant IDS files from plain language. Private beta · free while in beta. --- ## URL: https://idscompass.com/learn/what-is-ids Title: What Is IDS in BIM? A Practical Guide | IDS Compass # What is IDS in BIM? Information Delivery Specification, or IDS, is a buildingSMART standard for expressing information requirements so that software can interpret them. Written by Eli Weaver · Reviewed 21 September 2026 - What problem does IDS help solve? - What does an IDS file contain? - Who uses IDS? - What are the limits? - How do you get started? Information Delivery Specification, or IDS, is a buildingSMART standard for expressing information requirements so that software can interpret them. An IDS file defines requirements that can be used to check information in an IFC model, such as an expected property or classification. buildingSMART's IDS overview ## What problem does IDS help solve? Imagine receiving a model with an instruction to “include the information needed for handover”. The instruction leaves several decisions open. Which objects are included? Which information is needed? How should it be recorded? What would make the delivery acceptable? Working through those questions turns a broad request into something the delivery team can act on. IDS provides a structure for the part of that agreement that can be expressed as checks on IFC information. For example, a project might agree that every wall in a particular delivery must carry a fire rating value. The team still needs to decide the information's location, permitted values and intended use. Writing the specification brings those decisions into the open. ## What does an IDS file contain? An IDS file uses XML and normally has the .ids extension. It can contain metadata and multiple specifications. Each specification uses applicability to identify relevant objects and requirements to describe what those objects should satisfy. IDS user manual The distinction matters. “These are the objects to examine” and “this is the information they must contain” are separate decisions. Read the applicability and requirements guide for a worked example. ## Who uses IDS? An information manager might prepare the specification. A designer might use it to understand the expected information. A contractor or receiving organisation might use compatible checking software to review a delivery. Agree who owns the requirements, who reviews them and who resolves questions. The file supports that working agreement; the people responsible for delivery still need to understand it. ## What are the limits? IDS focuses on information in IFC. Geometric clash detection and verification of physical construction require other forms of checking. For example, a fire rating value recorded in a model does not establish that a constructed assembly achieves that performance. buildingSMART's explanation of IDS scope Use each result for the question it actually answers. Keep design review, information checking and evidence of installation connected in the wider delivery process. ## How do you get started? Choose one information requirement that matters to your team. Describe the objects, information and expected result. Review a small example before expanding the specification set. Follow the guide to creating an IDS file , browse our IDS examples , or explore IDS Compass . ## Continue reading Work from a clear project requirement to a specification you can review and test. Small examples for property values, naming rules and project information. Create specifications, reusable libraries and project releases in one workspace. ## Start with one requirement that matters. Join the IDS Compass beta and structure your first specification in plain language. Private beta · free while in beta. --- ## URL: https://idscompass.com/learn/how-to-create-an-ids-file Title: How to Create an IDS File for BIM | IDS Compass # How to create an IDS file Start with a clear information requirement, identify the objects it applies to, and define the information those objects should contain. Written by Eli Weaver · Reviewed 21 September 2026 - 1. Write down the purpose - 2. Agree the IFC delivery context - 3. Define applicability - 4. Specify the information precisely - 5. Describe and review - 6. Audit the IDS file - 7. Test passing and failing cases - 8. Issue and maintain To create an IDS file, start with a clear information requirement, identify the objects it applies to, and define the information those objects should contain. Use an IDS authoring tool to prepare the specification, audit the resulting file, and test its behaviour against a representative IFC model. The workflow below is a practical starting point for a small pilot. ## 1. Write down the purpose of the requirement Choose a real delivery question. Who needs the information? What decision or task will it support? At which stage is it needed? For a hypothetical design review, your team might need a fire rating recorded for each wall in scope. Write down what the reviewer will do with that information and who will resolve an unclear or missing value. Avoid beginning with a long list of every property the software can request. Begin with the information your team can explain and use. ## 2. Agree the IFC delivery context Record the IFC version used by the project and check that the receiving software supports it. Inspect a representative export to understand how the authoring team is producing the relevant objects and information. Agree whether the scope concerns object occurrences, types or another defined group. Resolve this before building a large specification set. ## 3. Define applicability Applicability selects the objects to which a specification applies. Entity and other facets can be combined to describe the intended group. Requirements then describe what the selected objects must satisfy. buildingSMART's specification guide For a first pilot, use a scope you can inspect easily, such as all wall occurrences in a small sample model. Add more selective conditions only when the project needs them. ## 4. Specify the information precisely For a property requirement, identify its property set and name. Decide whether you need a populated value or a particular value rule, and use the appropriate data type. Standardised IFC properties have defined names and data types. IDS property facet guidance In the wall example, Pset_WallCommon and FireRating identify the property. Agree the permitted project values before restricting them. Do not assume that an example value from another project is suitable for yours. ## 5. Describe and review the specification Give the specification a useful name, explain its purpose and identify the delivery it belongs to. Ask a person responsible for the model to review the wording and a person responsible for receiving the information to review the expected outcome. If AI helped produce the draft, review the selected objects and every information field. Resolve assumptions before issuing the specification. ## 6. Audit the IDS file Run an appropriate IDS audit on the file you intend to share. buildingSMART provides an open-source tool for checking IDS file validity. IDS Audit Tool Correct reported issues, then keep the reviewed file identifiable so the project team can refer to the same issue. ## 7. Test a passing and a failing case Use a small IFC example where you know what should happen. Include one object with the expected information and another with the information missing or deliberately incorrect. Check that the right objects are selected and that the results match your expectations. ## 8. Issue and maintain the requirements Identify the release, its intended delivery stage and the person responsible for questions. When requirements change, explain the change and the delivery to which it applies. Preserve the relationship between the requirement issue, the received model and the checking result. See practical IDS examples and the validation guide , or start organising specifications in IDS Compass . ## Continue reading Three illustrative requirements with their decisions and expected outcomes. Audit the file, check the model, and review the results properly. Author, reuse and release specifications in IDS Compass. ## Turn your next requirement into a specification. Join the IDS Compass beta and build your first specification set. Private beta · free while in beta. --- ## URL: https://idscompass.com/learn/ids-examples Title: IDS Examples for BIM Information Requirements | IDS Compass # IDS examples for BIM information requirements A useful IDS example explains the project intention, the objects involved, the information being requested and the expected result. Written by Eli Weaver · Reviewed 21 September 2026 - 1. Fire rating for walls - 2. Naming convention for doors - 3. Room-use category - How to adapt an example A useful IDS example explains the project intention, the objects involved, the information being requested and the expected result. The three examples below show different ways to make a requirement more precise. All project names, custom fields and sample values are illustrative. Use them to discuss the structure of your own requirements, then create and test the specifications in the software used by your team. ## Example 1: Record fire rating information for walls Project intention: A reviewer needs the agreed fire rating information for the walls included in a design delivery. - Decision - Example definition - Objects in scope - Wall occurrences represented as IfcWall - Property set - Pset_WallCommon - Property name - FireRating - Data type - IFCLABEL in the IDS property facet - Information rule - A populated property value is required - Value restriction - None in this first example The property and its data type are described in the buildingSMART property facet guide . Because this example does not restrict the value, it only asks for the agreed property to be populated. Before using it on a project, decide whether the review also needs an approved list of values. A populated but unsuitable label would require an additional rule to reject it. Also decide whether walls are expected to exist in this delivery. A specification that permits no applicable objects needs to be interpreted differently from one that requires them. ## Example 2: Use an agreed naming convention for doors Project intention: The coordination team wants door names in a consistent project format. For this hypothetical convention, the Name attribute must contain the prefix DR- followed by exactly three digits. The rule would be expressed with an attribute facet and a text pattern suitable for IDS. - Sample name - Intended outcome under this convention - Reason - DR-014 - Meets the convention - Correct prefix and three digits - DR-7 - Does not meet the convention - Only one digit - Door 014 - Does not meet the convention - Different prefix and format - DR-014A - Does not meet the convention - Additional character A naming rule should be agreed with the people producing and consuming the information. It is most useful when the convention supports an actual workflow, such as locating items in a schedule. ## Example 3: Record a project's room-use category Project intention: The briefing team wants spaces assigned one of three project categories for a pilot review. - Decision - Example definition - Objects in scope - Spaces represented as IfcSpace - Custom property set - Compass_SpaceBrief - Custom property - UseCategory - Expected data type - IFCLABEL - Allowed values - Teaching , Office , Support Compass_SpaceBrief and UseCategory are invented project fields, not buildingSMART standard definitions. A space with Office would satisfy the described value rule; a space with Administration would require review because that value is outside the illustrative list. Before adopting a custom field, check whether an existing standard property or classification already expresses the intended meaning. Record any mapping your delivery team needs. The pilot's short list is a design choice for this example, not a recommended classification for all buildings. ## How to adapt an example Write down the purpose, confirm the scope and replace the sample values with the project's agreement. Include passing, failing and out-of-scope objects in a small test. Document what you expect before running the checker. The result should help the next person understand both the rule and the reason for it. Follow the creation guide , review applicability and requirements , or organise your specifications in IDS Compass . ## Continue reading An eight-step workflow from requirement to tested specification. Select the right objects and avoid excluding the cases you want to find. Build reusable libraries in IDS Compass. ## Adapt an example to your own project. Join the IDS Compass beta and structure the requirement your next delivery depends on. Private beta · free while in beta. --- ## URL: https://idscompass.com/learn/ids-validation Title: IDS Validation and IFC Model Checking | IDS Compass # IDS validation and IFC model checking explained “IDS validation” can refer to two different tasks: checking that an IDS file is valid, and checking whether an IFC model satisfies the requirements in that file. Written by Eli Weaver · Reviewed 21 September 2026 - What does an IDS audit check? - What does IFC checking do? - A practical way to test - Review more than the headline - Keep a reproducible record “IDS validation” can refer to two different tasks: checking that an IDS file is valid, and checking whether an IFC model satisfies the requirements in that file. Keep those tasks distinct when planning a delivery review. buildingSMART's explanation of auditing and checking ## What does an IDS audit check? An IDS audit examines the specification file. buildingSMART's IDS Audit Tool supports quality assurance of IDS files and includes checks associated with the IDS schema and IFC-related definitions. The precise checks depend on the tool version. IDS Audit Tool documentation For your project, record the tool and version used, review its feedback and correct problems in the file before issuing it. Passing an audit is useful evidence about the file, but you should still check that the specification expresses the requirement you intended. ## What does IFC checking against IDS do? An IDS-capable model checker evaluates the IFC delivery against the supplied specifications and reports results. For example, IfcTester supports checking IFC models against IDS and producing reports. IfcTester documentation Plan the review around three questions: was the intended model checked, was the intended IDS release used, and did the specifications select the intended objects? ## A practical way to test a specification Prepare a small sample in which the expected outcome is known in advance. Include an object that should satisfy the requirement, an object with the requested information missing, and an object that should fall outside the specification's scope. For a hypothetical rule requiring an agreed project property on walls, write the expectations before checking: - Sample object - Expected treatment - Wall with the agreed property and an allowed value - Should satisfy this rule - Wall without the required property - Should fail this rule - Door outside the wall specification - Should not be assessed by this rule ## Review more than the headline result Check the number and identity of applicable objects. If the model contains the walls you expected but the specification selects none, investigate the selection logic. A result without that context can be misleading. When a rule fails, inspect the exported IFC information before assigning a correction. The source model, export mapping, specification or scope might need attention. Record the decision so that the next delivery is checked against an understood requirement. ## Keep a reproducible review record Retain the model issue, IDS release, checker/version and resulting report together in the project's agreed record system. When a requirement changes, identify the changed release before running another comparison. That record makes it easier to explain a result later and to distinguish an information correction from a change in the requirement itself. Read the guide to applicability and requirements , explore IDS examples , or prepare your specifications in IDS Compass . ## Continue reading Why a specification can select the wrong objects, and how to review the logic. Illustrative requirements with their decisions and expected outcomes. Author and release requirement sets in IDS Compass. ## Plan the checks before the delivery arrives. Join the IDS Compass beta and keep your requirement releases identifiable. Private beta · free while in beta. --- ## URL: https://idscompass.com/learn/ids-vs-ifc Title: IDS vs IFC: How They Work Together in BIM | IDS Compass # IDS vs IFC: how they work together IFC describes and exchanges information about a built asset. IDS expresses information requirements that can be checked against an IFC model. Written by Eli Weaver · Reviewed 21 September 2026 - What does each one contain? - A delivery example - Does a valid IFC model meet every requirement? - How should the team manage the files? IFC describes and exchanges information about a built asset. IDS expresses information requirements that can be checked against an IFC model. In a delivery workflow, IFC carries the model information and IDS provides a structured statement of selected expectations for that information. IFC introduction , IDS user manual ## What does each one contain? - Question - IFC - IDS - Main role - Represent and exchange model information - Express information requirements - Typical content - Objects, attributes, properties and relationships, including representations of geometry - Specifications identifying relevant objects and expected information - Typical project use - Deliver information produced by the model author - Communicate and check agreed information expectations - Example - A model containing walls and their recorded information - A specification asking for an agreed property on the relevant walls IFC supports a wide range of information about buildings and infrastructure. The existence of a field in the IFC schema does not by itself tell your team which project information to request. That decision needs a delivery purpose. buildingSMART's IFC overview ## A delivery example Imagine a project team preparing an IFC model for a design review. The reviewer wants an agreed project reference recorded for a defined group of spaces. First, the team agrees how the spaces will be identified and where the reference will be recorded. It then expresses the relevant information rule in an IDS specification. The model author prepares the delivery, and the receiving team uses compatible software to check the IFC against the issued specification. If a reference is missing, the reviewer has a specific issue to investigate. If the wrong spaces were selected, the team needs to revisit the scope before relying on the result. ## Does a valid IFC model meet every project requirement? An IFC schema check and a project information check answer different questions. A delivery needs to be usable as IFC data, and it also needs the information required for its intended purpose. For a pilot, record those acceptance questions separately. One reviewer might investigate a model-reading error while another investigates a missing project field. Keeping the questions clear helps the team find the correct remedy. ## How should the team manage the files? Agree the IFC version and the IDS support needed before exchange. Give the model issue and the requirement release clear identities, and retain the relationship between them when recording a check. Start with a small set of information that the team can inspect manually. Expand once the delivery and review workflow is understood. Read how to create an IDS file and how to review validation results , or explore the IDS editor . ## Continue reading From requirement to reviewed, tested specification. Audits, model checks and the questions behind each result. Author specifications and reusable libraries in IDS Compass. ## Define what your IFC deliveries must contain. Join the IDS Compass beta and make your information expectations explicit. Private beta · free while in beta. --- ## URL: https://idscompass.com/learn/ids-vs-cobie Title: IDS vs COBie: Roles in BIM Handover | IDS Compass # IDS vs COBie: where each fits in BIM handover COBie provides a standard structure and process for delivering information used to manage and maintain facility assets. IDS expresses requirements that can be checked against information in an IFC model. Written by Eli Weaver · Reviewed 21 September 2026 - Compare their roles - We already ask for COBie - Does an IDS pass establish a COBie delivery? - Decide whether the step is useful COBie provides a standard structure and process for delivering information used to manage and maintain facility assets. IDS expresses requirements that can be checked against information in an IFC model. They can support different parts of the same handover workflow. NIBS COBie guidance , IDS user manual ## Compare their roles - Question - IDS - COBie - What is its role here? - Specify checkable expectations for IFC information - Organise the asset information to be handed over - What would a team use it for? - Test agreed information rules on a model delivery - Prepare the agreed facility and asset information deliverable - Who needs to be involved? - People defining, producing and reviewing the model information - The owner and project participants responsible for handover data - What must the project decide? - Scope, information fields, value rules and software support - Required deliverable, fields, responsibilities and milestones COBie can be delivered in supported digital formats, including spreadsheet and other representations. Agree the required version and format at the start of the workflow. NIBS guidance on COBie structure and delivery ## We already ask for COBie. Where could IDS help? Consider the steps that produce your handover information. If some required data originates in an IFC model, an IDS-based check may help you identify missing or inconsistent model information before that data moves into the handover deliverable. This is a workflow application, rather than a promise of automatic mapping between the two standards. The team must agree how each relevant model field contributes to the deliverable, and confirm that the chosen requirement can be represented and checked with IDS. For a pilot, select a small group of maintainable assets and identify the information expected from the model. Record where it should be found, how it will be checked and what still needs review in the final handover package. ## Does an IDS pass establish a complete COBie delivery? Treat the IDS result as evidence about the rules that were applied to the IFC model. Continue to review the final COBie deliverable against its own agreed structure, required content and project acceptance process. For example, a project might request information supplied separately by a contractor or manufacturer. That part of the handover needs its own collection and review process, even if the model checks have already been completed. ## Decide whether the additional step is useful Map one real handover workflow. Identify a recurring information problem, its source and the stage at which it is currently discovered. Trial an earlier model check only where it addresses that problem. If the existing process already catches the issue reliably, focus on a different gap. The value of an IDS workflow should be visible in the team's actual delivery work. Explore BIM information management with IDS Compass , read the validation guide , or see the IDS editor . ## Continue reading Libraries, phases and releases for teams managing requirements. What an audit tells you, and what a model check tells you. Author and organise specifications in IDS Compass. ## Catch information gaps before handover. Join the IDS Compass beta and specify the model information your handover depends on. Private beta · free while in beta. --- ## URL: https://idscompass.com/learn/ids-applicability-and-requirements Title: IDS Applicability and Requirements Explained | IDS Compass # IDS applicability and requirements explained Applicability identifies the IFC objects that a specification concerns. Requirements define what the selected objects should satisfy. Written by Eli Weaver · Reviewed 21 September 2026 - Start with the information question - A selection mistake - When should a property be used? - What zero applicable objects means - Review the logic before expanding Applicability identifies the IFC objects that a specification concerns. Requirements define what the selected objects should satisfy. Keeping those roles clear helps you write a specification that checks the intended information on the intended objects. buildingSMART's specification guide ## Start with the information question Suppose a team wants every space in a pilot model to carry a project briefing category. The category is stored in the invented custom field Compass_SpaceBrief.UseCategory . The team's question is: “Which spaces are missing the required briefing category?” To answer it, the specification needs to examine spaces even when that category is absent. If it only selects spaces that already have the property, it will exclude the cases the reviewer is looking for. ## A selection mistake that changes the result - Part of the rule - Risky design for this task - Design that matches the stated intention - Applicability - Select spaces that already have UseCategory - Select all spaces in the agreed scope - Requirements - Require UseCategory - What happens to a space without the property? - It is excluded before the requirement is assessed - It remains in scope for the requirement check ## When should a property be used in applicability? Use a property to select objects when that property genuinely defines the group you want to examine. For instance, the project might want a particular rule applied only to spaces already assigned a specific, agreed use category. Write that scope explicitly. Then decide how the team will detect spaces that are missing the category used to identify them. A separate completeness requirement may be needed, or the selection may need to use another reliable part of the model. This question is particularly useful during review: “If the information used to select an object is missing, where will that problem be detected?” ## Decide what zero applicable objects means A specification can require applicable objects to exist or permit their absence. In the latter case, zero selected objects does not by itself demonstrate an information failure. Check the specification's applicability cardinality when reviewing the result. IDS cardinality guidance For your pilot, document whether the delivery is expected to contain spaces. A model containing none and a model containing spaces that a mistaken filter cannot find are different situations to investigate. ## Review the logic before expanding the library Create three small examples: an in-scope object with correct information, an in-scope object with missing information, and an out-of-scope object. Write the expected treatment of each, then inspect the actual result. That exercise often reveals an unclear scope more quickly than reviewing a long list of rules in isolation. Read the IDS validation guide , browse practical examples , or build your specification in IDS Compass . ## Continue reading Audit the file, check the model, and read the results in context. Illustrative requirements for properties, names and categories. Structure and review specifications in IDS Compass. ## Write specifications that find the cases you care about. Join the IDS Compass beta and review your selection logic before it ships. Private beta · free while in beta. --- ## URL: https://idscompass.com/pricing Title: Pricing | IDS Compass # Simple while we build. The IDS Compass private beta is free of charge. Future pricing has not been decided. There is no automatic move from the free beta to a paid plan. Before any paid plan begins, IDS Compass will explain the available options and pricing so users can decide whether to continue. --- ## URL: https://idscompass.com/contact Title: Contact | IDS Compass # Talk to IDS Compass. Email info@idscompass.com for product, beta access, privacy, or data-rights questions. Beta access requests are reviewed with a target reply time of two business days. --- ## URL: https://idscompass.com/terms Title: Terms of Use | IDS Compass # Terms of Use IDS Compass is in private beta and is provided as-is. Features may change or become unavailable. Users keep ownership of the requirements, documents and files they provide. This is a beta-stage summary and is not legal advice. --- ## URL: https://idscompass.com/privacy Title: Privacy Policy | IDS Compass # Privacy Policy IDS Compass collects information submitted for beta or guide access and basic usage data needed to operate and secure the service. It does not sell personal data. Contact info@idscompass.com for questions or deletion requests. This is a beta-stage summary and is not legal advice. --- ## URL: https://idscompass.com/gdpr Title: GDPR and Data Rights | IDS Compass # GDPR and Data Rights People can request access, correction, deletion, restriction, portability, or object to processing by emailing info@idscompass.com. IDS Compass aims to respond within 30 days. This is a beta-stage summary and is not legal advice. --- ## URL: https://idscompass.com/solutions/bim-information-management Title: BIM Information Requirements for Teams | IDS Compass # Manage BIM information requirements across projects IDS Compass helps BIM and information management teams organise the specifications behind a model delivery. Build reusable requirement libraries, apply them to a project and manage the specification sets for its phases and releases. Use a clear requirement structure to make the team's expectations easier to explain, review and maintain. Request beta access. IDS Compass reviews every request and aims to reply within two business days. ## Start with a requirement your team already uses Choose one recurring requirement, such as the fire rating needed for every door in a design delivery. Identify the relevant objects, the property to check and the accepted value. Save the reviewed specification by purpose. Record its scope and assumptions, and name the person responsible for questions or updates. ## Match each requirement to a delivery stage An early design review may need a space classification. A handover delivery may need a serial number and warranty date for every maintainable asset. For each item, record when it is needed, which objects it applies to and who must provide it. ## Make requirement changes clear When a project requirement changes, identify the release in which the change takes effect. Explain its purpose and the delivery to which it applies. Ensure the producing team can distinguish the current instruction from a previous issue. IDS Compass organises specifications in the context of projects and releases. Use that structure alongside the project's agreed communication and review process. ## Turn standards into checkable project instructions A standards reference alone does not identify the exact information needed for a delivery. The team must still decide which objects are in scope, what information is required and what result is acceptable. For example, every IfcPump in the handover model might need a manufacturer, model number and serial number. ## Try a focused pilot Choose one upcoming information delivery and a small set of requirements that matter to its recipient. Review the specifications, identify the release, and test them using the agreed checking workflow. After the delivery, record which questions arose, which issues the check revealed and which requirements were useful. Use that evidence to decide what belongs in the reusable library and what remains project-specific. ## Continue reading Author specifications, libraries and releases in one workspace. An eight-step workflow from requirement to tested specification. Where model information checks fit in an asset handover workflow. ## Make BIM information requirements predictable. Join the IDS Compass beta and organise your team's requirements around projects, phases and releases. Private beta · free while in beta. --- ## URL: https://idscompass.com/bim-standards Title: BIM Standards Guide — ISO 19650, IFC, IDS & buildingSMART # BIM standards, explained. A concise, practical guide to ISO 19650, IFC, IDS 1.0 and buildingSMART — and how IDSCompass turns these standards into a plain-language workflow for BIM information requirements. ## What are BIM standards? Building Information Modeling (BIM) standards are open, agreed-upon rules that help project teams create, share and verify digital building information. They cover processes, data formats and information requirements. The most important standards for construction information management are: The international standard for organizing and managing information about built assets using BIM. Industry Foundation Classes — the open, vendor-neutral data format for exchanging BIM models. Information Delivery Specification — the open standard for defining machine-readable information requirements. The international organization that develops and maintains open BIM standards including IFC and IDS. ## Information management, not just modeling. ISO 19650 is the international standard for managing information over the whole life cycle of a built asset using BIM. It is derived from the UK's BIM Framework and is now adopted across Europe, Asia-Pacific, the Middle East and beyond. The standard defines roles such as the Appointing Party, Lead Appointed Party and Task Teams; it requires an Asset Information Model (AIM) and a Master Information Delivery Plan (MIDP). At its core is a simple idea: information requirements must be defined clearly, then verified against what is delivered. ### Key ISO 19650 concepts - Information requirements must be defined before production begins. - The Exchange Information Requirements (EIR) set the brief. - The AIM captures approved information for operations and maintenance. - Verification proves deliverables meet the stated requirements. ### What IFC contains - Building elements: walls, doors, windows, stairs, slabs. - Spatial structure: sites, buildings, storeys, spaces. - Properties and property sets: fire rating, material, load capacity. - Relationships: containment, aggregation, spatial containment. ## The open model format. Industry Foundation Classes (IFC) is an open, vendor-neutral data format for exchanging BIM models. It is developed and maintained by buildingSMART and is the most widely adopted open standard for BIM interoperability. IFC 4.3 extends the standard to infrastructure assets such as roads, railways, bridges and tunnels, making it relevant for the entire built environment, not just buildings. Because IFC is open, owners can receive models from multiple design and construction tools and verify them against the same requirements. ## The requirement language for IFC models. Information Delivery Specification (IDS) is the buildingSMART standard for expressing BIM information requirements in a machine-readable way. An IDS file defines what an IFC model must contain — which entities, which properties, which values, and with what cardinality — so that compliance can be checked automatically. IDS 1.0 was released as a buildingSMART standard and is now supported by major verification tools. It closes the loop between ISO 19650 process requirements and the technical reality of an incoming IFC file. ### What an IDS file specifies - Applicability: which IFC entities the requirement applies to. - Property requirements: name, data type, value or allowed range. - Classification references: systems such as Uniclass or OmniClass. - Cardinality: whether a property is required, optional or prohibited. ## From brief to validated IDS file. IDSCompass maps the standards above onto a five-step workspace: describe requirements in plain language, let AI structure them, reuse and version them in a library, publish standards-compliant IDS files, and validate incoming IFC models. ### Describe Paste a brief, email, PDF excerpt or chat transcript in plain language. ### Structure AI extracts entities, properties, data types, values and constraints. ### Reuse Store requirements in a versioned library and compose them into sets. ### Publish Export a standards-compliant IDS 1.0 file for any downstream checker. ### Validate Run an incoming IFC model against the requirement set and get a pass/fail report. ## Manual XML authoring vs. IDSCompass. - Capability - Manual XML - IDSCompass - Authoring - Write XML by hand or template - Plain-language input with AI structuring - Validation - Validate externally after export - Built-in validation against IDS 1.0 - Reusability - Copy files between projects - Versioned library and requirement sets - Collaboration - Email files and track versions manually - Shared workspace with clear ownership - IFC checking - Use a separate checker - Validate IFC models against requirements - Standards - Author must know IDS schema - IDS 1.0 output generated automatically ## Who uses these standards with IDSCompass? ### BIM & Information Managers Turn project briefs into structured, reusable information requirements and publish IDS files the delivery team can execute against. ### Owners & Asset Managers Define the information you need to operate the asset, then verify that incoming models contain it. ### Consultants & Contractors Know exactly what models must contain before delivery, reducing rework and rejection. ## Standards-ready requirement checklist. Use this checklist to verify that your information requirements are ready for ISO 19650-aligned delivery and automated IDS checking. - Requirements are written in plain language before structuring. - Each requirement maps to a specific IFC entity or type. - Property names, data types and values are explicitly defined. - Cardinality is stated: required, optional or prohibited. - Classification references are included where relevant. - The IDS file is exported as buildingSMART IDS 1.0. - Incoming IFC models are validated against the published IDS. - Requirement sets are versioned and reusable across projects. ## Common questions. ## What is the difference between IFC and IDS? + ### What is the difference between IFC and IDS? IFC (Industry Foundation Classes) is the open data format that describes what is in a BIM model. IDS (Information Delivery Specification) is the open standard that defines what information a model must contain to be accepted. IFC is the answer; IDS is the question. ## Is IDS a buildingSMART standard? + ### Is IDS a buildingSMART standard? Yes. IDS is maintained by buildingSMART International as an open standard for specifying information requirements in a machine-readable way. IDS 1.0 is the current major release. ## Do I need to know XML to write an IDS file? + ### Do I need to know XML to write an IDS file? Not with IDSCompass. You describe requirements in plain language and the workspace structures them into standards-compliant IDS XML. You can still inspect or edit the XML at any time. ## How does ISO 19650 relate to IDS? + ### How does ISO 19650 relate to IDS? ISO 19650 defines the processes and information management principles for BIM. IDS provides the technical mechanism to express the information requirements that ISO 19650 asks you to define and verify. ## Can IDS files be reused across projects? + ### Can IDS files be reused across projects? Yes. Because IDS is a standard format, a requirement set written for one project can be reused, versioned and adapted for another. IDSCompass stores these in a versioned library so teams do not start from scratch. ## What downstream tools can read IDS files from IDSCompass? + ### What downstream tools can read IDS files from IDSCompass? Any tool that supports the buildingSMART IDS 1.0 standard, including Solibri, BIMcollab ZOOM, simplebim, DDS-CAD and open-source IDS validators. ## Turn standards into a working workflow. Join the IDSCompass beta and start authoring ISO 19650-ready IDS files from plain language. Private beta · free while in beta. © 2026 IDSCompass