Skip to content

Commit 7a386d0

Browse files
authored
LOIN metadata description (#303)
Make Purpose and Milestone definitions and examples aligned with the Level of Information Need (EN 17412-1, 5.2-5.3).
1 parent 6893df1 commit 7a386d0

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

Documentation/ids-metadata.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -13,9 +13,9 @@ Each `.ids` file has basic metadata that are common to all **Specifications** li
1313
| Version | The version of the IDS, to keep track of changes that have been made. Semantic versioning is recommended where versioning follows the naming scheme of X.Y, where Y represents a minor change, such as changes in metadata, description, or spelling errors, and X represents a major change, where models that used to pass or fail in a previous version may yield a different result. | "1.0" or "2.1" |
1414
| Author | The author of the IDS, provided as an email contact address | "<[email protected]>" |
1515
| Date | The date the IDS was published | "2022-01-01" |
16-
| Description | One or more sentences that further elaborate on a description who the IDS might be for, why it is created, what projects it might apply to, and so on. | "Minimum requirements for all OpenBIM projects to ensure basic coordination and data scheduling can be done by all stakeholders. Expected to be run prior to model sharing and is a requirement for all project milestones." or "Specifies required properties that have a large impact on the accuracy of cost estimation and quantities that are necessary for automated model-based quantity take-off. To be read in conjunction with the cost planning geometry guideline and reinforcing modeling practices guide". |
17-
| Purpose | A short one sentence summary of what the IDS achieves | "Minimum requirements for all OpenBIM projects for basic coordination" or "Property requirements for accurate model-based cost planning". |
18-
| Milestone | Which project milestone the IDS should be satisfied in | "Design", "Construction", or "Comissioning" |
16+
| Description | One or more sentences that further elaborate on a description who the IDS might be for, why it is created, what projects it might apply to, and so on. | "Minimum requirements for all OpenBIM projects to ensure basic coordination and data scheduling can be done by all stakeholders. Expected to be run prior to model sharing and is a requirement for all project milestones." or "Specifies required properties that have a large impact on the accuracy of cost estimation and quantities that are necessary for automated model-based quantity take-off. To be read in conjunction with the cost planning geometry guideline and reinforcing modeling practices guide". |
17+
| Purpose | Why the information is needed. | "quantity take off", "accessibility analysis", "clash detection", "coordination", "cost estimation". |
18+
| Milestone | Delivery milestone when the information is needed. | "Schematic Design", "Construction", "Commissioning", "RIBA Stage 3", "As-built", "Planning", "350", "400". |
1919

2020
## Specification metadata
2121

0 commit comments

Comments
 (0)