Using Change Management in Primavera Contract Management

FYI:
New Portal with same DocID
Archive
740964.1
Schedule
740966.1
Generic Advisor
Webcast Note
740966.1
before
now

Using Change Management in Primavera Contract
Management
Teleconference Access:
US & Canada: 888-259-4812
Toll Number: 706-679-4880
Password: AdvisorPG
Current Advisor Webcast
Schedule and Archived Download
– DOC#740966.1
Upcoming live webcasts and recent recordings:
April 25, 2013: PeopleSoft Payroll for North America and Benefits Release
9.2 – Empowering Employees with Employee Self Service
April 25, 2013: PeopleSoft: Your Upgrade: Preparing for Platform Changes
April 25, 2013: JDE E1: Change Assistant: Overview and Benefits
April 25, 2013: Database: Automation of patch conflict resolution and
deployment through EM 12c
April 25, 2013: EBS – MFG: ASCP-Rapid Planning Integration
April 30, 2013: FM: Diagnostics Enhancements in SOA Suite 11g PS6
(11.1.1.7)
April 30, 2013: Mutexes in Oracle Database
April 30, 2013: Demonstration of the benefits of PeopleSoft ePerformance
9.2
April 30, 2013: Primavera: Data Integrity When Performing Imports
May 1, 2013: What’s New in PeopleSoft Recruiting Solutions 9.2
May 2, 2013: Campus Solutions: Financial Aid Regulagtory 2013-2014
Release 3 (9.0 Bundle #29)
May 2, 2013: PeopleTools: Search Framework Introduction and Setup
May 7, 2013: Upgrading to PeopleTools 8.53
May 7, 2013: Oracle Systems: Best Practices for Migrating to Oracle
Solaris 11
May 7, 2013: Proactive Capabilities in MOS for JD Edwards EnterpriseOne

The following is intended to outline our general
product direction. It is intended for information
purposes only, and may not be incorporated into
any contract. It is not a commitment to deliver any
material, code, or functionality, and should not be
relied upon in making purchasing decision. The
development, release, and timing of any features
or functionality described for Oracle’s products
remains at the sole discretion of Oracle.
Safe Harbor Statement

<Insert Picture Here>
Using Change Management in Primavera Contract
Management
Sunny Bains
Janette Caceres
Senior Technical Support Engineers

AGENDA
 Change Management Process
 Defining Reason Codes
 Initiating Change Management from other Documents
 Adding Change Documents / Proposals / Change Orders
 Generating Change Documents from Change Management
 Applying Markup
 Collecting into Change Orders
 Approving Change Orders
 Costing
 Entering Change Orders / Proposals without Using Change
Management

 Contracts and Purchase Orders often change
 Change Management automates the Change Process
 Change Management is a workflow process
Change Management

Change Management is a Workflow Process

 Create customized workflow with Change Management
 Helps simplify the Change process
 One location to enter all necessary information
Change Management

Change Management Document

Project Settings

Document Setup

Adding a Custom Document Type

New Custom Document Type Added

Clearing Phases of Change Management

Calculating Net Amount of Previous Change

Calculating Net Amount of Previous Change
If calculating based on Change date:
 Date is the primary sort with the change number as a secondary sort
for changes created on the same day.
 Changes must be approved in sequence by date for the Net Amount of
Previous Change to be calculated accurately.
If calculating based on Change number:
 The date of the Change documents will be ignored.
 Changes must be approved in sequence by number for the Net
Amount of Change to be calculated accurately.
Note: Pending changes included in the calculation follow the same
rules

Contract Management User Levels
 Contract Management Administrator
- Full Access Rights to all projects
 Project Administrator
- Full Access Rights to currently assigned projects
 Regular User
- Administrator defined Access Rights

Restricting Access to Change Management

Project Access Dialog Box

Defining Reason Codes
 Add change reasons for Change Management
 Use the reasons for filtering grouping and sorting

Reason Codes

Adding and Deleting Reason Codes

Change Management Log Window

Change Management Document

Adding a Change Management Document
 From Change Management module
 From other document types:
- Daily reports
- Meeting minutes
- Notepads
- Noncompliance notices
- Notices
- Punch lists
- Request for information RFI
- Trends
- Contracts

Initiating Change Management (CM)

General Tab

Status Tab

Details Tab

Remarks Tab

Budgeted Tab

Commitments Tab

Documents by Phase

Adding Commitments

Add Multiple Estimates

Add Multiple Estimates Window

Multiple Estimates Added

Copy Commitments to Budgeted

Copy Commitments to Budgeted Window

Deleting Generated Proposal/Change
Documents
 Documents created via Change Management can not be deleted
outside of Change Management
 Document can not be deleted if later phases have been generated
from it.

Deleting Change Management Document

 Costing information assigned to generated documents
 Post to any portion of the Cost Worksheet
Costing Generated Documents

Including Changes on the Cost Worksheet

 Proposed change orders (PCO)
 Change order requests (COR)
 Estimates (EST)
 Request for proposal (RFP)
Proposals: Seek for a bid to perform a specific activity/change
Change Orders: Specify a redirection of plans or introduce new items to
show approved increases/decreases
Proposals & Change Orders

What can we do with Markup?
 Have different Markup values based on total labor, material, and
equipment costs
 Set default values for overhead and profit, but you can also add
additional Markup values for each document
 Assign Markup categories using a percentage rate or a flat amount
with both types
 Set Markup values at the contract or purchase order level, similar to
requisitions
 Specify the target cost code to which you want to apply the Markup
amount

Markup from Collected Documents

Cost Worksheet

Markup for Changes

Adding a Change Order Outside of Change
Management
 Enable setting in Project Settings dialog box
 Need to have collected at least one Change Order document

Document Creation Outside of CM

Change Order Document

Change Order Summary Tab

Markup for Changes

Collected Changes

Line Items Tab

Details Tab

Approval Process

Multiple Reviewer Process

Approving Change Orders

Getting Approved Change Order in to
Requisition

Collecting into Change Orders
 Collect costs from pending Change Orders
 Multiple Changes from one Contract into one Change Order

Line Items Tab

Collecting Change Orders

 Collect from Changes option only available if created
outside of Change Management
 Change Order must not have been collected before
 Change Order should not have status of Approved,
Closed or Rejected
 Status of Change Order collected in to another Change
Order gets set to Closed
Collecting into Change Orders

Are You Ready
To Get
Proactive?
Avoid the unexpected
Don’t leave value on the table
Lower overall organizational costs through preventative
maintenance
Reduce risks and maximize uptime
Achieve resolution faster
Streamline and simplify your daily operations
Get even more through connection
Discover more about Get Proactive
https://support.oracle.com/CSP/main/article?cmd=show
&type=ATT&id=1385165.1:DISCOVER
ACT Get Proactive
Access proactive capabilities available for your products
by visiting the product pages at My Oracle Support;
Article ID 432.1
Contact the Get Proactive team
today for help getting started
get-proactive_ww@oracle.com

THANK YOU

Using Change Management in Primavera Contract Management

More Related Content

What's hot (20)

Viewers also liked (16)

Similar to Using Change Management in Primavera Contract Management (20)

More from p6academy (19)

Recently uploaded (20)

Using Change Management in Primavera Contract Management