Blue Pillar IIoT Platform 2022.09.15
Release Date: September 16, 2022
The enhancements and defect fixes in this release are for internal applications used by Blue Pillar Engineer's and the Customer Support Desk.
- AdminIT, DesignIT, and
ManageIT have all been completely alphabetized. This includes every
drop-down selection list in each application. The ManageIT tag list
on the ‘Data’ tab has also been alphabetized and categorized (headers
added) by VALUE TAGS and CONTROL TAGS.
- The BluePillar API has
been enhanced by adding a ‘Raw Data’ route so that API customers can see
all data values with their actual time stamps. API calls now also
include the ‘Equipment Type’ in ‘SiteInfo’ routes (specifically requested
by Palm Energy). Sample API calls are detailed in the BluePillar API
documentation and require an API code, which is unique per customer.
Results of a ‘Raw Data’ call will look similar to this:
Notice that the timestamps are exact, and the tag Values are only rounded to four decimal places. This route was added so that the API would not miss any data points at higher publication rates due to the timestamp drift on the gateway.
- In the ViewIT application, the storage location of customer
ViewIT logos and ViewIT mobile logos has been changed. We have also
added a fallback safeguard in case the customer image is not found in the
specified logo file. The default fallback images are the BluePillar
logos that already show up in General2.
- The Telemetry Data monitoring
application where it would miss a Telemetry outage if the last hour showed all
-99s for a tag, but the hour prior to that had all valid data values for that
tag. We were previously looking for a mix of valid data points and -99
values in the hour prior to the last hour. This edge case almost never
occurs at lower publication rates. However, at a 15-minute publication
rate, it could very easily occur. The Telemetry outage would never be
detected because when the Monitoring app ran the next hour, it would detect all
-99s in the last hour and all -99s in the hour prior to that, which is a ‘do
not notify’ scenario because it would be a repeat notification. Now, the
monitoring application is set to check for all -99s in the last hour and ANY
valid data values in the hour prior to that.