Loading...
HomeMy WebLinkAboutAGREEMENT BETWEEN AUGUSTA, GEORGIA AND HARRIS COMPUTER TO IMPLEMENT ELECTRONIC PLAN REVIEW SOLUTION Sales Order—Proprietary and Confidential SALES ORDER DESCRIPTION Request Date: January 30, 2017 Order Number Augusta 2017-01 Client/Project: Augusta, GA Requestor: Debbie Freeman Created By Steve Favalaro Description of the Requested Enhancement: Purpose: Augusta has requested the following sales order for the purchase and implementation of CityView Electronic Plans Review for Building Permits. As part of the workflow re-write contract Augusta purchased a partial license to allow for online submittals for Building Permit Application. This sales order includes the additional license fee for Electronic Plans Review, Bluebeam Revu licensing and implementation services as described in the Statement of Work. List of attached documents: Included herein Impact Assessment: Estimated impact to budget, work effort and schedule $24,420 Implementation services $21,820 licensing $4,725 annual maintenance. Travel expenses will be billed at cost and as incurred, and is assumed to be completed with the workflow re-write project. This quote is good for 30 days and the proposal &scope are subject to the Software License and Support Agreement approved by the Augusta Commission on November 15, 2016. Total Estimated Cost: As above Planned Delivery Date: TBD Payment Terms: As per Schedule A of the Statement of Work QUOTATION APPROVAL Print Name Signature Date Client Executive: , Mayor Hardie Davis, Jr . LL 3 y CityView,Executive: YeAAJ n 1 G f&_) O, r 21 fATTEST�� % a,CH���� \ �+ 1 YY' 0 ® d /• ♦ I T'0 en.' £t' k= 0 Statement of Work P41, I. Table of Contents I. TABLE OF CONTENTS 3 II. BACKGROUND &OBJECTIVES 4 III. SCOPE 5 IV. WORK APPROACH 7 V. POST IMPLEMENTATION SUPPORT 12 VI. ROLES & RESPONSIBILITIES 13 VIII. SCHEDULE 19 IX. PROJECT ACCEPTANCE 20 X. CHANGE ORDER MANAGEMENT 21 XI. ISSUES &PROBLEM RESOLUTION 23 kit II. Background &Objectives II. Background & Objectives Augusta (hereinafter the "City") has been a valued CityView customer since 2007. Over the years there have been numerous enhancements and technology changes to CityView. In an effort to gain further efficiencies, reduce paper and improve electronic communication with its customers, Augusta has purchased the licensing and implementation services for CityView Electronic Plans Review. As the City does not currently use CityView for Planning, this implementation only pertains to Building Permits. The objectives of this project are to implement CityView Electronic Plans Review for Building Permits in order to: 1. Increase checks and balances to improve accuracy and consistency of application processing to ensure quality. 2. Reduce the amount of paper being submitted and stored 3. Improve online access and communications with the City's customers. Om 1. ? • III. Scope III. Scope The Project scope: 1. Fully license CityView Electronic Plans Review and provide licensing and support for Bluebeam Revu. 2. Collect City-specific data through a remote data collection (6 hours)for lookup table values, letters, workflow-specific values(assigned to, required dates, responsible departments, resource groups, email triggers), and other related values for Permits & Inspections. This data will be collected, providing the CityView Project Team relevant documentation, letter templates, and by City's completion of the CityView workbook pertaining to CityView Electronic Plans Review. 3. Configure the CityView Electronic Plans Review for Permits& Inspections, using the data collected in the workbooks. This will include the following: a. Lookup table data. b. Custom data fields for specific data capture requirements. c. Adjustments to the solution workflows, including the assigned to, required dates, email notifications, responsible departments and resource groups. d. Configuration of three(3) letter templates for Permits & Inspections. 4. Implement user security settings according to customer completion of organizational role spreadsheets defining the out the box organizational roles inherent in the solutions. 5. Deployment of the configuration changes to the City's Hosted Test environment(Orion V) in preparation for final testing, followed by deployment of changes to the City's Production environment in preparation for go live. 6. Conduct one(1) day of training. 7. Provide one (1) day onsite Go Live Facilitation 8. Ongoing support and maintenance of the software under the CityView Software License and Support Agreement. Exclusions: 1. Provision of hardware, databases and third party software. 2. Setup and support of network infrastructure supporting CityView. 3. Letters over and above the three(3) included in the budget, unless agreed to through change order. 4. Customizations and interfaces unless agreed to through change order. III. Scope 5. Custom workflows, unless agreed to through change order. As part of the workflow re-write project CityView Select workflows are delivered and tailored during that implementation, with sub- workflows connected or disconnected as described in the Inclusions. 6. Any Batch/Scheduled processes unless agreed to through change order. 7. No custom reports unless agreed to through change order. 8. Non-standard configuration —standard configuration would be what is provided in the "Inclusions" above and what comes preconfigured in the system. Examples of non-standard configuration would include: modifying record-level security from what is pre-defined; defining organizational role security criteria other than those defined in the out of the box organizational roles(e.g. read-only access to some sheets, read-write to others); creating batch processes other than those defined in the product for permit expirations and license renewals; creating business rules defining specific outcomes that are tied to specific users of the system only(e.g. message box reminding of a process that needs to be followed but where that message box is only invoked where a specific users is logged into the system). While these are not included in the Project's scope, the configuration tools are provided for City to undergo such configuration itself. ,„ xf i M IV.Work Approach IV. Work Approach The implementation will follow the methodology described below. Sign off will be required following the testing of the configuration prior to Bluebeam user training. Project Kickoff The CityView Project Manager will review all documentation with respect to the implementation in order to prepare the materials for project kickoff. CITYVIEW will prepare an Implementation Project Plan. Module Walkthrouh/Data Collection CityView will conduct remote walkthroughs with Augusta subject matter experts (SMEs) to review the best practice workflows for Electronic Plans Review. Following the walkthroughs, the City will be asked to complete workbooks to define the changes required to allow the best-practice workflows for Electronic Plans Review to be adapted, where necessary, to Augusta's practices. Configuration CityView will configure the environment to incorporate the required changes identified during the remote walkthroughs and defined in the workbook. QualiV Assurance CITYVIEW will undertake quality assurance activities throughout the project. The configuration changes are verified by a peer review committee which includes the project team, members of research and development and management, and occasionally subject matter experts from the customer's side. Review and Validation Remote walkthrough will be conducted to show the SMEs how the environment is now configured and any in-scope changes, identified through testing, will be made by CityView. The City will then complete testing of the new configuration and be asked to formally accept the final configuration prior to end user training. During the Review and Validation sessions CityView will document any changes, corrections, or deficiencies for further action. A customer feedback mechanism is provided within the environment for immediate feedback and reporting of issues to our implementation specialists and developers should the City's SME's conduct additional reviews without the CityView Implementation Specialist present. In Scope Refinements In scope corrections from the process of Review and Validation will be conducted. If out of scope issues are raised through Validation, these will be handled through approved change orders. User Acceptance Testing ,. < IV.Work Approach On completion of the Review and Validation session, the City will be provided a period of 2-4 weeks for additional User Acceptance Testing on their own completely installed test system. The CityView Implementation Specialist will monitor the client's feedback and continue to make any in scope corrections. Provided the acceptance criteria have been met, the City is asked to formally accept the delivered solution for go-live. Final Environment After the final environment receives client sign off CityView will restore the City's Hosted Test environment (Orion V)with the new configured system in order to establish an environment that can be used for training purposes. CityView will also deploy the changes to production just prior to go live. User Training CityView will conduct 1 day onsite training (up to 10 students)to include 4 hours on CityView Electronic Plans Review and four(4) hours of training on the use of Bluebeam Revu markup tools. Additional training tools are available on Bluebeam's website Go-Live CityView will deploy the configuration changes to the Production environment ready for go-live. During go-live CityView will provide one(1) day onsite Go Live Facilitation and will work with the City to record any known issues. The CityView project team is responsible for the resolution of these known issues. 30 days after Go Live CityView will request a formal letter of acceptance(the Statement of Completion, pursuant to the Contractual Services Agreement)that substantiates the product has been delivered and is being used successfully in a live, production environment. In the case of a partial go-live, a completion statement will be requested for that part of the solution that has gone live. During the first 4 weeks after go-live, the project team will begin to familiarize and transition the project to the Technical Support group. At the end of 4 weeks the Project Manager will arrange a formal hand-off involving the City of Augusta the CityView Project Manager and the CityView Support group formalizing the transition of any new defects, bugs and support issues to the Support team. 4fiaaiF IV. Work Approach 11/1 Training plan The training program is designed to provide your end users with the ability to use CityView for their day to day activities and your Subject Matter Experts (SMEs)with the skills to maintain your solution. The table below details the training plan. Training Plan pursow, ! �\ y3 CityView End User This course is designed to train the City's users on the business use Training (onsite) related to Electronic Plans Review. Users are able to: 1. Understand the key concepts that make up the business process. 2. Be able to navigate and complete tasks relevant to the Electronic Plans Review process. Bluebeam Markup This training will focus on basic use of Bluebeam Revu markup tools. Training (remote) ,l' f. 4 .% °L IV. Work Approach 1V2 Matrix of Responsibilities and Work Products ...................................................................................................................................................................................................................................................... The following table provides a summary of the Project. Responsibility and the lead for each step in the Project are defined and the deliverables received by City are presented. Step i jR�nst i L Deliv e b b Project Kickoff CityView CityView PM Hosted Development Environment, Project Plan Completed workbooks & Data collection Share CityView PM signed-off Scope Document, including Budget Validation Configured Development Configuration CityView CityView PM Environment, ready for Validation & Refinement Review and Validation Share CityView PM Completed Validation sessions Sessions Refinements based on Development Environment for Review and Validation CityView CityView PM Final Acceptance Testing sessions User Acceptance User acceptance of the fully Testing City City PM delivered system based on test scripts User Training Share CityView Completed training Trainer Go-live Share CityView PM Live production environment 1V,.3 Documentation Documentation is available through CityView Connect, CityView's on-line content management system. This is the source for the most updated CityView information at any time. City can search for a particular topic or browse through the menu items. The Product Training Guides will step City through a full training session for a particular topic. CityView Connect is accessible directly and within the CityView modules. By clicking the Help button, direct access is provided to the content in CityView Connect. Documentation is targeted to three main groups: business users, system administrators and application developers. Documentation is provided at every level of training, focused on the enabling objectives of the training in question. CityView Connect is the main source of documentation for the City throughout implementation of the Project and beyond. With each CityView release, detailed release notes document the changes zm 44:a , 74 ooOAP IV.Work Approach to the release both for new features, feature changes, and bug fixes. Any exceptions or changes for installation and upgrade are also noted. CityView offers the following documentation: • System technical documentation • System end user's documentation • On-line Help Desk documentation • System/Architecture diagrams • Data Dictionary— under Non-disclosure Agreement • Scope Documentation including — signed-off data collection materials £` V. Post Implementation Support Detailed in the CityView Service Level Agreement. V. Post Implementation Support rirtovi-' log s.s VI. Roles& Responsibilities VI. Roles & Responsibilities Below is a description of the roles and responsibilities of each of the resources in the Project. Your CityView project team is comprised of: ➢ Project Manager ➢ Implementation Specialist/Trainer, ➢ Application Development Team, ➢ Quality Assurance Team. Project Manager He/she is involved in both the facilitation of the project as well as hands-on work in each project phase to ensure that requirements are met and project deliverables are clearly defined. The responsibilities include: 1. Be the primary point of contact for the City's Project Manager 2. Ensure successful delivery of CityView's tasks 3. Participate, where necessary, in gathering of the business process requirements 4. In coordination with the City's Project Manager, create the project schedule and keep this schedule up-to-date throughout the project 5. Coordinate the scheduling of tasks for the implementation according to the project schedule 6. Manage the CityView project resources 7. In coordination with the City's Project Manager, co-conduct the project Kick-off meeting 8. Review and approve CityView's data collection scope documents for Sign-off 9. Seek sign-off on all CityView deliverables and approval documents from the City's Project Manager 10. In coordination with the City's Project Manager, manage scope change control 1. Assist the City's Project Manager in defining the training and Go-Live plans 12. Support City in the Go-Live preparation steps 13. Hold review &status meetings with City's resources 14. Facilitate and provide timely resolutions to issues and concerns as it relates to CityView resources, project issues, etc. ,. VI. Roles& Responsibilities Implementation Specialist/Trainer The Implementation Specialist/Trainer (IS) will work closely with the City through on-site visits, follow up calls, training, and demonstrations in order to define the scope of the configuration effort. The IS configures your CityView environment and prepares the environment for the onsite activities. Typically the IS's also deliver the end-user training and Go-live assistance. Responsibilities include: 1. Provide progress status to the CityView Project Manager 2. Perform the data collection and work with the City's Subject Matter Experts (SMEs) to understand and collect the business requirements 3. Work with the SMEs in designing the CityView Activities workflows 4. Provide best practices recommendation and solutions where applicable 5. Compile the data collection documents for the scope document 6. Configure the Software based on the scope documents 7. Unit test the configuration 8. Provide configured system to Application Developer Team Lead and QA Team lead for configuration review and testing 9. Provide validation and acceptance testing support 10. Work with the City's SMEs to log Validation feedback and correct misconfiguration items 11. Work closely with the CityView, Developers and QA Lead to answer any business related question that might arise Often the IS's are also the Trainers as they are qualified as such and they have the best understanding of the City's configured environment going into the training. Trainers have the following responsibilities: 1. Provide training to the different City groups as follows: i. End Users 2. Provide electronic copies of training materials where applicable 3. Provide electronic copies of training sessions' agendas 4. Leverage adult learning methodology and teaching techniques while documenting and escalating any concerns to the implementation Project Managers Application Development Team Reporting to the CityView Project Manager, the Developers will be responsible for the development of any assigned custom reports or customization requirements. Below is a list of responsibilities to be performed by the Developers: 1. Periodically review the ISs configuration for adherence to best practices and efficiencies and provide guidance and oversight where necessary 9 tiI / VI. Roles& Responsibilities Quality Assurance Team Responsible for testing the quality of your CityView Modules and any customizations and interfaces. They use a combination of automated and manual testing on your environment. Bug Tracker Tools, Unit Testing, and Manual Test Cases are used in a strategic test plan that results in a stable, error free application for delivery. Responsibilities include: 1. Maintain QA environments on the same version as the City's Development Environment for parallel testing and troubleshooting 2. Log test results, log issues in detail and provide issues logs to Application Development team 3. Provide unit testing as detailed within roles above 4. Provide advice on timing and readiness of version releases. We envisage the City's project team is comprised of: ➢ Project Manager, > Subject Matter Experts(SMEs), > Database Administrator, > Systems and Network Administrators, ➢ Testers(often the same people as the SMEs), > Application Administrators > Trainers ➢ End Users City Project Manager The City Project Manager is responsible for the overall City deliverables and the day-to-day management of the project. This resource is the primary liaison between the CityView Team, the City's project team and the Steering Committee. Both Project Managers will work together to meet the objectives, address issues, facilitate resolution and participate in active management of the teams. Below is a list of responsibilities to be performed by the City's Project Manager: 1. Manage all City resources for project related activities 2. Manage the project (budget, timeline, quality, risks, scope, issues, deliverables, etc.) in cooperation with CityView's Project Manager 3. Communicate project status to the Steering Committee, the Executive Sponsor and the project team leveraging updates from CityView's status updates y y - VI. Roles& Responsibilities 4. Create, maintain, manage and refine the project schedule with all its elements in cooperation with the CityView Project Manager 5. Maintain project standards especially Scope & Status reporting 6. Prepare, organize and co-conduct with the project kick-off meetings 7. Manage the delivery and coordination of City project tasks 8. Manage all project deliverables in coordination with CityView's Project Manager 9. Manage and streamline the issue management process in conjunction with CityView Project Manager 10. M.anage project deviations and take necessary corrective actions 11. Participate in gathering of the City's business process requirements when required 12. Plan, manage and execute the Acceptance Test efforts 13. Plan, manage and execute the end user training efforts 14. Provide timely reviews and potential sign-offs on all project deliverables approval documents as presented by the CityView Project Manager 15. Review and accept project milestones 16. Manage the logistical activities of the end user training a. Training facilities b. Students booking c. Scheduling of sessions d. Monitoring and logging the end user attendance 17. Capture the end user feedback 18. Responsible for internal & project communication 19. Provide guidance to project team members zo. Lead the Go-Live preparation planning 21. Participate heavily in the Go-Live preparation tests 22. Must provide Go/ No Go Decision throughout the project phases 23. Must be present for Go-Live City Subject Matter Experts The Business Experts own the business process within their functional areas since they perform these day-to-day business processes. These people collectively form the knowledge base of the City's business process requirements. Such resources will be involved in the Data Collection, as well as approval of the Scope Documentation and testing and acceptance of the configured system. They will further verify that the new configured system meets the City's business requirements as outlined in the Scope Documentation. They will participate in making decisions regarding the business processes and they will help both Project Managers manage the project scope and all the associated deliverables. Below is a list of responsibilities to be performed by the SMEs „„i „� 5 x VI. Roles& Responsibilities 1. Attend data collection & validation training sessions 2. Participate in appropriate project team meetings 3. Work with the CityView IS to provide input into the analysis of the business requirements and review the Scope Documentation 4. Work with the CityView IS to validate the configuration through validation testing 5. Develop appropriate validation test cases based on business scenarios 6. Assist in the development of user procedures 7. Assist the project team in defining user access levels and privileges 8. Assist the project team in the Go-Live support planning 9. Provide end user post implementation Go-Live support where applicable 10. Assist the City's Project Manager in problem resolution 11. Support End User Training and documentation preparation 12. Must be present for Go-Live City Database Administrator This resource will be responsible for setup and maintenance of the different databases (Testing/ Training and Production) during the initial project phase and for any subsequent requirement. Below is a list of responsibilities to be performed by the City's Database Administrator: 1. On-going database configuration, monitoring, tuning and troubleshooting of the database environments 2. Manage production database growth 3. Provide support to the project team during the project implementation as identified in the project schedule 4. Manage the performance of the database 5. Establish and maintain database security and coordinate with application administration the application security levels 6. Include the databases in the normal backup routines and add them to the recovery management plan 7. Coordinate activities with City network and workstation administrators 8. Manage and execute database installation and upgrade patches 9. Participate in user access rights and privileges planning, definition &testing City Systems &Network Administrators These resources will be required to provide assistance to the project team on an as needed basis. Below is a list of responsibilities to be performed by the City's Systems & Network Administrators: VI. Roles& Responsibilities 1. Prepare servers for initial software setup and configuration 2. Provide setup of servers and provide network connectivity 3. Setup testing environments as requested by the City's Project Manager 4. Participate in Go-Live preparation tests 5. Should be present for Go-Live City End Users These resources will be trained on the proposed Modules and components. Below is a list of responsibilities to be performed by the City's End Users: 1. Attend and actively participate in the appropriate training sessions provided by CityView 2. Understand existing business processes as well as the project scope at a reasonable level of detail 3. Have good Windows navigation skills .p RP,MiVIII. Schedule VIII. Schedule The current project plan for the Workflow Re-write project, that was approved by the Augusta Commission on November 15, 2016, will be revised to include the services provided in this Statement of Work. Currently this project plan has a tentative go live of August, 2017 k • ,, IX. Project Acceptance IX. Project Acceptance After delivery of the fully configured solution, we expect the City to undertake acceptance testing using self-generated testing scenarios. Should the testing identify any defects, CityView will provide in-scope fixes at no additional charge in parallel to, or immediately subsequent to, the acceptance testing. After all fixes deemed essential for go-live are provided and retested, the code will be frozen and deployment will commence. Provided the acceptance criteria have been met, the City will be asked to formally accept the delivered solution for Go-live. Following go-live the CityView project team will work with the City to record any known issues. The project team is responsible for the resolution of these known issues. 30 days after Go Live CityView will request a formal letter of acceptance that substantiates the product has been delivered and is being used successfully in a live, production environment to accept permit applications, generate fees, record fee payments and generate correspondence associated with permit and license processing. During the first 4 weeks after go-live, the project team will begin to familiarize and transition the project to the Technical Support group. At the end of 6 weeks the Project Manager will arrange a formal hand-off involving the City, the CityView Project Manager and the CityView Support group formalizing the transition of any new defects, bugs and support issues to the Support team. p ,, F_„ ,y pi ;a,,4/ f,,,,, v, X. Change Order Management X. Change Order Management To ensure timely and effective delivery of the project, the scope will be tightly managed. Project change control procedures will be reviewed with the team at the beginning of the project to ensure that they are clearly understood. This review helps establish a common understanding of the need for project change control and the mechanics for implementing any changes to the scope of the project. Any alterations to the project scope, budget, or schedule will be documented and authorized via the Change Control process. A Change Control refers to any modification and/or new development deviating from the baseline established in the Statement of Work and Scope Document. It includes changes to the software, database, training, consulting services, or related processes. Each modification (or group of modifications) to the Contract, Statement of Work, or Scope Document must be documented and approved by a Change Control Form. All potential changes are compared against the project baseline in terms of functionality, schedule, cost, upgrade capability, maintainability and resources. Change Control requests can be raised by any member of the CityView or City Project Teams. The following steps will be followed with any changes to the baseline system: • The change control process will begin with a team member identifying a function or design alternative not already identified as part of the baseline system or a function that is part of the baseline but because of design issues may impact cost, schedule, or resources • The person requesting the change will complete a Change Control Form and forward it to the appropriate Project Manager to determine cost, resources, and schedule impact, and the PM will forward the request on to their counter-part. Once these are determined, approval by the CityView Project Manager and City Project Manager is required. • Once approved (or denied), the change request is entered into the change control log and is placed on the agenda of the next Joint PM meeting Any impact to the cost, schedule and/or resources will be elevated to City Project Manager and CityView Project Manager for their review and approval. X. Change Order Management Sample Change Order Document CHANGE ORDER DESCRIPTION Request Date: Change #: Client/Project: Requestor: Created By Description of the Requested Change: List of attached documents: Impact Assessment: Estimated impact to budget,work effort and schedule Total Estimated Cost: Planned Delivery Date: Payment Terms: CHANGE ORDER APPROVAL Comments By: Date: Comments: Print Name Signature Date Client PM: Client Executive: CityView PM: CityView Executive: ' x tit Xl. Issues&Problem Resolution Xl. Issues & Problem Resolution An issue refers to any matter that requires someone to make a decision, and about which no agreement has been reached or can be routinely reached. Typically, issues impede project progress until they are resolved. Change Control items may become issues if they're not dealt with quickly, but Change Control items are specific to the process of authorizing design changes that impact scope, schedule or budget whereas issues can be related to anything about the project that needs to be decided. The CityView Project Manager will maintain an issue log and will assign responsibility for the resolution of project issues and reports progress to City's Project Manager and the CityView Project Team. Any Project Manager or team member can submit an issue for logging and resolution. Most project issues are expected to be resolved within the overall Project Team. If the issues are not resolved to the satisfaction of the Project Team, they may need to be escalated to the Project Executive Sponsor or appropriate level. Typical project situations requiring escalation include conflicting resource demands threatening project staffing, group dependencies not being met, scope disagreements and issues with functionality of the project's deliverables nearing release time. X11 Escalation Process: CityView escalation levels in the order listed below: 1. Project Manager 2. Director, Professional Services 3. VP Business Operations City escalation levels in the order listed below: 1. Project Manager 2. Director of IT 3. City Manager Schedule "A" — Payments and Milestones Schedule "A" — Payments and Milestones WWrit irf ii T rl it_, ,1 Mt, , Software Licenses Include: Provides: •Send licensing key for CityView Electronic Invoiced on execution of CityView Electronic Plans Review Plans Review $21,820 this agreement and due 10 named user licenses of Bluebeam •Send instructions for downloading net 30 da s Revu eXtreme Bluebeam Revu y ` g f€ s� 9 a Provides: •All major and minor software upgrades Invoiced on execution of Annual Software Maintenance •Unlimited technical support; $4,125 this agreement and due •Unlimited access to the CityView FTP site net 30 days •Unlimited access to the CityView Connect Bluebeam Revu Annual Software Invoiced on execution of Maintenance First line of support for Bluebeam Revu $600 contract and due net 30 days 3t r Project kick-off and confirmation of project plan. CityView Select Project Kickoff,Workbook Sessions,Data configuration review sessions,with up Invoiced upon delivery Collection(remote) to 6 Subject Matter Experts/session. $1,650 by CityView of data Delivery of Workbook. Collection of collection workbook& Workbook data for Electronic Plans due net 30 days Review for Building Permits. Deployment of configuration changes to the City's Test and Production environment in conjunction with the workflow re-write configuration changes. May include up to 1 Due upon completion of Environment Management upgrade. $1,980 the deployment to the Hosted Test Deliverable is successful set up of environment(Orion V) CityView configuration changes in Production and Hosted Test environment(Orion V). 50% invoiced upon commencement of the Configuration based on completed configuration and due Scope Document and workbooks. net 30 days;and Configuration Deliverable is CityView-Hosted Test $9 075 50% invoiced upon environment(Orion V).ready for scheduling of the first review&validation&configuration review&validation refinement. session and due on or before the first review& validation session. � a � firs ' VP- X56, Schedule "A" —Payments and Milestones Perform remote review session, focusing on configuration and workflow. If it is determined that additional reviews are required outside what is stated in the Statement of Work,an estimate will be provided. Gather validation feedback. Identify Invoiced on the first Remote Review Sessions for Validation and in-scope vs.out of scope feedback. $3,960 remote review session Refinement Implement any in-scope refinements and due net 30 days arising out of the validation. Complete in-scope refinements arising from two to four week final client- acceptance testing. Deliverable is final,end-user-training-ready environment. Written acceptance by client is required. 1 day end-user training for: Invoiced upon •CityView Electronic Plans Review(up scheduling of end user Training(onsite unless otherwise specified) to 10 students) $2,310 training and due on or •Bluebeam Revu(up to 10 students) before the first day of training. Ongoing management of all implementation services. Based on 24 hours of Project Management,should Due upon Project Management delays by the customer occur and $3,465 commencement of data require additional project collection management,time may be billed at $165/hr.upon authorization by the customer. 1 day of onsite facilitation to provide Invoiced on the first day Onsite Go Live Facilitation over-the-shoulder guidance and $1,980 of Go Live Facilitation training to users and due net 30 days. Budget for travel and expenses for services to be conducted on site customer(budget assumes 2 days spent on site, 1 day for end user training and 1 day for Go-Live Facilitation). This training is to be conducted at the same time as the Invoiced and due as Travel&Expenses workflow re-write project training or $600 incurred additional travel costs may be required. If additional travel is mutually agreed to be warranted,this will be charged at cost of flights, accommodation and expenses plus $55/weekday($110/weekend day)per diems&$75/h travel time. 3 Summary of Investment Price Total Professional Services(not including travel&expenses) $24,420 Total Licensing $21,820 Total Project $46240 Travel(estimate) $600 Notes: • The City will ensure the hardware and software requirements necessary for the efficient operation of CityView are present, according to the specifications included herein Schedule "A" —Payments and Milestones • The City shall reimburse CityView for its direct travel expenses, including but not limited to, hotel,airfare,car rental,tolls, parking and airline and travel agent fees;including a travel time rate of$75.00 per hour;a per diem rate of$55.00 for week days and a $110.00 for weekends and statutory holidays that includes all meal,food and telecommunications expenses;and a mileage charge based on the current recommended rate per mile.