Introduction
Introduction
Each project involves n jobs, and there are precisely n manufacturing units
available, capable of handling all project tasks. The objective? To assign these
jobs to the manufacturing units in a manner that minimizes the overall project
completion time across the two stages.
The study includes a numerical illustration supporting the proposed theory, along
with implementation and testing of the algorithm across various test problems. By
calculating the average run time for each problem, the effectiveness of the
algorithm in minimizing project duration is assessed."
---
**Stage-I Problem:**
- **Objective:** Minimize time for completing primary jobs (J1).
- **Formulation:** \(T_1(X) = \min_{X\in S} \max_{I\times J1} (t_{ij}(x_{ij}))\)
- **Constraints:** Allocation (\(x_{ij}\)) limited to 1 per unit, each primary job
done once (\(x_{ij} = 1\)), binary values for task allocation.
**Stage-II Problem:**
- **Objective:** Optimal completion for remaining jobs (J\J1) after Stage-I.
- **Formulation:** \(T_2(Y) = \min_{Y\in S(X)} \max_{\overline{I1}\times\
overline{J1}} (t_{ij}(y_{ij}))\)
- **Constraints:** Allocation (\(y_{ij}\)) similar to Stage-I, involving the
leftover units and jobs.
---
This concise overview highlights the objectives, formulations, and constraints for
both Stage-I and Stage-II problems, culminating in the overall Priority Based
Assignment Problem (PBAP).
1. **Initial Step:**
- Find an Optimal Basic Feasible Solution (OBFS) for (CP).
- Obtain corresponding Stage-I (T0_1) and Stage-II (T0_2) times.
3. **Terminal Step:**
- Stop if the OBFS of (CPk) is not M-feasible.
- Optimal value of PBAP: min{Th_1 + Th_2} for h = {0, 1..., k−1}.
*Table 1: PBAP*
(W1 W2 W3 W4 W5 W6)
P1 82 28 96 80 68 71
P2 91 55 49 96 76 04
P3 13 96 81 66 75 28
P4 92 97 15 04 40 05
P5 64 16 43 85 66 10
P6 10 98 92 94 18 83
*Table 2: CP*
(W1 W2 W3 W4 W5 W6)
P1 λ21 0 0 λ19 0 0
P2 λ24 0 0 λ27 0 0
P3 λ4 0 0 λ14 0 0
P4 λ25 0 0 λ1 0 0
P5 λ13 0 0 λ23 0 0
P6 λ3 0 0 λ26 0 0
**Example 1:**
**Example 2:**
**Remark:**
**Algorithm Verification:**
- Showcased average running times (seconds) taken over approximately 100 instances
for each class.
- Displayed in Fig. 1, the runtime variations based on the percentage of primary
and secondary jobs.
- Noticed maximum runtime peaks around 50% of primary or secondary jobs (40 in some
cases).
- The algorithm performed better when the percentage was below 40 or above 60 due
to variations in time entries between primary and secondary job sets.
- The peak around 50% suggests longer execution times as time variations in both
primary and secondary sets were maximal, unlike other cases.
**Concluding Remarks:**
3. Each iteration involves solving a TMAP via a corresponding CMAP, both solvable
by polynomial-bound algorithms, limiting the total problems to a finite number.
4. In the worst case, the algorithm solves at most m∗n problems, where m∗ is the
count of distinct time entries for primary jobs.
7. Limitation: Cannot solve problems when the one agent-one job condition is
relaxed.
9. Further exploration: Extend the problem to accommodate more than two types of
jobs prioritized differently.
10. Future exploration: Seek techniques that strictly decrease the sum T1 + T2 at
each iteration, improving upon the current algorithm's behavior.