Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
As the items move along the line, the work is progressed intermittently and
leaves the line as a finished product. Typically the objective is, to divide the
work content equally among the workstations so that the workstations are
loaded as evenly as possible. This is known as balancing. Firstly, if such a
balance is not achieved, a certain amount of inefficiency will arise because
some stations will have more work to perform than others, and all the
stations are expected to process same number of items per period of time.
Secondly, unequal work content at different workstations leads to unequal
work distribution and also formation of queue of items. Hence, to ensure a
smooth flow, all the workstations are given the same time to process the
items. The entire line typically, on a manual or power-driven conveyor
moves from workstation to workstation at a constant rate.
The time required to complete the work allotted to each station is known as
the service time and the time available at each station is known as the
cycle time, normally longer than the service time. The cycle time includes
both the productive as well as the non-productive time along with idle time if
any. Non productive time includes time for movement, handling and
inspection time. The manner in which the work content is allocated to the
station is influenced by the technological sequence of the assembly and
expressed by precedence requirements, that is, one operation must be
completed before the other operation can start. Such constraints limit the
ability to achieve complete or perfect balance while allocating work to
stations.
The allocation of work elements to a workstation may also be influenced by
zoning constraints which occurs in two ways: positive zoning constraint
demands that certain operations have to be clubbed together because of
certain sharing of resources, and negative zoning which insists that certain
operations should be clubbed together because of interference or conflict.
All these constraints make it very difficult or impossible to achieve perfect
line balance and hence, a certain amount of balancing delay or balancing
loss is inevitable. Balance delay is defined as the total time available to
complete the given job and the total time required. In other words, the
balance delay is the difference in time between the service time and the
cycle time, expressed as a percentage of the cycle time.
The objective of line balancing is that, given a desired cycle time, the
attempt is to assign work elements to workstations to:
Minimise idle time or balancing delay
Minimise the number of work stations
Distribute balancing delay evenly between stations
Avoid violating any constraints
As it is difficult to achieve all these objectives simultaneously at least one
objective has to be satisfied. Based on this premise, several researchers
have proposed different heuristic methods to realise the desired goal.
Discussing all the different approaches is beyond the scope of this topic and
hence a few methods are illustrated.
Several calculations are involved in line balancing. The different terms and
corresponding calculations are stated here as follows:
Cycle time, C
1
C=
r
Where, c = cycle time in hours per unit, and r = desired output rate in units
per hour
Theoretical minimum number of workstations:
t
TM =
c
Idle time nc t
Where, n = number of stations, and c = cycle time
t
Efficiency= 100
nc
Longest task time Choose the available task with the longest task time
Most following tasks Choose the available task with the largest
number of following tasks
Ranked positional weight Choose the available task for which the sum
of following task times is the longest
Shortest task time Choose the available task with the shortest task
time
Least number of following tasks - Choose the available task with the
least number of following tasks
Practice problems (Ref: Heizer and Render (2008) Operations
Management)
An assembly line is to operate eight hours per day with a desired output of
240 units per day. Table 6.8 depicts the task times and precedence
relationships.
Table 6.8: Task Times and Precedence Relationships
Draw the precedence diagram. What is the cycle time? Balance this line
using the longest task time rule. Find the efficiency and the balance delay. First we draw the
precedence diagram. Figure 6.17 depicts the precedence
diagram.
Cycle time = production time per day/ required output per day
= (8 hour/day) (3600 seconds / hour) / 240 units per day =
120 seconds per unit
After drawing the precedence diagram, the next step is to assign the tasks
to the workstations. First we calculate the theoretical minimum number of
workstations as follows:
Minimum number of workstations = total task time / Cycle time
= 420 / 120 = 3.5 or rounded as 4 (Workstations cannot be a fraction)
Now using this number of workstations the tasks have to be assigned
without violating the precedence relationships. Furthermore, in each
workstation the total task time cannot exceed the cycle time.
Starting from workstation 1, task A has a task time of 60 seconds and can
only be clubbed with another task such that the total time doesnt exceed
120 seconds.
A + B = 60 + 80 = 140 (Not feasible because exceeds 120)
A + C = 60 + 20 = 80 (Feasible)
A + D = 60 + 50 = 110 (Feasible)
Between the two feasible combinations, A + D is selected using the rule
longest task time.
Similarly, other tasks are assigned and line is balanced. The final allocation
of tasks to the four workstations is depicted in the Table 6.9.
The efficiency =
NC
T
a
4(120)
420
= 0.875 or 87.5%
And balance delay = 1- Efficiency = 1- 0.875 = 0.125 or 12.5 %
Activity 1
The desired output for an assembly line is 360 units which operates 450
minutes per day. Table 6.10 depicts information about task times and
The following steps should be considered for setting the data in a logical
order.
1. Check whether the participants in the process that is, people, teams,
and electronic applications are sufficient or, any changes and additions
need to be made.
2. Ensure that all the data expected is included or not. Generally, we start
with an initial set of data which we have. When we check them with the
requirements of the process for the desired outcomes, we find gaps.
These gaps help us in determining which subset of the data is
appropriate at each task in the process.
3. Check whether the data is sufficient for the implementation of the
process. This can be achieved by answering the following questions:
1. What is the path the process should take?
2. What decisions are to be made at any point in the process?
3. Are data available at those points?
4. State the rules used to define the various parts of the process. At
this stage, the naming conventions are also included. This is
important to be included at the process definition stage.
5. Determine the disposition of data at the end of the process and
decide the following:
a. Do we plan to keep the data or delete them?
b. If they are to be stored, where and in what form will be used?
c. What are the measures of security for access?
6. Determine the other elements depending upon the business process