1995
DOI: 10.1287/mnsc.41.10.1693
|View full text |Cite
|
Sign up to set email alerts
|

Characterization and Generation of a General Class of Resource-Constrained Project Scheduling Problems

Abstract: This paper addresses the issue of how to generate problem instances of controlled difficulty. It focuses on precedence- and resource-constrained (project) scheduling problems, but similar ideas may be applied to other network optimization problems. It describes a network construction procedure that takes into account a) constraints on the network topology, b) a resource factor that reflects the density of the coefficient matrix, and c) a resource strength, which measures the availability of resources. The stro… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1

Citation Types

3
293
0
9

Year Published

1997
1997
2008
2008

Publication Types

Select...
6
2
1

Relationship

3
6

Authors

Journals

citations
Cited by 523 publications
(322 citation statements)
references
References 29 publications
3
293
0
9
Order By: Relevance
“…Mingozzi et al (1994) compute lb 3 using a heuristic for the weighted node packing problem. Demeulemeester and Herroelen (1995) Demeulemeester and Herroelen (1995) indicate that lb; indeed outperforms lb o and that incorporating lb; in their branch-and-bound procedure reduces the computational effort to solve the 110 problems of Patterson (1984) and the 480 problems of Kolisch et al (1992). Note that, contrary to lb 3 as calculated by Mingozzi et al (1994), the procedure above may yield an lb; which is smaller than lbo, but this constitutes no real disadvantage since lb o is calculated as well and the final value for the lower bound equals…”
Section: A Time-and Resource-based Lower Boundmentioning
confidence: 90%
See 1 more Smart Citation
“…Mingozzi et al (1994) compute lb 3 using a heuristic for the weighted node packing problem. Demeulemeester and Herroelen (1995) Demeulemeester and Herroelen (1995) indicate that lb; indeed outperforms lb o and that incorporating lb; in their branch-and-bound procedure reduces the computational effort to solve the 110 problems of Patterson (1984) and the 480 problems of Kolisch et al (1992). Note that, contrary to lb 3 as calculated by Mingozzi et al (1994), the procedure above may yield an lb; which is smaller than lbo, but this constitutes no real disadvantage since lb o is calculated as well and the final value for the lower bound equals…”
Section: A Time-and Resource-based Lower Boundmentioning
confidence: 90%
“…Recently, Mingozzi et al (1994) Stinson et al (1978) on the 110 RCPSP instances assembled by Patterson (1984) and the 480 randomly generated RCPSP instances of Kolisch et al (1992). Mingozzi et al (1994) have also developed a new branch-and-bound procedure for the RCPSP based on this new mathematical formulation, which incorporates the most promising new lower bound lb 3 .…”
Section: A Time-and Resource-based Lower Boundmentioning
confidence: 99%
“…For example, the precedence ratio (also known as order strength (Mastor, 1970), flexibility ratio (De Reyck and Herroelen, 1995), and density (De Reyck and Herroelen, 1995)), i.e., the ratio between the number of pairs of activities which are ordered by precedence constraints and the overall number of pairs of distinct activities, is also important (a high precedence ratio makes the problem easier). Although some researchers, e.g., (Kolisch et al, 1995), have worked on such indicators, we believe much more work is necessary to discover which indicators are appropriate for designing, selecting, or adapting constraint programming techniques with respect to the characteristics of a given problem.…”
Section: Motivationsmentioning
confidence: 99%
“…Note, the slight corruption in denoting the network complexity NC within the base parameter setting of Table 7. Again, the variable paramter combination related to a cell can be found in the Ales XYZPAR.MM, e.g., Note, once more, for standardizational purpose we have renamed the files originally presented in [17] from MM1_1.DAT,..., MM64_10.DAT to J101J..MM,..., J1064_10.MM. Contrary to the single-mode case, due to mode-coupling via resource constraints, some of the multimode instances do not have afeasible Solution (cf.…”
mentioning
confidence: 99%