JP5412252B2 - Reliability analysis apparatus and method - Google Patents

Description

  The present invention relates to a reliability analysis apparatus and method, and in particular, has a reliability analysis sheet created based on design information data of a system to be analyzed for reliability, and the reliability analysis sheet This is a reliability analysis device that analyzes the reliability of the system on the basis of the database, taking into account the information in the database for project lifecycle management such as document management and requirements management, traceability over the entire project lifecycle of the analysis basis and analysis target equipment The present invention relates to a reliability analysis apparatus and method capable of establishing

In project management including on-site construction in transportation systems, reliability analysis work is performed to analyze the safety and reliability evaluation of the entire system.
For the reliability analysis work, a reliability analysis sheet such as a failure mode effect and criticality analysis (FMECA) sheet or a hazard log (dangerous event) sheet is used.

  Reliability analysis sheets such as FMECA sheets and Hazard Log sheets are generally created using spreadsheet software.

  FIG. 4 shows an example of an FMECA sheet created using spreadsheet software. The FMECA sheet differs in some items depending on the creator, the field used, the project to be managed, etc., and the FMECA sheet in FIG. 4 is merely an example.

  In FIG. 4, Item Ref. The column describes the ID of the product name subject to FMECA. The Item Name / Functional Identification column describes the name of the item subject to FMECA. The Function column describes the function of the target product. The Functional Failure Mode column describes the state when the target product has failed, that is, the failure mode. The Failure Cause column describes the cause of the failure. The Item Qty / Location column describes the quantity per place. The Failure Rate column describes the failure rate [1 / Hr]. The Subsystem column in Failure Effects describes the effect of the failure on the subsystem. The System column in Failure Effects describes the impact of the failure on the system. The Transit System column in Failure Effects lists the impact of the failure on the associated system. The Operational Safety Class column describes the classification of the severity of harm due to operational failure. The Safety Safety Class column describes the severity classification due to a safety failure. The Failure Mode Ratio column describes the failure mode ratio. The Failure Effect Probability column describes the probability of the failure effect, that is, the probability that the failure effect further leads to the failure. The Operating Time column describes the operation time [Hr]. The Criticality column describes criticality that is a value derived from the result of the failure mode and occurrence probability. The Failure Detection Means column describes failure detection means. The Available Continuity / Compensating Provisions / 1st Line Maintenance column describes applicable alternative / compensation means. The Design Action / Recommendation column describes design measures and recommended measures for preventing failures and their effects. Remarks column describes remarks.

  FIG. 5 shows an example of a Hazard Log sheet created using spreadsheet software. The Hazard Log sheet differs from the FMECA sheet in that some items differ depending on the creator, the field used, the project to be managed, etc., and the Hazard Log sheet in FIG. 5 is merely an example.

  In FIG. 5, the Hazard Identification Number column describes the hazard ID number. The Subsystem column describes the corresponding Subsystem name of the hazard item. The Component / Equipment column describes the component. The Hazard Owner column describes the owner of the hazard. The Operating Mode column describes the operation mode related to the hazard. The Hazard Origin column describes the hazard identification source, the Hazard Description column describes the hazard, and the Hazard Cause column describes the cause of the hazard. The Potential Accident column describes an event such as an accident that can be caused by the hazard, and the Exposed Group column describes a group that is exposed to the hazard, that is, a person who may be involved when the accident occurs. The Frequency (Initial Risk) column describes the initial risk occurrence probability. The Severity (Initial Risk) column describes the severity of the initial risk, and the Initial Risk column describes the initial risk. The Mitigating Measurement 1 to N column describes risk mitigation measures (1, ..., N), the Mitigating Measurement Design Verification 1 to N column describes design verification of risk mitigating measures (1, ..., N), and Mitigating The “Measurement Validation 1 to N” column describes the validity verification (1,..., N) of the risk mitigation measures. The Frequency (Residual Risk) column describes the residual risk occurrence probability, the Severity (Residual Risk) column describes the severity of the residual risk, and the Residual Risk column describes the residual risk. The Risk Assessment column describes the risk assessment, and the Risk Assessment Reference column describes the risk assessment reference source. The Action remaining to close column describes the remaining action schedule. The Hazard Status column describes the hazard status, and the Comments / Remarks column describes comments and remarks. The Safety Critical Item Information column describes safety critical item information, and the Safety Critical Item Identification Number column describes safety critical item ID. The ALARP Information column, the ALARP Demonstration 1 to N column, the ALARP Reference 1 to N column, and the ALARP Demonstrated column are ALARP information, ALARP demonstration (1, ..., N), ALARP reference sources (1, ..., A, N), respectively. Demonstrate completed.

