1 / 41

Architecture Updates RNI 3.1 SP1

Architecture Updates RNI 3.1 SP1. C-PAMI-WGE-0006-01. Summarize the differences between the RNI 2.2.4 and 3.1 SP1 software architecture. The goal of this module is to:. Identify key differences between the RNI 2.2.4 and 3.1 SP1 architectures.

loan
Download Presentation

Architecture Updates RNI 3.1 SP1

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Architecture UpdatesRNI 3.1 SP1 C-PAMI-WGE-0006-01

  2. Summarize the differences between the RNI 2.2.4 and 3.1 SP1 software architecture. The goal of this module is to:

  3. Identify key differences between the RNI 2.2.4 and 3.1 SP1 architectures. List the primary hardware and software components required for a RNI 3.1 SP1 installation. Identify the criteria used for sizing RNI 3.x deployments.

  4. Summary of Architectural Changes Software Architecture Model Additional Server Modules Deployment Sizing Methodology RNI Architecture Update

  5. RNI in the FlexNet System RNI Architecture Update Meters withSmartPoint module Regional Network Interface WirelessRF Servers, Software, & Databases Solid-state Digital AMI Meters (water, gas, electric) Tower and station Base Station

  6. RNI 2.2.4 Software Architecture RNI 2.x platform is based on a proven traditional software architecture Dependent on its database as the hub of all information Scalability is achieved by deploying specific sub components to a dedicated server RNI 2.x employs several operating systems—Red Hat Enterprise Server (Linux), and Windows Server 2003 RNI Architecture Update

  7. Deployment Sizing Estimates: RNI 2.2.4 Focused on number of end points and service types to determine deployment sizing RNI Architecture Update

  8. RNI 3.x Software Architecture RNI 3.x platform is based on the Service-Oriented Architecture (SOA) model Software services can be used across any number of hardware servers, or co-exist in a smaller configuration RNI 3.x employs several operating systems—Red Hat Enterprise Server (Linux), Windows Server 2008, and Windows Server 2003 RNI Architecture Update

  9. Deployment Sizing Estimates: RNI 3.1 SP1 Focuses on the following factors to determine deployment sizing: • Amount of incoming Over-The-Air (OTA) data • Number of end points • Configuration of end points (amount of data transmitted) • Network configuration (number of times RNI hears same message) • Amount of data stored • End point data (indefinite) • Interval, billing and alarm data (60 days) • Statistical data (13 months) • Amount of data being exported • To static reports (how often and volume) • Through gateway to an MDM (real-time) RNI Architecture Update

  10. RNI 3.1 SP1 Deployment Sizing Example Using the number of OTA messages and transmission rate determines an estimate of the number of end points that can be supported RNI Architecture Update * Larger systems are supported, but sizing is determined on a project-specific basis

  11. RNI Software Components: Server Modules RNI Architecture Update These components are provided by Sensus

  12. RNI Software Components: Web Interfaces RNI Architecture Update * Optional, except for small water deployments These components are provided by Sensus

  13. RNI Software Components: Applications RNI Architecture Update These components are provided by Third Parties

  14. RNI Software Components: OS and Security Software RNI Architecture Update These components are provided by Third Parties *Optional purchased from Sensus

  15. RNI Software Components: Database RNI Architecture Update *These components are provided by Sensus

  16. RNI 2.2.4 Server Modules Network Controller (NC) • Manages connections with Base Stations • Directs message traffic to/from back spool file to parsers • Perform encryption/decryption and de-duplication • Manages two-way communication engine Map • Optional server • Exports queries in KML (Keyhole Markup Languages) for rendering in Google maps • Used by links in FlexWare Web interface Communication Statistics (CommStats) diagnostics RNI Architecture Update

  17. RNI 2.2.4 Server Modules (Continued) Web/Gateway • Hosts the Web site for FlexWare Web Interface and MDM Web Interface • Hosts gateway interfaces • Runs the Lightweight Directory Access Protocol (LDAP) • Runs system monitoring scripts • Performs file transfers between the RNI and Utility Statistics (Stats) • Manages the network communication statistics for the Base Stations and meters • Manages the graphing capability for these stats RNI Architecture Update

  18. RNI 2.2.4 Server Modules (Continued) Database (DB) • Stores utility meter read data • Stores information to manage network • Stores Web-based reporting data Parsers • Breaks down messages into component parts for storage in the database RNI Architecture Update

  19. RNI 2.2.4 Small Deployment Diagram RNI Architecture Update

  20. RNI 2.2.4 Medium Deployment Same software server modules deployed as for Small deployments • Network Controller (NC), Map, Web/Gateway, Statistics (Stats), Database (DB), Parsers New for Medium deployments • NC and Map/Web/Gateway loaded onto separate hardware • Database and Statistics loaded onto separate hardware • Optional SAN RNI Architecture Update

  21. RNI 2.2.4 Medium Deployment Diagram RNI Architecture Update

  22. RNI 2.2.4 Large Deployments Same software server modules deployed as for Small and Medium deployments • Network Controller (NC), Map, Web/Gateway, Statistics (Stats), Database (DB), Parsers New for Large deployments • PostgreSQL Database loaded onto separate hardware • Parsers loaded onto separate hardware • Use of SAN and NMS highly recommended RNI Architecture Update

  23. RNI 2.2.4 Large Deployment Diagram RNI Architecture Update

  24. RNI 3.1 SP1 Server Modules Network Controller (NC) • Manages connections with Base Stations • Directs message traffic to/from backspool file to parsers • Performs encryption/decryption and de-duplication • Two-way communication engine function moved to FlexApp server Map • Optional server • Exports queries in KML (Keyhole Markup Languages) for rendering in Google maps • Used by links in FlexWare Web interface Communication Statistics (CommStats) diagnostics RNI Architecture Update

  25. RNI 3.1 SP1 Server Modules (Continued) Web/Gateway • Hosts the FlexWare Web Interface to the RNI • MDM Interface removed • Hosts gateway interfaces • Runs the Lightweight Directory Access Protocol (LDAP) • Runs system monitoring scripts • Performs file transfers between the RNI and Utility Statistics (Stats) • Manages the network communication statistics for Base Stations and meters • Manages the graphing capability for these statistics RNI Architecture Update

  26. RNI 3.1 SP1 Server Modules (Continued) Database (DB) • Stores utility meter read data • Stores information to manage network • Stores Web-based reporting data Parsers • Breaks down messages into component parts for storage in the database FlexApp • Runs variety of internal processes and applications • Manages message routing information • Firmware Download RNI Architecture Update

  27. RNI 3.1 SP1 Small Deployment Diagram RNI Architecture Update

  28. RNI 3.1 SP1 Medium Deployments RNI Architecture Update Same software server modules deployed as for Small deployments • Network Controller (NC), Map, Web/Gateway, Statistics (Stats), Database (DB), Parsers New for Medium deployments • FlexApp Server added • Map/Web/Gateway servers loaded onto separate hardware from the NC server • JMS Broker and FlexApp server hosted on single server separate from NC hardware

  29. RNI 3.1 SP1 Medium Deployment Diagram RNI Architecture Update

  30. RNI 3.1 SP1 Large Deployments RNI Architecture Update Same software server modules deployed as for Medium deployments • Network Controller (NC), Map, Web/Gateway, Statistics (Stats), Database (DB), Parsers, FlexApp New for Large deployments • Additional direct access external storage or optional SAN

  31. RNI 3.1 SP1 Large Deployment Diagram RNI Architecture Update

  32. RNI 3.1 SP1 Extra Large Deployments RNI Architecture Update Same software server modules deployed as for Large deployments • Network Controller (NC), Map, Web/Gateway, Statistics (Stats), Database (DB), Parsers, FlexApp New for Large deployments • NC and PostgreSQL database loaded onto separate hardware • RNI Database loaded onto separate hardware from Statistics and Parsers servers • JMS Broker and FlexApp servers loaded onto separate hardware • Use of SAN and NMS highly recommended

  33. RNI 3.1 SP1 Extra Large Deployment Diagram RNI Architecture Update

  34. Which of the following is true about the RNI 3.1 SP1 software architecture? • Uses an SOA model to enable services to run across multiple hardware servers • Uses an SOA model to enable services to be contained to a single server • Uses an SOA model to reduce the overall hardware requirements • Uses an SOA model to ease system configuration

  35. Check the box next to the Sensus server modules that are relevant to an RNI 2.2.4 deployment.

  36. Check the box next to the Sensus server modules that are relevant to an RNI 3.1 SP1 deployment.

  37. Which of the following Web Interfaces is NOT available with RNI 3.1 SP1? • FlexWare • Device Manager • Logic • Sensus MDM

  38. Both the RNI 2.2.4 and RNI 3.1 SP1 use Linux and Windows operating systems. • True • False

  39. Fill in the blanks.RNI 3.1 SP1 supports __________________and ___________________ databases for storage of meter read data. Microsoft SQL Oracle

  40. The expected number of OTA messages sent per second and how often the meter transmits data are used to estimate the potential number of meters that can be deployed using RNI 3.1 SP1. • True • False

More Related