AADvance Safety Manual - Tuv-fs.com

AADvance Safety ManualMonitoringTo ensure that the safety objectives are met through the lifetime of the system it isimportant to maintain records of all faults, failures and anomalies as they occur. Thisrequires the maintenance of records by both the end-user and the System Integrator. Itis highly recommended the following information is included: Description of the fault, failure or anomaly Details of the equipment involved, including module types and serial numberswhere appropriate When the fault was experienced and any circumstances leading to its occurrence Any temporary measures implemented to correct or work around the problem Description of the resolution of the problem and reference to remedial actionplans and impact analysisYou should define the procedure for field returns, and repair and defect handling. Theinformation requirements placed on the end user because of this procedure should beclearly documented and provided to the end user. The defect handling procedure shallinclude: Method of detecting product related defects and the reporting of these to theoriginal designers Methods for detecting systematic failure that may affect other elements of thesystem or other systems, and links to the satisfactory resolution of the issues Procedures for tracking all reported anomalies, their work around and resultantcorrective action where applicableMaintaining Functional Safety After System ModificationDesign changes will inevitably occur during the system life-cycle; to ensure that thesystem safety is maintained, such changes shall be carefully managed. Proceduresdefining the measures for updating the plant or system shall be defined anddocumented. These procedures are the responsibility of the end user, but the systemintegrator shall provide sufficient guidance to so that the procedures maintain therequired level of functional safety during and after the changes.Product Level Module and Firmware UpdatesSpecial consideration shall be given to procedures for product level module andfirmware updates.Updates to the system shall include the modification requirements for applicationchanges and firmware changes.The procedures shall include the need to undertake impact analysis of any suchchanges, and the measures to change the system and its application programs as aresult of the the modification requirements.Specifically, the additional requirements defined here shall be applied, as well as therequirements defined for the following items:3-8 Document number 553630 Issue 7: February 2010