|
US$1024.00 · In stock
Delivery: <= 5 days. True-PDF full-copy in English will be manually translated and delivered via email.
GB/T 9414.5-2018: Maintainability -- Part 5: Testability and diagnostic testing
Status: Valid GB/T 9414.5: Evolution and historical versions
| Standard ID | Contents [version] | USD | STEP2 | [PDF] delivered in | Standard Title (Description) | Status | PDF |
| GB/T 9414.5-2018 | English | 1024 |
Add to Cart
|
5 days [Need to translate]
|
Maintainability -- Part 5: Testability and diagnostic testing
| Valid |
GB/T 9414.5-2018
|
| GB/T 9414.5-1988 | English | 359 |
Add to Cart
|
3 days [Need to translate]
|
Guide on maintainability of equipment--Part 6: Maintainability verification
| Obsolete |
GB/T 9414.5-1988
|
PDF similar to GB/T 9414.5-2018
Basic data | Standard ID | GB/T 9414.5-2018 (GB/T9414.5-2018) | | Description (Translated English) | Maintainability -- Part 5: Testability and diagnostic testing | | Sector / Industry | National Standard (Recommended) | | Classification of Chinese Standard | K04 | | Classification of International Standard | 21.020 | | Word Count Estimation | 54,520 | | Date of Issue | 2018-06-07 | | Date of Implementation | 2019-01-01 | | Issuing agency(ies) | State Administration for Market Regulation, China National Standardization Administration | GB/T 9414.5-2018: Maintainability -- Part 5: Testability and diagnostic testing---This is a DRAFT version for illustration, not a final translation. Full copy of true-PDF in English version (including equations, symbols, images, flow-chart, tables, and figures etc.) will be manually/carefully translated upon your order.
Maintainability--Part 5. Testability and diagnostic testing
ICS 21.020
K04
National Standards of People's Republic of China
Replace GB/T 9414.7-2000
Maintainability Part 5. Test and diagnostic tests
(IEC 60706-5.2007, Maintainabilityofequipment-
Part 5. Testabilityanddiagnostictesting, IDT)
Published on.2018-06-07
2019-01-01 implementation
State market supervision and administration
China National Standardization Administration issued
Content
Foreword III
Introduction IV
1 Scope 1
2 Normative references 1
3 Terms and definitions, abbreviations 1
3.1 Terms and Definitions 1
3.2 Abbreviations 5
4 test description and diagnostic test 5
4.1 Overview 5
4.2 Test Purpose 6
4.3 Purpose of the diagnostic test 8
4.4 Method 8 for diagnostic testing
4.5 Method 8 for condition monitoring
4.6 Testability Concept 9
5 Testability Specification 9
5.1 Overview 9
5.2 Work Description 9
5.3 Specification 9
5.4 Testability characteristics 13
5.4.1 Test characteristics 13
5.4.2 Operating Environment 13
5.4.3 Test Task 13
5.5 Characteristic values of the test evaluation 14
5.6 Selection of evaluation criteria for diagnostic design 14
6 Testability during development 15
6.1 Summary 15
6.2 Function allocation 17
6.3 Test Engineering 17
6.3.1 Testability Design Guidelines 17
6.3.2 Testability design 17
6.3.3 Use of commercial off-the-shelf (COTS) 18
6.4 Testability R&D Process 18
6.4.1 Logistics support 18
6.4.2 Availability and diagnostic tests 19
7 Testability Assessment 19
7.1 Overview 19
7.2 Analysis and verification 19
7.3 Test Verification 19
8 test documents 19
Appendix A (informative) Characterization of fault identification and fault location 20
Appendix B (informative) Development steps for measurable products 24
Reference 47
Foreword
GB/T 9414 "Maintenance" is divided into the following parts.
--- Part 1. Application Guide;
--- Part 2. Maintainability requirements and research in the design and development phases;
--- Part 3. Verification and data collection, analysis and representation;
--- Part 5. Test and diagnostic tests;
--- Part 9. Maintenance and repair support.
This part is the fifth part of GB/T 9414.
This part is drafted in accordance with the rules given in GB/T 1.1-2009.
This part replaces GB/T 9414.7-2000 "Device Maintenance Guideline Part IV. Diagnostic Test", and GB/T 9414.7-2000
The main changes are as follows.
--- A reference to the IEC standard has been added to the normative reference document;
--- Chapter 4 was revised to "testability description and diagnostic test";
--- Chapter 5 was revised to "testability specification";
--- Chapter 6 was revised to "testability in the development process";
--- Added Chapter 7 "Testability Assessment" and Chapter 8 "Testing Documents".
This section uses the translation method equivalent to IEC 60706-5.2007 "equipment maintainability Part 5. Testability and diagnostic tests."
The documents of our country that have a consistent correspondence with the international documents referenced in this part are as follows.
---GB/T 2900.13-2008 Electrotechnical terminology reliability and service quality (IEC 60050-191.1990, IDT)
---GB/T 9414.1-2008 Maintainability Part 1. Application Guide (IEC 60300-3-10.2001, IDT)
---GB/T 9414.2-2012 Maintainability Part 2. Design and development phase maintainability requirements and research (IEC 60706-2.
2006, IDT)
---GB/T 9414.3-2012 Maintainability Part 3. Verification and data collection, analysis and presentation (IEC 60706-3.
2006, IDT)
This section has made the following editorial changes.
--- Modified the standard name.
This part was proposed by the Ministry of Industry and Information Technology of the People's Republic of China.
This part is under the jurisdiction of the National Technical Committee for Reliability and Maintainability of Electronic and Electrical Products (SAC/TC24).
This section is mainly drafted by. Ministry of Industry and Information Technology, Post and Telecommunications Industry Standardization Institute, Beijing University of Posts and Telecommunications.
The main drafters of this section. Xia Hailun, Wu Bingmei, Zeng Zhimin, Liu Yinlong, Huang Zhenglei, Huang Rong.
The previous versions of the standards replaced by this section are.
---GB/T 9414.7-2000.
Introduction
Testability is an important feature in the use and maintenance of systems or equipment, and is critical to the availability and maintainability of systems or equipment.
Heavy effect. Diagnostic tests can be performed manually or with test equipment of varying degrees of automation. Test-optimized design
Requires close collaboration between design, use, and maintenance organizations. This section is intended to highlight the various requirements of test and diagnostic testing and to help
Timely coordination with each other.
In this section, contract objects. systems, devices, or functional components, collectively referred to as "products", need to consider test design. Every product needs
Perform the necessary functions that are calibrated during the development and production phases and maintained throughout the life cycle. To maintain production
The functionality of the product, knowing the functional status of each sub-function at any time during the operation of the product. If a failure occurs, measures should be taken
Ensure that the fault is identified and locate the unit that caused the fault. Product testability requirements may seem simple, but if at the beginning of product development
The segment does not consider it, and subsequent implementations will result in increased workload and significant cost increases. If all requirements are at the beginning of development
Can be achieved, R & D engineers can specify the functional characteristics "testability" without a lot of extra work, which can significantly save
Cost, for example, by reducing the number of test steps to verify development results. Experience shows that the extra cost and work of the development phase can
Compensation is obtained, for example, existing test equipment can be used in the production phase. Reliable fault identification and low maintenance costs during operation, large
Greatly increased the market value of measurable products.
Since the products to which this section applies cover a wide range of technologies, this section uses a common approach to writing about the process and technical content.
Therefore, this section only provides a basis for evaluating the product estimates and the basic methods for achieving the necessary product testing. Product fault identification and
The technical realization of fault location is the task of product development engineers, and the implementation of this technology depends on the technical level of product development. Therefore,
It is not important that the required test tasks are implemented in hardware or software. It is important that all functions can be checked through the test path.
Check that the determined test characteristic value matches the given target value. If there is a deviation from the target value, measures should be taken to ensure that the target value is obtained.
Satisfy. These measures should be implemented in the early stages of development prior to freezing the design.
Maintainability Part 5. Test and diagnostic tests
1 Scope
The purpose of this part of GB/T 9414 is to.
--- Provide guidance for early consideration of testability issues in design and development;
--- Helps identify valid test procedures as part of operation and maintenance.
This section applies to all types of products, including commercial off-the-shelf, whether mechanical, hydraulic, electrical or other. In addition, this
Partially applicable to the development of any product, making the product characteristics verifiable (measurable).
The goal of this section is to ensure that the prerequisites related to product testability are defined at the beginning of development, so that the conditions established by the customer
Implement, document, and verify during development.
This section also provides a test implementation and evaluation method as an integral part of product design and suggests a product life cycle.
Product testing documents should be continuously updated.
2 Normative references
The following documents are indispensable for the application of this document. For dated references, only dated versions apply to this article.
Pieces. For undated references, the latest edition (including all amendments) applies to this document.
IEC 60050-191 Electrotechnical terminology reliability and quality of service (International electrotechnicalvocabulary-
Chapter191. Dependabilityandqualityofservice)
IEC 60300-3-10 Reliability Management Part 3-10. Application Guide Dependabilitymanagement-
Part 3-10. Applicationguide-Maintainability)
IEC 60706-2 Maintainability Part 2. Design and development phase requirements and research (Maintainability ofequipment-
Part 2. Maintainabilityrequirementsandstudiesduringthedesignanddevelopmentphase)
IEC 60706-3 Maintainability Part 3. Verification and data collection, analysis and presentation (Maintainabilityof
equipment-Part 3. Verificationandcolection, analysisandpresentationofdata)
3 terms and definitions, abbreviations
3.1 Terms and definitions
The following terms and definitions as defined in IEC 60050-191 apply to this document.
3.1.1
In-machine test built-intest; BIT
The product's inherent testing that automatically identifies and locates faults.
3.1.2
In-machine test equipment built-intestequipment; BITE
Hardware and/or software used to implement in-machine test functions.
3.1.3
Commercial spot commercialoff-the-shelf; COTS
Commercial off-the-shelf products are indicated.
3.1.4
Hazard criticality
The extent of the impact of the fault.
Note. The hazard is expressed in terms of the number of stages. The higher the number of stages, the more serious the expected consequences of the failure.
3.1.5
Test depth depthoftest
Description and description of a unit or subunit test level.
3.1.6
Design level designlevel
The level specified for existing design elements (functions and/or physical units) in the product breakdown structure.
Note. In some cases, the “design level” is also called the “convention level”.
3.1.7
Diagnostic accuracy rate diagnosticcorrectness
The proportion of product failures that can be correctly diagnosed under given conditions.
3.1.8
Diagnostic test
The test procedure used to perform the diagnosis.
3.1.9
False alarm falsealarm
There is no fault found when there is a fault indication.
3.1.10
False alarm rate falsealarmrate
The percentage of false alarms in the fault indication.
3.1.11
Fault identification time faultrecognitiontime
The time between the moment of failure and the time the fault is identified.
3.1.12
Fault simulation faultsimulation
To verify diagnostic capabilities, non-destructive interventions are employed in the hardware unit to generate faults and/or simulate faults through software.
3.1.13
Function
The capabilities required by the product.
Note. In the product breakdown structure, the function is always associated with the specified level.
3.1.14
Functional model
Describe a conceptual representation of the interaction and interdependence between incentives and measurement (response) terminals.
Note. The functional model in product development is the main block diagram showing the product functionality, supplemented by the test path developed by the developer.
3.1.15
Functional test
Test all specified functions of the hardware unit to verify product capabilities.
3.1.16
Hardware unit hardwareunit
Design elements that implement functions and/or sub-functions in hardware may also contain software components.
3.1.17
Field replaceable unit linereplaceableunit; LRU
A replaceable hardware or software unit that can be replaced directly on the device by the user or service support.
3.1.18
Maintenance plan maintenanceconcept
The relationship between the level of design and the level of maintenance used for product repairs.
3.1.19
Maintenance strategy maintenancepolicy
A common approach to repair and maintenance support based on the goals and strategies of owners, users, and customers.
3.1.20
Monitoring monitoring
In the selected operating mode, its function is automatically observed without affecting the operation.
3.1.21
Operating environment operationalcontext
The environment in which the product operates.
3.1.22
Parameter parameter
The physical quantity of the specification function.
3.1.23
Product
Designated deliverables or services.
Note 1. From a credibility perspective, the product may be simple (eg a device, a software algorithm) or it may be complex (eg a system or a
Includes a combination of hardware, software, human factors, ancillary facilities and activities).
Note 2. The product has its own life cycle stage.
Note 3. Product and item have the same definition.
3.1.24
Product breakdown structure
The image represents the tree structure of the physical structure of the product unit and the subunit.
3.1.25
Shop replaceable unit shopreplaceableunit; SRU
A hardware or software unit that can be replaced in the user's warehouse/workshop, the same level of service support, or at the supplier's shop.
3.1.26
Signal signal
A physical variable that represents information.
Note. A signal can be represented by one or more parameters.
3.1.27
Specification specification
A detailed description of the product's functionality at a given level of product breakdown.
Note. Specifications are generally derived from system requirements and can be verified.
3.1.28
Job description statementofwork; SoW
A detailed description of the documents provided for the goods and services.
Note. The job description is proposed or accepted by the client and defines the work proposed in the contract and the work provided by the contractor. Therefore, the job description has formed the main skill
According to the document, the bidders submit their bids, the contractor performs the work, and the customer accepts the goods and services provided.
3.1.29
Inspire stimulus
An input signal with certain parameters used to trigger a function.
3.1.30
Subfunction sub-function
Subdivision of functions (see 3.1.13 functions).
3.1.31
Port terminal
A generic term for a physical access point used to test product signals. Related terms for physical implementation or synonym are.
---plug;
---Connector;
---Plug/plug type connector;
---Test point;
---interface;
---Adapter.
Note. Ports are usually identified by a unique identifier.
3.1.32
Test plan testconcept
A description of the results of the system test requirements analysis and how to meet the requirements of the requirements method.
3.1.33
Test coverage testcoverage
The ratio of the number of faulty functions to the total number of functions can be diagnosed under a given test procedure.
3.1.34
Test equipment testequipment
The tools (hardware and/or software) required to implement the test.
Note. Test equipment is divided into in-machine test equipment (BITE) and off-board test equipment according to the technology involved in the test.
3.1.35
Test procedure testinstruction
A document describing how the tests required in the test specification are implemented.
3.1.36
Test path testpath
A description of the test steps from the associated hardware unit to the port.
Note. In addition, the test path defines the (functional) relationship between the stimulus and the response.
3.1.37
Test sequence testsequence
A series of test steps.
3.1.38
Test specification testspecification
A file detailing test sequences, parameters, and functions.
3.1.39
Test step teststep
The smallest unit in which the hardware unit is tested.
3.1.40
Test task testtask
The sum of all required tests that meet the fault identification and positioning instructions.
3.1.41
Testability testability
A design characteristic that determines the extent to which a product can be tested under specified conditions.
3.2 Abbreviations
The following abbreviations apply to this document.
ATE. automatic test equipment (automatictestequipment)
ATS. automatic test system (automatictestingsystem)
BIT. built-in test (built-intest)
BITE. built-in test equipment (built-intestequipment)
COTS. commercial off-the-shelf
DP. data processing
FL. fault location (faultlocalization)
FM. functional monitoring (functionalmonitoring)
FME(C)A. Failure mode, impact (and hazard) analysis [failuremode, effects, (and criticality) analysis]
FR. fault recognition (faultrecognition)
FT. functional test
FTA. Fault Tree Analysis (faulttreeanalysis)
HWE. hardware unit (hardwareunit)
LCC. life cycle cost
LORA. repair level analysis (levelofrepairanalysis)
LRU. field replaceable unit (linereplaceableunit)
PCB. printed circuit board (printedcircuitboard)
SoW. job description (statementofwork)
SRU. shop replaceable unit (shopreplaceableunit)
SF. sub-function
TS. technical specification
4 test description and diagnostic test
4.1 Overview
Product testing is considered at all stages of product design and its life cycle to help efficient, economical operation of the product.
And maintenance. Product repair programs include applicable diagnostic test methods. Test and diagnostic tests are implemented over the life of the product
Into.
Life cycle cost (LCC) is an increasingly important aspect of evaluating the quality of any design. Many customers care about direct purchases
In addition to the cost, it is also required to control the costs associated with daily use, maintenance and logistics support. These costs are mainly due to product reliability and maintainability.
And the impact of maintenance support features. In this sense, the application of diagnostic test techniques has the potential to significantly reduce the cost of a portion of the LCC.
However, the limitations imposed by LCC optimization should be considered when determining diagnostic test requirements.
This section applies to all phases of the product life cycle, from the design and development phase of determining product requirements to manufacturing and installation stages.
Paragraph, and finally to the operation and maintenance phase, as shown in Figure 1, specifically including.
a) Design and development phase
From the concept of the product to the realization, the product requirements should be consistent with the specific requirements of its application field. If necessary, it can go through some
Early stage.
b) Manufacturing and installation phase
At this stage, you need to validate the diagnostic technology with the current device and evaluate the performance of the product. Prepare the file and start working on the run and dimension
Trainers are trained.
c) Operation and maintenance phases
The device under test may change due to aging. Considering the continuous demand for diagnostic tests, the test function of the test equipment needs
Continue and replace or upgrade. In the latter case, the test equipment needs to be redesigned in the new development phase.
By using this section, the prerequisites for generating the necessary data/information for the product will be met and these prerequisites are throughout the product.
It can be verified and updated during the life cycle.
Appendix B gives examples of how test development, documentation, and verification can be performed based on product/system design.
Diagnostic tests include.
--- Functional testing, the purpose is to verify that the function is still valid.
--- Status monitoring to track the degradation of device status over time.
Condition monitoring is closely related to the concepts of diagnostic testing and is inseparable. However, this section only contains the sections for condition monitoring.
content.
Description.
TS---test specification;
CE---concurrent engineering;
M1---confirmation requirements;
M2---analytical verification;
M3---test verification.
Figure 1 Test and diagnostic tests over the life cycle
4.2 Test purpose
Testability in the design and development phase is closely related to maintainability, usability and safety. The main purpose of testing is to work for each system.
Can solve the following problems.
a) Whether the diagnostic test can detect a malfunction. Due to safety limitations or testing may be destructive (eg testing the rotor)
Overspeed capability), some features are not fully tested.
b) Whether the test is feasible. Risk of malfunction, test cost (cost of test equipment, maintenance cost of test equipment and test fee)
Use) and the use of better, less expensive alternatives do not necessarily lead to an increase in test economics.
Note. In both cases a) and b), alternatives are needed to ensure that these functions function properly over the life of the product. At the same time, these factors are also
Will affect test coverage. Since the system cannot be tested to determine the operation of the system during the life of the system, the low test coverage may be
Harmful, but with good maintainability and repair capabilities, testing is not required.
c) At what stage of the life cycle, the system function test is performed. Test capabilities should be considered at each stage of the life cycle. ratio
For example, functional testing is feasible at the unit level, but testing at the system level is impractical. This can be done by the washing machine and its waste
An example of water function is explained. From the user's point of view, by running the test in advance to confirm that the function is working properly
Beneficial (running phase testing is useless). The design of this feature does not require the use of test equipment to test the function.
This is because.
1) The life of the pump and related components is longer than the product life (other faults and their maintenance costs limit the life of the product);
2) It is convenient to use maintenance methods that eliminate possible malfunctions;
3) Ability to adequately test the unit that completes the drainage function during unit testing and system testing prior to delivery;
4) Which stage of testing will also affect life cycle costs.
d) What depth the test needs to go to. Test depth is also a very important criterion, as in the example above, it and dimensions
The concept of repair is closely related. The depth of the test indicates the criteria for distinguishing cells or subunits. For example. system test if not only
It can identify the units that need to be replaced, and can identify the subunits that need to be replaced with little impact on the cost. This will
Reduce the cost of test equipment associated with identifying and replacing failed subunits in a unit level test.
Verify that all developed features are fundamental to test design. However, it should be noted that the test coverage does not have to reach 100%.
Because the test itself may cause a fault during operation, this is more severe than a non-test fault, such as a fault caused by a test or false alarm.
weight. If system security is involved, all test coverage is not required to reach 100%, as the test itself may compromise system security.
It is important that the test provides a solid guarantee during the operation of the system. To achieve this, the test overlay should be accurately determined.
Cover rate with 100% offset.
In any case, test objectives should not conflict with higher-level goals, such as availability.
e) How to manage false alarms and “no faults found”. System test may detect and send to the user if the fault does not exist
error report. This can lead to unnecessary investigations and ultimately to false alarm reports. When diagnosed as "no fault found" (nofault
When found, it may also lead to unnecessary maintenance. The false alarm rate of various schemes cannot exceed the established standards and should be
Can be reduced to 0. A feedback system can be introduced to reduce false alarms and "no faults found", which will continuously evaluate the loop
And calibrate itself to accommodate damage to components within established standards. Repeated testing to eliminate false alarms (test scenarios may be due to unproductive
The alarm is completely changed. It will increase the test time and should be avoided.
A fault may also be displayed when there is no fault. This is due to a variety of reasons.
1) If a fault is found in the system and the faulty part is diagnosed. But remove the part and measure it separately
After the test has not found the fault, the system test specification related to the test specification of the faulty component shall be checked;
2) Ins...
Tips & Frequently Asked Questions:Question 1: How long will the true-PDF of GB/T 9414.5-2018_English be delivered?Answer: Upon your order, we will start to translate GB/T 9414.5-2018_English as soon as possible, and keep you informed of the progress. The lead time is typically 3 ~ 5 working days. The lengthier the document the longer the lead time. Question 2: Can I share the purchased PDF of GB/T 9414.5-2018_English with my colleagues?Answer: Yes. The purchased PDF of GB/T 9414.5-2018_English will be deemed to be sold to your employer/organization who actually pays for it, including your colleagues and your employer's intranet. Question 3: Does the price include tax/VAT?Answer: Yes. Our tax invoice, downloaded/delivered in 9 seconds, includes all tax/VAT and complies with 100+ countries' tax regulations (tax exempted in 100+ countries) -- See Avoidance of Double Taxation Agreements (DTAs): List of DTAs signed between Singapore and 100+ countriesQuestion 4: Do you accept my currency other than USD?Answer: Yes. If you need your currency to be printed on the invoice, please write an email to [email protected]. In 2 working-hours, we will create a special link for you to pay in any currencies. Otherwise, follow the normal steps: Add to Cart -- Checkout -- Select your currency to pay. Question 5: Should I purchase the latest version GB/T 9414.5-2018?Answer: Yes. Unless special scenarios such as technical constraints or academic study, you should always prioritize to purchase the latest version GB/T 9414.5-2018 even if the enforcement date is in future. Complying with the latest version means that, by default, it also complies with all the earlier versions, technically.
|