In both the FMECA sheet shown in FIG. 4 and the Hazard Log sheet shown in FIG. 5, there are many input items, and it is necessary to manually input related component information and related document information. There is a possibility that notation and input leakage will occur.
Furthermore, since the design change information associated with the progress of the project that uses the sheet has not been linked since the initial creation of the FMECA sheet or the Hazard Log sheet, the design change is not reflected in the FMECA sheet or the Hazard Log sheet. May occur.

  Therefore, it is conceivable to use a known reliability analysis tool that can hold the device information inside, but the reliability analysis tool is used for document management and requirement management of the device information that is held inside. It does not include the information in the database for project life cycle management, and it cannot be said that the traceability is ensured when the reliability analysis work is repeated due to the design change.

Further, for example, Patent Literature 1 and Patent Literature 2 disclose technologies relating to FMEA sheet and FMECA sheet creation support, which are methods of reliability analysis.
The technology disclosed in Patent Document 1 is intended to realize a product in an FMEA support apparatus that supports FMEA that predicts a possible failure and extracts the influence on the product and the cause of the failure to ensure the reliability of the product. The present invention relates to an FMEA support apparatus including functional model data composed of a function development expressing a function to be performed and a parts list, and FMEA execution means having input means for associating FMEA items with the functional model data. Further, the technique disclosed in Patent Document 2 is a quality improvement system using an FMEA table, which is collected by a defect data collecting unit that collects data on defects in a manufacturing or inspection process, and the defect data collecting unit. FMEA table updating means for updating the FMEA table online based on data, the FMEA table including a failure mode, the number of occurrences thereof, and an effect caused by the failure mode; The FMEA table update unit includes an FMEA table edit management unit that edits and manages the FMEA table, and the FMEA table edit management unit includes the failure mode and the influence that have occurred in advance when the FMEA table is stored in the FMEA table. If the number of occurrences is edited and it is not one of the failure modes and effects that occurred in the FMEA table, It is to edit the FMEA table to add the appropriate fields.

JP 2007-323219 A JP 2008-257700 A

  However, the techniques disclosed in both Patent Document 1 and Patent Document 2 are limited to general input items such as failure modes, functions, parts, etc. with respect to FMEA sheet creation support, such as document management and requirement management. The information in the project life cycle management database is not taken into consideration, and it is not sufficient to ensure traceability when the reliability analysis work is repeated due to design changes.

  Therefore, in view of the problems of the prior art, the present invention can establish traceability over the entire project life cycle of the analysis basis and the analysis target device in consideration of information in the database for project life cycle management such as document management and requirements management. An object of the present invention is to provide a reliability analysis apparatus and method that can be used.

As an apparatus invention for solving the above-described problems, a reliability analysis sheet created based on design information data of a system whose reliability is to be analyzed is provided, and the reliability of the system is determined based on the reliability analysis sheet. In the reliability analysis device that analyzes
A database for managing changes in the design information;
The reliability analysis sheet can acquire changes in design information managed by the database by associating each stored data with one or more databases among a plurality of databases corresponding to the data. And the databases are a plurality of databases that manage changes in different design information,
The plurality of databases include a document management database for managing documents related to the design information of the system, a requirements management database for confirming conformity of requirements related to the design of the system, and a life constituting data for life cycle management of the requirements management database. By including a cycle database, it is characterized by reliably establishing traceability throughout the project life cycle .
The database is a plurality of databases that manage changes in different design information, and the reliability analysis sheet includes one or more of the data held therein and the plurality of databases corresponding to the data. It is good to be associated with the database.

