-
Notifications
You must be signed in to change notification settings - Fork 66
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Make Purpose and Milestone definitions and examples aligned with the Level of Information Need (EN 17412-1, 5.2-5.3).
- Loading branch information
Showing
1 changed file
with
3 additions
and
3 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -13,9 +13,9 @@ Each `.ids` file has basic metadata that are common to all **Specifications** li | |
| 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" | | ||
| Author | The author of the IDS, provided as an email contact address | "<[email protected]>" | | ||
| Date | The date the IDS was published | "2022-01-01" | | ||
| 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". | | ||
| 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". | | ||
| Milestone | Which project milestone the IDS should be satisfied in | "Design", "Construction", or "Comissioning" | | ||
| 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". | | ||
| Purpose | Why the information is needed. | "quantity take off", "accessibility analysis", "clash detection", "coordination", "cost estimation". | | ||
| Milestone | Delivery milestone when the information is needed. | "Schematic Design", "Construction", "Commissioning", "RIBA Stage 3", "As-built", "Planning", "350", "400". | | ||
|
||
## Specification metadata | ||
|
||
|