Aurora Platform 5.9 Release Notes

Aurora Platform

Menu Options

The Aurora Platform menu is now configurable to display only the menu options that are needed.  By default, all menu options are displayed.  If there is a preference to hide some of the menu options then send a request to our Customer Support Team.

Here is an example where the Energy menu option and its associated sub-menus are removed from the Aurora Platform Menu header.

Trending Actual Value

Blue Pillar has introduced a new Data Roll-Up value called Actual in Trending.  This new option will be the default trending/reporting value.

When you select the Trending application then the new defaults are as follows:

  • From Date = 4 hours prior
  • Start Date = current time the application was opened
  • Data Interval = Minute
  • Roll-up = Actual

Trending default criteria

The Roll-up default will remain as Actual when the Data Interval is changed to Minute, Quarter Hour or Hour.  Once the Data Interval is changed to Day then the default Roll-up becomes Average.

Upgrade Note:  Data stored for Trending prior to 5.9 will continue to use Average as the default Data Roll-up and data stored after 5.9 upgrade the Data Roll-up default is Actual.

Note:  The Month Data Interval option has been removed. 

Trending Chart with Actual Data Rollup

Trending Data Grid with Actual Data Rollup 

When trending a tag that logs discrete data then the trending application will default to Seconds Data Interval with Actual Data Roll-up and a Data Grid Chart.  No other Data Interval or Data Roll-up options are available for this type of tag.

The application does not allow reporting/trending with a mix of analog and discrete tags.  When they are selected together the User will receive a message “Select discrete and analog tags separately for reporting.”

For step by step procedures on how to use Trending, please refer to the Aurora Platform User Guide available at https://help.bluepillar.com   

 

API Enhancements

Blue Pillar has updated our API so that our API Customers can retrieve current alarm data without directly accessing the Aurora Platform database.  Based on the authenticated user’s permissions the alarm data will be retrieved by Site and System the user has permission for.

Here is a list of retrieval statements

  1. GET API Route to Retrieve Current Alarm State for All Active and Unacknowledged Alarms

Containing these fields:

  • Id
  • AlarmType
  • TagId
  • Description
  • Value
  • ValueFriendlyName
  • Status - (Acknowledged or Unacknowledged)
  • SiteId
  • Site
  • SystemId
  • System
  • EntityId
  • Entity
  • DeviceId
  • Device
  • TagId
  • Tag
  • DateTimeInitiated (site time)
  • DateTimeInitiatedUtc
  • url - request route for the individual alarm
  1. GET API Route to Retrieve Current Alarm State for a Single Alarm

Containing these fields:

  • Id
  • AlarmType
  • TagId
  • Description
  • Value
  • ValueFriendlyName
  • Status - (Acknowledged, Unacknowledged, Cleared)
  • SiteId
  • Site
  • SystemId
  • System
  • EntityId
  • Entity
  • DeviceId
  • Device
  • TagId
  • Tag
  • DateTimeInitiated (site time)
  • DateTimeInitiatedUtc
  • DateTimeAcknowledged (site time)
  • DateTimeAcknowledgedUtc
  • DateTimeCleared (site time)
  • DateTimeCleared Utc

When an authenticated User makes a request for an invalid alarm id then the API will return a Http 400 Bad Request containing a message “Alarm id is invalid”.

When an authenticated User makes a request for an alarm id that they do not have permission for then the API will return Http 403 Unauthorized Resource containing a message “Unauthorized resource requested”.

Version 2 (v2) of the API presents all of the same sub routes as V1 and makes the following changes: 

Method

V1 Route

V2 Route

Change

Description

GET

/v1/filters

/v2/filters

None

Gets Filters owned by the authenticated user. Includes all associated tags and tag detail.

GET

/v1/filters/{filterId}/Historical

/v2/filters/{filterId}/Historical

See v2 Historical Data Object response changes here

Gets historical data for the tags associated with the provided filter.

GET

/v1/filters/{filterId}/Live

/v2/filters/{filterId}/Live

None

Gets live data for the tags associated with the provided filter.

GET

/v1/tags/{tagId}/Historical

/v2/tags/{tagId}/Historical

See v2 Historical Data Object response changes here.

Gets historical data for the provided tag. 

GET

/v1/tags/{tagId}/Live

/v2/tags/{tagId}/Live

None

Gets live data for the provided tag.

POST

/v1/tags/{tagId}?value={tvalue}

