Version Number 17 - Elexon

EAC/AA Operations Guide Version 17.100

© ELEXON Limited 2013

EAC/AA Operations Guide

Version Number 17.100


© ELEXON Limited 2013 Page 1 of 95

EAC/AA Operations Guide

Status : Draft

:

Version : 17.100

Date : 27 June 2013

Prepared by : Cognizant

Approved by (Cognizant) : Project Manager



Table Of Contents

1 Introduction .................................................................................................. 5 1.1 Purpose ...................................................................................................... 5 1.2 Scope ......................................................................................................... 5 1.3 Structure of Document ............................................................................... 6 1.4 Amendment History .................................................................................. 6

1.5 Summary of Changes ................................................................................. 8 1.6 Changes Forecast ....................................................................................... 9 1.7 References ................................................................................................. 9 1.8 Abbreviations ............................................................................................. 9

1.9 Intellectual Property Rights and Copyright ............................................. 11

2 System Overview ........................................................................................ 12 2.1 File Receipt .............................................................................................. 13 2.2 User Interface .......................................................................................... 13

2.3 Scheduler ................................................................................................. 13 2.4 Database ................................................................................................... 13 2.5 External Interfaces ................................................................................... 13

3 Operational Schedule ................................................................................. 16 3.1 Daily Tasks .............................................................................................. 16

3.2 Ad Hoc Tasks .......................................................................................... 16

4 Getting Started ........................................................................................... 18 4.1 Logging On .............................................................................................. 18

4.2 User Interface Overview .......................................................................... 18 4.3 On-line Help ............................................................................................ 24

4.4 Status and Exception Reporting .............................................................. 24

5 Load Daily Profiles ..................................................................................... 26 5.1 Load a Selected Daily Profile Coefficient ............................................... 29

5.2 Load all Daily Profile Coefficients .......................................................... 30 5.3 Field Summary ........................................................................................ 32

5.4 Differences in Automatic Mode .............................................................. 33

6 Calculate EAC/AA ..................................................................................... 34 6.1 Initiate Calculation of EAC/AA .............................................................. 35 6.2 Field Summary ........................................................................................ 36

6.3 Differences in Automatic mode ............................................................... 36

7 Determine Deemed Meter Advance .......................................................... 37 7.1 Initiate Calculation of Deemed Meter Advance ...................................... 38 7.2 Field Summary ........................................................................................ 38 7.3 Differences in Automatic mode ............................................................... 39

8 Ad Hoc Deemed Meter Reading ................................................................ 40 8.1 Initiate Calculation of Deemed Meter Reading ....................................... 40

8.2 Initiate Deemed Meter Reading Audit Report ......................................... 44

9 Maintain Standard Settlement Configurations ....................................... 46



9.1 Add a New Standard Settlement Configuration ...................................... 46 9.2 Delete a Standard Settlement Configuration ........................................... 47 9.3 Amend a Standard Settlement Configuration ......................................... 47 9.4 Identify SSCs for which Daily Profile Coefficients will not be loaded .. 47

9.5 Field Summary ........................................................................................ 47

10 Identify Input Files used in Calculations ................................................. 49 10.1 Display the Input Files ............................................................................ 49 10.2 Field Summary ........................................................................................ 50

11 Specify Smoothing Parameter .................................................................. 51 11.1 Create New Smoothing Parameter .......................................................... 51

11.2 Update Smoothing Parameter ................................................................. 51

11.3 Delete Smoothing Parameter ................................................................... 52 11.4 Field Summary ........................................................................................ 52

12 Report on Profile Coefficients ................................................................... 53 12.1 Field Summary ........................................................................................ 53

13 Display Latest Settlement Date for Profile Coefficients ......................... 55 13.1 Field Summary ........................................................................................ 55

14 Archive Daily Profile Coefficients and Smoothing Parameters ............ 56 14.1 Field Summary ........................................................................................ 57

15 Restore a Report on Archived Daily Profile Coefficients ....................... 58 15.1 Field Summary ........................................................................................ 59

16 Maintain User ............................................................................................. 60 16.1 Manage User Accounts ........................................................................... 60 16.2 Change of Password ................................................................................ 62

16.3 Field Summary ........................................................................................ 63

17 Browse GSP Group Profile Class Default EAC ...................................... 65 17.1 Field Summary ........................................................................................ 65

18 Reports ........................................................................................................ 66 18.1 User Initiated Reports ............................................................................. 66 18.2 Automatically Generated Reports ........................................................... 66 18.3 Viewing Reports ...................................................................................... 67

Appendix A Status and Error Messages .................................................................... 70 A.1 Error and Status Messages ...................................................................... 70 A.1.1 Error and Status Messages Displayed via the User Interface.................. 70 A.1.2 Deemed Meter Reading Calculation Short and Long Messages ............. 72 A.1.3 Deemed Meter Reading Calculation Audit Report Error Messages ....... 73

A.2 Error and Status Messages included in Exception and Control Reports . 73

Appendix B Report Directory .................................................................................... 80 B.1 Report on Profile Coefficients ................................................................ 80 B.2 Report on Archived Data ........................................................................ 81 B.3 EAC/AA Control Report ......................................................................... 82



B.4 EAC/AA Exception Report (Human-Readable) ...................................... 83 B.5 EAC/AA Tolerance Value Exceptions Report ........................................ 84 B.6 Determine Deemed Meter Advance Control Report ............................... 85 B.7 Determine Deemed Meter Advance Exception Report ........................... 87

B.8 Load Daily Profiles Control Report ......................................................... 88 B.9 Load Daily Profiles Exception Report ..................................................... 89 B.10 Load Standard Settlement Configuration Exception Report ................... 90 B.11 Ad Hoc Deemed Meter reading Calculation Audit Report ..................... 91



1 Introduction

This document is the Operations Guide for the Estimation of Annual

Consumption / Annualised Advance (EAC/AA) application software

developed for ELEXON.

Software Version

This version of the EAC/AA Operations Guide is applicable to Release

10.0.011.0.0 and later of the EAC/AA application software.

1.1 Purpose

The purpose of this Operations Guide is to provide information on the

features of the EAC/AA application software that will support the day-to-

day operational business of organisations responsible for handling

Estimations of Annual Consumption and Annualised Advances.

Estimations of Annual Consumption (EACs), derived for each Metering

System, are weather normalised estimates of annual consumption over a

calendar year.

Annualised Advances (AAs), also derived for each Metering System, are

calculated for a Meter Advance Period (period between successive meter

readings), and when profiled, produce a total consumption figure equal to

the meter advance.

1.2 Scope

The scope of this document covers the operational aspects of the EAC/AA

application software, encompassing the functionality of the software that is

available to the four EAC/AA Operational Roles, namely:

System Operator;

Operations Supervisor;

System Manager;

EAC/AA Auditor.

The EAC/AA functionality to which each user role has access is shown in

terms of the user interface menus in section 4.2.2. Details of this

functionality are described in the sections that follow.

Detail pertaining to hardware and third party software products is included

only where necessary to support the description of the EAC/AA application

software.

It is assumed that all users of the system have received some basic training

in the use of the following:

PCs;

Windows;

Oracle Forms.

For system management aspects of the environment in which the EAC/AA

application software will operate, refer to the EAC/AA System Management

Guide.



For details of installation of the EAC/AA application software, refer to the

corresponding Installation Guide.

Comments on the completeness and accuracy of this guide are welcome. A

Reader Response Form is contained at the back of this guide.

1.3 Structure of Document

The remainder of this document consists of the following sections:

Section 2 gives a high-level overview of the EAC/AA application

software and shows its data interfaces, with a brief description of

each;

Section 3 gives guidance on scheduling tasks using functionality

supplied by the EAC/AA application software;

Section 4 provides an introduction to the facilities for logging on to

the EAC/AA system, and an overview of the user interface, including

error messages and on-line help;

Section 5 to section 15 contain information on the functions provided

by the EAC/AA application software;

Section 15 provides guidance on generating reports from the

EAC/AA application software.

Appendices to this document are as follows:

Appendix A lists the error and status messages that may be generated

by the EAC/AA application software;

Appendix B shows examples of reports that can be generated from

the EAC/AA application software.

1.4 Amendment History

Issue Details

0.901 First issue to client

0.902 Addresses APP comments

0.990 Addresses outstanding comments and observations

1.000 Authorised version. Addresses Pool APP comments.

2.401 Draft for internal review containing Release 2

changes.

2.490 Incorporating internal review comments.

2.500 Authorised issue consistent with Release Two.

Incorporating Pool Review comments.

2.990 Draft for external review of merged Release One /

Release Two version. Since there have been no new

issues of the Release One document since v1.000, this

version is identical to v2.500 apart from the Version

Number and Amendment History. Change bars show

changes from v1.000.

3.000 Authorised version. Merge of v2.000 and v2.500.

Change bars show changes from v2.000.

3.001 Draft version incorporating the following ORs:



Issue Details

OR2716, OR2718,OR2726

3.900 Draft for internal review containing TA2000 changes.

Change bars show changes from v3.000.

3.990 Incorporating internal review comments.

3.991 Incorporating Pool comments.

OR2718 removed.

3.992 Incorporating further Pool comments.

4.000 Authorised Version.

4.001 Draft version incorporating the following ORs:

OR2869 (LCR138), OR2920

4.990 Issued to Pool for review.

5.000 Authorised Version.

5.100 Incorporating LCR160/3 (SIR 2296) - Reasonableness

Checks for AAs.

5.990 Incorporating LCR170/2 - Upgrade to Oracle 8i.

6.000 Authorised version.

6.001 Incorporating the following OR’s:

OR3118 – Updating the copyright notice

OR3119 – Correcting references

6.002 Change to Office 2000

6.003 Changes relating to ELEXON superseding The

Electricity Pool.


7.001 Incorporating OR3199

7.990 Issued to ELEXON for review

7.991 Updated unviewable graphic

7.992 Incorporated ELEXON review comments.


8.001 Incorporating LCR225 - Upgrade to Oracle 9i.

Updated for OR3238

8.990 Issued to ELEXON for review

8.991 Applied ELEXON review comments


9.001 Updated for LCRA218/4 BETTA Changes

Updated for OR3411

Updated for LCR223 - Rectification of EAC/AA

calculator issues

9.990 Version for ELEXON review

9.991 Apply ELEXON review comments

Updated to clarify operation of the “Identify Input

Files” screen – OR3434

10.000 Made Definitive

11.000 Updated document references

11.001 Updated with ELEXON comments on LCR223, issue

for ELEXON review



Issue Details

11.990 Updated with new ELEXON comments


12.001 Amendments started for Nov. 04 Release

CP1052 UNIX Upgrade 5.1A to 5.1B

12.002 Incorporated comments from test and programme

teams from review date 28/09/04. Issued to ELEXON

for review.

12.003 Incorporated additional comments. Issued to ELEXON

for review.

13.000 Made definitive.

13.900 Introduced new forms added as part of Nov-05 release.

Incorporating:

CP1081 : Manual Initiation of DMA Calculation;

CP933 : Management of System Security

13.901 Incorporated internal review comments.

13.990 Version for ELEXON review.

13.991 Incorporated ELEXON review comments and changes

for OR3498 OR3496 OR3499

13.992 Incorporated further ELEXON review comments.

14.000 Made definitive

14.001 Incorporating changes for Nov-06 release.

14.002 Incorporated Internal review comments and changes

for HD061638.

14.990 Draft for ELEXON review

15.000 Incorporated review comments & made definitive.

15.900 Incorporating Changes for Feb-08 Release: OR3571

HD048517 and internal OR3689

15.990 Incorporated Internal review comments ; draft for

ELEXON review

15.991 Incorporated ELEXON review comments.

16.000 Made definitive

16.010 Updated document classification

16.990 Incorporating Changes for Feb-10 Release: CP1311

16.991 After internal review

16.992 After ELEXON review. Included the CP1295 changes.

16.993 After incorporating the changes for PPT defect

17.000 Definitive Version

17.00117.1

00

June 2013 Party Agent Technology Upgrade

Updated for Tech Upgrade (Oracle DB upgrade from

10.2.0.3 to 11.2.0.3 and OAS upgrade from 10.1.2.2 to

11.1.1.6)

1.5 Summary of Changes

Changes as indicated in the amendment history.



1.6 Changes Forecast

Agreed Change Requests will be incorporated.

1.7 References

Mnemonic Information Details

[ESMGDE] Title:

Version No:

Author:

Date:

EAC/AA System Management Guide.

17.000

Cognizant

27 June 2013

[EINGDE] Title:

Version No:

Author:

Date:

EAC/AA Installation Guide.

17.000

Cognizant

27 June 2013

[ETSPEC] Title:

Version No:

Author:

Date:

EAC/AA Physical Design Technical Specification.

18.000

Cognizant

27 June 2013

1.8 Abbreviations

AFYC Average Fraction of Yearly Consumption

ASCII American Standard Code for Information Interchange

BETTA British Electricity Trading and Transmission

Arrangements

BM Balancing Mechanism

BMUIGG BM Unit In GSP Group

BSC Balancing and Settlement Code

BUSTEV BM Unit Supplier Take Energy Volume

CCC Consumption Component Class

CDCA Central Data Collection Agent

CTCU Central Tele-switch Control Unit

DA Data Aggregator

DC Data Collector

DMA Deemed Meter Advance

DMR Deemed Meter Reading

DPP Daily Profile Production

DRP Data Retention Period

DUoS Distribution Use of System

EAC/AA Estimation of Annual Consumption / Annualised Advance

EPD Elementary Process Description

GMT Greenwich Mean Time

GSP Grid Supply Point



HH Half-Hourly

HHDA Half-Hourly Data Aggregator

ISR Initial Settlement and Reconciliation

ISRA ISR Agent

LDM Logical Data Model

LLF Line Loss Factor

LLFC LLF Class

MDD Market Domain Date

