DEM-01569-H7S3 - Meter Asset Management - Group IT Project URS V1 5

Template
Project User Requirements 240-83570075 Rev 1

Identifier
Specification
Authorisation
Demand number IM3-00051 Draft
Date
Meter asset management system
Review Date
PROJECT DETAILS
Project No.’s ID Demand Number: IM3-00051 WBS CIT00410
Project Name Meter Asset Management System (MAMS)
GIT Information Management

Wires
Area
IM Portfolio Manager Carlos Betencourt
PD Portfolio Manager Gideon Schoonwinkel
Project Sponsor Musa Mabila
PLCM Phase Execution Phase
Controlled Disclosure
When downloaded from the document management system, this document is uncontrolled and the responsibility rests with the user to ensure it
is in line with the authorised version on the system. No part of this document may be reproduced without the expressed consent of the copyright
holder, Eskom Holdings SOC Ltd Reg No 2002/015527/30.
Hard copy printed on: 28 June 2019 Page 1 of 62 mm
Project User Requirements Specification Template
240-83570075 Rev 1
< IM3-00051> <Meter asset management> Identifier
PROJECT DETAILS _____________________________________________________________________1

Document Control Information __________________________________________________________4
Abbreviations ________________________________________________________________________4
Glossary of Terms / Definitions __________________________________________________________6
1 INTRODUCTION TO THE USER REQUIREMETS SPECIFICATION ______________________________7
2 SOLUTION BACKGROUND AND CONTEXT ______________________________________________7
2.1 Sponsor, project owner, business area ___________________________________________________ 7
2.2 Reason for the requirement ____________________________________________________________ 8
2.3 Business areas impacted_______________________________________________________________ 8
2.4 In/Out of Scope and Preconditions ______________________________________________________ 9
3 BUSINESS STRATEGY ______________________________________________________________10
4 BUSINESS REQUIREMENTS _________________________________________________________11
4.1 High Level Requirements _____________________________________________________________11
4.2 Functional Requirements _____________________________________________________________12
1. Uniquely Identify each meter _______________________________________________________12
2. Meter location history ____________________________________________________________13
3. Meter history ___________________________________________________________________16
4. User ID access ___________________________________________________________________17
5. Meter supplier’s meter information _________________________________________________17
6. Information required for each meter type _____________________________________________21
7. Entry points for the meter onto the Meter Asset Management system _____________________22
8. Meter installation information _____________________________________________________23
9. Seal management system _________________________________________________________31
10. Hand held device for meter installation _____________________________________________32
11. Inventory control of meters ______________________________________________________41
12. Meter maintenance requirements _________________________________________________42
13. Meter certification records _______________________________________________________43
14. Digital signature management ___________________________________________________44
15. Infrastructure requirements ______________________________________________________44
16. Handheld Device requirements ___________________________________________________44
4.3 Reporting Requirements / KPI Measures_________________________________________________46
holder, Eskom Holdings SOC Limited, Reg No 2002/015527/30.
Hard copy printed on: 28 June 2019 Page 2 of 62
mm
240-83570075 Rev 1
4.4 User Interface Requirements __________________________________________________________46

4.5 Information/Data Requirements _______________________________________________________47
4.6 Integration Requirements ____________________________________________________________48
4.7 Performance Requirements ___________________________________________________________53
4.8 Security Requirements _______________________________________________________________53
4.9 Archiving Requirements ______________________________________________________________54
4.10 Operating Environment ______________________________________________________________54
4.11 Training Requirements _______________________________________________________________54
4.12 Testing Requirements (if applicable) ____________________________________________________55
4.13 Legal Requirements (if applicable) ______________________________________________________55
4.14 Disaster Recovery Requirements _______________________________________________________55
4.15 Business Continuity __________________________________________________________________55
4.16 Capacity Planning Requirements (if applicable) ___________________________________________56
4.17 Environmental Management (if applicable) ______________________________________________56
4.18 Service Level Agreement (if applicable) __________________________________________________56
4.19 Support and Maintenance Contract Requirements _________________________________________56
4.20 Stakeholder Management ____________________________________________________________56
5 PROPOSED SOLUTIONS/ARCHTECTURE/TECHNOLOGY __________________________________58
6 BUSINESS PROCESS _______________________________________________________________58
6.1 AS-IS Process _______________________________________________________________________58
6.2 TO BE Process ______________________________________________________________________59
7 DEPENDENCIES __________________________________________________________________59
8 ASSUMPTIONS AND CONSTRAINTS __________________________________________________60
9 DOCUMENTS TO BE UPDATED ______________________________________________________60
10 REFERENCES___________________________________________________________________61
11 DOCUMENT APPROVAL _________________________________________________________62
mm
240-83570075 Rev 1
Document Control Information
Version
Effective from Amendment Modified By
Number
7 Sept 2012 Creation of document – Business 0.1 Ruth Stead
Requirements only
st
30 Oct 2012 Completion of all areas of the URS for 1 0.2 Ruth Stead
review
10 Mar 2015 Review and update URS on new 1.0 Mathys Willemse
approved GIT template
30 Apr 2015 Update feedback receive from 1.1 Mathys Willemse
stakeholders
3 July 2015 Update feedback and Sponsor Name 1.2 Mathys Willemse
10 Oct 2015 Update commends and feedback received 1.3 Mathys Willemse
from Bobby Naidoo
3 Nov 2015 Update Sponsor to Zone management 1.4 Mathys Willemse
forum chair Rudzani Tshikota
25 Nun 2019 Update project business sponsor to Musa 1.5 Mathys Willemse
Mabila
Abbreviations
Abbreviation Description
AMI Advance metering infrastructure
ASCII American Standard Code for Information Interchange
BSO Business systems officer
C&I Control and instrumentation
CC&B Customer Care and Billing
CIS Customer Information System
CNC Customer Network Centre
CNL Customer Network Link
CSC Customer service centre
CT Current Transformer
Cust Customer
CVT Current and Voltage Transformer
DAS Data and acquisition system
Dx Distribution
EBM Energy Balancing Module
ECU Electricity control unit
ED Energy dispenser
EDA Engineering data terminal application
EDL Electricity Dispenser Laboratory (now referred to as Prepayment Metering
Laboratory)
EMS Electrical maintenance sections
FBM Feeder Balancing Module
FC Fault Cause
mm
240-83570075 Rev 1
Fls Feeders
FM Fault Mode
FSA Field service area
GIS Geographical Information System
HV High Voltage
IPP Independent power producer
Kva Kilo volt ampere
Lab Laboratory (Prepayment Metering Laboratory)
LPU Large power user
LV Low Voltage
MAM Meter Asset Management
MATS Meter asset tracking system
MDMS Meter Data Management System
MIS Meter Initialisation System
MMF Meter movement form
MV Medium Voltage
NFF No Fault Found
NRS National Rationalization of Standards
OU Operating unit
PCM Process Control Manual
PPU Prepaid power user
PS Power station
PTA Prepaid technical advisor
RDC Regional Distribution Centre
RFID Radio frequency identification technology
RP Revenue protection
RPC Revenue protection centre
RPO Revenue protection officer
SCADA Supervisory Control And Data Acquisition
SEA Strategy Execution Architecture
SGC Supply group code
SP Service point ID in CC&B
SPU Small power user
StdLabel Standard labels
STS Standard Transfer Specification
Trfr Transformer
TSA Technical service area
TSC Technical Service Centre
TSU Technical Service Unit or Technician
Tx Transmission
ULM Utility load manager
URS User Requirement Specification
VT Voltage Transformer
mm
240-83570075 Rev 1
WMA Work management areas
RMC Resource management centre
Glossary of Terms / Definitions
Term Definition
CDX Works coordinator Was replaced with CC&B customer care and billing system and it
refer to an job profile of an works coordinator planning and
scheduling CC&B initiated works orders interfacing to Maximo.
CNC Has replaced the term TSC [Technical service centre]
CSC/ Hub Has replaced the term WIC [Walk in centre]
DAS Data and acquisition system to manage metering on remote, up
and downloading functions via the MV90 systems.
Device Refers to handheld
Handheld Device A mobile device that will be used by technicians in the field to
capture relevant data electronically also called an EDA.
LO10 Is a name given in Eskom DX for a mapping table listing all
networks in following format: WMA Location/ WMA description/
FSA location/ FSA description/ TSC location/ TSA description/ Fls
location/ Fls description/ location/ description/ type/ Class structure
ID/ Class description/ Latitude/ Longitude/ Owner/ Change by/
PremiseID/ Sdtlabel/ old stdLable/ Sw Voltage/ PPU/ SPU/ LPU/
Kva/ Total cust/ Cust note/ Trfr no cust Impact/ Trfr capacity impact/
Duplicate trfr impact/ customer overload count.
Meta data Meter data referring to amp rating, manufacturer, type of meter,
model name, store bin number
Meter seal The seal(s) used to prevent meter tamper or to help prove that the
meter or meter box has been opened illegally.
Meter Supplier The vendor, manufacturer or supplier of electricity meters to
Eskom.
Metering Assets “Metering assets include meters, communication equipment and
ancillary devices”. From Metering Assets PCM.
Metering equipment life Incorporates the installation, commissioning, maintenance,
cycle decommissioning, replacement and disposing of metering assets.
MV90 Data acquisition system is called MV90. The system remotely
measure interval consumption for billing/ statistical purposes on
meters in the DX business
NEDISys National electricity dispense information system file
PiLog PiLog is a leading provider of Master Data Quality Solutions,
supporting the creation and maintenance of high quality master
data in a variety of industries, including petrochemical, mining,
steel, food and beverage, transportation, large facility management,
telecommunications, aeronautical, defence, government, as well as
a diversity of processing plants and heavy manufacturing. The
PiLog master data quality solutions are comprehensive and can be
integrated with commercial systems such as SAP, Oracle, SAGE,
Microsoft, IBM (Maximo) and etc.
mm
240-83570075 Rev 1
Term Definition
RP Revenue protection is lately called Energy protection, RPO could
be renamed to EPO- Energy protection officer and RPC will
become EPC – energy protection centre.
System It can be application / middleware / a combination of something to
realise a requirement
Warranty A written guarantee, issued to the purchaser of an article by its
manufacturer, promising to repair or replace it if necessary within a
specified period of time.
1 INTRODUCTION TO THE USER REQUIREMETS SPECIFICATION

The User Requirements Specification clearly defines what the functionality and requirements of the
proposed solution will be, by providing all the information that is necessary to design and implement the
proposed solution.
The purpose of this document is to record and confirm the user (business) requirements for
• New solution required
• Replacement of existing solution or part of existing solution
• New modules to be added to existing solutions
• Upgrades to existing solution
This document is an official document and will be used to define the solution architecture design, if
applicable.
2 SOLUTION BACKGROUND AND CONTEXT

A business need was identified to have a Meter Asset Management system that would accommodate all
meters that are used by Eskom. This User Requirement will describe the specific requirements for
Electricity Meters, but will have generic requirements that could be used for a meter of any commodity.
Specific requirements for other Commodity’s meters will need to be specified in a separate User
Requirement Specification.
An investigation was initiated to determine the meter asset management system requirements for all
areas that make use of electricity meters (Generation and Wires).
2.1 Sponsor, project owner, business area
Business Sponsor Musa Mabila (Senior Manager

M&O)
Business Project Owner Archie Jaykaran (Business)
Aumkar Sukhoo (National)
Reginald Brookes (SCOT:
Metering)
Sebastian Pasquallie
(Maintenance)
Business Area Generation and Wires [TX and
DX]
mm
240-83570075 Rev 1
2.2 Reason for the requirement

Business requires a holistic Meter asset management solution in order to manage meters through its
asset live cycle. Presently Distribution has approximately 5 million Pre-Paid customers, 430 000 Small
power users and 20 000 large power users each with a meter. Over the next few years approx. 1.6
million customers will be added to the grid. Currently an in-house developed system exist viz. “MATS-
Meter asset tracking system”. The challenges with the existing system is that there are very limited
integration to other source systems e.g. Maximo; SAP which limit the controls on the management of the
metering assets. A holistic solution is required with proper integration and systematic controls to track
the meters through its life cycle MATS is currently doing the life cycle tracking successfully. Business
processes needs to be adapted to support the holistic asset management life cycle with all identified
integration systems in order to achieve proper control of these revenue generating assets in the
business.
Currently when meters are ordered and delivered at the Regional Distribution Centres [RDC’s] the store
person will book the procured meters into the store by accepting them on SAP system which is only
focusing on numbers of meters per order number with meter description details. The store person will
then have to scan all the barcoded meters numbers with a hand held unit and upload into MATS
recording the asset numbers per meter type received against relevant SAP order number. There are
currently no integration between MATS and SAP thus you require a manual method to compare SAP
quantity received with the MATS number scanned into the relevant RDC. The same happens when
meters are being replenished via the SAP system from the RDC to Customer network centre (CNC).
Meters will be booked out of RDC to CNC using the SAP reservation number and it is receipted at the
CNC on SAP as numbers of meters. The Store person at the CNC then scans the meters and uploads
the scanned meters into MATS as receipt. No integration between SAP an MATS means that there is no
reconciliation in place for meters that move from one location to the next within the business. When a
meter change is required the Technical service unit (TSU) will receive a work order (WO). via Maximo on
his/her hand held unit (EDA).The TSC store person will issue physically issue a meter out to the TSU by
scanning the meter out from the TSC to the TSU using SAP reservation -. MATS tracks the asset
number and SAP the quantity of meters. No integration exists between SAP/ Maximo and MATS thus
one transaction will require the store person to log into three systems to book out one meter. Business
require one system or automatic integration between systems to enable the store person user to issue
meters with one transaction updating the stock inventory, track the asset to latest transaction location
and updating work order or task order status.
System support is also a challenge and need to be centralized, the current MATS system is a classified
type 4 system been supported provincially by BSO’s in OU’s with two national developers based in EAL
not only supporting MATS but some other systems too.
2.3 Business areas impacted

Generation, Transmission and Distribution business are impacted with the greatest impact on DX where
the majority of metering points to customer level will be.
The people who will be affected by the implementation of these user requirements include:
 The stores receiving and dispatching staff.
 The Field technicians (Contractors and Eskom employees) who install new meters (both for customer
meters, tariff and stats meters).
 The Lab technicians (Contractors and Eskom employees) who maintain replace and calibrate meters
(both for customer meters, tariff and stats meters).
 The Meter Readers (Contractors and Eskom employees) who may detect possible faults with meters
whilst performing meter readings.
 Commercial staff that make decisions on meter suppliers, and also meter supplier payments.
mm
240-83570075 Rev 1
 Staff responsible for the capture of electricity network information.

 Staff responsible for the receiving, processing, and authorising of work order requests.
 Customer Services staff responsible for the capture and maintenance of Customer Data.
 Customer Services call centre staff, responsible for the responding to customer queries and
complaints.
 Staff responsible for the capturing and maintenance of asset data.
 Staff responsible for the capturing and maintenance of work order data.
 Revenue/ Energy protection staff who coordinate meter audits (Contractors and Eskom employees)
that audit and replace meters in high energy losses areas.
2.4 In/Out of Scope and Preconditions

A list of preconditions that need to be met in order for the URS proposed solution to be implemented. In
other words, the solution cannot be implemented if these preconditions are not met:
 Meter asset data that is currently stored in other systems, will need to be quality checked before
being migrated.
 Meter suppliers will need to update or develop meter information files as per Eskom’s specification to
keep meter data entering Eskom unique, valid and traceable.
 SAP will handle the purchasing of meters and the commercial processes involved in meter orders,
purchase and payment, but will need an integration point to the Meter Asset Management system, for
the receipt of delivery confirmations.
 SAP will handle Inventory Control of meters in RDC stores, but will need to allow for the update of
the Meter Asset Management system when meter movement is logged.
 All meter types Meta data will need to be stored and described in the PiLog Item Catalogue. PCM for
