Good Usage on Tasks

Good Usage is the record that connects a specific material (Variant) to a specific Task on a project. It is the final link in a chain that runs from “we planned to install this pipe here” all the way to “this task consumed it.”

What Good Usage is

When a Task requires a physical material, a Good Usage record is created. It captures:

Field	What it means
Task	The specific Task that needs or consumed this material
Quantity	How many units of the material this Task needs or consumed
Technical Structure Good	Optional link to the Required Good entry on a Technical Structure node, connecting back to the project design
Technical Structure Node	Optional direct link to a Technical Structure node, used when the usage is not tied to a specific Required Good line
Procurement Request	Optional link to the demand record that sources this material — either a STOCK pull or a PURCHASE

Note

A Good Usage stores its Quantity on the usage itself, starting at 1 by default — it is not pre-filled from the Required Good’s planned Bill of Materials quantity. Adjust it afterwards to match what the Task actually needs or consumed.

Why Good Usage matters

Without Good Usage, you would know that a Procurement Request exists and that a Purchase was made — but you would not know which Task on the project actually used the material. Good Usage closes that gap.

This matters for:

• Task progress — field workers and project managers can see exactly which materials are assigned to each task
• Traceability — you can trace from any task back to the purchase order, or from any purchase order forward to the task that consumed the goods
• Cost attribution — procurement costs can be attributed to the specific task and by extension to the project’s Work Breakdown Structure

For Engineers

When your project uses a Technical Structure, the Required Good on a node carries the design-level demand. Good Usage records connect that demand to the Task where the material is consumed — keeping design, procurement, and execution linked throughout the project.

For Field Workers

You will typically see Good Usage records listed under a Task in your work view. Each entry tells you which materials have been requested or are allocated to that Task. If a material you expect to see is missing, check with the procurement team whether a Procurement Request has been raised.

The full chain in one view

Technical Structure Node
  └── Required Good (Variant: Steel Pipe DN100, qty 10)
        └── Procurement Request (STOCK or PURCHASE)
              └── Good Usage
                    └── Task (e.g. "Install main distribution pipe, Segment A")

Reading top to bottom:

• The Technical Structure node captures where something will be installed
• The Required Good records which Variant is needed at that node
• The Procurement Request handles sourcing — either pulling from stock or raising a Purchase
• Good Usage links that procurement demand to the specific Task
• The Task is where the material is physically consumed

Caution

If you delete a Procurement Request that has Good Usage records attached, those usages lose their procurement link. Always check for Good Usage entries before removing a Procurement Request.