2016
DOI: 10.1016/j.cie.2016.03.024
|View full text |Cite
|
Sign up to set email alerts
|

Minimizing tardiness and maintenance costs in flow shop scheduling by a lower-bound-based GA

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
29
0

Year Published

2018
2018
2023
2023

Publication Types

Select...
8
1

Relationship

0
9

Authors

Journals

citations
Cited by 64 publications
(29 citation statements)
references
References 43 publications
0
29
0
Order By: Relevance
“…(2016) introduced a constructive heuristic based on the one proposed by Laha and Sarin (2009). Yu and Seif (2016) proposed a lower bound based on a GA to minimize the total tardiness and maintenance cost. Rossi et al.…”
Section: Related Workmentioning
confidence: 99%
“…(2016) introduced a constructive heuristic based on the one proposed by Laha and Sarin (2009). Yu and Seif (2016) proposed a lower bound based on a GA to minimize the total tardiness and maintenance cost. Rossi et al.…”
Section: Related Workmentioning
confidence: 99%
“…Specifically, in Fig. 2, if workstation 1 is to be maintained, tasks (1,2,4) are reallocated into workstations 2 and tasks (8,10) into workstation 3. After maintenance, all these tasks return immediately and the production mode under PM scenario 2 is changed back to the regular operation scenario.…”
Section: B Assignment Plans and Task Alterationsmentioning
confidence: 99%
“…In contrast, existing literature has demonstrated that integrating PM into the production scheduling within flexible flow shops can reduce the running cost and system unavailability time. Specifically, Yu and Seif [10] demonstrated the integration of them can shorten the total maintenance and tardiness costs. Feng et al [11] addressed a sequence-dependent group scheduling problem within a flexible flow shop and they claimed that implementing PM at the idle time between groups can shorten the production cycle time and save the manufacturing cost.…”
Section: Introductionmentioning
confidence: 99%
“…In general, such a scheduling problem with maintenance is NP-hard [55,57,59]. Even if only one single machine needs to be maintained within a maintenance window, the problem is still NP-hard.…”
Section: Problem Formulationmentioning
confidence: 99%