US20150378420A1

US20150378420A1 - Universal performance monitor for power generators

Info

Publication number: US20150378420A1
Application number: US14/605,629
Authority: US
Inventors: David IPPOLITO; David Kucharczuk
Original assignee: Versify Solutions Inc
Current assignee: Versify Solutions Inc
Priority date: 2008-03-07
Filing date: 2015-01-26
Publication date: 2015-12-31
Also published as: US20190171275A1; US8965719B1

Abstract

The invention broadly encompasses a system including a communications network, a plurality of remotely located data sources to provide power data, the power data including quantitative and qualitative data of one or more power generation units, and a performance monitor in communication with the plurality of remotely located data sources through the communications network, the performance monitor including a communications unit to extract the power data from the plurality of remotely located data sources, a data conversion unit to transform the power data into a common data format, a data store to store the transformed power data, and a user interface unit to display the transformed power data on one or more client devices through the communications network.

Description

This application is a continuation application of copending U.S. application Ser. No. 12/399,689, filed on Mar. 6, 2009, which claims the benefit of U.S. provisional patent application No. 61/034,912, which was filed on Mar. 7, 2008, both of which are hereby incorporated by reference in their entirety.

I. FIELD OF THE INVENTION

The invention encompasses a performance monitor for power generators, and more particularly to a performance monitor for power generators that is adaptable to handle data from any data source.

II. BACKGROUND OF THE INVENTION

The power industry has been rapidly changing with the advent of deregulation as well as other socio-economic factors. As a result, increases in efficiency and control of power generation costs are becoming of more importance. To meet the industry needs, a large number of siloed information technology (IT) applications have been introduced. However, these applications are typically not built with integration in mind with each application being too proprietary in nature and specifically tailored for a particular power generation operation. Accordingly, collection and integration of data from these applications and systems are extremely difficult outside of the intended operation. Many utilities have sought to create a large scale data warehouse to solve this integration problem with very little success.
Another difficulty with prior art systems is the disparate number of locations even within the organization that needs access to the data. For example, within a power company, traders on a central trade floor, plant personnel at each power plant, engineers stationed regionally, management dispersed throughout the organization, and third parties all need access to the data in some form. The traditional siloed applications are typically client-server based applications and it is difficult to provide access to everyone in need of the data.
In addition, due to the generally isolated nature of the prior art systems as described above, combining qualitative event type data (e.g., real-time or recorded plant operations data) and quantitative data (e.g., Supervisory Control and Data Acquisition (SCADA) and market data) becomes difficult and cumbersome, if not impossible, due to the size and disparity of the data. On the other hand, such information is important in determining proper operation of power generation as back office settlement activities determine penalties associated with under or over production of power, for example. Typically, back office personnel manually extract data from a number of different IT systems in the organization to determine the activities that occurred in prior reporting periods. Many times, logs maintained in word processing or hand written documents must be searched manually.
Moreover, when a type of report is required, IT developers have to develop some level of custom code to extract data from the data and format the data properly onto a report. This task becomes even more complicated when disparate data sources with varying data formats are used.

III. SUMMARY OF THE INVENTION

Accordingly, the invention encompasses a system and method for monitoring power generation operations that substantially overcomes the limitations and disadvantages of the related art.
In one embodiment, the invention encompasses a system and method for collecting power generation operation data from disparate data sources and generating a report of the performance of the operation.
Additional features and advantages of the invention will be set forth in the description which follows, and in part will be apparent from the description, or may be learned by practice of the invention. The objectives and other advantages of the invention will be realized and attained by the structure particularly pointed out in the written description and claims hereof as well as the appended drawings.
To achieve these and other advantages and in accordance with the purpose of the invention, as embodied and broadly described, a system encompasses a communications network, a plurality of remotely located data sources to provide power data, the power data including quantitative and qualitative data of one or more power generation units, and a performance monitor in communication with the plurality of remotely located data sources through the communications network, the performance monitor including a communications unit to extract the power data from the plurality of remotely located data sources, a data conversion unit to transform the power data into a common data format, a data store to store the transformed power data, and a user interface unit to display the transformed power data on one or more client devices through the communications network.
In one embodiment, the invention encompasses methods of communicating with a plurality of remotely located data sources from a performance monitor via a communications network, the plurality of remotely located data sources providing power data including quantitative and qualitative data of one or more power generation units, extracting the power data from the plurality of remotely located data sources, transforming the extracted power data into a common data format, storing the transformed power data in a data store, and displaying the transformed power data on one or more client devices through the communications network.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory and are intended to provide further explanation of the invention as claimed.

