Awesome! Going back to San Antonio.... when I was working there, I worked a technology implementation that had to be done at night. It was during the Fiesta time - so just as everyone went to party, we had to get to work. I slept like three hours a day so I could walk the Riverwalk during the day and photograph. So, as long as you could handle that 3 am - 7 am time slot - good for you.
Colorful!
I think there should be a slap upside the head penalty for that.
I agree, though I'm surprised you were able to tell, since you're doing your KMA wrong. I know because I study JMA.
I am an expert in FMEA. Does that count?
What's fmea?
Failure mode and effects analysis
Interesting, we recently failed the PPAT on a startup because our customer's customer FMEA fell out of tolerance. Ever heard of that one?
It can happen. FMEA also provides ideas as to how you might want to structure your SIT and UAT. At least I've used it a lot for that purpose. It's a pain in the neck to put together a really comprehensive FMEA, but it's worth it.
The issue we are having is FMEA does not apply to what we do. We design/build/program based on a written spec and standards if they apply. The end user creates their own FMEA. If the product is out of spec, then the specifications we built to were out of spec. It has happened before where somewhere in the chain either the product changed and we were not notified or a change order did not get processed. Even more frustrating when there are approvals based on project milestones. Life on the hamster wheel.
Ah! Yeah... that doesn't work very well. FMEA should be created in collaboration between the user and the programmer. That way, everyone who knows what might not work and what trouble it might cause is involved.
