Utafiti wa kitaaluma, lugha inayoeleweka

Verianla | Akademik Araştırmalardan Türkçe Ekonomi ve Bilim İçerikleri

03 Novemba 2026, Jumanne
VERİANLA Uchapishaji huru wa sayansi
Verianla on Google Play
Fungua au funga menyu
...
Home / Sayansi Tumizi / Uhandisi / Uboreshaji Thabiti Kiusambazaji kwa Upangaji Ratiba wa Karakana ya Mtiririko wa Permutation yenye Nyakati za Maandalizi Zinazotegemea Mfuatano na Gharama za Uendeshaji Chini ya Kutokuwa na Uhakika katika Mifumo ya Uzalishaji ya Viwanda 4.0
Uhandisi

Uboreshaji Thabiti Kiusambazaji kwa Upangaji Ratiba wa Karakana ya Mtiririko wa Permutation yenye Nyakati za Maandalizi Zinazotegemea Mfuatano na Gharama za Uendeshaji Chini ya Kutokuwa na Uhakika katika Mifumo ya Uzalishaji ya Viwanda 4.0

Uboreshaji Thabiti Kiusambazaji (Distributionally Robust Optimization, DRO) ni mkabala wa uboreshaji unaofanya maamuzi kwa kuzingatia matokeo mabaya zaidi yanayotarajiwa ndani ya ambiguity set yenye usambazaji mbalimbali unaowezekana, badala ya kudhani kuwa kigezo kisicho na uhakika kinatokana na usambazaji mmoja pekee wa uwezekano ulio kamili na unaojulikana.

31/10/2026  Veri Anla  Imetazamwa mara 127
Uboreshaji Thabiti Kiusambazaji kwa Upangaji Ratiba wa Karakana ya Mtiririko wa Permutation yenye Nyakati za Maandalizi Zinazotegemea Mfuatano na Gharama za Uendeshaji Chini ya Kutokuwa na Uhakika katika Mifumo ya Uzalishaji ya Viwanda 4.0

Uboreshaji Thabiti Kiusambazaji (Distributionally Robust Optimization, DRO) ni mkabala wa uboreshaji unaofanya maamuzi kwa kuzingatia matokeo mabaya zaidi yanayotarajiwa ndani ya ambiguity set yenye usambazaji mbalimbali unaowezekana, badala ya kudhani kuwa kigezo kisicho na uhakika kinatokana na usambazaji mmoja pekee wa uwezekano ulio kamili na unaojulikana. Utafiti huu unaunganisha DRO na muundo wa Permutation Flow Shop Scheduling Problem, ambamo kazi zote hupitia mashine kwa mpangilio uleule, nyakati za maandalizi zinazotegemea mfuatano (Sequence-Dependent Setup Times; SDST), processing times zisizo na uhakika na operational cost inayotokana na muda wa processing/setup/idle. Lengo ni kubainisha mpangilio mmoja wa kazi unaopunguza kwa pamoja Total Weighted Flow Time (TWFT) na operational cost katika fomula moja ya lengo yenye uzani.

Inakubaliwa kuwa processing-time distribution halisi haijulikani kikamilifu; processing scenarios za usanisi huundwa kuzunguka usambazaji wa kawaida, na scenario probability distributions zinazowezekana hutathminiwa ndani ya ambiguity set inayofafanuliwa kwa Kullback–Leibler divergence. Robustness radius \(\rho\) hudhibiti kiasi ambacho inaweza kuruhusiwa kujitenga na usambazaji wa kawaida. Kwa computational experiments zote kuu katika utafiti, \(\rho=0.05\) imewekwa bila kubadilishwa; kwa hiyo, viwango vya algorithms na matokeo ya robustness yaliyopatikana hayajathibitishwa kwa thamani tofauti za \(\rho\).

Kwa matatizo ya kiwango kidogo, suluhisho za global-optimum benchmark zilipatikana kwa mbinu ya exhaustive enumeration inayosaidiwa na IBM ILOG CPLEX. Kwa medium na large instances, Greedy Randomized Adaptive Search Procedure (GRASP), Hybrid GRASP (HGRASP) iliyopendekezwa na utafiti, Ant Lion Optimizer (ALO) na Slime Mold Algorithm (SMA) zililinganishwa. Katika mifano midogo, HGRASP ilizalisha upya exact benchmark zote zilizojaribiwa; mbinu nyingine za makadirio pia zilifikia matokeo exact au yaliyo karibu sana katika hali nyingi. Katika matatizo ya kiwango kikubwa, jaribio la Friedman lilionyesha kuwa kuna tofauti muhimu kati ya algorithms kwa solution quality na computational time. ALO na SMA zilifikia thamani sawa ya mean rank iliyo bora zaidi kwa solution quality na hazikupatikana kuwa tofauti kwa kiasi muhimu katika uchambuzi wa post-hoc; SMA ilifikia nafasi bora zaidi kwa computational time.

Utafiti haujathibitishwa kwa kutumia rekodi za uzalishaji kutoka kiwanda halisi. Processing times, setup times, job weights na machine cost coefficients zilitengenezwa kwa njia ya usanisi. Aidha, operational-cost coefficients si vipimo halisi vya matumizi ya umeme, nguvu, bei ya nishati au utoaji wa hewa chafu. Kwa hiyo, matokeo yanaonyesha tabia ya computational ya proposed DRO framework chini ya benchmark za usanisi; hayathibitishi kuwa akiba ileile ya gharama au nishati itapatikana katika kiwanda halisi cha Industry 4.0.

PFSP-SDST ni Nini na Ni Tatizo Gani Linalotatuliwa Katika Utafiti Huu?

PFSP-SDST ni tatizo la upangaji ratiba la kimchanganyiko ambamo kazi zilezile \(n\) hupitia mashine zilezile \(m\) kwa mfuatano uleule wa kiteknolojia na muda unaohitajika kuandaa mashine kwa kazi mpya hautegemei kazi hiyo pekee, bali pia kazi iliyochakatwa mara moja kabla yake; katika utafiti huu processing times pia zinachukuliwa kuwa stochastic na mpangilio mmoja wa kazi huchaguliwa ili kupunguza kwa pamoja TWFT na operational cost chini ya kutokuwa na uhakika.

