1. Local review first
Run the XER baseline/update review, parser health, DCMA orientation, and critical-path checks before cloud handoff.
Primavera P6 analytics for AWS teams
Keep SuperWave-XER local-first for the scheduler, then hand AWS and IT teams derived review facts for dashboards, portfolio workflows, governed storage, and downstream analytics without exposing raw XER bodies by default.
AWS is the cloud analytics lane; XER review stays evidence-first and local-first.
Run the XER baseline/update review, parser health, DCMA orientation, and critical-path checks before cloud handoff.
Use hashes, summaries, review rows, visual indexes, and evidence references rather than raw schedule bodies.
Discuss S3, Athena, Glue, QuickSight, or lakehouse patterns after the evidence boundary is clear.
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.