Please ensure Javascript is enabled for purposes of website accessibility
Powered by Zoomin Software. For more details please contactZoomin

PI Manual Logger

Effects of tag scheduling priority

  • Last UpdatedNov 22, 2022
  • 6 minute read

The following examples show how tag scheduling priority affects when tag data is due. Note that individual tags have priority over tag groups with respect to clock scheduling.

Example 1

Tour Scheduling Definition:

  • Group1 - Weekly on Mondays, Wednesdays, and Fridays between 4 and 6 PM

  • Tag1a - None

  • Tag1b - Daily between 4 and 6 PM

  • Group2 - Weekly on Tuesdays between 4 and 6 PM

  • Tag2a - None

  • Tag2b - None

Scenario Tour Run #1 for Example 1

Actual Due Status During Tour Run at 5:15 PM on Wednesday:

  • Group1 - All Due ()

  • Tag1a - Due ()

  • Tag1b - Due ()

  • Group2 - All Not Due ()

  • Tag2a - Not Due ( on the PC, on the mobile device)

  • Tag2b - Not Due ( on the PC, on the mobile device)

Scenario Tour Run #2 for Example 1

Actual Due Status During Tour Run at 4:45 PM on Tuesday:

  • Group1 - Something Due ()

  • Tag1a - Not Due ( on the PC, on the mobile device)

  • Tag1b - Due ()

  • Group2 - All Due ()

  • Tag2a - Due ()

  • Tag2b - Due ()

Example 2

Tour Scheduling Definitions:

  • Group1 - Weekly on Tuesdays and Wednesdays between 4 and 6 PM

  • Tag1a - None

  • Tag1b - Daily between 4 and 6 PM

  • SubGroup1 - Weekly on Wednesdays between 4 and 6 PM

  • SubTag1a - None

  • SubTag1b - None

  • Group2 - Weekly on Tuesdays between 4 and 6 PM

  • Tag2a - None

  • Tag2b - None

Scenario Tour Run #1 for Example 2

Actual Due Status During Tour Run on Tuesday at 5:30 PM:

  • Group1 - Something Due ()

  • Tag1a - Due ()

  • Tag1b - Due ()

  • SubGroup1 - All Not Due ()

  • SubTag1a - Not Due ( on the PC, on the mobile device)

  • SubTag1b - Not Due ( on the PC, on the mobile device)

  • Group2 - All Due ()

  • Tag2a - Due ()

  • Tag2b - Due ()

Scenario Tour Run #2 for Example 2

Actual Due Status During Tour Run on Wednesday at 4:30 PM;

  • Group1 - All Due ()

  • Tag1a - Due ()

  • Tag1b - Due ()

  • SubGroup1 - All Due ()

  • SubTag1a - Due ()

  • SubTag1b - Due ()

  • Group2 - All Not Due ()

  • Tag2a - Not Due ( on the PC, on the mobile device)

  • Tag2b - Not Due ( on the PC, on the mobile device)

Scenario Tour Run #3 for Example 2

Actual Due Status During Tour Run on Wednesday at 10:00 AM:

  • Group1 - All Not Due ()

  • Tag1a - Not Due ( on the PC, on the mobile device)

  • Tag1b - Not Due ( on the PC, on the mobile device)

  • SubGroup1 - All Due ()

  • SubTag1a - Not Due ( on the PC, on the mobile device)

  • SubTag1b - Not Due ( on the PC, on the mobile device)

  • Group2 - All Not Due ()

  • Tag2a - Not Due ( on the PC, on the mobile device)

  • Tag2b - Not Due ( on the PC, on the mobile device)

In This Topic
TitleResults for “How to create a CRG?”Also Available in