MDDA MDD Agent

MSID Metering System ID

NETA New Electricity Trading Arrangements

NHH Non-Half-Hourly

NHHDA Non-Half-Hourly Data Aggregator

NPG Non-Pooled Generation

PFA Pool Funds Administrator

PPR Profile Production Run

SAA Settlement Administrator Agent

SPM Supplier Purchase Matrix

SRE Settlement Run Equitability

SSA Settlements System Administrator

SSC Standard Settlement Configuration

SSR Supplier Settlement and Reconciliation

SVA Supplier Volume Allocation

SVAA SVA Agent

TPR Time Pattern Regime

TUoS Transmission Use of System

UTC Universal Time Clock

VMRPC Valid Measurement Requirement Profile Class

VSCPC Valid combinations of Settlement Configurations and

Profile Classes



1.9 Intellectual Property Rights and Copyright

The copyright and other intellectual property rights in this document are

vested in ELEXON. These materials are made available to participants in

the GB electricity industry to review and copy for the sole purpose of their

participation in the electricity industry. All other commercial use is

prohibited including downloading, copying, distributing, modifying,

transmitting, publishing, selling or creating derivative works (in whatever

format) from this document or in other cases use for personal academic or

other non-commercial purposes. All copyright and other proprietary notices

contained in the document must be retained on any copy you make.

All other rights of the copyright owner not expressly dealt with above are

reserved.

No representation, warranty or guarantee is made that the information in this

document is accurate or complete. While care is taken in the collection and

provision of this information, ELEXON Limited shall not be liable for any

errors, omissions, misstatements or mistakes in any information or damages

resulting from the use of this information or action taken in reliance on it.



2 System Overview

This document is the Operations Guide for the Estimation of Annual

Consumption / Annualised Advance (EAC/AA) application software

developed for ELEXON.

The main functions of the EAC/AA application software are as follows:

Generate Estimated Annual Consumptions (EACs), based on Meter

Advances, Daily Profile Coefficients and previous estimates;

Generate Deemed Meter Advances (DMAs), based on Estimated

Annual Consumptions and Daily Profile Coefficients;

Generate Deemed Meter Readings, based on Meter Readings and

Daily Profile Coefficients;

Load Daily Profile Coefficients for different Settlement Dates to

support the functionality described above;

Ensure appropriate data is stored in order to view the details of any

calculations;

Maintain configuration data in the database;

To provide reports on data associated with EAC/AA.

Calculation of EAC/AA requires Daily Profile Coefficient data, with Meter

Advances (difference between successive meter readings) for the

Annualised Advance calculation and previous or initial EAC for the

Forward EAC calculation. The output from this calculation is the

Annualised Advance and the Forward EAC. The data required for the

process is supplied as files with the resulting calculated data output as a file.

The Deemed Meter Advance calculation is similarly supplied with data in a

file and the resulting advance made available as an output file.

Thus, for both EAC/AA calculation functions, files are received from

external sources, some processing is performed and outputs are delivered as

files. However, neither the inputs nor the outputs to these calculations are

stored in the database. The principal data stored in the EAC/AA database

are the Daily Profile Coefficients.

EAC/AA may be installed in Manual or Automatic Mode. In Automatic

Mode the calculation of Estimated Annual Consumptions, Deemed Meter

Advances and the Load of Daily Profile Coefficients all happen

automatically as soon as the system receives the files, whereas in Manual

Mode the user determines when these three functions are processed.

There is also an Ad Hoc Deemed Meter Reading Calculation for which the

user enters the input data on the screen, and the calculated data is output on

the screen. The inputs and the outputs of this calculation are stored in the

database.

The main components of the application software, which support this

functionality, are as follows:



2.1 File Receipt

A separate process is used to read in files as they arrive from outside the

system. This process checks that the file headers and footers are not corrupt

and stores information about the files in the database.

The files copied into the E_files_in directory must have read and write

permissions for the EAC user.

2.2 User Interface

The user interface is used to initiate the main processes, to maintain or view

the data in the database and to generate reports on the database.

2.3 Scheduler

This process is used to manage the execution of calculations and the

production of reports, initiated from the User Interface. Accordingly, when

a user performs a calculation, the details of the job are stored in the database

whereupon the Scheduler reads the details and initiates the required

processing.

2.4 Database

This stores Daily Profile Coefficients, Configuration data and details of

what files have been read by the system.

2.5 External Interfaces

The following diagram illustrates the external interfaces to the EAC/AA

system.

EAC/AA

System

ISR Agent

1.The Daily Profile

Coefficients File

Electricity Pool

7. Standard Settlement

Configuration File

Non- HH Data Collector

Non-HH Data Collector

5. Deemed Meter

Advance Request

File

4. Smoothing

Parameter User

Interface

3. The EAC/AA

Results File

6. Deemed Meter

Advance File

ELEXON (via user)

2. The EAC/AA

Request Files

8. Ad Hoc Deemed

Meter Reading

Request Interface

Supplier (via user)

Note that the numbering of the interfaces is for identification purposes only,

and does not imply any ordering of data transfer. The interfaces are

described below:



1. The Daily Profile Coefficients are transferred to the EAC/AA system

via a file interface. The Daily Profile Coefficient files are supplied by

the ISR Agent and the actual load process is initiated by the user, if in

Manual Mode, via the user interface. In Automatic Mode the actual

load process is initiated automatically as soon as the presence of such

a file is detected. Each file contains a set of Daily Profile Coefficients

for one or more GSP Groups for a given Settlement Date. Each set

comprises a Daily Profile Coefficient for each valid combination of

Standard Settlement Configuration, Time Pattern Regime and Profile

Class. See section 5 for information on loading Daily Profile

Coefficients and section 12 and section 13 for viewing related data.

2. The EAC/AA calculation Request Files are transferred to the

EAC/AA system via a file interface. These files are supplied by the

Non-HH Data Collector. The actual calculation process is initiated, if

in Manual Mode, via the user interface. In Automatic Mode the actual

calculation process is initiated automatically as soon as the presence

of such a file is detected.

3. The results of the EAC/AA calculations are accessed by the Non-HH

Data Collector via the file interface.

4. The Smoothing Parameter data originating from the Non-HH Data

Collector is maintained by the EAC/AA users via the user interface.

Refer to section 11 for further information.

5. The Deemed Meter Advance calculation Request Files are accessed

by the EAC/AA system via a file interface. These files are supplied by

the Non-HH Data Collector. Calculation of Deemed Meter Advance

is initiated by the user, if in Manual Mode, via the user interface. In

Automatic Mode the actual calculation process is initiated

automatically as soon as the presence of such a file is detected. See

section 7 which describes how to perform this operation.

6. The results of the Deemed Meter Advance calculations are passed to

the Non-HH Data Collector via the file interface.

7. The Standard Settlement Configurations and Average Fractions of

Yearly Consumption are transferred to the EAC/AA system via a file

interface. In Automatic Mode, the Standard Settlement Configuration

files are supplied by ELEXON and the actual load process is initiated

automatically as soon as presence of such a file is detected. If the

identifier of any Standard Settlement Configuration file already exists

in the database and the description is different, then an exception

report is generated, (see Appendix .1B.10 for an example), and the

data is not loaded into the database. Similarly if there are any

validation errors in Average Fractions of Yearly Consumption data

they are included in the exception report and the data is not loaded

into the database.

8. Requests an Ad Hoc Deemed Meter Reading are sent manually from a

Supplier to the Non-HH Data Collector and are then entered into the

EAC/AA system by the users via the user interface form for Ad Hoc

DMR Calculation. EAC/AA uses the data entered via the user

Field Code Changed

Field Code Changed



interface to perform the calculations required and return the result to

the user.

9. The GSP Group Profile Class Default EAC data is browsed by the

EAC/AA users via the user interface. Refer to section 11 for further

information. The underlying table for the GSP Group Profile Class

Default EAC screen is loaded from a script supplied by ELEXON.



3 Operational Schedule

This section provides guidelines on the scheduling of tasks that need to be

performed using functionality provided by the EAC/AA application

software.

Note that it is the responsibility of the organisation running the EAC/AA

system to devise its own schedule, taking into account the operational

environment.

The following notes numbered 3.1.1, 3.1.2 and 3.2.1 do not apply to

Automatic Mode since all these tasks occur automatically as the files arrive.

The data collector systems outside of EAC/AA can determine when the files

arrive.

3.1 Daily Tasks

1. Daily Profile Coefficients are received on a daily basis from the ISR

Agent, a number of days in arrears of the Settlement Date to which

they relate.

Daily Profile Coefficient files are normally loaded individually.

However, occasionally it may be necessary to load a greater number

of Daily Profile Coefficients, in order to support the Data Collector

being appointed to Metering Systems in a new GSP Group. The time

taken to perform this task will inevitably depend on the number of

files being loaded.

In addition, the Standard Settlement Configurations for which Daily

Profile Coefficients are loaded can be specified via the user interface,

thus reducing load time.

Occasionally, revised Daily Profile Coefficient files may need to be

loaded.

2. Calculation of Annualised Advances and Estimations of Annual

Consumption is performed on a daily basis.

If Daily Profile Coefficients are not available for any combination of

GSP Group, Profile Class, Standard Settlement Configuration and

Time Pattern Regime on any Settlement Date within the Meter

Advance Period, then Meter Advances are not calculated for any

Settlement Registers of that Metering System. The reason for not

calculating EAC/AA for a particular Metering System is contained in

the EAC/AA Control Report. It is therefore advisable that you check

which Daily Profile Coefficients have been loaded into the system

prior to calculating EAC/AA, and perform the load operation prior to

EAC/AA calculation if necessary. This can be done using the Process

Data Files form.

3.2 Ad Hoc Tasks

1. Deemed Meter Advances (DMAs) are required on an ad Hoc basis,

when an actual changeover reading cannot be obtained or agreed, on

change of Supplier for a Metering System.



If Daily Profile Coefficients are not available for any combination of

GSP Group, Profile Class, Standard Settlement Configuration and

Time Pattern Regime on any Settlement Date within the Meter

Advance Period, then Deemed Meter Advances are not calculated and

an exception report is generated. It is therefore advisable that you

check which Daily Profile Coefficients have been loaded into the

system prior to determining DMA, and perform the load operation

prior to DMA calculation if necessary. This can be done using the

Process Data Files form.

2. Deemed Meter Readings (DMRs) are required on an ad hoc basis

from time to time where the code allows for a DMR but the NHHDC

system is not able to initiate the calculation.

The Ad Hoc DMR Calculation form allows for a DMR to be

calculated for a specified date, for a metering system from a pair of

meter readings and the meter SSC, GSP Group, Profile Class and TPR

details.

3. Other tasks, such as maintenance of data, and reporting on data,

should be scheduled to avoid conflict with loading and calculation

tasks. Calculations of EACs and DMA take a snapshot of the

database at the beginning of calculations to maintain a consistent view

of the database until the calculations are complete.

The EAC/AA system handles conflicts in the following ways:

if Daily Profile Coefficients are being loaded, attempts to

archive data from the database via the Archive Daily Profile

Coefficients form will fail;

if data is being archived from the database, and the user attempts

to load Daily Profile Coefficients, the Load Daily Profile

Coefficient process will wait until the archiving has completed.



4 Getting Started

This section provides an introduction to the facilities for logging on to the

system; provides an overview of the user interface; outlines help and error

reporting functionality.

4.1 Logging On

Logging on to the EAC/AA system is controlled by the standard Oracle

User name and Password validation. This mechanism ensures that you are a

valid EAC/AA user. For further information about user names and

passwords, consult your System Manager.

Access to EAC/AA functions is controlled by the allocation of EAC/AA

user roles to users. You can only access a function if you have the

appropriate authority. See section 4.2.2 which includes a table showing

which menus and functions each EAC/AA User Role has access to.

4.2 User Interface Overview

This section gives an overview of the menus and toolbars to which users of

the EAC/AA system have access.

The User Interface has been developed using Oracle Forms. A form is a

window and its behaviour is similar to that of other Windows applications,

such as File Manager and Microsoft Mail. Some of the tasks that can be

performed by the user within the forms are specific to Oracle Forms. The

main features of the user interface are described in this document. For

further information about using Oracle Forms, refer to the Oracle Forms

Documentation Set.

The User Interface includes a toolbar, described in section 4.2.1, which

provides access to commonly used functions for navigating within the

forms, restricting data displayed on the forms (executing queries), editing

data and accessing on-line help. Above the toolbar is a set of menus. The

menus give access to the functionality provided by the toolbar, other

standard functionality provided by Oracle forms and also to EAC/AA-

specific functions. The menus are described in section 4.2.2. Function keys

that are defined with Oracle Forms can also be used to access the toolbar

and menu functions.

When entering a date in any of the date input fields, the date should be in

the DD/MM/RRRR format where ‘/’ is the delimiter. The delimiter entered

can be any character as long as it is not an alphabet. For example, the

following formats are valid

01-01-2004

01*1 2004

01-jan-2004

01=jan/2004



4.2.1 Toolbar

The toolbar, shown in the figure below, provides some of the functionality

for EAC/AA forms. Most forms display a subset of the toolbar buttons.

The table following the figure gives a brief description of the buttons on the

toolbar.

Previous

Record Add

Record

Delete

Record

Save

Changes

Discard

Changes

Keys

Help

Exit

Next

Record Enter

Query

Figure 4.2.1.1: EAC/AA Toolbar

Execute

Query

Cancel

Query

Figure 4.2.1.2: EAC/AA Toolbar



Enter Query Enter query mode. Queries enable you to define the criteria for the

data that you want to view on the screen. When the form is in query

mode, ENTER QUERY is displayed in the Status Line at the bottom

of the form.

When you click on this button, the Enter Query mode button

disappears and two further buttons are displayed:

Execute Query - initiates a query on the current area of

the form

Cancel Query - cancels out of query mode

