Wavepoint XI Implementation
ArcFM Wavepoint XI is an extension of ArcFM Fiber Manager XI, which itself is an extension of ArcFM Editor XI. Thus, prior to implementing and configuring Wavepoint XI, you need to implement and configure Editor XI and Fiber Manager XI. Those applications have dedicated implementation and configuration guides. Ensure you have satisfied their implementations before focusing on Wavepoint XI.
Good to Know
Here are some key considerations while implementing ArcFM Wavepoint XI:
Roles and Scopes
When you are configuring Group Membership for Editor XI, consult the ArcFM Solution XI Series Named User Functionality Matrix to accommodate the roles required for Wavepoint XI. In particular:
-
The role Fiber.Viewer is authorized to access and use Wavepoint XI.
-
The role Fiber.Editor is not authorized to access and use Wavepoint XI.
The Published Map Service
Wavepoint XI uses the same published fiber map service as Fiber Manager XI. Thus, pay particular attention to Publishing the Fiber Map Service, as it is used by both applications.
Further, when you Add Map Service and Configure Domain Network, ensure you toggle Wavepoint on.
Relationships in ArcGIS Pro
All fiber assets belong to one or more relationships, either at the parent level, child level, or both.
This is one example of a full path of relationship from the patch location to the front port:
-
Communications Junction with Asset Group of Patch Location
-
Rack
-
Patch Panel
-
Patch Panel Card
-
Front Port
For Fiber Manager XI functionality to work, these relationships are managed in Understanding Fiber Object Hierarchies.
For ArcGIS Pro and Wavepoint XI functionality to work (such as viewing the relationships within the Attributes pane), these relationships need to be created within the ArcGIS Pro project.
Parent/Child Relationships
When viewing this list of relationships, keep the following in mind:
-
The list below uses the names as found in the Fiber Manager Data Model. If your data model has different names, that is OK, but ensure the equivalent features and tables have the relationships below.
-
The list below displays the parent (origin) first and the child (destination) second. If it is a “sibling” relationship, that is noted below, and it displays the front/common side first and the back/split side second.
-
If your company does not incorporate a certain object (for example, shelf), you can omit its associated relationships.
-
All relationships have the following configuration:
-
Cardinality: One to Many
-
Primary Key: GlobalID
-
Foreign Key: FiberParent
-
The following relationships should be present in ArcGIS Pro:
-
ActiveCommonPort: ActiveSplitPort (sibling) — Foreign Key: ImpliedConnectionSourceGUID
-
ActiveDevice: ActiveCommonPort
-
ActiveDevice: ActiveSplitPort
-
BufferTube: Strand
-
Bundle: Ribbon
-
Communications Junction: Dev
-
Communications Junction: PassiveDevice
-
Communications Junction: Rack
-
Communications Junction: SplitIn
-
Communications Line: BufferTube
-
Communications Line: Bundle
-
Communications Line: Ribbon
-
Dev: DevPort
-
FrontPort: BackPort (sibling) — Foreign Key: ImpliedConnectionSourceGUID
-
PassiveDevice: PassiveDeviceCommonPort
-
PassiveDevice: PassiveDeviceSplitPort
-
PassiveDeviceCommonPort: PassDeviceSplitPort (sibling) — Foreign Key: ImpliedConnectionSourceGUID
-
PP: PPCard
-
PPCard: BackPort
-
PPCard: FrontPort
-
Rack: ActiveDevice
-
Rack: Dev
-
Rack: PassiveDevice
-
Rack: PP
-
Rack: Shelf
-
Ribbon: RibbonStrand
-
Shelf: PassiveDevice
-
SplitIn: SplitOut (sibling) — Foreign Key: ImpliedConnectionSourceGUID
Wavepoint Classic Web.config (Optional)
If you are a Wavepoint Classic customer, it is helpful to have your Wavepoint web.config file handy. You do not necessarily have to replicate all your previous configurations, but having the file handy helps you understand the choices in Solution Center that mirror the previous configurations in Wavepoint Classic.