Phase 1 (ArcGIS Pro)
Objectives
Upgrade from ArcMap Desktop to ArcGIS Pro (for one client) which would also act as a PoC
Key Activities
Installing ArcGIS Pro (along with Python 3.x)
Obtaining compatible license for ArcGIS Pro for PoC as well as the client
Upgrading all the other supporting libraries and packages like raumel, sqlalchemy, pyodbc versions etc
Upgrading all the code from Python 2.7 to Python 3.x such that it is compatible with ArcGIS Pro
Upgrading the WES Spatial Plugin (to be supported with ArcGIS Pro)
Data integration (and migration if needed) with ArcGIS Pro
Sanity / QA
Architecture
No change. Same as the current one.
Timelines (assuming 1 dedicated resource working on this full time)
Research and analysis (ongoing throughout the process): 1.5 weeks
Initial setup and licensing: 1.5 weeks
Understanding the licensing of ArcGIS Pro (uses a different license type than ArcMap) : 2 days
Apply & get the appropriate license for an internal environment depending upon client requirements and corresponding license capabilities : 1-2 days
Apply the license in ArcGIS Pro : 1 day
Setup a separate internal VDI (using a base client data & code backup): 1-2 days
Check database connections, file connections etc are working fine ArcGIS Pro: 1 day
NOTE: we would be replicating all these steps while setting up PROD environment for the client
Python code, libraries upgrade: 4 weeks
Libraries upgradation, installation and compatibility: 2 days
Python 2.x to 3.x for all scripts and any other ArcGIS Pro compatible changes: 2-3 weeks
Dev testing the new code: 1-2 weeks
Spatial Addin upgrade: 1 week to 1.5 weeks
Checking if current ArcMap plugin works in ArcGIS Pro: 1 day
If not, migrating to ArcGIS Pro compatible plugin: 1 week
Code Changes in the Manual linking, unlinking plugin scripts as required: 2 days
Dev Testing the Manual Linking / Unlinking Addin: 2 days
Data Integration: 1.5 weeks
PLSS and other grid data compatibility check : 1-2 days
Updating all the corresponding spatial views : 1 day
Changes maybe needed depending upon input/output data requirements: shapefiles / file gdb / enterprise gdb : 1 day to 4 days (if not compatible, specific changes required)
Sanity / QA: 2 weeks