RNI Component Review Release 3.1 SP2

1. RNI Component Review Release 3.1 SP2 C-PAMRAMI-E-0136-01

2. Provide additional detail about the functions and implementation of RNI hardware and software components. The goal of this module is to:

3. Describe the primary function of each of the software application servers. • Identify third-party software that the utility obtains and maintains. • State the purpose of the MultiSpeak interfaces in the RNI system. • Describe the type and format of reports available from the Reporting Component. • Describe the high-level flow of data through the RNI System. Module Objectives

4. Summary of RNI System Components RNI Component Review Software • Server modules (perform selected RNI functions) • Web-based user interfaces (FlexWare, Device Manager) • Third-party applications (OS, mapping, security, MDM) Hardware • Two or more servers running various software components • Optional security hardware Database • Microsoft SQL or Oracle database and management software

5. Example: Small RNI Deployment RNI Component Review

6. RNI Software Components: Server Modules RNI Component Review

7. RNI Software Components: Server Modules (Continued) RNI Component Review

8. RNI Software Components: Web User Interfaces RNI Component Review

9. RNI Software Components: Third-Party RNI Component Review A variety of third-party software is required to round out the RNI deployment including: • Operating system • Database • Security • General applications Refer to the RNI 3.1 SP2 Third-Party Software listing provided in your Student Guide for a complete list

10. RNI MultiSpeak Gateways and Interfaces RNI Component Review Optional gateway used to retrieve data from the RNI database and present it to third-party MDMs and network management systems Version 3.0 provides data about meter reads, remote connection/disconnection of devices, outage detection, and alarms/notifications Version 4.1 provides all Version 3.0 data, plus data about HAN communications and demand response activity

11. RNI Reporting Component Interface RNI Component Review Used to retrieve data from the RNI database for creation of standard and customized reports in CMEP, HHF, or Itron IEE/MV-RS format Typically provided to an MDM or other software for display and analysis Reports generated from this interface are not the same as those presented by the FlexWare web interface Reports can be generated and exported on an ad hoc or scheduled basis

12. RNI Hardware Components RNI Component Review Servers • Two or more, sized according to application needs • Minimum 8 core, 2.3 GHz processor with 32 GB RAM • Runs software servers and applications • Sensus recommends Dell servers Hardware Security Module (optional) • Used when data encryption is deployed • PCI card or stand-alone device • Manages digital keys, accelerates cryptographic processes, provides strong authentication to access critical keys for Sensus applications

13. Example: Medium-Sized RNI Deployment RNI Component Review

14. Data Flow Through RNI: From FBSs to Utility User RNI Component Review Network Controller receives data from Base Station(s) Data is parsed into: • Consumption data: sent to data base (DB) • Status data; sent to DB • Routing data; sent to FlexApp server JMS Broker/FlexApp server queries and receives data from DB Data provided to Web/Map/Gateway server, NMS, MDMs Data available to users through various RNI interfaces

15. Data Flow through RNI from Base Stations to Users RNI Component Review 1 2 3 4 4 1 Data is received from Base Station(s) 4 2 Consumption and status data sent to DB, routing info sent to FlexApp 3Broker/FlexApp server queries and receives data from DB 4Data provided to Web/Map/ Gateway server, NMS, MDMs 5Data available to RNI users 5 5

16. Data Flow Through RNI: From Utility Users to FBSs RNI Component Review RNI users make requests via the FlexWare, Logic, and NMS interfaces Requests processed by Web/Map/Gateway server, NMS, MDMs JMS Broker/FlexApp server updates DB Consumption, status, and routing data sent to NC Data is transmitted to Base Station(s)

17. Data Flow through RNI from Users to Base Station(s) RNI Component Review 5 4 3 4 Consumption, status, and routing data sent to NC 5 Data is transmitted to Base Station(s) 3Broker/FlexApp server updates DB 2 2Requests processed by Web/Map/ Gateway server, NMS, MDMs 1 1 1 2 2 4 1 RNI users make requests

19. Which of the following is the responsibility of the Network Controller server module? • Manages the network communication statistics data for Base Stations and meters • Manages traffic to and from Base Stations, prepares messages for input to the database and messages to end point devices • Stores utility meter read data, information to manage network, and Web-based reporting data • Runs variety of internal processes and applications, including management of message routing information and Firmware Download

20. Which of the following is the responsibility of the Web server module? • Manages the network communication statistics data for Base Stations and meters • Manages traffic to and from Base Stations, prepares messages for input to the database and messages to end point devices • Stores utility meter read data, information to manage network, and Web-based reporting data • Hosts RNI FlexWare Web Interface, gateway interfaces, site LDAP, system monitoring scripts

21. What is the purpose of the Reporting Component? • Generates reports for the FlexWare web interface • Generates reports for each user • Enables generation of reports in exportable formats • All of the above

22. What is the purpose of the MultiSpeak gateway? • Provides method for communicating between meters and Base Stations • Provides RNI data to external applications using standard interface • Provides RNI data to groups of meters • All of the above

23. Draw the flow of data through the RNI from the Base Station to the User on the following graphic.