#Omniplan collaboration update#

This can be set in the Resource Info section of the Resource inspector. The key to balancing resource loads across projects is that individual resources be tagged and identified by a unique email address that is shared across all projects. If a project neither publishes or subscribes, it ignores external factors and syncs only with its own updates. A project that only publishes will always have its needs met first, while a project that only subscribes will be assigned resources only when available.īy publishing and subscribing to resource loads, projects are treated as equals. By using only the publish or subscribe option a hierarchy of priority can be established between simultaneous projects.

For example, if Julie is working on Project A on Wednesday and its loads are being published to Project B, after leveling Project B won’t schedule her to work on Wednesday.Ĭhoosing to Subscribe to resource loads means that the project will obey all constraints by projects in the repository that are publishing their loads. If resources (usually human members of your team) are shared between multiple projects in the same repository, you’ll need to decide whether to Publish the current project’s resource loads to other projects and whether the current project will Subscribe to the resource loads of others.Ĭhoosing to Publish a project’s resource loads means that other subscribing projects will obey its workload information when leveling. The server then pushes those changes to everyone so their local file is always up to date.īoth the Project Manager and Resources use the View menu to receive and review changes which, when accepted, are published back up to the server.

#Omniplan collaboration update#

The people ( Resources) assigned to the project then subscribe to the file, which places a copy of the OmniPlan file in their Local Documents folder.Īs people assigned to the project update their local file, they in turn publish those changes to the file on the Server Repository. The file on the server then becomes the “One Truth” to which everyone subscribes. When you initially publish an OmniPlan file, a copy of your file gets pushed up to the designated Server Repository. The key to making this work is the plan file itself, which resides on a Server Repository: The Project Manager and the Resources assigned to the project are both capable of publishing and subscribing to everyone’s updates to the file. Once set up, Publish and Subscribe works like an infinite loop.