Laserfiche WebLink
(Notification) Server methods for this functionality will be implemented by S&S: <br />o ServiceOrderOpened Notification - NOT <br />o GetNextNumber— CB. Will be used to keep track of created Service Orders. This will be called before <br />ServiceOrderOpened Notification in order to obtain service order number. <br />• Update Service Orders. Use case: Auto close of Move Out service order with a meter read. <br />Following MultiSpeak® NOT Server method for this functionality will be implemented by S&S: <br />o ServiceOrderChangedNotification <br />• Complete Service Orders. Use Case: Move Out, rules engine would have a list of move out's for the day. <br />Following MultiSpeak® NOT Server method for this functionality will be implemented by S&S: <br />o ServiceOrderClosed Notification <br />All above MultiSpeak® methods will be implemented in enQuesta and are one-way synchronous methods <br />where MDMS is a client and enQuesta is a server. <br />5.7.2. EnQuesta has a field order flag to distinguish work orders that require field visit from <br />those that can be completed with an AMI meter read. Following AMI kick off meeting, <br />Systems and Software and City will meet to review the work orders that can be completed <br />using the AMI system. Through this scope, S&S will change the work order flag of the <br />existing work order types. An example of a work order could be: Move In Work Orders <br />5.7.3. Systems and Software and City will meet regarding Non -automated Work Order <br />Creation and review those in MDMS's Task listing and decide which ones require <br />25H-118 Page111 <br />