13.07.2015 Views

MAINTAINABILITY DESIGN TECHNIQUES METRIC - AcqNotes.com

MAINTAINABILITY DESIGN TECHNIQUES METRIC - AcqNotes.com

MAINTAINABILITY DESIGN TECHNIQUES METRIC - AcqNotes.com

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Downloaded from http://www.everyspec.<strong>com</strong> on 2011-10-29T14:56:01.DOD-HDBK-791(AM)3. Built-in test equipment.Each of these categories is discussed in the paragraphsthat follow.7-3.5.2.1 Logic FlowLogic flow–-a troubleshooting road map is an outlineof the sequence to be followed in the event of a systemfailure; it is essentially a manual procedure. As a maintenanceaid for fault isolation, it provides a step-by-stepdescription of the questions to be asked, tests to be conducted,and continued sequential localization paths to befollowed depending on test results. The “roads” lead fromgeneralized localization to specific fault localization.Specific data required by the technician to enable him tolocalize a fault will allow him to accept or reject each<strong>com</strong>ponent tested as the source of the trouble. For example,an overheated engine can result from coolant leaks.low coolant pump pressure, and constricted passages.Measurement of fluid flow and temperature at strategicpoints in the cooling system can aid the technician ineliminating the source of the fault—radiator. hoses, andengine—and zero in on a pump leak or failure. A checkoutof the system after repair usually requires a repeat ofall the checks used for localization.In electronic systems, three data flow patterns aregenerally of diagnostic interest, i.e.,I. Simple series pattern2. Complex—series-parallel—pattern3. Loop pattern.In the simple series pattern the data flow goes throughone element at a time, and the element that standsbetween a good signal and a bad one is the fault source. Inthe <strong>com</strong>plex pattern, places exist where the data flow fansout along parallel paths. In this case the fault may belocalized to a parallel set, and further tests must be conductedto locate the faulty element of the set. In the looppattern, part of the flow returns to an element as feedback.In this case a fault in one loop element can make itmore difficult to distinguish between the element causingthe fault and elements simply reacting to the faulty signal.Logic flow diagrams are very important in designing<strong>com</strong>puter software used with ATE. The programmermust match the logic flow of his software with the logicflow of the hardware being tested and with various hardwarefault modes and <strong>com</strong>binations of some of the more<strong>com</strong>mon modes. The programmer must take precautionsto code the software for all conceivable circumstances.For example, under some fault circumstances one of thetests may prematurely transfer control to the end of thesoftware loop. Adequate design of test software requiresthat the programmer strive for reliability and that hethoroughly test his program before releasing it for use.The sequence of repair in a flowchart should re<strong>com</strong>mendcorrective actions according to1. Probability of failure2. Accessibility and/or simplicity of repairbut not necessarily in the order given—i.e., even if it isunlikely that Part A failed, if Part A is readily accessible,it might be advantageous to check Part A first.A logic flow for a tracking radar is discussed in par.7-5.5 and is illustrated in Fig. 7-3.7-3.5.2.2 Automatic Test EquipmentAutomatic test equipment (ATE) is defined as equipmentthat is designed to conduct automatically the analysisof functional or static parameters and to evaluate thedegree of the performance degradation of the unit undertest (UUT), and it may be used to perform fault isolationof the UUT malfunction (Ref. 14). The decision making,control. or evaluative functions are conducted with minimumreliance on human intervention and usually aredone under <strong>com</strong>puter control. ATE is used to detect andisolate a fault automatically and to check out the systemfollowing a maintenance action. ATF is separate from theunit under test and is used primarily at the intermediateand depot maintenance levels the UUT is brought to theATE or the ATE is brought to the UUT. If the use of ATFis contemplated, a trade-off analysis must be performedearly in the system acquisition process to determine thevalue of’ the automatic test features in relationship tooperational effectiveness. logistics, maintenance eflectiveness,and life cycle costs. The interdependent parametersof quantity, location, and reliability of ATE can bedetermined by using a generalized cost-effectivenessmodel. ATE is costly and. if not properly integrated intothe overall system, may introduce more reliability andmaintenance problems than it solves. However, the costsassociated with the design and procurement of ATF arenot the <strong>com</strong>plete story. If the ATE results cannot beconfidenty relied upon, false alarms can result in thedisposal of serviceable equipment and in reduced equipmentavailability resulting from unnecessary maintenance.ATE—when it is used properly and when it can berelied upon to yield an accurate diagnosis will reducemaintenance time and the skill level and number of maintenancepersonnel and will increase the availability of thesystem.Selection of test features to be incorporated into anATE system should be based on the following considerations:1. Test Function for Purpose. Is ATE to enhancemaintainability, optimize performance of the system.monitor operational readiness. improve system availability,or is it a <strong>com</strong>bination of these purposes?2. Testing Modes.. Will ATE be used on-line with thesystem operating, on-line with the system under test, oroff-line?3. Level for Defection. At which level will ATE detecta fault or malfunction equipment, subsystem, ormodule?4. Degree of Fault Isolation. At which level willATE isolate a fault—equipment, subsystem, groups ofreplaceable modules, modules, line-replaceable units, orindividual circuits?System level design requirements for the automatic testfeatures should be specified quantitatively and definedquantitatively in the system specification in terms of fail-7-8

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!