VISUAL often has several open customer orders on one project. The packet's customer, PO and dates come from one of them.
Built as the default (one function, feed/orders.py): a Clerical pin, else the base's own linked order, else the project order whose top job is the unit, else the project's first open order, else its newest. The source is stored and shown on the project page, which lists every open order; Clerical can pin another with a reason.
To answer: keep, or give a better rule.
Plan reference: Q5 in docs/PLAN.md (open questions). Answer here; the build takes the default until then.
VISUAL often has several open customer orders on one project. The packet's customer, PO and dates come from one of them.
**Built as the default** (one function, `feed/orders.py`): a Clerical pin, else the base's own linked order, else the project order whose top job is the unit, else the project's first open order, else its newest. The source is stored and shown on the project page, which lists every open order; Clerical can pin another with a reason.
**To answer:** keep, or give a better rule.
---
Plan reference: Q5 in [docs/PLAN.md](https://gt.pescoinc.biz/spencerm/PacketStation/src/branch/main/docs/PLAN.md) (open questions). Answer here; the build takes the default until then.
In VISUAL one project often has several open customer orders at once (for example a first order for two units and a later add-on order). The packet header shows one customer, PO number and due date, so Packet Station has to pick one order per packet.
How it picks today, in this order:
If Clerical pinned an order on the project page, that one.
Else the customer order VISUAL links to the packet's own work order.
Else the project order whose line lists this unit as its top job.
Else the project's first open order, else its newest.
The project page lists every open order and shows which rule picked it, and Clerical can pin a different one with a reason.
The question: does that match how Clerical would choose by hand? Reply "keep", or say which order should win when more than one is open.
More detail, since you asked.
In VISUAL one project often has several open customer orders at once (for example a first order for two units and a later add-on order). The packet header shows one customer, PO number and due date, so Packet Station has to pick one order per packet.
How it picks today, in this order:
1. If Clerical pinned an order on the project page, that one.
2. Else the customer order VISUAL links to the packet's own work order.
3. Else the project order whose line lists this unit as its top job.
4. Else the project's first open order, else its newest.
The project page lists every open order and shows which rule picked it, and Clerical can pin a different one with a reason.
The question: does that match how Clerical would choose by hand? Reply "keep", or say which order should win when more than one is open.
we will need to talk about this more, it needs to be really be based off the shop schedule. that would determine priority and order. it will need to link live to the scheduler so if jobs get moved, push, or pulled up the packets reflect
we will need to talk about this more, it needs to be really be based off the shop schedule. that would determine priority and order. it will need to link live to the scheduler so if jobs get moved, push, or pulled up the packets reflect
Understood, we will talk it through. Until then the rule stays as built. Recorded in docs/PLAN.md Q5 (PR 53).
To prepare for that conversation: by "the shop schedule", do you mean the schedule in VISUAL (the scheduling window and the operation start and finish dates the planners set), or a separate schedule kept outside VISUAL? Packet Station already reads VISUAL every few minutes, so a VISUAL schedule change would show up on the packets within one feed run. Packet Station can only read the schedule; it never writes to VISUAL.
Understood, we will talk it through. Until then the rule stays as built. Recorded in docs/PLAN.md Q5 (PR 53).
To prepare for that conversation: by "the shop schedule", do you mean the schedule in VISUAL (the scheduling window and the operation start and finish dates the planners set), or a separate schedule kept outside VISUAL? Packet Station already reads VISUAL every few minutes, so a VISUAL schedule change would show up on the packets within one feed run. Packet Station can only read the schedule; it never writes to VISUAL.
it would be Presley's Production Planner. That's what the whole shop operates off of right now. We just need to see what that looks like otherwise the shop has to filter down to what they need to start which is okay and what they do now but not ideal
it would be Presley's Production Planner. That's what the whole shop operates off of right now. We just need to see what that looks like otherwise the shop has to filter down to what they need to start which is okay and what they do now but not ideal
Thanks. A few details about Presley's Production Planner so we can plan the link:
What is it: an Excel workbook, an Access file, a web app, or something else?
Where does it live: a file share path, a server, or a PC?
What does one row hold: a VISUAL work order (base, lot, split, sub), a job or unit number, a department, a start date, a priority?
How often does Presley change it, and is the saved copy always the current one?
Packet Station would only read it, never write to it. With those answers I can say how the boards could follow its order. Until then the order rule stays as built.
Thanks. A few details about Presley's Production Planner so we can plan the link:
1. What is it: an Excel workbook, an Access file, a web app, or something else?
2. Where does it live: a file share path, a server, or a PC?
3. What does one row hold: a VISUAL work order (base, lot, split, sub), a job or unit number, a department, a start date, a priority?
4. How often does Presley change it, and is the saved copy always the current one?
Packet Station would only read it, never write to it. With those answers I can say how the boards could follow its order. Until then the order rule stays as built.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
VISUAL often has several open customer orders on one project. The packet's customer, PO and dates come from one of them.
Built as the default (one function,
feed/orders.py): a Clerical pin, else the base's own linked order, else the project order whose top job is the unit, else the project's first open order, else its newest. The source is stored and shown on the project page, which lists every open order; Clerical can pin another with a reason.To answer: keep, or give a better rule.
Plan reference: Q5 in docs/PLAN.md (open questions). Answer here; the build takes the default until then.
Please provide more information.
More detail, since you asked.
In VISUAL one project often has several open customer orders at once (for example a first order for two units and a later add-on order). The packet header shows one customer, PO number and due date, so Packet Station has to pick one order per packet.
How it picks today, in this order:
The project page lists every open order and shows which rule picked it, and Clerical can pin a different one with a reason.
The question: does that match how Clerical would choose by hand? Reply "keep", or say which order should win when more than one is open.
we will need to talk about this more, it needs to be really be based off the shop schedule. that would determine priority and order. it will need to link live to the scheduler so if jobs get moved, push, or pulled up the packets reflect
Understood, we will talk it through. Until then the rule stays as built. Recorded in docs/PLAN.md Q5 (PR 53).
To prepare for that conversation: by "the shop schedule", do you mean the schedule in VISUAL (the scheduling window and the operation start and finish dates the planners set), or a separate schedule kept outside VISUAL? Packet Station already reads VISUAL every few minutes, so a VISUAL schedule change would show up on the packets within one feed run. Packet Station can only read the schedule; it never writes to VISUAL.
it would be Presley's Production Planner. That's what the whole shop operates off of right now. We just need to see what that looks like otherwise the shop has to filter down to what they need to start which is okay and what they do now but not ideal
Thanks. A few details about Presley's Production Planner so we can plan the link:
Packet Station would only read it, never write to it. With those answers I can say how the boards could follow its order. Until then the order rule stays as built.
right now it is an excel spread sheet, we are developing a system to interface that and some others that would likely be linked to this later on