Collaboration and Multi-Project Review (Pro)

And, to make it easier for you to manage multiple projects with shared resources, OmniPlan Pro’s Dashboard makes it easy for you to review projects side by side.

Before you begin sharing your OmniPlan projects you'll want to make sure you have a server ready to act as a centralized repository for your files. Syncing a local copy of your project with the copy on the server—or to a calendar on a calendar server—is what makes sure everyone sharing the file is up-to-date with all of the latest changes.

The walkthrough in the following section describes setting up your first sync account using the Server Accounts window.

Click the Add Account (+) button in the lower left of the window to connect a new account. When you connect to an account for the first time, the window presents a guided setup mode for choosing the account type and entering the relevant login information.

If you are setting up a server account for collaboration, choose either Omni Sync Server or WebDAV. If you are adding or retrieving work hours from a synced calendar account, choose CalDAV or Google Calendar (depending on the account type).

Once you have an account connected, it appears in the list on the left side of the window. Add more accounts by clicking the Add Account (+) button at the bottom of the list.

With an Omni Sync Server or WebDAV account selected, the project files it contains appear in the list on the right. Select a project in the list and click Download Project to make a local copy. The file opens, ready for collaboration.

If you are setting up sharing for the first time and don't have any projects synced remotely, this list will be empty.

The Accounts list shows your Omni Sync Server, WebDAV, CalDAV, and Google Calendar accounts by name. Choose an account in the list to see the projects or calendars it contains. To add an account, click the Add Account (+) button below the list. To edit an account, select it and click Edit Account.

With an Omni Sync Server or WebDAV account selected, the list shows all projects that have been published to the repository, and the following information about them:

1. Project Name—The name of the project file.

2. Load—This column indicates, by the presence of a vertical bar graph icon, whether the project shares its resource load information with other projects in the repository for the purposes of leveling resources across projects.

3. Start Date, End Date, Last Modified—The dates when the project is scheduled to start and end, and the date it was last modified by any user with shared access to it.

4. Completed—The percentage of overall work on the project that has been completed.

5. Add Account, Remove Account—Click the Plus button here to add a repository account, and the Minus button to remove an existing account. Removing an account doesn't delete its contents on the server; it just deletes it from the list of servers you have connected to OmniPlan.

6. File Metadata—This section displays information about the project file: its unique ID, its size, the size of the associated changelog file (for change tracking), and when the file was last truncated.

If OmniPlan finds unused resource load information on the server, it detects the problem and prompts that you clean it up. This can happen if someone removes a project that is sharing resource loads using a version of OmniPlan older than v2.1, or if someone deletes the file directly from Finder or Terminal. Until you allow it to clean up, there may be misleading resource load information shared with your active projects.

The clean way to remove a project from a server repository is to open the Server Accounts window and use the Delete Project button.

Once you have a server account set up, you can begin syncing your project files with it to collaborate with other editors on your project.

With OmniPlan 3.10 and later, set up the sync actions for your project using the new Sync & Sharing sheet (Project > Sync & Sharing Options).

For this walkthrough we will assume you are starting with a brand new server account (set up in the Server Accounts window above) and a fresh project that you want to work on collaboratively with others. You'll be publishing changes you make to your shared server, which other editors will subscribe to (and vice versa).

When you first set up sync and sharing for a project, you'll see two options: Basic Syncing and Advanced Sharing. If you choose Basic Syncing you'll be directed to the setup process for OmniPresence or iCloud storage—two great options if all you need is a remote place to keep your files.

Since this example has multiple contributors, we'll choose Advanced Sharing instead. Click Continue to set up sharing for the project.

The list of share actions for your project starts out blank. Click the Plus button to add a new one and choose from among the available action types. You'll see that you can perform a variety of automated tasks when sharing (publishing) your project; we'll focus on collaboration for now. Choose Collaborate as the action type, then click Next.

