4.1.7 Mid-term: Data, Editing, & Maintaining

❑ ArcGIS Online/Portal and Web Applications ❑ Ensure key departmental users are aware of access and policies. ❑ Leverage ArcGIS Online/Portal and Web AppBuilder templates for simple, focused web applications for general viewing requirements. ❑ Implement the more intuitive, focused applications from ArcGIS Online and the ArcGIS for Local Government solutions. ❑ Leverage the ArcGIS Solutions Deployment Tool for rapid deployment of template solutions from ArcGIS Pro.

❑ Staffing ❑ Consider moving core GIS technical staff and responsibilities into Information Technology, managing the system as a central, organizational business system. ❑ Review and identify key business users in departments for routine tasks and firstlevel technical support. ❑ Consider regular attendance at Esri’s International User Conference, particularly for core technical users. ❑ Evaluate desired and lacking technical skills for Esri implementation, especially regarding managing the ArcGIS Enterprise server architecture. ❑ Consider professional services for special skills or additional capacity.

4.1.7 Mid-term: Data, Editing, & Maintaining These items are intended to be implemented within 6 - 12 months.

❑ Data Storage & Organize Data ❑ Review current database structure against current ArcGIS for Local Government (AG4LG) and ArcGIS for Water (AG4W) data models. Consider adoption for improved implementation of AG4LG and AG4W solutions. ❑ Consider the ArcGIS Utility Network Management extension for ArcGIS Enterprise at latest available versions for water utility networks. ❑ Consider broader adoption of the ArcGIS for Local Government solutions to provide an organizational framework for data management and solution provision. ❑ Migrate local machine data storage to the enterprise or file geodatabase from personal geodatabases and shapefiles. ❑ Migrate important organizational data currently managed in Excel spreadsheets into geodatabases. ❑ Implement Active Directory groups and database roles as primary database authentication mechanism. ❑ Improve departmental access and understanding of data organization around business use. ❑ Leverage ArcGIS Online/Portal for Organizations subscription accounts to improve data access and enable mobile workflows.

❑ Data Maintenance ❑ Consider Esri’s ArcGIS for Local Government (AG4LG) and ArcGIS for Water (AG4W) solutions including the database schema, editing templates, and web applications. ❑ Consider shifting some development and maintenance of datasets to departmental users. ❑ Engage departments to develop and maintain departmental data. ❑ Consider creating data matrix indicating ownership and maintenance responsibility. City of Miramar, FL | GIS HealthCheck | gisinc.com | page 13

❑ Evaluate needs for mobile data editing, particularly by field staff. ❑ Automate database maintenance tasks (versioning, indexing, compressing).

❑ Data Quality ❑ Review and maintain spatial and attribute indexes. ❑ Evaluate Esri’s AG4LG Data Reviewer template workflows for inclusion in QA/QC processes. ❑ Prepare for migration and implementation of the ArcGIS Utility Network Management to improve utility data maintenance and quality. ❑ Leverage the Attribute Assistant editing extension to ease repeated data editing patterns including those not in the ArcGIS for Local Government model (AG4LG).

❑ Metadata ❑ Review existing or produce metadata for consistency and quality. ❑ Leverage the Attribute Assistant editing extension for feature-level metadata.

❑ Review Hardware Architecture to Support Mid- and Long-term Recommendations ❑ Plan for a three-tier architecture for data, application, and web tiers ❑ Implement a clustered SQL Server database environment. ❑ Provide isolated development, test, and production environments. ❑ Consider need for high-availability and redundancy. ❑ Secure managed services (on-premises or Cloud-hosted) for a consolidated system architecture. Consider public Cloud (Amazon, Azure) hosting and/or ArcGIS Online/Portal for high-demand scalability. ❑ Identify opportunities to consolidate server architecture when available. Deploy stand-alone architecture when business needs (e.g. security, performance) demand isolation. ❑ Upgrade and increase server capacity to support next server life cycle with expected demand for increased internal web applications and public use. ❑ Continue to leverage virtualized server environment. ❑ Consider solid state drives for all virtual servers and heavy GIS users. ❑ Leverage services over direct data access to reduce network load, especially for mobile devices. ❑ Consider Bluetooth-enabled GPS equipment in conjunction with mobile devices.

❑ ArcGIS Enterprise ❑ Use map and geoprocessing services as access foundation to internal staff. ❑ Configure for both separate internal and public access. ❑ Improve performance and access to imagery and data. ❑ Evaluate linked database tables, database views, and RESTful services to support external business systems. ❑ Implement Esri replication and publication database isolation to reduce demand on internal database server, especially for those not requiring live data updates.

❑ ArcGIS Online/Portal for Organizations ❑ Leverage ArcGIS Enterprise as primary data source and services engine. ❑ Expand present use of ArcGIS Online/Portal and ArcGIS Enterprise for publishing web applications. ❑ Use ArcGIS Online/Portal-hosted data for lightweight departmental apps or with infrequently updated data.