ArcGIS migration - best practices and challenges - Vytautas Gipiškis HNIT-BALTIC, Lithuania - Esri
←
→
Page content transcription
If your browser does not render page correctly, please read the page content below
ArcGIS migration - best practices and
challenges
Vytautas Gipiškis
HNIT-BALTIC, Lithuania
GIS is Evolving
Influenced by Innovation in Many Areas
Geospatial
Virtualization
cloud
Big Data IoT Technology
Faster Computing
Distributed Processing
Smart Devices
Consumerization
Cloud
Content Applications
Real-Time Analytics
3D Implementation
Apps
Configurable Agile
Crowdsourcing Visualization Open Easier
UAVs Collaborative Ready to Use
ArcGIS Supports Multiple Implementation Patterns
Integrating Cloud and On-Premises Systems
Geo-Enabled
Systems
Portal
Projects Systems System of Systems
EA Account Engagement Cadence
Two approaches on enterprise system implementation
How is It Different?
Server GIS Geospatial Infrastructure
Users Users
App
Apps
… n+1
Services
Services
portal
Web Maps
Data Web Scenes
Data
Web Layers
Two approaches on enterprise system implementation (cont.)
GIS as an infrastructure vs GIS as a stovepipe system
- Stovepipe systems: - GIS as an infrastructure
- Heavily customized - GIS is serving as an organizational infrastructure
- System of engagement, system of insights, system
- Heavily integrated with other IT
of record (GIS is multipurpose)
- Single purpose, mostly system of record.
- Self service mapping, analysis, sharing
- Limited sharing of data or functionality VS - Mostly configure vs heavy customize &develop
- Hight costs to migrate because everyone is
- Mostly business driven (they do they need and
afraid to break, lots of customization and
want, and adjust when necessary based on tools
integration.
they have)
- Migration means full retesting of all
- Data and functionality sharable across the teams
customization
- Less liked by IT, because they do not control them
- Migration might change business processes
Both type of systems have to migrate because …
Change happens in IT: Change happens in Business:
• Other parts of IT aging and upgraded • Connectivity/Access to information
• Changes of the HW Infrastructure • New functionality that available with a new
• Connectivity/Access to information versions
• Regulations & compliance • New business requirements
• Security • Love of new things and curiosity
• Fixes in a new version • Competition (you can do faster/easier/…)
• Lower costs of operation • Lower costs of operation and maintenance
costs
Who are biggest pushers to migrate ?
Our experience …
Biggest innovators/pushers are Business users
• They care about get things done
• 80/20 rule
• Less integrations, or manual integration
• KISS (keep it simple stupid)
• They need it now!
• They want to do themselves, as they understand the business better than IT
• Tired to be hostages of IT/Dev departments (waterfall process)
• Configure vs develop
“we found nine and a half times out of 10 we could change the way we do
business because it wasn’t that critical; it was just habit”
“customizations are invariably more expensive than the no-technology
options - change your process. I’d rather spend this money in my business.”
Best Practice: Migration process
no matter how simple or complex systems you have
• Create a plan
• Inventory the systems to be migrated
• Avoid critical periods
• Define critical functionality, define test scenario
• Get key system users to test all functions that they rely on
• Evaluate and drop the customizations
• Test migration on staging servers (data which is similar with
production) on a cloned/staging env.
• Backup - Plan for the worst
• In case of failure - communicate the problem with the distributor
support about the problem.
• Upgrade staging, test & accept, then production
Best Practice: Application Implementation Strategies
Minimize cost and maximize development resources
• Configure First
• Extend Existing Apps & Templates
• Use the ArcGIS Web APIs and SDKs
Configure first for the lowest cost and least effort
Deviations from “core” increase risk!Best Practice: Environment Isolation
Separate and distinct compute environments
• Production: an operational, real-time compute environment
• Staging: a separate, mirrored, pre-production environment
• Development: a limited scale environment sufficient for primary code and data modeling
Reduce risk and protect operational systems from unintentional changes and negative business impactsRelease General
Version Extended Support Mature Support Retired
Date Availability
June 27, Jun 2019 - May
10.7.1 Jun 2021 - May 2023 Jun 2023 - May 2025 June 01, 2025
2019 2021
March 21, Mar 2019 - Sep
10.7 - Oct 2020 - Mar 2022 April 01, 2022
2019 2020
July 17,
10.6.1 Jul 2018 - Dec 2019 Jan 2020 - Dec 2021 Jan 2022 - Dec 2023 January 01, 2024
2018
January
10.6 Jan 2018 - Dec 2019 Jan 2020 - Dec 2021 Jan 2022 - Dec 2023 January 01, 2024
17, 2018
June 29,
10.5.1 Jun 2017 - Nov 2018 Dec 2018 - Nov 2020 Dec 2020 - Nov 2022 December 01, 2022
2017
December Dec 2016 - Nov
10.5 Dec 2018 - Nov 2020 Dec 2020 - Nov 2022 December 01, 2022
15, 2016 2018
May 31, May 2016 - Jan
10.4.1 Feb 2018 - Jan 2020 Feb 2020 - Jan 2022 February 01, 2022
2016 2018
February
10.4 Feb 2016 - Jan 2018 Feb 2018 - Jan 2020 Feb 2020 - Jan 2022 February 01, 2022
18, 2016
May 13, May 2015 - Nov
10.3.1 Dec 2016 - Nov 2018 Dec 2018 - Nov 2020 December 01, 2020
2015 2016
December Dec 2014 - Nov
10.3 Dec 2016 - Nov 2018 Dec 2018 - Nov 2020 December 01, 2020
10, 2014 2016
April 15,
10.2.2 Apr 2014 - Jun 2015 Jul 2015 - Jun 2017 Jul 2017 - Jun 2019 July 01, 2019
2014
January
10.2.1 Jan 2014 - Jun 2015 Jul 2015 - Jun 2017 Jul 2017 - Jun 2019 July 01, 2019
07, 2014• No patches
• No env certification
• Migrate to
supported version
• Patches for critical things
• New environment • Patches for critical
certification things
• Start new projects here • No env certification
• Start plan to migrateBest Practices: Enterprise
• Avoid zero releases (aka STS, use LTS for production)
• Do not rush on a release day one
• Develop on current version (avoid extended support versions)
• Apply all changes on staging (especially if system is critical)
• Snapshots/Backups for easier things
• Test from the day one, using your workflow/usage patterns.
• Never assume things will not break
• Apply patches
• Old and new can run side by side up to 6 months (migration period)
• The sooner you log a case with Esri support, and in case of bug escalate the
bug – the bigger is your chance to have it fixed on timeBest Practices: ArcMap ArcGIS Pro
- Upgrade license manager,
- Install on other machine machine, test typical workflows! ArcMap
New Innovations
- Always have a backup (independently from upgrades) Support
through
2025
- Do not rush on a release day one
- Apply patches (manual process )
- SU license have 2 authorizations (desktop and e.g. Laptop), to be used
by same person. Test on one, move to production later.
- ArcMap is no longer actively developed. Plan migration to Pro.Best Practices: ArcGIS Pro
- ArcGIS Pro have auto updater.
- Major release (2.1, 2.5, ..) – wait at least month or so
(if you are running critical things). Licensing things above apply.
- If you are running NU model, you can run 3 instances of Pro
simultaneously (assuming all 3 are used by the same person –
Workstation & Laptop & Home PC).
• The sooner you log a case with Esri support, and in case of bug escalate
the bug – the bigger is your chance to have it fixed on time
• ArcGIS Pro does not have backfixes, all fixes are in new versions
only (follow industry practice)Best Practices: Mobile
If you are big, use MDM/EMM to provision the software.
• Someone need to approve (and test) new versions and push to all devices
If you are smaller, then most likely app auto update will do a job for you.
Expect everything will go smooth.
The sooner you log a case with Esri support, and in case of bug escalate the bug – the
bigger is your chance to have it fixed on time
• ArcGIS mobile apps does not have backfixes, all fixes are in new versions
only (follow industry practice)Best Practices: ArcGIS Online
It is always current
It is almost always on, > 99,9% - status.arcgis.com
Follow Esri blog about update announcements
You can test new versions couple weeks before release (apply
for early adopter program)
The sooner you log a case with Esri support, and in case of bug escalate the bug
– the bigger is your chance to have it fixed on timeBest Practices: ArcGIS Monitor • Ubiquitous system monitoring for ArcGIS • Timely metrics and analysis • Proactive insights, alerting, and reports • Optimize the GIS environment
What is monitored?
Health Checks
Log Entry
Usage Statistics
Configuration
Software Security
Health
Services Response Time
Performance Busy Time
Throughput
Usage SOC Usage
CPU
Hardware Memory
Disk
Network
EventsEsri Maintenance Program Get more from Your ArcGIS
Esri global account associated with your org
my.esri.com
Support Statistics, Year 2019:
Lithuania, Latvia and Estonia
#of cases per year in the Baltic states - 513
#of bugs/enhancements - 149
- #82 closed (fixed, know limitation, …non reproducible)., assigned to developers - 21
- Rest are waiting for development review
CSAT 4.7, current quarter – 5 (out of 5)
NPS 67% (HB 79 %)
NPS above 0 is considered “good”, +50 is “Excellent,” and above 70 is considered “world class
8 dedicated professionals (1 in Latvia)Best Practices Documented https://go.esri.com/bp
Thank you for your
attention!
PRESENTER CONTACTS VISIT US
vgipiskis@hnit-baltic.lt
Vytautas Gipiškis Tel. +370 616 10343 www.hnit-baltic.lt
www.maps.ltYou can also read
