Oracle Primavera Cloud (OPC) + Datagrid Integration

Overview

What is Oracle Primavera Cloud (OPC): a cloud-native project planning, scheduling, resource, risk, and portfolio management platform built for the built world.

Oracle Primavera Cloud (OPC) runs on Oracle Cloud Infrastructure (OCI) and connects owners and delivery teams to shared CPM schedules, resource pools, risk registers with native Monte Carlo simulation, and cost/fund tracking, all within a single SaaS environment. OPC is part of Oracle's broader Smart Construction Platform, alongside Oracle Aconex and Oracle Primavera Unifier.

Datagrid's OPC integration pulls project data, including activities, projects, risk records, users, cost categories, and Work Breakdown Structures, into Datagrid's agentic AI platform. Datagrid's AI agents then process that data autonomously by computing schedule variances against baselines, flagging critical path slippage, generating EVM metrics, or routing structured findings to downstream systems and dashboards. Flows run on a defined schedule or respond to Datagrid trigger events like source changes.

The data flows between OPC and Datagrid cover the core objects project controls teams rely on daily. Activity-level schedule fields such as planned dates, actual dates, percent complete, and critical flag, WBS hierarchies for portfolio roll-ups, risk register entries for quantitative analysis, and cost categories for budget tracking all move through the integration. Datagrid can blend this OPC data with 50+ other sources, including field systems, BIM platforms, and legacy scheduling tools.

This integration focuses on one-way ingestion from OPC into Datagrid for supported data objects. The article does not describe OPC writeback, and OPC push-based webhooks are addressed separately in the FAQ.

How to integrate Oracle Primavera Cloud with Datagrid

Project teams use this setup to give Datagrid read access to Primavera Cloud schedule, risk, cost, and project data. The steps below cover how to configure the connection, authenticate with OPC, and review the data Datagrid syncs. This section starts with the connection workflow, then covers authentication and synced objects.

Configure the connection

1. Open your Datagrid workspace and go to Settings > Connectors > Add New.

2. Search for Oracle Primavera Cloud (OPC) in the connector library.