The reliability analysis sheet is associated with a database that manages the change of the design information, and the design information managed by the database is acquired and updated. Even if the information is updated, it is possible to perform the reliability analysis using the reliability analysis sheet again with the latest design information.
As a result, the analysis basis and analysis target device on the reliability analysis sheet can be implemented in accordance with the change of the design information, and traceability over the entire project life cycle can be established.

The plurality of databases include a document management database for managing documents related to the design information of the system and a requirements management database for confirming conformity of requirements related to the design of the system.
The document management database and the requirement management database are elements constituting the life cycle management data of the project. Therefore, by including the document management database and the requirement management database in the plurality of databases, traceability over the entire project life cycle can be reliably established.
In addition to the document management database and requirement management database, the plurality of databases include a test management database, a change management database, a nonconformity management database, and a device configuration management database that constitute the project life cycle management database. And more preferred. Here, the test management database has functions to register, record, and manage the status of test verification items such as factory tests and field tests, and the nonconformity management database occurred in design, verification, testing, etc. Non-conforming items are managed, and the device configuration management database is a device configuration managed.

The reliability analysis sheet may be an FMECA sheet, a Hazard Log sheet, a PMA sheet, or a CMA sheet.
Here, the PMA sheet and the CMA sheet are related to the maintainability analysis.
The PMA sheet means a preventive maintenance analysis sheet, and the PMA can be a tool for registering preventive maintenance tasks and estimating human resources, tools, and costs.
The CMA sheet means a post-maintenance analysis (CMA) sheet, and the CMA can be a tool for registering post-maintenance tasks and estimating human resources, tools, costs, and the like.

Further, as a method invention for solving the problem, a reliability analysis sheet is created based on design information data of a system whose reliability is to be analyzed, and the reliability of the system is improved based on the reliability analysis sheet. In the reliability analysis method to analyze,
A database for managing changes in the design information;
The reliability analysis sheet can acquire changes in design information managed by the database by associating each stored data with one or more databases among a plurality of databases corresponding to the data. And the databases are a plurality of databases that manage changes in different design information,
The plurality of databases include a document management database for managing documents related to the design information of the system, a requirements management database for confirming conformity of requirements related to the design of the system, and a life constituting data for life cycle management of the requirements management database. By including a cycle database, it is characterized by reliably establishing traceability throughout the project life cycle .

  The database is a plurality of databases that manage changes in different design information, and the reliability analysis sheet includes one or more of the data held therein and the plurality of databases corresponding to the data. It is good to acquire the change of the said design information from the database linked | related with the said data.

  The plurality of databases may include a document management database for managing documents related to the design information of the system and a requirements management database for confirming conformity of requirements related to the design of the system.

  The reliability analysis sheet may be an FMECA sheet or a Hazard Log sheet.

  As described above, according to the present invention, it is possible to establish traceability over the entire project life cycle of the analysis basis and the analysis target device in consideration of information in the database for project life cycle management such as document management and requirements management. An analysis apparatus and method can be provided.

It is a schematic diagram of the project management tool in an Example. It is the figure which showed the cooperation of each database in an Example. It is a flow sheet regarding Hazard Log. An example of the FMECA sheet created using spreadsheet software is shown. An example of a Hazard Log sheet created using spreadsheet software is shown.

  In creating the reliability analysis sheet, the inventor associates the database related to the reliability analysis with the database group for project life cycle management to associate the analysis basis on the reliability analysis sheet and the project life cycle of the analysis target device. This led to the establishment of general traceability.

  Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the drawings. However, the dimensions, materials, shapes, relative arrangements, and the like of the components described in this embodiment are not intended to limit the scope of the present invention unless otherwise specified, but are merely illustrative examples. Not too much.