To collaborate on this project it will have to be stored on a server so others can access it. If you set up an account with the Server Accounts window, click Choose Server and choose it from the list (if not, you'll want to set one up now and come back to this step). After choosing your account, click Save.

Your Sync & Sharing Options sheet now contains an active action for publishing to, and refreshing from, your shared server repository. To edit details of the action, select it and click the Pencil edit button at the bottom of the actions list. Use the checkboxes below the list to choose what prompts the project to publish or refresh its status.

Click Done, then save the project. If you selected Perform publishing actions automatically when saving, the project is published to the server for the first time. Otherwise, choose Project > Publish (Control-Command-P) to publish it manually.

The next time you check the Server Accounts window you'll see the project listed in your account. Subsequent changes you make are published to the server based on the settings you chose in Sync & Sharing Options, and you can monitor those changes—any incoming from other editors who have similarly connected to your project—using change tracking (Project > Show Changes).

You can publish your local version of the project to the server by choosing Project ▸ Publish (Control-Command-P), or by clicking the Publish button in the toolbar.

You can refresh manually from the server at any time by choosing Project ▸ Refresh (Control-Command-R) or the Refresh toolbar button.

The Sync & Sharing Options sheet provides an overview of the sharing actions you have set up for the current project, and includes tools for adding, removing, and editing those actions.

1. Action Type and Direction—The icon shows the type of action for the row, and the arrows next to it indicate whether the action occurs on Publish (the up arrow), Refresh (the down arrow), or both.

2. Action Description—The text in the center of each action row describes the action, and notes whether the action occurs on Publish, Refresh, or both.

3. Action Active Status—The rightmost column contains a checkbox that indicates whether the action is currently in use. Deselect it to exclude the action from occurring when it normally would.

4. Add and Remove Action—Click the buttons here to add a new action (plus) or delete a selected action (minus). Deleting an action removes it from the project entirely. To temporarily disable it instead, deselect its active status checkbox.

5. Publish and Refresh Options—Choose whether to perform publishing actions automatically when saving the project file, and choose whether to automatically update when notified of changes via Bonjour or a specified timeframe from the pop-up menu to the right. These options apply to all actions set up for the project.

6. Edit Action—Further options for each action are available; choose the action in the list and click this button to open and edit the action details.

When creating a Collaborate action, the following options are available:

1. Server Account—Choose the server account to publish and subscribe to from this dropdown menu. The menu lists all of the accounts you have set up in the Server Accounts window.

2. Account Info—Open a sheet with login details for the sync account associated with the action.

3. Resource Load Sharing—Choose whether to share the project's resource loads with other projects on the server, and choose whether to respect the resource loads of other projects on the server when leveling.

When creating an Export action, the following options are available:

1. Export As—Choose a file format to export from this dropdown menu. The list of formats includes all of those available from File > Export, as well as the default native OmniPlan file format.

2. Save To—Choose a name and location for the exported file.

3. Filter—Set up or choose a custom filter to apply when exporting the project file. Any items excluded by the terms of the filter will not appear in the exported version of the project.

When creating a Sync Tasks with a Calendar action, the following options are available:

1. Source—Choose an existing calendar source from this dropdown menu, or choose Add Account to open a sheet where you can choose a CalDAV or Google Calendar server to add as a new calendar source.

2. Calendar—With a source selected, use this dropdown menu to choose the calendar you want to sync with.

3. Filter—Set up or choose a custom filter to apply when syncing tasks from the project file. Any tasks excluded by the terms of the filter will not appear in the synced version of the project.

When creating a Sync Work Hours from a Calendar action, the following options are available:

1. Source—Choose an existing calendar source from this dropdown menu, or choose Add Account to open a sheet where you can choose a CalDAV account to add as a new calendar source.

2. Calendar—With a source selected, use this dropdown menu to choose the calendar you want to retrieve events from.

3. Events—Choose what happens when events are retrieved from the calendar. Calendar events can either represent new work hours added to the project, work hours subtracted from the project, or additional work or off hours for a specific resource.

4. Resource—If you chose for calendar events to add work or off hours for a specific resource, choose the resource from the dropdown menu here.

When creating a Run a Script action, the following options are available:

1. Script Type—Choose from between AppleScript and Omni Automation.

2. Script—Choose the script to run from this dropdown menu. The menu is empty until you add an AppleScript file to the OmniPlan Scripts folder, which is linked in the text next to this item.

   When you choose the Omni Automation script type, this is replaced by two other dropdown menus labeled Plug-In and Action respectively. Choose an Omni Automation Plug-In using the first, and choose one of its actions to run using the second. The Plug-Ins folder is linked in the text to the right.

3. Execute During—Choose whether the script should run when publishing changes to the repository, or when refreshing to receive changes from the server.

To connect other team members to your published project, you will need to provide them with the following information:

• Account Type: Either Omni Sync Server or WebDAV.
• The User Name and Password used to access the sync server account.
• The name of the file to which they will subscribe.

Team members will use that information to add an account in OmniPlan > Server Accounts. Once they have created the account, the members of your team can subscribe to the project with the following steps:

1. Open OmniPlan.
2. Choose OmniPlan > Server Accounts.
3. On the left side of the window that appears, click to select the Project Repository.
4. Click to select the Project Name from the list of available projects in the repository.
5. Click Download Project.
6. Save a copy of the project file locally on your Mac’s hard drive.

The downloaded file is automatically subscribed to, and linked to the master copy on the server.

Once subscribed, members of the team can edit and review the OmniPlan project using their local copies of the file. Any changes made to the project file are saved to the sync server when the project is published, and when other team members refresh their copy of the project, they receive those changes from the server.

To ensure that your local copy of the project file is always up to date with the latest changes from other team members, we recommend that you follow these steps whenever you open your local copy:

1. Open the OmniPlan project file that you have saved locally.
2. Get updates to the project; choose Project ▸ Refresh (Control-Command-R).
3. Accept or reject changes; choose Project ▸ Show Changes (Option-Command-T).
4. Make your changes to the project file, and then choose File ▸ Save (Command-S).
5. Publish your changes to make them available to other team members who subscribe to the same project; choose Project ▸ Publish (Control-Command-P).

To enable change tracking, choose Project ▸ Show Changes (Shift-Command-T). A sidebar appears that logs the changes you make and shows the changes of your teammates, along with a toolbar (beneath OmniPlan’s main toolbar) with controls for accepting and rejecting the changes of others.

To accept or reject all changes, use the Accept All and Reject All commands in the Gear menu in the change tracking bar.

To accept or reject individual changes, select an individual change in the sidebar and use the Accept or Reject buttons.

Choosing to publish a project’s resource loads means that other subscribing projects will obey its workload information when leveling; 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.

Choosing to subscribe to resource loads means that the project will obey all constraints by projects in the repository that are publishing their loads. By using only the publish or subscribe option a hierarchy of priority can be established between simultaneous projects—a project that only publishes will always have its needs met first, while a project that only subscribes will be assigned resources only when they can be spared.

By both publishing and subscribing, projects are treated as equals—and if a project neither publishes or subscribes, it ignores external factors and syncs only with its own updates.

Dashboards introduce a new file type to OmniPlan Pro: the OmniPlan Dashboard file format (.opld). An OmniPlan Dashboard file is a window that you can customize by adding as few or as many projects to it to manage your projects. When saved, the Dashboard file preserves the projects you have added to it, enabling you to quickly review your projects by opening the Dashboard file in OmniPlan Pro.

To create a new Dashboard, follow these steps:

1. Choose File ▸ New Dashboard (Shift-Command-N).

2. Click to add a project to the Dashboard. This opens a sheet from which you can locate and choose OmniPlan projects to add to the Dashboard. Alternately, you can also drag OmniPlan project files into the window from the Finder.

   

As you add projects to the Dashboard, you’ll see them laid out as rows with summary graphics of the projects’ Gantt charts in two-tone color schemes that reflect the work completed and the work yet to be done (these colors represent their respective projects throughout the Dashboard).

The Project column in the Dashboard provides you with a quick overview of your project's Summary information (similar to what you see in the Project inspector). This first column can be resized by dragging the header separator left or right:

By default, the projects you add to the Dashboard show the Actual timeline for the project. However, if you click Actual, you can view a list of the baselines currently set for the project, and select a baseline schedule to view in the Dashboard instead.

In addition to rows representing your projects, you’ll see an additional, automatically generated row—a graph of Idle Time to indicate when the projects’ resources are available for other tasks. White bars of idle time represent unused time in the past, while dark gray bars represent available time in the future.

Along the bottom of the Dashboard window, you’ll find a list of any resources to which an email address is assigned. Next to each person, you'll see diagram-style bars that illustrate when each person is busy or available, along with pie chart reference graphs noting the split of their effort between the projects in the Dashboard and their Idle Time.

Click to open the Dashboard window’s View menu, which offers the following options:

• Project Overview—Choose between the Gantt comparison view or a bar chart view for displaying the chronology of projects with task bar heights based on the amount of effort required for completion.
• Show Project Stats—Shows or hides details about the project(s) on the Dashboard, including start and end dates, duration, variance, completion, and cost.
• Show Resources—Shows or hides the list of project resources along the bottom of the Dashboard window.
• Timescale—Choose a timeframe for the Dashboard to display from among a list of preset time spans. These include All Tasks (the Dashboard automatically scales to fit every task across all of its projects), Today through the End of all projects, just This Month, This Quarter, or This Year. Alternatively, choose Custom to pick any date range you like.

You can open a project directly from the Dashboard by clicking its document icon. Edits made to project files included in the Dashboard are reflected there right away, so you can immediately see the effect your changes have on the project in question—and potentially on others, if you’re sharing resources between projects.

The power of dashboards is realized to its fullest when you’re also taking advantage of the publication and subscription of resource loads of the projects included in your dashboard.

When balancing resource loads across projects in a shared server repository, the dashboard recognizes that resources are being shared and provides a window on the intersection between resources and the projects they’re working on (sometimes simultaneously at 100% effort, as in the example above). You can identify where resources are overloaded (or are standing idle), and make the changes necessary to ensure your projects are running in tandem at peak efficiency.

Print-time options for dashboards are pretty straightforward; as with all standard documents in macOS, you can choose to save the dashboard as a PDF rather than send it to a printer. The standard page setup controls are available as well.

The most important thing to note about printing dashboards is that what you see is what you get—the content of the print preview changes based on the dimensions and content of the dashboard’s window at the time of printing.

A dashboard’s printed page width is dictated by the bounds of the window, and will never exceed one page; excess pages are generated vertically only. If you find that the printed version of your dashboard extends vertically more than you would like, consider turning off display of project stats and resources in the dashboard’s view menu.