Configure Relationships

Because Wavepoint is published from a map service with Fiber Manager data, most of the relationships below were likely created during your Fiber Manager implementation. However, where Fiber Manager is a flexible data model, Wavepoint is not, and thus you should still confirm the relationships below, and configure them if they are missing.

  • The list below uses the model names for the names of the feature class or object class. Your company might have changed the names of the feature classes and object classes. That is OK, because Wavepoint only cares about the model names assigned to those feature classes and object classes.

  • The list below displays the parent (origin) first and the child (destination) second.

  • For more information about Fiber Manager relationships, see the help topic Create Relationships.

All supported relationships are included in this list, but that does not imply you have to include them in your implementation. For example, Wavepoint supports small form-factor pluggable (SFP) transceivers. If your fiber network does not incorporate those devices, that is OK and you do not need to configure their relationships in your geodatabase.

IMPORTANT: When you Verify your Wavepoint configuration, missing relationships receive a Warning message, but not an Error message due to the fact that some fiber feature classes are optional (just like the SFP transceiver example above). However, if you intend to view fiber facilities in Wavepoint, then those facilities need their relationships configured, and a Warning should be treated as an Error.


  • ACTIVEDEVICE: ACTIVERECEIVEPORT

  • ACTIVEDEVICE: ACTIVETRANSMITPORT

  • ACTIVEDEVICE: SFP

  • BUFFERTUBE: FIBERSTRAND

  • ENDDEVICE: ENDDEVICEPORT

  • ENDDEVICEPOINT: ENDDEVICE

  • FIBERPATCHLOCATION: ACTIVEDEVICE

  • FIBERPATCHLOCATION: ENDDEVICE

  • FIBERPATCHLOCATION: PASSIVEDEVICE

  • FIBERPATCHLOCATION: PATCHPANEL

  • FIBERPATCHLOCATION: RACK

  • FIBERPATCHLOCATION: SPLITTERDEVICE

  • PASSIVEDEVICE: PASSIVECOMMONPORT

  • PASSIVEDEVICE: PASSIVESPLITPORT

  • PATCHPANEL: PATCHPANELCARD

  • PATCHPANELCARD: PATCHPANELFRONTSIDEPORT

  • PATCHPANELFRONTSIDEPORT: PATCHPANELBACKSIDEPORT

  • RACK: ACTIVEDEVICE

  • RACK: ENDDEVICE

  • RACK: PASSIVEDEVICE

  • RACK: PATCHPANEL

  • RACK: SPLITTERDEVICE

  • SFP: SFPCOMMONPORT

  • SFP: SFPSPLITPORT

  • SHEATH: BUFFERTUBE

  • SPLITTERDEVICE: SPLITTERINPUTPORT

  • SPLITTERDEVICE: SPLITTEROUTPUTPORT

QR Code is a registered trademark of DENSO WAVE INCORPORATED in Japan and other countries.

Was this helpful?