material and service master file management cataloguing [32-1222]
 The specification of the Meter Asset Management hand held devices will be handled
separately and will work hand in hand with this URS. (For review purposes only, the business
requirements for hand held devices have been left in this URS, but after the first round of review, this
information will be removed from this URS and placed in the OMO T&T Mobile Workforce
Management URS.)
 A document management system will need to be in place, in order to store warranty, certification,
suppliers’ meter specifications, meter seal and meter maintenance requirements. The storage could
be physical or electronic. Hyperwave is Eskom document management system. Electrical dispense
specialist and Senior procurement specialist should enquire and keep records of all contracted
suppliers OEM-original equipment manufacturer specifications e.g. warranty periods, meter
standards testing certification, meter technical specifications, OEM maintenance requirements and
meter seal requirements.
 All approved mobile units recommended by Mobile workforce URS which will be used to scan meter
assets, compatible software should be developed and implemented in the meter asset management
project. The software should enable bidirectional data flow between Eskom systems and mobile
solution down to hand held devices.
 Updates done on the Meter movement form used by business should formally be logged to GroupIT
change request process in order for GIT to develop and implement the change on the electronic
version of the form.
 Any proposed change on the existing manual Meter movement form and business work instruction
should be managed through the correct business institutions. When approve business should log a
change request with GroupIT to update the approved change accordingly on the Mobile unit
electronic version of the MMF.
mm
240-83570075 Rev 1
Out of scope
 The handheld device requirements will be described in full in the mobile workforce URS
 A separate initiative will be needed in order to collect the meter asset data required of meters already
in the field, in stores and in maintenance. Contracts agreements with electrification and post
connection external contractors to specify the information required for any meter movements e.g.
new installations and / or change-outs, specified time frames and payment implications for non-
compliance.
A list of dependencies that could negatively impact the implementation of the URS proposed
solution:
 Asset Performance Management Tools
 Mobile Workforce Management
 Documentation Management System
 Integration to other source systems
 Electronic signature on mobile unit asset movement forms [This function is currently available on the
EDA mobile device but need clarity if it could be used legally in this format?]
 Credit token issue from mobile units
 Key change token issues from mobile units
 Providing customer and vendor with copy of electronic movement form. [Suggestion - Blue tooth
connection with the customers phone to download the form or a website where the customer can
view the form or Portable printer. (Costly)]
 Selection of the future most optimal method or technology to track metering assets e.g. by barcode
serial number scanner/ reader or by RFID technology? Radio frequency identification technology is
every meter been fitted with an electronic chip which is traceable via radio frequency networks though
the asset live cycle.
3 BUSINESS STRATEGY
Business benefits/value of the solution

By properly managing Eskom assets it will have financial benefits to the business when connected
meters are all registered and/ or linked to customers - improving revenue collection/ allocation. It will
improve customer satisfaction when the customer is able to buy energy when linked correctly to the
billing system – should enforce online vending. It should improve Eskom service delivery when metering
point could be created and maintained with minimal interruptions to the customer and job been
completed the first time around.
Eskom Strategic Objectives being supported

 Leading and partnering to keep the lights on and Ensuring Eskom’s financial sustainability.
Divisional / Departmental Mandate / Focus areas being supported

The Gx/ Tx and Dx wires and Group CS business will be able to support the Eskom mandate to
“Provide electricity in an efficient and sustainable manner” to customers with a well-integrated Asset
management system to support the huge numbers of metering points in the business.
Business benefit, financial benefit, creating efficiencies.

Standard approach to asset management will streamline the business operations; it should also have
financial benefits if meters under guarantee with manufacturer faults could be identified and replaced
without cost, dispatching meters around business with correct configurations should reduce the number
of visits to customers resolving supply challenges the first time around.
mm
240-83570075 Rev 1
4 BUSINESS REQUIREMENTS
 To implement an integrated Meter Asset Management solution. The solution requires to track
where meters are in the field and to which customer the meter is allocated. Where meters are
used as Stat meters the feeder/ pole name/ ID and location should be reflected.
 When meter movement happens the required information needs to be captured in the field and
this information needs to be undated and reflected in all supporting systems.
 It is required that the solution integrates with Customer Information System(CIS), Customer
Relationship Management (CRM), Engineering Tools and Mobile Workforce Management
System, Feeder balancing and Energy balancing FBM/ EBM systems, MV90 system for
automated meter reading systems and Meter data management system MDMS. The total
solution should form part of the Advance metering infrastructure in the business.
 A critical success factor for this URS implementation is for the business to be able to identify the
exact location of the actual asset. The URS will describe the system requirements for Meter
Asset Management, but will not be responsible for the updating and collecting of Data required to
exactly locate the meters. Other systems who could be used to supply the missing info are
CC&B, Small World, Maximo, CNL, and FBM.
4.1 High Level Requirements

Replace existing meter asset tracking system [MATS] with an integrated meter management
solution. The system should incorporate inventory management of assets as well as asset location
tracking throughout the meter asset live cycle via the work management systems in the business
and interface with customer care and billing system to update meter movements at customer/
power delivery level to ensure the revenue collection is correctly allocated.
This solution should perhaps form part of the modern trends around Advance metering
infrastructure [AMI]. The over-riding philosophy in the user requirements is that the user should
update the information once and all the systems that need to be updated will be optimally
integrated and updated accordingly with proper data validation rules in place.
mm
240-83570075 Rev 1
4.2 Functional Requirements
Requirement Details
1. Uniquely Identify each meter
Business It is of the utmost importance to be able to uniquely identify each and every meter that
Functionality is loaded on the system. Due to there being a number of different meters measuring
different commodities, and different Suppliers of meters, as well as many different types
of meters, there will need to be a number of different fields combined in order to create
a unique identification for each meter. The user who needs to search for, or update a
meter, and its history, needs to be able to find exactly the meter required, there must
not be a number of meters with the same unique identifier. The histories updates need
to be stored per unique ID.
There will need to be a combination of a number of catalogues/ entities that will then
produce the unique identifier of each single meter.
For each Meter Type there will also need to be a definition of the exact length and
format of the meter serial numbers expected for that meter type. The meter serial
number will need to be validated when it is initially loaded onto the system, to ensure
that it complies with the length and format requirements.
The meter serial number will also need to be validated to ensure that it is unique. It
must not be possible to add a duplicate meter serial number (for that meter type and
supplier combination), onto the system.
It could be of important use to investigate the possibility of making use of RFID
technology to uniquely identify and track meters through its live cycle.
1.1 Entities/catalogues required to identify the meter

1.1.1 Commodity
There will need to be a catalogue of the different commodities that are being measured
by the meters, such as electricity, water, gas, fuel etc. This catalogue needs to be
edited at a high level of access. When a new commodity of meters is added to the
Meter Asset Management System, there will need to be a complete configuration of
what fields will need to be captured for that commodity’s meters. The specific
requirements for each commodity will need to be defined separately. This URS will only
specify electricity meter requirements, but there will be much functionality that can be
used across all commodity meters.
1.1.2 Meter Supplier

There will need to be a catalogue of meter suppliers that may be edited at a high level
of user access. The supplier catalogue should have a catalogue code and a supplier
name allocated to it. The catalogue can be confirmed against the commercial list of
meter suppliers, but must allow for suppliers that are no longer on the approved meter
supplier list, to accommodate old meters loaded on the Meter Asset Management
system. The catalogue should make a distinction between current approved meter
suppliers and those that are not. A meter prefix associated with a specific supplier
needs to be maintained e.g. Conlog meters have a prefix of 04. This assists in ensuring
the correct meter manufacturers are used and validations could be instituted to prevent
meta data errors.
mm
240-83570075 Rev 1
1.1.3 Meter measurement types

There needs to be a catalogue of what the meter measures. Electricity meters could be
measuring, a combination of:
 kWh,
 Amps,
 Voltage,
 KVarh
 QOS
This is not a complete list of measurement types that will be required.
It must be possible to select up to n different items that the meter measures. (E.g.
currently seven for four quadrant meters measuring six separate quantities for billing
data as well as a minimum of nine other engineering/ QOS quantities such as voltage
per phase, current per phase, phase angle per phase. )
1.1.4 Electricity meter types

For the Electricity Commodity meters, the system must accommodate the attributes of
numerous types of electricity meters, such as:
 Pre-paid
 Post-paid :
o Conventional post paid
 Generation metering
 Grid metering (DAS)
 Commercial and industrial metering (DAS)
 Residential (manual or MV90)
 Smart Meters – AMI (front end systems and MDMS)
 ULM
 Tariff meters - wires
 Stats meters – wires
 Tariff meters - generation
 Stats meters – generation
Refer to Standard for information on prepaid meters dispatched from/ to manufacturer

to/ from Eskom: ST_240-76627071_newdraft_rev3-x.docx
2. Meter location history

The different locations that a meter goes through, needs to be stored against the meter
history.
The location change, must also save how the meter location change got entered onto
the system (uploaded or manually captured-either hand held device or manually). A
meter may be manually captured initially and then get updated later by a meter file.
Existing DX system make use of Location types e.g. RDC/CNC/ EP/ CSC and Location
names e.g. Bela-Bela RDC, Groblersdal CNC/ Witbank RP/ Kwaggafontein CSC[WIC]
There needs to be a date and time stamp for each location history record, as well as a
user ID for each history item of a meter. There may be times when the information is
captured by one User ID, but was actually performed by a different User ID. Both these
User IDs, and the separate date and time stamps must be stored (this would happen in
the case of a field technician filling in an installation form, and a clerk capturing the
information on the system at a later stage).
mm
240-83570075 Rev 1
The system the meter history data was changed on, also needs to be stored, i.e. if it
was changed on:
 the Meter Asset Management System,
 the CIS,
 the CMS,
 The hand held unit for field technicians or contractors, etc.
Each step of the meter’s location life cycle must be tracked and recorded, until it is
scrapped. (There should be strict scrapping processes to ensure that meters really are
scrapped, and that they do not get reconditioned and sold back to Eskom as new
meters. Not part of this scope to describe processes.)
In each step of the meter location history, the system must clearly record, who handed
over the meter, and who received the meter, so that there is a responsible person at
each step of the meter’s location life cycle. It is better for a meter serial number to be
scanned in, at each step of its history, both to ensure correct serial number data, and as
proof that the meter physically was present at that transfer.
The locations of a meter are depicted in the diagram below:

Wires Dx - Sub Dx- Technical Dx Customers
Business x section stores personnel:
Retirement
n OU’s LAB TSU-PTO/ Statistical

STO/ TO/ network
Dx CNC Contractor locations &
IPP’s
Store RP RPO
Contractor.
RDC Contractor Tx Customers
Tx – Technical Statistical
Tx personnel:
Tx - Sub network
Supplier
Store section stores Technicians locations &

IPP’s
Generation
Business x
Gx - Sub
n PS Gx – Technical Plant ID
section stores
Gx personnel: network
EMS/ C&I
Technicians locations
Main Maintenance
Store section stores
Logical flow of meters’ location history in Meter Asset Management system

The arrows in the diagram show the only way that the meter may move. The Meter
Asset Management system must not allow meters to flow in any order, other than what
is depicted in the location history flow.
It is not necessary to store the actual name of the RDC and CNC stores, as this system
will not be used to perform Inventory control and Inventory allocation. The Inventory
Control System will need to be updated at the same time as the Meter Asset
Management System is updated (one capture, multiple system updates) of the meter
movement. The Inventory Control System will know exactly which actual Store the
meter is in.
mm
240-83570075 Rev 1
When a meter is Issued to Technician-TSU and Uninstalled, it must be possible to see

who the person is who is currently responsible for the meter. If there is an Inventory
control system used in the Meter Stores and Maintenance departments, the Meter
Asset Management system must integrate with it, so that whenever a meter is received
or dispatched, the Inventory Controller needs to capture the movement once, and all
relevant systems are updated.
It must be possible to track which meters have been issued to which person, over which
time frame, and to determine which of those meters have been issued from stores, but
have not yet been installed or returned back to Store.
Proper business and system control rules needs to be set to ensure the meter cannot
move forward in any of the integrated systems if the previous control is not met. E.g.
user should not be able to issue a meter out to a TSU if the meter was not received into
the CNC store from where it originated from? Another example is there should be a one
on one relation between work order request to change a meter and the meter issued to
the TSU. One WO linked to one meter issued to TSU. WO should only be able to be
closed after the successful capturing and submission of the electronic MMF via hand
held unit or PC interphase at office.
Considering the proposed controls to be implemented in order to reduce current

operational human factor gaps, different technology available could suggest the best
solution for future meter and other material asset management systems. See pages 12-
27 of following document: Draft Report- Meter Management by Joe Drapkin Nov
2004.doc
Different trigger events could initiate meter asset movement trough the above diagram.
The material inventory system will ensure the relevant material orders are placed and
stock levels are replenished in different stores in the business from predetermined
minimum to maximum stock levels. When material is delivered at warehouse level in
Dx/ Tx/ Gx, the meter serial number recording will start as soon as the supplier delivery
note is accepted at the relevant store by scanning or bulk uploading meters details into
store or by tracking meters with RFID technology. When store inventory system place a
reservation to replenish meters to any sub section store the same tracking needs to
take place and supporting systems needs to be updated accordingly with meter latest
location. When customer request are logged and it could possibly involve a meter to
restore power a meters will be issued to TSU together with the Work order request.
Depending on the customer request and data from CRM system the correct meter will
be issued to the TSU. The location of the meter will again be updated from divisional
sub store location to the relevant technical personnel location. After meter change out
the meter movement form will be completed electronically and it will update the meter
location to customer location returning the removed meter into the TSU location. The
captured information at customer level needs to interface with the CC&B system to
update the meter for billing purposes.
mm
240-83570075 Rev 1
3. Meter history
All meter history updates need to be stored against the meter. Each history record
must contain the User ID of the person capturing the change, as well as the User ID of
the person who is responsible for the change. In most instances these two IDs will be
the same, but there can be times when the update and function are performed by
different people. User ID meta data should map to the business hierarchy. The user
selection should only reflect the relevant location hierarchy down selections when
completing movements on meters. Some of the meter history records will be
automatically generated, in which case, the System name must be recorded in the User
ID field.
Each history record must have a date and time stamp, both of when the history was
being captured, as well as when the history update occurred. Again these two date and
time stamps will be the same in most instances, but can be different if the capturing of
the history update is not real time.
The system that was used to capture the history record update must also be stored. In
most instances, the history record will be updated from the Meter Asset Management
system, but there may be instances where the update will come from another system.
Besides meter location history updates, the other history records that need to be
captured and stored include:
 Meter Supplier data supplied
 Calibration records
 Test certificates
 Suspected reason(s) for failure
 Actual reason(s) for failure (the failure modes of meters need to tie up with
current initiatives for Maintenance Engineering strategies initiated in design base
environment?)
 Maintenance performed
 Opening meter reading performed
 Final meter reading performed
 Warranty period expired
 Routine maintenance work due
 Routine maintenance work requested
 Routine maintenance work completed
For each of these meter history records, there needs to be the associated detail
available.
 Meter Supplier data will show all the required data as supplied by the meter
supplier.
 The calibration certificate needs to be stored and linked to the calibration history
record.
 The test certificates needs to be stored and linked to meter history
 The suspected reason(s) for failure should be from a drop down list of possible
failure reasons.
 The actual reasons for failure should be from a drop down list and can be
updated by an Eskom technician and/or from a Meter Supplier.
 The Opening meter reading performed must show the actual reading taken
when a meter is installed.
 The Final meter reading performed must show the actual reading taken when a
mm
240-83570075 Rev 1
meter is removed from an installation.

 The Warranty expiry rule must be shown here. In most cases this will be the
date when the warranty expires, but it may be some other parameter that is used
to determine the warranty period (such as hours in usage, total measurements
performed, etc.)
 Routine maintenance work due will show the date when the meter was due for
