The Performance Characteristics Acquisition is used for the central storage of the data defined in the object monitoring lines, i.e. the actual values of the linked Counter Readings, Threshold Values or Attrition Values.
Performance Characteristics can be acquired in two ways:
- Entry via a work order and a corresponding checklist entry
- Entry via the Performance Characteristics Journal
The latter approach is mostly used and is therefore explained below:
When searching for „Performance Characteristics Journals“ a List of Journal Templates appears, if several Templates exist. The Template and, if necessary, the desired “Batch Name” must be selected, in which the entry is to be recorded. As a rule, the “STANDARD” Journal of same name is used.
After selection, an “empty” Journal line is displayed.
In the first line of the Performance Characteristics Journal required entries are recorded from left to right. The following table explains the most important fields (fields in italics are not mandatory fields):
Field Name | Description / Information |
Posting Date | will be filled automatically and can be changed manually |
Document Date | will be filled automatically and can be changed manually |
Posting Type | The choices are:
|
Document No. | Can be filled manually, if no „No.-Series“ has been selected for the Performance Characteristics Journal |
Type | The choices are:
|
No. | Selection of Technical Object Code |
Description | will be filled automatically and can be changed manually |
Line No. | Selection of desired Object Monitoring Template Line |
Actual Value | The Value to be recorded must be entered |
Total Value | will be filled automatically |
Example of a completed line of the Performance Characteristics Journal:
Note:
- In case of a Counter Reading the “Monitoring Template Code” Column must not be filled in (Column eventually hidden).
- The “Line No. (Object Monitoring Line)” must be selected (see Table above)
With the „Post“ Button, the Counter Reading must be posted, creating at least one or, in case of inheritance, several Performance Character Ledger Entries. The Performance Characteristics Journal line is deleted.
To check the performed posting, the list of Ledger Entries can be opened by clicking on “More Options”, Navigate”, “Line” and then “Ledger Entries”. The current filter can be viewed by clicking on the filter icon in the upper right corner, then “Views: All” and “Show system filters” and modified, if needed.
By clicking “Entry No.”, the current view can be sorted in ascending or descending order.
Alternatively, the performance Characteristics assigned to the technical component can be checked as follows:
Open the technical component and click on "More options", "Navigate", "Technical Component", "Ledger Entries", "Performance Characteristics Ledger Entries".
„Import Object Monitoring Lines“ Function
The “Performance Characteristics Journal” has a “Import Object Monitoring Lines” function for simultaneously acquisition of a large number of different data.
This function can be used, for example, if counter readings are to be transferred regularly after an inspection walkway. For this purpose, the technical objects, that are to be updated with the values to record, can be listed in a filtered table first. Finally, the entered performance characteristics can be posted in one step.
This function is directly available at the “Performance Characteristics Journal”.
In the „Options“ Tab, the posting types „Post Value“ and „Reverse Value“ are available for selection.
In the other tabs, comprehensive filtering options are available to reduce the number of displayed results to the desired technical objects in the best possible way.
All table fields of the respective technical objects are available as filter criteria, which can be combined with any number of "AND Operations".
If no filters are selected, all Technical objects are displayed, for which one or more Object Monitoring Template Definition/s exist.
MAIN-TOOL does not provide any checkboxes for these filter options, with which e.g. only technical components or the data type of the object monitoring line, e.g. only Counter Readings could be filtered. Thus a target-oriented criterion must be defined for each register, as shown in the following example.
The figures of the example show a filtering to determine the main components of the component group "Pump" without vehicles and without Component Addresses. The following conditions are assumed:
- There are no Vehicles and Component Addresses belonging to the component group "Pump".
- The searched main component of the component group "Pump" is located in level 1 of the technical components in the Equipment Structure.
The Result is displayed as follows:
It is recommended to check, if the Read-In Lines correspond to the desired result. Then, the values to be recorded, must be entered to the column “Actual Value”.
Clicking on “Post” completes the Performance Characteristics Acquisition.
Further Posting Types – „Change value“ and „Reverse Value“
- „Change value“ cancels the last posted value and posts a new value. Until the posting is executed, the last current value is displayed in the footer.
- „Reverse Value“ cancels the last posted value. If several postings are to be reversed, these reversals must be entered one after the other and posted step by step. It is recommended to check the selected booking date before each booking.
Following figures show entries for posting the posting types “Change value“ and „Reverse Value“.
Posting Type „Change Value“ before clicking on „Post“:
Posting Type „Reverse Value“ before clicking on „Post“:
Performance Characteristics Ledger Entries after several reversals:
Concluding Notes to this manual
- The „Import of Object Monitoring Lines“ function is an effective option, to record many
Performance Characteristics in one step. The filter options are very extensive and might take some getting used to, so it makes sense to define clear and practicable filter characteristics for each technical object for which performance characteristics are to be recorded, in order to be able to carry out the filtering as easily as possible.
- MAIN-TOOL supports only numbers to record a status. This means, that any status messages used in daily operation in the form of text information, such as “OK” and “Not OK”, must be converted into numerical values if these states are to be recorded as performance characteristics.
- For Vehicles, MAIN-TOOL already supports inheritance of Performance Characteristics to itself. Example: For a vehicle, the milage indicator is defined as a criterion for different maintenance. Since the inheritance of the counter to itself is possible, the current counter reading only has to be posted 1x to update the various object monitoring lines for the different maintenance. This function has not yet been set up for Technical Components and Component Addresses. Should this be required, please contact our support.
- Only the last open posting can be reversed. If several postings are to be reversed, these reversals must be entered one after the other and posted step by step. The Posting Date and current Value must be checked or selected with particular care.
- Re-posting of an already posted value is possible but must be explicitly confirmed in a query message.
- Entries in the posting lines are only posted by clicking on „Post“. “OK“ does not trigger a posting but closes the Performance characteristics Journal. However, the Entries in the posting lines will be retained until the Performance Characteristics Journal is reopened.
- The entry of a “Ultimate value” in the Counter Tab of the Card Page of the object monitoring leads to the fact, that MAIN-TOOL recognizes, when the counter starts counting from the beginning. I.e. with each posting of performance characteristics, that have a smaller counter reading than the last posted value, it is assumed that the Counter has reached the end value and starts counting from the beginning. In order to force a message to appear if a smaller value is to be posted, no “Ultimate value” must be entered at the mentioned field and by this, entries of smaller and thus possibly incorrect values can be recognized.
Comments
0 comments
Article is closed for comments.