application administration guide - oracle · application administration guide 8 cbs overview........

Oracle Primavera Cloud Application Administration Guide

Version 20 May 2020

3

Contents

About This Guide ............................................................................................................................. 13

Configuration Process in Oracle Primavera Cloud .......................................................................... 13

Application Administrators Overview .............................................................................................. 14

Add an Application Administrator ........................................................................................................ 15

Managing Personal Information in Primavera Cloud ...................................................................... 16

About Consent Notices ......................................................................................................................... 16

About Personal Information ....................................................................................................... 16

Cookies Policy ............................................................................................................................. 16

Your Responsibilities ............................................................................................................................ 17

PI Data in Primavera Cloud ........................................................................................................ 17

Configure Consent Notices for Oracle Primavera Cloud .......................................................... 17

Audit Consent Notices for Oracle Primavera Cloud .................................................................. 17

License Usage Overview ................................................................................................................. 18

Types of Licenses ................................................................................................................................. 18

Assign a License to a User ................................................................................................................... 20

View License Usage .............................................................................................................................. 20

View User Usage ................................................................................................................................... 21

Application Settings Overview......................................................................................................... 21

Configure a Company Logo for a Report ............................................................................................. 21

Configure the Workspace Label .......................................................................................................... 22

Configure the Fiscal Year Setup Settings............................................................................................ 22

Configure the Global Search Settings ................................................................................................. 23

Configure the Time Periods Settings ................................................................................................... 23

Configure Boundary Security Settings................................................................................................. 24

Configure Background Services Settings ............................................................................................ 24

Configure Authentication Settings ....................................................................................................... 24

Configure Authentication Timeout Settings ........................................................................................ 25

Workspaces Overview ..................................................................................................................... 25

Working with Workspace Hierarchies ................................................................................................. 26

Create a Workspace ............................................................................................................................. 28

Edit the Root Workspace ........................................................................................................... 28

Add a Workspace ....................................................................................................................... 29

Add an Image to a Workspace................................................................................................... 29

Best Practices for Initial Configuration of Workspace Security and User Groups ............................ 30

Access a Workspace ............................................................................................................................ 32

Shared Data Overview .......................................................................................................................... 32

Manage Shared Dictionaries ..................................................................................................... 33

Application Administration Guide

4

Edit the Dictionary Sharing Method .......................................................................................... 34

Update the Owning Workspace of Dictionary Items ................................................................. 35

Update the Owning Workspace of Permission Sets ................................................................. 36

Security ........................................................................................................................................... 37

Permission Sets Overview .................................................................................................................... 37

Create a Permission Set in Global Admin ................................................................................. 38

Create a Workspace Permission Set ......................................................................................... 39

Create a Project Permission Set ................................................................................................ 40

Create a Portfolio Permission Set ............................................................................................. 40

Create a Report Permission Set ................................................................................................ 41

Create a File Permission Set ..................................................................................................... 42

Create an Idea Permission Set .................................................................................................. 43

Create a Custom Log Permission Set ....................................................................................... 43

Create a Program Permission Set ............................................................................................. 44

Security Privileges Definitions ................................................................................................... 45

Global Security Privileges Definitions ................................................................................ 45

Workspace Security Privileges Definitions ........................................................................ 46

Project Security Privileges Definitions ............................................................................... 52

Portfolio Security Privileges Definitions ............................................................................ 66

Report Security Privileges Definitions ............................................................................... 68

File Security Privileges Definitions .................................................................................... 69

Ideas Security Privileges Definitions ................................................................................. 69

Custom Log Security Privileges Definitions ....................................................................... 70

Program Security Privileges Definitions ............................................................................ 70

User Groups Overview .......................................................................................................................... 72

Manage User Groups in Global Admin ...................................................................................... 73Add a User Group in Global Admin .................................................................................... 74

Assign a User to a User Group on the User Groups Page ................................................ 75

Assign User Group Access to a Workspace or Project...................................................... 75

Manage User Groups at the Workspace Level ......................................................................... 76Add a User Group at the Workspace Level ....................................................................... 76

Assign a Default Permission Set to a User Group at the Workspace Level .................... 77

Assign a Deleted System User Group in the Root Workspace ......................................... 77

Assign a User to a User Group at the Workspace Level ................................................... 78

View Inherited Users in a Workspace User Group ............................................................ 78

User Access Overview ........................................................................................................ 79

Assign a User or User Group Access to a Workspace ...................................................... 79

Assign User Roles to a Workspace .................................................................................... 80

Manage User Groups at the Project Level ................................................................................ 81Add a Project User Group ................................................................................................... 81


Enable a User Group at the Project Level ......................................................................... 82

Assign a User or User Group Access to a Project ............................................................. 82

Contents

5

Companies and Users ..................................................................................................................... 83

Companies Overview ............................................................................................................................ 83

Add an App Preset ...................................................................................................................... 84

Set Up a Company ...................................................................................................................... 84

Add a Company ................................................................................................................... 85

Download an Import Template for Importing Companies, Offices, and Users ................ 86

Import Companies, Offices, and Users from Microsoft Excel .......................................... 86

Edit Company Details ......................................................................................................... 87

Add an Office to a Company .............................................................................................. 87

Edit Office Details ............................................................................................................... 87

Users Overview ..................................................................................................................................... 88

Add a User .................................................................................................................................. 89

Download an Import Template for Importing Companies, Offices, and Users ....................... 91

Import Companies, Offices, and Users from Microsoft Excel .................................................. 92

Add an App Preset ...................................................................................................................... 92

Assign a User to a User Group on the Users Page ................................................................... 93

Edit User Details ......................................................................................................................... 94

Manage Access .......................................................................................................................... 94


Manage Access Panel Overview ........................................................................................ 94

Assign User Access ............................................................................................................. 95

Manage a User's Default Permission Sets ............................................................................... 96

Manage a User's Apps ............................................................................................................... 96

View User Summary ................................................................................................................... 97

Add and Associate a Resource with an Existing User .............................................................. 97

Associate a Resource with a User ............................................................................................. 98

Assign Inspection Managers and Reports ................................................................................ 98

Set Up a User to Receive Dispatch Reports by Email .............................................................. 99

Reset a User Password .............................................................................................................. 99

Set a User as Inactive .............................................................................................................. 100

User Profiles Overview ....................................................................................................................... 101

View a User Profile ................................................................................................................... 101

Assign a License to an Individual User through Profiles ........................................................ 102

Proxy Users Overview .................................................................................................................... 102

Add a Proxy User ................................................................................................................................. 102

View Your Proxy Users ........................................................................................................................ 103

Act as a Proxy User ............................................................................................................................. 103

Field App Configuration ................................................................................................................ 103

Field Project Details Overview ........................................................................................................... 104

Configure the Maximum File Size for a Field Mobile Upload ................................................. 104

Set the Project Dates for Field Reporting ............................................................................... 104

Add an Issue Custom Field ...................................................................................................... 105

Add an Area or Item Custom Field .......................................................................................... 105


6

Set Up a Work Order Cover ...................................................................................................... 106

Add a Commissioning Step ...................................................................................................... 107

Set Up Revisions Tracking ....................................................................................................... 108

Field Setup Overview .......................................................................................................................... 108

Configure the Field Setup Project Data .................................................................................. 108Define Non-Working Days and Holidays .......................................................................... 108

Inspection Templates Overview ....................................................................................... 109

Add an Inspection Template ............................................................................................ 109

Archive an Inspection Template ...................................................................................... 110

Import a Form for an Inspection Template ..................................................................... 110

Edit the Form Setup for an Inspection Template ............................................................ 111

Link an Inspection Template ........................................................................................... 112

Set Up an Issues Workflow for Inspection Templates .................................................... 112

Add a Dispatch Rule ......................................................................................................... 113

Set Up Field Setup Application Data ....................................................................................... 114

Add an Issue Category/Status ......................................................................................... 115

Monitor and Release a Tablet ......................................................................................... 116

View the Data Modification Audit .................................................................................... 116

Email Content Manager Overview ................................................................................... 116

Edit Email Content ............................................................................................................ 117

Configure the Email Queue .............................................................................................. 117

Monitor the Email Queue ................................................................................................. 118

Send Emails from the Email Queue ................................................................................ 118

Areas Overview ......................................................................................................................... 119

Add an Area ...................................................................................................................... 119

Download an Import Template for Importing Areas ....................................................... 119

Import Areas ..................................................................................................................... 120

Edit an Area ...................................................................................................................... 120

Add an Item to an Area .................................................................................................... 121

Delete an Area .................................................................................................................. 121

Item Masters Overview ............................................................................................................ 121Add an Item Master .......................................................................................................... 122

Download an Import Template for Importing Item Masters ........................................... 122

Import Item Masters ......................................................................................................... 122

Export an Existing Item Master ........................................................................................ 123

Add a File to an Item Master............................................................................................ 123

Define a Standard Issue for an Item Master .................................................................. 124

Delete an Item Master ..................................................................................................... 124

Items Overview ......................................................................................................................... 125

Add an Item....................................................................................................................... 125

Create an Upload Template for Uploading Items ........................................................... 125

Upload an Item ................................................................................................................. 126

Export Existing Items ........................................................................................................ 126

Add a File to an Item ........................................................................................................ 126

Delete an Item .................................................................................................................. 127

Contents

7

Dictionary Configuration ............................................................................................................... 127

Calendars Overview ............................................................................................................................ 127

Add a Holiday List ..................................................................................................................... 128

Add a Calendar ......................................................................................................................... 129

Set a Calendar Exception Time ............................................................................................... 130

Assign Calendar Availability ..................................................................................................... 131

Set Number of Work Hours Per Time Period .......................................................................... 131

Set the Default Calendar ......................................................................................................... 132

Update the Owning Workspace of a Calendar ........................................................................ 133

Codes Overview .................................................................................................................................. 133

Add a Code................................................................................................................................ 134

Add a Value to a Code .............................................................................................................. 135

Update the Owning Workspace of a Code .............................................................................. 136

Currencies Overview ........................................................................................................................... 137

Add a Currency ......................................................................................................................... 138

Add a Custom Currency ........................................................................................................... 138

Modify a Project Currency ........................................................................................................ 139

Add an Exchange Rate ............................................................................................................. 140

Update the Owning Workspace of a Currency ........................................................................ 141

Folder Templates Overview ................................................................................................................ 141

Add a Folder Template ............................................................................................................. 142

Edit a Folder Template ............................................................................................................. 142

Forms Overview .................................................................................................................................. 143

Locations Overview ............................................................................................................................ 143

Add a Location .......................................................................................................................... 144

Download an Import Template for Importing Locations ........................................................ 145

Import Locations ...................................................................................................................... 146

Update the Owning Workspace of a Location ........................................................................ 146

Workflow Designs and Workflow Configurations Overview .............................................................. 147

Portfolio Configuration Options ......................................................................................................... 148

Analysis Views Overview .......................................................................................................... 148

Create an Analysis View in a Workspace ........................................................................ 148

Add an Analysis View ........................................................................................................ 149

Configure a Chart or Grid ................................................................................................. 149

Publish an Analysis View to a Portfolio............................................................................ 150

Measures Overview .................................................................................................................. 150Create a Measure ............................................................................................................. 151

Add a Measure ................................................................................................................. 151

Set a Threshold for a Measure ........................................................................................ 153

Associate a Measure with a Portfolio .............................................................................. 154

Associate a Measure with a Strategy .............................................................................. 154

Working with Creating Measures ..................................................................................... 155

Project Configuration Options ............................................................................................................ 159


8

CBS Overview............................................................................................................................ 159

Create a Workspace CBS ................................................................................................. 159

Add a Workspace CBS ...................................................................................................... 160

Create a Workspace CBS by Import ................................................................................ 161

Download an Import Template for Importing CBS Codes .............................................. 161

Import a CBS ..................................................................................................................... 162

Copy a Sibling Workspace CBS ........................................................................................ 163

Copy a Parent Workspace CBS ........................................................................................ 163

Modify a Workspace Segment Definition ........................................................................ 164

Add a CBS Code ................................................................................................................ 165

Import Additional CBS Codes ........................................................................................... 165

Cost Categories Overview ........................................................................................................ 166

Add a Cost Category ......................................................................................................... 166

Update the Owning Workspace of a Cost Category ........................................................ 167

Curve Profiles Overview ........................................................................................................... 167

Define a Curve Profile ...................................................................................................... 168

Update the Owning Workspace for Curve Profiles .......................................................... 169

Evaluation Categories Overview .............................................................................................. 169

Add an Evaluation Matrix ................................................................................................. 170

Reporting Cycles Overview ....................................................................................................... 171Define a Reporting Cycle .................................................................................................. 171

Assign a Default Reporting Period ................................................................................... 172

Update the Owning Workspaces of a Reporting Cycle ................................................... 172

Risk Thresholds Overview ........................................................................................................ 173Add a Risk Threshold Template ....................................................................................... 173

Update the Owning Workspace of a Risk Threshold Template ...................................... 174

Risk Matrixes Overview ............................................................................................................ 175Add a Risk Matrix Template ............................................................................................. 175

Configure the Probability and Impact Diagram Settings ................................................ 176

Update the Owning Workspace of a Risk Matrix Template ............................................ 177

Rules of Credit Overview .......................................................................................................... 177Add a Rule of Credit ......................................................................................................... 178

Update the Owning Workspace of a Rule of Credit ........................................................ 178

Strategy Types Overview .......................................................................................................... 179Add a Strategy Type .......................................................................................................... 179

Update an Owning Workspace for a Strategy Type ........................................................ 180

Units of Measure Overview ...................................................................................................... 180Add a Unit of Measure...................................................................................................... 180

Update Owning Workspace of a Unit of Measure ........................................................... 181

Defaults & Options Configuration ................................................................................................. 181

Field Labels Overview ......................................................................................................................... 181

Access a Standard Field Description ...................................................................................... 182

Change a Standard Field Label ............................................................................................... 182

Configured Fields Overview ............................................................................................................... 183

Add an Activity Field ................................................................................................................. 184

Contents

9

Add a Budget Field ................................................................................................................... 185

Add a Budget Changes Field ................................................................................................... 186

Add a Budget Transfers Field .................................................................................................. 187

Add a Budget Details Field ...................................................................................................... 188

Add a Changes Field ................................................................................................................ 189

Add a Company Field ............................................................................................................... 189

Add a Change Order Field ........................................................................................................ 190

Add a Changes Estimates Field ............................................................................................... 191

Add a Commitment Field ......................................................................................................... 192

Add a Contract Field ................................................................................................................. 193

Add a File Field ......................................................................................................................... 194

Add a Fund Field ....................................................................................................................... 195

Add an Idea Field ...................................................................................................................... 195

Add a Payment Application Field ............................................................................................. 196

Add a Portfolio Field ................................................................................................................. 197

Add a Potential Change Order Field ........................................................................................ 198

Add a Project Field ................................................................................................................... 199

Add a Project Actuals Field ...................................................................................................... 200

Add a Project Cost Sheet Field ................................................................................................ 201

Add a Resource Assignment Field ........................................................................................... 202

Add an RFI Field ....................................................................................................................... 203

Add a Risk Field ........................................................................................................................ 205

Add a Scope Assignment Field ................................................................................................ 206

Add a Scope Item Field ............................................................................................................ 207

Add a Strategy Field ................................................................................................................. 208

Add a Submittal Field ............................................................................................................... 209

Add a Task Field ....................................................................................................................... 210

Add a WBS Field ....................................................................................................................... 211

Add a Work Package Field ....................................................................................................... 212

Add a Workspace Cost Sheet Field ......................................................................................... 213

Change a Configured Field Label ............................................................................................ 214

Add a Formula-Based Configured Field: Example .................................................................. 215

Update the Owning Workspace of a Configured Field ........................................................... 216

Defaults for Workspaces Overview.................................................................................................... 217

Set the Details Page for Projects ............................................................................................ 217

Configure Default Activity Settings for a Workspace.............................................................. 217

Configure Default Activity Calculation Settings for a Workspace .......................................... 219

Set the Default Calendar ......................................................................................................... 220

Set the Default Print Layout for a Workspace or Project ....................................................... 221

Set the Default My Activities Settings ..................................................................................... 222

Configure Auto Numbering Defaults for Budget Changes ..................................................... 223

Configure Auto Numbering Defaults for Budget Transfers .................................................... 224

Configure Auto Numbering Defaults for a Change Order ...................................................... 224


10

Configure Auto Numbering Defaults for a Change ................................................................. 225

Configure Auto Numbering Defaults for a Commitment ........................................................ 225

Configure Auto Numbering Defaults for a Contract ............................................................... 226

Configure Auto Numbering Defaults for Ideas ....................................................................... 226

Configure Auto Numbering Defaults for a Payment Application ........................................... 226

Adjust the Default Retainage Percentage for Payment Applications .................................... 227

Adjust the Default Period To Value for Payment Applications ............................................... 227

Configure Auto Numbering Defaults for a Project Actual ...................................................... 228

Configure Auto Numbering Defaults for a Risk ...................................................................... 228

Configure Auto Numbering Defaults for a Scope Change Request ...................................... 229

Configure Auto Numbering Defaults for a Scope Assignment ............................................... 229

Configure Auto Numbering Defaults for a Scope Item ........................................................... 230

Configure Auto Numbering Defaults for a Potential Change Order....................................... 230

Configure Auto Numbering Defaults for a Task ...................................................................... 231

Configure Auto Numbering Defaults for Work Packages ....................................................... 231

Assign a Custom Workflow at the Workspace Level .............................................................. 232

Integration Overview ..................................................................................................................... 233

Integrate P6 EPPM ............................................................................................................................. 234

Add a P6 EPPM Connection ..................................................................................................... 235

Modify P6 EPPM Integration Advanced Settings .................................................................... 235

Enable or Disable a P6 EPPM Business Flow ......................................................................... 236

Modify a P6 EPPM Business Flow ........................................................................................... 237

Delete Cross-references for a P6 EPPM Connection ............................................................. 238

Integrate Gateway .............................................................................................................................. 238

Add a Gateway Connection ...................................................................................................... 239

Add Gateway Synchronizations ............................................................................................... 239

Integrate Microsoft Project ................................................................................................................ 240

Add a Microsoft Project Connection ........................................................................................ 240

Modify a Microsoft Project Business Flow .............................................................................. 241

Run a Synchronization Job ................................................................................................................. 242

Schedule a Synchronization Job ........................................................................................................ 242

Monitor a Synchronization Job .......................................................................................................... 243

View Synchronization Job Details ...................................................................................................... 244

Default Business Flow Reference ..................................................................................................... 244

P6 EPPM Default Business Flow Reference ........................................................................... 244

Global ................................................................................................................................ 244

Send Resources to Primavera Cloud Field Mappings .................................................... 244

Send Roles to Primavera Cloud Field Mappings ............................................................ 245

Create EPS Code in Primavera Cloud Field Mappings ................................................... 246

Create Workspace Code in P6 Field Mappings .............................................................. 246

Send Resources and Roles to Primavera Cloud Field Mappings................................... 246

Project ............................................................................................................................... 248

Create Project Header - P6 to Primavera Cloud Field Mappings ................................... 248

Contents

11

Create Project Header - Primavera Cloud to P6 Field Mappings ................................... 248

Send P6 Project Data to Primavera Cloud for Risks Field Mappings ............................ 249

Send P6 Project Data to Primavera Cloud for Schedule Field Mappings ...................... 259

Send P6 Project Data to Primavera Cloud for Scope Field Mappings ........................... 264

Send Planned Budget & Plan Dates from P6 to Primavera Cloud Field Mappings ...... 270

Send Primavera Cloud Project Data to P6 Field Mappings ............................................ 270

Send Project Actual Cost & Progress from P6 to Primavera Cloud Field Mappings ..... 272

Send Proposed Budget & Plan Dates from Primavera Cloud to P6 Field Mappings .... 272

Send Approved Budget & Plan Dates from Primavera Cloud to P6 Field Mappings .... 273

Send P6 Project Data to Primavera Cloud Field Mappings ............................................ 273

Send Primavera Cloud Project Data to P6 for Lean Task Field Mappings .................... 285

Microsoft Project Default Business Flow Reference .............................................................. 287Import MSP Project Data to Primavera Cloud Field Mappings ...................................... 287

Export Primavera Cloud Project Data to MSP Field Mappings ...................................... 295

Import/Export Overview ................................................................................................................ 302

Import/Export Configuration Data Overview ..................................................................................... 302

Export All Configuration Data from Primavera Cloud ............................................................. 303

Import Configuration Data to Primavera Cloud ...................................................................... 304

Export Customized Configuration Data from Primavera Cloud ............................................. 304

View the Import/Export Configuration Data Log .................................................................... 304

Download the Import/Export Configuration Data Log............................................................ 305

P6 XML Import/Export Overview ....................................................................................................... 305

Import P6 XML Data into Oracle Primavera Cloud ................................................................. 309

Export Oracle Primavera Cloud Data to P6 XML .................................................................... 312

Create Projects by Excel Import ......................................................................................................... 312

Download an Import Template for Importing Projects ........................................................... 313

Import Projects from Microsoft Excel ...................................................................................... 313

Microsoft Project Import/Export Overview ........................................................................................ 314

Import Microsoft Project Data into Oracle Primavera Cloud ................................................. 315

Export Oracle Primavera Cloud Data to Microsoft Project XML ............................................. 316

Manage Services Overview ........................................................................................................... 317

Monitor Service Status ....................................................................................................................... 317

Configure Recurring Services ............................................................................................................ 318

Manage Services Filters ..................................................................................................................... 319

Test Network Speed ...................................................................................................................... 320

Set the Locale ............................................................................................................................... 320

Appendix of Referenced Navigation Steps ................................................................................... 323

Navigate to the WBS page ................................................................................................................. 323

Navigate to the Activities page .......................................................................................................... 323

Navigate to the project Activities page.............................................................................................. 323

Navigate to the project or project collections Activities page .......................................................... 323

Navigate to the Baselines page ......................................................................................................... 324


12

Navigate to the Schedule Comparison page .................................................................................... 324

Navigate to the workspace resource page ....................................................................................... 324

Navigate to the project resources page ............................................................................................ 324

Navigate to the workspace or project resources page .................................................................... 325

Navigate to the workspace roles page .............................................................................................. 325

Navigate to the project roles page .................................................................................................... 325

Navigate to the workspace or project roles page ............................................................................. 326

Navigate to the workspace resource assignments page ................................................................. 326

Navigate to the project, program, or project collection resource assignments page .................... 326

Navigate to the workspace resource analysis page ......................................................................... 326

Navigate to the project, program, or project collection resource analysis page ............................ 327

Navigate to the files page .................................................................................................................. 327

Navigate to the project files page ..................................................................................................... 327

Navigate to the project or portfolio files page .................................................................................. 327

Navigate to the project Details page ................................................................................................. 328

Navigate to the project codes page .................................................................................................. 328

Navigate to the project settings page ............................................................................................... 328

Navigate to the program settings page ............................................................................................. 329

Navigate to the program codes page ................................................................................................ 329

Navigate to a dictionary page ............................................................................................................ 329

Navigate to the Calendars dictionary page ....................................................................................... 329

Navigate to the Codes dictionary page ............................................................................................. 330

Navigate to the Curve Profiles dictionary page ................................................................................ 330

Navigate to the Units of Measure dictionary page ........................................................................... 330

Navigate to the Locations dictionary page ....................................................................................... 331

Navigate to the Currencies dictionaries page .................................................................................. 331

Navigate to an object configuration page ......................................................................................... 331

Navigate to the Activity configuration page ...................................................................................... 332

Navigate to the Project configuration page ...................................................................................... 332

Navigate to the Program configuration page .................................................................................... 332

Navigate to the Resource Assignment configuration page.............................................................. 332

Navigate to the Resource/Role configuration page ......................................................................... 333

Navigate to the WBS configuration page .......................................................................................... 333

Navigate to the Manage Services page ............................................................................................ 333

Navigate to the Preferences page ..................................................................................................... 334

Copyright ....................................................................................................................................... 335

13

About This Guide

This guide instructs you on how to begin using Oracle Primavera Cloud. You should complete most of the tasks in this guide before you let your users work with the application. These tasks include defining the following: application administrators, application settings, workspaces, permission sets, user groups, security settings and privileges, and configuration options. You can use the Global Admin settings and Summary & Settings panel to complete the tasks.

Configuration Process in Oracle Primavera Cloud

The following list provides guidelines and a general process for configuring your environment, including configuring application settings, setting up companies and workspaces, and administering user security. Because the structures are global across the organization, some processes might require information from many participants. You can vary the order in which you complete these processes depending on your organization's implementation plan.

Add application administrators.

Application administrators are afforded privileges to access all objects and carry out all functions in the application. See Add an Application Administrator (on page 15).

Configure general application settings.

Application settings define parameters that apply globally in the application. See Application Settings Overview (on page 21).

Set up the workspace hierarchy for your organization.

Identify your organization's project structure, which is global across the organization. See the Workspaces Overview (on page 25) for more information.

Create global, workspace, project, program, file, portfolio, idea, custom log, and report permission sets.

Define a standard set of permission sets that determine access rights to global and object-specific data. See Permission Sets Overview (on page 37) to determine what permission sets you need to create or customize.

Create user groups.

User groups are a collection of users with the same security privileges and access. Groups can be assigned directly to a workspace, project, portfolio, file, idea, custom log, program, or report. When you create user groups, you assign permission sets to them to define the level of access that users will gain. See User Groups Overview (on page 72) to learn more about adding user groups.

Add companies that partner with your organization.

See Set Up a Company (on page 84).

Add users to companies in the application.

When you add users, you can determine the user groups that they will belong to as well as assign them direct access to objects. See Users Overview (on page 88) for more information on types of users.


14

Assign user groups to objects.

Assigning a user group enables the users to receive the permissions assigned to the user group. User groups can be assigned to any object at the Global Admin leve (see "Assign User Group Access to a Workspace or Project" on page 75)l or from the Security tab for a workspace, project, portfolio, program, custom log, file, idea, or report.

Add projects to the workspace (if needed).

Project managers usually perform this step. Refer to the Oracle Primavera Cloud Help for more information.

Additional user groups may be created at the project level.

Configure shared data and objects at the workspace-level including Dictionary Configuration (on page 127) and Defaults & Options Configuration (on page 181).

Application Administrators Overview

An application administrator is a user with privileges to access all workspaces, ideas, projects, portfolios, programs, project collections, and global elements (such as workflows). Only users created in the owning company can be application administrators. Oracle recommends that you assign the application administrator privilege sparingly.

Application Administrator Security Privileges

Application administrators are automatically assigned the Application Administrator global permission set. This permission set is not visible on the Global Permission Sets page and cannot be modified or deleted. Application administrators can access all objects in the application and are afforded all of the privileges that are available for a global permission set (see Global Security Privileges Definitions (on page 45)). Along with these privileges, application administrators are the only users able to complete the following tasks:

Assign and unassign other application administrators.

Modify global permission sets and assign them to users.

Import/export configuration data.

View all jobs running as background services from the Manage Services page.

View all workflow instances from the Monitor Workflows page.

Access the User Profile, License Usage, and User Usage pages.

Configure integration settings.

Act as proxy users for other application administrators.

The Application Administrator permission is a separate concept from the Administrator permission sets that can be set at the object level. The Administrator permission sets that can be set at the object level grant administrator privileges to a user for that object only, while application administrators, with the Application Administrator permission set, have administrative rights to all objects across the application.

Application Administrators Overview

15

Add an Application Administrator

Add application administrators to your organization to add users, configure application settings, create workspaces, and set up dictionaries and defaults & options. Oracle recommends that you assign the application administrator privilege sparingly.

To assign a new user as an application administrator:

1) In the object selector, select Global Admin settings.

2) In the sidebar, select Companies.

3) Select a company, and in the Users section, select Add.

4) In the Add User dialog box, do the following:

a. On the General tab, complete the following fields:

1. First Name: Enter the first name of the user.

2. Last Name: Enter the last name of the user.

3. Email: Enter the email address for the user.

Note: The email address will be the username required for logging into the application.

4. Office: Select the office for the user.

5. In the Locale list, select the locale of the user.

6. (Optional) Complete additional fields.

b. Select the Permissions tab.

c. In the User Type section, select Application Administrator.

Note: This option is only available for users created in the owning company.

To assign an existing user as an application administrator:

1) On the Companies page, in the table, select the owning company.

2) In the Users section, in the table, select a user row, and then select Application Administrator.

3) Select Save.


16

Managing Personal Information in Primavera Cloud

About Consent Notices

Consent notices inform users how personal information (PI) is collected, processed, stored, and transmitted, along with details related to applicable regulations and policies. Consent notices also alert users that the action they are taking may risk exposing PI. Primavera Cloud helps you to ensure that you have requested the appropriate consent to collect, process, store, and transmit the PI your organization holds as part of Primavera Cloud data.

Consent notices should:

be written in clear language which is easy to understand.

provide the right level of detail.

identify the purpose and legal basis for your collection, processing, storage, and transmission of PI.

identify whether data will be transferred to named third parties.

identify PI categories and list the data which will be collected, processed, stored, and transmitted.

About Personal Information

Personal information (PI) is any piece of data which can be used on its own or with other information to identify, contact, or locate an individual or identify an individual in context. This information is not limited to a person's name, address, and contact details. For example, a person's IP address, phone IMEI number, gender, and location at a particular time could all be personal information. Depending on local data protection laws, organizations may be responsible for ensuring the privacy of PI wherever it is stored, including in backups, locally stored downloads, and data stored in development environments.

Caution: Personal information (PI) may be at risk of exposure. Depending on local data protection laws, organizations may be responsible for mitigating any risk of exposure.

Cookies Policy

Oracle might use cookies for authentication, session management, remembering application behavior preferences and performance characteristics, and to provide documentation support.

Also, Oracle might use cookies to remember your log-in details, collect statistics to optimize site functionality, and deliver marketing based on your interests.

Managing Personal Information in Primavera Cloud

17

Your Responsibilities

Information security and privacy laws can carry heavy penalties and fines for organizations which do not adequately protect PI they gather and store. If these laws apply to your organization, it is your responsibility to configure consent notices before they are required. You should work with your data security and legal teams to determine the wording of the consent notices you will configure in Oracle Primavera Cloud.

If a consent notice is declined, it is your responsibility to take any necessary action. For example, you may be required to ensure that the data is not stored or shared.

PI Data in Primavera Cloud

Personal information (PI) may be visible in multiple areas of Oracle Primavera Cloud, including but not limited to the following apps: Contracts, Cost and Funds, Dashboard, Documents, Field, Integration, Portfolio Analysis, Reports, Resources, Risk, Schedule, Scope, Strategic Alignment, Tasks, and Workflows and Forms. PI may also be visible in the following pages, including but not limited to: Global Admin settings, Profile, Preferences, Manage Proxy Users, Manage Services, and Monitor Workflows.

PI may be at risk of exposure in multiple areas of Primavera Cloud, including but not limited to downloaded tables, reports, documents, API, and mobile applications. Primavera Cloud allows for the creation of configured fields and codes that could be used to store PI. Consideration should be taken when creating these fields and codes to ensure PI policies for your organization are followed.

Configure Consent Notices for Oracle Primavera Cloud

To configure consent notices for Oracle Primavera Cloud:


2) In the sidebar, select Privacy.

3) On the Privacy page, select Accept PI Usage on Login.

4) In the Consent Notice Message details window, enter the consent notice.

5) Format the consent notice including headings, fonts, and links.

6) Select Save.

Audit Consent Notices for Oracle Primavera Cloud

You can see the status of consent acceptance for users. If the consent notice is changed, the consent acceptance for all users is reset.

To audit consent status for Oracle Primavera Cloud:



3) Select a company row.


18

4) In the Users table, select the Consent Status column to sort by Accepted, Declined, and No Response.

License Usage Overview

Licenses control project creation and user access in Oracle Primavera Cloud. Three license models are available to best fit the needs of your organization.

The three license models include:

Project: Access a limited number of projects created for your organization for an unlimited amount of users.

Note: Users cannot add projects or edit a project's name in this model. However, they can edit the project ID, if needed.

Named User: Create an unlimited amount of projects for a limited number of users. Additional user licenses can be purchased by contacting your Oracle sales representative.

Enterprise: Create an unlimited amount of projects for an unlimited amount of users.

The application enables you to view license usage and assign licenses to users and partner users. You should monitor the License Usage page to ensure your company is compliant with the number of licenses they have purchased. Organizations that purchase an Enterprise or Project license will not have access to a license usage page because they can create an unlimited number of users.

Types of Licenses

There are four types of licenses designed to meet the needs of your organization. Licenses determine what apps, pages, and mobile apps to which you have access.

If you have the Named Users license model, then you will assign available licenses to users. If you have the Project license model, then users will automatically receive the Schedule License and the Field License. If you have the Enterprise license model, the user will automatically receive all four licenses.

Schedule License: Prioritize, plan, manage, and evaluate projects across your organization.

Portfolio License: Propose, select, and manage portfolios across your organization.

Idea License: Add the Idea license to your Portfolio license to capture, evaluate, and process ideas for new initiatives and business endeavors.

Field License: Add the Field license to your Schedule license to increase construction productivity in the field.

Each license gives you different access to apps and mobile apps. The table below highlights which apps come with which licenses. The Idea and Portfolio licenses gives you access to the ideas context.

License Usage Overview

19

Licenses by App

App Schedule License Field

License

Portfolio License Idea License

Contracts & Commitments

X

Cost & Funds X X

Dashboards X X X

Field X

Files X X X X

Integration X X X

Lean X

Project Team X X X

Related Items X

Reports X X X

Resources X X

Risk X

Schedule X

Scope X

Strategic Alignment X

Submittals X

Workflows and Forms X X X

Primavera Field for iOS X

Primavera Projects for iOSPrimavera Projects for Android

X

Primavera Progress for iOSPrimavera Progress for Android

X X


20

Oracle Primavera Portfolios for iOS

X

Primavera Professional X

Assign a License to a User

Assign licenses to users so that they can work in the application.

To assign a license to a user:


2) In the sidebar, select License Usage.

3) On the License Usage page, select the licenses.

4) In the Users detail window, select Assign.

5) In the Assign Users dialog box:

a. Enter part or all of the user's username or personal name into the Search field.

b. Select a user, and then select Assign.

6) Select Save.

Tips

Remove a user from a license by selecting the Context menu and then selecting Remove.

You can also assign a license to an individual user on the User Profiles page or during user creation.

View License Usage

You can view how many licenses your organization purchased, how many are assigned, and how many are available. Only organizations that purchase a Named User license will have access to a license usage page.

To view the number of licenses available and in use:


2) In the sidebar, select License Usage.

3) Compare the Purchased and Assigned columns. If the number assigned is larger than the number purchased, reduce the number of users assigned to the license or obtain additional licenses.

4) In the Users detail window, view the users assigned to that license.

Tips

Use the Chart detail window for a visual representation of your organization's license usage over time.

Application Settings Overview

21

If your organization is in compliance with the amount of licenses they have purchased, you will see Licensing is in compliance for this product in the Available column. If your organization is using more licenses than they have purchased, you will see To be in compliance, you must reduce the number of users assigned to this product in the Available column.

View User Usage

View user usage to evaluate which individuals are consistently logging into the application. By identifying users who are not logging into the application, you can evaluate which user licenses can be released. You can also identify users who are not logging in and change their status to inactive so that they can no longer access your system.

To view user usage:


2) In the sidebar, select User Usage.

3) In the time frame list, select the period of time from which to view user log ins.

4) Select one of the following views:

Active Users: Users who have logged into the application in the specified time frame.

Dormant Users: Users who have not logged into the application in the specified time frame.


Application settings define parameters that apply globally in the application. Use these settings to customize the application to meet specific organization requirements and standards.

Configure a Company Logo for a Report

Upload your organization’s logo to the application to make it available to add to customized reports. You cannot upload an image with a CMYK color format. The recommended size for a company logo is 240 x 240 pixels.

To upload your company logo to the application:


2) In the sidebar, select Application Settings.

3) On the Application Settings page, in the Company Logo for Reports section, select Upload Logo.

4) In the Upload Logo dialog box, select Browse, select your company logo, and then select Upload.


22

Configure the Workspace Label

Your organization can customize the application to match the terminology of your industry. For example, you can update the label workspace to say something more applicable to your organization such as Enterprise Project Structure (EPS).

Note: If you choose to customize the workspace label, the field name will no longer match messages, training content, or documentation materials.

To edit the workspace label in the application:



3) On the Application Settings page, in the Workspace Label section:

a. In the Workspace Label (Singular) field, enter the singular form of the name to use in place of workspace.

b. In the Workspace Label (Plural) field, enter the plural form of the name to be in place of workspaces.

c. Select Configure More Languages, and do the following:

1. In the Workspace Label Language Configuration dialog box, select a language row.

2. In the Workspace Label (Singular) field, enter the singular form of the name to use in place of workspace in the selected language.

3. In the Workspace Label (Plural) field, enter the plural form of the name to be in place of workspaces in the selected language.

4. Select Save.

4) Select Save.

Configure the Fiscal Year Setup Settings

Define the start month and start date of the fiscal year. These settings will determine the timescale layout for budget planning and cash flow views.

To configure fiscal year settings:



3) On the Application Settings page, in the Fiscal Year Setup section:

a. In the Fiscal Start Month list, select a month.

This setting will drive the budget planning and cash flow timescales. For example, if the fiscal start month is April, Quarter 1 will show Apr, May and Jun as 1st Quarter months when the year bucket is expanded.

b. In the Fiscal Start Date list, select a date of the selected month.

This setting, along with the Fiscal Start Month, will drive the timescale layout for the budget planning and cash flow views.


23

c. Select Display dates in timescale to display the fiscal start and end date in the monthly buckets of the timescale.

For example, if the fiscal start date is the 20th, the monthly bucket would display Apr 20 - May 19.

4) Select Save.

Configure the Global Search Settings

Configure global searches to determine how users view results on the Advanced Search page. Configure caching specifications to show search results for multiple searches or only the latest search.

To configure global search settings:



3) On the Application Settings page, in the Global Search section, complete the following fields:

a. Recent Items Added Ranking: The number in this field represents the added ranking percentage to add to global search results that were recently accessed by the user. The highest ranking item is displayed first when the user searches.

b. Number of Days to Consider Items as Recent: The number in this field represents the number of days a search result will be considered as recent.

c. Maximum Number of Results in Search Results: The number in this field represents the maximum amount of search results per type returned on the global search page.

d. (Optional) User Multiple Search Caching: Select this option if you want to cache multiple searches per user instead of only the latest search.

4) Select Save.

Configure the Time Periods Settings

Configure time periods settings to specify time period abbreviations and the default number of hours in a work period. The Hours per Time Period setting is used as a conversion factor when users choose to display time units and durations in units other than hours, and no configured calendar overrides these defaults.

To configure time periods settings:



3) On the Application Settings page, in the Time Periods section, configure the Hours per Time Period and Time Period Abbreviations fields.

4) Select Save.


24

Configure Boundary Security Settings

Configure API and Gateway access and Data Service access to enable integration features across the application. If these settings are enabled, users can synchronize external data with Primavera Cloud using the Integration app, Primavera Cloud REST APIs, or the Data Service.

You can also enable access to download and login to Primavera Professional.

To configure boundary security settings:



3) On the Application Settings page, in the Boundary Security section, configure any applicable settings:

Allow API and Gateway Access: To allow integration using the API and Gateway.

Allow Data Service Access: To allow you to extract data from the application database using the Data Service, and to allow access to data using Primavera Analytics.

Allow Primavera Professional Access: To allow users to download and access Primavera Professional.

4) Select Save.

Configure Background Services Settings

Configure background services settings to customize how the application handles background job processing.

To configure background services settings:



3) On the Application Settings page, in the Background Services section, in the Delete Integration Jobs Older Than (Days) field, enter a value to determine when integration jobs will be automatically deleted from the application.

4) Select Save.

Note: If the Delete Integration Jobs Older Than (Days) field is set to 0, no integration jobs will be automatically deleted. The value must be greater than zero for the automatic deletion process to take effect.

Configure Authentication Settings

Configure authentication settings to determine how Primavera Cloud handles identity federation when adding new users. These settings are available only when Primavera Cloud detects that the current instance of Primavera Cloud is configured with an identity provider other than Oracle Identity Cloud Service for authentication.

To configure the authentication settings:


Workspaces Overview

25


3) On the Application Settings page, in the Authentication section, select one of the following:

Allow adding users as federated only option when all users must be authenticated by their company's own authentication system or identity provider.

Note: This option is selected by default.

Allow adding users as a mix of federated and non-federated option when users can be authenticated using their company's identity provider or through Identity Cloud Service.

Configure Authentication Timeout Settings

On an instance of Primavera Cloud hosted in the Oracle Cloud Infrastructure, application administrators determine the time in seconds before mobile and API users must authenticate their sessions. Requiring users to periodically authenticate with the server ensures the security of the server and protects against unauthorized access to application data. Application administrators can determine the frequency of authentication to suit their company's security needs. The minimum value for this setting is 1 second and the maximum value is 2,592,000 seconds (30 days).

To configure Authentication Timeout settings:



3) On the Application Settings page, in the Authentication Timeout section, complete the following fields:

a. Mobile (Seconds): The duration in seconds before mobile users are required to authenticate with the Primavera Cloud server.

b. API (Seconds): The duration in seconds before API users are required to authenticate with the Primavera Cloud server.

4) Select Save.

Workspaces Overview

Workspaces represent the hierarchical structure of your organization's businesses, projects, or processes. Workspaces can be subdivided into as many nodes or levels as needed to represent work at your organization. Nodes at the highest level might represent divisions within your organization, project types, site locations, or other major groupings that meet the needs of your organization.


26

The number of workspaces and their structure depend on your organization's project structure. For example, you might want to define increasingly lower levels of workspaces, similar to an outline, to represent broad areas of work that expand into more detailed projects. You might also want to create workspaces to contain users that require the same access to your organization's projects. Specify as many workspaces as necessary to fulfill the requirements of your operations executives and program managers. You can create workspaces under the production and non-production workspaces that are established for you. Most structures or data that you create under the non-production workspace can be moved to a production workspace through the import/export configuration feature.

Workspaces provide a way to customize sets of data for the projects contained within that structure. You can share data from higher level workspaces and create additional custom data within a specific workspace. Data that is required for the entire organization should be associated at the root level workspace so it can be pushed down to child production and non-production workspaces.

Working with Workspace Hierarchies

Workspaces in Primavera Cloud are arranged in a hierarchy that allows shared data and security to either be set at a high level and pushed down to child workspaces or configured individually at the workspace or project level. The top level of the workspace hierarchy consists of the root, or Company, workspace, and the root workspace has two child workspaces, Production and Non-Production. Each workspace, except the root workspace, can have additional child workspaces and projects with custom data sets and security. You can customize your workspace hierarchy with as many workspaces as necessary to suit the needs of your organization.

Tips for Creating Workspace Hierarchies

You should always plan ahead when creating your workspace hierarchy. Here are a few things to keep in mind when creating your workspace hierarchy in Primavera Cloud:

After shared data is added, you cannot modify the placement of a workspace in the hierarchy. It cannot be deleted or moved up or down in the hierarchy.

Workspaces cannot be added between two workspaces, which means that you cannot add another level to the workspace hierarchy between two already existing levels. For example, if you add "Workspace A" to the "Production" workspace, then you will not be able to add a workspace between them. If you believe that you may one day want to add a level between existing workspaces, then you can add placeholder workspaces to ensure that that level can be utilized later. If you set the sharing method for shared data in the placeholder workspace to Automatic, then all shared data will be automatically pushed down to the child workspace.

Some organizations might find it beneficial to organize the workspace hierarchy based on security access. Since security and permissions are defined at the workspace level, users who require the same security access should be added to the same workspace. If users from different departments in your organization require the same access to projects, then you should create the workspace hierarchy based on security needs instead of department or industry.

Workspaces Overview

27

Users can choose to use the Non-Production workspace as a test area before transferring data to the Production workspace. However, the Production and Non-Production workspaces can also be repurposed and renamed if you do not believe your organization will need a test area in the application.

Certain shared data, including security data, can be pushed down to child workspaces manually or automatically. Global shared data should be configured as high up in the workspace hierarchy as it will be needed and set it to automatically share to all child workspaces. For example, if your organization has a list of codes that apply to all projects in all workspaces, you should configure those codes in the root workspace so that all workspaces can inherit them.

Workspace Hierarchy Example

The following is an example workspace hierarchy in Primavera Cloud using a placeholder workspace. In this example, the company utilizes the Non-Production workspace and has set up workspaces for Development, Testing, and Integration so that they can figure out the best configuration to suit their organization's needs. For example, they are using the Integration workspace to test integrations with P6 and Microsoft Project. They use these workspaces to make final changes before transferring data to the Production workspaces that users will be working in.

For the workspaces that will live under Production, the company has decided to organize its shared data and security access by location and currently has projects based in New York City and Los Angeles. The company believes that it may one day have projects in other locations, and they would need to differentiate the location further in the workspace hierarchy to better organize shared data. Therefore, when this company was first establishing its workspace hierarchy, it left a placeholder workspace between the Production workspace and the workspaces for the New York City and Los Angeles-based projects. They can now add workspaces at that level as child workspaces to Production.

In this example, the company branches out to Japan and decides to add countries as parent workspaces to cities because each country will have its own unique shared data. Because they created their workspace hierarchy with a placeholder workspace, they are able to add another child workspace to the Production workspace to designate another country (Japan) and change the name of the placeholder workspace to United States. The company is now able to incorporate countries into their workspace hierarchy.


28

Create a Workspace

Creating multiple workspaces in the application enables you to represent hierarchical positions of all the projects in the database.

To create a workspace:

1) Edit the Root Workspace (on page 28)

This task is performed by the application administrator during the initial setup and can be repeated for the production and non-production workspaces.

2) Add a Workspace (on page 29)

3) Add an Image to a Workspace (on page 29)

4) Assign a User or User Group Access to a Workspace (on page 79)

5) Assign User Roles to a Workspace (on page 80)

6) Access a Workspace (on page 32)

Edit the Root Workspace

Your organization can customize workspaces to conform to the hierarchy of your organization's structure and contain users that should have the same security access to projects. Each organization has one root workspace with the option to add an unlimited number of child workspaces to the production and non-production workspaces. The root workspace represents your organization. Only an application administrator can edit the root workspace. You can create data at the root workspace level to share in your production and non-production environments.

To edit the root workspace:

1) In the object selector, select Workspaces, and then select View All Workspaces.

Workspaces Overview

29

2) In the Workspaces inventory panel, double-click the root workspace Name, ID, or Description column, and enter your changes.

3) Select Save.

4) In the inventory panel, select Close.

Tips

You can also edit the Name, ID, or Description fields for any other workspaces, including production and non-productions workspaces.

Add a Workspace

Add workspaces to categorize projects using similar data sets. Use sibling workspaces to represent those that are hierarchically equal and child workspaces to represent those that are subordinate. If you have already created a workspace with data and object configurations that will meet the needs of your new workspace, you can create a copy of the original workspace to revise.

To add a workspace:


2) In the Workspaces inventory panel, in the table, select a workspace row.

Note: Do not select the Company workspace. You cannot create additional workspaces under the Company workspace.

3) Select Add Workspace, and enter a Name, ID, and Description.

4) In the Parent Workspace field, select Select, choose where the workspace will reside in the organizational hierarchy, and select OK.

5) (Optional) In the Copy From Another Workspace field, select a workspace to copy.

6) Select Save.

7) In the inventory panel, select Close.

Tips

To remove any unnecessary workspaces, select the workspace, and then select Delete. You must have Administrator access to a workplace to delete it. You cannot delete a workspace that contains child workspaces, projects, portfolios, programs, resources, roles, and other configuration data. You can delete a workspace if it is created with shared data only.

You cannot create workspaces directly under the root workspace.

You cannot move a workspace in the workspace hierarchy once it is created, or add a workspace in the hierarchy between an existing parent and child workspace.

Add an Image to a Workspace

A workspace image is shown in some areas of the application such as the Workspace Home page. You can upload your own image or choose from existing images. You cannot upload an image with a CMYK color format.


30

To add an image to a workspace:

1) In the object selector, select a workspace.

2) In the sidebar, select Home.

3) Select Upload Image.

4) In the Select Image for Workspace dialog box, choose one of the following:

Under the Upload New Image section, in the Image field, select Browse, and then select an image.

Under the Choose from Existing section, select Gallery or Uploaded, and then select an existing image.

5) Select Select.

You can also perform this task from the workspace Details pages:


2) In the sidebar, select Summary & Settings.

3) On the Summary & Settings menu, select Details.

4) On the workspace Details, select Upload Image.

5) In the Summary & Settings panel, select Close.

Tips

To restore the default workspace image, select Reset to Default in the Select Image for Workspace dialog box.

Best Practices for Initial Configuration of Workspace Security and User Groups

This topic provides the recommended steps to set up user groups and permissions in your organization's workspace structure. Depending on how your organization is structured and how you plan to use Primavera Cloud, this guide might not be the best practices for you.

Workspaces Overview

31

Primavera Cloud provides automatic sharing of workspace security settings to create permission sets and user groups at a high level. As an application administrator, you only have to create the necessary user groups and permission sets for users once at the root workspace. The user groups will become available to all child workspaces, enabling you to add the appropriate users to the correct user groups at each child workspace. This process is shown in the image below.

For example, you might have a group of users that propose projects in the application. All project proposers need to have the same permissions, but they need to work in different workspaces. At the root workspace, you can create the Project Proposer user group and assign it the Project Proposer permission set. The Project Proposer user group will become available to each child workspace. In each child workspace, you can then assign the users that belong to the Project Proposer user group for that workspace. You can complete this process for all of the necessary user groups in your instance of Primavera Cloud.

You can take the following steps for the initial workspaces security configuration in your instance of Primavera Cloud:

1) Create Permission Sets at the Root Workspace

Permission sets are collections of security privileges that can be assigned to users or user groups. When you create the permission sets required by your organization at the root workspace, they will be available to be assigned to user groups at the root workspace and all child workspaces. See Permission Sets Overview (on page 37) for information about the permission sets available to be created.

2) Create Empty User Groups and Assign Permission Sets at the Root Workspace


32

User groups are collections of users with the same security permissions. At the root workspace, create the user groups needed to suit your organization's needs and assign the appropriate permission sets. Adding user groups at the root workspace makes them available to all workspaces in your instance of Primavera Cloud. By keeping the user groups empty at the root workspace, you will be able to determine who is added to each user group at the child workspace. See Add a User Group at the Workspace Level (on page 76) for more information.

3) Add and Assign Users to User Groups in Child Workspaces

By assigning users to the correct user group at the child workspace level, the user is afforded the associated security permissions in the child workspace. Assign users to user groups as soon as they are added to Primavera Cloud to ensure that they are afforded the correct permissions when they receive their welcome email containing their login credentials. See Assign a User to a User Group at the Workspace Level (on page 78) for more information.

Access a Workspace

Open a workspace to view apps that enable you to configure or view data at a workspace level such as workflows, shared data, reports, dashboards, ideas, resources, and documents.

To open a workspace:

In the object selector, select a workspace.

Shared Data Overview

Workspaces provide a way to customize sets of data for the workspaces and projects contained within that structure. You can share data from higher level workspaces and create additional custom data within a specific workspace. Data that is required for the entire organization should be associated at the root level workspace and use an Automatic sharing method so it is pushed down to child workspaces. Data that does not need to be automatically pushed down to child workspaces should use the default Manual sharing method.

Shared data prevents the need to re-enter data. It is locked for editing by the owning workspace, prohibiting unauthorized changes in other workspaces and projects. You must have the required security privileges to add, edit, and delete shared data. If your data ownership needs change, you can update the owning workspace. You cannot delete or move shared data if it is actively used by a child workspace or project.

All shared data is accessible from the Summary & Settings panel. A limited subset of shared data is also available in the project context. You can manage various configuration and security data types including:

Analysis Views

Calendars

Charts

Codes

Configured Fields

Cost Categories

Workspaces Overview

33

Currencies

Curve Profiles

Dashboards

Evaluation Categories

Folder Templates

Forms

Locations

Measures

Reasons

Reporting Cycles

Reports

Risk Matrix Templates

Risk Threshold Templates

Rules of Credit

Strategy Types

Units of Measure

Workflow Designs

Workflow Configurations

User Groups

Workspace Permission Sets

Project Permission Sets

Portfolio Permission Sets

Report Permission Sets

Idea Permission Sets

Program Permission Sets

Manage Shared Dictionaries

A child workspace can inherit dictionary data with a Manual sharing method from a parent workspace by using the Assign feature. Child workspaces can select which data to inherit instead of receiving all data by default. This method of data sharing prevents irrelevant data from being added to the workspace.

To pull down data from a parent workspace:

1) Navigate to a dictionary page (see page 329).

2) On the dictionary item page, select Assign.

3) In the Assign dialog box, select additional dictionary items, and select Assign.


This setting is used in the following apps:

Contracts and Commitments

Cost and Funds


34

Dashboards

Field

Files

Lean

Portfolio Analysis

Resources

Risk

Schedule

Scope

Strategic Alignment

Submittals

Workflows and Forms

Edit the Dictionary Sharing Method

If your data sharing methods change, you can update the sharing method of the data object. Any changes will affect new child workspaces. For example, if you change a data object to be shared automatically, all new child workspaces will automatically inherit this data. If you would like to use the data in pre-existing workspaces, you must use the Assign button to inherit the data.

The data sharing method must be changed in the owning workspace.

To edit the sharing method:


2) On the dictionary item page, select a dictionary entry.

3) In the Sharing Method list, specify how the data is shared between parent and child workspaces:

Manual: The data can be pulled down by child workspaces individually, using the Assignbutton in each child workspace. This is the default option.

Automatic: The data is pushed down to child workspaces automatically.

4) Save your changes:

In Primavera Cloud:

a. Select Save.

b. In the Summary & Settings panel, select Close.

In Primavera Professional:

Select Save.



Cost and Funds

Dashboards

Field

Files

Workspaces Overview

35

Lean

Portfolio Analysis

Reports

Resources

Risk

Schedule

Scope

Strategic Alignment

Submittals

Workflows and Forms

Update the Owning Workspace of Dictionary Items

Update the owning workspace to move a dictionary item to another workspace that you are assigned. If you move the item higher in the workspace hierarchy, it will be available to more workspaces. If you move it to a higher workspace, all child workspaces can access the dictionary item.

To update the owning workspace of a dictionary item:


2) On the dictionary item page, select a dictionary entry.

3) Select the Context menu, and then select Change Owning Workspace.

4) In the Select Workspace dialog box, select the new owning workspace, and select Select.


In Primavera Cloud:

a. Select Save.



Select Save.

Tips

You can also perform this task from context-specific pages in a workspace.



Cost and Funds

Dashboards

Field

Files

Lean

Portfolio Analysis

Reports


36

Resources

Risk

Schedule

Scope

Strategic Alignment

Submittals

Workflows and Forms

Update the Owning Workspace of Permission Sets

Update the owning workspace to move permission sets to another workspace that you are assigned. If you move the item higher in the workspace hierarchy, the permission set will be available to more workspaces. All child workspaces can access a permission set.

To update the owning workspace of a permission set:



3) On the Summary & Settings menu, select Permissions, and then select an object.

4) On the permission set page, select a permission set.

5) Select Manage Shared Data.

6) In the Manage dialog box, select a permission set row.



9) Select Save.


Tips

You can also perform this task from context-specific pages in a workspace.

Create shells of permission sets and user groups at the root workspace so that they inherit down the hierarchy to child workspaces.



Cost and Funds

Field

Files

Lean

Portfolio Analysis

Reports

Resources

Risk

Schedule

Security

37

Scope

Strategic Alignment

Submittals

Workflows and Forms

Security

Setting up the security for your application will allow you to control which users have access to what objects. Any security privileges set in the application will apply to mobile users.

To set up the security for the application, create permission sets and assign them to user groups. User groups are inherited down the workspace hierarchy. In child workspaces and projects, users can be added to the user groups, and the user groups can be assigned to objects.

Global permission sets and permission sets for all objects in all workspaces can be created and managed from the Permission Sets page in Global Admin. Permission sets for a workspace and the projects, portfolios, programs, custom logs, files, ideas, and reports in the workspace can also be managed at the workspace level. User groups for all workspaces can be managed from the User Groups page in Global Admin and also at the workspace or project level.

Permission Sets Overview

Permission sets are collections of security privileges that can be assigned to individual users or user groups. There are two types of permission sets in the application: global and object permission sets.

Global Permission Sets

All users must be assigned a global permission set. Global permission sets determine a user's access to application settings and application-wide functions such as administering workflows, assigning proxy users, adding and supervising timesheets, managing users and companies, and more.

Global permission sets are configured when a user is being added to the application or by editing the user’s details. The default global permission set for new users is View Only, though the application administrator can choose a different default global permission set. Global permission sets cannot be assigned to user groups.

Object Permission Sets

Users and user groups can also be assigned security permission sets for workspaces, projects, portfolios, programs, custom logs, files, ideas, and reports when access to these objects is being granted. Object permission sets are comprised of privileges that define a user’s ability to perform certain functions such as add, edit, and delete. They also define a user’s level of access to an object and its data. Object permission sets can be created by application administrators in Global Admin and by workspace administrators at the workspace level.


38

When you assign access to an object, you can choose to define permission sets to pertain to the objects within that object. For example, when you are assigning a user access to a project, you can choose to also assign a files permission set, which will then grant the user those privileges for all files in the project. If you want a user to only be able to access one file, then you should assign that user to the file directly. Additionally, when you assign a user or user group access to a workspace, the permission sets you define will also apply to any child workspace.

If a user or user group is assigned more than one permission set for an object, the user or group has the privileges for all assigned permissions. For example, if a user is granted the Add Project privilege in one user group that they are assigned to but not another, they will still be granted the Add Project privilege.

There are two permission sets that cannot be modified from the Permission Sets page but are available to assign to users: Administrator and View Only.

The Administrator permission set has all privileges assigned. It grants all functionality for an object as well as access to all of the object’s data. If a user has the Administrator permission set for a workspace, they will be able to see all data in the child workspaces as well. The Administration permission set for a workspace or project also grants the ability to edit the user and user group security for that object. If a user adds a workspace, project, portfolio, program, custom log, file, idea, or report, then they will automatically gain the Administrator permission set for that object.

The View Only permission set is the default permission set assigned to objects for users and provides read-only access to objects and their data. Note that the View Only permission set for a project, portfolio, or program does not include access to cost or financial information.

Create a Permission Set in Global Admin

The Permission Sets page in Global Admin provides application administrators one location to create and edit global permission sets and permission sets in all workspaces.

All users added to Primavera Cloud must receive a global permission set. You must also choose a global permission set to be the default permission set for new users who are added to the application. Select the default permission set for all new users by selecting the Default Permission Set checkbox in the privileges section of the Permission Sets page. The global permission set can be changed from the default permission set when a user is being added. Global permission sets are stored at the Global Admin level.

Depending on what they need access to, users may also receive permission sets for workspaces, projects, portfolios, programs, custom logs, files, ideas, and reports. The system Administrator and View Only permission sets for these objects are not listed on the Permission Sets page. However, they will be available to users when they are choosing default permission sets or assigning permission sets. When creating permission sets for these objects, you will first select the workspace where the permission set will be owned. These permission sets are inherited by all child workspaces. Inherited permission sets are also displayed on the Permission Sets page. The Owning Workspace of the permission set is the workspace that the permission set was created at.

To create a permission set on the Permission Sets page of Global Admin:


Security

39

2) In the sidebar, select Permission Sets.

3) On the Permission Sets page, select an object tab.

4) In the Workspace picker, select a workspace to add a new permission set in that workspace.

Note: You do not need to select a workspace on the Global tab.

5) On the Permission Sets page, on the object tab, select Add.

6) In the Name field, enter a unique name.

7) Expand each category to assign privileges.

8) Select Save.

Tips

To duplicate a permission set, select the Context menu, and then select Duplicate.

To delete a permission set, select the Context menu, and then select Delete. The system View Only global permission set cannot be deleted.

For quicker configuration, use Select All to select or deselect all checkboxes. Select the check box in a privilege column to select all privileges in that column.

Create a Workspace Permission Set

Create workspace permission sets to determine a user's level of access to a workspace. Users can only access workspaces that they have been assigned.

To create a workspace permission set:



3) On the Summary & Settings menu, select Permissions, and then select Workspace.

4) On the Workspace permission sets page, select Add.


6) In the Description field, enter a description of the permission set.

7) In the Privileges section, expand each category to assign privileges.

8) Select Save.


Notes:

To assign users to a workspace permission set, use the Securitypage in the Workspace Summary & Settings panel.

To assign a default workspace permission set to a user group, use the Default Permissions tab of the User Groups page.

Tips

You can duplicate existing permission sets by selecting the Add menu and selecting Duplicate.


40

Provide clear permission set names and descriptions to help you manage permissions.

You can delete a permission set by selecting the profile and selecting Delete. You can only delete permission sets that are not currently in use.

Create a Project Permission Set

Create project permission sets to determine a user's level of access to each project. Users can only access projects that they have been assigned.

To create a project permission set:



3) On the Summary & Settings menu, select Permissions, and then select Project.

4) On the Project permission sets page, select Add.




8) Select Save.


Notes:

To assign users to a project permission set, use the Security page in the Project Team app.

To assign a default project permission set to a user group, use the Default Permissions tab of the User Groups page.

Tips




Create a Portfolio Permission Set

Create portfolio permission sets to determine a user's level of access to each portfolio. Users can only access portfolios that they have been assigned.

To create a portfolio permission set:



3) On the Summary & Settings menu, select Permissions, and then select Portfolio.

4) On the Portfolio permission sets page, select Add.


Security

41



8) Select Save.


Notes:

To assign users to a portfolio permission set, use the Security page in the Portfolio Summary & Settings panel.

To assign a default portfolio permission set to a user group, use the Default Permissions tab of the User Groups page.

Tips




Create a Report Permission Set

Create report permission sets to determine a user's level of access to reports. Users can only access reports that they have been assigned.

To create a report permission set:



3) On the Summary & Settings menu, select Permissions, and then select Report.

4) On the Report permission sets page, select Add.




8) Select Save.


42

Notes:

To assign users access to all reports owned by a workspace, use the Security detail window in the Workspaces inventory panel. To assign users access to a specific report, use the Security detail window on the Report List page.

To assign a default report permission set to a user group, use the Default Permissions tab of the User Groups page.

Tips




Create a File Permission Set

Create file permission sets to determine a user's level of access to files. Users can only access files and folders that they have been assigned.

To create a file permission set:



3) On the Summary & Settings menu, select Permissions, and then select File.

4) On the File permission sets page, select Add.




8) Select Save.


Notes:

To assign users to a file permission set, use the Security detail window on the File List page.

To assign a default file permission set to a user group, use the Default Permissions tab of the User Groups page.

Tips




Security

43

Create an Idea Permission Set

Create idea permission sets to determine a user's level of access to each idea.

To create an idea permission set:



3) On the Summary & Settings menu, select Permissions, and then select Idea.

4) On the Idea permission sets page, select Add.

5) In the Name field, enter a unique name for the permission set.

6) In the Description field, enter a description for the permission set.

7) In the Privileges section, expand the Idea category to assign privileges.

8) Select Save.


Notes:

To assign users to an idea permission set, use the Security page in the Idea Summary & Settings panel.

To assign a default idea permission set to a user group, use the Default Permissions tab of the User Groups page.

Tips




Create a Custom Log Permission Set

Create custom log permission sets to determine a user's level of access to each project. Users can only access custom logs that they have been assigned.

To create a custom log permission set:



3) On the Summary & Settings menu, select Permissions, and then select Custom Log.

4) On the Custom Log permission sets page, select Add.




8) Select Save.


44


Notes:

To assign users to a custom log permission set, use the Permissions detail window on the Custom Logs page in the Project Summary & Settings panel.

To assign a default custom log permission set to a user group, use the Default Permissions tab of the User Groups page.

Tips




Create a Program Permission Set

Create program permission sets to determine a user's level of access to each program.

To create a program permission set:



3) On the Summary & Settings menu, select Permissions, and then select Programs.

4) On the Program permission sets page, select Add.

5) In the Name field, enter a unique name for the permission set.

6) In the Description field, enter a description for the permission set.


8) Select Save.


Notes:

To assign users to a program permission set, use the Security page in the Program Summary & Settings panel.

To assign a default program permission set to a user group, use the Default Permissions tab of the User Groups page.

Tips




Security

45

Security Privileges Definitions

Global Security Privileges Definitions

When creating a permission set, use the following definitions to determine the functionality each privilege controls and other privileges that may also be required. Selecting one privilege may automatically select other privileges if they are required for the original privilege to function properly. These other privilege selections cannot be changed without affecting the selection of the original privilege. Any privilege requirements are noted in the definition.

Configuration

Administer Workflow Instances

Enables users to view and manage all workflow instances on the Monitor Workflows page.

Application Settings

Enables users to edit application settings, which set global preferences for Oracle Primavera Cloud.

Assign Proxy Users

Enables users to assign other users to act as a proxy user.

Companies

Enables users to add, edit, and delete companies.

If Add is selected, the Edit privilege for Companies is also selected and cannot be changed. If Delete is selected, the Add and Edit privileges for Companies are also selected and cannot be changed. Selecting Add, Edit, or Delete also selects the Enable User Administration privilege and cannot be changed.

Create and Run User Reports

Enables users to create and run user reports.

Download Excel Files

Enables users to download tables as Microsoft Excel files.

Export Projects

Enables users to export projects to P6 XML and Microsoft Project XML.

Field Audit Records

Enables users to view field audit records such as the Data Modification Audit. Audit records include data such as logins, imports, and object setups. This privilege is used in the Field app only.

Manage Field Tablets

Enables users to manage tablets used by workers in the field. Users with this privilege can view IP addresses, assigned dates, and the last time the tablet was synchronized. They can also release tablets which will disconnect the tablet from the server. The next time that user tries to synchronize the tablet, it will erase all the data and remove the Host Number assignment. This privilege is used in the Field app only.


46

Manage Timesheets

Enables users to enter time and submit, approve, or reject a resource's timesheets.

If Enable is selected, the Add, Edit, Delete, and View privileges for Timesheets are also selected and cannot be changed.

Supervise Timesheets

Enables users to enter time and submit timesheets on behalf of the resources assigned to the projects.

If Enable is selected, the Add, Edit, Delete, and View privileges for Timesheets are also selected and cannot be changed.

Timesheet Settings

Enables users who are not application administrators to manage timesheet settings.

If Edit is selected, the View privilege for Timesheets is also selected and cannot be changed.

Timesheets

Enables users to add, edit, delete, and view timesheets.

User Administration

Enables users who are not application administrators to add, edit, and delete users.

This privilege can be assigned to users from another company. However, users that are also marked as restricted can only add, edit, and delete users from their company.

Workspace Security Privileges Definitions


Configuration

Administer Field Email Queue

Enables users to administer emails for the Field app.

Analysis Views

Enables users to add, edit, and delete Analysis Views.

If you select the add, edit, or delete privileges, all privileges are automatically selected.

CBS

Enables users to add, edit, and delete a workspace CBS.

Calendars

Enables users to add, edit, and delete calendars.

Security

47

If you select the add privilege, edit is automatically selected and cannot be changed. If you select the delete privilege, add, edit, and view are automatically selected and cannot be changed.

Charts

Enables users to add, edit, and delete charts.


Codes

Enables users to add, edit, and delete codes and code values data.


Configured Fields

Enables users to add, edit, and delete configured fields.

If you select the add privilege, edit is automatically selected. If you select the delete privilege, add and edit are automatically selected and cannot be changed.

Cost Categories

Enables users to add, edit, or delete cost categories.


Create Inspection Template

Enables users to create inspection templates in the Field app.

Currencies

Enables users to add, edit, and delete currencies.


Curve Profiles

Enables users to add, edit, and delete a curve profile.


Evaluation Categories

Enables users to add, edit, or delete evaluation categories.

If you select the add privilege, edit is automatically selected and cannot be changed. If you select the delete privilege, add and edit are automatically selected and cannot be changed.

Field Labels


48

Enables users to edit field labels.

Folder Templates

Enables users to add, edit, and delete folder templates.

If you select the add, edit, or delete privileges, all privileges are automatically selected.

Forms

Enables users to add, edit, delete, or view forms.

If you select the add privilege, edit, delete, and view are automatically selected. If you select the edit privilege, the view privilege is automatically selected. If you select the delete privilege, add, edit, and view are automatically selected.

Locations

Enables users to add, edit, and delete locations data.

You must assign all privileges.

Manage Field Email

Enables users to create and edit email templates in the Field app.

Manage Issue Custom Fields

Enables users to create and edit configured or custom fields for use in the Field app.

Manage Issue Statuses

Enables users to manage the status of application-wide issues in the Field app.

Manage Items Catalog

Enables users to add, edit, and delete items and standard issues in the items section of the Field app.

Measures

Enables users to add, edit, and delete measures.


Reasons

Enables users to add, edit, and delete reasons.


Report Cycles

Enables users to add, edit, and delete reporting cycles.


Resources

Enables users to add, edit, and delete resources.


Security

49


Enables users to add, edit, and delete risk matrixes.

You must assign all security privileges.


Enables users to add, edit, and delete risk thresholds.


Role Cost/Financials

Enables the user to edit and view role costs defined at the workspace level.

If you select the edit privilege, the view privilege is automatically selected and cannot be changed. The edit privilege for Roles is also selected.

Roles

Enables users to add, edit, and delete roles.


Rules of Credit

Enables users to add, edit, and delete rules of credit.


Start Workflows

Enables users to start workflow instances manually from the Start Workflow page.

If the Start Workflows privilege is enabled, the Workflows and Forms view privilege is automatically selected and cannot be removed.

Strategy Types

Enables users to add, edit, or delete strategy types.


Units of Measure

Enables users to add, edit, and delete units of measure.


Views

Enables users to add, edit, and delete workspace views and filters.


Work Orders


50

Enables users to add, edit, delete, or view work orders.


Workflow Configuration

Enables users to add, edit, delete, or view workflow configurations.


Workflow Design

Enables users to add, edit, delete, or view workflow designs.


Workspace Dashboards

Enables users to add, edit, and delete dashboards at the workspace level.


Workspaces

Enables users to add, edit, and delete workspace hierarchy nodes, and edit the workspace ID and name. Workspace nodes at the highest level (root) must be added by an application administrator.

If you select the add privilege, edit is automatically selected. If you select the delete privilege, add and edit are automatically selected.

General

Allow Project Creation to Copy from Existing

Enables users to allow project creation to copy from an existing project.

Funding

Enables users to add, edit, delete, and view funds.

If you select the add privilege, edit and view are automatically selected and cannot be changed. If you select the delete privilege, add, edit, and view are automatically selected and cannot be changed. If you select the add, edit, or delete privilege, the edit and view privilege for Funding Costs/Financials are automatically selected.

Funding Costs/Financials

Enables users to edit and view funds and financial data.

If you select the edit privilege, view is automatically selected and cannot be changed. If you select the edit or view privilege, the view privilege for Funding is automatically selected and cannot be changed.

Ideas

Security

51

Enables users to add ideas to the workspace.

Import Project

Enables users to import XML files from P6 EPPM and Microsoft Project.

Import Project Excel

Enables users to import Microsoft Excel (.xls or .xlsx) files for creating projects.

Portfolios

Enables users to add portfolios.

Print Layouts

Enables users to add print layouts.

Programs

Enables users to add programs to the workspace.

Project Proposals

Enables users to add project proposals.

Project Template

Enables users to add project templates.

Projects

Enables users to add projects.

Promote Report to Workspace

Enables users to promote a user report to a workspace report.

Recalculate Workspace Costs

Enables users to recalculate workspace costs when editing cost information.

Strategies

Enables users to add, edit, or delete strategies.

If you select the add privilege, edit and view are automatically selected and cannot be changed. If you select the delete privilege, add, edit, and view are automatically selected and cannot be changed.

Workspace Aggregate Cost Data

Enables users to view aggregate cost data for all projects and child workspaces within the workspace. If users also have the Project Costs/Financials privilege, they can access CBS costs in the project from the workspace Cost Sheet page.

Workspace Cost Sheet

Enables users to add and edit the workspace cost sheet.

If you select the edit privilege, the edit privilege for CBS is automatically selected and cannot be changed.


52

Users and Security

Permission Sets

Enables users to add, edit, and delete global, workspace, project, portfolio, file, and report permission sets.


User Groups

Enables users to add, edit, and delete user groups for the workspace. Users with this privilege can edit the user groups from the Workspace Summary & Settings or from the User Groups page in Global Admin.

If you select the add privilege, edit is automatically selected and cannot be changed. If you select the delete privilege, add and edit, are automatically selected and cannot be changed.

Project Security Privileges Definitions


Commissioning

Actual Dates

Enables users to edit the actual dates that work began or ended for commissioning (Cx) steps.

Commissioning Steps

Enables users to view Cx steps.

Complete Commissioning Steps

Enables users to complete Cx steps.

Planned and Forecasted Dates

Enables users to edit the Planned and Forecasted dates for Commissioning steps.

Reopen Commissioning Steps

Enables users to reopen completed Cx steps.

Contract

Contracts

Enables users to add, edit, delete, or view contracts.

The add and delete privileges for contracts also apply to contract line items.

If you select the add privilege, edit and view are automatically selected and cannot be changed.

Security

53

If you select the edit privilege, the view privilege is automatically selected and cannot be changed.

If you select the delete privilege, all privileges for Contract Costs/Financials are also automatically selected and cannot be changed.

Contract Costs/Financials

Enables users to edit or view contract costs and financial information associated with contracts.

If you select the edit privilege, the view privilege is automatically selected and cannot be changed. The edit and view privileges for Contracts are also selected and cannot be changed.

Contracts Approval

Enables users to approve and withdraw contracts.

If you enable this option, the privileges to edit and view Contract Costs/Financials are selected and cannot be changed.

Commitments

Enables users to add, edit, delete, or view commitments.

The add and delete privileges for commitments also apply to commitment line items.



If you select the delete privilege, all privileges for Commitment Costs/Financials are also automatically selected and cannot be changed.

Commitment Costs/Financials

Enables users to edit or view commitment costs and financial information associated with commitments.


Commitments Approval

Enables users to approve and withdraw commitments.

If you enable this option, the privileges to edit and view Commitment Costs/Financials are selected and cannot be changed.

Changes

Enables users to add, edit, delete, and view changes.



Changes Costs/Financials


54

Enables users edit and view changes.


These privileges also apply to changes.

Close/Reopen/Void Changes

Enables users to close, reopen, or void changes.

Change Orders

Enables users to add, edit, delete, and view change orders.

The add and delete privileges for change orders also apply to change order line items.



If you select the delete privilege, all privileges for Change Order Costs/Financials are also automatically selected and cannot be changed.

In order to add change orders, you also need at least the view privilege for contracts or commitments.

Change Order Costs/Financials

Enables users to edit or view change order costs and financial information associated with change orders.

If you select the edit privilege, the view privilege is automatically selected and cannot be changed. The edit and view privileges for change orders are also selected and cannot be changed.

Change Orders Approval

Enables users to approve and withdraw change orders.

If you enable this option, the privileges to edit and view Change Orders are selected and cannot be changed.

Potential Change Orders

Enables users to add, edit, delete, and view potential change orders.



If you select the delete privilege, all privileges for Potential Change Orders Costs/Financials are also automatically selected and cannot be changed.

Potential Change Orders Costs/Financials

Enables users to edit and view Potential Change Orders Costs/Financials.

These privileges also apply to potential change orders.

Potential Change Order Proposals

Security

55

Enables users to add, edit, and delete potential change order proposals.

Approve a Proposal and Close the Potential Change Order

Enables users to approve proposals and close potential change orders.

Withdraw a Potential Change Order

Enables users to withdraw potential change orders.

Payment Applications

Enables users to add, edit, delete, and view payment applications.



If you select the delete privilege, all privileges for Payment Application Costs/Financials are also automatically selected and cannot be changed.

In order to add payment applications, you also need at least the view privilege for contracts or commitments.

Payment Application Costs/Financials

Enables users to edit or view payment application costs and financial information associated with payment applications.

If you select the edit privilege, the view privilege is automatically selected and cannot be changed. The edit and view privileges for payment applications are also selected and cannot be changed.

Payment Applications Approval

Enables users to approve and withdraw payment applications.

If you enable this option, the privileges to edit and view Payment Applications are selected and cannot be changed.

Cost

Accept Proposed Budget and Request Changes

Enables users to accept a proposed budget for a project or request change.

Actuals

Enables users to add, edit, delete, or view actuals.



If you select the delete privilege, all privileges for Actuals and Actuals Costs/Financials are also automatically selected and cannot be changed.

Actuals Costs/Financials

Enables users to edit or view actuals costs and financials.


56

If you select the edit privilege, the view privilege is automatically selected and cannot be changed. The edit and view privilege for Actuals is also automatically selected and cannot be changed.

If you select the view privilege, the view privilege for Actuals is automatically selected and cannot be changed.

Cash Flow Snapshots

Enables users to add, edit, or delete cash flow snapshots.


Project Budget

Enables users to add, edit, delete, or view budgets.


Project Budget Approval

Enables users approve project budgets.

Project Cost Sheet

Enables users to add, edit, or delete project CBS codes. It also enables users to select and edit budget sources.


Recalculate Project Costs

Enables users to recalculate project costs when editing cost information.

Documents

Accept RFI Answer

Enables users to officially accept answers to RFIs.

Custom Log Types

Enables users to add, edit, or delete custom logs.


Manage Submittal Approvals

Enables users to manage submittal approvals.

If you enable this privilege, the Upload Submittals for My Company privilege is also enabled.

RFIs

Enables users to add, edit, and delete RFIs.


Reply/Forward RFI

Security

57

Enables users to forward and reply to RFIs.

Spec Sections

Enables users to add, edit, or delete spec sections.


Submittals

Enables users to add, edit, or delete submittals.


Upload Submittals for All Companies

Enables users to upload submittals for all companies.

Upload Submittals for My Company

Enables users to upload submittals for their associated companies.

View All RFIs

Enables users to view all published RFIs of any status.

If you enable this permission, then the View Pending RFIs option is also enabled.

View Pending RFIs

Enables user to view pending RFIs.

Field

Areas

Enables users to add, edit, delete, and view reports that were dispatched.

If you select the add, edit, or delete privilege, all privileges are automatically selected and cannot be changed.

Field Project Settings

Enables users to delete and view reports that were dispatched.

If you select the delete privilege, view is automatically selected and cannot be changed.

Import Areas

Enables users to import areas from a CSV file and edit and delete areas created through import.

Punchlist Issues and Inspections

Enables users to view punchlist issues and inspections.

QA/QC Issues and Inspections

Enables users to view QA/QC issues and inspections.

Safety Issues and Inspections

Enables users to view safety issues and inspections.


58

Subcontractor Daily Reports

Enables users to add, edit, or view subcontractor daily reports.

If you select the add privilege, edit and view are automatically selected. If you clear the view privilege, add and edit are automatically cleared.

Superintendent Daily Reports

Enables users to add, edit, or view superintendent daily reports.

If you select the add privilege, edit and view are automatically selected. If you clear the view privilege, add and edit are automatically cleared.

Funds

Funding

Enables users to add, edit, delete, and view funds.

If you select the add privilege, edit and view are automatically selected and cannot be changed. If you select the delete privilege, add, edit, and view are automatically selected and cannot be changed. If you select the add, edit, or delete privilege, the edit and view privilege for Funding Costs/Financials are automatically selected.


Enables users to edit and view funds and financial data.

If you select the edit privilege, view is automatically selected and cannot be changed. If you select the edit or view privilege, the view privilege for Funding is automatically selected and cannot be changed.

Inspections

Access Other Users Inspections

Enables users to access inspections of all users in the project.

Conduct Inspections

Enables users to conduct inspections. This privilege should be assigned to inspectors who will conduct onsite inspections.

Completed Inspections

Enables users to delete completed inspections.

Incomplete Inspections

Enables users to delete completed inspections.

Inspection Templates

Enables users to add, edit, and delete or view inspection templates.

If you select the add, edit, or delete privilege, all three privileges are automatically selected and cannot be changed.

Inspections

Enables users to add, edit, or view inspections.

Security

59

If you select the add or edit privilege, all privileges are automatically selected and cannot be changed.

Reopen Inspections

Enables users to reopen completed or approved inspections and return the inspection to in progress status.

Issues

Change Issue Status

Enables users to change the status of the issue.

Corrective Actions

Enables users to edit the corrective actions of the issue.

Issues

Enables users to add, edit, delete, or view issues.

If you select the add or edit privilege, both privileges are automatically selected and cannot be changed. If you select the Delete privilege, all privileges are automatically selected and cannot be changed.

Manage Field Work Calendar

Enables users to manage the calendar in the Field app including setting holidays and working days.

Manage Issue Statuses

Enables users to manage the issue workflow for the project including categories, statuses, and actions.

Lean

Manage Commitments and Complete All Users' Tasks

Enables users to commit to the tasks, delete the commitments, and complete the tasks that are assigned to any user.

If the privilege is enabled, Manage Commitments and Complete My Tasks and the Edit privileges for Tasks for My Company and Tasks for All Companies will also be enabled and cannot be changed.

Manage Commitments and Complete My Tasks

Enables users to commit to the tasks, delete the commitments, and complete the tasks that are assigned to them.

If the privilege is enabled, the Edit privilege for Tasks for My Company will also be enabled and cannot be changed.

Tasks for All Companies

Enables users to add, edit, or delete tasks for all companies.


60

If you select the add privilege, edit is automatically selected. If you select the delete privilege, add and edit are automatically selected. Any privileges selected here will also be selected for Tasks for My Company.

Tasks for My Company

Enables users to add, edit, or delete tasks for their company.


Project

Add WBS from other projects/templates

Enables users to copy WBS nodes and objects within the nodes from a project template or another project. To use this feature, the Add Activities privilege must also be selected.

Applies to: Schedule, Scope

Alerts

Enables users to add, edit, and delete system alerts that appear when thresholds are met on project-level data. Users do not require privileges to subscribe or unsubscribe themselves to an alert.

If you select the add, edit, or delete privilege, all Alerts privileges are also selected and cannot be changed.

Applies to: Costs and Funds, Schedule, Scope

Baselines

Enables users to add, edit, and delete project baselines. To choose or change a baseline type, the Enable Baselines - Set Project Baselines privilege must also be selected.

The Add and Edit privileges must be selected together. If Delete is selected, the Add Baselines, Edit Baselines, and Enable Baselines - Set Project Baselines privileges are also selected and cannot be changed.


Baselines - Edit Activity Data

Enables users to edit the activity data within a baseline. When this privilege is disabled, baseline activity data is read-only.

If Enable is selected, the Add Baselines and Edit Baselines privileges are also selected and cannot be changed.

Applies to: Schedule

Baselines - Set Project Baselines

Enables users to select a baseline type when adding a baselines or change the type of an existing baseline.

If Enable is selected, the Add Baselines and Edit Baselines privileges are also selected and cannot be changed.


Close Reporting Periods

Security

61

Enables users to close the current reporting period to further edits. Closed periods allow for accurate project analysis and reporting.

Applies to: Scope

Companies

Enables users to assign or remove companies from a project and change the color associated with each company.

Applies to: Project Team

Currencies

Enables users to change the project currency and its associated exchange rate.

If Edit is selected, the Edit Project privilege is also selected and cannot be changed.

Applies to: Project Settings

Global Change

Enables users to add, edit, or delete public global changes or private global changes that belong to them.

If Add is selected, Edit is also selected and cannot be changed. If Delete is selected, Add and Edit are also selected and cannot be changed.


Global Change - Run

Enables users to run public global changes or global changes that belong to them.

If Enable is selected, the Add Global Change and Edit Global Change privileges are also selected and cannot be changed.


Project

Enables users to edit or delete project-level data such as project details, codes, and settings. Some data such as alerts, currencies, and dictionaries have their own privileges.

If Delete is selected, Edit is also selected and cannot be changed.

Applies to: Project Inventory, Project Settings

Project Costs/Financials

Enables users to view and edit project cost fields across the application, including at the portfolio and program levels, for pages to which the user has access. Without the Edit privilege, cost fields will be read-only. Without the View privilege, depending on the page, cost fields may be hidden, show a lock icon instead of a value, or the page may be restricted entirely.

Configured fields with a Data Type of Cost for objects in other contexts, objects with their own Cost/Financials privileges (Changes, Change Estimates, Change Order, Contract, Commitments, Fund, Payment Applications, Potential Change Orders, Project Actuals), and the File object are not controlled by the Project Costs/Financials privileges.

When the View privilege is selected, the following functionality is enabled:

Cost-related field values on the Cost Sheet page are displayed.

All fields on the project Cash Flow page are displayed.


62

Cost-related field values on the project Budget page are displayed and editable as long as the project Edit Project Budget and View Project Budget privileges are also enabled.

Cost-related project-level field values on the program Summary Cost Sheet page are displayed.

Cost-related project-level field values on the portfolio Budget Planning, Published Views, and Scenario Comparison pages are displayed.

Cost-related project-level risk field values on the project Risk Register page are displayed.

Cost-related project-level risk field values on the program Risk Register page are displayed as long as the program View Risk and project View Risk privileges are also enabled.

All cost-related scope field values are displayed.

The Construction Value field in the project details is displayed.

Configured fields with a Data Type of Cost are editable for the following objects as long as the Edit privilege for the corresponding object (Project Budget or Project Cost Sheet) is also enabled: Budget, Budget Changes, Budget Transfers, Project Cost Sheet. These objects do not require the Edit privilege for Project Costs/Financials to be enabled in order to be edited. Cost type configured fields for the Budget Details object can be edited without enabling the Edit privileges for Project Costs/Financials or Project Budget. Cost type configured fields for the Budget Details object are displayed as long as the View Project Costs/Financials and View Project Budget privileges are also enabled.

When the Edit privilege is selected, the following functionality is enabled:

All fields on the project Cash Flow page are editable.

Cost-related scope fields are editable as long as the Edit privilege for an individual scope object is also enabled.

Cost-related project-level risk fields on the project Risk Register page are editable as long as the project Edit Risk and View Risk privileges are also enabled.

Cost-related project-level risk fields on the program Risk Register page are editable as long as the program View Risk, project Edit Risk, and project View Risk privileges are also enabled.

Configured fields with a Data Type of Cost are editable for the following objects as long as the Edit privilege for the corresponding object is also enabled: Activity, Custom Log, Project, Resource Assignment, RFI, Risk, Scope Assignment, Scope Item, Submittal, Task, WBS, Work Packages.

If the Edit privilege is selected, the View Project Costs/Financials and Edit Project privileges are also selected and cannot be changed.

Applies to: Costs and Funds, Project Details, Risk, Scope

Project Dashboards

Enables users to add, edit, and delete dashboards at the project level.

If you select the add, edit, or delete privilege, all Project Dashboards privileges are also selected and cannot be changed.

Applies to: Dashboards

Project Integration

Security

63

Enables users to run project synchronizations between Primavera Cloud and P6 EPPM or Primavera Gateway. To view project synchronizations, the Edit Project privilege must also be selected.

Applies to: Integration

Promote Report to Project

Enables users to promote user type reports to the project type, making them available to other users of the project.

Applies to: Reports

User Groups

Enables users to add, edit, and delete project-level user groups. Users with the Edit privilege can also edit the permission sets of enabled inherited user groups, assign users to an inherited user group, and remove users from an inherited user group if the user was assigned at the project level. Users with these privileges can configure user groups from the Project Team app or from the User Groups page in Global Admin.


Applies to: Global Admin, Project Team

Views

Enables users to add, edit, and delete project-level views and filters. Users do not require privileges to add, edit, or delete personal views or filters.


Applies to: Project-level pages that support named views

WBS

Enables users to add, edit, and delete WBS nodes.



Project Proposals

Project Proposals

Enables users to edit or delete project proposals.

You need this privilege to launch a project proposal workflow. This privilege allows users to add project proposals and launch a workflow even if they do not have the Start Workflows privilege.

Project Proposals and WBS Costs/Financials

Enables users to edit WBS costs and financials.

Resources

Resource Demand


64

Enables users to add, edit, and delete resource demands.


Resources

Enables users to add, edit, and delete resources.


Roles

Enables users to add, edit, and delete roles.


Risk

Risk

Enables users to add, edit, delete, or view risks.

If you select the add privilege, edit and view are automatically selected. If you select the delete privilege, add, edit, and viewt are automatically selected.

Risk Analysis

Enables users to run risk analysis.

Risk Matrix

Enables users to add, edit, delete, or risk matrixes.


Schedule

Activities

Enables users to add, edit, or delete activities.


Level

Enables users to run the leveler.

Relationships

Enables users to add, edit, or delete relationships.


Schedule

Enables users to run the scheduler.

Security

65

Schedule Scenario

Enables users to add, edit, delete, or view schedule scenarios.

If you select the add privilege, edit and view are automatically selected. If you select the delete privilege, add, edit, and view are automatically selected.

Set Baseline as Current Schedule

Enables users to set a baseline as the current schedule.

When this privilege is selected, the add, edit, and delete Activities privileges are automatically selected and cannot be changed.

Set Scenario as Current Schedule

Enables users to set a scenario as the current schedule.

When this privilege is selected, the add, edit, and delete Activities privileges are automatically selected and cannot be changed.

Scope

Approve/Reject Scope Change Requests

Enables users to approve or reject scope change requests, reject individual change items, withdraw approved change requests, and reopen rejected change requests and items. When this privilege is selected, the following add and edit privileges are also selected: Work Packages, Scope Items, Scope Assignments, and Scope Change Requests. The edit and view privileges for Project Costs/Financials are also selected.

PBS

Enables users to add, edit, or delete PBSs.


Scope Assignments

Enables users to add, edit, or delete scope item assignments. If you have the delete privilege, you can only delete work packages before the baseline is set.


Scope Change Requests

Enables users to add, edit, or delete scope change requests and pending change items in the Scope Item Changes, Work Package Changes, Scope Item Change Details, and Work Package Change Details pages. This privilege also allows users to add and edit scope items on the Scope Item Change Details page if the user also has the corresponding add and edit Scope Items privileges. Also allows users to add and edit work packages and scope assignments on the Work Package Change Details page if the user also has the corresponding add and edit Work Packages and Scope Assignments privileges.


Scope Items


66

Enables users to add, edit, or delete scope items. If you have the delete privilege, you can only delete work packages before the baseline is set.


Work Packages

Enables users to add, edit, or delete work packages. If you have the delete privilege, you can only delete work packages before the baseline is set.


Work Order

Dispatched Reports

Enables users to view reports that were dispatched.

Send Work Orders

Enables users to send work orders to the responsible party.

Work Order Rule

Enables users to create dispatch rules for work orders.

If you select the edit privilege, view is automatically selected and cannot be changed.

Portfolio Security Privileges Definitions


Budget Plan

Approve Budget Scenario

Enables users to approve scenarios associated with budget plans.

Budget Scenarios

Enables users to add, edit, or delete budget scenarios.


Propose Budget Scenario

Enables users to launch a Propose workflow from the Budget Planning and Selection Analysis views.

This privilege allows a user to launch workflows using the actions button or menu even if they do not have the Start Workflow privilege.

Send Budget Scenario for Approval

Security

67

Enables users to launch the Send for Approval workflow from the Budget Planning and Selection Analysis views.

This privilege allows a user to launch workflows using the actions button or menu even if they do not have the Start Workflow privilege.

Send Budget Scenario for Review

Enables users to launch the Send for Review workflow from the Budget Planning and Selection Analysis views.

This privilege allows a user to launch a workflow using the action button or menu even if they do not have the Start Workflow privilege.

Funds

Funding

Enables users to add, edit, delete, and view funding for portfolios.

If you select the add privilege, edit and view are automatically selected for both Funding and Funding Costs/Financials and cannot be changed. If you select the delete privilege, add, edit, and view for Funding and Funding Costs/Financials are automatically selected and cannot be changed.


Enables users to edit or view funding costs and financials.

If you select the edit privilege, view is automatically selected and view privileges for Funding are also enabled.

Portfolio

Assign Workflows to Portfolios

Enables users to specify which workflows the system initiates when budget plans are set to the Send for Review, Propose, and Send for Approval phases.

Portfolio Costs

Enables users to view or edit portfolio costs.

If you select the edit privilege, view is automatically selected and edit is selected for Portfolios and cannot be changed.

Portfolio Dashboards

Enables users to add, edit, and delete dashboards at the portfolio level.

You must assign all privileges.

Portfolio Thresholds

Enables users to add, edit, or delete portfolio monitoring thresholds.


Portfolios

Enables users to edit or delete portfolios.


68

If you select the delete privilege, edit is automatically selected and cannot be changed.

Snapshots

Enables users to add or delete snapshots.

If you select the delete privilege, add is automatically selected and cannot be changed.

Resource Plan

Approve Resource Scenario

Enables users to approve scenarios associated with resource plans.

If you select enable, the edit privilege for Resource Scenarios is automatically selected and cannot be changed.

Propose Resource Scenario

Enables users to launch a Propose workflow from the Resource Planning page.

This privilege allows a user to launch workflows using the actions button or menu even if they do not have the Start Workflow privilege. If you select enable, the edit privilege for Resource Scenarios is automatically selected and cannot be changed.

Resource Scenarios

Enables users to add, edit, or delete resource scenarios.

If you select the add privilege, edit is automatically selected and cannot be changed. If you select the delete privilege, add, and edit are automatically selected and cannot be changed.

Send Resource Scenario for Approval

Enables users to launch the Send for Approval workflow from the Resource Planning page.

This privilege allows a user to launch workflows using the actions button or menu even if they do not have the Start Workflow privilege. If you select enable, the edit privilege for Resource Scenarios is automatically selected and cannot be changed.

Send Resource Scenario for Review

Enables users to launch the Send for Review workflow from the Resource Planning page.

This privilege allows a user to launch a workflow using the action button or menu even if they do not have the Start Workflow privilege. If you select enable, the edit privilege for Resource Scenarios is automatically selected and cannot be changed.

Report Security Privileges Definitions


Project Report

Enables users to edit or delete project reports.


Security

69

Run and Preview Project Report

Enables users to run and preview project reports.

Run and Preview Workspace Report

Enables users to run and preview workspace reports.

Workspace Report

Enables users to edit or delete workspace reports.


File Security Privileges Definitions


Download Files

Enables users to download files to use offline.

Files

Enables users to add, edit, or delete files.


Folders

Enables users to add, edit, or delete folders.


Ideas Security Privileges Definitions


Accept

Enables users to accept a submitted idea.

Assign Owner

Enables users to assign an owner to an idea. Idea owners are responsible for evaluating and accepting or rejecting ideas.

Evaluation


70

Enables users to access the Evaluation page in the Strategic Alignment app and assign evaluation scores to ideas.


Idea

Enables users to edit or delete ideas.

If you select the delete privilege, the edit privilege is automatically selected and cannot be changed.

Reject

Enables users to reject a submitted idea.

Reopen

Enables users to reopen rejected ideas for reconsideration.

Set as Draft

Enables users to set an idea as a draft.

Custom Log Security Privileges Definitions


Custom Log

Custom Log Items

Enables users to add, edit, or delete custom log items.


Program Security Privileges Definitions


Program

Program

Edit or delete a program.

Security

71

If you select the delete privilege, the edit privilege is automatically selected and cannot be changed.

Program Costs/Financials

Enables users to edit and view costs and financial information for programs.

Program Dashboards

Enables users to add, edit, and delete dashboards at the program level.


Cost

Cash Flow Snapshot

Enables users to add, edit, or delete cash flow snapshots.

Program Aggregate Cost Data

Enables users to view the cost data on the Summary Cost Sheet page.

Program Budget

Enables users to add, edit, or delete program budget data.

Program Budget Approval

Enables users to approve program budgets.

Program Cost Sheet

Enables users to add, edit, or delete program CBS codes.


Recalculate Program Costs

Enables the Recalculate button on the Program Cost Sheet to refresh the data on the program.

Risk

Risk

Enables users to add, edit, delete, or view program risks.

Risk Matrix

Enables users to add, edit, delete, or view program risk matrixes.



72

User Groups Overview

A user group is a collection of permission sets that determine access to objects for a group of users. Users that should be afforded the same access to an object are added to user groups in the appropriate workspace or project. A user group can be assigned to a workspace, project, portfolio, report, file, idea, custom log, or program.

How are user groups inherited?

User groups are owned by a workspace, which means that they can be inherited by workspaces and projects below the owning workspace in the hierarchy. The owning workspace for a user group is the workspace it was created at or the owning workspace of the project that the user group was created at. The owning workspace does not control access, but instead determines where the user groups become available to be assigned.

User groups created at the workspace level are automatically inherited by child workspaces and projects, where they are available to be modified and assigned as needed. User groups created at the project level will only be available to that project.

Since workspace user groups are inheritable and customizable, they should be created as high in the workspace hierarchy as possible so that they are available to be assigned in all child workspaces and their projects.

How are users added to user groups?

Users are assigned to user groups at the workspace or project where they should gain access. For example, if you assign User A to User Group 1 in Workspace X, then the user will gain access to Workspace X and its child workspaces. This won't grant User A access to the objects that User Group 1 is assigned to in the parent workspace of Workspace X.

Can users be added to more than one user group?

Yes. A user in multiple user groups assigned to the same object has access to that object with all permissions assigned by the user groups of which they are a member. For example, if they are granted the Add Project privilege in one user group that they are assigned to but not another, they will still be granted the Add Project privilege.

Do user groups grant access as soon as they are created and users are added?

No. User groups need to be directly assigned to a workspace, project, portfolio, report, file, idea, custom log, or program for access to be granted. Before a user group is assigned to an object, no access has been granted to users in the user group, even to the owning workspace of the user group.

Users added to a user group after the user group has been assigned to an object will automatically gain access to those objects.

Multiple user groups can be assigned to the same object.

Where are user groups managed, and who can create and edit user groups?

User groups can be managed at the Global Admin, workspace, or project level.

Security

73

In Global Admin, user groups in the application can be managed by application administrators, workspace and project administrators, and users with the user group privilege for a project or workspace. While application administrators have access to all user groups, all other users who manage user groups in Global Admin can only view user groups for workspaces and projects that they have access to.

User groups can also be managed from the Summary & Settings of a workspace or from the Project Team app of a project. At the workspace or project level, only user groups for that object and inherited user groups can be managed by administrators and by users with the User Groups privilege at that level.

User groups can be assigned to workspaces and projects on the Global Admin User Groups page. They can be assigned to all objects at the object level as well.

Manage User Groups in Global Admin

The User Groups page in Global Admin provides one central location to add user groups and assign user group access for all workspaces and projects in the application. You can select a project or workspace in the Context picker to view all user groups for that context including those inherited from workspaces in the hierarchy.

On this page, users can also be assigned to user groups for any context. Use the Show Inherited Workspace Users toggle in the Users section to view the users in the user group that were inherited by that context from workspaces up the hierarchy.

User Group Page Permissions

Access to the User Groups page in Global Admin and its functionality is only available to users with the correct permissions.

Application administrators have complete access to the Users Groups page and its functionality. They are able to view all workspaces and projects in the Context picker, view all users for any user group, and assign access for all user groups.

Workspace administrators (users assigned the Administrator permission set for a workspace), project administrators (users assigned the Administrator permission set for a project), and users with the User Group privilege for a workspace or project can access the User Groups page in Global Admin, but with limited functionality. For these users, the availability of workspaces and projects in the Context picker will depend on the user’s individual access – all inaccessible contexts will be labeled Restricted in the hierarchy. These users will also not be able to view inherited workspace users for a user group if they do not have access to the workspace where the user belongs to the user group.

Workspace administrators and project administrators can assign user groups to a workspace or project on the User Groups page, but users with the User Group privilege for a workspace or project do not have this functionality.

The access and actions for a user based on their permission level are summarized in the table below.


74

User Groups Page Functionality by Role

Access All Contexts in Context Picker

Add, Edit, and Delete User Groups

View All Inherited Users for a User Group

Assign Users to a User Group

Assign User Group to a Workspace or Project

Application Administrator

X X X X X

Workspace Administrator

X X X

Project Administrator

X X X

User with User Group privilege for a Workspace

X X

User with User Group privilege for a Project

X X

Note: The User Administration global privilege does not provide access to the User Groups page.

Add a User Group in Global Admin

A user group is a collection of permission sets that determine access to objects for a group of users. The User Groups page in Global Admin provides one location where user groups in all workspaces and projects can be added and managed.

Application administrators, workspace administrators, project administrators, and users with the User Groups privilege can add a user group on the User Groups page in Global Admin. Workspace administrators, project administrators, and users with the User Group privilege might have restrictions on what contexts they can access from the Context picker. See Manage User Groups in Global Admin (on page 73) for more details.

To add a user group:


2) In the sidebar, select User Groups.

3) In the Context picker, select a workspace or project to add the user group to.

4) On the User Groups page, select Add.

5) In the Name field, enter a unique name for the user group.

Security

75

6) In the Description field, enter a description of the user group.

7) In the Permission Sets field for each Permission Type, select a permission set.

Some permission sets may be required in order to assign access later.

8) Select Save.

Note: Users will not be granted access to objects until their user group is assigned to an object.

Assign a User to a User Group on the User Groups Page

On the User Groups page in Global Admin, you can assign users to all of your user groups. You can assign multiple users to a user group at the same time on the Assign dialog box. To assign a user to a user group, you must be an application administrator, workspace administrator, project administrator, or have the User Group privilege for a workspace or project.

To assign a user to an existing user group:



3) In the Context picker, select the workspace or project to assign the user to the user group at.

4) Select a user group row, and in the Users section, select Assign.

5) In the Assign Users dialog box, in the View By field, select All Companies, All Users, orActive Users.

6) Select one or more users from the Available list, and then select Add from Available to move them to the Selected list.

7) Select Assign.

8) Select Save.


Tips

If a user group is inherited by a child workspace, you can view the inherited users by selecting Show Inherited Workspace Users.

Assign User Group Access to a Workspace or Project

Assign user groups to a workspace or project so that users will gain access to the objects. Until the user group is assigned to an object, it does not grant any access to the users in it.

Only application administrators, workspace administrators, and project administrators have the ability to assign user group access in Global Admin. For user group access to be assigned, the required permission sets must be defined.

To assign user group access to a workspace or project:



76


3) In the Context picker, select a workspace or project to assign the user group to.

4) In the User Group list, in the Enabled column, select the check box for a user group that you want to assign to the chosen workspace or project.

5) Select Save.

Tips

To unassign user group access to a context, select a context from the Context picker, and then clear the Enabled check box for a user group row.

Manage User Groups at the Workspace Level

Add a User Group at the Workspace Level

User groups can be created at the workspace level, where they will be available to be assigned to objects in the workspace. They will also be automatically inherited by child workspaces and projects.

User groups can be assigned to a workspace, project, portfolio, report, file, idea, custom log, and program.

To create a user group at the workspace level:



3) On the Summary & Settings menu, select User Groups.


5) In the Add Group dialog box:

a. In the Name field, enter a unique name for the group.

b. In the Description field, enter a description of the user group, and select Next.

c. Enter part or all of a user's login name or personal name into the Search field.

d. Select one or more users, and then select Next.

e. In a Permission Set column for each Permission Type, select a permission set. Add any permission sets applicable to all users of the group.

6) Select Add.

7) Select Save.



Tips

Duplicate a user group by selecting the Add menu and selecting Duplicate.

To remove a user from the user group, select the Context menu by the user's name, and then select Remove.

Security

77

If a user group is inherited by a child workspace, you can view the inherited users by selecting View Inherited Users.

The Search feature searches the entire list of users for matches. During that initial search, it will stop after finding 500 results, then filter out those who have already been assigned. For this reason, your maximum number of search results might vary. To limit the number of results, be as specific as possible when entering a name in the search field. For example, enter the first and last name of the user.

Assign a Default Permission Set to a User Group at the Workspace Level

Default permission sets allow you to assign an existing permission set automatically when you assign user groups to workspaces, projects, portfolios, reports, files, ideas, custom logs, and programs. After a user group is assigned to an object, the permission set can be modified at any time. You do not have to select a default permission set. If you change a default permission set for a user group, permissions on existing assignments will not change.

To assign a default permission set to a group:




4) On the User Groups page, select a user group, and then select the Default Permissionsdetail window.

5) In the Default Permissions detail window:

a. In the Permission Set column, in the Permission Type row, select a permission set.

b. Add any permission sets applicable to all users of the group.

6) Select Save.


Assign a Deleted System User Group in the Root Workspace

By default, Primavera Cloud includes several predefined—or "system"—user groups. If any of these groups is deleted from the root workspace, you can retrieve it as long as you have access to the root workspace.

To retrieve a deleted system user group in the root workspace:

1) In the object selector, select the root workspace.



4) Above the list of user groups (and not in the Users detail window for a user group), select Assign.

5) In the Assign System User Groups dialog box, select a deleted system user group.

6) Select Assign.

7) Select Save.



78

Assign a User to a User Group at the Workspace Level

You can assign a user to a user group on the User Groups page in the workspace Summary & Settings.

To assign a user to a user group:




4) On the User Groups page, select a user group, and then select the Users detail window.

5) In the Users detail window, select Assign.

6) In the Assign dialog box, enter part or all of a user's login name or personal name into the Search field.

7) Select one or more users, and then select Assign.

8) Select Save.


Tips

To remove a user from the user group, select the Context menu by the user's name, and then select Remove.

If a user group is inherited by a child workspace, you can view the inherited users by selecting View Inherited Users.


View Inherited Users in a Workspace User Group

User groups are automatically inherited by child workspaces and projects. If you select an inherited user group, you can view a list of all users inherited from parent workspaces.

To view inherited users:




4) On the User Groups page, select an inherited user group, and then select the Users tab.

5) On the Users tab, select View Inherited Users.

6) Review the inherited users, and select OK.


Security

79

User Access Overview

User access can be set at the workspace, project, portfolio, report, file, idea, custom log, and program level. Access can be assigned to individual users or to groups of users through user groups. Users and user groups can also gain access to objects when they are assigned to a workspace. Privileges are assigned to users and groups through permission sets, which determine what a user can see and what tasks a user can perform.

Assign a User or User Group Access to a Workspace

Assign user access at the workspace level individually or through groups. Each user or group must be assigned a workspace permission set. If a user or user group has a set of default permission sets, these will be used but can be changed during the assignment. At the workspace level, assigning a user or group an object permission set will grant access to all instances of that object within the current workspace.

To assign user access to a workspace:



3) On the Summary & Settings menu, select Security.

4) Select the Assign menu, and then select User or Group.

5) In the Assign User or Assign Group dialog box, enter the user or group name.

6) Select the name, and select Next.

7) In the Permission Set column, select the workspace permission set.

8) (Optional) Add any other permission sets applicable to that user or group.

9) Select Assign.

10) Select Save.


You can also do this in the Workspace inventory panel.


2) In the table, select a project, and then select the Security detail window.

Tips

If you added the workspace, you are automatically assigned access to the workspace with the Administrator permission set.

User access assignments made at the workspace level will not be seen in the Security detail windows for the objects within the workspace.



80

Assign User Roles to a Workspace

Assigning roles enables you to route built-in portfolio budget and resource planning-related workflows to specific users. Assigning roles at the workspace level is useful if the same people will be assigned the same roles for all projects within the workspace. These assignments can also be updated at the project level or at the portfolio level for all projects in the portfolio.

The creator of a workflow, project, or portfolio is, by default, assigned to it as a reviewer, approver, and owner. The creator is also assigned as the primary reviewer, primary approver, and primary owner and can assign other role assignments to it. New projects in any workspace automatically inherit the role assignments from that workspace, but changes to the workspace role assignments do not affect the role assignments of its projects.

To assign user roles to a workspace:



3) On the Summary & Settings menu, select Security.

4) Select Edit Roles.

5) In the Edit Roles dialog box, in the Assign Roles section, select Assign Users.

6) In the Select User dialog box, enter a username, select the name, and then select Assign.

7) In the Edit Roles dialog box, select the roles you want users to perform:

Reviewer: The users assigned to the Reviewer role will receive notification when a planner sends a budget or resource plan scenario out for review.

Approver: The users assigned to the Approver role will receive notification when a planner sends a budget or resource plan scenario out for approval.

Owner: The users assigned to the Owner role in the respective projects will receive notification when a planner shares the projects in a budget or resource plan scenario proposal for negotiations.

8) Review the primary roles in the Set Primary Role Defaults section and make updates as necessary.

9) Select Assign.

10) Select Save.


You can also do this in the Workspace inventory panel.


2) In the table, select a workspace, and then select the Security detail window.

Security

81

Manage User Groups at the Project Level

Add a Project User Group

You can create user groups at the project level to give a group of users the same access and privileges to a specific project. Project-level user groups will not have access to other projects in the workspace unless they belong to other user groups for those projects. Users can belong to multiple user groups, and multiple user groups can be assigned to a project. Project-level user groups will not be inherited by other objects.

User groups created in a parent workspace will also appear in the project user group list. You can add users at the project level to these inherited user groups.

To add a project user group:

1) In the object selector, select a project.

2) In the sidebar, hover over Project Team, and select User Groups.


4) In the Add User Group dialog box:

a. In the Name field, enter a unique name for the group.

b. In the Description field, enter a description of the user group.

c. In the Permission Sets section, select a Permission Set for each Permission Type, and then select Next.

d. In the Assign Users step, configure the View By settings and enter Search terms to locate users to add to the group.

e. Select one or more users, and then select Next.

5) Select Add.

Tips

To show the list of users assigned to a user group at the workspace level, select an inherited user group, and then select Show Workspace Users.

To remove a user from a group, select the Context menu next to a user, and then select Remove. Inherited users can only be removed from the user group in the workspace they were added.




82

Enable a User Group at the Project Level

You can enable user groups to work on projects. This also means that the user group will be assigned to the project. Enabling a workspace or project user group requires the selection of a project permission set, thereby granting the user group access to the current project. After you enable a user group to work on the project, you can select or edit all permissions that are applicable at the project level. When a project user group is created, it is automatically enabled.

To enable a user group to work on a project:


2) In the sidebar, hover over Project Team, and select User Groups.

3) In the User Group section, select Enabled next to a user group.

4) (Optional) Select Show Workspace Users to show users assigned to the user group at the workspace level.

5) (Optional) In the Permission Sets section, modify any available permission sets.

Note: All enabled user groups must have an assigned project permission set.

6) Select Save.

Tips

Use the Security page to manage user group access and assignment to the project. User groups assigned to the project on the Security page are automatically enabled on the User Groups page.

Assign a User or User Group Access to a Project

Users can be assigned to projects individually or through user groups. To access a project, each user or user group must be assigned a project permission set. A user or user group may have been configured with a default permission set. This permission set can be changed for the project assignment at any time.

To assign user access to a project:


2) In the sidebar, hover over Project Team, and select Security.

3) Select the Assign menu, and then select User or Group.

4) In the Assign User or Assign Group dialog box, enter the user or group name.

5) Select the name, and select Next.

6) In each Permission Set column, select a permission set for each permission type.

Note: If you assigned a user or user group that is configured with a default permission set, you can keep the default or select another if necessary.

7) Add any other optional permission sets applicable to that user or group.

8) Select Assign.

9) Select Save.

Companies and Users

83

You can also do this in the Projects inventory panel.

1) In Primavera Cloud:

In the object selector, select Projects, and then select View All Projects.


a. On the File menu, select Open.

b. In the Open dialog box, select the Projects or Programs tab, select a project or program, and then select Open.

c. On the Workspace menu, select Projects.

2) In the table, select a project, and then select the Security detail window.

Tips

If you added the project in the application, you are automatically assigned access to the project with the Administrator permission set assigned.


Companies and Users

Add companies and users that need access to Primavera Cloud.

All users must belong to a company and at least one office when added to the application. You can add users directly to the company on the Company Details page or to any company on the Users page. User details and user access can also be edited from either page.

You can download the import template and import companies and users to the application from the Companies or Users page.

Companies Overview

Multiple companies can work together using the same Primavera Cloud environment. For example, if the owning company hires a design firm and a subcontractor to work on the same project, the owning company can add both of the other companies as partner companies. The owning company can also add users to the partner companies and give them access to workspaces, projects, portfolios, programs, and ideas. Application administrators and users with any Companies global privileges are able to manage companies in the application.

Companies are categorized into groups such as vendors, resellers, owners, design consultants, architects, engineers, subcontractors, suppliers, and more. Users are added to companies, making information more manageable. Users working at partner companies can be assigned as a restricted user to give them limited access to your Primavera Cloud environment.

Two types of companies can exist in the application:


84

Owning company: An owning company has been created for you. A single owning company is required. You cannot change the status of an owning company to inactive, and it is not possible to delete an owning company.

Partner companies: A partner company is a separate entity from the owning company that needs to access your application. Examples of partner companies include vendors, resellers, subcontractors, owners, suppliers, and other consultants. Partner companies are listed under the owning company on the Companies page in the Global Admin settings. Users can be added to a partner company and assigned restricted access which will only allow them to see projects, portfolios, and programs assigned to their company in specific apps.

Add an App Preset

You can create app presets to customize which apps are available to your company, companies you partner with, and individual users. For example, if you are partnering with a company that should not have access to your budget information, you can create an app preset that hides the Cost and Funds app. Create as many app presets as necessary to meet the needs of your organization. Choose a default preset and create custom presets as needed. A custom preset, called All New Users, has already been created.

To add an app preset:



3) On the Companies page, select the Actions menu, and then select Manage App Presets.

Note: This can also be done from the Users page.

4) In the Manage App Presets dialog box, select Add.

5) In the Add preset field, enter a name for the app preset.

6) In the app list, select Make this app visible or Hide this app.

7) Select Save.

Tips

You can also manage app presets from the Users page.

Select Hide All or Show All to hide or show all apps in an app preset.

Select the Context menu, and select Use as Default to use that app preset as the default app preset when adding new users.

When new apps are available, you can edit your App Presets to include the new app for all or a select group of users.

Set Up a Company

Add the companies your organization works with manually or by importing spreadsheets with existing company data.

Choose one of the following methods to add companies:

Companies and Users

85

Manually Add Companies

Add a Company (on page 85)

Import Companies and Users

Download an Import Template for Importing Companies, Offices, and Users (on page 86)

Import Companies, Offices, and Users from Microsoft Excel (on page 86)

You can make corrections or updates to company data from the General page for a company:

Edit Company Details (on page 87)

Add an Office to a Company (on page 87)

Edit Office Details (on page 87)

Add a Company

Add the companies that work with your organization. After you add partner companies, you can add users to the companies.

To add a company:



3) On the Companies page, select Add.

4) In the Add Company dialog box, complete the following required fields:

a. On the General tab, complete the following fields:

Name: Enter the name of the company. If the company already exists in another Oracle Primavera Cloud instance, you can select it from the Import Existing Company list. You should not create a duplicate record for the same company.

(Optional) Complete other fields including Website, Status, Business Type, or Description.

b. Select the Corporate Office tab and complete the following fields:

Postal Code: Enter the postal code of the corporate office.

Country: Select the country of the corporate office.

Entering a Postal Code and Country will generate City and State / Province.

(Optional) Complete the other fields, including Street, Street 2, Phone, Fax, and Willing to Travel.

The Willing to Travel field specifies how far, in miles or kilometers, the company is willing to travel for work.

c. (Optional) Select the Other Information tab, and complete any other fields or assign a Performance Rating by selecting the highest star of the rating.

d. (Optional) Select the Configured Fields tab, and enter default values for any company specific fields.

5) Select Add.


86

Tips

You can also add inactive companies or change active companies to inactive.

Download an Import Template for Importing Companies, Offices, and Users

Download a Microsoft Excel template from the Companies or Users page to use when importing companies, offices, and users.

To download an import template:


2) In the sidebar, select Companies or Users.

3) On the Companies or Users page, select Actions, and then select Download Import Template.

Tips

The import template is downloaded as a Microsoft Excel file with the default file name CompanyImportTemplate.

The top two rows of the worksheet are required when importing companies from a worksheet. Do not change the data in these rows.

Application administrators and users with the necessary permissions can import companies and users using the import template. A user must have the Add Companies global privilege to import new companies. A user must have the User Administration global privilege to import users for a company. User administrators will not be able to import user information for a company that does not already exist or that the user is not associated with. Companies and users for the company can be created in the same Import Template, or the Import Template can be imported with only company details or user details added.

Review the Instructions worksheet for helpful tips on populating the import template.

Import Companies, Offices, and Users from Microsoft Excel

You can import new companies, offices, and users into the application from a Microsoft Excel (.xls or .xlsx) file.

Application administrators and users with the necessary permissions can import companies and users using the import template on the Companies or Users page. A user must have the Add Companies global privilege to import new companies. A user must have the User Administration global privilege to import users for a company. User administrators will not be able to import user information for a company that does not already exist or that the user is not associated with. Companies and users for the company can be created in the same Import Template, or the Import Template can be imported with only company details or user details added.

To import companies:



3) On the Companies or Users page, select the Actions menu, and then select Import from Excel.

Companies and Users

87

4) In the Import Companies and Users dialog box, select Browse, select a file, and then select Import.

Edit Company Details

You can edit details about a company, such as address and URL, if they change.

To edit company details:



3) On the Companies page, in the table, select a company.

4) In the company details section, select Edit.

5) In the Edit Company dialog box, make any changes on the General, Corporate Office, Other Information, or Configured Fields tabs.

6) Select Save.

Add an Office to a Company

After a company is created with a corporate office, you can add branch offices to the company. Users can be added to the corporate office or branch offices.

To add an office to a company:




4) In the Offices section, select Add.

5) In the Add Branch Office dialog box, on the General tab, complete the following fields:

Name: Enter the name of the office. If the office already exists in another Oracle Primavera Cloud instance, you can select it from the list that generates as you type. You should not create a duplicate record for the same company.

(Optional) Complete the Phone, Fax, or Willing to Travel fields. The Willing to Travelfield specifies how far, in miles or kilometers, the company is willing to travel for work.

6) Select the Address tab, and complete the following fields:

Postal Code: Enter the postal code of the branch office.

Country: Select the country of the branch office.

Entering a Postal Code and Country will generate City and State.

(Optional) Complete other fields including Street and Street 2.

7) Select Add.

Edit Office Details

You can edit details about an office, such as address and phone number, if they change.

To edit office details:



88



4) In the Offices section, select the Context menu for an office and then select Edit Office.

5) In the Edit Branch Office dialog box, make any changes on the General or Address tabs.

6) Select Save.

Note: The address and contact information for a Corporate Office must match the company. Therefore, if you select the Context menu and then select Edit Office for a company's Corporate Office, the Corporate Office tab on the Edit Company dialog box will open. From here, you can edit both the Corporate Office and the company at the same time.

Users Overview

You can add and manage all of your users from the Global Admin settings. There are four user types in the application: regular users, company restricted users, application administrators, and contacts. You can add users manually or by importing spreadsheets with user data. All users are stored in the same LDAP store in the owning company's group.

You can add the following types of users in the application:

Users: Users of the application whose access to data is determined by assigned permissions. Users are not restricted to view only the records of certain companies by default.

Company Restricted Users: Users from other companies may need access to your Primavera Cloud database. You can add users to the companies that your organization partners with as restricted users. When you add a user to a partner company, restricted user is selected by default. You can create restricted users in the owning company and partner companies. Restricted users cannot be added as application administrators and can only view records assigned to their company in specific apps. Restricted users can be given access to add users, but they can only add, edit, and delete users from their company.

Application Administrators: Application administrators are users with privileges to access all workspaces, projects, portfolios, programs, project collections, ideas, and global elements (such as workflows). Only application administrators can assign or remove the application administrator user type for a user. Only users created under the owning company can be assigned the application administrator user type. The Administrator permission set that can be set at the object level is a separate concept from the application administrator user type.

Contact Only: A user who receives Primavera Cloud email notifications but cannot log in to the application. A contact does not require a Primavera Cloud license.

For example, your company may have several projects that require work from an outside subcontractor. Employees of the subcontractor company will need access to the projects in your database. You can add the company as a partner company, and then add users to that company. You can add the employees of the subcontractor as company restricted users, giving them access only to the projects that their company is working on in specific apps. Your other data and projects remain protected and secure.

Companies and Users

89

You do not need to be an application administrator to create users if you have the User Administration global privilege. Users with the User Administration global privilege can add and manage users in their own company.

If you are managing users in IDCS, be aware that deleting a user in IDCS will prevent a user from logging into Primavera Cloud, even if the user is recreated with the same email address and user name. The unique key that matched the original user account to their Primavera Cloud login is erased upon deletion and cannot be recreated. Therefore, do not delete a user in IDCS unless they no longer need access to Primavera Cloud.

Add a User

Add users to assign access to the individuals your company works with. You can choose whether to assign application administrators, company restricted users, contacts, or general users.

All users added to the application must be associated with a company. Users can only be assigned to one company throughout Primavera Cloud. When you are adding a user to a company for the first time, add them to the correct company. A user may be invited to multiple instances of Primavera Cloud, but can only be associated to the same company. For example, if a user is assigned to Company A on an instance of Primavera Cloud, then they can only be added to Company A on any other instance that they are invited to.

To add a user:


2) In the sidebar, select Users.

Note: This can also be done from the General page for a company. To access the General page, select a company on the Companies page.

3) On the Users page, select Add.

4) In the Add User panel, complete the following steps:

Notes:

If Consent Notice is not enabled, application administrators can view all of the below steps in the Add User panel. User administrators can only view the User Details, User Groups, Apps, and Summary steps when adding a new user.

If Consent Notice is enabled, then only certain steps of the Add User panel will be available. For application administrators, the User Details, Defaults, Apps, and Summary steps will be available. For user administrators, only the User Details, Apps, and Summary steps will be available.

In the User Details step, complete the Basic and Permissions sections.

1. In the Basic section, complete the following fields:

a. Company: Enter the company that the user is being added to.


90

Note: If the user is being added to a company from the General page for a company, then this field will be autopopulated with that company and can't be edited.

b. Office: Select one or more offices for the user.

Note: If the user is being added to a company from the General page for a company, then this field will be autopopulated with the office selected on the page. You can also add additional offices for the user.

c. Email: Enter the email address for the user.

Notes:

The email address will be the username required for logging into the application. If the email address already exists in the system, a Use This button will appear.

If a user is added to an instance of Oracle Primavera Cloud hosted in the Oracle Cloud Infrastructure, select the Non-Federated User option when adding a new user who does not exist in your company's identity provider.

d. First Name: Enter the first name of the user.

e. Last Name: Enter the last name of the user.

f. Language: Enter the user's language.

g. (Optional) Complete additional fields.

2. In the Permissions section, complete the following fields:

a. (Optional) Copy Security Settings from Existing User: Application administrators can choose to copy the security settings from an existing user, which will copy their user groups, permission set defaults, user access, and apps. This will populate the User Groups, Defaults, Access, and Apps steps on this Add User panel, though you can then modify the choices on those steps to personalize the options for the new user. If Consent Notice is enabled, the User Groups and Access will not be copied from another user.

b. User Type: Select a User Type for the user from the following options:

User: A user of the system whose access to data is determined by assigned permissions.

Company Restricted User: A user of the system who can only access records associated with the assigned company.

Application Administrator: A user of the system who can administer all components of the application. This option is only available for users created in the owning company.

Contact Only: A user of the system who receives Primavera Cloud email notifications but cannot log in to the application. A contact does not require a license.

a. License: Select which licenses to assign to the user.

b. Global Permission Set: Select a permission set for the user.

Companies and Users

91

In the User Groups step, assign the user to user groups. Users will gain access to the objects that the user group is assigned to.

In the Defaults step, determine the default permission sets that a user will have when being assigned to a new object. The default permission sets will populate the permission set fields when new user access is being assigned. However, the permission sets chosen for the user's access to the specific object can be modified when the access is being added.

In the Access step, assign the user direct access to individual projects, portfolios, workspaces, ideas, and programs. When you assign access to an object, you must also define the permission sets for that access. You can choose to keep the default permission sets or assign different permission sets. An access type of User indicates that the user was assigned directly to the object. An access type of Workspace indicates that the user has gained access to that object indirectly through the user's assignment to the workspace. The user was assigned to the owning workspace of the object with a permission set defined for that object that grants the user access.

In the Apps step, determine the apps that a user will be able to access from the sidebar.

In the Summary step, view a summary of all of the user information configured in the Add User panel. You can also edit your selections if necessary.

5) Select Finish.

Tips

Users will receive an email with instructions on how to set their password.

If you are adding users to a partner company, they will automatically have company restricted users selected by default. Deselect this option if you want to add the users as regular users.

Download an Import Template for Importing Companies, Offices, and Users

Download a Microsoft Excel template from the Companies or Users page to use when importing companies, offices, and users.




3) On the Companies or Users page, select Actions, and then select Download Import Template.

Tips

The import template is downloaded as a Microsoft Excel file with the default file name CompanyImportTemplate.

The top two rows of the worksheet are required when importing companies from a worksheet. Do not change the data in these rows.


92

Application administrators and users with the necessary permissions can import companies and users using the import template. A user must have the Add Companies global privilege to import new companies. A user must have the User Administration global privilege to import users for a company. User administrators will not be able to import user information for a company that does not already exist or that the user is not associated with. Companies and users for the company can be created in the same Import Template, or the Import Template can be imported with only company details or user details added.


Import Companies, Offices, and Users from Microsoft Excel

You can import new companies, offices, and users into the application from a Microsoft Excel (.xls or .xlsx) file.

Application administrators and users with the necessary permissions can import companies and users using the import template on the Companies or Users page. A user must have the Add Companies global privilege to import new companies. A user must have the User Administration global privilege to import users for a company. User administrators will not be able to import user information for a company that does not already exist or that the user is not associated with. Companies and users for the company can be created in the same Import Template, or the Import Template can be imported with only company details or user details added.

To import companies:



3) On the Companies or Users page, select the Actions menu, and then select Import from Excel.

4) In the Import Companies and Users dialog box, select Browse, select a file, and then select Import.

Add an App Preset

You can create app presets to customize which apps are available to your company, companies you partner with, and individual users. For example, if you are partnering with a company that should not have access to your budget information, you can create an app preset that hides the Cost and Funds app. Create as many app presets as necessary to meet the needs of your organization. Choose a default preset and create custom presets as needed. A custom preset, called All New Users, has already been created.

To add an app preset:



3) On the Companies page, select the Actions menu, and then select Manage App Presets.

Companies and Users

93

Note: This can also be done from the Users page.

4) In the Manage App Presets dialog box, select Add.

5) In the Add preset field, enter a name for the app preset.

6) In the app list, select Make this app visible or Hide this app.

7) Select Save.

Tips

You can also manage app presets from the Users page.

Select Hide All or Show All to hide or show all apps in an app preset.

Select the Context menu, and select Use as Default to use that app preset as the default app preset when adding new users.

When new apps are available, you can edit your App Presets to include the new app for all or a select group of users.

Assign a User to a User Group on the Users Page

You can assign a user to a user group on the Users page. Users that are added to a user group will gain access to the objects that the user group is assigned to. The level of access will be determined by the permission sets configured for the user group.

You must be an application administrator or have the User Administration global privilege to be able to assign a user to a user group on the Users page. However, if you have the User Administration privilege, then you will only be able to see contexts that you have access to in the Context picker - contexts that you do not have access to will appear as Restricted.

To assign a user to a user group from the Users page:



3) In the table, select a user row to open the User Details panel.

4) In the User Details panel, in the User Groups section, select Assign.

5) In the Assign User Groups dialog box, in the Context picker, select a context.

The context is the workspace or project where the user will be assigned to the user group.

6) Select one or more user groups from the Available list, and then select Move Right to move them to the Selected list.

7) Select Save.


Tips

In the User Groups section of the User Details panel, the Owning Workspace is the owning workspace of the user group. The Assigned At field is the workspace where the user was assigned to the user group.


94

Edit User Details

From the Edit User Details panel, you can edit the general information for a user, such as name and language, as well as user permissions such as user type, licenses, and global permission sets. You can also configure Field app settings for the user or set the user as inactive.

To edit user details from the Edit User Details panel:




3) On the Users page, select the Context menu for a user row, and then select Edit User Details.

4) On the Edit User Details panel, edit user details.

5) Select Save.

Manage Access

Manage the objects that a user has access to from the Manage Access panel.



Manage Access Panel Overview

User access determines what objects a user has access to and to what extent. The Manage Access panel provides you with one location to manage direct user access and workspace user access to projects, portfolios, workspaces, ideas, and programs. In this panel, you can add user access to an object and also edit the permission sets for a user access. You must be an application administrator in order to access the Manage Access panel.

Understanding Access Type

The Manage Access panel provides a central location to view assignments for a user with either of two access types: User or Workspace. You can use the quick filter options to filter the Manage Access panel by a specific access type.

If an assignment has an access type of User, the user gained access to the object by being assigned to it directly.

Companies and Users

95

If an assignment has an access type of Workspace, then the user gained access to the object indirectly through the user's assignment to the object's owning workspace. When the user was assigned to the owning workspace, a permission set for the object (project, portfolio, workspace, idea, or program) was defined, which gave the user access to all instances of that object in the workspace and all child workspaces. The owning workspace is the workspace that the object exists in.

For example, if a user is assigned to Workspace A with a Portfolios permission set defined, then the user will then gain access to all portfolios in the workspace that already exist or are added later. The portfolios will appear on the Portfolios tab of the Manage Access panel with an access type of Workspace and an owning workspace of Workspace A. The level of access that the user has to the portfolios will depend on the privileges in the Portfolios permission set.

Note: If a user has gained access to a project, portfolio, idea, or program through both a user access and a workspace assignment, the Access Type on the Manage Access panel will say User.

Assign User Access

You can assign a user access to all projects, portfolios, workspaces, ideas, and programs from the Manage Access panel. When a user is assigned access to an object, the permission sets chosen will determine what privileges a user has for that object. Users will gain access to the object as soon as the assignment is added. You must be an application administrator to access the Manage Access panel.

When you add access to an object from the Manage Access panel, the access type will be User.

To assign user access:




3) On the Users page, select the Context menu for a user row, and then select Manage Access.

4) In the Manage Access panel, select the Projects, Portfolios, Workspaces, Ideas, or Programs tab.

5) On the tab, select Assign.

6) In the Assign dialog box, select an object from the Available list and then select Move Right to move it to the Selected list.

7) Select Next.

8) In a Permission Set column for each Permission Type, select a permission set.

Some permission sets may be required in order to assign the access.

9) Select Assign.

Note: If a user has gained access to a project, portfolio, idea, or program


96

through both a user access and a workspace assignment, the Access Type on the Manage Access panel will say User.

Manage a User's Default Permission Sets

You can manage a user's default permission sets from the Users page. A user's default permission sets are the permission sets that a user will have when assigned to a new object. However, the permission sets can be changed when the access is being added.

To manage a user's default permission sets:




3) On the Users page, select the Context menu for a user row, and then select Manage Defaults.

4) In the Manage Defaults dialog box, for each Permission Type, select the default permission set you want a user to have when assigned to a new object.

5) Select Save.

Manage a User's Apps

A user's apps are the apps that are available to them from the sidebar when they are using the application. When you manage a user's apps, you can either choose an existing app preset for the user, or customize the apps available for the user.

To manage a user's apps:




3) On the Users page, select the Context menu for a user row, and then select Manage Apps.

4) In the Manage Apps dialog box, do one of the following:

In the Presets list, select an existing app preset to assign that app preset to the user.

In the app list, select Make this app visible or Hide this app to customize the user's apps.

Select an app preset and then customize the user's apps based on the presets.

5) Select Save.

Companies and Users

97

View User Summary

Open the User Summary panel to view information about a user in a printer-friendly format. The user summary panel is view only and includes the user details, user groups, access, default permission sets, and apps for the user.

To view the user summary:




3) On the Users page, select the Context menu for a user row, and then select View User Summary.

4) (Optional) Select the Print icon to print the user summary.

5) Select Close when you are done viewing the user summary.

Add and Associate a Resource with an Existing User

You can add and associate a new resource with an existing user. An associated resource is required for users updating their timesheets to record progress on activities.

To add and associate a resource with an existing user:




3) In the table, select a user row, select the Context menu, and then select Add Resource.

Note: The Add Resource option for the user is disabled if a resource is already associated with the user.

4) In the Add Resource dialog box, complete the following fields:

Resource ID: Enter a unique ID for the new resource.

(Optional) Select Timesheet Approver: If timesheets are going to be submitted, select a timesheet approver for the resource.

Select Workspace: Select the owning workspace for the new resource. This should be the workspace where the projects that the resource will be assigned to will reside. The resource will be available to all child workspaces in the workspace selected.

In the table, select an existing resource that you will add the new resource to as a sibling or child.


98

Add resource as: Select whether to add the resource as a sibling or child of the selected resource in the workspace resource hierarchy.

5) Select Add.

Associate a Resource with a User

When a user of the application is also a resource in the application, you can associate the resource with the user's account. An associated resource is required for users updating their timesheets to record progress on activities.

To associate a resource with a user:




3) In the table, select a user row, and select the Associated Resource column.

Note: If the Associated Resource column is not available on the grid, you can add it from the Settings panel.

4) In the Select Resource dialog box:

In the Associate a field, select Workspace Resource or Project Resource to associate the user with a workspace resource or a project resource.

In the Select Workspace or Select Project field, select a workspace containing the existing resource to be associated.

In the table, select a resource. You can also search for a resource in the Search field.

5) Select Select.

Tips

To remove an associated resource, select Remove in the Select Resource dialog box.

Assign Inspection Managers and Reports

If your organization is using the Field app, you can assign active users as inspection managers or select if they report to an inspection manager. Users who are designated as an inspection manager will appear as an option for the Reports to Inspection Manager field. Inspection managers have access to view information such as issues, inspections, and the schedule calendar.

To assign an inspection manager or report:



Note: This can also be done from the General page for a company. To

Companies and Users

99

access the General page, select a company on the Companies page.

3) In the table, select a user row, and select the Inspection Manager column.

Note: If the Inspection Manager column is not available in the grid, you can add it from the Settings panel.

4) In the Reports to Inspection Manager column, select a user, and select OK.

Note: Inspection managers can report to other inspection managers.

5) Select Save.

Tips

You can also assign inspection managers and reports from the Edit User Details panel.

Set Up a User to Receive Dispatch Reports by Email

If your organization is using the Field app, you can designate users to receive dispatch reports through email. These users are included as a contact in dispatch reports sent to the company.

To set up a user to receive dispatch reports through email:




3) In the table, select a user row, and then select Receive Dispatch Reports by Email.

Note: If the Receive Dispatch Reports by Email column is not available on the grid, you can add it from the Settings panel.

4) Select Save.

Tips

You can also set up a user to receive dispatch reports through email from the Edit User Details panel.

Reset a User Password

You can send a password reset email to an active user. The user will receive an email with instructions on how to reset the password.

To reset a password of a user:




100


3) In the table, select a user row, select the Context menu, and then select Reset User Password.

4) In the Confirm dialog box, select Yes.

An email is sent to the user with instructions on how to set up a new password.

Note: The Reset User Password option is not available if a user is set to use identity federation in an instance of Primavera Cloud hosted in the Oracle Cloud Infrastructure.

Set a User as Inactive

When a user no longer needs access to your company's instance of Oracle Primavera Cloud, you can change the status of the user to inactive. Deactivating a user removes the license and prevents the user from logging into your company's environment. If the user needs access again in the future, you can change the status back to active.

Users cannot be deleted from the Primavera Cloud application to protect historical data. If you are managing users in IDCS, be aware that deleting a user in IDCS will prevent a user from logging into Primavera Cloud, even if the user is recreated with the same email address and user name. The unique key that matched the original user account to their Primavera Cloud login is erased upon deletion and cannot be recreated. Therefore, do not delete a user in IDCS unless they no longer need access to Primavera Cloud.

To set a user as inactive:




3) In the table, select a user row, select the Context menu, and then select Deactivate User.

Note: The user will only be inactive in this company's instance of Primavera Cloud. Any other instances that the user has access to will not be changed.

4) Select Save.

Tips

To set a user as active, select a user row, select the Context menu, and then selectActivate User. When you set a user as active, licenses need to be associated with the user.

Companies and Users

101

User Profiles Overview

A user profile provides a complete picture of a user’s access to projects and portfolios as well as license assignment and security assignments. A profile also provides access to personal data, such as username, company, phone number, and email address. Personal data is stored outside the application in an LDAP server.

You can assign licenses directly from the User Profiles page. User groups and permission sets are created in the Permissions section, while security assignments for workspaces, projects, portfolios, files, and reports are assigned directly to those objects.

View a User Profile

View user profiles to see contact information, license assignments, and general assignments for a user. Only application administrators can view the profiles of other users.

To view a user profile:


2) In the sidebar, select User Profiles.

3) On the User Profiles page, select Select User.

4) In the Select User dialog box:

a. Enter part or all of the username or personal name into the Search field.

b. Select a user, and then select Select.

5) On the User Profiles page, you can view the following information about a user:

High Level Profile: The user's avatar and all available information about the user. Information about the user's name, phone number, and email is drawn from the LDAP store.

General Assignments: The assigned global permission sets and user groups.

Licenses: The licenses assigned to the user. You can also assign or remove a license to the user here.

Portfolios tab: The user's portfolio assignments.

Name: The name of the portfolio.

Permission: The name of the portfolio permission set assigned to the user for viewing the portfolio.

Assigned: The way that the user was assigned to the portfolio, either as part of a group or as an individual user.

Projects tab: The user's project assignments, corresponding Project permission set assignments and whether assignments are made to a user or group.

View Workspace Path: Launches the project's workspace path dialog box to display the hierarchy of workspaces for the selected project.

ID: The project ID.

Name: The project name.

Permission: The name of the permission set assigned to the user for viewing the project.


102

Assigned: The way that the user was assigned to the project, either as part of a group or as an individual user.

Assign a License to an Individual User through Profiles

Assign licenses to users so that they can work in the application.

To assign a license to a user:


2) In the sidebar, select User Profiles.

3) On the User Profiles page, select Select User.

4) In the Select User dialog box, enter the username.

5) Select the name, and then select Select.

6) In the Licenses section of the User Profiles page, select the licenses.

7) Select Save.

Tips

You can remove a license from a user by deselecting the license.

Proxy Users Overview

The proxy user feature permits you to act as another user in the application. You can complete tasks or assignments on behalf of another user, and another user can complete tasks or assignments on your behalf. For example, if you will be out of the office for two weeks of vacation, you can assign a co-worker or manager to act as your proxy in your absence if they have the same licenses as you. The user will have access to any projects and workspaces that you do. While other users are acting as proxy for you, each action they complete will be noted as Added On Behalf Of or Modified On Behalf Of to indicate that another user has completed the action on your behalf.

You must have the required security privileges to assign proxy users. Only application administrators can act as a proxy user for other application administrators.

Add a Proxy User

Assign a user to serve as a proxy for you if you will be away from work. The proxy user that you assign will be able to complete tasks on your behalf.

Note: The proxy user must have the same or more licenses as you to act as your proxy.

To add a proxy user:

1) In the header, select your username.

2) On the User menu, select Proxy Users, and then select Manage Proxy Users.

3) On the Manage Proxy Users page, select Assign.

Field App Configuration

103

4) In the Assign Users dialog box:

a. Enter part or all of a user's login name or personal name into the Search field.

b. Select a user, and then select Assign.

5) In the Start Date field, select a start date.

6) In the End Date field, select an end date.

7) Select Save.

Tips

Select Revoke to revoke an active user's ability to act as your proxy.

Select Delete to delete a pending user's ability to act as your proxy.

View Your Proxy Users

You can use the Manage Proxy Users page to manage the users you can act as a proxy for. This table includes active, pending, and expired proxies.

To view your proxy users:


2) On the User menu, select Proxy Users, and then select Manage Proxy Users.

3) On the Manage Proxy Users page, in the Proxy To section, view the list of users that you can act as a proxy for.

Act as a Proxy User

If you are assigned as a proxy user in the application, you can act as that user at any time during the proxy period to complete any work or tasks on behalf of a user. While acting as another user, you cannot change any user preferences. The only objects on the user menu that you will be able to access are the Background Services and Get Mobile Apps pages.

To act as another user:


2) On the User menu, select Proxy Users, and then select a username.

3) Select Yes to act as that user.

Tips

Select the User menu, and then select Logout of Proxy to end the proxy session.


Oracle Primavera Cloud enables your organization to define a series of parameters and values that apply to projects in the Field app. Use these settings to customize the application to meet specific requirements and standards.


104

Field Project Details Overview

You should complete most of the following tasks before you let your users use the app. You can vary the order in which you complete these processes depending on your organization's implementation plan.

Configure the Maximum File Size for a Field Mobile Upload

Synchronization settings control the maximum file size that users can upload using Primavera Field for iOS. The file size should be entered in MB.

To set up synchronization settings:



3) On the Summary & Settings menu, select Field Project Details.

4) On the Project Details tab, under the Synchronization Settings section, in the Maximum file size for upload on the tablet, MB field, enter a number.

5) Select Save Changes.



Field

Set the Project Dates for Field Reporting

Project dates in the Field app control the date range in which daily reports should be generated. Project dates in the Field app do not affect the planned start and planned finish dates on the Details page in Summary & Settings or in other Oracle Primavera Cloud apps.

To set up project dates:




4) Select the Projects Details tab, and under the Project Dates section, in the Start Date field, select the start date.

5) In the Estimated Completion Date field, select the estimated finish date.




Field


105

Add an Issue Custom Field

Project managers can configure a standard set of up to five custom data fields per issue type that are included by default on all issues created across all projects. Up to five application-wide custom issue fields can be configured for all projects in the application and each project can define up to five project-specific custom issue fields. Each custom issue field includes a label and data input field which can formatted as a check box, radio-button, drop-down list, or text input field. Issue custom fields can be set to be optional or required.

To add an issue custom field:




4) Select the Custom Fields tab, and then under the Issue Custom Fields section, in the Type field, select Punchlist, QA/QC, Commissioning, or Safety.

5) Select Add.

6) In the Issue Custom Field Details section, complete the following fields:

a. Label: Enter the label of the field.

b. Required: Select Required if the field will be a required field.

c. Data type: Select the data type of the field. Valid entries include check box, radio button, drop-down, and Text.

d. If you selected check box, radio button, or drop-down, complete the following steps:

1. (Optional) Select Default if the value should be the default answer. You can only select one default.

2. In the Value field, enter a response to the field.

3. Select Add New.

4. Add additional responses.

e. If you selected Text, in the Text field, enter a value.



Tips

To delete an issue custom field, select the custom field, and then select Delete.


Field

Add an Area or Item Custom Field

Project managers can define labels for up to five custom fields for areas and items.

To add an area or item custom fields:




106


4) Select the Area/Item Custom Fields tab, and enter custom field labels in the Area Profile Custom Field Labels and Item Custom Field Labels section.




Field

Set Up a Work Order Cover

You can set up a work order cover to use for all work orders in the project.

To set up a work order cover:




4) Select the Work Order Cover tab, and complete the following fields:

Title area: Enter text to appear in the header section of the document.

Company name area: Enter the name of the company.

Address area: Enter the address of your company. You may also want to enter phone or fax.

Main area: Enter the default text that should appear on the work order cover.

Signature area: Enter a signature.



Tips

Select Reset to default to restore the default entries.

You can view a preview of your work order cover in the Work Order Cover Preview section.

You can use tags in the work order cover that will render the details for each company and project. Choose from:

Prj. email: Email address set up for the project

Prj. contact: User set up as the project contact

Originator name: Name of the user who creates the report

Prj. Phone: Phone number set up for the project contact

Prj. address: Street address set up for the project

Prj. fax: Fax number set up for the project

Contact Name: Contact set up for the project


Field


107

Add a Commissioning Step

The project manager can set up custom commissioning steps. These steps will be used on the Commissioning page to track the progress for each applicable item. For example, a commissioning step may be created for final performance testing. Commissioning steps streamline the process, allowing any project manager to see the current status of their project broken out in steps. If any steps are dependent on another step, that step cannot be completed or started until the previous step is complete, enforcing that rules and standards are followed.

To set up commissioning steps:




4) Select the Commissioning Steps tab, and then select Add New Step.

5) In the Commissioning Steps Settings dialog box, complete the following fields:

Name: Enter the name of the step.

No Form Required: Select if no form is required in this step. If a form is required, you must upload a PDF form.

Color: Select the color bar to display the color picker. Select again to choose a color.

Order: Select the order of the step. For example, if you already created 4 steps, but you want the new step to be the second step in the series, select 2.

Select Save.

6) Add steps until your commissioning process is captured.

7) (Optional) in the commissioning step row, select Set up, and do any of the following:

Select Start Criteria, and select the check box next to any steps that must be completed before the step can be started.

Select Completion Criteria, and select the check box next to any steps that must be closed before the step can be completed.

Select User Permission, and select which users or permission sets can save steps, complete steps, and receive notifications when steps are completed.



Tips

Select Set up to enter start and completion criteria that are applicable to the step.

Names of commissioning steps should be short, especially if there are a lot of commissioning steps in the project.


Field


108

Set Up Revisions Tracking

Project managers can customize the application to avoid tracking revisions on large files to avoid syncing large files.

To set up revisions tracking:




4) Select the Library tab.

5) Under the Revisions Tracking section, in the Do not track revisions if file size is above MB field, enter the maximum file size in MB.

Note: The PDF Hyperlinking Detection Enabled feature is not available for this release.




Field

Field Setup Overview

You should complete most of the following tasks before you let your users use the app. You can vary the order in which you complete these processes depending on your organization's implementation plan.

Configure the Field Setup Project Data

Project managers and application administrators can configure project-level data for web and mobile users.

To set up your project for the Field app:

1) Define Non-Working Days and Holidays (on page 108)

2) Add an Inspection Template (on page 109)

3) Add a Dispatch Rule (on page 113)

Define Non-Working Days and Holidays

Project managers can define the non-working days of the jobsite. For example, if the jobsite is never open on Sunday, you can add Sunday as a non-working day. If Sunday is a non-working day, there will never be a daily report generated on a Sunday.

You can also define holidays and other custom, non-working days. These days will also never have a daily report generated on that day. You cannot create repeating dates. If the date repeats annually, you must create a separate entry for each year.


109

To define non-working days and holidays for a project:



3) On the Summary & Settings menu, select Field Setup.

4) Select the Projects tab, and then under the Projects and Project-related Data section, select Working days.

5) Under the Define Weekly Non-working Days section, select the days that no work is completed onsite.

6) Under the Define Holidays and other Non-working Days section, complete the following fields:

a. In the Date field, enter a date.

b. In the Name field, enter a name or short description of the holiday or non-working day.

c. Select Add Date.



Field

Inspection Templates Overview

All inspections require an inspection template to capture and track information about the inspection and issues created during the inspection. Inspection templates define information about an inspection, including the threshold, duration, state, data type, and template type. An inspection template consists of the inspection questions, a format for the responses to the questions, predefined response values, and specifies if the question can be used to create issues.

The Template Type data field specifies one of two methods for conducting an inspection:

Form: Based on a predefined set of inspection questions on a form from which issues can be created.

Issues List (Punchlist): Allows issues to be created.

In both types of inspection methods, issues can be created in the application and assigned to a responsible party. Generally, inspections conducted for quality, commissioning or safety use Form inspection templates, while punchlist use Issue List inspection templates. As many inspection templates as necessary can be created to facilitate a smoother workflow.

Add an Inspection Template

You can create electronic inspection templates for inspectors and field workers to use on the jobsite.

To add an inspection template:





110

4) Select the Projects tab, and then under the Templates section, select Issue and Inspection Templates.

5) Select Add New Template.

6) On the Template Details tab, complete the following fields:

a. Type: Select the type of inspection to be completed. Valid options include Punchlist, QA/QC, Commissioning, and Safety.

b. Template Type: Select Form or Issues List (Punchlist) depending on what type of inspection to be completed.

c. Template Name: Enter a unique name for the template.

d. Threshold (days): Enter the number of days for an issue to remain open and be corrected after which the application sends a second work order to the company assigned to the issue.

e. Duration (hours): Enter an estimate of how many hours it will take to complete the inspection.

f. (Optional) Instructions: Enter any additional instructions or notes for the inspector.




Field

Archive an Inspection Template

You can archive inspection templates that are no longer used.

To archive an inspection template:





5) In the table, select a template name.

6) Select Archive, and then select OK.


Field

Import a Form for an Inspection Template

You can import forms for inspectors to use during inspections.

To import a form for an inspection template:





111


5) In the table, select a template name, and then select the Form Setup tab.

6) Select Select from Files, and in the Oracle Primavera Cloud Field Cloud Management Files dialog box, choose a file.


Tips

In the Form Preview section, view the preview of the form.

You can customize the form after it is imported to avoid reimporting the same form.


Field

Edit the Form Setup for an Inspection Template

You can edit the form fields list of inspection template forms after the fields are in the application using the optical recognition power of the application. Revise or change fields without having to correct and upload a PDF multiple times.

To edit the form setup of an inspection template:





5) In the table, select a template name, and then select the Form Setup tab.

6) In the field row, select Edit.

7) In the Label field, enter a new label.

8) (Optional) Select Issues? if this field is part of an issues list.

9) (Optional) Drag and drop fields to rearrange their order.

10) Select Save.


Tips

In the Form Preview section, select the name of the PDF to download the inspection template.


Field


112

Link an Inspection Template

You can link other inspection templates to your current inspection template. For example, one of your inspectors may perform multiple inspections that require different inspection templates. You can link the inspections so that as inspectors complete one inspection, they can start the next inspection in a determined amount of time. If the inspections should be completed at the same time, you can schedule the newer inspection to occur on the same date at the same or a different time.

To link inspection templates:





5) In the table, select a template name, and then select the Workflow tab.

6) In the Linked Inspections section, select Link Inspection, and complete the following fields:

a. New Inspection Template: Select an inspection template to link to the current inspection.

b. Inspector: Select the user who will complete the inspection. You can also select the same inspector as the original inspection or the manager of the original inspector.

c. Scheduled date: Select the same day as the original inspection was completed and approved or enter an amount of Days, Weeks, Months from the date that the original inspection was completed and approved.

d. Scheduled time: Select the same time as the original inspection or in the specific time list, select a time.



Tips

In the Form Preview section, select the name of the PDF to download the inspection template.


Field

Set Up an Issues Workflow for Inspection Templates

You can set up an issues workflow that uses start on and finish by dates to schedule work for the responsible party.

To set up an issues workflow:





113


5) In the table, select a template name, and then select the Workflow tab.

6) In the Issues Workflow section, choose from the following options:

Responsible party assignment required: Select to require a subcontractor be assigned to all new issues.

Start on/Finish by: Select to indicate that the Start on and Finish by fields on an issue are automatically populated with the current date as the start date and the finish date will be calculated based on the number of days specified as the threshold for this inspection template.

Display Items: Select to display only the items linked to areas.



Tips

Different template types have different issues workflow configurations. For example, you can make item assignment and standard issue assignment required for all safety inspection templates.


Field

Add a Dispatch Rule

The application generates and sends work orders (also known as issue reports) automatically based on a set of rules, defined by the administrator for all projects, or by the project manager for each project. Rules are specific for each type of issue or inspection object. A rule is created for:

All projects and all inspection templates

Selected projects and selected inspection templates

All projects and selected inspection templates

Selected projects and all inspection templates

There is no limit to the number of rules that can be defined. However, all rules apply unless they are deactivated, and multiple rules may create work orders (issue reports) for the same company with the same set of issues.

Rules can be scheduled to periodically run or event based and run when a specified system event occurs. Each rule can be activated and deactivated, but only active rules apply. The project manager can view when a recurring rule will next apply.

To define a dispatch report rule for a project:





114

4) Select the Projects tab, and then under the Dispatching section, select Report Dispatching Rules Setup.

5) Select Add New Rule.

6) In the General section, complete the following fields:

Rule Name: Enter a unique name for the rule.

Type: Select Punchlist, QA/QC, Commissioning, or Safety.

Project: Select the project the rule applies to or select All projects with common statuses.

Template: Select one or all templates.

Report separation: Select how the issues report should be organized and distributed.

Status: Select Active or Inactive.

Note: Read the Rule Explanation if you need more information on rules.

7) In the Dispatching section, complete the following fields:

Notification: Select Create and Notify to create the rule and notify stakeholders, or select Just Create to create the rule.

Report creation type: Select how the report should be created.

Event-based (Issue was modified): Run the report on-demand.

Recurring (periodical): Schedule the report to run.

8) Select Additional Persons to Notify, and select the check box next to the usernames of users to notify.

9) Select Next.

10) In the Details section, complete the following:

Report formatting template (XSL): Select Default, Project-specific, or Rule-specific.

Cover letter and content: Select which cover letter and content to use. Valid options include Default (for entire application), Project-specific, or Rule-specific.

Report originator (if used on template): Select the user who should be shown as the report originator.

Notification from address: Select Static to use the default application email. Select Dynamic to use the email of the originator.

11) Select Next.

12) Select Save This New Rule or Save and setup WO Cover.



Field

Set Up Field Setup Application Data

Project managers and application administrators can configure application-level data for web and mobile users.

To set up and monitor your project:


115

Add an Issue Category/Status (on page 115)

Monitor and Release a Tablet (on page 116)

View the Data Modification Audit (on page 116)

View a log of user activity.

Edit Email Content (on page 117)

Customize the template for a variety of emails.

Configure the Email Queue (on page 117)

Monitor the Email Queue (on page 118)

Send Emails from the Email Queue (on page 118)

Add an Issue Category/Status

Project managers can create issue categories to group issues and issue statuses to show the state of the issues.

To add an issue category:




4) Select the Application tab, and then under the Inspections/Issues section, select Issue Category/Status.

5) In the Type list, select a category type. Valid options include Punchlist, QA/QC, Commissioning, and Safety.

6) Select Add New Category.

7) In the Category details section, complete the following fields:

a. Category: Enter a name for the category.

b. Abbreviation: Enter an abbreviation for the category.

c. Apply to inspection templates: Select one of the following:

None: Select if the category should not be applied to inspection templates.

Selectively: Select if the category should be enabled on inspection templates as they are set up.

All: Select if the category should apply to all inspection templates.


9) (Optional) Under the Category Statuses section, select Add New Status.

10) Complete the following fields:

a. Status name: Enter a name for the status.

b. Action Name: Enter a label for the button for the action that can be executed for the status. For example, you might enter Done so that a user can indicate issues with work that is complete.

c. State: Select open if the issue is unresolved. Select closed if the issue is resolved.




116


Field

Monitor and Release a Tablet

Each tablet used to access Primavera Field for iOS is assigned a unique host number during the first sync. If a field device is lost or needs to be removed from the application, you can release the device’s host number so it is available for another device assignment.

To monitor and release a table:




4) Select the Application tab, and then under the Security settings section, select Control and Release Tablets.

5) (Optional) To release a tablet, in the tablet row, select Release, and then select OK.



Field

View the Data Modification Audit

Application administrators can view the data modification audit to review the activity of all users in the Field app and Primavera Field for iOS.

To view the data modification audit:




4) Select the Application tab, and then under the Security settings section, select Data Modification Audit.



Field

Email Content Manager Overview

The email content manager enables you to customize email templates for a variety of different email types. You can use tags which function as variables in the emails to render items like the project name, server URL, links to reports, area IDs, last sent dates, and more.

You can create emails for a variety of situations including:

Vendor Without email: Notifies the user that a vendor profile does not have the appropriate contact information for vendors being sent work orders.


117

Daily report notification: Notifies a user that the company's daily report has not been submitted.

Area Inspection Completion email: Sent to selected users upon inspection completion. The inspection completion PDF is attached to this e-mail.

Inspection Approval Task email: Notifies a user required to approve an inspection.

Inspection Rejected email: Notifies the inspector for an inspection requiring approval that the inspection was rejected.

Inspection Create email: Notifies an inspector that an inspection was created.

Work Order email: Sends vendors work orders as PDF attachments.

Edit Email Content

You can edit the system generated email content of email templates to meet the needs of your organization.

To edit an email template:




4) Select the Application tab, and then under the Email related section, select Email Content Manager.

5) In the Email type list, select the type of email template.

6) Under the Mail setup section, complete the following fields:

a. From address: Enter the email address the email should come from.

b. Subject: Enter a subject line for the email or notification.

c. Body: Enter the text you want the email or notification to say. In the Tags section, select any variables to be used in the template.




Field

Configure the Email Queue

You can customize which emails you want to take action on before they are sent. You can intercept all emails or just those that have a send error.

To monitor the email queue:




4) Select the Application tab, and then under the Email related section, select Email Queue.

5) Under the Queue Administrative Controls section, in the Which emails do you want to intercept and queue for action field, select Only emails with errors or All emails.


118

6) Select Save mode.



Field

Monitor the Email Queue

The email queue enables you to determine which items will be sent. You can select to send all items in the email queue, or you can send or delete specific emails. The email queue lists outgoing emails and faxes awaiting approval for sending. Filter the email queue items by date, recipient's e-mail or fax, and description to manage emails.

To monitor the email queue:





5) Under the Filter section, choose from the following options:

In the Select message status list, choose from pending, sent, not sent, or sending emails.

In the Select message type list, choose the type of message.

6) Select Filter.



Field

Send Emails from the Email Queue

You can send any emails on demand from the email queue.

To send emails from the email queue:





5) Under the Filter section, do one of the following:

Select the check box by the email and select Send selected emails. Select OK.

Select Send All to send all emails in the queue. Select OK.



Field


119

Areas Overview

Project managers can define areas for a project to define information about areas that are used multiple times throughout a project. Areas refer to specific segments of a physical project. Subareas can be defined for each area. Information defined for areas includes name number, project, type, street address, status (active or not active), and area owner. For example, a condominium project can have an area defined for a one-bedroom condo and define locations for the subareas of living room, kitchen, bedroom, and bathroom.

In addition to these fields, up to five custom fields can be set up. Areas can be displayed in a hierarchal structure or area tree.

Add an Area

Project managers can manually add areas and subareas for use in the Field app and Primavera Field for iOS.

To add an area:



3) On the Summary & Settings menu, select Field Setup, and then select the Areas tab.

4) Under the Add New Area section, select a Parent Area, and then enter an Area Name or ID.

5) Select Add New Area.



Field

Download an Import Template for Importing Areas

Download a Microsoft Excel template to use when importing areas.





4) Under the Import Areas From File section, select Sample CSV File.


Tips

The import template is downloaded as a Microsoft Excel file with the default file name, import_sample.csv.


Field


120

Import Areas

You can import new areas into the application from a Microsoft Excel (.xls or .xlsx) file.

To import areas:




4) Under the Import Areas From File section, select Browse, select a file, and then selectImport Areas.

5) View the import results, and select Go Back.



Field

Edit an Area

Project managers can edit an area, adding details or changing the status. If you change an area from active to inactive, all subareas will change to inactive.

To edit an area:




4) Under the Area section, in the table, in the area row, select Edit.

5) Complete any of the following applicable fields under the General section:

Area: Enter a new name for the area.

Status: Select Active, Inactive, or Complete. Inactive areas will not be shown.

Details Level: Select Simple or Extended. Select Extended if you want to edit Property address, Buyer / Owner Info, or Contact information.

ID/Tag: The filename of the bar code or QR code associated with the area.

6) Complete any of the following applicable fields under the Spatial Data section:

Description: Enter a brief description of the area.

Category: Enter a category name.

Net area: Enter the net area.

Gross area: Enter the gross area.

Usable height: Enter the height of the area that is usable.

7) Select Save.



Field


121

Add an Item to an Area

Project managers can add items to areas to indicate the quantity of items in an area.

To add an item to an area:




4) In the table, in an area row, select Edit, and then select the Items tab.

5) In the Inventory Item List panel, in the item row, select Add.

The item will appear in the Area Items panel.


Tips

To add a serial number to an item assigned to an area, select Edit.


Field

Delete an Area

You can delete unneeded areas from the application.

To delete an area:




4) In the table, in the area row, select Edit.

5) Select Delete, and then select OK.


Field

Item Masters Overview

An item master is a template hierarchical listing of equipment and materials that are used multiple times in a project. Specification information, such as part number or model, can be defined on the item master, in addition a list of standard issues can be associated with the item master, and commissioning steps and the associated forms can be setup. All this information will be inherited by any inventory item that is linked to this master item.

Note: Serial numbers cannot be defined as they refer to a specific item. The item master maintains information about items in general. The inventory feature can be used to maintain information about specific items.


122

Add an Item Master

You can manually add item masters to your project.

To add an item master:



3) On the Summary & Settings menu, select Field Setup, and then select the Item Masters tab.

4) Under the Add New Item Master section, in the Parent Item column, select a parent item.

5) In the Description field, enter a brief description or name for the item.

6) Select Add New.



Field

Download an Import Template for Importing Item Masters

Download a Microsoft Excel template to use when importing item masters.





4) Under the Import Item Master and Standard Issues from File section, select Download Sample Data.



Field

Import Item Masters

You can upload new item masters into the application from a Microsoft Excel (.xls or .xlsx) file or an XML file.

To import item masters:




4) Under the Import Item Master and Standard Issues from File section, select Browse, select a file, and then select Upload Item Master.


123

5) Select OK.



Field

Export an Existing Item Master

You can export existing item masters for use in other projects or applications.

To export existing item masters:




4) Under the Import Item Master and Standard Issues from File section, select check to include IDs into XML to include IDs.

5) Select Export Existing Item Masters, and then select OK.

6) Save or open the file.



Field

Add a File to an Item Master

You can add files to item masters.

To add a file to an item master:




4) In the table, in the item master row, select Edit.

5) Select the Files tab, and then select Select from Files.

6) Select a file.



Field


124

Define a Standard Issue for an Item Master

Project managers can define a set of standard issues associated with an item master that can be used during issue creation to prepopulate the issue description and responsible party. Standard issues are used extensively by some safety managers. This is can save time and create consistency during the punch list process. For instance, you can setup an item master for electrical items and then predefine all electrical standard issues.

To define a standard issue:




4) In the table, in the item master list row, select Edit, and then select the Standard Issuestab.

5) Under the Standard Issues for Item Master section, complete the following fields:

Standard Issue Description: Enter a short description or name for the standard issue.

(Optional) Code: Enter a code. Codes are used with the standard issue description as a means of identification.

(Optional) Specialty: This feature is not available for this release.

(Optional) Company: This feature is not available for this release.

6) Select Add New, and then select Save Changes or Save & Exit.



Field

Delete an Item Master

You can delete unneeded item masters from the application.

To delete an item master:




4) In the table, in the item master row, select Edit.

5) Select Delete.



Field


125

Items Overview

The application provides a feature to define specific inventory items. Items include equipment and materials used at the jobsite. Information about each item, such as the serial number, and up to five custom fields, can be defined for each item. The items display in a hierarchal tree for which categories and sub-categories can be defined. Project managers can create new items manually or by uploading data for the items.

Add an Item

You can add items manually to your project. When you manually add an item, you can assign an item master. Assigning an item master to an item ensures that the item inherits the item properties, standard issues and commissioning forms from the item master which streamlines the setup process.

To add an item:



3) On the menu, select Field Setup, and then select the Items tab.

4) Under the Add New Inventory Item section, complete the following fields

Description: Enter a short description or name of the item.

(Optional) Item Master: Select not selected to open the Select item master dialog box. Select an item master and select Close.

Item Type: Select Component or Category. Select component if the item is a physical component or piece of equipment. Select category if the items is a description of a group of items.

Quantity: Enter the amount of the item required to complete the work.

5) Select Add New.



Field

Create an Upload Template for Uploading Items

Create a Microsoft Excel template to use when importing items.

To create an import template:




4) Under the Upload Inventory From File section, select Download Sample Data.



126


Field

Upload an Item

You can import new area types into the application from a Microsoft Excel (.xls or .xlsx) file or an XML file.

To import areas:




4) Under the Upload Inventory From File section, select Browse, select a file, and then select Upload Inventory.

5) Select OK.



Field

Export Existing Items

You can export items to use them in other projects or applications.

To import areas:




4) Under the Upload Inventory From File section, select check to include IDs into XML to include IDs.

Note: The format of the exported file may not be formatted the same or contain the same columns as a file that was imported.

5) Select Export Existing Inventory, and then select OK.

6) Save or open the file.



Field

Add a File to an Item

You can add files to items.

To add a file to an item:

Dictionary Configuration

127




4) In the item row, select Edit, and then select the Files tab.

5) Select Upload from a local drive, and choose a file.



Field

Delete an Item

You can delete unneeded items from the application.

To delete items:




4) In the table, in the item row, select Edit.

5) Select Delete.



Field


Oracle Primavera Cloud enables your organization to define a series of application-wide parameters and values that apply globally and to all projects in a workspace. Use these settings to customize the application to meet specific requirements and standards.

Calendars Overview

Calendars enable you to define available workdays and work hours in a day. You can also specify national and recognized holidays and exceptions to the standard work time. Separate calendars can be made available to projects, resources, and roles. Each project, resource, and role must have a calendar assigned. Assign calendars to each resource, role, and activity to determine time constraints in a uniform way. For example, based on its calendar, a resource might not be available; or, if the resource is available, the activity might not fit the calendar requirements. The application uses the calendar assignments for scheduling and leveling resources and roles, and scheduling and tracking activities.

There is one default calendar per workspace. The default calendar is automatically assigned to all resources, roles, and projects in the workspace. Any calendar in the workspace can be assigned as the default calendar.


128

You can establish an unlimited number of calendars to accommodate different work patterns. For example, if some activities require a five day workweek, while others are performed part-time (such as Monday, Wednesday, and Friday), you can create different calendars and assign them to the activities and resources in your projects. An activity’s Type field value determines whether the activity uses the calendar of an assigned resource, role, or its activity calendar.

Add a Holiday List

Add a holiday list to include any public or company holidays observed by the organization that should be reflected in project and resource schedules. One holiday list can be added per calendar.

To add a holiday list:

1) Navigate to the Calendars dictionary page (see page 329).

2) Select Holidays.

3) In the Manage Holiday Lists dialog box, enter a name for the holiday list.

4) Select Edit Holiday List.

5) Enter a holiday name.

6) Choose when the holiday occurs.

Once on: Select if this holiday is a onetime occurrence.

Repeat every: Choose if a holiday occurs on the same date every year.

Note: You can select on a calendar when holidays are recognized as part of the standard work week.

Repeat the: Choose if a holiday occurs on a different date each year, but always occurs on the same day and week each year.

7) Continue to enter dates as needed.


In Primavera Cloud:

a. Select Save.



Select Save.



Cost and Funds

Lean

Resources

Risk

Schedule

Scope


129

Add a Calendar

Add calendars to a workspace to assign to projects, resources, and roles to determine work and nonwork time on a project.

To add a calendar:


2) Select Add.

3) In the Add Calendar wizard, on the Name step, enter a Name and ID for the calendar. Select Next.

4) On the Create Work Week step, specify the number of work hours per day by manually entering the number of hours or by selecting the time period on the calendar. Change the time periods on the calendar by dragging the entire block of time or by expanding or reducing the block of time. Select Next.

5) On the Add Holidays step, choose a holiday list to apply.

6) Select the If a holiday falls on unavailable time, move option if your calendar has holidays that fall on standard nonwork time and should be marked as holiday time during standard work time. Select where on the calendar the holiday should be reflected.

7) Select Finish.


In Primavera Cloud:

a. Select Save.



Select Save.

Tips

You can also create a calendar by duplicating an existing calendar. Select the Contextmenu next to the calendar, and select Duplicate. Be sure to change the Name and ID for the calendar.



Cost and Funds

Lean

Resources

Risk

Schedule

Scope


130

Set a Calendar Exception Time

Exception time is used when there are differences in the standard work hours for particular time periods. An entire day, or specific hours during the day, can be marked as an exception.

For example, the organization may decide to give employees a half day of vacation time the day before a scheduled holiday. In this case, the work hours would be adjusted for that work day to reflect the exception.

To set exception time:


2) Select a calendar.

3) Select the Calendar tab.

4) Make the necessary adjustments to the calendar.

To change the work hours for a day, select a period of time on a specific day. Change the exception time on the calendar by dragging the entire block of time or by expanding or reducing the block of time. The block of time indicates the new work hours for the day.

To mark an entire work day as a nonwork day, select the date menu, and select Unavailable.

To mark a holiday as a work day, select the date menu, and select Available. Adjust the exception time for the new work day by dragging, expanding, and reducing the block of time.

Note: To revert any changes you made to a day, select the date menu, and select Set to Standard.


In Primavera Cloud:

a. Select Save.



Select Save.



Cost and Funds

Lean

Resources

Risk

Schedule

Scope


131

Assign Calendar Availability

Calendars can be assigned to projects, resources and roles, or both. By default, a calendar is assigned to both.

Note: The default calendar must be available to both projects and resources and roles.

To assign calendar availability:



3) Select the Summary tab.

4) In the Available To section, adjust values as needed.


In Primavera Cloud:

a. Select Save.



Select Save.



Cost and Funds

Lean

Resources

Risk

Schedule

Scope

Set Number of Work Hours Per Time Period

Configure the work hours per time period settings to specify the default number of hours in a work period for a calendar if different from the standard time periods defined in Application Settings. These settings display by default.

The application calculates and stores time unit values in hourly increments, but you can set preferences to display time units in other increments, such as days or weeks. The values specified for Time Periods are used to convert hours to other time increments for display, and to convert all non-hourly time increments to hours for storage in the database.

To set the number of work hours for each time period:



3) Select the Summary tab.


132

4) In the Time Periods section, adjust values as needed.


In Primavera Cloud:

a. Select Save.



Select Save.



Cost and Funds

Lean

Resources

Risk

Schedule

Scope

Set the Default Calendar

The default calendar is set in the workspace-level Calendars dictionary and is available to projects, resources, and roles within that workspace. One calendar must always be defined as the default.

Notes:

The application has a built-in default calendar. The settings in this calendar cannot be changed. After another calendar has been assigned as the default, this calendar can be deleted.

You can also set the default calendar on the Project page in Defaults & Options. You can choose from a list of calendars that are available to the Project object.

To set the default calendar:


2) In the list of calendars, select the Default option for the calendar.


In Primavera Cloud:

a. Select Save.



Select Save.


133

Tips

If the calendar you selected was only available to Project or Resource/Role, then both options are automatically selected when you select a new default calendar.



Cost and Funds

Lean

Resources

Risk

Schedule

Scope

Update the Owning Workspace of a Calendar

Update the owning workspace of a calendar to move it to another workspace that you are assigned. If you move a calendar to a workspace that is higher in the workspace hierarchy, it will be available to more workspaces.

To update the owning workspace of a calendar:

1) Navigate to the Calendars dictionary page (see page 329)




5) Select Save.




Cost and Funds

Lean

Resources

Risk

Schedule

Scope

Codes Overview

Codes help you categorize your data objects based on characteristics that they share. If you have many instances of an object, codes help you group and filter potentially vast amounts of information spanning different areas of the organization. You can also use codes to arrange objects hierarchically. The application supports an almost unlimited number of codes and values; therefore, you can establish as many as you need to meet the filtering, sorting, and reporting requirements of your organization.


134

Codes are configured at the workspace level and can be created for the following objects:

Activities

Commitments

Contracts

Custom Logs

Files

Funds

Ideas

Portfolios

Programs

Projects

RFIs

Reports

Resources/Roles

Risks

Scope Assignments

Scope Items

Strategies

Submittals

Tasks

WBSs

Work Packages

Add a Code

Create codes to help categorize and track objects based on attributes they share.

You can apply codes to one or more of the following objects: Activities, Commitments, Contracts, Custom Logs, Files, Funds, Ideas, Portfolios, Programs, Projects, RFIs, Reports, Resources/Roles, Risks, Scope Assignments, Scope Items, Strategies, Submittals, Tasks, WBSs, and Work Packages.

To add a code to one or more objects:

1) Navigate to the Codes dictionary page (see page 330).

2) In the table, select Add.

3) In the new row, in the Name and ID columns, enter a name and ID for the new code.

4) In the Applies to panel, select one or more objects to apply the code.


In Primavera Cloud:

a. Select Save.



Select Save.


135

You can also perform this task on a single object from the Summary & Settings panel inPrimavera Cloud:



3) On the Summary & Settings menu, select Defaults & Options.

4) Select the object, and then select the Codes tab.

Note: To add a code to this object that exists in the current or parent workspace, select Assign. Codes that display for the current workspace are the codes assigned to other objects in the workspace. Codes that display from the parent workspace are only the codes that are assigned to the same object type.



Cost and Funds

Dashboards

Field

Files

Lean

Portfolio Analysis

Reports

Resources

Risk

Schedule

Scope

Strategic Alignment

Submittals

Workflows and Forms

Add a Value to a Code

Add values to a code to group, sort, and filter data.

To add a code value:

1) Navigate to the Codes dictionary page (see page 330).

2) Select a code.

3) Select the Context menu, and select Add Code Value.

4) In the Name and ID columns, enter a name and ID for the code value.


In Primavera Cloud:

a. Select Save.


136



Select Save.

You can also perform this task on a single object from the Summary & Settings panel inPrimavera Cloud:



3) On the Summary & Settings menu, select Defaults & Options.

4) Select the object, and then select the Codes tab.



Cost and Funds

Dashboards

Field

Files

Lean

Portfolio Analysis

Reports

Resources

Risk

Schedule

Scope

Strategic Alignment

Submittals

Workflows and Forms

Update the Owning Workspace of a Code

Update the owning workspace of a code to move it to another workspace that you are assigned. If you move the code to a workspace that is higher in the workspace hierarchy, it will be available to more workspaces.

To update the owning workspace of a code:

1) Navigate to an object configuration page (see page 331).

2) On the object page, select the Codes tab.

3) On the Codes tab, select a code.




In Primavera Cloud:


137

a. Select Save.



Select Save.



Cost and Funds

Dashboards

Field

Lean

Portfolio Analysis

Reports

Resources

Risk

Schedule

Scope

Strategic Alignment

Submittals

Workflows and Forms

Currencies Overview

Configure currencies in the application to track the cost of your projects in their native currency. For example, if the base currency of your organization is Euros, but your project is located in the United States, you may want to set your project currency to United States Dollars. From the project Cost Sheet page, you can view project costs in the project currency or the base currency.

Base Currency

The base currency is set at the root workspace during company provisioning. The base currency you select should be the currency that the majority of the workspaces and projects will use. You cannot change the base currency if costs exist for projects.

Workspace Currency

Create currencies at the workspace level to make them available to projects in the workspace and projects of child workspaces. Currencies should be created at the highest level workspace they apply so they are inherited. You can select from a preexisting list of currencies or create custom currencies.

Project Currency

Set project currencies for any projects that will not use the base currency. The project currency exchange rate follows the exchange rates defined at the workspace.


138

Add a Currency

Add currencies to workspaces to make them available to projects in the workspace. All currencies added to the root workspace are inherited in child workspaces. Changes to these currencies must be made in the owning workspace. Add any other currencies that projects may need by selecting them from the preexisting list.

To add a currency:

1) Navigate to the Currencies dictionaries page (see page 331).

2) On the Currencies page, select Add.

3) In the Select Currency dialog box, select currencies, and select Select.

4) Modify other currency settings as needed.


In Primavera Cloud:

a. Select Save.



Select Save.

Tips

The Decimal Places setting enables you to select how many decimal places to show when viewing costs in the application. The database stores values for up to 6 decimals for cost fields, regardless of the number of decimal places set to display.



Cost and Funds

Lean

Portfolio Analysis

Resources

Risk

Schedule

Scope

Strategic Alignment

Add a Custom Currency

You can create custom currencies if the default currencies do not meet the needs of your organization.

To add a custom currency:


2) On the Currencies page, in the Currencies table, complete the following fields:

Name: Enter a unique name for the currency.


139

Currency Code: Enter a unique currency code with fewer than 3 characters.

Currency Symbol: Enter a currency symbol. The currency symbol is displayed next to monetary amounts in the application for users who chose to display currency symbols.

Decimal Places: Enter the amount of decimal places to display. The application shows up to 5 decimal places.

Sharing Method: Specify how the currency is shared between parent and child workspaces:

Manual: The currency can be pulled down by child workspaces individually, using the Assign button in each child workspace. This is the default option.

Automatic: The currency is pushed down to child workspaces automatically.


In Primavera Cloud:

a. Select Save.



Select Save.



Cost and Funds

Lean

Portfolio Analysis

Resources

Risk

Schedule

Scope

Strategic Alignment

Modify a Project Currency

Projects inherit the base currency by default, but you can set a custom project currency. A project can be viewed in the project currency or the base currency. A workspace currency must have an exchange rate defined to appear in the list of currencies available to the project.

To modify a project currency:

1) Navigate to the project Details page (see page 328).

2) In the Currency section, in the Project Currency field, select the project currency.


In Primavera Cloud:

a. Select Save.




140

Select Save.

The Exchange Rate field is automatically populated with the exchange rate defined at the workspace level.

Note: The project currency cannot be changed if costs exist for a project.



Cost and Funds

Lean

Portfolio Analysis

Resources

Risk

Schedule

Scope

Strategic Alignment

Add an Exchange Rate

Add exchange rates to currencies to keep cost calculations up-to-date. Exchange rates added to workspace currencies will apply to project currencies. A workspace currency must have an exchange rate defined to appear in the list of currencies available to the project. You can add past exchange rates to retain a historical record before the currency is in use, or you can enter the current exchange rate. You cannot enter future exchange rates. All exchange rates must be added to the currency in the owning workspace.

To add an exchange rate to a currency:


2) On the Currencies page, in the table, select a currency.

3) In the Exchange Rates detail window, enter an Effective Date and Exchange Rate.


In Primavera Cloud:

a. Select Save.



Select Save.

Note: You cannot delete or edit historical exchange rates.



Cost and Funds


141

Lean

Portfolio Analysis

Resources

Risk

Schedule

Scope

Strategic Alignment

Update the Owning Workspace of a Currency

Update the owning workspace of a currency to move it to another workspace that you are assigned. If you move a currency to a workspace that is higher in the workspace hierarchy, it will be available to more workspaces.

To update the owning workspace of a currency:


2) On the Currencies page, in the table, select a currency.



5) Select Save.




Cost and Funds

Lean

Portfolio Analysis

Resources

Risk

Schedule

Scope

Strategic Alignment

Folder Templates Overview

Folder templates provide a way to create folder and file structures that can be used across your organization. If your organization has standard folders or files that will be used across various workspaces, you can create a folder template that can be applied to project or portfolio file folders. Applying a template applies all folders and files to the selected folder from the template. Using templates saves time by eliminating the need to re-import files and folders multiple times in multiples projects and portfolios. Folder templates are managed at the workspace level, in either the Files app or workspace-level settings.


142

Add a Folder Template

Create folder templates to use across your organization.

To add a folder template:



3) On the Summary & Settings menu, select Dictionaries, and then select Folder Templates.

4) On the Folder Templates page, select Add, and then enter a Template Name.

5) Select Save.


Tips

You can also add a folder template in the Files app at the workspace level.

Select the template name to edit your template.



Cost and Funds

Field

Files

Lean

Portfolio Analysis

Resources

Risk

Schedule

Scope

Strategic Alignment

Submittals

Edit a Folder Template

You can use the Editing Folder Template page to create a folder structure, add files, and apply previously created templates.

To edit a folder template:



3) On the Summary & Settings menu, select Dictionaries, and then select Folder Templates.

4) In the table, select the name of a template.

5) On the Editing Folder Template page, choose from the following options:


143

a. Select Add File to add files that will be used in multiple projects and portfolios.

b. Select Add Folder to set up a folder structure.

c. Select the Context menu, and then select Apply Template. In the Apply Template to Selected Folder dialog box, choose a template, and select OK.

Tips

You can also edit a folder template in the Files app at the workspace level.



Cost and Funds

Field

Files

Lean

Portfolio Analysis

Resources

Risk

Schedule

Scope

Strategic Alignment

Submittals

Forms Overview

In Oracle Primavera Cloud, forms are used to present or collect data about a variety of objects. They can be shown to users during workflows, or they can be used to replace some default forms in the application.

When creating workflows, you can add forms to form tasks and manual decision tasks. Form tasks require performers to complete or review forms. Manual decision tasks do not require forms, but they can include forms that performers can fill out or view before making required decisions.

When configuring workspace settings, you can choose a form to take the place of the default General page for all projects in the workspace. You can also replace the default Propose Risk or Add RFI forms with custom forms.

To add, edit, delete, and view workflows and forms, you must have the corresponding security privileges.

Consult the Workflow Design Guide to learn more about designing forms.

Locations Overview

A location is a geographical reference defined by a pair of coordinates; longitude and latitude.


144

To create a location, you can enter its coordinates directly or enter a street address and allow the application to find the longitude and latitude for you.

Assign locations to projects, resources, or risks to produce reports based on geographical location. You can also group and filter lists of objects that support locations. Locations are created and stored in the Locations dictionary at the workspace level. They can also be created and stored at the project, resource, or risk level and optionally saved to the Locations dictionary for future use. When choosing projects for a portfolio, location data can be used as a filter condition.

Note: Oracle Primavera Cloud uses Oracle Map Cloud service for location data. (http://elocation.oracle.com(http://elocation.oracle.com))

Add a Location

Create locations to assign to projects, resources, or risks so that you can report, search, and filter by location.

To create a location:

1) Navigate to the Locations dictionary page (see page 331).

2) On the Locations page, select Add.

3) In the Add Location dialog box:

a. In the Name field, enter a name for the new location.

b. In the ID field, enter a unique identifier for the location.

c. (Optional) In the Description field, enter a description of the location

d. Enter either a street address or the latitude and longitude.

Notes:

Input longitude and latitude in the format that is appropriate for your geolocation service. Enter longitude and latitude in decimal degrees or directional designators.

Select a country when locating using longitude and latitude to improve results.

e. Select Locate.

f. Select Add.


In Primavera Cloud:

a. Select Save.



Select Save.

http://elocation.oracle.com/


145

Tips

You can also import locations from a worksheet. Select Import , and then select Download Import Template to generate a template to help you format the data correctly.

Locations can be created on the Details Summary & Settings page for a project, on the Resource List page for a resource, or in the project or program Risk Register for a risk. By default, the locations created for a project, resource, or risk are stored with the object, but you can optionally save the location to the Locations dictionary for future use.



Cost and Funds

Portfolio Analysis

Resources

Risk

Schedule

Scope

Strategic Alignment

Download an Import Template for Importing Locations

Download a Microsoft Excel template to use when importing location data.



2) On the Locations page, select Import , and then select Download Import Template.


In Primavera Cloud:

a. Select Save.



Select Save.

Tips

The import template is downloaded as a Microsoft Excel file with the default file name LocationImportTemplate.

The top two rows of the worksheet are required when importing data locations from a worksheet. Do not change the data in these rows.



Cost and Funds

Lean

Portfolio Analysis


146

Resources

Risk

Schedule

Scope

Strategic Alignment

Import Locations

You can import new locations into the application from a Microsoft Excel (.xls or .xlsx) file.

To import locations:


2) On the Locations page, select Import.

3) In the Import Locations dialog box, select Browse, select a file, and select Import.


In Primavera Cloud:

a. Select Save.



Select Save.

Tips

Select Download Import Template to download a template file ready for you to populate with data.

Input longitude and latitude in the format that is appropriate for your geolocation service. Enter longitude and latitude in decimal degrees or directional designators.



Cost and Funds

Lean

Portfolio Analysis

Resources

Risk

Schedule

Scope

Strategic Alignment

Update the Owning Workspace of a Location

Update the owning workspace of a location to move it to another workspace that you are assigned. If you move the location to a workspace that is higher in the workspace hierarchy, it will be available to more workspaces.


147

To update the owning workspace of a location:


2) In the table, select a location row.



5) Select Save.




Cost and Funds

Lean

Portfolio Analysis

Resources

Risk

Schedule

Scope

Strategic Alignment

Workflow Designs and Workflow Configurations Overview

Workflows use predefined sequences of steps and tasks to route different kinds of information among different kinds of workers. Organizations use workflows to manage processes that involve many people, many steps, or steps that need to be completed in a specific order.

In Primavera Cloud, workflows can be configured to manage these objects:

Budgets

Budget changes

Budget transfers

Changes

Change orders

Commitments

Contracts

Ideas

Portfolios


Projects

RFIs

Risks

Submittals


148

After a workflow has been created, it can start automatically or manually. Workflows can be set to start automatically when some action occurs with the objects they run against. For example, a project workflow can be set to start automatically when a project proposal is created. Similarly, an RFI workflow can be set to start automatically when an RFI is submitted. Managers and administrators can also start workflows on the Start Workflows page.

Consult the Workflow Design Guide to learn more about designing and configuring workflows.

Portfolio Configuration Options

Analysis Views Overview

Analysis views are dynamic tools budget planners use to view, compare and analyze budget plan data. Analysis views are built upon customizable layout types, charts, and grids that capture information from budget plan scenarios. Charts provide a visual representation of data, while grids enable planners to view plan values and costs in greater detail.

Create analysis views to simplify scenario comparisons, and speed up the planning process. Budget planners use analysis views along with the Budget Planning page during selection analysis to determine the best mix of projects for a budget plan. While the Budget Planning page provides time phased budget data, analysis views provide fast and accurate insights into additional project attributes. Planners use analysis views to get a direct comparison of project data, such as Return on Investment, Net Present Value, and Profitability Index, and to evaluate projects for potential inclusion in a budget plan.

In the workspace-level settings, you can add, publish, and delete analysis views for individual portfolios in the workspace. In the portfolio-level settings, you can add analysis views to the portfolio or associate an analysis view from the parent workspace or another portfolio in the workspace.

Create an Analysis View in a Workspace

Create analysis views to analyze important project data while developing the portfolio budget. Analysis views are highly customizable and enable you to select the values important for evaluation, such as Return on Investment, Net Present Value, and Internal Rate of Return. Analysis views aid in providing budget planners with concise and clear information when selecting projects for a budget plan. At the workspace level, you can add, publish, and delete analysis views for individual portfolios in the workspace. Analysis views are displayed and opened from the Published Views page at the portfolio level.

To create an analysis view:

1) Add an Analysis View (on page 149)

2) Configure a Chart or Grid (on page 149)

3) Publish an Analysis View to a Portfolio (on page 150)


149

Add an Analysis View

Add an analysis view to create a meaningful display of portfolio budget plan scenario data. When adding an analysis view, you can select a view type to specify the arrangement for the charts and grids included in the view.

To add an analysis view:



3) On the Summary & Settings menu, select Dictionaries, and then select Analysis Views.

4) Select Add View, and select a view type.

5) In the Name dialog box, enter a unique name for the analysis view.

6) Select OK.

7) Select Save.


Tips

When editing an Analysis View, select the Change Type menu on the View tab, and select a type to change the layout of the analysis view after you have created it.


Cost and Funds

Configure a Chart or Grid

You can configure charts and grids to tailor them to your analysis views.

To configure a chart:




4) Select an analysis view.

5) On the View tab, select the chart pane or grid pane you would like to modify, and select Configure.

6) Configure your chart or grid:

If you selected a chart, use the Configure Chart wizard to change the properties of the chart.

If you selected a grid, use the grid Settings dialog box to change the properties of the grid.

7) Select Save.

8) Select Save.



150


Cost and Funds

Publish an Analysis View to a Portfolio

Publish analysis views to portfolios to enable planners to evaluate project selection based on key performance indicators and other project attributes. You can publish multiple views to a single portfolio, enabling planners to switch between views and compare data based on different sets of criteria. Analysis views published to portfolios can also be viewed in the portfolio-level settings.

To publish an analysis view to a portfolio:




4) Select an analysis view.

5) On the Settings tab, select the portfolio.

Select Publish View to enable a user with the appropriate privileges to access the analysis view from the Published Views page for a portfolio.

Select User Customization to allow a user with the appropriate privileges to customize the analysis view while viewing data.

6) Select Save.



Cost and Funds

Measures Overview

Performance for portfolios and strategies is captured using measures. Measures are defined to monitor data such as number of projects on time and return on investment.

Measures have two dimensions: actual and target. These values can be calculated using a formula, or they can be set for manual entry. The target value can also be used when setting thresholds for the measure. Thresholds and indicators are defined to visually represent the status of a measure when monitoring a portfolio or strategy.

Measures are defined at the workspace level and can be associated to any portfolio or strategy node. Measures are created using aggregates of project attributes or by using existing measures. Measures using other measures can reference specific portfolios and strategy nodes. Project attributes and existing measures cannot be used in the same expression for a measure.

Portfolios are monitored using measures on the portfolios Scorecard page, the workspace Summary Scorecard page in the Portfolio Analysis app, and in Dashboards. Strategies are monitored on the workspace Strategy Scorecard page in the Strategic Alignment app.

You can also create project measures to monitor activity attributes in a project. Project measures are configured in the Project Defaults & Options settings.


151

Create a Measure

Create measures to provide data that can be used for monitoring the health and status of portfolios or strategies.

To create a measure:

1) Add a Measure (on page 151)

2) Set a Threshold for a Measure (on page 153)

3) Associate a Measure with a Portfolio (on page 154)

4) Associate a Measure with a Strategy (on page 154)

For more details, see:

Working with Creating Measures (on page 155)

Add a Measure

Add a measure to quantitatively monitor the health and status of portfolios and to monitor the performance of strategy nodes.

The target and actual values used for measures can be configured for manual entry or using a formula. Formulas are defined by creating expressions using project attributes or using existing measures.

For information on creating advanced formulas for measures, refer to the Oracle Primavera Cloud Expression Language Guide on Oracle Help Center.

To add a measure:



3) On the Summary & Settings menu, select Dictionaries, and then select Measures.


Note: Select Context next to an existing measure, and then select Duplicate to duplicate the measure. Duplicated measures do not maintain the portfolio or strategy associations of the original measure.

5) In the table, complete the following fields as required:

Name: The name of the measure.

(Optional) Description: Details about the measure.

Data Type: The type of data that the formula generates. Options include Cost, Number, and Percentage.

Target Type: Determines whether the Target value of the measure is manually entered or calculated using a formula.

Actual Type: Determines whether the Actual value of the measure is manually entered or calculated using a formula.

Measure Based: Determines whether the measure is created using existing measures. Either Target Type or Actual Type must be set to Formula.


152

Tracking Frequency: Determines how frequently you want to monitor the measure. For example, if a formula-based measure's tracking frequency is set to Weekly, it is computed every week. If it is a manual measure with Weekly tracking frequency, you can enter measure values in weekly buckets.

6) Select the Data Source detail window to configure formulas if either Target Type, Actual Type, or both are set to Formula.

Note: The Data Source detail window does not display if Formula was not selected for either Target or Actual Type.

7) Select the field to enter a formula.

Actual: Formula that calculates the current values for the measure.

Target: Formula that calculates a value that can be used when setting thresholds to measure against.

Base Expression: The base expression for the Actual or Target formulas when Percentage is the selected Data Type.

8) Enter a formula manually or using a formula template.

a. To enter a formula manually:

1. Select the Field list to locate the field to use in the calculation. Select Insert.

2. Select the mathematical symbols for the expression.

3. Add any additional fields for mathematical symbols needed for the expression.

b. To use a formula template:

1. In the Aggregation Type list, select the calculation needed for the formula, and select Insert. The formula template appears.

2. To use the template, highlight or delete Field or Filter, including angle brackets, select a field from the Field list, and select Insert. Repeat for any additional fields or fields to filter by.

3. Add any additional mathematical symbols needed for the expression.

9) To insert measure based measures:

a. Select the Field list. All the measure based measures display in this list when the Measure Based option is selected.

b. Select one of the following:

A measure based measure. This inserts the formula for the measure based measure.

Referenced Measures. This opens a dialog box to select measures that are currently assigned to portfolios or strategies. Select the Portfolios or Strategiestab, select the measure based measure, and select Insert.

10) Select Validate Formula.

11) Select Save.

Tips

After the measures process is complete, you can review the measures log to view details about the process, including process start and finish and what portfolios or strategies were included. You can access the measures log from the Manage Services page.


153


Dashboards

Portfolio Analysis

Strategic Alignment

Set a Threshold for a Measure

Set thresholds for measures to see the status of measures using visual indicators when monitoring portfolios and strategies.

To set a threshold:




4) In the table, select the measure.

5) Select the Thresholds detail window.

6) Select Add.

7) In the Operator field, select a parameter to use in the threshold calculation.

8) In the Value field, enter a threshold value to use in the calculation.

9) In the High Value field, enter the top of the range when the operator is set to Within Range or Not Within Range.

10) In the Indicator Color field, select a color to visually represent status when the threshold is met.

11) In the Indicator Icon field, select an icon to visually represent status when the threshold is met.

12) In the Goal list, select whether a high or low value indicates a positive change in the measure.

For example, High Values would be selected when measuring Net Savings to represent that an increase in value is a positive change.

13) In the Threshold Computation Method, select how thresholds are calculated using Actual and Target values.

Actual Value: The current value. This is the value as calculated by the expression for Actual on the Data Source tab.

Percent of Target: The percentage of the actual value compared to the target value.

14) Add as many thresholds as necessary for the measure.

15) Select Save.


Dashboards

Portfolio Analysis

Strategic Alignment


154

Associate a Measure with a Portfolio

Associate measures with portfolios to perform quantitative analysis on project data.

To associate a measure with a portfolio:





5) Select the Portfolios detail window.

6) Select Link.

7) In the Link Portfolios dialog box, select the portfolios, and select Link.

8) Select Save.


You can also perform this task from the Portfolios inventory panel:

1) In the object selector, select Portfolios, and then select View All Portfolios.

2) In the table, select the portfolio, and select the Measures detail window.


Portfolio Analysis

Strategic Alignment

Associate a Measure with a Strategy

Strategy performance is monitored using measures assigned to the strategy nodes. Associate the measures that capture the data needed for monitoring the current strategies.

Note: If measures have not been created, see Create a Measure (on page 151).

To associate measures with a strategy:





5) Select the Strategies detail window.

6) Select Link.

7) In the Link Strategies dialog box, select the strategies, and select Link.

8) Select Save.


You can also perform this task from the Strategy List page:



155

2) In the sidebar, hover over Strategic Alignment, and select Strategy List.

3) In the table, select the strategy node, and select the Measures detail window.


Strategic Alignment

Working with Creating Measures

Measures are configured data used to monitor the health and status of a portfolio and to measure strategy performance. Measures can be created using aggregates of project attributes, by using existing measures, or set for manual entry. Project attributes and existing measures cannot be used in the same expression for a measure.

Measures have two dimensions: actual and target. A target value can optionally be defined to use when setting thresholds for the measure. Thresholds and indicators are defined to visually represent the status of a measure when monitoring a portfolio on the Scorecard page or on a configured dashboard.

For information on creating advanced formulas for measures, refer to the Oracle Primavera Cloud Expression Language Guide on Oracle Help Center.


156

Table of Screen Highlights

Item Description

1 Aggregation Type: Provides a template for formulas that use Sum, Min, Max, Count, and Average equations. Select the Aggregation Type, and select Insert.

For example, the Sum template displays the following:

sum(< Field >,< Filter >)

Replace <Field> with the name of the field to be summed. Optionally, replace <Filter> with a field that will filter the results by. Add any additional filter requirements using the mathematical symbols provided.

2 Field: Provides all the fields that can be used in formulas.

If Measure Based is selected, only existing measures display. Select Referenced Measures in the Field list to view measures that are currently assigned to Portfolios or Strategies.

Select a field name, and select Insert. The proper formatting for the field displays.

3 Mathematical Symbols: Used when defining formulas manually or when using the aggregation type template.

4 Validate Formula: Verifies the formula works.

The following table provides examples of formulas that can be created. Total Cost is represented in the preceding image.

Table of Measure Examples

Measure Name

Data Type

Target Actual Base Expression (Actual)

Total Cost Cost sum(object.Project_currentApprovedBudgetBase)

sum(object.Project_atCompletionCost, object.Project_status=='Active')

Projects on Time

Percentage

count(object.ProjectCode_Code, object.Project_scheduleVariance<10)

count(object.ProjectCode_Code)

Cost/ROI Ratio

Number

object.'PortfolioMeasure_Total Cost'/object.'PortfolioMeasure_Return on Investment'

Note: This expression is Measure Based.


157

Measure Name

Data Type

Target Actual Base Expression (Actual)

Project Count

Number

count(object.ProjectCode_Code,object.Project_status=='Active')

Return on Investment

Number

average(object.Project_returnInvestment)

Net ROI Number

0.25*Portfolios.get("Consulting","Consulting Portfolio").'PortfolioMeasure_ROI' +

0.50*Portfolios.get("E&C","E&C Portfolio").'PortfolioMeasure_ROI' +

0.50*Portfolios.get("Energy","Energy Portfolio").'PortfolioMeasure_ROI'

Note: This expression is Measure Based and references measures from other portfolios.


158

Defining Thresholds

The following image provides an example of thresholds that can be set for the Total Cost example. These thresholds are used to determine how status for the measure is visually represented on the scorecard and any configured dashboard.

Table of Screen Highlights

Item Description

1 Goal: Determines whether a high or low value indicates a positive change in the measure.

2 Threshold Computation Method: Determines how thresholds are calculated using Actual and Target values.

Actual Value: The current value. This is the value as calculated by the expression for Actual on the Data Source detail window.

Percent of Target: The percentage of the actual value compared to the target value.

3 Operator: The operators necessary for comparing values in the thresholds.

4 Value: The values the operators use for comparison.

5 High Value: The top of the range when the operator is set to Within Range or Not Within Range.

6 Indicator Color: The color to visually represent status when the threshold is met.

7 Indicator Icon: The icon to visually represent status when the threshold is met.


159

Project Configuration Options

CBS Overview

A Cost Breakdown Structure (CBS) is used to track, manage, and report costs related to a project or program. The CBS standardizes costs into categories that represent manageable cost sources for an organization and a standard cost classification system. The CBS is comprised of cost codes that are classified into three types: expense, capital, or none. These codes are concatenated based on the segment definition and can be viewed as a flat or hierarchical structure. CBS codes are used in top-down and bottom-up cost planning and tracking.

The app enables you to create a custom CBS at the workspace, project, and program level. When you create a CBS at the project level, you can select the budget sources for your project. This selection can be edited from the Cost Sheet page.

Workspace CBS

Any CBS codes that are standards in your organization should be associated at the highest level workspace or node that they apply to so that they are available to child workspaces and projects. A CBS at the workspace level can be copied from the parent workspace, copied from sibling workspaces, imported from a Microsoft Excel spreadsheet, or entered manually. If you have created a unique workspace CBS, it can serve as a resource for projects in that workspace and sibling and child workspaces. Each workspace can contain only one CBS. The workspace CBS is created to serve as a CBS for projects and child workspaces to roll up the child workspace and project costs for a high level view of costs within that workspace.

Project or Program CBS

CBS codes at the project or program level can be copied from the parent workspace, copied from a sibling project or program, imported from a Microsoft Excel spreadsheet, or entered manually. If you have created a unique project or program CBS, it can serve as a resource for other projects or programs in that workspace. Each project or program cost sheet can contain only one CBS.

Create a Workspace CBS

Creating a workspace CBS enables you to use the same CBS across multiple projects in your workspace and in sibling workspaces. If a workspace and a child workspace share the same CBS, costs will roll up to the workspace Cost Sheet page, providing a high level view of project and child workspace costs in the workspace.

Choose one of the following methods to create your CBS:

Add a Workspace CBS (on page 160)

Add a new CBS if your workspace has a unique CBS.

Copy a Parent Workspace CBS (on page 163)

Copy a parent workspace CBS if you want to use the same CBS as the parent.

Create a Workspace CBS by Import (on page 161)


160

Add a CBS by importing if your organization already has a structured CBS you want to use.

Copy a Sibling Workspace CBS (on page 163)

Copy a sibling workspace CBS if you want to use a CBS from a sibling workspace.

Add a Workspace CBS

Add a CBS at the workspace level when projects included in the workspace or sibling workspaces need to use the same CBS.

To add a workspace CBS:



3) On the Summary & Settings menu, select Dictionaries, and then select CBS.

4) On the CBS page, select Create CBS.

5) In the CBS Setup dialog box, select Create new, and select Next.

6) Provide at least one segment definition. Each segment definition you enter here corresponds with a level in the CBS hierarchy. The number of segment definitions you create determines the number of hierarchical levels you can have in your CBS. For example, if you only define one segment, then the CBS will be a flat list with one level. If, however, you define two segments, then the CBS can be two levels deep, with some CBS codes nested under the top-level CBS codes. Use these fields to provide segment definitions:

Name: The name of the segment definition. Remember, here you are defining the name of the hierarchical level, not the name of an individual item. For example, if you are using MasterFormat to organize specs and documents, it would make more sense to enter "Divisions" here than to enter something like "Procurement and Contracting" or "General Requirements." That's because each of these things is itself a division. After you have defined the segment definitions, you can enter the individual divisions—like "Procurement and Contracting" or "General Requirements"—back where you are defining the CBS.

Default Value: For CBS codes that are subordinate to top-level CBS codes, this optional default value appears in their place before you add them. For example, let's say you've defined two segments, one called Divisions and another called Subdivisions. Let's also say that the default value for Subdivisions is 00. On the Cost Sheet page, if you add a new top-level CBS code titled "HVAC", then that code will be appended with 00 to read "HVAC 00." The Separator value determines how this default code is separated from the name of the parent code. In this case, we're using a space.

a. Separator: The separator that follows the name of the division. This can be a period, space, or hyphen. For example, let's say you have two segment definitions and have set the Separator value of the top-level segment to be a period. Let's also say the default value for both is 00. If you then add a new top-level CBS code titled "HVAC," it will appear on the Cost Sheet page as "HVAC.00".

7) Select Finish.

8) Enter your CBS codes, and select Save.

9) On the Summary & Settings panel, select Close.


161

Tips

Create an import template in Microsoft Excel instead of manually entering values if you have a lot of CBS codes to enter.



Cost and Funds

Risk

Scope

Create a Workspace CBS by Import

Creating a CBS using Microsoft Excel enables you to use the CBS already defined by your organization.

To create a CBS by import:

1) Download an Import Template for Importing CBS Codes (on page 161)

2) Import a CBS (on page 162)

Download an Import Template for Importing CBS Codes

Download a Microsoft Excel template to use when importing a workspace CBS. The number of levels in the segment definition in the spreadsheet must match the number of levels in the segment definition in the application.






5) In the CBS Setup dialog box, select Create new, and select Next.

6) Provide at least one segment definition. Each segment definition you enter here corresponds with a level in the CBS hierarchy. The number of segment definitions you create determines the number of hierarchical levels you can have in your CBS. For example, if you only define one segment, then the CBS will be a flat list with one level. If, however, you define two segments, then the CBS can be two levels deep, with some CBS codes nested under the top-level CBS codes. Use these fields to provide segment definitions:

Name: The name of the segment definition. Remember, here you are defining the name of the hierarchical level, not the name of an individual item. For example, if you are using MasterFormat to organize specs and documents, it would make more sense to enter "Divisions" here than to enter something like "Procurement and Contracting" or "General Requirements." That's because each of these things is itself a division. After you have defined the segment definitions, you can enter the individual divisions—like "Procurement and Contracting" or "General Requirements"—back where you are defining the CBS.


162

Default Value: For CBS codes that are subordinate to top-level CBS codes, this optional default value appears in their place before you add them. For example, let's say you've defined two segments, one called Divisions and another called Subdivisions. Let's also say that the default value for Subdivisions is 00. On the Cost Sheet page, if you add a new top-level CBS code titled "HVAC", then that code will be appended with 00 to read "HVAC 00." The Separator value determines how this default code is separated from the name of the parent code. In this case, we're using a space.

a. Separator: The separator that follows the name of the division. This can be a period, space, or hyphen. For example, let's say you have two segment definitions and have set the Separator value of the top-level segment to be a period. Let's also say the default value for both is 00. If you then add a new top-level CBS code titled "HVAC," it will appear on the Cost Sheet page as "HVAC.00".

7) Select Finish.

8) On the CBS page, select the Actions menu, and then select Download Import Template.

9) Select Save.


Tips

The import template is downloaded as a Microsoft Excel file with the default file name, ExportDataToSpreadsheet.

The top two rows of the CBS Codes worksheet are required when importing data from a worksheet. Do not change the data in these rows.

The top row of the Segment Separators worksheet is required when importing data from a worksheet. If you need to add another level to your hierarchy, increment the level number for each new level.

The segment definition specified in the spreadsheet must match the segment definition specified in the application.




Cost and Funds

Risk

Scope

Import a CBS

Import a CBS into the application from a Microsoft Excel (.xls or .xlsx) file.

To import a CBS:




4) On the CBS page, select the Actions menu, and then select Import.


163

5) In the Import CBS dialog box, select Browse, select the file you want to import, and select Import.

6) Select Save.


Tips

The segment definition specified in the spreadsheet must match the segment definition specified in the application.



Cost and Funds

Risk

Scope

Copy a Sibling Workspace CBS

Copy the CBS of a sibling workspace if any projects within your workspace will use the same CBS.

To copy a sibling workspace CBS:





5) In the CBS Setup dialog box, select Copy from other, and select Next.

6) Select a CBS to use, and select Next.

7) Select the CBS codes you want to include, and select Finish.

8) Select Save.




Cost and Funds

Risk

Scope

Copy a Parent Workspace CBS

Copy the parent workspace CBS if your workspace will use the same CBS.

To copy a parent workspace CBS:





164


5) In the CBS Setup dialog box, select Build from, and select Next.

6) Select the CBS codes you want to include, and select Finish.

7) Select Save.




Cost and Funds

Risk

Scope

Modify a Workspace Segment Definition

Use segment definitions to control the depth of the CBS hierarchy and how codes are concatenated. The number of segment definitions you create determines the number of hierarchical levels you can have in your CBS. For example, if you only define one segment, then the CBS will be a flat list with one level. If, however, you define two segments, then the CBS can be two levels deep, with some CBS codes nested under the top-level CBS codes.

To modify a segment definition:




4) On the CBS page, select the Actions menu, and then select Edit Segment Definitions.

5) In the Segments dialog box, make any edits, and select Save.


Tips

You cannot add a new segment definition if the existing segment definition is associated with a CBS code that is already assigned costs.

You cannot remove a segment definition if the CBS codes form a hierarchy as deep as the row number of the segment definition.

You cannot add or remove segment definitions to or from a workspace or project CBS that has been copied from its parent. However, importing from the parent CBS may pull down additional segment definitions.



Cost and Funds

Risk

Scope


165

Add a CBS Code

Add or delete CBS codes if your workspace CBS needs change.

To add a CBS code:




4) On the CBS page, in the Context menu, select Add Below.

5) In the new row, enter the new CBS code.

6) Select Save.


Tips

All CBS codes are created as active, but you can deactivate any codes that you do not want to be available for use by other users for scope assignments or copying CBSs.

Select the Context menu to organize your codes by moving them vertically or hierarchically.

If the CBS was copied from its parent workspace, you cannot add CBS root codes. However, you can add a new child CBS code indented below the root. To add a child CBS code, select the Context menu, and then select Add.

You cannot delete a CBS code if the code has been copied by any projects or child workspaces in the owning workspace.



Cost and Funds

Risk

Scope

Import Additional CBS Codes

If you copied a parent workspace CBS, you can update the workspace CBS with additional codes as your CBS needs change. You can import new codes added to the original CBS or import codes that you did not select before.

To import additional CBS codes:




4) On the CBS page, select the Actions menu, and then select Import.

5) In the Import CBS dialog box, select the codes you want to include, and select Import.

6) Select Save.



166



Cost and Funds

Risk

Scope

Cost Categories Overview

A cost category is used to define costs into a category more specific than a CBS code. The most commonly used cost category types are labor, equipment, materials, and other. These types allow you to categorize costs into groups. For example, you may want to track costs associated with labor. However, that label may be too broad. You can create a cost category called Subcontractor Labor with a type of Labor. This cost category can be assigned to all budget line items or actual line items that are a result of subcontractor labor.

When you create cost categories, you should evaluate what fields you want to be enabled for use, particularly if you plan to use the calculation fields. Different cost categories enable different fields. A cost category type of Other will not enable any extra fields.

Labor: If the cost category type is Labor, Quantity, Unit of Measure, Production Rate, and Labor Rate are editable fields. Cost for a budget line item with a labor cost category is equal to Quantity multiplied by Production Rate multiplied by Labor Rate. You can also manually enter the Cost.

Equipment: If the cost category type is Equipment, Quantity, Unit of Measure, and Unit Rate are editable fields. Cost for a budget line item with an equipment cost category is equal to Quantity multiplied by Unit Rate. You can also manually enter the Cost.

Materials: If the cost category type is Materials, Quantity, Unit of Measure, and Unit Rate are editable fields. Cost for a budget line item with a materials cost category is equal to Quantity multiplied by Unit Rate. You can also manually enter the Cost.

Other: Other is the most broad cost category type, which is used when your costs do not fall into the labor, equipment, or materials types. Cost categories with a type of Other allow the user to enter a cost value only. All other fields used for calculating costs are unavailable.

Add a Cost Category

You can create as many cost categories as necessary to meet the business needs of your organization.

To add cost categories:



3) On the Summary & Settings menu, select Dictionaries, and then select Cost Categories.

4) On the Cost Categories page, select Add.

5) In the new row, complete the following fields:

a. Abbreviation: Enter an abbreviation that is 10 characters or less.

b. Name: Enter a unique name.


167

c. Type: Select a type. Valid values include Labor, Equipment, Materials, and Other.

d. Sharing Method: Specify how the data is shared between parent and child workspaces:

Manual: The data can be pulled down by child workspaces individually, using the Assign button in each child workspace. This is the default option.


6) Select Save.




Cost and Funds

Scope

Update the Owning Workspace of a Cost Category

Update the owning workspace of a cost category to move it to another workspace that you are assigned. If you move a cost category to a workspace that is higher in the workspace hierarchy, it will be available to more workspaces.

To update the owning workspace of a cost category:



3) On the Summary & Settings menu, select Dictionaries, and then select Cost Categories.

4) In the table, select a cost category row, select the Context menu, and then select Change Owning Workspace.


6) Select Save.




Cost and Funds

Scope

Curve Profiles Overview

Curve profiles enable you to specify the allocation of scope assignment costs, quantities, and hours over the duration of an activity; resource or role hours spread over the duration of an activity; and budget quantities over their durations.

Amounts are distributed evenly throughout an activity unless a nonlinear distribution is specified using a curve profile. Scope assignments can use curve profiles regardless of whether they are linked to activities.


168

Interpreting Curve Profiles

After you navigate to the Curve Profiles dictionary page, you can view all of the default and custom curve profiles available to you. Select a curve profile to view a graph that represents how it works. The x-axis, labeled at the top of the graph, represents the percentage of the object's duration. The y-axis, labeled along the left side of the graph, represents the percentage of the object that has been allocated to th e duration percentages. The numbers along the bottom of the graph indicate what percentage of the is allocated at each increment of the duration.

Among the simplest built-in curve profiles is the Linear profile. Select it to view its graph. By default, the Linear curve profile evenly distributes 5.00% of the total quantity to every 5% increment in the item's duration, rounding as necessary.

Here is a list of all the built-in curve profiles:

Bell

Double Bell

Delayed Double Bell

Offset Triangular

Triangular Decrease

Triangular Increase

Front Loaded

Three Step

Linear

Back Loaded

Trapezoidal

Triangular

Define a Curve Profile

Define curve profiles to specify how scope assignment costs, quantities, and hours spread over the duration of an activity; resource or role hours spread over the duration of an activity; and budget quantities over budget durations. There are some default curve profiles defined in the application. You can add a new curve, which is based on the default linear curve, or copy and modify one of the existing curves.

To define a curve profile:

1) Navigate to the Curve Profiles dictionary page (see page 330).

2) To copy an existing curve, select the Context menu next to the curve to copy, and select Duplicate.

To create a curve, select the Context menu for a curve, and select Add.

3) Enter a Curve Name.

4) Modify the curve value percentages to create a curve that indicates how your costs and quantities should distribute over time. Curves are defined by 21 points (5% intervals from 0 to 100 is the default for a new curve).

5) Select Prorate to make the total of the distribution values equal to 100% while maintaining the shape you specified.



169

In Primavera Cloud:

a. Select Save.



Select Save.


Cost and Funds

Resources

Risk

Schedule

Scope

Update the Owning Workspace for Curve Profiles

Update the owning workspace of a curve profile to move it to another workspace that you are assigned. If you move the curve profile to a workspace that is higher in the workspace hierarchy, it will be available to more workspaces.

To update the owning workspace of a curve profile:



3) On the Summary & Settings menu, select Dictionaries, and then select Curve Profiles.

4) In the table, select a curve profile.



7) Select Save.




Cost and Funds

Resources

Risk

Schedule

Scope

Evaluation Categories Overview

Define project, program, and idea evaluation categories based off of organizational business drivers. Evaluation categories are grouped into an evaluation matrix, which you can use to rank and assess your projects, programs, and ideas against your company's requirements and standards. In portfolio management, overall project and program evaluation scores are then viewed in the Prioritization Matrix.


170

Add an Evaluation Matrix

There is one evaluation matrix per workspace. The evaluation matrix includes categories and one level of sub-categories under each category. Each category must include at least one sub-category. Add evaluation categories to rank and assess projects, programs, and ideas.

To add an evaluation matrix:



3) On the Summary & Settings menu, select Dictionaries, and then select Evaluation Categories.

4) Select Add.

5) In the new row, complete the following fields for a category:

Name: The name of the evaluation category.

(Optional) Description: Details describing the evaluation category.

Weight: The relative weight of the sibling evaluation node to indicate contribution of a given node to its parent evaluation node.

Weight Percent: The weight or relative rank of the evaluation node compared to its siblings. This value indicates the percentage that the evaluation node is contributing to the parent strategy. The Weight Percent for all sibling evaluation nodes equals 100. This field is read-only.

6) Select the Context menu, and select Add Sub-category.

7) In the new row, complete the same fields for the sub-category.

8) In the Ranks detail window, configure the ranking for the sub-category. A scale is preconfigured for you. Make any of the following modifications:

Scale: Determine how many options are available on the rating scale.

Reverse Ranks Order: Select the icon to reverse the order of the ranks. Weight percentage values remain the same.

Name: Modify the names as needed.

Weight Percent: The weight percentages for the evaluation ranking. The default values are evenly distributed based on the number of selected ranks. You can manually specify different percentage values.

Color: Select a color representing the evaluation ranking.

(Optional) Description: Details describing the rating.

9) Select Save.



Portfolio Analysis

Strategic Alignment


171

Reporting Cycles Overview

The reporting periods for projects are defined by patterns set in reporting cycles. Reporting periods are used as part of the project control process to compare actual progress for scope assignments against the planned progress captured in the project baseline.

Reporting periods for a reporting cycle can be set to occur daily, weekly, semi-monthly, or monthly, depending on the reporting requirements for a project. Each project can have one reporting cycle defined. Factors to be considered when defining reporting cycles include duration, cost, overall risk, and reporting needs of stakeholders involved in the project. For example, if a project is expected to have an overall duration of one month, the reporting period may be daily. In contrast, if a project has an expected duration of five years, then the reporting period may be monthly.

Define a Reporting Cycle

Reporting cycles are defined to create reporting periods which are used to plan and update progress on scope assignments.

Reporting cycles can be set to occur daily, weekly, semi-monthly, or monthly, depending on the reporting requirements for a project.

To define a reporting cycle:



3) On the Summary & Settings menu, select Dictionaries, and then select Reporting Cycles.

4) In the Name field, enter a name for the reporting cycle.

5) Complete the following fields in the Period Pattern section:

Period Frequency: Choose whether the reporting periods should be Daily, Weekly, Semi-Monthly, or Monthly.

A daily cycle begins at 12 a.m. and ends at 11:59 p.m. A semi-monthly cycle includes days 1 through 15 in one period and days 16 through the end of the month in a subsequent period, except for February which ends on day 14 in the first period.

Period End: Select the last day in the reporting period for the cycle when the Period Frequency is set to Weekly or Monthly.

A monthly cycle ending with a Middle of the month setting will end on the 15th, except for February which ends on the 14th.

Base Date: Select the date used as the starting point for generating the period start and end dates in a reporting period.

Prefix: Enter a prefix for the period naming convention label, which is used to distinguish individual time periods when viewing reporting cycles in a time phased view.

Suffix: Enter a numerical suffix for the period naming convention label, which is used to distinguish individual time periods when viewing reporting cycles in a time phased view.

Increment: Select a number to increment the suffix by in each period naming convention label, which is used to distinguish individual time periods when viewing reporting cycles in a time phased view.


172

6) Select Save.


Tips

A reporting cycle cannot be deleted if it is used by a project or inherited by a child workspace.


Scope

Assign a Default Reporting Period

If several projects within a workspace will use the same reporting cycle when reviewing data for reporting periods, you can set a default reporting cycle for all new projects within the workspace to inherit. This can be changed at the project level.

To assign a default reporting period:




4) Locate the reporting cycle.

5) Select Default.

6) Select Save.



Scope

Update the Owning Workspaces of a Reporting Cycle

Update the owning workspace of a reporting cycle to move it to another workspace that you are assigned. If you move a reporting cycle to a workspace that is higher in the workspace hierarchy, it will be available to more workspaces.

To update the owning workspace of a reporting cycle:




4) Select a reporting cycle.



7) Select Save.



173



Resources

Schedule

Scope

Risk Thresholds Overview

Risk thresholds are scales that you define for rating risks in terms of likelihood, cost impact, schedule impact, and any custom impacts you want to define. Each scale comprises a range of values used to delineate different levels of risk that may face the project or program. The risk thresholds are the inputs used to create a risk matrix, the scoring mechanism used to compute risk scores for identified project or program risks.

The risk thresholds that are necessary for a risk matrix are:

Probability: The likelihood of a risk occurring.

Schedule: The amount of time the risk will increase or decrease the project or program schedule, defined as either a percentage of the project's planned duration or as a project or program duration value. Programs do not support relative thresholds, which use percentage values.

Cost: The cost impact if a risk occurs, defined as either a percentage of the project's planned cost or as a monetary value for the project or program. Programs do not support relative thresholds, which use percentage values.

User-defined: Any optional user-defined impacts configured for your workspace, such as safety or environmental impacts. User-defined thresholds use text, rather than quantitative values, to define the impact of the risk.

Add a Risk Threshold Template

Add risk thresholds to define the risk scoring criteria to use for a risk matrix. Risk thresholds are added at the workspace level as templates, making them available to use in child workspaces, projects, and programs. You should add risk threshold templates at a level in your workspace hierarchy where they are available to all workspaces, projects, and programs that will need them. The risk threshold template data is copied to a project or program when a matrix is assigned. You can modify the risk threshold at the project or program level without affecting the template or other projects or programs to which the template is assigned.

To add a risk threshold template:



3) On the Summary & Settings menu, select Dictionaries, and then select Risk Threshold Templates.



Name: Enter a name for the risk threshold.

Type: Select a threshold type:


174

Probability: Measures the likelihood of a risk occurring.

Schedule: Measures the amount of time the risk will increase or decrease the project or program schedule, defined as a duration value.

Cost: Measures the cost impact if a risk occurs, defined as a monetary value.

User: Measures the impact of the risk in terms of a user-defined impact.

Relative Schedule: Measures the amount of time the risk will increase or decrease the project schedule, defined as a percentage of the project's planned duration.

Relative Cost: Measures the cost impact if a risk occurs, defined as a percentage of the project's planned cost.

Notes:

Relative threshold values used by project risk matrixes are unable to be recalculated by program risk matrixes. At the program level, program probability and impact fields for a project risk using relative thresholds will appear blank.

You cannot assign a matrix with relative thresholds to a program.

Relative thresholds cannot be used in quantitative risk analysis.

Number of Levels: Select a number of threshold levels.

6) In the Levels detail window, configure each level defined for the threshold:

Name: Enter a name for the level.

Code: Enter a short name or abbreviation for the level.

Low: Enter a minimum value for the threshold range.

High: Enter a maximum value for the threshold range.

(Optional) Color: Select a color for the threshold level.

7) Select Save.



Risk

Update the Owning Workspace of a Risk Threshold Template

Update the owning workspace of a risk threshold template to move it to another workspace that you are assigned. If you move a risk threshold template to a workspace that is higher in the workspace hierarchy, it will be available to more workspaces.

To update the owning workspace of a risk threshold template:



3) On the Summary & Settings menu, select Dictionaries, and then select Risk Threshold Templates.

4) In the table, select a risk threshold template.


175



7) Select Save.



Risk

Risk Matrixes Overview

The risk matrix is a tool that helps provide a guide for risk assessment using qualitative metrics. A risk matrix includes probability threshold values, cost and schedule impact threshold values, and user-defined threshold values, which are used in the calculation of the risk score. The risk score is a general indicator of the significance of a risk and whether it requires extra attention. You can define separate risk matrixes for projects and programs.

Add a Risk Matrix Template

Add risk matrixes to assess and prioritize project or program risks.

Risk matrixes are added at the workspace level as templates, making them available to use in child workspaces, projects, and programs. You should add risk matrix templates at a level in your workspace hierarchy where they are available to all workspaces and the projects or programs that will need them. When a risk matrix is assigned to a project or a program, the data from template is copied to the project or program. This enables you to modify the project's or program's risk matrix without changing the template or other project or program matrixes to which the template is assigned.

To add a risk matrix template:



3) On the Summary & Settings menu, select Dictionaries, and then select Risk Matrix Templates.



Name: Enter a name for the new matrix.

Matrix Size: This is a read-only field that indicates the number of probability levels and the number of impact levels.

Probability: Select a probability threshold.

Cost Impact: Select a cost threshold.

Schedule Impact: Select a schedule threshold.

(Optional) User Impact: Select one or more user-defined thresholds.

Notes:

All impact thresholds for a risk matrix must contain the same number


176

of levels.

You cannot assign a matrix with relative thresholds to a program.

6) In the Scoring Method column, select one of the following risk scoring methods:

Highest Impact: The overall impact for a risk is set to the highest of all the impacts assigned to the risk.

Average Impact: The overall impact is determined by calculating the average of all impact values.

7) (Optional) In the Description column, enter a summary of the risk matrix.

8) In the Sharing Method list, specify how the data is shared between parent and child workspaces:

Manual: The data can be pulled down by child workspaces individually, using the Assignbutton in each child workspace. This is the default option.


9) Select Save.


Tips

The inputs for the risk matrix are the risk thresholds, which you must add on the Risk Threshold Templates page in the workspace settings.

The Probability and Impact Diagram (PID) is a graphical representation of your risk matrix which is automatically created based upon your threshold selections. Select Settings to modify the PID color settings.


Risk

Configure the Probability and Impact Diagram Settings

The Probability and Impact Diagram (PID) is a graphical representation of your risk matrix template which is automatically created based upon your threshold selections. You can adjust the color settings for the PID to color-code risk scores.

To configure the PID color settings:




4) Select a risk matrix template, and then select the Probability and Impact Diagram detail window.

5) Select Settings.

6) On the Score Colors tab in the Settings dialog box, do the following to define grid colors for the PID:

a. In the Color list, use the picker to select a grid color.


177

b. In the Greater Than Value field, select a risk score value to associate with the selected color.

c. (Optional) To define additional grid colors, select Add, and specify the color settings.

7) Select Apply.

8) Select Save.



Risk

Update the Owning Workspace of a Risk Matrix Template

Update the owning workspace of a risk matrix template to move it to another workspace that you are assigned. If you move a risk matrix template to a workspace that is higher in the workspace hierarchy, it will be available to more workspaces.

To update the owning workspace of a risk matrix template:




4) In the table, select a risk matrix template.



7) Select Save.



Risk

Rules of Credit Overview

Rules of credit can be used when tracking progress on scope assignments. A rule is defined by its milestones and their percentage complete. These rules are used when contracts require certain conditions to be met before a payment is made. The rules are also used when it is necessary to track progress of an assignment at a more detailed level or when there are specific steps that need to be completed to satisfy the scope assignment.

The rules are configurable to meet the needs of the contract or general project statusing requirements. In some cases, it is necessary to track the percentage complete for each milestone. In other cases, it is only important to track whether the milestone is complete.

A rule of credit is set at the scope assignment level when the work package is set to measure progress by Milestone Percent Complete. The milestones defined for the rule of credit are used to show progress.

Rules of credit are typically defined by project managers and cost controls engineers.


178

Add a Rule of Credit

Add rules of credit for tracking progress on scope assignments when the work package progress measure is set to Milestone Percent Complete.

To add a rule of credit:



3) On the Summary & Settings menu, select Dictionaries, and then select Rules of Credit.

4) Select Add.

5) In the Name field, enter the name for the rule of credit.

6) In the Input Type list, choose how to apply the rule of credit:

Manual: Enables users to enter their percentage complete on a milestone. Use this option if it is important to track the percentage complete on a milestone.

0/100 Percent Complete: Enables users to mark a milestone as complete. Use this option if it is important to show whether the work is complete or not complete. A weighted percentage is still applied to enable a percentage complete rollup at the work package level.

7) Use the table to define milestones used to track percentage complete.

a. In the Milestone Name field, enter the name of a milestone.

b. In the Incremental Percent Complete field, enter the percentage each milestone represents for the rule of credit. The Cumulative Percent Complete must equal 100%.

8) Select Save.


Tips

A rule of credit cannot be deleted if it is applied to a work package.


Scope

Update the Owning Workspace of a Rule of Credit

Update the owning workspace of a rule of credit to move it to another workspace that you are assigned. If you move a rule of credit to a workspace that is higher in the workspace hierarchy, it will be available to more workspaces.

To update the owning workspace of a rule of credit:



3) On the Summary & Settings menu, select Dictionaries, and then select Rules of Credit.

4) In the table, select a rule of credit.




179

7) Select Save.




Cost and Funds

Scope

Strategy Types Overview

Strategy types represent corporate-level strategy or goal categories that align with the mission and vision of the organization. For example, types defined could be Business Drivers, Strategic Themes, Objectives, Goals, or Initiatives.

A strategy type is assigned to each strategy defined in the application to determine which projects are aligned with the different strategy types and how they are performing.

Before you add strategies, you should define strategy types.

Add a Strategy Type

Add strategy types that represent corporate-level strategy or goal categories that align with the mission and vision of the organization.

To add a strategy type:



3) On the Summary & Settings menu, select Dictionaries, and then select Strategy Types.

4) In the Name column, enter a name for the strategy type.

5) In the Icon column, select an icon to represent the strategy. This icon displays on the Strategy Scorecard as a visual indicator for the strategy type.

6) Select Save.


Tips

Select Assign to assign strategy types from the parent workspace to the current workspace.

The sequence number determines the order in which strategy types appear for selection when adding strategies in the Strategic Alignment app. To change the order, select the Context menu, and select Move Up or Move Down.


Strategic Alignment


180

Update an Owning Workspace for a Strategy Type

Update the owning workspace of a strategy type to move it to another workspace that you are assigned. If you move the strategy type to a workspace that is higher in the workspace hierarchy, it will be available to more workspaces.

To update the owning workspace of a strategy type:



3) On the Summary & Settings menu, select Dictionaries, and then select Strategy Types.

4) In the table, select a strategy type.



7) Select Save.



Strategic Alignment

Units of Measure Overview

A unit of measure is a standardized way to define how materials or products are measured.

Assigning the unit of measure provides a means to identify how the quantity is evaluated. Units of measure can be defined for material resources, scope items, and actuals line items.

Add a Unit of Measure

Add units of measure labels to assign to material resources, scope items, and actuals line items.

To add a unit of measure:

1) Navigate to the Units of Measure dictionary page (see page 330).

2) In the Abbreviation field, enter a short name or code for the unit of measure.

3) In the Name field, enter the name for the unit of measure.


In Primavera Cloud:

a. Select Save.



Select Save.



Cost and Funds

Resources

Defaults & Options Configuration

181

Risk

Schedule

Scope

Update Owning Workspace of a Unit of Measure

Update the owning workspace of a unit of measure to move it to another workspace that you are assigned. If you move the unit of measure to a workspace that is higher in the workspace hierarchy, it will be available to more workspaces.

To update the owning workspace of a unit of measure:

a) In the object selector, select a workspace.

b) In the sidebar, select Summary & Settings.

1) On the Summary & Settings menu, select Dictionaries, and then select Units of Measure.

2) In the table, select a unit of measure.



5) Select Save.




Cost and Funds

Resources

Risk

Schedule

Scope


Oracle Primavera Cloud enables your organization to define a series of application-wide parameters and values that are available globally and to all projects in a workspace. Use these settings to customize the application to meet specific requirements and standards.

Field Labels Overview

Standard fields are the default fields found in Oracle Primavera Cloud. Fields can be used to store data, provide details, and accept user input. On many pages, fields can be added as columns in a table, used to sort or group data, or used as filters to reduce the number of items displayed on a page. They can also be found in dialog boxes, detail windows, and settings pages. Fields may be associated with a specific object. For example, the activity object is associated with various activity-related fields, such as Start, Finish, and Duration. These fields can be used on pages that support activities.


182

The Field Labels tab in the Defaults & Options section of the workspace Summary & Settings provides the default column name, column label, data type, and description of each field associated with an object. Labels are the field names displayed throughout the application. Default field labels may not reflect the terminology of your organization or industry. You can customize labels to meet the needs of your organization in any of the twelve supported languages.

Oracle Primavera Cloud and Primavera Professional documentation uses default field labels. If you change a field label in the application, it will no longer match the label used in documentation. Modified field labels can be reset back to their defaults.

Access a Standard Field Description

You can view the default column name, column label, data type, and description of any standard field in the application. The column label of each field can be modified to match the terminology used by your organization. Fields are associated with objects and can be used in pages that support that object.

To view the details of a standard field:


2) On the object page, select the Field Labels tab, and view the Column Name, Column Label, Data Type, and Description columns.



Cost and Funds

Field

Files

Lean

Portfolio Analysis

Resources

Risk

Schedule

Scope

Strategic Alignment

Change a Standard Field Label

You can update standard field labels in your native language or update labels in the Localization detail window to customize the field label in other languages. In the table of standard fields, the Column Name field specifies the original field name. The Column Label field specifies the custom label, entered by the user. By default it matches the original field name.


183

Note: Oracle Primavera Cloud documentation uses default field labels. If you follow these steps to change a field label in the application, it will no longer match the label used in documentation.

To change a standard field label:


2) On the object page, select the Field Labels tab.

3) In the table, select a field.

4) In the Column Label field, enter a new label.

5) In the Localization detail window, select the Column Label field of the language, and enter a new label.


In Primavera Cloud:

a. Select Save.



Select Save.

Tips

You can restore the default label of a standard field by selecting the Context menu and then selecting Reset Label.

New child workspaces inherit the field labels set in the parent workspace. To apply field labels to all existing child workspaces, select one or more fields, select the Contextmenu, and then select Apply Label to Child Workspace.



Cost and Funds

Field

Lean

Portfolio Analysis

Resources

Risk

Schedule

Scope

Strategic Alignment

Configured Fields Overview

Configured fields are user-created fields that allow you to define and maintain data specific to your organization. For example, you can track information such as Strategic Importance or Main Stakeholder.


184

Configured fields are created in the context of an object and can be used in views on pages that support that object. For example, you can create an Activity configured field and use it on the Activities page as a column, grouping band, sorting option, or filter criterion. Configured fields are global, so they can be used across all workspaces, projects, portfolios, programs, project collections, and ideas.

Oracle Primavera Cloud fields are categorized by data type, including: Boolean, cost, date, integer, list, number, or text. For some types of data, you can define a formula or statement to calculate values for a field. For more information on creating or using custom formulas, consult the Oracle Primavera Cloud Expression Language Guide on Oracle Help Center.

Documentation on adding a configured field to a specific object can be found under that object.

Add an Activity Field

Add custom activity fields to enable users to enter or view information which is important to your organization.

Note: On pages that support auto-save, configured field formulas will be automatically recalculated when a change is made that impacts the value of a configured field formula. However, there may be times where the recalculation is not updated in the user interface. When this occurs, refresh the page to see the recalculated value.

To add an activity field:

1) Navigate to the Activity configuration page (see page 332).

2) Select the Configured Fields tab.


a. In the Column Label column, enter a name for the new field.

b. In the View Column Name column, enter a name for the field as it will be seen in the database when creating reports.

c. In the Data Type column, select the type for the new field. The choices are: Boolean, Cost, Date, Integer, List, Number, or Text.

d. In the Type column, select Manual if this field will hold data entered by a user or Formula if the data it holds will be calculated on the basis of a formula.

e. (Optional) In the Summary Calculation field, specify how the app calculates summary rollup values for the field.

In most tables where you can view a list of similar objects, you can also view the totals for the various values of these objects. For example, on the Activities table for a project, you can view rollup totals for numerical values like Planned Duration and Planned Labor Units at the top of the table.

The Summary Calculation field enables you to specify how totals are determined for configured fields.

If you selected Cost, Date, Integer, or Number as the Data Type, in the Summary Calculation column, select a simple calculation like Sum or Average, if applicable.


185

Alternatively, if you set the Type field to Formula, you can set the Summary Calculationfield to Use Formula. With this option selected, the app will use the formula defined in the Formula field to determine how the total rollup value is calculated for the field.

f. (Optional) If you selected Text as the Data Type, in the Field Length column, enter the maximum number of characters that can be used in the field.

g. If you selected Formula, configure the Formula section.


In Primavera Cloud:

a. Select Save.



Select Save.

Tips

To delete a configured field, select the field, select Context, and then select Delete. You cannot delete a configured field if it is used in a form, workflow, or field mapping.


Resources

Risk

Schedule

Scope

Add a Budget Field

Add custom project budget fields to enable users to enter or view information which is important to your organization.


To add a project budget field:



3) On the Summary & Settings menu, select Defaults & Options, and then select Budget.

4) On the Defaults & Options: Budget page, select the Configured Fields tab.





186



e. (Optional) If you selected Text as the Data Type, in the Field Length column, enter the maximum number of characters that can be used in the field.

f. If you selected Formula, configure the Formula section.

6) Select Save.


Tips



Cost and Funds

Add a Budget Changes Field

Add custom budget change details fields to enable users to enter or view information which is important to your organization.


To add a budget change detail field:



3) On the Summary & Settings menu, select Defaults & Options, and then select Budget Changes.

4) On the Defaults & Options: Budget Changes page, select the Configured Fields tab.








187


6) Select Save.


Tips



Cost and Funds

Add a Budget Transfers Field

Add custom budget transfer details fields to enable users to enter or view information which is important to your organization.


To add a budget transfer detail field:



3) On the Summary & Settings menu, select Defaults & Options, and then select Budget Transfers.

4) On the Defaults & Options: Budget Transfers page, select the Configured Fields tab.








6) Select Save.



188

Tips



Cost and Funds

Add a Budget Details Field

Add custom budget details fields to enable users to enter or view information which is important to your organization.


To add a budget details field:



3) On the Summary & Settings menu, select Defaults & Options, and then select Budget Details.

4) On the Defaults & Options: Budget Details page, select the Configured Fields tab.








6) Select Save.


Tips



Cost and Funds


189

Add a Changes Field

Add custom changes fields to enable users to enter or view information which is important to your organization.


To add a change field:



3) On the Summary & Settings menu, select Defaults & Options, and then select Changes.

4) On the Defaults & Options: Changes page, select the Configured Fields tab.








6) Select Save.


Tips



Cost and Funds

Add a Company Field

Add custom company fields at the root workspace to enable users to enter or view information which is important to your organization.

Note: On pages that support auto-save, configured field formulas will be automatically recalculated when a change is made that impacts the


190

value of a configured field formula. However, there may be times where the recalculation is not updated in the user interface. When this occurs, refresh the page to see the recalculated value.

To add a company field:

1) In the object selector, select the root workspace.


3) On the Summary & Settings menu, select Defaults & Options, and then select Company.

4) On the Defaults & Options: Company page, select the Configured Fields tab.





d. (Optional) If you selected Text as the Data Type, in the Field Length column, enter the maximum number of characters that can be used in the field.

e. (Optional) If you selected Cost, Date, Integer, or Number as the Data Type, in the Summary Calculation column, select a calculation if applicable.

6) Select Save.


Tips


Add a Change Order Field

Add custom change order fields to enable users to enter or view information that is important to your organization.


To add a change order field:



3) On the Summary & Settings menu, select Defaults & Options, and then select Change Order.

4) On the Defaults & Options: Change Order page, select the Configured Fields tab.



191







6) Select Save.


Tips




Add a Changes Estimates Field

Add custom changes estimates to enable users to enter or view information which is important to your organization.


To add a change estimate field:



3) On the Summary & Settings menu, select Defaults & Options, and then select Changes Estimates.

4) On the Defaults & Options: Changes Estimates page, select the Configured Fields tab.






192




6) Select Save.


Tips



Cost and Funds

Add a Commitment Field

Add custom commitment fields to enable users to enter or view information that is important to your organization.


To add a commitment field task:



3) On the Summary & Settings menu, select Defaults & Options, and then select Commitment.

4) On the Defaults & Options: Commitment page, select the Configured Fields tab.








6) Select Save.


193


Tips




Add a Contract Field

Add custom contract fields to enable users to enter or view information that is important to your organization.


To add a contract field:



3) On the Summary & Settings menu, select Defaults & Options, and then select Contract.

4) On the Defaults & Options: Contract page, select the Configured Fields tab.








6) Select Save.


Tips



194



Add a File Field

Add custom file fields to enable users to enter or view information which is important to your organization.

To add a file field:



3) On the Summary & Settings menu, select Defaults & Options, and then select File.

4) On the Defaults & Options: File page, select the Configured Fields tab.





6) Select Save.


Tips




Cost and Funds

Field

Files

Lean

Portfolio Analysis

Resources

Risk

Schedule

Scope

Strategic Alignment

Submittals


195

Add a Fund Field

Add custom fund fields to enable users to enter or view information which is important to your organization.


To add a workspace fund field:



3) On the Summary & Settings menu, select Defaults & Options, and then select Fund.

4) On the Defaults & Options: Fund page, select the Configured Fields tab.








6) Select Save.


Tips



Cost and Funds

Add an Idea Field

Add custom idea fields to enable users to enter or view information that is important to your organization.

To add an idea field:



196


3) On the Summary & Settings menu, select Defaults & Options, and then select Idea.

4) On the Defaults & Options: Idea page, select the Configured Fields tab.






6) Select Save.


Tips


Add a Payment Application Field

Add payment application fields to enable users to enter or view information that is important to your organization.




3) On the Summary & Settings menu, select Defaults & Options, and then select Payment Application.

4) On the Defaults & Options: Payment Application page, select the Configured Fields tab.








197


6) Select Save.


Tips




Add a Portfolio Field

Add custom portfolio fields to enable users to enter or view information which is important to your organization.


To add a portfolio field:



3) On the Summary & Settings menu, select Defaults & Options, and then select Portfolio.

4) On the Defaults & Options: Portfolio page, select the Configured Fields tab.








6) Select Save.


Tips



198


Portfolio Analysis

Add a Potential Change Order Field

Add custom potential change order fields to enable users to enter or view information which is important to your organization.


To add a potential change order field:



3) On the Summary & Settings menu, select Defaults & Options, and then select Portfolio.

4) On the Defaults & Options: Potential Change Order page, select the Configured Fieldstab.








6) Select Save.


Tips



Portfolio Analysis


199

Add a Project Field

Add custom project fields to enable users to enter or view information which is important to your organization.


To add a project field:

1) Navigate to the Project configuration page (see page 332).















In Primavera Cloud:

a. Select Save.



Select Save.


200

Tips


You can select up to five fields to use in the Field app from the root workspace.



Cost and Funds

Field

Files

Lean

Portfolio Analysis

Resources

Risk

Schedule

Scope

Strategic Alignment

Submittals

Add a Project Actuals Field

Add custom project budget fields to enable users to enter or view information which is important to your organization.


To add a project budget field:



3) On the Summary & Settings menu, select Defaults & Options, and then select Project Actuals.

4) On the Defaults & Options: Project Actuals page, select the Configured Fields tab.






201




6) Select Save.


Tips



Cost and Funds

Add a Project Cost Sheet Field

Add custom project cost sheet fields to enable users to enter or view information which is important to your organization.


To add a project cost sheet field:



3) On the Summary & Settings menu, select Defaults & Options, and then select Project Cost Sheet.

4) On the Defaults & Options: Project Cost Sheet page, select the Configured Fields tab.








202







6) Select Save.


Tips



Cost and Funds

Add a Resource Assignment Field

Add custom resource assignment fields to enable users to enter or view information which is important to your organization.


To add a resource assignment field:

1) Navigate to the Resource Assignment configuration page (see page 332).







203










In Primavera Cloud:

a. Select Save.



Select Save.

Tips



Resources

Risk

Schedule

Add an RFI Field

Add custom RFI fields to enable users to enter or view information that is important to your organization.


204


To add an RFI field:



3) On the Summary & Settings menu, select Defaults & Options, and then select RFI.













6) If you selected Formula, configure the Formula section.

7) Select Save.


Tips



205


Field

Add a Risk Field

Add custom risk fields to enable users to enter or view information which is important to your organization.


To add a risk field:



3) On the Summary & Settings menu, select Defaults & Options, and then select Risk.

4) On the Defaults & Options: Risk page, select the Configured Fields tab.













6) Select Save.


206


Tips



Risk

Schedule

Add a Scope Assignment Field

Add custom scope assignment fields to enable users to enter or view information which is important to your organization.


To add a scope assignment field:



3) On the Summary & Settings menu, select Defaults & Options, and then select Scope Assignment.

4) On the Defaults & Options: Scope Assignment page, select the Configured Fields tab.











207




6) Select Save.


Tips



Scope

Add a Scope Item Field

Add custom scope item fields to enable users to enter or view information which is important to your organization.


To add a scope item field:



3) On the Summary & Settings menu, select Defaults & Options, and then select Scope Item.

4) On the Scope Item page, select the Configured Fields tab.








208







6) Select Save.


Tips



Scope

Add a Strategy Field

Add custom strategy fields to enable users to enter or view information which is important to your organization.


To add a strategy field:



3) On the Summary & Settings menu, select Defaults & Options, and then select Strategy.

4) On the Defaults & Options: Strategy page, select the Configured Fields tab.





209





6) Select Save.


Tips



Strategic Alignment

Add a Submittal Field

Add custom submittal fields to enable users to enter or view information that is important to your organization.


To add a submittal field:



3) On the Summary & Settings menu, select Defaults & Options, and then select Submittal.

4) On the Defaults & Options: Submittal page, select the Configured Fields tab.








210






6) If you selected Formula, configure the Formula section.

7) Select Save.


Tips



Submittals

Add a Task Field

Add custom task fields to enable users to enter or view information which is important to your organization.

To add a task field:



3) On the Summary & Settings menu, select Defaults & Options, and then select Task.

4) On the Defaults & Options: Task page, select the Configured Fields tab.






6) Select Save.



211

Tips



Lean

Add a WBS Field

Add custom WBS fields to enable users to enter or view information which is important to your organization.


To add a WBS field:

1) Navigate to the WBS configuration page (see page 333).















212


In Primavera Cloud:

a. Select Save.



Select Save.

Tips



Resources

Risk

Schedule

Scope

Add a Work Package Field

Add custom work package fields to enable users to enter or view information which is important to your organization.


To add a work package field:



3) On the Summary & Settings menu, select Defaults & Options, and then select Work Package.

4) On the Defaults & Options: Work Package page, select the Configured Fields tab.








213







6) Select Save.


Tips



Schedule

Scope

Add a Workspace Cost Sheet Field

Add custom workspace cost sheet fields to enable users to enter or view information which is important to your organization.


To add a workspace cost sheet field:



3) On the Summary & Settings menu, select Defaults & Options, and then select Workspace Cost Sheet.

4) On the Defaults & Options: Workspace Cost Sheet page, select the Configured Fieldstab.




214






6) Select Save.


Tips




Cost and Funds

Change a Configured Field Label

You can update configured field labels in your native language or update labels in the Localization detail window to customize the field label in other languages. In the table of configured fields, the View Column Name field specifies the original field name. The Column Label field specifies the custom label, entered by the user. By default it matches the original field name.

To change a configured field label:


2) On the object page, select the Configured Fields tab.

3) In the table, select a field.

4) In the Column Label field, enter a new label.

5) In the Localization section, select the Column Label field of the language, and enter a new label.


In Primavera Cloud:

a. Select Save.



Select Save.


215

Tips

You can restore the default label of a configured field by selecting the Context menu and then selecting Reset Label.

New child workspaces inherit the field labels set in the parent workspace. To apply field labels to all existing child workspaces, select one or more fields, select the Contextmenu, and then select Apply Label to Child Workspace.



Cost and Funds

Field

Files

Lean

Portfolio Analysis

Resources

Risk

Schedule

Scope

Submittals

Add a Formula-Based Configured Field: Example

This example demonstrates how to create a configured field to calculate and store the Estimated Final Cost of a project.

Let us assume that you will define the Estimated Final Cost of a project as Approved Budget plus Proposed Budget.

Creating a Configured Field


2) On the Project page, select Configured Fields.

3) In the table, complete the following fields:

a. In the Column Label column, enter Estimated Final Cost.

b. In the View Column Name column, enter EST_FINAL_COST.

c. In the Data Type column, select Cost.

d. In the Type column, select Formula.

e. In the Summary Calculation column, select Sum.

Defining a Formula

1) In the Formula detail window, in the Field list, select Approved Budget, and select Insert Field.

2) Select +.

3) In the Field list, select Proposed Budget, and select Insert Field.


216

4) Select Validate Formula.

5) In the Formula validation passed dialog box, select OK.


In Primavera Cloud:

a. Select Save.



Select Save.

Tips


Update the Owning Workspace of a Configured Field

Update the owning workspace of a configured field to move it to another workspace that you are assigned. If you move the field to a workspace that is higher in the workspace hierarchy, it will be available to more workspaces.

To update the owning workspace of a configured field:


2) On the object page, select the Configured Fields tab.

3) On the Configured Fields tab, select Manage Shared Data.




In Primavera Cloud:

a. Select Save.



Select Save.



Cost and Funds

Field

Files

Lean

Portfolio Analysis

Resources

Risk

Schedule


217

Scope

Strategic Alignment

Submittals

Defaults for Workspaces Overview

Configure defaults at the workspace level to define the defaults of the projects of that workspace. You can customize any defaults at the project level if a project will not follow the defaults of the workspace. You should create defaults in the workspace before creating any projects. Projects that were created prior to setting defaults will not follow the defaults of the workspace. They will retain their original project defaults.

Set the Details Page for Projects

By default, the Details page shows basic information about the project. But you can replace the default Details page for all projects in a workspace with a custom form designed in the Form Editor.

Before you can set a custom Details page, you must have access to a published form that has a Context Type value of Project.

To choose a form as the Details page for all projects in a workspace:


2) Select the Forms tab.

3) In the Project Details Form row, in the Form field, select the form that you want to use instead of the default Details page.

4) Select Save.

5) In the Inherit Form Mapping dialog box, select Yes or No.

If the current form is already assigned in child workspaces, select Yes if you want to replace it with the new one. Otherwise, select No.


Now users who open the Details page for any project in this workspace will see the form you chose here, not the default Details page.

Configure Default Activity Settings for a Workspace

You can configure default system behavior for activities in a workspace.

To configure default activity settings for a workspace:


2) Select the Defaults tab.

3) In the New Activities section, configure default behavior for new activities:

Duration Type: Determines how remaining duration, units, and units/time are calculated when you update an activity that has resources assigned.


218

Fixed Units/Time: The resource units per time are constant when the activity duration or units are changed. Use this duration type when an activity has fixed resources with fixed productivity output per time period.

Fixed Units: The activity units are constant when the duration or resource units per time are changed. Use this duration type when the total amount of work is fixed, and increasing the resources can decrease the activity duration.

Fixed Duration & Units: The duration and units remain constant as the units/time is changed. Use this duration type when the activity must be completed within a fixed time period and the total amount of work is fixed.

Fixed Duration & Units/Time: The activity duration is constant as the units or resource units per time are changed. Use this duration type when the activity must be completed within a fixed time period regardless of the resources assigned.

Percent Complete Type: Determines the way in which the application calculates the percent complete for the activity. The type can be Physical, Duration, Units, or Scope.

Physical: The user will enter the percent complete for the activity.

Duration: The percent complete is calculated from the actual and remaining duration.

Units: The percent complete is calculated from the actual and remaining units.

Scope: The percent complete for the activity is derived from the scope percent complete of the linked scope assignment.

Activity Type: Determines how duration and schedule dates are calculated for the activity.

Activity Dependent: This type of activity indicates that assigned resources should be scheduled based on the activity's calendar, rather than the calendars of the resources.

Resource Dependent: This type of activity indicates that resources should be scheduled based on their assigned calendars. Use this type when the activity duration may be affected by resource availability.

Level of Effort: This type of activity indicates that it is ongoing with a duration determined by its dependent activities. The duration is calculated based on the schedule dates of its predecessors and successors. Administrative activities are typically designated as Level of Effort.

Start Milestone: This type of activity indicates the beginning of an important project phase. Activities of this type have a duration of zero (0) with no resource assignments.

Finish Milestone: This type of activity indicates the end of an important project phase. Activities of this type have a duration of zero (0) with no resource assignments.

Default duration for new activities: Enter the default time duration, in hours, for new activities.

Increment Activity ID based on selected activity: When disabled, new activity IDs follow the activity auto numbering rules set in the project settings. When enabled, new activity IDs are numbered based on the ID of the activities selected when the new activities are added. See Add an Activity for more information.

4) In the New Assignments section, configure default behavior for new activity assignments:


219

Drive activity dates by default: Determines whether new resource or role assignments drive activity dates by default.

Resource can be assigned to same activity more than once: Determines whether activities can be assigned to the same resource multiple times.

When adding or removing multiple resource assignments on activities: Select an option to determine application behavior when activity resource assignments are adjusted:

Preserve the Units, Duration and Units/Time for existing assignments: Select this option for units, durations, and units/time to remain constant when additional resources are assigned to any activity.

Recalculate the Units, Duration and Units/Time for existing assignments based on the activity Duration Type: Select this option to calculate a resource assignment’s remaining values based on the activity’s duration type.


In Primavera Cloud:

a. Select Save.



Select Save.


Resources

Risk

Schedule

Scope

Configure Default Activity Calculation Settings for a Workspace

You can configure default activity calculation settings for workspaces to specify how the application computes values for activities within that workspace.

To configure default activity calculation settings for workspaces:



3) In the Calculations section, under Activities, configure calculation settings for project activities:

When changing an activity to not started: Determines how units and duration are handled if activity progress is removed.

Reset planned duration and units to remaining: Select this option to reset planned unit spreads to match the remaining units.

Reset remaining duration and units to planned: Select this option to reset remaining unit spreads to match the planned units.


220

Link planned and remaining/at completion for not started activities: Determines whether to recalculate all of the planned unit and cost values using the remaining costs and units for activities that have not started.

Define critical activities as: Select a method to identify critical activities:

Total Float less than or equal to: Select this option to identify critical activities based on the lack of flexibility in their scheduled dates. Enter a minimum float duration. When the project is scheduled, activities with total float values less than or equal to this value are marked critical.

Longest Path: Select this option to define critical activities based on the sequence of driving activities that determine the project end date.

4) In the Units section, configure calculation settings for units:

When updating units: Determines how the application handles changes to units.

Add actual to remaining: Select this option to calculate a new at completion value when the remaining units or actual units change.

Subtract actual from at completion: Select this option to calculate a new remaining units value when the at completion or actual units change.

Recalculate actual units when Duration % Complete changes: Select this option to recalculate actual units when the duration percent complete is updated.

5) In the Scope Items section, select a default method for calculating scope completion percentages. Scope completion percentage can be calculated using cost, quantity, hours, or manually entered values.


In Primavera Cloud:

a. Select Save.



Select Save.


Resources

Risk

Schedule

Scope

Set the Default Calendar

The default calendar is set in the workspace-level Calendars dictionary and is available to projects, resources, and roles within that workspace. One calendar must always be defined as the default.


221

Notes:

The application has a built-in default calendar. The settings in this calendar cannot be changed. After another calendar has been assigned as the default, this calendar can be deleted.

You can also set the default calendar on the Project page in Defaults & Options. You can choose from a list of calendars that are available to the Project object.

To set the default calendar:


2) In the list of calendars, select the Default option for the calendar.


In Primavera Cloud:

a. Select Save.



Select Save.

Tips

If the calendar you selected was only available to Project or Resource/Role, then both options are automatically selected when you select a new default calendar.



Cost and Funds

Lean

Resources

Risk

Schedule

Scope

Set the Default Print Layout for a Workspace or Project

Before you can print a print layout report, you must set a default print layout for your object at the workspace or project level. Setting a default print layout at the workspace level affects all child workspaces and projects that do not have a default. Default print layouts set at a child workspace or project level will not be overwritten if changes are made at a higher level. Each of the objects compatible with print layouts can be assigned a different print layout.

The following objects support print layouts:

Change Orders

Commitments

Contracts


222

Payment Applications

RFIs

Submittals

To set a default print layout for a workspace (Primavera Cloud only):



3) On the Summary & Settings menu, select Defaults & Options, and then select an object.


5) In the Print Layout section, in the Default field, select a print layout.

6) Select Save.


To set a default print layout for a project:

1) Navigate to the project settings page (see page 328).

2) Select the Print Layouts tab.



Field

Reports

Submittals

Set the Default My Activities Settings

You can configure default My Activities settings for a workspace to determine how users update their project activities for any project in that workspace by default.

To configure default My Activities settings for a workspace:



3) In the Team members are assigned to activities as section, select a method for how team members are assigned to activities.

Resource Assignments: Each user who is assigned a resource assignment can view that assignment and update its progress.

Activity Owners: Each user who is assigned to an activity as its Owner can view the activity and update its progress.

Both: Resource assignments can view and update their assignments, and activity owners can view and update their activities. Users who have activities and resource assignments will see entries for both.

4) In the Select the fields team members can update section, add the fields you want team members to view and use to update their progress.

Assignment Fields: Add the fields you want team members assigned as resource assignments to use to status their activities.


223

Activity Fields: Add the fields you want team members assigned as activity owners to use to status their activities. If a team member who owns an activity also has a resource assignment for that activity, then the team member will be able to view and update both the assignment and the activity.

Codes and Configured Fields: Add codes and configured fields that you want activity owners or resource assignment performers to view or use to update their activities. To make any code or configured field read-only, select Read Only by the field. In order for a user to update Cost-type codes or configured fields, the user needs the Project Costs/Financials privilege on the project.

(Optional) Select Team member can update progress of other resource assignments on activity if you want activity owners to be able to update the progress of all resource assignments for their activities.


In Primavera Cloud:

a. Select Save.



Select Save.


Cost and Funds

Lean

Resources

Risk

Schedule

Scope

Configure Auto Numbering Defaults for Budget Changes

Unique IDs are required for objects in the application. The IDs are automatically generated based on the default values set for prefix, starting number, and increment. You can use the defaults set in the application or enter values that represent your numbering system. Setting these at the workspace level will apply the defaults to all projects or programs within the workspace. Defaults can be updated at the project or program level.

To set the auto numbering defaults:



3) On the Summary & Settings menu, select Defaults & Options, and then select Budget Changes.

4) On the Defaults & Options: Budget Changes page, select the Defaults tab.

5) In the Auto Numbering section, define the auto numbering default values.

6) Select Save.



224


Cost and Funds

Configure Auto Numbering Defaults for Budget Transfers





3) On the Summary & Settings menu, select Defaults & Options, and then select Budget Transfers.

4) On the Defaults & Options: Budget Transfers page, select the Defaults tab.


6) Select Save.



Cost and Funds

Configure Auto Numbering Defaults for a Change Order





3) On the Summary & Settings menu, select Defaults & Options, and then select Change Order.

4) On the Defaults & Options: Change Order page, select the Defaults tab.


6) Select Save.





225

Configure Auto Numbering Defaults for a Change





3) On the Summary & Settings menu, select Defaults & Options, and then select Changes.

4) On the Defaults & Options: Changes page, select the Defaults tab.


6) Select Save.




Configure Auto Numbering Defaults for a Commitment





3) On the Summary & Settings menu, select Defaults & Options, and then select Commitment.

4) On the Defaults & Options: Commitment page, select the Defaults tab.


6) Select Save.





226

Configure Auto Numbering Defaults for a Contract





3) On the Summary & Settings menu, select Defaults & Options, and then select Contract.

4) On the Defaults & Options: Contract page, select the Defaults tab.


6) Select Save.




Configure Auto Numbering Defaults for Ideas

Unique IDs are required for objects in the application. The IDs are automatically generated based on the default values set for prefix, starting number, and increment. You can use the defaults set in the application or enter values that represent your numbering system.

To set the auto numbering defaults for ideas:



3) On the Summary & Settings menu, select Defaults & Options, and then select Idea.

4) On the Defaults & Options: Idea page, select the Defaults tab.


6) Select Save.


Configure Auto Numbering Defaults for a Payment Application





227


3) On the Summary & Settings menu, select Defaults & Options, and then select Payment Application.

4) On the Defaults & Options: Payment Application page, select the Defaults tab.


6) Select Save.




Adjust the Default Retainage Percentage for Payment Applications

Retainage is the percentage of a payment that is withheld until a job is fully complete.

When you add a payment application, you can adjust the retainage for each payment, but you can also adjust the default retainage percentage for every new payment application in a workspace.

To adjust the default retainage percentage:



3) In the Defaults & Options list, select Payment Application.


5) In the Retainage field, enter the new default retainage rate.

6) Select Save.

Adjust the Default Period To Value for Payment Applications

The Period To value is the billing period of a payment application.

When you add a payment application, you can adjust the period to value for each payment, but you can also adjust the default period to value for every new payment application in a workspace.

To adjust the default Period To value:



3) In the Defaults & Options list, select Payment Application.


5) In the Period To field, enter the new default retainage rate.

6) Select Save.


228

Configure Auto Numbering Defaults for a Project Actual





3) On the Summary & Settings menu, select Defaults & Options, and then select Project Actuals.

4) On the Defaults & Options: Project Actuals page, select the Defaults tab.


6) Select Save.



Cost and Funds

Configure Auto Numbering Defaults for a Risk





3) On the Summary & Settings menu, select Defaults & Options, and then select Risk.

4) On the Defaults & Options: Risk page, select the Defaults tab.

5) In the Auto Numbering section, define the auto numbering default values for project or program risks.

6) Select Save.



Risk

Schedule


229

Configure Auto Numbering Defaults for a Scope Change Request





3) In the Auto Numbering section, define the auto numbering default values for Change Request and Change Item.


In Primavera Cloud:

a. Select Save.



Select Save.

Tips

Users can manually overwrite the default values when adding these objects in the application.


Scope

Configure Auto Numbering Defaults for a Scope Assignment





3) On the Summary & Settings menu, select Defaults & Options, and then select Scope Assignment.


5) In the Scope Assignment section, define the auto numbering default values.

6) Select Save.



230

Tips



Scope

Configure Auto Numbering Defaults for a Scope Item





3) On the Summary & Settings menu, select Defaults & Options, and then select Scope Item.


5) In the Scope Items section, define the auto numbering default values.

6) Select Save.


Tips


When importing scope items, if the ID column in the import template is left blank, the Scope Item ID fields are populated with the auto numbering defaults.


Scope

Configure Auto Numbering Defaults for a Potential Change Order






231

3) On the Summary & Settings menu, select Defaults & Options, and then select Potential Change Order.

4) On the Defaults & Options: Potential Change Order page, select the Defaults tab.


6) Select Save.




Configure Auto Numbering Defaults for a Task





3) On the Summary & Settings menu, select Defaults & Options, and then select Task.

4) On the Defaults & Options: Task page, select the Defaults tab.


6) Select Save.



Lean

Configure Auto Numbering Defaults for Work Packages





3) On the Summary & Settings menu, select Defaults & Options, and then select Work Package.


5) In the Work Packages section, define the auto numbering default values.


232

6) Select Save.


Tips



Schedule

Scope

Assign a Custom Workflow at the Workspace Level

In the Workflows and Forms app, you can create custom workflows that let you specify exactly how these objects are managed:

Budgets

Budget changes

Budget transfers

Changes

Change orders

Commitments

Contracts

Ideas


Projects

RFIs

Project Risks

Submittals

After you have created a custom workflow, you can assign it to an object and action at the workspace level to have your custom workflow run every time the action occurs in a project within the workspace.

Note: In order for workspace-level workflow assignments to take effect in projects, you must have the privileges required to edit the projects. Similarly, in order for workspace-level workflow assignments to take effect in child workspaces, the corresponding workflows must be shared with the child workspaces.

To assign a custom workflow at the workspace level:


2) On the Workflow Actions tab, find the row that represents the action to which you want to assign the custom workflow.

3) In the corresponding Workflow field, choose a custom workflow.

Integration Overview

233

Only forms with the relevant Context Type value are available here. For example, you can only assign a Risk workflow to manage risks.


In Primavera Cloud, select Save.

In Primavera Professional, select Save.

5) In the Confirm dialog box, select Yes if you want all workspaces, projects, and programs within the workspace to inherit the selected workflow, if applicable.

6) In Primavera Cloud, in the Summary & Settings panel, select Close.


Connections

Application administrators set up connections with external products using the Integration page of the Global Admin settings. Each connection is assigned to one or more workspaces. The application administrator also determines what business flows will be available for each connection. The selected business flows are only available for the workspaces associated with the connection.

Primavera Cloud supports the following connections:

P6 EPPM

Primavera Gateway

Microsoft Project

To learn more about supported product versions, consult the Client System Requirementsdocument available on Oracle Help Center(https://docs.oracle.com/cd/E80480_01/index.htm).

Note: When project data is imported into Oracle Primavera Cloud from P6 EPPM, it is recommended that you reschedule the project before making any project updates.

Business Flows

Primavera Cloud connections provide default business flows that determine how your Primavera Cloud data is mapped to fields and data types in external applications. For example, the default P6 EPPM integration business flow, Send Primavera Cloud project data to P6, maps the Primavera Cloud project Planned Finish Date field to the P6 EPPM Must Finish By Date field to maintain your project data in both applications. To learn more about default project and workspace business flows, see Default Business Flow Reference (on page 244).

https://docs.oracle.com/cd/E80480_01/index.htm


234

Synchronize and Monitor

You can run business flows available for a workspace or project at any time using the Synchronize page of the Integration app. The list of available business flows depends on how your application administrator has configured integration connections. After you have initiated a business flow, you can monitor its progress, check for errors, and view detailed information about the data it sends and receives on the Monitor page.

Integrated Objects

Objects integrated using the application REST API can only be modified using the REST API and cannot be updated using the user interface. The Imported Object icon indicates objects that follow these restrictions.

To learn more about which objects can be integrated using the REST API, consult the REST API documentation on Oracle Help Center (https://docs.oracle.com/cd/E80480_01/index.htm).

Integrate P6 EPPM

Integrate P6 EPPM with Primavera Cloud to synchronize project data, such as resources, activities, and budget dates, between the two applications.

To set up a P6 EPPM integration:

1) Add a P6 EPPM Connection (on page 235)

2) Enable or Disable a P6 EPPM Business Flow (on page 236)

P6 EPPM Default Business Flow Reference (on page 244)

Modify business flows to customize the data synchronized between P6 EPPM and Primavera Cloud for each business flow:

Modify a P6 EPPM Business Flow (on page 237)

You can also modify advanced settings to set the authentication method of the connection and encrypt data transfers between Primavera Cloud and P6 EPPM:

Modify P6 EPPM Integration Advanced Settings (on page 235)

Data sent from a source application is tracked by a flow using cross-references. You can delete the history of all data sent and received using a specific P6 EPPM connection by deleting cross-references. Use this option only if you want to reset all cross-references related to this connection, and want all data to be regarded as new data by the destination application when you run the next flow.

Delete Cross-references for a P6 EPPM Connection (on page 238)

Note: You can also delete cross-references for a specific job from the Monitoring page.

https://docs.oracle.com/cd/E80480_01/index.htm


235

Add a P6 EPPM Connection

Add a P6 EPPM connection to synchronize Primavera Cloud and P6 EPPM projects. Import project data from P6 EPPM to Primavera Cloud, or export Primavera Cloud project data to P6 EPPM.

To add a P6 EPPM connection:


2) In the sidebar, select Integrations.

3) In the P6 EPPM tile, select Integrate.

4) Select the Connect tab, and then select Add Connections.


What do you want to name your connection?: A unique name for this P6 EPPM connection.

Server URL: The URL, in the form of http://<server>:<port>/p6ws/services/SyncServiceV1 on which your P6 EPPM instance is hosted.

Username: The username of a user you want to use to connect to P6 EPPM when running synchronizations.

Password: The password for the user specified in the Username field.

Workspace: Select one or more Primavera Cloud workspaces to which this connection applies. Data from this P6 EPPM connection can only be synchronized with projects in the selected workspaces.

6) Select Test Connection. If the connection fails, verify that the connection information you entered is correct.

7) Expand business flow sections, such as Global or Project, to view a list of synchronization options available for this connection. Select or deselect business flows to enable or disable them for the workspaces associated with this connection.

8) Select Save.

Modify P6 EPPM Integration Advanced Settings

Modify P6 EPPM connection Advanced Settings to configure additional properties of your P6 EPPM connection, such as the P6 Webservices authentication type, P6 database ID, P6 Currency, and encryption options.

To modify advanced settings:




4) Select the Connect tab.

5) Select a P6 EPPM connection, and then expand Advanced Settings.



236

P6 Webservices authentication type: Determines the method of authentication used for this connection.

(Optional) SAML2.0 token file: If the selected P6 Webservices authentication type is SAML2.0 Token, select and upload a SAML2.0 token file to use to authenticate the connection.

P6 database instance ID: The ID of the P6 EPPM instance database used by this connection. If your P6 EPPM instance supports multiple databases, select the database that contains the project and global data you want to synchronize with Primavera Cloud.

P6 Currency: The currency type in the P6 EPPM instance.

7) Select Enable Encryption to encrypt data exchanged between Primavera Cloud and P6 EPPM using a Java keystore.


Keystore File: Select and upload a Java keystore (.jks) file to use to encrypt data transfers for this connection.

Keystore Password: If your Java keystore is password protected, enter the password required to use the keystore.

Certificate Alias: The alias used to access the provided Java keystore.

9) Select Save.

Notes:

If SAML2.0 Token is selected as the P6 Webservices authentication type, a SAML2.0 token file will be used to authenticate the connection instead of the password field.

To learn more about generating a Java keystore of SAML2.0 Token file for P6 EPPM, see P6 EPPM Documentationhttps://docs.oracle.com/en/industries/construction-engineering/primavera-p6-eppm/index.html

Enable or Disable a P6 EPPM Business Flow

You can enable or disable business flows for your P6 EPPM connections.

To enable or disable business flows:




4) Select the Connect tab, and then select a P6 EPPM connection.

5) Expand business flow sections, such as Global or Project.

6) Select the business flows to enable.

7) Select Save.

Tips

Select the option in the business flow table header to enable or disable all business flows in the table.

https://docs.oracle.com/en/industries/construction-engineering/primavera-p6-eppm/index.html

https://docs.oracle.com/en/industries/construction-engineering/primavera-p6-eppm/index.html


237

Modify a P6 EPPM Business Flow

You can modify business flows for your P6 EPPM connection.

To modify a business flow:





5) Expand a business flow section, such as Global or Project.

6) In the table, select the name of a business flow.

Note: You can only select the name of a business flow if it is enabled. To learn more about enabling and disabling business flows, see Enable or Disable a P6 EPPM Business Flow (on page 236)

7) In the business flow dialog box, on the Mappings tab, select an object row, select the Context menu, and then select Add field.

8) In the Primavera Cloud Field Name column, select a Primavera Cloud field.

9) In the P6 Field Name column, select a P6 EPPM field to synchronize with the selected Primavera Cloud field.

10) Select the Parameters tab.

11) In the Source Parameters section, select or deselect parameters, if available, to apply them to the business flow.

Calendar Filter: Enter the name of one or more global or resource calendars to integrate. Enter multiple values as comma-separated values or use % to select all calendars.

Summarize Project(s) before synchronization?: Select this parameter if you want to summarize projects before running a synchronization.

12) In the Destination Parameters section, select or deselect parameters, if available, to apply them to the business flow.

Compare Flag: Select this parameter if you want to compare the source and destination data to identify changed, deleted, and added objects so that the system can synchronize data efficiently.

Delete data that no longer exists in the source application?: Select this parameter if you want to delete data from the destination application if it no longer exists in the source application. Use this parameter in conjunction with the Compare Flag.

EPS Location: Enter the name of the EPS node of the project when it is transferred to P6 EPPM.

13) Select the Add field tab to add new objects and fields to the business flow.


Object: The primary object associated with the field you want to add to the business flow.

Name: The name of the field.


238

Type: The type of data stored in the field. Valid values are String, Int, Double, Boolean, and DateTime.

Category: The category to which the field belongs. The following values are valid categories:

Code: Defines the field as a code on the selected object.

UDF: Defines the field as a configured field on the selected object.

Note: An additional category for capturing additional information during synchronization.

Description: A short summary of the fields purpose.

15) Select Add.

16) Select Save, and then select Close.

Delete Cross-references for a P6 EPPM Connection

Primavera Cloud tracks data using cross-references between P6 EPPM and Oracle Primavera Cloud. It is used by the application to determine if the data is to be regarded as new data or an update to previously sent data. When you delete cross-references, you are deleting the history of all data sent to the destination application using this connection.

To delete all cross-references for a P6 EPPM connection:





5) Select Delete cross-reference.

6) Select Yes on the Confirmation dialog box.

Note: You are only deleting the cross-references of the data, not the data itself. Data sent previously using these cross-references will continue to exist in the destination application.

Integrate Gateway

Integrate Primavera Cloud and Gateway to synchronize Primavera Cloud data with data from external providers.

To set up Gateway integration:

1) Add a Gateway Connection (on page 239)

2) Add Gateway Synchronizations (on page 239)


239

Add a Gateway Connection

Set up a Gateway connection to integrate Primavera Cloud with an instance of Gateway and set Primavera Cloud business flows between Primavera Cloud and other providers configured in Gateway.

To add a Gateway connection:



3) In the Oracle, Gateway tile, select Integrate.



Server URL: The URL, in the form of http://<server>:<port>/gatewayapi, on which your Gateway instance is hosted.

Username: The username of a user you want to use to connect to Gateway when running synchronizations.

Password: The password for the user specified in the Username field.

Primavera Cloud Deployment Name: The name of the Primavera Cloud deployment to which this connection applies. The Gateway connection can only be used to transfer data from or to the selected Primavera Cloud deployment.

6) Select Test Connection. If the connection fails, verify that the connection information you entered is correct.

7) Select Save.

Note: If a workspace is assigned to a P6 EPPM connection, the P6 EPPM connection business flows will override any P6 EPPM synchronizations defined in Gateway.

Add Gateway Synchronizations

Add synchronizations to your Gateway connection to provide business flows users can run to synchronize Primavera Cloud data with external providers configured through Gateway.

To add a Gateway synchronization:



3) In the Oracle, Gateway tile, select Integrate.

4) Select the Connect tab, and then select Add.

5) In the Add Synchronization dialog box, select one of the following options:

Import: This synchronization will import data into Primavera Cloud from an external application.

Export: This synchronization will export data from Primavera Cloud to an external application.

6) In the Type list, select a type for the synchronization.


240

7) In the Synchronization Name list, select a synchronization.

8) Select Add.

9) Select Save.

Note: Only synchronizations configured in Gateway are available for selection as synchronizations in Primavera Cloud. To create business flows for use in your Primavera Cloud and Gateway connection, you must add synchronizations in Gateway. To learn more about Gateway synchronizations see Gateway Documentationhttps://docs.oracle.com/en/industries/construction-engineering/primavera-gateway/index.html

Integrate Microsoft Project

Integrate Microsoft Project with Primavera Cloud to synchronize project data, such as resources and activities, between the two applications.

To set up a Microsoft Project integration:

Add a Microsoft Project Connection (on page 240)

Modify business flows to customize the data synchronized between Microsoft Project and Primavera Cloud for each business flow:

Modify a Microsoft Project Business Flow (on page 241)

Add a Microsoft Project Connection

Set up a Microsoft Project integration to use existing data from Microsoft Project to create projects in Oracle Primavera Cloud.

To add a Microsoft Project connection:



3) In the Microsoft Project tile, select Integrate.


5) Complete either of the following steps:

Select Enable Import/Export for all Workspaces to enable or disable the Microsoft Project connection for every workspace in the application.

In the Workspaces field, select one or more Primavera Cloud workspaces to which this connection applies. Data from this Microsoft Project connection will only be available for the selected workspaces.

Note: You can only select workspaces in the Workspaces field if the Enable Import for all Workspaces switch is disabled.

6) Select Save.

https://docs.oracle.com/en/industries/construction-engineering/primavera-gateway/index.html

https://docs.oracle.com/en/industries/construction-engineering/primavera-gateway/index.html


241

Modify a Microsoft Project Business Flow

You can modify business flows for your Microsoft Project connection.

To modify a business flow:



3) In the Microsoft Project tile, select Integrate.

4) Select the Connect tab, and then select a Microsoft Project connection.

5) Select the Context menu next to a business flow, and then select Edit.

6) In the business flow dialog box, on the Mappings tab, do the following to create new field mappings:

a. Select an object row, select the Context menu, and then select Add field.

b. In the Primavera Cloud Field Name column, select a Primavera Cloud field.

c. In the MSP Field Name column, select a Microsoft Project field to synchronize with the selected Primavera Cloud field.

7) On the Parameters tab, do the following to configure parameters:

a. In the Source Parameters section, select or deselect parameters, if available, to apply them to the business flow.

b. In the Destination Parameters section, select or deselect parameters, if available, to apply them to the business flow.

Compare Flag: Select this parameter if you want to compare the source and destination data to identify changed, deleted, and added objects so that the system can synchronize data efficiently.

Delete data that no longer exists in the source application?: Select this parameter if you want to delete data from the destination application if it no longer exists in the source application. Use this parameter in conjunction with Compare Flag.

8) On the Add field tab, complete the following fields to add new objects and fields to the business flow:

a. Object: The primary object associated with the field you want to add to the business flow.

b. Name: The name of the field.

c. Type: The type of data stored in the field. Valid values are String, Int, Double, Boolean, and DateTime.

d. Category: The category to which the field belongs. The following values are valid categories:

Code: Defines the field as a code on the selected object.

UDF: Defines the field as a configured field on the selected object.

e. (Optional) Description: A short summary of the fields purpose.

9) Select Add.

10) Select Save, and then select Close.


242

Run a Synchronization Job

Run synchronization jobs to synchronize data between Primavera Cloud and external applications.


To run a synchronization job:

1) In the object selector, select a project or workspace.

2) In the sidebar, hover over Integration, and select Synchronize.

3) Select a synchronization row, select the Context menu, and then select Run.

Note: You will receive a notification when the synchronization job starts, and you will receive a notification when the job completes. To view a list of running and completed synchronization jobs, use the Monitor page in the Integration app.

Tips

Select a business flow name to view the objects and fields that will be synchronized when you run the business flow.

Note: Viewing synchronized objects and fields associated with a business flow is not supported for Gateway connections. To view Gateway business flow details, access the business flow definitions in Gateway.

Select Refresh to view the current list of synchronizations available for the project or workspace.

Select Search to search for a synchronization.

Schedule a Synchronization Job

Schedule integration jobs to set them to run automatically at a specified time on a daily, weekly, or monthly interval.


To schedule an integration job:


2) In the sidebar, hover over Integration, and select Synchronize.

3) Select a business flow row, select the Context menu, and then select Schedule.

4) In the Schedule Synchronization dialog box, complete the following fields:


243

Run Report: Determines the interval at which the job will run. For example, if Weekly is selected, the job will run at the specified time once a week.

Starts: The date on which the job schedule will begin to be applied. The selected integration job will run automatically based on the specified schedule after this date.

Time: The time at which the integration job will be initiated when launched by the schedule.

Ends: The date on which the schedule no longer applies. If an end date is provided, jobs will no longer be automatically initiated by the schedule after this date.

5) Select Schedule.

Monitor a Synchronization Job

Monitor running or completed synchronization jobs to determine the status of synchronizations and view their corresponding business flow step details.

Note: The Monitor page is only available for workspaces with a configured P6 EPPM or Microsoft Project connection.

To monitor a synchronization job:


2) In the sidebar, hover over Integration, and select Monitor.

3) Expand a job to view the status of each step of the job.

4) Expand a job step, and then select a format, request, or response to view more detailed information.

Tips

Select a job, select the Context menu, and then select Download to view or download a zip file containing the integration job details, delete a job or delete cross-references related to a job with the following statuses: Completed, Canceled, Completed with Warning, Completed with Error, or Failed.

Notes:

You are only deleting cross-references of the data related to this job, not the data itself. Data sent previously using these cross-references will continue to exist in the destination application.

You can also delete all cross-references for data sent using a specific P6 EPPM connection.

For failed jobs, select Failed in the Status column to view further details about a job failure, including any captured error messages.

Select Refresh to view the current list of synchronization jobs available for the project or workspace.

Select Search to search for a synchronization job.


244

View Synchronization Job Details

View synchronization job details to access further information about synchronization jobs, such as the business flow, parameters, and deployments used when running the synchronization.

To view synchronization job details:


2) In the sidebar, hover over Integration, and select Monitor.

3) Select an integration job, select the Context menu, and then select Job Details.

4) Use the Job Detail dialog box to view information about the selected job. Select Downloadto download an html file containing the synchronization job details.

5) Select Close.

Default Business Flow Reference

Primavera Cloud provides default business flows for many of its product integrations. The following sections detail the purpose of each default business flow, as well as their field mappings.

P6 EPPM Default Business Flow Reference

Primavera Cloud's default P6 EPPM business flows enable you to synchronize P6 EPPM project, resource, risk, schedule, and other data with Primavera Cloud. You can also use data from either application to scaffold new projects in the other application. The following sections lists field mappings for the default business flows for Primavera Cloud and P6 EPPM.


Global

The following sections detail field mappings between Primavera Cloud and P6 EPPM for each global business flow available for a P6 EPPM connection.

Send Resources to Primavera Cloud Field Mappings

Calendar

Primavera Cloud Field Name P6 Field Name

Code ObjectId

HolidayOrExceptions HolidayOrExceptions

IsPersonal IsPersonal

Name Name


245


StandardWorkWeek StandardWorkWeek

Type Type

Resource


CalendarCode CalendarObjectId

CalendarName CalendarName

DefaultUnitsPerTime DefaultUnitsPerTime

EmailAddress EmailAddress

EmployeeId EmployeeId

Id Id

IsActive IsActive

LocationCode LocationObjectId

LocationName LocationName

Name Name

OfficePhone OfficePhone

OtherPhone OtherPhone

ParentObjectId ParentObjectId

PrimaryRoleId PrimaryRoleId

ResourceType ResourceType

Title Title

Send Roles to Primavera Cloud Field Mappings

Role


Id Id

Name Name



246

Create EPS Code in Primavera Cloud Field Mappings

EPS


Id Id

Name Name

SequenceNumber SequenceNumber

Create Workspace Code in P6 Field Mappings

Project Code


CodeTypeName CodeTypeName

CodeValue CodeValue

Description Description


Project Code Type


Length Length

Name Name

Send Resources and Roles to Primavera Cloud Field Mappings

Calendar


Code ObjectId


IsPersonal isPersonal

Name Name


247



Type Type

Resource




DefaultUnitsPerTime DefulatUnitsPerTime



Id Id

IsActive IsActive



Name Name






Title Title


248

Role


Id Id

Name Name


Project

The following sections detail field mappings between Primavera Cloud and P6 EPPM for each project business flow available for a P6 EPPM connection.

Create Project Header - P6 to Primavera Cloud Field Mappings

Project

Primavera CloudField Name P6 Field Name


Owner OwnerResourceId

PlannedFinishDate MustFinishByDate

PlannedStartDate PlannedStartDate

ProjectId Id

ProjectName Name

Status Status

Create Project Header - Primavera Cloud to P6 Field Mappings

Project



IntegratedType IntegratedType


ParentEPSId ParentEPSId




249


ProjectId Id

ProjectName Name

RiskMatrixId RiskMatrixObjectId

Status Status

Send P6 Project Data to Primavera Cloud for Risks Field Mappings

Activity


ActivityPercentComplete PercentComplete

ActualDuration ActualDuration

ActualFinishDate ActualFinishDate

ActualStartDate ActualStartDate


CalendarObjectId CalendarObjectId

DurationType DurationType

EarlyFinishDate EarlyFinishDate

EarlyStartDate EarlyStartDate

ExpectedFinishDate ExpectedFinishDate

FinishDate FinishDate

Id Id

LateFinishDate LateFinishDate

LateStartDate LateStartDate

Name Name

PlannedDuration PlannedDuration

PlannedFinishDate PlannedFinishDate


PrimaryConstraintDate PrimaryConstraintDate

PrimaryConstraintType PrimaryConstraintType

ProjectId ProjectId


250


RemainingDuration RemainingDuration

RemainingFinish RemainingEarlyFinishDate

RemainingLateFinish RemainingLateFinishDate

RemainingLateStart RemainingLateStartDate

RemainingStart RemainingEarlyStartDate

ResumeDate ResumeDate

SecondaryConstraintDate SecondaryConstraintDate

SecondaryConstraintType SecondaryConstraintType

StartDate StartDate

Status Status

SuspendDate SuspendDate

Type Type

WBSCode WBSCode

Activity (Duration Fields)


MaximumDuration MaximumDuration

MinimumDuration MinimumDuration

MostLikelyDuration MostLikelyDuration

Activity Risk


ActivityId ActivityId

ProjectId ProjectId

RiskId RiskId


251

Calendar


Code ObjectId

HolidayOrExecptions HolidayOrExceptions


Name Name


Type Type

Project


ActivityDefaultCalendarCode ActivityDefaultCalendarObjectId

ActivityDefaultCalendarName ActivityDefaultCalendarName

ActivityDefaultCalendarObjectId ActivityDefaultCalendarObjectId

CalculateFloatBasedOnFinishDate CalculateFloatBasedOnFinishDate

ComputeTotalFloatType ComputeTotalFloatType

CriticalActivityPathType CriticalActivityPathType

CriticalDuration CriticalActivityFloatThreshold

DataDate DataDate



IgnoreOtherProjectRelationships IgnoreOtherProjectRelationships

MakeOpenEndedActivitiesCritical MakeOpenEndedActivitiesCritical

MustFinishByDate MustFinishByDate

OutOfSequenceScheduleType OutOfSequenceScheduleType



252



PrimaveraWorkspace PrimaveraWorkspace

ProjectId Id

ProjectName Name

RelationshipLagCalendar RelationshipLagCalendar

StartDate StartDate

StartToStartLagCalculationType StartToStartLagCalculationType

Status Status

StrategicPriority StrategicPriority

URL WebSiteURL

UseExpectedFinishDates UseExpectedFinishDates

Project (Risk Matrix)


RiskMatrixName RiskMatrixName

RiskMatrixObjectId RiskMatrixCode

Relationship


Lag Lag

PredecessorActivityId PredecessorActivityId

PredecessorActivityType PredecessorActivityType

PredecessorProjectId PredecessorProjectId

SuccessorActivityId SuccessorActivityId

SuccessorActivityType SuccessorActivityType


253


SuccessorProjectId SuccessorProjectId

Type Type

Resource







Id Id

IsActive IsActive



Name Name






Title Title

ResourceAssignment

Primavera Cloud Field Name P6 EPPM Field Name


ActivityType ActivityType


254


ActualRegularUnits ActualRegularUnits

ActualUnits ActualUnits

AssignmentCode ObjectId

AtCompletionUnits AtCompletionUnits

IsActivityFlagged IsActivityFlagged


PlannedLag PlannedLag

PlannedUnits PlannedUnits

PlannedUnitsPerTime PlannedUnitsPerTime

ProjectId ProjectId

RemainingUnits RemainingUnits

RemainingUnitsPerHour RemainingUnitsPerTime

ResourceId ResourceId


RoleId RoleId

Risk Impact


ProjectId ProjectId

RiskId RiskId

RiskThresholdCode RiskThresholdObjectId

RiskThresholdLevelCode RiskThresholdLevelCode

RiskThresholdName RiskThresholdName


255

Risk Matrix


Code ObjectId


ImpactThresholdLevel ImpactThresholdLevel

Name Name

ProbabilityThresholdLevel ProbabilityThresholdLevel

RiskScoringMethod RiskScoringMethod

Risk Matrix Score



RiskMatrixCode RiskMatrixObjectId


Severity1 Severity1

Severity1Label Severity1Label

Severity2 Severity2


Severity3 Severity3


Severity4 Severity4


Severity5 Severity5


Severity6 Severity6


Severity7 Severity7


256


Severity8 Severity8


Severity9 Severity9


Risk Matrix Threshold






Risk Response Action



ActualCost ActualCost


Id Id

Name Name

PlannedCost PlannedCost



ProjectId ProjectId

RemainingCost RemainingCost

RiskId RiskId

RiskResponsePlanId RiskResponsePlanId

Score Score

StartDate StartDate


257


Status Status

Risk Response Action Impact


ProjectId ProjectId

RiskId RiskId

RiskResponseActionId RiskResponseActionId




Risk Response Plan


Id Id

IsActive IsActive

Name Name

ProjectId ProjectId

ResponseType ResponseType

RiskId RiskId

Risk Threshold


Code ObjectId

Name Name

ThresholdType ThresholdType


258

Risk Threshold Level


Code Code

Color Color

CostRange CostRange

Level Level

Name Name

ProbabilityRange ProbabilityRange

Range Range



ScheduleRange ScheduleRange


ToleranceRange ToleranceRange

Role


Id Id

Name Name


WBS


Code Code

Name Name


259

ProjectId ProjectId


Send P6 Project Data to Primavera Cloud for Schedule Field Mappings

Activity













Id Id



Name Name

PercentCompleteType PercentCompleteType





260




ProjectId ProjectId





RemainingLateStartDate RemainingLateStart




StartDate StartDate

Status Status


Type Type

WBSCode WBSCode

Calendar


Code ObjectId



Name Name


Type Type


261

Project









DataDate DataDate










ProjectId Id

ProjectName Name


StartDate StartDate


Status Status


262



URL WebSiteURL


Relationship


Lag Lag







Type Type

Resource







Id Id

IsActive IsActive




263


Name Name






Title Title

ResourceAssignment













ProjectId ProjectId





264



RoleId RoleId

Role


Id Id

Name Name


WBS


Code Code

Name Name

ProjectId ProjectId


Send P6 Project Data to Primavera Cloud for Scope Field Mappings

Activity









265







Id Id



Name Name







ProjectId ProjectId





RemainingLateStartDate RemainingLateStart





266


StartDate StartDate

Status Status


Type Type

WBSCode WBSCode

Calendar


Code ObjectId



Name Name


Type Type

Project









DataDate DataDate



267










ProjectId Id

ProjectName Name


StartDate StartDate


Status Status


URL WebSiteURL


Relationship


Lag Lag






268




Type Type

Resource







Id Id

IsActive IsActive



Name Name






Title Title

ResourceAssignment




269












ProjectId ProjectId





RoleId RoleId

Role


Id Id

Name Name


WBS (Scope Fields)


IsWorkPackage IsWorkPackage


270

WBS


Code Code

Name Name

ProjectId ProjectId


Activity (Scope Fields)



Send Planned Budget & Plan Dates from P6 to Primavera Cloud Field Mappings

Project




PlannedBudget SummaryPlannedCost



ProjectId Id

ProjectName Name

Status Status

Send Primavera Cloud Project Data to P6 Field Mappings

Activity


Id Id



271


PostResponsePessimisticFinish PostResponsePessimisticFinish

PostResponsePessimisticStart PostResponsePessimisticStart

PreResponsePessimisticFinish PreResponsePessimisticFinish

PreResponsePessimisticStart PreResponsePessimisticStart

ProjectId ProjectId

ProjectObjectId ProjectObjectId

ScopePercentComplete ScopePercentComplete

WBSObjectId WBSObjectId

WorkPackageCode WorkPackageId

WorkPackageName WorkPackageName

Project







PlannedBudget PlannedBudget


ProjectId Id

ProjectName Name

Status Status


URL WebSiteURL


272

WBS


Code Code


Name Name


ProjectId ProjectId



Send Project Actual Cost & Progress from P6 to Primavera Cloud Field Mappings

Project


ActualCost SummaryActualTotalCost

ActualFinishDate SummaryActualFinishDate

ActualStartDate SummaryActualStartDate



PercentComplete SummarySchedulePercentComplete

ProjectId Id

ProjectName Name

Status Status

Send Proposed Budget & Plan Dates from Primavera Cloud to P6 Field Mappings

Project





273



ProjectId Id

ProjectName Name

ProposedBudget ProposedBudget

Status Status

Send Approved Budget & Plan Dates from Primavera Cloud to P6 Field Mappings

Project


CurrentApprovedBudget CurrentBudget





ProjectId Id

ProjectName Name

Status Status

Send P6 Project Data to Primavera Cloud Field Mappings

Activity











274





Id Id




MaximumDuration MaximumDuration

MinimumDuration MinimumDuration

MostLikelyDuration MostLikelyDuration

Name Name







ProjectId ProjectId




RemainingLateStart RemainingLateStartDate





StartDate StartDate


275

Status Status


Type Type

WBSCode WBSCode

Activity Risk



ProjectId ProjectId

RiskId RiskId

Calendar


Code ObjectId

HolidayOrExceptions HolidayOrExecptions


Name Name


Type Type

Project






276

ActualCost SummaryActualTotalCost

ActualFinishDate SummaryActualFinishDate

ActualStartDate SummaryActualStartDate

AnnualDiscountRate AnnualDiscountRate

AtCompletionCost SummaryAtCompletionTotalCost



CostPerformanceIndex SummaryCostPerformanceIndexByCost

CostVariance SummaryTotalCostVariance



DataDate DataDate


EarnedValueCost SummaryEarnedValueByCost

EstimateAtCompletionCost SummaryEstimateAtCompletionByCost

EstimateToCompletionCost SummaryEstimateToCompleteByCost






MaximumMultipleFloatPoints MaximumMultipleFloatPoints

MultipleFloatPathsEnabled MultipleFloatPathsEnabled

MultipleFloatPathsEndingActivityObjectId MultipleFloatPathsEndingActivityObjectId

MultipleFloatPathsUseTotalFloat MultipleFloatPathsUseTotalFloat


277


NetPresentValue NetPresentValue



PaybackPeriod PaybackPeriod

PlannedBudget SummaryPlannedCost

PlannedDuration SummaryPlannedDuration


PlannedValueCost SummaryPlannedValueByCost


ProjectId Id

ProjectName Name


RemainingDuration SummaryRemainingDuration

ReturnInvestment ReturnOnInvestment



SchedulePerformanceIndex SummarySchedulePerformanceIndexByCost

ScheduleVariance SummaryScheduleVarianceByCost

StartDate StartDate

StartToLagCalculationType StartToLagCalculatonType

Status Status


SummaryRemainingTotalCost SummaryRemainingTotalCost


278

URL WebSiteURL


VarianceFinishDate SummaryFinishDateVariance

VarianceStartDate SummaryStartDateVariance

Relationship


Lag Lag







Type Type

Resource







Id Id


279

IsActive IsActive



Name Name






Title Title

Resource Assignment













ProjectId ProjectId


280




RoleId RoleId

Risk


Cause Cause


Effect Effect

Id Id

IdentifiedDate IdentifiedDate

Name Name

ProjectId ProjectId

ResponseTotalCost ResponseTotalCost

Status Status

Type Type

Risk Impact


ProjectId ProjectId

RiskId RiskId

RiskThresholdCode RiskThresholdLevelObjectId




281

Risk Matrix


Code ObjectId


ImpactThresholdLevel ImpactThresholdLevel

Name Name


RiskScoringMethod RiskScoringMethod

Risk Matrix Score





Severity1 Severity1


Severity2 Severity2


Severity3 Severity3


Severity4 Severity4


Severity5 Severity5


Severity6 Severity6


282


Severity7 Severity7


Severity8 Severity8


Severity9 Severity9


Risk Matrix Threshold






Risk Response Action



ActualCost ActualCost


Id Id

Name Name

PlannedCost PlannedCost



ProjectId ProjectId

RemainingCost RemainingCost


283

RiskId RiskId

RiskResponsePlanId RiskResponsePlanId

Score Score

StartDate StartDate

Status Status

Risk Response Action Impact


ProjectId ProjectId

RiskId RiskId

RiskResponseActionId RiskResponseActionId




Risk Response Plan


Id Id

IsActive IsActive

Name Name

ProjectId ProjectId

ResponseType ResponseType

RiskId RiskId


284

Risk Threshold


Code ObjectId

Name Name


Risk Threshold Level


Code Code

Color Color

CostRange CostRange

Level Level

Name Name

ProbabilityRange ProbabilityRange

Range Range



ScheduleRange ScheduleRange


ToleranceRange ToleranceRange

Role


Id Id


285

Name Name


WBS


Code Code


Name Name

ProjectId ProjectId


WBS Spread


ActualTotalCost ActualTotalCost

AtCompletionTotalCost AtCompletionTotalCost

EndDate EndDate

PeriodType PeriodType

PlannedTotalCost PlannedTotalCost

StartDate StartDate

Send Primavera Cloud Project Data to P6 for Lean Task Field Mappings

Activity


ActivityWorkManagerTaskDateStatus TaskStatusDates


286

ActivityWorkManagerTaskStatus TaskStatusCompletion

ActivityWorkManagerTaskStatusIndicator TaskStatusIndicator

Id Id

ProjectId ProjectId


WBSObjectId WBSObjectId

Project








ProjectId Id

ProjectName Name

Status Status


URL WebsiteURL

WorkManagerTask

The following fields of the WorkManagerTask object in Primavera Cloud are mapped to the LeanTask object in P6 EPPM.


ActivityCompleteStatus StatusCompletion

ActivityDateStatus StatusDates

ActivityObjectId ActivityObjectId

CompanyName Company

CompletedDate CompletedDate

DurationHours Duration

Favorite Flag

ItemCode LeanTaskId


287

Overdue IsOverdue

StartDate StartDate

Status Status

TasksName Name

TentativeDate DueDate

Type TaskType

UseCalendar IsUseOnlyWorkDays

WBS


Code Code


Name Name


ProjectId ProjectId



Microsoft Project Default Business Flow Reference

Primavera Cloud's default Microsoft Project business flows enables you to use existing Microsoft Project data to create projects in Primavera Cloud and export Primavera Cloud projects for use in Microsoft Project.

Import MSP Project Data to Primavera Cloud Field Mappings

The following table lists field mappings for the default import business flow from Microsoft Project to Primavera Cloud:

Activity Fields

Primavera Cloud Field Name MSP Field Name

ActivityPriority Priority


288



ActualFinishDate ActualFinish

ActualLaborUnits ActualWork

ActualStartDate ActualStart

DurationPercentComplete PercentComplete

AtCompletionLaborUnits Work

CalendarCode CalendarCode

CalendarObjectID CalendarUID


EarlyFinishDate EarlyFinish

EarlyStartDate EarlyStart

ExpectedFinishDate Deadline

FinishDate Finish

Id ID

LateFinishDate LateFinish


289


LateStartDate LateStart

Name Name

PhysicalPercentComplete PhysicalPercentComplete

PlannedFinishDate Finish

PrimaryConstraintDate ConstraintDate

PrimaryConstraintType ConstraintType

ProjectId ProjectId



RemainingLaborUnits RemainingWork

StartDate Start

Status Status

Type Type

UnitsPercentComplete PercentWorkComplete

WBSCode WBS


290


WBSObjectId SummaryTaskObjectId

Calendar Fields


Code Name


HoursPerDay HoursPerDay

HoursPerWeek HoursPerWeek

HoursPerMonth HoursPerMonth

HoursPerYear HoursPerYear

Name Name



Type Type

Project Fields


ActivityDefaultCalendarCode CalendarCode


291


ActivityDefaultCalendarObjectId CalendarUID

DataDate StatusDate


ProjectDefaultDurationType DefaultTaskType

ProjectId Name

ProjectName Name

StartDate StartDate

Relationship Fields


Lag Lag

PredecessorActivityId PredecessorTaskId

PredecessorActivityObjectId PredecessorTaskObjectId

SuccessorActivityId SuccessorTaskId

SuccessorActivityObjectId SuccessorTaskObjectId

Type Type


292

Resource Fields


CalendarCode CalendarUID

CalendarObjectId CalendarUID


Id Name

IsActive IsActive

Name Name


ResourceType Type

UOMObjectId UOMObjectId

Resource Assignment Fields


ActivityObjectId TaskObjectId

ActivityType TaskType

ActualFinish ActualFinish

ActualStart ActualStart


293


ActualUnits ActualWork


AtCompletionUnits Work

CurveName WorkContour

FinishDate Finish

PlannedFinish Finish

PlannedLag Delay

PlannedStart Start

PlannedUnits BudgetWork

PlannedUnitsPerTime Units

ProjectId ProjectId

RemainingUnitsPerHour RemainingUnitsPerHour


ResourceObjectId ResourceObjectId



294


StartDate Start

ResourceRate Fields


EffectiveDate RatesFrom

MaxUnitsPerTime MaxUnits


UnitOfMeasure Fields


Key MaterialLabel

WBS Fields


Code WBS

Name Name




295

Export Primavera Cloud Project Data to MSP Field Mappings

The following table lists field mappings for the default export business flow from Primavera Cloud to Microsoft Project:

Activity Fields


ActivityPriority Priority


ActualFinishDate ActualFinish

ActualLaborUnits ActualWork

ActualStartDate ActualStart

AtCompletionLaborUnits Work


CalendarObjectID CalendarUID

DurationPercentComplete PercentComplete


EarlyFinishDate EarlyFinish

EarlyStartDate EarlyStart

ExpectedFinishDate Deadline


296


FinishDate Finish

Id ID

LateFinishDate LateFinish

LateStartDate LateStart

Name Name

PhysicalPercentComplete PhysicalPercentComplete

PlannedDuration Duration

PlannedFinishDate Finish

PlannedStartDate Start

PrimaryConstraintDate ConstraintDate

PrimaryConstraintType ConstraintType

ProjectId ProjectId



RemainingLaborUnits RemainingWork


297


StartDate Start

Status Status

Type Type

UnitsPercentComplete PercentWorkComplete

WBSCode WBS

WBSObjectId SummaryTaskObjectId

Calendar Fields



HoursPerDay HoursPerDay


HoursPerWeek HoursPerWeek


Name Name




298


Type Type

Project Fields


ActivityDefaultCalendarCode CalendarCode

ActivityDefaultCalendarObjectId CalendarUID

DataDate StatusDate


ProjectDefaultDurationType DefaultTaskType

ProjectName Name

StartDate StartDate

Relationship Fields


Lag Lag

PredecessorActivityId PredecessorTaskId

PredecessorActivityObjectId PredecessorTaskObjectId

SuccessorActivityId SuccessorTaskId


299


SuccessorActivityObjectId SuccessorTaskObjectId

Type Type

Resource Fields



CalendarObjectId CalendarUID


IsActive IsActive

Name Name


ResourceType Type

UOMObjectId UOMObjectId

Resource Assignment Fields


ActivityObjectId TaskObjectId

ActivityType TaskType


300


ActualFinish ActualFinish

ActualStart ActualStart

ActualUnits ActualWork


AtCompletionUnits Work

CurveName WorkContour

FinishDate Finish

PlannedLag Delay

PlannedUnits BudgetWork

PlannedUnitsPerTime Units

ProjectId ProjectId

RemainingUnits RemainingWork

RemainingUnitsPerHour RemainingUnitsPerHour




301



StartDate Start

ResourceRate Fields


EffectiveDate RatesFrom

MaxUnitsPerTime MaxUnits


UnitOfMeasure Fields


Key MaterialLabel

WBS Fields


Code WBS

Name Name




302

Import/Export Overview

Primavera Cloud offers a few options for importing and exporting workspace data and projects.

Use the Import/Export Configuration Data feature to copy workspace data from one environment to another. You can either export and import whole workspaces, or you can create configuration sets to specify the data. View the Import/Export Log on the Workspaces inventory panel to keep track of the configuration data imports and exports.

Import and export projects between Primavera Cloud and P6 XML, Microsoft Project, or other Primavera Cloud environments. When importing, you can use this feature to update existing projects or create new projects. An integration connection to Microsoft Project is required for importing or exporting Microsoft Project data.

Primavera Cloud also supports the ability to import Excel spreadsheets to create or update projects in the application. Download an Excel spreadsheet template from the Projects inventory panel, complete the spreadsheet with the required project information, and then import the spreadsheet back into Primavera Cloud.

Import/Export Configuration Data Overview

The import and export Primavera Cloud configuration data feature enables you to copy a configuration set from one workspace to another. You can select to export all data, or you can create a custom data set. You should create your ideal environment in test before moving to production. If you want to export and import workspaces, you must select all data. Customized data sets can only be imported in existing workspaces.

You can export and import the following items:

Analysis Views

Calendars

Charts

Codes

Configured Fields

Cost Categories

Custom Form Mapping

Custom Workflow Mapping

Dashboards

Evaluation Matrix

Field Labels

Field Mapping Sets

Folder Templates

Forms

Holiday Lists

Locations

Measures


303

Named Views

Permissions

Portfolios

Print Layouts

Programs

Reasons

Report Layouts

Reports



Rules of Credit

Strategies

Strategy Types

Units of Measure

User Groups

Workflow Configuration

Workflow Design

Workspace Auto-Numbering Settings

Workspace Settings

Notes

Customized data options do not support the import or export of workspaces or CBSs.

Any risk matrixes with risk thresholds from other workspaces will not be exported.

If you export and then import a workflow configuration that is associated with a non-current workflow design, you may not be able to track changes between designs. To prevent unexpected behavior, update any configurations that are flagged as being associated with non-current designs before exporting data.

Export All Configuration Data from Primavera Cloud

You should export all data if you want to export workspaces and all other supported data types including CBSs. You can only import all data into a new Primavera Cloud environment.

To export all data:


2) In the table, select the root workspace row, select the Context menu, and then select Export All Configuration Data.

3) In the Export Data Package dialog box, review the summary and log of exported objects, and select Download.

Data is saved in a file named ConfigData.zip by default and can be renamed.


304

Import Configuration Data to Primavera Cloud

Import data in your production environment using zip files exported from another Primavera Cloud environment. If duplicate objects are found during the import, you will be prompted to keep the existing object, update the existing object, or create a new object.

To import data:


2) In the table, select a workspace row, select the Context menu, and then select Import Configuration Data.

3) In the Import dialog box, select Browse, select a zip file, and select Import.

4) In the Import Data Package dialog box, select the objects you want to import.

5) Choose one of the following actions to take if duplicate objects are found during the import for each data type you are importing:

Keep Existing: Keeps the existing object and ignores the object from the import.

Update: Updates the existing object with the object from the import.

Create: Creates a new object and keeps the existing object.

6) Select Import, and then select OK.

Export Customized Configuration Data from Primavera Cloud

You can export customized data sets by specifying which objects you want to export. Customized data sets do not export workspaces or CBSs. If you want to export workspaces or CBSs, you must select all data.

To export customized data:


2) In the table, select a workspace row, select the Context menu, and then select Export Configuration Data.

3) In the Export Data Package dialog box:

a. Select the objects you want to export, and select Export.

b. Review the summary and log of exported objects, and select Download.

Data is saved in a zip file named ConfigData.zip by default and can be renamed.

View the Import/Export Configuration Data Log

You can view activity logs to access information on successful and failed configurations. In the Success section, you can view information on the workspace, the action attempted, and the action taken. In the Failure section, you can view an error message explaining the cause of failure.

To view the import/export log:


2) In the Import/Export Log detail window, select an instance, select the Context menu, and then select View Log.


305

3) In the View Log dialog box, view the successful and failed imports and exports data.

4) (Optional) Select Download to download the log.

The log is saved in a file named logData.json.

Download the Import/Export Configuration Data Log

You can download activity logs to review data on successful and failed imports and exports. You can view information on the workspace, the action attempted, and the action taken for successful actions, and you can view an error message explaining the cause of failure for failed actions.

To download the import/export log:


2) In the Import/Export Log detail window, select an instance, select the Context menu, and then select Download Log.

3) Open or Save the file.

The log is opened and saved in a file named logData.json.

P6 XML Import/Export Overview

P6 XML Import/Export enables you to share data across applications and environments. Import P6 projects into your Oracle Primavera Cloud environment and export Primavera Cloud projects for use in P6. You can also export project data for use in a different Primavera Cloud environment.

When you import a project from a P6 XML file, the system gives you the option to create a new project, update an existing project, or ignore the project and not import it. In XML files that contain multiple projects, you can set separate import actions for each project. Before you begin the import process, you must specify the target workspace into which the projects will be imported. Data that can be imported from P6 includes objects stored at the workspace and project levels. You can set separate import actions for each workspace and project data type, providing greater control over the data that gets imported. You also have the ability to specify the action that the application takes when an object in the XML file already exists in Oracle Primavera Cloud. Your import configuration settings can be saved and used the next time you run the import process.

After the import process completes, you can review the import log to view data and statistics about the process, as well as any errors encountered that need to be resolved. You can access the import log from the system notification you receive when the process is complete, from the Inbox page, or from the Manage Services page.

When exporting data from Primavera Cloud, you can export multiple projects from the same workspace. When the export process completes, you can download the P6 XML file that is generated from the system notification, from the Inbox page, or from the Manage Services page.

The maximum file size that you can import is 500 MB. The P6 XML Import/Export feature is available for both Oracle Primavera Cloud and Primavera Professional.

Note: When project data is imported into Oracle Primavera Cloud from


306

P6 EPPM, it is recommended that you reschedule the project before making any project updates.

Project Import Actions

When you import a P6 XML file, you can select one of the following actions for each project included in the file:

Create New Project: The project data is used to create a new project in Primavera Cloud. If the project already exists in the current workspace, the project will be imported into the target workspace with a numeric value appended to its project ID.

Update Existing Project: The project data is used to update an existing Primavera Cloud project. This option is only available if a project with a matching project ID is found in the current workspace.

Do Not Import: The project data is ignored and is not imported into Primavera Cloud.

Import Objects

P6 XML files include the configuration and settings data used by a project. Workspace-level data (called "Global data" in P6) is imported to the workspace and is shared among the projects, child workspaces, and other objects in the workspace. Project-level data belongs only to the project and is not shared.

The following types of workspace data can be imported:

Calendars

Codes

Activity Codes

Project Codes

Resource Codes

Configured Fields

Activity Fields

Assignment Fields

Project Fields

Risk Fields

WBS Fields

Notes:

Called "user defined fields" in P6 EPPM, you can only import configured fields with a Type of "Manual".

You cannot import configured fields with a Data Type of "Indicator" or a UDF Type of "Formula."

Imported configured field names must begin with a letter. Names cannot contain spaces, reserved words, multi-byte characters, or special characters except for an underscore.

Curves

Resources


307

Risk Threshold and Matrix Templates

Note: The cost threshold, schedule threshold, and probability threshold associated with a risk matrix template must be included in the import in order for the risk matrix template to import successfully.

Roles

Note: Roles in Primavera Cloud must have unique IDs. To successfully import roles into Primavera Cloud, ensure that the role IDs being imported from P6 are all unique.

Units of Measure

The following types of project data can be imported:

Activities

Relationships

Resources and Roles

Risks

WBS

Workspace Data Import Actions

Data objects in Oracle Primavera Cloud must be unique within each workspace hierarchy branch. During the import process, the application searches up and down the hierarchy of the target workspace to determine whether matching workspace objects already exist in the application. Workspace data import settings specify the action that is taken when a matching object is found in the application. Matching objects found in other workspaces in the hierarchy may need to be assigned or promoted to the target workspace to maintain existing data associations. Changes to an object's owning workspace are detailed in the list of import actions below. Separate import actions can be chosen for each workspace data type. The selected actions apply to all projects being imported from the P6 XML file.

When configuring the workspace data import settings, you can choose from the following import actions:

Insert New: If a matching object is found, the object will be inserted into the target workspace as a unique record by appending a numeric value to the object. If no matching object is found, the object will be created as new.

Update Existing: If a matching object is found in the target workspace, its owning workspace will remain the same and the object will be updated based on the data from the import file. If a matching object is found in a higher-level workspace, its owning workspace will remain the same, but an association will be created with the target workspace. The object will not be updated because objects can only be updated from their owning workspace. If a matching object is found in a lower-level workspace, the application will attempt to promote its owning workspace to the target workspace and create an association with the workspace where the object was found. The promoted object will be updated based on the data from the import file. If no matching object is found, the object will be created as new.


308

Keep Existing: If a matching object is found at any level, the existing object will be kept and its data will not be updated. If the matching object is found in the target workspace, its owning workspace will remain the same. If the matching object is found in a higher-level workspace, its owning workspace will remain the same, but an association will be created with the target workspace. If the matching object is found in a lower-level workspace, the application will attempt to promote its owning workspace to the target workspace and create an association with the workspace where the object was found. If no matching object is found, the object will be created as new.

Do Not Import: The data type is ignored and is not imported. However, if a matching object is found, any associated data (such as resource assignments) will be imported.

Note: Because codes can be associated with multiple object types, importing code types with different import actions may interfere with new and existing codes. For example, assume an existing code is associated with both activities and resources. Choosing to insert new activity codes and update existing resource codes during the import may cause unintended changes to the existing code. To prevent this from happening, all code import actions are set to the same option. If you change the import action for one code, the import actions for all other codes will automatically be changed to the same option. This ensures that all codes are imported consistently.

Conflict Actions

When importing a workspace data type using Update Existing or Keep Existing, the application automatically attempts to promote any matching object found in a lower-level workspace and create an association with the workspace where the object was found. Conflicts may occur if multiple matches of the same object are found in sibling workspaces. Promoting one of the matching objects to a common parent workspace will violate the application's hierarchy uniqueness requirements and cannot be done. In these scenarios, you can select alternate actions during import configuration to resolve potential promotion conflicts. A conflict action can be set for each workspace data type:

Insert New: The matching object will be inserted into the target workspace as a unique record by appending a numeric value to the object.

Fail Import: If a promotion fails, the import process will fail immediately and no data will be imported.

Do Not Import: The matching object is ignored and is not promoted or imported.

Separate conflict actions for each data type provide greater control over your imported data. For example, you may want to insert as new any matching calendars found in a lower level, but prevent the insertion of matching resources. You can set resource objects to fail the import, enabling you to manually resolve uniqueness conflicts before running the import again.


309

Notes:

Because configured fields must be unique across the application for each object type, they do not support promotion or conflict actions. The conflict action is set to Not Applicable for configured fields.

All code conflict actions are set to the same option during the import process.

Project Data Import Actions

You can configure the action that is taken for each project data type imported with a project. The selected actions apply to all projects being imported from the P6 XML file.

When configuring the project data import settings, you can choose from the following import actions:

Update Existing: If a matching object is found in the project, it will be updated based on data from the import file. If no matching object is found, the object will be created as new.

Keep Existing: If a matching object is found in the project, it will be kept and its data will not be updated. If no matching object is found, the object will be created as new.

Do Not Import: The data type is ignored and is not imported. However, if a matching object is found, any associated data (such as resource assignments) will be imported.

For activity, relationship, and resource and role data types, select Remove from Projects to remove an object from the project if the object does not exist in the XML file. This ensures that a project being updated is consistent with the data in the XML file.

Export Objects

All project-related data and objects that can be used in P6 are included in the P6 XML export process. To export a project from the application, you must have the Export Projects global security privilege enabled.

Import P6 XML Data into Oracle Primavera Cloud

Import P6 data from a P6 XML file into your Oracle Primavera Cloud environment. For each project included in the file, you can create a new project, update an existing project, or ignore the project and not import it. For projects you choose to import, you can specify how individual workspace and project object types are imported into the application. When the import is complete, you can view a log file to see the results of the process.

The P6 XML import process contains many different options for importing your data, each with its own set of rules to describe how your data is impacted during the process. This topic describes the process and its options at a high level. For a detailed description of the process, available import actions, and the objects that you can import, see P6 XML Import/Export Overview (on page 305).

Notes:

You must have the required workspace security privileges to import projects and add new projects. You must have the required project


310

security privilege to edit existing projects.

The maximum file size that you can import is 500 MB.

To import P6 data from a P6 XML file:







Note: In Primavera Professional, open a project or program that belongs to the workspace where you want to import the projects.

2) (Primavera Cloud only) In the Projects inventory panel, in the workspace tree, select a destination workspace for the imported project.

Note: You must be within the context of the workspace where you want to import the file. Selecting a workspace name in the grid will not change the workspace context.

3) Select Actions, and then select Import P6 XML.

4) In the Import P6 XML panel, in the Select File field, select a P6 XML file to import.

5) In the Project Import Actions section, specify an Import Action for each project.

6) Select Next.

7) In the Workspace Data section, specify the following for each item:

Import Action: Select an import action for each workspace item.

Conflict Action: Select an alternate action to take when multiple matches are found in the application.


311

Notes:

Because configured fields must be unique across the application for each object type, they do not support promotion or conflict actions. The conflict action is set to Not Applicable for configured fields.

Because codes can be associated with multiple object types, importing code types with different import actions may interfere with new and existing codes. For example, assume an existing code is associated with both activities and resources. Choosing to insert new activity codes and update existing resource codes may cause unintended changes to the existing code. To prevent these unintended changes, all code import actions and conflict actions are synchronized during the import process. This ensures that all codes are imported consistently.

Conflict action options are available for workspace data items with an import action of Update Existing or Keep Existing.

8) In the Project Data section, specify the following for each item:

Import Action: Select an import action for each project item.

Remove from Projects: Select this option to remove objects in Oracle Primavera Cloud that do not exist in the P6 XML file. This option is available for the activity, relationship, and resource and role project data items.

9) (Optional) Select Save Configuration to retain these settings for future use.

10) Start the import process:

In Primavera Cloud:

a. Select Finish.

b. In the inventory panel, select Close.


Select Finish.


Tips

After the import process is complete, you can review the import log to view data and statistics about the scheduling process, as well as any errors encountered that need to be resolved. You can access the import log from the system notification you receive when the process is complete or from the Manage Services page.


312

Export Oracle Primavera Cloud Data to P6 XML

Export one or more projects from Primavera Cloud to a single P6 XML file. You must have the required global privilege to use the export functionality. The list of projects available for export depends on the workspace or project selected in the table.

For more information, see P6 XML Import/Export Overview (on page 305).

To export project data to a P6 XML file:







2) In the table, select a workspace or project row.

3) Select Actions, and then select Export P6 XML.

4) In the Export P6 XML dialog box, in the Select Project field, select one or more projects, and then select Select.

5) Start the export process:

In Primavera Cloud:

a. Select Export.



Select Export.

Tips

When the export process is complete, you will receive a system notification. Select Download File in the notification to download the P6 XML file. You can also download the P6 XML file from the Inbox or Manage Services pages.

A single P6 XML file is created during the export process. If multiple projects are exported, the file is named after the first project in the export list.

Create Projects by Excel Import

You can bulk import a group of projects into the application using Microsoft Excel. Download a pre-formatted template, follow the instructions in the spreadsheet, and then import the completed template into Oracle Primavera Cloud. Using data from an outside system can save you time from manual entry. The same template can also be used to update the data of existing projects.


313

Download an Import Template for Importing Projects

Download a pre-formatted Microsoft Excel template to use when importing projects. The template contains all project codes and configured fields that are available to the workspace where you downloaded the template. After you download the template, enter the name, ID, and details of each project you want to import. When you are finished, you can import the updated template to create the projects in Oracle Primavera Cloud. The template can also be used to update data in projects that already exist in Primavera Cloud.








2) Select Actions, and then select Download Import Template.

Tips

The import template is downloaded as a Microsoft Excel file with the default file name ProjectsImportTemplate.

The top two rows of each worksheet are required when importing resources from a spreadsheet. You can delete unused optional columns, but do not change the data in these rows.


Import Projects from Microsoft Excel

You can bulk import projects into the application from a Microsoft Excel (.xls or .xlsx) file. After downloading the import template, follow the instructions to create or update projects in the spreadsheet. The import will fail if there are any invalid values in the spreadsheet. You can download the spreadsheet file to view and fix the errors indicated in the error column at the end of each worksheet, and then import the file again.

You must have sufficient workspace privileges to import projects from Microsoft Excel.

To import projects from Microsoft Excel:








314

Note: In Primavera Professional, open a project or program that belongs to the workspace where you want to import the projects.

2) (Primavera Cloud only) In the workspace tree, select a destination workspace for the imported project.

Note: You must be within the context of the workspace where you want to import the file. Selecting a workspace name in the grid will not change the workspace context.

3) Select the Actions menu, and then select Import.

4) In the Import Projects dialog box, select Browse, select a file, and select Import.

Tips

You will receive a notification when the process is complete.

Microsoft Project Import/Export Overview

You can import Microsoft Project projects into your Oracle Primavera Cloud environment and export Primavera Cloud projects for use in Microsoft Project. An integration connection to Microsoft Project (see "Add a Microsoft Project Connection" on page 240) is required for importing or exporting Microsoft Project data.

During the import process, you have the option to create a new project using the data in the Microsoft Project XML, update an existing project, or automatically detect which action to take based on the XML filename. Imported data includes project configuration and setting data associated with the project, such as activities, calendars, relationships, resource assignments, and WBS. Microsoft Project external dependencies are not imported by Primavera Cloud.

During the export process, you can select a project from the workspace where you chose to export. The full list of data imported or exported between Primavera Cloud and Microsoft Project can be reviewed in the Microsoft Project Default Business Flow Reference (on page 287) (Oracle Primavera Cloud Help only).

To run the import process, you must have the required workspace security privileges to import and add new projects, and the required project security privilege to edit projects. To export a project from the application, you must have the Export Projects global security privilege enabled.

When the import process is complete, you can review the integration details on the Manage Services page. When the export process completes, you can download the Microsoft Project XML file that is generated from the system notification.

Only one project can be imported at a time.


315

Import Microsoft Project Data into Oracle Primavera Cloud

Import a Microsoft Project XML file to create a project in Oracle Primavera Cloud containing Microsoft Project activity, resource assignment, and general project data. Only one project can be imported at a time.

Note: The parent workspace for the project must have a Microsoft Project connection to enable importing Microsoft Project data.

To import data from a Microsoft Project XML file:







Note: In Primavera Professional, open a project or program that belongs to the workspace where you want to import the project.

2) (Primavera Cloud only) In the workspace tree, select a destination workspace for the imported project.

3) Select Actions, and then select Import/Export - Microsoft Project.

4) In the Import/Export - Microsoft Project dialog box, select the Import tab.

5) In the Select File field, select a Microsoft Project XML file.

6) In the Import Action field, select one of the following options:

Auto-Detect: Select to allow the application to detect whether a new project should be created or an existing project should be updated.

Notes:

The XML file name is the project ID. This ID is used to determine which action to take.

If you want to update a project that has a different project ID, then select the Update Existing option.

Create New: Select to create a new project in Primavera Cloud using the data from the Microsoft Project XML file.

In the New Project ID field, enter a unique ID for the project.

Update Existing: Select to update an existing project.

In the Import To field, select the project to update.


316

Caution: Ensure you choose the correct project. Selecting a non-related project may corrupt the data in your existing project.

7) Start the import process:

In Primavera Cloud:

a. Select Import.



Select Import.

Export Oracle Primavera Cloud Data to Microsoft Project XML

Export a project and its data from Oracle Primavera Cloud for use in Microsoft Project. The data is exported as a Microsoft Project XML file. You must have the required global privilege to use the export functionality. The list of projects available for export depends on the workspace or project selected in the table.

To export project data to Microsoft Project XML:







2) In the table, select a workspace or project row.

3) Select Actions, and then select Import/Export - Microsoft Project.

4) In the Import/Export - Microsoft Project dialog box, select the Export tab.

5) In the Select Project field, select a project, and then select Select.

6) Start the export process:

In Primavera Cloud:

a. Select Export.



Select Export.

Tips

When the export process is complete, you will receive a system notification. Select Download MSP File in the notification to download the Microsoft Project XML file. You can also download the XML file from the Manage Services page.

Manage Services Overview

317


The Manage Services page lists the user-initiated processes in the application that are in progress or have completed. This page consists of the Service Status and Recurring Services tabs. The Service Status tab shows the status of the background services triggered manually from various contexts or triggered automatically as recurring services and the workflow instance details. The Recurring Services tab enables you to configure services that need to run at regular intervals.

Monitor Service Status

The Service Status tab on the Manage Services page provides a summary of the progress and completion of background services initiated by the users. It also provides the summary of recurring services configured to run automatically in the background. Background services include schedule, level, risk analysis, global change, set as current schedule, import, export, measures, recalculate cost, and integration service types. You can filter for a service type using the pre-defined filters in the filter panel or specify additional filtering criteria in the Filter By section. View a quick summary of the selected service type, context, start and end date, and the status in the grid. Use the preview panel to view additional details about the service, such as its frequency, or to terminate a running service.

To monitor the service status:

1) Navigate to the Manage Services page (see page 333).

2) Select the Service Status tab, and then select a service.

Note: You can apply filters to reduce the number of services displayed on the page. For more information, see Manage Services Filters (on page 319).

Tips

To terminate a service while it is still running, select a service that is in progress, select Terminate in the preview panel, and then select Yes in the confirmation dialog box. You can terminate the following services: import, export, level, risk analysis, and schedule.

Application administrators can view all background services that all users have initiated. Users who are not application administrators can only view the background services they have initiated.

Many background services that are complete include a log you can view to see additional details about the service. Select View Log or View Details in the preview panel to view the details of the completed service.

Select Set up recurring schedule in the Schedule field in the preview panel to quickly set up a recurring service. Or, select Edit to edit the recurring service schedule if it was scheduled already.


318

Configure Recurring Services

Select the Recurring Services tab on the Manage Services page to configure recurring services that need to run at regular intervals for schedule, level, and risk analysis. You can configure schedule recurring services for projects or project collections and level and risk analysis services for projects. You can define the frequency of the service and view the run history and log on this page.

You can also view recurring service details for measures on the Recurring Services tab, including general service information and job history. The configuration of measure recurring services must be done in the workspace Measures dictionary.

To configure a recurring service:

1) Navigate to the Manage Services page (see page 333).

2) Select the Recurring Services tab.

3) Select Add.

4) In the Add Recurring Service wizard, complete the following steps:

In the General step, enter general information for the service type, such as name and frequency, including the day and time of recurrence, and then select Next.

In the Assign Projects step, select the projects or project collections on which the service is scheduled to run, and then select Next.

In the Options step:

For schedule service type, specify the Schedule Settings and Data Date options, and then select Add.

For level service type, specify the Schedule Settings, and then select Add.

Note: The Options step is only available for schedule and level service types.

Tips

Use the preview panel to view the details for the selected recurring service. The following tabs are available:

General: Use this tab to view general information about the service, such as its schedule and recurrence settings.

Projects: Use this tab to view the project on which the service type is scheduled to run.

Service Details: Use this tab to view the service details, such as the Schedule Settingsand the Data Date of the scheduled service type.

Job History: Use this tab to view the run history and log of the service type.

To terminate a recurring service while it is still running, navigate to the Job History tab of the preview panel, select the Context menu for a service that is in progress, select Terminate, and then select Yes in the confirmation dialog box. You can terminate the following services: import, export, level, risk analysis, and schedule.

You can apply filters to reduce the number of recurring services displayed on the page. For more information, see Manage Services Filters (on page 319).


319

Manage Services Filters

Filter for a service type on the Manage Services page using the filter panel on the Service Status or Recurring Services tabs. You can use a pre-defined filter or specify additional filtering criteria in the Filter By section.

Filtering options for Service Status:

a) Pre-defined filters:

All: Shows all the available services. This is selected by default.

In Progress: Shows the services that are currently running.

Completed: Shows the services that are completed.

Global Change: Shows all global change services.

Export: Shows all project export services.

Import: Shows all import services for a project or other objects.

Integration: Provides a list of running, complete, or failed integration jobs for each integration type, such as P6 EPPM or Microsoft Project.

Level: Shows all level services.

Measures: Shows all measure services.

Recalculate Cost: Shows all recalculate cost services.

Risk Analysis: Shows all the risk analysis services.

Schedule: Shows all schedule services.

Set as Current Schedule: Shows all the set as current schedule services.

b) Filter By options:

Project: Applies to the services in the project context and shows all projects to which the user has access.

Portfolio: Applies to the services that have the context field value of a portfolio and shows all portfolios to which the user has access.

Subject Area: Applies to imports. Shows all entities that support Microsoft Excel and P6 XML import.

Business Flow: Applies to integration jobs. Shows all business flows available for P6 EPPM or Microsoft Project integrations.

Integration: Applies to integration type services. Choose either P6 EPPM or Microsoft Project.

Filtering options for Recurring Services:

a) Pre-defined filters:

All: Shows all services that are configured to occur periodically. This is selected by default.

Enabled: Shows all the enabled services.

Schedule: Shows all schedule services.

Level: Shows all level services.

Risk Analysis: Shows all risk analysis services.

Measures: Shows all measure services.


320

b) Filter By options:

Project: Shows all projects to which the user has access.

Added By: Shows all users who added the services.

Test Network Speed

You can run a network test to determine network speed and latency. This information is used to troubleshoot network issues and might be required when you contact My Oracle Support.

The network test analyzes two network impacts:

Speed: The average data rate for the transfer of a file in megabits per second (Mbps).

Latency: The amount of time in milliseconds (msec) before the transfer of data begins.

To test your network:


2) On the User menu, select Network Test.

3) In the Network Test dialog box, select Start Network Test.

Set the Locale

The default language is determined by the browser locale of the user.

To change the language setting:

1) Enter the URL for the application in your browser.

2) At the end of the URL, enter: ?locale=<locale code>

If the URL already contains a question mark, use an ampersand instead. For example: &locale=<locale code>

The locale codes are as follows:

de = German

en = English

es = Spanish

fr = French

it = Italian

ja = Japanese

ko = Korean

nl = Dutch

pt_BR = Brazilian Portuguese

ru= Russian

zh_CN = Simplified Chinese

zh_TW = Traditional Chinese

Set the Locale

321

For example, to change the language to German, the URL would be https://servername:port/web/p/inbox?ctx=none&app=inbox&locale=de.

3) Bookmark this URL for future access.

Note: When you navigate to a different page from the one referenced with the locale parameter, the parameter is removed from the URL. However, it will be remembered for the rest of the login session.

323

Appendix of Referenced Navigation Steps

Navigate to the WBS page

In Primavera Cloud:

a) In the object selector, select a project.

b) In the sidebar, hover over Schedule or Scope, and select WBS.


a) On the File menu, select Open.

b) In the Open dialog box, select the Projects tab, select a project, and then select Open.

c) On the Project menu, select WBS.

Navigate to the Activities page

In Primavera Cloud:

a) In the object selector, select a project, program, or project collection.

b) In the sidebar, hover over Schedule, and select Activities.



b) In the Open dialog box, select the Projects or Programs tab, select a project or program, and then select Open.

c) On the Project or Program menu, select Activities.

Navigate to the project Activities page

In Primavera Cloud:






c) On the Project menu, select Activities.

Navigate to the project or project collections Activities page

In Primavera Cloud:

a) In the object selector, select a project or project collection.



324




c) On the Project menu, select Activities.

Navigate to the Baselines page

In Primavera Cloud:


b) In the sidebar, hover over Scope or Schedule, and select Baselines.




c) On the Project menu, select Baselines.

Navigate to the Schedule Comparison page

In Primavera Cloud:


b) In the sidebar, hover over Schedule, and select Schedule Comparison.




c) On the Project menu, select Schedule Comparison.

Navigate to the workspace resource page

In Primavera Cloud:


b) In the sidebar, hover over Resources, and select Resource List.




c) On the Workspace menu, select Resources.

Navigate to the project resources page

In Primavera Cloud:



325





c) On the Project menu, select Resources.

Navigate to the workspace or project resources page

In Primavera Cloud:

a) In the object selector, select a workspace or project.





c) On the Workspace or Project menu, select Resources.

Navigate to the workspace roles page

In Primavera Cloud:


b) In the sidebar, hover over Resources, and select Role List.




c) On the Workspace menu, select Roles.

Navigate to the project roles page

In Primavera Cloud:






c) On the Project menu, select Roles.


326

Navigate to the workspace or project roles page

In Primavera Cloud:

a) In the object selector, select a workspace or project.





c) On the Workspace or Project menu, select Roles.

Navigate to the workspace resource assignments page

In Primavera Cloud:


b) In the sidebar, hover over Resources, and select Assignment List.




c) On the Workspace menu, select Resource Assignments.

Navigate to the project, program, or project collection resource assignments page

In Primavera Cloud:


b) In the sidebar, hover over Resources or Schedule, and select Assignment List.




c) On the Project or Program menu, select Resource Assignments.

Navigate to the workspace resource analysis page

In Primavera Cloud:


b) In the sidebar, hover over Resources, and select Analysis.




327


c) In the Workspace menu, select Resource Analysis.

Navigate to the project, program, or project collection resource analysis page

In Primavera Cloud:


b) In the sidebar, hover over Resources, and select Analysis.




c) On the Project or Program menu, select Resource Analysis.

Navigate to the files page

In Primavera Cloud:

a) In the object selector, select a project, portfolio, program, or idea.

b) In the sidebar, hover over Files, and select File List.




c) On the Project or Program menu, select Files.

Navigate to the project files page

In Primavera Cloud:






c) On the Project menu, select Files.

Navigate to the project or portfolio files page

In Primavera Cloud:

a) In the object selector, select a project or portfolio.


328





c) On the Project menu, select Files.

Navigate to the project Details page

In Primavera Cloud:



c) On the Summary & Settings menu, select Details.




c) On the Project menu, select Details.

Navigate to the project codes page

In Primavera Cloud:



c) On the Summary & Settings menu, select Codes.




c) On the Project menu, select Project Codes.

Navigate to the project settings page

In Primavera Cloud:



c) On the Summary & Settings menu, select Settings.




c) On the Project menu, select Project Settings.


329

Navigate to the program settings page

In Primavera Cloud:

1) In the object selector, select a program.


a) On the Summary & Settings menu, select Settings.



b) In the Open dialog box, select the Programs tab, select a program, and then select Open.

c) On the Program menu, select General.

Navigate to the program codes page

In Primavera Cloud:

1) In the object selector, select a program.

a) In the sidebar, select Summary & Settings.

b) On the Summary & Settings menu, select Codes.



b) In the Open dialog box, select the Programs tab, select a program, and then select Open.

c) On the Program menu, select Program Codes.

Navigate to a dictionary page

In Primavera Cloud:



c) On the Summary & Settings menu, select Dictionaries, and then select a dictionary item.




c) On the Dictionaries menu, select a dictionary item.

Navigate to the Calendars dictionary page

In Primavera Cloud:



c) On the Summary & Settings menu, select Dictionaries, and then select Calendars.


330




c) On the Dictionaries menu, select Calendars.

Navigate to the Codes dictionary page

In Primavera Cloud:



c) On the Summary & Settings menu, select Dictionaries, and then select Codes.




c) On the Dictionaries menu, select Codes.

Navigate to the Curve Profiles dictionary page

In Primavera Cloud:



a) On the Summary & Settings menu, select Dictionaries, and then select Curve Profiles.




c) On the Dictionaries menu, select Curve Profiles.

Navigate to the Units of Measure dictionary page

In Primavera Cloud:



c) On the Summary & Settings menu, select Dictionaries, and then select Units of Measure.





331

c) On the Dictionaries menu, select Units of Measure.

Navigate to the Locations dictionary page

In Primavera Cloud:



c) On the Summary & Settings menu, select Dictionaries, and then select Locations.




c) On the Dictionaries menu, select Locations.

Navigate to the Currencies dictionaries page

In Primavera Cloud:



c) On the Summary & Settings menu, select Dictionaries, and then select Currencies.




c) On the Dictionaries menu, select Currencies.

Navigate to an object configuration page

In Primavera Cloud:



c) On the Summary & Settings menu, select Defaults & Options, and then select an object.




c) On the Workspace menu, select Configuration, and then select an object.


332

Navigate to the Activity configuration page

In Primavera Cloud:



c) On the Summary & Settings menu, select Defaults & Options, and then select Activity.




c) On the Workspace menu, select Configuration, and then select Activity.

Navigate to the Project configuration page

In Primavera Cloud:



c) On the Summary & Settings menu, select Defaults & Options, and then select Project.




c) On the Workspace menu, select Configuration, and then select Project.

Navigate to the Program configuration page

In Primavera Cloud:



c) On the Summary & Settings menu, select Defaults & Options, and then select Program.




c) On the Workspace menu, select Configuration, and then select Program.

Navigate to the Resource Assignment configuration page

In Primavera Cloud:



333


c) On the Summary & Settings menu, select Defaults & Options, and then select Resource Assignment.




c) On the Workspace menu, select Configuration, and then select Resource Assignment.

Navigate to the Resource/Role configuration page

In Primavera Cloud:



c) On the Summary & Settings menu, select Defaults & Options, and then select Resource/Role.




c) On the Workspace menu, select Configuration, and then select Resource/Role.

Navigate to the WBS configuration page

In Primavera Cloud:



c) On the Summary & Settings menu, select Defaults & Options, and then select WBS.




c) On the Workspace menu, select Configuration, and then select WBS.

Navigate to the Manage Services page

In Primavera Cloud:

a) In the header, select your username.

b) On the User menu, select Manage Services.



334

On the User menu, select Manage Services.

Navigate to the Preferences page

In Primavera Cloud:

a) In the header, select your username.

b) On the User menu, select Preferences.


On the User menu, select Preferences.

335

Oracle Primavera Cloud Application Administration Guide

Copyright © 2014, 2020, Oracle and/or its affiliates. All rights reserved. Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are “commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate failsafe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

This software or hardware and documentation may provide access to or information on content, products and services from third-parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.

Copyright