Skip to content
Page cover
For the complete documentation index, see llms.txt. This page is also available as Markdown.

⭐VisiLean × Primavera P6 EPPM Integration: Plan and Progress, Always in Step!

On most large projects, the master programme lives in Oracle Primavera P6 and the day-to-day progress lives with the site team. Keeping the two aligned has meant exporting files, re-keying percentages and actual dates, and hoping nothing changed in P6 in the meantime. VisiLean now connects directly to P6 EPPM, so the plan and the progress move between the two systems without the manual handover.

Why This Matters

Every manual transfer between the site and the master programme is a chance for a stale date, a missed activity or a percentage typed into the wrong field. Planners lose hours each update cycle reconciling the two sides, and site teams end up working to a lookahead that no longer matches the programme. Contractual reporting depends on P6 being right, so the transfer has to be trustworthy not just fast.

What's New?

  • Connect and import: In Project Settings, enter your P6 EPPM address and sign-in, test the connection, and link the VisiLean project to a P6 programme. Before importing, you see exactly what will come in. The first import brings in the WBS, activities, planned dates and logic links in one all-or-nothing step.

  • Get updates (P6 → VisiLean): Pull the latest plan from P6 into your schedule. A preview groups what's new, what's changed, what's already in progress on site and what's been removed in P6. Tasks whose dates moved are marked until someone opens them.

  • Send progress (VisiLean → P6): Send percent complete, actual start and finish, remaining duration, expected finish and labour hours back to P6, along with activities created in VisiLean. P6 reschedules once the values are in.

  • Verified, not assumed: After every send, VisiLean reads the values back from P6. Only values P6 actually kept are counted as sent; anything else stays pending for the next send, and failed items can be retried.

  • Clear ownership: P6 owns the plan (planned dates, activity type); VisiLean owns progress. Names, WBS and logic links move both ways. The full ownership table is shown in the settings.

  • Custom field mapping: Optionally send location, trade, work package, quantities and durations to P6 custom fields.

  • Full history: Every import, update, send and settings change is kept in one history, showing what P6 held before each write. Download any run as CSV.

How It Helps

A Planner updates the baseline programme in P6 on Friday. On Monday, they run Get updates, review the preview 12 new activities and 30 changed dates and apply it, so the lookahead session starts from the current programme.

A Site Engineer records actual starts and progress in VisiLean through the week. At the end of the week, the Planner reviews the Send progress preview, sends it, and P6 reschedules with no re-keying and a CSV of the run for the monthly report.

A Project Manager checks History after a client query and can show exactly which values were sent to P6, when, and what they replaced.

Key Considerations & Caution Points

Every sync is started by a person: Nothing runs on a timer, and every exchange shows a preview first. Automatic scheduled sync is not yet available.

Admin setup: Connecting, linking, previewing and sending are available to Project Admins, Process Managers and Customer Admins. Other roles see the sync status and the change markers on tasks.

P6 version: P6 EPPM 21.12 or later is required.

Planned dates come from P6: Changes to planned dates in VisiLean are kept locally but not sent to P6. If both sides rename an activity or move it in the WBS, P6's value wins.

Not synced: Task status, priority, costs, baselines and resource assignments are not exchanged. Labour hours are sent only when an activity has exactly one labour resource.

Nothing is deleted automatically: Activities removed in P6 are flagged in VisiLean for an admin to keep or relink, never deleted. Removing a logic link in P6 needs separate confirmation.

Large programmes: Linking a programme with more than 2,000 activities shows a warning but is allowed.

Last updated