104
6 Engineering Applications of Facility Layout
Table 6.24 Distances between pairs of locations
1 2 3 4 5 6 7
8
9
10 11 12 13 14 15 16 17 18 19
1 – 12 36 28 52 44 110 126 94 63 130 102 65 98 132 132 126 120 126
2
– 24 75 82 75 108 70 124 86 93 106 58 124 161 161 70 64 70
3
– 47 71 47 110 73 126 71 95 110 46 127 163 163 73 67 73
4
– 42 34 148 111 160 52 94 148 49 117 104 109 111 105 111
5
– 42 125 136 102 22 73 125 32 94 130 130 136 130 136
6
– 148 111 162 52 96 148 49 117 152 152 111 105 111
7
–
46 46 136 47 30 108 51 79 79 46 47 41
8
–
69 141 63 46 119 68 121 121 27 24 36
9
–
102 34 45 84 23 80 80 69 64 51
10
–
64 118 29 95 131 131 141 135 141
11
–
47 56 54 94 94 63 46 24
12
–
100 51 89 89 46 40 36
13
–
77 113 113 119 113 119
14
–
79 79 68 62 51
15
–
10 113 107 119
16
–
113 107 119
17
–
6
24
18
–
12
19
–
pairs of departments are given in Table 6.24, and the flows are given in Table 6.25.
The entries in Table 6.25 were obtained by averaging the flow between each pair
of clinics, thus generating a symmetric matrix. The flow between facilities 15 and
16 (the two components of Minor Operations) is set to 99999 to force them to be
adjacent in the optimal solution.
The distances between the locations were measured by tracing the paths taken
by patients as they moved from one location to another. If the movement involved a
change in floors, the corresponding vertical distance was multiplied by a subjective
factor of 3. After visiting all the necessary clinics, the patient must return to the
first one visited for administrative purposes. This essentially involves retracing the
outward path because all the clinics are in the same building and there is only one
main corridor per floor. Thus, the distance matrix can also be taken to be symmetric,
even for pairs of locations on different floors.
6.10 References and Further Reading
The metallurgical industry instance presented in Sect. 6.1 comes from the master’s
thesis of Patil (1963). The manufacturing example in Sect. 6.2 is from El-Baz
(2004). This example does not contain real-world data; we include it because
6 Engineering Applications of Facility Layout
Table 6.24 Distances between pairs of locations
1 2 3 4 5 6 7
8
9
10 11 12 13 14 15 16 17 18 19
1 – 12 36 28 52 44 110 126 94 63 130 102 65 98 132 132 126 120 126
2
– 24 75 82 75 108 70 124 86 93 106 58 124 161 161 70 64 70
3
– 47 71 47 110 73 126 71 95 110 46 127 163 163 73 67 73
4
– 42 34 148 111 160 52 94 148 49 117 104 109 111 105 111
5
– 42 125 136 102 22 73 125 32 94 130 130 136 130 136
6
– 148 111 162 52 96 148 49 117 152 152 111 105 111
7
–
46 46 136 47 30 108 51 79 79 46 47 41
8
–
69 141 63 46 119 68 121 121 27 24 36
9
–
102 34 45 84 23 80 80 69 64 51
10
–
64 118 29 95 131 131 141 135 141
11
–
47 56 54 94 94 63 46 24
12
–
100 51 89 89 46 40 36
13
–
77 113 113 119 113 119
14
–
79 79 68 62 51
15
–
10 113 107 119
16
–
113 107 119
17
–
6
24
18
–
12
19
–
pairs of departments are given in Table 6.24, and the flows are given in Table 6.25.
The entries in Table 6.25 were obtained by averaging the flow between each pair
of clinics, thus generating a symmetric matrix. The flow between facilities 15 and
16 (the two components of Minor Operations) is set to 99999 to force them to be
adjacent in the optimal solution.
The distances between the locations were measured by tracing the paths taken
by patients as they moved from one location to another. If the movement involved a
change in floors, the corresponding vertical distance was multiplied by a subjective
factor of 3. After visiting all the necessary clinics, the patient must return to the
first one visited for administrative purposes. This essentially involves retracing the
outward path because all the clinics are in the same building and there is only one
main corridor per floor. Thus, the distance matrix can also be taken to be symmetric,
even for pairs of locations on different floors.
6.10 References and Further Reading
The metallurgical industry instance presented in Sect. 6.1 comes from the master’s
thesis of Patil (1963). The manufacturing example in Sect. 6.2 is from El-Baz
(2004). This example does not contain real-world data; we include it because