An Internal Activity may contain a checklist and/or a schedule. If the Internal Activity contains a schedule it will be scheduled by the Balthzar Scheduler. If the Internal Activity contains a checklist the user must perform it before the activity is closed. When creating an Internal Activity you may also choose from additional rules which must be fullfilled before the activity are created. If a part is choosen the Internal Activity will only be created if the part is running on the choosen machine. If all machines are choosen the Internal Activity will be created for all machines which fullfill the criterias of the schedule.
If the all machines are chosen the activity will be created for all machines found in the department, category and zone selected.
A schedule in Internal Activities describes an event when an activity should be scheduled. These events may be of the following types:
Schedules of type amount and frequency refers to the time/amount since a new work order was started.
To avoid a large number of activities being created at once, only one activity will be created for each program search cycle. E.g., if you have a schedule to create an activity for each 10th produced unit and manually report 50 units, only one activity will be created instead of 5.
First you create a checklist and then you add rows to this checklist. A row type is either numerical or yes/no. If the row is numerical you must also enter the nominal value, upper/lower limit, upper/lower reasonable limit and unit. You must also enter the row number the row should have, e.g. in which order the rows are displayed in the checklist. Finally you may enter a note.
An Internal Activity may have a type. The use for this is twofold; first it is used to filter amongst activities and secondly it is used to determine wether an activity are to be performed at a machine. If an activity are to be performed at a machine eTouch will notify the operator of this.
In Internal Activities there are the following events:
These events occur when a production order is started, stopped or when the first piece are approved. Each event occurs for one machine, one part number and possibly one tool.
It is possible to tie an activity to an event. This means that is the event occurrs on the chosen machine, with the chosen tool and part number the activity will be created regardless of its schedule and rules. The activity will then be using the machine ID, part number, tool ID and operation number of the event.