Previous Record Navigate to the record above the one the cursor is currently on.

Next Record Navigate to the record below the one the cursor is currently on.

Insert Record Create a new record in the current part of the form.

Delete Record Delete the current record.

Save Commit any outstanding changes to the database.

Clear Record Clear the contents of the current record from the screen. This should

not be confused with the Delete Record function which removes the

record from the database.

Show Keys Display the keys available in a pop up window.

Help Display the help available.

Exit Return to the top level of the Application.

4.2.2 Menus

Menus are also displayed on the initial form and on the subsequent forms,

beneath the Title bar (see Figures 4.2.2.1 to 4.2.2.5). The menu items to

which you have access depend on the EAC/AA user role to which you have

been allocated by the System Manager and with which you have logged on.

If you do not have access to a particular menu item it will be greyed out.

Figure 4.2.2.1: EAC/AA Initial Menu



The File Menu allows the user to change their password through the Change

Password menu option.

Figure 4.2.2.2: EAC/AA Initial Menu’s Items






The second leftmost menu item, EAC/AA, provides access to EAC/AA

application-specific menus, illustrated in the following figure.

Process Files

Menu

Process Data

Files

Maintain

Parameters

Menu

Archive And

RestoreReports

Standard

Settlement

Configurations

Report On

Profile

Coefficients

Latest DPC

Settlement

Day

Identify Input

Files

Smoothing

Parameters

Restore Profile

Coefficients

Report

Archive Profile

CoefficientsSelect Reports

Manual

Calculations

Ad Hoc DMR

Calculation

User

Administration

Maintain User

Ad Hoc DMR

Audit Report

GSP Group

Profile Class

Default EAC

Figure 4.2.2.6: EAC/AA Menu Structure



The following table identifies the functions that each EAC/AA User Role

has access to.

EAC/AA User Role Available Menus Available Functions

System Operator Process Files Process Data Files, if using Manual Mode

Maintain Parameters Smoothing Parameters (browse only)

GSP Group Profile Class Default

EAC(browse only)

Identify Input Files

Latest DPC Settlement Date

Report on Profile Coefficients

Reports Select Reports

Operations Supervisor Process Files Process Data Files, if using Manual Mode

Manual Calculations Ad Hoc DMR Calculations

Ad Hoc DMR Audit Reports

Maintain Parameters Smoothing Parameters

GSP Group Profile Class Default

EAC(browse only)

Identify Input Files

Latest DPC Settlement Date

Report on Profile Coefficients

Standard Settlement Configurations


System Manager User Management Create/Edit/Delete user accounts

Archive and Restore Archive Profile Coefficients

Restore Profile Coefficient Report


System Auditor Maintain Parameters Report on Profile Coefficients


Manual Calculations Ad Hoc DMR Audit Reports

Figure 4.2.2.7: EAC/AA Subsequent Menu



The subsequent menu ( the one with menu items Action, Edit, Block, Field,

Record, Query, Window, Help - see Figure 4.2.2.6) give access to

functionality for navigating within forms, entering and executing queries,

adding and removing data and accessing on-line help. The most commonly

accessed items from these menus are also available from the toolbar

described in section 4.2.1.

4.3 On-line Help

On-line help is available by clicking on the Help key on the toolbar or by

selecting Help from the menu. Help is an on-line version of this Operations

Guide, converted into Windows help format, with a Contents page.

4.4 Status and Exception Reporting

The EAC/AA system provides several mechanisms for reporting of status

and errors:

control report, providing information on the following batch

processes:

loading of Daily Profile Coefficients (see section 5 for further

information);

calculation of Deemed Meter Advances (see section 7 for further

information);

calculation of Estimations of Annual Consumption and

Annualised Advances (see section 6 for further information).

Examples of these control reports are given in Appendix B.

exception report, reporting on exceptions generated during:

loading of Daily Profile Coefficients (see section 5 for further

information);

calculation of Deemed Meter Advances (see section 7 for further

information);

calculation of Estimations of Annual Consumption and

Annualised Advances (see section 6 for further information);

loading of Standard Settlement Configurations.

Examples of these exception reports are given in Appendix B.

application error messages, displayed via the user interface, in

message boxes and at the bottom of forms. These error messages

are listed in Appendix A;

audit log, which logs changes via the Smoothing Parameter form,

GSP Group Profile Class Default EAC form and the Maintain User

form;

job log, which details batch jobs that are handled by the Scheduler;

file receipt manager log, which logs files that are received by the

EAC/AA system;



Ad Hoc DMR Audit reports, which is requested by the user and

reports on the results of Ad Hoc DMR calculations.

The audit log, job log and file receipt manager log are described in more

detail in the EAC/AA System Management Guide.



5 Load Daily Profiles

The following sections up to section 5.3 are written to describe the operation

of the system in Manual Mode. These sections contain some information

relevant to both Manual Mode and Automatic Mode. Section 5.4 describes

what is different in Automatic Mode.

This form allows you to load into the EAC/AA system one or more Daily

Profile Coefficient files that have been received from the ISR Agent/s.

Figure 5.1: The Process Data Files Form

When the form is loaded, each row of the table displays one of the following

unprocessed files:

Daily Profile Coefficient;

EAC/AA Request;

Deemed Meter Advance Request.

These files have been received by the EAC/AA system, but have not been

loaded into the appropriate file store. You can filter the files against the

field content using standard Oracle query functionality.



Additionally, to filter the display by file type, select one of the following

relevant option buttons and execute a query:

All File Types, to display all file types;

EAC Files, to display only EAC/AA Request files (these are not

applicable for this function);

DMA Files, to display only Deemed Meter Advance files (these are

not applicable for this function);

DPC Files, to display only Daily Profile Coefficient files.

Daily Profile Coefficient files displayed on this form cannot be updated or

deleted and new files cannot be inserted directly.

In principle, there are two categories of Daily Profile Coefficient files:

Type 1 contains data for one or more GSP Groups in which a Non-

Half Hourly Data Collector was known to be operating, by the ISR

Agent concerned, when it sent the Daily Profile Coefficient file to

the EAC/AA system.

Note that by the time a Type 1 file is received by the EAC/AA system,

it is possible that the Non-Half Hourly Data Collector may have

started operating in a further GSP Group. In such circumstances, the

file is not operationally a Type 1, because Daily Profile Coefficient

data is not contained in the file for the new GSP Group. Under such

conditions, the ISR Agent will send a Type 2 file, (see next bullet), for

the new GSP Group.

A Type 1 file may be a revised file sent by the ISR Agent if an error is

detected in the original file.

For Type 1 Daily Profile Coefficient files, the GSP Group field on the

form is blank.

Type 2 always contains data for a single GSP Group in which a

Non-Half Hourly Data Collector operates. A Type 2 file is only

sent if a Non-Half Hourly Data Collector, which already operates

in one or more GSP Groups, starts operating in a new GSP Group,

and so data will not have been received for that GSP Group in

previous Type 1 files.

Type 2 Daily Profile Coefficient Files always have a value in the GSP

Group field.

The following example illustrates the rationale for these file types:

1. The ISR Agent does run number 777 for all GSP Groups, and sends a

Daily Profile Coefficient file Type 1 to the Non-Half Hourly Data

Collector via the EAC/AA system interface. The file contains DPC

data for the GSP Groups in which the Data Collector operates, say

GW, GX, GY;

2. The ISR Agent performs a second run, with amended data for GSP

Group GY. The ISR Agent sends another Type 1 Daily Profile

Coefficient file to the Data Collector; this file contains the same data



for GSP Groups GW and GX as in the first Type 1 file, but with

revised data for GSP Group GY. The run number is different to that

of the first run;

3. After the ISR Agent sends the revised Type 1 file, the Data Collector

begins operating in another GSP Group, GZ. The ISR Agent

subsequently performs another run, and sends to the Data Collector a

Type 2 Daily Profile Coefficient file, with data only for the new GSP

Group, GZ. The run number is the same as that of the first run.

You can load one Daily Profile Coefficient file (this will be the usual case),

or all Daily Profile Coefficient files.

Loading Individual Daily Profile Coefficient Files

The Daily Profile Coefficient files must be loaded in ascending

Settlement Date order for a given originating ISR Agent, ie. there

must be at least one Daily Profile Coefficient file from this ISR Agent

already loaded for the previous Settlement Date. There are three

exceptions to this:

if the Daily Profile Coefficient file is the first to be received;

if there is already a Daily Profile Coefficient file loaded for the

same Settlement Date, implying a revised Daily Profile

Coefficient file.

if the ISR agent is loading data for the first time from any

participant.

Each Daily Profile Coefficient file must also be loaded in correct run

number sequence for the same originating ISR Agent and Type (1 or

2), (the run numbers are shown on the form). For Type 1 files, there

cannot be any Type 1 files already loaded for the same Settlement

Date with a higher run number. Additionally, the system rejects files

containing DPCs for Scottish GSP Groups for Settlement Dates before

the BETTA Start Date unless the files are from the Scottish ISR

Agent. It also rejects files containing DPCs for Settlement Dates on

or after the BETTA Start Date if the files are from the Scottish ISR

Agent. Appropriate error messages are written to the Exception

Report file if these checks fail. For Type 2 files, there cannot be any

Type 2 files already loaded for the same Settlement Date and same

GSP Group with a higher run number.

These rules ensure that files are loaded in Settlement Date order, and

that when revised files are received, older files do not overwrite more

up-to-date versions.

Loading Multiple Daily Profile Coefficient Files

The system attempts to load the Daily Profile Coefficient files in

ascending Settlement Date order for each originating ISR Agent.

If there are multiple files for the same Settlement Date, and there is

one or more Type 1 files, then the system attempts to load the Type 1

file with the highest run number first. The system then attempts, for

each GSP Group Id, to load the Type 2 file that has the highest run



number. Upon completion of the loading process, if there are any

Type 1 or Type 2 files that have not been processed because they did

not have the highest run number (within a GSP Group for Type 2

files), they are marked as being processed to avoid being displayed

again via the Process Data Files form, and via the Identify Input Files

form, and remain in the File Store directory.

By default, Daily Profile Coefficients are loaded for all effective Standard

Settlement Configurations. If you do not wish to load Daily Profile

Coefficient files for particular values of Standard Settlement Configurations,

you can use the Specify Standard Settlement Configuration form prior to

performing the load. See section 9 for further information. Note that Daily

Profile Coefficients for which Standard Settlement Configurations have not

been set up in the EAC/AA database are, by default, loaded when you

initiate the Load Daily Profile Coefficient process via the Process Data Files

form.

5.1 Load a Selected Daily Profile Coefficient

1. Select a record from the table;

2. Click on the Process button.

If the Daily Profile Coefficient file is a Type 1 file:

data contained in such a file replaces and invalidates any previous

data with the same Settlement Date and Market Participant Id;

the number of Annualised Advances already calculated from the set

of Daily Profile Coefficients being replaced, is displayed in the

Load Daily Profile Coefficient Control Report, (see Appendix

.1B.8 for an example);

the file is rejected if:

a) its run number is not the highest sequence number of available

type 1 files, and is left in the File Store directory, but marked as

processed.

b) it contains data for Scottish GSP Groups for a Settlement Date

prior to the BETTA Start Date, and has been sent by an agent

other than the Scottish IAR Agent.

c) it contains data for a Settlement Date on or after the BETTA

Start Date, and has been sent by the Scottish IAR Agent.


data contained in such a file does not replace or invalidate any

previous data stored against the same GSP Group and Settlement

Date;

if no data exists in the database for the GSP Group and Settlement

Date, the Daily Profile Coefficients are appended to the existing set

of data for the Settlement Date; otherwise the Daily Profile

Coefficient file is not processed and an exception report is

generated (Appendix .2B.9 includes an example of this report);





type 2 files, or another type 2 file for the same GSP Group and

Settlement Date already exists. The file remains in the File

Store directory, but is marked as processed.






For Type 1 and Type 2 files:

if the Daily Profile Coefficient file is not found, processing is

aborted, and an exception report is produced;

if a Daily Profile Coefficient file fail to load, an exception report is

generated:

if the file fails to load because there is no data for the previous

Settlement Date, an exception report is generated with an

appropriate error message, (see Appendix A); the file’s status is

reset to null so that it can be re-loaded once the previous

Settlement Date’s data has been successfully loaded;

if the file fails to load because a file for the same Settlement

Date and a higher run number (and GSP Group for type 2 files)

has already been loaded, an exception report is generated with

an appropriate error message, (see Appendix A); the file’s status

is set to Failed;

if the file originates from the SVA Agent for a Settlement Date

prior to BETTA and contains coefficients for Scottish GSP

groups, an exception report is generated with an appropriate

error message, (see Appendix A); the file’s status is set to

Failed;

if the file originates from the IAR Agent, for a Settlement Date

on or after BETTA, an exception report is generated with an


set to Failed;

a Daily Profile Coefficient Control Report is produced, showing a

count of the number of Daily Profile Coefficients loaded. See

Appendix .1B.8 for an example of this report;

any negative Daily Profile Coefficients are reported in a Control

Report.

5.2 Load all Daily Profile Coefficients

1. Click on the Process All DPC button.




data contained in such a file replaces and invalidates any previous

data with the same Settlement Date and Market Participant Id;

the number of Annualised Advances already calculated from the set

of Daily Profile Coefficients being replaced, is displayed in the

Load Daily Profile Coefficient Control Report, (see Appendix

.1B.8 for an example);



type 1 files for a given originating ISR Agent. The file remains

in the File Store directory, but is marked as processed.







data contained in such a file does not replace or invalidate any

previous data stored against the same GSP Group and Settlement

Date;

if no data exists in the database for the GSP Group and Settlement

Date, the Daily Profile Coefficients are appended to the existing set

of data for the Settlement Date; otherwise the Daily Profile

Coefficient file is not processed and an exception report is

