The task sheet is where you can enter task related details and map model, option, and resource data. Clicking the tag on the column heading gives the option to filter the task data according to unique items in that column. The fields described below with a (WPP) designation, indicate that those data fields are saved from ProBalance and transferred to the Proplanner Workplace Planner application.
Located in the Task Sheet are the following eighteen columns:
1. |
ID: The ID of a task is a unique identifier. The ID can be as simple as 1,2,3 or could be based on the manufacturing process (Assembly01 or Inspect01), line location or workstation (Stn603-01), or by the product being manufactured (Chassis01). |
2. |
Description: The description column allows users to enter information to identify the task. |
3. |
Type (WPP): The process type helps in identifying value added or non-value added tasks. A "M" type implies it is a manual process, a "W" type implies it is a walk process and an "I" type implies it is a combination of walk and a manual process. Typically a walk process is 0% value added and a manual process is 100% value added. |
4. |
Time (WPP): There are three types of times being tracked within the tool. Process time, Walk time and Machine time. If the user has only one time for the task, that time should be entered in the Process Time column. |
· |
Process Time: The process time is the time involved in doing value added work. |
· |
Walk Time: The walk time is the time involved in doing non value added work (Walk). This field is required if using ProBalance in conjunction with WPP. |
· |
Machine Time: The machine time is the time involved in doing non value added work (the user waiting on a machine cycle). This field is required if using ProBalance in conjunction with WPP.. |
5. |
Freq.: The frequency of the activity within the process plan. By default, the frequency is set to one. |
6. |
Occ.: The occurrence of the activity. By default the occurrence is set at one. |
7. |
Net Time: The net time of the activity is computed as: |
[(Process time + Machine time) * Frequency + Walk Time]* Occurrence
The net time computation can best be explained through an example. Suppose there is a process which requires tightening four bolts. Tightening one bolt consumes one second. After two bolts are tightened, the operator walks to a bin and picks up two more bolts and then returns and finishes the assembly. A one way trip to the bolt bin takes two seconds. For this scenario, the process time is one second, and the walk time is four seconds (round trip), per cycle. Frequency for the bolt tightening process is four, since the operator is tightening four bolts per cycle. The net time for this operation is calculated below.
[(1+0) * 4 + 4] * 1 = 8 seconds
This entire set could happen for every assembly coming down the line(as is the case above). The occurrence in such a case is 1, or for a specific set of assemblies (say 1 in every 4), the occurrence would then be 0.25.
8. |
VA% (WPP): Value added percentage is a user input. The user can provide a percentage based on the value added content of the task. |
9. |
NVA% (WPP): Non value added percentage is a user input. The user can provide a percentage based on the non-value added content of the task. |
10 |
NVBN% (WPP): Non value added but necessary percentage is a user input. The user can provide a percentage based on the non-value added but necessary content of the task. |
Note: ProBalance does not automatically calculate the value added or non value added content of the task. It is purely a user input.
11 |
Models: ProBalance handles both single and mixed model processes. In a single model, the user does not need to specify the model and can leave the column blank. In the mixed model case, the user can select any model which has already been defined in the Model Editor. A task is mapped to any model which is selected or typed into the model column. If the task is necessary for multiple models, users must separate each model name with a comma.
|
12 |
Net Take Rate: The net take rate is the probability of occurrence for a specific task and its value is dependant on the demand percentage for the models and the penetration percentage for the options mapped to the task. For example consider a process for manufacturing three automobile models (standard, deluxe, and luxury). The demand percentage for the three models is 0.45, 0.25, and 0.30 respectively. Tasks which are only applicable to a “standard” model would have a net take rate of 0.45. A task which is used for "standard" and "deluxe" would have a net take rate of 0.70 (0.45 + 0.25). Finally if the task is used for all three models, the net take rate would be 1.00 (0.45 + 0.25 + 0.30). |
13 |
Resources: The tools and machines required by the tasks are listed in the resource column. The user needs to first define all resources in the Resource Editor. Mapping a resource to a task provides information to ProBalance to flag the user if there is a missing resource after the line balance for the tasks has been generated. |
14 |
Station: ProBalance computes the station assignment automatically. Once the tasks have been line balanced, the station ID appears in the station column. All current stations on a production line can be defined in the Station Editor. |
15 |
Work Location (WPP): The work location is where the work is being done. This is a WPP input, for those doing just line balance this column can be left blank. |
16 |
Remarks: The remarks column is a place for the user to add additional comments about the task. |
17 |
Element Data (WPP): Pre-determined time codes (MODAPTS, MTM-1, MMMM etc.) for the activity should be provided in the element data column. This again is a WPP input. |
18 |
Zone: Each station can have multiple work zones in it. The user can define these zones and then map them to the task. The tool looks into the zone requirement of the task and assigns it to a station with the corresponding zone. For instance, a station could have four zones, L (Left), R (Right), A (Above) and U (Under). The underbody tasks should be done in a station which contains a U zone. Refer to the documentation in Menus for Adding zones.
Modify the config file by adding values to the key called Work Zone. For e.g. in the above image Front, Back, Top etc. are new zones added to the application. The user can then add on the Zone column and map the zone to the task.
|
