Background function – When PM are auto generated via Service Level Agreement, the Craftsperson assigned and work requested assigned dates are generated by a calculation from the Date to first do on the PMS table.

The Craftsperson assigned and work requested assigned Time is generated by the Service Window on the SLA and the time is defaulted to the earliest start time on the Service level agreement.

Problem
When there are multiple PM activities that are always scheduled on the same day for the same Craftsperson (example 7 small jobs of 50 minutes) when the PM is generated the Work Request and Craftsperson Labour assignments date and time will all be generated to the same date and time because the work request will be based on the earlies time in the Service Level Agreement, for that craftsperson.

There currently needs to be manual intervention by use of the labour scheduler to adjust the start time of the Craftsperson for each work request. This additional administration overhead is time consuming and adds overhead labour cost to the business. In our case we project over 400 to 600 Building will have 12+ visits per year with a small travel window between jobs. This means manual intervention in Circa 5,000 low cost low profit margin PM WR.

There are also some longer duration WR that are to be scheduled over several days and there are multiple CF assignments for the same CF for the same WR. This is an ancillary issue that could be dealt with

Solution
In the PMS table/screen Introduce a “default start time” for the Work Request. This is not a mandatory field. The PM generation logic enhanced to add the following. This will allow the configuration of a repeating schedule in the correct sequence and time.
If [pms].[defaultstarttime] exists (not null) then update WR and CF time assigned to = [pms.defaultstarttime] Else use SLA Service Window as default

Practical example of Not Null [pms].[defaultstarttime]
PM1 - [pms.defaultstarttime] = 0900 (labour effort of 50 Minutes)
PM2 - [pms.defaultstarttime] = 1000 (labour effort of 50 Minutes)
PM3 - [pms.defaultstarttime] = 1100 (labour effort of 50 Minutes)
PM4 - [pms.defaultstarttime] = 11200 (labour effort of 50 Minutes)
Will result in
WR1 - WR and CF estimated start time = 0900 and duration finish at 0950
10 minute trave time absorbed by company overheads
WR2 - WR and CF estimated start time = 1000 and duration finish at 1050
10 minute trave time absorbed by company overheads
WR3 - WR and CF estimated start time = 1100 and duration finish at 1150
10 minute trave time absorbed by company overheads
WR4 - WR and CF estimated start time = 1200 and duration finish at 1250

The result is ha the CF assignment times are pre scheduled (and of course can be moved by the labour scheduler)

This scenario is relevant to multi trades where one must precede the other (lets say a maintenance WR followed by an cleaning WR by another trade of CF)
The Mobile application need to include an “Order by/Sort by” CF assignment time to allow CF to see his day in order of their routine assignments – the current application does not allow this functionality.

As for the ancillary issue of scheduled over multiple days
Introduce In the PMS table/screen Introduce a “spread CF assignment over Multiple days” for the Work Request. This functionality will add multiple CF assignments for the same WR over several days an proportionally divide the Trade or SLA effort into those days
Example
spread CF assignment over Multiple days = yes (PMS layout)
Day 1 [Yes] % [20]
Day 2 [Yes] % [10]
Day 3 [Yes] % [10]
Day 4 [Yes] % [null]
Day 5 [Yes] % [10]
Day 6 [Yes] % [15]
Day 7 [Yes] % [35]

This will result in six CF assignments (note do not send emails to the CF six times if notification are on)

Geolocation of PMS.
Introduce a lat and long field that will populate the WR Location
Allow access to direction finder to show CF where to go
WR Geolocate Logic = Use Building or Equipment Geo data by default [Yes/No]
Or option to Geolocate PMS on Map the same as the current building Geolocate.
Add option to mobile app work request to “Update PMS and or Asset Location from your current location this would then use location tracking turned on, or a photo to get coordinates. I do not think it would be wise to update the building geo location data

Regards
Stephen O'Donnell Sydney Australia