Offline Considerations

ArcFM Mobile requires configuration of the ArcFM Sync Service for offline operational maps. For system requirements, refer to the GIS – Supported Versions – ArcFM Mobile Services, Portal, and Tools article on myArcFM.

Is the server machine you have chosen for the Sync Service web-accessible via HTTPS protocol and secured with an SSL certificate? This is required for the Sync Service and recommended for your ArcGIS servers. Refer to Install SSL Certificate for more information.

Does your database use Global IDs for identifiers and relationship classes? This is required for offline ArcFM Mobile. Refer to Offline Data Preparation for more information.

Does your organization’s geodatabase use high-precision geometry storage (as opposed to low precision)? High precision is required for taking ArcFM Mobile offline. Refer to Esri's Spatial reference and geoprocessing article regarding Data migration.

Do your ArcGIS map displays meet the requirements of sync-enabled feature services? This is required for offline ArcFM Mobile. Refer to Map Requirements for more information.

Will you break up your maps into regions so that users can download only the data they need for their region? If so, you must provide a polygon feature class defining the regions. For instructions, refer to Esri’s Feature classes article for more information.

ArcFM Mobile uses the Esri tile package (.tpk) and vector tile package (.vtpk) formats.

Have you implemented Feeder Manager? It is required for tracing in Mobile. The solution supports both Feeder Manager 1.0 and Feeder Manager 2.0 but requires FM1.0 fields to be populated. Therefore, if you are using FM2.0, you must have Feeder Sync enabled to populate the applicable FM1.0 fields.

Plan for your offline needs prior to configuring ArcFM Mobile for offline use.

Do you have maps that use custom fonts for symbols? If so, those font files need to be manually deployed to all mobile devices. Refer to Configure Data for more information.