Lesson 1 of 0
In Progress

Ensuring Data Requirements

Depending on the complexity of a building, collecting and coordinating data on maintainable assets from various specialists might become a mammoth task.

Chances are that if we leave all the COBie information to be recorded and recorded near the end of a project, we are not going to get the results we expected.

That is why it is important to create mechanisms that will allow people to check how information is progressing so that we can ensure that data requirements are being met.
On projects where COBie is a deliverable, is important that clients specify the stages at which partial COBie information should be handed in.

Establishing a ‘data-drop’ together with intermediate quality control tests is an efficient way to measure how information is progressing and make sure that the golden thread of information will not be broken.
But how are these checks carried out?

Every Model View Definition – MVD – specifies the attributes used to collect data and the checking rules to validate that this data is being inserted in an appropriate way.

COBie is no different. The standard specifies a series of rules that should be applied to each field to validate the data structure.
• We already have seen one of these rules: the “Unique” rule for values that are referenced by other tables.
• Many other rules can be found in the COBie standard.

We don’t need to memorise them, because these rules are usually coded into tools that do these checks automatically.

Can you imagine checking an excel spreadsheet with more than one-hundred-thousand entries manually?