Network component hierarchy

Hierarchically, the component parentage is: network, device, device extensions, points (Figure 2).

Figure 2. Example driver architecture (Bacnet)

To simplify driver modeling, the New Station wizard automatically creates the necessary “Drivers” container, complete with a NiagaraNetwork (and its required component slots).

If engineering a JACE station, you invariably add additional driver networks, opening the driver’s palette and copying the network-level component into Drivers. Or, you can use the New button in the Driver Manager. Examples are a LonNetwork or BacnetNetwork.
If engineering a Supervisor (PC) station, the NiagaraNetwork may be the only one needed. Optionally, you may add a “database” network (providing the PC host is licensed for it). And, if a PC host licensed as a direct “integration Supervisor” (e.g. BACnet Supervisor), you may add a driver network (e.g. BacnetNetwork) directly into its Drivers container.

Regardless of host platform, in most cases the network component is the only item you need to manually copy from that driver’s palette. After that, you use “manager views” to add child components like devices and proxy points, even if programming offline.This enforces the correct component hierarchy under that driver as you engineer, and helps coordinate mechanisms used by the driver for communications. Exceptions to this rule are noted (as applicable) in other documentation about NiagaraAX drivers.