Mantiki ya Permutation Flow Shop

Seti ya kazi:

\[ J=\{1,\ldots,n\} \]

na seti ya mashine:

\[ M=\{1,\ldots,m\} \]

imefafanuliwa.

Kila kazi hupitia mashine zote kwa mfuatano uleule. Zaidi ya hayo, si njia ya kiteknolojia pekee bali permutation ya kazi pia ni ya pamoja katika mashine zote. Kwa mfano:

\[ \lambda=[J_3,J_1,J_4,J_2] \]

ikichaguliwa, kazi kwenye mashine zote huendelea kwa mpangilio huo wa pamoja.

Kwa nini Sequence-Dependent Setup Time ni muhimu?

Muda wa maandalizi unaohitajika na mashine wakati wa kutoka kazi \(J_i\) kwenda kazi \(J_j\):

\[ s_{i,j,k} \]

unawakilishwa kwa hiyo.

Kwa hiyo muda wa maandalizi hautegemei kazi lengwa pekee; jozi ya predecessor–successor na mashine \(k\) ni muhimu kwa pamoja.

Hali hii inaweza kuwakilisha mabadiliko ya viwandani kama kubadilisha rangi, kurekebisha mold, kubadilisha zana, kusafisha au kubadilisha familia ya bidhaa. Chanzo hakitumii matrix halisi ya setup ya mchakato mmoja wa kiwanda; kinatengeneza benchmark za usanisi zinazodhibitiwa.

Stochastic processing time inawakilishwaje?

Processing time ya job \(j\) kwenye machine \(k\) katika scenario \(\omega\):

\[ p^\omega_{j,k} \]

imefafanuliwa.

Kazi inapopewa sequence position \(r\), position-level processing time:

\[ PT^\omega_{r,k} \]

huwa hivyo.

Kutokuwa na uhakika kunawakilishwa kupitia scenario set:

\[ \Omega=\{1,\ldots,S\} \]

.

Vigezo vikuu

AlamaMaana
\(n\)Idadi ya kazi
\(m\)Idadi ya mashine
\(\omega\)Indeksi ya uncertainty scenario
\(\lambda\)Job permutation ya pamoja
\(x_{j,r}\)Binary variable inayokuwa 1 ikiwa job \(j\) imepewa position \(r\)
\(y_{i,j,r}\)Adjacency variable inayokuwa 1 ikiwa kwenye position \(r-1\) kuna \(i\), na kwenye position \(r\) kuna \(j\)
\(p^\omega_{j,k}\)Katika scenario \(\omega\), processing time ya job \(j\) kwenye machine \(k\)
\(s^0_{j,k}\)Initial setup time kwa job \(j\)
\(s_{i,j,k}\)Sequence-dependent setup time ya mpito \(i\rightarrow j\)
\(ST_{r,k}\)Katika position \(r\), setup duration ya machine \(k\)
\(A^\omega_{r,k}\)Setup completion time
\(B^\omega_{r,k}\)Processing start time
\(C^\omega_{r,k}\)Processing completion time
\(I^\omega_{r,k}\)Machine idle time
\(w_j\)TWFT priority weight ya job \(j\)
\(c_k^{run}\)Processing unit cost coefficient ya machine \(k\)
\(c_k^{setup}\)Setup unit cost coefficient ya machine \(k\)
\(c_k^{idle}\)Idle unit cost coefficient ya machine \(k\)
\(\alpha,\beta\)Uzani wa TWFT na operational-cost
\(q_\omega\)Scenario probability ndani ya ambiguity set
\(\hat q_\omega\)Nominal scenario probability; katika chanzo uniform \(\hat q_\omega=1/S\)
\(\rho\)KL ambiguity-set robustness radius
\(\eta\)Auxiliary variable katika DRO dual reformulation

Mlinganyo (1): Total Weighted Flow Time

\[ TWFT^\omega= \sum_{r\in R}\sum_{j\in J} w_j x_{j,r} C^\omega_{r,m} \tag{1} \]

Unahesabu nini? Huzidisha completion time ya kila job kwenye mashine ya mwisho kwa job priority weight na kisha kuzijumlisha.

\(C^\omega_{r,m}\), katika scenario \(\omega\), ni completion time ya kazi iliyo kwenye position \(r\) kwenye mashine ya mwisho.

Kadiri \(w_j\) inavyoongezeka, kuchelewa kukamilika kwa job husika kunaleta adhabu kubwa zaidi katika objective. Kwa namna hiyo, kazi za dharura au zenye kipaumbele cha juu zinaweza kupata uzani mkubwa zaidi ndani ya optimization.

Mlinganyo (2): Operational Cost

\[ Cost^\omega= \sum_{k\in M} \left[ c_k^{run}\sum_{r\in R}PT^\omega_{r,k} + c_k^{setup}\sum_{r\in R}ST_{r,k} + c_k^{idle}\sum_{r\in R}I^\omega_{r,k} \right] \tag{2} \]

Cost function ina sehemu tatu:

  • processing cost,
  • sequence-dependent setup cost,
  • machine idle cost.

Chanzo kinaweka tofauti muhimu: kwa scenario isiyobadilika, jumla ya processing time haitegemei mpangilio wa kazi. Kwa hiyo term ya processing-cost hutenda kama gharama ya msingi isiyoepukika ndani ya scenario hiyo. Athari kuu ya uamuzi wa job sequencing juu ya gharama hutokana na vipengele vya setup na idle.

Mpaka wa kisayansi: \(c_k^{run}\), \(c_k^{setup}\) na \(c_k^{idle}\) si thamani zilizochukuliwa kutoka kifaa halisi cha kupima nishati. Objective hii haihesabu kWh halisi, bili ya umeme au utoaji wa CO₂.

Mlinganyo (3): Objective iliyounganishwa

\[ J^\omega= \alpha TWFT^\omega+ \beta Cost^\omega \tag{3} \]

Malengo mawili hubadilishwa kuwa objective moja kwa weighted aggregation.

Kwa computational experiments:

\[ \alpha=\beta=0.5 \]

imetumika.

Hata hivyo, chanzo kinasisitiza kuwa chaguo hili halimaanishi numerical contribution za TWFT na cost ni sawa wala kwamba linawakilisha muundo wa jumla wa decision-maker preference. Vipengele viwili vinaweza kuwa na mizani tofauti.

DRO Inatofautianaje na Stochastic Programming na Robust Optimization ya Kawaida?

Stochastic programming kwa kawaida hudhani kuwa probability distribution fulani inajulikana kwa usahihi, huku Robust Optimization ya kawaida ikilinda dhidi ya hali mbaya zaidi ya parameter realizations moja moja ndani ya uncertainty set; DRO katika utafiti huu, badala ya usambazaji mmoja, hupunguza thamani mbaya zaidi ya expected objective katika familia ya probability distributions zilizo karibu vya kutosha na usambazaji wa kawaida kwa kipimo cha KL divergence.

Mlinganyo (4): Worst-case expected objective

\[ \min J_{DRO} = \min_\lambda \max_{q\in Q_\rho} \sum_{\omega\in\Omega}q_\omega J^\omega \tag{4} \]

Inner maximization hapa hutafuta probability distribution isiyofaa zaidi ndani ya ambiguity set kwa schedule iliyochaguliwa.

Outer minimization huchagua job permutation inayopunguza worst-case expected objective hii kadiri iwezekanavyo.

Mlinganyo (5): Kullback–Leibler ambiguity set

\[ Q_\rho= \left\{ q\in\mathbb{R}_+^S: \sum_{\omega\in\Omega}q_\omega=1,\; \sum_{\omega\in\Omega} q_\omega \ln\left( \frac{q_\omega}{\hat q_\omega} \right) \le\rho \right\} \tag{5} \]

Sharti la kwanza linahakikisha jumla ya probability values ni 1.

Sharti la pili linaruhusu candidate distribution \(q\) kujitenga na nominal distribution \(\hat q\) kwa kiwango kisichozidi \(\rho\) kwa KL divergence.

Robustness Radius \(\rho\) Inafanya Kazi Gani?

\(\rho\) hudhibiti ukubwa wa ambiguity set; \(\rho\) ndogo huiweka optimization karibu na nominal probability distribution, huku \(\rho\) kubwa ikiruhusu usambazaji zaidi unaowezekana na kufanya schedule iwe ya tahadhari zaidi dhidi ya kutokuwa na uhakika wa usambazaji, lakini matokeo yote makuu yaliyoripotiwa katika utafiti huu yanahusu tu sharti la \(\rho=0.05\).

Kwa hiyo haiwezi kuhitimishwa kuwa “ALO ni sawa katika kila thamani ya \(\rho\)” au “SMA ndiyo ya haraka zaidi katika viwango vyote vya robustness”.

Mlinganyo (6): Dual DRO reformulation

\[ J_{DRO} = \min_{\eta>0} \left[ \eta\rho+ \eta\ln \left( \sum_{\omega\in\Omega} \hat q_\omega \exp\left(\frac{J^\omega}{\eta}\right) \right) \right] \tag{6} \]

Reformulation hii hubadilisha sehemu ya inner distribution maximization ya muundo wa nested min-max katika Equation (4) kuwa convex expression ya tabaka moja inayotekelezeka zaidi computationally kwa kutumia Lagrangian duality.

\(\eta\) ni auxiliary dual variable na huoptimizwa kwa kila candidate permutation.

Katika exact enumeration implementation, \(\eta\) ilioptimizwa kwa bounded one-dimensional optimizer ya MATLAB, fminbnd.

Mchoro wa source-derived uliotengenezwa upya kwa Verianla kutoka modeli na mbinu za utatuzi za chanzo. Unaonyesha jinsi uamuzi wa PFSP-SDST unavyounganishwa na DRO objective kupitia stochastic scenarios na KL-divergence ambiguity set.

Equations (7)–(25): Vikwazo vya Feasibility na muda

Mathematical model ya chanzo haijumuishi objective function pekee. Job assignment, uhusiano wa predecessor–successor, setup calculation, machine precedence, completion times na variable domains hufafanuliwa kwa constraints zifuatazo.

\[ \sum_{j\in J}x_{j,r}=1,\qquad \forall r\in R \tag{7} \]

Kila sequence position inapewa job moja kamili.

\[ \sum_{r\in R}x_{j,r}=1,\qquad \forall j\in J \tag{8} \]

Kila job inapewa position moja kamili. Equations (7) na (8) kwa pamoja huunda permutation halali.

\[ y_{i,j,r}\le x_{i,r-1} \tag{9} \]

\[ y_{i,j,r}\le x_{j,r} \tag{10} \]

\[ y_{i,j,r}\ge x_{i,r-1}+x_{j,r}-1 \tag{11} \]

Equations (9)–(11) ni linear adjacency formulation inayohakikisha \(y_{i,j,r}\) huwa 1 tu ikiwa job \(i\) iko katika position iliyotangulia na job \(j\) iko katika position ya sasa.

\[ ST_{1,k} = \sum_{j\in J}s^0_{j,k}x_{j,1} \tag{12} \]

Kwa position ya kwanza hakuna predecessor, hivyo initial setup huhesabiwa kulingana na job ya kwanza iliyochaguliwa.

\[ ST_{r,k} = \sum_{i\in J}\sum_{j\in J} s_{i,j,k}y_{i,j,r}, \qquad r=2,\ldots,n \tag{13} \]

Katika position zinazofuata setup time hutegemea jozi ya predecessor–successor.

\[ PT^\omega_{r,k} = \sum_{j\in J} p^\omega_{j,k}x_{j,r} \tag{14} \]

Constraint hii huhamisha scenario-dependent processing time ya job iliyowekwa kwenye position \(r\) kwenda kwenye position hiyo.

\[ C^\omega_{0,k}=0 \tag{15} \]

\[ C^\omega_{r,0}=0 \tag{16} \]

Mwanzoni mwa scheduling horizon, completion times za job iliyotangulia na upande wa “machine 0” huwekwa sifuri.

