Primavera (software)
project planning and control program
Primavera is an enterprise project portfolio management software. It includes project management, scheduling, risk analysis, opportunity management, resource management, collaboration and control capabilities, and integrates with other enterprise software such as Oracle and SAP’s ERP systems. Primavera was launched in 1983 by Primavera Systems Inc. which was acquired by Oracle Corporation in 2008.
History
Founders
Primavera was founded in the spring of 1983 by Joel Koppelman and Dick Faris. It was headquartered at Three Bala Plaza West in Bala Cynwyd Pennsylvania, USA.
Products and versions
The company produced many products over the years including:
Finest Hour
Parade
Primavera Project Planner (P3)
Monte Carlo
SureTrak
Expedition - which was rebranded Contract Manager
P3e and TeamPlay - which were rebranded as P6
As of 2008 Primavera Systems supported long-established products - P3 and SureTrak - and the newer P6 version. The long-standing P3 product in its various forms was used by 25% of the heavy construction industry, its predominant customer base; the next most popular software was used by 11%. Nearly 40% of general contractors with an annual revenue of $5M to $10M used Primavera P3. In comparison, the P6 version did not register in a CFMA 2008 survey of the United States construction industry. The Primavera Project Planner DOS core launched in 1983 and the P3 Windows interface launched in 1994.
Begin with the source’s own compact description: “Primavera (software)” is project planning and control program. The dossier treats that line as a proposition to test through Primavera, software and project, not as a finished interpretation.
Why this record matters
The phrase “project planning and control program” supplies a clear boundary for inquiry. It also exposes the unanswered questions: who defined that boundary, when it became stable and which sources sit outside it.
The citation trail is more important than the brevity of the summary: it shows where individual claims can be examined in context. The source revision retrieved here is dated Apr 14, 2026. The linked authority identifier is Q2111327. 1 of 1 selected statements include explicit references; 0 carry qualifiers and 0 use preferred rank. The first chronological checks are 1983, 2008 and 1994.
Overview language is designed for orientation and should not be treated as a substitute for the evidence cited beneath it. The lead is largely declarative, so disagreement and counter-evidence require a deliberate search beyond the opening account. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.
How to read it
Use the entry as an orientation point, then follow its citations and revision history. Names, dates and institutional relationships should be checked against the original record.
- Subject orientation
- Search vocabulary
- Locating named sources
The closest primary source, responsible institution and strongest cited specialist reference.
Three-step research path
- Establish the record: confirm the title “Primavera (software)”, its source revision and the description used here.
- Expand the search: follow Primavera (software) primary sources, Primavera (software) archive and Primavera research across catalogues and specialist indexes.
- Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.
Questions for further research
- Which source most directly establishes the central claim about “Primavera (software)”?
- Which cited source is closest to the event, object or claim?
- What terminology or title could unlock a more precise catalogue search?
Search terms from this dossier
This entry incorporates text from “Primavera (software)” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.