Schneider Electric's ArcFM product suite is an extension of Esri's ArcGIS product suite (ArcGIS for Desktop). Getting started with an ArcFM Geodatabase initially requires setup of an ArcGIS SDE geodatabase. Once a geodatabase has been converted ("ArcFM-ified") to an ArcFM geodatabase, you can add additional features such as Session Manager (for making versioned edits) or Designer (for asset management).
The steps below assume that you are starting from scratch. Depending on the state of the your database, some steps can be skipped or may not be applicable. If you have further questions on your specific situation, please contact Schneider Electric Support (FAQ - Logging a Case - online or phone).
Some general steps are as follows:
- Install and license the DBMS software. ArcFM is compatible with either Oracle or SQL Server. For the full compatibility and support matrix, please refer to: GIS - Supported Versions - 10.2.1a - 10.2.1c ArcFM Desktop, Designer, Designer Express, Network Adapter, Fiber Manager, Conduit Manager, License Manager, and Object Reader for Desktop
- Install and license the ArcGIS software and create a geodatabase.
- Install and license the ArcFM software.
- "ArcFM-ify" the geodatabase by running the Create/Update ArcFM Solution System Tables function to create the ArcFM System Tables. Refer to: How-To - ArcFM - Assign Permissions to ArcFM System Tables.
- Import and populate spatial data.
- If you are importing data from shapefiles, you can use Esri's Copy Feature geoprocessing tool. Refer to: ArcGIS Help (10.2, 10.2.1, and 10.2.2).
- If you are transitioning from a personal (.mdb) or file (.gdb) geodatabase, you can simply copy and paste the desired features.
- There may be a pre-existing ArcFM configuration in the personal or file geodatabase.
- To copy the configuration over, refer to: How-To - ArcFM - Export ArcFM Properties from a Personal/File Geodatabase for Import into an SDE Database.
- Build and configure geometric networks. ArcFM provides powerful tracing and modeling functionality based on these geometric networks.
- Create roles and assign permissions to feature classes.
- At a minimum, there should be an ArcFM_Editor role and an ArcFM_Admin role.
- To ensure that permissions are correctly assigned, this should be performed in ArcCatalog, rather than in SQL Server Management Studio, SQL Developer, or Toad.
- Register feature classes as versioned.
- Users will be able to make their own version of the master DEFAULT database, make edits to their version, and post the edits back to the DEFAULT database.
- A versioned database can track and handle editing conflicts between different versions.
- Add Session Manager: ArcFM Desktop Configuration Guide.
Refer to the ArcFM Solution Resource Center for further documentation on using, configuring, and customizing ArcFM: http://resources.arcfmsolution.com/.