Seth Dostaler SethD
  • Joined on 2026-07-28
SethD commented on issue spencerm/PacketStation#4 2026-10-26 15:45:11 +00:00
Which customer order a packet shows when a project has several open orders

Please provide more information.

SethD commented on issue spencerm/PacketStation#6 2026-10-26 15:44:09 +00:00
Policy tightenings against the old build (ten rules to keep or veto)

i think this is good as shown

SethD commented on issue spencerm/PacketStation#7 2026-10-26 15:41:18 +00:00
Retention period for packets, data books and audit (SECURITY.md D6)

I'm pretty sure all data has to be preserved. We will need to figure out where to store all this. M-Files??

SethD commented on issue spencerm/PacketStation#8 2026-10-26 15:38:47 +00:00
Customer-facing data book copy (SECURITY.md D7)

I think for now we can leave the history off. This is something we can look at later implementing or that we can look up the history on our side if there are questions

SethD commented on issue spencerm/PacketStation#9 2026-10-26 15:35:37 +00:00
Same-rev drawing re-release on an in-shop packet: change order or silent swap

swap silently as long as it is the same drawing with no changes

SethD commented on issue spencerm/PacketStation#10 2026-10-26 15:34:58 +00:00
Cancelled (X) work orders in VISUAL: flag only, or remove drafts

i think this is okay. Your discretion

SethD commented on issue spencerm/PacketStation#11 2026-10-26 15:34:03 +00:00
Partspecs, title or folded-operation target changes on an in-shop packet

Please provide more information

SethD commented on issue spencerm/PacketStation#12 2026-10-26 15:11:33 +00:00
Work-order-gone confirmation after 2 runs and the 10 percent suspect-batch guard

your discretion on this

SethD commented on issue spencerm/PacketStation#13 2026-10-26 15:10:52 +00:00
Pause scope on the Feed settings tab

Please provide more information

SethD commented on issue spencerm/PacketStation#14 2026-10-26 15:10:18 +00:00
Who may set the data book date (was anyone, even on a filed packet)

leave as clerical and/or Q.C. only

SethD commented on issue spencerm/PacketStation#15 2026-10-26 15:09:31 +00:00
Undoing signatures: change-order verifications and ITP line signatures

i would say leave as is for now

SethD commented on issue spencerm/PacketStation#16 2026-10-26 15:08:39 +00:00
Warehouse release gate enforced on the server

this we must keep. If we relax, they will start sending parts through without filling the heat map. Warehouse is to fill the heat map on the parts they send.

SethD commented on issue spencerm/PacketStation#17 2026-10-26 15:06:57 +00:00
Hold and short reasons as closed lists

Please provide more information. Do these notes come from visual?

SethD commented on issue spencerm/PacketStation#18 2026-10-26 15:05:43 +00:00
Who may receive a short on a packet the warehouse no longer holds

The department supervisors need to also verify on their side they received it. Warehouse verifies on their end that it came in and was received but the supervisor needs to verify they game the…

SethD commented on issue spencerm/PacketStation#21 2026-10-26 15:03:26 +00:00
Carried marks on routing: computed flag, not copied rows

yes always keep the data on further progression. some drawings call parts weld and weld assembly welds on the same drawing. in this case weld assembly would need to be able to add welds to the…

SethD commented on issue spencerm/PacketStation#22 2026-10-26 15:00:46 +00:00
The old "copy marks to the new sheet" button on a change order

Yes leave as is. if there is a change order, the work must be re verified through the department. There will be situations where the change order may drastically change something that can't just…

SethD commented on issue spencerm/PacketStation#23 2026-10-26 14:58:19 +00:00
Checklist templates: who edits them

It would be nice to have a special page in which these people can edit the needed checklist templates, and they reflect across packets that have not started. If the update across packets completed…

SethD commented on issue spencerm/PacketStation#24 2026-10-26 14:54:15 +00:00
Q.C. reject: minimum reason or a well-formed NCR number

Q.C. can reject whatever needs to be rejected, but, they cannot approve it without a NCR#. A NCR# has to be provided before acceptance of the failed or rejected item. They do also need to write a…

SethD commented on issue spencerm/PacketStation#25 2026-10-26 14:50:53 +00:00
A filed packet does not lock the unit's ITP

If the ITP is not complete, we need to block it from compiling a data book. It will need to be sent back to be completed

SethD commented on issue spencerm/PacketStation#26 2026-10-26 14:49:58 +00:00
Removing an ITP block signature: signer or Admin only, while the ITP is open

This is okay to stay. If something for any reason needs to be changed or updated as for customer fields or previous step remarks, the packet needs to be sent back to those earlier steps or back to…