ASPEN Enterprise Module

Introduction

ASPEN Enterprise Module (EDX) is an add-on module for the ASPEN OneLiner program. It consists of centralized storage for OneLiner short-circuit-model data and relay-setting and user-defined data, plus a Web API server that facilitates access and update of the data by ASPEN and third-party applications.

The EDX will enable ASPEN OneLiner users to continue running engineering studies using the traditional desktop app with GUI while having access to a shared source of network and relay settings data. Users will also be able to create API-based data connectors in the EDX to exchange data with their enterprise-wide systems on their network. The EDX’s built-in data change monitoring, notification and propagation framework will allow users to keep the study cases in the EDX synchronized with changes in other EDX tables and external data sources as desired.

Only ASPEN OneLiner users with OneLiner version 15 or later will be able to acquire a license to install and use the EDX.

EDX users who had already purchased licenses for the ASPEN Relay Database and/or the ASPEN Line Database will be able to merge their existing data tables into the EDX. The ASPEN Relay Database and Line Database programs will continue to operate normally in the merged database. Having all the data in single storage will allow users to leverage the EDX software’s data management capabilities to keep their OneLiner cases in sync with updates in the Relay Database and/or Line Database in both directions. 

Users will be able to create their own data table(s) in the EDX and make use of the EDX software’s data management capabilities to keep their OneLiner cases in sync with updates in these data tables.

Architecture

The EDX module consists of the following main components (See also pictures in the next page):

  1. A central database hosted on a Oracle or MS SQL database server provided by the user.
  2. [Optional] EDX Web API server software: Windows server application to enable EDX operations through Web API.
  3. EDX desktop client software: Windows desktop applications that allow EDX operations from Windows desktop PCs with client/server connection to Oracle or MS Sql database servers:
    1. OneLiner V15 program: ASPEN fault study and relay coordination software with built-in EDX client.
    2. The EDX DashBoard program (Included with the EDX software package): EDX apps launcher with built-in graphical browser for OneLiner cases and various user-defined data tables and the EDX admin tool. The DashBoard can also launch user-developed and third party EDX applications that are built on top of EDXAPI.DLL included with the EDX software package.
    3. [Optional] Third party applications that are built on top of the EDXAPI.DLL.
  4. EDX web client software: ASPEN and third party applications that make use of the Web API server for EDX operations

A typical application

Each user of OneLiner receives from the EDX Administrator a login credential with a set of privileges that controls what network objects he/she is allowed to view, add, modify, change and delete.  The privileges can be assigned by location, kV levels or bus number ranges. For example, protection engineers in a regional office can be restricted to change only the network and relays in their local area. 

A user who wants to perform a study in OneLiner has to first login to the EDX and retrieve to his/her PC an OneLiner file (.olrx) for the desired study date and configuration. The EDX will assign an globally unique identifier to each of these OLRX files. OneLiner will show this identifier in all program fault solutions and relay coordination checking reports.  With the identifier, the user will always be able to retrieve the very same file from the EDX when needed at a later time.

When a user checks in an OLRX file with his/her modification and corresponding study reports to the EDX, they are always stored in a holding area.  The changes are committed into the EDX tables only after review and approval by a supervisor or peer.  A submit-review-approval workflow can be customized by the EDX administrator using a scripting language.

The DBX will maintain a detailed journal of all changes made in network model and relay data in all OLRX cases that users check in.  Each journal entry will include a time-stamp, the user name, the “before” and “after” values, as well as user description, justification, and references for the changes.

Configuration and Integration

One-time user-specific undertakings:

  • Data model analysis and optimization: Design and establish a set of OneLiner cases that allow optimal case update propagation workflow.
  • Initial data transfer, import and validation.
  • Development of data connectors and mapping scripts to other existing network and relay data providers.
  • Customization and development of query and reports per user requirements.
  • Customization and development of workflow trigger logics: check-out, check-in, approval etc. per user requirements

Development of EDX Extensions and Apps that make use of EDX APIs for network and relay data access. Example are:

  • Model data analysis and presentation applications. 
  • Automatic relay settings and coordination applications. 
  • PRC compliance tools.