Mentum Ellipse typical usagefor VHA

Peter Cheung,Mentum (HK)

11 April 2012

Things to demo in Video (1hr recorded on 12 April 2012 at VHA Brisbane office)

• Install ellipse, VHA PID = 93642-21455-00352• Activate license from hosted server• Checkout project from DM

• for 1st time only

2

• Copy map from hosted server to client• Height/clutter/vectors as coastline, (dark) fibre, BSC/RNC

boundary

• Edit local checkout project• Eg change circuit• Eg change capacity

• View modification (delta between local/DB)• Update/synch local to DB

summary• How to import/export mwlink• How to do batch edit via tabular editor• How to do batch edit via excel import/export

• Export for whole project or selection• Where excel table/column required?• Import excel to planet à log, error, time

• Eg1 add/change new site

3

• Eg1 add/change new site• Eg2 add/change NE at site• Eg3 add/change circuit path• Eg4 allocate circuit capacity from mwlink and/or LL and/or ring• Eg5 allocate port and define port details for NE along circuit path

• How to import/export project to database/local data via command line interface

• this is ONLY for “experienced” admin user who has permission to write back to DB

• Do import/export excel to local/DB without opening ellipse

Tips for Ellipse import/export• Import via excel will add new + update old data in ellipse project, but it will

NOT delete old data. • If need to delete data by batch, best to export all existing data (file ->

export -> excel file) of whole project first, and delete all objects (ctrl-A + Del), edit exported excel and re-import excel back to ellipse afterwards

• Mlink file is “clean” and most flexible way to import/export mwlink related ONLY data, because mfile will NOT affect transport related data like NE and circuit (e.g., port and capacity allocation are unchanged)

4

and circuit (e.g., port and capacity allocation are unchanged)• Update via Tabular editor is slow, but is suitable for column sorting/filtering

“on-the-fly”. User can not delete object in tabular editor, also some field are read-only (ie grey-out)

• Exported excel will contains group/flag, but during excel import, group/flag will NOT get imported. However, group/flag do get store in DB. Best to create group/flag via query conditions

• During excel import, it will do a data consistency check first on excel, it just 1 error is found, NONE of the data will get imported

• Log file of import process can show all error and can be saved

1. Export/import mwlink• Each mlink file is just a zip file which has same folder structure as ellipse project, but only for 1 mwlink

5

• User 1 and export 1 or multiple mwlink to mfile files and send to user 2• user 2 can edit mwlink standalone without open the whole project and updated mfile files• user 2 send updated mlink files back to user 1• user 1 can import 1 or multiple files back to whole project

1. Export/import mwlinkMfile contains only data from mwlink only, it does not contains transport related data (e.g., circuit, NE, port)

6

however, since circuit capacity allocation comes from mwlink available capacity. If mwlink radio is updated with capacity changes, as long as new mwlink capacity>= old mwlink capacity, then previous E1 and/or KLM slot circuit allocation will remain unchanged

1. Export/import mwlink

7

Multiple select mfile and import back to ellipse project

2. Batch edit via tabular editor• Copy from tabular editor to excel/text editor• paste column from excel/text editor back to tabular editor

(but must have same order)• sort ascending/descending• export to excel• can ONLY update existing data, can NOT add/delete data

8

2. Batch edit via tabular editor

9

• format (table/column structure) is same as exported excel• useful for batch update on selected data (e.g., change all mwlink within a group to some capacity xxx)• tabular editor can be used on 1 or multiple selected object for site/mwlink/NE/other tx link/circuit

3. Excel import/export

• exported whole project or selected object to excel(e.g., if select circuit X, Y, Z, then all site/mwlink/LL/ring/NE used by X, Y, Z will dump to excel)• if delete object is required, then after export to excel, delete all object in project• must use pre-defined column/table format in excel• for import, any extra column/table is not pre-defined column/table is allowed, but not used during import• can only import excel 2003 xls format

10

• can only import excel 2003 xls format

3. Excel import/exportImport excel basically have 2 implicit steps• data consistency check• import actual excel table one by one

