buildingSMART
Construction phase/LOI related IDS Check
A question about the attribute check of the IDS with reference to phases. As far as I can see the examples and documentation Nowhere has a phase been defined from which an attribute / an attribute value is defined must be present. All requirements of the IDS are therefore always compared with the IFC without the phase in which they are IFC is located would be taken into account.
From the perspective of an ongoing project, the IDS makes sense because it contains all the attributes to be delivered contains, but these are always checked as a whole. Due to the fact that certain attributes / attribute values will only be present in the model in later phases - such as product attributes such as manufacturer or serial number - comparing an IFC with the IDS results in unnecessary not being relevant Missing attributions can be found because they cannot yet be provided.
An selection of attributes an the phase on which those needed to be check:
In particular, it should be possible to attribute according to a phase such as the planning phase or construction phase or a LOIN. However, it currently looks like the IDS only as a tool for testing as-built models - if all information is available.
The main question is therefore whether it is planned for the IDS to be able to check attributions for each phase?
Furthermore, the question arises as to whether a period of time can be specified within which attributions must be made. so that, for example, the attribute BSMART_Variant can only be used in the planning phase but not in later phases.
IfcProject.Phase is available to solve this.
- Require setting it from your allowed values. In the U.K. we are encouraged to use 0-7 (see iso19650 part 2 U.K. National annex v2)
- Use it as applicability for subsequent requirements. A greater than test is possible with the U.K. usage. Otherwise a Regex may be needed.
Every IDS file has a Milestone property in the metadata. So Milestone should contain your Phase name. This means you'd have multiple IDS files split by phase (& potentially Purpose).
Version 1.0 has very limited support for LOIN, like @andyward explained. I would argue that the next release should take a significant step to improve this, and hopefully provide full coverage.
Resolution: the IDS Purpose and Milestone now closely align with Purpose and Milestone description from the LOIN standard (EN17412). A user can use that IDS metadata to reference/implement their LOINs. The current limitation is that one IDS file (containing many specifications) can only refer to one pair of purpose and milestone. In the future version of IDS, it should be considered if it should be possible to address many LOINs in one IDS file. Moving to milestone 2.0.
Good move and direction. Btw. the European Standard EN 17412 is currently transformed into an International Standard ISO 7817, so even more important (not sure about current policy in bSI to directly refer to ISO Standards in own deliverables).
One more point for milestone 2.0. In the LOIN standard, there are four so called prerequisites. Beside milestone and purpose, also actor and object (ako breakdown structure). Those could be relevant for an IDS2.0, if the scope would extend from validating a single IFC file into also validating federated models (here you want to adress e.g. the information by a certain actor (like architect) or coming from a certain discipline model (like structural model) which is currently not in scope. So could we put it onto an 2.0+ wish list?
