The Maintenance Setup screen is setup as a Startup Task, and therefore opens when Valuekeep is started with an Administrator profile. From this screen you can set the Reporting Currency, the Default Work Center and the Default Access Level. Please note that the Reporting Currency can only be changed if no document has been created.
When creating Assets or Locations, the values setup in the Maintenance Setup screen will be used if the Work Center and the Access Level are not specified by the user. This behavior is valid for all Asset or Location creation methods, either through the Asset or Location creation screen, corresponding WebAPI methods or Batch Load Sessions.
If you want this screen to stop being a Startup task, unselect the Startup Task field on that same screen.
The “Structure Required” field indicates whether the structure is necessary to create assets and locations. This field cannot be changed if asset and locations have already been created.
The “Is Function Family Association” field indicates whether assets are required to be associated with a family from the location functions. This field cannot be changed if asset and locations have already been created.
The “Allocate Cost to CC(asset/loc)” field specifies which cost center will be suggested when reporting labor. If this field is enabled, the cost center from the asset or location for which you are reporting costs will be the one suggested. If it is not enabled, the work order’s cost center will be suggested, if available.
FAQ
Multi-Currency
Valuekeep is ready to handle several currencies simultaneously so that you can record, process and view reports with currency information in several currencies.
This functionality is generally designated as “multi-currency support”.
There are some concepts which need to be explained:
Multi-currency concepts
Transaction Currency: This is the currency the user selects when recording a specific transaction/document or business entity and it affects all the currency fields of the entity being created.
Base Currency: It is the application’s standard or “default” currency. It is set only once when subscribing or installing and it cannot be changed. Usually, this currency reflects the subscriber’s nationality. This currency is important since, if there is no indication otherwise, the displayed or requested currency fields are in the base currency. Besides, all stored currency fields, regardless of the transaction currency, are also kept in the base currency along with the corresponding exchange rate and becoming, as such, “frozen” in time. This exchange rate may or may not be available for editing when the transaction takes place; the exchange rate used, which cannot be set by the user, will be the one in force when the transaction takes place.
Reporting Currency: The reporting currency is an alternative currency whose purpose, as the name indicates, is to allow for viewing reports of information in a 3rd currency. Just like the base currency, the reporting currency is set only once when subscribing or installing. All currency values are also converted and kept in this currency, but, unlike with the base currency, the values in the reporting currency are always converted using the current exchange rate which, besides never being directly available for editing, is also not stored.
ISO Symbol: In all situations in which a currency field is displayed or requested, the user can quickly identify the currency with which that field is associated through the displayed ISO symbol.
How to validate the daily Preventive Maintenance recalculation
Preventive Maintenance events recalculation is a daily process that recalculates all preventive Maintenance events. To validate that it runs for all preventive maintenances or for a specific one, follow these steps:
Validating that the daily recalculation was executed
- Open Maintenance Configuration;
- Select the “Preventive Maintenance” tab;
- Check if the “Enable Event Rescheduling” option is selected;
- Check the date of the next execution:
- If the process was executed without errors, the date of the next execution must be at 00:00 the following day (default value);
- If it was executed with errors, the date of the next execution must be 2 hours after the last attempt (default value);
- Analyze the record of the last execution to check which preventive maintenances were recalculated correctly, and if there was an error.
Sending a notification when errors occur in the daily recalculation
To be automatically notified when errors occur in the daily recalculation, follow these steps:
- Open Maintenance Configuration;
- Select the “Preventive Maintenance” tab;
- Set the events notification.
This notification is only sent when a recalculation error occurs. No notifications are sent if the process runs without errors.
Validating that a preventive maintenance recalculation was executed
The following fields can be added to the preventive maintenance list:
- Result of Last Scheduling
- Date of Last Scheduling
- Log of Last Scheduling
With these fields you can check if the events recalculation was executed without errors for a preventive maintenance. The automatic recalculation process updates these values whenever it is executed.
Forcing the recalculation of a preventive maintenance
The “Schedule” option available on the Preventive Maintenance file allows you to force the recalculation of a preventive maintenance. After selecting this option, validate the outcome using the information fields on the last scheduling of preventive maintenance or the events list.
This option is only available for preventive maintenances in the “Approved” state.