Operation and Maintenance / Helpdesk 20.18

Improved functionality to use object to do concept for all types of objects and using QR code scanning in the Facility App (EMM-2057)

Now it is possible to give access to the action <Object To Do> in lists, forms and as action for ALL types of objects in the object structures (Sites, buildings, floors, rooms, building components, equipment etc.). NOTE each type of object has there own user administration so user roles must be given access to the action for the different types of objects were they should be able to run this action.

The action <Object To Do> can also be assigned to QR code for object, so that is the action that is triggered when scanning a specific QR code in the Facility App

The action <Object To Do> has also a changed functionality. Previously it only showed the checklists that were directly attached to the object but now it also shows all checklists where the object has one or more checkpoints in the checklists. Also when expanding the checklist, only the points that has to do with the object are shown (unless the checklist belongs to the object, than all checkpoints for all objects is shown as it was previously). The same applies for locations, that is if you open object to do list for a building space you get checkpoints for all objects located in the building space as well as the points belonging to the building space itself.

This functionality makes it possible to go through a building for instance daily rounds and perform To Do points by scanning QR codes on object, get list over To Do points (for different work orders, checklists etc.) for the object and perform/register the result.

A small site note. The Logout possibility now only appears in checklist action and to do action for users that are marked as <Multiple users account>

Work order creation with default data setup (EMM-2248)

These changes were made to improve functionality when creating work order from incident and when work order are automatically created when incident is created (Response demand)

When work order is created from selected incident we wanted to simplify the registration of the work order. Following was added for systems that are set in System settings to have task demanded on work orders

Another demand is that task category is used in task registrations

Finally a mapping has to be done between incident type and task categories

When that is all in place the functionality works as follows when the action <Create work order from incident> is used

Based on the incident type on the incident, the system fetches the task category/task subcategory/profession attached to it

It then searches for an active single task (not recurring) (for the running year) on the location of the incident (searching up the hierarchical location tree). First it searches with all three criterias, if it finds no match it searches for task category/task subcategory. If still no match then it searches only for task category

If it finds an task fulfilling this criteria it is automatically selected in the work order form (but can of course be changed to another task). Also derived fields from task such as Account/Account section/Account activity are automatically selected as well.

The same logic also applies when the system is setup to automatically create work orders for specific incident types through SLA/KPI demand

Possible to set default work order for account (EMM-2100)

Now it is possible to set default account for work order either by selecting the work order in the account form or with a new action <Set as default work order for account> available from the work order list. The action puts the selected work order as default work order on the account it is attached to

Now it is also an option to mark accounts as primary accounts on object and they then are default selected when task is created on the object NOTE: That functionality only applies to systems where account are connected to objects. If an account is marked as Primary account then all other accounts on the same objects loose their marking as primary account, that is only one account can be marked as primary account per object

When task is added for an object that is connected to an primary account (or object above the selected in the object tree), then that account is automatically selected in the form

When tasks are created from standard tasks and the system is set to calculate what account is assigned to the task, then the primary accounts are the first choise.

Action to change task location (EMM-2136)

New multi select action <Change task location> that moves tasks and its connected data to new selected location. The action can be run for one or more selected tasks.

In the action window, the user can then select Site and object. The selected task is moved to the select object/location. Also following data is localized

• Task checklists for task

• Task planned cost for task

• Work orders belonging to task

• Checklists belonging to work orders on task

• Time, material, cost registrations etc. belonging to work orders on task

• Transactions belonging to work orders on task

NOTE the sub data does only change the location if is not below the selected object. For instance if you move task from site level to building A on the same site and some work orders on the task are located on a floor belonging to that building A. Then the work order is not moved.

Simplify time registration on specific work orders (EMM-1996)

By setting the System settings>Operation and maintenance>Only register hours on time registration work orders then in the time registration actions only work orders which have the marking <Time registration work order> appear in drop down as option

Standard action for registering hours

Action for registering hours when using clocking system integration

NOTE. It does not stop that the user can through sub data time registrations register hours on work orders. This is more intended to simplify the selection when using time registration directly from time registration overview

Add or change time registration for others (EMM-2206)

It is now possible to set user role to <Can register hours for others> so that i.e. administrators or team leaders are able to register hours, trips etc. for others.

When that is set, users with this assigned user role can register hours for all other employee in organisations that on company level are marked as <Internal>

Standard action for registering hours

Action for registering hours when using clocking system integration

This also opens up that user can change employee on an existing time registration

Changes to Paymech calculations (EMM-2120)

First, the concept has been changed to fetch the date reported from incident if work is created from incident and put it as Date registered (DateStarted) on the work order. User creating the work order can change the default if needed

Adjustments have been done to how paymech calculations are configured and calculated

For response demand data and response demand availability you can now decide for EACH phase if deadlines are calculated based on number of session or hours. NOTE when using core sessions you should enter numbers without digits

It has also been added possibilities to have up to 5 defined core sessions per weekday. Here below for instance the day includes five sessions

07:00-12:00

12:00-16:00

16:00-20:00

20:00-07:00

The calculations for deadlines for each phase and the calculated deductions take these new configuration possibilities into account. The response demand calculations can as before be verified through the action <Test paymech calculations>

Be able to run calculation of running lost sessions/deduction (Paymech) (EMM-2130)

Three new fields have been added to the paymech calculations. They show the calculated status of lost sessions deductions (for ongoing work orders for the date the last calculation was done)

To do the actual calculations a new multi select action <Calculate running lost sessions> has been added to the work order list. The user can then filter the work order list on the unfinished work orders he wants to get the status of lost sessions/deductions for those.

BUG FIXES

Fix performance issue in the work order (and other) list if the field “Location” is added as search field (EMM-2050)

Fix that checklist template report was sent out empty (EMM-2303)

Fix and change email sending for incidents so it checks the the category of the incident and sends out email for all notification rules of that type if it applies to any. (EMM-2245)

Fix that account is set as default on task from standard task when it should not (EMM-2197)