Operations Reporting Applications
A component of the OPERA Framework
Transaction Scheduling System (TSS)
TSS Transaction Scheduling System provides a relational database
representation of scheduled and completed interchange transactions. TSA is used
for pre-scheduling, real-time scheduling, and reconciliation/billing, and by
management to analyze and report on transaction behavior.
TSS Functionality
TSS provides a centralized repository of Interchange Transaction data for
operations analysis, tracking, and billing. This includes the ability to track
improvement in scheduling practices, to identify additional revenue sources, and
to execute a monthly reconciliation. TSS replaces or supplements traditional
"Interchange Transaction Schedulers" provided with SCADA Systems, which may not
include NERC path data.
In future, Net Interchange data may be provided by a Regional Transmission
Operator (RTO), and TSS can accommodate this need. A Transaction is defined as a
purchase or sale to/from an Agency/PSE of a defined MWh amount for a given path
at a fixed $/MWh cost. Until the restructuring which will eliminate NERC Tags,
transactions are tagged. For Transaction Cost accounting, each transaction is
associated with an Account Code. The business logic to track Account Code's and
agreements is built in and stored with TSS
Account Code database. These codes define the transmission rights and agreements
established by the Utility for implementing energy transactions (delivery point,
agency/utility, account, type of energy, etc.).
TSS Application Architecture
TSS consists of three independent databases: Transactions, Paths, and Energy
Contracts. Transactions is used for billing and analysis, Paths for guiding
staff in pre-scheduling and next hour trading, and Contracts to provide
schedulers with a summary of the key data associated with long-term energy
contracts such as Terms associated with long-term contract agreements. In
entering a Transaction into the database, when a user specifies a Delivery
Point, the Entry Form presents a list of Account Codes associated with that
Delivery Point. The Account Code database can contain inactive codes, a filter
is used to only select active codes. This will increase the user's ability to
define more creative purchases or sales of energy and introduces uniformity in
defining transactions and reducing user error.
Reporting
TSS includes a set of standard reports focusing on purchases and sales by date,
source / sink, and total. Reports can be easily mailed for workgroup
collaboration, and ASCE offers custom reports to meet any other need.
|
The Transaction Entry Form allows users to
analyze each hour of the day, correlating PSE
and Cost Of Power Information at top, with PSE Credit and Credit Rating.
The Transaction Analysis Form enables
three levels of Purchase and Sale analysis:
total for a date range, total by day (graphed for trending),
and total by Source/Sink (in table view at form bottom) for each day.
|
|