Setting up non-productive activities |
|
|
|
Setting up non-productive activities |
|
|
Setting up non-productive activities |
|
|
|
Setting up non-productive activities |
|
|
Non-productive activities are any activities that need to be scheduled but are not productive. Non-productive activities are assigned to roster exceptions and can also be inserted within a resource input path. In the latter case they are called 'In Path' delays.
|
There is only one list of non-productive activities for each project. This list can be edited from the All Items tab or from the tree for any scenario on the Scenario tab. An example of a Non Productive Activities list is provided below. |
The Activity Number is listed on the far left of the Non Productive Activities list. The first non productive activity is number 101 and XPAC increments this number by one for each subsequent non productive activity. You cannot edit the activity number, although you could edit the rest of the non productive activity details to re-assign numbers in directly. The Activity Number is used in some XCM and Report Writer functions to identify the non-productive activity and is assigned when you run the schedule.
The Activity Name is user-defined and can be edited at any time. It may be up to 50 characters in length and can include alphanumeric characters as well as spaces.
You must assign an Activity Type to each activity:
Option |
Description |
Non Operating Delay |
The equipment is not operating during these delays. In most cases, this will mean the engine is not running. |
Operating Delay |
The equipment engine is running, but is not productive. |
Extended Operation |
Use this activity type to add operating time, over and above the normal roster time. It can be used to model overtime shifts which are not included in the roster. |
The Parallel Type field only applies to Roster Exceptions. In path delays can use the same non productive activities, but XPAC ignores the Parallel Type. The Parallel Type controls whether the Roster Exception can be carried out in parallel with in path delays and productive steps. Select one of the following Parallel Type options for each non productive activity from the drop-down list:
Option |
Description |
Standard |
This is the default Parallel Type. When a roster exception is of this type, it will not occur in parallel with either in path delays or productive steps. |
Parallel with Delays |
Roster Exceptions of this type will occur in parallel with in path delays, but not productive steps. |
Parallel with Steps |
Roster Exceptions of this type will occur in parallel with productive steps, but not in path delays. |
Parallel with Both |
Roster Exceptions of this type will occur in parallel with both in path delays and productive steps. |
