BS EN 16590-3:2014
$198.66
Tractors and machinery for agriculture and forestry. Safety-related parts of control systems – Series development, hardware and software
| Published By | Publication Date | Number of Pages |
| BSI | 2014 | 68 |
This part of EN 16590 provides general principles for the series development, hardware and software of safety-related parts of control systems (SRP/CS) on tractors used in agriculture and forestry, and on selfpropelled ride-on machines and mounted, semi-mounted and trailed machines used in agriculture. It can also be applied to municipal equipment (e.g. street-sweeping machines). It specifies the characteristics and categories required of SRP/CS for carrying out their safety functions.
This part of EN 16590 is applicable to the safety-related parts of electrical/electronic/programmable electronic systems (E/E/PES), as these relate to mechatronic systems. It does not specify which safety functions, categories or performance levels are to be used for particular machines.
Machine specific standards (type-C standards) can identify performance levels and/or categories or they should be determined by the manufacturer of the machine based on risk assessment.
It is not applicable to non-E/E/PES systems (e.g. hydraulic, mechanic or pneumatic).
PDF Catalog
| PDF Pages | PDF Title |
|---|---|
| 9 | 1 Scope 2 Normative references 3 Terms and definitions 4 Abbreviated terms |
| 10 | 5 System design 5.1 Objectives 5.2 General |
| 11 | 5.3 Prerequisites 5.4 Requirements 5.4.1 Structuring safety requirements |
| 12 | 5.4.2 Functional safety concept 5.4.2.1 General requirements of functional safety concept |
| 13 | 5.4.2.2 Specification of the functional safety concept 5.4.3 Technical safety concept 5.4.3.1 General requirements of technical safety concept |
| 14 | 5.4.3.2 Specification of the technical safety concept |
| 15 | 6 Hardware 6.1 Objectives 6.2 General |
| 16 | 6.3 Prerequisites 6.4 Requirements |
| 17 | 6.5 Hardware categories |
| 18 | 6.6 Work products 7 Software 7.1 Software development planning 7.1.1 Objectives |
| 19 | 7.1.2 General 7.1.3 Prerequisites 7.1.4 Requirements 7.1.4.1 Phase determination 7.1.4.2 Process flexibility 7.1.4.3 Process timetable |
| 20 | 7.1.4.4 Applicability 7.1.4.5 Supporting processes 7.1.4.6 Phases of software development |
| 21 | 7.1.4.7 Using the tables |
| 22 | 7.1.5 Work products 7.2 Software safety requirements specification 7.2.1 Objectives 7.2.2 General 7.2.3 Prerequisites |
| 23 | 7.2.4 Requirements 7.2.4.1 Software safety requirements specification methods |
| 25 | 7.2.4.2 Non-safety–related functions 7.2.4.3 Level of detail 7.2.4.4 Consistency 7.2.4.5 Hardware and software co-dependency 7.2.4.6 Software safety requirements specification |
| 26 | 7.2.4.7 Software safety requirements verification 7.2.5 Work products 7.3 Software architecture and design 7.3.1 Objectives 7.3.2 General 7.3.3 Prerequisites 7.3.4 Requirements 7.3.4.1 Software architecture and design methods |
| 27 | 7.3.4.2 Design method characteristics |
| 28 | 7.3.4.3 Software architecture structure 7.3.4.4 Level of detail 7.3.4.5 Software architecture traceability 7.3.4.6 Software architecture verification 7.3.4.7 Combination of safety-related software components |
| 29 | 7.3.5 Work products 7.4 Software module design and implementation 7.4.1 Objectives 7.4.2 General 7.4.3 Prerequisites 7.4.4 Requirements 7.4.4.1 Software module design and implementation methods |
| 37 | 7.4.4.2 Software module design and coding verification |
| 38 | 7.4.5 Work products 7.5 Software module testing 7.5.1 Objectives 7.5.2 General 7.5.3 Prerequisites 7.5.4 Requirements 7.5.4.1 Software module testing methods |
| 46 | 7.5.5 Work products 7.6 Software integration and testing 7.6.1 Objectives 7.6.2 General |
| 47 | 7.6.3 Prerequisites 7.6.4 Requirements 7.6.4.1 Software integration and test plan 7.6.4.2 Software integration strategy 7.6.4.3 Software integration and test procedures 7.6.4.4 Software integration and test methods |
| 48 | 7.6.4.5 Elimination of defects 7.6.5 Work products |
| 49 | 7.7 Software safety validation 7.7.1 Objectives 7.7.2 General 7.7.3 Prerequisites 7.7.4 Requirements 7.7.4.1 Software safety validation methods |
| 50 | 7.7.4.2 Extent of tests 7.7.4.3 Software safety requirements validation |
| 51 | 7.7.4.4 Documentation 7.7.4.5 Elimination of defects 7.7.5 Work products 7.8 Software-based parameterisation 7.8.1 Objective 7.8.2 General 7.8.3 Prerequisites |
| 52 | 7.8.4 Requirements 7.8.4.1 Data integrity 7.8.4.2 Executable code in parameter data 7.8.4.3 Configuration management 7.8.4.4 Software-based parameterisation verification 7.8.5 Work products |
| 54 | Annex A (informative)Example of agenda for assessment of functional safety at AgPL = e A.1 Functions of system A.2 Hardware A.3 Safety concept A.4 Safety analysis and safety data A.5 Safety design process for phases of life cycle |
| 55 | A.6 Software development A.7 Verification and testing A.8 Documentation and safety documentation A.9 Summary and assessment |
| 56 | Annex B (informative)Independence by software partitioning B.1 General B.2 Terms, definitions and abbreviated terms |
| 58 | B.3 Objectives |
| 59 | B.4 General B.5 Requirements B.5.1 General requirements B.5.1.1 SRL B.5.1.2 Software architecture B.5.2 Several partitions within a single microcontroller B.5.2.1 General |
| 60 | B.5.2.2 Software partitioning methods/measures B.5.2.3 Software partitioning effectiveness |
| 62 | B.5.3 Several partitions within the scope of a microcontroller network B.5.3.1 General |
| 63 | B.5.3.2 Methods for multi-processor partitioning B.5.3.3 Multi-processor partitioning effectiveness |
| 65 | Annex ZA (informative)Relationship between this European Standard and the Essential Requirements of EU Machinery Directive 2006/42/EC |