\[ A^\omega_{r,k} = C^\omega_{r-1,k} + ST_{r,k} \tag{17} \]

Setup completion time ni jumla ya previous job completion kwenye mashine hiyo hiyo na setup duration inayohitajika.

\[ B^\omega_{r,k}\ge A^\omega_{r,k} \tag{18} \]

Processing haiwezi kuanza kabla setup haijakamilika.

\[ B^\omega_{r,k}\ge C^\omega_{r,k-1} \tag{19} \]

Job haiwezi kuanza kwenye mashine inayofuata kabla haijakamilisha uchakataji kwenye mashine iliyotangulia.

\[ C^\omega_{r,k} = B^\omega_{r,k} + PT^\omega_{r,k} \tag{20} \]

Completion time = processing start + processing duration.

\[ I^\omega_{r,k} = B^\omega_{r,k} - A^\omega_{r,k} \tag{21} \]

Tofauti ya muda kuanzia setup inapokuwa tayari hadi processing ianze ni machine idle time.

\[ ST_{r,k}\ge0 \tag{22} \]

\[ PT^\omega_{r,k}, A^\omega_{r,k}, B^\omega_{r,k}, C^\omega_{r,k}, I^\omega_{r,k}\ge0 \tag{23} \]

Temporal variables haziwezi kuchukua thamani hasi.

\[ x_{j,r}\in\{0,1\} \tag{24} \]

\[ y_{i,j,r}\in\{0,1\} \tag{25} \]

Assignment na adjacency variables ni binary.

Illustrative example: kazi 7, mashine 5

Chanzo kinatoa illustrative instance ili kuweka wazi mantiki ya DRO, kikitumia:

  • \(n=7\) job,
  • \(m=5\) machine,
  • 300 generated processing-time scenarios,
  • \(\rho=0.05\),
  • \(\alpha=0.5\),
  • \(\beta=0.5\)

.

Job weights:

\[ w=[4,2,5,3,1,4,2] \]

Feasible sequence ya kwanza ya maelezo:

\[ \lambda=[J_4,J_1,J_2,J_6,J_3,J_5,J_7] \]

imechaguliwa.

Optimal robust permutation iliyobainishwa na DRO:

\[ \lambda^*=[J_1,J_3,J_6,J_4,J_7,J_2,J_5] \]

ni hiyo.

Representative processing-time scenario tatu

Chanzo kinachagua matrix tatu kutoka 300 generated scenario ili kurahisisha ufasiri, zikawakilisha hali favourable, degraded na variable.

\[ PT^1= \begin{bmatrix} 2&17&9&11&14&9&11\\ 4&8&10&10&13&8&6\\ 7&14&8&9&15&7&11\\ 14&7&8&15&5&9&13\\ 11&9&6&9&8&8&10 \end{bmatrix} \]

\[ PT^2= \begin{bmatrix} 6&11&7&14&15&11&11\\ 7&8&12&11&13&8&5\\ 9&15&6&8&14&5&11\\ 15&9&10&14&4&10&12\\ 11&7&7&12&10&9&9 \end{bmatrix} \]

\[ PT^3= \begin{bmatrix} 10&12&10&14&15&9&9\\ 8&7&12&12&12&7&6\\ 9&15&5&12&16&6&11\\ 15&6&14&15&8&11&12\\ 10&8&8&8&7&10&8 \end{bmatrix} \]

Safu mlalo zinawakilisha mashine, na safu wima zinawakilisha kazi.

Uchanganuzi wa Kutokuwa na Uhakika wa GUM Unaongeza Nini kwa DRO?

Wakati DRO huchagua job sequence kwa namna robust chini ya probability-distribution ambiguity, uchanganuzi wa GUM hupima kando jinsi matokeo ya makespan ya optimal schedule yanavyotawanyika katika scenario realizations; chanzo huhesabu mean makespan, combined standard uncertainty na \(k=2\) expanded uncertainty kwa 300 scenario na kuripoti optimal makespan kuwa \(129.45\pm9.62\) pamoja na expanded interval \([119.83,139.07]\).

Mlinganyo (26): Mean makespan

\[ \overline{C}_{max} = \frac{1}{N} \sum_{\omega=1}^{N} C_{max}(\omega) \tag{26} \]

Hapa \(N=300\) ni generated scenario.

Mlinganyo (27): Combined standard uncertainty

\[ u_c^2(C_{max}) = \frac{1}{N-1} \sum_{\omega=1}^{N} \left[ C_{max}(\omega)-\overline{C}_{max} \right]^2 \tag{27} \]

Usemi huu huhesabu variance ya scenario makespan values. Combined standard uncertainty \(u_c\) ni mzizi wa mraba wa variance.

Mlinganyo (28): Expanded uncertainty

\[ U=k\,u_c \tag{28} \]

Chanzo hutumia:

\[ k=2 \]

na kuihusisha na takriban %95 coverage level.

Mlinganyo (29): Matokeo ya Makespan

\[ C_{max} = \overline{C}_{max} \pm U \tag{29} \]

Kwa illustrative example:

\[ C_{max}=129.45\pm9.62 \]

na expanded uncertainty interval:

\[ [119.83,\;139.07] \]

imetolewa.

Haiigi histogram ya Figure 1 ya chanzo; inaonyesha upya mean makespan na mipaka ya expanded uncertainty iliyoripotiwa na chanzo kama mchoro huru wa interval kwa Verianla.

Ulinganisho wa optimal DRO permutation na manual permutation

ScenarioHali\(TWFT^\omega\)\(Cost^\omega\)\(J^\omega\)
1Favourable1406.2546.07976.14
2Degraded1612.7558.081085.4
3Variable1787.2586.981187.1
ScenarioHali\(TWFT^\omega\)\(Cost^\omega\)\(J^\omega\)
1Favourable2262.4557.511410
2Degraded2335.7570.811453.3
3Variable2359.1591.221475.2

Kwa kuwa processing-time realizations, setup times, machine cost coefficients na job weights zilezile zinatumika, tofauti katika illustrative comparison hii inatokana na sequence selection.

