Aurora Platform 5.7 Release Notes

Release Date:  February 20, 2017

A PDF Version is available as an attachment at the bottom of the article.

Aurora Platform

Event History | Compliance

The Aurora Platform has been updated to provide Event History with or without compliance features. Blue Pillar healthcare customers will benefit having the compliance features turned on (enabled) and the Blue Pillar energy customers will benefit having the compliance features turned off (disabled). The platform has configuration settings for the Administrator to enable and disable compliance features by server and by emergency power supply system. The compliance features have been streamlined to provide visual indicators to help find events that can be selected for compliance review. In addition, there are several new compliance reports to help determine how well an emergency power supply system is doing month to month to prepare for a compliance review.

Event History – Compliance Disabled

Event History – Compliance Enabled

Compliance Configuration Settings

How to enable compliance features by system:

  1. Select the Operations menu option
  2. Select Event History and Aurora Platform displays the Event History
  3. Select the Compliance Setting Cog in the upper right hand corner and Aurora Platform displays the Compliance Setting screen
  4. Select a System that has compliance disabled from the System list and Aurora Platform displays the settings for the selected system
  5. Select the Enable button and Aurora Platform displays the compliance settings options
  6. Select at least one of the Compliance Event Criteria
  7. Click on the window ‘X’ once your selection is complete and Aurora Platform will save the selections and close the window 

Compliance Settings by System

Compliance Settings by System Options

Note: The Compliance Event Criteria is the criteria the application will check each event for compliance. When the event meets the selected compliance event criteria then the event will receive a successful visual indicator that the event can be used for compliance review.  

How to disable compliance features by system:

  1. Select the Operations menu option
  2. Select Event History and Aurora Platform displays the Event History
  3. Select the Compliance Setting Cog in the upper right hand corner and Aurora Platform displays the Compliance Setting
  4. Select a System that has compliance enabled from the System list and Aurora Platform displays the settings for the selected system
  5.  Select the Disable option and Aurora Platform turns the compliance off with the option to turn it back on

Compliance Settings by System Options

Compliance Settings by System

Event History

The Event History provides all of the events that occur for each emergency power supply system by date in a calendar view. The calendar view has been updated to filter by event type, event status and compliance status for systems configured with compliance enabled.

Event Types:

  • Load Test (blue) – a test initiated through the Avise interface in which a system was transferred to and ran on emergency power for a user defined period of time.
  • No Load Test (green)– a test initiated through the Avise interface in which a system generator(s) ran for a user defined period of time.
  • Load Shed (blue) – an event to reduce the load on the emergency power supply system at the request of the utility company.
  • Outage (red) – a system detected loss of normal power for at least one of the ATS in the system.  Planned or unplanned, emergency events are tracked in the same manner as a Load Test.

Event Status:

  • Complete – Events with no post checklist items that auto completed or events with post checklist items that have been completed and saved in the Event Details.
  • Incomplete – Events that have post checklist items that are pending completion on the Event History calendar.
  • Cancelled/Aborted – Tests initiated through the Aurora Platform interface can be “aborted” if necessary.  Aurora Platform tracks these and provides as much data as possible in order to account for a potential run time or switch activity event though the test was aborted.  The Compliance report is generated with “Aborted” in the title of the report. 

Compliance Status:

  • Successful √  – when all of the configured compliance event criteria has been met
  • Unsuccessful X – when and event failed to meet all of the configured compliance event criteria

How to view Events in Event History for disabled compliance systems:

  1. Select the Operations menu option
  2. Select Event History and Aurora Platform displays the Event History
  3. Select the System filter
  4. Select a System from the enabled list and Aurora Platform displays 2 filtered lists: Event Types and Event Status
  5. Click on the Refresh button to apply the filters and Aurora Platform displays the system’s events in the calendar
  6. To remove an event type or event status filtered item then click on the “X” next to an item name in the filter fields
  7. Click on the Refresh button to apply the filter changes and Aurora Platform will only display the event types and event statuses listed in the filter fields
  8. To add an event type or event status back to the filter then click on the list of values down arrow button and select the item and Aurora Platform will place the item back into the filter field
  9. Click on the Refresh button to apply the filter changes and Aurora Platform will only display the event types and event statuses listed in the filter fields

