Back to ontology

Table of Contents

Phase Index

Level Index

Risk Tracking

Relations to Other Scenarios

Summary🔗

This scenario is a sub-scenario of "Risk Management" which considers how the risks are tracked, mitigated and escalated on day-to-day basis on the construction site.

Definitions🔗

preventive resource🔗

This is an role (from actor_management) that is responsible for one or more responsibility zones on the construction site to keep track and mitigate the risks (from risk_management).zone

(Mind that a preventive resource and the risk manager (from risk_management) can be one and the same person in certain sites, e.g., when the site is small.)

responsibility zone🔗

A responsibility zone as an IfcZone living in the bim_extended (from evolving_plan).

assignment🔗

Responsibility assignment of a preventive resource.

The assignment is a non-IFC data structure and relates the risks (from risk_management) and the preventive resources.

Scenario🔗

As-planned🔗

Update of the risks (from risk_management). Both the risk manager (from risk_management) and the preventive resource can insert new and change existing risks (from risk_management) accordingly.construction

Specification of the assignments. There needs to be a separate application so that the risk manager (from risk_management) can create, list and modify assignments of the risks (from risk_management) to the preventive resources.

Though some risks (from risk_management) are not necessarily spatially confined (e.g., some risks can be abstract, such as "the workers are wearing safety helmets"), they are still part of an assignment. In these cases, the assignment means that a preventive resource is responsible for the unconfined risk (from risk_management) in the given zone (e.g, that all workers wear a helmet in the given zone).

As-observed🔗

The risk manager (from risk_management) needs to create focus spots (from uxv_recording) in order to observe the necessary spots for potential new or changed risks.

The focus spots (from uxv_recording) are observable through recordings (from digital_reconstruction) and taken into account during the missions (from uxv_recording).

Divergence🔗

Depending on the risk (from risk_management), we can use "Thermal Inspection" and/or "Virtual Inspection" to inspect whether the risk is present or absent.

For example, the preventive resource can check if the safety nets are still there and not damaged using "Virtual Inspection". The absent, ill-placed or damaged elements are reported as a topic (from topic_management) using "Topic Management".

This is different to assessing or discovering a new risk (please see the Safety section).

Analytics🔗

The system allows the risk manager (from risk_management) to track the following indicators:

The assignments should be visualized separately (e.g., as a 3D or 2D geometry).

Scheduling🔗

The risk manager (from risk_management) needs to inspect the tasks (from scheduling) in "Scheduling" as the task shadows (from scheduling) are linked to the risks (from risk_management).

Safety🔗

Virtual inspection. The risk manager (from risk_management) filters the tasks (from scheduling) with an elevated risk in "Virtual Inspection".

The spatial and temporal relations between the risk zones (from risk_management) are then automatically visualized in "Virtual Inspection" (e.g., using the temporal validity of the risk (from risk_management)).

Reporting. The system needs to report an overview of all the risks (from risk_management).

The risks (from risk_management) need to be displayed together with their related tasks (from scheduling), if any, as a time table.

For example, we can display the risks (from risk_management) as a Gantt diagram. The risks (from risk_management) would be represented with thick bars, while the related tasks (from scheduling) would be visualized inside these bigger bars as thin bars. (Mind that this is just an idea and needs to be experimented with during the implementation.)

The user should filter by:

Escalation. If there is a problematic task (from scheduling), the risk manager (from risk_management) should create a topic (from topic_management).