generated (Appendix .2B.9 includes an example of this report);



type 2 files. The file remains in the File Store directory, but is

marked as processed.






For Type 1 and Type 2 files:

if the Daily Profile Coefficient file is not found, processing is

aborted, and an exception report is produced;

if any Daily Profile Coefficient files fail to load, an exception

report is generated:

if a file fails to load because there is no data for the previous

Settlement Date, an exception report is generated with an

appropriate error message, (see Appendix A); the file’s status

remains unchanged so that it can be re-loaded once the previous

Settlement Date’s data has been successfully loaded;



if a file fails to load because a file for the same Settlement Date

and a higher run number (and GSP Group for type 2 files) has

already been loaded, an exception report is generated with an


set to Failed. The status of subsequent files is set to null, so that

once the problem with the failed file has been resolved, the later

files can be re-loaded, (this occurs regardless of the reason for

the failure of the file);

if the file originates from the SVA Agent for a Settlement Date

prior to BETTA and contains coefficients for Scottish GSP

groups, an exception report is generated with an appropriate

error message, (see Appendix A); the file’s status is set to

Failed. The status of subsequent files is set to null, so that once

the problem with the failed file has been resolved, the later files

can be re-loaded, (this occurs regardless of the reason for the

failure of the file);

if the file originates from the IAR Agent, for a Settlement Date

on or after BETTA, an exception report is generated with an


set to Failed. The status of subsequent files is set to null, so that

once the problem with the failed file has been resolved, the later

files can be re-loaded, (this occurs regardless of the reason for

the failure of the file);

a Daily Profile Coefficient Control Report is produced, showing a

count of the number of Daily Profile Coefficients loaded. See

Appendix .1B.8 for an example of this report;

if one Daily Profile Coefficient file fails to load, no further files are

loaded;

any negative Daily Profile Coefficients are reported in a Control

Report.

5.3 Field Summary

Field Details

GSP Group Unique identifier of the GSP Group. This is blank for Type 1

files.

Settlement Date The settlement date for the data file

Content Identifies the subject of a Data File. For Daily Profile

Coefficient files, the Content is Daily Profile Coefficients

Run Number The version of the data file

Time Stamp The date on which the file was created by the ISR Agent

Source The source of the data file. For Daily Profile Coefficient files,

the Source is ISR Agent

Filename The name of the Daily Profile Coefficient file

All File Types Option button for displaying all files when used with the query

functionality

EAC Files Not applicable for this function

DMA Files Not applicable for this function



Field Details

DPC Files Option button for displaying only Daily Profile Coefficient

files when used with the query functionality

5.4 Differences in Automatic Mode

In Automatic Mode, there is no Process Data Files Form but control and

exception reports are still produced, and the information about Type 1 files,

Type 2 files and the order of loading still applies.

In Automatic Mode, files are usually processed one at a time, as they arrive,

unless they cannot be processed, because a settlement date is missing. For

example, if the data is already in the database for 1st September 1998 and

then files arrive for subsequent dates in this order:

04/09/98

03/09/98

02/09/98

then the file for 03/09/98 and 04/09/98 will not be loaded until the file for

02/09/98 has arrived. The control report for 04/09/98 will report that the file

was not loaded. The control report for 03/09/98 will report that the 03/09/98

file was not loaded. The control report for 02/09/98 will report the loading

of all three files.



6 Calculate EAC/AA





This form enables you to initiate the calculation of Annualised Advances

(AAs) and Estimated Annual Consumptions (EACs) for a file of Meter

Advances that has been received from a Non-Half Hourly Data Collector.

In automatic mode there are control and exception reports.

Figure 6.1: The Process Data Files Form


unprocessed files:


EAC/AA Request;






field content using standard Oracle query functionality.


option buttons and execute a query:


EAC Files, to display only EAC/AA Request files;

DMA Files, to display only Deemed Meter Advance files (these are

not applicable for this function);

DPC Files, to display only Daily Profile Coefficient files (these are

not applicable for this function).

6.1 Initiate Calculation of EAC/AA

1. Select an EAC/AA Request file from the table;


For any non-fatal errors an error message is raised in the control file and the

next Metering System in the data file is processed. The whole data file is

only rejected if a fatal error is encountered.

If the calculation completes successfully, the output file is created in the

Output file store.

A machine-readable exception file is created in the Machine-readable

reports store (even if there are no exceptions). It contains details of any

exceptions.

A machine-readable EAC/AA Tolerance Values exception report is created

in the Machine-readable reports store (even if no Annualised Advances are

outside the tolerance values). It contains details of any Annualised

Advances that are outside the tolerance values for the Profile Class and GSP

Group.

If there has been a change of Profile Class for the Metering System during

the Meter Advance Period, an Annualised Advance only is calculated.

If the EAC/AA Request File is not found, then this is recorded in the

exception report.

The number of Annualised Advances calculated for the Daily Profile

Coefficients is incremented and is shown in the control report.

A human-readable control report provides the following information (see

Appendix .1B.3 for an example):

all negative values of Meter Advances, AA and Daily Profile

Coefficients;

the Meter Advance read from the file is non-zero and Fraction of

Yearly Consumption is calculated to be zero (in this case the value

of the AA is recorded as zero).

The following information is provided in the control report and in the

exception report :



no Daily Profile Coefficients matching the details in the file could

be found;

a Daily Profile Coefficient file, with Settlement Date matching the

Meter Advance Period, cannot be found;

all unprocessed Metering Systems with an Advance Period greater

than 2 years.

the total number of Metering Systems for which a negative EAC

has been replaced by the default EAC.

The following information is provided in the control report and in the

EAC/AA Tolerance Values exception report :

all Annualised Advances that are outside the tolerance values for

the metering system’s Profile Class and GSP Group.

When the user displays or prints the exception report for the first time, the

system generates a human-readable exception report from the machine-

readable exception report. The control report is produced in human-

readable format in the first place. See Appendix .1B.3, Appendix .2B.4

and Appendix .3B.5 for examples of the control report, the human-readable

exception report and the human-readable EAC/AA Tolerance Values

exception report.

6.2 Field Summary

Field Details

GSP Group Unique identifier of the GSP Group


Content Identifies the subject of a Data File. For calculation of

EAC/AA, the Content is EAC/AA Request File


Time Stamp The date on which the request file was created by the Non-Half

Hourly Data Collector

Source The source of the data file. For EAC/AA Request files, the

source is Non-HH Data Collector

Filename The name of the EAC/AA Request file


functionality

EAC Files Option button for displaying only EAC/AA Request Files when

used with the query functionality

DMA Files Not applicable for this function

DPC Files Not applicable for this function

6.3 Differences in Automatic mode

In Automatic Mode the EAC/AA calculation occurs automatically but there

are control and exception reports.



7 Determine Deemed Meter Advance





This form enables you to calculate Deemed Meter Advance based on data

received from a Non-Half Hourly Data Collector, in the event of a change of

Supplier for a Metering System, where the existing Supplier and new

Supplier cannot agree a changeover meter reading.

Figure 7.1 :The Process Data Files Form


unprocessed files:


EAC/AA Request;




field content using the standard Oracle query functionality.




relevant option buttons and execute a query:


EAC Files, to display only EAC/AA Request files (these are not

applicable for this function);

DMA Files, to display only Deemed Meter Advance files;

DPC Files, to display only Daily Profile Coefficient files (these are

not applicable for this function).

7.1 Initiate Calculation of Deemed Meter Advance

1. Select a Deemed Meter Advance Request file from the table;


For any non-fatal errors an error message is raised in the control file and the

next Metering System in the data file is processed. The whole data file is

only rejected if a fatal error is encountered.

If the calculation completes successfully, the output file is created in the

Output file store.

A Deemed Meter Advance Control Report is produced (see Appendix

.4B.6).

An exception report is produced when, for a combination of an effective

GSP Group, Profile Class, Standard Settlement Configuration and Time

Pattern Regime, there are no Daily Profile Coefficient files with any

Settlement Date within the Meter Advance Period. See Appendix .5B.7 for

an example.

An exception report is also generated when there are no Daily Profile

Coefficient records for the Settlement Date.

Other circumstances under which an exception report is produced are

indicated by the error messages that may appear in the DMA exception

report. See Appendix A for a list of these error messages.

7.2 Field Summary

Field Details



Content Identifies the subject of a Data File. For determining Deemed

Meter Advance, the Content is:

Deemed Meter Advance Request File


Time Stamp The date on which the request file was created by the Non-Half

Hourly Data Collector

Source The source of the data file. For Deemed Meter Advance

Request files, the source is Non-HH Data Collector

Filename The name of the Deemed Meter Advance Request file



Field Details


functionality

EAC Files Not applicable for this function

DMA Files Option button for displaying only Deemed Meter Advance

Request file

DPC Files Not applicable for this function

7.3 Differences in Automatic mode

In Automatic Mode the calculation of Deemed Meter Advance occurs

automatically but there are control and exception reports.



8 Ad Hoc Deemed Meter Reading

This form which is used to perform an Ad Hoc Deemed Meter Reading

Calculation. The input data for the calculation is entered on the form, and

the results of the calculation are then displayed on the form. The calculation

is performed by a batch process initiated via the scheduler. The status of a

submitted calculation can be monitored by viewing its status as displayed on

the form.

There is also a form that is used to initiate an audit report which contains

details of past Ad Hoc Deemed Meter Reading Calculations. This audit

report is a batch process initiated via the scheduler.

Figure 8-1 Ad Hoc Deemed Meter Reading Calculation Form.

When the form Ad Hoc DMR Calculation form is first loaded the form is

blank and in insert mode.

8.1 Initiate Calculation of Deemed Meter Reading

In order to enter the details for a new Ad Hoc Deemed Meter Reading,

please make sure that the forms data entry fields are all empty. If this is not

the case, use the Clear Form button to set the data entry fields to writable

and to clear any existing data.

Should a new Ad Hoc Deemed Meter Reading calculation be required that

is based on an existing calculation, display the existing calculation

transaction and use the Modify button to set the data entry fields to writable



and clear the results fields only. It is then possible to modify the existing

input data and to submit the modification as a new calculation transaction.

The following data is required to successfully submit a new DMR

calculation:

Metering system ID

SSC Id

GSP Group Id

Deemed date (Must be in the past)

First and second meter reading details and their associated TPR and

register details.

At least one Profile Class.

An effective from date for each Profile Class entered.

Once the required details are entered, use the Calculate button to submit the

data for processing. The results will be displayed once the batch process

has completed the calculation and the transaction results are available for

display.

Note, if the user presses the Modify or Clear buttons in the period between

submission and batch process completion, then the results of the calculation

will not be automatically displayed and it will be necessary to retrieve the

results in ‘Enter Query’ mode using appropriate search criteria. For more

information please refer to section 8.1.1 Viewing Submitted

CalculationsViewing Submitted Calculations.

Negative advances.

Where the second meter reading is less than the first meter reading, a

register rollover is assumed. The Rollover checkbox will automatically

check itself when this situation arises. Note that in order to achieve a

genuine negative advance it will be necessary to uncheck the rollover box

after entering the values for readings one and two.

Metering Systems with non-standard “multiplier”.

Metering systems which have a "multiplier" with a value other than 1 are

those where the registers measure in some other unit instead of

kWh. Therefore the AA values are calculated in units other than kWh.

Profile Class tolerances do not apply in these instances, and warnings may

be produced where none are expected or may not be forthcoming when they

are expected.



8.1.1 Viewing Submitted Calculations

If the user selects the Enter Query button on the tool bar, the form may be

used to retrieve details of an existing Deemed Meter Reading calculation by

using the forms input fields as search criteria.

The Ad Hoc DMR Calculation form is then used to view a previously

submitted Deemed Meter Reading calculation, with field details displayed

according to the calculations status and calculation result. Note that the most

recent calculation will be displayed if no criteria are entered.

Where there are errors associated with a calculation, these will be displayed

in the register detail section of the form. To view more detail for specific

errors, highlight the register associated with the error message in the

Register Detail section and press the TPR errors button. Error details

displayed will be the error or warning severity and a full description of the

warning or error.

Figure 8-2 Ad Hoc Deemed Meter Calculation Warnings and Errors Form

Use the Close button to close the Ad Hoc DMR Calculation Warning and

Errors form and return to the Ad Hoc Deemed Meter Reading Calculation

Form.



8.1.2 Field Summary

Field Details

Metering System Details

Metering System Id Unique identifier of the Metering System.

SSC Id Standard Settlement Configuration identifier.

GSP Group Id Unique identifier of the GSP Group

Deemed Date The date for the Deemed Meter Reading

Transaction Number Read only field. Contains an identifier for the Deemed Meter

Reading Calculation.

Status Read only. The status of the Deemed Meter Reading

calculation. Possible statuses are:-

Requested

In-progress

Application Success

Application Warning (Completed with warnings)

Application Error (Business error(s) prevented successful completion)

Fatal Error (An Oracle error occurred)

Profile Class Details

Profile Class Profile Classes that apply to the Deemed Meter Reading MAP.

Effective From Date The start dates for the Profile Classes that apply to the Deemed

Meter Reading MAP.

Register Details

TPR Time Pattern Regime for a register in the Metering System

Reg ID Register ID for a register in the Metering System

Register Digits The number of digits for the identified meter register.

1st Reading Top row:- Date of the first meter reading used to calculate the

Deemed Advance.

Register rows:- Register reading for the identified meter

register for the first meter reading date.

2nd

Reading Top row:- Date of the second meter reading used to calculate

the Deemed Advance.

Register rows:- Register reading for the identified meter

register for the second meter reading date.

Rollover This checkbox is ticked if there was a register rollover between

the first and second meter register reading.

Deemed Reading Read only field. The calculated deemed meter register reading.

Warning/Error Read only field. Notification of any warnings or errors

associated with the deemed meter register reading. Details are

