E
I'm looking to this group for some feedback on what is typical across the industry. I realize that there is no standard, but any feedback would be great.
A typical custom control system might be created from PLCs, PC software, databases, and operator interface software. Often these control systems, or parts of the system, are contracted out to various integrators. Like any product the integrator supplies a quote, the software is ordered, and once it is installed the bill is paid. I'm looking for how service on the software is handled. What is billable and what is covered by some kind of warranty, and for what time period? (I don't mean changes to the software due to the customer changing the process or adding requirements.)
I'm interested in feedback from both integrators and end users on a few
points:
1. How is initial simulation/acceptance handled? Is it the responsibility of the customer, the integrator, or both together? 2. What is done about errors in writing the code that are not discovered during checkout and acceptance? Not logic errors in this case but things like the wrong PLC address entered into a tag, or something like that. 3. How are logic errors handled, such as a special case not being handled correctly? This isn't a syntax error as much as the system was programmed to do the wrong action. 4. How do integrators stand behind their work for problems discovered after the system has been in use for some time?
Thanks for your thoughts.
Ed
Speaking for me, not for Starbucks. . .
A typical custom control system might be created from PLCs, PC software, databases, and operator interface software. Often these control systems, or parts of the system, are contracted out to various integrators. Like any product the integrator supplies a quote, the software is ordered, and once it is installed the bill is paid. I'm looking for how service on the software is handled. What is billable and what is covered by some kind of warranty, and for what time period? (I don't mean changes to the software due to the customer changing the process or adding requirements.)
I'm interested in feedback from both integrators and end users on a few
points:
1. How is initial simulation/acceptance handled? Is it the responsibility of the customer, the integrator, or both together? 2. What is done about errors in writing the code that are not discovered during checkout and acceptance? Not logic errors in this case but things like the wrong PLC address entered into a tag, or something like that. 3. How are logic errors handled, such as a special case not being handled correctly? This isn't a syntax error as much as the system was programmed to do the wrong action. 4. How do integrators stand behind their work for problems discovered after the system has been in use for some time?
Thanks for your thoughts.
Ed
Speaking for me, not for Starbucks. . .