{"id":35597,"date":"2015-06-15T10:07:14","date_gmt":"2015-06-15T07:07:14","guid":{"rendered":"https:\/\/smartlogic.co.il\/?p=35597"},"modified":"2015-06-15T10:07:14","modified_gmt":"2015-06-15T07:07:14","slug":"%d7%95%d7%9c%d7%99%d7%93%d7%a6%d7%99%d7%94-testing-process-automation-systems","status":"publish","type":"post","link":"https:\/\/smartlogic.co.il\/staging_new\/%d7%95%d7%9c%d7%99%d7%93%d7%a6%d7%99%d7%94-testing-process-automation-systems\/","title":{"rendered":"\u05d5\u05dc\u05d9\u05d3\u05e6\u05d9\u05d4 -Testing Process Automation Systems"},"content":{"rendered":"

\u05d5\u05dc\u05d9\u05d3\u05e6\u05d9\u05d4 –\u00a0Testing Process Automation Systems \u00a0<\/strong><\/a><\/h2>\n

\u00a0Testing Responsibilities \u00a0Supplier and User<\/h2>\n

Where a Supplier has been assessed and its quality management system found to be acceptable, the User may benefit from the testing already carried out as part of the product development life cycle in order to minimize additional testing.<\/p>\n

Similarly, the User may benefit from the testing carried out by the Supplier as part of the application, for example, to allow a small sample of tests to be repeated at witnessed FAT.<\/p>\n

\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 Example of Life Cycle for a Custom Application<\/h3>\n

Supplier Product Life Cycle<\/strong><\/h3>\n

For example in\u00a0a life cycle where a new application is developed for an embedded control system, \u00a0the Supplier's product may be SW<\/a> or tools used to develop the User specific application. The Supplier of the control system has been assessed and its quality management system found to be acceptable. Thus, the User does not need to repeat the testing of product functionality. The testing should instead concentrate on the application of the control system<\/p>\n

\u00a0 \u00a0 \u00a0End User Application Life Cycle<\/h3>\n

Assuming that the application is critical to product quality and includes a custom sequence coded as a sequence function chart, a test approach could be agreed :that includes the following elements<\/p>\n

Supplier's module testing of the sequence function chart program.<\/p>\n

Supplier's integration testing (100% test) and FAT (sampled) to demonstrate correct interaction configuration of the control system and correct operation of the process equipment.<\/p>\n

SAT and IQ<\/a>\/OQ\/PQ of the control system as part of the process equipment.<\/p>\n

\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 Example of Life Cycle for a Standard Application<\/h3>\n

\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0Supplier Product Life Cycle<\/h3>\n

In the case \u00a0of a life cycle where a standard application is purchased containing an embedded control system, the control system<\/a> Supplier has been assessed and its quality management system found to be acceptable. Thus, the User does not need to repeat the testing of product functionality (including mature library functions such as standard control modules) or of the standard application. The testing has to cover only the setup and use of the application.<\/p>\n

\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 End User Application Life Cycle<\/strong><\/h3>\n

Assuming that the application is still critical to product quality, there is now much lower risk associated with the application development, as the configuration is limited to selecting the required functions and entering setup parameters. A test approach could, therefore, be agreed including the following elements:<\/p>\n

FAT to demonstrate correct setup of the control system and correct operation of the process equipment.<\/p>\n

SAT and IQ<\/a>\/OQ\/PQ of the control system as part of the process equipment.<\/p>\n