| Checklist performance group planning | Session |
|---|
| 1 | "Route
based"-scheduling is more time consuming than "Time based"-scheduling. More
calculations must be done. | Service Planning
Parameters | tsspc0100m000 |
| 2 | Using option "Minimize Slack" requires more
response time of the system. More calculations must be done. | Service Planning Parameters | tsspc0100m000 |
| 3 | "Geographically based" workload leveling is more time consuming
than "Scheduling based" work load leveling. Geographically based leveling makes
use of the so called “territory planning engine” and related algorithm. | Service Planning Parameters | tsspc0100m000 |
| 4 | A
short Time Period (e.g. "Day") for generating groups and activity sets is more
time consuming than a longer Time Period (e.g. "Month"). A shorter period leads
to more groups and/ or activity sets. | Service Planning
Parameters | tsspc0100m000 |
| 5 | A high Number of Iterations (e.g. 10) for work
load leveling is more time consuming than a lower Number if Iterations (e.g.
5). | Service Planning Parameters | tsspc0100m000 |
| 6 | Resource allocation based on skills should only be used if skills
are actually assigned to service engineers. Otherwise it takes significant
unwanted response time. | Service Planning Parameters | tsspc0100m000 |
| 7 | “Planning activities in resource calendar” takes additional
response time of the system, since activities are rescheduled based on
allocated resource (department or engineer). | Service
Planning Parameters | tsspc0100m000 |
| 8 | The more different values of proposed
priorities are setup, the more response time is required for proposed and
allocation resources. Especially the value 'Not allocated to other planning
groups' can require significant amount of additional time, since after
allocating each resource, a recalculation of the proposed resource plan is
done. | Service Planning Parameters | tsspc0100m000 |
| 9 | Checking the availability of the resource in a calendar requires a
significant amount of additional response time, especially when every resource
(department of engineers) has its own unique calendar. The caching of the
number of calendars in LN is limited. | Service Planning
Parameters | tsspc0100m000 |
| 10 | The best value for Distance Calculation
Method from a performance point of view is ‘as the crow flies’. This requires
less response time than the values 'Bing Maps' and 'Google Maps', since the
latter methods call web services to performance the calculations, whereas "as
the crow flies" is done by LN 4GL. | Service Planning
Parameters | tsspc0100m000 |
| 11 | The maximum number of route locations fixes
the absolute maximum allowed number of locations in one route. For sake of
performance the number of locations in a route of group or activity set must be
minimized. This is also controlled by limiting the number of activities in one
group or set, so that it depends on the chosen planning attributes, and the
number of activities that are loaded in group planning. | Service Planning Parameters | tsspc0100m000 |
| 12 | Grouping based on attribute "reference point" takes more response
time than a standard order attribute (e.g. Sold-to BP) since group planning
first needs to be assigned to the applicable reference point value based on the
reference point closest to location of the order. | Service
Planning Parameters Attribute Group - Reference Points | tsspc0100m000 tsspc0120m000 |
| 13 | The more activities are loaded into group planning the more
response time is needed to (re)plan groups and activity sets. | Generate Plan | tssp3200m000 |
| 14 | Make sure group planning is actually grouping
activities together in sufficient groups and activity sets by choosing at least
one "parallel" planning attribute. Choosing 2 more or parallel is ok, but can
be suboptimal from a performance perspective. | Planning
Attributes | tsspc0100m000 |