Event History – Compliance Disabled

How to view Events in Event History for enabled compliance systems:

  1. Select the Operations menu option
  2. Select Event History and Aurora Platform displays the Event History
  3. Select the System filter
  4. Select a System from the enabled list and Aurora Platform displays 3 filtered lists: Event Types, Event Status and Compliance Status
  5. Click on the Refresh button to apply the filters and Aurora Platform displays the system’s events in the calendar and a list of compliance months
  6. To remove an event type, event status or compliance status filtered item then click on the “X” next to an item name in the filter fields
  7. Click on the Refresh button to apply the filter changes and Aurora Platform will only display the event types, event statuses and compliance statuses listed in the filter fields
  8. To add an event type, event status or compliance status back to the filter then click on the list of values down arrow button and select the item and Aurora Platform will place the item back into the filter field
  9. Click on the Refresh button to apply the filter changes and Aurora Platform will only display the event types and event statuses listed in the filter fields

Event History – Compliance Enabled

The compliance enabled Event History provides √  and X indicators to show when events have met or failed to meet their Compliance Event Criteria. The indicators also provide an easy way to select an event for compliance review.

  • An event in the calendar that met its configured compliance event criteria will receive a
  • An event in the calendar that failed to meet its configured compliance event criteria will receive an X
  • A month in the list of months that has at least 1 event that met its configured compliance event criteria will receive a
  • A month in the list of months that failed to have at least 1 event meet its configured compliance event criteria will receive an X

How to navigate to another month on the calendar:

    1. Select a month in the Last 12 Months list to the left of the calendar and Aurora Platform will display that month’s calendar
    2. Alternatively, you can click on the right and left arrows of the Calendar header to view one month at a time.

Event Details

Aurora Platform provides event details for each event. The event details include the Event Log, a place to enter event comments and the ability to conduct trending and ad hoc reporting on the event. This is also where Event Post Checklist items would be completed. All Events that without a post checklist will be completed automatically.

How to view Event Details for enabled and disabled compliance systems:

  1. Viewing the Event History with a system pre-selected, select an event on the calendar and Aurora Platform displays the Event Details modal

Event Details – Incomplete Event

This event is awaiting the completion of the post checklist items and then click the Save Event button to get the compliance reports.

Event Details – Complete Event

This event is complete and the event reports are available. We have a new report available on the event details called Time to Bus Compliance that provides a list of ATS service types of critical and life safety that meet Time to Bus during the event reporting time period.

Compliance Reporting

Several new reports have been created for compliance. The reports should be able to help determine if the emergency power supply system is being operated and tested properly for compliance review.

Note: The compliance features must be enabled in order to access the compliance reports.

How to execute a compliance report:

  1. Select the Operations menu option
  2. Select Event History and Aurora Platform displays the Event History
  3. Select the reporting icon in the application header and Aurora Platform displays the Compliance Reporting modal
  4. Select a report from the Report list field and Aurora Platform displays the report selection criteria fields
  5. Select the start and end date or use the default dates
  6. Select one of the systems in the System(s) field
  7. Select the Preview button and the Aurora Platform displays the report in the report viewer 

Compliance Reports

Compliance Reports – Report Viewer