/v2/tags/{tagId}?value={tvalue}

None

Attempts to update the value for the provided tag.

POST

/v1/tags/Historical

/v2/tags/Historical

New

Allows insert of data to our telemetry tables for Minute, QuarterHour, Hour and Day for one or more existing tags.  See sample request body here and historical post data object definition here.

GET

/v1/alarms

/v2/alarms

New

Returns a list of current alarms.  See sample response here and alarm data object definition here.

GET

/v1/alarms/{alarmId}

/v2/alarms/{alarmId}

New

Returns the current state for the provided alarm.

 

Historical Data Object v2 Changes

Field

Type

Change

Description

Total

Number

Modified

This is now the value of the sample at the earliest time unit for the sample, rather than the sum of the values over the interval of the sample.

MinTsUTC

string

New

The date/time when the Min value was captured

MaxTsUTC

string

New

The date/time when the Max value was captured.

SampleTsUTC

string

New

The date/time when the SampleValue was captured.

Sample

Number

New

The earliest value within the sample interval. For an interval of Minute this is the first (00) second, for all other intervals this is the first minute.

 

Historical Data POST Sample

{

  "insertType": "insertNew",

  "interval": "Day",

  "timeZoneSource": "Site",

 

  "intervalData": [{

    "timeStamp": "2017-12-05 00:00:00",

   

    "tagData": [{

      "tagId": "18D906E3-41B2-4E93-A434-75B7B8281767",

      "value": "18380",

      "mean": "18370",

      "min": "18350",

      "max": "18380",

      "median": "18350",

      "stDev": "1.5",

      "sampleSize": 59,

      "quality": 1,

      "minTimeStamp": "2017-12-05 00:00:59",

      "maxTimeStamp": "2017-12-05 00:00:00"

    }]

  }   

  ,{              

    "timeStamp": "2017-12-04 00:00:00",

   

    "tagData": [{

      "tagId": "18D906E3-41B2-4E93-A434-75B7B8281767",

      "value": "18390"

    }]

  }   

  ,{             

    "timeStamp": "2017-12-03 00:00:00",

   

    "tagData": [{

      "tagId": "18D906E3-41B2-4E93-A434-75B7B8281767",

      "value": "18400"

    }]   

  }

  ,{

                "timeStamp": "2017-12-05 00:00:00",

               

                "tagData": [{

      "tagId": "722612A6-D4CD-4C67-8C16-13EB2B102CAB",

      "value": "9987"

                }]

   

                  }]               

 

}

 

Historical Data POST Object Definition

***Note: there are 2 sample types supported for a post, a single data point which contains a tagId, timestamp, value and an aggregated type which contains additional fields such as min/max/mean etc. over an interval.  When posting an aggregated sample, all aggregated fields are required as stated below.

Field

Type

Required

Description

insertType

string

yes

Only supports ‘insertNew’ which means a new record will be added.  If the record already exists, the data point will be ignored.  May support updates in the future.

interval

string

yes

This defines the type of sample being posted.  Supported values are minute, quarter-hour, hour and day. 

timeZoneSource

string

yes

The source of the time zones for the timestamps in the posted payload.  Supported values are site and utc.  When set to utc, there will be no conversion done on the posted timestamps.  When set to site, the time zone associated to the tag’s site, will be used to convert the timestamp to utc for persistence.

timeStamp

string

yes

Timestamp for the samples in the post.  Can provide multiple timestamps/data points per payload.

tagId

string

yes

Aurora internal identifier for the data point.

value

string

yes

Actual value for the data point.

mean

string

Only when part of an aggregated sample

Average value for the data point over an interval.

min

string

Only when part of an aggregated sample

Minimum value for the data point over an interval.

max

string

Only when part of an aggregated sample

Maximum value for the data point over an interval.

median

string

Only when part of an aggregated sample

Median value for the data point over an interval.

stDev

string

Only when part of an aggregated sample

Standard deviation for the data point over the interval.

sampleSize

number

Only when part of an aggregated sample

Number of actual data points used to calculate the aggregated values over the interval.

quality

number

Only when part of an aggregated sample

If there were actual data points used to calculate the aggregated values, this should be set to 0.  If only estimated data points were used, then 1.

minTimeStamp

string

Only when part of an aggregated sample

The timestamp associated with the minimum value over the interval.

maxTimeStamp

string

Only when part of an aggregated sample

