Simplification

Hello Everyone, In this article, I plan on doing my best to simplify the Esri Product Suite. When I do this I do run the risk of oversimplification and I just ask all the readers moving forward to take into consideration, and understand that this is meant to help guide, but not be a full-blown definition of what these products can do.

If you go to www.esri.com you will see how they arrange products however if you have been in GIS for a while this may be confusing. I am going to try to break it down.

Now products are categorized by these categories you see in the image.

However, if your like me and started in GIS before the emergence of WebGIS. Esri products may have gone something like this... You use to have ArcMap and Possibly Server. You use to give people in your organization ArcReader, and you possibly may still be doing this. You may have stored data in SHP format and then maybe you started putting it in a database. Some people used Access and some people used SQL. Some people used SDE. You may have served a Map or two on a server to the public and if you gave data out it was through an FTP and or you just shared via an external HD or a thumb drive. If you're still doing it this way it's time to improve...

These changes all started back in 2012 with the release of ArcGIS Online instead of an evolution of GIS, it was coined a revolution of GIS. This was the first start to breaking down silos and getting data in the hands of the decision-makers.

Now we break it down into SaaS - Desktop - Enterprise... Now don't get me wrong there are Developer and PaaS also but the main ones to local government are the first 3...

Below are some quick overviews but if you click on the image above this Esri Product page does a good job and shows almost everything.

Desktop Application: comes in (basic, standard, or advanced)

ArcMap - (Desktop) - Old desktop application 32-bit framework

ArcGIS Pro - (Desktop) - New desktop application 64-bit framework works best with ArcGIS Online and Portal

Web GIS: modern GIS that enables the use of all web apps. (Dashboards, FieldMaps, Survey123, etc... The pathway to collaboration and sharing...)

ArcGIS Online - (SaaS) - This exists in Esri's Cloud and we maintain and update it for you. Because it is in the cloud, utilization is based on Credit Consumption.

ArcGIS Portal - (ArcGIS Enterprise) - Like ArcGIS Online except it exists on your infrastructure and you maintain it.

ArcGIS Server: (ArcGIS Enterprise) - Use to be how we shared our data now can be a component that helps get that data to Portal as well as still serve out rest endpoints if need be. There are multiple server roles that can be added to ArcGIS Server, and it is part of a bigger product ArcGIS Enterprise . Below is an image showing the basic software components of ArcGIS Enterprise.

As you can see ArcGIS Server is just one Component in Enterprise as it use to be basically a stand-alone product. However, because Esri is so modular it still can stand-alone if need be. Check out this Architeing your deployment documentation if you are thinking about standing this up.

Real-Time GIS: Ingesting sensor data and turning it into a format that is streamed inside of ArcGIS can be done with either of these two products.

ArcGIS Velocity - (SaaS) - A SaaS product that lives in Esri Cloud and, compliments ArcGIS Online and helps bring sensor data into your ArcGIS Online.

GeoEvent Server - (ArcGIS Enterprise) - An on-premise server role that can help bring sensor data into your ArcGIS Online and or Portal

Named User Roles: (SaaS or ArcGIS Enterprise) - Named Users are the Identity-based permissions you give to your government employees so they can work in either Portal or ArcGIS Online. You add them to your Portal or ArcGIS Online and Assign them a User Name.

• Viewer —Viewers?can view items that are shared with them by other ArcGIS users and have access to a selection of?apps . This user type is ideal for members of an organization who need to view ArcGIS content in a secure environment.?Viewers?can’t create, edit, share or perform analysis on items or data.
• Editor —Editors?can view and edit data in ArcGIS maps and apps that are shared with them by other ArcGIS users. This user type is ideal for users who need to access and edit data that is shared with them and includes access to a selection of?apps . The?Editor?user type can also be used with custom editing applications created by customers or by?Esri?business partners.?Editors?can’t analyze, create, or share items or data.
• Field Worker —Field Workers?can view and edit data that has been shared with them by other ArcGIS users and have access to a selection of?apps .?This user type is ideal for users who primarily interact with ArcGIS content through field apps. It allows users in the field to view and edit data directly in?ArcGIS Online?or in field apps, share their location and record location tracks, and collect and edit data in the field.?Field Workers?can’t analyze, create, or share items or data.
• Creator —Creators?can create and edit content such as maps and apps, perform spatial analysis using the analysis tools in?ArcGIS Online, collect data, and collaborate and share content for use in apps. Creators have access to a selection of?apps , can view content created by other organization members, and administer users and content in the organization. The?Creator?user type is a good choice for GIS specialists, asset managers, data journalists, and other content creators and collaborators.

If you're looking to modernize your GIS...

Step 1: Create a Centralized GIS and have someone in place to manage it.

Step 2: Choose your architecture do you need Portal if so you should have both ArcGIS Online and Portal Stood Up if you only need ArcGIS Online get it stood up.

Step 3: Identify people in your organization in different departments that could help be your point of contact and possibly in the future become admins in the Portal or AGOL orgs.

Step 4: Identify the needs of the different organizational departments.

Step 5: Do a Software assessment with Esri based on those needs. To make sure you have all the tools you need.

Step 6: Set up Training Based on those needs.

Step 7: Set up Data Models and Governance.

Step 8: Set up Training Governance, Identify the need for training to become admins in the org.

Step 9: Always look to solve problems with the tech.

Just some food for thought.

If you have any questions let me know.

Until Next time Keep up the good work!!!