This algorithm uses spring framework pagination to incrementally retrieve node names from each page created by the Page Creator processor. This algorithm uses the following logic:

1. Gets all the node names from EquipmentExportDAO.

2. For each node:

   1. Creates a physical and logical device in the Information Model.

   2. Gets the root equipment (such as a shelf, or rack) from EquipmentExportDAO.

3. For each root equipment:

   1. Verifies that the occupiedMountingPositions attribute value is 0:

      • If yes, the equipment is modeled as a rack.

      • If no, verifies whether the root equipment has a mounting position. If there is a mounting position, the equipment is modeled as a shelf.

   2. Associates the rack and shelf to the physical device and states the equipment type (rack or shelf) in the equipment name.

   3. Retrieves the child equipment hierarchy from EquipmentPositionHierDAO (child equipment are represented as EquipmentPositionHier entities).

   4. Queries the ports in the root equipment hierarchy from EquipmentPortAddressDAO (ports are represented as EquipmentPortAddress entities).

   5. Creates a list that maps card IDs to their ports.

   6. For each EquipmentPortAddress entity, verifies if leafEquipmentId equals EquipmentId.

      • If yes, models the port as a physical port (FTP) and associates it with the parent equipment. Models a media interface, associates it to the physical port, and sets the media interface as a child of the logical device.

      • If no, fills the card ID and all ports with the leafEquipmentId value as the list of associated ports.

   7. Builds the child equipment hierarchy in the Information Model with the EquipmentPositionHier entities.

   8. Saves the modeling information to the physical and logical trees.

The input for this algorithm is the list of EquipmentPositionHier entities and the map of cards-to-ports. Each EquipmentPositionHier is an immediate child (either a card or shelf) of the root equipment. This algorithm uses the following logic:

1. Gets the list of mounting position numbers down the hierarchy for each EquipmentPositionHier entity.

2. For each mounting position number:

   1. Models a shelf object as an equipment entity if its parent is a rack object and the shelf is not yet built in this hierarchy and associates the child with its parent.

   2. Models a card object as an equipment entity if the shelf is already built. Models a slot object as an equipment holder entity for the card. If the slot is already built, models a sub-slot object as an equipment holder entity. Associates children objects with their parent.

   3. Gets the list of ports associated with the card from the map of cards-to-ports.

   4. Models each port as a physical port and a media interface entity. Associates the media interface and the physical port with the logical device.

   5. Adds the EquipmentPortAddressDAO entities to each port as a collection.

MSS and the MSS Integration cartridge distinguish between the following types of circuits:

• STM (physical circuit, such as STM1 or STM4)

• HOT (logical circuit, such as VC4)

• LOP (logical circuit, such as E1, E3, or E4)

Table 5-16 shows the relationship between the imported MSS data, physical TMF814 entities, and physical Information Model entities.

MSS organizes logical circuits as children to physical circuits. The input for this algorithm is the list of EquipmentPortAddress entities produced by the Build Equipment Hierarchy algorithm. This algorithm uses the following logic:

1. For each port entity from the EquipmentPortAddress table:

   1. Gets the CircuitPortAddress instance containing the circuit ID corresponding to an STM link passing through that port.

   2. Queries the CircutExport table to get the STM link with the circuit ID.

   3. Obtains the aPort and zPort for the STM link from the CircuitPortAddress table.

   4. Models the STM link as an optical topological link entity, models its ports as pipe termination point entities, and associates the ports to their link.

   5. Adds the modeled STM link circuit ID to the stmSet collection.

2. Identifies all VC4 HOT circuits for all the STM circuit IDs in the stmSet collection by querying the trail from CircuitPositionDAO. For each trail:

   1. Identifies E4 customer circuits by counting its children in the CircuitPosition table. For each E4 customer circuit:

      • Queries the CircuitExport table for the circuit ID and models the CircuitExport object as a pipe entity.

      • Queries the ports for the circuit from the CircuitPortAddress table, models them as PTPs, and associates them to their pipe entity.

      • Queries the trail path from the CircuitPosition table, models them as trail path entities, and associates them to their pipe entity.

      • Verifies the JKLM value for the trail path, and corrects it if necessary.

   2. Identifies VC4 HOT circuits by evaluating the layer rate code. For each VC4 HOT circuit:

      • Models them as transport pipe entities.

      • Queries the CircuitExport table for circuit ID and models the CircuitExport object as a transport pipe entity.

      • Queries the parent STM link from the CircuitPosition table, and queries the STM link ports from the CircuitPortAddress table.

      • Determines the start-port and end-port from the STM link ports, models them as pipe termination points entities, and associates them to their transport pipe entity.

      • Queries the trail paths from the CircuitPosition table, models them as trail path entities, and associates them to their pipe entity.

   3. Adds the modeled transport pipe circuit ID to the vc4sForLops list.

3. Queries E1 and E3 trail circuits for each VC4 circuit in the vc4sForLop list. For each trail circuit:

   • Queries circuits from the CircuitExport table and models them as pipe entities.

   • Queries customer circuit ports from the CircuitPortAddress table, models them as pipe termination point entities, and associates the ports to the pipe.

   • Queries trail paths from the CircuitPosition table, models them as trail path entities, and associates them to the pipe.

   • Verifies the JKLM value for the trail path, and corrects it if necessary.