The timestamp associated with the maximum value over the interval.

 

Alarm Data Object GET Response Sample

{

    "TimeStampUtc": "2018-02-12T17:34:23.6502952Z",

    "AlarmData": [

        {

            "Id": "c7091524-54c5-43e2-b965-5de5e3317b61",

            "AlarmType": "dig",

            "Tag": "ConnectedToEmergency",

            "TagId": "2ff0b25e-b2e0-4da6-9627-05ac22146dab",

            "Description": "Connected To Emergency",

            "Value": "True",

            "CurrentValue": "False",

            "ValueFriendlyName": "Closed",

            "Status": "Cleared",

            "SiteId": "4b0cbbed-bb0d-4b9e-a2ab-f2d2f561f76c",

            "Site": "fake site",

            "BuildingId": "ebe8ca5c-1f92-4b00-a4b1-3ead85563efd",

            "Building": "Robertson Surgery Center",

            "FloorId": "011c855f-4c3a-4e54-9d2c-a84cf360cd1e",

            "Floor": "Ground",

            "RoomId": "30d977e6-4b96-42f8-8a8c-65d97bd39acd",

            "Room": "Outside",

            "EntityId": "9e86c496-c9c2-4f34-bd5c-d1c30cc0c880",

            "Entity": "Kep_ATS5",

            "Device": "GIM",

            "DateTimeInitiatedUtc": "02/06/2018 19:15:50",

            "DateTimeAcknowledgedUtc": "",

            "DateTimeClearedUtc": "02/06/2018 19:21:59",

            "UserAcknowledged": "",

            "Url": "/api/v1/alarms/c7091524-54c5-43e2-b965-5de5e3317b61"

        },

                                {

            "Id": "020f34bb-3560-4731-8005-1b9403f723ff",

            "AlarmType": "lo",

            "Tag": "FuelLevel",

            "TagId": "db73f43b-79c3-45a9-b981-74f74685e5ca",

            "Description": "",

            "Value": "500.000",

            "CurrentValue": "550",

            "ValueFriendlyName": "",

            "Status": "Unacknowledged",

            "SiteId": "",

            "Site": "",

            "BuildingId": "1afbff47-0ea8-4f14-8851-a34e5edfe7c1",

            "Building": "MSK Main Hospital",

            "FloorId": "96fc5236-52a7-4d81-96aa-c5c824dd315b",

            "Floor": "Ground",

            "RoomId": "6cb9f8a0-93be-4be1-8c95-ab1f07cc530a",

            "Room": "Outside",

            "EntityId": "a3c97491-4c7c-4375-86f3-b8345c72e7bd",

            "Entity": "Kep_Fuel1",

            "Device": "FIM",

            "DateTimeInitiatedUtc": "10/24/2017 15:40:19",

            "DateTimeAcknowledgedUtc": "",

            "DateTimeClearedUtc": "",

            "UserAcknowledged": "",

            "Url": "/api/v1/alarms/020f34bb-3560-4731-8005-1b9403f723ff"

        }

    ]

}

 

Alarm Data Object Definition

Field

Type

Definition

Id

string

Unique identifier for the alarm instance

AlarmType

string

Possible values:

sys,dig,hihi,hi,lolo,lo,run

 

sys – system

dig - digital

Tag

string

If the alarm is on a specific tag, this is the tag name, otherwise, empty string.

TagId

string

If the alarm is on a specific tag, this is the unique identifier for the tag.

Description

string

Description of the alarm.

Value

string

The value that triggered the alarm.

CurrentValue

string

The current value for the data point that triggered an alarm.

ValueFriendlyName

string

For alarms of type hihi, hi, lolo and lo.  Distinct friendly names can be configured for the alarms.

Status

string

Current state of the alarm.  Possible values are:

Cleared, Acknowledged, Unacknowledged

SiteId

string

If related to a site, this is the unique identifier for the site.

Site

string

If related to a site, this is the site name.

BuildingId

string

If related to an entity which is mapped to a building, this is the unique identifier for the building.

Building

string

If related to an entity which is mapped to a building, this is the name of the building.

FloorId

string

If related to an entity which is mapped to a floor, this is the unique identifier for the floor.

Floor

string

If related to an entity which is mapped to a floor, this is the name of the floor.

RoomId

string

If related to an entity which is mapped to a room, this is the unique identifier for the room.

Room

string

If related to an entity which is mapped to a room, this is the room name.

EntityId

