2.1 PC Installation Requirements

The host computer must operate under the Windows 95, Windows 98 or Windows NT operating systems.
 

2.2 PC Installation Procedure

To install the Diagnostic Profiler:
 

1. If you are installing from a CDROM, place the CDROM in the CD Drive, If you are installing form a set of diskettes, insert the installation disk labeled Disk 1 into the disk drive.
 

2. On the Windows desktop, click on the "Start" button usually found at the lower left corner of the screen. On the menu that results, click on the button labeled "Run". A pop-up window entitled "Run" will appear.
 

3. Depending on the drive containing the install CDROM (usually D: or E:) or the install diskette (usually A: or B:), enter the drive letter, colon, and "\setup (For example "d:\setup" or "a:\setup"). You can also click on the "Browse" button to select the "setup.exe" file path. When the text has been entered, click on the "OK" button. The installation will begin.
 

4. Follow the instructions presented by the automated installation procedure. If you decide to change the default directory from "C:\Program Files\Profiler", make a note of the change in the box below and where ever the "PC Installation Procedure" and "Quick Start" uses PROFILER_DIRECTORY use the selected directory rather than the default "C:\Program Files\Profiler".
 
The automated installation procedure will automatically install and register the appropriate files in the Windows registry. Under the PROFILER_DIRECTORY, it will generate subdirectories as follows:
 

PROFILER_DIRECTORY Main Root Directory

.\Profiler\Bin Containing executable and program files

.\Profiler\Projects Containing individual project directories

.\Profiler\Samples Containing sample net lists and projects

.\Profiler\Help Containing help data files
 

2.3 Starting the Diagnostic Profiler

2.4 Quick Start

The Concurrent Engineering Tool Set is a series of tools which are used to develop and deploy a Model-Based, Dynamic Diagnostic Reasoning capability for products and processes. The Concurrent Engineering Tool Set consists of both a development component (a series of tools collectively called the Diagnostic Profiler) and a runtime component (the Diagnostician). The development component is used to generate a Diagnostic Knowledge Base of the product, which is used by the runtime component, the Diagnostician, in a test environment to automatically isolate faults based upon interpretation of test results.
 

The Diagnostic Profiler creates a diagnostic representation, or model, of the fault propagation behavior of an item. This model is created from design data imported from net lists, and from user-defined tests and measurements.
 

The Diagnostic Profiler is a collection of tools which enable you to synthesize a runtime diagnostic knowledge base (DKB) through a standard graphical user interface. The synthesis of the model is done for the primary purpose of preparing a DKB for use in runtime to automatically isolate faults based upon interpreting test data. Towards this end, there are five primary functions of the Diagnostic Profiler as follows:
 

1) Import Design Accept input from CAD packages, legacy data or engineers to create a model of the system to be diagnosed and to prepare this information for use by the developer.
 

2) Specify Tests & Repairs

Accept inputs and updates to define the tests, measurements, repairable units and faults to be used in a diagnosis.
 

3) Testability Analysis

Provide fault coverage, fault isolation and ambiguity group information for use by the developer in meeting diagnostics requirements.
 

4) Generate Runtime Formats the data for use during runtime (generates the diagnostic knowledge base .DKB file) and permits the user to set runtime parameters.
 

5) Diagnostic V&V Provide support for the verification and validation of the runtime diagnostic system being developed.
 

This Quick Start session takes about forty-five minutes and will introduce you to the operation of tools supporting each of the five primary Diagnostic Profiler functions. We recommend that you use Quick Start to get a overall understanding of the use of the Diagnostic Profiler to develop an automated diagnostic package.
 

Along with the files required to implement the Diagnostic Profiler, a simple model called JAST is provided to practice on the JAST model is based on the block diagram shown in Figure 2-1. Its net list and a completed diagnostics project are provided in DIAGNOSTIC_PROFILER/Samples. The JAST model will be used throughout this Quick Start to illustrate the Diagnostic Profiler operations.

This Quick Start is intended as an introduction only. More complete information on the features and operation of the Diagnostic Profiler is provided in other sections of this User's Manual. To go through the Quick Start follow the directions in the steps below, and operate the Diagnostic Profiler as described.
 

Step 1 - Initiate the Diagnostic Profiler
 

1. On the Windows desktop, click on the "Start" button usually found at the lower left corner of the screen.
 

2. On the menu that results, click on the word "Programs".
 

