For customers that have multiple sites on their single server, they arrive at a site map after logging into the application.  The map has color-coded site pins that provide a site status.  We have introduced a new site pin color status, Yellow.  The yellow status indicates there are inactive unacknowledged alarms.  For example, if your site had an alarm for engine running but the engine is no longer running then the alarm is inactive and awaiting user acknowledgment, as a result, the site pin color status would change from red to yellow.  

      

Here is a refresher of the site pins status colors:

We are introducing Chrome as one of our supported Internet browsers for the application.  Warning, if you use the generator camera feature you will still need to use IE 10 or newer as your default internet browser.  In the near future, we will be working on options for using Chrome with the generator cameras.

In the equipment list of the EPMS screen, we have filtered out all equipment except for ATSs and Generators.  

The camera section on the EPMS screen has changed from showing a generator to a camera.  Click on the Select a Camera area to select the camera you want to view.

The live view entity image configuration has been enhanced to configure the entity image and associate that image to a status.   This was enhanced to provide a larger variety of statuses that can be supported in the Live View.

       

       

       

       

       

• Any Entity that does not have a default_image definition in Aurora Admin will display with the original version of defined Entity Images. Existing Live Views will not be broken and will continue to operate in exactly the same way as they had previously.
• Any entity that is configured with custom Entity State icons (previous functionality) prior to this upgrade will need to be re-defined in Aurora Admin.
  
• Existing Entities in Aurora Admin can be upgraded to the new defaults simply by running a script on the BluePillarConfiguration database on the Aurora server. Once the script has been executed on the Aurora Server, and after Control Manager has been restarted, the new default images will show up in any Live View that was created using these Entities.
  
• In existing Live Views, the original image will show up in the designer, but the new image will be applied at Runtime.

Solar Edge Entity

An Aurora API Connector Plugin was created for SolarEdge.  The entity can be selected and created when a custom kepware entity is defined and the GIM is unconfigured.

      

1. API Endpoint
   
2. API Key
   
3. SolarEdge SiteId(s)
   
4. SolarEdge kW TagId (from Aurora)
   
5. Beginning and Ending request times in eastern  (site time)
   

DevOps

Aurora Server Maintenance (ASM)

A new ASM Task was created to identify when the Diagnostic Retriever Cleanup has failed transactions.  It checks to see if any Diagnostic Retriever tasks have failed and removes the failed transaction zipped folders older than 1 week in the temp folder.  The task also checks to see f there are any log files unzipped in the temp folder and if so then removes log files older than 1 week, zips up the folders without the log files and then removes the empty zip folders. The task is scheduled to run once a day.

A new ASM Task was created to check for configured Aurora Data Interval Rollups that have stopped running.  If the rollups have stopped running then an email notification is sent to the Blue Pillar help desk to investigate.  The task is scheduled to run once a day.  

A new ASM Task was created to check once a day for Aurora's second, minute and quarter-hour data cleanup that has fallen behind and needs to be cleaned up.  When the task runs and finds the telemetry data needs to be cleaned up then an email is sent to the Blue Pillar help desk to take action.  The task is scheduled to run once a day.

A new ASM Task was created to check for stale data every 15 minutes by tag log id in the log minute table for every 10 intervals.  When stale data is detected then an email alert is sent to the Blue Pillar help desk to take action.

The Diagnostic Notification Task has been updated to check for certifications that will expire in 15 days and/or 30 days of their expiration date.  Certifications that are checked are the OPCUA Certification (Gateway Comms) and the Webservice Certification.  The task is scheduled to run once a day.

Notifications

Defect Fixes

Functional Area	Description of Bug
Telnet Connect Error	We are seeing errors in EventViewer: Telnet Connect in CONNECT Error: No connection could be made because the target machine actively refused it. This is due to us trying to connect to Telnet for non-sixnet devices. We blacklisted the ip addresses from trying to connect to Rtu Security so that we stop trying to connect to non-sixnet devices.
Alarm processor is ignoring alarmtimedelay for gate kept tags	This was fixed by having the aforementioned method check against the time delay before it returns true, or better yet check the time delay before it attempts to activate.
Incorrect IP Address listed in the EntityDeviceAttribute table	When a gateway config is initially applied with a default ip address and then later pushed again with the known ip address the confg was updating the network interface table but not the entitydeviceattribute table.
Microserver Device Configuration	When a new Microserver Entity is created, the Device Configuration screen has the Microserver selection dropdown locked.
Alarm Processor Timer Elapse Error in Event Viewer	Updated the linq query from trying to access a null property.
EPMS Alarm Count	An entity with an active alarm that was not displayed on the EMPS screen was included in the alarm count when the alarm count should only include entities with active alarms that are displayed on the screen.
ASM DatabaseBackup Task	The ASM Database Backup Task logs was erroring when the task was successful.