Question:
Hi QM Gurus,
I'm in 46C. I save defects in production.
The QM department change something in the work center.
I need to save this change (with date and time) to verify if after this change I find more defects or less defects.
What I can use to do this?
Thanks in advance
Odl
Answer:
Any suggestion?
Thanks
Odl
Answer:
When you say "change something in the workcenter"... do you mean in the master data for the workcenter?
I'm not really clear here..
Craig
_________________
Available for spot consulting, troubleshooting, remote configuration/consulting and teaching. 10+ yrs in QM. Primary focus on Pharma and Chemicals.
Answer:
Craig,
I didn't explain very well.
I try to explain better: when I say "change something in the work center" it means that nothing change in master data for the work center but physically they change a process parameter (temperature, pressure ...) or they change a component of the work center (engine, piston...) to try if they have a little number of defects.
I need to save data about these changes with date and time of start, I also need to seve these data in only one place (as a sort of solution for problems).
Thanks in advance
Odl
Answer:
Ok.. those sound very much like process control values. Have you considered using free inspection points with the various things that can be changed? You record the process settings in the 03 inspection lot much like you would a test result. Make the recording optional. The only record what they need to. Since the operations are tied to the workcenter you know what was changed for what. You also have time stamps of then the value was recorded.
You could use PI sheets as well and inlclude the link to record the values right on the PI sheet.
Craig
_________________
Available for spot consulting, troubleshooting, remote configuration/consulting and teaching. 10+ yrs in QM. Primary focus on Pharma and Chemicals.
Answer:
Thanks Craig,
the problem is that I don't know previously what are the various things can be changed (I think you said I must create an inspection point for each thing can be changed)
What about solutions database?
Odl
Answer:
What do you mean you don't know what can be changed? Any process should have a finite number of things that can be changed.
Ok.. if you really don't know what can be changed, and you really only need it for documentation, you could try the following.
Use free inspection points. In the inspection point identifers use the 18 character field. Create a label for this of maybe "Process Control ID:". Also make sure the date and time field are set up.
The user creates the inspection point, enters in the identifier or name of the control being changed. The date and time field are defaulted in by the system. So the inspection point name might now look something like:
Drum Dryer #5 temperature/04-APR-2004/23:24:32.
For the tests, create two characteristics. A quantitative test. The UOM is "No UOM". (add this to your UOM if you don't have something like it).
The limts on this are set wide... -9999999999 to 9999999999. Or something like that.
Create a second qualitative test. Create a selected set that contains all the common UOM's you might need to use in your production enivornment. I.e. Deg. C, Deg. F, lbs, ft. lbs, torque, etc...
So the operator would create the inspection point, identifying the process control being modified. They then enter in the new value for the control in the first characteristic and select the UOM from the second qualitative characteristic.
You could actually create two quantitative characteristics. "Previous setting" and "New setting". Also, alternatively, if you don't want to create the qualitative characteristic to hold the UOM, the operator could type in the UOM in the inspection description field of the quantitative characterisitic(s)
Hope this helps.
Craig
_________________
Available for spot consulting, troubleshooting, remote configuration/consulting and teaching. 10+ yrs in QM. Primary focus on Pharma and Chemicals.
Answer:
Craig,
thanks for spending your time,
when I write I don't know what are the things that can be changed I mean that there are several parameters that technician can change.
Another problem is that the user doesn't insert the inspection point when the change is made but some hours later
I was thinking about solutitions database but today looking for a new solution I thought I can use items for notification:
when I save a defect I've also a notification for inspection type 03.
When the change is made I can use QM02 and insert an item with starting date and time: so in this case I've the change linked with the production order and I've a starting date and time.
I think this is a good solution for us because what we do it's a change after we find some defects and we try to solve this problem: it's a kind of item (change) after a defects.
What do you think about?
The only problem (but I think will solve with my ABAPER) is that I'm doing a query and what I need is to find a column with the item code for all the defects saved after the starting date and befor the ending date of the item (but in this case the item is linked to a quality notification so I think I will use a program and not a query).
Thanks a lot
Odl
Answer:
Ok.. sounds like you have workable idea there. Defects recording only for the 03 inspection lot. The only problem I might see there is that it might be hard to search for items, as you would have to enter what is being changed and what it is changed from and to as free text.
Now if your process people can narrow down the various choices, these could all be put in catalogs and would make searching and statistics easier. Of course the actual value would still need to be enterred as text.
But from your description of the problem, you don't know all the variables so I would guess your stuck with free text.
But your notification would be linked to the process order.
BTW: in the sceanrio I proposed to you, the date and time for the inspection point will default in BUT it can be changed by the operator to any value at time of creation or even later. So if the data-entry doesn't happen right away, it's ok, your not limited.
Craig
_________________
Available for spot consulting, troubleshooting, remote configuration/consulting and teaching. 10+ yrs in QM. Primary focus on Pharma and Chemicals.
Answer:
Got an idea. Why not use QN Activities instead of the Item itself?
That way you can create Catalogs specific to changes in Work Center settings -- since you define the codes you can make them as specific as possible and leave some available that are very general.
Also, your Activity data will be written not to QMFE but instead to table QMMA. QMMA doesnt have Work Center but I presume that is in your QN and QMMA certainly points back to the QN. Plus you will not cause QMFE to store a miz of problems and these actions taken to change the process.
In the Plant Maintenance world, Activities are sometimes/often used to record those actions taken that were not planned in advance. That sounds like a possible match to your situation.
Good luck,
Warren