Survey
* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project
* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project
ARCHITECTURE UPDATES RNI 3.1 SP1 © 2013 Sensus. All rights reserved. C-PAMI-WGE-0006-01 Module Goals 2 The goal of this module is to: Summarize the differences between the RNI 2.2.4 and 3.1 SP1 software architecture. Module Objectives 3 Following this module, you should be able to: 1. Identify key differences between the RNI 2.2.4 and 3.1 SP1 architectures. 2. List the primary hardware and software components required for a RNI 3.1 SP1 installation. 3. Identify the criteria used for sizing RNI 3.x deployments. Summary of Architectural Changes RNI Architecture Update • Software Architecture Model • Additional Server Modules • Deployment Sizing Methodology 4 RNI in the FlexNet System RNI Architecture Update Meters with SmartPoint module Regional Network Interface Wireless RF Solid-state Digital AMI Meters (water, gas, electric) Servers, Software, & Databases Tower and station Base Station 5 RNI 2.2.4 Software Architecture RNI Architecture Update • 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 6 Deployment Sizing Estimates: RNI 2.2.4 RNI Architecture Update • Focused on number of end points and service types to determine deployment sizing Size Number End Points Target Service Type ≤10K Water or Gas 10K-25K Water or Gas 25K-50K Water or Gas 10K-50K (Water or Gas) + Electric 50K-100K Water, Gas, and Electric 50K-200K Electric Small Medium Large 7 RNI 3.x Software Architecture RNI Architecture Update • 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 8 Deployment Sizing Estimates: RNI 3.1 SP1 RNI Architecture Update • 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) 9 RNI 3.1 SP1 Deployment Sizing Example RNI Architecture Update • Using the number of OTA messages and transmission rate determines an estimate of the number of end points that can be supported Size* OTA Message Transmission Rate (#/sec) Meter Transmission Frequency (min) Potential Number End Points Small ≤10 30 10 K ≤10 240 100 K ≤30 30 50 K ≤30 240 300 K ≤100 30 175 K ≤100 240 600 K ≤700 30 1.25 M ≤700 240 3M Medium Large Extra Large * Larger systems are supported, but sizing is determined on a project-specific basis 10 RNI Software Components: Server Modules RNI Architecture Update Sensus Components RNI 2.2.4 RNI 3.1 SP1 Network Controller (NC) Database (DB) Map Statistics (Stats) Web/Gateway Parsers FlexApp These components are provided by Sensus 11 RNI Software Components: Web Interfaces RNI Architecture Update Sensus Components FlexWare RNI 2.2.4 RNI 3.1 SP1 Device Manager 1.0 MDM (optional) Logic Data Analytics (optional*) * Optional, except for small water deployments These components are provided by Sensus 12 RNI Software Components: Applications RNI Architecture Update Third Party Components RNI 2.2.4 RNI 3.1 SP1 Apache Camel n/a 2.5 Apache Tomcat 5.5.23 5.5.23 (6.0.29 for gateway) Apache HTTP Server 2.2.4-22 2.2.3-63 Mapping Tiger Maps Tiger Maps 2009 TIGER/Line Shapefiles and Google Earth 5.1.x Internet Browser IE6 IE7 Java 1.6.0.13 1.0.6.24 JMS Broker ActiveMQ 5.2 ActiveMQ 5.5.0 JOSSO 1.5 1.5 Perl 5.8.8 5.8.8-38 Putty 13 Latest available These components are provided by Third Parties RNI Software Components: OS and Security Software RNI Architecture Update Third Party Components RNI 2.2.4 RNI 3.1 SP1 Microsoft Windows Server 2003 R2 2003 SP2 and 2008 Standard R2 SP1 or Enterprise R2 CU3 Red Hat Linux Enterprise 5.6 Enterprise 5.8* Open LDAP 2.3.43-3 2.3.43-25 OpenSSL 0.9.8e 0.9.8e-22 OS Software Security Software CopSSH *Optional purchased from Sensus 14 Latest available These components are provided by Third Parties RNI Software Components: Database RNI Architecture Update Third Party Components RNI 2.2.4 RNI 3.1 SP1 Microsoft SQL Server 2005 2008 Oracle DB Server Oracle 11g Oracle v11.2.0.3 with latest patch (Enterprise Edition for large deployments) PostgreSQL* 8.3.7 9.1.3-1 PostGIS* 1.5.0SVN 1.5.3-2 *These components are provided by Sensus 15 RNI 2.2.4 Server Modules RNI Architecture Update • 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 16 RNI 2.2.4 Server Modules (Continued) RNI Architecture Update • 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 17 RNI 2.2.4 Server Modules (Continued) RNI Architecture Update • 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 18 RNI 2.2.4 Small Deployment Diagram RNI Architecture Update 19 RNI 2.2.4 Medium Deployment 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 – NC and Map/Web/Gateway loaded onto separate hardware – Database and Statistics loaded onto separate hardware – Optional SAN 20 RNI 2.2.4 Medium Deployment Diagram RNI Architecture Update 21 RNI 2.2.4 Large Deployments RNI Architecture Update • 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 22 RNI 2.2.4 Large Deployment Diagram RNI Architecture Update 23 RNI 3.1 SP1 Server Modules RNI Architecture Update • 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 24 RNI 3.1 SP1 Server Modules (Continued) RNI Architecture Update • 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 25 RNI 3.1 SP1 Server Modules (Continued) RNI Architecture Update • 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 26 RNI 3.1 SP1 Small Deployment Diagram RNI Architecture Update 27 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 28 RNI 3.1 SP1 Medium Deployment Diagram RNI Architecture Update 29 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 30 RNI 3.1 SP1 Large Deployment Diagram RNI Architecture Update 31 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 32 RNI 3.1 SP1 Extra Large Deployment Diagram RNI Architecture Update 33 Questions 34 Learning Check 35 Question: 1. Which of the following is true about the RNI 3.1 SP1 software architecture? a) Uses an SOA model to enable services to run across multiple hardware servers b) Uses an SOA model to enable services to be contained to a single server c) Uses an SOA model to reduce the overall hardware requirements d) Uses an SOA model to ease system configuration Learning Check 36 Question: 2. Check the box next to the Sensus server modules that are relevant to an RNI 2.2.4 deployment. Network Controller FlexApp Server Web Server Map Server Database Server Statistics Server JMS Broker Gateway Server Learning Check 37 Question: 3. Check the box next to the Sensus server modules that are relevant to an RNI 3.1 SP1 deployment. Network Controller FlexApp Server Web Server Map Server Database Server Statistics Server JMS Broker Gateway Server Learning Check 38 Question: 4. Which of the following Web Interfaces is NOT available with RNI 3.1 SP1? a) FlexWare b) Device Manager c) Logic d) Sensus MDM Learning Check 39 Question: 5. Both the RNI 2.2.4 and RNI 3.1 SP1 use Linux and Windows operating systems. a) True b) False Learning Check 40 Question: 6. Fill in the blanks. Microsoft SQL RNI 3.1 SP1 supports __________________and Oracle ___________________ databases for storage of meter read data. Learning Check 41 Question: 7. 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. a) True b) False