Workforce
Every workplace gets its own list: what is due next, and why.
A worklist per station.
A storage area, a plotter, a packing table and a desk are four workplaces with the same question: what is next?
Nobody creates tasks by hand. They arise from what is already there, and Gimel reconciles them: an internal order is a cutting task; without staged material it is also a picking task; an order with parts that are cut but not shipped is a packing task; an order that still needs attention in the office is a processing task.
A station's queue is the sum of all its tasks, not only the internal orders: a packing table with many open shipments is full even if no internal order lies there.
- Not first come, first served
- Every task carries a priority made of named factors: the promised date, a rush flag, how long it has waited and whether work on it has started.
- Fewer changeovers, no broken promise
- Within the promise window the order may be rearranged to save changeovers: internal orders of the same material and thickness run back to back, so the machine is set up once instead of each time. The one hard rule is that the bonus applies only as long as not a single promise breaks.
- Readable afterwards
- Every task shows its factors, every place its sentence and every move its reason.
Three roles are enough.
Keeping prices and managing access are different levels of trust.
- Customer
- Orders and follows their own orders.
- Staff
- Maintains materials, prices and rates and runs production, but cannot create users.
- Admin
- May do everything, including managing users.
Accounts can be protected with a second factor from an authenticator app. Recovery codes are stored hashed and work once. Guessing is limited, a code works only once, and other sessions end when the second factor changes.
An audit trail for what matters.
Who changed what, and when.
Prices, rates, stock movements, shipments and user accounts each write an entry with the person, the action, the object and the detail. A change to prices or access without a trace is not provided for in a B2B system.
Compliance.
The workflow for security reports and advisories under the EU Cyber Resilience Act.
Vulnerability reports arrive through a public form. Staff sort them, set status and severity, and write and publish security advisories and the support period for each product. A report is stored before it is announced, so a mailer that is off cannot lose one, and the reporter's contact details are deleted once the case is closed and the deadline has passed.