Source Figures 2–4 zinaonyesha Gantt charts za optimal DRO schedule kwa favourable, degraded na variable scenarios. Picha za chanzo zinaonyesha jinsi machine occupation, setup, idle na job progression zinavyorefuka scenario inapobadilika. Kwa kuwa Exact Gantt bar coordinates hazijachapishwa katika jedwali la namba, Verianla haichori upya michoro hii kwa usahihi bandia.

Mbinu na Matokeo ya Utafiti

Computational experimental framework

KigezoThamani ya chanzo
Idadi ya Job4–300
Idadi ya Machine2–20
\(\mu_P\)\(U(5,15)\)
\(\sigma_P\)\(U(0.5,2)\)
Scenario processing time\(PT\sim N(\mu_P,\sigma_P^2)\)
Search scenario set\(S_{small}=30\)
Final evaluation scenario set\(S_{large}=300\)
Base random seed7
Initial setup\(setup_0\sim U(0.5,2.5)\)
Sequence-dependent setup\(setup_{seq}\sim U(0.5,3.5)\)
Job weight\(w_j\sim U(1,5)\)
Processing cost coefficient\(c_k^{run}\sim U(1,1.5)\)
Setup cost coefficient\(c_k^{setup}\sim U(0.6,1)\)
Idle cost coefficient\(c_k^{idle}\sim U(0.2,0.5)\)
TWFT weight\(\alpha=0.5\)
Operational-cost weight\(\beta=0.5\)
Ambiguity radius\(\rho=0.05\)
GRASP RCL parameter\(\alpha_{RCL}=0.7\)
Maximum iterations100
Random-Keys population\(nPop=30\)
Independent runs50
MATLABMATLAB R2021a
Exact solverIBM ILOG CPLEX Optimization Studio 12.10.0
HardwareASUS VivoBook X1502VA, 13th Gen Intel Core i9, 16 GB RAM

Kwa nini \(\alpha_{RCL}\) ni 0,7?

Chanzo kilichunguza thamani:

\[ \alpha_{RCL}\in\{0.3,0.5,0.7\} \]

wakati wa preliminary exploratory tests na kuchagua 0,7 kama practical compromise inayofaa zaidi kati ya solution quality na diversification.

Mchakato huu hauwasilishwi kama systematic hyperparameter optimization.

Je, 100 iteration zinatoa computational budget sawa kwa algorithms zote?

Hapana. Ingawa chanzo kinatumia 100 iteration kwa iterative algorithms zote, kinaeleza wazi kuwa algorithms tofauti zinaweza kufanya idadi tofauti ya DRO objective evaluation ndani ya iteration moja.

Kwa hiyo, 100 iteration haimaanishi kila mbinu imepewa computational work sawa. Kwa sababu hii CPU time ililinganishwa kando.

Exact enumeration inafanyaje kazi?

Kwa small instances, CPLEX assignment model huzalisha feasible permutation ambayo haijajaribiwa kabla katika kila iteration.

Baada ya permutation kuwa decoded, setup, processing, start/completion na idle variables huhesabiwa nje na full DRO objective hutathminiwa.

Kisha no-good cut huongezwa ili kuzuia permutation ileile kuzalishwa tena:

\[ \sum_{j\in J}\sum_{r\in R} x^*_{j,r}x_{j,r} \le n-1 \]

Kwa kuwa kila feasible permutation huzalishwa mara moja kamili, katika small instances permutations zote \(n!\) hutathminiwa exhaustively.

Chanzo kimeweka exact procedure kwa instances zenye hadi job 10.

GRASP-DRO

GRASP hutumia randomised greedy construction.

Initial job priority score:

\[ \phi_j= w_j \sum_{k=1}^{m} \mu P_{j,k} \]

huundwa.

Kati ya candidate solutions, Restricted Candidate List:

\[ RCL= \left\{ cand_t: DRO(cand_t) \le J_{min} +\alpha_{RCL}(J_{max}-J_{min}) \right\} \]

hufafanuliwa na random candidate huchaguliwa kutoka RCL.

HGRASP-DRO

HGRASP inaunganisha vipengele vinne vikuu:

  • DRO-adapted NEH initialization,
  • GRASP constructive search,
  • swap-based local search,
  • restart/diversification mechanism.

Mwanzoni mwa iteration inayofuata, original robust NEH sequence hutumiwa tena kwa uwezekano wa %50; vinginevyo mpangilio wa mwanzo hutofautishwa kwa random swaps.

ALO-DRO

Kwa kuwa Ant Lion Optimizer hufanya kazi kiasili kwenye continuous search space, Random Keys representation ilitumika ili kuzalisha job permutation.

Thamani za continuous vector hupangwa na kubadilishwa kuwa feasible permutation. Wakati wa population search, elite solution huhifadhiwa na candidate schedules hutathminiwa kwa DRO objective kupitia reduced scenario set.

SMA-DRO

Slime Mold Algorithm pia hutumia Random Keys representation. Population hu-update kwa adaptive weighting; solutions bora hupata influence kubwa zaidi, huku solutions dhaifu zikiendelea kuwa na nafasi ndani ya population ili exploration isipotee.

Chanzo kimetumia \(nPop=30\) kwa Random-Keys population settings zote.

Matokeo ya small-scale exact benchmark

InstanceExactExact CPUGRASPCPUHGRASPCPUALOCPUSMACPU
4×2101.022.35101.021.61101.022.74101.022.38101.023.12
4×4200.661.10200.660.42200.660.96200.661.00200.660.94
4×6267.160.49267.161.00267.161.11267.161.15267.161.08
6×2239.238.61239.20.85239.22.49239.21.25239.21.13
6×4338.4938.89338.490.86338.492.59338.491.26338.491.16
6×6410.6138.55410.610.87410.612.80410.611.27410.611.16
8×2368.3989,964369.621.31368.395.22368.391.27368.391.13
8×4562.4130,600588.911.88562.47.44562.41.91562.41.71
8×6642.6470,895646.411.35642.645.51642.641.29642.641.17
9×4532.6785,640536.151.33532.675.99533.621.09533.620.97
10×2509.65108,450517.294.08509.6519.16509.652.84509.652.45

