High-Level Architecture of the Geodatabase
During the implementation phase, Schneider Electric appends your existing geodatabase with the required features, tables, and relationships for DHFC.
Network Features
The geodatabase includes a Coax dataset for in-design work. This dataset includes all the features and components the users edit in the DHFC application. The same features are also inserted into the existing Fiber dataset, if they do not already exist. In other words, both the Coax and Fiber datasets contain the same components, the former for in-design work and the latter for the as-built representation and final system of record.
For example, in the following image notice the same set of features are located in both datasets (the image only shows a subset of features for explanation purposes):
In terms of the naming convention, can you see the difference between the two datasets? Notice that in the Coax dataset, all the features end with an “_D” designation. This indicates these are all the in-design representations of the features.
The dataset location and name are the only differences between the two representations of the feature. In other words, the attribute fields on RFCable are identical to the attribute fields on RFCable_D.
The same hold true for object tables. Notice in the following image, the tables are identical aside from the suffix “_D.”
Structure Features
DHFC-specific structures are also appended to the Structure dataset in the geodatabase (or, the Structure dataset is created, if necessary). This is a separate dataset from the Landbase dataset, if you have one. It includes structures such as Address Points, Multiple-Dwelling Units, and underground structures, for example (the following image only shows a subset of features for explanation purposes):
Further, Schneider Electric recommends creating a structure geometric network. Such a network is not necessary for the CoaxDataset_D or for the as-built features in the FiberDataset.