displayed in Warnings/Errors.

Warnings/Errors

Severity Read only. Severity of each error or warning associated with a

deemed register advance selected from the Register Details.

Possible values:-

‘W’ Warning

‘E’ Error

Error Description Read only. Full description of each error or warning associated

with a deemed register advance selected from the Register



Field Details

Details..

8.2 Initiate Deemed Meter Reading Audit Report

Figure 8-3 Ad Hoc Deemed Meter Reading Audit Report Form.

This form is used to initiate an Ad Hoc Deemed Meter Reading Audit

Report that matches the criteria entered by the user. Note that a minimum

entry of one of a Metering System Id, Calculation Date or Transaction

Number must be entered, and that when using the range criteria, only one of

the Calculation Date, Deemed Read Date and Transaction Number may be

used at any time.

Once the required details are entered, the Report Button is used to submit

the report request.

8.2.1 Field Summary

Audit Report Criteria

Metering System Id Unique identifier of the Metering System.

SSC Id Standard Settlement Configuration identifier.

GSP Group Id Unique identifier of the GSP Group



Username User name of the user who submitted the Deemed Meter

Reading transactions to be reported on.

Calculation Date From: Start date for a range of Calculation Dates to be reported

on.

To: End date for a range of Calculation Dates to be reported on.

If this value is left blank then a single day range is set to the

date entered as the From date.

Deemed Read Date From: Start date for a range of Deemed Read Dates to be

reported on.

To: End date for a range of Deemed Read Dates to be reported

on.

If this value is left blank then a single day range is set to the

date entered as the From date.

Transaction Number From: Start of a range of Transaction Numbers to be reported

on.

To: End of a range of Transaction Numbers to be reported on.

If this value is left blank then a single transaction is set to the

transaction entered as the From Transaction Number.



9 Maintain Standard Settlement Configurations

This form enables you to maintain values of Standard Settlement

Configurations and specify whether Daily Profile Coefficients should be

loaded for those values.

Standard Settlement Configuration files are loaded automatically by the

EAC/AA system upon receipt of the files from a Non-Half Hourly Data

Collector.

Once loaded, Standard Settlement Configurations can be amended and

deleted. New Standard Settlement Configurations can be created.

Upon accessing the Maintain Standard Settlement Configuration form,

execute a query to display all loaded Standard Settlement Configurations.

The Don’t Load Daily Profile Coefficients check box is checked by default

and the individual Don’t Load DPC check boxes are unchecked. Refer to

section 9.4 for further information about these check boxes.

Figure 8.1:The Maintain Standard Settlement Configuration Form

9.1 Add a New Standard Settlement Configuration

1. Click on the Insert Record button;

2. Type in the Standard Settlement Configuration Id and Description.

Note that the Standard Settlement Configuration is not added to the database

until you commit the change.



9.2 Delete a Standard Settlement Configuration

1. Navigate to the Standard Settlement Configuration that you want to

delete;

2. Click on the Delete Record button.

Note that the Standard Settlement Configuration is not deleted from the

database until you commit the change.

9.3 Amend a Standard Settlement Configuration

1. Edit the required Standard Settlement Configuration description.

Note that the Standard Settlement Configuration value cannot be amended.

Any changes to a Standard Settlement Configuration are not applied to the

database until you commit them.

9.4 Identify SSCs for which Daily Profile Coefficients will not be loaded

When you load Daily Profile Coefficients into the EAC/AA system via the

Process Data Files form (see section 5 for further information), Daily Profile

Coefficients are loaded for all effective Standard Settlement Configurations.

You can use the Maintain Standard Settlement Configuration form to

identify Standard Settlement Configurations (which exist in the EAC/AA

database) for those Daily Profile Coefficients which are not to be loaded.

Upon entry to the form, the Don’t Load Daily Profile Coefficients check

box defaults to checked, and the individual Don’t Load Daily Profile

Coefficient check boxes default to un-checked. By un-checking and

checking the Don’t Load Daily Profile Coefficients check box, the

individual check boxes are all checked, implying that Daily Profile

Coefficients will not be loaded for the displayed Standard Settlement

Configurations when the user invokes the load operation.

1. Use standard Oracle query functionality to display the required

Standard Settlement Configurations;

2. Click on the Don’t Load Daily Profile Coefficients button twice.

The Load DPC check boxes of all displayed Standard Settlement

Configurations are checked. When you next load Daily Profile Coefficients,

any Daily Profile Coefficients with the checked Standard Settlement

Configurations will not be loaded.

Alternatively, check individual Standard Settlement Configurations using

the individual check boxes.

Note that Daily Profile Coefficients for which Standard Settlement

Configurations have not been set up in the EAC/AA database are, by

default, loaded when you initiate the Load Daily Profile Coefficient process

via the Process Data Files form.

9.5 Field Summary

Field Details

Standard Settlement Unique identifier for a Standard Settlement Configuration



Field Details

Configuration

Description A description of the configuration used

Don’t Load DPC A flag to indicate whether Daily Profile Coefficients associated

with the Standard Settlement Configuration are to be loaded

into the system

Don’t Load Daily

Profile Coefficients

If this is checked, then the DPC column for all displayed

Standard Settlement Configurations is set to checked



10 Identify Input Files used in Calculations

This form allows you to identify the Daily Profile Coefficient files

(including archived Daily Profile Coefficients, where DPCs have arrived

from a single Settlement Agent) used in calculations of EAC/AA and

Deemed Meter Advance. For the situation where multiple Settlement

Agents have supplied Daily Profile Coefficient files for a particular

calculation (as possible under BETTA), this form will show the most

recently loaded DPC file, irrespective of Settlement Agent.

If you need to identify the run time of a particular calculation run, you can

refer to the header of the associated control report. Refer to Appendix B for

examples of these control reports. Refer to the EAC/AA System

Management Guide for details of report locations.

Figure 9.1:The Identify Input Files Form

10.1 Display the Input Files

1. In query mode, enter all the following criteria:

Effective From Settlement Date for the Meter Advance Period;

Effective To Settlement Date for the Meter Advance Period;

Date and Time of Calculation.

2. Click on the Execute Query button.



The form displays details of the Daily Profile Coefficient files that have

been used in performing the calculation (in accordance with the description

above).

The Latest Loaded check box is checked for any files that are the latest

loaded for the corresponding Settlement Date.

10.2 Field Summary

Field Details

Advance Period Date

From

A settlement date from which to begin the search, in the format

DD/MM/YYYY

Advance Period Date To A settlement date at which to end the search, in the format

DD/MM/YYYY

Date and Time of

Calculation

The date and time of the calculations. This must be in the

following format:

DD/MM/YYYY HH:MI

Settlement Date The settlement date for the file



Date and Time The date on which the file was created by the external

organisation

Source The source of the data file

Filename The name of the Daily Profile Coefficient file

Latest Loaded This check box will be ticked if the Daily Profile Coefficients

file is the latest loaded in the EAC/AA system



11 Specify Smoothing Parameter

This form can be used to browse and maintain Smoothing Parameters

received from a Non-Half Hourly Data Collector.

Users logged on using the EAC/AA System Operator role are only able to

browse the Smoothing Parameters. Users logged on with the EAC/AA

Operations Supervisor role can maintain the Smoothing Parameters.

Figure 10.1:The Smoothing Parameters Form

11.1 Create New Smoothing Parameter

1. Enter Smoothing Parameter and Effective from Settlement Date.

The Effective From Settlement Date cannot be prior to a Settlement Date for

which Daily Profile Coefficients have been loaded.

The Smoothing Parameter value must be positive.

Note that the Smoothing Parameter is not added to the database until you

commit the change.

Creation of Smoothing Parameters is recorded in the Audit Log. Refer to

the EAC/AA System Management Guide for details of the Audit Log.

11.2 Update Smoothing Parameter

1. Select the required Smoothing Parameter. To view a subset of all

Smoothing Parameters according to Settlement Date, you can use



standard Oracle query functionality. For example, to display

Smoothing Parameters that are effective after 01/02/1997, in query

mode, enter >01/02/1997 in the Settlement Date From field, and

execute a query;

2. Amend the Smoothing Parameter value; the Effective From

Settlement Date cannot be changed.

The Settlement Date From cannot be amended to a Settlement Date prior to

that for which Daily Profile Coefficients have been loaded.

The change is not updated to the database until you commit the change.

Amendments to Smoothing Parameters are recorded in the Audit Log.

Refer to the EAC/AA System Management Guide for further information.

11.3 Delete Smoothing Parameter

1. Select the required Smoothing Parameter. To view a subset of all

Smoothing Parameters according to Settlement Date, you can use

standard Oracle query functionality. For example, to display

Smoothing Parameters that are effective after 01/02/1997, in query

mode, enter >01/02/1997 in the Settlement Date From field, and

execute a query;

2. Click on the Delete Record button.

The Smoothing Parameter can be deleted only if Daily Profile Coefficients

have not been loaded for a Settlement Date on or after the Settlement Date

From corresponding to the Smoothing Parameter.

A Smoothing Parameter cannot be deleted if the Daily Profile Coefficients

have been archived for the effective to date (indicated by the Settlement

Date From of the subsequent Smoothing Parameter).

Note that the Smoothing Parameter is not deleted from the database until

you commit the change.

Deletions of Smoothing Parameters are recorded in the Audit Log. Refer to

the EAC/AA System Management Guide for further information.

11.4 Field Summary

Field Details

Settlement Date From The Settlement Date from which the corresponding Smoothing

Parameter is effective, in the format DD/MM/YYYY

Value Value of the Smoothing Parameter, with maximum of 6 digits,

including 3 decimal places



12 Report on Profile Coefficients

Use this form to request a report on Daily Profile Coefficients held in the

EAC/AA database.

Figure 11.1: The Report on Daily Profile Coefficients Form

1. Enter the criteria for the report. Note that the Settlement Date From and

Settlement Date To fields are mandatory. All other fields are optional

and may be left blank;

2. Click on the Report button to schedule the report.

The report will be created in the Report file store.

An example report is given in Appendix .1B.1.

12.1 Field Summary

Field Details

Settlement Date From The lower range of Settlement Date for which the report is

required, in the format DD/MM/YYYY

Settlement Date To The upper range of Settlement Date for which the report is

required, in the format DD/MM/YYYY

GSP Group The GSP Group Id within the Settlement Date range for which

the report is required

Profile Class The Profile Class Id within the Settlement Date range for

which the report is required



Field Details

Standard Settlement

Configuration

The Standard Settlement Configuration Id within the

Settlement Date range for which the report is required

Time Pattern The Time Pattern Regime Id within the Settlement Date range

for which the report is required



13 Display Latest Settlement Date for Profile Coefficients

This form displays, for each GSP group in the EAC/AA system, the latest

Settlement Date for which Daily Profile Coefficients have been loaded.

The GSP groups and latest Settlement Dates are displayed when you select

this option from the menu.

Figure 12.1: The Latest Settlement Date For Daily Profile Coefficients Form

13.1 Field Summary

Field Details

GSP Group The GSP group

Latest Settlement Date The latest Settlement Date for which Daily Profile Coefficients

have been loaded into the EAC/AA system



14 Archive Daily Profile Coefficients and Smoothing Parameters

The form below can be used to archive to tape all Daily Profile Coefficients

and superseded Smoothing Parameters up to a specified Settlement Date.

It is envisaged that Daily Profile Coefficients and superseded Smoothing

Parameters will be archived approximately 25 months after the latest

settlement date.

The volume of data to be archived is expected to be approximately 1.08

Gigabytes. Thus, you should ensure that the tape media has sufficient

capacity to store the archived data.

Figure 13.1 The Archive Daily Profile Coefficients Form

1. Enter Settlement Date To, the date up to which Daily Profile

Coefficients and Smoothing Parameters will be archived;

2. Click on the Archive button to schedule the archive.

If no Daily Profile Coefficients or Smoothing Parameters are found prior to

the date entered, you are prompted to enter another date.

If the date entered is less than two years prior to the latest settlement date, a

warning is displayed, but you can continue the operation.

If valid Daily Profile Coefficient and Smoothing Parameter data is found,

you are prompted to insert a tape into the tape drive. The data to be

archived to tape is written in a report format ready for archive to the tape.



The report is placed in the Archive Store directory prior to transfer to tape

storage and deletion of data from the database.

Once the archive process has been initiated via the form, details are passed

to the scheduler. When the scheduler starts up the process, the Daily Profile

Coefficients, Smoothing Parameters and Data Files database tables are

locked, until the process is complete.

A maximum of three attempts are made to write the report to the tape.

If a failure is encountered at any stage of the archive process prior to

deletion of the archived data from the database, then the process terminates

and the archive report is deleted. A message is inserted in the job log.

If the data is successfully written to the tape, the report is deleted from the

Archive Store directory, and the database records that have been archived

are deleted.

Note that the details of the tape to which Daily Profile Coefficients are

archived is not maintained by the EAC/AA system. Procedures should be

put in place to ensure that the media is appropriately labelled.

A rewind or non-rewind tape device can be used to perform this operation.

If a non-rewind device is used, the tape must be rewound using operating

system commands prior to restoring the data in report format using the

Report on Archived Data form. If a rewind device is used, previously

archived files will be overwritten if multiple archives are performed to the

same tape.

14.1 Field Summary

Field Details

Settlement Date To The Settlement Date up to which Daily Profile Coefficients and

superseded Smoothing Parameters will be archived



15 Restore a Report on Archived Daily Profile Coefficients

This form allows you to generate a report of archived Smoothing Parameters

and Daily Profile Coefficients for a specified Settlement Date.

Figure 14.1:The Report on Archive Data Form

1. Enter a Settlement Date in the following format:

DD/MM/YYYY

2. Click on the Report button.

If archived Daily Profile Coefficient files with a Settlement Date matching

the date entered exist, then a prompt is displayed for you to insert the tape

