Critical-path scheduling
Activity logic, relationships, calendars, and constraints produce dates, float, and the critical path. Several users can work on schedules, and several projects can be scheduled together.
Enterprise scheduling, baselines, resources, and portfolio reporting, set up around how your planners and project controls teams actually work.
Illustrative. Your own process is designed with you.
Oracle describes Primavera P6 EPPM as an integrated solution for prioritizing, planning, managing, and delivering projects, programs, and portfolios. It is a web-based enterprise application, with P6 Professional as the Windows client for planners, and it is available on-premises and in cloud deployments.
Where Unifier controls cost and process, P6 is the scheduling backbone: the logic, the calendars, the resources, and the baseline everything else is measured against.
Activity logic, relationships, calendars, and constraints produce dates, float, and the critical path. Several users can work on schedules, and several projects can be scheduled together.
A baseline is a snapshot of the schedule that later updates are compared against. Baselines can be typed, for example a client sign-off or a mid-project baseline, and progress is recorded by planners and team members.
Labor, nonlabor, and material resources, with roles planned first and resources assigned later. Histograms, usage profiles, and leveling help find over-allocation and plan capacity.
Projects are organized into portfolios and programs for consistent roll-up, grouped by business unit, region, or client. Project templates let you reuse structures in full or in part.
Reports and dashboards in the web application, with additional reporting and analytics options in the P6 EPPM suite, including the Primavera data warehouse.
Oracle positions P6 EPPM to share data with financial, human capital, and ERP systems, and to work with Primavera Cloud, Unifier, Primavera Risk Analysis, and Primavera Earned Value Management. Integration is available through APIs and web services.
These describe what the platform supports. Your actual scope is set during assessment.
P6 EPPM is the enterprise web application with dashboards, portfolios, projects, resources, reports, and administration. P6 Professional is the Windows desktop client used by planners, and it can work against the same enterprise database.
No. Primavera Cloud is a separate cloud product. P6 EPPM can be deployed on-premises or in the cloud. Choosing between them is part of our advisory work.
Schedule risk analysis is done with Oracle Primavera Risk Analysis, an optional solution that works with P6 data. MethoSys works in both.
Upgrades and migrations are in scope: assessment, test upgrade, data validation, and cutover. The approach depends on your current version, data quality, and downtime constraints.
By agreeing standards up front (logic, constraints, calendars, durations, and update rules), then building them into templates, layouts, and a review checklist, so that quality is checked the same way on every update.
Oracle, Primavera, Unifier, uDesigner, and Aconex are trademarks of Oracle Corporation and its affiliates. They are named here to describe products MethoSys works with, and do not imply sponsorship or endorsement. Capability descriptions summarize Oracle's published product documentation; the scope and release you have licensed determine what is available to you.
Tell us what you are running, replacing, or planning. We reply with what we would look at first.
Platform selection, implementation, integration, reporting, and support.
A roadmap concept for schedule quality and what-if analysis. Availability has not been announced.