Set Data Collection Seasonal Schedule and Planned Exceptions

Compliance and the understanding of what is expected to meet data collection requirements can include planned events such as seasonal outages, extended repair cycles, and other situations where assets might not be available to meet the expected collection periodicity.

In PredictivePortal, the setting of "Planned Exceptions" will impact what is due for collection both in the portal and on the portable data collector.  "Period Exceptions" can be entered on a case-by-case basis to indicate why a periodicity might be missed.  A Planned Exception, however, covers situations typically known ahead of time and likely to extend beyond one collection cycle.  See these articles: Compliance and Configuration: Wireless Sensor Planned Exception

In Watchman Reliability Portal, this feature was known as "Seasonal Scheduler".  The objective of this, and the Planned Exception, fundamentally, is to accurately depict the Compliance score for a program.

Watchman Reliability Portal: Seasonal Scheduler

Purpose

Seasonal machines can appear to be “overdue” in our system which causes a poor compliance rate for
customers. In order to provide improved compliance results by taking seasonal machines into account,
we have created the Seasonal Scheduler. Within ExpertALERT there is the ability to, per database,
override the initial collection periods with a custom collection period within the Seasonal Scheduler.
This will help get compliance rates back to where they are expected during “off” seasons.

Example: If Machine A is turned off during the months of June, July, and August, it is currently factored
into the compliance calculation and will lower the compliance rate. By turning off Machine A with the
Seasonal Scheduler, overall compliance rate numbers will improve during June, July, and August since
it won’t be factored into the compliance rate calculation.

Note: Within the Website Configuration in ExpertALERT there is a global check that allows access to
the View Seasonal Scheduler. This is a backend tool that is not part of the user interface. Once enabled,
access per user also has to be assigned within the User Manager back-end tool. If the user has the box
enabled, but the website configuration is disabled, all access is disabled. Each user who needs access to
the Seasonal Scheduler will have to request it through their account manager.
The Seasonal Scheduler also has the ability to filter the machines by searching machine name to make
searching through Areas with a large number of machines easier.

To Use

1. Log into Watchman Reliability Portal, www.watchmanportal.com
2. Click on Utilities > Seasonal Scheduler.
   1. The database and user must have Season Scheduler enabled in order to view this option.
3. In the dialog that comes up, you’ll see a list of Plants, Areas, and Machines.
4. If you select Machines you’ll find that each machine has a checkbox that corresponds to a
   month in the year. The checkboxes are on by default, and the hard-coded default collection
   period for Seasonal Scheduler is 31 days.
   1. Note: For every month that is unchecked, another 31 days will be added to the
      collection period for the last month with a checked box (and its original 31 days) in
      order to ensure enough coverage. If/when a new month is once again checked the
      collection period starts back at 31 days for every checked month.
   2. Important: You can’t have custom collection periods (e.g. 14 days vs. the default 31
      days) with Season Scheduler enabled.
   3. If all checkboxes are unchecked, the collection period will be turned to 1,000.
      Note: A 1,000 day period was chosen so the overdue date is not hit when a
      machine is offline for longs periods of time. If the machine is close to reaching
      the 1,000 days beyond the test date, the machine should probably be deleted by
      the owner.
      d. Here is an example of how to “read” the checkboxes:
      
5. Select which – if any –month(s) you want to uncheck (i.e. turn “off”).
   1. If a database has Seasonal Scheduler enabled, it will override any collection period in EA.
   2. Note: Checkbox selection changes are updated once every 24 hours.

M-01 will be active all year
M-02 will be inactive for the month of May with a collection of 62 days once May is the
current month. The collection period will be set back to 31 once June is the current
month.
M-03 will be inactive for the months of May-July. The collection period when May is the
current month will be 124. Once June is the current month, the collection period will be
93. Finally, once July is the current month, the collection period will be 62. Once August
is the current month, the collection period will default back to 31.