Self-hosted AWP software runs on infrastructure you control and connects to Primavera P6 for the schedule and to Power BI for reporting. Work packages, constraints, and progress stay inside your environment, and the connections to P6 and Power BI remain yours to maintain and extend after the vendor engagement ends.
Why Owners Ask for Self-Hosting
Three reasons come up on capital projects.
- Data stays in your environment. Package, constraint, and progress records sit on servers governed by your own IT policies
- Your other systems can read it. The database and API are reachable by your data warehouse and reporting stack
- The platform outlives the engagement. The software and its data remain with the project team when the implementation partner leaves
How the P6 Connection Works
Primavera P6 holds the Level 3 schedule, and under AWP the activities in that schedule are the work packages themselves. CWPs, EWPs, and PWPs each appear as an activity with a duration, logic, and resources. Installation work packages stay out of P6 and live at Level 4 in the AWP software, because IWP scope changes every week.
That split decides what the integration carries. The schedule supplies package activities and dates, and the AWP software holds the IWPs, constraints, and field progress beneath them. Both sides reference the same package IDs, and a package change goes through the AWP Matrix before either system is updated. How Primavera P6 carries an AWP program covers the coding and the four tests of an AWP-compliant schedule.
How the Power BI Connection Works
Power BI works best as the last stop in a governed pipeline, reading validated package data. A self-hosted AWP platform shortens that pipeline, because reports read package status, constraint counts, and progress from a source inside your own environment. Package skylines, constraint dashboards, and model views built on that data are what project controls reviews each week, and our reporting and analytics team builds them.
What to Look For
- Who runs it. Upgrades, backups, and monitoring sit with your IT team, a partner, or both
- The data model. Forms, fields, and the package hierarchy should match your AWP procedures without code changes
- The API. A documented API lets P6, the warehouse, and Power BI read the same records
- Package governance. The P6 integration follows the AWP Matrix, so no package is created or split in one system alone
How openAWP Does It
openAWP is advanced work packaging software with no license fee. It is a web application that runs on your own infrastructure, or on ours if you prefer. It reads schedule activities, WBS, and resources from Primavera P6 through the P6 REST API, on a schedule or on demand, and maps them onto its package tables. Power BI reports can be embedded inside openAWP, and a documented REST API, authenticated with API tokens, lets Power BI and the rest of your stack read the same data. On your own infrastructure, the software and data stay with you after the engagement.
Planning a self-hosted AWP rollout? Our data integration team connects P6, the model, and your reporting stack, or book a demo to see openAWP on your own project.