Using the Audit Trail
- Last UpdatedMay 14, 2025
- 6 minute read
After the Audit Trail function has been Audit Trail activation you can open the Audit Trail window by going to menu Extra -> Audit Trail.
Note: The option Audit Trail - field level details is explained below.
Opening the Audit Trail window
A new window will be opened that looks like the image displayed below. This window displays all of the changes that have been made in Asset Strategy Optimization. The window is not linked to the application, so it is possible to keep the window open while actively working in the Asset Strategy Optimization software. With the button 'Retrieve log' you can refresh the audit trail data. The refresh is not done automatically.
Audit Trail window (using Extra > Audittrail)
Another option is to retrieve the information of a single object in an FMECA system. In order to do so use the right mouse-button in the shortcut window from one of the objects in the FMECA screen.
-
Audit Trail from a separate object
The option History will only show the history of the selected object. This can be a complete model or folder (left part of the screen) or a system, part, component, failure mode or maintenance action (right part of the screen). if the audit trail is opened from the context menu, only the Audit Trail information from the selected object will be shown. When the Audit Trail is accessed by using the menu and then 'Extra' the underlying objects their information will be displayed.
-
Audit Trail from an FMECA System
The option System History will show the Audit Trail data of all the changes in a recursive way for the objects related to the selected FMECA system.
Audit Trail information
The Audit trail screen is empty at the start, until you select Retrieve log. After selecting this option the data will be retrieved and filtered based on your settings at the top of the screen. The following variations are possible:
The filter option for the separate object or the FMECA system are as follows:
-
From the start of the application - all the data will be shown that has been changed from the moment Asset Strategy Optimization has been started
-
From a specific date - all the data will be shown that has been changed after the specified data (instead of option 1)
-
Until now - all the data will be shown that has been changed until now by pressing Retrieve log
-
Until a specific data - all the data will be shown that has been changed until the specified date (instead of option 3)
Audit Trail data from an object in an FMECA system
|
FIELD |
DESCRIPTION |
|
Log id |
A unique number that shows the id for this log item |
|
User |
The user that made the change for the given rows in the log |
|
Action |
The action that was executed on your FMECA data (see below)
|
|
Level |
The level on which the action was executed |
|
Data Type |
The type of object that the action was executed on |
|
Description |
The name of the object the action was executed on |
|
Database Id |
The id of the object in the database |
|
Model Id |
The model which the action was executed against |
|
Model |
The name of the model which the action was executed against |
|
Context |
Displays the type of change or how the change was done |
|
Date |
The date of the change on the object |
Filter on User
When the Audit Trail screen is opened from the menu: Extra > Audit Trail it is possible to filter on users, if you have the right authorization for this action. You can filter on one or more users or view the changes made by every user.
Pass through (F9)
By clicking the right mouse-button you can open a context menu with the option Pass through. With this option (or by using the F9 key) on the selected log row you can immediately pass through to the selected tree object. This option works exclusively for objects that can be found in a tree structure.
Show detailed changes
For Updates of FMECA objects the Audit Trail only shows the fact that the object was updated. To see what changes were made exactly, the user may double-click the row in the audit trail table. This will display a new screen containing changes on field level. What change was made can be read by comparing the columns 'Old Value' and 'New Value'.
Note: Asset Strategy Optimization sometimes also updates other fields when the user changes a property of an FMECA object, e.g. setting initial values, to ensure data integrity. These automatic changes will also be stored in the audit trail, and thus appear in the field level window.
Export to Excel
By using the Excel Export button you can export the shown log data to an Excel file.
The Audit trail - Field level data window
By going to menu Extra -> Audit trail - Field level details it is possible to filter the shown data. It is possible to, unlike the Audit Trail window which shows all of the logged data, filter on field level on FMECA object types in the Audit trail - Field level details.
Description of the window
|
FIELD |
DESCRIPTION |
|
Miscellaneous |
The miscellaneous part of the screen allows you to select your filter for the timespan of the log data and on which FMECA objects you want to see log data |
|
Query |
The query field in the screen shows the timespan and fields that you have selected for specific FMECA objects |
|
Fields |
The bottom part of the screen shows the results from your query on the log data. This is similar to what is shown in the Audit trail dialog |
Creating queries on audit trail log data
In case you want query data in a specific timespan (click button) you can drag the timespan text to the query field. This results in a text such as 'the object is changed between <date> and <date>'. By clicking the pencil icon that is in front of the text you can adjust the from and until date. The next step is to select the object type from which you would like to have the data. By clicking the arrow-down icon a list will appear with the possible objects/fields that can be selected. By dragging 'all fields' from for example components to the search command window will result in all of the changes in all fields for the object type component. It is also possible to drag one or multiple fields from an object, for example 'buffering time' to view all the changes related to that specific object.