Schedule Migration - Metasys - LIT-1201535 - Supervisory Device

Schedule Migration - Metasys - LIT-1201535 - Supervisory Device - Network Engine

N1 Migration with the NIE Technical Bulletin

Product name

Network Engine

Document type

Technical Bulletin

Document number

LIT-1201535

Revision date

2019-04-09

N1 Network schedules defined in NCMs remain in the NCMs and are viewed in the NIE UI after migration. The Metasys N1 Network scheduling feature differs significantly from the Metasys system scheduling object. The major differences are:

Metasys N1 Network schedules contain 14 days of schedules (seven regular and seven alternate), plus one holiday and infinite temporary (exception) calendar schedules. Metasys system schedules contain 7 days of schedules and 4 different mechanisms for exceptions.
Metasys N1 Network schedules are on a single object basis. Metasys system schedules can have an infinite number of objects operated by a single schedule.

Using the previous differences, the following describes how a Metasys N1 Network schedule is migrated to a Metasys system schedule object.

Schedules are migrated only on AO objects, AD objects (mapped as a Metasys system AO), BO objects, BD objects (mapped as an Metasys system BO), MSO objects, and MSD objects (mapped as an Metasys system MSO objects). In all cases, only operational command schedules are migrated (start/stop/state0-4, adjust).

Note: The N1 exception schedule only supports the Date exception (for example, to schedule the same exception three days in a row using an N1 Exception schedule requires the use of three separate date exception entries). Date range, week day, and calendar reference exceptions are not supported.

A Metasys system schedule object is created if the Metasys N1 Network schedule contains weekly scheduling (days 1–7). It is named weekly and is created under the Metasys system object it is acting on; that is, the only object reference in the List of Object Property References attribute.

A Metasys system schedule object is created if the Metasys N1 Network schedule contains alternate scheduling (days 8-–14). It is named alternate and is created under the Metasys system object on which it is acting (that is, the only object reference in the List of Object Property References attribute).

The weekly schedule object contains the following exceptions:

an Alternate Calendar referenced exception with an empty timevalue/list (no operations on the exception days)
a Holiday Calendar referenced exception with the schedules for the holiday read from the Metasys N1 Network schedule
one or more date-based exceptions based on the temporary (calendar) schedules read from the Metasys N1 Network schedule

The alternate schedule object contains no exceptions.

The priority for writing attribute is undefined in this object because the schedule executes at the NCM.