List of new Compliance Reports: 

  • Initiating ATS Report – this report provides all ATS that were the initiating ATS for the reporting time period for Outage, Load Reduction, Auto Load or Manual Load event types
  • 30 Minute Generator Loaded Run Report – this report provides all Generator runs during the reporting time period with the Generator configured rated kW and 30% rated kW with the actual loaded run time regardless of event type
  • Generator 30% Rated Load Report – this report provides all Generator runs during the reporting time period with the Generator configured rated kW, 30% rated kW with actual run time and average load from the event start time to the event end time regardless of event type
  • All ATSs Transferred – this report provides all ATSs that were in an event group that transferred successfully for the reporting time period for Outage, Load Reduction, Auto Load or Manual Load event types
  • Time to Bus Compliance – this report provides a list of ATS service types of critical and life safety that meet Time to Bus during the event reporting time period

How to export a compliance report:

  1. Select the download option in the report modal header and Aurora Platform provides the following option: Adobe PDF File, Excel, Rich Text Forma, TIFF file and Web Archive
  2. Select one of the output options and Aurora Platform downloads the report awaiting selection of Open, Save or Cancel 

Compliance Reports – Report Viewerats.png

Generator Loaded Runs 20/40 Day Window Report

The Generator Loaded Runs 20/40 Day Window Report is still available for the electrical systems that are being inspected on the 20/40 day window instead of monthly. In order for the generator information to be included on the report in the event details the “Include on Generator Loaded Runs 20/40 Day Window Report (Legacy) flag must be checked in the Event Details.

Event Details

SNMP Traps

Feature Description

The SNMP Traps message has been updated to include the Blue Pillar IANA subscribed vendor id, when an alarm has been set and when an alarm has been cleared.

Each trap message will include the following variables in a string pipe delimited text format:

  • OID Line Item 1 – a required line item that can be ignored
  • OID Line Item 1 – Vendor Id
  • OID Line Item 3 – Site | System | Entity | Description | AlarmSet | AlarmSetValue | AlarmClear | AlarmClearValue | AlarmDateTime

Definition of each item in trap message

  • Vendor Id – the Blue Pillar IANA subscribed Vendor Id
  • Site – the location name of where the alarm occurred
  • System – the emergency power supply system of where the alarm occurred
  • Entity – the equipment name of where the alarm occurred
  • Description – a description of the event or type of alarm
  • Alarm Set – a value of True indicates the Alarm has been set
  • Alarm Set Value – the discrete value that set the alarm to active
  • Alarm Clear – a value of True indicates the Alarm has cleared
  • Alarm Clear Value – the discrete value that cleared the alarm
  • Alarm Time – the date and time the alarm was set or cleared in this format MM-DD-YYYY 00:00:00

Here is an example of an Alarm Set Trap Message:

OID:  1.3.6.1.2.1.1.3.0  Value:  0      

OID:  1.3.6.1.6.3.1.1.4.1.0  Value:  1.3.6.1.4.1.49042

OID: 1.3.6.1.4.1.49042 Value: Site: TestSite_1 | System: TestSystem_1 | Entity: TestGenerator_1 | Description: Generator Engine is Running | AlarmSet: True | AlarmSetValue: True | AlarmClear: False | AlarmClearValue: False | AlarmDateTime: 12-01-2016 13:10:02

Here is an example of an Alarm Clear Trap Message:

OID:  1.3.6.1.2.1.1.3.0  Value:  0

OID:  1.3.6.1.6.3.1.1.4.1.0  Value:  1.3.6.1.4.1.49042

OID: 1.3.6.1.4.1.49042 Value: Site: TestSite_1 | System: TestSystem_1 | Entity: TestGenerator_1 |Description: Generator Engine is Running | AlarmSet: False | AlarmSetValue: True | AlarmClear: True | AlarmClearValue: False | AlarmDateTime: 12-01-2016 13:26:02

Note: SNMP Trap will only get alarm messages that have a configured alarm level.

Alarm Email Template

Feature Description

The Alarm Email Template has new Available Fields so that Email Templates can be created to provide additional information about where the alarm occurred.

The following have been added:

  • Tag_FriendlyName
  • ServerName
  • AlarmTimeDelay
  • Site_StreetAddress1
  • Site_StreetAddress2
  • Site_City
  • Site_PostalCode
  • Site_State

