Ideas
Our machinists use admin portal to check available tools while programming and at start of setups. It would be great if user could save picking lists in admin portal and then later open it from storage as picking list. Now for jobs with big amount of items you need to have separate list to go pick the tools. This is just waste of time. Even one list per user would be nice addition, but as we run multiple machines per operator, better would be few lists with savable names (for different jobs, other machine, next job, job in programming etc.). Also to keep picking lists in control, it should be deleted after picking (otherwise some operators will have all of them stored rest of life, which gonna lead to mess).
Thanks Tuomas. We're linking this with CRW-I-411 (80 votes for general pick list management) since both address the same gap: Admin Portal needs native pick list capabilities.
Between your feedback (resumable, reusable user lists) and CRW-I-411's requirements (full CRUD, reservation visibility), we have a clear picture of what's needed. Moving both to "Under consideration" as we evaluate a combined approach.
Thank you Anton to finally react this idea.
Your points are good questions:
It would be of course good if user would be able to continue picking later, in case all was not picked.
Of course reusable list would be nice, and I guess in some companies they would love them even more (if only reccuring jobs). Reusable list just should have option to leave some items off from picking if they are not needed (for example in was used in previous job). On the other way reusable lists need to be easily updatable from portal.
I have tiny workshop and I trust my workers, so I would let them handle lists individually. Bigger companies probably would want to control lists otherway to have unneccary people in middle-management something to do ;)
Thanks for flagging this, Tuomas - and Harri, appreciate you bringing it back to our attention.
We see the real workflow problem here: you're planning jobs in Admin Portal (checking what tools exist) but then have to manually recreate that list to actually pick in SFI. That's friction we should solve.
Current state: Pick Lists do exist, but they're created only through ERP or Excel import - there's no "quick save" button while you're browsing tools in Admin Portal. That's the gap.
Before we design the solution, a few questions to make sure we get this right:
1. List lifecycle: You mention lists should "delete after picking" - but what if an operator accidentally picks only 5 of 10 items? Should the list stay available for a retry, or is deletion automatic regardless?
2. List reuse: Do some lists become recurring (e.g., "Job Type A always needs these 12 tools"), or are most truly one-time/per-job?
3. Scope: Is this mainly for individual machinists managing their own jobs, or do supervisors need to see/manage other users' lists?
These details will help us design something that works for your specific workflow.
Is there any progress on this matter? Would be very useful for some of the customers.