I am tracking what we call a Dock Audit. It is a random review of some parts before they are shipped to a customer. We have over 300 part numbers. Basically, this particular part of the app, I want to count occurrences of a part, so that auditors don’t just keep checking the same parts over and over.
So they pick a part (some parts ship in packs, i.e. there are a left hand and a right hand, or going to the same destination. This is the reason why I want the ability to add up to 12 parts in an audit. Generally, there aren’t that many, but there COULD BE), review questions listed in the app for accuracy, quality, etc.
If there is some sort of error, then a supervisor is notified, “hey, there is a problem.” The supervisor reviews the reason for the error, puts something in to place to ensure the problem doesn’t recur, and then signs off. “Problem fixed.” (I am trying to get that to appear in the app too, but that is NOT this question. I only mention it to explain the whole scope of the app.)
In addition, there is a scheduling function. 3 plants. Different parts are made at different plants. So users are notified via email: you have an audit coming up in Plant x next week, or; you are 3 days late on your audit, get your tushy moving.
I hope that helps give the scope. Is it “vital”, my question? No. As it exists, my app is performing as planned. I just thought a count of part numbers checked already helps the next auditor to select different parts so our audits are more thorough across all the parts we make.
David Goscinski, M.Ed