One wall. Every project in context.
Schedules, field progress, approvals, and resources stay connected—without surrendering ownership or writing directly to your production Primavera database.
complete
Evidence is attached to assigned activities before planner review.
A controlled loop, not another disconnected report.
Planning Integration keeps each update traceable from imported schedule activity to field evidence, planning decision, and reviewed export. The production Primavera database remains outside the application boundary.
Import a controlled copy
Bring in XML, XER, XLSX, or CSV under the correct company and project scope.
Collect assigned progress
Site engineers record actuals, completion, quantities, pictures, and inspection evidence.
Approve with context
Planners inspect submitted changes before they become part of an export package.
Return reviewed change
Export approved deltas and reports for a controlled Primavera update process.
One platform, honest availability.
The field-progress workspace is the production core. Optional modules are marked from the server’s actual runtime, so a missing application is never presented as live.
Team Member
Activity assignment, field updates, evidence, approvals, reporting, paid quantities, and resource tracking.
AvailableSmart Contracts
Local semantic discovery and clause workflows when the contracts runtime is installed and entitled.
Coming soonIntelligent Schedule
Browser-based schedule authoring and diagnostics when its production bundle is installed.
Coming soon4D Dimension
Schedule-linked model coordination when the 4D runtime is installed on this server.
Coming soonProject truth stays owned.
Authentication, tenant boundaries, exact file authorization, and controlled migrations are part of the product—not release-day patches. Protected data stays scoped to its organization and resource.
Tenant-specific authorization
Every protected action is checked against the authenticated user, company, project, and exact resource.
Separated identity namespaces
Legacy and unified sessions cannot be confused simply because two records share a numeric identifier.
Controlled files and jobs
Private evidence, generated schedules, and exports require authenticated ownership and contained paths.
Additive production change
Database evolution is explicit and reviewed so existing users, projects, and records remain intact.