HGRASP ilizalisha upya exact objective value katika small-scale instances hizi zote.

Exact enumeration huwa computationally expensive haraka sana kadiri instance inavyokua.

Matokeo ya Medium-scale

InstanceGRASPCPUHGRASPCPUALOCPUSMACPU
10×5798.971.96785.1710.71788.961.38785.631.23
10×101413.72.041397.112.711397.11.441397.11.28
10×151932.22.151904.913.131904.91.511904.91.35
20×52674.77.382529.771.172535.71.962535.11.54
20×103679.126.493509.4268.033524.67.723526.95.98
20×154339.957.774171.0885.544183.042.154184.211.76
30×55078.1713.024749.670.834528.462.074564.331.72
30×106352.4214.076006.9677.825888.472.225895.961.89
30×158242.8515.288022.30867876.462.457876.792.10
40×58846.7727.58386.14149.88016.264.817990.323.49
40×1010,849.972.910,296.85286.69860.566.789864.145.28
40×1513,639.628.2813,111.05105.4212,695.52.8912,627.732.26
50×512,626.237.712,006.1100.7210,170.42.6010,961.061.83
50×1014,524.4145.3813,739.86410.7113,028.19.6113,079.047.27
50×1517,4824616,967128.8516,0973.1715,9212.43
60×516,11758.3815,679127.8214,5972.9514,4532.03
60×1021,6872028.521,143616.8419,65613.2719,7249.57
60×1526,425.670.5126,124.06160.0524,834.73.4824,842.042.65
70×522,5051162.521,971643.4620,14312.7820,2348.66
70×1027,914108.6327,491209.625,2544.5325,0342.98
70×1531,230.1181.3530,464.62506.5928,931.517.0729,210.985.08
80×529,386.5108.5828,444.54185.9526,555.803.6926,178.902.24
80×1036,061.27119.9235,943.01206.5133,641.23.6233,134.32.56
80×1536,972.0225236,608.48399.4734,376.156.8734,079.124.81
90×536,832.33136.636,661.97211.8933,847.333.6634,033.452.23
90×1046,181.93298.5645,608.33438.1042,326.876.2642,919.344.36
90×1549,909.87298.6749,594.48486.8546,529.068.4546,315.515.97

Kadiri medium scale inavyoongezeka, solution quality ya GRASP hudhoofika kwa kulinganisha; HGRASP huiboresha GRASP, lakini katika medium instances kubwa zaidi ALO na SMA mara nyingi hutoa DRO values za chini.

Matokeo ya Large-scale

InstanceGRASPCPUHGRASPCPUALOCPUSMACPU
100×1053,070.93217.752,270.26322.6548,791.984.4949,201.73
100×2064,020.76407.7562,724.74487.2859,460.947.0559,525.175.49
150×10112,8001290.4111,17038,421107,0706.8078106,9404.2935
150×20133,2521305129,0204540.02124,2307.067120,0144.305
200×10194,8801477.5194,0305541.4180,9407.2912181,0404.5586
200×20220,8906762.9218,31012,749203,98010.55210,2507.7775
250×10294,6806529.8295,28012,448278,10036.944284,34021.774
250×20326,43017,367321,59053,927306,21056.61305,19041.28
300×10416,76013,019413,9003824.1393,59010.779393,4306.9293
300×20466,7408101464,82020,180446,44015.3965442,83011.7650

Katika large scale, GRASP kwa ujumla hutoa objective values zilizo juu zaidi. HGRASP huiboresha GRASP, lakini computational time huongezeka sana kwa sababu ya local search yenye uzito mkubwa.

ALO na SMA huwa wazi kuwa competitive zaidi katika matatizo makubwa. Hakuna mojawapo inayomshinda mwingine katika kila instance.

Representative 300×20 instance: mikimbio huru 50

MbinuMedian DROAverage DROStd. Dev.Best DROMaximum DROAverage CPU
GRASP1,010,536.651,006,974.817713.28Haijatolewa katika sentensi hii ya maandishi ya chanzo1,012,263.52—
HGRASP1,002,959.091,002,307.415487.10996,523.57—12,697.84 s
ALO962,154.30961,918.263583.37—965,377.78—
SMA966,327.54964,057.766827.03956,384.95969,460.799.16 s

Katika representative experiment hii, chanzo kinaitathmini ALO kuwa mbinu iliyo robust zaidi kwa sababu ya median/average ya chini na variability ya chini; SMA hutathminiwa kuwa optimization performer yenye nguvu kwa sababu ya individual DRO solution bora zaidi na average computational time fupi zaidi.

Figure 6 ni convergence history ya representative execution moja tu; si statistical summary ya 50 run. GRASP na HGRASP hufikia plateau mapema, huku ALO na SMA zikiendelea kuboreka kwa muda mrefu zaidi. Kwa kuwa raw iteration-level series hazijachapishwa, Verianla haichori Figure 6 upya kama exact curve bandia.

Jaribio la Medium-scale Friedman

MbinuDRO Mean RankCPU Mean Rank
GRASP4.0003.074
HGRASP2.6303.926
ALO1.6302.000
SMA1.7411.000

Solution quality:

\[ \chi^2=60.115,\qquad df=3,\qquad p=5.56\times10^{-13} \]

Computational time:

\[ \chi^2=78.778,\qquad df=3,\qquad p=5.94\times10^{-17} \]

Matokeo haya yanakataa null hypothesis kwamba medium-scale algorithms zina performance sawa.

Jaribio la Large-scale Friedman

MbinuDRO Mean RankCPU Mean Rank
GRASP3.93.2
HGRASP3.13.8
ALO1.52.0
SMA1.51.0

DRO objective:

\[ \chi^2=25.920,\qquad df=3,\qquad p=9.91\times10^{-6} \]

Computational time:

\[ \chi^2=28.080,\qquad df=3,\qquad p=3.49\times10^{-6} \]

Kati ya ALO na SMA, Ipi ni Bora Zaidi?

