2.2 Business Objective 1 Migrate current proprietary software code based Accela implementation to open source code based application that is fully owned and controlled by RLD. High RLD will purchase a cloud based permitting system. Business Objective 2 Maintain or increase by 10% the percentage of business services transactions that can be customer initiated and handled online and outside of regular business hours. Low Using Accela permitting system transaction counts as a baseline. The new systems will increase the transaction counts by 10% Business Objective 3 Maintain or increase the ease-of-use and in the Permitting and Licensing portal application. Low Complaints about the current Accela permitting system will be used as baseline. The new system will have 10% less than baseline. 2.3 Technical Objective 1 Create online permitting application using Low RLD will have a permitting system using industrial
coding and best practices standards. standard coding and best practice standards Technical Objective 2 Create robust data repository for the permitting application program following best practices standards. Low RLD will have a permitting system using a robust data repository following best practices standards. Technical Objective 3 Create a very user friendly public facing interface. Low RLD will have a permitting system with very user friendly public facing interface. Technical Objective 4 Create an easy to use day to day operations interface. Low RLD will have a permitting system with an easy to use day to day operations interface. Technical Objective 5 Create a comprehensive administration interface. Low RLD will have a permitting system will have a comprehensive administration interface. Technical Objective 6 Create a mobile interface for the inspectors. Low RLD will have a permitting system will have a mobile interface for the inspectors. Technical Objective 7 Create an easy way to create new permits or record types. Low RLD will have a permitting system will have easy way to create new permits or record types. Technical Objective 8 Ensure the replacement programs has an unlimited upload document size. Low RLD will have a permitting system will have an unlimited upload document size. 2.4
Laws of 2019, Chapter 11,Section 7, Item 16. $967,000 The funds will only be used for Accela replacement project 5.2. Budget Acquire the software and licensing to implement the permitting and inspection software for construction industries. $413,000 7/1/18 Planning Gather requirements and design workflows for 10 permit types. Select one permit type as a pilot for Go-Live. Design integration interfaces and data migration strategy for the selected permit from Accela SQL Database to new application. $195,000 10/31/2018 Planning Develop application and Contractors Portal with design information for 10 Permit Types. Integrate PSI’s License Import text file, credit card transactions, Geolocation used by inspector’s and document management for plan review and historical documents). Migration of permit records for one permit type from Accela to new application. Configuration of Inspection Software and Mobile Application for one permit type. Go Live with one permit type. $359,000 3/31/2019 Implementation Total $967,000 5.3 initiation $0 planning $608,000 implementation $359,000 Total $967,000
Cost 8.0 M,D,E Dependency 1 Project Certification Committee (PCC). The success of meeting the project deadlines depends on RLD’s ability to expeditiously go through the PCC gates. M Dependency 2 succefull contract creation and signage. M 9.0 Assumption 1 Contract will require Software Development Vendor will stay with project to completion. Assumption 2 RLD and vendor staff will ensure multiple members of each organization are present during requirements gathering and design phases. 10.0 Risk 1 Description - Vendor abandonment (software development): If the contracted vendor were to abandon the project then the project would be halted or seriously delayed. Probability Unlikely Impact High Mitigation Strategy: Continue with reliable vendor Contingency Plan: If the vendor were to abandon the project early in the process, before funds were used then another developer could be brought in. If the vendor were to abandon the project late in the development process it would be possible for existing RLD IT staff to finish the required software development work to finish the project. If neither of these were feasible we would need to turn to one of the other alternatives listed. Risk 2