Performance Characteristic Entry is used for the central recording of actual values defined in the Object Monitoring Lines – i.e. counter readings, threshold values and consumption values. Data can be recorded via a Work Order with a checklist entry or via the Performance Characteristic Journal. Posting via the journal is the standard method and is described below.
Opening the Performance Characteristic Journal
Use the "Tell Me" search (Alt+Q) for Performance Characteristic Journals to open a list view if multiple journal templates exist. Select the desired template; the STANDARD template is used in most cases.
After selecting the journal name, an empty journal line is displayed.
Filling in the Journal Line
Entries are made from left to right. Mandatory fields are described in the table below (optional fields are shown in italics):
| Field Name | Description / Information |
| Posting Date | Filled in automatically; can be overwritten. |
| Document Date | Filled in automatically; can be overwritten. |
| Entry Type |
|
| Document Number | Must be filled in manually if no number series has been assigned to the journal name. |
| Type | Component Address, Technical Component or Vehicle |
| No. | Code of the technical object |
| Description | Filled in automatically; can be overwritten. |
| Line No. | Select the desired line of the Object Monitoring Template |
| Actual Value | The value to be recorded |
| Total Value | Filled in automatically. |
Example of a completed journal line:
| For counter readings, the Monitoring Template Code column must not be filled in (the column may be hidden). The Line No. of the Object Monitoring Template must always be selected. |
Posting and Verification
Click Post to post the counter reading. In the case of inheritance, multiple Performance Characteristic Entries are created. The journal line is deleted after posting.
To verify the posting: Related > Line > Entries opens the Performance Characteristic Entries list view. Use the filter icon (top right) > View: All to adjust active filters. Click Entry No. to sort ascending or descending.
Alternatively, entries can be checked directly from the Technical Component: More Options > Related > Technical Component > Entries > Performance Characteristic Entries.
Function "Read Object Monitoring Lines"
For recording a large number of values simultaneously – e.g. after an inspection round – the read function is available directly in the Performance Characteristic Journals.
In the Options tab, the entry types Post Value and Cancel Value are available.
The additional tabs provide extensive filter options to narrow down the displayed technical objects.
| maintool does not provide checkboxes to filter exclusively by object type (e.g. Technical Components only) or by data type (e.g. counters only). A suitable filter criterion must therefore be defined for each tab. It is recommended to define clear and practical filter criteria for each technical object. |
If no filters are set, all technical objects with defined Object Monitoring Templates are displayed. The following screenshots show an example filter for the component group "Pump":
Filter result:
After reviewing the filter results, enter the values to be recorded in the Actual Value column. Click Post to complete the entry.
Entry Types "Change Value" and "Cancel Value"
Change Value reverses the last posted value and posts a new one. The last current value is displayed in the footer until the posting is confirmed.
Reverse Value reverses only the last posted value. If multiple postings need to be reversed, the cancellations must be entered and posted one at a time. The posting date should be carefully checked before each posting.
Entry type Change Value before clicking Post:
Entry type Reverse Value before clicking Post:
Performance Characteristic Entries after multiple reversals:
Notes
The read function is particularly effective for bulk entry of performance data. The filter options are extensive – it is recommended to define clear filter criteria for each technical object.
maintool only supports numerical values for condition monitoring. Text-based status descriptions such as "OK" / "Not OK" must be converted to numerical values (e.g. 1 / 0).
For vehicles, self-inheritance of performance data is already supported: a single counter reading updates all associated Object Monitoring Lines. This function is not yet available for Technical Components and Component Addresses – please contact support if required.
Only the last open entry can be cancelled at any time. Multiple cancellations must be carried out one after another.
Re-posting an already posted value is possible but must be explicitly confirmed in a prompt.
Entries in journal lines are only saved when Post is clicked. Clicking OK closes the journal without posting. Entries are retained until the journal is reopened.
If an End Value is stored in the Counter tab, maintool automatically detects a counter rollover. If a warning message should appear instead when a smaller value is entered, no end value should be stored in that field.
Related to