This description is divided into the following sections:
Mobile Workforce Management is a scalable optimization framework which conducts advanced mobile workforce scheduling.
The integration of Mobile Workforce Management with IFS Applications provides functionality for scheduling work orders to maintenance employees in order to:
Resources (employees) and activities (separate or route work orders) are sent from IFS Applications to Mobile Workforce Management where they are scheduled. The scheduling is conducted based on the following:
Once scheduled, an allocation plan is returned to IFS Applications and the work order can be updated through any of the following methods:
Both inbound and outbound integration use XML messages that are sent and received via standard IFS Connect functionality.
Note: In the Mobile Workforce Management, permission groups define which users are allowed to view a set of resources and activities. These permission groups are called object groups. In the integration, object groups have the equivalence of sites in IFS Applications. This means that in order for a iSWB user to be able to view information like resources and activities belonging to a particular site, the user must be connected to the corresponding object group in the iSWB (Workspace - Administration). The object groups for activities and resources are transferred automatically from IFS Applications to Mobile Workforce Management , but object groups for the users must be set up and granted to the users manually from the iSWB (Workspace - Administration). In order for a user to be able to view a dataset, the user must also be granted to the dataset itself. This also can be done manually in the iSWB.
The following IFS Applications components must be installed in order to use the Mobile Workforce Management integration:
Furthermore, the following solutions cannot be used together with the Mobile Workforce Management integration at the same time by Mobile Workforce Management scheduled sites:
In order for employees to be available in the Mobile Workforce Management, the following data must be defined:
Note that the employee's allocations, such as, absences, training allocations, project allocations, breaks and lunches will be transferred for scheduling to Mobile Workforce Management.
The resource types which are used within a company must be defined. Each resource type can be set up with information on the start and end locations for a work shift, maximum travel hours and costs such as scheduling cost per hour and scheduling cost per overtime hour.
If an employee is to be scheduled by the Dynamic Scheduling Engine (DSE) in Mobile Workforce Management, this employee must be set up as a scheduling resource and valid scheduling data must be entered for this resource. If scheduling data is not defined for a resource it will inherit the data from the connected resource type, for example, the start and end locations of a resource type's work shift and scheduling costs will be assigned to the resource. For the start and end locations the geo-coordinates of the map positions will also be transferred to the Mobile Workforce Management. The skills of a resource will also get transferred to Mobile Workforce Management. The skills can be any of the following:
The scheduling data for a resource can be changed at any time, but updates will only be transferred to Mobile Workforce Management when the next main data load is sent, rather than by incremental updates.
Scheduling activity types should be defined. The following scheduling information can be defined per activity type:
Weight criteria and weighting values should be defined. Weight criteria can be set up for the priority of the work order and the criticality of the equipment object that is connected to the work order. Weight criteria can also be set up for service contract types and will have an effect on the work orders that are connected to service contracts. For each weight criteria define the weighting values that will be used as an input for activity base value calculations.
Appointment values need to be defined and will be used to calculate the base value for activities that are managed as appointments. The base value for an appointment activity, e.g., work order, is calculated by multiplying the base value for the appointment by the activity duration and weightings.
Scheduling types should be set up with values, such as, the start and end proportions and curve shape, that will be used as an input when calculating SLAs (service level agreements) in the Scheduling Engine. The SLA is used to calculate the urgency of an activity. Scheduling types are used when scheduling breaks and activities. Scheduling types when combined with the base value is used to determine the scheduling behavior of a break or an activity.
Datasets are used to transfer data to Mobile Workforce Management. A dataset contains information on how data should be scheduled and the time horizon for the scheduling. There are two types of scheduling that can be carried out, that is, dynamic scheduling or static scheduling. Static scheduling is generally used for long term rough scheduling (e.g., the resource capacity for a year) where data over several weeks can be loaded into Mobile Workforce Management and scheduled for analysis. This type of scheduling is beneficial, for instance, when you need to identify resource shortfalls and over capacity. Dynamic scheduling is used for the short term detail scheduling (anything from 2 to 5 days) and focuses on optimizing the utilization of resources. This type of scheduling provides the best schedule at all times and is continuously scheduled by the DSE to incorporate any event changes in the field of operation. The window the DSE operates in is referred to as the Scheduling Work Days, and an additional window referred to as the Appointment Work Days may be defined. The activities in the appointment window will be scheduled using a less accurate algorithm than those in the scheduling window.
The time horizon for which the data should be transferred and scheduled is the number of days specified in Scheduling Work Days and Appointment Work Days according to the connected calendar. For instance, if the number of days is set to 5 in the Scheduling Work Days and 30 in the Appointment Work Days, the data that should be scheduled per company or site for the given time interval (5 days + 30 days) will be transferred and scheduled by the DSE. 5 days will be optimized using the scheduling algorithm and the 30 days will be optimized by using the appointment algorithm. In the Time Zone, you need to enter in what time zone the dataset should be scheduled, used and displayed. i.e. If you are working in an Australian or American company, you can have one central installation for the complete country and different work dispatchers and service technicians in the different time zone regions, you should have one dataset for each of the time zone regions. When this is correctly set up, you will get the scheduled availability and activities correctly displayed on your own computers, configured with your local regional settings. The following is a list of the data transferred in an active dataset:
Default values for a work order can be entered on the dataset. If a work order is missing any of the required data, such as, the primary scheduling type or the activity type, the default values from the dataset will be assigned to the work order. It is possible to set the lowest status from which work orders in the dataset can be transferred for scheduling. The default values for HR activities should also be entered per dataset and will be used as an input when scheduling the relevant activities in the DSE.
Broadcasts are used to instruct Mobile Workforce Management how and when a plan is to be returned to IFS Applications, and to manage the interface between the Mobile Workforce Management and IFS Applications. Broadcasts can be set up per allocation type. The allocation type indicates which type of data should be output based on its association with the DSE, SDS or iSWB (Scheduling Work Bench). The connection between the broadcast and allocation type is made on the applicable dataset. The type of output generated based on the selected allocation type is further described in the Schedule Work Orders with Mobile Workforce Management section. The same broadcast can be used for both DSE and SDS broadcasts, whereas separate broadcasts are required for ABE and iSWB broadcasts.
For DSE broadcasts, how the plan is to be returned is determined by the broadcast type that is selected. If the broadcast is set up with the File broadcast type, the plan is returned and stored using FTP (File Transfer Protocol) services. If the Webservice broadcast type is selected, the plans will be returned using HTTP (Hyper Text Transfer Protocol) services. The parameters for each broadcast type must be entered when defining the broadcast.
Scheduled tasks are used to transfer datasets to Mobile Workforce Management. It is recommended to have two scheduled tasks set up per dataset, one to transfer all data and another to transfer changes. For more information on how to set up the scheduled tasks, refer to the activity Set up a Scheduled Task for Transferring Data to Mobile Workforce Management.
For more information on the scheduling parameters related to the Mobile Workforce Management Integration please refer to the activity Define Scheduling Configuration
In order to schedule a work order, the work order must be set to the transfer status or a higher status (where the transfer status is set per dataset in Scheduling Dataset/WO Defaults). Before setting the work order to this status however you need to make sure that all information required by the Mobile Workforce Management is present in the work order.
Once the work orders transferred to the Mobile Workforce Management are scheduled, an allocation plan with the current scheduling status, resource assignment and activity start and finish dates is returned to IFS Applications. Depending on the allocation type associated with the dataset, the following will occur:
| Allocation Type | Description |
| DSE | If the work order is allocated by the DSE, the DSE will produce a plan. You can choose to assign or unassign directly on the work order. If the suggested plan does not meet the requirements, you can choose to wait for the next broadcast of the plan or manually schedule the plan in the iSWB. It is also possible to manually assign or unassign a work order in the iSWB. |
| SDS | If the work order is processed by the SDS, the SDS will propose to automatically assign (or unassign) work orders already allocated by the DSE based on the given rules. The work orders that are returned are automatically promoted to the Assigned status and the Executed By field on the work order is set to the suggested employee's ID or demoted to the Released status and the Executed By field is cleared (depending on the SDS decision). The rules for the SDS are set up in an XML file and referenced in broadcast parameters. |
| iSWB | If the work order is manually updated in the iSWB, IFS Applications will be synchronized with the changes made to the data in the iSWB, which is the web based user interface for Mobile Workforce Management. In the iSWB client, a work order can be assign/unassigned, allocated to an employee, fixed to an employee and the start date can be fixed. This is only used to manage exceptions, the DSE and SDS normally deal with allocation and assignments automatically. |
The work orders will be scheduled based on resource skills, cost of scheduling the resource, the preferred resource for the work, the location of the resource and activity, the importance (value) of the activity and the urgency (SLA) on the activity.
In order for a work order to be allocated to a resource the skills of the resource will have to match the skills required by the activity.
The work order will be scheduled in the Dynamic Scheduling Engine until it is set to the Assigned (Committed) scheduling status or transferred to a mobile device, after which it will no longer be scheduled by the DSE. Work orders which are in the Assigned status or a higher status without a value entered in the Executed By field will not be scheduled by the DSE.
If the suggested plan is suitable, assign the work order to the employee allocated by the DSE.
If the suggested plan does not meet the requirements, wait for the next broadcast of the plan or manually change the plan in the iSWB. When the employee is assigned to the work order, the status of the work order is automatically set to Assigned. This includes work orders which are processed by the SDS.
If the Work Order Status option is used to directly set a work order to the Assigned status, the work order is considered manually scheduled and will no longer be re-scheduled by the DSE. Furthermore, if an employee is not entered on the work order or if the employee specified is not set up as a scheduling resource and the work order has reached the Assigned status, the work order will not be sent to Mobile Workforce Management. .
If the employee who is assigned to the work order cannot carry out the activity, it is possible to unassign the employee from the work order. When unassigned, the work order will be resent to Mobile Workforce Management to be rescheduled by the DSE, and a new employee may be suggested in the allocation plan that is returned to IFS Applications. If an employee is unavailable for work, this should be notified via the HR system/Time Management so that Mobile Workforce Management will receive the absences and will adjust the schedules accordingly.