Log book entries are time based events. They can be generated manually or automatically.
Note |
|
|---|---|
 |
To enable system events to be viewed and custom events to be created, the logged in user must have logging privileges. |
A log can contain multiple comments, e.g. created by different users.
Log level
Events are linked to a log level, which provides information about the severity of an event. The log level also enables you to filter very effectively to find the most important messages. The following log levels are used for the events:
|
ID |
Level |
Description |
|---|---|---|
|
1 |
Info |
Information messages that do not indicate abnormal behavior. |
|
2 |
Anomalous |
Warning (information), indicates an abnormal state. No immediate action is required. |
|
3 |
Critical |
Highest level of severity; these events should definitely be followed up |
Log types
Log types are helpful for grouping related log messages. iba AG recommends using the following log types according to the description:
|
Log types |
Description |
|---|---|
|
Analysis |
Logs regarding data analysis, e.g. if you found anomalies you want to document |
|
Data acquisition |
Logs regarding data acquisition, e. g. sensor defect, interfering signal, no signal etc. |
|
General |
Logs without specific relation, e.g. system was updated |
|
Maintenance measure |
Logs regarding maintenance actions, such as motor changed, bearing oiled, oil changed |
Log status
The status can be used to document the processing of an entry.
|
Log status |
Description |
|---|---|
|
Open |
Each new entry gets automatically the status "open". |
|
Planned |
The entry was noted, and a course of action was planned. |
|
In progress |
Somebody is working on the issue. |
|
Under observation |
Observing the root cause of the entry/analyzing the problem |
|
Recommendation given |
The issue of the entry was analyzed and a recommendation for further actions was given to the operator |
|
Done |
Problem solved/issue closed; no further action required |
Tags
You can use tags to categorize and label log entries by topic, for example. A single entry can be assigned multiple tags. There are some predefined tags that you cannot modify. However, you can define your own additional tags in the system settings.
|
Tag name |
Recommended use |
|---|---|
|
CM-System |
Issues regarding the CM-system |
|
Lubrication |
Events, actions, issues regarding the lubrication |
|
Measurement signal |
Issues or actions regarding sensors and signal quality |
|
Mechanics |
Mechnical issues like imbalance, bad alignment etc. |
|
Replacement |
A component, component group or aggregate was replaced |
|
Trend |
In case of increasing, decreasing or instable trends of indicators |
|
Wear |
Wear or defects of mechanical components |
|
Test |
For testing purposes |