The niagaraStation in the “profile.bog file” on a subordinate JACE has significance in property values of the station, for example the “Virtuals Enabled” property, or “Alarm Source Info” properties, as well as properties in various “device extensions” (for example, the Alarms and Users extension).

Example of device extension properties are the Alarms extension’s property “Alarm Class”, and the Users extension’s property “Sync Out Enabled” (used in “network users”). Default values for these two properties are “Default Alarm Class” and “false”, respectively. However, it may be that non-default values are wanted for these two properties in the Supervisor’s NiagaraStation (that models this JACE).

If working directly in the Supervisor station, you can set these property to non-default values. However, note that those values will be overwritten upon the next Join of this JACE (unless of course they have the same values in the profile.bog file in that JACE).

This can explain why after configuring “NiagaraStation properties” in the Supervisor station, that property values in that NiagaraStation and/or in its device extensions are later seen to “revert to default values”. Likely this happened following a Join, where that JACE’s profile.bog file still has default property values.

Therefore, you should review property values in the profile.bog file’s niagaraStation and its various device extensions, and change any ones that need to vary from default values. Again, remember to Save the profile.bog file after making any changes.

Additionally, in cases where you are pre-engineering a JACE for eventual Join to a Supervisor, and want to do as much engineering as possible in the JACE station (possibly even lacking access to the Supervisor station), there are possible “property additions” that you may need to perform in the profile.bog file. See Provisioning slot additions in a profile.bog file.