Laserfiche WebLink
a�e- <br />software <br />best business value to the customer. Any design requirements not available to the care system and/or requiring development will be <br />scoped and presented in a separate Statement of Work. Assurance services afforded the project maybe leveraged for work identified <br />as outside the scope of the project. <br />ProjectDox Configuration Requirements Document <br />Advanced Integration permitting system touchpolnt discussion for Land Management System Includes: <br />o Project Creation — Required application data is pushed from the permitting system to the ProjectDox application <br />using the Avolve provided REST API and configuration of the ProjectDox Windows Service Process. Required <br />field for project creation: <br />o Permit Number/Project Name (Key value) <br />o Description <br />o Applicant/Submitter First Name <br />o Applicant/Submitter Last Name <br />o Applicant/Submitter Email Address <br />o Permit/Project Type <br />o Application Data — Pull of data from the permitting system to display of up to 18 read-only permit application data <br />fields within the plan review process. <br />o Review Status — Push of data to provide the permitting system the following data related to the plan review <br />o Reviewer Name <br />o Reviewer Department <br />o ReAewCyde <br />o Review Status (Approved, Redacted) <br />o Date Completed <br />o Final Approval Status — Push final status orlog event of approved to permitting system API indicating to the <br />permitting system that all reviews are approved in ProjectDox. <br />• Project Plan (task lisf/schedulelresource assignments) not to exceed budget <br />Configuration & Integration • Offsite I Remote <br />Configuration of applicad a software products, forms and the workflows (rased on the configuration requirements document findings. <br />This includes the development of the integration work defined in this Statement of Work and confirmed during requirements <br />discussions. <br />• Configured Working products and modules as specified in the Purchase Agreement/ Sales Order <br />o Configured Working ProjectDox and OAS Application (OAS Optional) <br />• 3 BIC Wordows <br />• Builcing <br />• Planning <br />• Public Works (optional) <br />Advanced Integration <br />• 1 OAS Advanced Application Form <br />o Form design contains between 75-150fields <br />• 1 Avolve Payment Processor (Gavon, Paymentus, Global Transport, Authorized.net) <br />o Design the OAS application to interface wrath Customer's payment processor to <br />allow for online payments through OAS. <br />• 1 OAS Advanced Integration <br />o Defined application data to be pushed to the target permitting system API to <br />allow for creation of the permit and triggering of the Project Creation process <br />into ProjectDox. Design requires API's to be available for customer permitting <br />system. Direct database calls from OAS to the target system are not <br />supported. <br />• 1 OAS Advanced Validation <br />25E-16 Page 11 of 19 <br />