routine maintenance. If the maintenance philosophy is run to failure, there will
be no routine maintenance due. The maintenance due date should initiate the
Work Order process to have a Work Order Request, or a Task Number for
relevant division and craft.
 Routine maintenance work requested must show the work order number
generated that is associated with the work request.
 Routine maintenance work completed must show the date and time stamp of
when the maintenance work was completed, as well as the date and time stamp
of when the record was captured, and the system used to capture the record. It
must also show the actual maintenance performed and results of tests
performed.
4. User ID access
The Meter Asset Management system needs to have a link into the SAP HR system, in
order to derive the User IDs directly from SAP HR. In this way, it will be possible to
determine the actual person who is responsible for the update of the meter history, or
who fulfilled a role in changing the meter history.
Different profiles with access privileges should be created to enable users in different
disciplines of the business to view/ read/ write data relating to their profile only.
 Senior store person profile RDC & CNC
 Store person profile RDC, CNC, ED LAB & RP
 Dispatcher profile RMC/ Scheduler profile Plant
 Works coordinator profile CNC and CC&B
 Service representative profile CS
 Service agent profile CS
 System administrator profile
 Technical service unit TSU [TSO/PTO/ STO/ TO – Mobile unit access]
 Contractor [Mobile unit access]
5. Meter supplier’s meter information

The Meter Serial numbers (asset numbers) will be added onto the Meter Asset
Management system when they are received into the RDC Store (or when they are
installed, if the meters were supplied by the electrification contractor – normally
electrification contractors do not supply own meters they receive meters from RDC
stores). The meter supplier’s meter information will not be available at either of these
points, and must be supplied directly from the meter supplier.
If the meter is not supplied to Eskom stores first, before being installed by the
Contractor, the Contractor would be responsible for supplying the meter supplier’s
meter information. There are projects called Turn Key projects where a new town/
village is developed by private institutions/ Municipalities/ Mines and the appointed
contractors supply the residential properties with meters. Eskom only become aware of
these projects when they apply for electricity in these towns. Eskom Customer service
together with Electrification projects coordinators should then perform an audit or
request the data from the relevant contractor/ municipality/ mine in a PCS file format.
mm
240-83570075 Rev 1
The meter asset management system should then be able to upload the relevant file
with the meter movement information. For Gx and Tx meters, the meter will only
become Eskom property once the take-over certificate has been signed. Meter supplier
information should be supplied by the installation contractor along with the take-over
certificate.
When a meter is received into stores, it is not going to be possible for the Receiving
Clerk to capture the entire meter supplier’s meter information, as required by Eskom, so
this information must be supplied directly from the meter supplier, and loaded onto the
Meter Asset Management system.
5.1 New meters received

The type of information required by the store person when receiving meters from a
meter supplier, would include:
 SAP bin/ material number
 Meter type: PP/ Conventional [Prepaid/ Post-paid]
 the meter supplier manufacturer name,
 Meter serial number, on PP meters the first two digits specify the manufacturer
name?
 Configuration details about that meter type (each meter type would have specific
requirements),
o PP-Prepaid meters –
 ED=Energy dispenser
 ECU=Electricity control unit
 Amp rating e.g. 60A or 20A;
 Model numbers.
o Conventional meters
 Amp ratings
 Constant [multiplier to calculate consumption]
 Model numbers
 Single phase or poly/ three phase meter
 the manufacture date,
 manufacture batch number,
 warranty expiry date,
 SAP order number,
 Calibration certificate and date,
 Test certificate.
To capture a Meter Serial number into the system for the first time, the user will need to
select the correct meter Commodity, Supplier and Type etc. The meter serial number
needs to be validated against the length and format requirements for that selected
Meter Type. The meter serial number needs to be unique for that Meter Type.
There needs to be a function to upload the supplier’s meter information. The function
must allow the user to select the Meter Type that is about to be uploaded. This function
could be used by the meter supplier directly after dispatching meters, or could be used
by an Eskom employee – not necessarily the Stores receiving staff.
The upload function needs to validate the serial number length and format for the Meter
Type selected. The upload function needs to validate that the meter serial numbers
being uploaded, are unique for that Meter Type.
mm
240-83570075 Rev 1
There needs to be some form of file validation to ensure that the number of meter
records found in the file match the number of meter records initially loaded into the file
(to make sure that the complete file is received from the supplier).
Only the lines that have experienced problems must be rejected. All other meter serial
numbers must load correctly.
The upload file must contain the SAP order number, and this number must be validated
to ensure that the number of meters supplied is less than or equal to the number
specified in the order. There should be a running total of meters supplied against the
order, so that the final figure of meters delivered against an order number can be
validated against the number of meters ordered.
Any errors experienced in the uploading of the file, must be included in the Fault Report.
The errors must be specified by file line number, the meter serial number and the exact
errors being experienced, such as non-unique meter serial number, serial number
format or length errors. The Fault Report must give details of the total number of
meters in the file, the total number of meters loaded, the total number of meters
rejected.
The Meter Asset Management system must attempt to match all meter information
records that are in the upload file, to meters that have been received into the Regional
or local Stores (RDC, CNC, Tx store, PTM or Power station store), and may already
have been issued to a technician to be installed (the TSU) (or may even be installed). If
a meter information record is found to match a physically received record, the meter file
information must be added to the meter record to make one complete meter record. If
there is already meter file information about a meter that has been received into Stores
on the Meter Asset Management system (or has got further in the meter location cycle),
the new meter information record must be rejected from the upload, with reasons of
“duplication”?
The meter file may contain meters that have not yet been capture into Regional Stores
(RDC, CNC, Tx store, PTM or Power station store), (or Installed). These records must
not be rejected. The meter information records need to be kept and these records
searched whenever a new meter is captured onto the system (either to Stores (RDC or
CNC), issued to the technician (TSU) or installed). If a meter information record is
found to match a physically received record, the meter file information must be added to
the meter record to make one complete meter record.
The file format of the meter upload will need to be defined and agreed with all meter
suppliers who will be supplying meters (all meter types) to Eskom (part of tender
process would be to test and approve file formats received from the meter suppliers).
There should be a process of closing the loop between receiving the meter file and the
commercial process of paying for the meters, so as to encourage the meter suppliers to
be punctual with the meter information delivery. There should be an Order Fulfilment
Report that is drawn once the meter information has been uploaded, that indicates the
number of meters that have been uploaded and against which order number(s). It must
also show the number of meters for those orders that have actually been received by
the stores that have been matched up to the meter information records. These
matched up meters (physical and meter file received), need to be tagged as being
accounted for.
mm
240-83570075 Rev 1
The Order Fulfilment Report will act as an acknowledgement of receipt to be sent back
to the commercial process per SAP order number, in order to approve the payment for
the meters.
It must be possible to run the Order Fulfilment Report at any other stage, per meter
supplier, for specific order numbers, or all order numbers or a range of order numbers,
to account for any physical meter to supplier’s meter information matches, that have
occurred, since the meter information file was initially loaded.
There will need to be a reconciliation of the number of meters physically scanned into
the store, compared to the number of meter information records successfully uploaded
in the meter upload files.
There would need to be a report, per meter supplier, per SAP order number (or all
orders), per date range (or all dates), of meters that have been received by stores (or
directly installed), but not in an upload file, and also meters in an upload file that have
not been received by stores or installed.
5.2 Repaired meters from supplier

If meters are sent back to the supplier to repair, and are not repaired in house, it must
be possible to compile a file of all meters that have been sent to the supplier for repair.
The meters must have been captured in the system as received to Repair Store-CNC,
and then to Repair Store-RDC. Only meters for a specific supplier will be sent to that
supplier for repair, from the RDC.
If meters within the warranty period only get sent back to the supplier, there must be a
validation to ensure that the selected meters are within the warranty period (uninstalled
date is before the warranty or extended warranty expiry date).
If meters that are out of warranty are being sent to the supplier to repair, there should
be a separate file created for those meters.
The repair technician must be able to capture what the suspected reason for failure is.
This reason needs to be sent in the repair request file to the supplier against the unique
meter number. (Codes can be given for standard suspected failure reasons.)
When the meters are returned from the supplier, there needs to be a repaired meter file
sent with those meters. The file needs to contain all the information about the meter, as
per a new meter file, but must also include what was repaired (codes can be given to
the standard repair types), as well as what the actual fault was. It must also include the
current, new or extended warranty expiry date for the repaired meter. (The warranty
period impact will be part of the meter supplier contract.)
Any costs for repairs will not be included in this meter repair file. This information will
need to be handled separately, but there should be some validation in process, to
ensure that repair costs charged, do match to meters and repair meter files returned
from the supplier.
If a meter is scrapped, then a record must be returned to indicate that the meter was
scrapped.
mm
240-83570075 Rev 1
If the meter was still within its warranty period, then a replacement meter must be
supplied for that meter, if the fault is on the meter supplier’s side (if this is part of the
meter supplier contract). The under warranty replacement meter details must be
indicated to show that it is a replacement meter. It must be possible to link these
meters as being replacements for failed meters, so that the Meter Asset Management
system can reconcile the number of meters scrapped by the supplier, that were within
the warranty period, but that have been replaced, and how many meters have not been
replaced, that were within the warranty period and were the supplier’s fault.
6. Information required for each meter type

Each of the meter types need specific information, in order for the correct configuration
and details to be stored.
There are a number of attributes that all meters should have stored about them.
 Hardware ID
 Firmware ID
 Purchase cost
 Financial value
 Manufactured date
 Manufacture Batch number
 Purchase Date
 SAP Purchase order number
 PiLog Item number
 Warranty expiry date
 Warranty over a time period of being installed, or after having read a specific
amount of a commodity i.e. after having read 100 000 kWh – if applicable
 Extended warranty expiry date or time or usage period.
 Meter owner (Eskom, external or shared by both)
 Calibration date, as been submitted by the supplier.
 Configuration programming records. MAMS should also allow for uploading
latest meter configurations done by Eskom technicians depending on the
customer tariff structure and or changes.
6.1 Electricity meters - Pre-paid

Each of the prepaid meters stored on the system, must also contain the following fields:
 Supply Group Code [SGC]
 Tariff index
 Key Revision number
 Amp limit
These fields can be updated through the life of the meter, and must reflect in the
meter’s history with the date and time of the update, and User ID and system that
created the change.
Whenever Key Change tokens are issued for a meter, this information must be sent
back to the Meter Asset Management system to update the meter’s history. The meter
card that is issued with the meter should also be reprogrammed when the key change
tokens are issued. Key change tokens are issued from the Online Vending System/
Prepaid Supply Gateway (PSG), either directly to the customer, or via SMS. Require
integration between vending/ billing system and meter asset management system to
update any key change token properties on meters asset management system.
mm
240-83570075 Rev 1
6.2 Electricity meters - Smart Meters (AMI and ULM)

Each of the smart meters stored on the system, must also contain the following fields:
 Electronic address depending on the communication protocol [e.g. IP]
 Proprietary master station linked to.
 Concentrator meters are linked too.
7. Entry points for the meter onto the Meter Asset Management system
There are 2 different entry points for a meter to be initially captured on the system. That
is when they are entering the stores from the manufacturer (or as a warranty
replacement of a failed meter), or when the meter is installed at the customer Service
Point or asset location for Stats and Tariff meters.
If a contractor has been assigned to electrify an area, part of the contract will need to be
to supply not only the customer and meter details, but the meter supplier’s meter
information as well, if the contractor buys meters directly from the supplier. Turnkey
projects can also be run so that the contractors receive their materials, including meters,
from an Eskom Store (either Regional or local (RDC/CNC)), so that all materials used
within a project have been ordered and received through Eskom’s buying process.
It may be possible (due to bad business processes) that the meter is captured as
installed at a Service Point, and then the file is uploaded from the supplier, giving all the
meter details. There needs to be a decision as to which meter data is to be over written
by which if there is a discrepancy. The meter location record of being “installed” should
over-rule the location of being “in Stores”. The latest recorded movement transaction
location should be the physical location you will find a meter in. The historical
transactions against the same meter should show the meter location history through the
asset management process. High level view should display meter latest location on top
and first transaction at the bottom. This should cover the meter total life cycle from first
day entering RDC to last day when RDC scrapped the meter.
The multiple entry possibility should be prevented, as far as possible, by improving

business processes and by ensuring that the meter suppliers are incentivised to supply
meter information files, in order for them to be paid for the meters.
Electrification contractors should also be incentivised to supply meter and customer

connection details first, before being paid. If the data about the meter, in the meter
information file, and the physical receipt of the meter either into Regional Stores (RDC),
local Stores (CNC) or captured as being installed at a Service Point i.e.
captured/scanned into the Meter Asset Management are matched, the meter supplier
can be paid for that meter, or the contractor can be paid for the installation of that
Service Point. The whole SAP order would not need to be fulfilled before payment for
the completed portion is received (this does depend on the agreement of the supplier /
contractor contract).
When meters are received by Stores, these meters need to be physically scanned in.
This information must be updated on the Inventory Control system, the SAP ordering
system and the Meter Asset Management system, from the single scanning. A decision
needs to be made as to whether the leg to SAP ordering only occurs, if there is a match
of meter receipt into Stores and from the Meter Supplier Information data.
mm
240-83570075 Rev 1
The meter serial number must be validated as being of the correct length and format,
for that meter type, and also that it is a unique meter serial number. Non-unique meter
serial numbers must be rejected, with an error message to the user of the duplicate.
The Meter Asset Management system will store the meter serial number and any other
information that can be derived from the meter serial number being scanned in. There
needs to be an attempt to match any meter serial numbers scanned in, with any meter
information that has been uploaded from a supplier’s meter information file, that has not
yet been matched up to a physically received meter. The physical meter location record
will then combine with the meter file information to create a complete unique meter
record.
8. Meter installation information

When a meter is installed in a location (customer or stats meters), all the information
about the location of the meter needs to be captured and stored. This information
includes the network information of the meter’s location, the GPS co-ordinates of the
location, the customer and account information linked to that meter ensuring proper
customer network link [CNL] is established?
If the meter is a stats or tariff electricity meter, it is still necessary to be able to exactly
locate the meter from a GPS perspective and from a network perspective. These
meters will not have a customer record, as the post and prepaid electricity meters do,
but it will be necessary to know where on the network the meter is positioned. They will
need to be linked on the Feeder Balancing Module and/or the Energy Balancing
Module, as well as their location will need to be stored on SCADA mapping it to the
LO10 feeder data of an network.
If the meter is measuring a point from which generation, transmission, international

boundaries or distribution is “billed”, this meter data needs to be connected to the MV90
system or Feeder Balancing Module and/or the Energy Balancing Module system that
records the handover point between generation, transmission and/or distribution. The
actual measurements or readings from the meters will not be stored in the Meter Asset
Management system.
The meter location of an installed meter needs to be accurate down to the final network
detail (Service Point for customers’ meters). It must be possible to know, from a
network perspective, where exactly a meter is located, on which feeder, down side of
which transformers, on which phase (if applicable). The network address is made up of
the Transformer and the last pole before the meter. The network address information is
currently resident on Small World for HV and MV network and CNL for LV network, or
SAP PM for HV network (TX). The Transformer name and pole number information
captured must be validated against these systems, when the information is captured.
The Small World and CNL systems need to know that a specific meter is installed at a
specific point. The Meter Asset Management system will be able to give all meter asset
data associated with that specific meter.
The Customer Information System (CIS) will store all the customer specific information
and will know which specific meter is installed at that Service Point, but any further
meter data will be obtained from the Meter Asset Management System. Regular meter
readings will not be stored in the Meter Asset Management System.
mm
240-83570075 Rev 1
The capture of a new customer and linking that customer to a meter, meter change out
or connection termination should only be captured once. It must not be necessary to
capture the service point, meter detail, customer detail, physical and network location
detail more than once. The Customer Information System, Meter Asset Management
System, FBM, EBM, SCADA, GIS and the Network Systems (Small World, SAP PM or
CNL), where applicable, need to be integrated so that the required information is
populated from one set of capture screens, into the required systems.
Each different meter type will need its own specific information that needs to be stored.
There needs to be functionality to capture new installations, meter change outs and
termination of supply.
8.1 New installation

