Test Omission Test Type

Test Omission Test Type
 

Section 1

 

1.1 Test Types

ProCalV5 allows for the addition of different “Test Types” to the database that may be applied to any item master record whose required calibration does not fit perfectly into the typical ProCal template.  Test types may be used to provide specific testing in addition to or instead of a standard calibration with target set points and as found/as left readings.  Examples of some calibration test types that ProCalV5 normally could not accommodate efficiently are extreme values, linearity and standard deviation tests.

1.1.1 Set up Test Type Packages Screen

The Set Up Test Type Packages screen (shown in Figure 1) is used to add, modify and if necessary delete test type packages from the database.  This screen is invoked by selecting the “Set Up Test Type Packages…” option on the File menu when the System Options and Defaults screen is open.

 

 

                                                                                                                                                        Figure 1

1.1.2 Adding New Test Types

To add a new test type to your database you must first copy the required library file “TestOmit.bpl” into the folder labeled “bin” under the ProCal V5 directory (typically “C:\Program Files\Prime Technologies\ProCal V5\bin”) in Windows Explorer.  The “TestOmit.bpl” file contains all the information necessary for the test type’s automatic and proper setup in ProCal.  Once the file has been copied into the correct folder you may launch the Set Up Test Type Packages screen.  Once the screen is open you may click the Add New Record button or select “New Record” from the screen’s File menu.  This will invoke a browser screen titled Choose New Package File that automatically directs you to the “bin” folder in which all the “.bpl    ” files reside. Select the required file “TestOmit.bpl” and click the Open button or double-click the file name.

 

Once the correct file has been selected you will be returned to the new test type record which will already be set up for you.  In this instance you can save the record, making it available for application to all types of item master records in the system (i.e. instruments, loops, systems, test instruments, in addition to any PM records that may require a calibration).  Once a test type has been saved to the database, as long as it is marked as “Active”, it will be available for selection on the Test Type field’s drop-down list on the Calibration Points tab in all screens where that tab exists.  

 

Although you will have no ability to change the test type’s calibration requirements, you do have the ability to make some customizations to it in terms of field label changes and also giving users the ability to edit target setpoints and such when entering calibrations using that test type.  Please reference section 8 of the user manual for information on modifying test type packages once they have been imported into the database.

1.1.3 Distributing Test Types

Test Types only need to be installed in the System Option and Defaults screen once, but for all Client, Administrator, or Mobile Workstations, the “TestOmit.bpl” file must be present in the “bin” directory one level down from the ProCal V5 installation directory.

1.1.4 Entering Item Records Using The Test Omission Test Type Package

When creating a new master record that uses the Test Omission Test Type, the test type must be applied to the record through the Calibration Points tab on the master record screen.  Once a new group has been added to the record, click the Test Type drop-down list and select Test Omission from the available test types, as shown in Figure 2:

Figure 2          

The Test Omission Test Type Package for ProCalV5 allows the user to omit a particular test group from the overall determination of Calibration Pass/Fail.

Test Inputs: The inputs appear for configuration on master record items, and some variables can be edited for entry on the calibration screen during calibration entry.

Found in “Show Group Options” Button in Calibration Points Tab on Master Instrument Records:

Test Performed – if this field is set to ‘No’, no failure fields will be set regardless of other data entered

As Left Entered – List contents: “Yes” “No”; If No is selected, no As Left data-specific failure fields will be set regardless of other data entered. It is disregarded

1.1.5 Entering Calibration Records For Items Using The Test Omission Test Type

Once a Test Point Group has been created for a master item record that uses the Test Omission Test Type, a calibration record can be created and data can be entered on the Test Results tab on the Calibrations screen.  It should be noted that the required inputs must be entered on the master item record as detailed above.  

 

Calculations/Logic:

  • If Test Performed equals “Yes” on the cal record, the test type package code will perform the same checks as the main application code at each test point for As Found failure and set the As Found Result accordingly. If Test Performed equals “No”, set the As Found Result to “Not Entered”.
  • If Test Performed equals “Yes” AND As Left Entered equals “Yes” on the cal record, do the same checks as the main application code at each test point for As Left failure and set the As Left Result accordingly. If Test Performed or As Left Entered equals “No”, set the As Left Result to “Not Entered”.

Seen in Figure 3 below

 

    Figure 3

 

 

1.1.6 Pass/Fail Logic

Pass/Fail:

As Found Failure

Failed if As Found Result = “Fail”

As Left Failure

Failed if As Left Result = “Fail”

1.1.7 Reports

A calibration report that checks for this test type will simply display some sort of “Test was not performed” message instead of detailing the gathered readings when the “Test Performed” value is set to “No”.

 

 
 
Was this article helpful?
0 out of 0 found this helpful

Articles in this section

See more
2024 Client Training Schedule
See the full list of web training events scheduled for 2023. Watch completed training sessions or register for upcoming events.