Working with the EPSYour database of projects is arranged in a hierarchy called the enterprise project structure (EPS). The EPS can be subdivided into as many levels or nodes as needed to parallel work at your organization. Nodes at the highest, or root, level might represent divisions within your company, project phases, site locations, or other major groupings that meet the needs of your organization. Projects always represent the lowest level of the hierarchy. Every project must be included in an EPS node. Ideally, one person or group controls the EPS across the organization. The project control coordinator creates the hierarchical structure that identifies the company-wide projects. The coordinator works with the project manager in each area of the organization to define basic project information for each group and to develop standards before any projects are added. After you set up an EPS, you can define additional data about each EPS node, such as anticipated dates, budgets, and spending plans. Use the detail windows on the EPS page to specify this information. Or, you can begin adding projects under the applicable nodes in the structure if you have access rights to these functions. Access rights are set by your application administrator. Throughout the application, when selecting projects to work with, you can open all projects that belong to an EPS node or sort them by EPS. When you create a project, you must specify a single parent EPS node. User access and privileges to nodes within the EPS hierarchy are implemented through a global OBS that represents the management responsible for each project. Each manager in the OBS is associated with an area of the EPS, either by node or by project, and the WBS of the particular level of the hierarchy. The EPS Page
|
||||||||||||||||
|