string

If related to an entity, this is the unique identifier for the entity.

Entity

string

If related to an entity, this is the entity name.

Device

string

If related to a device, this is the device name.

DateTimeInitiatedUtc

string

DateTime the alarm was initiated in UTC.

DateTimeAcknowledgedUtc

string

If acknowleded, this is the datetime that the alarm was acknowleded in UTC.

DateTimeClearedUtc

string

If cleared, this is the datetime that the alarm cleared in UTC.

UserAcknowledged

string

If acknowledged by a user, this will contain the userid.

Url

string

url to retrieve the state of this alarm

 

Along with this change the AlarmHistory table in the History database was updated so that the Alarm ID does not change when the alarm is active, acknowledged, cleared or reactivated.  As a result, the alarm date time for active, acknowledged, cleared and reactivated will be displayed in the same row of the database table query list view.

Energy Apps

Energy Live and Historical Trending

The new Site Energy Live streams real time Total Site Energy kW one second data on a 10-minute chart.  Below the live streaming is Total Site Energy kW historical data that can viewed by the Last 12 Months, Last 30 Days, Last 7 Days and Last 24 hours.

To access this page, click on Energy on the Menu bar and then select Site Energy Live option.

The Energy menu option and associated sub-menus are removed from the Aurora Platform Menu header if the site has not configured any Energy tags for monitoring and reporting. 

To personalize the page the following is configurable:

  • Live minutes interval
  • Title color
  • Graph line color
  • Logo
  • Title Name
  • Live and Historical Tag that is charted

Note:  This feature is only available by request.  Please contact Customer Support or your Customer Success Manager to request this feature.

Live View

Hide/Unhide Live View Collateral

The Live View Designer now has the option to make entities on a Live View invisible.  So why would you want to make something on the Live View invisible?  Here is an example, when the Designer wants to show an entity’s associated live value or input/control value but does not want to see the entity on the canvas.  The Designer can configure the entity as invisible to obtain the desired look they are going for. 

In this view the entity is visible in design mode.

In this view the entity is invisible in design mode.  The entity is left in place as a watermark.

Once the Live View is displayed in run time mode then the entity invisible along with any connector lines to the bus bar.

Aurora Admin

Support Alert Notifications

The Aurora application has a critical alert for notifications when Kepware Runtime Service is down.  Prior to this release there was not a place within the Aurora Admin UI to manage which email address this alert should be delivered.  On new installs, the email address defaulted to support@bluepillar.com from the database configurator tool.  This email address is monitored by Customer Support but they are moving to monitoring two different email accounts based on the customer's service agreement.

Customer Support requested to have the application honor the Server Configuration Alert Notification field for the following alarms:

  • Alarm Processor errors
  • Control Manager errors
  • Integration Manager errors
  • Test Manager errors
  • Test State errors
  • Kepware Runtime Service errors

Customer Support is now able to enter the service agreement email address in the Email Address(es) field of the Alarm Logging Server Configuration screen in Admin.

For Managed Service Customer enter this monitored email address:  bpmanagedservice@bluepillar.com

For Basic Service Customer enter this monitored email address:  bpbasicservice@bluepillar.com

Avise

Live View

This information is for Customer Support, the Top Level Summary Live View in the legacy Avise application no longer displays systems.  The Platform Dev team has started to remove the old functionality by removing this feature first.  With each subsequent release we will see more features of the legacy Avise application being removed.

 

Technical

DevOps Tool

API Filter for 40+ Tags

Currently the User Interface for the API Filter Tag creation is limited to selecting only 40 tags.  If an API Filter needs to be created with more than 40 tags then contact Blue Pillar Customer Support and Blue Pillar will create the API Filter on your behalf using our DevOps Tools.  This is a temporary solution; Blue Pillar will develop the functionality soon so that the API Filter can be created through a User Interface on your own. 

Convert Live View Scada Grids to Name Value Pairs

In the Live View image below there are multiple data grids that provide equipment data.  Since our 5.8 release these grids are no longer available.  If the desire is to design a custom grid then the data grids can be converted to displaying just the equipment tag name and value and then moved into a new custom grid.

The conversion from the data grid to the tag/value display is done using our DevOps Tool by Customer Support.

In this view you can see the tag/value displayed not in a grid.

Custom Features

ABB API Integration