It must be possible to capture the meter asset information, when a new installation is
being captured. This may be in two separate steps as an application and then a
connection, or the application and connection may be captured at the same time.
The clerk needs to be able to capture all the required and compulsory fields for the
meter, such as the manufacturer (unless the manufacturer code is part of the meter
serial number) and the meter serial number.
If the meter is a post-paid or stats meter, the start meter reading will need to be
captured and this information sent to MDMS for managing the meter readings.
There needs to be a date and time captured, when the meter was installed, as well as
the date and time of when the installation was captured as being installed. There
should also be a date and time of when the installation was uploaded onto the system.
It would then be possible to view the delay between actual installation date and time
and capture date and time onto the system. There should also be an activation date
when the meter is live this stored on the meter service point records in CC&B. In CC&B
the meter has an activation date and a de-activation date. This means when the meter
is changed out it will be de-activated in CC&B on that date and the new meter installed
will have the same date and time as activation date from where the billing system will
start counting again. The historical meters against the service point will stay linked to
the SP.
The meter serial number must be validated against the same validation rules that are
used for capturing a new meter into the Meter Asset Management System. The
uniqueness of the meter serial number must also be validated against all meters loaded
on the Meter Asset Management System. A meter being installed, should already exist
on the Meter Asset Management System, as having been received in stores (RDC /
CNC / Repaired in Store / Warranty replacement in Store), then issued to the technician
(TSU). When the meter is captured as being installed, its history must be updated to
Installed, and show the required installation information. This is the correct route that a
meter should follow.
Due to process problems, it may be necessary to add the new meter onto the Meter
Asset Management system, as it is being captured as being connected to the customer.
The new connection form will not contain all the information required for a new meter to
be loaded onto the Meter Asset Management system, so only the basic information will
mm
240-83570075 Rev 1
be captured at this point (the clerk will not know the manufacturer date, batch number,
warranty period etc.).
The system must try to match any meter data, per meter serial number, that has been
uploaded from the supplier upload files, that has not yet been matched to meters
received by stores or installed. All the information supplied by the meter supplier will
then be linked to the meter that has been installed.
It must be compulsory for the clerk to capture the network information of where the
installation has taken place (transformer name and last pole name). This information
must be validated against Small World and/or CNL.
The GPS co-ordinates of where the meter is being installed must also be captured. If it
is not possible to get a location reading (highly built up area, or overcast day), there
needs to be an electrification project or area GPS location stored. This information
must be validated against the GIS location information.
All other information that is normally captured on the installation sheet must be captured
in the relevant systems. Where there is meter seal information, that information needs
to be captured. A meter can have up to 6 meter seals, and each seal is an alpha
numeric field, made up of the alpha representing the region and a numeric field. The
combination of the complete seal number must be unique.
A meter may be linked to at least 3 CT and / or 3 VT or 3 CVTs. This information must

also be stored against the meter record. Only specific meter types will be linked to CTs
and VTs, so these fields must only become compulsory for those meter types. Each
CT, VT and CVT has a unique serial number. These serial numbers must be validated
(length, format and uniqueness) at the time of capture. CT and VT serial numbers
needs to be integrated from Smallworld or Maximo where plant have created and
documented the details and the same on Gx SAP system side.
There are other assets that may be part of the meter asset installation. These assets
also need to be associated with the meter at time of installation.
 Meter Panel – not uniquely numbered asset, but size and design needs to be
captured.
 Modem – the modem type, antennae type, and unique identifier for the
modem.
 SIM details – all the details to be able to connect with the SIM, such as the
phone number, cell phone network provider, SIM number, PIN, PUK.
 Circuit breaker – the details of the size of circuit breaker installed.
 Surge arrestors – the details of the surge arrestors installed.
There may be between 5-10 photographs that need to be taken by the field technician
of the meter installation, using the hand held device. These photographs need to be
stored against the meter history and must be accessible for any future work associated
with the meter (maintenance site visits, change outs, physical meter readings etc.).
There may be commissioning information that needs to be captured, to make sure that
if the meter communicates to the correct control Master Station (smart meters), that that
information is captured against the connection record.
mm
240-83570075 Rev 1
The clerk details must be stored against the record that is being captured, along with
the date and time of when the information was captured. It is necessary to capture
which technician was responsible for the installation. This can be used from a Quality
Assurance point of view. It should be linked to KPIs and contractor payments, to
ensure timeous handing in of connection information and also for high quality data.
The new installation needs to update the customer application record on the CC&B
system, and with all the relevant meter data, network data and physical location data.
(Still to define whether the location data will be master data on the Meter Asset
Management system or on the CC&B system. The Location data will need to be readily
accessible for CC&B, Customer management system, network management system
and the Meter Asset Management system, and validated against GIS).
The meter history needs to be updated to indicate that it is now installed, and must
show the customer ID of where it is installed, as well as the physical and network
position of the installation. Small World and/or CNL must also be updated with the
record of the meter being installed on that specific part of the network.
If the meter is already on the Meter Asset Management System, as installed, the new
installation record cannot be added against that meter serial number. The system
should give an error indicating that the meter serial number is not unique, and should
show to which customer that serial number is currently allocated.
There should also be a totals report indicating the number of new meters added to the
Meter Asset Management system as a new meter installation (i.e. missed In Stores, and
Issued from Stores), as a measurement to show whether that new meters being
captured in Stores first process is working properly. This should be a KPI for the stores
management team and part of the contract for supply for the meter supplier. It should
be possible to draw this report for a time period, for a specific TSU, or number of TSUs
and for a specific meter supplier or all meter suppliers.
There are instances of meters being installed for the first time, and failing immediately
on going live. It must be possible for the field technician to record a meter failure on
installation. Is it necessary to record it as being installed and then doing a meter
change out, or can the system allow for the meter to move from Issued to Technician
(TSU) to Uninstalled by Technician (TSU), without having to record the Installed step?
If it has to go through the installation step, the technician would have to send in a meter
change out Work Order request, which will slow down the installation and capturing of
data.
8.2 Meter change-outs

There needs to be functionality to be able to capture meter change-outs. All meter
change-outs have to come with a work order. (It is presumed that the work order
process will confirm that the customer needs to be reconnected, and that the customer
has not been disconnected due to some legal action.) There must be upfront validation,
before the work order is created, to ensure that there is no currently applicable
disconnection order against the customer record (this is not a validation that will be
performed within the Meter Asset Management system).
mm
240-83570075 Rev 1
In order for the meter change-out to be captured, the clerk should be able to capture the
meter currently installed, and the rest of the customer, technical and meter seal
information should be displayed.
What happens if the meter and/or customer are not on the system, when the meter
change out is being captured? The basic information about the connection should be
captured, but the rest of the application for the connection needs to be flagged as
incomplete, and a work order request sent to get the complete information about the
customer and the connection. An investigation is to be done before sending out a
Service Rep to investigate the installation and collect customer data to connect that
customer in CC&B. If the meter is not found, an investigation into whether the meter
was not registered on CC&B or exist at another premise.
If the failed meter serial number is not visible for the technician to write down, there
needs to be other information written down, so that the clerk can find the
customer/meter record another way, if it does exist.
What happens when there is no physical meter installed at the premises? What if the
meter is missing out of the installation box? What should be stored against the meter
that is not there?
The clerk should be able to validate that the configuration of the new meter that is
installed is the same as the failed meter (tariff, supply group code, amps etc. for prepaid
meters). For post-paid meters the capture screen must show what was the last
recorded meter reading, and when it was taken. The final change-out meter reading
must be validated, against the last meter reading recorded for that meter, to ensure that
it is equal to or greater than the last recorded meter reading. There should be a check
to ensure that the final change-out meter reading is within xx % of the customer’s
consumption pattern.
The technician needs to indicate if there were no seals present on the meter, at the time
of change out, or if the seals had been broken. If the meter was initially captured as
having a meter seal (or seals), and they have been broken and/or removed, the logging
of this fact, must initiate a fine being sent to the customer, via the CC&B process.
The clerk needs to be able to capture all the required and compulsory fields for the
serial number) and the meter serial number.
The meter serial number must be validated against the same validation rules that are
used by the Meter Asset Management system for adding a new meter. It must validate
the uniqueness of the meter serial number (and the other information that makes the
record unique) against all meters. It must not be possible to add a new meter with the
same serial number (and the other information that makes the record unique), if that
meter serial number is already on the system. It must not be possible to install a meter
against a customer, if it is recorded as being installed against a different customer
record.

(length, format and uniqueness) at the time of capture.
mm
240-83570075 Rev 1
also need to be associated with the meter at time of installation.
captured.
modem.
There may be between 5-10 photographs that need to be taken by the field technician
of the meter installation, using the hand held device. These photographs need to be
stored against the meter history and must be accessible for any future work associated
with the meter (maintenance site visits, change outs, physical meter readings etc.).
A new meter installation/change out should only move the meter from Issued to
technician (TSU) and then installed. (If the process is being followed correctly.)
If the old meter is a post-paid meter, it must be compulsory for the clerk to capture the
final meter reading. What must be captured if the meter is burnt out and it is not
possible to read anything? Would the Meter Data Management system calculate a
figure based on average consumption? The clerk must also capture the new meter’s
start reading. This information will need to be synchronised to the CC&B system.
All the information that is normally captured on the meter change-out form, needs to be
captured.
If the technician does not have a hand held unit, and the meter being changed out is
prepaid, the technician needs to give the customer a free issue voucher for the value on
the broken meter. This voucher information needs to be stored against the technician’s
user ID, to control the number of Free Issue tokens given out.
If the technician is not able to create key change tokens for the new prepaid meter, the
customer will need to be instructed as to what must be done to change the receive key
change tokens and recode the meter card.
It must also be possible for a prepaid to post-paid and a post-paid to prepaid meter
change-out to be performed and captured. The post-paid meter in either of these
scenarios, may be a Smart meter. There could also be a meter change out from
conventional post-paid meter, to a Smart meter. There could also be an installation
upgrade or down grade, such as a 20 Amp to 60 Amp, or vice versa, or a Single phase
to a 3 Phase, or vice versa.
All the information required for these meter type changes, must be captured, depending
on which meter type it is.
The meter seal information needs to be captured. This would include the type of meter
seal, the meter seal serial number, date and time of sealing. The old meter seal
information should also be captured as having been broken by the technician and
mm
240-83570075 Rev 1
updated against the old meter number.
The clerk should be able to update / correct physical and network data about the
customer and the meter, which has been filled in the form, by the field technician. This
updated information needs to be updated on the Customer Information system, Small
World and CNL and Customer Management systems where applicable. All changes to
the physical and network address must show who changed the record, and the date
and time stamp.
The clerk needs to capture that the old meter is uninstalled, and capture which repairs
store it is being handed over to. The repair technician will decide whether the meter
should be scrapped or repaired. In some OU’s there are metering LABs and other do
not have. In the OU’s with LABS the faulty removed meter could be moved to the LAB
for testing to determine if the meter is Repairable or Scrap-able?
In OU’s without LABS the PTA [Prepaid technical advisors] will visit CNC’s to assist the
CNC store person to test faulty removed meters to determine which meters should
move back to RDC as Scrap-able and which should be send back via RDC to suppliers
for repairs?
The meter history must be updated with the move, and must include the date and time
of the move, who captured the move, the field technician (TSU) who removed the meter
and who is now responsible for the meter at the CNC. It must also store the date and
time of when the information was captured. If this manual process is being followed (no
hand held unit used by the field technician), the meter should still be scanned in by the
CNC to indicate that it has been physically received there. When completing the MMF-
meter movement form the serviceable meter issued to the technician [TSU location],
this meter should move out of the TSU location into the Customer location and the
faulty removed meter will move out of the customer into the TSU location and then out
of the TSU location into the CNC location all in one transaction when the MMF is saved.
(The data update of the meter location history could get out of sync in this manual
process, because the change out information may be captured long after the failed
meter has been received by the CNC. The Meter Asset Management system would
need to show the meter history in the correct physical order, even though the capturing
of the information was performed out of order.)
There needs to be a formal hand over of the meters that have been uninstalled, and
formally received, on the Meter Management System, by a repairs technician, linked to
a specific repair store. The repairs technician should scan in each meter received from
the field technician. (What if the meter is burnt out and the bar code is not visible?
There is an internal chip in the meter that will store its serial number, as long as that has
not been burnt out as well.) The scanning in of the failed meters would change the
meters from Uninstalled TSU to Repair Stores-CNC. (What if the field technician does
not have a hand-held unit and the Meter record has not yet been updated to indicate
that it has been uninstalled, but is now being received into Repair Stores? The system
should allow for this incorrect order, as discussed above.) Field technician should also
request the meter blue vending card form the customer as well as possible previous
vending slips when meters has burned. This will enable technicians to get the meter
number identified from one of these sources.
The old meter history needs to be updated to indicate that it was uninstalled, and sent
to a Repair Stores, as well as the date and time and responsible person who changed-
out the meter and who is receiving the meter for repair. MMF - meter movement forms
mm
240-83570075 Rev 1
should be captured on either work order dispatched hand held unit or afterwards at
CNC on PC web interphase and needs to be saved before the Work Order could
change status to Close/ QA Close? Either the store person works coordinator, senior
clerk or the field technician should be able to capture the MMF required details.
There should be a way of summing the number of meters that are being handed over to
the repair technician, so that there can be a reconciliation of the number of meters
uninstalled, with the physical number of meters handed over to the repairs technician.
The Inventory control system will need to be updated at the same time (one scan,
multiple systems updates), to indicate that the meters have been received for repair.
A successful capture report can be used as part of the commercial process for paying
the technicians for work completed (especially if the technician is a contractor). Zero
errors in data should be a KPI for the field technicians.
Meter Asset Management system as a meter change-out (i.e. missed In Stores (RDC or
CNC), and Issued to Technician (TSU)), as a measurement to show whether that new
meters being captured in Stores first process is working properly.
8.3 Termination of supply

It must be possible to capture a termination of supply for a customer. (The legal /
customer requirements are not described here.)
It must be possible to find the customer record, by either searching on the customer
information, or on the meter serial number that has been removed from the service
point or network address.
The meter serial number needs to be confirmed as being the meter that was installed at
the Service Point or network address. The meter history must then be updated to show
that the meter has been uninstalled, with date and time of disconnection, and has been
returned to Repair Stores, as well as the date and time and person who captured the
information. This information must be updated against the customer, network and
meter record history (captured once, but updated on CC&B, Smart World or CNL and
Meter Asset Management systems).
If the meter was a post-paid meter, the final meter reading of the meter must also be
captured. This meter reading must be validated to be within xx% range of the
customer’s normal consumption pattern. The standard, regular meter reading
information will be held on MDMS. The final meter reading will need to be updated on
CC&B and MDMS.
If meter was Pre-Paid meter the balance of energy on the meter should be recorded. If
tapering is the reason for termination the meter infrastructure [Meter, base plate and
bundle conductor] should also be removed to prevent future tampering on installation?
If the meter was sealed, the seal number(s) must also be captured as being broken by
the technician. If the seals were found to be broken, by someone other than the
technician, the field technician needs to be able to capture this information, and this
should then trigger a fining process for tampering with the meter.
mm
240-83570075 Rev 1
9. Seal management system