3. On the submenu that results, click on the words "Diagnostic Profiler".
 

4. On the sub-submenu that results, click on the words "Diagnostic Profiler" again.
 

5. After a few moments, the Diagnostic Profiler main screen will appear (as shown in Figure 2-2).
 

Step 2 - Set-Up a "Work Area"
 

First, we must define a "Work Area" for the project we are creating. A "Work Area" has a name that appears at the top of the Diagnostic Profiler's main screen next to the button labeled "Work Area". Each "Work Area has its own set of projects. Using "Work Areas", you can group projects according to the overall system addressed or according to the developer responsible or in any other way needed. (Find the details in Section 3.1)
 

1. On the Diagnostic Profiler's main screen, click on the button labeled "Work Area". A window labeled "Work Areas" will appear that supports changing the set of Work Areas.
 

2. In the window labeled "Work Areas", click on the tab labeled "New" to create a new Work Area.
 

3. In the window labeled "Work Areas", click on the text box labeled "New Work Area Name". This click makes the text box accept keyboard data. Key in the word "Samples". "Samples" should appear in the text box labeled "New Work Area Name". Do not change the selection in the area labeled "Select A Default Directory".
 

(Note: Each "Work area" has a default directory. For a new "Work Area" this default directory is initially set to PROFILER_DIRECTORY/Projects. It is good practice to use this directory.)
 

4. In the window labeled "Work Areas", click on the button labeled "Save".
 

5. In the window labeled "Work Areas", click on the button labeled "Done". The "Work Areas" window will disappear. On the Diagnostic Profiler main screen, which remains visible, the word "Samples" appears in the text box to the right of the button labeled "Work Area".
 

Step 3 - Build a Project By Importing the CAD data for JAST
 

The Computer Aided Design (CAD) data for JAST is provided as a net list file containing an EDIF specification. The file path is "PROFILER_DIRECTORY\samples\Jast.net". In this step, a new Diagnostic Profiler project is generated using this data to describe the system for which automated diagnostics is being developed.
 

1. Select the Diagnostic Profiler's Import Design function by clicking the mouse on the Tab labeled "Import Design" on the Diagnostic Profiler's main screen
 

2. On the Diagnostic Profiler's main screen in the white area labeled "Import Design Tool List" there is a list of tools. Double-click on the tool labeled "EDIF Import Wizard". This is the first tool in the list. A window labeled "Step 1: EDIF Import Wizard" will appear.
 

3. In the window labeled "Step 1: EDIF Import Wizard", note that the "Create New Project" option is selected (the small circle is darkened) and click on the button labeled "Next". The window labeled "Step 1: EDIF Import Wizard" will be replaced by a window labeled "Step 2: EDIF Import Wizard".
 

4. In the window labeled "Step 2: EDIF Import Wizard", click on the text box labeled "Name. This click makes the text box accept keyboard data. Key in the project name "My Jast Sample". When this is done, click on the button labeled "Next". The window labeled "Step 2: EDIF Import Wizard" will be replaced by a window labeled "Step 3: EDIF Import Wizard".
 

5. In the window labeled "Step 3: EDIF Import Wizard", select the file:

"PROFILER_DIRECTORY\samples\Jast.net". This is done using three mouse clicks as follows:

(1) In. the box labeled "Directories" click on the folder labeled "Profiler"

(2) In the box labeled "Directories", click on the folder labeled "Samples"

(3) In the list box under the text box labeled "Filename" click on the list item "Jast.net".

When this is done, click on the button labeled "Next". The window labeled "Step 3: EDIF Import Wizard" will be replaced by a window labeled "Step 4: EDIF Import Wizard".
 

6. In the window labeled "Step 4: EDIF Import Wizard", note that the option labeled "No" is selected (the small circle is darkened) and click on the button labeled "Next". After a little processing, the window labeled "Step 4: EDIF Import Wizard" will be replaced by a window labeled "Step 5: EDIF Import Wizard".
 

7. In JAST, there is no power or ground. Thus in the window labeled "Step 5 EDIF Import Wizard", you should only click on the button labeled "Next". The window labeled "Step 5: EDIF Import Wizard" will be replaced by a window labeled "Step 6: EDIF Import Wizard".
 