containing the archived data into the tape drive. A maximum of three

attempts are made to read the data from the tape. Note that when using a

tape, the tape must be rewound to the start.

If the restore is successful, the Report on Archived Data is retrieved from

the tape into the Reports store, from where it can be examined.

Note that the archived data is not restored into the EAC/AA database.

If no Daily Profile Coefficient files with a matching Settlement Date exist,

then an empty report is produced.

An example of the report produced is included in Appendix B.



15.1 Field Summary

Field Details

Settlement Date The Settlement Date for which to create a report on archived

Daily Profile Coefficients and Smoothing Parameters



16 Maintain User

This section provides information on maintaining user accounts and

password change for both the System Manager who has control over all

accounts, and for the system user who may change only their own password.

16.1 Manage User Accounts

This form is available to users with the user role of system manager only. It

allows the user to view user account details for a selected user and to make

changes to the user’s account where required. The form also allows the user

to add users to the system, or to drop a selected user.

Figure 16-1 Maintain User - View User Details

Upon opening the Maintain User form, the System Manager is presented

with a list of existing users as well as the details of the first user listed

displayed in the Account Details section. To select a different user and

display their details, move the cursor to any of the listed users.



Figure 16-2 Maintain User - Create/Edit User details

Create a new user.

Press the Create User button on the Maintain User - View User Details

form. A blank Maintain User – Create/Edit User Details form is displayed.

Enter your password to confirm your System Manager role, and then enter

the user’s details and initial password, together with the user roles required

for that user. Press the Save button and the new user will be created.

Note:- You may wish to create new users with expired passwords, so that

they are forced to change their passwords on first logon.

Edit an existing user.

Select the user to edit by placing the cursor in the user’s username on the

Maintain User - View User Details form and then press the Edit User button

on that form. The Maintain User – Create/Edit User Details form is

displayed, populated with the chosen user’s details. Enter your password to

confirm your System Manager role. After this, these details can then be

edited. When the edit has been completed, press the Save button and the

amended user details will be saved.

An account may be locked, either by the System Manager setting the

Account Locked checkbox, or by a user exceeding the allowed number of

failed login attempts. The System Manager may unlock the account by

clearing the Account Locked checkbox.



Drop an existing user.

Select the user to be dropped in the Maintain User – View User Details form

and press the Drop User button. After a confirmation, the user will be

dropped. Note that a System Manager cannot drop his own user account or

the account of a user who is currently logged in. The Sys, System and other

standard Oracle users cannot be dropped.

16.2 Change of Password

A user can change their password at any time by using the change password

form from the action menu. If a password has expired either by becoming

stale dated or by being marked as expired by a System Manager, the user

will be asked to change their password at login before being allowed to

continue. At login the form used will be the standard Oracle Change User

Password dialogue box, however if the user has an expired password, and

presses the Cancel button, then the user will be logged out and the

application closed. User initiated password changes use a password form

modelled on the Oracle Change User Password dialogue box shown in

Figure 16-3 Change User Password.

Figure 16-3 Change User Password

When this form is displayed the user is required to enter their old password

to confirm their identity and then is required to type in a new password.



This password must be six or more characters long. The user is then

required to confirm the new password by entering it into the Retype New

Password field. Pressing the Change Password button will then change the

user’s password. The user may abort the process at any time prior to its

completion by pressing the cancel button.

16.3 Field Summary

Field Details

Users

User Existing users set up on the system.

Account Details (View User Details)

Username Read only. The username for which Account Details are being

displayed.

Account Status Read only. The Account Status for the Username displayed.

Password Expiry Date Read only. The Password Expiry Date for the Username

displayed

Checkboxes Read only. Ticked for the roles applied to the username

displayed. See Roles section of this table.

System Manager

Your Password The password of the System Manager using the form.

Concealed with asterisks, must be entered to be able to save

any changed made on the form.

Account Details (Create/Edit User details)

Username The username for which Account Details are being changed.

Note this field is blank and enterable only when a new user is

being added.

New Password Used to provide an existing or new user with a new password

Retype New Password Required to check the password entry in the New Password

field.

Account Status

Account Locked Ticked when an account is locked. Used to lock and unlock an

account.

Password Expired Checked for an expired password. Can be used to expire a

password early and force a user to change their password.

Roles

System Operator Tick this checkbox to grant this role to the selected user.

Operations Supervisor Tick this checkbox to grant this role to the selected user.

Systems Manager Tick this checkbox to grant this role to the selected user.

EAC/AA Auditor Tick this checkbox to grant this role to the selected user.

Change Password

Old Password The user’s current password

New Password The user’s new password to replace the current password

Retype New Password Required to check the password entry in the New Password

field.



17 Browse GSP Group Profile Class Default EAC

This form can be used to browse GSP Group Profile Class Default EAC

received from ELEXON.

Users logged on using the EAC/AA System Operator and Operations

Supervisor roles are only able to browse the GSP Group Profile Class

Default EAC details.

Figure 17.1: The GSP Group Profile Class Default EAC Form

17.1 Field Summary

Field Details

GSP Group ID The GSP Group ID

Profile Class ID The Profile Class ID

Effective From Date The Settlement Date from which the corresponding GSP Group

Profile Class Default EAC record is effective, in the format

DD/MM/YYYY

Effective To Date The Settlement Date To which the corresponding GSP Group

Profile Class Default EAC record is effective, in the format

DD/MM/YYYY

Default EAC Value of the Default EAC Parameter, with maximum of 6

digits, including 3 decimal places



18 Reports

The reports that can be generated by the EAC/AA system fall into two

categories:

User initiated;

Automatically generated.

An example of each report is given in Appendix B.

18.1 User Initiated Reports

User initiated reports, listed below, can be generated on an ad hoc basis by

authorised EAC/AA users, for a set of parameters specified by the user:

Report on Profile Coefficients;

Report on Archived Data.

DMR Audit Report

The Report on Profile Coefficients is described in section 12. This report is

created in the Report file store, the physical location of which is dependent

on system installation and configuration. Refer to the EAC/AA System

Management Guide for guidance on locating and viewing these reports.

The Report on Archived Data is described in section 15. This report is

created in the Report file store, the physical location of which is dependent

on system installation and configuration. Refer to the EAC/AA System

Management Guide for guidance on locating and viewing these reports.

The Report on Archived Data is complete when the End of Report text is

displayed on the last page of the report, (refer to Appendix .2B.2 for an

example). The file name format for the Report on Archived Data is:

R<role><participant_id><settlement date>

The DMR Audit report is described in section 8.2. This report is created in

the Report file store, the physical location of which is dependent on system

installation and configuration. Refer to the EAC/AA System Management

Guide for guidance on locating and viewing these reports.

18.2 Automatically Generated Reports

Control reports are automatically generated when a batch process

completes. Control reports provide information on the batch process, such

as settlement date, number of records processed, and number of records

processed successfully.

The following control reports are generated by the EAC/AA system:

Estimated Annual Consumption/Annualised Advance;

Deemed Meter Advance;

Load Daily Profile Coefficients.

Exception reports are similar to control reports, but with a focus on any

exceptions that have been generated as a result of any processing by the



EAC/AA system. The following exception reports may be generated by the

EAC/AA system:

Estimated Annual Consumption/Annualised Advance;

Deemed Meter Advance;

Load Daily Profiles;

Load Standard Settlement Configuration.

The conditions leading to the generation of exception reports are given in

the relevant sections (5, 6 and 7) above and Appendix A. The conditions

leading to generation of the exception report for loading Standard

Settlement Configurations, is given in section 2.5 and Appendix A. An

example of this report is given in Appendix .2B.9.

18.3 Viewing Reports

You can use the following form to select a report, which has been generated

on the EAC/AA database server, for viewing at your PC or for printing to

your default printer. This form is available from the Reports|Select Reports

menu option. When you request to display or print a particular report for

the first time, the report is copied to the application server; this may take a

while if the report is large, or if other processing is occurring on the

EAC/AA server. Note that the first time you request to display or print an

EAC/AA Calculation Exception Report, EAC/AA Tolerance Values

Exceptions Report, DMR Audit Report, or Report on DPCs, the EAC/AA

database server software must be running; for subsequent displaying or

printing of these reports, the EAC/AA database server software does not

need to be running, as the report exists on the application server.

Please note:- Should a report being viewed inadvertently have spurious

characters saved to its content, there is a possibility that these changes could

appear to persist. This is caused by the Internet Browser redisplaying a

local copy of the displayed report. This can be rectified by adding sufficient

additional change to the report to trigger the browser into refreshing the

report file from the application server after which the report will appear in

its correct state.

Only reports that have a status of ‘completed’ are displayed.



The following EAC/AA reports can be viewed and printed from this form:

EAC/AA Calculation Control Report

EAC/AA Calculation Exception Report

EAC/AA Tolerance Values Exception Report

DMA Calculation Control Report

DMA Calculation Exception Report

DPC Load Control Report



DPC Load Exception Report

Report on DPCs

SSC Load Exception Report

DMR Audit Report

The Report Time is the date and time at which the file was created on the

server.

During installation of the application software, the default viewer for reports

is set to Wordpad. Within Wordpad, the No Wrap option (from the

View|Options) menu should be set, to ensure that the report text does not

wrap.

Note that if you attempt to print or display an EAC/AA Calculation

Exception Report, EAC/AA Tolerance Values Exception Report, DMR

Audit Report, or Report on DPCs for the first time when the EAC/AA

software on the server is not running, the following message will be

displayed, with <no> substituted with the id of the job:

30 Failed to wait for formatting job <no> EAC/AA may not

be running. If this message persists please contact the

System Administrator. Do you wish to continue to wait?

Should this happen, press the OK button to wait longer, or the Cancel button

to give up waiting and return to the Select Reports screen.

Should you experience other unexpected error messages when attempting to

print or display a report, you should ensure that you are using the correct

printer driver for your printer.



Appendix A Status and Error Messages

Error and status messages that may be generated by the EAC/AA

application software are given below. Note that error messages for

underlying products, such as Oracle, are not shown.

Errors and statuses that may be shown in log files are listed in the EAC/AA

System Management Guide.

A.1 Error and Status Messages

This section details the error and status messages that may be displayed.

A.1.1 Error and Status Messages Displayed via the User Interface

The following error and status messages are displayed via the user interface,

either in a message box or at the bottom of forms. Those suffixed with (S)

are status or information messages.

1st Reading date should be less than 2

nd Reading date

Advance From Date must be earlier than Advance To Date (S) All Criteria fields must be specified.(S) All files submitted for processing(S) Archive date is less than 2 years from latest settlement date. Proceed with archive?(S) At Least One Compulsory Field Required: At least one Profile class Effective From Date must be on or before earliest calculation date At least one user role must be selected per user Audit Report Has Been Scheduled(S) Both From and To values are required: Cannot un-tick the Password Expired without entering the New Password Combined number of days spanned by the three dates (DMR Reading 1 and 2) exceeds 730 calendar days. Do you want to continue with Calculation? Compulsory fields do not identify any calculation records: Decimals values are not allowed for Reading Deemed date entered cannot be same as 1

st Reading Date or 2

nd Reading

Date Deemed date must be in the past Deemed Reading Date is expected to be at least 14 days in the past Default Oracle user accounts cannot be dropped

Duplicate Value Found1 Effective From Date must not be greater than Effective To Date Effective To Date must not be less than Effective From Date Error occurred while executing DDL statement. Details are: Exceeded simultaneous SESSIONS_PER_USER limit Failed to Log changes to Audit File Field must be entered File with a higher number already submitted for processing File with a higher run number exists. Please reselect Files for preceding settlement date must be loaded. Format Failed From value must occur before the To value: Incorrect current Password entered Invalid date specified.(S) Invalid GSP Group ID for Deemed Date entered Invalid Metering System Id: checksum error Invalid Profile Class ID for Deemed Date entered

1 OR3571 HD048517

Field Code Changed



Invalid SSC ID for Deemed Date entered Invalid username/password; Logon denied Job already submitted or running.(S) Key is Not currently Valid(S) Loaded DPC files exist from this date onward. Insertion disallowed. Loaded DPC Files exist from this date onwards. Delete disallowed Loaded DPC Files exist from this date onwards. Update disallowed Mandatory fields omitted: Metering System Id should be a 13 digit number Minimum length of Password should be 6 Minimum length of Username should be 4 Negative Reading value is not allowed New Password must be entered No Archived files exist for this date(S) No Changes to Save(S) No Daily Profile Coefficients loaded or Archived found.(S) No Del Command No DPC data exists for GSP Group ID and No Filename No files for on or before this date exist.(S) No files found within criteria specified.(S) No Placeholder No Print Command No Report No Temporary Directory No View Command Open Failed Password changed successfully(S) Please insert a tape into the tape drive.(S) Press OK to continue waiting for the calculation to complete Problem occurred while appending changes to audit log file Record has already been inserted Register_Digits field value cannot be less than meter readings length Repeat Password is only allowed when New Password is entered Repeat Password should be same as New Password Rollover cannot be checked when Meter Reading-2 is greater than Meter Reading-1 Settlement Date From must be ON or BEFORE Settlement Date To. Settlement Date Parameters must be specified. The account is locked The password has expired The password will expire within [number] days This Report has been printed TPR is invalid for combination of Deemed Date and SSC ID entered Transaction Number Value Cannot Be Negative unable to find description for market Role Unable to read domains MARO and FCCO Unable to read domains MARO and/or FCCO User Created Successfully(S) User details have been changed by another user. Cancel and refresh the details before re-applying the changes User Dropped Successfully(S) User Modified Successfully(S) Username must be entered Wait Failed You are about to Clear Form. Are you sure? You are about to Drop User [username]. Press OK to confirm. You are about to Exit Form. Are you sure? You cannot Drop the currently logged-in user Your Password must be entered



A.1.2 Deemed Meter Reading Calculation Short and Long Messages

