12.07.2015 Views

IEC 61508 Functional Safety Assessment Rosemount Inc. - Exida

IEC 61508 Functional Safety Assessment Rosemount Inc. - Exida

IEC 61508 Functional Safety Assessment Rosemount Inc. - Exida

SHOW MORE
SHOW LESS
  • No tags were found...

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

These results must be considered in combination with PFD AVG values of other devices of a <strong>Safety</strong>Instrumented Function (SIF) in order to determine suitability for a specific <strong>Safety</strong> Integrity Level(SIL). It is the responsibility of the <strong>Safety</strong> Instrumented Function designer to do calculations for theentire SIF. exida recommends the accurate Markov based exSILentia tool for this purpose.The analysis shows that design of the 3051 C/T/L Pressure Transmitter meets the hardwarerequirements of <strong>IEC</strong> <strong>61508</strong>, SIL 2 @HFT=0 and SIL 3 @ HFT=1.5.3 Opportunities for improvementDuring the course of the assessment, there were a number of cases found where there was eithera minor non-conformance or a recommended update to the development process identified. In allof these cases the issues identified were deemed not to have a significant effect on the overallfunctional safety of the product. Therefore, these items can be considered recommendations toreduce the risk of non-compliance for future development efforts or modifications. The items foundare described below: Test environment, tools, configuration and programs used should be included in futureintegration test plansThe integration plan shall consider details of those who shall carry out the integration. Thisinformation could also be included in another document such as the roles andresponsibilities document. Update the coding standard to include a requirement for structured programming. Thisinvolves using structured constructs such as sequences (case), iterations (for, while, do)and selection (if/then/else) to control program flow and to avoid unstructured constructssuch as goto and longjmp. Update coding standard to state that if dynamic objects are used, checking must beincluded to determine if the allocation succeeded and if not, to take appropriate action.Coding standard or other document should state that interrupts should only be used if theysimplify the design.Unit test plan should indicate that input equivalence class and boundary value techniquesare used. Recommend adding to source code standard the following: Complex calculations areavoided as the basis of branching and loop decisions.The analysis made and the decisions taken on whether to continue the integration test orissue a change request, in the case when discrepancies occur should be documented in theintegration test results.© exida Certification rosemount 11-07-062 r007 v1 r1 iec <strong>61508</strong> assessment.docx, 3/8/2012Michael Medoff Page 19 of 21

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!