Modeling telecom systems can pose significant challenges from a data volume perspective. The concept of grouping allows nonspatial objects with shared attribution and topology to be logically grouped together and represented in a telecom domain network using a single row in the database.
When modeling an individual fiber strand in a fiber cable, grouping allows for efficient representation by using unit identifiers and an extended schema to reduce storage requirements. This approach replaces physical groups of objects with system-maintained attributes, which makes interactions with large numbers of similar objects more intuitive and enhances the modeling of connectivity between equipment with large cardinalities, such as ports and transceivers in a switch or router.
Unit identifiers (or unit IDs) are used to identify all objects (for example, ports or fibers) within a piece of equipment that can be connected. A unit ID is unique for each component of the equipment and is managed at the top of an equipment's containment hierarchy to logically group assets in a nonspatial junction object when its asset type is assigned the Unit Identifiable network category.
Consider for example, a 96-strand fiber cable represented below (left) as one line feature with 96 nonspatial edge objects and 96 corresponding containment associations. This can be represented more efficiently as shown below (right) by grouping the strands into a single feature with one edge object and containment association, streamlining the modeling process and reducing the number of records needed to manage the network effectively.
Color schemes can be applied to fiber cables and fiber strands to distinguish and identify the individual units which compose the grouped object. The Modify Associations and Trace panes provide the ability to work with these unit identifiers and color schemes to establish associations and specify trace locations respectively.
Note:
When working with grouped edge and junction objects in a telecom domain network, connectivity is not supported between a grouped edge object and an ungrouped junction object. A generic grouped junction object assigned the Connector Junction network category can be used to transition between grouped and ungrouped objects in this scenario.
An exception to this rule is found in scenarios in which ungrouped unit container devices are connected with grouped edge objects. In this case, connector junctions are not required. The grouped edge object specifies the necessary From and To first unit and num units information for connectivity to be established with the device's unit identifiable junction object contents on validate.