Logical Links data transformation

oEach service is idetified by top level service. Group by top level service

DSEMAN~1_img47

Name identified by Service name

DSEMAN~1_img48

Types and herachy is identified by layer protocol. Also used to map capacity in dse manager

DSEMAN~1_img49

Start and end detatls, NE and Port

DSEMAN~1_img50

Status is identified by AdminState

DSEMAN~1_img51

 

Parent refence is identified supportting reference. The supporting reference is logical assignemnt.

DSEMAN~1_img52

 

The heirachy is ODS->ODU->OTU->OCH->OMS/OCSA->OTS

Protection is determined by protection type. If a service is protected the next level has 2 routing paths and the longest one is assumed to be the proected path in ConnectMaster. Example ODU1-1561078381244 is protected by the  two ODU2s in the nexte level ODU2-1561073973330 & ODU2-1561013722215. By checking the top level routing paths it is determince that  ODU2-1561073973330 is the protection as at OMS/OPS level service goes over more OMS sections.