For the Aurora Vision (ABB) Solar Integration Blue Pillar has built the functionality to persist the solar data for an ABB Entity in the Historical Data API.  Blue Pillar persists minute, quarter hour, hour and day data for single or multiple tags to the Historical Data API.

How to create an ABB Entity in Aurora Admin:

  1. From the Admin | Server Config select Add Entity
  2. Enter the Entity name
  3. Select Custom for the Energy Device Type
  4. Select Custom for the Entity Type
  5. Select Kepware for the Tag Server and the application displays a Blue Pillar Device field
  6. Select ABB for the Blue Pillar Device field
  7. Click on the Save Entity button and the application displays the Device Configuration screen and creates an Entity Status and kWh tags

Admin Entity Configuration

Admin Entity Configuration 

  1. Enter the IP Address
  2. Click on the Save Device button
  3. Navigate to the Server Name in the left panel
  4. Click on the server name
  5. Click on the Download to Server button

Admin Entity Configuration

 

ALSO Energy API Integration

The Aurora Platform can retrieve inverter data from the ALSO Energy API and post it to Aurora Platform SQL Instances.  We make one API call per day to retrieve the 1-hour inverter data.

How to create an ALSO Energy Entity in Aurora Admin:

  1. From the Admin | Server Config select Add Entity
  2. Enter the Entity name
  3. Select Custom for the Energy Device Type
  4. Select Custom for the Entity Type
  5. Select Kepware for the Tag Server and the application displays a Blue Pillar Device field
  6. Select ALSO ENERGY for the Blue Pillar Device field
  7. Click on the Save Entity button and the application displays the Device Configuration screen and creates an Entity Status and kWh tags

Admin Entity Configuration

Admin Entity Configuration

  1. Enter the IP Address
  2. Click on the Save Device button
  3. Navigate to the Server Name in the left panel
  4. Click on the server name
  5. Click on the Download to Server button

Admin Entity Configuration  

Sunny WebBox API Integration

Blue Pillar has made some enhancements to the Sunny WebBox API Integration:

  • Added the functionality to update the Sunny WebBox Entity Status only when the status changes
  • Added the functionality to persist one-minute data to the Historical Data API
  • Added kWH tag to the Sunny WebBox Entity template
  • When the Sunny WebBox Integration is unable to post to the Aurora Platform then an error message is persisted to a log file
  • When the Sunny WebBox Integration is unable to reach the Sunny WebBox API then an error messages is persisted to a log file

How to create a Sunny WebBox Entity in Aurora Admin:

  1. From the Admin | Server Config select Add Entity
  2. Enter the Entity name
  3. Select Producer for the Energy Device Type
  4. Select BP Elect Equip for the Entity Type
  5. Select Kepware for the Tag Server and the application displays a Blue Pillar Device field
  6. Select Sunny Webbox for the Blue Pillar Device field
  7. Enter the Rated Current, Voltage and Rated kW fields
  8. Click on the Save Entity button and the application displays the Device Configuration screen and creates an Entity Status and kWh tags

Admin Entity Configuration  

Admin Entity Configuration

  1. Enter the IP Address
  2. Click on the Save Device button
  3. Navigate to the Server Name in the left panel
  4. Click on the server name
  5. Click on the Download to Server button

Admin Entity Configuration  

Customer Energy Report

Blue Pillar has created a custom monthly campus energy report available upon request.  This report is used for their overall energy efficiency and measurement/verification of energy projects/measures to monitor their progress towards their overall campus energy goals.

The report includes the following information:

  • From – To Date Time
  • Meter Name
  • Tad Id
  • kWh Value
  • kWh Period
  • kWh Average
  • kw Average Daily Maximum
  • kVa Maximum
  • kVA Average
  • kVARS Maximum
  • kVARS Average
  • PF Maximum
  • PF Average 

Bug Fixes

Work Item

Summary

Description of Bug

19321

Aurora Admin Gateway Config

Editing two separate Gateway devices prior to Save and Download was only changing the second device

19387

Aurora Admin Gateway Config

Errors were occurring when the microserver entities were configured as ElectricalEquipment/Consumer

20940

Time to Bus Reporting

Post Event processing generating wrong Time To Bus Report

21568

Aurora API

Aurora API was not Displaying All Fields on Filters Call

20746

Live View

In Live View Design Mode, the entity selection was required before placing a node on the bus bar

14658

Aurora Admin Building Config

In the Admin Building configuration, a building that was deleted couldn’t be added back in with the same name

20783