Alarm Email Template

How to create a custom Alarm Email:

  1. Logon to Admin
  2. Select the Admin menu option
  3. Select the Server Config menu option
  4. Select the Alarm Email Template on the left hand side and the application displays the Alarm Email Template
  5. Insert desired variables (denoted with the double percent signs) into the SUBJECT field by selecting each one and clicking on the ‘insert’ arrow in front of the SUBJECT line
  6. Insert any desired text into the SUBJECT line
  7. Insert desired variables into the BODY of the email by selecting each one and clicking on the ‘insert’ arrow in front of the email body
  8. Insert any desired text into the email body
  9. Check the desired ALARM STATE checkboxes for email receipt Note: more than one alarm state can be selected.
  10. Click the SAVE button at the bottom of the page
  11. Log out, clear browser cache, and log back in to verify saved configurationHow it will look in an email Subject Line: Alarm Detected for GEN_101 How it will look in the email Body:   Check the Generator Oil Pressure – LoLo Detected at 0 for GEN_101 at Site: BP Indy Site and System: BP Indy System A at 06/17/2016 04:10:49.

Notes:  

Here is an example of a message entry in the template:   %%Description%% %%AlarmState%% at %%Value%% for %%Entity%% at Site: %%Site%% and System: %%System%% at %%DateTime%%.

Here is an example Subject Line entry in the template: Alarm %%AlarmState%% for %%Entity%%

By default, there will be standard alarm template created for the 'detected' Alarm State only.

The Administrator can check the 'acknowledged' and 'cleared' Alarm States to receive emails if desired.

If all Alarm State boxes are unchecked, then no emails will be sent for alarms.

There is only one template for All Types of Alarms. Alarms will be identified based on the fields insert in the subject and body of the email template.

If there is no value for a specified field, then it will not be included in the alarm notification. The email will be presented with a blank area of where it would have been inserted.  

Dev Admin Tool

Feature Description

A tool has been built for Blue Pillar Development that provides the ability to rename a site, system or entity and the ability to move entities to other sites and systems. If there is a desire to make a configuration name or location change then submit a request to help@bluepillar.com.

Bug Fixes

Work Item

Summary

Description of Bug

6760

Installer - DB_SERVER Name

Fixed the Aurora Platform Software Installer so that when a server name is entered for the server database location (for remote databases) that the installer will retain the entered server name and not revert to local server name.

6761

Installer - Client Name Mismatch

Fixed the Aurora Platform Software Installer so that when the ClientName in the Client tables does not match the server name then the installer will not insert another client record.

6805

ATS Entity Details Template

Fixed the ATS Entity Details template view when the entity is offline to display the correct description of Connected to Available. It previously displayed Emergency Available.

8762

Fuel Tank Trending

Fixed the trending so that entities that are not configured to a site can be reported on in the Trending Tool.

11098

Active Directory User Name

When Active Directory sign on is setup then the Login name will appear throughout the application.

11500

Fuel Tank Config

Fixed the Fuel Tank configuration so that the generator to fuel tank association works the first time it is selected.

14742

Active Directory Logon to Aurora Admin

Fixed the Active Directory sign on to Aurora Admin.

15238

Update location field on legacy reports

Fixed the location fields on existing reports to display the building as the location of an entity.

15832

Admin and Alarm Configuration

Fixed the save collision when Admin configuration and Alarm configuration was taking place as the same time.

16177

Admin Gateway Config

Fixed the validation of the Gateway Network Configs so that the IP Address and Mac Address can only be used once.

16178

Admin Gateway Config

Fixed the list of Gateways in the Gateway Config to be in alpha order.

16179

Admin Gateway Config

Removed the “Is OPC UA Server?” flag in the Network Config so that the Administrator has to configure the OPC UA Server in Network 2 config.

16180

Admin Gateway Config

Add the functionality to be able to delete a Gateway that is not in use.

16181

Admin Gateway Config

