SoftwareJanitor
Member
We are still in the process of deciding whether we will be using PlantPax (Large Pharma system here) or another solution.
The problem I have with these claims of being able to 'put your systems together more quickly with AOI's' etc.) is - I see that as an advantage for the *integrator*, and maybe a drawback for me (the ultimate *owner* of the system).
I don't care how *quickly* the system can be put together as much as I care about how *cleanly* it's put together. I don't want a lot of "baggage" logic in my final system, and that's what I fear will happen with these one-size-fits-all generic AOI's that allow the software to be slapped together more quickly.
I see people here talking about CPU loading with PlantPax, which makes me believe even more that these solutions contain unnecessary overhead logic - which is what you'd expect. If you can build it quickly, it's probably not going to be very efficient (or clean)...
The problem I have with these claims of being able to 'put your systems together more quickly with AOI's' etc.) is - I see that as an advantage for the *integrator*, and maybe a drawback for me (the ultimate *owner* of the system).
I don't care how *quickly* the system can be put together as much as I care about how *cleanly* it's put together. I don't want a lot of "baggage" logic in my final system, and that's what I fear will happen with these one-size-fits-all generic AOI's that allow the software to be slapped together more quickly.
I see people here talking about CPU loading with PlantPax, which makes me believe even more that these solutions contain unnecessary overhead logic - which is what you'd expect. If you can build it quickly, it's probably not going to be very efficient (or clean)...