3. Enter your OPC server URL (the base URL follows the pattern https://<SERVER_URL>/api/restapi/).

4. Authenticate using your OPC credentials (see authentication details below).

5. Select the data objects you want to sync: Activities, Projects, Risk, Users, Cost Category, and/or WBS.

6. Configure your sync schedule or trigger conditions (time-based schedule, source change, or Datagrid webhook trigger).

7. Save and test the connection.

Authenticate with OPC

OPC uses an OAuth Bearer Token flow. The standard method for OCI-hosted instances exchanges Base64-encoded credentials for a Bearer token via the primediscovery endpoint. In Oracle's documented token request, the scope value uses http://<SERVER_URL>/api:

POST https://<SERVER_URL>/primediscovery/apitoken/request?scope=http://<SERVER_URL>/api Authorization: Basic <Base64-encoded-username-and-password>

The returned access_token is valid for 3,600 seconds (1 hour). For machine-to-machine integrations running on a schedule, OPC also uses a JWT Bearer grant type with 7,200-second (2-hour) token expiry and refresh token support.

Note: OAuth integrations targeting Oracle US Defense Cloud (OC3) deployments must be registered through the Oracle Construction and Engineering Lobby to receive a Client ID and Client Secret. This is a separate step from configuring the connection in Datagrid.

Select the data to sync

The OPC integration syncs six core data objects into Datagrid's workspace for transformation, cross-referencing, and automated reporting.

• Activities — OPC → Datagrid, Schedule activities with planned/actual dates, percent complete, critical flag, cost fields

• Projects — OPC → Datagrid, Project metadata, start/end dates, workspace assignments

• Risk — OPC → Datagrid, Risk register entries, categories, probability/impact scoring

• Users — OPC → Datagrid, User records and assignments

• Cost Category — OPC → Datagrid, Cost classification structures

• WBS — OPC → Datagrid, Work Breakdown Structure hierarchies and node metadata

Sync runs on a configurable schedule or in response to Datagrid trigger events. Data is returned in JSON format from OPC's REST API.

For full setup details, use the Datagrid documentation linked above.

Why use Oracle Primavera Cloud with Datagrid

Project teams use this integration to keep schedule, cost, and risk workflows connected to the rest of the project stack.

• Automated schedule variance detection: Datagrid AI agents compare current activity dates against baseline data from OPC and flag critical path slippage and float erosion without manual report pulls.

• Cross-platform data blending: Combine OPC schedule and risk data with field data, BIM models, or legacy schedules within a single workspace.

• Scheduled and event-driven ingestion: Run data syncs on a fixed schedule or trigger them from source changes so project controls dashboards reflect the latest OPC data.

• Risk register intelligence: Datagrid AI agents process unstructured field signals such as RFIs, daily reports, and change orders, then match them to the correct OPC risk records, WBS nodes, or activity IDs for analysis and reporting workflows.

• Reporting without manual assembly: Generate interactive dashboards from OPC data and share them directly with project teams or embed them into document management and collaboration tools.

• WBS-level portfolio roll-ups: Pull hierarchical WBS structures from OPC to aggregate schedule and cost performance across an entire capital program.

What you can build with Oracle Primavera Cloud and Datagrid

This integration fits project teams that need schedule intelligence, cross-system validation, and reporting workflows that run without spreadsheet handoffs.

Common workflows include:

• Live schedule health dashboards with automated alerting: Pull activity-level data from OPC, including planned start and finish dates, actual dates, percent complete, and the critical flag, then compare it against baseline snapshots. A Datagrid AI agent computes the delta between baseline and current schedule, identifies critical path activities that have slipped, and routes alerts to team chat tools or email. Project controls teams get daily schedule health summaries without opening OPC or building manual reports.

• Cross-platform schedule synchronization between OPC and field systems: On large programs, owners run OPC for master scheduling while contractors track field progress in other project systems. A Datagrid AI agent extracts OPC activities, WBS structures, and milestone dates, maps them to contractor system structures, and detects conflicts such as a successor activity marked complete before its predecessor closes. This keeps the owner's schedule of record aligned with actual field progress across multiple platforms.

• Automated earned value management (EVM) reporting: Extract planned and actual cost fields per activity from OPC, including at-completion costs, planned labor and material costs, and percent-complete values. A Datagrid AI agent computes CPI and SPI metrics, flags cost overrun trajectories, and generates narrative variance summaries. The output routes to BI dashboards or executive email digests, replacing multi-day manual EVM spreadsheet compilation.

• Document-driven risk register workflows: RFIs, change orders, and daily field reports contain schedule- and cost-relevant information that rarely reaches OPC in structured form. A Datagrid AI agent processes these project files, extracts impacted activities, requested time extensions, and cost impacts, then matches them to the corresponding OPC risk records and structured fields such as category, probability, impact rating, and response plan linkage for downstream analysis or custom API workflows. This reduces the lag between a field event and its formal capture in project controls workflows.

These workflows give operators running mission-critical programs a more consistent path from raw project data to action.

Resources and documentation

• OPC REST API reference (G50269-01) — full endpoint index with Swagger spec download

• OPC REST API endpoints index — versioned endpoint listing

• OPC authentication guide — Basic Auth to Bearer Token — standard token exchange flow

• OPC authentication guide — JWT Bearer grant (M2M) — non-interactive machine-to-machine auth

• OPC activity endpoints reference — activity CRUD, batch, and baseline data retrieval

• OPC WBS endpoints reference — WBS CRUD, import, and hierarchy operations

• Datagrid blog — OPC live scheduling analytics — walkthrough of schedule analytics using OPC data in Datagrid

Frequently asked questions

Understand the authentication method for API connections

The standard method for OCI-hosted deployments is a Basic Auth to OAuth Bearer Token exchange. You Base64-encode your username and password, POST them to the primediscovery/apitoken/request endpoint, and receive a Bearer token valid for 1 hour. For automated server-to-server integrations, OPC also supports a JWT Bearer grant type with 2-hour tokens and refresh token support. Full OAuth 2.0 via Lobby is currently limited to US Defense Cloud (OC3) deployments.

Review the OPC data objects Datagrid syncs

The Datagrid OPC integration currently supports six data objects: Activities, Projects, Risk, Users, Cost Category, and Work Breakdown Structure (WBS). The underlying OPC REST API exposes 26+ entity types, including Resources, Assignments, Documents, Portfolios, Programs, and Budget Items, and Datagrid accepts requests for additional endpoint support.

Check whether Oracle Primavera Cloud supports webhooks

No. OPC does not document any webhook or event-push capability. Integrations use polling-based patterns. Long-running async operations like risk analysis and project scheduling require polling the job status endpoint (GET /api/restapi/action/jobStatus/{jobId}). In Datagrid, you configure scheduled syncs or Datagrid-side trigger-based flows to pull updated data at defined intervals.

Determine whether Oracle registration is required before connecting

Not for the standard Basic Auth to Bearer token flow described above for typical OCI-hosted instances. Registration is required for OAuth-based integrations that use the Oracle Construction and Engineering Lobby to receive a Client ID and Client Secret, including Oracle US Defense Cloud (OC3) deployments. For machine-to-machine setups using the JWT Bearer grant type, you also need registered credentials. New OAuth integration users for cloud environments require a service request through Primavera Administration.

Handle large datasets with more than 5,000 records

The OPC API enforces a maximum of 5,000 objects per response. If a query returns more than 5,000 records, the API silently truncates the results without returning an error. You must implement pagination using start and limit parameters. Oracle recommends using the REC_COUNT_ONLY parameter first to get the total count, then looping through pages. Full details are in the OPC pagination documentation.

Similar integrations

Teams that use OPC often also work across adjacent Primavera systems.

• P6 EPPM: Oracle's on-premises CPM scheduling tool and OPC's predecessor in the Primavera ecosystem, commonly used alongside OPC on programs transitioning to cloud.

• P6 Primavera Data Service (PDS): A separate data access layer for Primavera P6, used for reporting and integration flows distinct from the P6 EPPM application API.