IV. BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are included to provide a further understanding of the invention and are incorporated in and constitute a part of this specification, illustrate embodiments of the invention and together with the description serve to explain the principles of the invention. In the drawings:

FIG. 1 describes a block diagram illustrating an overall system architecture of an exemplary embodiment of the present invention;

FIG. 2 shows a block diagram illustrating an exemplary embodiment of a communication interface architecture of the present invention;

FIG. 3 is an example of a config file in accordance with the present invention;

FIG. 4 shows a block diagram illustrating an exemplary embodiment of generating a report interface in accordance with the present invention;

FIGS. 5A-5K show exemplary embodiments of a dashboard report interface in accordance with the present invention;

FIGS. 6A and 6B show exemplary embodiments of a daily report interface in accordance with the present invention;

FIGS. 7A and 7B show exemplary embodiments of a unit performance report interface in accordance with the present invention;

FIG. 8 illustrates an exemplary unit interface in accordance with the present invention;

FIG. 9 illustrates an exemplary unit attribute interface in accordance with the present invention;

FIG. 10 illustrates an exemplary event log interface in accordance with the present invention; and

FIGS. 11A and 11B illustrate an exemplary real time monitor in accordance with the present invention.

V. DETAILED DESCRIPTION OF THE INVENTION

General Description