In the present embodiment, the present invention is applied to a project management tool whose requirement management is mainly performed. The project management tool will be described with reference to FIG.
FIG. 1 is a schematic diagram of a project management tool in the embodiment.
As shown in FIG. 1, the project management tool in the embodiment includes a requirement management database 1, a test management database 2, a document management database 3, a change management database 4, a device configuration database 5, a RAMS analysis database 6, and a nonconformity management database 7. Consists of

First, requirement management applied in the requirement management database 1 will be described.
Requirements management refers to managing requirements (requirements) presented by customers so that they are reflected in design and production without omission or omission. Requirements management consists of a verification process and validation process. The initials of the verification process and validation process are used in the V & V process, and the V-shaped diagram shown in FIG. Sometimes referred to as a process.
“Verification” means that the requirement must be clearly stated in an appropriate document such as a design document or a test procedure, and that the requirement item is correctly reflected in the document.
In addition, validation is performed after production and installation, and it is verified by objective evidence that the equipment and system produced and installed satisfy the requirements and design specifications from customers. It means you have to.

  In the requirement management database 1, requirements 1a consisting of high-level requirements, requirement definitions, etc., requirements 1b consisting of basic design, detailed design, test plan, etc., requirements 1c consisting of test procedures, etc. are clarified as high-level requirements. Associations are made so that a specific or detailed one becomes a lower requirement. In other words, the requirements 1a, 1b, and 1c are associated in order from the top. The requirement management database 1 associates requirements as described above, and makes it possible to track and verify the conformity of requirements between designs and documents. In the requirement management database 1, the relationship between the upper and lower requirements is associated with each other, and verification of conformity (Verification) is performed.

Each requirement is managed as information accompanying the document. The management is performed in the document management database 3 and the change management database 4.
The document management database 3 registers all the related documents and manages the drawing / revision status. In addition, the change management database 4 performs change request approval / confirmation of revision consistency when a related document is revised.

  Test management database 2 has functions to register, record, and manage the status of test verification items such as factory tests and field tests, and has a comprehensive track record of unit tests, combination tests, and comprehensive tests for equipment and components. Managed.

  The device configuration database 5 manages information items of configuration items constituting the system.

  The nonconformity management database 7 is used to manage nonconformities that occur in design, verification, testing, and the like.

  The reliability analysis (RAMS analysis) database 6 is a database relating to reliability analysis, and the aforementioned FMECA sheet, Hazard Log sheet, or preventive maintenance analysis (PMA: Preventive Maintenance Analysis) related to maintainability analysis among reliability analysis. It has a sheet and a post-maintenance analysis (CMA: Collective Maintenance Analysis) sheet.

  The requirement management database 1, the test management database 2, the document management database 3, the change management database 4, the device configuration database 5, the RAMS analysis database 6, and the nonconformity management database 7 are associated with each other as described later. .

FIG. 2 is a diagram illustrating the cooperation of the databases in the embodiment.
As shown in FIG. 2, the RAMS analysis database 6 is linked with the requirement management database 1, the test management database 2, the document management database 3, the change management database 4, the device configuration database 5, and the nonconformity management database 7. In addition, the requirement management database 1, the test management database 2, the document management database 3, the change management database 4, the device configuration database 5, and the nonconformity management database 7 are mutually linked.

(Reliability analysis)
Next, reliability analysis will be described.
In the project management tool shown in FIGS. 1 and 2, when performing reliability analysis, a hazard log is first performed to identify risk / failure factors and to consider avoidance / reduction measures.
FIG. 3 is a typical example of a flowchart relating to Hazard Log in a railway / traffic system development project. The Hazard Log will be described with reference to FIG. In FIG. 3, a customer (end user) means a user of a device or system in which reliability analysis of this embodiment is performed, and a manufacturer means a creator of the device or system. Assume that the manufacturer orders equipment, systems, etc.

  When Hazard Log is started, the customer discloses a contract document to the manufacturer in step S1. The contract document describes information related to the design such as specifications of devices and systems to be ordered.

  When the contract document is disclosed in step S1, the manufacturer receives the contract document and examines it in step S2, and collects related information and reference drawing documents in step S3.

  When step S2 and step S3 are completed, an SSPP (System Safety Program Plan) is created in step S4, and a Hazard Analysis / Hazard Log template is created in step S5.

  When step S5 is completed, the SSPP is then reviewed in step S6 and submitted to the customer. When step S6 ends, the customer reviews the SSPP in step S7.

