My WebLink
|
Help
|
About
|
Sign Out
CITY COUNCIL REGULAR MEETING AGENDA PACKET
City of Pleasanton
>
CITY CLERK
>
AGENDA PACKETS
>
2024
>
0604
>
CITY COUNCIL REGULAR MEETING AGENDA PACKET
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
5/30/2024 8:35:17 AM
Creation date
5/30/2024 8:32:27 AM
Metadata
Fields
Template:
CITY CLERK
CITY CLERK - TYPE
AGENDA REPORT
DOCUMENT DATE
6/4/2024
DESTRUCT DATE
15Y
Jump to thumbnail
< previous set
next set >
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
428
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
View images
View plain text
Statement of Work Page 5 of 10 <br />Proprietary and Confidential <br />WORK DESCRIPTION <br />Accela will perform a migration of the customer’s on-premise Accela environments using MS SQL (up to 3 <br />environments: Support, Test, Production) to the Accela SaaS platform. <br />Steps: <br />1. Customer provides an updated backup of the MS SQL databases for the environments to be <br />migrated <br />2. Perform the database migration (Accela, Jetspeed, AGIS, and ADS databases as required) <br />a. Copy database to Accela site <br />b. Execute preparation and remediation scripts; drop any custom objects <br />c. Import data from the MS SQL DB into Accela SaaS SQL instance <br />3. Execute validation scripts to confirm the schema <br />4. Provision tenant instance in Accela SaaS <br />5. Update environment specific data in the databases <br />6. Load ADS documents <br />7. Start Accela services and validate the system is functional i.e. login, search, create records, etc. <br />8. Execute automated test tool to ensure proper system functionality <br />9. Customer performs migration validation <br />10. Remediate any data issues that found from the migration <br />11. Provide the customer with a backup of the revised SQL DB <br />12. Upgrade EMSE master scripts to the current version <br />13. Migrate and Test integrations <br />o Repoint service endpoints to new URLs <br />o Adjust firewall rules and network topologies as necessary <br />o Update interface EMSE scripting dependences for Azure compatibility <br />o Unit test and ensure base functionality <br />14. Migrate and update SSRS reports (maximum of 50) <br />o Import reports into the Accela SaaS environment <br />o Update reports to remove dependencies on custom objects (stored procedures, <br />functions) <br />o Facilitate customer testing and remediate any issues found resulting from migration <br />15. Validate Ad Hoc reports <br />o Remove dependencies on custom views where possible <br />o Convert to SSRS as needed <br />16. Develop go live plan <br />17. Final go-live/roll back decision <br />18. Execute go live plan <br />19. Provide 2 weeks of post go live support from the project team <br />OUT OF SCOPE <br />Any Coding, conversion or additional services not specifically described in this document is the <br />responsibility of Agency. <br />Page 65 of 428
The URL can be used to link to this page
Your browser does not support the video tag.