The following error and error messages may be displayed on the Ad Hoc

DMR Calculation Screen:-

Short Message Long Message Type

Warning:

Missing Tol Val

Tolerance Values Missing % From % To %

For PC

Warning



Warning: AA

outside tol

Tolerance Exception: AA % Meter Advance

% From % To % For Profile Class % High %

Low %

Warning

Warning:Date

Span > 730

Date Range Exceeded: Combined number of

days spanned by the three dates (DMR,

Reading 1 and 2) exceeds 730 calendar days.

Warning

Error: DPCs not

present

DPCs not present Error

Error:DPC

Calculation

Calculating DPC for PC % between % and % Error

Error:DMR

Calculation

Calculating DMR: % Error

Error: AA

Calculation Error: Calculation of AA too large - Calculation aborted

Error

A.1.3 Deemed Meter Reading Calculation Audit Report Error Messages

The following error messages may be displayed in the Status Message field

of the Ad Hoc Deemed Meter Reading Calculation Audit Report:-

No data found in edb_dmr_calc_profile_classes and edb_tolerance_values.

No data found in edb_dmr_calc_tprs p_emc_read_only_state: dbms_lock. allocate_unique failed allocating handle for lock named %

A.2 Error and Status Messages included in Exception and Control Reports

A.2.1 Determine DMA

The following error and status messages may be displayed in the DMA

exception and control reports.

Error and Status Messages relating to Business Rules

These error and status messages indicate inconsistencies with the data used

in the DMA calculation. A brief explanation of each of these status or error

messages is given. That suffixed with (S) is a status message.

Negative EAC/AA %f for TP %s (S)

A negative value for Estimation of Annual Consumption (EAC) or Annualised

Advance (AA) was supplied in the DMA Request File by the NHH Data Collector.

No DPC for GSP %s PC %s SSC %s TP %s Sett Date %s

No Daily Profile Coefficient for the displayed combination of GSP Group (GSP),

Profile Class (PC), Standard Settlement Configuration (SSC), Time Pattern (TP)

and Settlement Date (Sett Date) was found

No DPC values for Sett Date %s

No Daily Profile Coefficients were found for the Settlement Date displayed

Fatal Error Messages

These error messages indicate that there is a more serious problem. If any

of these messages are shown on the DMA Exception or Control Reports,

you should contact your System Manager.

Field Code Changed

Field Code Changed

Field Code Changed



Allocating %d DMA records.

Bad command line.

Bad file type %s, expecting %s.

Bad record type at line %ld.

Bad record type for header %s, expecting %s.

Calculating DMA.

(Failure of DMA calculation due to non-business rule related error)

Checksum at line %ld position %ld.

Code %d returned by dma_get_daily_profile_coefficient.

End of file at line %ld.

Failed adding missing date.

Failed processing file.

Failed to delete exception file %s, errno is %d.

Failed to initialise application.

Failed to open control file %s, errno is %d.

Failed to open exception file %s, errno is %d.

Failed to open file %s.

Failed writing to control file.

Fclose

(Unable to close output file)

fgets at line %ld.

Fgets failed, errno %d at line %ld

Footer record type at line %ld position %ld.

Fprintf at line %d printing text %s

ftell failed, errno %d

Invalid job %s specified on command line.

Invalid option %c ignored.

Line %ld is too long.

No job specified on command line.

No memory for %d missing dates.

No memory for %ld PCI records at line %ld.

No memory for EAA list.

No memory for GSP list.

No memory for PCI list.

No memory on GSP record.

Non-matching success & failed counts. Total %ld, success %ld, failed %ld.

(This message is displayed if the information in the footer (number of Metering

Systems read, success, fail) is suspect due to processing problems)

Record count record type at line %ld position %ld.



The output file has been deleted.

Unable to create new edb_data_files record

Unable to create new edb_report_files record

Unable to get next value of edb_file_seq

Writing DMA record.

Writing MSI record.

A.2.2Calculate EAC/AA

The following error and status messages may be displayed in the EAC/AA

exception and control reports. Those suffixed with (S) are status messages.

Error and Status Messages relating to Business Rules

Meter Advance Period longer than %d Days

The Meter Advance Period is longer than the number of days displayed

Negative AA %12.1f for TP %s (S)

A negative Annualised Advance has been calculated for the Time Pattern

given

Negative DPC %1.13f for GSP %s PC %s SSC %s TP %s Sett Date %s (S)

A negative Daily Profile Coefficient has been found for the displayed

combination of GSP Group (GSP), Profile Class (PC), Standard Settlement

Configuration (SSC), Time Pattern (TP) and Settlement Date (Sett)

Negative EAC %12.1f replaced by %.1f for TP %s (S)

A negative EAC has been replaced with default EAC for the displayed Time

Pattern

No AFYC exists for GSP %s PC %s SSC %s TP %s, no EAC will be

calculated

No EAC will be calculated as no AFYC entry exists for the given GSP

Group, Profile Class, Standard Settlement Configuration and Time Pattern

Regime to replace the negative EAC

No Default EAC exists for GSP %s PC %s, no EAC will be calculated

No EAC will be calculated as no Default EAC entry exists for the given GSP

Group and Profile Class to replace the negative EAC

Negative Meter Advance %8.1f for TP %s (S)

A negative Meter Advance value for the Time Pattern given

No DPC loaded for GSP %s PC %s SSC %s TP %s Sett Date %s

No Daily Profile Coefficient found for the displayed combination of GSP

Group (GSP), Profile Class (PC), Standard Settlement Configuration

(Standard Settlement Configuration), Time Pattern (TP) and Settlement Date

(Sett Date)

No DPC values for Sett Date %s

No Daily Profile Coefficient found for the displayed Settlement Date

No Effective Smoothing Parameter found, no EAC will be calculated

No Smoothing Parameter found for the end date of the Meter Advance

Period that was supplied in the EAC/AA Request file

Non-zero Meter Advance %8.1f Zero FYC TP %s (S)

The Meter Advance value supplied in the EAC/AA Request file is non-zero,

but the Fraction of Yearly Consumption has been calculated as zero. In this

circumstance, the calculation sets the Annualised Advance to zero.

Field Code Changed

Field Code Changed



AA Exceeds Tolerance MA %s AA %s PC %s SSC %s TP %s Tolerance %s %s (S)

A calculated AA has exceed either the high or low tolerance value for the metering system’s

GSP Group and Profile Class.

Fatal Errors


of these messages are shown on the EAC/AA Exception or Control Reports,

you should contact your System Manager.

AA value %f is too large.

Allocating %d EAC records.

Bad command line.

Bad file type %s, expecting %s.

Bad record type at line %d.

Bad record type for header %s, expecting %s.

Calculating EAC.

(Failure of EAC calculation due to non-business rule related error)

Cannot find range of reasonable AA values for GSP %, PC %

Checksum at line %ld position %ld.

Code %d returned by eac_get_daily_profile_coefficient.

EAC value %f is too large.

End of file at line %ld.

Failed adding missing date.

Failed processing file.

Failed to initialise application.

Failed to open control file %s, errno is %d.

Failed to open exception file %s, errno is %d.

Failed to open file %s.

Failed to open file %s.\n

Failed writing to control file.

fclose

fgets at line %ld.

fgets failed, errno %d at line %ld

Footer record type at line %ld position %ld.

fprintf at line %d printing text %s

ftell failed, errno %d

Invalid job %s specified on command line.

Line %ld is too long.

No job specified on command line.

No memory for %d missing dates.

No memory for %ld PCI records at line %ld.

No memory for GSP list.

No memory for PCI list.

No memory for SRD list.

No memory on GSP record.

Non-matching success & failed counts. Total %ld, success %ld, failed %ld.



(This message is displayed if the information in the footer (number of Metering

Systems read, success, fail, is suspect due to processing problems)

Record count record type at line %ld position %ld.

The output file has been deleted.




Writing EAC record.

Writing MSI record.

A.2.3 Load Daily Profile Coefficients

The following error and status messages may be displayed in the Load Daily

Profile Coefficients exception report. Status messages are suffixed with (S).

Status and Error Messages relating to Business Rules

Data exists for GSP Group

Attempts were made to load Daily Profile Coefficients from a Type 2 file,

for a GSP Group for which Daily Profile Coefficients have already been

loaded

Data exists for Sett Date at higher run number

The system was unable to load a Daily Profile Coefficient file for a

particular Settlement Date because a file with a higher version number has

already been loaded for that Settlement Date

DPC Validation Failed at Line

Failed getting file detail Oracle

Failed to open the file

GSP Validation Failed at Line

No data exists for previous Settlement Date

A Daily Profile Coefficient file for the previous Settlement Date was not

found, so subsequent files could not be loaded

PCI Validation Failed at Line

SCI Validation Failed at Line

Settlement Date Or Run Number is null

TPR Validation Failed at Line

Wrong Mkt PID ISRA: Scott DPCs before BETTA

Wrong Mkt PID IARA: DPCs on/after BETTA

The following messages may be included in the Load Daily Profile

Coefficient Control Report:

Failed

One of the reasons why this message may be displayed is if the system was

unable to load a Daily Profile Coefficient file for a particular Settlement

Date because a file with a higher version number has already been loaded for

that Settlement Date

File not loaded

A Daily Profile Coefficient file for the previous Settlement Date was not

found, so subsequent files could not be loaded

Negative DPC Loaded: Line xx, GSP group yy (S)

Field Code Changed

Field Code Changed



Fatal Errors


of these messages are shown on the DPC Exception or Control Reports, you

should contact your System Manager.

$EACAA is not set

Failed closing check_dpc cursor

Failed fetching check_dpc cursor

Failed opening check_dpc cursor

Failed to close check_gsp

Failed to close get_next_date

Failed to close get_next_type2

Failed to close get_old_file_recs

Failed to convert edb_jobs.parameter to long type

Failed to delete from edb_daily_profile_coefficients

Failed to fetch from check_gsp

Failed to fetch from get_next_date

Failed to fetch from get_next_type2

Failed to get Directory Locations

Failed to get system_mode from edb_system_configuration

Failed to get the count from edb_daily_profile_coefficients

Failed to get the date or user.

Failed to insert edb_daily_profile_coefficients

Failed to open check_gsp

Failed to open Control File

Failed to open DPC File

Failed to open Exception File

Failed to open get_next_date

Failed to open get_next_type2

Failed to open get_old_file_recs

Failed to process the file

Failed to read edb_data_files

Failed to select edb_jobs.parameter1

Failed to select edb_std_settlement_configs

Failed to update edb_data_files.

Failed to update old versions of file sequence number %ld

Failed validating previous files

Invalid Arguments

Job Number not read

No edb_jobs.parameter

System mode has invalid value

Taking lock.

The Collector Participant ID not found.






Failed to obtain BETTA start date value

A.2.4 Load Standard Settlement Configuration

The following error messages may be displayed in the Load Standard

Settlement Configuration exception report:

Aborted process, Oracle error: <Oracle error number>

Failed to commit record of exception file to the database

Failed to get input file details

Failed to get market participant name

Failed to get user name and current date & time

Failed to open input file

Failed to process the whole file, processed <number of records> record(s)

Missing/Invalid record type, record: <record_number>

Missing/Invalid SSC Description, record: <record number>

Missing/Invalid SSC ID, record: <record number>

Missing/Invalid Av Frac Yearly Consumption value, in record: <record

number>

Missing/Invalid Effective From Date for GSP Group Id<GSP Group Id>,

in record: <record number>

Missing/Invalid Effective To Date for GSP Group Id <GSP Group Id>, in

record: <record number>

Missing/Invalid GSP Group Id for Profile Class Id <Profile Class Id>, in

record: <record number>

Missing/Invalid Profile Class Id,in record: <record number>

Missing/Invalid Time Pattern Regime Id for Profile Class Id <Profile

Class Id>) and GSP Group Id <GSP Group Id>, in record: <record

number>

Record Ignored - Received Effective From Date <Effective From Date>

older than database Effective From Date, in record: <record number>

Record Rejected - Invalid AFYC <AFYC>, value found in record:

<record number>

SSC Description in database can't be changed, record: <record number>

(An attempt was made to load a Standard Settlement Configuration

where a Standard Settlement Configuration already exists in the database

with the same Id, but a different description)




Field Code Changed

Field Code Changed



Appendix B Report Directory

This appendix gives an example of each report that can be generated from

the EAC/AA system. User initiated and automatically generated reports are

shown.

B.1 Report on Profile Coefficients

Report On DPC An Electricity Company 25/02/1998 14:27

User: OPSSUPER

Report Criterion Value

======================================== =====

Settlement Date From 01/01/1997

Settlement Date To 02/01/1997

GSP Group G1

Profile Class 1

Standard Settlement Configuration (Not Specified)

Time Pattern Regime (Not Specified)

Settlement GSP Profile Standard Time Daily Profile

Date Group Class Settlement Pattern Coefficient

Configuration Regime Values

====================== ============== ================= ======================= ========= ================

01/01/1997 G1 1 SSC1 TPR01 0.0730788684758

01/01/1997 G1 1 SSC1 TPR02 0.0915178545137

01/01/1997 G1 1 SSC1 TPR03 -0.0347614797508

01/01/1997 G1 1 SSC1 TPR04 0.0836437016075

01/01/1997 G1 1 SSC2 TPR04 -0.0590207062692

01/01/1997 G1 1 SSC3 TPR01 -0.0478120953295

01/01/1997 G1 1 SSC3 TPR02 0.0760006268729

01/01/1997 G1 1 SSC3 TPR03 -0.0377271283827

01/01/1997 G1 1 SSC3 TPR04 -0.0435407800509

01/01/1997 G1 1 SSC4 TPR01 -0.0428339051681

01/01/1997 G1 1 SSC4 TPR02 -0.0598159008832

01/01/1997 G1 1 SSC4 TPR03 -0.0344333725371