Katika matokeo ya large-scale ya utafiti huu, Friedman mean rank ya ALO na SMA kwa solution quality ni sawa 1,5 na jaribio la Wilcoxon–Holm post-hoc halionyeshi tofauti muhimu ya DRO kati yao; ALO inaonekana robust zaidi katika representative 300×20 runs kwa median/average na variability ya chini, huku SMA ikitoa individual solution bora zaidi na computational-time rank bora zaidi, hivyo chanzo hakitangazi algorithm moja kuwa bora kabisa kwa vigezo vyote.

Matokeo ya Large-scale Wilcoxon–Holm post-hoc

UlinganishoDRO Raw pDRO Holm pDROCPU Raw pCPU Holm pCPU
GRASP vs HGRASP0.0039060.011719Muhimu0.1054690.105469Si muhimu
GRASP vs ALO0.0019530.011719Muhimu0.0019530.011719Muhimu
GRASP vs SMA0.0019530.011719Muhimu0.0019530.011719Muhimu
HGRASP vs ALO0.0019530.011719Muhimu0.0019530.011719Muhimu
HGRASP vs SMA0.0019530.011719Muhimu0.0019530.011719Muhimu
ALO vs SMA1.0000001.000000Si muhimu0.0019530.011719Muhimu

Kusema kwamba ALO au SMA ni bora kuliko nyingine kwa solution quality hakuungwi mkono na jaribio hili.

Kwa computational time, tofauti ya ALO–SMA ni muhimu na Friedman ranking inaonyesha SMA kuwa favorable zaidi.

Matokeo yanayoungwa mkono na utafiti

  • PFSP-SDST, stochastic processing times na operational cost zinaweza kumodeliwa ndani ya optimization framework moja kwa DRO.
  • KL-divergence ambiguity set imetumika kufafanua distributional uncertainty kuzunguka nominal probability distribution.
  • Kwa small instances, CPLEX-assisted exhaustive enumeration imetoa global optimum benchmark.
  • HGRASP imezalisha upya exact objective value katika small-scale instances zote zilizojaribiwa.
  • Kadiri medium na large scale zinavyoongezeka, ALO na SMA za population-based zimekuwa competitive zaidi.
  • Kwa large-scale solution quality, jaribio la Friedman limeonyesha tofauti muhimu kati ya algorithms.
  • Kwa large-scale CPU time, jaribio la Friedman limeonyesha tofauti muhimu kati ya algorithms.
  • ALO na SMA zimepata mean rank sawa kwa large-scale DRO quality.
  • Tofauti ya pairwise DRO ya ALO–SMA si muhimu.
  • SMA ndiyo mbinu favorable zaidi kwa computational-time ranking.
  • Katika representative 300×20 instance, ALO imeonyesha median/average na standard deviation ya chini.
  • Katika representative instance hiyo hiyo, SMA imetoa individual DRO solution bora zaidi.

Matokeo yasiyoungwa mkono na utafiti

  • Framework haijathibitishwa katika kiwanda halisi.
  • Operational cost si kipimo cha matumizi halisi ya umeme.
  • Modeli haihesabu CO₂/emission reduction.
  • Haijaonyeshwa kuwa matokeo ya \(\rho=0.05\) yatabaki sawa kwa ambiguity radii nyingine.
  • \(\alpha=\beta=0.5\) haionyeshi kuwa umuhimu wa maamuzi halisi au numerical scales za TWFT na cost ni sawa.
  • Haijaonyeshwa kuwa ALO ni bora kuliko SMA katika instances zote.
  • Haijaonyeshwa kuwa SMA ni bora kwa kitakwimu kuliko ALO kwa solution quality.
  • Global optimum haijulikani kwa medium na large instances.
  • Matokeo ya synthetic benchmark si performance ya moja kwa moja ya commercial Industry 4.0 deployment.
  • Parameter tuning si exhaustive/systematic.

Vikwazo vikuu

Data za usanisi: Kwa kuwa hakuna public benchmark, processing, setup na cost parameters zimetengenezwa kutokana na controlled synthetic distributions.

Hakuna validation halisi ya viwandani: Hakuna jaribio la uwanjani lililofanywa kwenye production line maalumu.

Ambiguity radius isiyobadilika: Matokeo yote makuu yanategemea sharti la \(\rho=0.05\).

Hakuna sensitivity analysis: Systematic calibration/sensitivity analysis kwa thamani tofauti za \(\rho\) imeachwa kama future work.

Fixed algorithm settings: \(\alpha_{RCL}\), iteration limit, population sizes na algorithmic settings nyingine ni chaguo za practical/preliminary; systematic tuning haijafanywa.

Iteration sawa ≠ budget sawa: Algorithms zinaweza kufanya idadi tofauti ya objective evaluation kwa kila iteration.

Operational cost si nishati ya kimwili: Cost coefficients si direct power, electricity-price au emissions measurements.

Exact method scalability: Exhaustive enumeration imetumika kwa small instances pekee kutokana na combinatorial explosion.

Upeo wa Figure 5/6: Robustness boxplot na convergence curves ni za representative 300×20 instance; haziwezi kujumlishwa peke yake kwa instances zote.

Code availability: MATLAB source code si public wakati wa uchapishaji.

Utafiti wa baadaye

Chanzo kinapendekeza upanuzi ufuatao:

  • stochastic setup times,
  • machine disruptions,
  • fluctuating energy prices,
  • industrial case studies halisi,
  • \(\rho\) calibration na sensitivity analysis,
  • systematic metaheuristic parameter tuning,
  • comparison pana na deterministic scheduling, stochastic programming, conventional DRO na RO,
  • out-of-sample evaluation chini ya uncertainty distributions tofauti,
  • multi-objective DRO inayoshughulikia kwa pamoja production efficiency, real energy consumption na sustainability indicators.

Maelezo ya Chanzo na Mbinu

Utafiti asili: Distributionally Robust Optimization for Permutation Flow Shop Scheduling with Sequence-Dependent Setup Times and Operational Cost Under Uncertainty in Industry 4.0 Manufacturing Systems.

Waandishi: Hafsa Mimouni, Abdelilah Jalid, Said Aqil.

Mpangilio wa waandishi: Mpangilio katika PDF ya chanzo na rekodi rasmi ya MDPI umehifadhiwa.

