IEC 62061:2012 pdf free download

IEC 62061:2012 pdf free download
IEC 62061:2012 pdf free download.Safety of machinery – Functional safety of safety-related electrical, electronic and programmable electronic control systems
3.2.46 application software
software specific to the application, that is implemented by the designer of the SRECS,generally containing logic sequences, limits and expressions that control the appropriate input, output, calculations, and decisions necessary to meet the SRECS functional requirements
3.2.47 embedded software
software, supplied by the manufacturer, that is part of the SRECS and that is not normally accessible for modification
NOTE Firmware and system software are examples of embedded software.
3.2.48 Full Variability Language
FVL
type of language that provides the capability to implement a wide variety of functions and applications [IEC 61 51 1 -1 , 3.2.81 .1 .3 modified]
NOTE 1 Typical example of systems using FVL are general-purpose computers.
NOTE 2 FVL is normally found in embedded software and is rarely used in application software.
NOTE 3 FVL examples include: Ada, C, Pascal, Instruction List, assembler languages, C++, Java, SQL.
3.2.49 Limited Variability Language
LVL
type of language that provides the capability to combine predefined, application specific,library functions to implement the safety requirements specifications[IEC 61 51 1 -1 , 3.2.81 .1 .2 modified]
NOTE 1 A LVL provides a close functional correspondence with the functions required to achieve the application.
NOTE 2 Typical examples of LVL are given in IEC 61 1 31 -3. They include ladder diagram, function block diagram and sequential function chart. Instruction lists and structured text are not considered to be LVL.
NOTE 3 Typical example of systems using LVL: Programmable Logic Controller (PLC) configured for machine control.
3.2.50 safety-related software
software that is used to implement safety-related control functions in a safety-related system
3.2.51 verification
confirmation by examination (e.g. tests, analysis) that the SRECS, its subsystems or subsystem elements meet the requirements set by the relevant specification [IEC 61 508-4, 3.8.1 modified and IEC 61 51 1 -1 , 3.2.92 modified]
NOTE The verification results should provide documented objective evidence.
EXAMPLE: Verification activities include:
– reviews on outputs (documents from all phases) to ensure compliance with the objectives and requirements of the phase, taking into account the specific inputs to that phase;
– design reviews;
– tests performed on the designed products to ensure that they perform according to their specification;
– integration tests performed where different parts of a system are put together in a step-by-step manner and by the performance of environmental tests to ensure that all the parts work together in the specified manner.