Operational Process Guide

Transcription

TWACS NET SERVER (TNS)
Operational Process Guide
Y10352TM
Proprietary Notice
Information contained in this document is private to Distribution Control Systems, Inc., St. Louis,
Missouri (DCSI). This information may not be published, reproduced, or otherwise disseminated without
the express written authorization of DCSI.
Any software or firmware described in this document is furnished under a license and may be used or
copied only in accordance with the terms of such license.
Disclaimer
The information in this document is subject to change without notice and should not be construed as a
commitment by DCSI. DCSI assumes no responsibility for any errors that may appear in this document.
No responsibility is assumed for the use or reliability of software on equipment that is not supplied by
DCSI.
TWACS, the TWACS logo, and the DCSI logo are registered trademarks of Distribution Control Systems,
Inc., St. Louis, Mo. All other registered trademarks are property of their respective owners.
TWACS®
Two-Way Automatic Communication System,
a product of
Distribution Control Systems, Inc.
Confidential and Proprietary
Copyright 2004 All Rights Reserved
TNS Operational Process Guide
( Y10352TM)
Table of Contents
Using this Manual
Chapter Overview . . . . . . . . . . . . .
TWACS User Roles . . . . . . . . . . . . .
TNS Operator . . . . . . . . . . . . . .
TWACS Project Manager . . . . . . . . .
Customer Service Representative/Manager .
Billing Personnel . . . . . . . . . . . . .
Substation and Transmission Engineer . . .
Meter Technician. . . . . . . . . . . . .
Customer Engineer . . . . . . . . . . . .
Recommended Chapters by User Role . . . .
Support . . . . . . . . . . . . . . . . .
1
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Chapter 1: The TWACS System
TWACS System Overview . . . . . . . . . . . . . . . .
Understanding TWACS System Basic Applications . . . .
TWACS Enables New Functions . . . . . . . . . . .
Automatic Meter Reading . . . . . . . . . . . . . .
Scheduled Daily Shift Reads . . . . . . . . . . .
Scheduled Hourly Reads . . . . . . . . . . . . .
On-Request Meter Reads . . . . . . . . . . . . .
Demand Reads . . . . . . . . . . . . . . . . .
Load Control . . . . . . . . . . . . . . . . . . .
Service Disconnect/Connect . . . . . . . . . . . .
Tamper Detection/Energy Theft Reduction . . . . . .
No Pulses in 24 Hours . . . . . . . . . . . . . .
Reverse Rotation . . . . . . . . . . . . . . . .
Blink Count . . . . . . . . . . . . . . . . . . .
Service Reliability/Outage Count Monitoring . . . . .
Blink Count Indications of Future Problems . . . .
False Dispatch: Customer Problem . . . . . . . .
Are All the Customers Back Up? . . . . . . . . . .
Where Did the Power Go? . . . . . . . . . . . .
How is the Transformer Load? . . . . . . . . . .
Getting Pathmaps Straight . . . . . . . . . . . .
Billing Enhancements . . . . . . . . . . . . . . .
Consolidated Billing . . . . . . . . . . . . . . .
Specific Day of Month Billing . . . . . . . . . . .
Vacation Home Monitoring . . . . . . . . . . . .
Budget Billing Causes Lost Energy Tracking Problem
Time of Use Billing . . . . . . . . . . . . . . .
Cross-Utility Cooperative Work . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
2
3
3
4
5
5
6
7
7
8
8
9
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
10
10
10
11
12
13
13
14
15
16
16
17
17
17
17
18
18
18
18
19
19
19
20
20
20
20
20
21
i
Table of Contents
TWACS System Design. . . . . . . . . . . . . . .
TWACS Levels Overview . . . . . . . . . . . . .
TWACS Level 3 Components - RCE . . . . . . . .
Meter versus Transponder . . . . . . . . . . .
Meters, Meter Numbers, and Serial Numbers . .
Commercial versus Residential Meters . . . . .
Mechanical versus Solid State or Digital . . . . .
Single Port versus Multiport . . . . . . . . . .
Read Frequencies . . . . . . . . . . . . . . .
Read Types: Consumption versus Kilowatt Hours .
Common Meter Reference Page . . . . . . . .
Common Meter Vendor Reference Page . . . . .
Load Control Transponders. . . . . . . . . . .
Remote Service Disconnect/Connect Modules . .
TWACS Level 2 Components . . . . . . . . . . .
Electrical System Bus and Feeder . . . . . . .
Bus . . . . . . . . . . . . . . . . . . . .
Feeder . . . . . . . . . . . . . . . . . .
MTU . . . . . . . . . . . . . . . . . . . .
Substation Communication Equipment . . . . .
TWACS Flow of Information . . . . . . . . . .
TWACS Communication . . . . . . . . . . . .
TWACS Level 1 Components . . . . . . . . . . .
TWACS Net Server. . . . . . . . . . . . . . .
TNS Basic Configuration . . . . . . . . . . . .
TNS Advanced Configuration . . . . . . . . . .
TNS Communications Options . . . . . . . . .
General TNS Communications Topics . . . . .
Dialup versus Dedicated. . . . . . . . . . .
Distributing Communication Servers . . . . .
Using Existing Networks . . . . . . . . . . .
TNS System Design . . . . . . . . . . . . . . . .
TNS System Overview . . . . . . . . . . . . . .
TNS System Components . . . . . . . . . . .
Oracle Database Manager and Servers . . . .
What is a Database? . . . . . . . . . . . .
What is a Table? . . . . . . . . . . . . . .
Log Files in TNS . . . . . . . . . . . . . .
Managing TNS . . . . . . . . . . . . . . . .
TNS Watchdog . . . . . . . . . . . . . . .
Alerts from TNS . . . . . . . . . . . . . .
Integrating AMR Data with Utility Billing Systems
TNS Read Data . . . . . . . . . . . . . . .
ii
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 21
. 22
. 23
. 23
. 23
. 24
. 24
. 24
. 25
. 26
. 27
. 28
. 28
. 29
. 30
. 30
. 30
. 31
. 31
. 32
. 33
. 34
. 35
. 35
. 35
. 36
. 36
. 36
. 37
. 38
. 39
. 39
. 39
. 39
. 40
. 41
. 42
. 43
. 44
. 44
. 44
. 45
. 45
Table of Contents
Chapter 2: Substation Setup
Understanding Substation Communications and Architecture . . . . . .
SCE Overview . . . . . . . . . . . . . . . . . . . . . . . . . . .
SCE Process Flow . . . . . . . . . . . . . . . . . . . . . . . .
Substation Components . . . . . . . . . . . . . . . . . . . . .
SCE Information Flow . . . . . . . . . . . . . . . . . . . . . .
SCE to Meter Communications. . . . . . . . . . . . . . . . . . . .
CRU COMPONENTS . . . . . . . . . . . . . . . . . . . . . . . .
SCE Outbound Communications . . . . . . . . . . . . . . . . . .
SCE Inbound Communications . . . . . . . . . . . . . . . . . . .
Bus-Level IPU . . . . . . . . . . . . . . . . . . . . . . . . .
Feeder-Level IPU . . . . . . . . . . . . . . . . . . . . . . .
Inbound Modes: Single Receiver versus Concurrent Phasing . . . .
IPU to CRMA Connection Facts . . . . . . . . . . . . . . . . .
Concurrent Phasing Facts . . . . . . . . . . . . . . . . . . .
IPU to Termination Panel Connections: Single Receiver Mode . . .
Termination Panel to CRMA Backplane Connections: CRMA 1 and 2
Concurrent Phasing IPU Connection Diagram . . . . . . . . . . .
Inbound Communication Configuration Summary . . . . . . . . .
Pictorial Representation of the IPU Connections . . . . . . . . .
TWACS System Substation Component Count Summary . . . . . .
Question Flow for Documenting TNS Settings for IPU Map . . . . .
IPU Map Reference Table. . . . . . . . . . . . . . . . . . . .
Adding Substations . . . . . . . . . . . . . . . . . . . . . . . . .
Adding Substations to TNS . . . . . . . . . . . . . . . . . . . . .
Adding Substations Process Flow . . . . . . . . . . . . . . . . .
Adding Substations Process Flow Detail . . . . . . . . . . . . . .
Drop IDs and Substation IDs . . . . . . . . . . . . . . . . . . . .
Facts About Drop IDs and Substation IDs . . . . . . . . . . . . . .
Adding Substations. . . . . . . . . . . . . . . . . . . . . . . .
Adding Buses . . . . . . . . . . . . . . . . . . . . . . . . . .
Adding Feeders . . . . . . . . . . . . . . . . . . . . . . . . .
Understanding Inbound Scalars . . . . . . . . . . . . . . . . .
Calculating the Inbound Scalar . . . . . . . . . . . . . . . . .
Adding IPU Mappings . . . . . . . . . . . . . . . . . . . . . . .
Adding Receivers . . . . . . . . . . . . . . . . . . . . . . . .
Adding OMU Parameters . . . . . . . . . . . . . . . . . . . . .
Adding Substation Communications Links to TNS . . . . . . . . . . . .
Communications Link Overview . . . . . . . . . . . . . . . . . . .
Process Flow Detail . . . . . . . . . . . . . . . . . . . . . . .
Dedicated versus Dialup Connections . . . . . . . . . . . . . . .
Setting Up the Communications Link in TNS . . . . . . . . . . . . .
47
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
48
48
49
51
51
52
52
53
55
55
55
56
56
57
57
58
59
60
61
62
62
65
66
66
67
67
70
70
71
73
75
77
78
80
82
88
93
93
93
94
94
iii
Table of Contents
Chapter 3: Searching Meters
101
Receiving Meters at the Utility - Preliminary Search Activities . . . . . . .
Verifying Product Table Information. . . . . . . . . . . . . . . . . . .
Understanding Meter Types and Model Numbers . . . . . . . . . . . .
TWACS System Type and Model Example . . . . . . . . . . . . . .
Deciding Which Meter Features to Use . . . . . . . . . . . . . . .
Changing Deployed Meter Type and Model Configurations . . . . . .
Verifying and Adding Product Table Information . . . . . . . . . . . .
Verifying SubProduct Table Information . . . . . . . . . . . . . . . . .
Verifying Information in the SubProduct Table . . . . . . . . . . . . .
Search Mode and Search Type . . . . . . . . . . . . . . . . . . .
Updating the Product Type Model Cross Reference Table . . . . . . . . .
Overview of the Product Type Model Cross Reference Table . . . . . . .
Serial Number or Meter Number?. . . . . . . . . . . . . . . . . .
Meter Type and Model Number . . . . . . . . . . . . . . . . . .
Adding Serial Numbers to the Product Type Model Cross Reference Table
Searching Meters into TNS . . . . . . . . . . . . . . . . . . . . . . .
Searching Overview . . . . . . . . . . . . . . . . . . . . . . . . . .
Search In Process Overview . . . . . . . . . . . . . . . . . . . . .
Process Flow Detail . . . . . . . . . . . . . . . . . . . . . . . .
Required Meter Fields. . . . . . . . . . . . . . . . . . . . . . .
Batch versus Interactive Search . . . . . . . . . . . . . . . . . .
Searching Meters into TNS Interactively . . . . . . . . . . . . . .
Searching Meters into TNS Using Batch Search. . . . . . . . . . . .
Enhancing TNS Functionality through Meter Fields . . . . . . . . . . .
Best Practices for Meter Field Use . . . . . . . . . . . . . . . . .
Meter Type versus Type and Model Fields . . . . . . . . . . . . . .
Why Program the Meter with Type and Model? . . . . . . . . . . .
What Does the Kh Value Mean?. . . . . . . . . . . . . . . . . . .
Meter Type and the Meter Conversion Table . . . . . . . . . . . .
Meter Conversions in the Meter Conversion Table . . . . . . . . . .
Hourly and Interval Conversions in the Meter Conversion Table . . . .
What are Thermal Limits? . . . . . . . . . . . . . . . . . . . . .
Meter Shop to TNS Operator Communications . . . . . . . . . . . .
Interactively Searching Meters . . . . . . . . . . . . . . . . . . . . .
Adding Meters Interactively . . . . . . . . . . . . . . . . . . . . .
Post-Search Activities . . . . . . . . . . . . . . . . . . . . . . . .
Substation Command Queue . . . . . . . . . . . . . . . . . . . .
Inbound and Outbound Paths (SCE to Meter) . . . . . . . . . . . .
Primary and Secondary Detection Points . . . . . . . . . . . . . .
Verifying Meters Searched . . . . . . . . . . . . . . . . . . . . . .
Where Do Meter Definitions in TNS Go After the Search? . . . . . . .
Identifying Where to Monitor Meters Being Searched. . . . . . . . .
Viewing Temp Failed Records . . . . . . . . . . . . . . . . . . .
Viewing Temp Non-Failed Records . . . . . . . . . . . . . . . . .
Viewing the General Status Log . . . . . . . . . . . . . . . . . .
Viewing the Detail Search Status Log File . . . . . . . . . . . . . .
iv
102
102
102
102
103
104
104
108
108
110
112
112
112
112
113
115
115
115
116
117
117
118
119
120
121
124
125
125
126
126
127
127
128
129
130
137
138
140
140
141
141
143
144
147
147
148
Table of Contents
Dealing with Failed Searches . . . . . . . . . . . . . . . . . .
Why Meters Fail . . . . . . . . . . . . . . . . . . . . . . .
Meter Failures . . . . . . . . . . . . . . . . . . . . . . .
Process Flow Detail . . . . . . . . . . . . . . . . . . .
Recovering from Meter Failures . . . . . . . . . . . . . .
Failures that Produce Errors . . . . . . . . . . . . . . . .
Failures that Do Not Produce Errors . . . . . . . . . . . . .
General Troubleshooting Procedures for Failed Searches . . . . .
Identifying and Viewing Error Codes for Failed Meters . . . . .
Re-Searching All Meters . . . . . . . . . . . . . . . . . .
Checking the Notification Log in SCE Maintenance . . . . . .
Multi-Update/Sub for Global Path . . . . . . . . . . . . . .
Change the Search Mode from Advanced Search . . . . . . .
Multi-Update/City-Sub for Multiple Substation Search . . . . .
Search Neighboring Meter . . . . . . . . . . . . . . . . .
View Search History Log . . . . . . . . . . . . . . . . . .
Dispatch Meter Technician . . . . . . . . . . . . . . . . .
Batch Searching Meters into TNS . . . . . . . . . . . . . . . .
Batch Search Process . . . . . . . . . . . . . . . . . . . . .
Creating the Batch Search File . . . . . . . . . . . . . . . .
Batch Search File Format Overview . . . . . . . . . . . . .
PATH Line Format . . . . . . . . . . . . . . . . . . . .
SNDATA Line Format . . . . . . . . . . . . . . . . . . .
Port Line Format . . . . . . . . . . . . . . . . . . . .
Meter Line Format . . . . . . . . . . . . . . . . . . . .
Common Batch Search File Format Problems . . . . . . . . .
Creating the Batch Search File Using the Spreadsheet Template
Running the Batch Search File . . . . . . . . . . . . . . . . .
Starting the Batch Search Job in the Batch Job Scheduler . . .
Scheduling the Job in the Future . . . . . . . . . . . . .
Scheduling a Recurring Interval Job . . . . . . . . . . . .
Starting the Batch Job Immediately . . . . . . . . . . . .
Troubleshooting Batch Searches Using the Pre-Tiq Log File. . .
Batch Search Add Validation Process . . . . . . . . . . .
Sample Pre-TIQ.log File . . . . . . . . . . . . . . . . .
Monitoring Batch Job Progress . . . . . . . . . . . . . . .
Monitoring Batch Job Details . . . . . . . . . . . . . . .
Chapter 4: Reading Residential Meters
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 149
. 149
. 149
. 150
. 150
. 151
. 152
. 154
. 155
. 159
. 160
. 161
. 164
. 166
. 172
. 172
. 172
. 173
. 173
. 175
. 175
. 177
. 178
. 179
. 180
. 181
. 181
. 181
. 181
. 185
. 185
. 186
. 188
. 189
. 190
. 191
. 192
193
Reading Meters Overview . . . . . . . . . . . . . . . . . . . . . . . . 194
Meter Read Types . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
On-Request Reads for Customer Service . . . . . . . . . . . . . . . . . . 195
On-Request TC Reads . . . . . . . . . . . . . . . . . . . . . . . . . . 196
Residential and Commercial On-Request Reads . . . . . . . . . . . . . . 197
Getting Meters to Appear in the Meter Read Application. . . . . . . . . 198
Getting Meters to Appear in the MIT On-Request Application. . . . . . . 199
Different Reading Between TNS and the Meter . . . . . . . . . . . . . 199
Performing On-Request TC Reads for IMT and CENTRON Meters (Residential) 200
Troubleshooting On-Request Reads. . . . . . . . . . . . . . . . . . . . 202
v
Table of Contents
Reading Meters to Generate Billing Output Files for Residential Meters
Billing Read Overview . . . . . . . . . . . . . . . . . . . . . .
Performing Daily, Monthly, and One-Time Billing Reads . . . . . .
Relationship Between Data Table and Billing Process . . . . . . .
How Does the Utility Charge for Energy? . . . . . . . . . . . .
How Does the Utility Want to Read for Billing? . . . . . . . . . .
Helpful Hints for Billing Reads . . . . . . . . . . . . . . . . . .
Performing Daily Billing Reads . . . . . . . . . . . . . . . . . .
Creating the AMR Calendar Input File for Monthly Billing . . . . . .
AMR Calendar Input File Format . . . . . . . . . . . . . . . .
Performing Monthly Billing Reads . . . . . . . . . . . . . . . . .
Performing a One-Time Billing Read. . . . . . . . . . . . . . . .
Troubleshooting Billing Reads . . . . . . . . . . . . . . . . . .
Verifying Jobs in the TNS AMR Calendar . . . . . . . . . . . . .
Verifying Jobs in the DCSI Job Scheduler . . . . . . . . . . . .
Verifying Commands in the AMR Command Lists . . . . . . . . .
Verifying Commands in the Substation Command Queue . . . . .
Isolating Error Codes in AMR Command Lists. . . . . . . . . . .
Miscellaneous Problems with AMR Jobs . . . . . . . . . . . . .
Reviewing Billing Files . . . . . . . . . . . . . . . . . . . . . .
Billing File Details . . . . . . . . . . . . . . . . . . . . . .
Billing File Record Types . . . . . . . . . . . . . . . . . .
Using Hourly Reads . . . . . . . . . . . . . . . . . . . . . . . .
Setting a Meter’s User1 Field to HOURLY . . . . . . . . . . . . .
Adding User1 as a Set ID . . . . . . . . . . . . . . . . . . . . .
Setting Up the Hourly Read Job . . . . . . . . . . . . . . . . .
Reviewing and Graphing Hourly Read Files. . . . . . . . . . . . .
Hourly File Location and Naming . . . . . . . . . . . . . . . .
Hourly File Details . . . . . . . . . . . . . . . . . . . . . .
Hourly File Record Types (Reading Record) . . . . . . . . . .
Interpreting Hourly Interval Data . . . . . . . . . . . . . .
Generating Hourly Data Graph Reports for a Specific Month . . .
Generating Hourly Data Graph Reports for a Specific Time Frame .
Troubleshooting Meters that Fail Reads. . . . . . . . . . . . . . .
Entering a Set of Transponders to Measure with TCT . . . . . . . .
Creating and Uploading a Batch File . . . . . . . . . . . . . . .
Viewing or Modifying a Batch Job. . . . . . . . . . . . . . . .
Running and Interpreting TCT Tests . . . . . . . . . . . . . . . .
TCT Using Two-Way Addressing . . . . . . . . . . . . . . . . . .
Outage Mapping. . . . . . . . . . . . . . . . . . . . . . . . .
Planning for Outage Mapping. . . . . . . . . . . . . . . . . .
Implementing Outage Mapping . . . . . . . . . . . . . . . . .
Voltage Monitoring Using TCT Volt . . . . . . . . . . . . . . . .
Planning for Routine Voltage Monitoring . . . . . . . . . . . .
Performing Routine Voltage Monitoring . . . . . . . . . . . . .
Running Ad-Hoc Voltage Monitoring . . . . . . . . . . . . . . .
Viewing TCT Voltage Results . . . . . . . . . . . . . . . . . .
vi
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
204
204
206
207
208
208
209
215
219
219
223
227
230
231
232
232
236
237
240
241
242
242
245
246
248
250
253
253
254
254
255
256
260
263
263
267
271
273
277
281
281
282
283
283
284
287
289
Table of Contents
Chapter 5: Operating TNS
Building Alternate Pathmaps . . . . . . . . . . . . . . . . . . .
Understanding Alternate Paths and Maps . . . . . . . . . . . . .
Feeder Layouts . . . . . . . . . . . . . . . . . . . . . . .
Simplified Feeder Layout. . . . . . . . . . . . . . . . . .
Connecting Feeders Together for Redundancy . . . . . . . .
Neighboring Substations . . . . . . . . . . . . . . . . . .
Interconnections Between Substations. . . . . . . . . . . .
Triggers for Switching Feeder Paths . . . . . . . . . . . . . .
Maintenance Triggers . . . . . . . . . . . . . . . . . . .
Outage Restoration Trigger . . . . . . . . . . . . . . . . .
Load Balancing Triggers . . . . . . . . . . . . . . . . . .
Effect of Alternate Pathmaps on Meter Reading . . . . . . .
Alternate Substation Mapping . . . . . . . . . . . . . . . . . .
Determining Feeder/Substation Associations . . . . . . . . . .
Populating the Alternate Substation Table . . . . . . . . . . .
Creating and Using Alternate Path Tables. . . . . . . . . . . . .
Determining When to Use Alternate Path Tables . . . . . . . .
Creating an Alternate Pathmap Table . . . . . . . . . . . . .
Performing Alternate Path Searches. . . . . . . . . . . . . . . .
Creating and Running AP Searches Using APM Search . . . . . . .
Distinguishing Between Normal and Grouped Searches . . . . .
Overview of Alternate Path Search Options in APM Search . . . .
Performing an Immediate Alternate Path Search . . . . . . . .
Performing a Scheduled Alternate Path Search for Later. . . . .
Viewing Alternate Path Search Logs . . . . . . . . . . . . . . .
Viewing the Alternate Path Search Log. . . . . . . . . . . . .
Viewing the Alternate Path Transaction Log . . . . . . . . . .
Creating and Printing an AP Transaction Log Report . . . . . . .
Viewing the Serial Number Path History Log . . . . . . . . . .
Creating and Printing a Serial Number Path Change History Report
Fraud and Theft Prevention Applications . . . . . . . . . . . . .
Introduction to Fraud and Theft Prevention . . . . . . . . . . .
Daily Activities . . . . . . . . . . . . . . . . . . . . . . .
Weekly Activities . . . . . . . . . . . . . . . . . . . . . .
Monthly Activities . . . . . . . . . . . . . . . . . . . . . .
Daily Trouble Analysis Activities . . . . . . . . . . . . . . . . .
Checking 24 Hour No Pulse . . . . . . . . . . . . . . . . . .
Checking Reverse Rotations . . . . . . . . . . . . . . . . . .
Weekly Blink Count Processing . . . . . . . . . . . . . . . . .
Accessing and Analyzing Blink Counts . . . . . . . . . . . . .
Resetting Blink Count Registers . . . . . . . . . . . . . . . .
Scheduling Routine Processes . . . . . . . . . . . . . . . . . .
Scheduling Trouble Server Applications . . . . . . . . . . . .
Scheduling Reset of Blink Count Registers . . . . . . . . . . .
Trouble Mask Setup. . . . . . . . . . . . . . . . . . . . . . .
Unknown Trouble Flag Bit Descriptions Problems/Solutions . . .
291
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 292
. 292
. 292
. 292
. 293
. 293
. 294
. 295
. 295
. 296
. 296
. 297
. 299
. 299
. 300
. 304
. 304
. 306
. 309
. 309
. 309
. 310
. 311
. 312
. 314
. 314
. 315
. 317
. 320
. 321
. 323
. 323
. 324
. 326
. 327
. 327
. 327
. 333
. 337
. 337
. 342
. 343
. 343
. 345
. 346
. 347
vii
Table of Contents
SCE Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Performing Diagnostics Using the Diagnostic and Substation Response
Data Logs . . . . . . . . . . . . . . . . . . . . . . . . . . .
Preparing for Diagnostics . . . . . . . . . . . . . . . . . . .
Run Diagnostics and View Logs . . . . . . . . . . . . . . . . .
Notification Log. . . . . . . . . . . . . . . . . . . . . . . . .
Viewing Other Logs . . . . . . . . . . . . . . . . . . . . . . .
Environmental Log . . . . . . . . . . . . . . . . . . . . . .
Exception Log . . . . . . . . . . . . . . . . . . . . . . . .
Snapshot Log . . . . . . . . . . . . . . . . . . . . . . . . .
Unsuccessful Activity Log . . . . . . . . . . . . . . . . . . .
. . . 350
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Chapter 6: Load Control
375
Load Control Overview . . . . . . . . . . . . . . . . . . .
Developing Load Control Schemes . . . . . . . . . . . . .
Hardware for Controlling Loads . . . . . . . . . . . . .
Classifying Loads . . . . . . . . . . . . . . . . . . . .
Separating Classes into Subgroups . . . . . . . . . . . .
Understanding X and Y Addressing . . . . . . . . . . . . .
Reviewing Serial Number and Two-Way Addressing . . . . .
Operation of X and Y Addressing . . . . . . . . . . . . .
Load Control Implementation Strategies . . . . . . . . . .
Strategy, Objectives, and Addressing . . . . . . . . . . .
Implementing a Simple X&Y Based Addressing Strategy. . .
Implementing a Geographical Strategy . . . . . . . . . .
Implementing the Fast Scram Strategy . . . . . . . . . .
Configuring Load Control in TNS . . . . . . . . . . . . . . .
Building LCT Tables and Searching in LCTs . . . . . . . . . .
Developing a Work Plan for Load Control . . . . . . . . .
Building the Load Control Class Table . . . . . . . . . . .
Additional Prerequisites for Searching in LCTs . . . . . . .
Searching in LCTs . . . . . . . . . . . . . . . . . . . .
Defining Ports and Assigning Addresses . . . . . . . . . . .
Planning Ports and Addressing . . . . . . . . . . . . . .
Defining Ports on the LCTs . . . . . . . . . . . . . . . .
One-Way Address Assignment (Typed List Method) . . . . .
One-Way Address Assignment (All Transponders Method) . .
Activating Load Control Commands . . . . . . . . . . . . .
Calculating Load Control Parameters . . . . . . . . . . .
Issuing Load Control Commands . . . . . . . . . . . . .
Cancelling Immediate Load Control Program . . . . . . .
Viewing and Printing Logs . . . . . . . . . . . . . . . .
Automating Command Activation . . . . . . . . . . . . . .
Creating Commands for Automation . . . . . . . . . . .
Creating and Activating Load Control Automation Strategies
viii
355
356
359
361
366
367
369
371
373
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
376
377
377
378
378
380
380
381
382
382
383
383
386
389
389
389
389
391
393
396
396
397
400
405
407
407
409
412
413
414
415
421
Table of Contents
Chapter 7: Two-Way Addressing
429
Overall Process Flow . . . . . . . . . . . . .
Planning Activities . . . . . . . . . . . . . .
Understanding Two-Way Addressing Applications
Two-Way Addressing Structure . . . . . . .
Process for Forming Groups . . . . . . . . .
Use of Two-Way Addressing by Applications .
Develop Addressing Plan . . . . . . . . . . .
Develop Data Entry Instructions and Policies . .
Initial and Ongoing Data Entry . . . . . . . . .
Define Two-Way Set IDs . . . . . . . . . . . .
Define Two-Way Functions . . . . . . . . . .
Define Related Forms/Entries . . . . . . . . .
Assign Two-Way Addresses . . . . . . . . . .
Ongoing Maintenance . . . . . . . . . . . . .
Monitor Group Sizes . . . . . . . . . . . . .
Monitor Path Changes . . . . . . . . . . . .
Other Status Descriptions Requiring Monitoring .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Chapter 8: TNS Watchdog
GUI Operation . . . . . . . . . . . .
Adding a Service . . . . . . . . . . .
Starting a Service . . . . . . . . . .
Stopping a Service . . . . . . . . . .
Deleting a Service . . . . . . . . . .
Using the Main Menu Options . . . . .
Project . . . . . . . . . . . . . .
Connect. . . . . . . . . . . . . .
Edit . . . . . . . . . . . . . . .
Select . . . . . . . . . . . . . .
Help . . . . . . . . . . . . . . .
Troubleshooting . . . . . . . . . . .
Command Line Interface Operation . . .
Accessing the Command Line Interface.
Issuing Commands . . . . . . . . . .
Help . . . . . . . . . . . . . . .
Add. . . . . . . . . . . . . . . .
Troubleshooting . . . . . . . . .
Delete . . . . . . . . . . . . . .
GetState . . . . . . . . . . . . .
GetInfo . . . . . . . . . . . . . .
Start . . . . . . . . . . . . . . .
Stop . . . . . . . . . . . . . . .
. 430
. 431
. 431
. 431
. 431
. 432
. 434
. 435
. 435
. 436
. 438
. 439
. 440
. 442
. 443
. 446
. 447
449
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 450
. 451
. 453
. 455
. 456
. 457
. 457
. 458
. 459
. 460
. 461
. 462
. 466
. 467
. 468
. 469
. 470
. 472
. 473
. 475
. 476
. 478
. 480
. 482
. 484
. 485
. 487
. 488
ix
Table of Contents
Maint . . . . . . . . . . .
On . . . . . . . . . . .
Off . . . . . . . . . . .
Troubleshooting . . . . .
Performing System Maintenance
The Shutdown Process. . . .
The Startup Process . . . . .
The Batch File . . . . . . . .
Multiple Machine Distribution .
Exit Codes . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Chapter 9: TNS Server Administration
TNS Log Cleaner Version 1.02 . . . . . .
Log Cleaner Options . . . . . . . . . .
Log Cleaner Configuration Menu . . .
Edit INI File Manually . . . . . . . .
Start. . . . . . . . . . . . . . . .
Log Monitor Options . . . . . . . . . .
Install . . . . . . . . . . . . . . .
Remove . . . . . . . . . . . . . .
Log Monitor Configuration Menu . . .
Edit INI File Manually . . . . . . . .
Log File Options . . . . . . . . . . .
Substation Traffic Monitor. . . . . . . .
Substation Traffic Collection . . . . . .
Starting a New Job . . . . . . . . .
Scheduling Data Collection . . . . .
Using Job Options. . . . . . . . . .
Continuing a Previous Job . . . . . .
Substation Traffic Analysis . . . . . . .
Graphing Data . . . . . . . . . . .
Analyzing Graph Data . . . . . . . .
Substation Available Threshold . .
Dynamic Refresh . . . . . . . . .
Zoom . . . . . . . . . . . . . .
Detail Breakdown. . . . . . . . .
Function Code and Priority . . . .
Substation Data Selection . . . . .
Create a Report . . . . . . . . .
TNS Config Utility . . . . . . . . . . .
New Server Setup (Hosting TNS Services)
Changing the Password . . . . . . . .
x
490
490
491
491
492
492
493
494
496
499
501
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
502
503
504
506
507
508
509
510
510
512
513
514
514
516
517
519
520
522
522
524
524
526
526
528
529
530
531
532
533
536
Table of Contents
Download Firmware . . . . . . . . . . . . . . .
Download Procedure . . . . . . . . . . . . . .
Downloading the New Firmware to the SCE . .
Selecting the Substation to be Updated . . . .
Starting the Download Process . . . . . . . .
Monitoring the Download Process . . . . . . .
Applying the Download . . . . . . . . . . . .
Verifying the Status of the Apply Download . .
Re-Downloading the Tables . . . . . . . . . .
Daylight Saving Time Procedure . . . . . . . . .
Before You Begin . . . . . . . . . . . . . . . .
Spring Procedure (April) . . . . . . . . . . . .
Set SCE Date . . . . . . . . . . . . . . . .
Autumn Procedure (October) . . . . . . . . . .
Set SCE Date . . . . . . . . . . . . . . . .
TNS Backup Procedure for Oracle 7.3.1 . . . . . .
TNS Backup Procedure for Oracle 8.1.7 . . . . . .
Installing TNS Forms . . . . . . . . . . . . . . .
Installing the Oracle Universal Installer . . . . .
Installing Forms, Graphics, and Reports Runtime .
Installing TNS Forms . . . . . . . . . . . . . .
Server Startup and Shutdown. . . . . . . . . . .
TNS Server Shutdown and Startup for Oracle 8i . .
TNS Server Shutdown and Startup for Oracle 7.3.1
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Chapter 10: MultiSpeak Flow 2A Batch Mode
Software Installation . . . . . . . . .
Using MultiSpeak Flow 2A CB Files . . .
Customer Billing Files . . . . . . . . .
Generating MultiSpeak Flow 2A MR Files.
617
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Chapter 11: TNS Messenger Service
Recipient Addressing .
Sender Addressing. . .
Sample Configurations .
Service Options . . . .
Mail Server . . . . .
Log Stats . . . . . .
Reset Stats . . . . .
Log State . . . . . .
Loop Period . . . . .
Run Level . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 538
. 538
. 539
. 541
. 541
. 542
. 543
. 543
. 544
. 547
. 547
. 555
. 559
. 564
. 568
. 573
. 581
. 591
. 591
. 595
. 600
. 606
. 606
. 612
. 618
. 622
. 623
. 623
625
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Appendix A: Searchfile Spreadsheet Template
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 626
. 629
. 632
. 633
. 633
. 634
. 635
. 635
. 636
. 637
639
Creating the Batch Search File . . . . . . . . . . . . . . . . . . . . . . 640
Editing the Batch Search File. . . . . . . . . . . . . . . . . . . . . . . 646
xi
Table of Contents
Appendix B: Decoding Search History Log Files
651
Interpreting Search History Logs . . . . . . . . . . . . . . . . . . . .
Logical Elimination and Amplitude Summation . . . . . . . . . . . . .
Reviewing the General Status Log . . . . . . . . . . . . . . . . .
Reviewing the Search History Log Data for Amplitude Summation . . .
Global Search versus Directed Search . . . . . . . . . . . . . .
Translating Amplitude Summation and Logical Elimination Search Logs. .
Search Request Fields . . . . . . . . . . . . . . . . . . . . . . .
Search Response Fields . . . . . . . . . . . . . . . . . . . . . .
Example Search History Log for Advanced Search . . . . . . . . . . .
Reviewing the Search History Log Data for Advanced Search Raw Data.
Translating Search History Logs for Advanced Search . . . . . . . . . .
Search Request Fields . . . . . . . . . . . . . . . . . . . . . . .
Search Response Fields . . . . . . . . . . . . . . . . . . . . . .
Decoding the Log File. . . . . . . . . . . . . . . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
652
652
653
654
655
656
656
657
661
661
663
663
664
667
Acronyms
671
Glossary
675
Index
683
xii
USING THIS MANUAL
The TNS Operational Process Guide presents high level procedures and
processes for operating your TWACS system, through the TNS interface.
These processes and procedures span a number of application sets, and are
organized around functions such as reading meters, substation setup, and
operating TNS.
This guide is a companion document to the TNS End User Guide, which
presents detailed procedures, and definitions of fields on the various TNS
forms, and is organized by TNS tool bars rather than by process.
This section of the TNS Operational Process Guide includes the following
information:
• Chapter Overview on page 2 - Lists the chapters in this manual and
provides an overview of their content.
• TWACS User Roles on page 3 - Explains the common roles defined for
those using the TWACS system.
• Recommended Chapters by User Role on page 8 - Identifies the chapters
of this manual that DCSI recommends for the various TWACS user
roles.
• Support on page 8 - Provides DCSI Customer Care contact information.
1
Chapter Overview
Chapter Overview
The following table provides an overview of this manual:
Chapter
Description
1 - The TWACS System
Provides a description of the TWACS
system and its functionality, and an
overview of TNS
2 - Substation Setup
Presents substation architecture and the
process of setting up substations in TNS
3 - Searching Meters
Begins with the receipt of meters at the
utility, ending with searching the meters
into the TNS database
4 - Reading Residential Meters Reading meters for billing, customer
service, and engineering purposes,
automatically and on request, including
hourly reads and troubleshooting meter
read problems
5 - Operating TNS
Providing for alternate communication
paths to meters, fraud and theft prevention,
and using SCE logs for maintenance
6 - Load Control
Planning for and setting up load control,
including optional load control automation
7 - Two-Way Addressing
Setting up and maintaining the efficiency
of two-way addressing, which increases the
speed of sending commands to meters
8 - Service Disconnect/Connect Procedures to set up and use commands
from TNS to disconnect or connect service
using switches in the meter base
9 - TNS Watchdog
Using TNS Watchdog to automatically
start critical TNS services and notify TNS
Operators of service changes via e-mail
enabled devices
10 - TNS Server Administration Procedures the TNS Operator will use to
maintain the health of the TNS software
and database
Appendix A - Searchfile
Procedures to use the Searchfile
Spreadsheet Template
Spreadsheet Template to create a batch file
for searching meters into the database
Appendix B - Decoding Search Reference information for interpreting the
History Log Files
Search History logs and procedures for
running the decode program on the log
files.
2
Using This Manual
TWACS User Roles
Specific roles exist for users when interacting with the TWACS system. This
section explains the common roles defined for those using the TWACS
system. The TWACS system revolutionizes the way a utility can conduct
business. To take full advantage of the TWACS system, the utility must
understand who will need to use information from the TWACS system, who
will use which capabilities within the TWACS system, and in what capacity.
TNS Operator
The TNS Operator is a new role at the utility with the installation of the
TWACS system. TWACS Net Server (TNS) is the computer system that
controls aspects and interacts with components of the TWACS system.
Although it is a new role, it is common that an existing utility employee will
add the role of TNS Operator to their existing list of responsibilities. The TNS
Operator is the person who has the most comprehensive knowledge of the
TNS system and should be the focal point of responsibility for the TNS
system. The TNS Operator is responsible for a number of critical system
functions including but not limited to:
• Entering information into TNS about substation equipment
• Entering meters into the database
• Configuring meter addresses
• Setting up Automatic Meter Reading (AMR)
• Using the system for enhanced functionality
• Ensuring that TNS information is backed up
3
TWACS User Roles
TWACS Project Manager
The TWACS Project Manager (PM) is a new role at the utility that comes
with the decision to deploy the TWACS system. The TWACS PM is
responsible for successful deployment of the entire TWACS system. The
TWACS PM must have a good understanding of the overall capabilities of
the TWACS system and the goals of the utility in their deployment of the
TWACS system. The TWACS PM must develop an understanding of
many aspects of the TWACS system including, but not limited to:
• What the TWACS system enables the utility to do
• What the utility would like for the TWACS system to do
• Meter capabilities
• Read functions and their uses
• Regulatory issues the utility may be facing
• Billing capabilities the utility possesses or would like to possess
• What customers want the utility to do for them
• What the utility would like to do for its customers
Although the TWACS PM is a new role introduced by the deployment of
the TWACS system, the role of TWACS PM may be added to the
functional responsibilities of an existing employee or it may be contracted
out to a third party. In either case, the TWACS PM will work closely with
DCSI personnel to develop an understanding of how the TWACS system
should be deployed to meet the goals of the utility.
4
Using This Manual
Customer Service Representative/Manager
The Customer Service Representative (CSR) and the CSR Manager are
existing utility employees who interact with customers on issues relating to
the customer’s electric service. The CSR interfaces with the TNS system
within the TWACS system for various functions including:
• Immediate service disconnects/connects
• On-request meter reads for customer billing complaints
• Meter read history review
• Read functions and their uses
• Review of outage counts
• Review of daily or hourly usage reports of customer energy use
• Interaction with Load Control elements to tailor use to customer need
• Interaction with the TWACS system to test voltage if a customer has
problems with power that cause dimming lights or other problems
Billing Personnel
Billing personnel are existing utility employees responsible for billing
customers for energy use. Billing personnel use the TWACS system through
TNS relating to the following functions:
• Collection of export files detailing customer use and input into existing
Customer Information Systems
• Validation of billing data
• Establishment of appropriate rate classes (in conjunction with the TNS
Operator)
• Service disconnect for overdue payment (in conjunction with CSRs)
• Fraud and theft protection
5
TWACS User Roles
Substation and Transmission Engineer
The Substation and Transmission (S&T) Engineer is an existing utility
employee who deals with the infrastructure that delivers power to the
customer. An S&T Engineer might have the following responsibilities
relating to the TWACS system:
• Design of substation components for the TWACS system
• Support of TWACS substation system components
• Validation that the TNS system configuration mirrors the equipment
and configuration of the substation (with the TNS Operator)
• Use of outage reports for indications of major problems
• Support of Load Control applications for load shedding advantages
• Review of consumption reports for short-term load estimates
• Validation that Alternate Paths account for distribution changes (with
TNS Operator)
• Use of testing tools for voltage validation
6
Using This Manual
Meter Technician
The Meter Technician is an existing utility employee that deals with
installation and support of meters. The Meter Technician would interact with
TWACS system components at the customer site for various functions
including, but not limited to:
• Determining meter configurations by working with the TNS PM and the
TNS Operator
• Installing, configuring, and supporting meters to support the utility's
goals for the TWACS system
• Determining device location identifiers to help the TNS Operator sift
through faulty tamper indicators
• Determining load control unit configuration by working with TNS PM,
TNS Operator, and S&T Engineer
• Installing, configuring, and supporting load control units to support the
utility's goals for the TWACS system
• Working with TNS Operator and Billing personnel to resolve energy
theft issues
• Reviewing TNS quality of signal indicators that indicate meter
problems
• Reviewing TNS outage reports that indicate service problems
Customer Engineer
The Customer Engineer is a person who interfaces with predominantly large
customers on issues relating to their service requirements. The Customer
Engineer may or may not be a new role for the utility. The Customer Engineer
must be fluent with capabilities provided by the TWACS system to perform
the following functions:
• Discussing with customers capabilities the utility can provide through
the use of the TWACS system
• Producing/reviewing utilization reports for customers from TNS
• Performing custom reads for customers in TNS
7
Recommended Chapters by User Role
Recommended Chapters by User Role
Distribution Control Systems, Inc. (DCSI) suggests the following chapters
based on the interests of the user:
User
Suggested chapters
TNS Operator
TWACS Project Manager
Customer Service Representative
Manager
All
All
1 The TWACS System
2 Substation Setup
4 Reading Residential Meters
5 Operating TNS
6 Load Control
7 Two-Way Addressing
8 Service Disconnect/Connect
1 The TWACS System
2 Substation Setup
5 Operating TNS
8 Service Disconnect/Connect
All
Billing Personnel
Substation and Transmission
Engineer
Meter Technician
Customer Engineer
All
1 The TWACS System
2 Substation Setup
3 Searching Meters
5 Operating TNS
6 Load Control
Support
Please address your questions to Customer Care as follows:
E-mail:
[email protected]
Phone:
1-800-892-9008
Address: Distribution Control Systems, Inc.
945 Hornet Drive
Hazelwood, MO 63042
USA
8
CHAPTER
1
THE TWACS SYSTEM
This chapter explains DCSI’s Two-Way Automatic Communication System
(TWACS) and provides an overview of the TWACS Net Server (TNS).
The TWACS system enables electric utility companies to perform enhanced
functions and gather information not previously available. Utilities can
revolutionize the way their business is done through the TWACS system.
As an electric utility begins the process of evaluating or implementing the
TWACS system, it is important that those involved with the use and
implementation of the system have a general idea of the TWACS structure
and what the TWACS system will do for the utility. This chapter provides a
high-level overview of how the TWACS system can change the way business
is done in the utility.
9
TWACS System Overview
This section provides a high-level overview of what the TWACS system is,
what the TWACS system does, and how the TWACS system fits in the
overall scheme of utility company systems.
Understanding TWACS System Basic Applications
TWACS is a system designed for electric utility companies that provides a
unique bi-directional system for collecting, communicating, and analyzing
information about and managing utility customer electricity usage. The
TWACS system uses existing power line assets for two-way remote data
acquisition and control solutions.
The TWACS system is a critical business tool for utilities who understand
that serving customers and keeping them loyal rests on:
• The meter
• Near real-time data
• The best-in-class performance and competitive advantages that the
TWACS system enables
TWACS Enables New Functions
Using the TWACS system, electric utility companies can revolutionize the
way they do business.
The TWACS system enables the electric utility to gather information and
perform functions not previously available. The TWACS system uses the
existing infrastructure as the path for gathering information. The TWACS
system can be valuable in many aspects of the utility’s business including:
• Automatic Meter Reading (AMR)
• Interval data collection
• Line voltage and power quality
monitoring
• Outage mapping
• Remote service
disconnect/connect
• Load shedding
10
Chapter 1 • The TWACS System
Automatic Meter Reading
Traditionally, utilities read meters manually by a person actually going from
one meter to the next documenting readings from the meter. Using the
Automatic Meter Reading (AMR) function of TWACS, electric utilities can
read meters for various reasons at various times of the month without ever
dispatching a person to a meter site. AMR provides a level of cost savings for
the utility and enables the utility to perform many other functions not
previously available with manual reads.
AMR can be a valuable tool in aiding both customers and electric utility
personnel in resolving customer problems and managing customer energy
use. Among these problems are customer situations like the following.
Customer Problems
Type of meter read that can help
“I want to know why my bill was so high last month.”
AMR, Hourly, Daily Shift,
On-Request
Hourly
“I want to know how much energy we use when we’re at
work versus when we’re at home.”
“I want to know what impact my visiting kids have on
my energy use.”
“I want to know how much it would impact my energy
costs to keep my business open another three hours in
the evening.”
“I want to use trend information on energy use as part of
an analysis to see if it makes sense to adjust business
hours during certain times of the year.”
“Can you help me figure out why my bill is so much
higher than my neighbors’?”
“I’m moving out of my home today. Can you disconnect
my service now so I won’t get charged for additional
days?”
“How much capacity will we need in this subdivision in
the next six months?”
“We’re in a mid-summer crisis. We need to re-engineer
the transmission facilities. How can I isolate which
customers have a recent increase in usage?”
Daily Shift, On-Request, Hourly
Hourly
Hourly, Daily Shift
AMR, Hourly Daily Shift,
On-Request
On-Request, Service Disconnect
(see the TNS Service
Disconnect/Connect Manager User
Guide Y10357TM)
Daily Shift, Demand, Hourly or
Interval Data
Daily Shift, Demand
11
Scheduled Daily Shift Reads
DCSI recommends the TWACS system be set up to perform reads every
day. DCSI manufactures meters to store a freeze snapshot at midnight, and
the TWACS system has a 24-hour window in which to pull off the
snapshot data for the daily read before it is overwritten.
Using the TWACS system, the utility runs reports detailing the amount of
usage per day. The utility can establish trends with this information.
Daily historical information shows the customer’s utilization. A customer
may have a complaint about a bill. In the previous example, the Customer
Service Representative (CSR) views customer usage on a daily basis for
the month of December. By reviewing daily information, the customer can
see that having two college age kids home over the December weekends
and Christmas holiday caused a spike in utilization.
The daily read report in the previous example, combined with an analysis
of the temperatures for those days listed, can help isolate the issue. The
heater was running feverishly on cold days for the customer. After a site
visit, the utility determined for the customer that the building contractor
had neglected to properly insulate the attic.
12
Scheduled Hourly Reads
Meters can be read more often than every day. Meters can store information
for hourly tracking of information. You can run reports that detail the amount
of usage per day in order to establish trends.
The hourly report in the previous example is from a home in which the
builder neglected to insulate the attic. The report shows the attic was insulated
between 8:00A.M. and 10:00A.M. on December 5th. The report yields a good
estimate of what the lack of insulation was costing the homeowner.
Commercial customers benefit from this type of information as well. Hourly
reports provide information to commercial customers that can be used in
cost/benefit analysis for staying open later or cutting the workday shorter.
Trends can also be established for specific times of the year to help determine
optimal seasonal hours of operation.
On-Request Meter Reads
CSRs often receive calls relating to billing questions. In the days of manual
meter reading, the utility would dispatch meter readers or customers would
self-read their meters for an accurate count or verification. The TWACS
system enables CSRs to take an immediate reading while the customer is on
the telephone. This on-request read capability provides CSRs with new
capabilities not available with the previous manual process. For example:
A utility’s customer contacts the utility and
notifies them that moving day has arrived
and the utility must disconnect service. The
CSR can perform an immediate service
disconnect followed by an on-request meter
read with the customer on the line to provide
the customer with a statement of the final
bill.
13
Demand Reads
Peak demand is a tariff component for some utilities, particularly for
commercial customers. Utilities can use the TWACS system to accurately
track and bill for high periods of usage accordingly.
It is often difficult to estimate energy requirements for a customer or group
of customers. Using demand reads, the utility can get an idea of how much
energy to budget for a customer or group of customers. This can be
particularly beneficial in a short-term energy crisis created by high use or
power failure. With demand reads in the TWACS system, the meters store
a high-water mark for usage. This high-water mark represents the highest
15-minute demand of usage for the customer. Using this information,
Substation and Transmission Engineers can estimate peaks more
accurately based on high usage for customers and groups of customers.
Some utilities use this high-water mark reading as the basis of the billing
rate for the rest of the year.
14
Load Control
With two-way communication to the customer site, the TWACS system
enables powerful methods for utilities to perform functions that allow
management of peak power demand. One of those functions is load control.
Using load control, utilities can remotely engage and disengage elements of
high use on the customer premise. Examples of customer situations that
benefit from such management are as follows.
Customer Situations
“Peak times in July are causing us to have problems with brown-outs.”
“When we lose power for a corporate customer and redistribute facilities to
accommodate, load capacities are exceeded.”
“Our customers ask us for help controlling their energy bills.”
“Pricing changes from deregulation have created windows of opportunity for
customers to shed peak time rate power costs.”
Load control uses the same TWACS system
infrastructure deployed for AMR. Using the
TWACS system load control, the utility can
plan strategies that allow trimming of
utilization during peak usage times. Load
control allows the utility to remotely turn off
components within a residential (or
commercial) customer premise that draw
substantial levels of power. This shedding of
power allows the utility to control peak
demand that can avert brownouts.
Typical components set up on load control
include items like water heaters and air
conditioners.
15
Service Disconnect/Connect
Using the service disconnect/connect features of the TWACS system,
CSRs can perform a near immediate physical deactivation and reactivation
of service without dispatching a meter technician to the premise. For more
information, see the TNS Service Disconnect/Connect Manager User
Guide (Y10357TM). This feature can help resolve problems like the
following.
Problems
“I’m moving today, and I want my billing to stop now.”
“I can't pay my bill this month…or next month…or next month.”
“Can you disengage the service at our vacation home for the next two months?”
“We just moved in. Can you turn our power on?”
Meters can be equipped with a collar that can receive and respond to
commands from the TWACS system to disconnect or reconnect the power
in a matter of seconds. Connections may be made in response to a new
customer who has just moved into a new home and is requesting power.
Disconnects may be performed on bad credit customers who are
continually late on payment. Disconnects may also be performed at the
time of account closeout when a customer is moving out of a home or
business. Automatic disconnect followed by an on-request read can give
the customer a bill of their exact usage. Utilities gain a level of
responsiveness not previously available and reduce the cost associated with
connecting and disconnecting customer service by disconnecting service
through the TWACS system.
Tamper Detection/Energy Theft Reduction
The TWACS system enables the utility to detect meter tampering, thus
reducing the occurrence and impact of energy theft. Energy theft can take
several forms including the following.
Problems
“We think the customer may have turned the meter upside down for part of the
month, but we can’t prove it.”
“The customer's bill is substantially less over the past few months. It may be
that they have bypassed the meter.”
The TWACS system can detect meter tampering. Customers who pirate
electricity generally do so by either disconnecting the meter for a period of
time or turning the meter to run in reverse. Both of these actions are illegal
but can be difficult to prove without the TWACS system. TWACS
transponders report three items that can indicate tampering:
• No pulses in 24 hours
• Reverse rotation
• Blink count
16
No Pulses in 24 Hours
This indicator identifies if the meter has not recorded energy use in a 24-hour
period. In the case of this indicator, the TWACS system allows the utility to
track nuisance no pulse indications from barns, light poles, vacation homes,
etc., by documenting special fields that allow you to identify customers for
whom a no usage would be normal.
Reverse Rotation
This indicator identifies if the meter has run in reverse. A customer may
reverse the feeds on the meter causing the meter to run in the opposite
direction, thus reducing the customer’s usage and bill. The TWACS
transponders on the meter can detect this condition, report the theft attempt,
and bill for the pulses in the reverse direction.
Blink Count
When the meter loses power, the transponder in the meter tracks the outage
through the blink count. If a customer is intermittently bypassing the power
throughout the billing cycle to avoid detection, the TWACS system records
the blink count and provides an indication of what is happening.
Service Reliability/Outage Count Monitoring
The TWACS system enables the utility to detect outage counts and collect
availability information in real-time, thus helping to isolate trouble and avert
more major failures. The following are a few examples of customer problems
that might occur.
Problems
“The customer says they are getting frequent power flickers. Can we isolate if it’s a
customer problem or utility problem?”
“We’ve had a customer call every couple of days about light flickers, but we
haven't been able to isolate the trouble. We need more information about the scope
of the problem.”
“The customer said their power was out. We dispatched a technician only to find
out that it was the customer’s problem.”
“Can we tell if all our customers are back in service after the outage?”
“Our lost energy average runs too high.”
“We lost another transformer to overload. We need to monitor these more closely.”
“Our distribution path data is way off. We continue to make mistakes in our
judgment.”
17
Blink Count Indications of Future Problems
Outage monitoring can be done through the use of the TWACS blink count
tracking. Intermittent problems in service can be very difficult to
troubleshoot and can be a sign of more major problems to come.
As an example, equipment intermittently failing or tree limbs brushing
against power lines may cause a temporary power failure that the customer
sees as a blink in their electricity. The customer may not report a minor
outage such as this. The TWACS system will see these blinks and track
them as part of its blink count. Since the meter reports the blink count, the
focus on the problem is narrowed to the locations that share the problem.
This forewarning might be used to summon tree service personnel focusing
on specific neighborhoods and customer locations for trouble, hence
narrowing the focus of where major trouble is likely to show. Using this
blink count feature of the TWACS system effectively has the potential to
save the utility major expenses associated with line repair, not to mention
the potential of saving the life of an unfortunate person who could be
caught in the wrong place at the wrong time if a power line falls due to the
weight of a tree limb.
False Dispatch: Customer Problem
Outages reported by a customer often result in dispatching service
personnel to the location of the outage. If the problem is the customer’s, the
manpower of a truck roll is wasted. With the TWACS system, while the
customer is on the line, the CSR can do a quick test on the line to see if the
meter responds. If the meter responds, then the problem is beyond the
meter and, hence, is the customer’s problem. There is no need to dispatch a
technician to the site to ensure it is not the utility’s problem.
Are All the Customers Back Up?
After a major system outage, the TWACS system can be used to validate
which customers are back on line and which ones still have residual
problems. This can save valuable time for the technician that is still in the
area when they find out that three homes in the neighborhood are still
without power.
Where Did the Power Go?
When utility companies purchase power from upstream sources, the
difference between the amount of power they purchase minus the amount
of power they sell represents the amount of power lost. While a certain
amount of power loss is a normal part of distributing power, excessive
amounts can cause unnecessary revenue loss. Excessive loss amounts can
come from a variety of sources including equipment failure and customer
theft. Using the TWACS system, a very accurate estimate of loss can be
calculated at various levels, allowing the utility to focus efforts on when
the power is lost and where the lost power is going. One utility was able to
cut lost power from seven to three percent after deploying and using the
TWACS system.
18
How is the Transformer Load?
Often times, utilities find out about overloaded transformers when the
transformers blow and have to be replaced. Using the TWACS system,
customer demand can be monitored so that when utilization exceeds certain
thresholds, distribution problems can be handled in a more graceful manner.
Getting Pathmaps Straight
Utility pathmaps and actual
distribution facility configurations
Radial Circuit
do not always match. Keeping these
two elements synchronized is
particularly challenging when
cabling is underground and not
visible. Using the TWACS system,
the utility can validate and correct
pathmaps to avoid costly mistakes.
Radial Circuit
For example, a neighborhood that is
documented on the wrong phase can
have problems if they are redirected to another distribution path and
consumption estimates are exceeded. Using the TWACS system, the utility
can improve the accuracy of maps to avoid these types of mistakes.
MTU OMU
12.47kV
D
Normally Closed
RAD1
LTN1
LTN2
D
D
D
Area Network
120/208V
Spot
Network
277/480V
D
D
12.47kV
D
D
LTN3
LTN4, ...
RAD2, ...
MTU OMU
Billing Enhancements
The TWACS system information can be used for a number of benefits
relating to billing and other customer service related issues. Since it is easy
and inexpensive to collect usage information down to the day, hour or
15-minute increment, the utility can enhance the way it interacts with
customers relating to billing.
The following are some examples of customer situations in which the
TWACS system might be useful:.
Problems
“Our customer wants a consolidated bill for five sites. We can’t provide one bill
with the same interval, and we’re having to hold up billing while we queue the
reads that come in.”
“I get my Social Security check on the 5th. Can you bill me on the 6th so I'm sure
to have enough money to cover the bill?”
“Can you monitor the power at our vacation home so our pipes don’t freeze?”
“We have implemented budget billing, but to save money, we only read annually.
Now we have no idea how much lost power we have.”
“We need to reflect in our customer’s billing our actual cost. That cost goes up if
we need to go to outside resources during peak times, and our customer bills need
to reflect this increased cost.”
19
Consolidated Billing
The TWACS system makes consolidated billing very easy. Since reads are
generally done at least every day, a customer’s billing cycle does not need
to be related to the geographical location of the customer. A customer with
five different locations spread across the metropolitan area can have a
consolidated bill for all the sites with minimal effort on the part of the
utility.
Specific Day of Month Billing
For many people, living from paycheck to paycheck is a reality,
particularly for those living on fixed incomes. Some customers want to
prioritize certain bills so they are paid as soon as they receive their
paycheck. The TWACS system allows you to set up the billing cycles to
meet the needs of the end customer. This ultimately means a more
consistent revenue stream and less cost for the utility when they do not
have to worry about funds availability with the customer.
Vacation Home Monitoring
People who own vacation homes that they visit infrequently, or seasonally,
may need help monitoring the availability of electricity. If electricity is
disrupted, there is the potential for bad things to happen like frozen water
pipes or lost food in the freezer. Using the TWACS system, utilities can set
up paid services in which they monitor the availability and use of
electricity pro-actively at a customer’s vacation home to avoid such
problems.
Budget Billing Causes Lost Energy Tracking Problem
When budget billing is implemented, there is temptation to save cost by
reducing meter reads to a minimum annual reading. Reducing meter reads
to once annually makes it difficult to track lost energy. With the TWACS
system, you can implement budget billing and still maintain the daily or
hourly reads needed for tracking lost energy without incurring additional
cost.
Time of Use Billing
It is the law of supply and demand when a utility has to pay a premium for
energy from sources like energy brokers during peak times. The result is
higher energy costs during the peaks. At certain times of the day, energy
demand and energy costs peak. Many utilities want customer billing to
reflect this additional cost. Prior to the TWACS system, time-of-use (TOU)
billing required special meters and a lot of hassle. With the TWACS
system, hourly billing can be enabled quickly and easily, without
additional cost, simply by configuring the TWACS system and the meters
for hourly billing cycles.
20
Cross-Utility Cooperative Work
The TWACS system enables the utility to interact with other meters on the
customer’s premise. The electrical system provides an ideal path for flow of
two-way information (unlike gas and water paths). The utility can use the
communication path, enabled by the TWACS system, to read not only
electric meters, but water and gas meters as well. This function may solve
problems from several different perspectives:
Problems
“The water co-op has asked us if we can help them automate their meter reading
process.”
“The board is pressing us for revenue growth, so we are approaching the gas
company to use automation of their meter reading as a source of revenue.”
Properly equipped electric meters,
such as the Schlumberger
CENTRON RF, have inputs for
water and gas meters. The
TWACS system can read all three
meters automatically.
TWACS System Design
The TWACS system enables electric utility companies to perform enhanced
functions and gather information not previously available to the utility. By
using the TWACS system, electric utilities can revolutionize the way they do
business.
TWACS system, it is important for those involved with the use and
implementation of the system to develop a general idea of how the TWACS
system is structured. The general areas of understanding covered in this
section include:
• Knowledge of components involved in the TWACS system
• Understanding how the TWACS system integrates with existing
electrical system elements
• Knowing what changes utilities must make to equipment, configuration,
and procedure to deploy the TWACS system
This section provides a general overview of the TWACS component levels,
what is included in each component level, and how the TWACS components
fit in the overall scheme of the electrical system.
21
TWACS System Design
TWACS Levels Overview
There are three levels of TWACS components.
Level 1 – Central Control
Equipment (CCE) includes
computer and related
components installed at the
utility’s central office. These
components include the
TWACS Net Server (TNS), and
communication equipment
connecting the TNS system with
Level 2 components.
Level 2 –
Substation
Communications
Equipment (SCE)
includes
equipment found
at the substation.
Level 2
components
interface the
TWACS system
with the electrical system to enable outbound and inbound communications
across the existing electrical system infrastructure. The main components
include the Control and Receiving Unit (CRU), the Outbound Modulation
Unit (OMU), the Modulation Transformer Unit (MTU), and the Inbound
Pickup Unit (IPU).
Level 3 – Remote
Communications
Equipment (RCE)
includes
equipment found
at the customer’s
premise. Level 3
components
include meters
and other
equipment designed to provide information about the services provided by
the electric utility and allow the utility control of those services.
The TWACS system is a fixed system because it uses existing
infrastructure components to distribute electricity to automate
communication with meters. In the case of the TWACS system, the
communication infrastructure is, in part, composed of the electrical system
infrastructure the utility already has in place.
22
TWACS Level 3 Components - RCE
The TWACS system includes components
on the customer’s premise that allow the
utility to gather information and perform
activities relating to the customer’s electrical
service. The generic term for customer
premise devices is Remote Communications
Equipment (RCE). The most common RCEs
are meters and Load Control Transponders.
Meter versus Transponder
Electric companies have used meters for generations to track electricity
usage. Utilities can equip a meter with a transponder that reads the meter and
relays information back to a central collection resource. DCSI manufactures
transponders that attach to or integrate with a variety of meters. The meter in
to the right is a traditional electro-mechanical meter with a transponder
integrated within the lower half of the meter.
Think of the transponder as the brains of the meter. When using the TWACS
system, the term meter refers to the combination of meter and transponder.
Meters, Meter Numbers, and Serial Numbers
A meter manufacturer assigns a
meter number to each meter it
produces. Utilities key in the meter
number into their billing system.
The meter number is different from
the serial number of the TWACS
transponder. DCSI assigns a unique
serial number to each TWACS
transponder it manufactures. A
utility may track both the meter
number and serial number in the
customer billing system and in TNS. The utility may choose to replace the
meter number with the TWACS serial number. In a TWACS deployment, the
utility must populate the TWACS serial number field, and the meter number
is optional. The TWACS system uses the serial numbers to communicate with
the meter.
Component Name
Meter/Serial#
Manufacturer Assigning
Siemens SX Meter
CMT-SX Transponder
Meter# 84 642 886
Serial# 5859549
Siemens
DCSI
23
TWACS System Design
Commercial versus Residential Meters
Meters come in a variety of types and models, but the most general
categories are commercial meter and residential meters. Since businesses
generally consume much more energy than residences, commercial meters
accommodate higher amounts of energy. Commercial meters are those that
are three-phase meters allowing all three phases of energy to flow into a
business. The phases are called Phase A, B, and C.
Since residences typically consume less power than businesses, residences
receive a lesser-powered connection to the electrical system. Hence,
residential meters are considered single phase meters allowing only a
single phase of energy to flow into the residence. Any available phase may
service a residence. It is common to distribute residences across phases for
load balancing. Utilities may use meters classified as residential for small
business.
Mechanical versus Solid State or Digital
Like our music and our watches, our electric
meters evolved from mechanical (or analog) to
digital. With mechanical meters, a technician
will bolt the TWACS transponder to the
mechanical meter, and the transponder reads a
black mark on the bottom of the spinning disk.
With digital meters, the TWACS transponder
is a circuit board the meter manufacturer
includes with the digital meter. It is common to
refer to digital meters as solid state.
Single Port versus Multiport
Another way to categorize meters is with the number of ports the meter has
for inputs. A single port meter can only track electricity use. A multiport
meter has inputs for gas and water meter inputs.
NOTE
24
The meter in this example has an extra set of inputs on the front panel
for the water and gas meter plug-ins.
Read Frequencies
Another way to categorize meters is by the frequency of the reads the utility
performs on them. Meter read frequency categories include daily, hourly, or
interval. With daily reads, the utility will program the TWACS system to
collect the meter information every day. The meter marks a daily freeze read
at midnight and the utility has until midnight the next day to read the meter
before the next day’s read replaces the previous read. With hourly reads, the
utility reads the meters three times per day and collects the information stored
in the meter’s registers for the previous eight hours. Some meters are capable
of more frequent reads. Commercial customers may want to see detail of
electricity usage broken down into 15 or 30-minute intervals. For this level of
detail, the customer needs a meter capable of interval usage tracking.
If the utility wants readings every then you read
or every x hours
Day
Hour
30 minutes
15 minutes
24 hours
8 hours
4 hours
2 hours
1 time per day
3 times per day
6 times per day
12 times per day
25
TWACS System Design
Read Types: Consumption versus Kilowatt Hours
The TWACS system categorizes read types into two groups, consumption
and Kilowatt Hour (KWH). A consumption reading tells The TWACS
system how much energy the customers used in a given interval. Meters
track intervals in 60-minute, 30-minute, and 15-minute increments. A
kilowatt-hour reading tells the TWACS system where the meter dial
settings are at particular moments in time. The type of read requested
determines the information received.
If a utility is collecting
0 1
0 1
0 1
0 1
0 1
2
2
2
2
2
9
9
9
9
9
8:00am
interval data, then
8
3 8
3 8
3 8
3 8
3
24730 KWH
4
4
4
4
4
7
7
7
7
7
utility personnel will
6 5
6 5
6 5
6 5
6 5
0 1
0 1
0 1
0 1
0 1
issue reads for
9
9
9
9
9
2
2
2
2
2
9:00am
8
8
8
8
8
consumption data. If a
3
3
3
3
3
24736 KWH
4
4
4
4
4
7
7
7
7
7
utility is collecting a
6 5
6 5
6 5
6 5
6 5
0 1
0 1
0 1
0 1
0 1
monthly read for
9
9
9
9
9
2
2
2
2
2
10:00am
8
billing, then utility
3 8
3 8
3 8
3 8
3
24739 KWH
4
4
4
4
4
7
7
7
7
7
6 5
6 5
6 5
6 5
6 5
personnel will issue a
0 1
0 1
0 1
0 1
0 1
read for KWH from
9
2
9
2
9
2
9
2
9
2
11:00am
8
8
8
8
8
3
3
3
3
3
the meter telling the
24744 KWH
4
4
4
4
4
7
7
7
7
7
6
5
6
5
6
5
6
5
6
5
utility what is on the
meter dial. The meter
shows the KWH readings from a meter at 8:00 A.M. and 10:00 A.M. at
24730 and 24736 kilowatt hours respectively. The consumption reading for
the hour between 8:00 A.M. and 9:00 A.M. is the difference between the
two readings or six-kilowatt hours. The previous illustration and following
table detail the KWH and hourly consumption readings for a three-hour
period.
26
Time
KWH
Hourly Consumption KWH
8:00 A.M.
9:00 A.M.
10:00 A.M.
11:00 A.M.
24730
24736
24739
24744
N/A
6 KWH
3 KWH
5 KWH
Common Meter Reference Page
The following table lists aspects of commonly used meters.
Meter Name
Use
Phase
Category
Ports
Freq.
IMT-3
IMT-3H
IMT-3H-3Port
Altimus
EMT-3A
CENTRON
EMT-3C-SP
CENTRON
EMT-3C-MP
CMT-SX
CMT-Vectron
Residential
Residential
Residential
Residential
Single
Single
Single
1
Mechanical
Mechanical
Mechanical
Digital
1
1
3
1
Daily
Hourly
Hourly
Hourly
Residential
Single
Digital
1
Hourly
Residential
Single
Digital
3
Multi
Commercial
Commercial
Three
Three
Digital
Digital
1
1
15,30,60
Hourly
IMT-3/3H
CMT-S4
CMT Vectron
IMT-3H-3Port
Altimus EMT-3A
Centron EMT-3C-SP/MP
27
TWACS System Design
Common Meter Vendor Reference Page
The following table lists the DCSI transponder name and the meter make
and model with which the transponder will operate.
DCSI Transponder Name
Meter Make
Meter Model
IMT-3
ABB/Westinghouse
GE
Siemens/L&G
Schlumberger
Altimus EMT-3A
CENTRON EMT-3C-SP
CENTRON EMT-3C-MP
CMT-SX
CMT-Vectron
Siemens
SchlumbergerSema
SchlumbergerSema
Landis+Gyr
SchlumbergerSema
D4, D5, AB1
I70
MS, MX
J4, J5
Altimus
CENTRON
CENTRON
SX
VECTRON
Load Control Transponders
A load control transponder (LCT) is remote
communication equipment that helps avoid
brownouts by diverting load. LCTs allow the utility
to turn off components like central air conditioning
units, electric water heaters, pool heaters, heat
pumps, pool pumps, baseboard heaters, and other
equipment remotely. Typically the utilities shed load
during peak times of the day for selected
components and at intervals designed to minimally
impact the customer. LCTs provide the utility
independent control of each component attached.
LCT
In some cases, the meter has LCT
capabilities built into the meter. For
example, the Altimus EMT-3A has an
optional load control feature.
Altimus (EMT-3A)
28
Remote Service Disconnect/Connect Modules
The TWACS system components can
interface with remote service
disconnect/connect (SDC) modules, which
are useful for a number of applications. The
transponder connects to an inter-base collar
that performs the disconnect/connect
function. There are three primary
applications for the disconnect/connect
feature:
• Revenue collection tool for problem accounts
• Customer Service enhancement for seasonal and rental customers
• Improved efficiency for safe and convenient connects/disconnects from
the central office
Currently, the IMT-3H SDC transponder supports an interface to the service
disconnect/connect (SDC) inter-base collar. Future enhancements will enable
capabilities for disconnect/connect on additional meters.
29
TWACS System Design
TWACS Level 2 Components
This section covers TWACS Level 2 Components. TWACS Level 2
components are the components that interface with the electrical system for
communication with Remote Communications Equipment (RCE) at the
customer’s premise.
Electrical System Bus and Feeder
Utilities have designed
the existing electrical
system to distribute
power to customers
located all over rural
and metropolitan areas.
Utilities distribute
power through a
network of substations.
Ultimately, utilities
draw power from a
power source such as a
nuclear power plant,
hydropower from a dam, wind-power from a windmill farm, or a
conventional power plant drawing power from burning coal or natural gas.
Power plants ultimately feed geographically dispersed substations designed
to service large areas of customer populations. At the substation, utilities
distribute power to area customers from large substation transformers
through the use of buses and feeders. This section focuses on the substation
where the TWACS system integrates with the electrical system.
Bus
A bus is the major transmission facility that distributes power from a
substation transformer. It is common to have only one or two buses coming
from a substation. Buses are contained within the substation area.
30
Feeder
The bus or buses connect
multiple feeders. Feeders
are the portions of the
distribution network
distributing power to
utility customers.
Appleway
Substation
B
u
s
Feeder
Feeder
A substation may have
many feeders distributing
power to customer areas
like neighborhoods. The
diagram to the right illustrates a simple Bus/Feeder layout.
MTU
Buses distribute power to the feeders at fairly high
levels of voltage. Common voltage for a bus or feeder
is between 4,000 and 35,000 volts. For TWACS to
interface with the power system, technicians install a
Modulation Transformer Unit (MTU) to step down
the voltage.
The purpose of a transformer is to
change the voltage from one level to
another. Think of the MTU as
having two sides. One side plugs
into the bus (or the primary side at
4000 to 35,000 volts) and the other
side plugs into the TWACS
equipment (or the secondary side at
480 volts).
31
TWACS System Design
Substation Communication Equipment
The second level of the TWACS system is the Substation Communications
Equipment (SCE), commonly referred to as the substation. There may be
one or more substations in a utility. The main SCE component is the
Control and Receiving Unit or CRU. A communications link (represented
by the modem) connects the CRU to the TNS master station located at a
utility central office (likely in the computer center). The TNS master
station is a TWACS Level 1 computer component providing a user
interface to the TWACS system. Commands from the TNS master station
are sent over the communications link to the CRU at the substation. The
CRU then communicates with other SCE components to execute
commands sent by the TNS master station. The following graphic depicts
the SCE components and how the components fit the substation.
32
TWACS Flow of Information
The diagram to the right represents the
flow of information through the SCE
components.
The TNS Operator or other user issues
a command to the TNS master station.
The TNS master station forwards the
command over a communications link
to the CRU. Once the CRU receives a
command from the TNS master station,
the CRU sends the required instructions over the power lines via the
Outbound Modulation Unit (OMU) through the Modulation Transformer
Unit (MTU), to the meter (or other RCE).
The meter sends a response to the command over the power lines and the
response is picked up by the inbound pickup unit (IPU) which forwards the
response back to the CRU. The CRU sends the response back to the TNS
master station over the communications link. Hardware configurations vary
slightly from installation to installation.
33
TWACS System Design
TWACS Communication
As previously mentioned,
communication in the TWACS
system utilizes the existing
power lines. Utilities distribute
power to customers using a
60-hertz signal. The waveform
of the typical 60-hertz signal is
illustrated in the graphic to the
right.
The CRU sends outbound
commands to the OMU. The OMU
then sends the command to the meter
by varying the current slightly at the
zero crossing point of the 60-hertz
sine wave. This unique approach
gives TWACS an advantage of
reaching meters long distances from
the substation, while still using the
existing infrastructure provided by
the electrical system. If the utility can
deliver electricity to the customer,
then the TWACS system can
automate meter reads and load control to the customer.
Similarly, inbound
communications from the meter
to the IPU are accomplished by
sending a signal near the zero volt
crossover point. When the CRU
sends commands out to the meter,
the IPUs are instructed to watch
for a return response on a
particular path of the electrical
system.
34
TWACS Level 1 Components
This section covers TWACS Level 1
components. TWACS Level 1
components form the interaction
point for TWACS users.
Communications link options for
connecting the substations to the
Level 1 components are also covered
in this section.
TWACS Net Server
The TWACS Net Server (TNS) is the heart of the TWACS system. TNS
interfaces the TNS Operator and other users to the TWACS system. While
configuration options vary depending on the complexity established by the
number of users and substations managed, the basic TNS configuration
involves a server and some form of communications links connecting TNS to
the substation.
TNS Basic Configuration
Often times, TNS is configured with a
bank of modems allowing the TNS
server to dial out and connect with
substations. A minimal base-level TNS
server configuration involves a
Windows 2000 server running three
applications:
• Oracle database server
• TNS application server
• Communication server
Modem bank
Windows 2000 Server with
Oracle database server
TNS application server
Communication server
The oracle database server is
responsible for managing the meter and meter-related databases.
The TNS application server is responsible for running the TNS programs and
providing an interface for communications.
The communication server is responsible for interacting with
communications facilities like dialups or dedicated-line facilities to connect
to the substation equipment.
35
TWACS System Design
TNS Advanced Configuration
In larger deployments of TWACS,
the basic TNS configuration may
not provide the optimum level of
performance. It is possible to
improve system performance, if
necessary, by segregating the
functions of the TNS system so that
the Oracle database server, TNS
application server, and
communication server run on
separate processing machines.
TNS User
TNS User
TNS User
TNS User
Local Area Network
Modem Bank
TNS
Communication
Application
Server
Oracle
In advanced configurations, like
Server
Database
the one shown on the right, the
Server
computers take on more distinct
roles. In the advanced configuration detailed in the graphic, the TNS
application server is the TNS master station. Although the TNS user
stations can perform functions in the TWACS system, all of the commands
and responses would flow through the TNS application server to the
substation, as it is the TNS master station in this configuration.
TNS Communications Options
There are various ways to configure the TNS communications facilities
linking TNS to the substations. There are many factors that might impact
how a utility configures their communication options. These factors
include, but are not limited to:
• Long distance costs between the substation and TNS
• Support for interactive use by CSRs
• Speed of processing reads
• Cost of communications facilities
• Use of existing infrastructure
General TNS Communications Topics
In the most basic configuration, the TNS server can have communication
ports and modems built in, and the TNS server can directly connect to a
communications line connecting the TNS master station to the substation.
In the substation, the equipment terminating the communications link is the
Control and Receiving Unit (CRU). The CRU has communications ports
able to connect to a modem or other data communications equipment.
36
Dialup versus Dedicated
Utilities can configure
the TNS server to
operate using a dialup
communications line.
In this case, the TNS
server must dial each
time it has a need to
communicate with a substation. This process can slow the overall
communication time since it takes about 30 seconds to actually connect with
the substation equipment. This slow connection feature may not be the best
method if the utility wishes to use the TWACS system for Customer Service
Representative (CSR) queries while tending to a customer calling for support.
A potential exists for no available dialup facility when the CSR needs to
connect to a substation. Busy signals, telephone system problems, and poor
line quality can cause issues with dialup access.
Alternatively, configuring the TNS server to operate using dedicated
communications facilities is possible. With a dedicated link to each
substation, there is no communications delay in setting up the connection (as
with dialup communications). Hence, CSRs and other users can expect much
quicker responses from the TWACS system.
Communications Facility
Connect Speed
Cost
Dialup
Dedicated
Slow
Fast
?
?
While cost is certainly a factor, a utility, when considering dedicated versus
dialup communications facilities, should acknowledge it is impossible to
make a blanket assumption about which facility has a higher cost. For
example, it may appear that dialup facilities are less costly than dedicated
facilities. If the utility incurs long-distance charges when calling between the
TNS server and the substation, the long-distance adds to the cost of dialup. If
the utility already has a dedicated communications link in place, designed for
other communications with the substation, then it may actually cost the utility
less to use the existing dedicated facilities.
37
TWACS System Design
Distributing Communication Servers
In certain geographically challenged TWACS deployments, it can be costly
to network all of the substations back to a central site where the TNS server
is located. Fortunately, utilities can design the TWACS system with
geographically dispersed communication servers.
In the illustration above, notice the TNS server is located in Mason City,
Iowa, and the communication servers are in Lincoln and Omaha, Nebraska.
Since Lincoln and Omaha are long-distance phone calls from Mason City,
this configuration provides a cost savings by eliminating charges from
dialing directly from Mason City to Lincoln and Omaha. Also, telephone
companies bill some dedicated communications services based on distance,
and this configuration allows a consolidation of substations in one area to
share the communications link (through the communication server) back to
Mason City. Notice also the design of the Lincoln system uses an existing
radio network. As long as the network designer provides proper interfaces
at the end equipment, the TWACS system is very flexible when it comes to
communications options.
38
Using Existing Networks
Many utilities have an existing network connecting the substations to a utility
central office. This network is normally some form of Wide Area Network
(WAN) using telephone company services like Frame Relay, ‘Private Line
networking, or Internet Virtual Private Network (VPN). Using terminal
servers to convert the serial inputs to a LAN-based communication interface
like Ethernet, it is relatively easy to use an existing network to connect the
TNS server to the substations. The following diagram illustrates a general
method for to configure WAN use for the TWACS system.
TNS System Design
TNS is the central control element of the TWACS system. TNS provides
utility companies with a user interface to manage two-way communications
with their meters.
TWACS system, it is important those involved with the direct and indirect
use and implementation of the system develop a general idea of TNS design
and how TNS operates.
TNS System Overview
This section discusses the general characteristics and design of TNS, typically
located at the utility central office. TNS provides the user interface for utility
company employees to interact with TWACS.
TNS System Components
TNS provides utility employees an interface to communicate with the
TWACS system. The following functions are set using TNS:
• Batched automatic meter reads
• Interactive meter reads
• Management of load control elements
• Interval data collection
39
TNS System Design
• Line voltage and power quality monitoring
• Outage mapping
• Remote service disconnect/connect
It is important to understand that TNS is comprised of many components.
These components work together to complete the functions required of
TNS. This section covers a number of general aspects of the TNS design,
including the following concepts:
• Oracle Database Manager and servers
• Databases
• Tables
• Log files
Oracle Database Manager and Servers
DCSI has developed TNS around a database manager called Oracle. Many
system tasks known as server processes run through the Oracle database
manager. These server processes control aspects of the TNS system. The
diagram below lists the critical servers found in TNS. Server processes
must be active to perform certain functions. Each server process may have
its own databases and logs of information, and server processes may share
databases of information depending on requirements of the server process.
40
What is a Database?
TNS uses several databases to track information.
A database is nothing more than a collection of
related items kept in an electronic folder. For
example, there is a:
• Permanent Meter database responsible for
tracking all meters found on one of a
utility’s substations.
• Temporary Meter database that tracks meters TNS has yet to find.
• Database to track substation information.
• Database to track jobs to be scheduled.
The TNS users employ TNS applications to read and manipulate TNS
databases. Some examples of databases include:
Database
Name
TNS Program Name
Used
Permanent
Meter database
Temporary
Meter database
SCE database
Meter Misc.
Temp Meter Misc.
SCE Maintenance
Purpose
Tracks meters TNS has found on a
substation.
Tracks meters that have not made it
to the permanent meter database.
Tracks substation equipment
configuration.
41
TNS System Design
What is a Table?
Tables are simplified versions of databases. A
table is a simple list of items, and a table is usually
limited in size. TNS uses tables for lists of
information it must track. For example, there is a
table to:
• Track the types of meters a utility uses.
• Track the types of substations relating to the
meters used.
• Track blocks of serial numbers for meters used by the utility.
A TNS user uses a TNS program to read and modify tables. Some
examples of tables follow:
Table Name
TNS Program
Name Used
Product table
Product
Sub Product table
SubProduct
Product Type Model
Cross Reference table
Product Type
Model Cross
Reference
Purpose
Tracks types of meters used by a
utility and aspects about the
meter.
Tracks types of meters and how a
particular substation should
communicate with the meter.
Tracks serial numbers of meters
utility will use and type and model
of the meters.
Lists reference codes from various
functions within TNS.
Response Status Cross
Reference table
Response Status
Cross Reference
Meter Conversion table
Tracks meter pulse conversions to
KWH readings.
Meter Conversions
42
Log Files in TNS
TNS tracks some historical information about TNS activity in TNS databases.
This information is available using the TNS programs. AMR read data is an
example of this type of information. TNS also uses a number of log files that
track historical information about various aspects of TNS operation. TNS
users often view log files using a standard text editor like Microsoft®
WordPad©. DCSI programmers and Field Service personnel use some of the
log files to determine program problems. Utility employees will find some of
the log files relevant when performing basic tasks within TNS. Some of the
relevant log files include the following.
Log Name
File Name
Purpose
Search-in
History log
PreTIQ log
SHyyyymmdd.dat
Shows results of meters searched
into the database.
Shows meters that failed the
prequalification phase of the
meter search process.
Shows all connection and
disconnection history for a
communication server to
substations.
Shows a history of all transactions
to a substation and back.
PreTIQ.dat
Com Server
log
CSyyyymmdd.dat
Transaction
(TR) log
TRyyyymmdd.dat
43
TNS System Design
Managing TNS
TNS provides the utility with valuable tools for managing the TWACS
system, among these tools are TNS Watchdog and TNS Alerts. The utility
can use these tools to pro-actively respond to problems that arise.
TNS Watchdog
The Watchdog application monitors the availability of each critical server
process in TNS. At times, problems may arise with TNS components.
Utility personnel can use the Watchdog application to view the general
health of the TNS system. If a server process is not working properly, the
TNS Operator can view the Watchdog to see if the application is no longer
communicating with the Watchdog. From the Watchdog, the TNS
Operator can stop and start server processes in an attempt to correct
problems. You can access the Watchdog GUI by following the menu path
Start > Watchdog GUI.
The utility should contact DCSI Customer Care if a server process
continually fails.
Alerts from TNS
The Watchdog application also allows the TNS Operator to designate who
receives alerts if the Watchdog discovers a problem with one or more of
the server processes. Nearly every cell phone and pager today has an
associated Internet E-mail address. The utility may wish to send TNS alerts
to employee cell phones or pagers to expedite problem resolution.
NOTE
44
The TNS Operator can access the Options screen, as shown in the
screen snapshot by clicking Project > Options.
Integrating AMR Data with Utility Billing Systems
The TWACS system allows the utility to automate the meter reading process.
Utilities must harness the information from the AMR process and insert the
data into the existing billing process for AMR to be effective.
TNS Read Data
TNS outputs files from each AMR
process with information relevant to
customer billing. The TNS default
billing file created from the AMR
process may not be suitable for
Meter Read Data
integration into a utility’s customer
information system (CIS) or billing
system. DCSI, on request, will program TNS to create a custom, billing file
tailored to integrate with the utility’s billing system. TNS creates the custom
file in addition to the default billing file.
TNS
AMR Process
(Daily Shift TC)
TNS
Default
Billing
File
Custom
Billing File
Utility Billing
Process
(CIS)
45
TNS System Design
46
CHAPTER
2
SUBSTATION SETUP
The first part of this chapter, Understanding Substation Communications and
Architecture, discusses architectural aspects of the TWACS substation
components. Included in this section is a detailed discussion of component
configuration options and numbering. If you already understand the
architecture and numbering of substation system components, skip to Adding
Substations on page 66 for information specific to entering substation
information in the TNS application.
The substation is the entry point for TWACS communications over the
electrical system to and from the meters. It is essential for utility personnel to
understand the TWACS substation configuration and architecture in order to
configure TNS when adding or changing a substation configuration.
This chapter provides an overview of the substation communications and
architecture and covers, in detail, adding substations and communications
links to TNS.
47
Understanding Substation Communications and Architecture
Understanding Substation Communications and
Architecture
The substation is the point at which the TWACS system interfaces with the
electrical distribution system for automatic meter reading (AMR). The
utility installs various components at the substation to equip the substation
for TWACS AMR.
Prior to installing the Substation Communications Equipment (SCE) for
the system, the utility must make some decisions about how the utility
should configure the TWACS substation components to function relative
to the goals of the utility. The design of the substation is determined by the
configuration options chosen by the utility.
SCE Overview
Before deploying substation components, the utility must make some
decisions about how the utility wants to use the TWACS system. TWACS
substation components are integral to the ultimate communications
between TNS and the meters.
48
Chapter 2 • Substation Setup
SCE Process Flow
When a utility decides to deploy
the TWACS system, there are
several items the utility must
consider. The way in which a
utility plans to use the TWACS
system can substantially impact the
design of the TWACS substation
configuration.
SCE Process Flow
Review the options available on
the Feeder/Bus IPU and
communications.
The utility must consider several
factors, including:
• Will Customer Service
Representatives (CSRs)
perform interactive meter
reads while customers wait
on the telephone?
• Will CSRs use the TWACS
system to check power at a
customer site to avoid
technician truck rolls?
• What are the substation load
characteristics and will these
characteristics impact the
quality of signal received
from the meter?
• Will the utility incur
long-distance charges
connecting to the substation?
Discuss the options relevant
to the capabilities the utility
desires to provide now and
in the future.
Install CRU, MTUs, OMUs, IPUs
and document installation
configuration.
Install and configure
communications link between
CRU and TNS.
Configure TNS with the SCE
components and communication
link.
Search in installed meters.
Set up AMR on meters.
• Is there an existing Wide Area Network (WAN) or SCADA connection
in place to the substation?
• How many meters and load control devices will the utility manage using
the TWACS system from the substation?
• How many customers will the utility want to monitor in 60-minute,
30-minute, or 15-minute intervals?
49
The following table describes the potential impact to the TWACS system
design based on functions the utility desires to gain from the TWACS
system.
If the Utility Wants to
Impact to SCE Configuration
Have the CSR read meters
with the customer on the
phone.
Have the CSR test power to
a customer site with the
customer on the phone to
avert a technician truck roll.
Connect avoiding potential
long-distance charges to the
substation.
Connect using existing
SCADA or WAN links.
Dedicated communications link between TNS
and SCE (instead of dialup) provides fast
interactive reads.
and SCE (instead of dialup) provides fast
interactive reads.
Improve response quality
from meters.
Have more than 4000 meters
and/or load control devices.
Use interval reads to read
more than once per day.
Overcome problems that
might occur with a
transformer Open Air (OA)
Rating 30 Mega Volt Amps
or greater.
50
and SCE (instead of dialup) may save on
communication costs.
and SCE (instead of dialup) may save on
communication costs.
Use feeder-level IPU configuration over bus
level to overcome noise on a busy bus.
Employ the use of concurrent phasing (rather
than single receiver) to accelerate reads.
Employ the use of concurrent phasing (rather
than single receiver) to accelerate reads and
use dedicated communications link between
TNS and SCE (instead of dialup).
Parallel OMU Configuration
Substation Components
The following table
defines the
components and
their functions in the
substation.
Component
Acronym
Component Name
CRU
Control and Receiving Unit
OMU
MTU
IPU
Function
Responsible for handling
communications between TNS and
the other substation components.
Outbound Modulation Unit
Responsible for outbound
communications to the meter.
Modulation Transformer Unit Assists with outbound
communications by stepping down
voltage for the OMU.
Inbound Pickup Unit
Responsible for picking up signals
sent from the meters and passing
those signals to the CRU
components for interpretation.
SCE Information Flow
Com
Link
The TNS Operator or other user issues
a command to the TNS master station.
TNS
Utility Command
Center
The TNS master station forwards the
Appleway
command over a communications link
Substation
to the Control and Receiving Unit
IPU
B
CRU
(CRU). Once the CRU receives a
u
Meter
s Feeder
MTU
OMU
command from the TNS master
station, the CRU sends the required
instructions over the power lines via
the Outbound Modulation Unit
(OMU) through the Modulation Transformer Unit (MTU), to the meter or
other Remote Communications Equipment (RCE).
TNS-TWACS Net Server
CRU-Control and Receiving Unit
OMU- Outbound Modulation Unit
IPU-Inbound Pickup Unit
MTU-Modulation Transformer Unit
The meter sends a response to the command over the power lines and the
inbound pickup unit (IPU) picks up the response and forwards the response
back to the CRU. The CRU sends the response back to the TNS master station
over the communications link.
51
SCE to Meter Communications
Before deploying substation components, the utility must make some
decisions about how the utility wants to use the TWACS system.
Configuration options vary depending on the functions the utility expects
to gain from the TWACS system. This section discusses components
involved with substation to meter communications and the configuration
options of substation components.
CRU COMPONENTS
m
Co
k
Lin
TNS
Utility Command
Center
CRU
Appleway
Substation
CRMA
CRPA
SCPA
OFIA
The Control and Receiving
Unit (CRU) is the heart of
communications control at
the substation. The CRU
controls the communications
interface to TNS and the
communications interface to
components that interact
with the meter. The CRU
card cage contains several
cards that perform various
functions relating to inbound
and outbound
communications with the meter
and communications with TNS.
IPU
OMU
CRU Components
SCPA-Substation Control Processor Assembly
OFIA- OMU Fiber-Optic Interface Assembly
CRPA-Correlation Receiver Processor Assembly
CRMA-Correlation Receiver Multiplexer & Analog
Assembly
B
u
s Feeder
Meter
MTU
SCE Components
The CRU is comprised of several cards
including (pictured from left to right) the
Substation Control Processor Assembly
(SCPA), Correlation Receiver Multiplexer
Assembly (CRMA), Correlation Receiver
Processor Assembly (CRPA), and OMU
Fiber-Optics Interface Assembly (OFIA).
52
The following table lists the CRU cards and the functions each card performs.
CRU
Card
Component Name
SCPA
Substation
Communications
Processor Assembly
CRMA Correlation Receiver
Multiplexer and Analog
Assembly
CRPA
OFIA
Correlation Receiver
Processor Assembly
OMU Fiber-Optics
Interface Assembly
Function
Interfaces with TNS over a
telecommunications link and interfaces with
other CRU components over the CRU bus.
Transfers the analog inbound signals over
copper connections from the IPU to the
CRPA. Responsible for digitizing the analog
signal from the meter.
Works in conjunction with the CRMA to
process inbound information from the IPUs.
Interfaces via fiber optics with the Outbound
Modulation Unit for outbound
communications.
SCE Outbound Communications
NOTE
m
Co
SCPA
k
L in
TNS
Utility Command
Center
CRU
Appleway
Substation
OFIA
When installing TWACS
components at the substation,
the TNS Operator must know
the configuration of the SCE to
input to TNS. For outbound
communications, the
configuration is relatively
simple since there are few
variables. Each substation must
have a CRU. The number of
buses in the substation impacts
the number of OMU and MTU
devices. Each bus must have an
OMU and MTU connected to
the bus. The OFIA card in the
CRU supports connections to
four OMUs attached to each
OFIA card.
OMU
OMU
B
u
s Feeder
Meter
B
u
s Feeder
Meter
MTU
MTU
CRU Components
OFIA-Optical Fiber-optics Interface Assembly
SCE Components
There is a condition in which a utility may place two OMU/MTU pairs on a
bus. DCSI calls placing a dual pair of OMU/MTUs on a single bus parallel
OMU configuration. The condition requiring a parallel OMU configuration
occurs when a transformer Open Air (OA) Rating is 30 Mega Volt Amps or
greater. In this case, the utility will place two OMU/MTU pairs on the bus
and the OMU/MTU pairs will fire simultaneously. By firing simultaneously,
there is a better chance of successfully communicating with the meter.
53
The following table describes the quantities of SCE components required
for outbound communications.
Component
Quantity
Per
Notes
TNS
CRU
SCPA
OFIA
1
1
1
1
company
substation
CRU
every 4
substation
buses
OMU
1
substation
bus
MTU
1
OMU
The OFIA card has 4 sets of 3
fiber-optic ports per card. Each
set of 3 fiber-optic ports
connects one OMU.
Unless substation transmission
OA rating is 30MVA or more,
then 2.
A common problem with setting up communications between the OMU
and TNS is that the substation technician sometimes reverses the fiber
connectors for transmit and receive. The utility must connect the OFIA and
OMU ports as shown in the following table.
OFIA Port
Tx
Rx
Zc
54
OMU Port
--------------------- Tx
--------------------- Rx
--------------------- Timing
SCE Inbound Communications
When installing TWACS components at the substation, the TNS Operator
must know the configuration of the SCE to input to TNS. For inbound
communications, the configuration has several options depending on the
needs of the utility. The primary option for inbound communications is bus
versus feeder level IPUs.
Bus-Level IPU
m
Co
Utility Command
Center
CRU
CRPA
SCPA
TNS
k
Lin
Appleway
Substation
CRMA
The simplest way to design IPU
connections into the CRU is to connect
one IPU to each bus. DCSI calls
connecting one IPU to each bus bus-level IPU. With bus-level IPU
attachment, each bus requires only one
IPU and that IPU can read signals from
all feeders attached to that bus.
IPU
B
u
s Feeder
IPU
The diagram depicts single-receiver
mode.
CRU Components
Assembly
B
u
s Feeder
Meter
Meter
SCE Components
Feeder-Level IPU
m
Co
TNS
Utility Command
Center
CRU
CRMA
SCPA
k
L in
CRPA
DCSI may recommend the
utility configure a substation
with feeder-level IPUs. DCSI
will make this
recommendation if the load on
the bus is high. By placing the
IPU on the feeder, there is a
better chance of receiving
successful communications
from the meter since there is
less potential interference on
each feeder than on a bus with
high load levels.
Appleway
Substation
B
u
s
B
u
s
CRU Components
Assembly
IPU
Feeder
IPU
Feeder
IPU
Feeder
IPU
Feeder
Meter
Meter
SCE Components
55
Inbound Modes: Single Receiver versus Concurrent Phasing
CRMA
CRMA
CRMA
CRPA
CRPA
CRPA
The term receiver refers to
TNS
Utility Command
k
the CRPA card in the CRU.
Center
L in
m
Co
Single receiver mode and
SCPA CRU
Appleway
concurrent phasing are the
Substation
two methods for
IPU
B
configuring a substation for
u
Meter
inbound communications.
s Feeder
Concurrent phasing
provides the utility the
advantage of increased
speed when reading meters.
Using concurrent phasing,
the utility can double or
triple the speed of reads
from the meters over the
speed of using single receiver mode. Concurrent phasing and single
receiver mode have different physical configurations in the quantity of
CRMA/CRPA cards in the CRU card-cage and in the way the IPU
interfaces with the termination panels.
CRU Components
Assembly
SCE Components
IPU to CRMA Connection Facts
An IPU connects to a CRMA card through a termination panel that
connects to the backplane to which the CRMA card attaches. There are
design facts for how the IPUs connect to the termination panels and how
the termination panels connect to the backplane. The following is a list of
those design facts.
• A CRU can have up to four CRMA cards total, each supporting 32
inputs for a total of 128 inputs.
• An IPU has inputs for all three phases of inputs per IPU. DCSI
Engineers will reserve the spot on the termination panel for the
neutral lead as the SCE can convert into a synthetic neutral.
• The backplane connects each CRMA card to two ribbon cables. Each
ribbon cable supports two termination panels daisy-chained together.
Hence, each CRMA card can connect to four termination panels. The
two termination panels are identical. A person must visually inspect
the ribbon cable connection to identify whether the termination board
is the first or second in the daisy-chain.
• Each termination panel has two mux ports. A pair of termination
panels has four muxes, and each CRMA card supports two
termination panel pairs or eight muxes. Muxes are numbered 0
through 7 for each CRMA card, but mux ports are not labeled on the
termination panel.
56
• Each mux port connects four inputs. (Hence, a single termination panel
can connect eight inputs or two IPUs (four per mux), and a termination
pair can connect 16 inputs or four IPUs.
• Each bus must have at least one IPU with four inputs from that IPU
reserved on a termination panel for Phase A, B, C, and neutral.
• The label on the backplane for a CRMA card numbers 1 through 4, but
TNS numbers the CRMA cards 0 through 3.
Concurrent Phasing Facts
Concurrent phasing allows the utility to double or triple the read speed of
meters over single receiver mode.
• With concurrent phasing, there are two or three pairs of CRPA and
CRMA cards in the CRU chassis.
• With concurrent phasing, each CRMA is jumpered between the
termination panel and the backplane connection to connect the IPU
signaling to CRMA 1, 2, and 3 (or 1 and 2 if only two receivers are
used).
• With concurrent phasing, the utility is limited to eight IPUs or 32 inputs
on a CRU. If additional IPUs are required, the utility may add an
additional CRU at the substation.
IPU to Termination Panel Connections: Single Receiver Mode
The diagram is a logical
representation of how the
IPUs connect to the
termination panels when
a single receiver (CRPA
card) is used. Each IPU
connects to a bus or
feeder with each phase,
A, B, and C on one side
of the IPU. On the other
side of the IPU, each IPU
has a connection point or
input for each phase A, B,
and C that connects to the
termination panel.
Termination Panel #1 in Daisy-Chain
Mux 0
Mux 1
4 Inputs - 1 IPU
4 Inputs - 1 IPU
A, B, C, D
E, F, G, H
To
der
1
To
A B C N
IPU 2
A B C
Ribbon
Cable
Mux 2
Mux 3
4 Inputs - 1 IPU
4 Inputs - 1 IPU
A, B, C, D
E, F, G, H
To
B us
ee
or F
A B C N
IPU 1
A B C
r2
ede
r Fe
o
s
Bu
Ribbon
Cable
to
Backplane
or F
B us
eed
er 3
To
A B C N
IPU 3
A B C
4
der
F ee
r
o
Bus
A B C N
IPU 4
A B C
57
NOTE
REMEMBER
The neutral lead on the IPU is not connected to the termination panel,
however, a slot is reserved for the input on termination panel ports D
and H.
There is no physical label for the mux port on the termination panel.
Termination Panel to CRMA Backplane Connections: CRMA 1 and 2
The following diagram shows a logical representation of how the
termination panels connect to the backplane for CRMA 1.
Ribbon Cable
J13
1-16
J14
17-32
CRMA 1
J17
1-16
J18
17-32
J15
1-16
CRMA 3
Backplane
Ribbon Cable
J19
1-16
CRMA 2
Mux 0
Mux 1
4 Inputs - 1 IPU
4 Inputs - 1 IPU
A, B, C, D
E, F, G, H
Mux 2
Mux 3
4 Inputs - 1 IPU
4 Inputs - 1 IPU
A, B, C, D
E, F, G, H
J16
17-32
J20
17-32
CRMA 4
Mux 4
Mux 5
4 Inputs - 1 IPU
4 Inputs - 1 IPU
A, B, C, D
E, F, G, H
Ribbon
Cable
Mux 6
Mux 7
4 Inputs - 1 IPU
4 Inputs - 1 IPU
A, B, C, D
E, F, G, H
Ribbon
Cable
The following diagram is a logical representation of how the termination
panels connect to the backplane for CRMA 2.
J13
1-16
J14
17-32
CRMA 1
Ribbon Cable
J17
1-16
J18
17-32
CRMA 2
Mux 0
Mux 1
4 Inputs - 1 IPU
4 Inputs - 1 IPU
A, B, C, D
E, F, G, H
Mux 2
Mux 3
4 Inputs - 1 IPU
4 Inputs - 1 IPU
A, B, C, D
E, F, G, H
NOTE
58
J15
1-16
Backplane
Ribbon Cable
J16
17-32
CRMA 3
J19
1-16
J20
17-32
CRMA 4
Mux 4
Mux 5
4 Inputs - 1 IPU
4 Inputs - 1 IPU
A, B, C, D
E, F, G, H
Ribbon
Cable
Mux 6
Mux 7
4 Inputs - 1 IPU
4 Inputs - 1 IPU
A, B, C, D
E, F, G, H
Ribbon
Cable
The termination panel connections and numbering repeat for CRMAs 3
and 4.
Notice in the previous diagram, each termination panel pair is daisy-chained
and connected to a port on the backplane numbered J13 through J20. Each
pair of J ports is associated with a CRMA number as denoted on the
backplane portion of the diagrams.
Concurrent Phasing IPU Connection Diagram
The following diagram illustrates the CRMA to termination panel
connections when the utility configures the substation for concurrent phasing.
Ribbon Cable
Jumper Cable
Termination Panel #1 CRMA 1
Mux 0
Mux 1
4 Inputs - 1 IPU
4 Inputs - 1 IPU
A, B, C, D
E, F, G, H
J13
1-16
J14
17-32
CRMA 1
J17
1-16
J18
17-32
CRMA 2
r
so
Bu er 1
o
T ed
Fe
J15
1-16
Backplane
J16
17-32
CRMA 3
J19
1-16
J20
17-32
CRMA 4
A B C N
IPU 1
A B C
The utility uses a jumper cable to connect an IPUs termination panel to three
different CRMAs through the backplane connections, thus attaching the IPU
to all three CRMA boards in the CRU chassis. By attaching the IPU to all
three CRMAs, the CRPA cards paired with the CRMA cards can read all
three phases simultaneously. DCSI refers to a pair of CRMA and CRPA cards
used in concurrent phasing as a receiver set.
59
Inbound Communication Configuration Summary
The following table summarizes the various receiver options available for
inbound communication from the meter to the substation. Notice that
concurrent phasing increases the read speed, but decreases the number of
IPUs supported by the CRU.
Config
Mode
CRPA CRMA Cards
Cards (“Receivers”)
Maximum
IPUs
(4 inputs Max
per IPU)
Inputs
Single
receiver
Single
receiver
Single
receiver
Single
receiver
Concurrent
phasing
Concurrent
phasing
1
1
8
32
0-4000
1x
1
2
16
64
0-4000
1x
1
3
24
96
0-4000
1x
1
4
32
128
0-4000
1x
2
2
8
32
4000-8000
2x
3
3
8
32
8000 and up
3x
Meters Read
Effectively
per Day
Read
Speed
The following table details the number of SCE components needed for
inbound communication from the meter to the substation.
Component
Qty
Per
Notes
TNS
CRU
SCPA
IPU
1
1
1
1
company
substation
substation
substation bus or
feeder
Depends whether the utility
uses bus or feeder level IPUs.
Single Receiver Mode
CRMA
1
8 IPUs
CRPA
1
Substation
Termination
1
2 IPUs
Panel
Concurrent Phasing Mode
CRMA/CRPA 2 or 3 Substation
Receiver Sets
Termination
Panel
3-way Jumper
Cable
60
1
2 IPUs
1
Termination panel
pair
Single receiver mode
Concurrent phasing mode:
2 for 2x reads,
3 for 3x reads.
Concurrent phasing mode
Concurrent phasing only
Pictorial Representation of the IPU Connections
The following figure depicts the IPU connections using pictures of the
components.
CRMA Card
Backplane
One pair of termination
panels
61
TWACS System Substation Component Count Summary
The following table details the quantity of TWACS components the utility
may have in a substation.
Component
Quantity
Per
TNS
CRU
SCPA
1
1
1
Company
substation
CRU
Notes
Outbound Components
OFIA
1
every 4
substation buses
OMU
1
substation bus
MTU
1
OMU
The OFIA card has 4 sets of 3
fiber optic ports per card. Each
set of 3 fiber optic ports
connects one OMU.
Unless substation transmission
is 30MVA or greater, then 2.
Inbound Components
IPU
1
substation bus or
feeder
Depends whether utility uses bus
or feeder level IPUs.
8 IPUs
substation
2 IPUs
Single Receiver Mode
CRMA
CRPA
Termination
Panel
1
1
1
Concurrent Phasing Mode
CRMA/CRP
A Set
3
substation
Termination
Panel
3-way
jumper cable
1
2 IPUs
1
termination
panel pair
1 for single receiver mode
3 for concurrent phasing
Concurrent phasing mode
Concurrent phasing only
Question Flow for Documenting TNS Settings for IPU Map
TNS requires the user to configure the inbound communications through
IPU Map Settings. The TNS Operator determines the IPU Map Settings
based on the physical connections of the IPUs into the CRU components.
The following question flow will aid the TNS Operator in validating the
IPU map settings for connecting the IPU to the termination panel and
CRMA. Should the TNS Operator need to walk someone at the substation
through the physical connections to identify the appropriate parameters for
TNS, the following tables provide a logical flow of questions to assist in
the process of identifying TNS IPU Map Settings.
62
TNS will prompt the TNS Operator for the following information:
Detection
Point
TNS
IMA/CRMA
TNS
ISA/MUX
TNS
Channel
Phase A
Phase B
Phase C
Neutral
1.
2.
To which port is the IPU connected on the termination panel?
(Termination panel ports are labeled A-H.)
Port
TNS Channel
A
B
C
D
E
F
G
H
0
1
2
3
0
1
2
3
To which port on the backplane is the ribbon cable from the
termination panel plugged?
J-Port
TNS IMA/CRMA Port
J13
J14
J15
J16
J17
J18
J19
J20
0
0
1
1
2
2
3
3
63
3.
Is the termination panel the first or second on the ribbon cable daisy
chain?
J-Port
J13,
J15,
J17,
J19
J13,
J15,
J17,
J19
J13,
J15,
J17,
J19
J13,
J15,
J17,
J19
J14,
J16,
J18,
J20
J14,
J16,
J18,
J20
J14,
J16,
J18,
J20
J14,
J16,
J18,
J20
4.
Termination
Panel Ports
Daisy Chain
Sequence
Mux Port
A, B, C, D
1
0
E, F, G, H
1
1
A, B, C, D
2
2
E, F, G, H
2
3
A, B, C, D
1
4
E, F, G, H
1
5
A, B, C, D
2
6
E, F, G, H
2
7
The TNS Operator now has enough information to isolate the mux
port and complete the TNS entry.
Refer to the table on the following page to complete the information for the
TNS IPU Map Settings based on the information gathered and the IPU
positions identified from the previous question flow.
64
IPU Map Reference Table
The following table details the numbering scheme used in TNS for mapping
IPUs.
65
Adding Substations
Adding Substations
The substation is the point at which the TWACS system interfaces with the
electrical distribution system for AMR. The utility installs various
components at the substation to equip the substation for TWACS AMR.
When a utility installs TWACS equipment at a substation, the TNS
Operator must update TNS with the appropriate equipment configuration.
This section covers the steps required to update TNS to reflect equipment
configurations at the substation.
Adding Substations to TNS
After installing the TWACS substation equipment, the utility must
configure TNS to match the configuration of the substation.
The SCE Maintenance tool bar applications (refer to Chapter 1, SCE
Maintenance in the TNS End User Guide Rev D) allow the utility to define
the substation components in TNS.
66
Adding Substations Process Flow
When a utility installs a
substation, the substation
configuration in TNS must
match the physical
characteristics of the TWACS
substation components.
Adding Substations to
TNS Process Flow
Install SCE hardware and
document configuration settings
Communicate configuration
settings to TNS Operator
Add substation to TNS
Add bus and feeder to TNS
Add IPU mapping to TNS
Add receiver to TNS
Add OMU to TNS
Assign OMU to bus
Set up TNS to SCE
communications
Adding Substations Process Flow Detail
When adding substations to TNS, documentation and communication
between the Substation & Transmission (S&T) Engineer and the TNS
Operator are critical for a successful configuration of the system. After the
S&T Engineer installs the hardware configuration, the documented
configuration must pass to the TNS Operator. The tables, Substation
Outbound Configuration Worksheet, and Substation IPU Map and
Communication Server Worksheet, found on the following pages, provide a
sample document format the utility can use for the information handoff to the
TNS Operator. Once the S&T Engineer documents the SCE, the TNS
Operator can easily configure TNS to accurately reflect the appropriate
configuration by adding the substation, bus, feeder, IPU mapping, OMU
parameters, and receivers to the TNS configuration database.
67
Adding Substations
68
69
Adding Substations
Drop IDs and Substation IDs
The TWACS system uses the Drop ID and Substation ID to
uniquely identify substations. The utility configures the drop ID
on the substation hardware by changing the panel dials on the
faceplate of the SCPA card in each CRU. TNS uses the Drop ID
as a common link to the SCPA card.
ID
Defined
in TNS
Defined in
SCE
SCE Reference
Drop ID
Substation ID
Yes
Yes
Yes
No
SCPA front panel dials
Not applicable
The utility uses the substation ID with the drop ID to guarantee a
substation's uniqueness in SCE identification across the utility’s TWACS
network.
Facts About Drop IDs and Substation IDs
The following list will help you better understand the difference between
the Drop ID and the Substation ID.
• Drop IDs are configured in both the SCPA hardware and TNS.
• The substation does not know its Substation ID.
• The Drop ID in TNS must match the SCPA dial pad.
• The SCPA dial pad Drop ID is in hexadecimal.
• The TNS Drop ID is in decimal, and the TNS Operator must convert
the dial pad hex number to decimal for TNS entry.
• If the Drop ID does not match the dial pad, the substation will not
communicate with TNS.
• The Drop ID can be from 1 to 254 (hex 01-FE), but TNS does not
verify the Drop ID field is within the valid range.
• The Drop ID must be unique within each Communication Server.
• The TNS Operator can assign the same Drop ID used to identify a
substation on one Communication Server to a substation residing on
another Communication Server provided the Substation ID is
different on the two substations.
• The Substation ID can be from 1 to 999.
70
• The TNS Operator can change the Substation ID to whatever the TNS
Operator desires without impacting communications with the
substation.
• If possible, the utility should keep the Drop ID and the Substation ID
the same.
Adding Substations
The TWACS system components in the substation have a hierarchical
relationship both in TNS and in actual operation. The TNS Operator must
enter the SCE components in a particular order to maintain the hierarchical
structure. The first component the TNS Operator enters is the substation.
1.
Open the TNS SCE Maintenance tool bar by following the menu path
Start > Programs > TNS SCE Maintenance > TNS SCE
Maintenance.
2.
Enter your login information, and click the OK button
3.
From the SCE Maintenance tool bar, click the
SCE Maintenance
with Command View button to open the SCE Maintenance with
Command View window.
71
Adding Substations
From the SCE Maintenance with Command View window, you can
view:
•
All substations in the utility’s system
•
The state and status of each substation
•
The total commands and searches out and waiting
•
The total command slots and searches open
Refer to Chapter 1, SCE Maintenance in the TNS End User Guide
Rev D for more information about the SCE Maintenance
applications.
NOTE
The command information is only visible by using the scroll bar at the
bottom of the Substation List section.
4.
Add a new substation entry by clicking the Insert
5.
Define the Substation’s ID, Name, and Model.
button.
The Substation ID field uniquely identifies the substation for the
entire TWACS system deployment of the utility company. The
Substation ID field may be any number between 1 and 999. The
Name field must also be unique for the entire TWACS system
deployment of the utility company. The Model field identifies the
model of the CRU at the substation and this is typically AS93 for
newer CRUs.
NOTE
DCSI recommends the Substation ID match the Drop ID when possible.
6.
72
Click the Save button to save the substation entry.
Adding Buses
After setting up the initial substation entry, the TNS Operator must next
configure TNS to accurately reflect the buses at the substation.
The initial entry for the substation displays in the SCE Maintenance with
Command View window. The next step is to select the entry and add the bus
information.
1.
Double-click the substation entry in the Substation List.
The TNS Operator uses this window to install Bus, Feeder, and IPU
information.
73
Adding Substations
2.
Click the Insert
button to the right of the Bus Information
section of the screen to add a new bus.
The Bus Settings screen appears.
3.
Enter the Bus ID and the Name of the bus in the fields.
The Bus ID field may be any number between 1 and 254 and is
unique to the substation. DCSI recommends the TNS Operator start
numbering buses in the substation at 1 and increment for each bus in
the substation. The Name field may be up to eight characters and
must be unique for the substation. The Name field may be any
name that uniquely identifies the bus in the substation.
4.
Click the OK button to save the Bus entry.
Repeat the steps for adding a bus for each bus in the substation.
The Bus update is complete.
74
Adding Feeders
After setting up the initial substation entry and buses, the TNS Operator must
next configure TNS to accurately reflect the feeders at the substation.
1.
Click the Insert
button to the right of the Feeder Information
section of the screen.
The Feeder Settings screen appears.
NOTE
If you have more than one bus, you must first select the bus in the Bus
Information portion of the screen, and then add feeders to the selected
bus. Since Bus 1 is selected, TNS will add the feeder to Bus 1.
The Feeder ID field may be any number between 1 and 254 and is
unique to the Bus. DCSI recommends the TNS Operator start
numbering feeders on the bus substation at 1 and increment for each
feeder on the bus. The Name field may be up to 12 characters and
must be unique for the bus. The Name field may be any name that
uniquely identifies the feeder on the bus.
75
Adding Substations
NOTE
Utility feeders may already have names or IDs assigned by the utility.
These may be used.
2.
Enter the information in the Feeder Settings screen.
3.
Click the OK button to save each Feeder entry.
The Feeder Detail Information screen appears.
Leave most of the fields at the default setting unless requested by
DCSI to alter the default settings. You may need to alter the
inbound scalars field under certain circumstances.
76
Understanding Inbound Scalars
NOTE
The Inbound Scalars field may be modified if the utility uses
feeder-level IPUs and the CT ratios differ. If the utility uses bus-level
IPUs, leave the Inbound Scalars field parameters at the default setting.
In some substations, the substation current transformers (CTs) for the feeders
are set at different CT ratios. The higher the amperage level on the feeder, the
weaker the signal to the IPU that picks up the inbound meter information for
the TWACS system. The Inbound Scalars field allows the utility to
compensate for varying levels of inbound signal strengths from different
feeders. This compensation is accomplished by setting a ratio to apply to the
signal input on the feeder for the IPU. This ratio is calculated using the CT
ratio ranges. The Inbound Scalar ratio is used to reduce the signal strengths
for feeders to an equal level so crosstalk from one feeder to another does not
appear to be a signal on the wrong feeder. The follow table displays sample
current transformer (CT) ratio settings for three feeders on a bus.
Feeder Name
Substation CT Ratio
Feeder1
Feeder2
Feeder3
200/5
400/5
1200/5
The utility places Substation CTs for various functions, such as SCADA
inputs or metering of overall electrical use, on a feeder or bus. The utility uses
a CT to connect the TWACS IPUs to a bus or feeder to detect inbound
signals. The Substation CT calculation used for Inbound Scalar references the
CT ratio settings for the CT connecting the TWACS IPUs.
77
Adding Substations
Calculating the Inbound Scalar
The method for calculating the Inbound Scalars field for the feeder data
defined in the previous table follows:
1.
2.
Determine the feeder with the highest CT ratio on the bus. In the
example in the previous table Feeder 3 has the highest CT ratio at
1200/5.
Feeder Name
Substation CT Ratio
Feeder1
Feeder2
Feeder3
200/5
400/5
1200/5
For each feeder, divide that feeder’s CT ratio by the highest CT
ratio.
Feeder
Name
Existing Substation CT Amp
Setting Divided by Highest CT
Amp Setting
Inbound
Scalar
Feeder1
Feeder2
Feeder3
200/5 divided by 1200/5
400/5 divided by 1200/5
1200/5 divided by 1200/5
=.167
=.333
=1
Based on the example provided, the TNS Operator would set both
the Neutral and Phase parameters of the Inbound Scalars field
to.167 for Feeder1. Similarly, the TNS Operator would set the
Feeder2 and Feeder3 Inbound Scalar fields to their appropriate
settings.
Feeder Name
Feeder1
Feeder2
Feeder3
78
Inbound Scalar
Neutral
.167
.333
1
Phase
.167
.333
1
3.
Populate the required information and click the Apply Updates and
Return
the changes.
button on the Feeder Detail Information window to save
The Substation Edit window reappears.
Notice that three feeders are entered with the appropriate information.
4.
Perform an incremental save by clicking the Save Updates and
button. This button performs a save operation on the
Continue
substation record without leaving the Substation Edit window.
5.
Repeat the steps for adding feeders for each feeder on each bus.
The Feeder update is complete.
79
Adding Substations
Adding IPU Mappings
After setting up the initial substation entry, buses, and feeders, the TNS
Operator must next configure TNS to accurately reflect the IPU Map
Settings at the substation.
IPU map configurations vary depending on several factors including:
Configuration issue
How many IPU Maps?
Are bus-level IPUs used
Are feeder-level IPUs used
one IPU per bus
one IPU per feeder
Before adding an IPU map configuration, you must first select the
appropriate bus and feeder to which the S&T Engineer attached the IPU.
Notice in the example above, Bus1 and Feeder1 are both selected.
1.
Add a new IPU by clicking the Insert
IPU Information section of the screen.
button to the right of the
The IPU Map Settings screen appears.
80
NOTE
Refer to Understanding Substation Communications and Architecture on
page 48 for more complete information about determining the IPU Map
Settings for the substation installation.
The TNS Operator may select from four detection points for each IPU
representing the three phases (A, B, and C) and neutral. Each detection
point represents a physical connection on the IPU. Normally, the TNS
Operator will enter all four detection points for an IPU.
The IMA/CRMA field refers to the CRMA card to which the IPU
attaches.
NOTE
The CRMA card backplane connection is labeled 1 through 4. In TNS, the
IMA/CRMA field options are 0 through 3. The TNS Operator must
subtract one from the CRMA physical port location number for accurate
entry of the IMA/CRMA field in TNS.
The ISA/MUX field refers to the mux port on the CRMA, and the
channel field refers to the channel defined for the input.
2.
Click the OK button to save the IPU Map Setting.
3.
Add an IPU Map Setting for all four detection points. Once the TNS
Operator enters all four detection points for the feeder, the substation
edit window should look like the example above, showing the
configuration with all four detection points added for Bus1-Feeder1.
4.
Repeat the steps for adding IPU maps for each feeder on each bus.
81
Adding Substations
Adding Receivers
After setting up the initial substation entry, buses, feeders, and IPU
Information, the TNS Operator must then configure TNS to accurately
reflect the receivers or CRPA cards at the substation.
1.
View the screen where the TNS Operator inserts receivers by
selecting the Receiver and OMU Parameters radio button.
The Substation Edit screen will change to display the Receiver
Parameters and OMU Parameter sections.
The above example shows the window used to enter receivers
(CRPAs) and OMUs.
82
2.
NOTE
Click the Insert
button to the right of the Receiver Parameters
section of the screen. The RPA Settings screen appears.
DCSI uses the terms CRPA, RPA, and receiver synonymously.
3.
Populate the RPA ID and Synch State fields.
The CRU can have up to three CRPA cards. The TNS Operator must
create an entry for each physical CRPA card in the TNS database. The
CRPA ID field in TNS must be 1 through 3 numbered in sequence. At
the substation, the CRPA cards number 0 through 2 and must be
positionally placed in the appropriate slot in the CRU chassis.
NOTE
There is a fourth CRPA card slot that is typically unused.
NOTE
TNS allows you to enter any single digit number in the CRPA ID field.
There is no incorrect station reported at time of entry, but
mis-numbering the CRPA ID field will cause errors in other processes.
The Receiver Parameters Sync State field identifies the number of ½
cycles the receiver should wait, after the OMU sends a command,
before looking for inbound traffic. The Sync State field should
always be set to 6, unless otherwise directed by DCSI to change the
entry.
Receiver ID
Sync State
1
2
3
6
6
6
83
Adding Substations
4.
Click the OK button to add the first receiver.
After the TNS Operator adds the first receiver, notice TNS disables
button. To add additional receivers the
(grays out) the Insert
TNS Operator must configure TNS for concurrent phasing.
5.
To configure concurrent phasing, click the Configuration Key
Information
button on the Substation Edit window.
The Configuration Key Maintenance screen appears.
REMEMBER
84
The speed of meter reads desired by the utility impacts the number of
CRPA/CRMA cards or receiver sets. The substation may have one, two,
or three receiver sets depending on the meter read speed desired.
CRPA/CRMA Cards
(Receiver Sets)
Mode
Speed of Meter Reads
1
2
3
Concurrent phasing
Concurrent phasing
1x
2x
3x
To enable concurrent phasing, the TNS Operator must check the
following options:
NOTE
•
Concurrent Phase Comm.
•
IPU Input Shadowing
•
Supports Multiple RPAs
Notice the sample TNS screen has the Concurrent Phase Comm. field
and the IPU Input Shadowing field grayed out. If this situation exists,
the TNS Operator must correct this problem in the DCSI Maintenance
application as described in Appendix A, Concurrent Phasing in the TNS
End User Guide Rev D.
6.
If necessary, follow the steps to enable the concurrent phase selector
options.
85
Adding Substations
7.
Once the concurrent phase selector options are selected, close the
Configuration Key Maintenance window and reopen it by clicking
the Configuration Key Information
edit window.
button on the substation
The Configuration Key Maintenance window reappears.
REMEMBER
To enable the options on the screen, you may need to follow the
procedures in Appendix A, Concurrent Phasing in the TNS End User
Guide Rev D.
Notice the Concurrent Phase Comm., IPU Input Shadowing,
and Supports Multiple RPAs fields are no longer grayed out.
8.
86
Select the fields Concurrent Phase Comm., IPU Input
Shadowing, and Supports Multiple RPAs so a check appears
before each option.
9.
Click the Save
button to save the changes.
Notice the Insert
10.
button is no longer grayed out.
Click the Insert button to add the additional receivers.
Once the second and third receivers are added, the screen should look
like the example above.
87
Adding Substations
Adding OMU Parameters
After setting up the initial substation entry, buses, feeders, IPU Map
Settings, and Receivers, the TNS Operator must then configure TNS to
accurately reflect the OMUs at the substation.
REMEMBER
There is a condition in which a utility may place two OMU/MTU pairs on
a bus. DCSI calls placing a dual pair of OMU/MTUs on a single bus
parallel OMU configuration. This condition occurs when a transformer
has an open air (OA) rating of 30MVA or higher. In this case, the utility
will place two OMU/MTU pairs on the bus and the OMU/MTU pairs will
fire simultaneously. By firing simultaneously, there is a better chance
to overcome noise on the bus and successfully communicate with the
meter.
In the following sample configuration, the TNS Operator will configure the
following OMUs for the Lancaster substation.
Sub
OMU
OFIA Port
Bus
Transformer OA Rating
Lancaster
Lancaster
Lancaster
1
2
3
1
2
3
Bus1
Bus2
Bus2
20MVA
45MVA
45MVA
Bus1 has a single OMU. Bus2 has a number of industrial customers, and
the load on Bus2 is high enough (greater than 30MVA) to justify using a
parallel OMU configuration.
The example above shows the window used to enter OMUs.
88
1.
Add a new OMU by clicking the Insert
OMU Parameters section of the screen.
button to the right of the
The OMU Parameter Settings screen appears.
2.
Enter the OMU ID and firing angles.
Each OMU must have an OMU ID unique to the substation. The OMU
ID is defined in TNS and must correspond to the OMU’s connection
position on the OFIA cards. The OMU ID field may be 1 through 12.
REMEMBER
A maximum of three OFIA cards may exist and each OFIA card has four
inputs for attaching OMUs. A maximum of 12 OMUs may exist at a
substation. Valid numbers for the OMU ID field in TNS are 1 through 12.
Each OMU has a definition for firing angle on the entries for each line
to ground and line to line combination. The OMU Firing Angles
fields define how many degrees before the zero crossing the OMU
should fire commands. Valid parameters for the Firing Angles fields
are between 15 and 30 degrees. The higher the degree, the more power
generated to the transponder. The default firing angle may vary
depending on the version of TNS. Set the firing angles to 22 degrees.
The TNS Operator should only adjust this parameter when
interference exists on the line. Industrial customers on the bus might
be a source for interference on the bus, and by increasing the firing
angle and subsequently the firing power, the utility stands a better
chance of getting the commands to the transponder. A higher setting is
harder on the OMU; therefore the TNS Operator will want to increase
the amount only as needed.
NOTE
The TNS Operator can get an indication of the power level required by
looking at the outbound signal indicator in the Test Communication Tool.
Refer to Chapter 9, Test Communication Tool in the TNS End User Guide
Rev D.
89
Adding Substations
Notice when the TNS Operator changes the Firing Angles field to
22 for phase A, it changes the Firing Angles field for all other
phases automatically.
3.
After adding the OMU ID and changing the default for the Firing
Angles field, click the OK button to save the changes.
The Substation Edit window appears.
Once the TNS Operator adds the OMUs, the TNS Operator must
assign each OMU to its associated bus.
4.
Click the Bus Information radio button to return to the Bus
Information screen.
The Bus Information appears on the Substation Edit window.
90
5.
Assign an OMU to a bus by selecting the bus to which the OMU
button to the right of
should be assigned, then clicking the Insert
the OMU Map Information portion of the window.
The OMU Mapping screen appears.
NOTE
6.
Click the ID drop-down box to view the OMUs previously added to
TNS. Select the OMU assigned to the bus from the list.
7.
Click the OK button to select the OMU.
8.
Click the OK button on the OMU Mapping window to complete the
assignment.
The configuration calls for two OMUs assigned to Bus2. Select Bus2 and
add both OMUs by performing the assignment procedure twice on Bus2.
The example above displays the way the window should look with a
standard OMU configuration.
91
Adding Substations
The following example displays the way the window should look
with a parallel OMU configuration.
9.
Click the Save Updates and Exit
button to complete the
substation edit process. The SCE Maintenance with Command
View window will appear.
The substation update for Lancaster is complete except for the
communications link. TNS cannot communicate with the substation until
the TNS Operator configures the communications link to the substation.
Proceed to the next section for information on configuring the
communications link.
92
Adding Substation Communications Links to TNS
After installing the TWACS system substation equipment and the
communications facilities to link TNS to the substation, the utility must
configure TNS to connect to the communication equipment at the substation.
The SCE Maintenance applications allow the utility to define the substation
components in TNS, including the communication link configuration. See
Chapter 1, SCE Maintenance in the TNS End User Guide Rev D for more
information about the SCE Maintenance applications.
Communications Link Overview
When a utility installs a substation, the utility also installs a communication
facility to link TNS to the substation for communication purposes.
Process Flow Detail
When adding substation
communication links to TNS,
Adding Communication
documentation and
Links Process Flow
communication between the S&T
Engineer and the TNS Operator
are critical to successful
Order, install, and configure the
configuration of the system. After
substation communications link
installation of the substation
hardware, the S&T Engineer will
configure and connect a
communications link to the CRU.
The S&T Engineer must pass
configuration information for the
communications link to the TNS
Operator. The Substation IPU
Map and Communication Server
worksheets in Adding Substations
Add communications link to TNS
Process Flow Detail on page 67
provide sample document formats
Bring substation online
the utility can use for the
information handoff of the entire
substation. The sample worksheets also include information on tracking the
communications link. Once the S&T Engineer documents the SCE and
communications link, the TNS Operator can easily configure TNS to
accurately reflect the appropriate configuration by adding the
communications parameters to the TNS configuration database. Once the
TNS Operator successfully installs and configures the communications link
in TNS, the TNS Operator may connect to the substation over the
communications link and bring the substation on line.
93
Dedicated versus Dialup Connections
TNS defines two types of connections to a substation - dialup and
dedicated. Dialup connections are ones in which the TNS operator defines
a telephone number to be dialed through a modem dial command.
Dedicated connections include all other types of connections. Dedicated
connections can be:
• Analog private lines or Digital Data Services (DDS) circuits from a
telephone carrier used exclusively for the TWACS system.
• Existing Wide Area Network (WAN) connections (using carrier
services used to connect the substation or remote offices near the
substation to the utility network such as:
•
Private line
•
Frame Relay
•
ATM
• Internet VPN from an ISP
• Private radio connections
REMEMBER
Dialup connections take about 30 seconds to connect before
communications can flow across the link. Depending on the utility’s
plan for TWACS system usage, dedicated communications may be
required.
Setting Up the Communications Link in TNS
The TNS Operator must define the communications link to a substation in
each substation record. The key items needed for defining the
communications link include:
• Drop ID
• Dedicated or dialup communications designation
• Communication Server port servicing the substation
• Phone number of substation modem if dialup is used
94
Complete the following steps to define the communications link.
1.
Open the TNS SCE Maintenance tool bar selecting Start > Programs
> TNS SCE Maintenance > TNS SCE Maintenance.
2.
Click the
SCE Maintenance with Command View button to open
the SCE Maintenance with Command View window.
3.
Open a substation by clicking on any field on the substation line. The
Substation Edit window appears.
95
4.
Click the Drill Down
Information screen.
button to open the Substation Detail
5.
Populate the Drop ID field. In the example, the Drop
ID is 4, the same as the Substation ID. The Drop ID
must match the Drop ID on the SCPA card dials.
6.
Populate the time synchronization information.
Time Synchronization is an important element of TNS. Having
meters with accurate time is important to many aspects of the
TWACS system, including hourly and daily shift reads. To ensure
the meters have accurate time, TNS performs a time
synchronization with the meter at specified intervals. This interval
is determined by the Time Synchronization portion of the
Substation Detail Information window. The Interval field denotes
the interval for time synchronization in minutes. The Interval must
evenly divide into 60 minutes. The recommended Interval value is
15 minutes. The Delay defines how many minutes after the interval
starts to wait for transmission of the time synchronization. The
recommended Delay value is 5. The Window field defines the
number of minutes the substation has to complete the time
synchronization. The recommended value for the Window field is 5
minutes. The All T10 field tells TNS that all of the substations are
TWACS-10 compatible, and this field should normally be checked.
96
Time synchronization is
done through a broadcast
on all phase
combinations for each
bus. If time
synchronization fails,
TNS will place an error
in the Notification log.
Interval
Delay
Window
15
5
5
7.
Click the Communications Configuration Name drill-down box to
select the communications port to use for connecting to the substation.
The Communications Information list may contain dialup ports as well
as direct-connected ports. The first Comm Port Name is used for this
example.
The example details configuration of a simple dialup configuration.
97
8.
Click the Phone Line Information
button. The Substation
Detail Information screen expands to display the Dial Up Line
Information section of the window.
9.
Enter the telephone number of the substation modem in the Sub
Dial Up Phone Number field. Enter the number as if dialed from a
telephone at the TNS location.
The Connect Retention Time and Connect Redial Time fields
define how long to stay connected and how often between redials
when active commands exist in the queue for a substation. The TNS
Operator may adjust these fields as needed.
10.
Click the Apply Updates and Return
button to save the
changes and return to the Substation Edit window.
The Substation Edit window appears.
98
11.
Click the Apply Updates and Return
button on the Substation
Edit window to save the dialup changes permanently and return to the
SCE Maintenance with Command View window.
12.
Bring the substation online by clicking Commands > Standard >
Bring Substation Online.
13.
Verify the substation is online. If the screen does not refresh quickly
enough, you can click the box labeled ID to initiate an immediate
refresh.
99
When the substation is on line, the Sub State field displays Disconnected
and the Sub Status field displays Configured. The following table
provides a list of substation states and status values.
Sub State
Description
Disconnected
Connected
Waiting for
modem
Dialing
Hanging up
TNS is currently not communicating with the SCE.
TNS is currently communicating with the SCE.
TNS is waiting for an open line to dial the SCE.
TNS has a modem and is currently dialing the SCE.
TNS is disconnecting a dial connection.
Sub Status
Description
Offline
The SCE is currently offline and commands cannot be
issued before it is brought online by downloading
tables
TNS is currently communicatin.g with and sending
commands to the SCE.
The SCE is in the process of being brought on line.
The SCE tables are downloading.
The SCE is ready to receive commands. Tables are
downloaded. This status is most often seen when the
SCE is a connected via dialup.
The SCE is ready to receive commands. Tables are
downloaded. This status occurs when the
CommServer has tried to communicate with the
substation and failed.
Online
Downloading
tables
Configured
Slowpoll
NOTE
For dialup substations, having a substation on line does not necessarily
mean TNS is physically dialed and connected to the substation. Online
means that TNS will dial the substation if any commands are initiated
for the substation.
The substation link addition is complete.
100
CHAPTER
3
SEARCHING METERS
The utility must make several decisions about what it wants to gain from
using the TWACS system. These decisions impact the type and configuration
of meters ordered. Once the meters are ordered and received, the utility will
configure and install the meters. The meters must then be entered into the
TNS database by serial number. An automated process exists to ease entering
meters into the database. This process is known as searching meters.
This chapter addresses processes dealing with receipt of meters at the utility
through searching meters into the TNS database.
101
Receiving Meters at the Utility - Preliminary Search Activities
Receiving Meters at the Utility Preliminary Search Activities
For every customer requiring Automatic Meter Reading (AMR), the utility
will order TWACS-enabled meters. Once the utility receives the
TWACS-enabled meters, the utility must then install the meters on the
customer premises. Before installation, the utility must complete several
preliminary steps.
When a utility orders a batch of TWACS-enabled meters, the utility must
update TNS in preparation for the meter installation. The Product table,
SubProduct table, and Product Type Model Cross Reference table may all
need to be updated prior to entering meters into the meter databases. This
section covers the initial steps the utility must do to prepare TNS for the
meter installation. See Chapter 2, System Administration in the TNS End
User Guide Rev D for more information on the tables discussed in this
chapter.
Verifying Product Table Information
The Product table defines how TNS interacts with various meter types and
models. Although DCSI personnel populate the Product table with
information the utility is likely to need, the utility may need to add some
meter types and models to the Product table list.
NOTE
TNS cannot enter a meter into the Meter database with a given type or
model unless that type and model is in the Product table.
Understanding Meter Types and Model Numbers
When a utility purchases a meter or transponder, there are several options
the utility can configure. Most meters are programmable meters.
Programmable meters allow the utility to change the meter configuration.
Varying meter options changes the way TNS must interact with the meter
and interpret the meter’s information. TNS tracks the various options of a
meter through the designation of a type and model number associated with
the meter's particular configuration.
TWACS System Type and Model Example
The type of meter generally identifies the family of meter. For example, the
IMT3H is either a Type 21 (non-programmable Kh) or Type 31 or 38
(programmable Kh). The following is a list of configuration, or purchase
options, that can change the model number for the IMT-3H transponder.
• Location of use (US or Canada)
• Ports (1 or 3)
• Service disconnect/connect feature enabled (model specific)
102
Chapter 3 • Searching Meters
• Total consumption metering
• Demand metering
• Daily/hourly/interval consumption
• Integrated load survey
• Meter constant (Watt-hour per disk revolution)
• Voltage
For details about types, models, and features, refer to the product
documentation for the relevant transponder.
Deciding Which Meter Features to Use
By varying the options, there are
hundreds of combinations possible for
type and model based on the features
and configurations desired by the
utility.
Due to the vast number of options
available for meter configurations,
utilities must carefully consider which
features to utilize in their TWACS
system deployment. Careful planning
prior to meter deployment can save the
utility time and effort due to
reconfiguration changes to meet new
requirements.
103
Changing Deployed Meter Type and Model Configurations
As with most projects, better
planning leads to easier
deployments. The process for
changing a meter’s type and
model, once deployed to the
field, is more extensive than the
original installation.
For meters previously deployed
to the field, the utility will likely
opt to swap out old meters with
newly configured meters. The
utility must add the new meter
to TNS. The utility then
reconfigures and redeploys the
old meter, leading to a number
of process steps and table
updates in TNS.
Meter Type Model
Change Flow
Utility decides to change features
on programmable meters already
deployed at customer sites
Meter tech pulls old TWACS
meter and replaces it with meter
configured for new features
TNS Operator updates customer
record with new serial/type/model
numbers
Meter tech ships old TWACS
meter back to meter shop for
reprogramming
Delete TNS entry from meter
database
Update Product Type Model
Cross Reference Table with new
type/model for serial number
Re-install old meter on different
customer premise
Search in new meter interactively
or in batch mode
Verifying and Adding Product Table Information
The Product table tracks the various types and models of meters TNS will
use. DCSI personnel populate the Product table with known meter types
and models at TNS installation. At times, it may be necessary to add new
or uncommonly used meters to the Product table. (See Chapter 2, System
Administration, Product Table in the TNS End User Guide Rev D for more
information about the Product table.)
NOTE
104
TNS cannot add a meter to the Meter database unless the type and
model of the meter is in the Product table.
Utility employees should contact DCSI support personnel for information
relating to the type and model numbers not present in the TNS Product table.
You can open the Product table from the TNS System Administration tool bar
(Start > Programs > TNS System Administration).
Click the Product
button to open the Product table.
button
To view all of the items in the Product table, click the Query
twice and all of the elements in the table will display in numerical order
sorted by type and model. Manually search the table by clicking the vertical
scroll bar on the left side of the screen until the table shows the type and
model desired.
To quickly find a specific item in the Product table, click the Query button
once, enter the search criteria (in this example, Type = 21, Model = 11) and
then click the Query button a second time to see the results. If the table
contains the type and model searched, it will show just that type and model in
the list. If the entry is not in the table, the table display is empty.
Similarly, the query will search all entries of one type if the you enter a Type
with the Model number blank on a query. You can also enter greater than
( > ) or less than ( < ) symbols before the type or model number to find ranges
of types and models.
Notice in this example, the selected meter type and model has three ports
(designated by the Prod Port field).
105
When a meter type/model has more than one port, the ProductPort portion
of the screen lists details about the ports on the meter (gas, water, and
electric).
To find a list of entries using a wildcard (e.g. beginning with ALT), TNS
clears the table when you press the Query button once. Enter “ALT%” in
the Name field to have TNS find all records that start with ALT.
Press the Query button a second time for TNS to display the table view.
106
The Command Delay 1 and Command Delay 2 fields are important
options in the records of the Product table. If the utility uses feeder-level
detection, the Command Delay 1 and Command Delay 2 fields must
both be set to 5 for each meter type and model.
Click the Add
NOTE
button to add a new type and model to the Product table.
Contact DCSI Customer Care for information relating to your meter type
and model number. Insert the information DCSI provides for the type and
model in the Product table record entry.
Enter the appropriate information, then click the Save button to save the new
entry.
107
Verifying SubProduct Table Information
The SubProduct table defines how a particular substation type
communicates with a meter type and model. Through the years, DCSI has
created different types of Substation Communications Equipment (SCE),
with different capabilities.
The SubProduct table allows the utility to specify capabilities for a specific
meter based on the capabilities of a substation type in TNS.
See Chapter 2, System Administration, SubProduct Table in the TNS End
User Guide Rev D for more information about the SubProduct table.
Verifying Information in the SubProduct Table
The TNS SubProduct table tracks the various types and models of meters
TNS will use in relation to the substation types to which the meter types
and models attach. DCSI personnel populate the SubProduct table with
known meter types and models during the TNS installation. At times, it
may be necessary to add new or uncommonly used meters to the
SubProduct table.
NOTE
TNS cannot add a meter to the Meter database unless the type and
model of the meter is in the SubProduct table for the substation type
used.
Utility employees should contact DCSI Customer Care for information
relating to the type and model numbers not present in the TNS SubProduct
table.
You can open the SubProduct table from the TNS System Administration
tool bar (Start > Programs > TNS System Administration).
108
Click the SubProduct
NOTE
button to open the SubProduct table.
While at first glance it may appear TNS orders the table by Sub Model,
this is not the case. You will likely need to query the database with a
specific type and model number.
To view all of the items in the SubProduct table, click the Query
button
twice and all of the elements in the table will display in numerical order
sorted by type and model. Manually search the table by clicking the vertical
scroll bar on the left side of the screen until the table shows the type and
model desired.
To quickly find a specific item in the SubProduct table, click the Query
button once, enter the search criteria (in this example, Prod Type = 21, Prod
Model = 11) and then click the Query button a second time to see the results.
If the table contains the type and model searched, it will show just that type
and model in the list. If the entry is not in the table, the table display is empty.
Similarly, the query will search all entries of one type if the you enter a Type
with the Model number blank on a query. You can also enter greater than
( > ) or less than ( < ) symbols before the type or model number to find ranges
of types and models.
109
Click the Add
button to add a new type and model to the SubProduct
table. (Review Search Mode and Search Type on page 110 before adding
an entry.)
NOTE
Contact DCSI Customer Care for information relating to your meter
type and model number. Insert the information DCSI provides for the
type and model in the SubProduct table record entry.
Enter the appropriate information, then click the Save button to save the
new entry.
Search Mode and Search Type
The Search Mode and Search Type fields are important options in the
records of the SubProduct table.
After the meter technician physically installs a meter, the utility must enter
the meter into the Meter database. TNS can automatically find new meters
using the TNS search in process.
110
There are several valid values for the Search Mode and Search Type
fields. Varying these fields changes the way TNS searches meters into the
database. Valid values include:
Search
Mode
Search Type
Value Description
0
1
4
Logical Elimination
Amplitude Summation
Advanced Search
0
0
1
In general the utility will use two Search Mode and Search Type options. For
all new meters, the utility may use any search method. Older meters including
the LCT, MIT, IMT1, and IMT2 do not support Advanced Search, and the
utility must use Logical Elimination or Amplitude Summation.
Search Search
Mode
Type
Value Description
0
1
4
Logical Elimination
Medium LCT, MIT, IMT1, IMT2
Amplitude Summation Slow
No longer used
Advanced Search
Fastest All other meters
0
0
1
Speed
Recommended for
Which Meters?
Logical Elimination
The substation equipment searches paths in an optimized manner to identify
the correct path with the fewest number of transactions. The substation
equipment uses the pass/fail of the Cyclic Redundancy Check (CRC) and the
analysis of the signal strength to determine the best path.
Amplitude Summation
The substation equipment performs communications on all paths for a feeder.
The substation equipment sums and analyzes the signal strengths to choose
the best path.
Advanced Search
The substation equipment commands the meters to respond with a specific
pattern. The substation equipment then scans each detection point of each
feeder and compares the result. The substation performs path verification on
the feeder with the strongest inbound signal strength to confirm the location
of the meter.
111
Updating the Product Type Model Cross Reference Table
The Product Type Model Cross Reference table defines the serial numbers
of the meters used and the associated type and model numbers for those
meters with listed serial numbers.
The Product Type Model Cross Reference table allows the utility to specify
serial numbers of new meters purchased in preparation for searching the
new meters into the meter database.
See Chapter 2, System Administration, Product Type Model Cross
Reference Table in the TNS End User Guide Rev D for more information
about the SubProduct table.
NOTE
TNS cannot enter a meter into the Meter database unless the meter’s
serial number is in the Product Type Model Cross Reference table.
Overview of the Product Type Model Cross Reference Table
The TNS Product Type Model Cross Reference table tracks the serial
numbers of the meters the utility installs. TNS uses this table to search
meters into the Meter database.
NOTE
TNS cannot add a meter to the meter database unless the serial
number for the meter is in the Product Type Model Cross Reference
table.
When a utility receives a shipment of meters (or transponders), the packing
list details the serial number range of the meters shipped.
Serial Number or Meter Number?
Every meter has a meter number assigned by the meter manufacturer. The
transponder manufactured by DCSI has a serial number assigned by DCSI.
The DCSI assigned serial number is the number TNS associates with the
meter in the Product Type Model Cross Reference table.
Meter Type and Model Number
Meters ordered from DCSI are ordered with a specific configuration. As
mentioned earlier in this chapter, in Understanding Meter Types and Model
Numbers on page 102, meter model numbers can change when the meter is
reprogrammed. When the meter shop receives a batch of meters, meter
technicians may reprogram the meters to have desired functions, thus
changing the model number of the meter. The exact model type and model
number assigned to a meter may not always be clear to the TNS Operator.
The TNS Operator can assume a best guess for the meter type and model
number, but a wrong guess may create additional work later in the search in
process.
112
If the TNS Operator enters the same Type family of meter into the Product
Type Model Cross Reference table as the meter itself, TNS will correct the
type model mismatch during the search process. The following table defines
meter types commonly used.
Type
Product Table Name
21
31
36
37
38
39
40
45
IMT 3H - 7.2Kh - non-programmable
IMT-3-3H - programmable
CENTRON
CMT-SX
IMT 3H - programmable
CMT-Vectron
DCSI Service Disconnect/Connect Switch
Altimus
Adding Serial Numbers to the Product Type Model Cross
Reference Table
The packing list for a
new shipment of
meters shows the
serial number list, or
range, for the meters
or transponders
shipped. Save this
information to add to
the Product Type
Model Cross
Reference table.
In addition to the
range of serial
numbers, it is helpful
to have the type and
model number of the
meter serial numbers
received.
113
You can add serial numbers to the Product Type Model Cross Reference
table using the System Administration tool bar.
Click the Product Type Model Cross Reference
Product Type Model Cross Reference table.
button to open the
When a batch of transponders or meters ships to the utility, the utility
typically receives a range of serial numbers detailed on the packing list.
You can add the new range by clicking the Add
button.
The last row in the table is highlighted and will allow entry.
Enter the serial number range in the SerialNo Start and SerialNo Stop
fields. In the example, the serial number range 6135750 was changed to
6135759.
114
Since the type and model may change if the meter shop configures the meter,
enter a best guess for type and model numbers in Type and Model fields. If
the TNS Operator enters the proper family of meters, the search will complete
successfully, and the meter will notify TNS of the exact type and model. TNS
will then enter the correct meter type and model into the permanent database.
If you are unsure about what type and model to enter, contact DCSI Customer
Care.
The DrawingNo Ref and Comments fields are user definable. DCSI
recommends putting the meter name in the DrawingNo Ref field and
possibly date information in the Comments field.
NOTE
The TNS Operator may not enter serial number ranges that overlap with
an existing record in the Product Type Model Cross Reference table (X-Ref
table). TNS will notify the user of any overlap with an error message. The
TNS Operator must first delete the record causing the overlap to enter
new values. TNS only uses the X-Ref table for the search process. Once a
meter searches into the database, TNS no longer needs the records in the
X-Ref table.
You can save the edits by clicking the Save
button.
Searching Meters into TNS
When a utility purchases meters, utility personnel will configure, document,
and install the new meters at customer locations. Once installed, the TNS
Operator must search the meters into TNS.
DCSI refers to the process of automatically finding meters and inserting them
into the Meter database as searching in meters.
Searching Overview
After the utility installs meters, the TNS Operator must enter new meters into
the TNS database.
The search in process allows the utility to find meters on a TWACS network
without knowing the meter’s exact location or configuration.
Search In Process Overview
When a utility purchases and installs meters, the meter configuration in TNS
must match the physical characteristics of the TWACS substation
components. In Receiving Meters at the Utility - Preliminary Search
Activities on page 102 the preliminary updates made to TNS to prepare for
meter installation was explained. In this section, the process for entering
meters in TNS after the meter technician installs the meter, is explained.
115
Process Flow Detail
When adding meters to TNS,
documentation and
communication between the
Substation and Transmission
(S&T) Engineer and the TNS
Operator is critical to successful
configuration of the system.
After the meter shop receives the
purchased meters, the meter
technician may custom
configure the meter for the
utility. The meter technician will
then install the meter at a
customer location and must pass
configuration information to the
TNS Operator for entry into
TNS.
The more information the meter
technician documents about the
meter, and the TNS Operator in
turn documents in TNS, the
more functional TNS becomes
for the utility. Once the utility
collects the basic information
about the installed meters, the
TNS Operator can, in batch
mode or interactively, search the
electrical system for the meters
by the meter serial number.
When the search process finds
the meters on the electrical
system, TNS will enter the
meters into the database
readying the meters for AMR.
REMEMBER
116
Searching Meters into
TNS Process Flow
Purchase Meters
Meter shop configures meters
Meter shop documents Meter
configurations per serial#
(optional, but desired)
Meter shop installs meters
Verify Type/Model in Product
Table
Verify Type/Mode in SubProduct
Table
Update Product Type Model XRef Table
Verify Meter Type in Meter
Conversion Table
Batch or interactively search in
meters
Review and correct problems
with search...verify meters are in
permanent database
Set up AMR
The more information TNS has about each meter, the more
functionality the utility will gather from TNS.
Required Meter Fields
The TNS Operator must populate certain meter fields for TNS to operate
properly. The required meter fields include:
Meter Field
Residential Meters
Altimus and
Commercial Meters
(CMT S4 and
CMT-Vectron)
Serial Number
Port (0)
Meter Type
Rate Class
Substation ID (Path)
Yes
Yes
Yes
No
Yes
Yes
Yes
Yes
Yes
Yes
Batch versus Interactive Search
There are two ways to search meters into the database, interactive or batch.
• With an interactive search, the TNS Operator types information for a
meter into the Temporary Meter database and then initiates the search
process on the meters keyed into TNS.
• With a batch search, the utility sets up a batch file with information
documenting a large number of meters. The utility may export most of
the information in the batch file from the Customer Information System
(CIS) or billing system. The TNS Operator then imports the information
from the batch file into the Temporary Meter database automatically.
The Temporary Meter database in TNS stores information about meters TNS
will search into the Meter database. The Temporary Meter database is a
holding area for meters TNS must locate. If successfully located, TNS places
the meters in the Permanent Meter database or Meter database.
117
Searching Meters into TNS Interactively
Searching meters into TNS requires several human and computer
processes. The following diagram shows detailed steps utility personnel
and computers make to enter meter records interactively into the Meter
database.
Human Processes
Utility
Purchases
AMR
Meters
Meter Tech
configures, installs
and documents
meters
Documentation
from Meter Tech
feeds creation of
batch or interactive
input file for TNS
“Search In”
process
TNS Processes: Interactive “Search In” Meters
Input meter
information
Program Location:
TNS Metering Maintenance
Verify in TNS,
Product Table with
Type & Models
represented in
purchase (optional)
Verify in TNS, Sub
Product Table with
Type & Models
represented in
purchase
(optional)
Phase I
- Read Type/Model of
Serial Number from
X-ref table
Open Temp
Meter
Database
(Temp Meter
Misc)
118
Temp Meter
Database
X-re
f tab
le
- Non-Failed Meters
- Failed Meters
Meter in X-ref table
Input in TNS, Meter
Serial Number Ranges
(manditory) with Type/
Model into Product
Type Model Cross
Reference (X-ref) Table
Mete
r NO
T in
r
or
mo
ble roblem lem
pro
p
b
NS tation th pro
T
.
1 ubs r pa
2. S eter o
3. M
Connect to Substation
- Find Path
- Read Type & Model
- Deassign 2-way Addr
Program Location:
Meter Misc.
Meter Found
and Type and
Model Family
on meter match
X-ref table fam
ily for Serial #
Permanent Meter
Database
Search History Log
SHyyyymmdd.dat
Searching Meters into TNS Using Batch Search
The batch process to search meters into TNS is slightly different than the
interactive process. The following diagram shows detailed steps utility
personnel and computers make to enter meter records into the Meter database
when using a batch file.
Human Processes
Utility
Purchases
AMR
Meters
Meter Tech
configures,
installs and
documents
meters
Merge/
manipulate
export file for
TNS specs
Verify in TNS, Sub
Product Table with
Type & Models
represented in
purchase
(optional)
Input in TNS, M eter
(m anditory) with Type/
Model into Product
Type M odel Cross
Reference (X-Ref)
Table
Schedule
batch job in
TNS
Program Location:
\users\xxx\batch\PreTIQ.Log
Program Location:
Batch Scheduler
(Batch file in \users\xxx\batch)
Verify in TNS,
Product Table with
Type & Models
represented in
purchase (optional)
Documentation
from Meter Tech
feeds creation of
input file for TNS
and/or CIS
Possible
export of
CIS
information
TNS Processes: “Search In” Meters
“Search In”
process
started with
batch file
Phase I
Serial Number from
X-ref table
tio n
da
r
v a li e t e
ed or M
il
a
f
nt Tem p
e
e
te m in
s ta e a d y t a b a s
lr
tc h
Da
B a ter a
Me
tab le
t in X- ref
Me ter no
Me ter in
X- re f ta ble
PreTIQ log
- Failed phase I
check
- Failed M eters
(phase I)
Temp Meter
Database
- Non-Failed Meters
Non
Phase II
- Find Path
- Read Type & Model
-F a il
e te
ed M
n ly
rs O
- Failed M eters
(phase II)
or
r
mo
le m
p ro b p ro b le b le m
n
NS
1 . T b s ta tio a th p ro
u
p
2 . S e te r o r
3. M
Program Location:
Meter Misc.
Me ter Fou nd
and Typ e and
Mod el Fam ily
on me ter m atc
h
for Ser ial #
Permanent Meter
Database
Search History Log
SHyyyymmdd.dat
119
Enhancing TNS Functionality through Meter Fields
The functions the utility can perform with TNS will depend on the
information TNS stores about the meters. TNS uses specific fields in the
Meter database to allow certain functionality. Understanding the use of the
fields prior to populating the database can help utility personnel decide
which fields are critical to the anticipated operation of TNS. Examples
include the following.
Customer
Problems/Functions
I need to be able to sort
through meters reading “no
pulses in 24 hours” to
differentiate energy theft
from low usage customer
locations like light poles.
I want the flexibility for my
Customer Service
Representatives (CSRs) to
perform reads and
disconnects based on
information they know,
rather than the TWACS
serial number.
I want to use TNS to help
map outages in my system.
I want to run AMR based on
the billing cycle.
I want to monitor a group of
customer meters for a
problem or situation.
I want to be able to view
AMR Hourly graphs.
I want to use Altimus meters
and commercial meters like
the CMT-SX and CMT
Vectron.
I want to complete meter
searches without having the
system search every
substation in my TWACS
network.
120
TNS Meter Setup
Populate the meter Device Location field to
qualify meters in Trouble Processing Details.
Treat the Device Location field as if the
category were low usage locations. Leave the
value blank for customers with normal read
patterns and only populate for locations like light
poles, pole barns, vacation homes, etc.
Populate any or all of the following meter fields:
• Customer Account Number
• Premises ID
• Meter Number
Populate the Transformer Grid and/or
Protective Device meter fields.
Populate the Cycle field.
Define a unique setting for the User 1 or User 2
fields that uniquely identifies each group of users.
Meter Number or Account Number fields
must be populated to view some hourly graphs.
Rate Class field must be defined on the meter
record. The rate class defines the command
parameters or registers to be read from the meters.
Accurately populate the SubID field for the
meter.
Best Practices for Meter Field Use
The following example shows the fields a utility may populate when adding a
meter to the Temp Meter database. Many of the meter fields can take any type
of data the TNS Operator keys into the field. The tables on the following
pages provide a list of recommended uses for the meter fields in the three
sections of the Temp Meter database record when adding meters
interactively.
The following table lists the fields in the Temp Serial Number Data
portion of the Temp Meter database entry screen.
Temp Serial
Number Data
Field
SerialNumber
Type and Model
Recommended Use
Field must match the serial number on the
transponder/meter. TNS uses the serial number to
address the meter during reads.
Used to identify the make and configuration of the meter.
Example: Type 31 Model 98. The meter technician
should know the type and model number based on how
the utility ordered or configured the meter. These fields
display on the form, but the TNS Operator cannot insert
type and model numbers into this TNS form. TNS will
populate the information with the serial number reported
by the meter. The TNS Operator must populate the
Product Type Model Cross Reference table with the type
and model information.
121
Temp Serial
Number Data
Field
PremiseID
SubID
Detection
ProtectiveDevice,
TransformerGrid
InstallDate
DistrictNo.
DeviceLoc.
User1, User2
Comm Type,
Device, Connect
Type
ConnectDate
122
Recommended Use
Is usually the address of the meter assigned by the utility.
PremiseID is one of the four fields a CSR can use to
perform reads or disconnect/connects.
Identifies the substation to which the meter attaches
under normal circumstances. If the TNS Operator inserts
the correct SubID prior to the search process, the search
process will go faster. If not, the TNS Operator must use
the City Sub search function to search all subs for the
meter. (See Chapter 12, City-Sub in the TNS End User
Guide Rev D for more information.)
Identifies the normal location of the meter at the time of
the search. TNS can search specific paths (directed
search) or all buses, feeders, phases, signals, or detection
points (global search) if the TNS Operator does not enter
a specific path.
Identifies a protective device and transformer grid to
which the meter attaches upstream. The utility will have
a naming structure for Protective Devices. Populating the
Protective Device and Transformer Grid fields
aids the utility in outage mapping.
TNS populates automatically based on date of entry.
Can represent the district number of the meter (e.g. 23).
Best used in the Trouble Detail application. (See Chapter
7, Trouble Server Applications in the TNS End User
Guide Rev D for more information.) The most effective
use of this field is to treat the field as a designator for low
usage categories. Leave the field blank if the customer is
a normal usage account. Populate the field if the
customer is a low usage account for which “no pulses in
24 hours” would be normal. This scheme will help the
utility isolate customers that unplug their meters. For
example, leave blank for normal home and business
customers, populate for low usage customers: PolBrn,
LtPole, VacHom, HuntCb, etc.
Populate for special purposes such as monitoring. For
example, the TNS Operator may type in groups for
Billing Issues, Theft Watch, etc.
Leave blank.
TNS will populate.
The following table lists the fields in the Temp Port Data portion of the
Temp Meter database entry screen
Temp Port Data
Fields
Port
Premises
Device Type,
Connect Type
Modified
District
Location
User 1, User 2
Recommended Use
Used to identify the port. At a minimum, Port 0 must be
defined. If a multiport transponder is used to connect the
gas and water meters, 1 and 2 may be defined if supported
by the meter.
This should typically match the PremiseID defined for the
Temp Serial Number Data.
Leave blank.
Dates TNS will populate.
This should typically match the District defined for the
Temp Serial Number Data. Since each port may represent a
different utility's meter, District is defined per port.
This field may be the same as the Device Location in the
Temp Serial Number Data or may indicate the specific
location ID for the premise. The Location field is 6
characters long.
Populate for special purposes such as monitoring. For
example, set up groups for Billing Issues, Theft Watch, etc.
The following table lists the fields in the Temp Meter Data portion of the
Temp Meter database entry screen
Temp Meter Data
Fields
Rate Class
Meter Type
Meter Number
Route
Cycle
Recommended Use
The rate class code used by the utility. This field is required
for an Altimus meter or commercial meter such as the
CMT-SX or CMT-Vectron.
Select from the available drop-down list of meter types (e.g.
Altimus, CMT, IMT3H, etc.). The Meter Type field maps
to a Meter Type entry in the Meter Conversion table and
tells TNS how to interpret rotations to KWH. The Meter
Conversion table entry specified by Meter Type also
references an RCE Type field that identifies the meter
types for meter reading. Meter Type is a required field.
Typically used in the utility CIS. The meter manufacturer
usually prints the meter number on the meter. The utility
must populate this field if the utility wants to view hourly
usage graphs or pull up CSR reads and
disconnects/connects by meter number.
A route ID assigned by the utility. Since each port may
represent a meter from a different utility, the route field
may vary per port for a customer.
The cycle field represents the billing cycle. Since each port
may represent a meter from a different utility, the cycle may
vary per port for a customer.
123
Temp Meter Data
Fields
Customer
Account
Initial Read
Offset Read
Offset Re-Calc
Flag
User1, User2
Class
Recommended Use
The customer account as defined in the utility CIS.
The value of the meter’s mechanical register (in KWH).
Used to initialize the register for the meter port. TNS
initializes this value only if the value is greater than zero.
This field should normally be set to 0.
The register reading of the meter port in pulses. Used to
calculate the offset. The Offset Read field should be set to
0. Consult with DCSI before modifying this field.
Indicator used by the utility to denote that the offset should
be recalculated. Consult with DCSI prior to changing this
flag.
A field assigned for grouping purposes for special reads.
These fields might be used for troubleshooting or special
monitoring.
A three digit numerical code the utility can use for meter
class identification. The Class code is used for meters that
can perform interval reads and should be set to 15, 30, or 60
depending on the interval set. Leave blank for meters that
do not support interval reads.
Meter Type versus Type and Model Fields
The meter record has three fields that are often misinterpreted:
Meter Field
Meter Record Section
Meter Type
Type
Model
Temp Meter Data
Temp Serial Number Data
Temp Serial Number Data
The Meter Type field is part of the Temp Meter Data Field portion of
the Temp Meter database record. It is a required field that references a
Meter Conversion table entry that defines how many KWH to track based
on a single rotation or pulse of the meter for the electric meter. The record
in Meter Conversion also specifies a field called RCE Type. TNS uses
RCE type in the read process to determine the capabilities of the meter for
the purpose of the read. Similarly, the Meter Conversion table tracks
conversions of pulses for water and gas meters to cubic feet. Alternatively,
the Type and Model fields define the configuration of a meter. TNS will
identify the correct type and model provided the Product Type Model
Cross Reference (X-Ref) table has the meter’s serial number listed with the
same Type family documented for the meter. The entry in the X-Ref table
is treated as an initial value. The real type and model values are entered in
the database based on the meter’s response to its type and model queried.
124
Why Program the Meter with Type and Model?
The Type and Model fields in the TNS meter record will match the Type and
Model programmed into the meter. TNS will query the meter to find its type
and model designation. Hence the meter knows its type and model based on
its configuration. The meter never sends KWH readings to TNS in response
to queries. The meter, instead, sends pulse counts. Thus the question, “Why
does the meter need to know its type and model, which can vary based on
pulse conversion rate, if the meter only tracks and reports pulses?” The meter
must know the type and model so the meter knows how many pulses it takes
to return the meter counter to zero. The rollover count defines the number of
pulses before the meter resets to zero. The following table lists the rollover
counts for various Kh values for the IMT3 meter.
Kh Code
Kh Value
Rollover Count
0
1
2
3
4
5
6
7
0.30
0.60
1.80
3.60
7.20
12.00
14.40
28.80
333,333,333.33
166,666,666.67
55,555,555.56
27,777,777.78
13,888,888.89
8,333,333.33
6,944,444.44
3,472,222.22
What Does the Kh Value Mean?
The Kh is the watt-hour constant of the meter. The Kh value tells TNS the
energy used for one rotation of the dial or pulse. For a .6Kh meter, one disk
rotation means the customer used .6 watt hours. Mathematically, Kh is equal
to the watt-hours divided by disk revolutions.
125
Meter Type and the Meter Conversion Table
Using TNS Metering Maintenance, the Meter Conversions application
allows the TNS Operator to define the conversion rates of pulses to KWH
for categories of meter types. (See Chapter 3, Metering Maintenance in the
TNS End User Guide Rev D.) There are three categories of fields in the
Meter Conversion table:
• Meter Conversion
• Hourly Conversion
• Interval Conversion
TIP
The TNS Operator can view the Meter Conversion table by clicking the
Meter Conversions
button on the Metering Maintenance tool bar.
Meter Conversions in the Meter Conversion Table
The Meter Conversion portion of the screen provides a translation of
pulses into KWH for reporting and billing purposes for the Total
Consumption (TC) reads and Daily Shift TC reads. Residential meters only
track and report pulses, not KWH. The transponder on the meter does not
know nor does it report the actual numbers on the dial. The transponder
knows the number of dial pulses and how many dial pulses it should
increment before restarting at a zero count. When TNS requests a total
consumption (TC) read or a Daily Shift TC read from a meter, the meter
will respond with the number of rotations of the dial seen.
126
When TNS requests a read, TNS converts pulses reported by the meter to
KWH based on conversion factors.
The following table details a basic configuration using some of the
parameters defined in the Meter Conversion table.
Kh Conversion
Factor
Meter Pulses
KWH Calculation
KWH
.6KH
1.8KH
7.2KH
12KH
14.4KH
2000
2000
2000
2000
2000
(2000*.6)/1000
(2000*1.8)/1000
(2000*7.2)/1000
(2000*12)/1000
(2000*14.4)/1000
1.2KWH
3.6KWH
14.4KWH
24KWH
28.8KWH
If the meter conversion factors are not correct, the utility will bill the
customer incorrectly. When adding new meter types and models, the utility
should consult with DCSI for assistance in configuring the Meter Conversion
table.
Hourly and Interval Conversions in the Meter Conversion Table
The Hourly and Interval Conversion portions of the Meter Conversion table
deal with setting a factor to apply to pulse counts reported by the meter for the
interval. The factor or multiplier allows TNS to re-create the number of actual
pulses based on the reported pulses. This factoring reduces the amount of data
the meter must send, thus eliminating potential data loss from exceeding
thermal limits of the meter.
What are Thermal Limits?
Each meter transponder has a resistor that produces the signal back to
TWACS substation equipment. The resistor in the meter can only produce a
certain number of signals before excessive heat builds up in the resistor. Each
resistor has a pre-defined thermal limit. When the meter transmits an amount
of information causing the resistor to reach its thermal limit, the meter ceases
to transmit information, thus resulting in an incomplete response to TNS
which TNS will discard. The resistor must then regain firings before
transmitting any additional information. Large amounts of information
produced by tracking of hourly and interval energy use can cause the meter to
exceed the thermal limit of the resistor when transmitting the interval
information to the substation. To reduce the amount of information and
enhance the potential for a successful read for residential meters, the meter
reduces the pulse counts by a certain factor (defined by the hourly and
interval conversion multiplier fields). The multiplier includes the Kh factor
multiplied by a number.
In the case of IMT3s, the multiplier is eight times the Kh factor of 7.2 or 57.6.
TNS applies the hourly and interval conversion multipliers to the information
received from the meter to achieve an accurate count of pulses read from the
meter for a given interval.
127
NOTE
DCSI Field Service populates the Meter Conversion table during
installation. If the utility adds new meter types, the TNS Operator
should call Customer Care to request consultation with DCSI Field
Service for assistance adding new elements to the Meter Conversion
table.
Meter Shop to TNS Operator Communications
Documentation of meters and communication of information from the
meter shop technician to the TNS Operator is crucial to successful and
accurate configuration of TNS. The Meter Configuration Worksheet Basic and Advanced, found on the following pages, detail information the
meter technician might pass to the TNS Operator or the TNS Operator
might gather from the CIS. Once the meter technician documents the meter
configurations, the TNS Operator can easily configure TNS to accurately
reflect the appropriate configuration, by adding the meter settings to the
TNS database.
Meter Configuration W orksheet - Basic
Ne w Meter Information
Serial Number
Type Model
(Transponder) Meter Number #
#
Normal Substation
128
Substation Informa tion
Phase
(A/B/C/ALL)
Feeder
Bus
Re placed Meter Information
Signal
Serial Number
(L/L or L/G) (Transponder) Meter Number
Meter Configuration Worksheet - Advanced
New Meter Information
Type
Meter Number
#
Serial Number
(Transponder)
Replaced Meter Information
Serial Number
(Transponder) Meter Number
Model
#
Substation Information
Normal Substation
Detection Point
Premises ID #
Protective Device
Transformer Grid
Install Date/Time
District Number
Device Location
Active
One Way Device
User 1
User 2
Bus
Feeder
Phase
(A/B/C/ALL)
Would it be normal for this meter to
Reason
New for TWACS frequently record "no pulses in 24 hours"?
Suspect Meter
Y/N
Failed Meter
Feature Upgrade
Add Load Ctrl
Add Port Meter
Other
None/A/B/C/N/All
/
/
___:___
Y/N
Y/N
Note:
Port Information (Multiport)
0
1
Serial Port
Premises ID
Install Date/Time
Port District Number
Port Device Number
Active
Device Type
Connect Type
Connect Date
Port User 1
Port User 2
Signal
(L/L or L/G)
Y/N
/
Y/N
/
/
2
Y/N
/
/
/
Meter Information (Multiport)
0
1
2
Customer Acct #
Rate Class
Meter Type
Meter Number
Route ID
Cycle #
Initial Reading
Offset Reading
Meter Class
60/30/15
60/30/15
60/30/15
Offset Recalc
Recalc/None Recalc/None Recalc/None
Meter User 1
Meter User 1
Class
Interactively Searching Meters
TNS. One method of entering meters into TNS is to interactively enter meter
information directly into the Temporary Meter database.
The Temp Meter Misc application allows the TNS Operator to interactively
add information to the Temporary Meter database.
129
Adding Meters Interactively
When a utility installs a meter,
the TNS Operator must enter
the meter into TNS so the
utility can read the meter
automatically. After the TNS
Operator acquires the meter
information from the meter
technician or meter shop, the
TNS Operator will enter the
information into TNS using the
Temp Meter Misc application.
Next the TNS Operator will
initiate a search for the meter. If
the Substation Communications
Equipment (SCE) finds the
meter, TNS will initiate an
initial read of the meter’s type
and model. TNS will:
1.
Search the meter
2.
Read the meter type and
model
3.
De-assign the 2-way
address
Interactive Search for
Meters Process Flow
Acquire meter information from
meter tech
Open Temp Meter Misc
application
Add meter information to the
Temp Meter Database
Initiate search of new meter
Validate meter status
Troubleshoot failed meters
- Review search status flags
- Review TNS, SCE, RCE codes
in Response Status X-Reference
When TNS issues the read for
the meter type and model, the type and model read may fail, thus failing the
search process. TNS inserts the type and model read from the meter into
the meter record. TNS will validate the type is located in the Product table
and will locate the de-assign command defined for the meter. TNS will
then de-assign two-way addressing for the meter and insert the meter into
the Meter database. After searching for the meter, the TNS Operator must
check whether the meter made it to the Meter database or failed. If the
meter failed, the TNS Operator must troubleshoot the cause of the failure
using various database and log file lookups.
130
Complete the following steps to add a meter to the Temp Meter database.
1.
Open the TNS Metering Maintenance tool bar by following the menu
path Start > Programs > TNS Metering Maintenance > TNS
Metering Maintenance.
2.
Click the Temp SN, Port, & Meter Data
button to open the
Temp Serial Number, Port and Meter Data window.
From the Temp Serial Number, Port and Meter Data window you can:
•
Add meters interactively to the Temp Meter database,
•
Initiate a search of meters in the Temp Meter database, and
•
Research the status of meter searches.
131
3.
Click the Add Record
button to open the Add Temp Serial
Number Records window.
The Add Temp Serial Number Records window enables you to
manually enter information into the Temp Meter database.
4.
Populate the fields using the information provided in Best Practices
for Meter Field Use on page 121.
The window is divided into three segments:
Temp Serial
Number Data
Temp Port
Data
Temp Meter
Data
132
Used to document general information common
to all (potentially 3) meters of a multi-port
transponder. This region includes the path
information for the meter.
Used to document information specific to a
particular meter port. Meters may have up to three
ports for connecting electric (0), water (1) and gas
(2) meters.
Used to document information specific to the
meters on the three ports.
5.
Click the Set Path button to select entries from a table listing of
SubID, BusID, FdrID, Phase, Signal, and Detection.
The Set Communication Path window appears.
The TNS Operator must select a New Sub element. The New Phase,
New Signal, and New Detection fields will default to ALL or
BOTH if nothing is selected.
NOTE
The TNS Operator may select a substation and leave all other elements as
ALL or BOTH, and TNS will request the substation to search all possible
paths for a meter (global search). Narrowing the search to a more specific
path will speed the search process (directed search).
6.
Populate the information on the screen and click the Apply button.
7.
Click the Exit button to return to the Add Temp Serial Number
Records window.
8.
Validate the Command Delay in the Product table if you are using
feeder-level detection.
If the utility uses feeder-level detection, and TNS requests the SCE to
search all feeders for a meter, the meter transmits a substantial amount
of information in response to the TNS request and has the potential to
surpass the thermal limits of the meter and cease communications.
Thus, when a utility uses feeder-level detection, the TNS Operator
must configure the Command Delay 1 and Command Delay 2
fields, in the Product table, with a value of “5”. The Command Delay 1
and 2 fields indicate delay factors TNS must use during the search
process for meters to regain firings. This delay time allows the meter
to regain firings so successful transmission of information can occur.
Product Table Field
Defines the Delay Between
Command Delay 1
Command Delay 2
Search and meter type/model read
Meter type/model read and 2-way address
de-assign
133
For detailed information about each field in the Temp Serial
Number Data area, see Enhancing TNS Functionality through Meter
Fields on page 120.
The Serial Number field is a required field.
There are two Transaction Types: Add and Search Only.
Select the Add radio button for the Transaction Type to:
•
Search paths for the meter
•
Read the meter’s type and model
•
De-assign the meter’s two-way addressing
•
Add a meter to the permanent database if found
The TNS Operator can click the Search Only radio button as a
diagnostic tool to find a meter’s path. The Search Only option will
cause TNS to look for and report a path of a meter.
134
9.
Populate the information in the Temp Port Data region of the screen.
For detailed information about each field in the Temp Port Data
region, see Enhancing TNS Functionality through Meter Fields on
page 120.
The TNS Operator must populate the Port field. For single port
meters, the value is 0 (zero).
10.
Populate the information in the Temp Meter Data portion of the
screen.
For detailed information about each field in the Temp Meter Data
region, see Enhancing TNS Functionality through Meter Fields on
page 120.
135
NOTE
REMEMBER
The TNS Operator must select a meter type in the Meter Type field.
This field corresponds to an entry in the Meter Conversion table, which
specifies the conversion of rotations or pulses to usage. If the TNS
Operator enters an incorrect value, the utility will inaccurately bill for
usage.
The TNS Operator must populate Rate Class for Altimus and CMT
(commercial) meters. If a utility desires time of use billing, rate class
must be specified.
11.
Click the Save New Records button to save the meter entry.
12.
Click the Exit button to close the window after saving all new
records.
The Temp Serial Number Port and Meter Data appears.
When a meter is in the Temporary database, and TNS has yet to
search it, the meter will have a non-failed status. DCSI refers to
meters of this status as temp non-failed.
13.
Click the Do Search
added meters.
button to initiate a search of the newly
After clicking the Do Search button, the meter will disappear from the
Temp Serial Number Port and Meter Data screen. If the meter search is
successful, the meter definition will move to the Meter database. If the
search is unsuccessful, the meter will receive a failed status in the Temp
Meter database sometimes called temp-failed. The section, Verifying
Meters Searched on page 141, discusses diagnosing problems with
Temp-Failed meters.
136
Post-Search Activities
Once the TNS Operator issues the command to search a meter, TNS and the
SCE begin a series of communications. There are various places the TNS
Operator can look to check on the status of the search.
The following diagram details the search process from the perspectives of
TNS and the substation.
TNS to Substation Search
Process
TNS
Substation
Input meter information
Serial Number from
X-ref table
- Read Search Mode
for Type/Model from
SubProduct Table
- Connect to substation
and issue search
command to find path.
Disconnect from sub.
and check status until
completed
and check status until
completed
Receive Commands
from TNS to search
meters
Sub searches up to
meters simultaneously
Report status back to
TNS when requested
137
There are three different search modes available. The SubProduct table
defines the type of search to use for a given type and model of meter. TNS
reads the SubProduct table to determine the type of search to have the
substation perform.
Search
Mode
Search
Type
0
1
4
0
0
1
Value Description
Speed
Meters that
Support
Logical Elimination
Medium All
All
Advanced Search
Fastest
New meters only
(not LCT, MIT,
IMT1, and IMT2)
When a search is performed, the TNS Operator can monitor the status of
the search operation using the following TNS forms.
• Substation Command Queue (below)
• Temp Non-Failed Database Records (page 141)
Substation Command Queue
Open the Substation Command Queue, on the Metering Maintenance tool
bar, by clicking the Substation Command Queue
138
button.
Double-click the desired substation to display commands for that substation
in the Outbound Command Queue.
The TNS Operator can tell which command is in queue by the Function
(Func.) field. All three commands in the example are Function 300, which
defines the RCE Search Function.
The TNS Operator can deduce that TNS is currently searching three meters.
The following table lists other common RCE function codes.
Function
Code
Description
62
63
89
82
83
151
300
Read Reg (Demand Request, AMR, etc.)
Write Reg (Assign/De-assign 2way, clear buffer)
Interval and Hourly Reads
Test Communication Tool
Voltage Read
Service Disconnect
RCE Search Function
139
Inbound and Outbound Paths (SCE to Meter)
Understanding what the substation does when the search command
executes can help the TNS Operator develop patience for the time it takes
to search a meter. There are several paths the SCE may search to find
meters. The paths are different for inbound and outbound traffic. Since the
outbound traffic flows through the OMU/MTU equipment which attaches
to the bus, the outbound path consists of the Bus ID, Phase (A, B, or C),
and Signaling Mode (line-neutral or line-line). The Inbound Path consists
of the Bus ID, Feeder ID, and Detection Point (A, B, C, or N). The
following table summarizes the inbound and outbound paths.
Path Component
Outbound Path
Inbound Path
Bus
Feeder
Phase
Signaling Mode
Detection Point
Bus ID
Bus ID
Feeder ID
A, B, C
L-G, L-L
A, B, C, or N
TNS uses the terms line-neutral and line-ground synonymously, since TNS
uses a neutral detection point definition for an IPU and a neutral outbound
phasor definition. It is common to hear the term line-neutral in reference to
these communication elements. In the search function, the TNS Operator
defines a signal of line-line, line-ground, or all. Although there are slight
differences between the definitions for line-neutral and line-ground, the
terms are often used synonymously.
Primary and Secondary Detection Points
The search process returns a primary path, and sometimes a secondary
path, in the Search History log when the substation finds a meter. All
meters have a primary path. In most cases, the SCE will identify a
secondary inbound path or detection point. Most meters that have a
line-ground outbound path have a primary path in the phase and a
secondary path in the neutral, provided a neutral detection point exists. The
following table illustrates the primary and secondary detection points for
line-neutral signaling.
140
Outbound
Phasor
Primary
Detection Point
Secondary
Detection Point
A-Ground
B-Ground
C-Ground
A
B
C
N
N
N
Meters that have a line-line outbound path will always have a primary path in
one phase and the secondary path in the adjacent phase. Either detection point
is equally valid, but by convention, the TWACS system uses the primary path
for two-way communications. The following table illustrates the primary and
secondary detection points for line-line signaling.
Outbound
Phasor
Primary
Secondary
Detection Point Detection Point
A-B
B-C
C-A
A
B
C
B
C
A
Verifying Meters Searched
Once TNS has the order to search a substation for meters, TNS connects with
the specified substations. When TNS sends the substation commands to
search the various meters on dialup the communications link may hang up
while the substation performs the search. TNS will dial the substation
intermittently to check on the status and collect information about found
meters.
Where Do Meter Definitions in TNS Go After the Search?
After the search, meters defined in the Temp Meter database go to one of the
following locations.
• Meters not searched stay in the Temp Database with a non-failed status.
• Meters in the process of searching receive a SRCH status of Y and are
visible only through the Temp-Failed application window.
• Meters failing the search stay in the Temp Database and receive a failed
status (e.g. Failed = Y)
• Meters found are moved to the Meter database.
• A General Status log of the meter search result for all meter searches is
found in the file genstatus.log.
• A detailed Search History log of the meter path search is found in the
SHyyyymmdd.dat file where yyyymmdd represents the run date of the
search. (yyyy=year, mm=month, dd=date).
141
The TNS Operator will want to monitor the status of the search as the
search process proceeds. The following diagram details the process the
TNS Operator may follow to check on the status of the meter search.
TNS Operator Process to
Monitor Search Activity
Input meters to be
searched in Temp
Meter Misc
View Meters to be
searched in Temp
Meter Misc
Submit search in Temp
Meter Misc
Meter search
begins
View status of meters
being searched in
Temp Non-Failed
View general log of
adds/searches in
genstatus.log
View status of failed
meters in Temp Failed
Meter search
completes
Validate meters found
in Meter Misc
View Shyyyymmdd.dat
for detail on failure
Adding Meters Interactively on page 130, discussed how to input the meter
information in the Temp Meter database and submit the meters to the
search process. The following section, Identifying Where to Monitor
Meters Being Searched, steps through monitoring search activity.
142
Identifying Where to Monitor Meters Being Searched
Depending on the time in the search process, when viewing certain tables, the
TNS Operator may or may not see a meter listed where expected. To help
isolate where a meter should be viewed, the following table details where to
view meters during phases of the search process. It is necessary to open the
TNS Metering Maintenance tool bar to view the meters regardless of the
meter’s location.
Temp Meter
Misc
Temp
Non-Failed
x
*x
Temp Failed
Meter Misc
Status of Meter
Search
Meters to be
searched
Meters in process
of being searched
Search completed
and meter not
found, not read or
not deassigned
Search completed
and meter found,
read, and
deassigned
*x
x
x
x
* You must click the See Non-Failed button after opening the Temp Failed/Non-Failed
Interface window to see the meters.
143
Viewing Temp Failed Records
Click the Failed Temp Serial Number Maintenance
button on the
Metering Maintenance tool bar (or the Run TempsN-Failed Form
button from the Temp Meter Misc application), to open the Temp
Failed/Non-Failed Interface window.
The initial screen appears with the Failed Temp Serial Numbers showing
no records.
You can view the failed meters by clicking the Enter/Execute Query
button twice to query all failed records. You can query for a specific entry
by clicking the Query button, entering data in the Serial Number field,
then clicking the Query button again to see the results. If the table contains
the serial number searched, it will show just that serial number in the list. If
the entry is not in the table, the table display is empty.
TIP
144
The user can enter “< or >” before the serial number to find ranges of
serial numbers or the “%” after as a wildcard.
The previous example shows all failed meters in the TNS Temp Meter
database. TNS gives a failed status to those meters where the:
• Meter was not found
• Meter Type/Model family did not match X-Ref table entry
• Meter Type/Model not listed in Product table
• Meter Type/Model not listed in SubProduct table
• Substation was not able to de-assign 2-way addressing
NOTE
When the See Non-Failed button is visible, TNS displays the temp failed
entries. When the See Failed button is visible, TNS displays the temp
non-failed entries.
Notice the columns to the right of the window. These columns define the
status of the meter search. The following table details the meaning of the
status codes.
Status
Meaning
IP
SRCH
SOK
REG
In Progress: TNS is in the process of searching the meter.
Search: TNS has started the search for the meter.
Search OK: TNS found the path of the meter.
Read Register: TNS has initiated read of the meter type and
model.
Read OK: TNS successfully read the read register for type and
model.
De-assign: TNS initiated de-assign of two-way addressing on the
meter. The de-assign command code for the meter is in the
Product table. If the de-assign command code is not in the
Product table, the meter will fail.
De-assign OK: De-assign of meter two-way addressing is
successful.
Completed: The TNS Operator should not see a “Y” completed
code unless the TNS Operator issued a SRCH ONLY command.
When TNS completes the search only, TNS marks the meter
complete. On an ADD, TNS places the meter into the Meter
database and removes it from the Temp Database.
Marked failed: TNS failed to successfully add the meter to the
Meter database.
Failure codes: Pull up Response Detail by double-clicking on one
of these fields, or look up the codes in the Response Status Cross
Reference window in the TNS System Administration tool bar.
Search, Add or Mod: Depending on what the user requested for
Transaction Type.
The last substation that was searched.
ROK
DEA
DOK
COMP
FAIL
TNS, SCE,
RCE
Type ID
Substation
145
REMEMBER
The TNS Operator must populate Serial Number, Port 0, and Meter
Type for all meters and Rate Class for CMT-SX and CMT-Vectron
(commercial) meters and Altimus meters. The more information TNS
has about each meter, the more functionality the utility will gather
from TNS.
The TNS Operator can view the status codes, TNS, SCE, and RCE temp
failed error codes by scrolling to the right of a Temp-Failed meter record.
These codes provide an indication of whether the problem with the search
was with a TNS configuration (TNS), the substation (SCE), or with the
meter or path (RCE). The TNS Operator can translate the TNS, SCE, and
RCE codes by double-clicking on the code.
Clicking the OK button will return the display to the Temp Failed window.
146
Viewing Temp Non-Failed Records
Temp Non-Failed records are meters in the Temporary database that have
either not been searched or are in the process of being searched.
Click the See Non-Failed button on the Temp Failed/Non-Failed Interface
window to view the Temp Non-Failed records. The initial screen appears
showing no records.
Click the Enter/Execute Query button twice to query all non-failed records.
You can view the non-failed meters by clicking the Enter/Execute Query
button twice to query all failed records. You can query for a specific entry by
clicking the Query button, entering data in the Serial Number field, then
clicking the Query button again to see the results. If the table contains the
serial number searched, it will show just that serial number in the list. If the
entry is not in the table, the table display is empty.
TIP The user can enter “< or >” before the serial number to find ranges of
Viewing the General Status Log
The genstatus.log file contains general historical information about the
searches performed by TNS. The genstatus.log file can be viewed with any
standard text editor such as Windows Notepad or WordPad. The following
table displays sample genstatus.log data.
Genstatus.log Data Entries
ADD
ADD
ADD
ADD
ADD
ADD
PATH : SN
PATH : SN
PATH : SN
PATH : SN
PATH : SN
PATH : SN
996094 Search Failed. 08-SEP-2003 14:56:20
990082 Add to SN. 08-SEP-2003 15:56:01
990087 Add to SN. 08-SEP-2003 16:09:09
990082 Add to SN. 09-SEP-2003 13:29:48
147
Genstatus.log Data Entries
ADD PATH : SN 173272 De-assign Failed. 09-SEP-2003 13:45:08
ADD PATH : SN 990078 Add to SN. 09-SEP-2003 13:54:33
ADD PATH : SN 990087 De-assign Failed. 09-SEP-2003 13:54:45
SEARCH ONLY : SN 996094 Search Failed. 09-SEP-2003 15:44:51
SEARCH ONLY : SN 996094 Search successful. 09-SEP-2003 16:04:03
SEARCH ONLY : SN 996094 Search successful. 09-SEP-2003 16:05:59
ADD PATH : SN 996094 Search Failed. 09-SEP-2003 17:54:53
ADD PATH : SN 996094 Search Failed. 09-SEP-2003 17:58:35
ADD PATH : SN 996094 Read Reg Failed. 10-SEP-2003 07:16:35
ADD PATH : SN 996094 Read Reg Failed. 10-SEP-2003 07:20:11
Viewing the Detail Search Status Log File
The Search History log file contains detailed information about the search
completed on a particular day by TNS. The name of the file depends on the
day created. For example, TNS assigns a search completed on April 5 the
name SH20040405.dat. The genstatus.log file can be viewed with any
standard text editor such as Windows Notepad or WordPad. The following
table displays sample data from a Search History log.
Sample Search History Log File SH20040405.dat
Version 1.02 06/06/2000
3 09/09/2003 13:46:46 CDT 4 0 990078 255 255 255 255 255 3 01 57
0 1 1 1 2 2 2 12 27248 249 0 99 FF
0 1 1 1 2 2 3 0 29939 248 0 98 FF
8 4 1 1 3 2 1 0 1 0 0 39 00
8 4 1 1 3 2 3 0 1 253 0 41 00
8 4 1 1 3 1 3 0 1 2 0 43 00
7 4 1 1 2 2 3 0 29939 248 0 98 FF
7 4 1 1 2 2 2 0 27248 249 0 99 FF
8 4 1 1 2 1 2 0 2 252 0 51 00
8 4 1 1 1 2 2 0 41 246 0 52 00
8 4 1 1 1 2 1 0 3 244 0 57 00
8 4 1 1 1 1 1 0 3 250 0 52 00
Version 1.02 06/06/2000
8 09/09/2003 15:37:41 CDT 4 0 996094 255 255 255 255 255 3 01 00
1 0 0 0 0 0 0 12 0 0 0 0 00
1 0 0 0 0 0 0 0 0 0 0 0 00
8 4 1 1 3 2 1 0 1 252 0 47 00
8 4 1 1 3 2 3 0 2 254 0 64 00
148
Sample Search History Log File SH20040405.dat
8 4 1 1 3 1 3 0 1 4 0 52 00
8 4 1 1 2 2 3 0 2 9 0 51 00
8 4 1 1 2 2 2 0 2 9 0 56 00
8 4 1 1 2 1 2 0 2 254 0 50 00
8 4 1 1 1 2 2 0 19 248 0 54 00
8 4 1 1 1 2 1 0 3 255 0 55 00
8 4 1 1 1 1 1 0 3 252 0 44 00
Version 1.02 06/06/2000
9 09/09/2003 16:06:26 CDT 4 0 996094 255 255 255 255 255 3 00 00
0 1 1 1 1 2 1 12 42759 241 0 98 FF
0 1 1 1 1 2 2 0 30792 248 0 93 FF
7 4 1 1 1 2 1 0 42759 241 0 98 FF
7 4 1 1 1 2 2 0 30792 248 0 93 FF
The Search History log file is a good source for detailed information about
searches. The TNS Operator will, with time, learn to look at the raw data file
and determine whether the SCE found a meter’s path. Appendix B Decoding
Search History Log Files details the interpretation of Search History Logs.
Dealing with Failed Searches
After a utility runs a meter search, meters either successfully enter the Meter
database or they fail. If meters fail, the TNS Operator must work with TNS to
isolate the problem.
There are several approaches to isolate the problems associated with failed
meters.
Why Meters Fail
After the utility searches for meters, some meters may fail the search process.
This section discusses situations that can cause meters to fail the search
process.
Meter Failures
After the TNS Operator runs the search process, some meters will
successfully search into the Meter database, and some meters may fail the
search. Meters that fail the search will reside in the Temp Meter database with
a failed status.
149
Process Flow Detail
When meters fail the search
process, there are a number of
tools and processes the TNS
Operator may use to resolve the
problem and search the meter
successfully into the Meter
database. TNS may provide
error messages with
information relating to a failure
in the Temp Meter database.
With some failures, there may
be no information available,
and the TNS Operator must rely
on general processes to isolate
the problem.
Dealing with Meters that
Fail the Search
Identify the failed meters
Determine any error messages
Look up potential error codes
Determine possible causes of
meter search failure
Apply steps to correct the
problem with failed meters
Search or re-search the meters
Repeat steps until meter search
is successful
Recovering from Meter Failures
Meters fail the search process for a number of reasons. The following table
lists the general categories for meter search failure.
150
Type of Failure
Status Code
Provided?
Search Timed Out
Yes
Type/Model not in tables
Wrong type of Meter
Wrong path
Yes
Possibly
No
Wrong serial number
Possibly
No power to the meter
Poor communication
Inaccuracy in search mode
No
No
No
Defective meter
No
Recovery Process
Re-search failed meters. May also increase
time-out value.
Fix Product or SubProduct table. Re-search.
Fix X-Ref table. Re-search.
Select Multi-Update, change path to global
search or use City-Sub search. Re-search.
Enter new meter with correct serial number.
New search.
Fix meter power. Re-search.
Fix communication problem. Re-search.
Update SubProduct table for new search
mode using Logical Elimination or
Amplitude Summation. Re-search (if
Advanced Search initially used).
Fix/replace meter and re-search or replace
the meter, enter new meter serial number
and new search.
Failures that Produce Errors
Some search failures may produce error codes the TNS Operator can view to
assist in diagnosing problems with the TNS search process. Failures that may
produce error codes include:
• Search timed out
When submitting a large number of meters to search, the search process
may extend past the time-out value specified for the search. If all the
meters in the search do not successfully respond in the allotted time,
TNS will report a TNS error 113 in Temp Failed. The TNS Operator
can simply re-search the failed meters, and can optionally increase the
time-out value specified.
NOTE
The search process is a low priority job for the substation. Higher priority
functions like reading meters take precedence over the search process. If
the search occurs while the substation is processing AMR jobs, it may be
necessary to allow even more time for the search to complete. In very
large installations, the TNS Operator may want to allow the searches to
run over the course of a few days.
• Type/model not in the tables
Prior to searching for a meter, the TNS Operator must ensure the
Product table and SubProduct table contain the type and model of the
meter TNS seeks. If the type and model do not exist in either the
Product or SubProduct tables, TNS will generate an error code 1031 or
1033 in the Temp Failed record. The TNS Operator may correct the
problem by placing entries into the Product or SubProduct tables and
re-searching the failed meters.
NOTE
There is a process the TNS Operator can activate from the Temp Failed
Meter database called re-search. The TNS Operator can issue the
re-search function for a meter or group of meters with a failed status
without re-entering the meter into the Temp Meter database. Depending
on the reason for the failure, the TNS Operator may re-search some
meters without change. For other meters, the TNS Operator may need to
delete and re-enter the meter into the Temp Meter database and perform
a new search on the meter.
• Wrong type of meter
The X-Ref table must contain the type and model of each serial number
TNS will search into the database. TNS does not require the exact
model of meter to be accurate in the X-Ref table since the substation
will query the meter and use the model number reported by the meter
when the meter record enters the Meter database. If the X-Ref table
specifies an incorrect type of meter, TNS may produce an error code of
the problem. The TNS Operator may correct the problem by placing the
correct type in the X-Ref table for the failed serial numbers and
re-searching the failed meters.
151
Failures that Do Not Produce Errors
Some search failures do not produce error codes in TNS. These failures can
be more difficult to isolate. Failures that do not produce error codes
include: wrong path, wrong serial number, no power to the meter, poor
communication, inaccuracy in search mode, and defective meter (discussed
in the following section).
Wrong Path
The Meter Technician may have installed a meter on a path other than what
the TNS Operator entered into TNS. This problem can occur due to a
number of reasons and may be beyond any one person’s control. For
example, a utility may switch feeders to a different substation to resolve
outage conditions. This switch would cause the meter to fail when TNS
queries the primary substation for the meter. Wrong path may also occur if
the meter installation is incorrectly documented.
There are a number of items that can correct this problem. TNS has a
function called Multi-Update that allows the TNS Operator to perform two
functions:
• Multi-Update/Sub
This option allows the TNS Operator to change the path to search for
a meter, and then re-search the meters with the new path.
• Multi-Update/City-Sub
This option allows the TNS Operator to select pre-configured groups
of substations when searching for a meter. TNS checks the
substations one at a time for the meter, causing the process time to
expand linearly with the number of substations for a City-Sub Search.
The TNS Operator can manage groups of substations in the City-Sub
application accessible by clicking Start > Programs > TNS City-Sub
Maintenance > CitySub.
REMEMBER
152
A directed search means that the TNS Operator lists a specific bus,
feeder, phase, signal modes, or detection point on the Temp Meter
record for the search. A global search means that the TNS Operator
specifies that TNS should use all buses, feeders, phases, signal modes,
or detection points in the search for a meter.
Wrong Serial Number
It is possible that the TNS Operator incorrectly typed the serial number or the
Meter Technician provided the wrong serial number for an installed meter.
The TNS Operator must enter a new record into the Temp Meter database
with the correct information and perform a new search on the new meter
serial number.
No Power to the Meter
It is possible that the meter has no power. The customer may be disconnected,
or there may be a problem with the meter. Check the Customer Information
System (CIS) and ensure the customer account is active. For this type of
problem, the Meter Technician can correct the problem, and then the TNS
Operator can re-search the existing entry in the Temp Meter database.
Poor Communication
Poor communication with the meter can occur due to a number of reasons.
There may be corroded connectors, loose connections, excessive lubricating
grease on the meter, or debris on the meter. It may also be a problem with the
wrong voltage or wrong type of meter. For these types of problems, the Meter
Technician can correct the problem and then the TNS Operator can re-search
the existing entry in the Temp Meter database.
Inaccuracy in Search Mode
There are three search modes used to search a meter. The fastest method,
Advanced Search, may not find a path due to noise or other harmonics. If
problems occur using the Advanced Search method, the TNS Operator can
change the entry in the SubProduct table for the type and model of the meter
to use Logical Elimination or Amplitude Summation on the new search to
improve the chance of a successful path identification. The TNS Operator can
then re-search the meter and the change in the SubProduct table will cause
TNS to select the new search mode.
Defective Meter
It is possible that a meter is defective. If the Meter Technician replaces a
defective meter, the TNS Operator must enter the new meter serial number
into the Temp Meter database and search for the new serial number.
153
General Troubleshooting Procedures for Failed Searches
After the utility searches for meters, some meters may fail the search
process. While the exact process for recovering from a search failure varies
depending on the failure, this section provides a general approach to help
guide the TNS user through trouble isolation and resolution.
There are a number of problems that can cause a meter search to fail.
Specific procedures vary depending on the exact nature of the failure. The
section, Why Meters Fail on page 149, details the general causes of meter
search failure and how to address specific failures. The problem the TNS
Operator has is that for a number of the problems, the exact cause is not
obvious. For this reason, DCSI has created a general process to help isolate
problems with failed meters. The process allows the TNS Operator to
exhaust all possibilities prior to dispatching a meter technician to the
customer site.
Failed Meter Search Process
Phase I - Pre-Dispatch
Yes
Abort troubleshooting
and begin AMR setup.
Successful
Search?
No
View error codes in Temp Meter
Misc. If TNS problem, fix tables and
re-search.
Re-search all meters.
Failed Meter Search Process
Phase II - Tech Dispatch
Visually inspect/correct
environmentals of path and
meter….corrosion, loose
connections, excessive lubricant
grease, debris in/on meter.
Re-search meter.
Call into TNS Operator and arrange
for test/search of neighboring meter
Review Notification Log in SCE
Maintenance for substation
problems.
Replace meter.
Enter new meter in TNS.
Search new meter.
Multi-Update/Sub - Change path to
global search within sub.
Re-search.
Contact DCSI Customer Care.
Multi-Update/City-Sub Configure City-Sub and
Re-search over multiple subs.
If Advanced Search, change
SubProduct Table Search Mode to
Logical Elimination or Amplitude
Modulation.
Re-search meter.
Search or read neighboring meter to
aid meter tech in trouble isolation.
View Search History Log.
Dispatch meter tech.
154
When meters fail the search process, there are a number of tools and
processes the TNS Operator may use to resolve the problem and search the
meter successfully into the Meter database. TNS may provide error messages
that accompany the failed meter record in the Temp Meter database. These
error messages provide the TNS Operator with information relating to a
failure. With some failures, there may be no error message or information
available, and the TNS Operator must rely on general processes to isolate the
problem.
Identifying and Viewing Error Codes for Failed Meters
The first step in diagnosing a group of failed meters is to pull up the list of
Temp Failed meters and review the status of each meter.
1.
Open the TNS Metering Maintenance tool bar by following the menu
path Start > Programs > TNS Metering Maintenance > TNS
Metering Maintenance.
2.
Click the Failed Temp Serial Number Maintenance
open the Temp Failed/Non-Failed Interface window.
button to
From the Temp Failed/Non-Failed Interface window, the TNS
Operator can view the failed meters.
155
3.
Click the Enter/Execute Query button twice to query all failed
records.
To see a specific entry, click the Enter/Execute Query button once,
type query data in the Serial Number field, and then click the
Enter/Execute Query button a second time to see the results. If the
table contains the serial number searched, it will show just that
serial number in the list.
You can enter “< or >” before the serial number to find ranges of
Failure
Description
Example
TNS
Failures that occur because of
TNS table problems.
SCE
Failures that occur because of a
substation problem.
RCE
Failures that occur because of
the meter or the path to the
meter.
Type/model not in
Product/SubProduct tables or
time-out.
Substation equipment is down,
bad hardware, phase down, blown
fuse.
Meter is not on the specified path
or substation.
There are three areas of failures when searching meters into TNS.
TNS categories include TNS, SCE, and RCE.
Meter Search Failure
Order of Trouble Isolation
Isolate/correct TNS failures
Isolate/correct SCE failures
Isolate/correct RCE failures
156
When troubleshooting a large number of failed meter searches, it is
best to start with the TNS failures, then work on the SCE failures, then
complete the RCE failures. This process flow will help the TNS
Operator correct problems in an organized flow working toward the
final steps in which a technician must be dispatched to a customer site.
The example above shows all failed meters in the TNS Temp Meter
database.
4.
Scroll to the right in the window, to view the columns for the TNS,
SCE, and RCE error codes.
The TNS, SCE, and RCE columns appear in the upper right corner of
the window after scrolling to the right.
5.
To view all TNS failures, click the Query button once, enter “>0” in
the TNS field, and then click the Query button a second time to see the
results.
157
The Temp Failed records with TNS failures will appear if any TNS
failures exist in the Temp Failed records.
6.
Double-click in the TNS field with the 1030 TNS error code listed,
TNS will open the Response Detail window that details the error
code.
The Response Detail window provides a description of the error
code. Note that the 1030 response means the Type/model is not in
the X-Ref table. The TNS Operator must correct this problem and
re-search the meter.
NOTE
The TNS, SCE, or RCE values must be greater than 0 (zero) before the
Response Detail window will display an error.
Repeat the previous steps to isolate failures codes for the SCE and
RCE.
158
REMEMBER
By working from TNS to SCE to RCE, the TNS Operator can minimize the
potential for dispatching a technician for problems the technician cannot
solve.
Re-Searching All Meters
The next logical step in the process of troubleshooting failed meter searches
is to have TNS attempt to re-search the meters. TNS can circumvent transient
problems such as temporary communication problems simply by trying the
search a second time.
From the Temp Failed/Non-Failed Interface failed view, view all TNS
failures by clicking the Query button twice.
Click the Re-Search All button to research all serial numbers.
A confirmation
window appears.
Click the OK button to
confirm the re-search.
159
The section, Verifying Meters Searched on page 141, provides instructions
for monitoring the search process. Wait until the re-search is completed
before proceeding to the next step in the troubleshooting process.
Checking the Notification Log in SCE Maintenance
To ensure that nothing is wrong with the substation at the time of the
search, the TNS Operator can check the Notification log. The Notification
log provides historical information about the status of the substations. If a
substation was off line, or not working properly during a search, a message
in the log may indicate the problem.
Access the SCE Maintenance with Command View window by clicking
the SCE Maintenance with Command View
button on the SCE
Maintenance tool bar (Start > Programs > TNS SCE Maintenance > TNS
SCE Maintenance).
160
Click Logs > Notification Log to open the Notification Log in the Event
Viewer window.
Review the Notification log and look for any problems with substations
during the search process. If no problems exist, continue with the global path
search.
Multi-Update/Sub for Global Path
The next logical step in the process of troubleshooting failed meter searches
after re-searching the meters is to expand the search. Initially, the TNS
Operator should attempt a global path search on the same substation.
161
Complete the following steps to expand the search and perform a global
path search after re-searching failed meters.
1.
From the Temp Failed/Non-Failed Interface failed view, view all
TNS failures by clicking the Query button twice.
All the Temp Failed records will appear in the window.
2.
Click the Update All Records
button.
A Forms window will appear asking whether to perform a City-Sub
or Sub update.
NOTE
The Sub and City-Sub path changes will apply to every meter listed in
the current query. The TNS Operator must query to the screen only the
records to change.
3.
162
Click the Sub button to change the path to a global path.
From the Multi-Record Path Update window, the TNS Operator can
select options to perform a global search, or change the substation to a
new one if necessary.
4.
Enter the expanded (or changed) search criteria for all the Temp Failed
meters.
5.
Click the Apply Updates
button to apply the changes.
A confirmation screen appears confirming that all Temp Failed
records must be updated.
6.
Click the OK button to confirm the update.
The Multi-Record Path Update window stays on the screen.
163
7.
Click the Exit button to exit back to the Temp Failed window.
Notice that all of the Buses, Feeders, Phases, Signal Modes and
Detection Points are set to global search criteria.
8.
Re-search all the failed meters by following the steps in
Re-Searching All Meters on page 159.
Change the Search Mode from Advanced Search
The next logical step in the process of troubleshooting failed meter
searches, after performing a global search, is to change the search mode to
one that is more accurate. The Advanced Search mode is fast, however, not
as accurate as the Logical Elimination and Amplitude Summation search
modes. If TNS is set up to use Advanced Search for a type and model of
meter, change the search mode type to Logical Elimination or Amplitude
Summation and re-search the meter.
NOTE
The TNS Operator should know the type and model of the meters. If
uncertain about the type and model entered, the TNS Operator can
search the X-Ref table for the serial numbers and verify the types and
models listed for the failed meters.
The example provided in the following steps will use the following
information:
164
Sub Type
Meter Type/Model Existing Search Mode
New Search Mode
AS93
21/51
Logical
Elimination
Advanced Search
REMEMBER
TNS looks up the serial number in the X-Ref table. From there, TNS reads
the suspected type and model for the meter. TNS then looks up the type
and model in the SubProduct table to determine the search mode to use
for the meter. To change the search mode, the TNS Operator must know
(or look up) the meter type and model, and change the search mode for
that type and model in the SubProduct table.
Search Search
Mode
Type
0
1
4
0
0
1
Value Description
Speed
Meters that Support
Logical Elimination
Medium All
All
Advanced Search
Fastest
New meters only (not LCT,
MIT, IMT1, and IMT2)
Complete the following steps to change the search mode.
1.
Open the Sub-Product table by clicking the SubProduct
button
on the TNS System Administration tool bar (Start > Programs > TNS
System Administration > TNS System Administration).
Find the meters’ type and model. The example details type 21, model
51 for Substation model AS93.
2.
Change the Advanced Search (Search Mode 4, Search Type 1) to
Logical Elimination (Search Mode 0, Search Type 0).
The items in the SubProduct table display when the TNS Operator
opens the SubProduct table.
REMEMBER
The SubProduct table lists each type and model for every model of
substation defined. The TNS Operator must be careful to select the
correct substation model prior to making the change.
165
3.
Click the Save button to save the update.
4.
Re-search all the failed meters by following the steps in
Re-Searching All Meters on page 159.
Multi-Update/City-Sub for Multiple Substation Search
The next logical step in the process of troubleshooting failed meter
searches is to expand the search beyond global searching to multiple
substations. The Multi-Update City-Sub function allows the TNS Operator
to define a range of potential substations to search. City-Sub will find a
meter if the meter technician incorrectly documented the substation for a
meter. City-Sub is particularly useful in areas where it may be difficult to
determine which substation serves a customer.
TIP
Refer to Chapter 12, City-Sub Maintenance in the TNS End User Guide
Rev D for more information.
The first step in running a City-Sub search is to set up potential substations
into a City-Sub group. The TNS Operator can then select that group of
substations for the City-Sub search.
166
Complete the following steps to run a City-Sub search.
1.
Open the TNS City-Substation Maintenance application by following
the menu path Start > Programs > TNS City-Sub Maintenance >
CitySub.
2.
Click the Add New City
new city definition.
3.
Type the city name in the New City Name field.
4.
Click the Add New City button.
button (in the Cities region) to add a
167
5.
Click the Exit button to return to the City-Substation Maintenance
window.
6.
Click the Add New Substation
button (in the Substations
region) to assign a substation to the city.
The Add Substations window appears.
7.
168
Select the substation from the list by double-clicking on each
substation to add to the city definition.
8.
Click the Exit button to return to the City-Substation Maintenance
window.
The substations should show under the city definition on the
City-Substation Maintenance window.
9.
Click the Exit
window.
10.
Return to the Temp Failed window.
11.
Click the Update All Records
button to exit the City-Substation Maintenance
button.
169
The following dialog box appears asking if would like to update
items for the city-substation path or for the substation path only.
12.
Click the City-Sub button to change the path to include multiple
substations in a city definition.
13.
Click the Query button twice to view the available city definitions.
14.
Highlight the City Name to use for the Search and click the Update
Records
records.
button to assign the City Name to the Temp Failed
A confirmation window appears.
15.
170
Click the OK button to confirm the assignment.
16.
Click the Exit button to return to Temp Failed window.
The Temp Failed window will not immediately reflect the changed
substation.
17.
Click the Query button twice to re-query all the Temp Failed records.
Notice that the Sub name for all the records is now Erie South*. The
asterisk indicates TNS has defined a city-sub for the meter.
18.
Re-search all the failed meters by following the steps in Re-Searching
All Meters on page 159.
171
Search Neighboring Meter
The search results of a neighboring meter are a valuable trouble isolation
tool if the utility must dispatch a Meter Technician to a customer location.
Search a meter in the same vicinity and path as the meter in trouble to
validate the substation and path are in working order.
REMEMBER
If TNS has already searched a meter into the Meter database, the TNS
Operator can search the meter without disrupting the live Meter
database. This is done by selecting the Search Only parameter when
adding the meter to the Temp Meter database.
View Search History Log
The Search History log can provide valuable information about the reason
for a search failure. The Search History log can indicate to the TNS
Operator whether the substation heard the meter a little or not at all. The
Search History may also indicate that TNS could not establish a clear path
for the meter. Appendix B Decoding Search History Log Files details the
interpretation of Search History Logs.
Dispatch Meter Technician
After exhausting the resources available within TNS, the utility must
dispatch a technician to the meter site. The technician should visually
inspect the area around the meter and the path leading to the meter for signs
of corrosion, loose connections, excessive lubricant grease, or debris. After
the technician validates these conditions, the TNS Operator should
re-search the failed meter by following the steps in Re-Searching All
Meters on page 159, selecting only a single meter for the search.
If the search continues to fail, replace the meter with a new one. The TNS
Operator must input the new meter’s serial number in TNS and restart the
search process. If the new meter does not search into TNS, the TNS
Operator should contact DCSI Customer Care ([email protected] or
1-800-892-9008) for further assistance.
172
Batch Searching Meters into TNS
When a utility purchases meters, utility personnel will configure, document,
and install the new meters at customer locations. Once installed, the TNS
Operator must enter the meters into the TNS Meter database.
When the utility installs large numbers of meters in a relatively short time or
desires to integrate existing Customer Information System (CIS) or billing
system data into TNS, the utility will use the batch method for input to TNS.
Batch Search Process
the TNS Meter database.
When the TNS Operator must search a large numbers of meters or export
meter numbers from an existing database, the batch search can provide an
efficient mechanism for searching. The TNS Operator must develop an
understanding of the process to effectively use batch searching.
When a utility purchases and installs meters, the meter configuration in TNS
must match the physical characteristics of the installed meters.
Receiving Meters at the Utility - Preliminary Search Activities on page 102
explained the preliminary updates made to TNS to prepare for meter
installation.
Searching Meters into TNS on page 115 explained how to interactively enter
meters for searching into the TNS database.
This section will help you develop an understanding of the process for
entering a large number meters into TNS through the use of a batch search
file. The TNS Operator can also use the batch search file formats as a
template for exports from an existing CIS or billing system.
173
When searching a batch search
file of meters into TNS,
documentation and
communication between the
meter shop and the TNS
Operator is critical to
successful configuration of the
system. Searching Meters into
TNS on page 115 discussed
what fields the TNS Operator
must populate in TNS to
perform certain functions. The
utility must decide how much
information to track in TNS
based on the functions desired
and how much information to
track in the existing CIS or
billing system. Once the utility
decides what information to
track, it may improve
efficiency, depending on the
utility’s processes, to export
information common to both
systems from the CIS or billing
system for import into TNS.
Batch Search Meters into
TNS Process Flow
Utility decides what information to
track in CIS and TNS
Export information from existing
CIS (optional)
Manipulate/merge new
information for TNS
Ensure format for batch file is
consistent with TNS specs
Verify Product, SubProduct
Tables have types/models listed
Insert serial numbers (ranges)
into X-Ref Table
Schedule/run batch file in TNS
Batch Job Scheduler
Review results of Pre-Tiq batch
Once the utility exports
log file
information from the CIS or
billing system, the TNS
Review TNS Temp Fail Meter
Database
Operator may need to
manipulate or merge
Troubleshoot discarded (Pre-Tiq)
information common only to
and failed meters
TNS into a batch search file for
TNS import. The TNS Operator
must ensure the batch search
file format is consistent with
the specifications for import into TNS. As with interactive searches, the
TNS Operator must update the Product, SubProduct, and X-Ref tables as
defined in Searching Meters into TNS on page 115. The TNS Operator then
schedules and runs the batch search file in TNS. While the normal
troubleshooting procedures (defined in the Dealing with Failed Searches
on page 149) are common to both interactive and batch searches, the batch
search process creates an additional log file helpful in diagnosing problems
with the batch search file itself.
The following diagram shows more detailed steps the utility personnel and
TNS take to enter meter records into the Meter database when a batch
search file is used.
174
Human Processes
TNS Processes: “Search In” Meters
Utility
Purchases
AMR
Meters
Meter Tech
configures,
installs and
documents
meters
Merge/
manipulate
CIS export
file for TNS
specs
Verify in TNS, Sub
Product Table with
Type & Models
represented in
purchase
(optional).
Input in TNS, Meter
(manditory) with Type/
Model into Product
Type Model Cross
Reference (X-Ref)
Table.
Program Location:
\users\xxx\batch\PreTIQ.Log
Program Location:
Batch Scheduler
(Batch file in \users\xxx\batch)
Verify in TNS,
Product Table with
Type & Models
represented in
purchase (optional).
Documentation
from Meter Tech
feeds creation of
input file for TNS
and/or CIS.
Possible
export of
CIS
information.
“Search In”
process
started with
batch file
Phase I
Serial Number from
X-ref table
n
a tio
alid te r
d v r Me
e
il
o
t fa e m p
en
e m y in T se
ta t
a
h s lrea d atab
c
t
a
D
B a te r
Me
table
t in X-ref
Meter no
Meter in
X-ref tabl
e
PreTIQ log
- Failed phase I
check
- Failed Meters
(phase I)
Temp Meter
Database
- Non-Failed Meters
N on-F
Phase II
- Find Path
- Read Type & Model
Schedule
batch job in
TNS
a iled
M ete
n ly
rs O
- Failed Meters
(phase II)
or
r
mo
le m
p rob n pro ble blem
NS
1. T bstatio ath pro
u
p
2. S eter or
3. M
Program Location:
Meter Misc.
Me ter Fou nd
and Typ e and
Mo del Fam ily
on me ter ma tch
for Serial #
Permanent Meter
Database
Search History Log
SHyyyymmdd.dat
Creating the Batch Search File
When the utility needs to input a large number of meters into the Meter
database, the most efficient method is to use a batch search file.
The format of the batch search file is very specific. The TNS Operator must
develop the batch search file to the specific format or the batch job process
will not successfully populate the Meter database as desired.
Batch Search File Format Overview
TNS runs the batch search file to insert information into the Temp Meter
database for subsequent searching of meters into the Meter database. The
batch search file may contain any number of records, but the records must be
in a specific format in order for TNS to accurately populate the Meter
database fields.
The batch method requires the creation of a text file with file extension .dat.
The TNS Operator can create the dat file in any ASCII text editor application,
such as Microsoft Windows Notepad or WordPad (for larger files).
NOTE
The file must contain four consecutive lines of text for TNS to read each
meter into the database. The order of the lines as listed in the following
table is important.
175
There are four record types representing line formats the TNS Operator can
define in the batch search file. The record types or line formats include:
REMEMBER
Record Type/Line
Format
Description
PATH
SNDATA
PORT
METER
Defines the path of the meter
Defines the Serial Number and other meter information
Defines a specific port (0, 1, or 2)
Defines the meter on the specific port
Searching Meters into TNS on page 115 showed how to enter
information interactively into the Temp Meter database. The four line
formats represent the sections of fields on the Temp Meter Misc
window.
Each record in the batch search file has the same first four fields. Those
fields are:
Position
Common Line Format
Field Element
Value
1
2
3
4
Process Type
Transaction Type
Record Type
Serial Number
Always BATCH
ADD or *MOD or *DEL
PATH or SNDATA or PORT or METER
Serial number of meter
These common fields are shaded in the tables on the following pages.
When the TNS Operator enters “ADD”, the record commands TNS to add
the record to the Temp Meter database. When the TNS Operator enters
“MOD” or “DELETE”, the record commands TNS to update or delete the
(permanent) Meter database.
176
Transaction Type
Database Impacted
Value
ADD
Temp Meter database
MOD
Meter database
DEL
Meter database
Adds a new entry to the Temp
Meter database
Modifies an existing entry in
the Meter database
Deletes an existing entry in
the Meter database
PATH Line Format
The following table defines the ten items that make up the path line of a batch
search file.
Position
Path Line Format
Field Element
1
2
3
4
5
Process Type
Transaction Type
Record Type
Serial Number
Substation Name
6
7
Bus Name
Feeder Name
8
9
10
Phase
Signal
Detection Point
Value
Always BATCH
ADD or *MOD or *Delete
PATH
Substation name in Substation table
(case sensitive)
Bus name in Substation table | ALL
Feeder name in Substation table | ALL|
NONE
A | B | C | ALL
LG | LL | BOTH
A | B | C | N | ALL
The following is an example Path line from a batch search file.
1
2
3
4
5
6
7
8
9
10
BATCH,ADD,PATH,1720349,SARDIS,BUS1,ALL,ALL,LG,ALL
Notice that a comma separates each position. A space between two commas
represents a blank field value for the relative position.
177
SNDATA Line Format
The following table defines the 20 items that make up the SNDATA line of
a batch search file.
Position
SNDATA Line Format
Field Element
1
2
3
4
5
6
7
8
9
10
11
12
13
Process Type
Transaction Type
Record Type
Serial Number
Type
Model
Premise ID Number
Protective Device
Transformer Grid
Installation Date/Time
District Number
Device Location
Active Flag
14
15
16
One-Way Device Flag
Comm Type
Device Type
17
18
19
20
Connect Type
Connect Date
User1
User2
Value
Always BATCH
SNDATA
Leave blank
Leave blank
Assigned by utility
Assigned by utility
Assigned by utility
TNS assigns
Assigned by utility
Assigned by utility
Y (active) | N (inactive)
blank defaults to Y
Y | N blank defaults to N
Leave blank
Leave blank…1 if service disconnect
meter
Leave blank
TNS assigns
May be blank - user defined
The following is an example SNDATA line from a batch search file.
1
2
3
4
5-12 13 14 15-20
BATCH,ADD,SNDATA,1720349, , , , , , , , ,Y,N , , , , , ,
Notice that a comma separates each position. A space between two
commas represents a blank field value for the relative position.
178
Port Line Format
The following table defines the 16 items that make up the Port line of a batch
search file.
Position
Port Line Format Field
Element
1
2
3
4
5
Process Type
Transaction Type
Record Type
Serial Number
Serial Port
6
7
8
9
10
11
Premise ID Number
Install Date/Time
Modify Date/Time
Port District Number
Port Device Number
Active Flag
12
13
14
15
16
Device Type
Connect Type
Connect Date
PortUser1
PortUser1
Value
Always BATCH
PORT
Port on transponder 0 | 1 | 2 must be port
0 on first record added; 1 and 2 may be
added after 0
Assigned by utility
Leave blank (TNS assigns)
Leave blank (TNS assigns)
Assigned by utility
Assigned by utility
Y (active) | N (inactive)
blank defaults to Y
Leave blank
Leave blank
TNS assigns
The following is an example Port line from a batch search file.
1
2
3
4
5 6-10 11 12-16
BATCH,ADD,PORT,1720349,0, , , , , ,Y, , , , ,
Notice that a comma separates each position. A space between two commas
represents a blank field value for the relative position.
179
Meter Line Format
The following table defines the 16 items that make up the Meter line of a
batch search file.
Meter Line Format
Field Element
Position
1
2
3
4
5
6
7
8
Process Type
Transaction Type
Record Type
Serial Number
Serial Port
Customer Acct
Number
Rate Class
Meter Type
9
10
11
12
13
14
15
16
17
Meter Number
Route ID
Cycle Number
Initial Reading
Offset Reading
Meter Class
Offset Recalc Flag
MeterUser1
MeterUser2
Value
Always BATCH
METER
The port of the transponder (i.e. 0,1,2)
Assigned by utility
The rate class assigned by the utility
The meter type to associate with the
conversion table. The system uses the
default if left blank.
Assigned by utility
Assigned by utility
Assigned by utility
Leave blank
Leave blank
Required for Interval Meters 60 | 30 | 15
Leave blank. Default is 60.
The following is an example Meter line from a batch search file.
1
2
3
4
5
6
7 8
9
1011 12-17
BATCH,ADD,METER,1720349,0,7102, ,IMT3H,1720349, ,1, , , , , , ,
Notice that a comma separates each position. A space between two
commas represents a blank field value for the relative position.
180
Common Batch Search File Format Problems
There are several problems that can occur from invalid information in the
batch search file. The TNS Operator must meticulously manage the
information in each position and line of the batch search file. The following
table details some of the problems the TNS Operator may experience with the
batch search file.
Problem
Result
TNS path names do not
exactly match
Meter Type name does not
exactly match
Serial number already in
Meter or Temp Meter
database on ADD
Error in Pre-TIQ log file that serial number has an
invalid path.
Adds meter with default as meter type, but will not
convert data properly.
Error in Pre-TIQ log file that meter is already in
database message.
Creating the Batch Search File Using the Spreadsheet
Template
A spreadsheet is a valuable tool for organizing information to feed into a
batch search file. Spreadsheets allow the TNS Operator to view all positional
information with each position occupying a column in the spreadsheet. The
spreadsheet view allows the TNS Operator to quickly view any problems
with positional information in the batch search file.
DCSI has created a spreadsheet with macros for the specific purpose of
quickly generating batch search files. The name of the spreadsheet is
searchfile.xls.
For more information about using the searchfile spreadsheet to create the
batch search file, see Appendix A, Searchfile Spreadsheet Template.
Running the Batch Search File
After the creating the batch search file, the TNS Operator will execute the
batch search file as a job in TNS. This section explains how to use the Batch
Job Scheduler to execute the search file job in TNS.
Starting the Batch Search Job in the Batch Job Scheduler
The TNS Operator must place the DAT search file in the batch directory of
TNS. The batch directory is likely in the folder \users\batch. The TNS
Operator must then initiate the batch search file as a job in the TNS Batch Job
Scheduler.
Prior to submitting a batch search file to the Batch Job Scheduler, the
substations represented by the meters in the batch search file must show
either a Connected/Online or Disconnected/Configured status for the Sub
State and Sub Status fields in the SCE Maintenance with Command View
window.
181
Open the SCE Maintenance with Command View window by following
the menu path Start > Programs > TNS SCE Maintenance > TNS SCE
Maintenance.
The sample batch search file used in the example has meters from the
Peters substation. Notice the Sub State and Sub Status field values for
Peters is Disconnected/Configured.
TNS uses the Pre-TIQ.log file for error messages generated from the batch
job. TNS appends information to the Pre-TIQ.log file each time it runs a
batch search job. To keep the file readable, delete the file before running
each batch search file. Renaming the old file is also an option if the TNS
Operator desires to keep the old log data.
Complete the following steps to initiate the batch search file as a job in the
TNS Batch Job Scheduler.
1.
182
Open Windows Explorer and locate the Pre-TIQ.log file in the
\users\batch directory.
2.
Delete the Pre-TIQ.log file.
3.
Click the Batch Scheduler
button, from the Metering
Maintenance tool bar (Start > Programs > TNS Metering
Maintenance > TNS Metering Maintenance), to open the Batch Job
Scheduler window.
4.
Click the Add Job
Window.
button to open the Batch Job Schedule - Add
183
5.
Click the Browse button to select the name of the search DAT file.
If opening on the TNS Master Station, TNS will display the Open
window in the Batch directory where TNS expects to find the search
dat file for execution. If opening from a TNS client, you must go
across the network or type the file name manually.
6.
Select the search dat file (searchfile.dat in the example) and click the
Open button.
Notice the Command field currently displays:
BATCHINSERT(100…'|')
7.
To populate the command line with the search DAT file name, click
the Initial Job Status drop-down arrow and reselect On-Hold.
By re-selecting the Initial Job Status, TNS will update the
Command line with the information necessary to run the job.
184
NOTE
The TNS Operator can also force populate the Command field by simply
pressing the Tab key.
Notice TNS populated the Command field with:
BATCHINSERT(100,'DCSI',1,'TNS|searchfile.dat');
Scheduling the Job in the Future
The TNS Operator may schedule the job to run at a future time by specifying
the desired time in the Start Date/Time fields and selecting Active from the
Initial Job Status drop-down box. The TNS Operator may also leave the
Initial Job Status as On-Hold and manually start the job (as demonstrated in
Starting the Batch Job Immediately on page 186).
Scheduling a Recurring Interval Job
The TNS Operator may also schedule the job to run at certain intervals like
every evening at 20:00 (military time). Recurring interval searches can be an
effective tool particularly if the CIS or billing system exports a pre-formatted
search DAT file to the proper location on a daily basis.
NOTE
When TNS completes the DAT batch file, it renames the file from a .dat
extension to a .tad extension.
185
Starting the Batch Job Immediately
The TNS Operator may run the batch search file immediately by leaving
the Initial Job Status as On-Hold and proceeding with the remainder of the
following steps.
8.
After completing the updates, click the Add Job
button.
TNS prompts for confirmation to add the job to the scheduler.
9.
186
Click the OK button to accept the add and open the Batch Job
Scheduler - Add Window.
10.
NOTE
Click the Return
window.
button to return to the Batch Job Scheduler
Notice TNS added the job to the list. The command line indicates the
searchfile.dat file is the batch job to run. Also notice the status of the
job is HOLD.
187
11.
With the job highlighted, click the Run Job Now
button.
A window appears to confirm running the batch job.
12.
Click the OK button.
The batch job submission is now complete.
Troubleshooting Batch Searches Using the Pre-Tiq Log File
TNS runs a batch search file to insert information into the Temp Meter
database for subsequent searching of meters into the Meter database. The
batch search file may contain any number of records, but the records must
be in a specific format in order for TNS to accurately populate the Meter
database fields.
Several conditions may cause a record not to make it into the Temp Meter
database. When the batch search process meets one of these conditions, the
batch job outputs an error message to the Pre-TIQ.log file found in the
\user\batch directory.
188
Batch Search Add Validation Process
The following diagram details the validation checks performed by the batch
search process for Adds. The batch search process logs items that fail the
validation checking in the Pre-TIQ.log file. The batch search process does not
log items that pass the validation checking.
Batch Search Add Validations
Truncate all fields to valid length
For Add Path,
1. Ensure SubID, BusID, FeederID
are defined in TNS
2. Ensure SerialNumber is not
already in Temp Meter Misc or Meter
Misc
For Add SerialNumber, ensure that
serial number is in Temp Meter Misc
or Meter Misc (from previous Add
Path command)
For Add Port, ensure
1. Port does not already exist in
Temp Meter Misc or Meter Misc and
2. Port equal or greater than 0
3. SerialNumber exists in Temp
Meter Misc or Meter Misc
(from previous Add Path command)
For Add Meter, ensure
1. Meter does not already exist in
Temp Meter Misc or Meter Misc and
2. Port exists in Temp Meter Misc or
Meter Misc
(from previous Add Port command)
3. SerialNumber exists in Temp
Meter Misc or Meter Misc
(from previous Add Path command)
Program Location:
Batch Scheduler
(Batch file in \users\batch)
Log File Location:
\users\batch\PreTIQ.Log
PreTIQ log
- Failed
validation check
Temp Meter
Database
All checks passed
189
Acronyms
ADLC
Asynchronous Data Link Communication
AMR
Automatic Meter Reading
AP
Alternate Pathmaps
ASCII
American National Standard Code for Information Exchange
ATM
Asynchronus Transfer Mode
BPA
Backplane Assembly
CCA
Card Cage Assembly
CCE
Central Control Equipment
CIS
Customer Information System
CLI
Command Line Interface
CMT
Commercial Meter Transponder
CPSA
CRU Power Supply Assembly
CRA
Correlation Receiver Assembly
CRC
Cyclic Redundancy Check
CRMA
Correlation Receiver Multiplexer Assembly
CRPA
Correlation Receiver Processor Assembly
CRU
Control and Receiving Unit
CSR
Customer Service Representative
CT
Current Transformer
DCPA
Direct Current Power Assembly
DCSI
Distribution Control Systems, Inc.
DDS
Digital Data Services
DP
Diagnostic Pending
DPA
Distribution Panel Assembly
DS
Diagnostic Set
DSI
Disconnect Switch Interbase
EMA
Electronic Metering Assembly
EOM
End of Message
FEP
Front-End Processor
GUI
Graphical User Interface
IC
Incomplete IMT/CMT Data
ILS
Integrated Load Survey
671
Acronyms
IMA
Inbound Multiplexer Assembly
IMT
Integrated Metering Transponder
IP
In Progress
IPU
Inbound Pickup Unit
ISP
Internet Service Provider
KWH
Kilowatt Hours
LAN
Local Area Network
LCT
Load Control Transponder
LS
Load Survey
MIT
Meter Interface Transponder
MS
Master Station
MSFE
Master Station Field Equipment
MTU
Modulation Transformer Unit
NA
Invalid Data
NS
Register Not Supported
ODBC
Open Database Connectivity
OFIA
OMU Fiber Optics Interface Assembly
OK
Successful Read
OMU
Outbound Modulation Unit
OA
Open Air
OPA
Outbound Processor Assembly
PD
Partial Data
PE
Pending
PR
Pending Retry
QC
Quality Code
RC
Reasonability Check Failed
RCE
Remote Communications Equipment
RI
Reset In Progress
RL
Register Length Invalid
RM
Read Meter
RO
Retry Override
RPA
Receiver Processor Assembly
S&T
Substation & Transmission (Engineer)
SCADA
Supervisory Control and Data Acquisition
SCE
Substation Communications Equipment
672
Acronyms
SCPA
Substation Communications Processor Assembly
SDC
Service Disconnect/Connect
SP
Substation Status
STS
Substation Test Set
TC
Total Consumption
TD
Total Demand
TNS
TWACS Net Server
TOU
Time of Use
TP
Tamper Pending
TS
Tamper Set
TWACS
Two-Way Automatic Communication System
VPN
Virtual Private Network
WAN
Wide Area Network
ZC
Zero Crossing
673
Acronyms
674
Glossary
Automatic Meter Reading (AMR)
Electronic accumulation and transport of meter data.The process of reading a meter from
a remote location at scheduled times or on demand.
Alternate Pathmaps (AP) search
This search is the basic method used in TWACS to locate the communication path of a
transponder. An AP Search will find a new communication path for a transponder whose
communication path has changed since the last time it was searched into the database.
This function is activated automatically in AMR or can be activated manually on a
selection of transponders.
binning data
Read data stored in the registers of the meter.
Blink count
The number of outages from a customer’s location. It is the number of times a
transponder experiences loss of power for more than five cycles (ten half cycles).
BLP switch
A BLP switch is integrated with the meter. BLP switches are scheduled through the TNS
Job Scheduler using the Service Disconnect/Connect Manager.
bus
An electrical pathway along which current is distributed.
bus identification
Identifies the substation bus to which DCSI’s equipment is connect.
Central Control Equipment (CCE)
The equipment at the utility's home office where the TWACS Net Server (TNS) resides.
Provides system control, data storage, and user interface functions for the system. See
also TWACS Net Server.
Command Line Interface (CLI)
A means of communication between a program and its user, based solely on textual input
and output. Commands are input with the help of a keyboard or similar device and are
interpreted and executed by the program. Results are output as text or graphics to the
terminal.
Commercial Meter Transponder (CMT)
A TWACS AMR transponder for installation in a commercial meter for transmission via
the power line.
675
Glossary
cold restart
Initializes all memory that contains downloaded information and memory that is used
for MS/SCE transaction processing. Historical logs are retained. The hardware ports
and internal timers are also reset. Communication with all SCE equipment is verified.
Upon cold start completion, the SCE must be reconfigured by the Master Station
before RCE communication can be resumed. (See warm restart.)
Correlation Receiver Multiplexer Assembly (CRMA)
Transfers the analog inbound signals from the IPU to the CRPA.
Correlation Receiver Processor Assembly (CRPA)
The CRPA is a master/slave device that resides on the VMEbus. It receives commands
from, and responds to, the SCPA. It controls a Correlation Receiver Multiplexer
Assembly (CRMA) assigned to it by the SCPA TCF logic, and acquires TWACS
inbound messages to support the CRU function.
Control and Receiving Unit (CRU)
The CRU directs all incoming and outgoing communications at the substation level
and is responsible for all communication between the TNS, substation, and meter. The
CRU is subordinate to the CCE and includes up to 25 assemblies.
Current Transformer (CT)
An electrical device that increases or decreases the supply current output.
Customer Information System (CIS)
A computer database that utilities use to keep track of their customer information
(name, address, phone, meter serial number). Often includes bill printing
functionality.
delay
The number of minutes after the interval has occurred before the SCE attempts to send
a time sync command to the RCE.
detection point
Identifies the specific conductor on which the inbound signal is detected. This point is
identified as either phase A, phase B, phase C, or neutral.
Direct Current Power Assembly (DCPA)
The DCPA furnishes the DC power for the OMU low-voltage circuits and monitors
the input line voltage. This module is connected to the OMU 3-phase input line
voltage through 2-amp fuses.
676
Glossary
Disconnect Switch Interbase (DSI)
A DSI switch is mounted between the meter and the base of the meter. DSI switches
allow you to continue using the existing meter for AMR, after you attach the switch. DSI
switches can be scheduled directly at the meter or through the TNS Job Scheduler using
the Service Disconnect/Connect Manager.
Electronic Metering Assembly (EMA)
An electronic assembly integrated into an electric meter to add TWACS communications
capability to the meter.
feeder identification
Identifies which feeders are connected to which bus(es).
firing angle
The place on the sine wave where the RTS places the TWACS signal.
Front-End Processor (FEP)
A small computer necessary to enable an IBM mainframe using SNA to communicate
beyond the limits of a traditional mainframe.
Graphical User Interface (GUI)
The use of pictures rather than just words to represent the input and output of a program.
The interface part of a software program that allows users to interact with the program
through the use of icons that represent program features.
KH
The watt-hour constant of the meter. The Kh value tells TNS the energy used for one
rotation of the dial or pulse. Mathematically, Kh is equal to the watt-hours divided by
disk revolutions.
Inbound Multiplexer Assembly (IMA)
Transfers analog inbound signal from the IPU to the RRA. The IMA contains the SPA.
Maximum of four per SCE.
Inbound Pickup Unit (IPU)
IPUs are Current Transformers (CTs) connected in series with a utility's metering or
relaying CTs and used for inbound signal detection. The inbound signal is part of the
phase current. The IPU picks up this current on its primary side. The secondary side is
terminated with a resistor, converting the current into a voltage. The voltage is then sent
to the CRU inbound receiver, where inbound signal detection takes place. Each phase
that has a TWACS inbound signal will have an IPU in its circuit.
677
Glossary
Integrated Metering Transponder (IMT)
The IMT is the RCE type which is an integrated combination of a single phase watthour meter and TWACS metering transponder electronics.
interval
How often the SCE sends the Set date/time command relative to the top of the hour.
interval data
A breakdown of consumption over specific intervals of time.
interval readings
Consumption deltas that express the consumption that occurred with a certain interval
of time. The IMT-3A supports hourly intervals.
load control
Temporary control of electrical usage at a premise in order to control peak usage by
the Utility company.
Load Control Transponder (LCT)
An electrical device connected to a unit that provides temporary control of electrical
usage at a premise in order to control peak usage by the Utility company.
load profile
Recording, storing, and analyzing consumption data over a period of time for a
particular installation.
Master Station (MS)
Complex which houses the CCE. See Central Control Equipment (CCE).
Meter Interface Transponder (MIT)
A surface mounted TWACS transponder for converting data from a commercial meter
for transmission via the power line.
Modulation Transformer Unit (MTU)
The MTU is the link between the power line and the OMU. The MTU decreases the
HV bus voltage to 480 VAC in order to power the OMU, and serves as the coupling
device for getting the outbound signal onto the bus. The OMU typically mounts on the
outside of the MTU.
on-demand reads
An unscheduled command to read a register.
678
Glossary
Outbound Fiber Optics Interface Assembly (OFIA)
The OFIA is a multiplexer board for communicating with the OMUs. The OFIA receives
and transmits messages from the OMUs by fiber optic links connected to the front edge
of the board.
Outbound Modulation Unit (OMU)
Acts in conjunction with the CRU to generate TWACS outbound signal messages. The
OMU is a microprocessor-based electronic controller which interfaces with the CRU and
the MTU. The OMU receives the outbound TNS commands through the CRU, translates
them to the TWACS format, and injects them on the substation bus through the MTU.
Outbound Processor Assembly (OPA)
Located inside of the OMU. Provides the interface from the OMU to the CRU through
fiber optic cables. Transforms digital information from the CRPA into an analog signal
by controlling the OSSA SCRs. The OPA sends an End of Message notice to the CRPA
upon outbound signal completion.
peak demand
Highest demand that occurs during the reporting period. For demand reads delivered
daily, the reporting period corresponds to the previous 24-hour calendar day. In cycle
billing interfaces, the reporting period is from the previous consumption billing date until
the current consumption billing date.
phase
The current supply conductors, other than the neutral conductor of a polyphase circuit,
that usually carry the designation phase A, phase B, or phase C.
Quality Code (QC)
An alphabetical code that indicates the status of the meter Read.
RCE Exchange
This exchange type is initiated by the Master Station to perform an RCE function. An
RCE exchange consists of a transaction from the Master Station requesting RCE
functions to be performed. This is followed by a transaction from the SCE containing the
response data. The respond transaction contains an execution status in the transaction
header and any requested RCE data when execution is successful.
receivers
Receivers are one-way devices, capable of receiving messages and performing control
functions only; they are not able to transmit messages back to the SCE.
Receiver Processor Assembly (RPA)
The RPA collects and transfers inbound digital information from RAA to CPA. The
RPA instructs the RAA to begin inbound signal collection. Maximum 4 per SCE.
679
Glossary
registers
Devices, such as transponders, located at a consumer's premises that collect and
transmit register data through TWACS.
Remote Communications Equipment (RCE)
The RCEs represent the bottom hierarchical TWACS equipment level. An RCE is
located at the customer site, which provide AMR and/or load management functions.
SCE Exchange
This exchange type is initiated by the Master Station to perform an internal SCE
function. An SCE exchange consists of a Master Station request transaction sent to the
SCE requesting a specific function. This is followed by a response transaction from
the SCE containing the requested data. The response transaction contains an
execution status in the transaction header and any requested data when execution is
successful.
signal mode
Identifies the path combination used during outbound communications. This
combination can be either line-to-ground or line-to-line.
Substation Communications Equipment (SCE)
SCE is the collective name for all substation equipment types (CRU, OMU, IPU,
MTU), and communication and power equipment, including hardware and software,
that comprise the mid-hierarchical level of TWACS. The SCE is the intelligent
interface between TNS and the remote meter modules in the TWACS power line
network. The SCE transmits and receives data and sends results back to the TNS.
There is no limit to the number of meters that each substation can read.
Substation Communications Processor Assembly (SCPA)
The SCPA is the top level of Substation Control processing assemblies. The SCPA is
the computation center of the SCE. The SCPA creates the application level request
transaction response to the Master Station, forwards response transactions, and allows
the reception and construction of link level communication frames. The SCPA
controls the SUA.
Substation Test Set (STS)
The STS is a portable field unit used to perform SCE-level diagnostics.
Time-of-Use (TOU)
A multiple tiered billing technique based on when the consumer uses the energy.
Total Consumption (TC)
The total electrical usage (in kWh) for the specified type of meter read.
680
Glossary
transaction
This activity defines data passed between the Master Station and the SCE during a
communication exchange. A transaction may contain a requested function to be
performed, the response data for the performed function, or a notification of a change in
the operational state of the SCE.
transaction header
Contained in all transactions exchanged between the master Station and the SCE. The
transaction header identifies the originator, receiver, function, priority, and expiration of
MS-SCE exchange transactions. With the exception o the Response Status, the
information in the transaction header remains unchanged by the SCE and is only used for
transaction processing.
transponders
Two-way field devices that can receive and send messages to and from the substation.
TWACS Net Server (TNS)
Chief component of the entire Two-Way Automatic Communication System. Manages
all collected metering and interval data as well as the connection between the utility and
the consumer’s premises.
Two-Way Automatic Communication System (TWACS)
A patented technology that allows the utility to send and retrieve information to and from
meters and other devices using the utility’s power lines as a communication network.
warm restart
Initializes the transaction buffer and the response buffers used for MS/SCE transaction
processing and any other data structures in volatile memory. All operational parameters
and downloaded tables remain intact. (See cold restart.)
Zero Crossing (ZC)
Point at which the voltage waveforms approach zero volts.
681
Glossary
682
Index
Symbols
.dat file 503, 507
.log file 503
assign two-way address 440
ATM 94
automatic conversion 256
Numerics
B
2 Flow2A batch mode 621
24hr No Pulse 323, 327
3-way jumper cable 60
A
acquisition Dt/Tm 275
add command 470
advanced search 111, 138, 153, 164, 652,
661, 663
alternate path maintenance 298, 308
alternate path search 309
Alternate Path Search log 314
Alternate Path table 297, 304, 309
Alternate Path Transaction log 317
Alternate Pathmap table 306
alternate pathmaps 292
alternate pathmaps search 675
Alternate Substation mapping 299
Alternate Substations table 299, 300, 309
Altimus 27, 28, 113, 123
amplitude summation 111, 138, 153, 164,
652, 656
AMR Calendar 195, 204, 212, 215, 227, 230,
231, 250, 297, 434, 436
AMR Calendar input file 206, 219, 222, 223
AMR Command List 205, 232, 234
AMR Command List queue 236
AMR Hourly applications 256
AMR hourly data history 12, 256, 257, 260
AMR hourly data history hourly data expanded graphic view 259
AMR hourly data history meter selection 261
AMR hourly usage 256, 260, 261
AMR IMT Command List 234, 237
AMR interval usage 261
AMR MIT/CMT/Altimus command list 232,
235, 237
analog private lines 94
AP search field 297
APM search 306, 309, 310
apply download 543, 544
appProperties 618, 621, 623
assign one-way address 400
Batch Add file 622
batch file 119, 267, 639
Batch Job Scheduler 181, 183, 192, 622, 644
Batch Operations/Maintenance 266, 271,
285
batch search 117, 119, 173
batch search file 174, 175, 177, 178, 181
batch search process 639
batched automatic meter reads 39
billing file 241, 242, 253
Billing personnel 5
billing read 230
blink count 16, 17, 18, 323, 326, 337, 342,
345
BTCHCVRT.DLL 605
budget billing 20
bus 30, 55
bus ID 140
bus-level IPU 55, 80
C
CBMRParser.class 618
Central Control Equipment 22
CENTRON 21, 27, 28, 113
check date/time 357, 359
CitySub 152
class 124
CMT-SX 23, 27, 28, 113, 123
CMT-Vectron 27, 28, 113, 123
cold load pickup 377
Com Server log 43
Command Delay 1 107, 133
Command Delay 2 107, 133
commercial meter 24, 27, 123, 195
Communication Server 38, 453
COMP 145
concurrent phasing 56, 57, 59, 60, 84
configuration key information 84, 550
configuration key maintenance 84
consolidated billing 20
consumption 26
Control and Receiving Unit 32, 36, 51, 52
convert data 258, 262
683
Index
Correlation Receiver Multiplexer and
Analog Assembly 53
Correlation Receiver Multiplexer Assembly
52
Correlation Receiver Processor Assembly
52, 53
CSR Manager 5
custom billing file 241
Customer Care 8
Customer Engineer 7
Customer Service Representative 5
cutoff time 214
cycle 123
cyclic redundancy check 658
D
daily billing read 206
daily consumption display 258
daily shift TC 126, 208, 213, 215, 227, 325,
433
daylight saving time 501, 547
Autumn procedure 564
Set SCE Date 559, 568
Spring procedure 555
DBA Studio 581, 606
DCSI Job Scheduler 232
DCSI Service Disconnect/Connect switch
113
DEA 145
deassign two-way address 445
dedicated 37
dedicated communications link 50
dedicated connections 94
default billing file 241
delete command 473
demand 208
demand reads 14
detection point 81, 140
device location 120
diagnostic command 357
Diagnostic Data 365
Diagnostic log 351, 355
diagnostic test 365
diagnostics 359
dialup 37, 94
Digital Data Services 94
digital meter 24, 27
directed search 655
display monthly data 257
do search 136
684
DOK 145
download firmware 501, 538
DP 202, 233
drop ID 70, 72
DS 202, 233
E
edit INI file manually 506
electro-mechanical meter 23
email notifications 458
EMT-3A 27, 28
EMT-3C-MP 27, 28
EMT-3C-SP 27, 28
energy theft 16, 291
Environmental log 351, 366, 367
equipment ID 365
equipment information 356, 359
equipment type 365
error code 1031 151
error code 1033 151
error code 113 151
error status 365
Event Viewer 458
Exception log 351, 366, 369
EXDAYLIGHTSAVING 555, 564
exit codes 499
F
FAIL 145
failed searches 149
Failed Temp Serial Number Maintenance
144, 155
failure codes
RCE 156
SCE 156
TNS 156
false dispatch 18
fast scram strategy 386
fatal 361
feeder 31, 55
feeder ID 140
feeder layout 292
feeder paths 295
feeder-level IPU 55, 80
firing angle 89
firmware 501, 538
floating point 242, 254
Flow 2A batch mode data exchange 617
forms runtime 591, 595
Frame Relay 39, 94
fraud 323, 343
Index
function group unit details 277, 444, 446
function/group maintenance 443
G
General Status log 141, 147, 651, 653
geographical strategy 383
GetInfo command 480
GetState command 476
global search 655
graph all data 262
graph row 262
graphics runtime 595
grouped search 295, 309
H
header record 243
heavy load 323
hourly consumption 26
hourly file 253, 254
hourly interval data value 256
hourly read 194, 250
hourly/daily repeating read 206, 219, 250,
252
K
Kh 125
KWH 26, 208, 215, 223, 227, 258
L
LC Log 413
LCACCTS table 386
line-ground 140
line-neutral 140
load balancing 295
load control 15, 39, 375, 429, 433, 439
Load Control Accounts table 439
Load Control applications 390
load control class 379, 385, 390, 408
Load Control Class table 381, 389, 391, 439
Load Control log 413
Load Control scheme 377
Load Control transponder 23, 28, 377
Load Management Schedule application 415
load shedding 10, 385
load survey 429
Log Cleaner 501
Log Cleaner configuration menu 504
Log Monitor 508
Log Monitor configuration menu 510
Log Monitor service menu 508
logcleaner.ini file 503
options 503
I
IMT-3 27, 28
IMT-3H 27, 113
IMT-3H-3Port 27
Inbound Pickup Unit 22, 51, 61
inbound scalars 77, 78
initial read 124
Instance Manager 573
interactive meter reads 39
interactive search 117, 118, 129
inter-base collar 29
Internet Virtual Private Network 39
Internet VPN 94
interval data 26
interval data collection 10, 39
interval usage tracking 25
IP 145, 202, 233
IPU input shadowing 85
IPU Map reference table 65
IPU map settings 62, 81
J
J2RE software 619
JDOM 618
Job Queue Maintenance 313
Job Scheduler 287, 313
Log Monitor 501
configuration menu 510
logmonitor.ini file 513
log state 635
log stats 634
logcleaner.ini file 503, 506
logical elimination 111, 138, 153, 164, 652,
656
logmonitor.ini file 508
loop period 636
M
macro 643
mail server 633
maint off command 491
maint on command 490
maintain strategies 415, 421
maintenance command 490
MaxComFailCount field 211
mechanical meter 24, 27
685
Index
Messenger Service 625
categories 629
configuring recipient addressing 626
configuring sender addressing 629
configuring service options 633
log state 635
log stats 634
loop period 636
mail server 633
reset stats 635
run level 637
sample configurations 632
severities 627
Meter Configuration worksheet 128, 129
Meter Conversion table 42, 126, 128, 198,
199, 203
hourly and interval conversion
meter conversion 126
127
Meter database 104, 108, 112, 117, 120,
130, 141, 149, 172, 173, 190, 191, 435,
651, 652, 653
meter fields 120
Meter Misc 143, 203, 347, 435
meter number 112
meter read 197
meter tampering 16
Meter Technician 7
meter type 124
meter type and model 107
Meter Type field 136
Metering Maintenance 138, 144, 195, 197
Misc AMR Scheduler 555, 564
MIT on-request 197
model 124
modify AMR Calendar records 231
Modulation Transformer Unit 22, 31, 33, 51
monitor scheduler 458
monthly billing read 206
monthly consumption display 259
Motorola S-Record 538
MRCBWriter.class 618
multiport meter 24
MultiSpeak 617
customer billing files 623
flow 2A MR files 623
installation 618
third-party Flow 2A CB file 622
Multi-Update/City-Sub 152
mux ports 56
686
N
NA 202, 233
no pulses in 24 hours 16, 17, 120
non-programmable Kh 102
normal search 295, 309
notices
fatal 361
severe 361
warning 361
Notification log 97, 160, 351, 361, 362, 363
O
offset read 124
offset re-calc flag 124
OK 202, 234
OMU Fiber-Optics Interface Assembly 52,
53
one-time billing read 194, 206, 227
on-request meter reads 13
on-request Total Consumption 194, 195,
325
Oracle 40
Oracle 7.3.1
backup procedure 573
TNS server startup and shutdown
612
client 591
TNS server startup and shutdown
606
Oracle 8.1.7 backup procedure 581
Oracle 8i
Oracle Database Manager 40
Oracle Enterprise Manager 573
Oracle installation products 601
Oracle Service DCSI 575, 585, 610, 614
Oracle TNS Listener 575, 585, 610, 614
Oracle Universal Installer 502, 591
outage counts 17
outage mapping 10, 40, 281
Outbound Command Queue 139, 233
Outbound Modulation Unit 22, 33, 51
P
packing list 113
parallel OMU configuration 53, 88, 92
Path History reports 320
Path History table 297, 309
pathmaps 19
PE 202, 234
perform diagnostic 359
Permanent Meter database 41
port accounts 397
potential cause 365
Index
power factor 208
PR 202, 238
Premises ID 120
PreTIQ log 43, 181, 182, 188, 190
private line 94
Product table 42, 102, 104, 105, 107, 130,
133, 145, 391
Product Type Model Cross Reference table
42, 102, 112, 113, 115, 121, 124
products.jar 602
programmable Kh 102
programmable meters 102
programmable registers 235
progress (%) column 542
pulses 126
Q
quality codes 202, 234
R
rate class 123, 146, 208
RCE error code 234
RCE function codes 139
RCE type 203
read indicator 200, 221
reading record 244, 254
receiver sets 84
recipient addressing 626
record size 540
recurring daily and monthly billing read 194
REG 145
Remote Communications Equipment 22, 23,
30
reports runtime 591, 595
reset statistics 635
residential meter 24, 27, 126, 195
response mode 657, 664
Response Status Cross Reference table 42
reverse rotation 16, 17, 323, 324, 333
RM 202
RO 202, 234
ROK 145
route 123
RS232 serial connection 414
run job now 188
run level 637
S
SCADA 414
SCE 539
SCE database 41
SCE error code 234
SCE Maintenance 66, 71, 93, 95
SCE Maintenance logs 350
Diagnostic 351
Environmental 351
Exception 351
Notification 351
Snapshot 351
Sub Response Data 351
Unsuccessful Activity 351
SCE Maintenance with Command View 71,
95, 160, 181, 298, 300, 352, 541, 544, 549,
553
SCE tables 554
SCEMain Download 539, 541, 543, 546
schedule deassign 445
schedule load control 410
SCRAM 382
Search History log 140, 141, 148, 172, 651,
652, 653, 656, 657, 661, 663, 669
Search History log file decode 667
search mode 110
search request fields 663
search response fields 657, 664
acquisition window 660, 667
detection point 666
method status 661, 667
normalized signal strength 660, 666
path status 657, 664
path type 658, 665
quality code 661, 667
SCE execution status 660, 666
signal mode 660, 666
search type 110
searchfile spreadsheet 639
searchfile.dat 187, 644, 647
searchfile.xls 181, 640
Search-in History log 43
searching in meters 115
searching meters 101
sender addressing 629
serial number 112
serial number addressing 380
Serial Number Path Change History report
321
Serial Number Path Change log 321
Serial Number Path History log 320
Serialport/Load Control Maintenance 399,
439
Serialport/Meter Account Maintenance 247
server startup and shutdown 502
687
Index
Service Disconnect/Connect 16, 29, 40
service display name 500
service name 500
service options 633
Set ID Maintenance 248, 436
Set SCE Date 559, 568
severe 361
shed loads 382
shift amount 565
Siemens SX meter 23
single port meter 24
single receiver 60
single receiver mode 56, 84
slowpoll 100
snapshot data 12
snapshot log 351, 366, 371
SNDATA 176, 178
software upgrades 502
SOK 145
SP 202, 234
SR file 538
SRCH 145
SRCH status 141
standard billing file 242
start command 484
status codes 145
stop command 487
Sub Product table 42
Sub Response Data log 351
sub state 182, 553
sub status 182, 553
SubProduct table 102, 108, 109, 138, 145,
165, 392, 653
substation 30, 32, 47, 66
adding 67
adding buses 73
adding feeders 75, 82
adding IPU mappings 80
adding OMU parameters
ID 70
dynamic refresh 526
graphs 524
reports 531
substation available threshold
substation data selection 530
525
Substation Traffic Collection 514, 515,
516, 520
continuing a previous job 520
job options 519
scheduling data collection 517
Substation Traffic Monitor 501, 514
Substation Traffic Analysis 522
Substation Traffic Collection 515,
System Administration 108, 114
system tools 575, 586
516
T
tamper detection 16
TC 195
TCT batch job 281
TCT for 2-Way 277
TCT Volt 283, 284
TCT Volt Response log 289
TCT-Voltage 432
Temp Failed 143
Temp LC Misc 393
Temp Meter database 41, 117, 121, 131,
141, 142, 145, 149, 153, 172, 190, 191,
639
Temp Meter Data 123
Temp Port Data 123
Temp Serial Number Data 121
Temp Meter Misc 129, 143, 144
Temp Non-Failed 143
Temp Serial Number, Port and Meter Data
131
88
Substation and Transmission Engineer 6
substation available threshold 524, 525
Substation Command Queue 138, 236
Substation Communications Equipment 22,
32, 48, 108
Substation Communications Processor Assembly 53
Substation Control Processor Assembly 52
substation data selection 530
Substation Diagnostic log 360
688
Substation ID 72
Substation Response Data log 355, 357
Substation Traffic Analysis 514, 522
terminal servers 39
termination panel 58, 63
Test Communication Tool 89, 263, 274, 432
Test Communication Tool 2-Way 277
test set creation 271
theft prevention 323
thermal limits 127
three-phase meters 24
time synchronization 97
time-of-use 208
time-of-use billing 20
Index
TNS
Application Server 35
Communication Server 35
Oracle Database Server 35
TNS backup procedure 502
TNS Configuration Utility 501, 532
TNS database 101, 115, 128
TNS default billing file 45
TNS Defaults 211
TNS error codes 234, 239
TNS forms 502, 591, 605
TNS Generic Applications 277, 386, 429
TNS Log Cleaner 501, 502
TNS log files 501, 502
TNS master station 32, 33, 36, 51
TNS Metering Maintenance 155, 342, 345,
555, 564
TNS Operator 3
TNS SCE Maintenance 351, 539
TNS System Administration 211
TNS System Maintenance 348
TNS Traffic Analyzer 524
TNS Watchdog
See Watchdog
449
TNS Watchdog GUI 573, 580, 581, 590, 606,
611, 612, 615
TNSCfg.cfg 532, 536, 537
TNSCfg.exe 535
TNSCfg.ini 532, 535, 536, 537
tnsnames.ora 600
Total Consumption 126
TP 202, 234
trailer record 243
Transaction (TR) log 43
transformer 31
transformer load 19
transformer Open Air 53
transponder 23, 29
Trouble Detail 327
Trouble Detail table 324, 325, 343
trouble flags 197, 347
Trouble History 331, 336
Trouble History purge 327, 344
Trouble History table 324, 325, 327, 344
Trouble Initialization 324, 326, 343
Trouble Initialization table 343
Trouble Mask 346, 348
Trouble Process 343
Trouble Processing 197, 233, 344
Trouble Processing Detail table 343
Trouble Processing Details 120
Trouble Purge 326, 343
Trouble Reset 326, 343
Trouble Reset Retry 326, 344
Trouble Retry 326, 344
Trouble Server applications 327, 333, 344
troubleshooting 681
TS 202, 234
TWACS components 22
TWACS Project Manager 4
TWACS-enabled meters 102
two-way addressing 380, 429
Two-Way Function Definition 438
Two-Way Function Definition Maintenance
387
Two-Way Function Group Delete 443
Two-Way Set ID Definition/Maintenance
386
two-way set IDs 436
U
Unsuccessful Activity log 351, 366, 373
User1 120, 122, 124, 246, 248, 250, 434
User2 120, 122, 124
Utility Account Maintenance 623
V
vacation home monitoring 20
verbose logging 458
view responses 289
view results 274
voltage monitoring 283, 287
689
Index
W
warning 361
Watchdog 44, 449
Command Line Interface (CLI)
See Watchdog CLI 466
GUI
See Watchdog GUI 450
Watchdog alerts 44
Watchdog CLI 468
add command 470
batch file 494
delete command 473
exit codes 499
GetInfo command 480
GetState command 476
help command 469
maint command 490
multiple machine distribution
shutting down TNS 492
start command 484
starting TNS services 493
stop command 487
496
Watchdog GUI 44, 450
adding a service 450
deleting a service 456
main menu options 457
starting a service 453
stopping a service 455
troubleshooting 462
watt hours 256
wdcli.bat 494
Wide Area Network 39, 94
X
X/Y addressing 380, 383
690

Operational Process Guide

Transcription

Similar documents

SC76 with 5 accessories v01.qxd

Miglin-Beitler Skyneedle Fact Sheet

News Report – The Hitavada News Report – Lokmat “ Hello “ Nagpur

here. - Affinity

funJoin Play Meter on facebook

Wednesday`s Words

Revenue Systems Brochure

Title slide Three line presentation title Using property

this page - OpticsPlanet.com