8. Make the overall JAST assembly be the connector. To do this, in the window labeled "Step 6: EDIF Import Wizard", on the grid labeled "Design Parts", click on the gray box to the left of the part named "Jast". The whole row will be highlighted. Next click on the button labeled "Connector->". The highlighted part will be moved from the grid under the label "Design Parts" to the grid under the label "Connectors". When this is done, click on the button labeled "Next". After some file saving, the window labeled "Step 6: EDIF Import Wizard" will be replaced by a window labeled "Step 7: EDIF Import Wizard".
 

9. In all JAST, all component outputs are connected to all component inputs so that there is no need to describe a more complicated interconnectivity. Click on the button labeled "Next". The window labeled "Step 7: EDIF Import Wizard" will be replaced by a window labeled "Step 8: EDIF Import Wizard".
 

10. Assuming we have done everything right, we are ready to import the design. Click on the button labeled "Import". Status bars will show the progress of the import activities. When the data has been imported, the "Step 8: EDIF Import Wizard" window will disappear. The Diagnostic Profiler's main screen will be updated so that the text box to the right of the button labeled "Project" will contain the name "My Jast Sample" and the text box to the right of the button labeled "Candidate" will contain the import provided candidate name "Edge".
 

(For more information on the Diagnostic Profiler's main screen "Work Area", "Project" and "Candidate" elements, see Section 3)
 

Step 4 - Create A New Diagnostics Candidate
 

1. In the upper portion of the Diagnostic Profiler's main menu, click on the button labeled "Candidate". A window labeled "Candidates" will appear.
 

2. In the window labeled "Candidates", click on the tab labeled "New" to select the Diagnostic Profiler's new candidate function
 

3. In the window labeled "Candidates", click on the text box labeled "New Candidate Name". This click makes the text box accept keyboard data. Key in the words "Functional Tests". "Functional Tests" will appear in the text box labeled "New Candidate Name".
 

4. In the window labeled "Candidates", click on the button labeled "Save". The mouse hourglass will appear while the new candidate is being created. Wait until the hourglass disappears before proceding.
 

5. In the window labeled "Candidates", click on the button labeled "Done". The "Candidates" window will disappear.
 

6. Select the new candidate. This is done on the Diagnostic Profiler's main screen by clicking on the button in the right hand side of the text box to the right of the button labeled "Candidates". This provides a list of candidates. Select the candidate called "Functional Tests" by clicking on it.
 

Step 5 - Define Tests and Measurements
 

1. On the Diagnostic Profiler's main screen click on the tab labeled "Specify Tests And Repairs".
 

2. On the Diagnostic Profiler's main screen in the white area labeled "Specify Tests and Repairs Tool List" there is a list of tools. Double-click on the tool labeled "Specify Tests". This is the first tool in the list. A window labeled "Specify Tests (Functional Tests)" will appear.
 

3. On the upper portion of the "Specify Tests (Functional Tests)" window click on be button labeled "Tests". A window labeled "Tests" will appear. On the "Tests" window the "New" tab will be selected.
 

4. In the "Tests" window, click on the text box labeled "New Test Name". This selects this box for keyboard entry. Key in the name "Functional Tests". "Functional Tests" will appear in the text box labeled "New Test Name".
 

5. In the "Tests" window, click on the button labeled "Save".
 

6. In the "Tests" window, click on the button labeled "Done". The "Tests" window will disappear.
 

7. On the window labeled "Specify Tests (Functional Tests)", select the new test. To do this, click on the button in the right of the test box next to the button labeled "Tests". A dropdown list will appear. Click on the name "Functional Tests".
 

8. Add measurements to the test named "Functional Tests" by clicking on the button labeled "Measurements". A window labeled "Measurements" will appear. . On the "Measurements" window the "New" tab will be selected.
 

(Referring back to the JAST diagram shown in Figure 2-1, the JAST model has three functional outputs, T01, T02 and T03. We will add three measurements to the test, one for each output. )
 

9. In the "Measurements" window, click on the text box labeled "New Measurement Name". This selects this box for keyboard entry. Key in the name "T01". "T01" will appear in the text box labeled "New Measurement Name".
 

10. A list box labeled "All Design Locations" is in the lower portion of the window labeled "Measurements". In that list box, click on the word "JAST.T01". "JAST.T01" will be highlighted. Next click on the button below that text box with the arrow pointing down. "JAST.T01" will disappear from the text box labeled "All Design Locations" and appear in the text box labeled "Selected Measurement Location(s)".
 

11. In the "Measurements" window, click on the button labeled "Save". A mouse hourglass may appear briefly while the new measurement is created. When there is no hourglass, click on the button labeled "Clear". The "Measurements" window will return to the way it looked after step 8.
 

12. Repeat steps 9 through 11 with "T02" substituted for "T01" and "JAST.T02" substituted for "JAST.T01"
 

13. Repeat steps 9 through 11 with "T03" substituted for "T01" and "JAST.T03" substituted for "JAST.T01"
 

14. In the window labeled "Measurements", click on the button labeled "Done". The window labeled "Measurements" will disappear.
 

15. In the window labeled "Specify Tests (Functional Tests)", click on the button in the right of the text box next to the "Measurements" button. A dropdown list of the three measurements will appear. Select the one labeled "T01". The "Specify Tests (Functional Tests)" screen will be updated.
 

16. The "Specify Tests (Functional Tests)" window contains a table with headings "Parts", "Coverage (All Covered)", "Reachable (Both)", "Connection (Both)" and "Failure Rates (All)". The parenthesized text identifies which items are being displayed. The only column that does not display all items is "Coverage" (Among other parts not displayed, it does not display U13). We would like to see all parts. To do so, click on the column header labeled "Coverage (All Covered)". A drop down menu will appear. On the dropdown menu, click on the option box next to the word "All". The dropdown menu will disappear and the table will be updated to show all the parts (including U13).
 

(Note that the "Specify Tests (Functional Tests)" table shows that a failure on part U13 will not show up as a failure in measurement T01 of "Functional Tests" (i.e. U13 is not covered by T01). As indicated by the "No" in the "Reachable (Both)" column, U13 was not covered by measurement T01 during the creation of measurement "T01" because the underlying JAST model does not permit a signal to flow from U13 to JAST.T01 (i.e. T01 was not reachable from U13).)
 

17. In JAST, no U14 fault will show up as a measurement T01 failure. Modify the run time diagnostics to reflect this fact by modifying the table in the "Specify Tests (Functional Tests)" window. To do this, click on the button in the "Coverage (All)" column that is also on the row containing part U14. The check mark on the button will disappear.
 

18. In JAST, the faults that can occur in U16 can sometimes be seen as failures in measurement T01 and sometimes will not be seen as failures in measurement T01. Modify the run time diagnostics to reflect this fact by modifying the table in the "Specify Tests (Functional Tests)" window. First, change the table to show the faults rather than the parts. Click on the table heading labeled "Parts". A drop down menu will appear. On the drop down menu click on the option box labeled "Faults". The dropdown menu will disappear and the table will be updated to display faults.
 

19. In the "Specify Tests (Functional Tests)" window, scroll the table until the four U16 faults U16.1, U16.2, U16.3 and U16.4 are visible. For each of the three faults that have check marks in the "Coverage (All): column, click on the button in the "Coverage (All)" column until a question mark (?) appears on it. The question mark indicates that the fault will sometimes make the measurement fail.
 

Step 5 - Define a Failure Mode
 

When a design is initially imported, all the failure modes are allocated to the design locations and one fault is identified at each design location. Thus, in the initial design a fault can represent several failure modes. If some of the failure modes in a fault will cause a measurement to fail and some will not, you could change the table to use the question mark to indicate the sometimes aspect as shown in items 18 and 19 of Step 4. You can get better diagnostic resolution by dividing the single fault into two or more faults. In this step, you will modify the set of faults in U3.2 to reflect different behaviors for stuck open and stuck closed failure modes.
 

1. For Jast, the output of U3 can fail as Stuck Open or Stuck Closed. The Stuck Open failure mode only causes the "T01" measurement to fail and the Stuck Closed failure mode only causes the "T03" to fail. To add these two faults to U3 and make the runtime diagnostics reflect their different behaviors, enter the "Failure Mode Wizard" by clicking on the button labeled "Failure Mode Wizard" in the window labeled "Specify Tests (Functional Tests)". A window labeled "Failure Mode Wizard - Step 1: Attribute Failure Modes To Fault Locations" will appear.
 

2. In the window labeled "Failure Mode Wizard - Step 1: Attribute Failure Modes To Fault Locations", select the failure modes named "Stuck Open" and "Stuck Closed" in the left list box labeled "Failure Mode Names". To do this, click on "Stuck Open"; then hold down the keyboard CTRL key and click on "Stuck Closed"; and then, release the Ctrl key. Both "Stuck Open" and "Stuck Closed" will be highlighted.
 

3. In the window labeled "Failure Mode Wizard - Step 1: Attribute Failure Modes To Fault Locations", select "U3.2" In the right list box labeled "Faults". To do this, scroll down the list box labeled "Faults" until "U3.2" appears and then click on "U3.2". "U3.2" will be highlighted.
 

4. In the window labeled "Failure Mode Wizard - Step 1: Attribute Failure Modes To Fault Locations", click on the button between the text box labeled "Failure Mode Names" and the text box labeled "Faults". This button is labeled with an arrow pointing to the right. After a little computation, the text box labeled "Faults" will be updated. It will contain two faults at location U3.2. One will be named "U3.2(Stuck Closed)" and one will be named "U3.2(Stuck Open)".
 

5. In the window labeled "Failure Mode Wizard - Step 1: Attribute Failure Modes To Fault Locations", select the two faults: "U3.2(Stuck Closed)" and "U3.2(Stuck Open)". To do this, click on "U3.2(Stuck Closed)" and then hold down the keyboard key CTRL while clicking on "U2.2(Stuck Open)". Both faults sill be highlighted. Next, click on the button labeled "Next->". The labeled "Failure Mode Wizard - Step 1: Attribute Failure Modes To Fault Locations" window will be replaced by the "Failure Mode Wizard - Step 2: Test Mapping" window.
 

6. In the window labeled "Failure Mode Wizard - Step 2: Test Mapping", the text box labeled "Test" contains "Functional Tests" and the text box under it labeled "Measurement" contains "T01". In the table, the two faults that were selected in the preceding window are displayed. Both of them have check marks in the "Covered" column. Remove the check mark from the button at the intersection of the "U3.2(Stuck Open)" row and the "Covered" column by clicking on it.
 

7. In the window labeled "Failure Mode Wizard - Step 2: Test Mapping", modify the mapping for measurement "T03" as follows. Click on the button labeled "Next Measurement->". The text in the text box labeled "Measurement" will change to "T03" and the table will now show the relationship between measurement "T03" and the two faults "U3.2(Stuck Closed)" and "U3.2(Stuck Open)". Remove the check mark from the button at the intersection of the "U3.2(Stuck Closed)" row and the "Covered" column by clicking on it.
 

8. In the window labeled "Failure Mode Wizard - Step 2: Test Mapping", click on the button labeled "Done". A window labeled "Failure Mode Wizard" will appear with two buttons, one for saving the test coverage changes labeled "Yes" and one for forgetting those changes labeled "No". Click on the button labeled "Yes". After some operations whose progress may be shown with a status bar, the window labeled "Failure Mode Wizard - Step 2: Test Mapping" will disappear.
 

9. In the window labeled "Specify Tests (Functional Tests)", click on the button labeled "Done". The window labeled "Specify Tests (Functional Tests)" will disappear leaving only the Diagnostic Profiler main screen.
 

Step 6 - Specify Failure Rates
 

1. On the Diagnostic Profiler's main screen in the white area labeled "Specify Tests and Repairs Tool List" there is a list of tools. Double-click on the tool labeled "Specify Failure Rates". A window labeled "Specify Failure Rates (Functional Tests)" will appear.
 

(As part of the import of the JAST design, each part was given a default failure rate of 1.0 and all the faults on a part were assigned equal rates which together add up to 1.0)
 

2. In JAST, U3 has three (3) times as high a failure rate as the other parts. Change its failure rate to reflect this fact as follows: In the table on the "Specify Failure Rates (Functional Tests)" window, click on the "1" that is at the intersection of the row containing "U3" and the column labeled "Failure Rate". This click prepares that table cell to accept keyboard data. Key in "3". "3" will replace the "1".
 

3. In JAST, the three faults in part U3 all have equal failure rates. At this point they have different failure rates. The faults "U3(Stuck Close)" and "U3(Stuck Open)" have a combined failure rate of the original fault that they replaced (U3.2). Thus each has half of the failure rate of the fault "U3.1". To change the fault distributions, click on the "U3" in the table in the "Specify Failure Rates (Functional Tests)" window. A button will appear on the right side of the table cell containing "U3". Click on that button. A drop-down box will appear showing the relative percent of each fault as follows: "U3.1" is 50%, "U3.2(Stuck Closed)" is 25% and "U3.2(Stuck Closed)" is 25%.
 

4. On the "Specify Failure Rates (Functional Tests)" window in the dropdown box under U3, click on the "50%". The "50%" will be highlighted and will accept data entered from the keyboard. Key in "25" to make that fault have the same failure rate as the other faults. When this is done, click on the button to the right of the table cell containing "U3". A window labeled "Percentage of Part Failure Rate" will appear.
 

5. In the window labeled "Percentage of Part Failure Rate", click on the button labeled "Normalize". This button will preserve the equality of the fault failure rates but change the numbers to add up to 100%. The "Percentage of Part Failure Rate" window will disappear.
 

6. In the window labeled "Specify Failure Rates (Functional Tests)", click on the button labeled "Done". The window labeled "Specify Failure Rates (Functional Tests)" will disappear leaving only the Diagnostic Profiler main screen.

Step 7 - Testability Analysis
 

1. On the Diagnostic Profiler's main screen click on the tab labeled "Testability Analysis".
 

2. On the Diagnostic Profiler's main screen in the white area labeled "Testability Analysis Tool List" there is one tool labeled "Testability Analysis". Double-click on that tool. A window labeled "Testability Analysis (Functional Tests)" will appear and on top of it will appear a window with three buttons labeled "Testability Analysis".
 

3. In the window labeled "Testability Analysis" click on the button labeled ""Run Calculations". After some computations are made whose progress is shown via a status bar, the "Testability Analysis" window disappears and the "Testability Analysis (Functional Tests)" window will be filled with data.
 

4. The first order of business is to determine why the Fault Detection Summary is not 100%. To do this, click on the option box labeled "Non-Detectable" on the "Testability Analysis (Functional Tests)" window. The Table under "Ambiguity Groups" will be updated to show that there is 1 part which contains 7 faults that are not detectable.
 

5. In the window labeled "Testability Analysis (Functional Tests), click on the cell of the table in the column labeled "Faults". A button will appear in the right part of the cell. Click on that button. A drop down list identifying the seven JAST test points, TP1, TP2, TP3, TP4, TP5, TP6 and TP7 will appear. Since in JAST, none of the connectors can fail, we should make a note to ourselves to eliminate them as faults by setting the failure rate of the part "Jast" to zero (0).
 

6. Our next order of business is to investigate the diagnostic resolution (number of parts that could account for a pattern of measurement failures and successes). To do this, click on the option box labeled "Detectable" on the "Testability Analysis (Functional Tests)" window. The Table under "Ambiguity Groups" will be updated to show that for 36% of the failures detected, the diagnostic resolution will be to 9 parts and that for 24% of the failures detected, the diagnostic resolution will be to 8 parts and so on.
 

7. In the window labeled "Testability Analysis (Functional Tests), click on the cell in the top row of the table in the column labeled "Parts". A button will appear in the right part of the cell. Click on that button. A drop down list will appear that identifies the list of parts that would cause the same pattern of measurement passes and failures. The list includes JAST, U1, U10, U11, U2, U4, U5, U6 and U8. We should make a note to reduce these groups by adding measurements that are only sensitive to some of the failures in that list.
 

8. In the window labeled "Testability Analysis (Functional Tests)", click on the button labeled "Done". The window labeled "Testability Analysis (Functional Tests)" will disappear leaving only the Diagnostic Profiler main screen.
 

Step 8 - Attach ACompleted JAST@ Project To The "Samples" Work Area
 

In order to keep the Quick Start short, additional changes have been made to the Jast diagnostic specification and data has been added to support demonstration of the Diagnostic Profiler's verification and validation function. The results of these changes and additions have been saved in the PROFILER_DIRECTORY\Samples directory as a project named "Completed JAST". This step will make the "Completed JAST" project available for your use in Quick Start.
 

1. On the Diagnostic Profiler's main screen, click on the button labeled "Project". A window labeled "Projects" will appear that supports changing the list of projects in a Work Area.
 

2. In the window labeled "Projects", click on the tab labeled "Attach" to make an existing project accessible to the Work Area "Samples".
 

3. In the "Select Project Directory" Box of the "Projects" window click first on the folder labeled "Profiler", then on the folder labeled "Samples" and then on the folder labeled "Completed JAST". The words "Completed JAST" will appear in the text box labeled "Project Name"
 

4. In the window labeled "Projects", click on the button labeled "Attach". The mouse may briefly change to an hourglass. Wait for it to turn back to a pointer.
 

5. In the window labeled "Projects", click on the button labeled "Done". The window labeled "Projects" will disappear.
 

6. Select the newly attached project. This is done on the Diagnostic Profiler's main screen by clicking on the button in the right hand side of the text box to the right of the button labeled "Project". This provides a list of projects. Select the project called "Completed JAST" by clicking on it.
 

Step 9 - Generate A Runtime Diagnostic Knowledge Base
 

1. On the Diagnostic Profiler's main screen click on the tab labeled "Generate Run Time".
 

2. On the Diagnostic Profiler's main screen in the white area labeled "Generate Runtime Tool List" there are the names of two tools. Double-click on the tool labeled "Generate Runtime Diagnostic Knowledge Base". A window labeled "Status" will appear and will show the status of the generation process. When the "Status" window disappears, the runtime Diagnostic Knowledge Base has been generated.
 

Step 10 - Exercise The Runtime Diagnostic Knowledge Base
 

Once we have generated a Diagnostic Knowledge Base, we need to verify and validate its diagnostic accuracy and, if appropriate, the order in which it selects tests and the number of tests it requires to make a diagnosis. Verification and validation of diagnostic accuracy needs to be done against real test and measurement data. Any diagnostic discrepancy turned up by this data is analyzed using the "Diagnostic Verification and Validation Tool". When real data is not available, we use the "Maintenance Exerciser" to emulate real operations and evaluate the test sequencing constraints in the Diagnostic Knowledge Base. In this step we will demonstrate the operation of the Maintenance Exerciser.
 

1. On the Diagnostic Profiler's main screen click on the tab labeled "Diagnostic V&V".
 

2. On the Diagnostic Profiler's main screen in the white area labeled "Diagnostic V&V Tool List" there are the names of two tools. Double-click on the tool labeled "Maintenance Exerciser". A window labeled "Maintenance Exerciser for Diagnostician 4.?.?m Windows 95 / NT" will appear.
 

3. Evaluate the diagnostic performance of the "Completed JAST" Diagnostic Knowledge base for the case where a fault occurred at location "U11.4". Use the "Maintenance Exerciser for Diagnostician 4.?.?m Windows 95 / NT" window to make the evaluation as follows: Click on "U11" in the list box labeled "Failure Events". "U11" will be highlighted. Observe that "All Tests" is already highlighted in the list box labeled "Test Scenarios". Start the simulation by clicking on the button labeled "Simulate". The text box labeled "Status" will flick through several messages and end by saying "Scenario Simulation Complete"
 

4. Evaluate the precision of the simulation just completed by observing the data that is available in the "Maintenance Exerciser for Diagnostician 4.?.?m Windows 95 / NT" window. Observe that the text box labeled "Suspect Count" has a one in it and that there is one suspect "U11" in the list box labeled "Suspect Parts List". Check the suspect faults by clicking on the option labeled "Faults" in the box labeled "Select Information To Display". A list box labeled "Suspect Faults List" will replace the list box labeled "Suspect Parts List". It contains the fault "U11.4". The diagnosis is exact.
 

5. Evaluate the measurements used in the simulation just completed by observing the data that is available in the "Maintenance Exerciser for Diagnostician 4.?.?m Windows 95 / NT" window. Check the measurement values by clicking on the option labeled "Measurements" in the box labeled "Select Information To Display". A list box labeled "Measurements Made List" will replace the list box labeled "Suspect Faults List". It contains 5 measurements: the 3 "Functional Tests" measurements, the "Test Point 3" measurement and the "Test Point 4" measurement. As an engineer who knows JAST well, you observe that the value of these measurements is what you expect (If it isn't, you will correct the test specifications).
 

6. Evaluate the tests used in the simulation just completed by observing the data that is available in the "Maintenance Exerciser for Diagnostician 4.?.?m Windows 95 / NT" window. . Observe that the text box labeled "Tests Count" contains a 3. Check that the sequence in which these three tests are used is valid by clicking on the option labeled "Tests Used" in the box labeled "Select Information To Display". A list box labeled "Used Tests List" will replace the list box labeled "Measurements Made List". It contains the three Tests used in the order in which they were requested. If the test "Test Point 3" or "Test Point 4" had appeared before the test "Functional Tests", you would need to add sequencing constraints to the Diagnostic Knowledge Base.
 

(Note: refer to Section 8 to find out how to add fault events and Test Scenarios to the list available to be simulated as well as how to utilize the other options and features of the Maintenance Exerciser)
 

Summary