A Cost Breakdown Structure (CBS) in Oracle Primavera Cloud (OPC) is comprised of cost codes classified into three types: expense, capital, or none. The codes are organized based on segment definitions to form a flat or hierarchical structure. A CBS is used alongside the Work Breakdown Structure (WBS). The WBS breaks down project work, and the CBS represents the associated costs.

Familiarity with the workspace hierarchy and reporting requirements helps ensure that the CBS is set up to allow required rollup functionality.

Are you looking for a resource display in Oracle Primavera Cloud (OPC) that clearly indicates the under/overallocation of resources (and roles)?

Let’s have a quick look at a couple of functionality pieces now available in Oracle Primavera Cloud (OPC) that you may not have used yet. They were added in OPC v25.7.

When using task cards, you can now display the crew size on the task cards. When the task card is displayed, the icon with the crew size number can be included with the display.

With the new release of the Emerald BI-GanttView visual for Power BI, we wanted to take the chance to look at some of the features that this visual offers.

You can add as many global changes as you need for your project in Oracle Primavera Cloud (OPC).

Below a list of some of the new features in Oracle Primavera Cloud (OPC) v25.6 that I thought you might find interesting.

The OPC-Integrator can extract information from, and load information to, multiple files within Oracle Primavera Cloud (OPC) in the same load. This means that there’s no need to run separate extracts from each file when you need the same (or similar) data pulled from each file. With the OPC-Integrator, you can just select the definition or select the modules you need, configure them, and then select all the files you want to download the module information from. Then, simply click the download button!

Are you an Application Administrator in Oracle Primavera Cloud (OPC) and looking to add users?

Recently, when working with a client who was combining several Primavera P6 databases into one, we discovered some interesting things with respect to layouts and filters.

In the latest version of Primavera P6 v24, there have been major changes to updating baselines, including a visual overhaul and some new functionality. However, some of our clients have recently noticed that their baselines weren’t updating correctly. While the Job Services logs showed that everything was updating properly, in reality users weren’t seeing any changes when they actually went into their projects to check if their baseline changes were reflected.

When creating a schedule in Oracle Primavera Cloud (OPC), you should consider using the Scope App in conjunction with the Schedule App. With the Scope app, you can create scope items and choose whether to connect them to activities in the schedule, depending on your project requirements. Scope items are the materials or products needed to complete a project.

At Emerald Associates, we’ve worked with many clients who’ve had to migrate standalone databases over to a shared environment in Primavera P6. One of the struggles they often face is getting their EPS structures and global data out of their standalones and into their new Cloud environments, especially when their databases are in a SQLite format.

New features have been added to both Oracle Primavera Cloud (OPC) V25.1 and V25.2.

If you’re a longtime user of Primavera P6, you may have noticed that there’s been a change to the ability to update your baselines.

It might not seem like a big deal to give meaningful or unique names to your filters and layouts in Primavera P6, especially when they are your own user filters and layouts. After all, you made the filter and likely know what it’s for. However, having an abundance of unnamed filters can quickly become an issue.