1. Upload the XER files
Start with ordered baseline and update snapshots, source hashes, and parser health.
Primavera P6 analytics for lakehouse teams
Keep XER as the scheduler's working language. Start with baseline and update files, complete the review, then give IT buyers and data teams versioned facts for Databricks notebooks, quality checks, pipelines, and governed portfolios.
Versioned schedule facts, not raw XER bodies.
Start with ordered baseline and update snapshots, source hashes, and parser health.
Review schedule health, DCMA orientation, calendars, constraints, and path signals.
Turn date, float, logic, and WBS movement into versioned quality facts.
Land changed, delayed, added, removed, critical, and near-critical activity facts.
Carry task findings and available OBS-related coverage into governed notebook and pipeline models.
SuperWave-XER can be discussed as a product inside your data center, inside your cloud account, or as a managed hosted path. The boundary and operating responsibilities stay explicit.
Install inside your secure data center with your own network, storage, identity, and operations.
Run from Docker or source code when you want to own deployment and upgrades.
Bring your own cloud account and retain control of tenancy, keys, network, and data placement.
Shape a boundary-specific federal deployment with inherited controls reviewed separately from application controls.
Primavera P6/XER remains the scheduler input. Publish governed derived facts and evidence references to Snowflake, Databricks, Google BigQuery, Amazon Redshift, or MotherDuck when the selected architecture approves that path.
Warehouse trends, dashboards, and portfolio reporting.
Lakehouse notebooks, pipelines, and governed models.
Curated schedule facts for SQL analytics and reporting.
Warehouse-ready review summaries and portfolio views.
Collaborative DuckDB analytics for lightweight sharing.