0% found this document useful (0 votes)
19 views32 pages

Oracle Primavera P6 R17.x Post-Install Functionality Test Spec

Project Management
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
19 views32 pages

Oracle Primavera P6 R17.x Post-Install Functionality Test Spec

Project Management
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 32

Oracle P6 PPM R 17.

x
Post-Install Functionality Test

Monday, 9 December 2024

LogiKal Projects | Commercial in confidence


Table of Contents

TABLE OF CONTENTS I

DETAILS III

1 PURPOSE 4

2 CONSIDERATIONS 4

3 PREREQUISITES 4

3.1 Software Installed 4

3.2 Obtain Client requirements 4

3.3 Permissions during testing 4

4 STEP BY STEP CHECKLIST 5

4.1 Open PPM and restore sample project 5

4.2 Create new project 5

4.3 Define a new project calendar 6

4.4 Create a WBS 9

4.5 Create activities and assign relationships and constraints 10

4.6 Generate Activity Network 14

4.7 Create and apply a baseline 14

4.8 Create new resources and assign them to tasks 17

4.9 Level resources 18

4.10 Update schedule 19

4.11 Create activity code 20

4.12 Create User Defined Field 21

4.13 EPPM - Create a new user and apply security policy 21

4.14 Apply Global Change 22

4.15 Check in/out project 23

4.16 Export Project Data 24

4.17 Delete project and test information 24

ACCEPTANCE 26

LogiKal Projects Approval and Acceptance 26

Client Approval and Acceptance 26

i
Post-Install Functionality Test | Table of contents LogiKal Projects | Commercial in confidence
ii
Post-Install Functionality Test | Table of contents LogiKal Projects | Commercial in confidence
Details

Submitted to:

Name
Title
Telephone
Email
Company
Address

Prepared by:

Name: Paul de Cort


Title: Senior Consultant
Telephone:
Email: [email protected]
Company: LogiKal Projects

Document History

Version Author Description Date

1.0 Andrew Byrnes First draft of checklist (v7.0) 4 July 2014

2.0 Paul de Cort Up-rev’d for Version 8.x 1 April 2015

3.0 Paul de Cort Up-rev’d for Version 17.x 26 November 2017

iii
Post-Install Functionality Test | Table of contents LogiKal Projects | Commercial in confidence
1 Purpose

This document is to be used by LogiKal consultants and Client Staff to validate the functionality of the installation of Primavera
Project Management in a Client’s working environment.

2 Considerations

This version of P6 will be used by the client in the client’s workplace environment. Ensure that during the testing process, no Global
values are changed, only change setting for the test project being set up. Ensure the test project is deleted at the end of the test
and no remnants of the test exist once complete, Such as Global User Defines Fields, Global Activity codes etc.

3 Prerequisites

3.1 Software Installed


This test shall be performed after:

 A necessary database has been established for P6 use (Oracle, SQL)


 P6 has been installed on clients system and linked to database in use

3.2 Obtain Client requirements


Section 4.5 sets the ‘start day of the week’

Check with the client which day of the week is required to be the first day. E.g. Western companies usually have ‘Monday’. Others
may have ‘Sunday’ or even ‘Saturday’

3.3 Permissions during testing


Certain aspects of the test script require elevated permissions.
For example, in most environments, only specific users can ‘create new users’.

Therefore, ensure that the users performing the test script have sufficient privileges to complete the steps.

4
Post-Install Functionality Test | Pre-amble

LogiKal Projects | Commercial in confidence


4 Step by Step Checklist

4.1 Open PPM and restore sample project

Tick when
Task No Instructions
complete

1.1 Open P6 Professional from the start menu

Select Database that was established in the installation process


1.2
Login to P6 using the administrator login and password

Open the Projects Window: Enterprise>Projects


1.3
and verify the sample/client projects are visible

1.4 Open the first Sample Project and confirm you can view the nodes and activities listed (layout is not
important)

1.5 Return to the Projects screen

1.6 Import the LogiKal sample Layout.

5
Post-Install Functionality Test | Pre-amble LogiKal Projects | Commercial in confidence
4.2 Create new project

Tick when
Task No Instructions
complete

From the projects screen, create a new project by selecting File>New and follow the wizard:

Create a new project under “All Initiatives” EPS

Give it a Project ID “Test1”

Name it “Test Project”

Set the Project Planned start to be 8 June 2018

Leave ‘Must Finish By’ blank

Select Finish

2.1

2.2 Once setup is complete, ensure the project can be viewed in the “Projects” Window

