Secure Remote Access to Primavera P6
Remote access to Primavera P6 lets distributed schedulers work on shared plans. It works best when sign-in is controlled, performance is tested where people work, and everyone understands what happens to local files and interrupted sessions. If schedulers connect from Germany and elsewhere in Europe, test common tasks at each important location.
Choose an access route for real tasks
Compare access options against the work users actually do. Do they only review projects, edit schedules, or move large files? Check which devices and networks are allowed and how sign-in is protected. A pilot involving internal schedulers and outside partners exposes friction early. Record which applications the remote route should reach and which systems should remain outside it, then verify that those boundaries hold.
Measure everyday performance
A successful login says little about daily usability. Test opening large projects, filtering activities, entering status, and exporting data over the home and office connections people normally use. Record delays and disconnects with the date, location, and connection type. This helps separate network issues from application bottlenecks. Include busy periods when many schedulers work at once before a reporting cut-off.
Manage local copies deliberately
Remote work can leave exports on laptops, in download folders, or in informal file shares. Decide what may be stored locally, how files are named and transferred to partners, and when copies must be removed. Mark the authoritative schedule version clearly. A controlled exchange reduces the chance that two teams make decisions from different versions while believing each is current.
Plan for disconnects and device changes
Mobile connections fail and devices sometimes need replacing. Show users how to check whether their last change was saved after a session drops. Provide a clear path for signing in again and revoking a lost device. During critical status cycles, agree who can cover for an unavailable scheduler. Try the handover before a tight reporting window so that the process is familiar when needed.
Frequently asked questions
What should a P6 remote-access pilot test?
Include sign-in, large projects, status updates, exports, and interrupted sessions with users at the intended work locations.
How do we avoid outdated local schedules?
Define one authoritative source, label exports with their date and purpose, and remove copies that are no longer needed.
Need help with your project schedule? Explore our project planning services.