What Is BI Publisher (and Why Should You Care)?
Oracle BI Publisher is an enterprise reporting engine that ships with Primavera P6 EPPM. If you’ve been in the P6 world long enough, you remember the Crystal Reports days — BI Publisher is Oracle’s replacement, and it’s a significant upgrade in almost every way.
The core value proposition: BI Publisher takes data from your P6 database, applies a formatted template, and produces reports in PDF, Excel, Word, HTML, or RTF. You design the template once, and every time the report runs, it pulls live data and renders a consistent, professional document.
One thing to be clear about upfront: BI Publisher is available in P6 EPPM (the web-based, server-deployed version). If you’re running P6 Professional standalone with a local database, you don’t have access to BI Publisher. You’ll need to use P6’s built-in print layouts or export to Excel and build reports manually.
How BI Publisher Connects to P6
The architecture is straightforward once you see it:
Data Model — A set of SQL queries that run against the P6 database schema (either the standard schema or the extended schema). The data model defines what data is available to the report. Think of it as the SELECT statement behind the scenes.
Template — An RTF file (Rich Text Format) that defines the layout, formatting, headers, footers, and logic. Templates are designed in Microsoft Word using the BI Publisher Desktop plugin. The template defines how the data looks.
Report — The combination of a data model + a template + user-selected parameters (like project filter, date range, or WBS level). When you “run” a report in P6’s web interface, you’re triggering this combination.
Output — The rendered document in your chosen format. PDF is the most common for formal distribution. Excel is popular when people want to manipulate the data afterward.
In the P6 web interface, navigate to the Reports section. You’ll see a list of available BI Publisher reports organized by category. Select one, choose your parameters, pick your output format, and run. The report generates server-side and downloads to your browser.
The Standard Report Library
P6 ships with a library of pre-built BI Publisher reports. The exact count varies by P6 version — Oracle has added and removed reports across releases — but the core categories have remained stable:
Schedule Reports
- Activity Listing — The workhorse. Lists activities with their dates, durations, float, and status. Filterable by WBS, activity codes, or date range.
- Schedule Summary — Higher-level view by WBS, showing rollup dates, progress, and key milestones.
- Schedule Comparison — Compares current schedule to baseline. Useful for variance analysis and delay claims.
Resource Reports
- Resource Loading — Shows resource assignments over time. Histograms by month, week, or custom period.
- Resource Assignment Detail — Activity-level resource assignments with planned vs. actual units and costs.
Cost and Earned Value Reports
- Earned Value Analysis — SPI, CPI, EAC, and other EVM metrics at the project and WBS level.
- Budget Summary — Original budget, current budget, actuals, and remaining forecast.
- Cost Breakdown — Costs by WBS, by resource, or by cost account.
Project Summary Reports
- Project Status — One-page overview with key dates, percent complete, and budget summary.
- Milestone Report — Tracks key milestones against baseline dates.
These standard reports are functional but generic. They’ll get you started, and they’re good enough for internal use on many projects. But if you’re delivering reports to external clients, government agencies, or executive leadership, you’ll almost certainly need to customize them.
Customizing BI Publisher Templates
This is where BI Publisher earns its keep. The customization workflow:
Step 1: Export an Existing Template
Start from an existing report template. Always. Building from scratch is technically possible but painful — you’d need to define every data field binding, grouping, and layout element from zero. Instead, find the standard report closest to what you need and export its RTF template from BI Publisher’s catalog.
Step 2: Install the BI Publisher Plugin for Word
Oracle provides a free Microsoft Word plugin (BI Publisher Desktop). Install it. This adds a “BI Publisher” ribbon tab in Word that lets you insert data fields, define repeating groups, add conditional logic, and preview reports — all within the Word interface.
Step 3: Modify the Template
Open the exported RTF in Word. Now you can:
- Add your company logo and branding — replace the default Oracle/P6 header with your own
- Change column layouts — add or remove data columns, resize, reorder
- Add conditional formatting — show SPI values in red when below 1.0, highlight critical path activities, flag milestones that are late vs. baseline
- Insert calculated fields — BI Publisher supports XSL expressions for custom calculations
- Modify grouping and sorting — group activities by WBS level 2 instead of level 3, or sort by total float ascending
The RTF template syntax looks strange at first. You’ll see XML-style tags embedded in Word text — things like <?for-each:G_1?> to start a repeating group or <?Activity_Name?> to insert a field value. It’s not intuitive, but it is logical. After building two or three templates, the pattern clicks.
Step 4: Upload and Test
Upload the modified RTF template back to BI Publisher through the catalog interface. Run the report against a real project with sample data. Check the output carefully — field alignment breaks, page breaks land in wrong spots, and conditional logic has edge cases. Budget time for iteration.
Practical Tips From the Field
Sub-templates are underused. You can create reusable template fragments — a standard header with your company logo and report title, a standard footer with page numbers and confidentiality notices. Reference these sub-templates from any report. Change the logo once, and every report picks it up.
Conditional formatting makes reports actionable. A wall of black text is hard to scan. But a report where late activities show in red, critical float shows in bold, and budget overruns are highlighted in amber — that report gets read. I typically set up three rules: red for values beyond tolerance, amber for values approaching tolerance, and default for everything within range.
Watch your data volumes. A report pulling 10,000 activities with full resource assignments can take minutes to render and produce a 200-page PDF nobody will read. Use parameters to filter intelligently — by WBS, by date range, by activity status. Give users the ability to scope the report to what they actually need.
Version control your templates. Keep a repository of your customized RTF files outside of BI Publisher. When P6 gets upgraded, templates sometimes need adjustment. Having the RTF on a shared drive (or in Git) means you can track changes, revert, and collaborate.
Extended Schema: The Power Move
P6’s standard database schema is normalized — great for application performance, not great for reporting. Writing SQL joins across 15 tables to get a simple activity listing with resources and codes is tedious and error-prone.
The Extended Schema solves this. It’s a separate Oracle schema that P6 populates through an ETL (Extract, Transform, Load) process. The extended schema provides:
- Denormalized reporting tables — flattened views that join the data you commonly need
- Precomputed spreads — resource and cost data spread over time periods, ready for histograms and S-curves
- Activity code pivots — activity codes as columns instead of rows, making filtering and grouping straightforward
If you’re serious about BI Publisher reporting — or any reporting against P6 data — you need the Extended Schema enabled. The standard schema data model works for simple reports, but anything involving resource loading over time, earned value trends, or cross-project comparisons will be dramatically easier with the extended schema.
The setup requires your DBA. It’s a separate Oracle schema, needs its own tablespace, and requires a scheduled job (the ETL) to keep data in sync. The ETL can run hourly, daily, or on-demand depending on how current your reports need to be. On most projects I configure, we run it nightly — fresh data every morning for the reporting cycle.
BI Publisher vs. Power BI vs. Custom Dashboards
I get this question on nearly every engagement. Here’s my honest comparison:
| Aspect | BI Publisher | Power BI | Custom Dashboard |
|---|---|---|---|
| P6 Integration | Native — built in | Requires connector or API | Custom development |
| Output Format | PDF, Excel, Word, RTF, HTML | Interactive web, PDF export | Web-based |
| Primary Audience | Formal report consumers | Data analysts, managers | Operations teams |
| Customization | Template-based (RTF) | Drag-and-drop visual builder | Unlimited (code) |
| Cost | Included with P6 EPPM license | Separate Microsoft license | Development + hosting |
| Learning Curve | Moderate (RTF templates) | Low to moderate | High (requires developers) |
| Best For | Compliance, print, archives | Analysis, drill-down, exploration | Real-time operational views |
None of these tools is universally “best.” They serve different purposes.
When to Use BI Publisher
Formal deliverables. Monthly progress reports, weekly schedule updates, cost reports that get emailed to 50 stakeholders as PDF attachments. BI Publisher produces consistent, print-ready documents every time. No formatting surprises, no broken formulas, no “it looks different on my machine.”
Compliance and audit. Government contracts, DCMA 14-point assessments, ANSI/EIA-748 earned value submissions. These require specific report formats delivered on specific dates. BI Publisher templates enforce that format.
Consistency across projects. When you have 20 project managers who all need to produce the same monthly status report, give them a BI Publisher template. The report looks the same regardless of who runs it. Try achieving that consistency with Excel and see what happens.
When you’re already running P6 EPPM. It’s included in your license. No procurement cycle, no additional servers (BI Publisher runs on the P6 application server), no new vendor relationship. It’s already there.
When to Look Elsewhere
Interactive analysis. If your stakeholders want to click on a bar chart and drill down to activity-level detail, filter on the fly, or slice data by dimensions they choose at runtime — that’s Power BI territory. BI Publisher produces static documents, not interactive dashboards.
Real-time operational views. If the construction superintendent needs a live look at today’s planned activities with crew assignments and equipment status, a custom web dashboard connected to P6’s API is the right tool. BI Publisher reports are snapshots, not live feeds.
Cross-system reporting. When you need to combine P6 schedule data with cost data from an ERP (SAP, Oracle EBS), risk data from a risk register, and document status from a document management system — you’ve outgrown BI Publisher. You need an ETL pipeline feeding a data warehouse with a reporting layer on top. BI Publisher can be that reporting layer, but only if all the data lands in a schema it can query.
Quick ad-hoc analysis. A project controls analyst who needs to quickly answer “which activities consumed the most labor hours last month?” doesn’t want to build a BI Publisher report. They want to query the data, pivot it, and move on. Export to Excel, or connect Power BI directly.
The right answer for most organizations is a combination: BI Publisher for formal reports and compliance deliverables, Power BI or Tableau for interactive analysis, and Excel for everything in between. The mistake is trying to force one tool to do everything.