It’s not possible to make precedency relationships between activity steps. Often work packages contain deliverables that can be tracked with either activity steps or WBS milestones (see Activity Steps vs WBS Milestones). These are amounts of work done by a set of people with a defined scope, budget and time.
The lowest level of the WBS are the Work Packages. Usage 2 : Work Package summary / budget / Controls Project Initiation / Engineering / Execution / Commissioning). In this case, you can’t use a WBS Summary if your Work Breakdown Structure is phase-based (e.g. For example: say some overhead resources only work from the start of the project until the end of the engineering phase and they are not budgeted for the execution and commissioning of the project. The advantage of the Level of Effort over a WBS summary is that you have the flexibility to link it to any activity you want. They will automatically change their dates based on the progress of the project. Level of Effort activities are most popularly used to allocate overhead resources to your project. There are no links needed and the start/finish will be the earliest start/latest finish of the activities under that WBS node. They will span over the duration of the earliest linked (FS and SS) date and the latest linked (FF and exceptionally SF – see Best Practices) date.Īctivities of the type “WBS Summary” have a duration calculated from the activities within the WBS. The duration of activities of the type “Level of Effort” (= LoE) are calculated from their predecessor dates (no successors – see Best Practices). The major difference with ‘normal’ activities is that their durations are flexible. Unlike Milestones they can have resource-assignments. For more information about Oracle (NYSE:ORCL), visit “Level of Effort” and “WBS Summaries” have many similarities to normal activities. Oracle offers a comprehensive and fully integrated stack of cloud applications and platform services. My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts. To view full details, sign in with your My Oracle Support account.ĭon't have a My Oracle Support account? Click to get started! Notice duration is not calculated correctly.The issue can be reproduced at will with the following steps:
Level of Effort activities default to 5 days and do not calculate correctly.Įxpect LOE activities to calculate duration based on their relationships. Information in this document applies to any platform. Oracle Primavera Cloud Service - Version 19.9 to 20.9 Level Of Effort Activities Not Calculating Correct Durations
0 kommentar(er)