There needs to be seal management functionality to keep records of each seal that is
placed on each meter, when it is installed. If the meter is just sealed with a clamp/pliers
seal, this information needs to be captured against the meter record, with a date and
time stamp of when it was sealed. Meters can be sealed with up to 6 seals. Most
meters are sealed with the unique serial number seals. The same seals are used for
sealing test blocks in some metering configurations. These will also have to be captured
to ensure recon of seal numbers.
There needs to be records kept of all the unique numeric seals that have received into
Eskom stores (RDC), and moved to the Technical Service Centre (CNC), and issued to
a field technician. This is similar to the meter life cycle, but once the seal has been
removed from the meter it is thrown away, so its life cycle will end after being
uninstalled, and will not go through the repair and warranty replacement cycle.
If the meter is sealed with a uniquely identified seal (or up to 6 seals), the information
about the seal(s) needs to be recorded (i.e. its unique serial number and the seal type),
as well as the date and time of sealing the meter. Seals are numbered with a
combination of 2 letters to represent the Province and 6 numbers. The combination of
the letters and numbers must make the seal serial number unique. The system must
not allow for duplicate seal numbers to be captured.
The Meter Asset Management system must validate that the meter seal number is in
fact unique and is not currently being used to seal a different meter. It must not be
possible to have duplicate seal numbers against a meter. The duplicate seal must be
returned to stores / destroyed (business decision needed).
If a meter has been sealed, the type of seal, when it was sealed, and (if applicable) the
seal unique number(s), needs to be part of the meter asset information that is shared
with the Small World and / or CNL system and the Customer Information System, and
the Customer Relationship Management systems.
It must be possible to capture that the seal has been broken (tampered), or that the
technician has removed the seal (in order to maintain or replace the meter). If the
seal(s) have been broken (tampered), this information needs to be recorded, and from
this record, a customer fining process for tamper must be automatically initiated.
It must be possible to configure the Meter Asset Management system whether to

enforce meter seal data being captured for specific meter types and how many seals
should be used (if any), and also to capture what type of meter seal is to be used for
that meter type.
If the seal to be used for a meter type is to be a uniquely identified, the Meter Asset
Management System must enforce the capturing of the unique seal(s), when the meter
installation information is being captured.
Where existing meters reside in Generation boundaries without seals and business do
not require seals in this environment the system should allow for exclusion of seals in
meter installations at Generation divisions.
mm
240-83570075 Rev 1
10. Hand held device for meter installation

There is a requirement to be able to capture the required information for customer and
stats and tariff meter installations and change outs. For meters residing in substations
or on grid feeders the system should allow for substation name and feeder location
name/ numbers in the place of the customer details
10.1 New installation

It must be possible to capture the meter asset information, when a new installation is
being captured. The hand held unit should be preloaded with the new connection work
order request, to inform the technician where the meter needs to be installed and what
type of meter needs to be installed there (type of meter, amp, single phase or 3 phase,
prepaid or post-paid, tariff or stats meter etc.) and meter seals if required. A second
work order request could be generated and handed/ send via hand held device to ED
technician for LPU tariff/ Stats meters with the contracted tariff and meter configuration
settings for the programming of the meter configuration and communication testing.
The technician needs to be able to capture all the required and compulsory fields for the
serial number) the meter serial number (either by scanning in the number using a bar
code scanner, or manually typing in the meter serial number.
The hand held device must validate the meter serial number against the same
validation rules that are used by the Meter Asset Management system (especially
format and length). It will not be able to validate the uniqueness of the meter serial
number against all meters, only those meters that are on the hand held database
(unless the Hand Held Unit is on line. In which case the uniqueness of the meter serial
number must also be validated).
It must be possible for the technician to capture the network information of where the
installation is taking place (transformer name and last pole name etc.). The format of
this information must be validated.
The device must also be able to determine and store the GPS co-ordinates of where the
meter is being installed. (What about when it is not possible to get a location reading?
There needs to be some decision made as to what GPS co-ordinates would be used if
no GPS reading can be obtained due to high rise buildings and/or overcast skies.) The
GPS co-ordinates need to be created and stored in the agreed format (using minutes or
decimals, so that no conversion is required when uploading the data to CC&B and
Small World and/or CNL).
All other information that is normally captured on the installation sheet must be able to
be captured on the hand held device.
Depending on the meter that is being installed, different fields will need to be captured.
The hand held unit will need to display the required fields, depending on the meter type
that is part of the application.
Where there is meter seal information, the seal information needs to be captured and
uploaded. A meter can have up to 6 uniquely numbered seals installed. Each seal
needs to be captured and validated to be in the correct format, and also to be unique
(can only validate uniqueness against its own database, unless it is on line and can
mm
240-83570075 Rev 1
validate back to the main system database).

also need to be associated with the meter at time of installation as part of the meter
history.
captured.
modem.
There is a requirement that the hand held device can issue initialisation tokens for
prepayment meters to set their Supply Group Codes, Tariff, Amp, Key Rev Number.
This functionality needs to be highly controlled though, as it could be open to abuse,
and could also put the technician in danger, if they are threatened by the customer to
lower the tariff on the meter. Key change tokens should only be issued if the meter
being installed, as issued from the CNC to the technician, has the meter information
loaded on the device, and the customer application form has the required configuration
information loaded, and the meter data and the customer data differ. It must only be
possible to create key change tokens with the data preloaded on the hand held device,
and cannot be captured by the technician. It must be possible to disable this
functionality, if it is required that the technician does not perform this function. The
meter card will also need to be re-programmed with the changed meter initialisation
information. When key change tokens are issued, the meter’s history needs to be
updated with this information in the Meter Asset Management system.
There may be commissioning information that needs to be captured on the device, to

make sure that if the meter communicates to a control system, that that information is
received and allocated to the correct meter in the correct location.
If the meter is a post-paid or tariff meter, the start meter reading will need to be captured
and uploaded to CC&B and MDMS.
The technician’s details must be stored against the record that is being captured, along
with the date and time of when the information was captured.
It is not critical to sync the installation information real time. It could be done by
plugging it in to the master station to the hand held device (back office) at the end of the
day.
The upload of the new installation needs to update the customer application record on
the CC&B system, and all the relevant meter data, network data and physical location
data. The location data will need to be readily accessible for CC&B, Customer
mm
240-83570075 Rev 1
management system, network management system and the Meter Asset Management
system. The GPS co-ordinates of the location need to be validated against GIS.
There needs to be data validation of the meters that are being uploaded as installed.
The meter record should be found in the Meter Asset Management system, as being
Issued to Technician-TSU. The meter history needs to be updated to indicate that it is
now Installed, and must show the customer ID of where it is installed, as well as the
physical and network position of the installation. Small World and/or CNL must also be
updated with the record of the meter being installed on that specific part of the network.
If the meter serial number is not found on the Meter Asset Management system, must it
be possible to add the meter automatically with the data as captured in the hand held
device. This is not the recommended process for meters to follow, but it is felt that it is
better to receive the meter connection information, rather than reject it, due to poor
meter supplier and stores processes.
If the meter is already on the Meter Asset Management System, as installed, the new
installation record needs to be rejected.
If there are validation errors on the data that is being uploaded, those new installation
records need to be rejected.
There needs to be an upload completion report, to indicate how many records were
submitted to be uploaded as new installations, how many were accepted by the
Customer Information System, Small World, CNL, GIS and Meter Asset Management
system, and how many new installations were rejected. A full text reason for the
rejection needs to be given for each rejected new installation, with a reference to the
specific new installation, so that that record can be found. The rejected data must be
loaded onto a holding file on the hand held Master Station and the data needs to be
corrected from there and then re-uploaded onto the centralised system. There needs to
be a re-upload function to submit the records that have been corrected. It must be very
obvious to the hand held Master Station user to see that there are outstanding records
that need data correction. It must be possible for the user to reject single records, if the
data cannot be corrected. The data record must not be deleted, from a data audit
perspective, but must be removed from the list of records waiting to be corrected.
The successful upload report can be used as part of the commercial process for paying
the technician for work completed. Zero errors in data should be a KPI (except if the
meters captured as being In Stores (RDC or CNC) and being Issued to Technician
(TSU) process is the reason for the data errors).
There should also be a total indicating the number of new meters added to the Meter
Asset Management system at the time of new meter installation (i.e. missed In Stores,
and Issued from Stores), as a measurement to show whether that new meters being
captured in Stores process is working properly.
There are instances when a meter is installed, but when it comes to being energised,
the meter fails. This could happen to a meter in a new installation, or a meter change
out. It should be possible for the technician to capture the meter as being installed, at
that service point, and then create an immediate change out, and install another meter
at that service point. It should not be necessary for the technician to have to submit a
work order request, in order to capture the meter change out. When the new
mm
240-83570075 Rev 1
connection information is uploaded, the meter change out record will need to be
uploaded as well, so that a report can be drawn of all meters that fail on initial
installation, and so that the failed meter can be tracked as an uninstalled meter that
needs to be returned to Repair Stores and replaced by the supplier.
10.2 Meter change-outs

There needs to be functionality to be able to capture meter change-outs. All meter
change-outs have to come with a work order.
If a technician with a hand held device sees that there is a meter that needs to be
changed out, but there is no work order for that change out, the Technician needs to be
able to request a work order to be sent to the device, so that the work can be carried
out. The technician would need to input as much information about the meter, in order
to request the work order, such as the meter number, meter supplier, pole number,
transformer name feeding that meter, physical address, etc. If the hand held device can
go on line, the technician should be able to look up the customer detail, using the
information such as meter number, meter supplier, pole number, transformer name
feeding that meter, physical address, etc. The work order request would need to be
submitted to the Supervisor who would authorise this request, before it is sent as a work
order, back to the requesting field technician’s hand held unit.
What happens if the meter and/or customer are not on the system? A work order can
be requested anyway, with minimal information, and the technician must capture all
information possible, with the meter change out. The customer record needs to be
flagged as incomplete, and a separate work order created to complete the required
CC&B information or to find the original customer record.
What happens when there is no physical meter installed at the premises? What if the
meter is missing out of the installation box? What should be stored against the meter
that is not there?
In order for the meter change-out to be captured, the technician should be able to scan
the meter currently installed. If the hand held device is on line, it will be able to retrieve
all the customer information captured for this meter serial number. This could be useful,
to make sure that the new meter that is installed is configured to be the same as the
failed meter (tariff, supply group code, amps etc. for prepaid meters, as well as the
recorded purchase pattern for that meter – the technician can do a spot audit of
electrical goods compared to purchase patterns for that meter to know whether to look
out for meter bypassing evidence).
If the meter serial number is not visible and the hand held device is not online, the
technician will needs to use the information loaded from the work order for that
customer record.
If the hand held device is off line, and it is not possible to read the meter serial number,
the technician must capture the following details: physical address, network address,
customer information, as much information as possible about the failed meter –
supplier, meter type, amp setting etc.
The new meter needs to be captured against the customer record (or whatever
mm
240-83570075 Rev 1
information has been manually captured about the customer / location / meter on the
handheld device).
The technician needs to be able to capture all the required and compulsory fields for the
serial number) and the meter serial number (either by scanning in the number using a
bar code scanner-preferable, or manually typing in the meter serial number).
The hand held device must validate the new meter serial number against the same
validation rules that are used by the Meter Asset Management system (especially
format and length). It will not be able to validate the uniqueness of the meter serial
number against all meters, only those meters that are on it the hand held database
(unless it is on line).
If the old meter is a post-paid (or stats or tariff) meter, it must be compulsory for the
technician to capture the final meter reading. What must be captured if the meter is
burnt out and it is not possible to read anything? If the hand held device is able to
retrieve the customer record and last logged meter reading, the final meter reading
must be equal to or greater than the logged meter reading. (It would be good to have a
consumption trend to be able to determine if the final meter reading is within the
ballpark of this customer’s consumption trend – would give more accurate meter
reading records). The hand held device can then validate the final change-out meter
reading, against last meter reading recorded for that meter. (Validation rules of greater
than or equal to last meter reading, and within xx% of consumption trend.) The
technician must also capture the new meter’s start reading.
All the information that is normally captured on the meter change-out form needs to be
captured on the hand held device.
It must also be possible for a prepaid to post-paid and a post-paid to prepaid meter
change-out to be performed and captured on the hand held unit. The post-paid meter in
either of these scenarios, may be a Smart meter. There could also be a meter change
out from conventional post-paid meter, to a Smart meter. There could also be an
installation upgrade or down grade, such as a 20 Amp to 60 Amp, or vice versa, or a
Single phase to a three phase, or vice versa. Business terminology currently speaks
about conversion between meter types.
The meter seal information needs to be captured and uploaded. A meter can have up
to 6 seals installed. This would include the type of meter seal, the meter seal serial
number(s), date and time of sealing. The old meter seal information should also be
captured and updated against the old meter number.

also need to be associated with the meter at time of installation as part of the meter
history.
captured.
mm
240-83570075 Rev 1
modem.
The technician should be able to update / correct physical and network data about the
customer. This updated information needs to be updated on the Customer Information
system, Small World and CNL, Customer Management systems where applicable. All
changes to the physical and network address must show who changed the record, date
and time stamp, and indicate it was done from the hand held device.
There is a requirement that the hand held device can issue initialisation tokens for
prepayment meters to set their Supply Group Codes, Tariff, Amp, Key Rev Number.
This functionality needs to be highly controlled though, as it could be open to abuse,
and could also put the technician in danger, if they are threatened by the customer to
lower the tariff on the meter. Key change tokens should only be issued if the meter
being installed, as issued from the CNC to the technician, has the meter information
loaded on the device, and the change out work order has the required configuration
information loaded, and the meter data and the customer data differ. It must only be
possible to create key change tokens with the data preloaded on the hand held device,
and cannot be captured by the technician. It must be possible to disable this
functionality, if it is required that the technician does not perform this function. The
meter card will also need to be re-programmed with the changed meter initialisation
information.
The key change information must be stored against the meter history to indicate that the
meter has been reconfigured.
It must be possible to issue free issue tokens to transfer credit from the old broken
prepaid meter to the new meter. This needs to be done securely, so that the free issue
token function is not open to abuse. It must only be possible to issue a single Free
Issue token for a meter change out that is part of a work order. It must not be possible
to create a Free Issue token for any other meter. It must be possible to see all records
of Free Issue Tokens that have been uploaded from the hand held device, so that it is
possible to track possible abuse of this function. The Free Issue token records need to
be uploaded to the CC&B system for recon and energy balancing.
When the technician captures the change out, the system must record that the old
meter is uninstalled.
The field technician details must be stored against the record that is being captured,
along with the date and time of when the information was captured.
There needs to be a formal hand over of the meters that have been uninstalled, and
formally received, on the Meter Management System, by a repairs technician, linked to
the Repair Store-CNC. There should be a way of summing the number of meters that
are being handed over to the repair technician, so that there can be a reconciliation of
the number of meters uninstalled, with the number of meters handed over to the repairs
technician.
mm
240-83570075 Rev 1
The repair technician will decide whether the changed out meter should be scrapped or
repaired.
It is not critical to sync the meter change-out information real time. It could be done by
plugging it in to the master station (back office) at the end of the day. The only issue
would be if the meter history is updated first to say it has been received into Repair
Stores-CNC, and only later updated that it has been uninstalled. The order of the meter
history being captured, should wherever possible, be in the same order that it is actually
happening in real life.
The upload of the meter change-out needs to update the customer record, with all the
updated meter data, network data and physical location data. There needs to be data
validation of the meters that are now installed. The new meter record should be found
in the Meter Asset Management system, as being Issued to Technician. The meter
history needs to be updated to indicate that it is now installed, and must show the
customer ID of where it is installed, as well as the physical and network position of the
installation. Small World and/or CNL must also be updated with the record of the meter
being installed on that specific part of the network (last transformer and last pole
number).
The old meter history needs to be updated to indicate that it was Uninstalled, and when
received by the Repair Store, the history must show as being accepted into the Repair
Stores-CNC, as well as the date and time and responsible person who changed-out the
meter and who is receiving the meter for repair.
If the new meter serial number is not found on the Meter Asset Management system,
must it be possible to add the meter automatically with the data as captured in the hand
held device.
If the meter is already on the Meter Asset Management System, as being installed, the
meter change out record needs to be rejected in the upload process. It would be a lot
cleaner if this validation could be done when the technician is capturing the meter
change out in the field, so that as much information is checked at source.
If there are validation errors on the data that is being uploaded, those meter change out
records need to be rejected. These records must be stored on the Master Station, so
that they can be investigated and corrected, and then re-uploaded.
There needs to be an upload completion report, to indicate how many records were
submitted to be uploaded as meter change-outs, how many were accepted by the
Customer Information System, Small World and/or CNL and Meter Asset Management
system, and how many meter change-outs were rejected. A full text reason for the
rejection needs to be given for each rejected meter change-out, with a reference to the
specific meter change-out, so that that record can be found. The correction of the data
must be performed on the Master Station and the data be corrected from there. There
needs to be a re-upload function to submit the records that have been corrected. It
must be obvious to the user that there are meter change out records in the holding file
that need to be corrected and re-uploaded.
The successful upload report can be used as part of the commercial process for paying
the technician for work completed (especially if the technician is a contractor). Zero
errors in data should be a KPI (except if the meters captured as being In Stores (RDC
mm
240-83570075 Rev 1
or CNC) and being Issued to Technician-TSU process is the reason for the data errors).
Meter Asset Management system at the time of meter change-out (i.e. missed In Stores
(RDC or CNC) and being Issued to Technician-TSU), as a measurement to show
whether the new meters being captured in Stores first process is working properly.
There are instances when a meter is installed, but when it comes to being energised,
the meter fails. This could happen to a meter in a new installation, or a meter change
out. It should be possible for the technician to capture the meter as being installed, at
that service point, and then create an immediate change out, and install another meter
at that service point. It should not be necessary for the technician to have to submit a
work order request, in order to capture the additional meter change out. When the new
connection information is uploaded, the meter change out record will need to be
uploaded as well, so that a report can be drawn of all meters that fail on initial
installation, and so that the failed meter can be tracked as an uninstalled meter that
needs to be repaired or replaced by the supplier.
10.3 Termination of supply