Fixed the Gateway with a formula tag to use the full "GIM" name versus the JSON string that was being added to the tag attribute table.

16331

Gateway Restart

Fixed the Gateway in Pull Mode to trigger a restart when there is a Save and Download of the configuration from the Aurora Platform.

16336

Deactivated NetworkSystemGroups still being cached to Foresite

Fixed a deactivated NetworkGroup so that it will no longer be cached to Foresite.

16378

Accumulator Tags

Fixed the Accumulator Tag starting data point so deltas are accurate.

16414

DeviceInstances Record is Deleted When Modifying a Tag for a Gateway Entity

Fixed the Admin Config with a Gateway configured when a subsequent modification occurs then the application now retains the Gateway Entity and Device Settings in the DeviceInstances table in the BluePillarMicroserverDatabase.

16539

KPI Configuration

Fixed the KPI configuration so that it will save the modifications to the configuration.

16572

Alarms on Analog Tags

Fixed the Alarms so that it displays the accurate analog tag value that the alarm was triggered on.

16634

Un-configured Demand Response Alarms

Fixed the spamming of alarms to integrated endpoints that don’t have demand response configured.

16656

User Permission

Fixed the permission issue of allow a user with only CanViewLiveSummary being able to run a Load Test

17585

Admin Gateway Config

Fixed the gateway config so that it can be renamed.

17604

Alarm Config

Fixed the Alarm configuraton so that it is not required to conduct a save and download in the Aurora Admin Config.

17646

Fuel Tank Trending

Fixed the trending of Fuel Tanks to display the second and minute data.

17655

Site-less Entities default to Server Time in Trending

Fixed the entities that are not associated to a site to grab the datetime reference from the entities physical location so that it references the site time vs the server time for trending.

17702

Foresite User Permission

Fixed the Users access to systems in Foresite that are only included in Network System Group permissions.

17703

User Permission

Fixed the user with Read Only permission so that they are not able to start an event or acknowledge alarms.

17705

Groups Config

Fixed the Network Group Permissions config changes so that it does not require a Save/Download just a Save.

17714

Alarm History Report

Fixed the Alarm History Report from timing out.

 

Hotfixes

This includes any change to the release build post the release date.

Build

Hotfix Date

Summary

Description of Hotfix

5.7.0058.001

02/27/2017

UI Navigation and screen rendering is slow

Fixed the slowness of the platform when navigating between the EMPS and Operations Summary screens.

Empty Event Log

Fixed the subsequent loads of the EPMS page was causing the system’s event log to be empty

5.7.0062.001

03/03/2017

Event Complete Timing Out

Fixed events with post checklist items to complete and generate the reports.

5.7.0074.001

03/15/2017

Unable to trend discrete tags at a second interval

Fixed the trending so that discrete tags can be reported at the second interval rate.

5.7.0079.001

03/21/2017

IMonnet Database Setting

A new setting to allow duplicate (ip addresses) devices for IMonnet. 

5.7.0089.002

 

03/30/2017

 

Time Series Issues with Data Rollups

Fixed the Time Series Issues so that Qtr Hour to Month data rollups are now working.

Load Test not auto completing

Fixed the Load Test with no post checklist items to automatically complete.

5.7.0093.001

04/03/2017

Foresite Rending Views Issue

Fixed the rending Event History views in Cloud Foresite.

5.7.0107.001

04/17/2017

Alarm Configuration settings not honored

Fixed the platform to honor new and updated alarm configuration settings without having to restart control manager.

5.7.0130.001

 

5/11/2017

 

OPC UA required a restart after a Save/Download of the Config

Found an issue in the Installer that fixed the issue.

Verbosity was required to be On for OPC UA Connection to be stable

Created a MonitoredItemNOtificationDelay registry setting so that Verbosity does not have to be turned On.

5.7.0146.001

06/01/2017

Cameras not displaying on the EPMS screen

