Laserfiche WebLink
Tasks Name Description Customer Role <br />1. Installation Initial Installation of • Hardware Set Up <br />CentralSquare's Community • Completed <br />Development software Pre -Install <br />Checklist <br />• Attend Discovery <br />I Call <br />2. Test Account Test Account Creation is the <br />Creation creation of the test account <br />which is cloned from the pre- <br />production environment. <br />Assumptions <br />CentralSquare Role <br />• Pre -Install <br />Checklist <br />• Discovery Call <br />• Complete install <br />and data <br />migration <br />• Validate Account • Create Test <br />Account <br />• CentralSquare will migrate all Customer data contained within TRAKiT.net database into the Community <br />Development database and confirm that primary system functions are available. <br />• CentralSquare will provide the Community Development software and install it on a local server. Software <br />installation will be done one (1) time. <br />• Customer will be charged for any moving and/or reinstallation of the software. <br />• Customer is responsible for the procurement and installation of hardware based upon CentralSquare's <br />Recommended Hardware Specifications. <br />• CentralSquare will create one (1) Production Account and one (1) Test Account as part of the Agreement. <br />Additional accounts will require additional hours added to the Quote by mutual written agreement at <br />CentralSquare's prevailing rates. <br />• Initial installation of Community Development is completed into one (1) pre -production environment. All <br />configuration, training, and testing is completed in this environment. Prior to end user training a "testing" <br />environment is created and the data from Pre -Production is copied over. This second environment called "test" is <br />used to train end users and as a sand box for users to learn. Prior to final go live the Pre -Production environment <br />is cleared out of data and the "final conversion" from production is completed. Pre -Production is now considered <br />"production." <br />Data Availability to Third Party Products and Services <br />Cognos Export: <br />CentralSquare will create a Cognos report that will pull required/recommended fields from Community Development used <br />for BuildingEye. Considerations to include: <br />• Include any and all data to be supplied to BuildingEye that is stored in Community Development and that <br />is relevant to the purposes of the project <br />• Use the PRMRY Audit table to determine what records have changes <br />• Either limit or flag fields that do have changes identified based on BuildingEye guidance <br />• Use the PRMRY Notes table if it is required to know what has changed <br />• Use a combination of SQL data pulls and/or prebuilt content packages as a method for pulling the data <br />into the requested output <br />Report will be developed and passed along to be tested. Testing of the data will be done as the report is created, but final <br />testing will need to include BuildingEye. BuildingEye can identify incorrect or missing data items and we can make <br />modifications as required/available and re -submit for testing. <br />ATTY/AGR.2020.307/Central Square (Page 23 of 26) <br />