|
The WBS structure is a key object for top-down cost and budget control. It is therefore a function that in almost all cases should be handled by SAP even when external scheduling or project management tools are being used as well. The WBS is the most likely area where actual charges will hit a project, unless a detailed time and expense entry system is used in synchronization with the network structure of activities. In respect to the project structure, there are a number of aspects to consider: SAP concepts and terms are not identical to those used in other project management software packages. To reflect the full spectrum of a complex project structure, SAP uses no less than 8 different objects: PD, WBS, Network, Activity, Activity Element, Milestone, Work order, and Operation. On top of that SAP may have IM programs and IM positions. Compare this to Primavera where you have a mere 3 (project, WBS and Activities), or with MS Project where you have 2 (project and tasks). When used in conjunction with other project management systems, it is likely that SAP WBS numbers will be the unique ID used in such tools. WBS structures are often integrated with a higher-level investment management (IM) structure, and on the lower level with plant maintenance (PM). They are a typical operational tool, and as such used on the enterprise layer and on the project layer of enterprise project management. SAP does not allow "real" scheduling on the WBS level as usually understood. Relationships between WBS elements are of a hierarchical nature only, also considering thee order inside the same level and relationship of the hierarchy. Finish-Finish, Finish-Start, Start-Start or Start-Finish relationships cannot be set up on the WBS level. This means that scheduling on the WBS level requires the use or subordinate and linked network activities in SAP. The SAP concept for WBS elements is slightly different than the one described in the Project Management Book of Knowledge (PMBOK) of the world's biggest project management organization Project Management Institute (PMI). The PMBOK describes one single type of object to be used for hierarchical and same-level relationships, while SAP uses the WBS for the hierarchy and network activities (or maintenance order operations) for same level. This does not limit SAP's functionality and ability to reflect PMBOK definitions, though. MS Project is more in line with the PMBOK in this respect, although not in terminology (it uses the term "task" for these objects).
Copyright © 2007 Competitive Edge International, Inc. |
This Category is currently empty
|
|
|
