beta

Primavera P6 analytics for lakehouse teams

Bring Primavera schedule analytics into the Databricks lakehouse.

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.

Desktop browser · Excel / PDF iAppSys branded direct URL demo

Desktop browser workflow

From P6 evidence to Excel and PDF.

Upload an authorized XER, confirm the Data Date, inspect schedule and target measures, then download a review-bound handover.

Schedule, targets, and costs

Float and milestone movement remain distinct from cost forecasts. Cost dashboards require a supported cost or weighting basis; missing values remain unknown, never zero.

Construction FinOps with Odoo context

Optional procurement snapshots require configuration, authorized access, and explicit activity mapping. Preserve source and capture time. Unmapped items do not change schedule dates; this demo does not prove a live connector.

One evidence receipt

Excel and PDF outputs retain review/version, Data Date, calculation basis, and limits. Platform publishing depends on the approved customer architecture, not the demo page.

Why this matters.

Versioned schedule facts, not raw XER bodies.

Possible now Versioned schedule facts, not raw XER bodies. demo
Data boundary Raw XER bodies and source paths stay out of API, MCP, admin, and visual payloads. safe
Next conversation Start with P6 XER review, then land curated facts in the lakehouse. action

1. Upload the XER files

Start with ordered baseline and update snapshots, source hashes, and parser health.

2. Check the baseline

Review schedule health, DCMA orientation, calendars, constraints, and path signals.

3. Check schedule and WBS adherence

Turn date, float, logic, and WBS movement into versioned quality facts.

4. Check activities

Land changed, delayed, added, removed, critical, and near-critical activity facts.

5. Check tasks and OBS

Carry task findings and available OBS-related coverage into governed notebook and pipeline models.

Choose your deployment model.

SuperWave SPI 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.

On premise

Install inside your secure data center with your own network, storage, identity, and operations.

DIY

Run from Docker or source code when you want to own deployment and upgrades.

BYOC

Bring your own cloud account and retain control of tenancy, keys, network, and data placement.

FedRAMP environments

Shape a boundary-specific federal deployment with inherited controls reviewed separately from application controls.

Meet your analytics platform where it is.

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.

Snowflake

Warehouse trends, dashboards, and portfolio reporting.

Databricks

Lakehouse notebooks, pipelines, and governed models.

Google BigQuery

Curated schedule facts for SQL analytics and reporting.

Amazon Redshift

Warehouse-ready review summaries and portfolio views.

MotherDuck

Collaborative DuckDB analytics for lightweight sharing.

iAppSys brings FedRAMP experience and is working toward CMMC Level 2 certification. This is future/compliance-oriented deployment posture, not a blanket FedRAMP or CMMC authorization claim for every installation.
SuperWave SPI Demo Landing Page Tour. iAppSys branded. Public read-only examples, not findings about your project.