Unifier is licensed per Hosted Named User across four user classes and stacked module add-ons, with a License Manager that Oracle controls, not you. This breakdown shows where the metric bites, why On-Hold accounts still cost money, and how to size a renewal that Oracle cannot inflate.
Unifier is licensed per Hosted Named User across four user classes and stacked module add-ons, with a License Manager that Oracle controls, not you. This breakdown shows where the metric bites, why On-Hold accounts still cost money, and how to size a renewal that Oracle cannot inflate.
Oracle prices Primavera Unifier on the Hosted Named User metric. The Global Price List defines a Hosted Named User as an individual you authorize to access the hosted service, regardless of whether that individual is actively using the service at any given moment. Read that clause twice, because it is the source of most Unifier overspend. Authorization, not activity, is the billing trigger. There is no concurrent user option and no device metric. If someone has a login, they consume entitlement even if they log in once a quarter.
Because the metric tracks unique identities, everyone who touches Unifier needs a license: the engineer entering cost data, the manager approving a workflow, the analyst running a report, and the external vendor uploading a submittal. In 25 years of negotiating Oracle Construction and Engineering deals, this is the single most misunderstood rule on the buyer side. Teams routinely assume that read-only or occasional users are free. They are not. If you also run P6 EPPM, note that integration does not merge entitlement. A user who works in both P6 and Unifier needs a license in each product. Our companion analysis on Primavera Cloud versus P6 EPPM licensing covers where those two counts diverge at scale.
Authorization is the billing trigger, not activity. A dormant login costs the same as a power user.
One structural rule sits underneath the whole model: a hosted environment can host only one type of Oracle program. That means a Unifier environment cannot double as a home for another Oracle service. When Oracle quotes you additional environments, understand that each is a discrete purchase, and that has direct cost consequences discussed in the storage and environments section below.
Unifier does not treat all named users the same. The License Manager, the internal enforcement engine, tracks four distinct user classes, each with its own entitlement ceiling. Understanding the boundaries between these classes is where genuine savings live, because the price gap between them is enormous.
| User class | Access scope | Who it is for | Cost posture |
|---|---|---|---|
| Standard User | Full functional access: data entry, workflow approvals, reports, business processes | Internal (Company) and Partner users | Highest per-user list, several thousand dollars per user per year (Atonement, May 2025) |
| Collaborator User (Team for External Collaborators) | Limited access: Mailbox node, view and create User Defined Reports if permitted | External parties, primarily vendors | Add-on priced, minimum 10 users; far cheaper than a Standard seat |
| Portal User | Restricted portal-only access | High-volume, light-touch external users | Lowest per-user, minimum 100 users |
| EVM User | Earned Value Management functionality | Users needing EVM, gated by what you purchased | Separately entitled sub-count |
The Oracle admin guides are explicit that Standard Users cover both Company and Partner users, that any user can be declared a Collaborator but with limited functionality, and that Collaborator status must be granted to external users such as vendors. This matters because the classification decision is where you either save money or leak it. A vendor who only uploads documents and views reports does not need a Standard seat. Mis-classifying external contributors as Standard Users is one of the most expensive errors we see, and it compounds every renewal. We treat that in depth in counting external contractors in Primavera and Aconex deployments.
On the UK G-Cloud 14 price list effective 30 April 2024, the structure priced out as follows: the base Facilities and Asset Management module (including Earned Value Management and Data Access) at 1,311 GBP per Hosted Named User per year, minimum 25 users; Project Controls add-on at 1,192 GBP; Real Estate Management add-on at 636 GBP; Team for External Collaborators at 437 GBP, minimum 10; and Portal User at 16 GBP, minimum 100. The spread between a 437 GBP Collaborator seat and a full-stack internal user carrying multiple modules is the entire savings opportunity. Get the classification right before you get the count right.
Unifier is not a single SKU. The base module is Facilities and Asset Management, and it ships with the Unifier Accelerator base configuration: 65-plus preconfigured business processes, 250-plus layouts, reports and dashboards, and open APIs. On top of the base, Oracle sells Project Controls and Real Estate Management as optional add-ons, each priced per Hosted Named User. The historical Global Price List confirms these break out into distinct cloud service SKUs, including Primavera Unifier Project Controls Cloud Service and Primavera Unifier Facilities and Real Estate Management Cloud Service.
The practical trap here is over-provisioning modules across your whole user base. Oracle sales prefers to attach Project Controls and Real Estate Management to the entire named-user count because it lifts the per-seat total. In reality, module need is rarely uniform. Cost controllers may need Project Controls; facilities staff may need Real Estate Management; a large slice of your users may need neither. Because each module is priced per named user, buying a module for 200 users when only 60 use it is a straight-line overspend of 140 seats at add-on rate. Insist on module counts that match role, not headcount.
Module attach across the full user base is Oracle's margin. Attach by role, and the number falls.
One genuine cost relief: User Defined Reports carry no additional license fee. The Licensing Information User Manual dated April 2026 confirms UDRs are included as part of Unifier, and even Collaborator Users can view and create them if granted permission. Do not let anyone quote you a reporting add-on for UDR capability. That is included.
This is the section that justifies the article title. The License Manager tracks two things: named users and user record limits. When it comes to counting active named users, Oracle's own admin guide (28 April 2025) states plainly that the count includes users with a status of Active OR On-Hold. The term active named user refers to any user in the system with an Active or an On-Hold status. Deactivating a user by setting them On-Hold does not release the entitlement. The seat stays consumed.
We have seen this drive audit findings and renewal disputes repeatedly. Administrators believe they have freed licenses by placing departed staff or completed-project contractors On-Hold. The License Manager disagrees, and so does Oracle at true-up time. The only way to release a Unifier seat is to fully remove the account, not park it. Before any renewal or audit response, run the usage report the License Manager provides and separate Active from On-Hold. Every On-Hold account is a decision you must make deliberately: reactivate, or delete to reclaim the seat.
The system also fires automated overage notifications. The Company Administrator can configure the License Manager to warn when user counts approach the limit, and the system sends notifications when counts exceed available licenses. Treat those notifications as compliance evidence. Oracle can and does use its own telemetry against you in an audit. If you are receiving overage alerts and not acting, you are documenting your own exposure. What Oracle examines across the wider estate is set out in what an Oracle audit examines across the Primavera and Unifier estate.
Here is the leverage problem buyers underestimate. For cloud customers, only the Oracle Cloud Administrator (acting as Site Administrator) can change license terms. Your own Company Administrator cannot add a Collaborator User until Oracle first adds Collaborator licenses at the site level. When editing counts, the Site Administrator enters a combined number for active named users, plus separate sub-counts for Portal users and EVM users where entitlement allows.
The consequence is that you cannot self-serve a right-sizing. You cannot quietly move users between classes without Oracle touching the ceiling. Every adjustment routes through Oracle, which means every adjustment is a commercial conversation. Plan your user mix and module attach BEFORE you sign, because renegotiating mid-term puts you back at the table with the vendor holding the only wrench. This is the opposite of a self-service SaaS model, and buyers who assume flexibility get surprised.
Named users are not the whole bill. Storage is a separately priced add-on. On the same 30 April 2024 UK list, an additional 10 GB of database storage was 477 GBP per year, an additional 50 GB was 1,192 GBP, and an additional non-production environment was 39,332 GBP per year. That last figure is the one to watch. Because a hosted environment can host only one type of Oracle program, and because non-production environments are so heavily priced, Oracle can turn a modest test or training requirement into a five-figure annual line item.
Quantify your storage and environment needs at contract time and negotiate them in as included capacity or a fixed uplift schedule. Do not accept open-ended storage overage terms. A document-heavy Unifier deployment can consume storage fast through attachments and record volume, and the per-increment pricing above compounds. If you also run P6 EPPM, be aware that the embedded database carries its own restricted-use constraints, which we detail in the Oracle database hiding under P6 EPPM.
Support runs at roughly 22 percent of license cost annually, consistent with the wider Oracle Primavera portfolio (Atonement, May 2025). Because Unifier per-user list sits in the same range as P6 EPPM, several thousand dollars per user per year, the support line alone is material at any real user count. For term licenses, the Global Price List sets support at 22 percent of the list perpetual license fee, while term license fees themselves scale by duration: 20 percent of list for one year, 35 percent for two, 50 percent for three, 60 percent for four, and 70 percent for five.
The clause that costs buyers the most is reinstatement. If support lapses and you later need it back, or if an audit finds you running software without current support, Oracle may charge back the missed support fees plus a 150 percent penalty. That penalty structure is precisely why organizations weigh third-party support carefully rather than casually dropping Oracle maintenance. The decision has real consequences, and we lay out the trade-offs in Primavera and Unifier: should you move to third-party support.
A 150 percent reinstatement penalty is not a fee. It is a lock. Model the exit before you lapse.
Turn the mechanics above into a checklist and run it 90 days before any renewal or before responding to any Oracle contact about usage:
Unifier's cost is not driven by a single number. It is driven by the interaction of the named-user metric, the four user classes, the module stack, and a License Manager Oracle controls on your behalf. Buyers who treat it as a flat per-seat product overpay. Buyers who classify precisely, attach modules by role, purge On-Hold accounts, and lock storage and support terms at signing typically take double-digit percentages out of the annual cost. For the full portfolio view including Aconex and P6 EPPM, start with the Oracle Construction and Engineering licensing pillar.
Unifier is licensed on the Hosted Named User metric. Each individual you authorize to access the service consumes a license regardless of whether they actively use it. There is no concurrent user or device option. Users are further split into four classes: Standard, Collaborator, Portal, and EVM, each with its own entitlement and price.
Yes. Oracle's License Manager counts users with either Active or On-Hold status as active named users. Placing a departed user On-Hold does not release the seat. The only way to reclaim entitlement is to fully delete the account. Audit and reconcile On-Hold accounts before every renewal.
A Standard User has full functional access and covers both internal (Company) and Partner users at the highest per-seat price. A Collaborator User is a limited-access external license, intended for vendors, with access to the Mailbox and the ability to view and create User Defined Reports if permitted. On the April 2024 UK list the Collaborator add-on was 437 GBP versus several thousand dollars for a Standard seat, so classifying external users correctly is the main savings lever.
No. For cloud customers, only the Oracle Cloud Administrator acting as Site Administrator can change license terms, including adding Collaborator or EVM licenses. Your Company Administrator cannot self-serve. Every adjustment routes through Oracle, which is why you should finalize your user mix and module attach before signing.
Modules are priced separately. The base is Facilities and Asset Management, with Project Controls and Real Estate Management as per-user add-ons. Attaching modules across your whole user base rather than by role is a common overspend. User Defined Reports, however, carry no additional fee and are included with Unifier.
Oracle support runs at roughly 22 percent of license cost annually. If support lapses and you later need to reinstate it, or an audit finds you running without current support, Oracle may charge back the missed fees plus a 150 percent penalty. Never drop support without first modeling that penalty against a third-party support alternative.
Siebel is licensed on authorization across several user metrics, grants access through responsibilities and custom views, and sits under Oracle lifetime support. The traps and the
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.
