Laserfiche WebLink
Key Assumptions (continued) <br />3. Only features materially similar to V9.3 will be enabled to minimize change/risk to the affected End <br />Users and current workflows. TAB welcomes the opportunity to collaborate with Client on features <br />available within V10.2 that maybe of further benefit under a Change Order to this SOW or another <br />SOW at a later date <br />4. The Client will be able to upload a SQL Backup of their current Production Environment to a TAB <br />Provisioned sharefile or sFTP site. It is recommended that the backup be archived using WinRAR or <br />similar, separating the archive into 500MB volumes, including a 3% recovery record. <br />5. The Client maintains a Testing Environment that is in alignment with the technical specifications of <br />the Production Environment, including the restoration of a recent backup from the Client's <br />Production Environment into the Test Environment, confirming and testing it. <br />6. If users are to print TabQUIk color labels from the web -client, communication to/from <br />tabquik.com/.ca website is required. Any required networking and IT tasks associated with meeting <br />this prerequisite is the responsibility of the client. <br />7. If users are to print black & white labels from the web -client a supported print driver will be installed <br />and configured on the IS server. Any required networking and IT tasks associated with meeting this <br />prerequisite is the responsibility of the client. <br />8. TAB will have administrator access with dedicated remote (Microsoft Remote Desktop Access - <br />"RDP") credentials to all of the Fusion Environments hosted by the Client, including "sa" or "DB <br />Owner' permissions on the FusionRMS Database Server. TAB will always defer to the IT security <br />policies of the Client, but in scenarios where the above assumptions cannot be met, additional <br />efforts outside the scope of this project may be required. <br />9. TAB will document the solution design in the form of a Visio document describing the existing <br />structure notating interface points and key business process use cases. <br />Should any material deviation from the approach or the assumptions listed above present itself <br />during the course of this project, a change order "may" be issued as per our Change Management <br />Process (see Appendix A). <br />Page 5 of 19 <br />