{"id":35619,"date":"2015-05-05T07:52:56","date_gmt":"2015-05-05T04:52:56","guid":{"rendered":"https:\/\/smartlogic.co.il\/?p=35619"},"modified":"2015-05-05T07:52:56","modified_gmt":"2015-05-05T04:52:56","slug":"%d7%95%d7%9c%d7%99%d7%93%d7%a6%d7%99%d7%94-gamp-hardware-software-test-environments%d7%95%d7%9c%d7%99%d7%93%d7%a6%d7%99%d7%94-gamp-hardware-software-test-environments","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-gamp-hardware-software-test-environments%d7%95%d7%9c%d7%99%d7%93%d7%a6%d7%99%d7%94-gamp-hardware-software-test-environments\/","title":{"rendered":"\u05d5\u05dc\u05d9\u05d3\u05e6\u05d9\u05d4 – GAMP – Hardware & Software Test Environments"},"content":{"rendered":"

\u05d5\u05dc\u05d9\u05d3\u05e6\u05d9\u05d4<\/a>\u00a0– \u00a0GAMP – Hardware & Software \u00a0Test Environments<\/a><\/h2>\n

Good Automated Manufacturing Practice (GAMP)\u00a0Hardware (HW) Environment Test<\/h3>\n

HW can be categorized according to both GAMP 4 HW category (standard or custom) and its function within the test environment<\/a>. It can\u00a0be one o f these three things<\/p>\n

\u00a0Part of the system under test, i.e., part of the production HW<\/p>\n

\u00a0Test HW representing part of the production environment, which may be needed because it is not feasible to include a certain element of the production\u00a0system in the test environment<\/p>\n

A separate test system, which may be used to represent an external system<\/p>\n

\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 Representative Test Environment<\/strong><\/h3>\n

As started previously, the HW environment should represent as close as possible the production environment<\/p>\n

For example, if the test environment uses a standard network hub of the same type as the production environment, then the substitution probable introduces low probability if invalid test results in the production environment. If, however, the network cabling in the test environment is uses short patch cables, whilst the real environment has cable runs close to the maximum recommended length, there is clearly a possibility of different network behavior, and additional tests on site may be needed to prove proper network performance<\/p>\n

\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 Control of Test Environment<\/h3>\n

For standard HW (per GAMP 4 HW Category 1), the manufacturer's reference and serial numbers should be recorded.<\/p>\n

For custom HW (per GAMP 4 HW Category 2), the version of the item and its controlling specification should also be recorded.<\/p>\n

For all test HW, any applicable calibration status should be recorded in the context of the specific<\/p>\n

\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0Removal from Production Environment<\/h3>\n

If the test HW is added in the way that it may appear in the production environment, then, this should be documented a temporary modification to the production system. Removal of the temporary modification should be documented as well<\/p>\n

Good Automated Manufacturing Practice (GAMP) \u00a0Software (SW)\u00a0Environment Test<\/h3>\n

Test SW can also be categorized according to both GAMP 4 SW category and its function within the test environment:<\/p>\n

Part of the system under test, i.e., part of the production HW<\/p>\n

Test SW representing part of the production environment<\/p>\n

A separate test system<\/p>\n

\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 Representative Test Environment<\/h3>\n

The SW environment should represent as close as possible the production environment<\/p>\n

For example, if the test environment uses a process controller of the same type as the production environment, then the substitution probable introduces low probability if invalid test results in the production environment. If, however, a particular interface is simulated in the test environment, a possibility remains that different timing factors or process dynamics could affect the operation in the production environment, and additional tests on the production interface may be appropriate<\/p>\n

\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 Control of Test Environment<\/h3>\n

For standard SW (per GAMP 4 SW Category 1, 2 or 3), the manufacturer's reference and version numbers (including installed patch cables) should be recorded. Any configuration or setup parameters should be controlled<\/p>\n

For configured or custom SW (per GAMP 4 SW Category 4 or 5), the item should be placed under configuration management and the version in use recorded<\/p>\n

\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 Removal from Production Environment<\/h3>\n

If the test SW is added in the way that it may appear in the production environment, then, this should be documented a temporary modification to the production system. Removal of the temporary modification should be documented as well<\/p>\n

\u05d5\u05dc\u05d9\u05d3\u05e6\u05d9\u05d4<\/a>\u00a0– \u00a0GAMP – Hardware & Software \u00a0Test Environments<\/a><\/p>\n