Activity 2: Plan task
Introduction
In this activity, we will configure the task (its title, duration, linkage to the 3D model or other properties) and upload all documents necessary to perform risk assessment, task plan inspection or task execution.
Before starting working on this activity, you should know about:
- Basic understanding of DTXS API
- Working with documents via DTXS API
- Working with records via DTXS API
- How ontologies are used to classify records
Expected output
Detailed plan of the decommissioning task, saved to the DTXS server as:
- a 3D model of the inventory/room/facility in which the task will be performed, represented as an .ifc file
- a set of records of various classes holding information about task goal, workforce, planning information etc.
Steps
This task will be associated with the 3D model for better risk identification and plan inspection.
Let's upload the 3D model first. We will upload the model into the root folder.
Important Uploading a document will return UID of this document. This UID and all other UIDs generated in further steps, will be important - you shall save them in some notepad for the future use.
Do not forget to save the returned UID of the document for the future use.
To better describe the 3D model that we have uploaded now, it is good to upload some additional information. Other experts working on this task will value this.
Let's create a record of class ndc:Assets.Intangibles.Documents.
Important Creating a record will return UID of this new record. This UID and all other UIDs generated in further steps, will be important - you shall save them in some notepad for the future use.
Do not forget to save the returned UID of the document for the future use.
In later steps, we will be specifying team doing the task. But before, we need to prepare few other things.
Each member of a team (e.g., worker or robot) can have one or more roles assigned. For example, John can work as a robot operator in one team and a project manager in the second team. A role is a record of class ndc:Actors.Roles.
We will now create several roles to be used later in definition of a team.
Do not forget to save the returned UID of each role for the future use.
Team consists of its members; members can be of different nature. In this tutorial we will use Persons and Robots. Create few records of class ndc:Actors.Persons or ndc:Actors.Robots.
Note: We will create two records of class Actors.Persons and one record of class Actors.Robots
Do not forget to save the returned UID of the team for the future use.
Now we have everything ready to create team: roles, workers and robots. Let's create a team now.
The team will be:
- Jupiter Jones as Radiation protection expert
- Peter Crenshaw as Robot operator
- RadEye as the robot doing the measurements
Create record of class ndc:Actors.Teams.
Important We will be using UIDs of previously generated records for roles, workers and robots. In the command below, you will have to replace the UID placeholders with the UIDs that you received earlier.
Do not forget to save the returned UID of the team for the future use.
Tasks are stored as records of the class ndc:Tasks. Create the task now and store the returned UID of the task for the future use.
Do not forget to save the returned UID of the task for the future use.
Conclusion
In this activity, we've learned how to upload documents (3D models) and create records.
We have created a plan for the task:
- with an associated 3D model,
- and having a team responsible for performing the task
If you have access to the Aquila Twinlab tool, you should see all the data there.
Now, continue to the Next activity: Identify risks.