When step S7 ends, the process proceeds to step S8.
In step S8, if the SSPP is approved as a result of the customer review of SSPP, that is, if Yes in step S8, the process proceeds to step S9, and if not approved, that is, if No in step S8, the process returns to step S3.

  In step S9, the manufacturer investigates the design difference between the project in which this Hazard Log is being executed and the past project, that is, the old and new projects, and proceeds to step S10.

  In step S10, Hazard Analysis books are created / updated.

  When step S10 ends, the manufacturer reviews the Hazard Analysis book in step S11 and submits it to the customer. When step S11 ends, the customer reviews the Hazard Analysis book in step S12.

When step S12 ends, the process proceeds to step S13.
In step S13, as a result of the customer review of the Hazard Analysis book, if the Hazard Analysis book is approved, that is, if Yes in step S13, the process proceeds to step S14, and if not approved, that is, if No in step S13, the process returns to step S9.

  In step S14, the manufacturer prepares a rationale document for safety review, and in step S15, creates a Hazard Log draft based on past design information.

  When the Hazard Log draft is created in step S15, the manufacturer updates the Hazard Log based on the latest adjustment information in the project organization in step S16.

  When the Hazard Log is updated by the manufacturer in Step S16, the Hazard Log is reviewed in Step S17, the Hazard solution is presented, and the process proceeds to Step S18.

  In step S18, the manufacturer reviews the Hazard Log and submits it to the customer. When step S18 ends, the customer reviews the Hazard Log in step S19.

When step S19 ends, the process proceeds to step S20.
In step S20, as a result of the customer review of Hazard Log, if Hazard Log is approved, that is, if Yes in step S20, the process is terminated, and if not approved, that is, if No in step S20, the process returns to step S16.

  The Hazard Log made as described above is made into a database as a Hazard Log sheet. At this time, the requirement management database 1 shown in FIG. 1 is used for attributes and hazard mitigation measures related to this hazard log. Here, the hazard mitigation measures are registered as requirements in the requirement management database 1, and the design conformity confirmation and validity validation (Verification & Validation) of the mitigation measures are performed.

The requirement management database 1 is linked with design documents, test results, O & M (operation & maintenance) books, other records, etc. on the document management database 3 to show the basis of each. In addition, on the reliability analysis database (RAMS analysis database 6), the confirmation items of the Hazard Log sheet reduction / verification results are directly linked to the requirement items of the requirement management database 1 and the test items of the test management database 2. .
As a result, when a design change or update is made as a result of project progress, the corresponding part of the Hazard Log sheet is updated, and once the hazard has been treated such as design conformity confirmation and validation (Verification & Validation), etc. On the other hand, the necessity of re-verification becomes clear, the relationship of verification records can be maintained, and the traceability of the reliability analysis sheet can be established.

In the present embodiment, the example using the Hazard Log sheet has been described. However, an FMEC sheet can also be used instead of the Hazard Log sheet of the present embodiment for an apparatus failure or the like.
In the FMECA sheet, substitution / compensation measures and countermeasures for serious failures are registered as requirements in the requirement management database 1 and traceability is established by executing design conformity confirmation and validation (Verification & Validation), and measures in the FMECA sheet. Planning is effective. Confirmation / verification results are linked directly to project deliverables and documents. That is, it cooperates with the document management database 3, the test management database 2, and the like.
When a design change or device configuration change is made due to project progress, FMECA analysis will need to be performed again. However, the failure rate, quantity, and configuration information of each device are held as management attributes in the device configuration database 5. By directly linking the existing information, the analysis based on the latest information can be executed again.