2.3 Right click on TestProject and select “Open Project”

4.3 Define a new project calendar

Task No Instructions Tick when


complete

3.1 Open the Calendars menu by Enterprise>Calendars

6
Post-Install Functionality Test | Pre-amble LogiKal Projects | Commercial in confidence
Task No Instructions Tick when
complete

Select the Projects radio button to display project specific Calendars and click on Add:

7
Post-Install Functionality Test | Pre-amble LogiKal Projects | Commercial in confidence
Task No Instructions Tick when
complete

3.2 Highlight “Standard 5 Day Workweek” and click select, to use this calendar as a basis.

3.3 Rename the new Calendar - call it Test Calendar

8
Post-Install Functionality Test | Pre-amble LogiKal Projects | Commercial in confidence
Task No Instructions Tick when
complete

3.4 Highlight “Test Calendar” and click Modify…

9
Post-Install Functionality Test | Pre-amble LogiKal Projects | Commercial in confidence
Task No Instructions Tick when
complete

3.5

Make Fridays a non-workday (For this month). Ensure all workdays have the same number of hours and
there are no exception days (Coloured white)

3.6 Open Time Periods…

Ensure
the
time

p
eriods match the work day and work week hours for a 4 day week.

3.7 Close the Calendar windows and return to the Activities screen

1
Post-Install Functionality Test | Pre-amble LogiKal Projects | Commercial in confidence
4.4 Create a WBS

Tick when
Task No Instructions
complete

4.1 Open WBS window Project>WBS

Right Click on the Project ID “Test1” under WBS code, and select Add

Add two WBS Nodes, Name them Node1, Node2

Do not change the WBS code ID, ensure the code automatically formats as shown below.

Sort by WBS Code

4.2

Apply different WBS view Layouts through View>Layout>Open Layout and Apply the various layouts
4.3
defined. Check to ensure the layout changes with different selections

4.4 Re-apply the WBS Standard View Layout

4.5 Create activities and assign relationships and constraints

Tick when
Task No Instructions
complete

NOTE: Refer to Section 3.2 before completing this item.

5.1

Check the default First Day of week and activity duration

1
Post-Install Functionality Test | Pre-amble LogiKal Projects | Commercial in confidence
Tick when
Task No Instructions
complete

Admin>Admin Preferences>General Tab

First day of week could be Monday

Activity Default Duration could be 5

Close the Preferences Window

1
Post-Install Functionality Test | Pre-amble LogiKal Projects | Commercial in confidence
Tick when
Task No Instructions
complete

Return to the Activities Window

Create 3 Activities under each WBS node. Name them New Activity 1, to New Activity 6
5.2
In the General tab, make Activity Type “Task Dependent” and % Complete as “Physical”

Do not assign any resources or relationships

5.3
Create a Finish Milestone under each WBS node

Name them Milestone1 and Milestone2

Ensure to change the Activity Type to “Finish Milestone” in the General tab

5.4 Check the Activity ID number to ensure all activity IDs have automatically increment sequentially

Check the activity Duration in the Status tab to ensure the duration matches the default duration of 5
days.

5.5 Assign TestCalendar, which was created earlier. to the three activities in Node1

Do this by selecting the relevant activity and change the calendar in the General Tab in the bottom
layout. Ensure you select “TestCalendar” from the list of Project Calendars rather than the Global
Calendars.

1
Post-Install Functionality Test | Pre-amble LogiKal Projects | Commercial in confidence
Tick when
Task No Instructions
complete

5.6

Assign FS relationships between activities as shown

5.7 Apply the following Primary Constraint in the General tab:

New Activity2 to Start on or After 26 June 2018

5.8 Return to the Activities window

Schedule the Project using F9 or the schedule button. Set Current Data Date to 08 June 2018

5.9 Using the View>Bars window, display the “Float Bar”

5.10 Click the following toolbar icon: to display the relationships

1
Post-Install Functionality Test | Pre-amble LogiKal Projects | Commercial in confidence
Tick when
Task No Instructions
complete

Alternatively, turn the relationships on through the Layout Menu>Bar Chart Options…

5.11 Check that the Gantt chart appears like this:

Note that the first three 5-day tasks continue into subsequent weeks due to the ‘test Calendar’ making
Fridays non-work time; and Task2 has a constraint.

1
Post-Install Functionality Test | Pre-amble LogiKal Projects | Commercial in confidence
4.6 Generate Activity Network

Tick when
Task No Instructions
complete

6.1 View the Activity Network by selecting View>Show on Top>Activity Network

