Issues
Open points across 2D, 3D and the site
One issue can document an instance in the drawing, the objects in the model and at the site, linking all three instead of being kept as three separate issues. Each one saves the view it was raised from, and all of them are exchangeable with other platforms as BCF.
- The industry standardIssues follow the buildingSMART standard in full, with no proprietary extensions of our own. What is raised here reads unchanged elsewhere, and comes back the same way.
- One simple status flowDocuments and forms run the workflows a project draws for itself. Issues deliberately do not: they follow the simple status flow the standard defines, so a status means the same thing to everyone.
- Raised in every viewer
An issue is raised where the case turns up: in the PDF viewer, the BIM viewer and the GIS viewer.
- Linked to the object
An issue hangs on the objects it concerns, and is found again through the object itself instead of by searching the issue list.
- Themes define the values
Issues sit in themes, and the theme sets which values are allowed at all: statuses, types, labels, stages and priorities.
- Owner and due date
Every issue carries an owner and a due date, the fields the buildingSMART standard sets out.
- Linked to forms
A completed form can be linked to a single issue or to several, so the inspection and the open points that came out of it stay together.
- Exchange as BCF
Issues travel to other programs as BCF 3.0, the most current version of the standard, and come back the same way.
A theme decides which values an issue can have.
A theme is where a project sets the standard it has decided to follow, so every issue in it stays inside those values. An exported issue carries its theme's values inside it, as they are part of the buildingSMART standard too. On import, the values of the incoming issues are checked against the theme they belong to: values that do not match are adjusted, or added to the theme.
