Work has been completed to change the way the system forecast behaves in the event that there are no sales for the previous year’s tagged Notable Day. Previously, taking the example of the first Bank holiday in May, if for a particular site, the previous year’s sales were £0 (site was not open, data not obtainable), in the event that the Bank holiday in 2016 and 2017 were tagged as Notable Days, the system would forecast £0 sales for 2017. The change is so that in the event of missing data from previous year, the system continues to forecast as if it was not a tagged Notable Day.
Reason for the Change
Previously customers had experienced problems with the system unable to produce sales forecast or shape of day labour demand graph in the event of a Notable Day with no previous year’s sales on the equivalent Day. The system forecast will instead now forecast as normal (as if there was no Notable day tag) in the event that it cannot find previous year sales data for a particular site with a tagged Notable Day.
All current Team Hours customers.
No implementation is required on the customer side to enable this It is a standard function enhancement designed to benefit all Team Hours customers.
Customers should be aware and cascade to their sites, that in the event that the manager believes that they have a tagged Notable day and the system does not appear to reflect an uplift/decrease in sales as expected, they should first check whether they have previous years’ sales data for the equivalent Notable Day in their Team Hours portal before contacting support. If they do not have data for that day, the system will forecast as if the Notable day is a ‘normal’ day and the manager should adjust manually.
What has not changed?
No change to other normal system forecast behaviour
Please sign in to leave a comment.