I had an interesting conversation with my colleague recently. We were talking about different use of O-QIS modules and what are the advantages. When we talked about MCA/CMM Reporting, he asked a question that nobody really ask at first:
After O-QIS process the DFQ file, is it possible that it’s picked up by different O-QIS?
I was so happy with that question. What a proud moment it was. Somebody is directly thinking about different control loops. Huray.
Of course, that is possible. It’s called cascaded use of O-QIS CMM reporting. Typical example can be this:
- Part is produced in production.
- Part is measured in measurement room on CMM, and the DFQ file with results is exported.
- Operators control the results in O-QIS CMM reporting, accept the measurement, the DFQ file is exported and send to different location.
- DFQ file is picked up by O-QIS next to production machine in order to inform the responsible person about the state of the production immediately. Responsible person accept the measurement.
- Data are saved in the central database.
You see, there are more people than the operator in measurement room, who should take care about the results of the measurement. Thats why it is a good idea to create multiple control loops for all kinds of processes. If you haven’t considered it yet, make yourself a favour and think about it today. A little example can be seen in the documentation series "Dataflow concept". Link is below.