![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
|
Previous | Next | Contents | Index | Navigation | Glossary | Library |
In the Setback Days table, notice how single level resource requirements for components B and C are rolled up to become cumulative resource requirements for A. Note how the setback days and total hours change for the cumulative requirements.
For example, 4 days are required to build A, based on item lead times of 2 days each for A, B, and C. D1, R2 is needed at the start of operation 20 on day 2. Setback days for D1, R2 becomes 3 days when the resource requirement for D1, R2 is offset from the completion date of A rather than the completion date of C.
Previous | Next | Contents | Index | Navigation | Glossary | Library |