Core Concepts
IDS Metadata
Best practices for IDS file metadata
IDS files include metadata describing the purpose and scope of your specifications. Configure both file-level and specification-level metadata in IDSedit.
File Metadata
Configure these fields in IDSedit's IDS settings panel:
| Field | Description |
|---|---|
| Title | The document title (e.g., "Fire Safety Requirements") |
| Description | Detailed explanation of the IDS purpose |
| Version | Version number (recommended: semantic versioning like 1.0, 2.1) |
| Author | Contact email for questions |
| Date | Publication date |
| Copyright | Copyright holder |
| Purpose | Why the information is needed (e.g., "cost estimation", "coordination") |
| Milestone | When the information is needed (e.g., "Schematic Design", "Construction") |
Specification Metadata
Each specification in your IDS can have:
| Field | Description |
|---|---|
| Name | Short descriptive name |
| Identifier | Unique ID for tracking (e.g., "SP01", "FIRE-001") |
| Description | Why this requirement is important |
| Instructions | How to fulfill the requirement |
| IFC Version | Target IFC schema (IFC2X3, IFC4, IFC4X3_ADD2) |
Best Practices
- Write clear descriptions - Explain the business value of each requirement
- Include instructions - Guide model authors on how to comply
- Use meaningful identifiers - Make specifications easy to reference
- Specify IFC versions - Ensure compatibility with target workflows
Learn More
For detailed metadata guidelines, see the official IDS metadata documentation from buildingSMART.