Be sure to undo any changes, but check that the relationships between activities and the details can be
6.2
changed through the Activity Network View.

The Activity Network View should appear like this:

6.3

6.4 Return to the Gantt Chart view

4.7 Create and apply a baseline

Tick when
Task No Instructions
complete

Create a new baseline through <Project, Maintain Baselines>

Click Add

Select the “Save a copy of the current project as a new baseline” radio button:

1
Post-Install Functionality Test | Pre-amble LogiKal Projects | Commercial in confidence
Tick when
Task No Instructions
complete

A dialog will show stating the Job has been scheduled. Click “OK” on the message.

7.1

Close the ‘Maintain Baselines’ dialog box

Check the status of the scheduled job – i.e. the creation of the baseline.

Select <Tools, Job Status>

If the job is shown as ‘pending’ or ‘running’ wait a moment and then ‘refresh’ the screen.

Once the job has completed it should show as such in the list:

Verify the baseline was created by re-opening the ‘Maintain Baselines’:

1
Post-Install Functionality Test | Pre-amble LogiKal Projects | Commercial in confidence
Tick when
Task No Instructions
complete

Select Project>Assign Baseline and make “Test Project B1” the primary and project baseline:

7.3

1
Post-Install Functionality Test | Pre-amble LogiKal Projects | Commercial in confidence
Tick when
Task No Instructions
complete

7.4 Verify that the Baseline is displayed in the Gantt Chart as shown

You may need to reschedule and edit the Bars window to ensure baseline bars are visible.

4.8 Create new resources and assign them to tasks

Tick when
Task No Instructions
complete

8.1 Open the resources Window by selecting <Enterprise, Resources>

Right click and select Add to add 3 resources under ‘Import-Root’

8.2

Name them Resource 1, Resource 2, Resource 3

Set all resources to type Labor with Prices of $100/h $80/h $60/hr respectively.

1
Post-Install Functionality Test | Pre-amble LogiKal Projects | Commercial in confidence
Tick when
Task No Instructions
complete

Assign resources to activities as below.

8.3

8.4 Assign a $2000 expense to Activity3


You may need to make the Expenses tab visible in the bottom layout,

Click Add and make a new expense named “Test Expense” with budget cost of $2000. Leave the rest as
default.

8.5 View the following columns in the Activity window:

 At Completion Labor Cost


 At Completion Non-Labor Costs
 At Completion Material Cost
 At Completion Expense Cost &
 At Completion Total Cost.

Ensure cost and expense data is shown.

8.6 Return to the project screen

2
Post-Install Functionality Test | Pre-amble LogiKal Projects | Commercial in confidence
4.9 Level resources

Tick when
Task No Instructions
complete

9.1 Display the Activity Usage Spreadsheet View>Show on Bottom>Activity Usage Spreadsheet

Display the resource usage sheet. View>Show on Bottom>Resource Usage Spreadsheet

Select Resource1 and note that it is overloaded (16hr days)

While still selecting Resource1, Display the Resource Usage Profile noting the red bars:

9.2

Select Tools>Level Resources

9.3 Select resources to ensure all resources are checked

9.4 Click Level to level the schedule

The Gantt Chart should now look like this.

Re- schedule (to remove the levelling function)

2
Post-Install Functionality Test | Pre-amble LogiKal Projects | Commercial in confidence
Tick when
Task No Instructions
complete

4.10 Update schedule

Tick when
Task No Instructions
complete

10.1 In the Activity window, ensure the physical complete column is viewable

In the status tab mark the following activities as ‘started’ and update the Physical % Complete values:

Activity1: 100% and mark as ‘finished’

Activity2: 20%
10.2
Activity5: 80%

Note that the ‘Remaining Duration’ will not change if the tasks are set as ‘Physical’ Percent complete
type.

10.3 Schedule and move the data date to 29 June 2018

10.4

2
Post-Install Functionality Test | Pre-amble LogiKal Projects | Commercial in confidence
Tick when
Task No Instructions
complete

The Gantt chart should look like this.

4.11 Create activity code

Tick when
Task No Instructions
complete

Add an Activity Code for the project <Enterprise, Activity Codes…>

11.1 Select the Project radio button and click Modify (Ensure it is only created under the current project)

Click Add

11.2 Name it “TestActivityCode” with Max Length of 5, and close

In the Activity Code View, assign “TestActivityCode”


11.3

11.4 Open the Add Code Value form and Add three values

 Dig
 Build
 Paint