It must be possible to capture a termination of supply for a customer on the hand held
unit. This termination request must form part of a work order sent to the technician on
the hand held device. (The legal / customer requirements are not in scope and not
described here.)
It must be possible to find the customer record, from the work order, so that the meter
serial number for that service point can be validated. What must the technician do if the
meter serial number against the customer record does not match the meter serial
number on the work order, or if the physical meter installed does not match the work
order or the customer record? The technician needs to confirm that the correct meter /
customer information has been sent in the work order. If the customer / location
information is correct, and it is just the meter that is incorrect, the technician needs to be
able to capture the meter serial number that is being removed from the service point.
If the meter was a post-paid meter (or Tariff or Stats meter), the final meter reading of
the meter must also be captured. This meter reading must be equal to or greater than
the last meter reading. It must be validated to be within xx% range of the customer’s
normal consumption pattern, if this can be loaded on the hand held unit.
If the meter was sealed, the seal number(s) must also be captured by the technician.
The technician must capture whether the seal(s) had already been broken, or was
broken by the technician. If the seals had already been broken, this information must
trigger an automatic follow-up action, when the data is uploaded to the CC&B system.
The termination record needs to be uploaded to update the Customer Service

information, MDMS, as well as the meter history in the Meter Asset Management
system and the Small World and CNL network systems.
The meter serial number needs to be validated as being the meter that was installed at
the Service Point. The meter history must then be updated to show that the meter has
been uninstalled.
mm
240-83570075 Rev 1
When the old meter is received by the Repair Store, the history must show as being
accepted into the Repair Stores-CNC, as well as the date and time and responsible
person who changed-out the meter and who is receiving the meter for
repair/maintenance.
The date and time of the termination must be uploaded. The date and time of the
upload must also be recorded against both, the customer network and meter record
history.
10.4 Meter maintenance investigation / work order request

When a meter reader is in the field, performing the meter readings, the meter reader
should be able to immediately log that there is a problem with a meter, and that log
should initiate a Work Order request for the technician to go and investigate the meter.
The Work Order request needs to be approved by the dispatcher/ CNC supervisor
before a Work Order is dispatched/ sent to the field technician.
The meter reader should have some basic information about the meter preloaded on
the meter reading hand held device. This should include the meter serial number,
supplier, and type of meter. There should be information about the physical and
network address of the meter as well.
To enable more accurate meter readings, the consumption pattern for that customer
should also be loaded, as well as the last actual meter reading recorded against the
meter. When the meter reader captures the latest meter reading, the device should
validate the reading captured, by comparing:
Is it greater than the last valid meter reading?
Is it within the consumption pattern range of the last valid reading?
If the new captured meter reading is not greater than the last valid meter reading, and /
or is not within the consumption pattern range of the last valid reading, the hand held
unit should alert the reader to confirm that the meter reading is correct. This will allow
the meter reader to correct possible miss-readings or miss-captures at source.
If the meter reader sees that the meter has not moved since the last reading (or has
gone backwards), or is “a lot” (what percentage would this be?) smaller or greater than
the consumption pattern, the meter reader can log a Work Order request for the meter
to be investigated by a field technician.
The meter reader may also see that there are other problems or potential problems that
need a field technician to investigate. The meter reader should be able to log a Work
Order request, using all the meter, physical and network location pre-loaded on the
hand held device, as well as to be able to give some description about the background
for the work order request. There should be a drop down of a number of possible
reasons for the request, that the meter reader can select from, such as meter not
working, meter tampered, meter missing, seals missing or broken etc. This list should
be configurable. There should also be a free text space for the meter reader to type in
other detail if required.
The meter reader should also be able to capture if there is a meter on a reading route,
but it does not exist on the hand held device. The meter reader should be able to
capture all the details about the meter, including meter serial number (or scan it in),
mm
240-83570075 Rev 1
supplier, meter type, as well as the physical and network address (at least last pole
number) of the meter. The meter reader’s hand held device should have some GPS
functionality in order for the GPS co-ordinates to be captured for the meter. The meter
reader will not be able to capture all the information to link the meter to a customer.
This would involve an extra visit to try and find the customer and possibly sign a new
contract with the customer.
A meter not on a reading route may also be due to a meter change-out that was not
captured on the system, so the customer exists on the Customer Management System,
but is linked to a different meter. If the GPS co-ordinates, physical and network
information is captured about the meter that is not on the hand held unit, and if there is
a customer on the hand held unit that matches the physical, GPS and / or network
address of the unallocated meter, the meter reader can suggest the link between the
meter and the customer, but this would need to be confirmed by a back office person.
The back office person would need to capture a meter change out and all applicable
systems updated with this information (CC&B, Meter Asset Management and Small
World or CNL).
The work order request and any other data correction information do not have to be
uploaded real time. It can be uploaded at the end of the day, onto the master station
(back office).
There would need to be back office reports to show all enquiries, data correction, work
order requests etc. that have been generated. There could be incentives for meter
readers to improve the meter / customer / network data, if many problems are known to
exist in a specific area.
The meter update details captured by the meter reader will not be immediately updated
on the Meter Asset Management system and Customer Information System, as there
should be some sort of validation of the information captured, before a meter change-
out can be captured.
The Work Order request from the meter reader should be uploaded to the Work
Management system and a work order approved and issued to the field technician.
11. Inventory control of meters

The Meter Asset Management system will not manage Inventory control and stock
levels in specific stores, for specific meters. There must be integration between the
Meter Asset Management system and the Inventory Management system, so that when
a meter is received or dispatched from stores, that the person responsible in the Stores
needs to capture the movement once, and both systems are updated.
It must be possible to perform inventory queries on the Inventory Management system

on a specific meter type and supplier, for a specific store, to reconcile the actual meters
that the system thinks are in stores, compared to what is actually in stores – down to
meter serial number. It would be useful to be able to separate those meters that have
returned from maintenance and those that are new or Warranty Replacements and
have never been installed, in the store’s inventory report.
 Meter Store stock Reconciliation Audits
Bi yearly store stock audits needs to be carried out with the hand held scanning
unit/ other technology decided upon. The store personal should receive an
mm
240-83570075 Rev 1
automatic reminder request from the material management system/ integrated

work management system to perform meter asset management recon audits.
Purpose is to verify that all meters listed per category on the meter asset
management system is still the true reflection of what physically are in store
shelves.
o Physical scanning of all stock in store location should take place on bi-
yearly intervals.
o After scanning all meter assets upload it into meter asset management
system.
o System should compare meter unique ID against latest movement location
and flag all location mismatches against this audit scan.
o System should have a function where senior store person could change
the mismatches found to the correct location with possible reasons for the
change.
o The previous action should update meter location on all systems it
integrates too, to ensure the meter location is in sync all over in the
business systems.
12. Meter maintenance requirements

It must be possible to log a work order request for a faulty meter (or any meter query)
using the meter reading device. This request must capture the following required
information about the meter:
Location (physical, GPS and/or network location), meter information, meter reading,
fault type, and/or account details.
With the upload of meter reading information, the work order request information must
be sent through to Work Order Management in order for a work order request to be
authorised and generated.
There needs to be information captured and stored, for each meter type about the
maintenance to be performed on the meter, and at what stages. All maintenance
performed on a meter must be logged, and all outstanding meter maintenance needs to
be displayed.
There should be alerts given for meters that are installed and are due to be maintained,
as per the meter supplier specifications and aligned with the maintenance requirements
determined for the different categories of meters. These alerts will be based on either
the meter supplier requirements, or from experience in the field. The maintenance
alerts will need to form part of a work order request that will need to be approved and
issued to a technician.
It must be possible to clear the maintenance alert, once the installed meter has been
maintained, with a record created of the maintenance performed. The record must
contain what maintenance was performed (preferably from a drop down box); by whom
and the date and time it was performed.
It must also be possible to capture a maintenance strategy of “run to failure” for the
meter type, in which case, no maintenance alerts will be generated.
Meter seals will also need to be captured with a “run to failure” maintenance strategy.
When maintenance requires seals to be removed new seal need to be applied after the
completion of the maintenance. The work order should then allow for an option to
mm
240-83570075 Rev 1
capture the new seal numbers applied to the maintained meters. These seal numbers
should be updated to all systems interphase with the meter asset management system.
It must be possible to link, in a document management system, any records, files or

reference material relating to the meter maintenance requirements per meter type.
It must be possible to give formal feedback to the meter suppliers, of meter failure rates
and life expectancy of meters. It must be possible to draw a failure report, per supplier,
per meter type, to show the time to fail, after installation. Possibly also show the actual
operating time of the meters (they may have sat in stores for some time), and also be
able to query the manufacturer’s batch range of a meter type.
13. Meter certification records

It is necessary to be able to store all the meter calibration certificates issued for each
meter. This requirement will mean that there will need to be document storage facilities
associated with each meter. The calibration certificate is most likely to be a paper
based certificate that needs to be scanned in for storage purposes.
From an ISO 9001 perspective records must be established and maintained to provide
evidence of conformity to governance, statutory and legal requirements. In terms of
ISO 9001 a record can be stored on any media: paper or electronic. The focus is that
the record media must comply with the following:
 Records shall remain legible
 Records must be readily identifiable and retrievable.
 A documented procedure shall be established to define the controls needed for
the:
o Identification and location
o Storage
o Protection
o Retrieval
o Retention time
o Disposition of records.
If an electronic option is selected, the following items will need to be considered:

 Legal requirements when setting retention times.
 Retention and access of electronic records, should consider the rate of media
degradation
 Availability of devices and software needed for access
 Records held in the email system
 Protection from computer viruses
 Unapproved or illegal access
 Proprietary information in records should be assessed to determine disposition
methods at end of retention period.
The information that needs to be stored on the meter certification will include:
 The meter unique identification (meter serial number, supplier, meter type etc.)
 The date and time of certification
 Who performed and captured the certification testing
 The result of the certification test
 The acceptable range for the certification test
 The detail of the unit that was used to perform the certification test.
mm
240-83570075 Rev 1
 The meter reading at time of certification.
It may be required to certify a meter in specific intervals in it life span. If this is a

requirement for this specific type of meter, all meters of this type must be linked to the
meter certification cycle, when they are initially loaded onto the system. When it comes
time for the meter to be certified, a works order request needs to be generated, per
meter to initiate the certification process.
Once the meter is certified, it needs to be monitored for the next due date for
14. Digital signature management

There are some meter types that transfer a meter signature to the master database, in
order to authenticate who they are and to set up a secure communication network
between the meter and the master database. These digital signatures will need to be
stored per meter (or derived from some meter data on the master database). The
storage and management of these signatures is done by the proprietary vendor Master
Station. There is a Multi-Vendor Integration layer for all the proprietary vendor master
stations.
15. Infrastructure requirements

 The network requirements for this centralised system are that it will be possible
to capture, update, and query any meter from any Eskom work station.
 There must be sufficient capacity to store all the meter records and the asset
history. There are currently more than 4 million prepaid and billed meters owned
by Eskom, and there are at least another 3 million households still not electrified.
(Eskom will not necessarily be the direct supplier to these households, but this
size of capacity should be planned for.) The average turn around on number of
new meters received into MATS at RDC level during 2013 was 287198.User
authentication (Novell will be migrated to Microsoft where the user authentication
functionality will be used – all users will have a username and password which
will specify their access). This will include all contractors working on these
systems.
o To access the current IDV the e-Directory is used. Going forward the e-
Directory will be replaced by the Active Directory when Microsoft has
been implemented.
16. Handheld Device requirements

 The handheld device requirements will be described in full in the mobile
workforce URS
 Meter Asset Management will need to have a device that is able to scan in the
meter serial number either by barcode or Radio Frequency Tag.
 The hand held device may need the functionality to be able to write to the Radio
Frequency Tag, if this functionality is required.
 The device will need to be able to take and store photographs of meter
installations "between 5-10 per installation".
 The device will need to be able to take GPS readings in the Eskom acceptable
format and accuracy.
 The device will need to be able to work on line and off line, depending on the
network available.
 It is unlikely that the hand held device will be used in the Generation metering
space, due to the small number of meters that are being managed in this area.
mm
240-83570075 Rev 1
Business Risk A list of tangible business risks that will be introduced because of the proposed solution.
Analysis
 This URS describes a fully computerised process. It is reliant on all people in
the process being computer literate and confidant.
 The centralised database of meters will need to be up and online at least for
normal field technician work hours, so that meter serial numbers can be
validated and the history updated. If the system is not accessible it will result
in data capture backlog or non-validated fields.
 The system will enforce the standardised procedure to be followed for the
meter history to be updated. If one leg in the process is not followed, any
further updates on the meter history will be blocked due to the previous step(s)
not being followed – there will be interdepartmental reliance’s on all processes
being followed correctly.
 There will be network capacity challenges if all meters are to be captured on
line in all areas. Slow capture and validation of meter data can introduce
frustration to the users, who will then resist the implementation of the system.
 The meter suppliers will need to update their systems and processes in order
to submit the files in the correct format, and in time.
 All personal involved in the meter asset management process [project
managers/ coordinators/ contractors/ RDC Warehouse Store personnel/
Energy protection personnel; Repair technicians in LABS/ Prepaid technical
advisors/ CNC field technicians and contractors] will need to be trained in the
new processes and systems, in order that all meters are captured timeously
and correctly.
 Contracts with meter suppliers and contractors will need to be updated with the
new system, file and data requirements.
 If there is no management buy-in and driving (championing) of the system, the
users in the field will resist the implementation of system and process changes.
 Network failure will result in the mobile application not being able to
download/upload work orders and other relevant information needed by the
technician/electrician in the field which might result in a delay in executing the
work orders until the network has been restored.
 The hand held device will need to receive a GPS reading when meters are
installed. If there is a high density of buildings or it is overcast, the GPS
readings may fail.
 The technicians using the hand held devices will need to be trained in getting
