Okaloosa County BOCC — January 17, 2017 — Software as a Service Agreement — reading text

may include, but is not limited to: analysis, testing, repair, maintenance, re-selting and other servicing of the hardware, cabling, networks, software and other devices, materials and systems through which access to and/or use of the Application(s) by the Customer is made avallable (the “Managed Systems"). Sensus shali endeavor to provide advance notice of such Emergency Work to Customer when practicable and possible. Lack of Internet Availability. Sensus shall not be responsible for any deterioration of performance attributable to latencies in the public internet or point-to-point network connection operated by a third party. Customer expressly acknowledges and agrees that Sensus does not and cannot control the flow of data to or from Sensus’ networks and other porfions of the Internet, and that such flow depends in part on the performance of Internet services provided or controlled by third parties, and that at times, actions or inactions of such third parties can impair or disrupt data transmitted through, and/or Customer's connections fo, the Intemet or point-to-point data connection (or portions therecf). Although Sensus will use commercially reasonable efforts to take actions Sensus may deem appropriate to mitigate the effects of any such events, Sensus cannot guarantee that such events will not occur. Accordingly, Sensus disclaims any and all liability resulting from or relating to such events. B. Data Center Site-Security. Although Sensus may modify such security arrangements without consent or notice to Customer, Customer acknowledges the fo\lowmg are the current arrangements regarding physical access to and support of the primary hardware components of the Managed Systems: iv. V. vi. The computer reom(s) in which the hardware is installed is accessible only to authorized individuals. Power infrastructure includes one or more uninterruptible power supply (UPS) devices and diese! generators or other alternative power for back-up electrical power, Alr-conditioning facllities (for humidity and temperature controls) are provided in or for such computer room(s} and can be monitored and adjusted for humidity and temperature settings and control. Such air systems are supported by redundant, back-up and/or switch-over environmental units. Such electrical and A/C systems are monitored on an ongolng basls and personnel are available to respond to system emergencies (if any) in real time. Dry pipe pre-action fire detection and suppression systems are provided. Data circuits are available via multiple providers and diverse paths, giving access redundancy. C. Responsibilities of Customer i Customer shall promptly pay all Software as a Service fees. Customer may not (i) carelessly, knowingly, intentionally or maliciously threaten, disrupt, harm, abuse or interfere with the Application(s), Managed Systems or any of thelr functionality, performance, security or integrity, nor attempt to do so; (ii) impersonate any person or entity, including, but not limited to, Sensus, a Sensus employee or another user; or (jii) forge, falsify, disguise or otherwise manipulate any identification information associated with Customer's access fo or use of the Application(s). The provisioning, compatibility, operation, security, support, and maintenance of Customer's hardware and software (“Customer's Systems”) is exclusively the responsibility of Customer. Customer is also responsible, in particular, for correctly configuring and maintaining (i) the desktop environment used by Customer to access the Application{s} managed by Sensus; and (i) Customer's network router and firewall, if applicable, to aflow data fo flow between the Customer's Systems and Sensus' Managed Systems in a secure manner via the public Internet. 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 respensible for maintaining the security and confidentiality of each user 1D and password pair assoclated 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 accur through the use of Customer's account and any user ID and password pairs. Customer agrees (i) 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; (i) 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 shalt be entitled to rely, without inquiry, on the validity of the user accessing the Application(s) application through Customer's account, account ID, usemames or passwords. Customer shall be responsible for the day-to-day operations of the Application(s) and AMI System. This includes, without limitation, (i) researching probiems with meter reads and system performance, (i) creating and managing user accounts, (iii) customizing application configurations, (iv) supporting application users, {v) investigating application operational issues, (vi) responding to alarms and nofifications, and (vii) performing over-the-air commands (such as firmware updates or configuration changes). lll. Sensus Analytics A, Essential Package. The Essential Package of the Sensus Analytics Application shall consist of the following medules: i Device Access a. Allows search for meter details by using data imported from the Billing system or the Sensus Device ID or AMI ID. b. Allows a view of the meter interval or register reads. ¢ Meter data is available to be copied, printed, or saved to certain user programs or file formats, specifically CSV, PDF, and Spreadsheet. d. Allows the current and historical data to be viewed. 6. Allows the current usage to be compared to historical distribution averages. f. Allows the user to see the meter location on a map view. g. Allows notifications for an event on a single meter to be forwarded to a Customer employee. h. Allows details to be viewed ahout a meter — (dependent on the data integrated from other systems). Meter Insight (provides the following) CONFIDENTIAL | Page 7 of 12 a«mfi SENSUS # of active meters. # of orphaned meters with drill down to the list of meters. # of inactive meters with drill down to the list of meters. # of stale meters with drill down to the list of meters. # of almost stale meters with drill down to the list of meters. # of meters where no read is available with drill down to the list of meters. # of meters with high threshold exceptions with drill down to the list of meters. # of unknown radios with drill down to the list of meters. jil. Report Access Allows the user to see meter alarms and choose a report from a list of standard reports. Master Route Register Reads: Shows the latest reads for all meters within specified time window. Meter Route Intervals Reads: Allows users to inspect intervals of a single meter over a period of time. Master Route No Readings: List all meters that are active in the system, but have not been sending reads within the specified time window. Consumption Report: List meters' consumption based on meter readings within the specified time window. Zero Consumption for Period: List meters whose readings do not change over a period of time. Negative Consumption: Shows the number of occurrences and readings of negative consumption for the last 24hr, 48hr and 72hr from the entered roll up date. High Low Exception Report: Displays meters whose reads exceed minimum or/and maximum threshold, within a time range. Consumption vs Previous Reported Read: Compares latest reading (from RNI) with last known read received from CIS. Consumption Exception 24 hour Report: This report shows meters that safisfy these two conditions: (1) The daily average consumptions exceed entered “daily consumption threshold;” (2) The number of days when daily thresholds are exceeded are greater than the entered * exception per day threshold.” k. Endpoint Details: Shows the current state of meters that are created within the specified time range. I, Orphaned Meters: List meters that are marked as ‘orphaned’, which are created as of entered “Created as of" parameter. m. Biling Request Mismatch: Displays meters in a billing request that have different AMR id with the ones sent by RNL. [t also shows AMR id in billing request that have different meter Id in the RNI. n. Users need to enter which billing request file prior to running the report. 0. Alarms Report: List all alarms occurred during a time window. Users can select which alarm to show. iv, Billing Access a. Initiate the creation of billing export files formatted to the import needs of the billing system. b, Receive billing request files from the billing system to identify what meters to include in the billing export file in the case where billing request file option is used. ¢. Provides a repository of past billing files that were either used for billing preparation or actually send to the billing system. d‘ Wil store created billing files for a period of three years unless otherwise denoted. Thé system will allow creation of test files before export to the hilling system. V., B\Illng Adaptor a. The underlying configurator and tools mapping the extraction of billing data fo enable integration to the utility's billing system. vi. Data Store a. Allows storage of meter reading data incuding Intervals, Registers, and Alarms to be stored. b. Stored data is available online for reports and analysis. ¢ Data will be retained for 3 years. Additional duration can be purchased. B. Enhanced Package. The Enhanced Package shall consist of the modules listed above in the Essential Package, as well as the following additional modules: I. Alarm Dashboard Allows the user to summarize and filter alarms by a date range. Allows the user to review alf alarm types on a single screen. The user can filter out the alarms not wanted on the screen. Alarm totals can be visualized. Adds a view of trending alarms over time. Click to drill down on an alarm to gain more information on specific events. Click to analyze a specific event on a particular device. . Alarm Console a. Follow real time monitors of the alarms coming from Customer’s meters. b. Provides a single view for all alarms across the entire network, ¢ Allows the user to view trending of each alarm over time. iil. ~ Alert Manager a. Allows creation of alert groups who will be notified when an alarm occurs. b. Users can manage alert groups by adding and removing group members. ¢ Allows selection of notification method for how end users in the group will be notified; email or SMS {fext message). d. Allows creafion of an alert from the available system events from smart points and assign to a group. e. Monitors the systems meters for events. When an event is tr]ggered all users in the group will be notified. C. Integratlon of Sensus Analytics. Sensus shall provide integration support services to Customer only to the extent specifically provided below: i. Sensus shall provide Customer with a simple flat file specification known as VFlex for the integration of the Customer's back office system to the Sensus Analytics modules. This flat file may be delimited or fixed width. This specification aflows Customer to fransmit each day or as needed: the devices and end users in the system, end user status, end user