2
Post-Install Functionality Test | Pre-amble LogiKal Projects | Commercial in confidence
Tick when
Task No Instructions
complete

11.5 Assign the Activity Codes to the Activities as shown below.

2
Post-Install Functionality Test | Pre-amble LogiKal Projects | Commercial in confidence
Tick when
Task No Instructions
complete

11.6

4.12 Create User Defined Field

Tick when
Task No Instructions
complete

12.1 Create a UDF through <Enterprise, User Defined Fields…>

12.2 Select Activities And add a new UDF titled ‘Last Period Start’ of type ‘Start Date’

12.3 Show the Last Period Start column in the Activities window

4.13 EPPM - Create a new user and apply security policy

Tick when
Task No Instructions
complete

13.1 Log into EPPM with appropriate access rights to administer users

13.2 To Create a new User:

2
Post-Install Functionality Test | Pre-amble LogiKal Projects | Commercial in confidence
Tick when
Task No Instructions
complete

Click the Administration tab; then select User Administration

select Add to create a new user

Enter the required details:

once completed the form – hit ‘Add’

13.3 Assign the new user a global profile from the ‘Global Security Profile’ drop-down in the column.

13.4 Select the ‘Project Access’ tab

Click the ‘Assign OBS’ button

Select an ‘Responsible Manager’ node and assign a Project Security Profile

Note: it is possible to ‘highlight and cell and ‘drag’ it’s value down to other rows (like a spreadsheet).

13.5 Log out of P6. Login again as the user you just created

13.6 Verify that the new user has access and relevant rights

2
Post-Install Functionality Test | Pre-amble LogiKal Projects | Commercial in confidence
Tick when
Task No Instructions
complete

13.7 Log out and login again as admin. Delete the new user.

13.8 Return to the project screen

4.14 Apply Global Change

Tick when
Task No Instructions
complete

Open the Global Change form


14.1
Tools>Global Change…

Select New and Name it TestGlobalChange


14.2
Highlight the new change and Select Modify to open the modify form

Create a change that will double the duration of each activity.

In the Modify window, build a change as shown below.

14.3

14.4 Click OK to save the Change and close the Modify window

14.5 In the Global Change window, highlight TestGlobalChange and click “Apply Change”

2
Post-Install Functionality Test | Pre-amble LogiKal Projects | Commercial in confidence
Tick when
Task No Instructions
complete

14.6 Open the Activities window

Check that the activity durations have changed.

4.15 Check in/out project

Tick when
Task No Instructions
complete

15.1 In the project window, select “TestProject” and go to File>Check out

15.2 Follow the prompts to check out the project to the desktop location

15.3 Ensure the .XER file is created on the desktop

15.4 Return to the P6 Projects screen and ensure the project icon has a small tick on it. This indicated the
project is currently checked out.

15.5 Select “TestProject” and go to File>Check In


Follow the prompts to check-in the .XER file from the desktop.

4.16 Export Project Data

Tick when
Task No Instructions
complete

Export Activity Data by selecting File>Export


16.1
Follow the export wizard to export a mix of data to an excel spreadsheet

16.2 Save to the desktop

Open the exported data in Excel to ensure the data you have selected to be exported appears as
16.3
expected

16.4 If the data appears as it should, delete the XLS file

16.5 Return to the project screen

2
Post-Install Functionality Test | Pre-amble LogiKal Projects | Commercial in confidence
4.17 Delete project and test information

Tick when
Task No Instructions
complete

17.1 In P6, return to the project window

17.2 Right click on the test project and delete it

Open the global changes window, in the projects area

17.3 Ensure TestGlobalChange does not appear

Delete it, if it does

17.4 In Enterprise Calendars, in the project area

Ensure “TestCalendar” does not appear

Delete it, if it does

17.5 In the Enterprise>Resources area

Delete test resources, Resource1, Resource2, Resource3

17.6 In the <Enterprise, User Defined Fields…> area – delete the ‘Last Period Start’ UDF

17.7 Delete the exported test project data from the desktop if not done already (XER, XML))

 :

2
Post-Install Functionality Test | Pre-amble LogiKal Projects | Commercial in confidence
3
Post-Install Functionality Test | Pre-amble LogiKal Projects | Commercial in confidence
Acceptance

LogiKal Projects Approval and Acceptance


This document has been reviewed and accepted by:

Name:

Position:

Signature: Date:

Client Approval and Acceptance


This document has been reviewed and is accepted by:

Name:

Position:
Signature: Date:

3
Post-Install Functionality Test | Pre-amble LogiKal Projects | Commercial in confidence

You might also like