the most accurate GPS readings possible, otherwise the data captured will be
of little or no use.
NOTE: The business case must indicate the negative impact of not introducing the
proposed solution.
Business In the event that the URS proposed solution fails in operation it is imperative that
Continuity business can continue operating.
 It must be possible for the field technicians/ contractors to complete a manual

meter movement form for all movement types [installation/ change out/
removal/ conversion/ audit], if the hand held devices fail.
 Data capturers must still be available to manually capture meter movement
forms in hard copy format.
 There will need to be some leniency in applying the rules of how a meter can
first enter the Meter Asset Management system, to allow for meter suppliers
mm
240-83570075 Rev 1
not being up to date in sending out meter files as meters are dispatched.
 There will need to be some leniency in applying the rules of the order that the
meter life cycle is to follow, to allow for the clean-up of old data, capturing
outstanding connections and meter movement as well as if the hand held units
are off line and the meter history data is not updated in the correct order.
4.3 Reporting Requirements / KPI Measures

Reports should be developed on all major control areas of the Meter asset management system
process.
 Report on numbers and status of meters per meter hand over location, location type and name
with drill down options to see details of the meters. If meters are issued but not received on
handover point it should reflect as floating against the sender location. The report should show
numbers of meters per location with drill down options from highest to lowest level. E.g. OU/
Zone/ Sector/ CNC.
 Reports for meters issued from RDC to Contractors for Electrification project as well as Post
connections which are not yet connected to the customer. Meters with MMF linked to it is
connected to customer but without MMF meter movement form needs to be highlighted. Need
payment release control on this point.
 Meter history reports with all transactions linked to the meter.
 Management dashboards per business areas e.g. turnover of meters in a Zone/ Sector/ RDC/
CNC/ RP location, number of meter movements captured/ uploaded versus the number of
movements updated in CC&B.
 Report listing all meters issued to TSU’s with no meter movement forms linked to them.
 Reports reflecting meter failure reasons, number of meters failed during guarantee periods
showing manufacturer names and failure reasons.
 System user reports differentiating between user’s access levels and date stamp of last user
interphase with system.
 Reports on number of key change tokens issued per TSU/ RPO/ Contractor.
 Reports on number of credit tokens issued by TSU RPO/ Contractor to customers with rand
values.
 Stock level audit report of meters at different locations in the asset tracking system live cycle.
4.4 User Interface Requirements

Depending on solution proposed, different users could require different access and user interphase to
systems and data e.g. could need interaction to Small World, Maximo, SAP HR/ Finance/ Material
management and work management [Gx] platforms, CC&B, FBM/ EBM, MV90, MDMS and CNL.
 The network requirements for this centralised system are that it will be possible to capture,
update, and query any meter from any Eskom work station.
 There must be sufficient capacity to store all the meter records and the asset history. There are
currently more than 5.5 million prepaid and billed meters owned by Eskom, and there are at least
another 3 million households still not electrified. (Eskom will not necessarily be the direct supplier
to these households, but this size of capacity should be planned for.) The average turn around on
number of new meters received into MATS at RDC level during 2013 were 287198.User
authentication (Novell will be migrated to Microsoft where the user authentication functionality will
be used – all users will have a username and password which will specify their access). This will
include all contractors working on these systems.
o To access the current IDV the e-Directory is used. Going forward the e-Directory will be
replaced by the Active Directory when Microsoft has been implemented.
o The handheld device requirements will be described in full in the mobile workforce URS
mm
240-83570075 Rev 1
 The SAP HR system will be used in order to register the User IDs on the Meter Asset
Management system.
 When a meter is received from a meter supplier into an Eskom store, there will be an interface
between the Meter Asset Management system and the Procurement and material management
modules of the SAP system.
 When a meter is moved in and out of any Eskom store, there will be an interface between the
Inventory Control system and the Meter Asset Management System.
 When a meter is captured as being connected to a customer, there will be an interface between
the Customer Information System or Feeder Balancing Module and Energy Balancing Module,
the Meter Asset Management System and the Network systems. When the meter which was
removed during a change out have any credits left on it the movement form should kick of a
credit token verification and a free issuing process to return the credit balance to the newly
installed meter customer impacted by the change out.
 Various options to capture or upload meter movements should be in place for example from the
mobile works force devices and movement form could be captured and uploaded into the meter
asset management system, when electrification projects is complete the electronic data file could
be uploaded in bulk into the system and it should create meter movement forms for each line
entry uploaded.
 When a meter needs to be maintained, changed out or a connection terminated, there will be an
interface between the Meter Asset Management System and the Work Order system.
 When a meter is initially installed, changed out or a connection terminated, there will be an
interface between the Meter Asset Management System and the Meter Data Management
system for the start and end meter readings, as well as the Customer Information System or
Feeder Balancing Module and Energy Balancing Module.
 If a meter is linked to MV90 or the Multi-Vendor Master Stations (AMI meters), the meter and
meter location data need to be received from these systems to populate the Meter Asset
Management system.
 Generation meters information needs to be integrated with the EMDAS tool, so that any meter
movement can be shared between the 2 systems.
4.5 Information/Data Requirements

 The meter should contain at least the following information:
o SAP order number
o Manufacturer details:
 Manufacturer
 Meter number
 Rating/amp limit
 Manufacture Batch number
o Meter Model ID
o Hardware ID
mm
240-83570075 Rev 1
o Firmware ID
o What meter measures (up to 6 different things)
o Purchase cost
o Financial value
o Purchase date
o Timestamp when consignment checked in
o PiLog item number
o Warranty expiry date
o Warranty extension expiry date
o Meter owner
There will need to be extra fields for specific meter types that will need to be defined.
 For the meter history data, there will need to be the following:
o Location
o User ID of person responsible for location change
o Date and time stamp of location change
o User ID of person who captured location change
o System used for location change
Depending on the Location, there will need to be further information stored against the meter.
If the meter is installed, there will need to be further information, such as:
o the customer detail link,
o network link (transformer and last pole),
o GPS location
o Seals installed (up to 6 seals)
o CT, VT or CTVT installed (up to 3 each)
If the meter is to be repaired, it will need to have detail on the suspected failure reason.
If a meter is repaired, it will need to store what repair was performed.
If a meter is replaced with a new meter under the warranty period, there will need to be a link
between the old scrapped meter and the new meter.
4.6 Integration Requirements

The following diagram depicts all the systems that need to be integrated with the Meter Asset
Management system. Note that this diagram does not depict how the other systems are integrated with
mm
240-83570075 Rev 1
each other.
 Process Activity: Meter upload file – new meters

o The application should integrate to the SAP ordering system:
 To validate the SAP order number in the meter upload files.
 To confirm receipt of the meters against the order number once the meter and the
file data for that meter has been received.
 Validation of the number of meters currently supplied (per file and/or physically)
per order number.
 Validate that the PiLog number exists for each meter that is loaded onto the Meter
Asset Management System.
 Process Activity: Accept meter into Stores

o The application should integrate to the SAP ordering system:
 To confirm receipt of the meters against the order number once the meter and the
file data for that meter has been received.
o The application should integrate with the Inventory Control system:
 To update both systems with one scan, that the meter has been received both for
inventory management and for asset management.
mm
240-83570075 Rev 1
 Process Activity: Meter movement in and out of Stores

Whenever a meter is moved in or out of any store, both the Meter Asset Management System
and the Inventory Control systems must be updated with a single scanning. The “Store” is any
RDC, CNC, TSU, RP [Revenue/ Energy protection], RPO [Revenue/ Energy protection officer] or
Repair Store [Metering Lab location]. A Contractor would also be considered a TSU.
o The application should integrate with the Inventory Control system:
 To update both systems with one scan, whenever a meter is moved in or out of a
store for inventory management and for asset management.
 Process Activity: Meter maintenance requests

o The application should integrate with the Work Order request system:
 To process and approve Work Order requests that have been created, due to
meter readers or field technicians submitting requests from the hand held devices,
when they are in the field.
 To process and approve Work Order requests that has been created by the Meter
Asset Management system, due to meter supplier specifications or Eskom policies
on specific meter maintenance.
 To send out Work Orders to field technicians to investigate, maintain, remove or
change out a meter in the field, on their hand held devices or on paper.
 To close the Work Order once the action has been completed.
 To update the Meter Asset Maintenance System of the maintenance completed.
o If the maintenance is usage based, there will need to be integration to the MDMS system
to track meter readings:
 To check whether the usage criteria has been reached to trigger a Work Order
Request for planned maintenance.
 Process Activity: Meter certification requests

o The application should integrate with the Work Order request system:
 To process and approve Work Order requests that has been created, due to
meters needing re-certification after a specified time period or period of usage.
o The application should integrate with the MDMS system to track meter readings, if the re-
certification is usage based:
 To check whether the usage criteria has been reached to trigger a Work Order
Request for re-certification.
 Process Activity: New Meter installation

This information may be captured directly onto the system or the information may be captured
onto the hand held unit and uploaded onto the system.
o The application should integrate to the CC&B (Customer information) system:
 To update the customer record with the meter information.
 To update the customer record with any location data required (network, GPS co-
ordinates and physical location).
o The application should integrate to the Meter Data Management system:
 To update the billing records of the opening meter reading (post-paid meters only).
o The application should integrate to the Feeder Balancing Module:
mm
240-83570075 Rev 1
 To update the system on the stats meter information installed.

o The application should integrate to the Energy Balancing Module:
 To update the system on the stats meter information installed.
o The application should integrate to SCADA:
 To update the system on the stats and MV and HV meters installed.
o The application should integrate to Small World for MV and HV installations:
 To update on the MV and HV meters installed.
o The application should integrate to CNL for LV installations:
 To update on the LV meters installed.
o The application should validate against GIS for all installations:
 To validate that the GPS information on the location is correct.
 Process Activity: Meter change-outs

 To update the customer record with the meter change out information.
 To update the customer record with any location data corrected (network, GPS co-
 Any meter tamper remedial action / fining process to be initiated.
 To update the billing records of the closing meter reading of the old meter and the
opening reading of the new meter, and the date and time of this change out.
 To update the system on the stats meter change out information.
 To update the system on the stats meter change out information.
 To update the system on the stats and MV and HV meters changed out.
 To update on the MV and HV meters changed out.
 To update on the LV meters changed out.
o The application should validate against GIS for all installations:
 To validate that the GPS information on the location is correct, if any changes
have been received.
 Process Activity: Termination of supply

 To update the customer record with the implemented termination information.
mm
240-83570075 Rev 1

To update the billing records of the closing meter reading of the meter and the
date and time of this closure.
 To update the system on the removal of the stats meter and all accompanying
information.
 To update the system on the removal of the stats meter and all accompanying
information.
 To update the system on the stats and MV and HV meters removed.
 To update on the MV and HV meters removed.
 To update on the LV meters removed.
 Process Activity: Meter conversions [Pre Paid to Post Paid or Post Paid to Pre-Paid]
 To update the customer record with the meter conversion information. (old/ new
meter type, amp rating, serial number, model, supply group code)
 To update the customer records (e.g. names, surnames, address, National ID
number, Contact information-Tel #, email.)
 To update any location data corrected (network, GPS co-ordinates and physical
location, pole numbers).
 To update the billing records of the closing meter reading of the old meter and the
opening reading of the new meter, and the date and time of this conversion.
 To update the system on the MV and HV meters conversions.
o The application should integrate to Small World for HV, MV and LV conversions:
 To update on the MV, HV and LV meters conversions.
 To update on the LV meters conversion.
o The application should validate against GIS for all conversions:
have been received.
 Process Activity: Meter Audits

This information may be uploaded/ captured directly onto the system or the information may
be captured onto the hand held unit and uploaded onto the system.
 To update the customer record with the meter audit information.
 To update the customer record with any location data corrected (network, GPS co-
mm
240-83570075 Rev 1

 To update the billing records of the actual meter reading of installed meter found
on the premise.
 To update the system on the MV and HV meters audit data.
o The application should integrate to Small World for MV, HV and LV audits performed:
 To update on the MV, HV and LV meters audited.
 To update on the LV meters audited.
o The application should validate against GIS for all audits:
have been received.
 To update the system on the audits of the stats meter and all accompanying
information.
 To update the system on the audits of the stats meter and all accompanying
information.
 Process Activity: Meter Store stock Reconciliation Audits
Yearly store stock audits needs to be carried out with the hand held scanning unit/ other
technology decided upon. The store personal should receive an automatic reminder request from
the material management or work order system to perform meter asset management recon
audits. Purpose is to verify that all meters listed per category on the meter asset management
system is still the true reflection of what physically are in store shelves.
o Physical scanning of all stock in store location should take place on yearly intervals.
o After scanning all meter assets upload into meter asset management system.
o System should compare meter unique Id against latest movement location and flag all
location mismatches against this audit scan.
o System should have a function where senior store person could change the mismatches
found to the correct location.
o The previous action should update meter location on all systems it integrates too, to ensure
the meter location is in sync all over in the business.
4.7 Performance Requirements

The Meter Asset Management system must be available during working hours of the field technicians
who would want to perform meter change-outs. This time would be the greatest of the operating hours
of Inventory Control for the acceptance and issuing of meters, new meter installations and meter repairs.
4.8 Security Requirements1

 The asset management system should have an audit trail of each transaction/ movement the
asset make with date and time stamp together with the user login ID who actioned it?
 All system users should use standard system access authentication and be mapped per work
location depending on the SAP HR locations where employees operate from.
mm
240-83570075 Rev 1
Solution need to adhere to the Eskom Information Security policy, processes, procedures, standards and
baselines - http://it.eskom.co.za/dept/is/Pages/HomePage.aspx
4.9 Archiving Requirements

A list of back up requirements to be implemented:
 All meter data and history must be backed up as part of the source system backups on a daily basis.
 Data stored on the mobile device needs to be backed up every day (to be confirmed) if it has not yet
been synchronised back to the master station.
A list of archiving requirements to be implemented:
 All source systems archiving arrangements to be reviewed to ensure that information security
requirements are met.
 A decision must be made as to how long scrapped meters’ history must be kept
NOTE: The Functional Design Requirement provides further detail.
4.10 Operating Environment

Central server with data base and solution application and all users will interphase with the system via
their individual desktop PC’s, Laptop PC’s, Meter asset management bar code hand held unit scanners
at RDC/ CNC/ RP LABS and CNC Field workers hand held units [EDA]/ Revenue protection hand held
loggers [Trimble geo loggers] or if decided to perhaps track material assets via RFID then compatible
hardware to monitor flow in and out of all above locations.
4.11 Training Requirements

The Training Requirements need to:
a) Confirm if training is required
 Process overview and system application training will be required
b) Define list of possible training interventions required as a result of new business requirements
 System application training together with process and performance reporting should be
done to end user level.
 Supervisor/ Management performance reporting training will be required for all end user
supervisors as well as direct management levels.
 System administration/ support training.
c) Define possible training duration time

 Process, Content and reports training for end users - three days
 Supervisor and management reporting training - one day
d) Define who will be designing the training

 HR Training departments together with GroupIT, Super users and Subject matter experts.
e) Define provider of training, if known
 Previously the training was planned and scheduled by HR training departments and the
physical training was presented by business super users, subject matter experts and
GroupIT system administrators. Need to build train the trainer capacity in-house, training
identified super users and in turn they train the end users. Historical experience taught us
there are large turnover of staff in business in this environment?
mm
240-83570075 Rev 1
4.12 Testing Requirements (if applicable)

The following scenarios must be tested:
 The different entry points of a meter onto the system.
 The upload and download meter information from and to the meter suppliers.
 The different acceptable meter life cycles steps.
 The upload and download off information together with work order to the hand held units for new
meter installation, meter change outs and termination of supply.
 The electronic and manual capture of information for new meter installation, meter change outs and
