Activity 3: Identify risks
Introduction
In this activity, the risks of the previously specified task will be identified. This activity will be done by an expert in the field of decommissioning safety. Let's assume that this expert is using some external tool for risk analysis and this tool uses inputs from the previous activity and generates list of identified risks.
We will show here, how this risk analysis tool can download necessary inputs from the DTXS server and upload the results of the risk analysis back.
Expected output
List of risks for the previously planned task, saved to the DTXS server as a set of records of ndc:Safety.Risks.Register class and assigned to the task using the ndc:Tasks:RiskIds property.
Steps
Note: In this example, the 'download-record' operations are creating separate JSON files. These files would then have to be loaded into an external risk-analysis tool. It is recommended to use a DTXS-client directly in the tool to avoid creating and reading JSON files back-and-forth.
The 3D model has been uploaded in the previous activity. Now we will use it for visualisation of the task plan.
Let's suppose that this activity is done by an expert who does not have any connection to those who planned the task in the previous activity. So, we will need to download all information about the planned task from the previous activity. Example below illustrates that there will be multiple download-record commands. Full example is available in https://github.com/wai-blue/dtxs-client/blob/main/use-case-1-3.py
Use download-record to download all other necessary data like worker roles, workers and robots or definition of teams. See the previous activity for the list of downloadable data. You will need UIDs of each record.
Note: These other data could be, e.g., already known hotspots. If your current task is, e.g., to dismantle a certain component, you might need to know the hotspots measured in one of the previous tasks. These measurements are important input to the identification of the risks and so the should be available in the next steps.
All inputs for the risk analysis are ready to be used. Feed/import them into the tool.
If the tool would have a DTXS client directly implemented, the transfer of data could be transparent, without using external JSON files.
No interaction with DTXS is necessary now.
Use your risk-analysis tool to identify risks.
Let's suppose your risk-analysis tool has a user interface which allows an expert to create a risk. Once the risk is created, the tool shall call the DTXS API to create a record of class ndc:Safety.Risks.Register.
Similar operation should be done for update: python dtxs-client.py config.json update-record ...
Conclusion
In this activity, we've shown how an external tool can download inputs from DTXS to perform risk analysis and then upload the results (list of risks) back to the server.
If you have access to the Aquila Twinlab tool, you should see list of identified risks there.
Now, continue to the Next activity: Task inspection and risk assessment.