When to Use Linked Sites

With Multi-Node work, you may want to dispatch employees to multiple geofences, but have their time in said geofences all charge to a single BP.

One way to do this would be to use Site-specific WOs. But this isn't ideal because you have to dispatch, each day, every node the crew might touch.

A better option is to Link Sites to form a "Site family." In this scenario, when you dispatch the primary Site, all the sub-Site geofences are activated with a single dispatch. Anytime the crew is inside any of the linked Sites they are On-Site for the BP.

When NOT to Use Linked Sites

This is probably not the best option when you have a large number of Sites that should be related to a single BP. In that situation, you will want to use a Carrier Group and possibly Site-Specific WOs.

See this article for more info on Carrier Groups: User Carrier Group to Dispatch Multiple Sites Under One BP

The Primary Site

Venue Primary Site

With a Venue, the Primary Site would be the Venue, in general (like an airport), and the sub-Sites would be sections of the Venue which need their own geofences (like different terminals).

Microwave Primary Site

Microwave work is unusual in that 2 nodes might be included in a single scope, and the relationship between them matters in that there is an "origin" Site and a "destination" Site. The relationship might be referred to as a "Path." Additionally, the destination Site for one Path might be the origin Site for another.

Fortunately, nothing in FCX stops you from making a Site a sub-Site for more than one Primary Site.

Configure Sites in Desktop Prior to GBP

Linking sub-Sites to a Primary Site is currently only possible in FCX Desktop. You'll want to set all this up prior to Generating your multi-Node Build Plan.

Create Primary Site

The Primary Site should represent the collection of Nodes which should all charge to the same BP. Examples include an entire Venue or one Microwave Path.

CAUTION
Note that you could make one of the Nodes just serve as the Primary and others serve as sub-Sites, BUT, this could prevent you from using the chosen Primary Node as a sub-Site somewhere else, because doing-so would bring-along "grandchildren Sites" you may not want to include. For this reason, we recommend the Primary Site be distinct from the Node.

There's no special way to create a Primary Site, just give it a Site ID that will represent the whole Venue, Path, etc.

Link Nodes to Primary Site

To do this:

• First create the sub-Sites as you would create any other Sites
• Find and open the Primary Site's Site card
• In the card Main Content pane, on the "Additional Information" tab, find the "Related Site" table at the bottom
• Click-into the table just below the headers to add a row
• Select one of the Sites that will serve as a sub-Site Node for the Primary Site

GBP and Dispatch for Primary Site

After the Sites are linked, you can GBP. You will dispatch the Primary Site via the BP's WOs, and the sub-Sites will be activated by said dispatch.