Concepts

Tasks

Settings

Setting up APM for Projects

Before you start creating capital, operational, or reliability projects, you must set up APM with the following objects:

Project Types

Project types are used to classify your projects into logical groups and to control the types of information that appear on project records.

See Setting up Project Types.

Project Classifications

Project classifications are used to further define your projects in conjunction with project types. This definition is similar to work types and work classifications. When you set up project types, you identify the project classification that is valid for each project type.

See Setting up Project Classifications.

Project Statuses

A project status is a set of user-defined values that is used to track the progress of your projects in APM. Project statuses are used in pick lists when working with projects and displayed in project banners and in tables. Each status is tied to a set of project controls that determine what actions you can take with a project having this status.

See Setting up Project Statuses.

Assignment Types

In addition to the team manager or facilitator, you can identify up to three roles in the project or analysis team and assign members to those roles.

See Setting up Assignment Types.

Project Settings

A project settings profile defines the fields that appear on project tasks, where users can record data. You can set up the fields and their labels to meet your organization’s requirements.

See Setting up Project Settings Profiles.

Project Task Types and Statuses

Setting up project tasks involves defining task types and statuses. Project task types describe the work to be done. Use task statuses to identify the stage of completion of a task and whether its properties can be updated, the task is completed, or canceled.

See Setting up Project Tasks and Task Statuses.

Project Events

You can set up workflow controls that automatically change the project status when a system activity occurs. For example, when the project is created, the status could be set to “New project” automatically.

See Setting up Events: Rules for Assigning Project Statuses.

Work Breakdown Structure (WBS) Codes

The work breakdown structure (WBS) is used to build the hierarchy location code of the work order tasks within your projects.

See Setting up Work Breakdown Structures.

For Capital and Operational Projects

For projects that record costs, you will need to refer to one or more GL accounts and cost types.

See Site Accounting.

For Approvals

Set up one or more approval routes and approvers to support the project approval process.

See Document Approvals.

Calculating Project Costs

There are two approaches to calculating project costs:

•	Update project costs in real time. For example, as work orders are added to a project and its descendant projects, the costs associated with work order tasks and transactions are added to the total project costs

This functionality is controlled by an option in project settings, which is enabled by default. You can clear the option if you wish to defer cost calculation.

•	Update projects manually. In the Project window, click the Tools menu and Recalculate Costs. The cost summaries for the current project and its descendant projects are recalculated

See Setting up Project Cost Calculation.