Furthermore, for the preventive maintenance of the apparatus, a PMA sheet can be used in place of the Hazard Log sheet of this embodiment and the above-mentioned FMECA sheet.
PMA can be a tool for registering preventive maintenance tasks and estimating human resources, tools, costs, and the like.
In PMA sheets, preventive maintenance tasks are registered as requirements in the requirement management database 1, traceability is established by executing design conformity confirmation and validation (Verification & Validation), and preventive maintenance tasks in PMA sheets are effective. Become. Confirmation / verification results are linked directly to project deliverables and documents. That is, it cooperates with the document management database 3, the test management database 2, and the like.
When a design change or device configuration change is made due to project progress, it will be necessary to perform the PMA analysis again. However, the failure rate, quantity, and configuration information of each device are held as management attributes in the device configuration database 5. By directly linking the existing information, the analysis based on the latest information can be executed again.

Further, for the subsequent maintenance of the apparatus, a CMA sheet can be used instead of the Hazard Log sheet of the present embodiment, the aforementioned FMECA sheet, and the PMA sheet.
CMA can be a tool for registering post-maintenance tasks and estimating human resources, tools, costs, and the like.
In the CMA sheet, the post-maintenance task is registered in the requirement management database 1 as a requirement, traceability is established by executing design conformity confirmation and validation (Verification & Validation), and the post-maintenance task in the CMA sheet is effective. Become. Confirmation / verification results are linked directly to project deliverables and documents. That is, it cooperates with the document management database 3, the test management database 2, and the like.
When a design change or device configuration change is made due to project progress, it will be necessary to perform CMA analysis again. However, the failure rate, quantity, and configuration information of each device are held as management attributes in the device configuration database 5. By directly linking the existing information, the analysis based on the latest information can be executed again.

  Considering information in the database for project lifecycle management such as document management and requirement management, it can be used as a reliability analysis device and method that can establish traceability over the entire project lifecycle of analysis basis and analysis target equipment. .

1 requirement management database 2 test management database 3 document management database 4 change management database 5 equipment configuration database 6 RAMS analysis database 7 nonconformity management database

Claims (5)

In the reliability analysis device that has the reliability analysis sheet created based on the design information data of the system to be analyzed for reliability, and analyzes the reliability of the system based on the reliability analysis sheet,
A database for managing changes in the design information;
The reliability analysis sheet can acquire changes in design information managed by the database by associating each stored data with one or more databases among a plurality of databases corresponding to the data. And the databases are a plurality of databases that manage changes in different design information,
The plurality of databases include a document management database for managing documents related to the design information of the system, a requirements management database for confirming conformity of requirements related to the design of the system, and a life constituting data for life cycle management of the requirements management database. A reliability analysis device characterized by reliably establishing traceability throughout the project life cycle by including a cycle database . In addition to the document management database and requirement management database, the plurality of databases include a test management database, a change management database, a nonconformity management database, and a device configuration management database that constitute the project life cycle management database. The reliability analysis apparatus according to claim 1, wherein traceability over the entire project life cycle is reliably established . The reliability analysis sheet, FMECA sheet, Hazard Log sheet, reliability analysis apparatus according to claim 1, characterized in that the PMA sheet or CMA sheet. In the reliability analysis method of creating a reliability analysis sheet based on the design information data of the system to be analyzed for reliability, and analyzing the reliability of the system based on the reliability analysis sheet,
A database for managing changes in the design information;
The reliability analysis sheet can acquire changes in design information managed by the database by associating each stored data with one or more databases among a plurality of databases corresponding to the data. And the databases are a plurality of databases that manage changes in different design information,
The plurality of databases include a document management database for managing documents related to the design information of the system, a requirements management database for confirming conformity of requirements related to the design of the system, and a life constituting data for life cycle management of the requirements management database. A reliability analysis method characterized by establishing traceability throughout the project life cycle by including a cycle database . The reliability analysis method according to claim 4, wherein the reliability analysis sheet is an FMECA sheet, a Hazard Log sheet, a PMA sheet, or a CMA sheet.

Images