Getting Started
The Oracle Utilities Live Energy Connect (LEC) Asset ID Manager (AIM) is designed to automate and maintain the alignment of an organization’s Supervisory Control and Data Acquisition (SCADA) or Energy Management System (EMS) system configurations, LEC Server configurations, and Oracle Utilities Network Management System (NMS) or CGI’s PragmaLINE Outage Management System (OMS) system configurations. The following are some tasks LEC AIM can automate:
- Generating LEC Server batch files from points configured on a SCADA system or EMS
- Loading LEC Server batch files into the LEC Server remotely
- Mapping the points in these batch files to NMS devices and device attributes or CGI OMS devices and device attributes
- Loading the resolve mappings into an NMS configuration or a CGI OMS configuration
After the LEC AIM application synchronizes the NMS or CGI OMS, and LEC Server configurations, the updated LEC Server will connect to NMS or CGI OMS and to the SCADA or EMS. Once these connections are made, the system communicates data in real-time without further interaction from the LEC AIM application until new point information needs to be updated on one of the systems.
About LEC Asset ID Manager
LEC Asset ID Manager (AIM) interacts with a SCADA or EMS system, an LEC Server, and an NMS or CGI OMS system. The following sections explain how these different systems typically communicate and the steps the LEC AIM application takes to keep their configurations aligned.
LEC Asset ID Manager and LEC Server
LEC AIM creates LEC Server batch files based on available points configured on a SCADA or EMS system. LEC Server batch files are text files in a CSV format that describe the points on the remote system and their dataflow through the LEC Server. LEC AIM can also load batch files remotely into the LEC Server. A user can start, stop, and debug the generated LEC Server configuration using the LEC Configuration Manager (LCM) GUI application.
LEC Asset ID Manager and NMS or CGI OMS
LEC AIM maps available points on SCADA (or EMS) to LEC Server to NMS (or CGI OMS) devices and device attributes.
LEC Asset ID Manager’s Interaction with Other Systems
LEC AIM typically interacts with software systems on three different machines and uses various communications protocols:
- LEC AIM runs on the same machine on which the NMS (or CGI OMS) is installed.
- LEC Server runs on a separate Windows Server 2016 or 2019 machine.
- The SCADA (or EMS) runs on any number of additional separate machines depending on an organization’s OT architecture.
Each customer’s use of LEC AIM may vary depending on the architecture of their OT system and the configuration of their LEC Server. The figure below shows a typical relationship between these systems and the communication protocols used between them and the LEC AIM application.
Purpose of LEC Asset ID Manager
The purpose of LEC Asset ID Manager (AIM) is to:
- automate the creation of LEC Server batch files from points configured on a SCADA (or EMS) system.
- load the prepared batch files into an LEC Server instance.
- map NMS (or CGI OMS) devices and device attributes to points configured on a SCADA (or EMS) system.
- update the NMS (or CGI OMS) configurations.
This allows the NMS (or CGI OMS) system to receive real-time data from points on the SCADA (or EMS) system by way of the LEC Server.
Once all of the mapping between the SCADA (or EMS) system and the NMS (or CGI OMS) system is configured, the LEC Server transmits the real-time data to the NMS (or CGI’s OMS) system typically using the LEC RTP protocol. In some customer configurations real-time data may be sent to and from the LEC server using other protocols and methods.
After an initial mapping, the LEC AIM application only needs to be run when either the SCADA (or EMS) or the NMS (or CGI OMS) configurations are updated or changed.
Customers have a choice to run the AIM application’s processes manually through a command-line user interface or to automate the processes.