01/01/1997 G1 1 SSC4 TPR04 0.0934281654317

02/01/1997 G1 1 SSC1 TPR01 0.0440048758565

02/01/1997 G1 1 SSC1 TPR02 0.0675107309799

02/01/1997 G1 1 SSC1 TPR03 0.0588216333700

02/01/1997 G1 1 SSC1 TPR04 0.0290588873580

02/01/1997 G1 1 SSC2 TPR01 0.0594950544907

02/01/1997 G1 1 SSC2 TPR02 0.0721942441236

02/01/1997 G1 1 SSC2 TPR03 0.0339154392415

02/01/1997 G1 1 SSC2 TPR04 0.0341950554125

02/01/1997 G1 1 SSC3 TPR01 0.0827127584195

02/01/1997 G1 1 SSC3 TPR02 0.0662850599774

02/01/1997 G1 1 SSC3 TPR03 0.0128906213593

02/01/1997 G1 1 SSC3 TPR04 0.0083041485654

02/01/1997 G1 1 SSC4 TPR01 0.0389750765866

02/01/1997 G1 1 SSC4 TPR02 0.0404531799643

02/01/1997 G1 1 SSC4 TPR03 0.0451367665504

02/01/1997 G1 1 SSC4 TPR04 0.0652153533046

Page 1

Note that the user has entered only the Settlement Date Range, GSP Group,

and Profile Class for the report criteria. The Standard Settlement

Configuration and Time Pattern Regime, which are optional, have not been

specified.

Field Code Changed



B.2 Report on Archived Data

Run Time: 06/06/1997 14:08 Organisation: An Electricity Company

Report on Archived Data

User: SYSMAN

Settlement Date: 10/01/1997

Smoothing Parameter: 1.100

Effective Date for Smoothing Parameter: 01/01/1997

GSP Profile Standard Time Run Daily Profile

Group Class Settlement Pattern Number Coefficient Configuration Regime Values

G1 1 SSC1 TPR01 1048 0.0552881620406 G1 1 SSC1 TPR02 1048 0.0246933261621

G1 1 SSC1 TPR03 1048 0.0294955663506

G1 1 SSC1 TPR04 1048 0.0365156934273 G1 1 SSC2 TPR01 1048 0.0373782461367

G1 1 SSC2 TPR02 1048 0.0023440533369

G1 1 SSC2 TPR03 1048 0.0216089400461 G2 1 SSC1 TPR01 1048 0.0554688705699

G2 1 SSC1 TPR02 1048 0.0254524871113

G2 1 SSC1 TPR03 1048 0.0768804979436 G2 1 SSC1 TPR04 1048 0.0443052128890

G2 1 SSC2 TPR01 1048 0.0267931242005

G2 1 SSC2 TPR02 1048 0.0367471964805 G2 1 SSC2 TPR03 1048 0.0061029201790

G2 1 SSC2 TPR04 1048 0.0812344753575

G2 1 SSC3 TPR01 1048 0.0379311625874

Page: 1


Report on Archived Data

End of Report

Page: 2

Field Code Changed



B.13 EAC/AA Control Report

Run Time: 10/06/1997 13:48:53 Organisation: An Electricity Company

Estimated Annual Consumption/Annualised Advance Control Report

User: OPSSUPER

Input File : EEVC0103.dat

Output File: DSEC53

Metering From To Details

System

1 01/01/1997 10/01/1997 No DPC for GSP G2 PC 1 SSC SSC1 TP TPR02 Sett Date 01/01/1997


2 01/01/1997 11/01/1997 No DPC values for Sett Date 11/01/1997 3 01/01/1997 10/01/1997 Negative EAC -4346655923.5 replaced by 45678.9 for TP TPR01

3 01/01/1997 10/01/1997 Negative AA -11515214.8 for TP TPR01

3 01/01/1997 10/01/1997 Negative Meter Advance -6789012.3 for TP TPR01 3 01/01/1997 10/01/1997 Negative DPC -0.0521753037605 for GSP G5 PC 1 SSC SSC1 TP TPR02 Sett 01/01/1997

3 01/01/1997 10/01/1997 Negative EAC -17286087132.0 replaced by 5678.9 for TP TPR02

3 01/01/1997 10/01/1997 Negative AA -19574053.1 for TP TPR02 3 01/01/1997 10/01/1997 Negative Meter Advance -8901234.5 for TP TPR02

3 01/01/1997 10/01/1997 Negative EAC -22712729382.1 replaced by 15678.9 for TP TPR03

3 01/01/1997 10/01/1997 Negative AA -226317.3 for TP TPR03 3 01/01/1997 10/01/1997 Negative Meter Advance -123456.7 for TP TPR03

3 01/01/1997 10/01/1997 Negative DPC -0.0521075489287 for GSP G5 PC 1 SSC SSC1 TP TPR04 Sett 01/01/1997

3 01/01/1997 10/01/1997 Negative EAC -45062203624.3 replaced by 65678.9 for TP TPR04 3 01/01/1997 10/01/1997 Negative AA -6015808.6 for TP TPR04

3 01/01/1997 10/01/1997 Negative Meter Advance -2345678.9 for TP TPR04

4 01/01/1997 10/01/1997 AA Exceeds Tolerance - MA 12345678, AA 123456, PC 01, SSC SSC1, TP TPR01, Tolerance 500000, -1000

Page: 1

Run Time: 10/06/1997 13:48:53 Organisation: An Electricity Company Estimated Annual Consumption/Annualised Advance Control Report

Processing Details:

No. of Metering Systems Read : 4

No. of Metering Systems Processed Successfully : 2 No. of Metering Systems Processed Unsuccessfully: 2

No. of MS for which a negative EAC was replaced : 1

End of Report

Page: 2

Field Code Changed



B.24 EAC/AA Exception Report (Human-Readable)

EAC/AA Calculation Exceptions An Electricity Company 10/06/1997 13:48

User: OPSSUPER

Input File : EMVC0102.dat

Output File: DSEC1482

Metering Reason

System Code From To Details

-------- ------ ---------- ---------- -------------------------------------------------------------

1 NDP 01/01/1997 10/01/1997 No DPC for GSP G2 PC 1 SSC SSC1 TP TPR02 Sett Date 01/01/1997

1 NDP 01/01/1997 10/01/1997 No DPC for GSP G2 PC 1 SSC SSC1 TP TPR03 Sett Date 01/01/1997

2 NDD 01/01/1997 11/01/1997 No DPC values for Sett Date 11/01/1997

3 NDD 01/01/1997 10/01/1997 Negative EAC -4346655923.5 replaced by 45678.9 for TP TPR01




No. of Metering Systems Processed Unsuccessfully: 2

Page: 1

Field Code Changed



B.35 EAC/AA Tolerance Value Exceptions Report

EAC/AA Tolerance Value Exceptions An Electricity Company 10/06/2000

13:48

User: OPSSUPER



Metering Meter

System AA Advance From To Pfl SC TPR High AA Low AA

------------ ------------ ------- ---------- -------- --- --- -----..---------.. ----------

1234567890123 987654321011.1 12345678 01/01/2000 10/01/2000 01 SC01 TPR01 222222222222 -11111111111

1234567890124 100 20 01/01/2000 10/03/2000 02 SC02 TPR03 80 -10

No. Of Exceptions: 2

Page: 1

Field Code Changed



B.46 Determine Deemed Meter Advance Control Report


Deemed Meter Advance Control Report

User: OPSSUPER




System


1 01/01/1997 10/01/1997 Negative EAC/AA -22345678901 200001 for TP TPR02

2 01/01/1997 11/01/1997 No DPC for GSP G2 PC 1 SSC SSC1 TP TPR03 Sett Date 01/01/1997 2 01/01/1997 11/01/1997 No DPC values for Sett Date 11/01/1997

Page: 1

Run Time: 10/06/1997 15:32:03 Organisation: An Electricity Company Deemed Meter Advance Control Report

Processing Details:


No. of Metering Systems Processed Successfully : 2 No. of Metering Systems Processed Unsuccessfully: 2

End of Report

Page: 2

Field Code Changed




User: A Person

Deemed Meter Advance Control Report

Input File Name : EMVC0102.dat

Output File Name : DSEC1482

Metering Details

System

1 No DPC loaded for GSP G2 PC 01 SSC SSC1 TP TPR01 Sett Date 01/01/1997

1 Negative EAC/AA -22345678901.200001 for TP TPR02

2 No DPC loaded for GSP G2 PC 01 SSC SSC1 TP TPR01 Sett Date 01/01/1997

2 No DPC values for Sett Date 11/01/1997

Processing Details:


No. of Metering Systems Processed Successfully : 1

No. of Metering Systems Processed Unsuccessfully : 2

From To

01/01/97

01/01/97

01/01/97

01/01/97

10/01/97

10/01/97

11/01/97

11/01/97

Failed Processing File.

Note that the “No. of Metering Systems Processed Unsuccessfully” includes those for

which processing was partially successful.



B.57 Determine Deemed Meter Advance Exception Report


Deemed Meter Advance Exception Report

User: OPSSUPER

Input File : EEVC0104.dat

Output File: DSEC53


System


1 01/01/1997 10/01/1997 Negative EAC/AA -22345678901 200001 for TP TPR02

2 01/01/1997 11/01/1997 No DPC for GSP G2 PC 1 SSC SSC1 TP TPR03 Sett Date 01/01/1997 2 01/01/1997 11/01/1997 No DPC values for Sett Date 11/01/1997

Page: 1


Deemed Meter Advance Exception Report

Processing Details:

No. of Metering Systems Processed Unsuccessfully: 2

End of Report

Page: 2

Field Code Changed



B.18 Load Daily Profiles Control Report


Load Daily Profile Coefficients Control Report

User: OPSSUPER

Settlement File Name No. of AAs No. of DPCs No. of DPCs Details

Date Calculated Replaced Loaded

01/01/1997 epvc0102.dat Negative DPC Loaded: Line 6, GSP group G5


01/01/1997 epvc0102.dat Negative DPC Loaded: Line 11, GSP group G5 01/01/1997 epvc0102.dat Negative DPC Loaded: Line 14, GSP group G5








01/01/1997 epvc0102.dat Negative DPC Loaded: Line 47, GSP group G5 02/01/1997 epvn0203.dat 0 0 320

02/01/1997 eqvn0203.dat 0 0 64

03/01/1997 epvn0304.dat 0 0 320 03/01/1997 eqvn0304.dat 0 0 64

04/01/1997 epvn0405.dat 0 0 320

04/01/1997 eqvn0405.dat 0 0 64 05/01/1997 epvn0506.dat 0 0 320

05/01/1997 eqvn0506.dat 0 0 64

Page: 1


Load Daily Profile Coefficients Control Report

End of Report

Page: 2

In the above example, some Daily Profile Coefficient files for 01/01/97

contained negative values, these are indicated in the Details column of the

report: Negative DPC Loaded: Line xx, GSP group Gy - where xx is the line

in the file and Gy is the GSP Group Id.

Field Code Changed



B.29 Load Daily Profiles Exception Report


Load Daily Profile Coefficients Exception Report

User: OPSSUPER

Settlement File Name Details

Date

03/01/1997 eqvn0304.dat DPC Validation Failed at Line 45

Page: 1

Run Time: 12/06/1997 12:07 Organisation: An Electricity Company Load Daily Profile Coefficients Exception Report

End of Report

Page: 2

Field Code Changed



B.110 Load Standard Settlement Configuration Exception Report


Load Standard Settlement Configuration Exception Report

User: EACAA

File Name: SSC1004319.dat

Settlement Date: 12/04/1997

Standard Reason for

Settlement Rejection Configuration

28 SSC Description in database can’t be changed, record: 12 30 Record Rejected - Invalid AFYC -900, value found in record: 15

Page: 1


Load Standard Settlement Configuration Exception Report

No. of Standard Settlement Configurations not loaded: 2

End of Report

Page: 2

Field Code Changed



B.11 Ad Hoc Deemed Meter reading Calculation Audit Report

EAC/AA Ad Hoc Deemed Meter Reading Calculation Audit Report An Electricity Company

10/06/2005 13:48

User: SYSAUDITOR

Report Criterion Value

------------------------- -------

Metering System Id 1234567890123 SSC Id

GSP Group Id

Username

Calculation Date From

Calculation Date To

Deemed Read Date From Deemed Read Date To

Transaction Number From

Transaction Number To

Metering GSP Reading Reading DMR Calculation Status

System Transaction Group SSC Date 1 Date 2 Date Date Time Username Status Message ------------------- -------------- ----- - ------ ------------- ------------ -------------- -------- ------ ------ ------------ ------- -----------

1234567890123 12345678 A 0001 01/01/2005 01/04/2005 15/05/2005 08/06/2005 11:43 FRED W

Profile

Class Effective From Settlement Date ------- ------------------------------

2 01/01/2000

3 04/08/2002

Reg Reg TPR Id Digits Reading 1 Reading 2 Rollover AA DMA Deemed Meter Reading

-------- ---- ------ ------------ ------------ ---------- --------- -------- ------------------------------ 00057 AA 7 4569327 4572567 T 12345.1 1500.1 4574067

Error

Severity Error Details

----------- ------------- W Tolerance Exception for AA 12345.1 Meter Advance 1500.1 From 01/01/2005 To 01/04/2005 For Profile Class 3

High AA 50 Low AA -5

Page: 1



Comment Form

Document Title EAC/AA Operations Guide

Document Issue 18.000

Issue Date 27 June 2013

If you have any comments on the accuracy and completeness of this document,

please write them on a copy of this form and forward by email to the ELEXON

Helpdesk at [email protected] or contact the Helpdesk on telephone number

020 7380 4222.

Comment no. Section Page Comment

Comments sent by: Organisation

Name

mailto:[email protected]

Version Number 17 - Elexon

Documents

Transcript of Version Number 17 - Elexon