Risk Management
Relations from Other Scenarios
- Fall Risk ← specific ← Risk Management
- Fire Risk ← specific ← Risk Management
- Risk Planning ← in planning ← Risk Management
- Risk Tracking ← in construction ← Risk Management
Summary🔗
This scenarios examines how the risks should be managed on a construction site.
This involves both keeping track of the existing risks as well as inspecting the site for the new risks, checking the state of the installations etc.
Models🔗
standard/risk_level🔗
Risk levels defined at the national and international level.
risks🔗
This model captures all the risks.
As risk is a non-IFC entity, it does not live in bim_extended (from evolving_plan).
Definitions🔗
risk manager🔗
This is an role (from actor_management) that manages certain kinds of risks.site
For example, this can be a health and safety manager (from fall_risk) monitoring the fall risks (from fall_risk) or site protection manager (from fire_risk) monitoring the fire risk (from fire_risk), but can also be a construction engineer responsible for curing the concrete etc.
risk level🔗
This is the risk level according to different standards.
The risk level refers to a concrete standard in standard/risk_level.
risk zone🔗
This is an IfcZone living in bim_extended (from evolving_plan) that demarcates a zone
of a specific risk.
risk type🔗
The risk type is a more general type of a risk ("fall", "fire" etc.).
risk🔗
A risk is a custom, non-IFC entity representing a safety or an economic risk.
A risk is of a risk type.
It is tied to zero, one or multiple responsibility zones (from risk_tracking).
The risk can be associated with zero, one or multiple risk zones. If there are no risk zones defined, the risk is considered unconfined. If there is one or more risk zones defined, the risk applies only to these zones.
The risk is also associated with zero, one or more tasks (from scheduling).
The risk must have a validity time span (which can also be open-ended). There should be a special flag to indicate that the temporal validity of a risk is directly tied to its corresponding tasks (from scheduling). For example, this is important if the tasks (from scheduling) are re-scheduled and the risk temporal validity needs to reflect that.
The risk is assigned a risk level.
The risk can be related to one or multiple topics (from topic_management) (e.g., when a safety-relevant element is missing or damaged).
The risk lives in riskss and have identifier (from unique_resource_identification).
Scenario🔗
In this scenario, we look into how to manage the risks with the system.
The risk in the context of this scenario does not refer strictly to a safety risk (such as fall risk or fire risk), but encompasses a much broader family of risks (such as concrete cracking, which is an economic risk, but not necessarily a safety risk).
This scenario is split into two sub-scenarios by the respective phase:
- "Risk Planning" which covers how the risk management plan is created during the planning,planning and
- "Risk Tracking" which looks into how the risks are tracked, mitigated and escalated during the construction.construction
As-planned🔗
We assume that the data from bim3d (from evolving_plan) and bim_extended (from evolving_plan) is accessible from the office.office
Test Cases🔗
test for magnitude🔗
We write a script to generate automatically dummy tasks.
We also use generated images from test_for_magnitude (from thermal_inspection) to randomly assign them to the dummy tasks.
blind test removed item🔗
(This is a blind experiment and might not be legally possible.)
Remove a safety item and inform the workers.
Check that the responsible person could find out that it is missing using the system.
analytics correct on an example🔗
Record 3 complete states of the whole system and freeze them.
Manually compute the expected analytics.
Check that the output of the system coincides with the manually computed analytics.
Acceptance Criteria🔗
magnitude🔗
The system needs to handle the risk related tasks (from scheduling) in the order of thousands.