Doc: ps2001-5-1101-001 Rev: R02. 00
The protecting of software modules
Download 1.5 Mb. View original pdf
|
1486357009-URS, URS
| 4.11.3 The protecting of software modules (1) The Validation Plan (VP, [Ref. 002] risk assessments require that certain modules and types of modules will have protection activated at certain points during the Project usually after formal testing. This protection will use the TIA Portal operation referred to as “write-protect”, it does not affect the content of the module, it simply prevents it from being changed either intentionally or inadvertently. (2) Write-protect will be applied to specific modules at specific point in the Project. The final released (and verified) version of the software will have all the Write-protect restrictions removed. Doc PS Rev R 67-71 5. Constraints 5 Constraints 5.1 Compatibility (1) The software will be written for the S range of Controllers and it will be fully compatible with that range. (2) The software will be largely compatible with the S range of controllers however, it is accepted that the S range has reduced capabilities in comparison to the S range and certain, more complex modules, may not be compatible with the S CPUs. Where a module is not compatible with the S series, this will be clearly noted in the module documentation. 5.2 Maintenance requirements (1) An Operation and Maintenance manual (OM, [Ref. 005] will be provided this will contain the principal operating instructions for the system it will include the manufactures literature and configuration details for all equipment installed within the system (2) The Operating and Maintenance manual will contain sections for faultfinding and repair, routine maintenance and recommended spares holding. 5.3 User skill level (1) All users of the software library shall be competent and familiar with the programming of Siemens Simatic Controllers and the TIA Portal programming environment, this may be by virtue of education, training, or experience. |