Laserfiche WebLink
16. <br />The system will be <br />Because the system is a hosted SaaS solution, there will be no limit <br />capable of sustaining a <br />X <br />to the number of notifications Contractor is capable of sending and <br />minimum volume of <br />no limit to the number of contacts that can be stored with the <br />50,000 phone calls <br />solution. Contractor will conduct regular capacity planning <br />simultaneously. <br />(quarterly) to ensure ample capacity, performance, storage, and <br />support to maintain guaranteed SLAB. <br />17. <br />The service will be <br />Contractor will provide a verifiable and configurable call throttling <br />configured with pre-set <br />X <br />mechanism. The throttling settings will allow County to modify the <br />call throttling rates set by <br />overall speed for all calls going out or specify an area code and <br />the User launching the <br />prefix to modify the speed for a specific area or building. <br />notification, not the <br />Contractor. <br />18. <br />The service will be <br />configured with real- <br />X <br />time automatic/ <br />intelligent throttling <br />during a call in progress <br />to ensure a high success <br />rate. This rate will be <br />displayed to the <br />notification sender and <br />recorded so that it can be <br />accessed and reviewed <br />upon demand by the <br />County. <br />19. <br />The service will use <br />Regardless of the target telephone provider, Contractor will utilize <br />multiple telephone <br />X <br />established telecommunication industry standards for placing <br />carriers and can switch <br />telephone calls among public networks. <br />between carriers during <br />notifications depending <br />upon telephone network <br />status. <br />20. <br />The system will be <br />By default, each contact targeted with a notification from the <br />configured to make <br />X <br />Contractor solution will be sent notifications based on a "rotational <br />multiple attempts to <br />contact methodology" whereby the contact devices (delivery <br />reach Registrants. <br />methods) for any contact are notified, one at a time, and Contractor <br />seeks confirmation/response. Should confirmation/response be <br />received, it will be recorded in the solution and no further <br />notifications are deployed to the recipient. If the recipient does not <br />confirm/respond to the incoming notification, Contractor will <br />"rotate" to the next available device and attempt to contact the <br />recipient again (seeking response). This process will continue until <br />all Contact Cycles are exhausted. <br />Comity of Orange MA-060-20010263 File No. CO21209 <br />Sheriff-Coroner/Purchasing Services Bureau Public Mass Notification Systmn Page 26 of 40 <br />