Setting an operator's equipment
Use this to say which machine an operator drives, or that the operator walks. The machine decides how heavy a task the operator is offered, and which picking policy a work area uses for cart picking.
Before you start
- You need the role
ADMINorMANAGER. The methodupdate_operatoris for these two roles by default. See Who can do what. - The equipment profile must exist. Profiles are set up on the work area and equipment screens, not here.
Steps
- Open
Task Manager > Operators. - Click the operator. The Operator card opens.
- In
Equipment Profileclick the picker and choose a profile. To make the operator walk, useClear valuein the picker. - Click
Save.
What happens
The operator row is updated. Only Equipment Profile is sent. Login, name and active cannot be changed here.
| Result | What follows |
|---|---|
A profile with max_weight above 0 | A task heavier than max_weight minus weight_reduction_per_level times the level of its location is not offered to the operator. |
A profile with max_weight 0, or no profile | No lifting limit. |
A task with no known weight passes any limit.
Source: TaskBmc::LIFTABLE_SQL in crates/libs/wms-lib-core/src/model/tasks/task.rs, crates/libs/wms-lib-core/src/model/equipment_profile.rs:55-90.
The value can be replaced later when the operator names a machine on the RF terminal. See Operator card.
If it is refused
| You see | Why |
|---|---|
| A refusal that names the profile (restrict key) | The profile does not exist or cannot be used. |
Forbidden for the method | Your role has no right to update_operator. |
Not confirmed by code: the exact text of both refusals. To verify: try to save as
SUPERVISORon a test warehouse. The profile is protected by aRESTRICTkey (comment inclaim.rs:180).
Related pages
- Operators
- Operator card
- API:
update_operator(sendsidandequipment_profile_id; an explicitnullclears it) - RF terminal:
PKA00"Get Area Work"