Mchango sawa: Hakuna taarifa ya equal-contribution katika chanzo.

Mwandishi wa mawasiliano: Hafsa Mimouni.

Taasisi 1: Mechanical and Thermal Processes and Controls (PCMT) Laboratory, National Graduate School of Arts and Crafts, Mohamed V University, Rabat, Morocco.

Taasisi 2: Intelligent Systems, Industrial and Mechanical Engineering (LISIME) Laboratory, National Graduate School of Arts and Crafts, Hassan II University, Casablanca, Morocco.

Jarida: Sustainability.

Mchapishaji: MDPI, Basel, Switzerland.

Juzuu / namba: 18(18).

Namba ya makala: 9278.

Mwaka wa uchapishaji: 2026.

Received: 26 June 2026.

Revised: 1 September 2026.

Accepted: 3 September 2026.

Published: 9 September 2026.

DOI: 10.3390/su18189278.

Aina ya chanzo: Peer-reviewed computational optimization research article.

Preprint: Hakuna toleo tofauti la preprint lililotajwa katika chanzo.

Leseni: Creative Commons Attribution (CC BY).

Aina ya utafiti: Utafiti wa mathematical optimization na computational-comparison unaotegemea benchmark za usanisi.

Tatizo kuu: PFSP-SDST with uncertain processing times.

Mbinu kuu: Distributionally Robust Optimization inayotumia Kullback–Leibler divergence ambiguity set.

Malengo makuu: Kupunguza Total Weighted Flow Time na machine-dependent operational cost kwa weighted aggregation.

Suluhisho exact: Exhaustive enumeration + no-good cuts inayosaidiwa na IBM ILOG CPLEX Optimization Studio 12.10.0; small instances, hadi job 10.

Approximate methods: GRASP, proposed HGRASP, ALO na SMA.

Mazingira ya programu: MATLAB R2021a; CPLEX 12.10.0.

Hardware: ASUS VivoBook X1502VA, 13th Generation Intel Core i9, 16 GB RAM.

Ukubwa wa benchmark: 4–300 job, 2–20 machine.

Processing mean: \(\mu_P\sim U(5,15)\).

Processing standard deviation: \(\sigma_P\sim U(0.5,2)\).

Scenario generation: \(PT\sim N(\mu_P,\sigma_P^2)\), strictly-positive lower bound hutumiwa inapohitajika.

Scenario sets: \(S_{small}=30\), \(S_{large}=300\).

Base seed: 7.

Initial setup: \(U(0.5,2.5)\).

Sequence-dependent setup: \(U(0.5,3.5)\).

Job weights: \(U(1,5)\).

Run-cost coefficient: \(U(1,1.5)\).

Setup-cost coefficient: \(U(0.6,1)\).

Idle-cost coefficient: \(U(0.2,0.5)\).

Objective weights: \(\alpha=\beta=0.5\).

Ambiguity radius: \(\rho=0.05\).

GRASP RCL: \(\alpha_{RCL}=0.7\); 0.3, 0.5 na 0.7 zilichunguzwa kwa preliminary exploratory.

Iteration limit: 100.

Random-Keys population: 30.

Independent stochastic runs: 50.

Illustrative GUM result: \(129.45\pm9.62\), expanded interval \([119.83,139.07]\), \(k=2\).

Medium Friedman — DRO: χ² = 60.115, df = 3, p = 5.56 × 10⁻13.

Medium Friedman — CPU: χ² = 78.778, df = 3, p = 5.94 × 10⁻17.

Large Friedman — DRO: χ² = 25.920, df = 3, p = 9.91 × 10⁻6.

Large Friedman — CPU: χ² = 28.080, df = 3, p = 3.49 × 10⁻6.

Large solution-quality ranking: ALO = 1.5, SMA = 1.5, HGRASP = 3.1, GRASP = 3.9.

Large computational-time ranking: SMA = 1, ALO = 2, GRASP = 3.2, HGRASP = 3.8.

ALO–SMA post-hoc DRO: Holm-adjusted p = 1.000000; hakuna tofauti muhimu.

ALO–SMA post-hoc computational time: Holm-adjusted p = 0.011719; kuna tofauti muhimu.

Uthibitishaji halisi wa uwanjani: Hakuna; umependekezwa kama future work.

Matumizi halisi ya nishati: Hayajapimwa. Operational-cost coefficients si direct physical energy, electricity price, power au emissions.

Funding: Hakuna External funding.

Institutional Review Board: Not applicable.

Informed Consent: Not applicable.

Data Availability: Synthetic datasets na run-level outputs hazikuhifadhiwa kama standalone historical files; generation procedures, scenario settings, parameter values na seed zimetolewa katika makala. Synthetic instances/output zinaweza kuzalishwa tena/kutolewa kutoka kwa corresponding author kwa reasonable request.

Source code: MATLAB implementation si public; inaendelea kutengenezwa kama ongoing research implementation.

Conflicts of Interest: Authors declare no conflicts of interest.

Michango ya waandishi: Conceptualization: H.M., A.J.; methodology: H.M., A.J.; software: H.M.; validation: H.M., A.J., S.A.; formal analysis: H.M.; investigation: H.M.; data curation: H.M.; original draft: H.M.; review/editing: H.M., A.J., S.A.; visualization: H.M.; supervision: A.J., S.A.

Dokezo la istilahi: Utafiti hutumia hasa istilahi PFSP-SDST; katika baadhi ya aya za computational-method kuna maandishi PFSSP/PFSSP-SDST. Kwa kuwa chanzo hakifafanui hizi kuwa darasa tofauti la tatizo, Verianla huhifadhi PFSP-SDST kama canonical term kuu.

Mpaka mkuu wa ufasiri: Comparative computational findings zote ni halali kwa synthetic benchmark conditions, fixed \(\rho=0.05\) na fixed algorithm settings zilizotumika.


Shiriki:

Maoni huchapishwa baada ya kukaguliwa. Maoni yako yatapitia mchakato wa idhini na yataonekana yakikubaliwa.

Acha maoni

Anwani yako ya barua pepe haitachapishwa. Sehemu za lazima zimewekewa alama ya *