Often, the (remote) source component of a Niagara proxy point is itself a proxy point, typically under the Points extension of device in a field bus driver network (Lonworks, Bacnet, and so on). Or, if the remote station is in a JACE with its own I/O, the source component may be an Ndio or Nrio proxy point.

Another possibility is for the (remote) source component to be a specific slot of a point extension under a point, for example, the Total property of a NumericTotalizerExt. In other cases, the (remote) source component may be a kitControl type, such as one of the Math or Logic types, or one of the other more complicated types (for example, a LoopPoint or DegreeDays object).

Regardless of the source component, you model all remote Niagara data with proxy points by selecting from the “atomic” model of the four read-only point types.