termination of supply.
 Issuing of work orders based on maintenance task requirements.
 Capturing /scheduling of maintenance tasks.
 Run reports for evidence on the above bullets
 It is important that user acceptance testing is performed by staff that will be required to make use of
the final system, so that usability as well as functionality can be tested.
Note: All the different meter types need to be tested in all the above scenarios.
4.13 Legal Requirements (if applicable)

 All intellectual property belongs to Eskom.
 See legal requirements in functional requirements page 42 and 43 point 13. Meter
certification records.
 Eskom currently have exemption from the Machinery and Factory inspector to issue a meter
movement form [MMF] to a customer as a Certificate of compliance [COC] for Pre-paid ECU
[Energy Control Unit with build in Earth leakage protection] movements. The MMF act only as
an Installation certificate when performing ED [Electricity Dispenser] meter movements. More
information on this could be read on Technical instruction 04 TI-0?? Part: 25 Prepayment
Enquiries: Edison Makwarela at 011 690 4065.
4.14 Disaster Recovery Requirements

The disaster recovery requirements for the proposed solution:
 Source systems’ DR plans will be as per standard IM disaster recovery requirements

 Data stored on the mobile device needs to be backed up every second day (to be confirmed)
4.15 Business Continuity

In the event that the URS proposed solution fails in operation it is imperative that business can continue
operating.
 It must be possible for the field technicians/ contractors to complete a manual meter movement
form for all types of movements [installation/ change out/ removal/ conversion/ audit], if the
hand held devices fail.
 Data capturers must still be available to capture meter movement forms captured manually on
hard copy format and CNC TSU’s should be trained to capture movements them self into the
meter asset management system when back in office.
 There will need to be some leniency in applying the rules of how a meter can first enter the
Meter Asset Management system, to allow for meter suppliers not being up to date in sending
out meter files as meters are dispatched.
 There will need to be some leniency in applying the rules of the order that the meter life cycle is
to follow, to allow for the clean-up of old data, capturing outstanding connections and meter
mm
240-83570075 Rev 1
movement as well as if the hand held units are off line and the meter history data is not updated
in the correct order.
4.16 Capacity Planning Requirements (if applicable)

 Due to the great number of meters that are currently installed (4 million, predominantly
prepayment meters), and the number of houses still to be electrified (another 3 million still
outstanding), the capacity of the system to store this number of meters, and all their history, the
centralised system will need to be designed to cope with this extensive requirement.
 There will be some improvement in system space currently used by off line systems that to store
meter data that is then duplicated in the Customer Information System.
 The mobile application must integrate to the required source systems to download/upload data
required, which will require sufficient network capacity to be in place.
4.17 Environmental Management (if applicable)

 Network capacity could be impacted as a result of the information uploaded/downloaded from
the Handheld Devices to the Meter Asset Management and Customer Information systems,
which will affect the connectivity and speed of information required.
 Scrapping of meters should also follow a proper environmental recycling contract to reduce
the possible carbon footprints.
4.18 Service Level Agreement (if applicable)

There will be an impact on the service level agreements with the systems that the Meter Asset
Management system needs to integrate with. There will be data flows between these systems
that will need to be accommodated in new SLAs with those systems. They are:
 SAP PM
 SAP HR
 SAP MM
 SAP Finance
 MV90
 MDMS
 Smart meter multi-vendor integration systems
 CNL
 GIS
 Small World
 EBM
 FBM
 CC&B
 CRM [CT-X]
4.19 Support and Maintenance Contract Requirements

 Standard In-house systems support and maintenance contract could be extended to
these new services.
 Establish extension on existing contract with mobile solution functions to incorporate the
meter movement form on the EDA’s.
4.20 Stakeholder Management
Stakeholder Represented by Contact Info

Business Musa Mabila MabilaM@eskom.co.za 013 755 2957
Sponsor 084 430 4181
mm
240-83570075 Rev 1
Stakeholder Represented by Contact Info

Business Owner Archie Jaykaran JaykarA@eskom.co.za 031 710 5150/ 083 778
7654
Aumkar Sukhoo SukhooAS@eskom.co.za 033 395 3699/ 083 777
0014
Reginald Brooks BrooksR@eskom.co.za 021 980 3590/ 083 442
8637
Business Project Reginald Courtenay CourteR@eskom.co.za 082 467 0940
Owner
Business Subject Bobby Naidoo NaidooJA@eskom.co.za 011 871 3652/ 084 450
Matter Expert(s) 7921
Morne Botha BothaML@eskom.co.za 011 655 2446/ 074 852
2628
Madhu Bellamkonda BellamM@eskom.co.za 011 800 8111/ 082 089
2921
Mathys Willemse willemmj@eskom.co.za 014 565 1114/ 082 921
6753
Janine De Kock dKockJ@eskom.co.za 021 915 2572 / 082 338
0369
Saralie Bezuidenhout 015 299 0678/ 079 494
BezuidSE@eskom.co.za 3239
Vanessa Sibongani SibongV@eskom.co.za 012 421 3033/ 071 269

5764
Key Users DRC store personnel; CNC store person,
(Target Works coordinator, TSU’s, Contractors;
Audience) EDFS LAB staff, PTA’s; Revenue Protection
Officer, Contractors, Customer service
representatives and service agents; Meter
readers contractors and Eskom personal,
Capital project management staff,
electrification projects major and minor
projects, contractors, Data acquisition system
DAS responsible staff for remote data on
metering and Quality of supply data,
Commercial staff who makes decisions on
awarding contracts to meter suppliers,
Network planning staff, Future AMI front end
system staff, contractors and MDMS meter
data management system staff, Quality of
supply staff from planning and performance
departments and lastly Control centre staff.
Zone or Sector CC&B works coordinator.
Plant and RMC schedulers.
Key Receivers Luvhani Mphagi <MphagiLA@eskom.co.za> 079 186 5264
Architect
Dawid Lok <Lokdaf@eskom.co.za> - Overall 011 516 7126/ 082 449
Tools and Technologies Lead 6121
Key Decision Ruth Stead <SteadRH@eskom.co.za> 011 690 4401/ 071 364
Makers Stream Lead 9081
mm
240-83570075 Rev 1
5 PROPOSED SOLUTIONS/ARCHTECTURE/TECHNOLOGY
This will be provided by Enterprise Architecture – but below the author’s ideas
Maximo and SAP is possible systems which could be customised to accommodate the meter asset
management system?
6 BUSINESS PROCESS
6.1 AS-IS Process
a) Due to the nature of the meters asset tracking a number of different PCM’s across the
business will cover the live cycle of the metering assets:
The following PCM’s do exist and is relevant to the process:

 32-1225 Requisition to receipting PCM
 240-49739197 Manage returns and reverse logistics PCM
 240-49739191 Manage Repairs PCM
 240-49739204 Manage material picking issuing PCM
 240-51999384 Manage receipt inspection and storage
 240-51999298 Manage shipping and haulage PCM
 240-56302025 Revenue Management PCM
 240-55054906 Customer base management PCM
 240-70041394 Asset construction management PCM
 32-1307 Execute Work Wires PCM
 32-1317 Manage planned network events
mm
240-83570075 Rev 1
6.2 TO BE Process
 Due to the nature of the asset tracking through its live cycle there is more than one
Process control manual involves with the process. All above listed PCM’s should be
reviewed and the correct integration activities should be identified and the PCM should
then be updated accordingly referring to Systems, RACI and supporting documentation.
7 DEPENDENCIES
The Dependencies need to:
a) Define any activities/processes/projects/business issues that this change is dependent on. If
no dependencies, validate.
 This URS describes a fully computerised process. It is reliant on all people in the process being
computer literate and confidant.
 The centralised database of meters will need to be up and online at least for normal field
technician work hours, so that meter serial numbers can be validated and the history updated.
If the system is not accessible it will result in data capture backlog or non-validated fields.
 The system will enforce the standardised procedure to be followed for the meter history to be
updated. If one leg in the process is not followed, any further updates on the meter history
will be blocked due to the previous step(s) not being followed – there will be interdepartmental
reliance’s on all processes being followed correctly.
 There will be network capacity challenges if all meters are to be captured on line in all areas.
Slow capture and validation of meter data can introduce frustration to the users, who will then
resist the implementation of the system.
 The meter suppliers will need to update their systems and processes in order to submit the files
in the correct format, and in time.
 All project managers/ coordinators/ contractors/ RDC Warehouse Store personnel/ Energy
protection personnel/ Repair technicians in LABS/ Prepaid technical advisors/ CNC field
technician and contractors will need to be trained in the new processes and systems, in order
that all meters are captured timeously and correctly.
 Contracts with meter suppliers and contractors will need to be updated with the new system, file
and data requirements.
 If there is no management buy-in and driving (championing) of the system, the users in the field
will resist the implementation of system and process changes.
 Network failure will result in the mobile application not being able to download/upload work
orders and other relevant information needed by the technician/electrician in the field which
might result in a delay in executing the work orders until the network has been restored.
 The hand held device will need to receive a GPS reading when meters are installed. If there is
a high density of buildings or it is overcast, the GPS readings may fail.
o The technicians using the hand held devices will need to be trained in getting the most
accurate GPS readings possible, otherwise the data captured will be of little or no use.
b) List critical/supporting factors/skills required to ensure the successful delivery of the solution.
 It is reliant on all people in the process being computer literate and confidant.
 Quantify existing unallocated meters per business OU broken down to CNC level before and
after implementation of new meter asset management system to measure the results of the
new controls in the business.
mm
240-83570075 Rev 1
8 ASSUMPTIONS AND CONSTRAINTS

The Assumptions need to:
a) Define any uncertainties that might impact the requirement.
b) Define any assumptions that the author is making.
In the event that the URS proposed solution fails in operation it is imperative that business can
continue operating.
 It must be possible for the field technicians/ contractors to complete a manual meter movement
form for all types of movements [installation/ change out/ removal/ conversion/ audit], if the
hand held devices fail.
 Data capturers must still be available to capture meter movement forms captured manually on
hard copy format and CNC TSU’s should be trained to capture movements them self into the
meter asset management system when back in office.
 There will need to be some leniency in applying the rules of how a meter can first enter the
Meter Asset Management system, to allow for meter suppliers not being up to date in
sending out meter files as meters are dispatched.
 There will need to be some leniency in applying the rules of the order that the meter life cycle is
to follow, to allow for the clean-up of old data, capturing outstanding connections and meter
movement as well as if the hand held units are off line and the meter history data is not
updated in the correct order.
The Constraints need to:

a) Define aspects of the problem domain that are not functional requirements of a solution, and
might/will limit or impact the design of the solution.
9 DOCUMENTS TO BE UPDATED
The Documents pertaining to this URS:
a) Confirm that the following documentation is in place, if applicable:-
b) Define any documents such as business processes, training documents, testing documents etc.
that will need to be updated as a result of this requirement.
c) Define any documentation that will need to be create as a result of this requirement
Type of Documentation In Place To Be To Be

Y/N/NA Updated Created
Y/N Y/N
Business Continuity Plan Y Y
Business procedures Y Y
Disaster Recovery Plan Y Y
Process Control Manual(s) Y Y
Policy document Y Y
Strategy document Y Y
Sponsor/requester sign-off N Y
Training Documentation N N Y
mm
240-83570075 Rev 1
10 REFERENCES
The following documents have been referenced or used to compile this User Requirement Specification
Number Name Location

34-749 STANDARD FOR SEALING OF METERING
EQUIPMENT
Meter Asset Management URS Document Rev 0.3 Architecture
240- STANDARD FOR Information on Electricity Engineering
76627071240- Dispensers Dispatched FROM/to Manufacturers
76627071 AND to/ From Eskom STANDARD FOR Information
on Electricity Dispensers Dispatched FROM/to
Manufacturers AND to/ From Eskom
IEC 62055-41 Standard transfer specification (STS) - Application National Standard
layer protocol for one-way token carrier systems.
34-1790 Eskom metering strategy Hyperwave

34-120 ED Repair process Hyperwave
04 TI 020 TI Meter Movement Form Local
32-1222 PCM for material and service master file Hyperwave
management cataloguing.
mm
240-83570075 Rev 1
11 DOCUMENT APPROVAL
By signing this document, the people listed record their agreement on the contents of this document.
Business Owner: Name:

Archie Jaykaran
Signature: ____________________________________
28 June 2018
Date: ____________________________________
MATS user forum Chairperson: Name: Bobby Naidoo
Signature:
__________ _____
Date: ____________________________________
IM Business Solutions Manager: Name: Thabani Dlamini
Signature: __________________________________
Date: 01/07/2019
__________________________________
IM Portfolio Manager: Name: Carlos Betencourt
Signature: ____________________________________
Date: 01/07/2019
____________________________________
Projects Delivery Manager: Name: Lizle De Kock
PP.
Signature: ____________________________________
Date: 01/07/2019
____________________________________
Project Sponsor: Name: Musa Mabila
Signature: ____________________________________
Date: 1/7/2019
____________________________________

DEM-01569-H7S3 - Meter Asset Management - Group IT Project URS V1 5

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

DEM-01569-H7S3 - Meter Asset Management - Group IT Project URS V1 5

Uploaded by

Copyright:

Available Formats

Template

Project User Requirements 240-83570075 Rev 1

Project No.’s ID Demand Number: IM3-00051 WBS CIT00410

Project Name Meter Asset Management System (MAMS)

GIT Information Management

IM Portfolio Manager Carlos Betencourt

PD Portfolio Manager Gideon Schoonwinkel

Project Sponsor Musa Mabila

PLCM Phase Execution Phase

PROJECT DETAILS _____________________________________________________________________1

4.4 User Interface Requirements __________________________________________________________46

Document Control Information

Glossary of Terms / Definitions

1 INTRODUCTION TO THE USER REQUIREMETS SPECIFICATION

2 SOLUTION BACKGROUND AND CONTEXT

2.1 Sponsor, project owner, business area

Business Sponsor Musa Mabila (Senior Manager

2.2 Reason for the requirement

2.3 Business areas impacted

 Staff responsible for the capture of electricity network information.

2.4 In/Out of Scope and Preconditions

Business benefits/value of the solution

Eskom Strategic Objectives being supported

Divisional / Departmental Mandate / Focus areas being supported

Business benefit, financial benefit, creating efficiencies.

4.1 High Level Requirements

4.2 Functional Requirements

1.1 Entities/catalogues required to identify the meter

1.1.2 Meter Supplier

1.1.3 Meter measurement types

This is not a complete list of measurement types that will be required.

1.1.4 Electricity meter types

Refer to Standard for information on prepaid meters dispatched from/ to manufacturer

2. Meter location history

The locations of a meter are depicted in the diagram below:

n OU’s LAB TSU-PTO/ Statistical

Store section stores Technicians locations &

Logical flow of meters’ location history in Meter Asset Management system

When a meter is Issued to Technician-TSU and Uninstalled, it must be possible to see

Considering the proposed controls to be implemented in order to reduce current

meter is removed from an installation.

5. Meter supplier’s meter information

5.1 New meters received

5.2 Repaired meters from supplier

6. Information required for each meter type

6.1 Electricity meters - Pre-paid

6.2 Electricity meters - Smart Meters (AMI and ULM)

The multiple entry possibility should be prevented, as far as possible, by improving

Electrification contractors should also be incentivised to supply meter and customer

8. Meter installation information

If the meter is measuring a point from which generation, transmission, international

8.1 New installation

A meter may be linked to at least 3 CT and / or 3 VT or 3 CVTs. This information must

8.2 Meter change-outs

A meter may be linked to at least 3 CT and / or 3 VT or 3 CVTs. This information must

updated against the old meter number.

8.3 Termination of supply

9. Seal management system

It must be possible to configure the Meter Asset Management system whether to

10. Hand held device for meter installation

10.1 New installation

validate back to the main system database).

A meter may be linked to at least 3 CT and / or 3 VT or 3 CVTs. This information must