• If just 1 error occurs, 2nd step of import will NOT start, so ALL excel data will NOT get imported• warning is OK for import, eg antenna tower < antenna ht

• Error log files is detailed enough to indicate which object in which table/column has error• log files can be save to a text file• all excel tables must be present when import to ellipse

11

• If “out-of-memory” error occurs, need to restart ellipse again

• each table is inter-related (i.e., if data in one table is changed, another table also needs to be changed)

Example of import with error

3. Excel import/export

After import process is finished, user can• undo import by ctrl-Z OR• Save project (i.e., update data.xml)

Log can be saved

12

Example of import without error (takes ~3min for whole VHA project)

3. Excel import/export

13

36 excel tables in total, with different # column in each tableSome column only allows number and/or pre-defined set of strings

3. Excel import/export

14

• Each object (site, mwlink, other tx link, NE, ring, circuit) have 5 comments field. The label for comments are defined in project setting

• these labels for comments field will be stored in DB as well

3. Excel import/export

Add new site and change existing site by

15

Add new site and change existing site by• table “Sites”• each row is 1 site with unique ID by column “Name”

For site long/lat projection, it is specified in project setting – datum and projection and degree coordinate specified in project setting – import – import csv/excel

3. Excel import/export

16

Add NE and change NE at existing circuit by

• define NE library with Name/Site/Number of Level, port # per level in table “Network Elements”• add NE in circuit path, by inserting NE within required circuit in table “Circuit_Elements” with column Position incrementing as circuit element ordering along path• column “Input” and “Output” are same for case of NE

3. Excel import/export

17

Add circuit and change existing circuit path by• add new circuit in table “Circuits” with first site=MTX site, last site = terminating BTS/NodeB, capacity #=1, capacity Type=E1

• table “circuit” is extracted from Huawei DD excel with comment2 = customer, Comment 5 = RF cluster

• table “Circuit Elements” consists of NE, mwlink, other tx link as path, these elements must already exist in their respective tables

• circuit path is from Kordia transmission excel ONLY for matched circuit with Huawei DD (e.g, same RNC termination)

3. Excel import/export

Allocate circuit capacity from mwlink or LL/ring

18

Allocate circuit capacity from mwlink or LL/ring

• table “Circuit Allocation” contains allocated capacity, with column “Type” = mwlink, other tx link or ring

• column “position” is circuit path index• column “allocation index” = 1 always for 1xE1 circuit• column “port” = E1 index for E1 based mwlink/other tx link• column “port” = highest hierachical STM/K/L/M for SDH based mwlink/other txlink à e.g., 1xSTM1 with KLM=1.2.3 always has port=1 for STM1=1• column VC3, VC2, VC12 is KLM for SDH based mwlink/other tx link/ring

Reserve or lock TDM based mwlink/LL• table “Microwave Link Subslots” or “other tx link subslots” define KLM in column VC3, VC2, VC12 and column “Locked” = true• fractional E1 or 64k can be added in column “E0”

3. Excel import/export

Assign port allocation to circuit by

• table “circuit connection”, column position = circuit element index, column

Note à port # of huawei equipment needs to refer to a separate port level template to resolve issue of some port level starts from 0 (as a temporary workaround fix)

19

• table “circuit connection”, column position = circuit element index, column “port” = port #, column “connection index” is not used during import, but need to have unique value for each NE connection

• table “connection” represent pair-wise connection between NE àNE or NE à mwlink or LL• column “port 1” and “port 2” are port allocate to NE

4. Command line interfaceImport/export from external excel to/from local client ellipse project OR ellipse DM server (for oracle/SQL DB server)

20

Useful for• wcfclient uses synchronous message as it waits until DB server respond.• import/export without running ellipse (i.e., without ellipse license)• regular backup of DB and/or client local ellipse project as excel files• import/export of selected objects• same import rules apply using wcfclient

Project_name, user_name and password are defined from admin console

4. Command line interface

Export from DM server to excel file xxx e.g., if export_type=CIRCUIT à export all tablese.g., if export_type=SITE à only export site table

21

Import from excel file xxx to DM server