...
The following are the minimum requirements for tagging points and histories. However, we recommend following the full haystack standard which allows more advanced querying (for example, querying for site meters).
| Points | Histories | |
|---|---|---|
| Tags | hs:point hs:kind | hs:his n:history hs:kind |
| Relations | hs:siteRef | hs:siteRef |
Tagging with the Program Service
...
| Tip | ||
|---|---|---|
| ||
Do you have a lot of energy trends all with the same name like "kWh"? Try batch-adding the "disMacro" tag to your points. disMacro uses $ to define template parts, so if you wanted your point to display the equipment name followed by the point name, you'd set your disMacro (String) tag as: "$equipRef $navName" |
| Anchor | ||||
|---|---|---|---|---|
|
| Info | ||
|---|---|---|
| ||
When a user updates tags or other items in the station, they should navigate to Station > Config > Services > PeriscopeService > Haystack Cache, right-click on "Haystack Cache" and choose Actions > Load Cache. This will force the load of any recent Haystack tags that were applied on the station, and ensure that Periscope will show that data appropriately as well. |
...
| Info | ||
|---|---|---|
| ||
| If the history extensions are created at the supervisory level, Niagara will automatically add the hs:his and n:history tags as implied tags for you. |
| Anchor | ||||
|---|---|---|---|---|
|
Sometimes a station may have histories that are created outside of a normal history extension, which causes it to lack the appropriate history tags. These types of trends can be manually added to the Haystack database by creating a new component and tagging the history appropriately. For example, let's assume a trend was imported from a .CSV file located at /Weather/CharlotteOAT. To add this to Periscope:
...