.png){kind=icon}
返回
Phantom float in commercial scheduling software
.png){kind=icon}
PRE
AI
DOI：10.1016/j.autcon.2019.03.014.png)
.png){kind=icon}
原文求助.png){kind=icon}
分享.png){kind=icon}
收藏
摘要
En 中文
On a regular basis, construction professionals use scheduling software to resource load the schedules without paying attention to the resulting critical path. Current scheduling software fix the resource supply-demand problem by performing a Resource-Constrained Scheduling (RCS) technique, but they report incorrect total float values and a broken critical path. RCS calculations suggest that activities have float but much of this float does not exist (phantom float). Phantom float is created in resource-constrained schedules because the existing RCS methodologies neglect the resource relationships that arise between activities when competing for the same but unavailable resources. This paper illustrates the presence of phantom float in Primavera's P6 and Microsoft's Project schedules. After removing phantom float from the schedule, non-critical activities may become resource critical and the actual float may be shorter than calculated or may be altogether non-existent. Users of P6 and MS Project should recognize that the calculation of total float by the software relies on a time based context (LF - EF and/or LS - ES) ignoring the presence of resource constraints. Therefore, the float reported cannot be trusted or used to mitigate delaying events, like the traditional time-based context definition of total float suggests. Currently, research is being carried out in order to remove phantom float from P6 and Microsoft Project schedules.
Keyword:
Phantom float
Resource-constrained schedules
Scheduling software
AI总结
对已上传原文的论文进行重点信息的提取，主要内容包括：简要概述、研究摘要、背景介绍、关键亮点、图文解析、展望与总结。
期刊
IF:
11.5
论文数:
6.3K
被引数:
4.2W
机构
暂无机构信息
引用论文
.png){kind=icon}
查看更多内容