The invention generally encompasses systems including:
a communications network;
a plurality of remotely located data sources to provide power data, the power data including quantitative and qualitative data of one or more power generation units; and
a performance monitor in communication with the plurality of remotely located data sources through the communications network, the performance monitor including
a communications unit to extract the power data from the plurality of remotely located data sources,
a data conversion unit to transform the power data into a common data format,
a data store to store the transformed power data, and
a user interface unit to display the transformed power data on one or more client devices through the communications network.
In certain illustrative embodiments, the quantitative data includes supervisory control and data acquisition (SCADA) data and/or market data.
In certain illustrative embodiments, the quantitative data includes operational cost data of the one or more power generation units.
In certain illustrative embodiments, the qualitative data includes event log data of the one or more power generation units.
In certain illustrative embodiments, the communications unit includes a gateway application programming interface (API) unit to pull the power data from the plurality of remotely located data sources.
In certain illustrative embodiments, the conversion unit includes an interface API unit to communicate with the gateway API unit and to transform the power data into the common data format.
In certain illustrative embodiments, the user interface unit includes an alarm unit to issue and track alarms based on user-defined events.
In certain illustrative embodiments, the user interface unit includes a reporting unit to display interactive reports on the one or more client devices.
In certain illustrative embodiments, the reporting unit includes any one of a dashboard reporting interface, daily operational reporting interface, unit performance interface, ad-hoc SCADA query interface, and unit status communications interface.
In certain illustrative embodiments, the user interface unit includes a library of extensible markup language (XML) configuration files, each XML configuration file being associated with a corresponding one of the interactive reports to map the power data stored in the data store directly to the corresponding interactive report for display on the one or more client devices.
In other embodiments the invention encompasses computer-implemented methods including
communicating with a plurality of remotely located data sources from a performance monitor via a communications network, the plurality of remotely located data sources providing power data including quantitative and qualitative data of one or more power generation units;
extracting the power data from the plurality of remotely located data sources;
transforming the extracted power data into a common data format;
storing the transformed power data in a data store; and
displaying the transformed power data on one or more client devices through the communications network.
In certain illustrative embodiments, the quantitative data includes supervisory control and data acquisition (SCADA) data and/or market data.
In certain illustrative embodiments, the quantitative data includes operational cost data of the one or more power generation units.
In certain illustrative embodiments, the qualitative data includes event log data of the one or more power generation units.
In certain illustrative embodiments, the step of extracting the power data from the remotely located data sources include pulling the power data from the plurality of remotely located data sources via a gateway application programming interface (API) unit.
In certain embodiments, the step of transforming the power data includes converting the power data into the common data format via an interface API unit.
In certain illustrative embodiments, the step of displaying includes issuing and tracking alarms based on user-defined events.
In certain illustrative embodiments, the step of displaying includes displaying interactive reports on the one or more client devices.
In certain illustrative embodiments, the interactive reports are displayed on any one of a dashboard reporting interface, daily operational reporting interface, unit performance interface, ad-hoc SCADA query interface, and unit status communications interface.
In certain illustrative embodiments, the step of displaying includes configuring the interactive reports via a library of extensible markup language (XML) configuration files, each XML configuration file being associated with a corresponding one of the interactive reports to map the power data stored in the data store directly to the corresponding interactive report for display on the one or more client devices.
In another embodiment, the invention encompasses a computer-readable storage medium, storing one or more programs configured for execution by one or more processors, the one or more programs comprising instructions to:
communicate with a plurality of remotely located data sources from a performance monitor via a communications network, the plurality of remotely located data sources providing power data including quantitative and qualitative data of one or more power generation units;
extract the power data from the plurality of remotely located data sources;
transform the extracted power data into a common data format;
store the transformed power data in a data store; and
display the transformed power data on one or more client devices through the communications network.
Reference will now be made in detail to the embodiments of the present invention, examples of which are illustrated in the accompanying drawings.
The system and method of the present invention is a flexible solution both in terms of the type and amount of data processed and in terms of monitoring and reporting to the above-identified problems of the prior art. In general, the system and method of the present invention is a hosting asset performance monitoring and reporting tool used by owners or power generators, such as independently owned utilities, municipalities, and cooperatives, for example. It is to be understood that other users and benefits may be realized without departing from the scope of the invention. The system and method of the present invention provides, for example, dashboard reporting (e.g., for management-level), summary/drill-down reporting (e.g., back office processing), daily operational reporting (e.g., operations), query interface for plant supervisory control and data acquisition (SCADA) information on ad-hoc basis, and near real-time status and logging capabilities. Accordingly, the system and method of the present invention provides, for example, logged information created by automated plant monitoring systems and/or plant personnel as events occur with relative SCADA and market information. The details of the system and method of the present invention is described below.
FIG. 1 shows a block diagram illustrating an overall system architecture of an exemplary embodiment of the present invention. As shown in FIG. 1, the system of the present invention includes a hosting monitoring center 10 in communication with a plurality of remotely located disparate data sources 20 over a communications network 30. The communications network may be any data communications network, such as point-to-point connections, local area networks (LAN), wide area networks (WAN), Internet, etc. and may be over a wired or wireless communication medium. The remotely located disparate data sources 20 provide qualitative information (e.g., events type data) and quantitative information (e.g., market data) related to a hosted power generating unit. For example, as shown in FIG. 1, the hosting monitoring center 10 may be in communication with a hosted power plant 20 a and SCADA data center 20 b. SCADA data center 20 b may be any data source that archives time-series SCADA or telemetry data of a power generator, also sometimes referred to as SCADA historian, such as megawatts produced, fuel consumption, etc. Generally, SCADA data center 20 b collects SCADA information from a plurality of power generations located within a defined region. However, any SCADA data source may be used without departing from the scope of the present invention. The hosted power plant 20 a provides internal operations data of the power plant, such as operational event logs, the amount of power being generated, operational cost information (including unit design and budget data), etc. “Budget” data, as used herein, includes financial/cost expectations as well as operational expectations, such as expected hours of operation, expected number of starting the generators over a projected time frame, how much power is expected to be generated, etc. It is to be understood that the data provided by the hosted power plant 20 a may overlap with the information provided by the SCADA data center 20 b and may be used independently of, or in conjunction with, each other. Other remote data sources may include market and financial information data services (not shown) that provide historic and real-time market information to the monitoring center 10.
The hosting monitoring center 10 includes power data server 12, market data server 14, and web server 16. It is to be understood that these servers may be implemented in a single machine or a plurality of machines without departing from the scope of the invention. The power data server 12 and market data server 14 are configured to obtain data from any number of the disparate data sources 20. The data sources 20 may be databases from hosted or unhosted systems, such as independent system operators (ISOs), regional system operators (RSOs), and SCADA data centers, for example. The data may also be obtained from internal data sources of hosted and unhosted system, such as data from internal databases, spreadsheets, and other software packages. The power data may, in some embodiments, include market-type data such as, for example, power pricing, fuel pricing, or the like. The power data server 12 and market data server 14 convert the collected data into a common format and store the transformed data in data store 18. The data store 18 may be a single or a plurality of data storage devices and may be implemented as a direct data repository or a relational database. Other data store configurations may be used without departing from the scope of the present invention. The web server 16 communicates with client devices 40 to provide monitoring functionality to the users. Client devices 40 may be workstations, notebooks, digital personal assistants, and other data-enabled devices. The web server 16 processes the requests from the client devices 40 and provides the requested information via reports and alarms to be described further below.
In an exemplary embodiment of the present invention, the web server 16 communicates with the client devices 40 via web-based applications. In the exemplary embodiment, the client devices 40 only need a web browser and do not require any specialized applications. The web server 16 includes a proprietary XML-HTTP callback architecture to initiate requests from a browser from the client device 40, for example, back to the web server 16.
FIG. 2 shows a block diagram illustrating an exemplary embodiment of a communication interface architecture of the present invention. As shown in FIG. 2, the system and method of the present invention extract data from any number of disparate data sources 20 using a combination of web services and SQL server integration services. For example, the interface architecture in accordance with the exemplary embodiment of the present invention includes hosted Gateway API web service located behind the hosted system's firewalls, Hosting Interface API web service located behind the firewall of the web server 16 that communicates with the hosted Gateway API, and SQL server integration services that communicate with the interface web service, located on the data servers 12 and 14. It is to be understood that locations of the services and additional services may be used without departing from the scope of the invention.
The Gateway API in accordance with the exemplary embodiment of the present invention extracts data from the hosted system's internal applications. The Gateway API accesses known APIs of other commercial software systems and databases as well as any custom code needed to pull data from the hosted system's internal proprietary applications. In an exemplary embodiment, the Gateway API extracts data and returns the data to the web service client as either a ADO DataSet, XML document, byte array, string, or other similar data types.
The Hosting Interface API in accordance with the exemplary embodiment of the present invention provides the ability to communicate with the Gateway API and contains interface logic to transform data into a common data format. The Hosting Interface API, for example, pulls hourly, snapshot, and market data into the data store 18. The Hosting Interface API also generates log events from SCADA information.
The SQL server integration services in accordance with the exemplary embodiment of the present invention drive the communication interfaces. The SQL server integration services utilize mapping data to execute, monitor, and report on scheduled interfaces for each hosted system. In accordance with the exemplary embodiment of the present invention, the SQL server integration services include “retry” logic to ensure that data is not missed due to any sort of system failure.
Once the qualitative and quantitative information of the hosted power generating unit (e.g., power plant 20 a) is available, the web server 16 of the hosting monitoring center 10 provides customized reports to the client devices 40 through report interfaces implemented on the web server 16. The report interfaces in accordance with an exemplary embodiment of the present invention are built from a customizable library of report interfaces. The report interfaces of the present invention are customized using extensible markup language (XML)-based “config files” that contain information about what data to extract and how to format the data on a report interface. Accordingly, the XML config files in accordance with the present invention combine data from any number of disparate systems into a comprehensive report. The XML config files of the present invention simply map data from the data store 18 directly to a report interface without requiring any customized code.
An exemplary embodiment of the present invention includes page config files and reports config files. The page config file, as shown in FIG. 3, includes XML that may direct the page to change any property of the page itself, or any property of any control on the page. This allows the user interface to be changed without writing any code and increases maintainability across multiple client devices 40. For example, when the page initially loads, the browser automatically looks for a page config file. If a page config file is found, the browser processes the XML for the page contained in the page config file. Each page or control property identified in the XML is then set based on the page config file setting. To illustrate, a button on the page may be hidden by setting the visible property of the button equal to hidden. Furthermore, properties have been created on certain pages such as a unit status report interface, to be explained below, that allow customization of entire sections of the page through the use of custom user controls. In addition, a config file may define standard .NET framework user controls that make-up a page. A particular user control may be overridden for one or more user or customer locations (e.g., power stations or generators) via the config file. In some embodiments, a class (e.g., basePage) invoked because of a load page event may process the config file, change page properties, and override user controls. In the case scenario where a user control is overridden, a new user control may be loaded and a local variable may be set accordingly.
The reports config file defines the layout of a report interface using XML included in the reports config file. The reports config file includes XML fragments for each object to be displayed on the report interface (e.g., graph, pie chart, data table, etc.) The XML fragment includes information specific to the object being shown (e.g., location on report, height, width, colors, etc.) as well as mapping information back to the data store 18 as to what data should be displayed. There may be mappings to multiple stored procedures defined for a single report object. For example, a chart may pull hourly megawatt (MW) data from one stored procedure and hourly price information from another in conjunction with a reporting engine to be described below. In an exemplary embodiment, reports config files may be defined for a single report but have different configurations depending on what hosted system (e.g., power plant) the report is for. For example, each reports config file may have a “default” configuration defined. For any hosted system (e.g., power plant) or unit (e.g., generators) referred to as “locations,” where the report is to have a different look and feel and/or different data source, a subsequent “override” XML fragment is defined for the location. Any location that does not have the override fragment reverts to the default layout.
FIG. 4 shows a block diagram illustrating an exemplary embodiment of generating a report interface in accordance with the present invention. A reporting engine 410 processes the page config file 420 and reports config file 430, executes the stored procedures identified 440, and creates and formats the report objects on a report interface 450. The reporting engine 410 returns an HTML div containing the formatted report. The reporting engine 410 loads the reports config file 430 and identifies all of the stored procedures to call using an XPATH query. Once the reporting engine 410 has gathered a list of stored procedures, the reporting engine 410 executes each one, via a data access layer. By executing all stored procedures once and holding them in memory for report processing, extraneous database calls are eliminated to optimize performance. Each result set returned is stored in memory for the remainder of the report processing. The reporting engine then iterates through the report objects to build the actual report interface 450. Object classes are defined for each possible report object (e.g., chart, pie chart, gauge, thermometer, note, table, etc.). The object classes include logic to generate HTML and format data appropriately for each type of report object. For each report object, the reporting engine 410 creates an instance of the class and initializes the object generating basic HTML required. The reporting engine 410 then iterates through each mapped data item to be illustrated in the report object and passes the data item to the class from the appropriate result set extracted from the database earlier. The class processes the data into HTML (or XML) for the report item and finally returns the completely formatted HTML, which is then inserted into the HTML div tags.
In an exemplary embodiment of the present invention, the report interface 450 is categorized as one of the following: dashboard report interface, daily operational report interface, quantitative summary/drill-down report interface (also referred to as “unit performance” interface), an ad-hoc SCADA query interface, and unit status communication interface.
FIGS. 5A-5K show exemplary embodiments of the dashboard report interface. The dashboards page allows users to select any configured dashboard for any power plant within the data store 18. FIGS. 5A-5K show exemplary embodiments of the following dashboards, respectively: Operations, Megawatts (MW), Availability, Budget, Cost/Revenue, MTD Portfolio Summary, YTD Portfolio Summary, Fuel Trading Summary, Power Trading Summary, Spark Spread Summary, and Financial Option Summary. It is understood that other dashboard interfaces may be included without departing from the scope of the present invention. In the exemplary embodiment, each dashboard is run for a selected month. However, other time ranges may be used without departing from the scope of the invention. For example, the user may select a power plant (i.e., location) and a month out of a year, and refresh the report. An XML-HTTP callback is made from the browser on the client device 40 to the web server 16. The web server 16 receives the XML-HTTP request and creates an instance of the reporting engine 410 described above. The reporting engine 410 builds the report interface 450 as described above, which may be an HTML div with report objects in it. The div is returned to the browser on the client device 40 that initiated the XML-HTTP call. The client device 40 refreshes the page on the screen with the newly created report. As shown in FIGS. 5A-5K, the dashboard interface includes a combination of report objects, such as gauges, bar graphs, line graphs, pie charts, and tables to provide an overall performance view of the selected location by integrating the qualitative and quantitative data obtained from the disparate data sources 20, converted into a common format, and stored in the data store 18. The report object may be animated as the information is provided to show movement of the various gauges, bar graphs, line graphs, pie charts, and other graphical representations.
FIGS. 6A and 6B show exemplary embodiments of the daily report interface. The daily reports page allows a user to select a configured daily report. FIGS. 6A and 6B show the Daily Summary and Trading Summary, respectively. Other daily reports may include Day Forecasted Availability and Daily Log. It is to be understood that other daily summary reports may be included without departing from the scope of the invention. For example, the user selects a power plant (i.e., location), a reporting day, and refreshes report. An XML-HTTP callback is made from the browser of the client device 40 to the web server 16. The web server 16 receives the XML-HTTP Request and creates an instance of the reporting engine 410 described above. The reporting engine 410 builds the report as described above, which may be an HTML div with report objects in it. The div is returned to the browser on the client device 40 that initiated the XML-HTTP call. The client device 40 refreshes the page on the screen with the newly created report. The daily report interface provides a summary of daily operational and financial activities of the selected location by integrating the qualitative and quantitative data obtained from the disparate data sources 20, converted into a common format, and stored in the data store 18.
FIGS. 7A and 7B show exemplary embodiments of the unit performance report interface. The unit performance report interface includes quantitative reports for daily, weekly, and monthly time horizon, for example. In addition, the unit performance report interface includes drill down capability so that hourly detail report data may also be retrieved. In the exemplary embodiment, the unit performance report interface includes the following reports: Operating Summary, Availability Summary, Actual Plant Dispatch, Actual Plant Usage, Budgeted v. Actual Dispatch, Budgeted Plant Usage, Operational Decisions, Trading Decisions, Outage Decisions, Gas Balance, and Trade Summary. It is understood that other summaries may be included without departing from the scope of the invention. In the exemplary embodiment, the unit performance report interface and the items displayed are maintained in an XML fragment in the unit performance page's reports config file 430. For example, a user selects a report, a time frame, and a time horizon to initiate the report. The browser of the client device 40 initiates a callback to the web server 16, which in turn calls a stored procedure 440. The stored procedure includes logic to summarize the data to the selected level (daily, weekly, monthly). When the result set is returned to the web server 16, the page is correctly formatted with the data into a table with the correct number of columns (e.g., based on daily, weekly, or monthly) and returns the table to the browser on the client device 40. As shown in FIG. 7B, the unit performance page also includes drill down capability to drill down into a finer granularity (e.g., hourly details). Database mapping tables are used to map summary items on the main page to the hourly detail. When a user clicks on a cell on the main report, the browser on the client device 40 initiates a callback. The callback request is received by the web server 16, and a stored procedure 440 is executed to retrieve mapped detail from the data store 18. The mapped detail is returned to the client device 40 as a table, for example.
FIGS. 8-11B show exemplary embodiments of ad-hoc SCADA query interface and unit status communication interface in accordance with the present invention. For example, FIG. 8 illustrates an exemplary unit interface that displays operational information of a selected unit. The information may include current status 805, operational statistics 810, schedules 815, event logs for the unit 820, and market data 825. The information may be displayed for a selected date. It is to be understood that other information regarding the selected unit may be included without departing from the scope of the invention.
FIG. 9 illustrates an exemplary unit attribute interface that displays a summary of the operational attributes based on region 905, control area 910, unit 915, and date range 920, for example. Other criteria, such as type 925, season 930, and attribute 935 may be selected for viewing.
FIG. 10 illustrates an exemplary event log interface for a selected unit. The event log may be sorted based on event type 1005 and date range 1010, for example. In an exemplary embodiment, the event types may include, but not limited to: Actual Shutdown, Actual Start, Derate (max cap change), General Note, Schedule Change, Schedule Test, Schedule Update, Trip (max cap change), and Workorder Impacting Operations.
FIGS. 11A and 11B illustrate an exemplary (near) real time monitor for a selected unit. In an exemplary embodiment, the operational data of a hosted power plant is updated every three (3) minutes. However, the period for update may be changed without departing from the scope of the present invention. The monitor may be selected based on region, control area, unit, and technology. Technology criteria may include, but is not limited to, BWR, CCGT Gas, CCGT Steam, Diesel, Fluidized Bed, Combustion, Fossil Steam, Gas Turbine, Geothermal, Hydro, Jet, Pumped Storage, PWR, and Wind Turbine. As shown in FIG. 11B, the real time monitor includes a pull-out to provide graphical representation of the monitored parameters, such as megawatt (MW), heat rate, and emissions. Other parameters may be included without departing from the scope of the present invention.
In addition to the real time monitoring, the system and method of the present invention includes alarm monitoring and tracking of user-defined significant events. For example, the monitoring center 10 of the present invention tracks and logs when a hosted unit comes on-line or goes off-line. The monitoring center 10 tracks alarms against any generation operational parameter that is archived in the time-series data store 18. This is implemented by querying the time-series historical data store 18 for values archived for a selected operational parameter over a set time interval. For example, for a generator unit on-line alarm, the monitoring center 10 queries the historical archive in the data store 18 for a fifteen (15) minute interval and examines breaker status recorded during that timeframe. Any change in the monitored value represents an event, which triggers an alarm. Once examination for the given parameter and time period is complete, the monitored time interval is marked as examined and the alarm as tracked. Future monitoring of the historical archived data in the data store 18 will check subsequent intervals based on what has already been marked as examined.
The alarming feature is not limited to tracking on/off types or digital state data. Rather, monitored recorded events may also be examined based on numerical thresholds. For example, generation managers may wish to monitor megawatt (MW) levels and create different events based on the number of megawatts produced at a power generation facility. The plant may want to be alerted when the megawatt (MW) level reaches a specific level, such as 100, 250, and 500. Each MW level reached requires a unique action or log entry to be recorded. Such alarms are defined in the monitoring center 10 to initiate tracking and logging. For example, in an exemplary embodiment of the present invention, alarms may be defined by noting the following data points:

- Archive historian database;
- Archive historian data point to monitor;
- Compare value (or alarm value);
- Alarm log message to create when value is greater than comparison value;
- Alarm log message to create when value is less than comparison value; and
- Alarm log message to create when value is equal than comparison value.

To ensure all intervals are examined, examined archived data may be marked by noting:

- Archive historian point examined;
- Alarm that is tracked;
- Examination start time; and
- Examination end time.

This serves to baseline subsequent interval checks. It is to be understood that other notations may be made without departing from the scope of the present invention.
In accordance with an exemplary embodiment of the system and method of the present invention, monitoring of any number of hosted power generation units is realized by collecting qualitative (e.g., event data) and quantitative (e.g., cost, market data) information from a plurality of disparate data sources, converting the disparate data into a common data format, and storing the transformed data to be served up through a communications network, such as the Internet, to a plurality of client devices that may be located anywhere in the world. The various report interfaces in accordance with the present invention allow the user to monitor the performance of the hosted power generation units including a comparison of the actual performance of the monitored unit with expected (i.e., budgeted) performance. The system and method of the present invention generates reports using XML config files to reduce the time to build and customize any number of reports. The XML config files allow developers to simply map data from database stored procedures directly to a report without writing any code to reduce the time required to deliver a report and eliminate the need for any code changes to existing applications.
It will be apparent to those skilled in the art that various modifications and variations can be made in the system and method of the present invention without departing from the spirit or scope of the invention. Thus, it is intended that the present invention cover the modifications and variations of this invention provided they come within the scope of the appended claims and their equivalents.

Claims

What is claimed is:

1. A system, comprising:

a communications network;

a plurality of remotely located data sources to provide power data, the power data including quantitative and qualitative data of one or more power generation units; and

a performance monitor in communication with the plurality of remotely located data sources through the communications network, the performance monitor including

a communications unit to extract the power data from the plurality of remotely located data sources,

a data conversion unit to transform the power data into a common data format,

a data store to store the transformed power data, and

a user interface unit to display the transformed power data on one or more client devices through the communications network.