Classic Avise Reporting

Removed the classic Avise reporting from previous versions of the application that is no longer used

19374

Trending

System was setting incorrect Trending Data Intervals

19463

Test State

Error in large formula fields was causing TestState to fail on startup

20654

Secure RTU Devices

Prevent telnet sessions for non-Sixnet devices such as BacNet.

22948

Aurora Admin Device Config

Post creating a Fuel Tank the application was displaying a generic device configuration screen; the application has been fixed to display the Fuel Tank Device Configuration.

22953

Energy App

The Key Performance Indicator (KPIs) were only reporting on the default interval.  The application will now honor a selected interval.

21109

Live View Designer

An error was produced with the end user selected the utility source color selector.

21133

Live View Designer

When there were multiple ATSs connected to a bus bar to a single Utility Source, if the User tries to select a general equipment breaker, the call stack is exceeded because there are too many connections to track and the system displays an error message.

21137

Live View Designer

When multiple general breakers were selected the horizontal and vertical align options were unavailable

22492

Gateway Configuration

In the Runtime COMM_ALARM ReadFormula Generated Incorrectly for non-GIM1 Devices.

20615

Fuel Tank Display

When more than one fuel tank exists for a fuel system the application was displaying an incorrect value for the tank capacity.

 

Hotfixes

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

Build

Hotfix Date

Summary

Description of Hotfix

5.9.0037.001

02/06/2018

Sunny WebBox Integration needs to support multiple platform endpoints

Upgrade the Sunny WebBox so that it supports multiple Aurora endpoints.

5.9.0059.001

02/28/2018

API Config File is overwritten on installs for an off-server database

When the application is installed on a off-server database, the installer was overwriting the API Config File.  As a result, the API Service was not starting.

5.9.0096.001

04/09/2018

Unable to add camera to a microserver device

Cameras can now be added to microserver devices in the Device Config

 5.9.0096.001

 04/09/2018

Multi-site Map View was locking up in IE

The correct Google API has been added to correct this issue

5.9.0096.001  04/09/2018 

Trending Data Intervals

Made a changed to only display data intervals that are available for the time period specified for trending data

5.9.0096.001  04/09/2018 

Trending Data Rollups

The data rollups in trending were stuck on Actual for trending time periods. 

5.9.0096.001  04/09/2018 

Trending on External Integrated API data

The Sample Size value was being set to 0 for the data passed in through the API.  The 0 was preventing the tag data from rolling up.

 When external integration API data is inserted into the tables then the seconds data is stripped before inserted so that the data can be reported and trended on.

5.9.0096.001 04/09/2018

Telemetry Data Cleanup

The Telemetry Data Cleanup has been fixes to deletes data from the new extension tables so that the tables won’t exceed their limit.

5.9.0115.001 05/01/2018

Custom Entity Config

With the implementation of the external integration the application was requiring the Blue Pillar Device Type to be required but not all custom entities need a device type so NA was added to the list.

5.9.0115.001 05/01/2018

Unable to Login

The default buffer in the WCF Server binding was increased from the default 65555536 to the max for int32, 2147483647 so that it can handle more data on the server.

5.9.0157.001 06/11/2018

Trending Save Tag Selection

Fixed the refresh issue that made it appear that the application was not honoring the trending save tag selection.

5.9.0164.001 06/14/2018

Live View Designer

In some instances, upon entering the Live View in Design Mode the canvas was shifting up and the items at the top of the canvas fall behind the Live View ribbon.  This has been corrected so that the canvas does not fall behind the ribbon in design mode.

5.9.0164.001 06/14/2018

Live View Designer

Fixed the scroll bar in the foreground and background image selector.

5.9.0165.001 06/15/2018 Live View Alarms Custom entities on a custom Live View were missing the alarm indicator when they had active and inactive/unacknowledged alarms.
5.9.0166.001 06/18/2018 Veris_Both Tag being set to incorrect setpoint Modified the enablemetermonitoring method to exclude entities with a tagserver of 'microserver' or include entities without a tagserver attribute at all or tagserver = 'kepware'.

Fields will be blank until there is a hotfix that took place. 

Hardware and System Requirements

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
    • Supported and Tested Operating Systems
  • Microsoft Client Operating Systems
    • Browsers demonstrating considerable compatibility
  • Microsoft Edge
  • Mozilla Firefox
  • Google Chrome 32 or higher

 

Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.
Powered by Zendesk