IANAL - thank God for that.... I detest the dopey bastids...Of course, I keep one on retainer, it's a lot like keeping a sewage system maintenance contract... U hardly ever need one, but when you do....
Actually JB, your voice is one of the stronger advisories here, and I take what you say fairly seriously.
flth01 wrote:I'd sure like to see a thread started that covers applying for and abiding by the rules of the permit. Especially the rules regarding the reports, they seem to be a little vague in the report requirements for an auditor and I'd hate to find out I'm not following protocol in the middle of a visit.
Heya flth01 - I've written process/procedures for a number of years for large datacenters, and these must all meet something called an ITIL standard, and carry strict auditing guidelines.
The basic premise in any process (and subsequent audit) is to record everything pertinent about a process.. start to finish, no single step left undocumented or recorded.. After all, an
audit is meant to ensure the rules of a process and procedure have been followed in actual deployment. In my world, that means using best practices for configuration, and operational processes to ensure the computing resources are always available and changes are delivered w/o breaking things. And believe me, computer jocks can break thinkgs you'd never expect...
In this context, I take that to mean, exact recording of each batch, from grain weights, water (source, ph levels), fermentation factors (how the mash was made), distilling factors, and dispostion of the output product and how it was used/disposed of, etc..
However, Bayou has gotten his, and probably can speak more clearly to what is expected. I tend to produce too much white paper information, and almost always end up trimin' it down.. but at corporate, too much is always better than not enough when it comes to auditing. I try to answer questions before they get asked, but I am not always perfect, and my perceptions tend to follow a scientists view, and not an auditors....
