IEC 62960:2020 pdf download – Dependability reviews during the life cyc.
Dependability reviews comprise a coherent set of reviews for different aspects of dependability. These reviews are performed repeatedly throughout the life cycle, continually providing follow- up actions and assessment of their effectiveness. Dependability reviews can be performed from various perspectives, such as: – the dependability attributes of an item including reliability, maintainability, supportability and availability; – other time related characteristics of an item such as durability and recoverability; – dependability related functions such as safety and security; – cost efficiency, including both life cycle cost and the short term cost; – activities carried out to achieve or assess dependability outcomes; – effectiveness of dependability processes; – accountability of, and to, various stakeholders for potential failures; – adaptation to changes in requirements, environments, objectives and/or purpose of the system. A dependability review provides assurance that dependability is achieved throughout the life cycle either by demonstrating that requirements are met or by identifying problems and making improvements. A dependability review can be used to provide evidence that a dependability claim is satisfied as part of a dependability case (IEC 62741 [3] 1 gives guidance on the content of a dependability case and establishes general principles for its preparation). Systematic dependability reviews across the system life cycle enable agile corrective redirection of effort with less waste. This is particularly beneficial given the current trends for increasing system complexity, tightening development time and prolonged operational life. Some environments or conditions for the trends include: – ubiquitous network connection to any range of systems controlled by others; – frequent changes in the system’s context such as user expectation and competitions in the market; – inability to discard the old and start anew due to, for example cost consideration and preferences for “circular economy”.
4.2 Technical reviews Technical reviews identify and analyse potential problems and opportunities, and recommend actions for improvement. They also provide assurance that processes are operating effectively and requirements are met. Technical reviews can include design reviews, operation reviews, maintenance reviews, risk reviews or reviews of other technical aspects of an item or process. They may focus on dependability or dependability may be considered as part of a wider performance review. Technical reviews of dependability can involve: – reviews of the achieved or predicted dependability of an item where the objective is to improve dependability of the item itself by evaluating dependability measures and by exploring opportunities for improvement; – reviews of the processes and activities planned to achieve dependability in order to learn lessons and improve future processes and activities. Participants should have a technical understanding of the system under review and of the reliability, maintenance and supportability disciplines. The participants should include experts who are independent from the design of the system and have necessary skills to analyse how items, systems and processes could fail. Participation of such experts is most important for securing independence and quality of the review. Participants might include, for example, quality professionals, reliability professionals, ergonomics professionals, safety analysts and test personnel. Management should normally not participate in a technical review. The customer or user of the system or process may participate in a technical review. Each technical review should designate a chair of the meeting (the facilitator), who can assign a secretary to assist the review.
4.4.2 Identifying stakeholders It is important for persons or organizations developing and operating systems to clearly recognize who their stakeholders are, since their ultimate aim is to satisfy the needs of these stakeholders. Stakeholders should therefore be identified and means of communication with them established. For some systems, it is relatively easy to identify stakeholders and they do not change through the lifecycle. For other systems, it may be difficult to identify all stakeholders at the outset and to fully determine their needs. For example stakeholders may change when a system enters the utilization stage or when a developed item is sold to a different person or organization. They can also change when a system enters the retirement stage.