If the participants are not recording and sharing information via COBie files or models, then they should be doing so through documents and spreadsheets. The way these documents should be formatted is specified in Annex A of PAS 1192-6.
Here we can see how all the topics covered previously come together to influence the way this spreadsheet is formatted. We can see for instance the definition fields that were established in the risk information section. They are shown here as ‘Risk Name’, ‘Risk Category’ and ‘Risk Description’.
Another example is the presence of the fields that are used to record information associated with a risk. These fields were defined in the context information section. They are shown in the spreadsheet as ‘Associated Product’, ‘Associated Activity’ and ‘Associate Location’.
Here we can see how all the topics covered previously come together to influence the way this spreadsheet is formatted. We can see for instance the definition fields that were established in the risk information section. They are shown here as ‘Risk Name’, ‘Risk Category’ and ‘Risk Description’.
Another case where this scale could be used is in the ‘Risk Likelihood’ and ‘Risk consequence’ fields. If you remember well, these fields had been established as recommended in the risk information requirements. Filling in these fields with a qualitative scale such as a ‘Green’, Amber’ ‘Red’ system could help people to visualise risks better.
If you do not want to record and share health and safety information manually in a document or spreadsheet, PAS 1192-6 gives you another two format options. One of these options is the use of COBie. Technically speaking COBie is not a format, but a schema. But this is not important for our discussion today.
Knowing that this is a possibility is important, as COBie is a format created to facilitate the exchange of information between systems, especially from proprietary systems used during design and construction to CAFM systems, during operations.
Annex A in PAS 1192-6 gives specifications on how to map out the fields established in context information requirements and risk information requirements to the fields established in the COBie standard – PAS 1192-4.
Here you can see, for example, that information on the built asset, required in context information is mapped out to be recorded in the Facility tab in the COBie standard. Here we can see the name/code for the building, the category code, the project to which this building is associated, etc.
On this figure, you can see that risk information has been recorded in the ‘Issue’ tab in COBie. Here again, we can see the code for the risk, the person who created this risk, the risk level is recorded in the ‘Risk’ field.
Finally, all the health and safety information could be recorded in a model. The advantage of doing so is that the two previous formats mentioned previously can be exported from the model. In fact, if the information is recorded in the model, you can choose how you are going to export it. just remember – PAS 1192-6 asks for participants to use a consistent format throughout the project.
Another advantage is that people can make better sense of health and safety data if it is recorded in a 3D environment. Usually, people feel more engaged with the risk identification activity – it is more fun to navigate a 3D model than an excel spreadsheet.
Recently, different organisations have been populating their models with ‘Risk cubes’ that have the functionality to hold all the health and safety information specified in PAS 1192-6. The cubes are a great tool for engagement as people can visualise what the problem is in the model and then fill in the parameters in these objects with relevant information.
This also allows for further analysis to be carried out, for instance, we could run a query in the model to know in which areas of a building more ‘Risk cubes’ have been placed.
A possible issue with the use of risk cubes is that when people are pressured for the time they might feel inclined to randomly populate the model with these objects and do not feel in the parameter appropriately.