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.2 Set Up Test Type Packages Screen
The Set Up Test Type Packages screen (see 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.
1.3 Adding New Test Types
To add a new test type to your database you must first copy the required library file “TaskList.bpl” into the folder labeled “bin” under the ProCalV5 directory (typically “C:\Program Files\Prime Technologies\ProCalV5\bin”) in Windows Explorer. The “TaskList.bpl” file contains all the information necessary for the test type’s automatic and proper setup in ProCalV5. Once the file has been copied into the correct folder you may launch the Set Up Test Type Packages screen. From the Home screen in ProCalV5 select FILE → System Options. From this screen select FILE → Set Up Test Type Packages…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 “TaskList.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.
1.4 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 “TaskList.bpl” file must be present in the “bin” directory one level down from the ProCalV5 installation directory.
2.1 Entering Item Records Using The Task List, Test Type Package
When creating a new master record that uses the Task List, 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 Task List from the available test types, as shown in Figure 2:
This new Test Type Package for ProCalV5 will be available to supply and record a list of tasks for maintenance or calibration-related maintenance steps to be recorded on a Calibration record. Each test point will be a “Task”. During Calibration the user can check off whether a task has been completed successfully or not, along with recording a brief comment for each one. The test type inputs used in this test should be entered through the Group Options box, which can be accessed by clicking the Show Group Options button on the right side of the screen. This interface is shown in Figure 3.
The inputs are as follows:
Fail if Step Fails - “Yes” or “No”. [blank = No] – If “Yes” then if the user does not successfully complete each step the test will fail. Otherwise, the test will always pass.
Fail if Step Skipped – Yes” or “No”. [blank = No] – If “Yes” then if the any step has a “Failed” status then the test will fail. Otherwise, the test will always pass.
User will use the Description column to describe each step, and use “# of Rows” to generally enter how many Steps they want to use. User will configure the [Fail if step skipped] and [Fail if step fails] options to their desired behavior. If a Step should span multiple rows in the grid, the steps will be concatenated together with the next grid row if it ends in the “>” (greater than) character. For example the second thru fifth rows in the example above will be concatenated to read the following:
Locate the condenser coils on top of the unit if applicable.
Using a vacuum cleaner or compressed air, remove the
dust and debris from on and around the coils.
This is when # of Rows can be increased to increase the capacity of each step, using the step concatenation character.
Note: There is no limit to the number of characters that can be entered using the “>” symbol, but due to restrictions in ProCalV5 only 255 characters will show on the calibration screen when the user presses the “View/Enter” button.
3.1 Entering Calibration Records for Items that use the Task List Test Type
Once a calibration has been created for a master item record that uses the Task List Type, the calibration data can be entered on the Test Results tab. The Calibration screen is shown in Figure 5 below. It should be noted that the required inputs must be entered on the master item record as detailed above.
The Data for the test points may be modified on the Test Results tab, which can be viewed by clicking the View / Enter Data button on the left side of the screen. This interface is shown in Figure 5a.
A grid will display each step as a row with the step number on the far left.. Corresponding to each step will be a drop-down field with the available [Step Result X] values with heading “Result”, along with a text column available for data entry labeled “Comment” for receiving and displaying [Step Comment X]. There are no calculations for this test other than the concatenation of steps ending in “>”.
The logic ignores “>” characters from this process if they are not the LAST character (excluding whitespace) of a given Description value.
The form will contain 2 buttons:
- Apply – Sets all outputs on the calibration record. (Note this does not save the data to the database. Hitting the “Save” button on the calibration is required for this)
- Close – Closes the input form. If there have been modifications the user will be prompted if they want to “Apply” before closing.
3.2 Pass/Fail Criteria
For the test point group to pass the following must be true:
As Found Result: Always set to “Pass”
As Left Passed:
If configured to have [Fail if step skipped] set to “Yes”, then the test will be set to “Fail” if any [Step Result X] is equal to “Skipped” or “Blank”.
A completed calibration report is included to display each step with its result and optional comment in a grid.