According to Oracle’s official documentation, Primavera P6 EPPM is designed to support project, program, and portfolio management, bringing together planning, scheduling, resource management, and performance control.
When a company has 10 projects—and 10 separate files
Consider a main contractor delivering 10 construction projects across different locations. Each project has a dedicated planner responsible for developing and updating its schedule, with its own activities, handover milestones, and resource plan. At the individual project level, this approach may be sufficient.
Challenges arise, however, when projects share survey crews, BIM engineers, construction equipment, or QA/QC personnel. A design change on Project A may require the engineering team to stay longer, even though that team is scheduled to start work on Project B the following week. When schedules are managed in separate files, this resource conflict may go unnoticed until it disrupts delivery.
At this point, the question for the project management team is no longer simply how many days each project is behind schedule. It is how quickly and accurately the company can identify and assess the impact across projects. This is the challenge that multi-project management solutions such as Primavera P6 are designed to address.
From single-project scheduling to multi-project management
A comprehensive schedule includes a work breakdown structure (WBS), activities, logical relationships, milestones, a critical path, and a baseline. These elements help project teams plan and track delivery. As the number of projects grows, however, companies must also manage factors beyond any individual schedule: shared resources, cross-project dependencies, data standards, and consolidated reporting to support management decisions. Single-project management focuses on the performance of an individual project. Multi-project management requires visibility and control over how projects interact within the same organization.
Primavera P6 supports this transition through a structured data environment, enabling companies to organize, schedule, link, and analyze multiple projects within a consistent management framework.
1. Enterprise Project Structure (EPS): Organizing projects within a unified hierarchy
When projects are managed independently, companies may struggle to maintain consistent project classifications, access permissions, and consolidated reporting. One project may be organized by department, while another follows a regional or project-type structure, resulting in inconsistent data.
In Primavera P6, the Enterprise Project Structure (EPS) is a hierarchy used to organize all projects within the database. According to Oracle, the EPS can include multiple levels to reflect the company’s organizational structure, scope of work, and reporting requirements. For example, a main contractor could structure its EPS by geographical region, grouping projects in northern Vietnam, southern Vietnam, and international markets. Within each region, projects could be further classified by type, such as industrial facilities, transport infrastructure, urban developments, or commercial buildings.
This structure enables companies to manage projects at each organizational level, support access control through the Organizational Breakdown Structure (OBS), and organize and consolidate budget, cost, and resource data.
The value of the EPS goes beyond arranging projects in a hierarchy. It provides the foundation for a structured data management environment, where each project is managed individually while remaining part of the company’s broader management system.
Source: Oracle – Enterprise Project Structure overview; Managing projects using the EPS.
2. Multi-project scheduling: Scheduling multiple projects together
One limitation of managing schedules in separate files is that assessing the impact of a change often requires several rounds of manual consolidation. When a project’s completion date changes, the planner must update the schedule, identify affected activities, and coordinate adjustments with the relevant teams. When the change affects multiple projects, this process becomes more complex.
Multi-project scheduling in Primavera P6 Professional allows users to open and schedule multiple projects in the same session. According to Oracle’s guidance, users can retain a separate data date for each project or apply a common data date, depending on their scheduling requirements.
This capability enables teams to analyze multiple project schedules within a single environment. For example, if Project A is delayed by two weeks due to a design change, the manager can update the schedule and reschedule the related projects. Where appropriate logical relationships have been established between activities across projects, the scheduling results can reflect the impact on successor activities.
However, Primavera P6 does not automatically identify every impact simply because projects share the same database. The results depend on the schedule structure, defined relationships, and scheduling options.
Source: Oracle – P6 Professional User Guide, Schedule a project.
3. Inter-project dependencies: Managing dependencies across projects
Construction projects often have direct dependencies on one another. One project may need to complete a site handover before another can begin equipment installation. Similarly, infrastructure works may require inspection and acceptance before related projects can move to the next phase. If these dependencies are missing from the schedules, delays may only become apparent when successor activities cannot start as planned.
Primavera P6 supports inter-project dependencies, also known as external relationships, allowing users to link activities across different projects. According to Oracle’s documentation, these links can use finish-to-start (FS), start-to-start (SS), finish-to-finish (FF), and start-to-finish (SF) relationships. For example, a site handover activity in Project A can be linked to the start of mechanical, electrical, and plumbing (MEP) installation in Project B. If the handover date changes, the scheduling results can reflect the impact on Project B’s start date, depending on the relationship logic and scheduling settings.
This gives planners and project managers a clearer basis for analyzing how changes affect connected projects, particularly at key interfaces such as site handovers, design approvals, equipment deliveries, and inspections and acceptance.
To use this capability effectively, companies need consistent standards for WBS structures, activity IDs, milestones, and schedule updates. Incorrect relationships can produce results that do not reflect actual project conditions.
Source: Oracle – P6 Professional User Guide, Relationships; Check a schedule.
4. Shared resources: Planning and coordinating resources across projects
Primavera P6 supports a resource hierarchy for managing labor, equipment, and materials across multiple projects. These resources can be assigned to individual activities, with associated calendars, usage levels, and costs. Using resource assignment data, managers can assess demand over time and identify overallocation. For example, a 3D survey team may be assigned to Project A during weeks 12–14 and Project B during weeks 13–15. If both projects require the team’s full capacity, a resource conflict arises during weeks 13–14.
Resource leveling in Primavera P6 can adjust activity schedules based on resource limits and defined priorities.
Based on the analysis, managers can consider rescheduling work, revising priorities, adding personnel, or outsourcing to meet project requirements. Resource management in Primavera P6 therefore goes beyond assigning responsibilities. It helps companies assess whether they have sufficient capacity when multiple projects compete for the same resources.
Source: Oracle – Understanding Data Structures in P6 EPPM; P6 Professional, Resource Leveling.
5. Cross-project roll-up: Consolidating data for management decisions
When data is fragmented, consolidated reporting often involves extensive manual collection, reconciliation, and processing. This increases reporting time and the risk of inconsistencies.
Primavera P6 Professional provides cross-project roll-up capabilities to consolidate schedule, cost, and earned value data from multiple projects. According to Oracle, its tracking features support dynamic cross-project roll-ups for these areas. With current data and appropriate configuration, managers can monitor start and finish dates, progress, costs, and performance indicators.
Earned value management (EVM) integrates scope, schedule, and cost data to assess project performance. Measures such as planned value (PV), earned value (EV), actual cost (AC), the schedule performance index (SPI), and the cost performance index (CPI) help teams evaluate performance against the plan.
For the PMO, consolidated data helps identify projects that require closer attention. For senior management, it supports portfolio reviews and resource allocation decisions.
However, consolidated reporting does not mean that all data is updated in real time. Report quality depends on update procedures, system configuration, input data, and calculation settings.
Source: Oracle – Introducing P6 Professional.
6. From project controls to portfolio management
At the project controls level, the focus is on schedules, baselines, resources, costs, and changes during execution. Planners and project managers use this data to assess performance, identify variances, and recommend corrective action.
At the program management level, companies coordinate projects with related objectives, timelines, or resources. An infrastructure development program, for example, may include several component projects that must follow a coordinated delivery sequence.
At the portfolio management level, the focus expands to the entire project portfolio. Senior management and the PMO consider priorities, resource utilization, delivery performance, and each project’s alignment with the company’s strategic direction.
The distinction between these levels is not simply the number of projects being monitored. It is the nature of the decisions being made. Project managers focus on delivering individual projects, while portfolio management involves selecting and coordinating projects to achieve organizational objectives.
Primavera P6 EPPM supports the data foundation and management processes needed for these activities. Its effectiveness still depends on the company’s governance model, access controls, and day-to-day use of the system.
Source: Oracle – Primavera P6 EPPM; P6 EPPM documentation.
Primavera P6: From scheduling to multi-project management
Primavera P6 supports these needs through six key areas:
- EPS: Establishes a consistent structure for organizing projects.
- Multi-project scheduling: Enables multiple projects to be scheduled together.
- Inter-project dependencies: Defines relationships between activities across projects.
- Shared resources: Supports resource allocation and capacity management.
- Cross-project roll-up: Consolidates data for management reporting.
- P6 EPPM: Extends management capabilities to programs and portfolios.
The value of Primavera P6 goes beyond building detailed schedules. It connects scheduling data with the company’s broader management needs.
A single project needs a well-controlled schedule. A company managing dozens of projects needs a system that brings those schedules together within a common management framework.
Primavera P6 solutions from OneBIM
Contact OneBIM to discuss a Primavera P6 tailored to your company’s scale and project management requirements.
Website: www.onebimvn.com | Hotline: 0934 14 44 98 | Email: hoang.lam@onebimvn.com
