Double-click Schedules 
under any BacnetDevice to access its Bacnet Schedule Import Manager. Figure 36 shows this view in “Learn mode” after a discover, with BACnet schedules added.
Imported schedules and calendars are Niagara schedule components with a BacnetScheduleImportExt. Events in an imported schedule (or calendar) are obtained from that BACnet device, and are read-only. By default, the Schedules device extension also contains a Retry Trigger, for automatic usage as needed. For details see “About the Retry Trigger” in the Drivers Guide.
Note that the Schedules device extension can also contain BacnetScheduleExport components. These correspond to Niagara schedules or calendars that are “pushed” to specific BACnet Schedule or Calendar objects in the remote device. See Bacnet Schedule Export Manager for related details. Also, see the next section Notes on Bacnet Schedule Imports.
The Add (and Edit) dialog for importing BACnet Schedules and Calendars is shown in Figure 37.
The default name is the BACnet object’s name, and you typically leave this and other properties at defaults. Upon adding, the object’s configuration is uploaded to the read-only Niagara schedule component. Note that the default import (read synchronization) from the device’s object is “Manual”, meaning that you must use the button in the Bacnet Schedule Import Manager to refresh the Niagara schedule. Alternatively, you can also set the trigger time of the BacnetScheduleImportExt to be either Daily or Interval, if you anticipate ongoing changes in the BACnet object’s configuration.
When the remote BACnet schedule is imported, if it contains a reference to a Calendar object in the device, the Calendar object
will also be brought in as a schedule import, in order to keep the schedule in Niagara self-complete.
Figure 38 shows the property sheet of a BacnetScheduleImportExt for an imported schedule.
Note that the BACnet property “Priority for Writing” is included—however, this means little in the Niagara (station) usage of this imported schedule.