25H - AGMT FOR METER READING AND MANAGEMENT

Home Browse Search

data to Flow between the Customer's Systems and Sensus' Managed Systems in a secure manner via the public Internet. iv. Upon receiving the system administrator account from Sensus, Customer shall create username and passwords for each of Customer's authorized users and complete the applicable Sensus registration process (Authorized Users). Such usernames and passwords will allow Authorized Users to access the Application(s). Customer shall be solely responsible for maintaining the security and confidentiality of each user ID and password pair associated with Customer's account, and Sensus will not be liable for any loss, damage or liability arising from Customer's account or any user ID and password pairs associated with Customer. Customer is fully responsible for all acts and omissions that occur through the use of Customer's account and any user ID and password pairs. Customer agrees (1) not to allow anyone other than the Authorized Users to have any access to, or use of Customer's account or any user ID and password pairs at any time; (ii) to notify Sensus immediately of any actual or suspected unauthorized use of Customer's account or any of such user ID and password pairs, or any other breach or suspected breach of security, restricted use or confidentiality; and (iii) to take the Sensus-recommended steps to log out from and otherwise exit the Application(s) and Managed Systems at the end of each session. Customer agrees that Sensus shall be entitled to rely, without inquiry, on the validity of the user accessing the Application(s) application through Customer's account, account ID, usernames or passwords. v. Customer shall be responsible for the day-to-day operations of the Application(s) and FlexNet System. This includes, without limitation, (1) researching problems with meter reads and system performance, (ii) creating and managing user accounts, (iii) customizing application configurations, (iv) supporting application users, (v) investigating application operational issues, (vi) responding to alarms and notifications, and (vii) performing over -the -air commands (such as firmware updates or configuration changes). D. Software Solution Components. i. Description of Software Solutions. Sensus software consists of a core communication module and a set of applications. Some applications are required to perform basic solution capabilities, other applications are optional and add additional capabilities and function to the overall solution. As Customer's business process expands and/or new Sensus offerings are made available, additional applications and functionality can dynamically be added to the solution, provided Customer purchases such additional applications. ii. Regional Network Interface. The Regional Network Interface (RNI) or Sensus head -end is the centralized intelligence of the FlexNet network; the RNI's primary objective is to transfer endpoint (such as meters) data to the Customer and the advanced feature applications. The RNI is adaptable to Customer configurations by simultaneously supporting a wide range of FlexNet enabled endpoints; including but not limited to meters (electric, water, gas), street lighting, and Home Area Network devices. a. Core Package (1) Communication 1. Manages all inbound and outbound traffic to and from endpoints 2. Outbound routing optimization 3. Route analyzer 4. AES256 bit encryption of radio messages 5. Reports and metric details of network performance and troubleshooting aids 6. Management of RF equipment (base stations and endpoint radios) (ii) Data Collection 1. Missing read management 2. Management of duplicate reads 3. 60 day temporary storage (iii) Application integration 1. To Sensus Analytics applications 2. Enable 3m party application integration 3. Batch CMEP file export 4. Real-time access through MultiSpeak (iv) Endpoint Management 1. Gas, water, electric, lighting concurrent support 2. Remote configuration 3. Remote firmware updates 4. Reports, metrics and Troubleshooting (v) User Management 1. Secure access 2. Password management 3. Definable user roles 4. User permissions to manage access to capabilities Integration of RNI. Sensus shall provide RNI integration support services to Customer only to the extent specifically provided below: (1) Sensus shall meet with the representative from the Customer's system(s) targeted for integration to determine which integration method is appropriate (e.g., Multispeak, CMEP, etc.). 1. In scope and included integration efforts: Provide the gateway URLs to the integrating system as needed, provide Customer with standard integration API documentation, validate and test that the correct Customer information is Flowing into and/or out of the RNI. 2. Out of scope and subject to additional charges: Modifications or extensions to the standard API provided by Sensus and any integration efforts not outlined above as in scope and included. (ii) Customer Responsibilities: 1. Provide Sensus with information about the relevant information Customer wishes to transfer and integrate with the RNI. 2. Establish the network and security required for the two systems to reasonably communicate. 3. Verify integration to third party system functionality is working as intended. (iii) If an item is not listed in subparagraph (1) above, such item is excluded from the integration of Sensus RNI Support and is subject to additional pricing. 3. Third Party Software. A. RedHat Linux. If Sensus is providing Customer with a license to use RedHat Linux Software, Customer agrees to the following: Confidential I Page 11 of 14 25H-157