Transcript Monitor Smart Meters

CONFIGURING AND MANAGING
RNI SYSTEM OPERATION
RNI RELEASE 3.1 SP2
© 2013 Sensus. All rights reserved.
C-PAMRAMI-E-0141-01
Module Goals
2
The goal of this module is to:
Introduce administrators to the RNI tools and
features used to configure and manage the
operation of the FlexNet system.
Section One
3
Creating Meter Groups
Section One Objectives
4
Following this section, you should be able to:
1. View, create, modify, and delete RNI meter
groups.
2. List two examples of when using a group
would make your job easier.
About Meter Groups
Creating Meter Groups
• Meter groups provide a method for performing a
task on multiple meters at once
–
–
–
–
Firmware download
Pinging meters
Reprogramming meters
Monitoring
• Groups can be created, viewed,
modified and deleted from the
FlexWare UI
5
Creating a Meter Group: Steps 1-3
Creating Meter Groups
1. Click Administration > Meters > Select Endpoints
Optionally select all
meters or remove all
meters from selection
2. Check
each meter
to include in
the group
6
3. Click
Create Group
Filter listing to
narrow search
for meters
Page through list of
meters to find all
desired meters
Creating a Meter Group: Steps 4-6
Creating Meter Groups
4. Enter a unique and descriptive name for the group
(no spaces)
5. Select the customer, if needed
6. Click Save to keep the group or Cancel to discard it
7
Creating a Meter Group: Results
Creating Meter Groups
• The group displays in the Meter Groups list
• It identifies the group by name, and provides the
number of meters in the group
Enter characters to
search for the group
and click Filter; Click
Reset to return to all
groups displayed
8
Click Edit next to
the group to add
a description or
modify meter
membership
Click Delete
next to the
group to
remove it
Editing a Meter Group
Editing Meter Groups
• Click Edit in the row of the meter group to be
modified
• Change the Name, Description, Customer, and or
meters to be included using the Edit Meter Group
Information pop-up
• Click Save to submit
the changes
9
Section Two
10
Introduction to the RNI
Reporting Component
Section Two Objectives
11
Following this section, you should be able to:
1. Describe the role of the RNI reporting
component.
2. Identify the output file formats.
3. List three read reports created by the
reporting component.
4. List two reports that output non-read data.
5. Locate additional information about the
individual reports and the reporting
component operation.
About the RNI Reporting Component
RNI Reporting Component
• Generates an output file for export to an MDM or
billing application
– Does not generate the reports created and viewed from
the Reports tab in the FlexWare web interface (e.g. Meter
Report, Installed Meters, Communication Statistics, etc.)
• Scheduler application contains jobs that run the
reports
• Can be run in Tracked or non-Tracked mode
12
About the CMEP File Format
RNI Reporting Component
• California Metering Exchange Protocol (CMEP)
• Latest version 1.20 (released in 2000)
– http://www.smi-ieso.ca/sites/default/files/resource_files/
California%20Metering%20Exchange%20Protocol.pdf
• Comma-separated value (CSV) file format (ASCII)
• Designed to facilitate the exchange of data between
electric/gas utility companies and billing agencies
• Sensus has added enhancements to the base
specification to support alarm data and specific
customer-requests
– Documented in Extended CMEP Specifications Reference
Manual and implemented in all CMEP reports
13
More About CMEP
RNI Reporting Component
• Protocol uses a small number of record (row) types
each having a fixed sequence of fields
• Standard protocol defines record types for exchange
of metering and non-metering data (e.g.
administrative, billing, distribution loss)
• RNI only utilizes the three original record types
defined for metering data, and those only in one
direction—to the customer
• Sensus has extended the solution with an additional
record type
14
Mapping of Record Types to Data Types
RNI Reporting Component
• MEPMD01: Metering Data Type 1 – Interval Data,
Pulse Data, Reference Register Reads
• MEPMD02: Metering Data Type 2 – TOU Data, Net
Metering
• MLA01: Meter Level Alarms (Sensus)
• MEPEC01: Equipment Configuration Type 1 – Meter
configuration information
15
Sensus Extended CMEP Summary
RNI Reporting Component
• A new record type, MLA01, has been added
– Based on the MEPMD01 record type
– Defined for delivery of meter-level alarms
˃ Meter level alarms are distinct from data quality flags in that they
are not associated with a particular interval or register read
• Options to receive rows in a specific order have been
added
• Additional Protocol Text values have been defined
– Some allow longer than the standard specification
limitation of 12 characters
16
About the HHF File Format
RNI Reporting Component
• Hand-Held Format (HHF)
• XML file format
• Originally used to convey metering data stored in a
hand-held device, but now used for data files read
via radio cards installed in utility meters as well
• Sensus supports an HHF generator for data stored in
the FlexNetDB database for customers who are
dependent on this format
17
About the Reports
RNI Reporting Component
• Each report takes at least one required parameter
(CustomerId) and usually some additional optional
parameters
• Parameters can be specified in any order and are not
case-sensitive
• Some parameters only have meaning if others are set
• Reports do not throw an error if extra parameter
values provided–just ignores them when they do not
apply
18
About the Reports (Continued)
RNI Reporting Component
• Tracked mode or non-Tracked mode is controlled by
the AdHoc command line parameter
• A list of supported parameters for any report is
available from the command line by executing the
report with “-?” as the only parameter
19
Reports that Export Meter Read Data
RNI Reporting Component
20
Executable Name Format
Data Reported
Comments
ReadReport.exe
CMEP
MEPMD01
Register reads, each with Enabled by default.
data quality and
timestamp
IntervalReport.exe
CMEP
MEPMD01
Interval consumption,
each with data quality
and timestamp
Consumption for meters is
calculated from successive
register reads. Enabled by
default.
LoadProfileInterval
Report.exe
CMEP
MEPMD01
Interval consumption,
each with data quality
and timestamp
Consumption for meters
originates from C12.19
data tables in meter.
Applies to iConA
residential, Elster
commercial, and ESM
meters. Enabled by default.
Reports that Export Meter Read Data (Continued)
RNI Reporting Component
21
Executable Name
Format
Data Reported
Comments
BackfillReport.exe
CMEP
Backfilled data, each
MEPMD01 with data quality and
timestamp
Legacy and ESM meters
supported. Enabled by
default.
TimeOfUseReport.exe
CMEP
MEPMD02
Time of use registers for
one or more quantities,
each with a time of use
label and data quality
Can be used to deliver
peak demand, with the
time of use label TOTAL.
Enabled by default.
SelfReadReport.exe
CMEP
MEPMD02
Peak and energy data
reads in response to a
Demand Reset
command
Available for Demand
history message and
iConAS extended
message. Enabled by
default.
Reports that Export Meter Read Data (Continued again)
RNI Reporting Component
22
Executable Name
Format
Data Reported
Comments
RegisterReadPreHHF
Report.exe
HHF (XML)
Register reads similar
to ReadReport.exe
Disabled by default.
LoadProfileIntervalPreHHF HHF (XML)
Report.exe
Interval consumption
similar to
IntervalReport.exe
Only commercial
meters included.
Disabled by default.
iConALoadProfileInterval
PreHHFReport.exe
HHF (XML)
Interval consumption
similar to
IntervalReport.exe
Only residential meters
included. Disabled by
default.
ItronMeterReadingReport. XML for
exe
Itron MVRS
Register reads similar
to ReadReport.exe
Available for tier and
non-tier data. Enabled
by default.
Reports that Export Other Data
RNI Reporting Component
23
Executable Name Format
Data Reported
Comments
AlarmReport.exe
CMEP
MLA01
iCon, iConA, Elster, L&G,
GE, water and gas alarms
for each meter within
reporting period
Enabled by default.
MeterSyncReport.
exe
CMEP
MEPEC01
Meters and corresponding E.g. lifecycle state,
configuration information POD, geospatial
coordinates, etc.
Enabled by default.
ClickCountReport.
exe
XML
Meters with at least one
click count value within
reporting period
SnapshotReport.
exe
CMEP
Meters with snapshot
MEPMD01 values, each with data
quality and timestamp
Value indicates count
change relative to
nearest prior message.
Enabled by default.
E.g. voltage snapshot
Reports that Export Other Data (Continued)
RNI Reporting Component
Executable Name
24
Format
Data Reported
Comments
PowerOutageReport.exe XML
Meters with power failure or Enabled by
power restore within
default.
reporting period
SystemHealthReport.exe XML
System-wide counts of
meters, alarms, warnings,
MRFs, meter events
Enabled by
default.
ItronEventReport.exe
Meters events
Enabled by
default.
XML for
Itron MVRS
Read and Interval Reports CMEP Outputs
RNI Reporting Component
Read Report
Interval Report
25
Alarm and Meter Sync Reports CMEP Outputs
RNI Reporting Component
Alarm Report
Meter Sync Report
26
RegisterReadPreHHFReport XML Output
RNI Reporting component
27
More Information About Reports
RNI Reporting component
• Refer to the Sensus FlexNet RNI 3.1 SP2 Reports
Operation Reference Manual
– Description, details, generated output, and parameters for
each report
– Examples for running the reports from the command line
interface
– Instructions for running reports concurrently with hashing
• All reports installed on the Database server by
default in Program Files\Sensus\Database Builder
SDB\Reporting
28
More Information About Reports (Continued)
RNI Reporting component
• For assistance with setting up receipt of up to five
standard reports by email, enter a Sensus technical
support ticket with the following in the description:
– Request for Email Reporting—Tier 2 NETOPS
• For assistance with creating custom reports, contact:
– Sensus Professional Services
Lynn Scott
919-428-7086
[email protected]
29
Questions
30
Learning Check
31
Question:
1. What is the purpose of the RNI Reporting
Component?
a) Generate reports for the FlexWare web
interface
b) Generate reports for use in MDMs and billing
applications
c) Generate reports for utility customers
d) Generate reports for HAN status reporting
Learning Check
32
Question:
2. Which of the following are output file formats
generated by the Reporting Component?
a) XML, text
b) CMEP, MS Word
c) CMEP, XML
d) Excel, text
Learning Check
33
Question:
3. Indicate whether the following reports
provide read data (R) or non-read data (N).
R
a) Read Report ___
N
b) Meter Sync Report ___
R
c) Interval Report ___
N
d) Alarm Report ___
Learning Check
34
Question:
4. Where can you find more detail about each of
the reports generated by the Reporting
Component?
a) Sensus FlexNet RNI 3.1 SP2 Reports
Operation Reference Manual
b) Sensus FlexNet RNI 3.1 SP1 Reports
Operation Reference Manual
c) Sensus FlexNet RNI 3.1 SP2 Reports
Operation User Guide
d) Sensus FlexNet RNI 3.1 SP1 Reports
Operation User Guide
Section Three
35
Configuring and Managing
Scheduled Jobs
Section Three Objectives
36
Following this section, you should be able to:
1. Identify the tools used to manage scheduled
jobs.
2. Verify reports are being generated in a timely
fashion.
3. Describe the procedure used to investigate
failed jobs.
4. Create a new job.
About Scheduled Jobs
Scheduled Jobs
• Used for Billing and System Maintenance
• Background jobs run on a scheduled basis
• Two engines manage the various jobs:
– Scheduler:
˃
˃
˃
˃
Fill gaps in meter reads
Import and export report data
Maintain time synchronization
Maintain database tables
– Job Monitor:
˃ Clean up system log files
˃ Update overall system graphs
37
Refer to the
RNI FlexWare
Reference Manual
for additional
information
about jobs
Managing Scheduled Jobs
Scheduled Jobs
38
1
2
3
Verify jobs
running
Investigate
failed jobs
Create
new jobs
Verifying Scheduled Jobs Are Running: Step 1
1
Scheduled Jobs
1. In FlexWare, click Tools > Scheduler
39
Verifying Scheduled Jobs Are Running: Step 2
1
Scheduled Jobs
2. Verify the schedule engines are connected
– Green = Connected
– Yellow = Connecting
– Red = Connection failed
Both the green highlight
and the text indicate these
are connected
40
Verifying Scheduled Jobs Are Running: Step 3
1
Scheduled Jobs
3. Click List Jobs.
Jobs are listed
alphabetically
Jobs highlighted in yellow
are currently running
Jobs highlighted in pink
are have failed
Jobs highlighted in gray
are disabled
Jobs highlighted in light
yellow are enabled, but
not currently running
41
Verifying Scheduled Jobs Are Running: Step 4
1
Scheduled Jobs
Each row shows the status
for a job: Enabled,
Disabled, Running, Failed
or Not Scheduled
42
4. Look for jobs that
have a Next Run Time;
those should be
running successfully
Investigating a Job Failure: Step 1
2
Scheduled Jobs
1. Click the Last Execution time link to view where the
job failed
43
Investigating a Job Failure: Step 2
2
Scheduled Jobs
For each step in the job,
the status, name,
start/end times are shown
The step at which it failed
is highlighted in red and an
error message written
44
Use the error message
and follow the link to
the log file generated to
determine the cause of
the error
Investigating a Job Failure: Step 3
2
Scheduled Jobs
3. Click Search History to see if there is a trend in the
job’s failure rate
Select the job from the
Tasks drop-down list
Select Failed
from the Status
drop-down list
45
Select the timeframe
you want to review
Click
Search
Filter by how long the
failure has occurred
Investigating a Job Failure: Steps 4-5
2
Scheduled Jobs
4. Look at the Start
Time to determine how
long the job has been
failing; adjust date
range if needed
46
5. View the step where
the job failed and any
error messages;
investigate accordingly
Investigating a Job Failure: Steps 6-9
2
Scheduled Jobs
6. Click List Jobs
7. Scroll to find the job that is failing
8. Click More…
9. View what the job
does using Edit Job
Definition
47
Investigating a Job Failure: Step 10
2
Scheduled Jobs
Look for what the job is
supposed to do
Determine if there is a
maximum time for the job to be
performed before cancelling it:
is this too short?
Determine the
steps performed
by the job
See what other
jobs cannot be
running when this
job is running:
should there be
others in this list?
View the details
of each step
Click Cancel to
return to list
48
Investigating a Job Failure: Steps 11-13
2
Scheduled Jobs
11. Try running the job manually. Click More… next to
the job
12. Click Run Once in the report window
13. Monitor the job progress on the List Jobs page
49
Creating a Scheduled Job
3
Creating a Job
Add a Job
50
Specify Job
Settings
Schedule
the Job
Add a Job to Run in the Scheduler: Steps 1-4
3
Creating a Job
1.
2.
3.
4.
In FlexWare, select Tools > Scheduler
Verify that the schedule engines are connected
Click List Jobs
Verify that the job you want to add has not already
been created
– Sort and/or filter list by Server, Name, Status, Last/Next
Execution Time
51
Add a Job to Run in the Scheduler: Step 5
3
Creating a Job
5. Click Add Job
52
Add a Job to Run in the Scheduler: Steps 6-7
3
Creating a Job
6. Select either New or Clone an existing job
– If you select cloning, select an existing job from the dropdown list
7. Click Next
53
Specify Job Settings: Steps 1-2
3
Creating a Job
1. Complete the Name and Server fields
2. Optionally add a Description, Timeout, and any Job
Dependencies
Fields marked
with a blue
star (*) are
required
54
Specify Job Settings: Step 3
3
Creating a Job
3. Enter Step details
– Enter a name and optionally a description of the first step
– Select the kind of step from the drop-down list
Three types of steps can be specified:
˃ Executable
• Executes a *.exe file via the command line
• Run as the scheduler user
˃ SQL Script
• Executes an SQL script against SQL Server (using sqlcmd) or
Oracle (using SQL*Plus)
• SQL default user is sa; Oracle default user is SYS
• Script parameters must be 4000 characters or less
˃ Stored Procedure
• Calls a procedure stored in the database
• Must provide password to access database
55
Specify Job Settings: Steps 3 (Cont’d) - 4
3
Creating a Job
3. Enter Step details (Continued)
– Select the Failure Behavior from the drop-down list
Three failure actions can be specified:
˃ Fail On Error
• Stops execution of the job
• No additional regular steps are performed, but final steps are
˃ Fail On Error (no final steps)
• Stops execution of the job
• No additional regular or final steps are performed
˃ Continue On Error
• Executes all remaining regular and final steps
– Enter additional fields as appropriate for the step type
4. Click Submit to create the job
56
Schedule the Job: Steps 1-2
3
Creating a Job
1. Locate the new job on the job list
2. Click More… next to the new job to open job
options popup
57
Schedule the Job: Step 3
3
Creating a Job
3. Click Add Schedule
58
Schedule the Job: Steps 4-5
3
Creating a Job
4. Set the
appropriate
frequency for
the job
5. Click Submit
Choose from
Monthly, Weekly,
Daily, Hourly, or
Every Minute
59
Managing Scheduled Jobs: Dos and Don’ts
Scheduled Jobs
• Do
– Look at the job definition to
identify the processes that occur
during the job and where
outputs are sent (if applicable)
– Look at the job history for trends
in failures
– Run the job one time for Ad Hoc,
or unscheduled, jobs
– Clone the job to create a new job
that is similar to a job already
created
60
Managing Scheduled Jobs: Dos and Don’ts
Scheduled Jobs
• Do Not
– Disable or delete default
jobs unless told to do so by
Sensus Technical Support
– Change the schedule
without making sure it
does not conflict with
other scheduled jobs or
system processing; can
cause increased noise in
system sufficient to impact
reading efficiency
61
Verifying UI and System Log Jobs are Running: Step 1
Scheduled Jobs
1. Click Diagnostics > Job Monitor
62
Verifying UI and System Log Jobs are Running: Step 2
Scheduled Jobs
2. Verify the service is running
Communication
Statistics
graphical
update
jobs
Log
update
jobs
63
The individual jobs have
their own status and often
run quickly enough that you
do not see any status other
than Not Running
Verify they are running by
seeing the Next Run date and
time is in the future
Questions
64
Learning Check
65
Question:
1. How do you verify that jobs are running as
scheduled?
a) Their next run time is in the future
b) Their status is Enabled or Running
c) They are highlighted in light or bright yellow
d) All of the above
Learning Check
66
Question:
2. Where do you look for the failure point for a
given job?
a) On the Scheduler home page
b) Click the job’s Last Execution link
c) On the Job Monitor page
d) None of the above
Learning Check
Question:
3. Indicate if the following statements are true or
false regarding the creation of a new job.
a) You can create a new job from an existing
True
job. ______
b) You should always remove unused jobs from
False
the jobs list. ______
c) The new job will be enabled and run
False
automatically. ______
d) New jobs must have at least one step.
True
______
67
Learning Check
68
Question:
4. Which jobs are monitored using the Job
Monitor instead of the Scheduler?
a) Daily database maintenance
b) Daily read reports
c) Daily system logs cleanup
d) Daily meter synchronization