Every product in Oracle's construction suite counts contractors differently, and getting the classification wrong upgrades a cheap seat into an expensive one silently. This guide shows where each metric bites, where the config traps sit, and how to cap external headcount before it inflates your renewal.
Every product in Oracle's construction suite counts contractors differently, and getting the classification wrong upgrades a cheap seat into an expensive one silently. This guide shows where each metric bites, where the config traps sit, and how to cap external headcount before it inflates your renewal.
The single most expensive mistake in Oracle Construction and Engineering (CEGBU) deployments is assuming one contractor-counting rule applies across P6, Unifier, and Aconex. It does not. P6 counts every authorized individual as a full named user with no external tier. Unifier has a purpose-built cheap external tier, but only if you set one specific keyword correctly. Aconex, by contrast, does not count external users at all, it prices on project value. A contractor who touches all three products can consume two paid licenses (P6 and Unifier) while costing nothing incremental in Aconex. If you provision blindly, you pay full freight on every external firm in the ecosystem.
This subpage is the construction-specific counterpart to the broader P6 contractor counting problem, extended to cover Unifier and Aconex. Read it alongside the CEGBU licensing pillar, which decodes the full suite. Our position is buyer-side: we want the smallest defensible license count, and the classification rules below are how you get there.
| Product | External user tier | Counting trigger | Enforcement |
|---|---|---|---|
| P6 EPPM (on-prem) | None. Everyone is an Application User | Any individual who accesses the software | No in-app block. Audit-based |
| P6 Cloud | None. Everyone is a Hosted Named User | Authorization, not activity | Contractual, audit-based |
| Unifier | Collaborator User (Partner tier) | 'Contractor' user-type keyword in admin | In-app block when count exceeded |
| Aconex | N/A. Unlimited participants | Total project construction value | No per-user cap, no enforcement |
P6 is licensed per named individual. Oracle's commercial model applies to the Application User metric on-prem: each license pertains to a specific number of users, and you may hold only as many users as you have purchased (Source: P6 Consulting FAQs, December 2024). There is no concurrent-user model and no external or contractor discount tier. A subcontractor scheduler who logs into your P6 environment twice a month consumes exactly the same license as a full-time internal planner.
In the cloud, the metric is Hosted Named User, defined as an individual authorized to access the service regardless of whether they are actively accessing it at any given time (Source: Oracle Primavera Global Price List). That definition is deliberate. It defeats the most common buyer defense, the "they only occasionally log in" argument. Authorization is the trigger, not activity. If a contractor's account exists and is enabled, it counts, even if the person left the project six months ago and never disabled the login.
In P6, an enabled login is a paid login. Dormant contractor accounts are audit findings waiting to be counted.
The integration trap compounds this. A P6 license does not cover Unifier, and a Unifier license does not cover P6. If data flows between the two systems, you still need appropriate licenses for users in each. A user who accesses both products needs two licenses, one per product (Source: Atonement Licensing, May 2025). Do not let anyone tell you that integrated systems share entitlements. They do not.
Unifier is the product where classification discipline pays off, because it has three user tiers: Standard, Portal, and the external Collaborator tier. The Collaborator User is a Partner User for external parties such as vendors and subcontractors, with deliberately limited functionality (Source: Oracle Primavera Unifier General Administration Guide v25, April 2025). It is cheaper than Standard, and it exists precisely so you do not burn a full Standard license on an external firm that only needs to exchange documents and read logs.
Here is the trap, and it is the most important sentence in this article. The keyword "Contractor" is what makes a user consume a cheap Collaborator license. If you assign the Contractor User Type in Primavera Administration, the user consumes a Collaborator license. Any other classification (Employee, Intern, Temp, External, Service, or Generic) consumes a Standard license (Source: Oracle Primavera Unifier General Administration Guide v22, February 2026). Read that again. Classifying an external subcontractor as "External" instead of "Contractor" silently upgrades them to a full Standard license. The word that sounds correct is the expensive one.
In Unifier, the user type 'External' costs a Standard license. The user type 'Contractor' costs a Collaborator license. The intuitive label is the wrong one.
Oracle's own documentation is blunt about this: while setting up Collaborator-type users, you must select the user type as "Contractor" in the Cloud admin tool, and you must not use "Contractor" for any user who should count toward Standard (Source: Oracle Primavera Unifier General Administration Guide v22, February 2026). This is a two-way discipline. Misclassify externals as anything but Contractor and you overpay. Misclassify internal staff as Contractor and you are out of license compliance the moment they use Standard-tier functionality. For the full user-type and module structure, see our breakdown of the Unifier named user metric and the records trap.
Unlike P6, Unifier enforces license counts inside the application. When you exceed a tier, the system displays "License limits for Standard/Portal/Collaborator [exceeded]" and blocks the provisioning (Source: Oracle Primavera Unifier General Administration Guide v22, February 2026). This is genuinely useful for a buyer: you cannot accidentally over-consume Standard licenses without hitting a wall. But it introduces a procurement dependency. Only the Site Administrator, which for cloud customers is the Oracle Cloud Administrator, can change license terms. To let your company administrator add Collaborator users, Oracle must first seed the Collaborator license pool (Source: Oracle Primavera Unifier General Administration Guide v25, April 2025).
That means adding external capacity is not self-service. It routes through Oracle. Plan for lead time on Collaborator pool expansion, and negotiate the Collaborator quantity generously up front, because expanding it mid-project means a purchasing conversation with the vendor exactly when your leverage is lowest. Size the Collaborator pool to peak external participation, not average.
The Collaborator tier is cheap because it is limited. A Collaborator User has access to the Mailbox node and its sub-nodes, the Document Manager, logs, and reports, and if permitted, can view and create user-defined reports (Source: Oracle Primavera Unifier General Administration Guide v25, April 2025). What it cannot do is run the full workflow and business-process functionality reserved for Standard. Before you classify a subcontractor as Collaborator, confirm the workflows they need are inside that boundary. If they must originate or approve business-process records, they need Standard, and no keyword changes that. The cost discipline is real, but do not force a Collaborator classification onto a user whose actual work requires Standard, because that becomes a compliance gap the moment they act beyond their tier.
Two further wrinkles matter for external planning. First, Unifier Essentials, the lighter SKU, does not support the Portal User type at all (Source: Oracle Primavera Unifier Essentials General Administration Guide, April 2025). If your contractor access strategy relies on portal-only users, Essentials will not carry it. Second, Oracle now sells dedicated external-collaborator SKUs, including the Primavera Unifier External Collaborator Cloud Service with NEC4 and UK Sovereign Cloud variants (Source: Primavera Unifier Licensing Information User Manual G31393-01, April 2026). If your contract predates these SKUs, ask whether the dedicated external-collaborator line item prices your third-party population more cheaply than adding Collaborator seats to the base subscription.
Aconex breaks the pattern completely. Its commercial design is that one paying organization covers the whole project ecosystem, paid and non-paying participants alike. Customers historically chose from three models: unlimited subscription for a specific project, unlimited enterprise subscription across all projects, or user-based pricing for the minority who preferred it. One organization pays for Aconex across the entire project, and the platform supports every organization in the ecosystem, paying and non-paying (Source: Saniel Ventures, May 2022).
The practical consequence: once the owner or general contractor pays, the platform is available to every firm on the project at no additional charge and with no limit on the number of users or the amount of data (Source: AECbytes Review, May 2015). Pricing is driven by total project construction value, factoring in complexity, location, and expected participation, not by headcount (Source: GulfSaasReview, July 2026). This is the explicit contrast with seat-based rivals. Where Procore or Autodesk charge by user seat or by annual volume tier (so adding 200 external subcontractors inflates cost rapidly), Aconex lets the main contractor invite unlimited third-party subcontractors, suppliers, and municipal inspectors into the common data environment at zero incremental per-user cost (Source: GulfSaasReview, July 2026).
In Aconex you do not cap the contractor count. You cap the project value that drives the fee, and you police who pays for what across the ecosystem.
For roughly 20 years the unlimited model was Aconex's strategic North Star, lowering total cost of ownership against traditional per-seat pricing (Source: Saniel Ventures, May 2022). Note also that Aconex is subscription-only, whereas Unifier supports both subscription and perpetual (Source: DRMcNatty & Associates, March 2023). This changes how you forecast external spend: in Aconex there is no perpetual buffer, and the recurring fee scales with project value over the project life. The negotiation lever is not user count, it is the project-value basis and which entity in a joint venture carries the paying subscription. For the deeper commercial structure, read our analysis of Aconex per-project versus enterprise licensing.
The expensive scenario is the contractor who touches multiple products. Because P6 and Unifier entitlements do not cross over, a subcontractor scheduler who also files documents in Unifier needs a P6 named user and a Unifier license, correctly typed as Contractor for the Collaborator tier. If that same person also participates in the Aconex CDE, Aconex adds nothing per-user because it is covered by the project-value subscription. So the same individual can cost two paid seats and zero, simultaneously, depending on the product.
This is why a single cross-product user register matters. In our experience, construction estates that manage P6, Unifier, and Aconex separately end up with duplicated and stale external accounts across all three, with nobody owning the reconciliation. Build one register keyed to the individual, showing product access, user type, and the entitlement consumed. That register is also your first-line audit defense. When Oracle examines the Primavera and Unifier estate, they reconcile provisioned accounts against purchased quantities, and the burden is on you to show the count is clean. See what that review covers in our note on Oracle audit scope across the Primavera and Unifier estate.
The through-line is that CEGBU contractor cost is a classification and hygiene problem, not a pricing problem. Aconex removed the count. Unifier turned it into a keyword. P6 left it as raw named-user discipline. Get the classification right in each and you stop paying full price for firms that should sit in cheap or free tiers.
No, it does the opposite. The 'External' user type consumes a full Standard license. Only the 'Contractor' user type consumes the cheaper Collaborator license. Oracle's documentation is explicit that 'Contractor' is reserved for the Collaborator tier and must be used for external parties you want on that tier.
Yes. P6 and Unifier entitlements do not cross over. A user who accesses both products needs two licenses, one for each, even when the two systems are integrated. Integration does not negate per-product licensing.
It does not count them at all. Aconex is priced on total project construction value, and once the owner or general contractor pays, all firms in the project ecosystem participate at no additional per-user cost and with no user cap. This is the defining contrast with seat-based tools like Procore or Autodesk.
In the cloud, yes. The Hosted Named User metric counts anyone authorized to access the service regardless of whether they actively log in. An enabled account is a paid and countable account. Disable dormant contractor logins quarterly to keep the count clean.
Not fully. Company administrators can assign users to the Collaborator tier, but only the Site Administrator (the Oracle Cloud Administrator for cloud customers) can seed the Collaborator license pool first. That is a procurement dependency, so size the pool to peak external participation up front.
Yes. Unifier enforces license counts in-app and displays a 'License limits exceeded' message for the Standard, Portal, or Collaborator tier when you exceed the purchased quantity. This is unlike P6, which has no in-app block and is policed through audit.
Oracle Primavera P6 compliance. Named user counting, EPS access, the contractor trap, and the audit defense framework.
Gated with a work email on the download page. No sales follow up you did not ask for.
Get the White Paper →
500+ enterprise clients. 11 vendor practices. Industry recognized. One conversation can change what you pay for the next three years.
One buyer side briefing a week. Renewal signals, audit moves, and the levers that work. No vendor spin.
