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.

See the workflow
Controlled exchange · tenant boundaries · reviewed updates
Coordination board · illustrative project data
Schedule control
PI-CTRL / REV 06
ActivityOwnerFinishDone
Substructure releaseCivil21 Oct92%
MEP first fixMEP29 Oct68%
Envelope inspectionQA/QC03 Nov44%
Level 04 handoverPM11 Nov16%
CONTROLLED PROGRESS
NEXT REVIEW
WED · 08:30
Field signal
LIVE
68%verified
complete

Evidence is attached to assigned activities before planner review.

Approval register
3 OPEN
IRConcrete pourAccepted
UPMEP first fixReview
QTYMonthly cut-offReady

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.

INPUT

Import a controlled copy

Bring in XML, XER, XLSX, or CSV under the correct company and project scope.

FIELD

Collect assigned progress

Site engineers record actuals, completion, quantities, pictures, and inspection evidence.

REVIEW

Approve with context

Planners inspect submitted changes before they become part of an export package.

OUTPUT

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.

01 / CORE

Team Member

Activity assignment, field updates, evidence, approvals, reporting, paid quantities, and resource tracking.

Available
02 / OPTIONAL

Smart Contracts

Local semantic discovery and clause workflows when the contracts runtime is installed and entitled.

Coming soon
03 / OPTIONAL

Intelligent Schedule

Browser-based schedule authoring and diagnostics when its production bundle is installed.

Coming soon
04 / OPTIONAL

4D Dimension

Schedule-linked model coordination when the 4D runtime is installed on this server.

Coming soon

Project 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.

01

Tenant-specific authorization

Every protected action is checked against the authenticated user, company, project, and exact resource.

02

Separated identity namespaces

Legacy and unified sessions cannot be confused simply because two records share a numeric identifier.

03

Controlled files and jobs

Private evidence, generated schedules, and exports require authenticated ownership and contained paths.

04

Additive production change

Database evolution is explicit and reviewed so existing users, projects, and records remain intact.

Bring the project wall into one controlled view.