Fixed Cameras on the EPMS screen for IE.  The fix does not apply to Chrome.

5.7.0220.001

07/18/2017

Entity Details display was slow when viewing a Generator associated with a fuel tank

Improved the display time for the Entity Details so that it loads faster.

Data processing in TestState.AnalyticsLog PersistanceTimer_Elapsed

Updated the processing time so that the UTCNow time is configurable.

5.7.0228.001

08/15/2017

General Equipment Breakers in Live View

The General Equipment Breakers in the Live View were not treated as independent tags causing 1 breaker to drive the status of all breakers on the view.

5.7.0292.003

10/19/2017

Event Groups Disappearing

The application has been updated to be able to handle same name ATS Groups

5.7.0293.001

10/20/2017

Kepware Service Start/Restart Errors

 

Kepware was trying to restart a non-existent version of Kepware thus causing stale data and causing test to abort with a message “No Generators being in an available condition”.

5.7.0348.002

12/14/2017

Alarm Lagging 

Stale Data 

Fixed the delay of alarms being triggered to be created and cleared. 

Modified Control Manager to reset connections for the gateway and prevent OPC UA connection from being restarted when test state has not completed loading the configuration.   

5.7.0036.003

02/05/2018

Gen not Added to Event

During an Event if Engine Not In Auto Is Null or Not Found then the application we excluding it from the event.  This has been corrected to include the Gen for Auto Load Test, Auto No Load Test and Manual Load Test.

5.7.0052.002

02/21/2018

Live View Map Locking

Updated the google map API to fix the locking of the map on multi-site instances.

 

Aurora Server Requirements

  • Hardware – The server hardware can be provisioned using any of the following options:
    • Hosted as a Virtual Machine in Windows Azure
    • Deployed as Virtual Machine using the customer’s existing virtual infrastructure
    • Using a Blue Pillar provided Intel-based physical server
  • Recommended Operating System Software
    • Windows Server 2012 R2 or minimum Windows Server 2008 R2 SP1
  • Other Recommended Software
    • Windows Server 2012 R2 or minimum Windows Server 2008 R2 SP1
    • Microsoft SQL Server 2012 SP1 or minimum SQL Server 2008 SP1
    • Microsoft .Net framework Version 4.5
    • Windows Internet Information Server (IIS) (access to port 80/443 via http/https)
    • SMTP Server access
  • Server Sizing – The physical specifications of the server will depend on the total number of tag counts that will be managed by the server. As a minimum, the following is recommended:
    • 8 Core Machine
    • 16 GB of Memory
    • 1 x 60GB OS Partition, 1 x 375GB Data Partition, 1 x 275GB Log Partition, 1 x 100GB Backup Partition

Aurora Server Administration Requirements

  • Database Backups
    • SQL database backups are taken and stored locally for 24 hours in the event of data corruption and recovery.
    • Additional SQL backups can be conducted in accordance with the customer’s disaster recovery policies.
    • Blue Pillar can provide best practice guidelines for setting up and managing additional backups.
    • Blue Pillar can also provide services to manage the SQL backups on behalf of the customer.
  • Remote Access for Blue Pillar
    • For ongoing support, maintenance, and upgrades, Blue Pillar needs to ability to remote into the server via Remote Desktop Protocol. This is typically accomplished using the customer’s existing VPN connection method.
  • User Access
    • Facilities personnel will access the server via http/https on port(s) 80/443. Firewall traffic to prevent all other traffic may be implemented at the Customer’s discretion provided it doesn’t interfere with Blue Pillar’s Aurora product’s functionality.
  • Browser/Workstations
    • Supported and Tested Browsers
      • Internet Explorer 10 or higher
      • Google Chrome 32 or higher
    • Supported and Tested Operating Systems
      • Microsoft Client Operating Systems
    • Browsers demonstrating considerable compatibility
      • Microsoft Edge
      • Mozilla Firefox

 

 

 

 

 

Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.
Powered by Zendesk