Você está na página 1de 103

Operator Guidelines

OGL:LMT BSS
OGL:IDF EVOLUTION
A30808-X3247-M72-1-7619

OGL:IDF EVOLUTION

Operator Guidelines
OGL:LMT BSS

Important Notice on Product Safety


DANGER - RISK OF ELECTRICAL SHOCK OR DEATH - FOLLOW ALL INSTALLATION INSTRUCTIONS.
The system complies with the standard EN 60950 / IEC 60950. All equipment connected to the system must
comply with the applicable safety standards.
Hazardous voltages are present at the AC power supply lines in this electrical equipment. Some components may
also have high operating temperatures.
Failure to observe and follow all installation and safety instructions can result in serious personal injury
or property damage.
Therefore, only trained and qualified personnel may install and maintain the system.

The same text in German:


Wichtiger Hinweis zur Produktsicherheit
LEBENSGEFAHR - BEACHTEN SIE ALLE INSTALLATIONSHINWEISE.
Das System entspricht den Anforderungen der EN 60950 / IEC 60950. Alle an das System angeschlossenen
Gerte mssen die zutreffenden Sicherheitsbestimmungen erfllen.
In diesen Anlagen stehen die Netzversorgungsleitungen unter gefhrlicher Spannung. Einige Komponenten
knnen auch eine hohe Betriebstemperatur aufweisen.
Nichtbeachtung der Installations- und Sicherheitshinweise kann zu schweren Krperverletzungen oder
Sachschden fhren.
Deshalb darf nur geschultes und qualifiziertes Personal das System installieren und warten.

Caution:
This equipment has been tested and found to comply with EN 301489. Its class of conformity is defined in table
A30808-X3247-X910-*-7618, which is shipped with each product. This class also corresponds to the limits for a
Class A digital device, pursuant to part 15 of the FCC Rules.
These limits are designed to provide reasonable protection against harmful interference when the equipment is
operated in a commercial environment.
This equipment generates, uses and can radiate radio frequency energy and, if not installed and used in accordance with the relevant standards referenced in the manual Guide to Documentation, may cause harmful interference to radio communications.
For system installations it is strictly required to choose all installation sites according to national and local requirements concerning construction rules and static load capacities of buildings and roofs.
For all sites, in particular in residential areas it is mandatory to observe all respectively applicable electromagnetic
field / force (EMF) limits. Otherwise harmful personal interference is possible.

Trademarks:
All designations used in this document can be trademarks, the use of which by third parties for their own
purposes could violate the rights of their owners.

Copyright (C) Siemens AG 2005.


Issued by the Communications Group
Hofmannstrae 51
D-81359 Mnchen
Technical modifications possible.
Technical specifications and features are binding only insofar as
they are specifically and expressly agreed upon in a written contract.

A30808-X3247-M72-1-7619

Operator Guidelines
OGL:LMT BSS

A30808-X3247-M72-1-7619

OGL:IDF EVOLUTION

OGL:IDF EVOLUTION

Operator Guidelines
OGL:LMT BSS

A30808-X3247-M72-1-7619

Operator Guidelines
OGL:LMT BSS

OGL:IDF EVOLUTION

Reason for Update


Summary:
First Edition for New Release BR 8.0
Details:
Chapter/Section

Reason for Update

All

New Release BR 8.0

Issue History
Issue

Date of Issue

Reason for Update

01/2005

First Edition for new Release BR 8.0

A30808-X3247-M72-1-7619

OGL:IDF EVOLUTION

Operator Guidelines
OGL:LMT BSS

A30808-X3247-M72-1-7619

Operator Guidelines
OGL:LMT BSS

OGL:IDF EVOLUTION

This document consists of a total of 103 pages. All pages are issue 1.

Contents

1
1.1

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Purpose of the IDF Editor Evolution tool. . . . . . . . . . . . . . . . . . . . . . . . . . . 13

2
2.1
2.1.1
2.1.2
2.2
2.3
2.3.1
2.3.1.1
2.3.1.2
2.3.1.3
2.3.2
2.3.3

IDF Architecture and Installation Procedures . . . . . . . . . . . . . . . . . . . . . . .


System Requirements for Microsoft Windows . . . . . . . . . . . . . . . . . . . . . .
Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
System Requirements for Solaris (32-bit and 64-bit) . . . . . . . . . . . . . . . . .
Prerequisites for IDF Editor Evolution Installation. . . . . . . . . . . . . . . . . . . .
Sun Java Runtime Environment (JRE) Installation . . . . . . . . . . . . . . . . . . .
JRE software for Solaris Platform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
JRE software for Windows Platform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Java Communication API Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
IDF Evolution Uninstall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Hints in Case of Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

14
14
14
15
15
16
16
17
19
24
25
25

3
3.1
3.2
3.3
3.3.1
3.3.2
3.3.3
3.3.4
3.3.5
3.3.6
3.3.7

Foundamentals of the IDF Editor Evolution . . . . . . . . . . . . . . . . . . . . . . . .


Purpose of the IDF Evolution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
File Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
IDF Editor Evolution Graphical User Interface (GUI) . . . . . . . . . . . . . . . . .
Title Bar. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Menu Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tool Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Root Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Inventory Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ASCII window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Status Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

26
26
26
28
28
29
29
29
30
31
31

4
4.1
4.1.1
4.1.1.1
4.1.1.2
4.1.1.3
4.1.1.4
4.1.1.5
4.1.1.6
4.1.1.7
4.1.1.8
4.1.1.9
4.1.1.10
4.1.2
4.1.2.1
4.1.2.2

Menu and Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


Menu Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
File Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Open Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Close Command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Save Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Save As Command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Attach Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Set SBS_Equip_Pos Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Set Functional Address Rack Position Command . . . . . . . . . . . . . . . . . .
Remove NOB RIUs Command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Search Command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Exit Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Export Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Export C_IDF Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Export C_TXT Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

32
32
32
32
33
34
34
35
36
37
38
39
41
42
42
43

A30808-X3247-M72-1-7619

OGL:IDF EVOLUTION

Operator Guidelines
OGL:LMT BSS

4.1.2.3
4.1.2.4
4.1.2.5
4.1.3
4.1.3.1
4.1.4
4.1.4.1
4.1.4.2
4.1.4.3
4.1.5
4.1.5.1
4.1.5.2
4.1.5.3
4.1.5.4
4.1.6
4.1.6.1
4.1.7
4.1.7.1
4.1.7.2
4.2
4.2.1
4.2.1.1
4.2.2
4.2.2.1
4.2.2.2
4.3
4.3.1
4.3.1.1
4.3.1.2

Export IDT Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43


Export IDF Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Export NOB Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
View Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
All, nob_RIus, ob_RIUs commans . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Hardware Table Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Insert Record Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Delete a HW Record Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Modify a HW Table Command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Options Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Select On Click. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Hide ASCII File Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Look and Feel Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Switch Command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Tools Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Set Scanner Port Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Help Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Help Contents Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
About IDF Evolution Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Pop Up Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Root Pane Pop Up Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Create an S-I Record Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Inventory Panel Pop Up Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Delete an S-I Record (S-I Stands for Structure and Inventory) Command 61
Edit an I Record (I Stand for Inventory) Command . . . . . . . . . . . . . . . . . . 62
2D Code Reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
METHANETICS CORPORATION IR-2000 . . . . . . . . . . . . . . . . . . . . . . . . . 64
Hardware Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Using the 2D Code Reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

5
5.1
5.1.1
5.1.1.1
5.1.1.2
5.1.1.3
5.1.2
5.1.2.1
5.1.2.2
5.1.3
5.1.4

Inventory Data Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67


Procedure: Update of a nob_RIU. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Step by Step Approach . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
In Case a Nob_RIU is Newly to Be Created . . . . . . . . . . . . . . . . . . . . . . . . 68
In Case a Nob_RIU is Already Present and is to be Replaced . . . . . . . . . . 70
In Case a Nob_RIU is Already Present and has to be Removed. . . . . . . . . 71
Automated Approach in Case the IDF File is imported from the RLC . . . . . 72
Logistics: Inventory Data Delivered by RLC to the Project . . . . . . . . . . . . . 72
Procedures: How to put the Inventory Data into the Network Element . . . . 76
Export IDF File for Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Export NOB for Downloading to the Network Element. . . . . . . . . . . . . . . . . 98

6
6.1

Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Use of the IDF Editor Evolution within RC Scripts . . . . . . . . . . . . . . . . . . . 101

Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

A30808-X3247-M72-1-7619

Operator Guidelines
OGL:LMT BSS

OGL:IDF EVOLUTION

Illustrations
Fig.
Fig.
Fig.
Fig.
Fig.
Fig.
Fig.
Fig.
Fig.
Fig.
Fig.
Fig.
Fig.
Fig.
Fig.
Fig.
Fig.
Fig.
Fig.
Fig.
Fig.
Fig.
Fig.
Fig.
Fig.
Fig.
Fig.
Fig.
Fig.
Fig.
Fig.
Fig.
Fig.
Fig.
Fig.
Fig.
Fig.
Fig.
Fig.
Fig.
Fig.
Fig.

A30808-X3247-M72-1-7619

2.1
2.2
2.3
2.4
2.5
2.6
2.7
2.8
2.9
2.10
2.11
2.12
2.13
3.1
3.2
3.3
3.4
3.5
3.6
3.7
3.8
3.9
3.10
3.11
4.1
4.2
4.3
4.4
4.5
4.6
4.7
4.8
4.9
4.10
4.11
4.12
4.13
4.14
4.15
4.16
4.17
4.18

JRE Solaris Download: Choice of the Edition Version. . . . . . . . . . . . . . 17


JRE Solaris Download: Choice of the Version. . . . . . . . . . . . . . . . . . . . 17
JRE Solaris Download: License Agreement . . . . . . . . . . . . . . . . . . . . . 18
JRE Solaris Download: Choice of the SW . . . . . . . . . . . . . . . . . . . . . . . 19
JRE Installation: Startup Window (Windows Version) . . . . . . . . . . . . . . 20
JRE Installation: License window (Windows Version) . . . . . . . . . . . . . . 20
JRE Installation: Setup Preparing (Windows Version). . . . . . . . . . . . . . 21
JRE Installation: Setup window (Windows Version) . . . . . . . . . . . . . . . 21
JRE Installation: Installation window - phase 1 (Windows Version). . . . 22
JRE Installation: Installation window - phase 2 (Windows Version). . . . 23
JRE Installation: Installation window - phase 3 (Windows Version). . . . 23
JRE Installation: End Icon (Windows Version). . . . . . . . . . . . . . . . . . . . 24
Example of IDF Editor Evolution Startup Window . . . . . . . . . . . . . . . . . 25
File Types Graphical Representation. . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Example of Exporting C_IDF or C_TXT file . . . . . . . . . . . . . . . . . . . . . . 27
Input and Output IDF Evolutions File Types . . . . . . . . . . . . . . . . . . . . . 27
IDF Editor Evolution Main Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Title Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Menu Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Tool Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Root Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Inventory Panel. Only OB RIUs are Displayed. . . . . . . . . . . . . . . . . . . . 31
ASCII Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Status Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
File Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Open Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Open Dialog Box Example with Windows XP OS.. . . . . . . . . . . . . . . . . 33
Close Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Save Command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Save As Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Attach Command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Set SBS_Equipement_Position Command . . . . . . . . . . . . . . . . . . . . . 36
Set SBS_Equipement_Position Dialog Box . . . . . . . . . . . . . . . . . . . . . . 36
Set F.A. RACK_Position Command . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Set RACK_Position (Functional Address) Dialog Box . . . . . . . . . . . . . . 37
Remove nob_RIUs Command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Search Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Search Dialog Box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Search Dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Exit Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Export Menu (in this example an IDF file has been opened). . . . . . . . 42
C_IDF Export Command (in this example a ZDT file has been opened)
42

OGL:IDF EVOLUTION

Operator Guidelines
OGL:LMT BSS

Fig. 4.19
Fig. 4.20
Fig. 4.21
Fig. 4.22

10

Fig.
Fig.
Fig.
Fig.
Fig.
Fig.
Fig.
Fig.
Fig.
Fig.
Fig.
Fig.
Fig.
Fig.
Fig.
Fig.
Fig.
Fig.

4.23
4.24
4.25
4.26
4.27
4.28
4.29
4.30
4.31
4.32
4.33
4.34
4.35
4.36
4.37
4.38
4.39
4.40

Fig.
Fig.
Fig.
Fig.
Fig.
Fig.
Fig.
Fig.
Fig.
Fig.
Fig.
Fig.
Fig.
Fig.
Fig.
Fig.
Fig.
Fig.
Fig.

4.41
4.42
4.43
4.44
4.45
4.46
4.47
4.48
4.49
4.50
5.1
5.2
5.3
5.4
5.5
5.6
5.7
5.8
5.9

Export C_TXT Command (in this example an ZDT file has been opened)
43
Export IDT Command (in this example an IDF file has been opened) . 43
Export IDF Command (in this example an IDT file has been opened) . 44
Export NOB Command
(in this example an IDT file has been opened) . . . . . . . . . . . . . . . . . . . . 44
View Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
All Records view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
View only nob_RIUs records. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
View only Ob Records . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Hardware Table Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Insert Record window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Delete Record window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Modify Record Selection window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Modify Record window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Options Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Select on Click Option Enabled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Select on Click Option Disabled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Hidden ASCII window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Look and Feel Command in case of Windows Operating System . . . 55
Switch Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Tools Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Set Scanner Port Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Error dialog box related to the search serial number function
(in case of a wrong port has been selected) . . . . . . . . . . . . . . . . . . . . . . 56
Help Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Help Contents window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
About IDF Evolution window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Create New nob_RIU Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
New NOB_RIU panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Panel for inserting the requested inventory data . . . . . . . . . . . . . . . . . . 60
Delete S-I Record Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Edit an I Record Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Edit I Record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
2D Code Reader Targeting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Open selected File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Insert a New Nob_RIU - Step 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Insert a New Nob_RIU - Step 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Insert a New Nob_RIU - Step 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Insert a New Nob_RIU - Step 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
2D-Code Reader. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Port Setting for 2D-Code Reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Replacement of a Nob_RIU - Step 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Replacement of a Nob_RIU - Step 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

A30808-X3247-M72-1-7619

Operator Guidelines
OGL:LMT BSS

OGL:IDF EVOLUTION

Fig.
Fig.
Fig.
Fig.
Fig.
Fig.
Fig.
Fig.
Fig.
Fig.
Fig.
Fig.
Fig.
Fig.
Fig.
Fig.
Fig.
Fig.
Fig.
Fig.
Fig.
Fig.
Fig.
Fig.
Fig.
Fig.
Fig.
Fig.
Fig.
Fig.
Fig.
Fig.
Fig.
Fig.

5.10
5.11
5.12
5.13
5.14
5.15
5.16
5.17
5.18
5.19
5.20
5.21
5.22
5.23
5.24
5.25
5.26
5.27
5.28
5.29
5.30
5.31
5.32
5.33
5.34
5.35
5.36
5.37
5.38
5.39
5.40
5.41
5.42
5.43

Fig.
Fig.
Fig.
Fig.
Fig.
Fig.
Fig.
Fig.

5.44
5.45
5.46
5.47
5.48
5.49
5.50
5.51

A30808-X3247-M72-1-7619

Delete a Nob_RIU - Step 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72


Confirmation of the deletions operation . . . . . . . . . . . . . . . . . . . . . . . . 72
IDFs Delivered with the BTS Equipment . . . . . . . . . . . . . . . . . . . . . . . . 73
Put Inventory Data into N.E. - Step 1. . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Put Inventory Data into N.E. - Step 2. . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Put Inventory Data into N.E. - Step 2.1 . . . . . . . . . . . . . . . . . . . . . . . . . 78
Put Inventory Data into N.E. - Step 3. . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Put Inventory Data into N.E. - Step 3.1 . . . . . . . . . . . . . . . . . . . . . . . . . 79
Put Inventory Data into N.E. - Step 3.2 . . . . . . . . . . . . . . . . . . . . . . . . . 79
Put Inventory Data into N.E. - Step 4. . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Put Inventory Data into N.E. - Step 4.1 . . . . . . . . . . . . . . . . . . . . . . . . . 80
Put Inventory Data into N.E. - Step 4.2 . . . . . . . . . . . . . . . . . . . . . . . . . 81
Alert Message for Saving File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Confirmation of File Saved. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Put Inventory Data into N.E. - Step 5. . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Put Inventory Data into N.E. - Step 5.1 . . . . . . . . . . . . . . . . . . . . . . . . . 82
Confirmation of NOB File Saved . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Alert Message for Exporting File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Put Inventory Data into N.E. - Step 6. . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Put Inventory Data into N.E. - Step 7. . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Put Inventory Data into N.E. - Step 7.1 . . . . . . . . . . . . . . . . . . . . . . . . . 85
Put Inventory Data into N.E. - Step 8. . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Put Inventory Data into N.E. - Step 8.1 . . . . . . . . . . . . . . . . . . . . . . . . . 86
Put Inventory Data into N.E. - Step 8.2 . . . . . . . . . . . . . . . . . . . . . . . . . 87
Put Inventory Data into N.E. - Step 9. . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Ask for Removing all Redundant nob_RIU . . . . . . . . . . . . . . . . . . . . . . 87
Confirmation of Deletion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Put Inventory Data into N.E. - Step 9.1 . . . . . . . . . . . . . . . . . . . . . . . . . 88
Put Inventory Data into N.E. - Step 9.2 . . . . . . . . . . . . . . . . . . . . . . . . . 89
Put Inventory Data into N.E. - Step 9.3 . . . . . . . . . . . . . . . . . . . . . . . . . 90
Put Inventory Data into N.E.- Step 10 . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Put Inventory Data into N.E. - Step 11. . . . . . . . . . . . . . . . . . . . . . . . . . 92
Pre-Processing of IDFs of Delivered Racks. . . . . . . . . . . . . . . . . . . . . . 93
Import of modified nob_RIU for the Racks in the Network Element IDF file
94
Download of the modified nob_RIU File to the related Network Element95
Export IDF File for backup purpose - Step 1 . . . . . . . . . . . . . . . . . . . . . 96
Export the IDF File - Step 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Export IDF File - Step 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Export NOB - Step 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Export NOB - Step 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Export NOB - Step 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Export NOB - Step 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

11

OGL:IDF EVOLUTION

Operator Guidelines
OGL:LMT BSS

Tables
Tab.
Tab.
Tab.
Tab.
Tab.
Tab.

12

2.1
3.1
4.1
4.2
5.1
5.2

System Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Format Conversion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Operating Parameters for the IR-2000HD . . . . . . . . . . . . . . . . . . . . . . . 64
Decode Options for the IR-2000HD . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Example of Filenames of IDFs Coming from the RLC . . . . . . . . . . . . . . 74
Default Values within IDF of RLC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

A30808-X3247-M72-1-7619

Operator Guidelines
OGL:LMT BSS

OGL:IDF EVOLUTION

1 Introduction
This manual has two purposes. The first purpose is to introduce the remote inventory
feature to the reader providing a general description of its main functionality implemented in the BSS Network Elements (BSC, BTS, TRAU). The second purpose is to
provide a consistent and efficient user guide for the management of the inventory data
supported by the functions implemented in the IDF Editor Evolution tool released for the
first time in the BSS BR 7.0 release. The term Evolution is related to the enhancement
of the IDF Editor tool supporting up to the BR7.0 release the user in the complete
process of the inventory data management.

1.1

Purpose of the IDF Editor Evolution tool


The Inventory Editor Evolution Tool (IDF Editor Evolution) is a very powerful software
application supporting users in the management of the Inventory data related to the
Siemens Base Station System (BSS). It provides functions supported by a powerful and
user friendly Graphical User Interface for the manual handling and for the collection of
the inventory data for the functional and physical identification of the hardware and software modules installed and configured on each Network Element (BSC, BTS, TRAU).
All the Least Replaceable Units (LRUs) that are in the scope of the inventory data are
called Remote Inventory Units (RIUs). An hardware module is identified by its Product
Identification Data (PID) which consists of at least an item number with issue and serial
number, and can be supplemented by the manufacturer's code, product designation,
repair data and modification data.
Two types of hardware resources are in the scope of the Remote Inventory feature:
Hardware resources with an on-board memory on which the PID is stored are called
On board memory RIU (ob-RIU).
Hardware resources without an on-board memory on which the PID is stored are
called Non On board memory RIU (nob-RIU).
The inventory data related to the ob-RIUs can be read automatically by the Remote
Inventory Scanning Procedure triggered on the related BSC when the user activates
from the LMT Evolution the Inventory data table generation. At the end of the procedure
the data are stored in S/I records of the table.
The inventory data related to the nob-RIUs are managed off-line by using the IDF Editor
Evolution tool. The file storing nob-RIU data (NOB file) has to be uploaded on the LMT
Evolution and stored in a local directory accessible also from the Inventory Editor Evolution tool. The NOB file can be modified on the IDF Editor Evolution, saved in a directory
accessible also from the LMT Evolution and then it is downloaded again from the LMT
Evolution to the BSC in which it is stored in a specific directory. The IDF Editor Evolution
tool is an independent tool. This means that it can be installed on a different machine on
which it is installed the LMT Evolution application. For the purpose a suitable and adhoc installation procedure has been implemented for the IDF Evolution tool. The procedure is described in detail in the chapter 2: IDF Architecture and installation procedures.

A30808-X3247-M72-1-7619

13

OGL:IDF EVOLUTION

Operator Guidelines
OGL:LMT BSS

2 IDF Architecture and Installation Procedures


In this chapter the hardware and software characteristics of the IDF Editor Evolution tool
together with the installation procedures are described.

2.1
i

2.1.1

System Requirements for Microsoft Windows


The Installation of the Java 2 Runtime Environment on a non-supported version of
Microsoft Windows or on a machine that does not have a sufficiently up-to-date Service
Pack generates the following warning message: "We recommend that you do not install
this Java Platform for the following reasons: This Java Platform does not support the
operating system or operating-system service pack on this machine".

Hardware
The IDF Editor Evolution can support two different hardware configurations, as follow:
Notebook configuration (portable):
The notebook must be a PC (for example a Siemens Scenic 510) and it must have
these mandatory elements for Notebook configuration:
CPU Intel Pentium 166MHz or a faster processor;
64 megabytes recommended with Windows NT, 128 megabytes with Windows
2000 and Windows XP; at least 48 megabytes of RAM is recommended for
applets running within a browser using the Java Plug-in;
Hardisk 4 Gigabytes IDE internal;
Floppy disk drive;
CD ROM drive;
LCD TFT Active Color 13,3" SVGA;
2 Serial ports (COM1 and COM2); a RS232 serial port is required in order to use
Java Communication API;
Mouse;
Li-Ion-Akku battery;
O/S: Windows NT/2000/XP.

14

Desktop configuration:
For the Desktop configuration an IBM Compatible PC is mandatory and it shall be
configured as follow:
Intel and 100% compatible processors are supported. A Pentium 166MHz or
faster processor is recommended;
O/S:Windows NT, Windows 2000, Windows XP;
64 megabytes recommended with Windows NT, 128 megabytes with Windows
2000 and Windows XP; at least 48 megabytes of RAM is recommended for
applets running within a browser using the Java Plug-in;
a Free Expansion slot ;
Color monitor;
Mouse;
SVGA 640x480;
2 Serial ports (COM1 and COM2); a RS232 serial port is required in order to use
Java Communication API;
CD ROM drive.

A30808-X3247-M72-1-7619

Operator Guidelines
OGL:LMT BSS

2.1.2

OGL:IDF EVOLUTION

Software
The IDF Editor Evolution runs on Sun Java RunTime Environment (JRE). It is supported
on:
Windows NT 4.0 (with Service Pack 6a);
Windows 2000 Professional (with Service Pack 3);
Windows XP Home;
Windows XP Professional (with Service Pack 1);
Windows Server 2003 (Web, Standard, Enterprise, and Datacenter Editions in 32bit).
The IDF Editor Evolution application can be installed on a Personal Computer
supporting one of these operating systems, in a directory defined by the user. After the
installation of IDF software on the IDF hard disk has been performed, the IDF directory
created by the user does not contain the whole IDF Evolution software.
Furthermore, at least Comctl32.dll version 4.72 is required for Windows NT 4.0. The
required version is installed with Microsoft Internet Explorer 4.01 or later (out-of-the-box
Windows 2000 Professional installations a match this requirement).

2.2

System Requirements for Solaris (32-bit and 64-bit)


The IDF Editor Evolution tool runs on Sun JRE so it requires Solaris 7, Solaris 8, or
Solaris 9 Operating Systems.

In case x86 processors are installed it is recommended to set the display color depth to
16 bit or higher.
Prior to installing the Java 2 Runtime Environment, it should be ensured that the full set
of required patches needed for supporting this release have been installed. Recommended and required patches are available for download from the SunSolve website.
(refer to the Sun site: http://java.sun.com).
For more detailed informations about which font packages should be set on the system
see also the following Solaris Font Package Requirements:
Platform

Version

Desktop Managers

Solaris SPARC
System Requirements
32-bit: SDK J2RE
64-bit: SDK J2RE

Solaris 9 (32/64 bit)

Gnome2-metacity, CDE-dtwm

Solaris 8 (32/64 bit)

CDE-dtwm/OpenWin-olwm

Solaris 7 (32 bit)

CDE-dtwm/OpenWin-olwm

Solaris x86
System Requirements (same as
SPARC 32-bit)

Solaris 9 (32/64 bit)

Gnome2-metacity, CDE-dtwm

Solaris 8 (32/64 bit)

CDE-dtwm/OpenWin-olwm

Solaris 7 (32 bit)

CDE-dtwm/OpenWin-olwm

Windows XP Professional
(SP1)

Windows Active & Classic Desktop

IA32 Windows
System Requirements 32-bit: SDK
J2RE
Tab. 2.1

A30808-X3247-M72-1-7619

System Configurations

15

OGL:IDF EVOLUTION

Operator Guidelines
OGL:LMT BSS

Platform

Tab. 2.1

2.3

Version

Desktop Managers

Windows XP Home

Windows Active & Classic Desktop

Windows 2000 Professional (SP3)

Windows Active & Classic Desktop

Windows NT 4.0 (SP6a)

Windows Active & Classic Desktop

Windows Server 2003,


Web Edition

Windows Active & Classic Desktop

Windows Server 2003,


Standard Edition

Windows Active & Classic Desktop

Windows Server 2003,


Enterprise Edition

Windows Active & Classic Desktop

Windows Server 2003,


Datacenter Edition

Windows Active & Classic Desktop

System Configurations

Prerequisites for IDF Editor Evolution Installation


For using the IDF Editor Evolution the following applications and programs shall be
installed:
1. Sun Java Runtime Environment (JRE) for Solaris or Windows platform;
2. Java Communication API;
3. IDF Editor Evolution main Application.
Sun Java Runtime Environment (JRE) program for Solaris can be downloaded from
Java Sun site http://java.sun.com.
The Sun Java Runtime Environment (JRE) for Windows version 1.4.2.1, the Java
Communication API and the IDF Editor Evolution applications are available in an IDF
Evolution compressed file (for example the file: 10000.tar.z).
For any problem related to JRE or javacommunication please refer to Sun site
http://java.sun.com.

2.3.1

Sun Java Runtime Environment (JRE) Installation


The IDF Editor Evolution application needs the Sun Java Runtime Environment (JRE)
version 1.4.2.1 or superior to run correctly.

16

A30808-X3247-M72-1-7619

Operator Guidelines
OGL:LMT BSS

2.3.1.1

OGL:IDF EVOLUTION

JRE software for Solaris Platform


The JRE for Solaris can be downloaded from java Sun site (http://java.sun.com), usually
the JRE can be found under the J2SE download page (see the Fig. 2.1).

Fig. 2.1

JRE Solaris Download: Choice of the Edition Version

The download of JRE for Solaris software is started and a number of panels are shown
on the screen. The main panels are described below.
The choice of the software Java Runtime Environment (JRE) version 1.4.2 or superior
is show in the Fig. 2.2.

Fig. 2.2

JRE Solaris Download: Choice of the Version

Then the License Agreement window (see the Fig. 2.3) is displayed: Then the user
shall select the buttons: Accept and Continue.

A30808-X3247-M72-1-7619

17

OGL:IDF EVOLUTION

Operator Guidelines
OGL:LMT BSS

Fig. 2.3

JRE Solaris Download: License Agreement

The Fig. 2.4 shows the software that shall be to downloaded. The choice between 64
or 32 bit depends on the type of Solaris Computer. The name of the file downloaded is
(for example):
j2re-1_4_2_03-solaris-sparc.sh for 32 bit;
j2re-1_4_2_03-solaris-sparcv9.sh for 64 bit.

18

A30808-X3247-M72-1-7619

Operator Guidelines
OGL:LMT BSS

OGL:IDF EVOLUTION

Fig. 2.4

JRE Solaris Download: Choice of the SW

It is recommended to refer to their installation procedure in order to assure a correct


installation. The installation procedure has been written in the Installation Instruction as
represented in the Fig. 2.2.

2.3.1.2

JRE software for Windows Platform


The JRE software version 1.4.2.1 for Windows is released together with the IDF Editor
Evolution file.
The installation procedure checks automatically if the JRE software is already installed
on the machine on which the IDF Editor Evolution shall be installed.
In case the JRE software is not installed the user is asked by a specific pop-up window
to confirm the installation of the JRE program. If the user confirms by clicking the button
OK the installation procedure starts the installation of the JRE software.
Within the pop-up window the user is informed that the JRE installation is permitted only
to the system administrator. On the contrary the JRE installation is aborted and consequently the IDF Editor Evolution will not be installed.
The main panels automatically displayed to the user by the JRE installation procedures
are described below.
The Java Platform Welcome window (see the Fig. 2.5) provides some installation
notes.

A30808-X3247-M72-1-7619

19

OGL:IDF EVOLUTION

Operator Guidelines
OGL:LMT BSS

Fig. 2.5

JRE Installation: Startup Window (Windows Version)

Then the Java Software License window is displayed to the user (see the Fig. 2.6):

Fig. 2.6

JRE Installation: License window (Windows Version)

The user must accept the license agreementby selecting I accept the terms in the
license agreement and click on the Next Button.

20

A30808-X3247-M72-1-7619

Operator Guidelines
OGL:LMT BSS

OGL:IDF EVOLUTION

Then the Preparing Setup Percentage window is displayed to the user as represented
in the Fig. 2.7:

Fig. 2.7

JRE Installation: Setup Preparing (Windows Version)

When the Preparing Setup Procedure ends successfully the Fig. 2.8 shows the Start of
Setup.

Fig. 2.8

A30808-X3247-M72-1-7619

JRE Installation: Setup window (Windows Version)

21

OGL:IDF EVOLUTION

Operator Guidelines
OGL:LMT BSS

The Fig. 2.9, Fig. 2.10 and Fig. 2.11 show the installation phase.
Select Modify in the appearing window (see Fig. 2.9) and click on the Next Button

Fig. 2.9

JRE Installation: Installation window - phase 1 (Windows Version)

Select Java 2 Runtime Environment (see Fig. 2.10) and click on the Next Button

22

A30808-X3247-M72-1-7619

Operator Guidelines
OGL:LMT BSS

OGL:IDF EVOLUTION

Fig. 2.10

JRE Installation: Installation window - phase 2 (Windows Version)

Fig. 2.11

JRE Installation: Installation window - phase 3 (Windows Version)

When the Installation procedure is completed successfully (see Fig. 2.12), the user
shall click on the Finish button. It is also requested to restart the computer.

A30808-X3247-M72-1-7619

23

OGL:IDF EVOLUTION

Operator Guidelines
OGL:LMT BSS

Fig. 2.12

JRE Installation: End Icon (Windows Version)

At the end of the succesful installation of the JRE software on the PC thre IDF Editor
Evolution startup procedure asks the user a confirmation for continuing with the IDF
Editor software installation. For the purpose a specific window is opened. If the user
clicks the button OK the installation procedure continues automatically.

2.3.1.3

Java Communication API Installation


The installation procedure checks if the Java Communication API have been already
installed on the machine on which the IDF Editor Evolution Application has to be
installed.
In case the Java Communication API have not been installed the user is asked by a
specific pop-up window to confirm the installation of the API software. If the user
confirms by clicking the button OK the installation procedure starts the installation of
the API software.
The Java Communication API installation is permitted only to the system administrator.
On the contrary the API installation is aborted but the IDF Editor Evolution installation
will continue. (Without API the 2D code Reader does not work).

24

NOTE
For Solaris version: to extract the javax_comm-2_0_3-solsparc[1].tar.Z file use:
gunzip javax_comm-2_0_3-solsparc[1].tar.Z
tar xvf javax_comm-2_0_3-solsparc[1].tar

A30808-X3247-M72-1-7619

Operator Guidelines
OGL:LMT BSS

OGL:IDF EVOLUTION

Finally, the extracted comm.jar file shall be copied under the IDF Editor Evolution folder
too.
At the end of the IDF Editor Evolution Application installation procedure, the user can
start the IDF Editor Evolution application from his/her Windows startup File menu by
clicking on a specific icon.
The start-up window is then opened as shown in the "Fig. 2.13 Example of IDF Editor
Evolution Startup Window".

Fig. 2.13

2.3.2

Example of IDF Editor Evolution Startup Window

IDF Evolution Uninstall


In the Solaris Environment: For uninstalling the IDF Editor Evolution it is necessary to
remove the installed files and folders by erasing/deleting them by hand.
In the Windows Environment: The user shall select Add/Remove Programs in his/her
control panel and then uninstall the IDF Editor Evolution Application.

2.3.3

Hints in Case of Error


IDF Editor Evolution provides a way to log a lot of information in order to trace debug
info.
In order to collect information user should change the value of TraceLevel contained in
IDF Evaluation properties file:
replace the line TraceLevel=0
with the new one TraceLevel=5
The result of these configurations action is a bigger file called: idfEvolution.log. This
file contains a lot of useful information for supporting the analysis of the occurred
problem.
For further problems also the Troubleshot.txt file can be a valid support.

A30808-X3247-M72-1-7619

25

OGL:IDF EVOLUTION

Operator Guidelines
OGL:LMT BSS

3 Foundamentals of the IDF Editor Evolution


3.1

Purpose of the IDF Evolution


The IDF Edtor Evolution manages the Inventory data of the BSS system which can be
stored in dedicated directory and in different formats with the following extensions:
Inventory Data Table (IDT) which consists of records of inventory data;
Inventory Data File (IDF) which consists of the Inventory Data Table (IDT) completed
with an header and footer;
ZDT file which is a collection of compressed IDT files;
NOB file that is a collection of a set of inventory data. It can be attached to the IDT
or the IDF file.
The IDF Editor Evolution provides functions for supporting the user during his/her daily
activity with the inventory data (inventory data creation/deletion/IDT,IDF management,
etc) together with an enhanced and very user friendly Graphical User Interfaces (GUI).
The GUI structure (panels and windows) and its main functions are described in the
chapter: "3.3 IDF Editor Evolution Graphical User Interface (GUI)". Menu and
commands are described in the chapter: "4 Menu and Commands".

3.2

File Formats
In the "Fig. 3.1 File Types Graphical Representation" below the files types that can be
managed by the IDF Editor Evolution are represented.

Fig. 3.1

File Types Graphical Representation

The IDF Editor Evolution provides the conversion of the files as follow:
Input

Output

IDT

to

IDF, NOB

IDF

to

IDT, NOB

ZDT

to

C_IDF, C_TXT

Tab. 3.1

Format Conversion

The ZDT format represents a collection of compressed IDT files. With this format operations like exporting a TXT file of a C_IDF file are supported. An example of this operation is shown in the "Fig. 3.2 Example of Exporting C_IDF or C_TXT file" below.

26

A30808-X3247-M72-1-7619

Operator Guidelines
OGL:LMT BSS

OGL:IDF EVOLUTION

Fig. 3.2

Example of Exporting C_IDF or C_TXT file

The "Fig. 3.3 Input and Output IDF Evolutions File Types" representes the files
managed by the IDF Editor Evolution.

Fig. 3.3

A30808-X3247-M72-1-7619

Input and Output IDF Evolutions File Types

27

OGL:IDF EVOLUTION

3.3

Operator Guidelines
OGL:LMT BSS

IDF Editor Evolution Graphical User Interface (GUI)


The Main Panel of the IDF Editor Evolution is structured into seven component as represented in the Fig. 3.4 :
1.
2.
3.
4.
5.
6.
7.

Title Bar
Menu Bar
Tool Bar
Root Panel
Inventory Panel
ASCII window
Status Bar

1 - Title Bar

3 - Tool Bar

2 - Menu Bar

4 - Root
Panel

5 - Inventory
Panel

6 - ASCII Windows

7 - Status Bar
Fig. 3.4

3.3.1

IDF Editor Evolution Main Panel

Title Bar
The Title Bar shows the word: IDF Evolution - GSM. See the Fig. 3.5.

28

A30808-X3247-M72-1-7619

Operator Guidelines
OGL:LMT BSS

OGL:IDF EVOLUTION

Fig. 3.5

3.3.2

Title Bar

Menu Bar
The Menu Bar (see the Fig. 3.6) contains all the available command groups like the
File, Export, View commands in relation with the file that has been opened. In case
no file has been opened, most of them are represented in grey and cannot be
launched. Some commands can also be given from the keyboard in order to navigate
through the command groups: If the user presses the ALT button a letter is associated
to each item. If the user presses this letter the correspondent menu is opened.

Fig. 3.6

3.3.3

Menu Bar

Tool Bar
The Tool Bar represents the most used functionalities as icons. For each of them a tool
tip is associated (see the Fig. 3.7).

Fig. 3.7

3.3.4

Tool Bar

Root Panel
The Root Panel (see the Fig. 3.8) shows a summary of the opened files, like:
Network entity record (N) included in the Inventory data table (IDT,IDF);
Header, network and footer in case of IDF file;
A collection of Network entity fields in case of ZDT file.
The information is displayed in a tree mode. The tree root always reports the file type:
IDF, IDT, ZDT or NOB.
The Root Panel can also be used to drag and drop the IDT, IDF and ZDT file types (only
Windows).
The N record consists of the following components (see the Fig. 3.8):
SalesUniqueName: 11 alphanumeric characters which identify the Network
Element. It is a unique worldwide identifier assigned by the Sales department.
NEyType: A = TRAU, C = BSC, S = BTS
SystemSWVersion: 12 characters which identify the software version running on the
Network Element.

Fig. 3.8

A30808-X3247-M72-1-7619

Root Panel

29

OGL:IDF EVOLUTION

3.3.5

Operator Guidelines
OGL:LMT BSS

Inventory Panel
All the information of the selected Network entity (NOB file with the same rack on
mounting position in case of NOB) is displayed in a tree model. It contains ob and nob
RIUs.
Ob-RIU are displayed with plain character, while NOB RIUs use bold characters. None
action can be performed on the ob_RIU tree leaf using the right mouse button, while you
can edit or delete Nob_RIU using right mouse button. The leafs color can change
depending on the RIU type: gray color is used for derived PID while black is used for not
derived.
The Inventory panel is also used to drag and drop IDT, IDF and ZDT file types (only
Windows).
The showed Structure records (S) and the Inventory records (I) of ob_RIU and nob_RIU
depend on the values set in the View menu. Two ways of displaing data in the Inventory
Panel can be chosen as represented in the Fig. 3.9; the first is the type of RIUs to be
displayed:
All
nob_RIU
ob_RIU
and the second is the type of records to be displayed:
Display N records
Display N-S records
Display N-S-I records

The S and I records of the nob_RIUs are in bold characters. The I records of the
ob_RIUs with an error in PID contents are displayed in a grey color, while black is used
for not derived.
The I records consist of the following elements (see the Fig. 3.9):
Mounting Location: for example 01010199 and the first 01 indicates the room, the
second 01 the row, the third 01 the rack and 99 the mounting position;
Origin Identifier, that indicates whether the contents have really been read by an
info-element, whether the data have been incorporated by an IDF, or whether the
data have been added by hand (I=info element, F=incorporated by an IDF, M=manually added, D=derived from mounting location, P=partly to be added);
Format Version, with 10 or 12 fixed value for ob_RIUs and 14 or 15 fixed value for
nob_RIUs;
PID, with the specification of SAG Item number, hardware Item number, Functional
Designation/MnemoCode and Serial Number;
Extension Level.

30

A30808-X3247-M72-1-7619

Operator Guidelines
OGL:LMT BSS

OGL:IDF EVOLUTION

Fig. 3.9

3.3.6

Inventory Panel. Only OB RIUs are Displayed.

ASCII window
This window displays the file content and it underlines the correspondent bytes of the
selected leaf of the inventory pane tree (see the Fig. 3.10). This last option can be
disabled by user, see the chapter: "4.1.5.1 Select On Click".
When the option SelectOnClick is selected in the Option menu, by clicking the left
mouse button on the I record the ASCII text related to the corresponding S record is
shown.

Fig. 3.10

3.3.7

ASCII Window

Status Bar
In the status bar the user can read the complete path_name of the opened file. When
no file is opened the status bar is hidden as represented in the "Fig. 3.11 Status Bar".

Fig. 3.11

A30808-X3247-M72-1-7619

Status Bar

31

OGL:IDF EVOLUTION

Operator Guidelines
OGL:LMT BSS

4 Menu and Commands


In this chapter the menu and the related commands provided by the Graphical User
Interface are described.

4.1

Menu Bar
The Menu Bar consists of the following seven menus as represented in the
"Fig. 3.6 Menu Bar":
1.
2.
3.
4.
5.
6.
7.

4.1.1

File;
Export;
View;
Hw Tables;
Options;
Tools;
Help.

File Menu
The Fig. 4.1 shows the file menu and its commands that are described in the following

Fig. 4.1

4.1.1.1

File Menu

Open Command
The user can open an IDT, an IDF or a ZDT file by clicking the menu command
File\Open or the corrisponding icon in the Tool Bar. See the "Fig. 4.2 Open
Command".

32

A30808-X3247-M72-1-7619

Operator Guidelines
OGL:LMT BSS

OGL:IDF EVOLUTION

or

Fig. 4.2

Open Command

Input: filename;
Output: file is loaded for further processing.
Remarks:
The user shall open a file before any I/O operation can be performed on it.
The Open command displays the Open dialog Box. If the file specified by the pathname
does not exist, the user has to verify the correctness of the filename. With Windows XP
OS, the Open dialog Box is represented in the Fig. 4.3.
If the IDF Editor Evolution finds a format error the input file is not opened and an error
dialog box is displayed. An explanation of the errors possible causes is provided.
When the user opens an IDT, an IDF or a ZDT file the related data are displayed in the
according to the selected View menu item.
In case of ZDT file, according to the selected View menu voices, the user has to click
the left mouse button on the related N record for retrieving S and I records.

Fig. 4.3

4.1.1.2

Open Dialog Box Example with Windows XP OS.

Close Command
The user can close the opened/created file by clicking the menu command File\Close
(see the Fig. 4.4).

A30808-X3247-M72-1-7619

33

OGL:IDF EVOLUTION

Operator Guidelines
OGL:LMT BSS

Fig. 4.4

Close Command

Command: Close;
Purpose: the currently loaded file is closed.
Remarks:
It completes the I/O file operation on an opened/created file.
IF the file is opened and the user tries to open another one the first file is automatically
closed.
If the user has modified the opened file the IDF Editor Evolution automatically saves the
changes before closing it.

4.1.1.3

Save Command
This command allows the user to save all the changes made in the opened file by
clicking the menu command File\Save or by the corrisponding icon in the Tool Bar (see
the Fig. 4.5).

or

Fig. 4.5

Save Command

Command: Save;
Purpose: the loaded file is saved.
Remarks:
This command saves the current file using the same filename of the opened file.
The menu command File\Save and the toolbar save button are enabled only if the user
has made some changes in the current opened file and they are disabled after saving it.

4.1.1.4

Save As Command
The command saves all the changes made or saves a Csv file as a NOB file. The
command is performed by clicking the menu command File\SaveAs (see the Fig. 4.6).

34

A30808-X3247-M72-1-7619

Operator Guidelines
OGL:LMT BSS

OGL:IDF EVOLUTION

Fig. 4.6

Save As Command

Command: Save as;


Purpose: the loaded file is saved.
Remarks:
It saves the current file using a new filename.
The menu command File\Save and the toolbar save button are enabled only if the user
has made some changes in the current opened file and are disabled after saving it.

4.1.1.5

Attach Command
The user can attach a NOB file to an IDT or an IDF file by clicking the menu command
File\Attach or the corrisponding icon in the Tool Bar (see the Fig. 4.7).

or

Fig. 4.7

Attach Command

Input: NOB file (to be attached);


Output: inventory objects of the input file are attached.
Remarks:
The Attach command is enabled only for IDT or IDF files.
The command displays the Open dialog Box.
If the file specified by pathname does not exist, the user shall reenter the correct file
name.
If the IDF Editor Evolution finds a format error the input file is not attached.

A30808-X3247-M72-1-7619

35

OGL:IDF EVOLUTION

Operator Guidelines
OGL:LMT BSS

Not all the inventory objects are attached, but only which have not been already registered, in the current file, as nob_RIUs or as ob_RIUs with their format different from D.
The number of attached objects is displayed after the command execution. If the original
file is an IDF the footer record is automatically updated.
If any inventory objects has been attached the File\Save menu command, File\SaveAs
menu command and the toolbar save button are enabled.

4.1.1.6

Set SBS_Equip_Pos Command


The user can replace all the SBS Equipment Positions within the Mounting Position by
clicking the menu command File\Set SBS_Eq_Pos (see the Fig. 4.8). The SBS Equipment Positions constitutes the first six bytes of the Mounting Position field (see the
Fig. 4.8).

Fig. 4.8

Set SBS_Equipement_Position Command

Fig. 4.9

Set SBS_Equipement_Position Dialog Box

Command: Set SBS_Eq_Pos;


Purpose: replace all SBS Equipment Positions.
It gives the user the possibility to replace all the SBS equipment positions, present in the
Mounting Position field of all the I-records of the current opened file, with the new BSS
equipment position specified in the window.
The field Mounting Position consists of the "SBS_Equipment_Position" concatenated
with the mounting location of the module within the rack.

36

A30808-X3247-M72-1-7619

Operator Guidelines
OGL:LMT BSS

OGL:IDF EVOLUTION

For example: "010101"+"02B004" 01010102B004.


The number of replaced objects is displayed after the command execution.
If any inventory object has been replaced the File\Save menu command and the toolbar
save button are then enabled.

4.1.1.7

Set Functional Address Rack Position Command


The user can replace all the rack positions within the Functional Addresses by clicking
the menu command File\Set RACK_Pos (see the Fig. 4.10 and the Fig. 4.11).

Fig. 4.10

Set F.A. RACK_Position Command

Fig. 4.11

Set RACK_Position (Functional Address) Dialog Box

Command: Set F.A. RACK_Pos;


Purpose: replace all rack positions.
Remarks:
The Set F.A. Rack Position command is enabled only for IDT and IDF, but it is useful
only for IDT files.
Once the user selects this command the Set RACK_Position window is displayed.
It provides to the user the function for replacing all the rack positions,in the Functional
Address field of all the S-records, with the new Rack Position Number specified in the
dialog box. The permitted value is a digit from 0 to 9.

A30808-X3247-M72-1-7619

37

OGL:IDF EVOLUTION

Operator Guidelines
OGL:LMT BSS

The number of replaced objects is displayed after the successful commands execution.
If an inventory object is replaced the File\Save menu command and the toolbar save
button is enabled.
Take into consideration that the field Functional Address is the logical address of the
inventory object and it consists of name, rack position and module number.
For example: FAN-0/1 with rack position=0 and module number = 1

4.1.1.8

Remove NOB RIUs Command


The user can remove all redundant Nob_RIUs inventory data stored in the current
opened IDT or IDF file (see the Fig. 4.12). The algorithm is is based on the Functional
Address information.

Fig. 4.12

Remove nob_RIUs Command

Command: Remove nob_RIUs


Purpose: all redundant nob_RIUs are removed
Remarks:
All the nob_RIUs stored in the current opened file which have the same Functional
Address of an ob RIUs object, with format different from D, are removed.
This command is very useful because all inventory data imported from the RLC are
considered as nob_RIUs. So, the same board would be reported as ob RIUs or as NOB
RIUs.
The number of removed objects is displayed after the commands execution. If the original file is an .IDF the footer record is automatically updated.
If any inventory objects has been removed the File\Save menu command and the
toolbar save button are enabled.

38

A30808-X3247-M72-1-7619

Operator Guidelines
OGL:LMT BSS

4.1.1.9

OGL:IDF EVOLUTION

Search Command
This command provides a quick module search as represented in the Fig. 4.13.

Fig. 4.13

Search Command

Command: File\Search\Serial Number or File\Search\Functional Address


Purpose: find the records in the opened file.
Remarks:
The search function is enabled for several type of opened file (IDT, IDF and NOB).
The inventory data (whether ob_RIU or nob_RIU) that match the search condition are
selected.
The user has the possibility to search a record either for:
Serial Number;
Functional Address.
1. Search Serial Number Command
This functionality provides to the user the possibility of searching an inventory record
by its Serial Number (see the Fig. 4.14).
For example the user has the possibility to search those modules having the Serial
Number like XIL/K3221159 or starting with XIL/K simply writing the serial number or
the initial part of serial number.

A30808-X3247-M72-1-7619

39

OGL:IDF EVOLUTION

Operator Guidelines
OGL:LMT BSS

Fig. 4.14

Search Dialog Box

Search Serial Number:


It is the string/initial substring the IDF Evolution has to look for in the Serial Number
fields.It shall be inserted by the user.
Scan:
This button enables the 2D Labels Reader to get the Serial Number the IDF Evolusearchs for.
Find Next:
This button repeats the search while the end of the file will be reached.
Cancel
This button deletes the search and closes the search window.
2. Search Functional Address command
This command offers to the user the possibility of searching an inventory record by
the functional Address.
For example, the user has the opportunity of find all th emodules, in the current
opened file, with their Functional Address lCU-0/0.
Once selected this functionality the IDF Editor Evolution displays the Search
Dialog Box represented int he Fig. 4.15.
The inserted value is the substring the IDF Editor Evolution has to look for in the
Functional Address fields.

40

A30808-X3247-M72-1-7619

Operator Guidelines
OGL:LMT BSS

OGL:IDF EVOLUTION

Fig. 4.15

Search Dialog box

Find Next:
This button repeats the search while the end of the file will be reached.
Cancel:
This button closes the search window.

4.1.1.10

Exit Command
The user can exit from the IDF Evolution by clicking the menu command File\Exit (see
Fig. 4.16).

Fig. 4.16

Exit Command

Command: Exit
Purpose: Stop the IDF Editor running application and exit.
Remarks:
The user can select the Exit command anytime in order to suspend the program execution.
The Exit command closes the opened file.

A30808-X3247-M72-1-7619

41

OGL:IDF EVOLUTION

Operator Guidelines
OGL:LMT BSS

If the user has modified the opened file the IDF Editor Evolution automatically saves the
changes before exiting.

4.1.2

Export Menu
The user can perform three kind of export by choosing one entry of the export menu or
by pressing on the relative export button (as represented in the Fig. 4.17.

or

Fig. 4.17

4.1.2.1

Export Menu (in this example an IDF file has been opened)

Export C_IDF Command


The user can export the current opened file in Central IDF format (a ZDT file is opened);
see the Fig. 4.18.

or

Fig. 4.18

C_IDF Export Command (in this example a ZDT file has been opened)

Command: Export C_IDF


Purpose: The current ZDT file is converted into a C_IDF file format
Remarks:
This command export the currently opened file in Central IDF format completed with an
header and footer record giving information about the format type, the creation time and
the number of records contained in the file.

42

A30808-X3247-M72-1-7619

Operator Guidelines
OGL:LMT BSS

4.1.2.2

OGL:IDF EVOLUTION

Export C_TXT Command


The user can export the currently opened file in Central TXT format (a ZDT file is
opened); see the Fig. 4.19.

Fig. 4.19

Export C_TXT Command (in this example an ZDT file has been opened)

Command: Export C_TXT;


Purpose: The current ZDT file is converted into a C_TXT format.

4.1.2.3

Export IDT Command


The user can export the current opened file into the IDT format by clicking the item menu
command Export\IDT or by the corrisponding icon in the Tool Bar (see the Fig. 4.20).

or

Fig. 4.20

Export IDT Command (in this example an IDF file has been opened)

Command: Export IDT;


Purpose: an IDT file is created and its extension will be .IDT.
Remarks
This command displays the SaveFileAs dialog Box, which enables the user to specify
the filename of the exported file. The default filename is retrieved from the Sales Unique
Name.
An IDT file format consists of IDF file without header and footer.
The export IDT command is enabled only if the operator has opened an IDF file and in
case the current opened file is saved.

A30808-X3247-M72-1-7619

43

OGL:IDF EVOLUTION

4.1.2.4

Operator Guidelines
OGL:LMT BSS

Export IDF Command


The user can export the current opened file in IDF format by clicking the menu command
Export\IDF or by the corrisponding icon in the Tool Bar (see the Fig. 4.21).

or

Fig. 4.21

Export IDF Command (in this example an IDT file has been opened)

Command: Export IDF


Purpose: an IDF file is created and its extension will be .IDF
Remarks
The Export IDF command displays the SaveFileAs dialog Box, which enables the user
to specify the filename of the exported file. The default filename is retrieved from the
Sales Unique Name.
An IDF file format consists of an IDT file with in addition an header and footer record.
The Export IDF command is enabled only if the operator has opened an IDT file and in
case the current opened file is saved.
If the file specified by pathname does not exist, the IDF Evolution creates it.

4.1.2.5

Export NOB Command


The user can export all the nob_RIUs data stored in the current opened file by clicking
the menu command Export\NOB or the corrisponding icon in the Tool Bar (see the
Fig. 4.22).

or
Fig. 4.22

Export NOB Command


(in this example an IDT file has been opened)

Command: Export NOB;


Purpose: the nob_RIUs data are exported.

44

A30808-X3247-M72-1-7619

Operator Guidelines
OGL:LMT BSS

OGL:IDF EVOLUTION

Remarks:
Export the NOB RIUs data of the current opened file.
The NOB command is enabled for an IDT or an IDF file storing nob_RIUs and only if the
current opened file is saved. The NOB command displays the SaveFileAs dialog Box,
which enables the user to specify the file name of the exported file. The default file name
is retrieved from the Sales Unique Name.
If the file specified by pathname does not exist, the IDF Evolution creates it.
The user has the possibility to create a copy of the exported file in an hidden directory,
with a fixed filename, visible only by the LMT Evolution during the downloading of the
NOB file to the related Network Element (BSC, BTS, TRAU).

4.1.3

View Menu

Fig. 4.23

4.1.3.1

View Menu

All, nob_RIus, ob_RIUs commans


This functionality is useful for viewing all the records, only ob_RIUs records or only
nob_RIUs records of the current opened file (see the Fig. 4.23).
Command: View\All, View\ob_RIUs or View\nob_RIUs;
Purpose: select the record displayed type.
Remarks:
The view function is enabled for the following type of opened file IDT, IDF and ZDT. In
case of ZDT when the user selects a different Network Element, from the root panel, the
view selection is restored to the default value.
The inventory data (All, ob_RIUs or nob_RIUs) that matches with the view conditions
are displayed.
To distinguish the different type of the displayed records the nob_RIUs S-I records are
displayed in bold, the ob_RIUs S-I records with an error in PID contents are display in
different colors (see the Fig. 4.24).
The user has the following possibilities:
All: Displays, in the Inventory Panel, all the records of the current file.

A30808-X3247-M72-1-7619

45

OGL:IDF EVOLUTION

Operator Guidelines
OGL:LMT BSS

Fig. 4.24

46

All Records view

nob_RIUs: Displays, in the Inventory Panel, nob_RIUs records of the currently


opened file. The nob_RIUs S-I records are displayed in bold as represented in the
Fig. 4.25.

A30808-X3247-M72-1-7619

Operator Guidelines
OGL:LMT BSS

OGL:IDF EVOLUTION

Fig. 4.25

A30808-X3247-M72-1-7619

View only nob_RIUs records

ob_RIUs: Display, in the Inventory Panel, only ob_RIUs records of the current
opened file. The ob_RIUs I-records with an error in PID contents are displayed in
different colors as represented in the Fig. 4.26.

47

OGL:IDF EVOLUTION

Operator Guidelines
OGL:LMT BSS

Fig. 4.26

View only Ob Records

Through the commands: View\Display N records, View\Display N-S records and


View\Display N-S-I records the user has the possibility to expand/reduce the inventorys tree.
Display N records: the inventorys tree will be reduced up to its root node:
Display N-S records: the inventorys tree will be reduced up to display all the structure records of the current file;
Display N-S-I records: This command expands the tree so that both structure and
inventory records are displayed.

4.1.4

Hardware Table Menu


This menu contains commands that allow the user to modify the Nob-RIUs inventory
data (see the Fig. 4.27).

Fig. 4.27

Hardware Table Menu

Command: HW Table

48

A30808-X3247-M72-1-7619

Operator Guidelines
OGL:LMT BSS

OGL:IDF EVOLUTION

Remarks:
All HW Table commands are stand alone operations (they do not involve the current
opened file).
This operation can be executed independently by other tool functionalities. In particular
an user can insert, delete or modify a NOB record through the commands: HW
Table\Insert record, HW Table\Delete record or HW Table\Modify record.
In addition the user can create a new Network Element Type by editing the NEy Type
field.

4.1.4.1

Insert Record Command


When the user selects the command HW Table\Insert record the "Insert record" form will
be opened (see the Fig. 4.28).
The user can insert a new nob_RIU object by means of the Insert Record window.See
the "Fig. 4.28 Insert Record window".
The user shall specify the Network Element Type, the Functional Address, the Functional Address Type and the Mounting Position of the inserted object.

Fig. 4.28

Insert Record window

NE:
The user shall specify the BSS Network Element (BSC, BTS, TRAU).

A30808-X3247-M72-1-7619

49

OGL:IDF EVOLUTION

Operator Guidelines
OGL:LMT BSS

NEy Type:
It represents the Network Element Type.
The user can choose an existing network element type, by selecting a record from the
combo Box, or he/she can create a new one by typing the new Ney Type name in the
combo box.
Functional Address:
It is the Functional Address of the object the user wants to insert.
Functional Address Type:
It is the Functional Address Type of the object the user wants to insert.
Mounting Position:
It is the second part of the mounting location. :
Insert
If all requirements are verified this button triggers the inserion of the record in the basic
Nob_RIUs table of that Network Element.

Requirements:
all data shall be inserted:
the pair Functional Address, Functional Address Type must not be already present
in the table.
Cancel:
This button closes the window leaving the data unchanged.

4.1.4.2

Delete a HW Record Command


When the user selects the command HW Table\ Delete record, the Delete record
window is opened (see the Fig. 4.29) and the user can delete an existing nob_RIU
object in the basic nob_RIU database.
The user shall also specify the Network Element Type, the Functional Address, the
Functional Address Type and the Mounting Position of the object he had delete.

50

A30808-X3247-M72-1-7619

Operator Guidelines
OGL:LMT BSS

OGL:IDF EVOLUTION

Fig. 4.29

Delete Record window

Delete:
If all the conditions are verified, when the user clicks on this button the IDF Editor Evolution deletes the record in the basic nob_RIU table.

Requirements:
all data must be inserted;
Cancel:
This button closes the window leaving the data unchanged.

4.1.4.3

Modify a HW Table Command


When the user selects the command HW Table\Modify record the Modify record
window is opened. It is represented in the Fig. 4.30).
By means of it, the user can modify an existing NOB RIUs object in the basic nob_RIU
database.
The user has to indicate the Network Element, the Functional Address, the Functional
Address Type and the Mounting Position of the object to be modified.

A30808-X3247-M72-1-7619

51

OGL:IDF EVOLUTION

Operator Guidelines
OGL:LMT BSS

Fig. 4.30

Modify Record Selection window

By clicking on the Modify button, the user can modify the Functional Address, the Functional Address Type and the Mounting Position of the selected object. The window
represented in the "Fig. 4.31 Modify Record window" is displayed.

Fig. 4.31

Modify Record window

Modify Data:
If all the conditions are verified, when the user has clicked on this button the IDF Editor
Evolution modifies the record in the basic nob_RIUs table of that Network Element.

52

A30808-X3247-M72-1-7619

Operator Guidelines
OGL:LMT BSS

OGL:IDF EVOLUTION

Cancel:
This button closes the window and leaves the data unchanged.

4.1.5

Options Menu

Fig. 4.32

4.1.5.1

Options Menu

Select On Click
This functionality (see the Fig. 4.32) allows the user to emphasize some bytes in the
ASCII window related to the selected node/leaf of inventory panel or root panel tree.
Command: Options\SelectOnClick.
Purpose: mark or not data in the ASCII window of the IDF Editor Evolution.
Remarks:
The SelectOnClick function is enabled for all type of opened file (IDT, IDF, NOB, ZDT).
When the SelectOnClick option is activated, clicking the left mouse button over a node
of the tree, the IDF Evolution emphasizes the relative bytes in the ASCII window as
represented in the Fig. 4.33 and Fig. 4.24).

Fig. 4.33

Select on Click Option Enabled

Fig. 4.34

Select on Click Option Disabled

A30808-X3247-M72-1-7619

53

OGL:IDF EVOLUTION

4.1.5.2

Operator Guidelines
OGL:LMT BSS

Hide ASCII File Window


This functionality (see Fig. 4.35) allows the user to hide/unhide the ASCII window. It is
very useful in presence of a big file for improving the IDF Editor Evolution performance
or in case the user is not interested in the file ASCII content.

The ASCII content window is hidden

Fig. 4.35

Hidden ASCII window

Command: Options\Hide ASCII file window.


Purpose: hide/unhide the file content window.
Remarks:
Each time the IDF Editor Evolution is closed, the default values is restored (default =
show ASCII file content window).

4.1.5.3

Look and Feel Command


This functionality (see Fig. 4.36) allows the user to choose one of the Java Look and
Feel. Available Look and Feels depend on the JRE installed version and supported
Operating System.

54

A30808-X3247-M72-1-7619

Operator Guidelines
OGL:LMT BSS

OGL:IDF EVOLUTION

Fig. 4.36

Look and Feel Command in case of Windows Operating System

Command: Options\Look & Feel.


Purpose: change the IDF Evolution look and feel.

i
4.1.5.4

Select the look and feel and then restart the IDF Editor Evolution in order to have all
application windows correctly displayed.

Switch Command
This command switches the IDF Editor Evolutiion from the GSM to the UMTS technology as shown in the Fig. 4.37.

Fig. 4.37

i
4.1.6

Switch Command

The Switch Application is currently not avalaible.

Tools Menu

Fig. 4.38

A30808-X3247-M72-1-7619

Tools Menu

55

OGL:IDF EVOLUTION

4.1.6.1

Operator Guidelines
OGL:LMT BSS

Set Scanner Port Command


The Set scanner port tool can be used to set the serial port the 2D Label scanner is
connected to. The dialog box displays eight selectable ports: the first fours can be
selected if the supported OS is Windows while the last fours can be selected if the
supported OS is Solaris (see the Fig. 4.39).

Fig. 4.39

Set Scanner Port Dialog Box

Select the appropriate communication port: use comX for Windows and others for
Solaris.
This tool does not inform the user if the selected port is not the one the 2D Label scanner
is connected to. In the view of the fact the user selects a wrong port, the IDF Editor
Evolution displays an error dialog box, while trying to get data, suggesting to change the
port settings as represented in the Fig. 4.40.

Fig. 4.40

4.1.7

Error dialog box related to the search serial number function


(in case of a wrong port has been selected)

Help Menu
An On-line help is provided as represented in the Fig. 4.41:The following buttons are
available:
Help Contents;
About IDF Editor Evolution.

56

A30808-X3247-M72-1-7619

Operator Guidelines
OGL:LMT BSS

OGL:IDF EVOLUTION

Fig. 4.41

4.1.7.1

Help Menu

Help Contents Command


The Help command supports the user in searching specific IDF Evolution functionalities.When the use clicks on the Help Contents button the Help panel is opened
(see Fig. 4.42).
This panel provides the following facilities:
Table of Contents;
Index (not available now);
Search;
Favorites.

Fig. 4.42

A30808-X3247-M72-1-7619

Help Contents window

57

OGL:IDF EVOLUTION

4.1.7.2

Operator Guidelines
OGL:LMT BSS

About IDF Evolution Command


This command visualizes to the user the IDF Evolution Version and opens the windowl
represented in the Fig. 4.43.

Fig. 4.43

58

About IDF Evolution window

A30808-X3247-M72-1-7619

Operator Guidelines
OGL:LMT BSS

4.2

OGL:IDF EVOLUTION

Pop Up Commands
Pop up menus are displayed when the user presses the right mouse button over an
appropriate node of the inventory or of the root panel tree.

4.2.1

Root Pane Pop Up Command


Theres only one available pop up (see Fig. 4.44):
Create.

4.2.1.1

Create an S-I Record Command


The user can insert a new NOB RIUs object, in the inventory panel of the current opened
file, by clicking the right mouse button on the N-record (this record is displayed in the
root panel tree), or by pressing the right mouse button over a RACK node of the root
panel tree (see Fig. 4.44).

Fig. 4.44

Create New nob_RIU Command

Command: Create
Purpose: create a nob_RIU object.
The user can create only nob_RIUs objects (ob_RIU comes directly from the boards).
To create a new nob_RIU the user has to insert all Structure and Inventory data. If all
data are inserted and the pair Functional Address Functional Address Type does not
already exist in the current opened file as nob_RIUs or as ob_RIUs with format different
from D then the new object will be inserted in the file.
The menu command File\Save and the toolbar save button are enabled only if the user
has made some changes in the current opened file and are disabled after saving it.
Insert Structure Data:
The aim of the "New NOB_RIU" panel is to make easier for the user the insertion of the
related inventory data.
The user has to specify the Network Element Type, the pair Functional Address::Functional Address Type and the SBS_Equipment_Position of the nob_RIU that has to be
added, as represented in the Fig. 4.45).

A30808-X3247-M72-1-7619

59

OGL:IDF EVOLUTION

Operator Guidelines
OGL:LMT BSS

Fig. 4.45

New NOB_RIU panel

By clicking the Inventory button, the user can insert all the requested Inventory data in
the apposite window represented in the Fig. 4.46.
The Item Number (HW, FW) field is enabled only for the Network Element that supports
the PID format 11. In all the other cases the related field is shown but disabled (this
means that it can not be filled in).

Fig. 4.46

Panel for inserting the requested inventory data

The buttons: Scan, OK!, Cancel, have the following meaning:

60

A30808-X3247-M72-1-7619

Operator Guidelines
OGL:LMT BSS

OGL:IDF EVOLUTION

Scan:
This button permitts the user to insert the FW Code, the HW Code and the Serial
Number of LRU by means of the 2D-Code_Reader device.
OK!:
This buttons confirms the data changing and closes the panel.
Cancel:
This button closes the panel without saving the data changed.

4.2.2

Inventory Panel Pop Up Commands


In this chapter the inventory panels pop up commands are described.
The available commands are:
Delete a S-I record;
Edit an I record.

4.2.2.1

Delete an S-I Record (S-I Stands for Structure and Inventory)


Command
The delete of a nob_RIU record can be done by pressing the right mouse button over a
nob_RIU of the Inventory panel tree. In particular the user can delete the correspondent
nob_RIUs of the currently opened file by clicking the right mouse button on a nob_RIU
S-record. An example is reported in the Fig. 4.47.

Fig. 4.47

Delete S-I Record Command

Command: Delete;
Purpose: delete a nob_RIU object.
Remarks:
It is important to put in evidence:
The delete command is enabled only for IDT, IDF NOB files;
The user can delete only an existing nob_RIU object;
The IDF Editor Evolution deletes the Structure and Inventory data of the selected
nob_RIU.
The menu command File\Save and the toolbar save button are enabled only if the user
has made some changes in the current opened file and are disabled after saving it.

A30808-X3247-M72-1-7619

61

OGL:IDF EVOLUTION

4.2.2.2

Operator Guidelines
OGL:LMT BSS

Edit an I Record (I Stand for Inventory) Command


The user can modify an existing nob_RIU record by clicking the right mouse button on
an Inventory record or on a PID-record as represented in the Fig. 4.48.

Fig. 4.48

Edit an I Record Command

Command: Edit
Purpose: modify a nob_RIU Inventory record.
Remarks:
It is important to put in evidence: :
The user can modify only the Inventory data of an existing nob_RIU object;
The IDF Evolution modifies only Inventory records.
The menu command File\Save and the toolbar save button are enabled only if the user
has made some changes in the current opened file and are disabled after saving it.
In order to edit the Inventory data of an existing board the "XXX Pid NOB RIUs" form is
opened.
The user can modify all the permitted fields as shown in the Fig. 4.49.
The Item Number (FW, HW) field is enabled only for the Network Element that supports
the PID format 11.

62

A30808-X3247-M72-1-7619

Operator Guidelines
OGL:LMT BSS

OGL:IDF EVOLUTION

Fig. 4.49

Edit I Record

The Buttons: Scan, OK!, Cancel have the following meaning:


Scan:
It permitts the user to insert the FW Code, the HW Code and the Serial Number of LRU
entry by means of the 2D-Code_Reader device.
OK! :
This button saves the inserted data and closes the panel.
Cancel:
This button closes the panel and does not save the data.

4.3

2D Code Reader
The IDF Editor Evolution supports the data entry by means of a 2D Code Reader device.
The string that is delivered by the 2D Code Reader reading a NodeB label provides the
following information:
SAG code Number /Issue;
Mnemonic Serial Number.
These inputs are necessary in case:
A new nob_RIU shall be inserted;
An existing nob_RIU shall be modified;
An existing nob_RIU board shall be searched;

A30808-X3247-M72-1-7619

63

OGL:IDF EVOLUTION

Operator Guidelines
OGL:LMT BSS

When the data input for the HW Code and Serial Number of LRU is required the user
just presses the Scan button and the data is automatically inserted into the relevant
fields.
When replacing the data for HW Code and Serial Number of an old board the user has
to select the module in the browsing window and just press the Scan button instead of
inserting manually the requested infromation.
The supported 2D Code Reader in the BSS system is the METHANETICS CORPORATION IR-2000 device.

4.3.1
4.3.1.1

METHANETICS CORPORATION IR-2000


Hardware Setting
The application runs only if the IR-2000HD imaging reader parameters are set to the
default values.
The default values for the IR-2000HD imaging reader are splecified in the 2D Code
Reader User's Manual (METHANETICS CORPORATION IR-2000TD HANDLE HELD
IMAGE READER USER'S GUIDE). They are reported in the following tables:
Operating Parameters
Baud Rate

9600 bps

Data Bits

8 bits

Flow Control

None

Parity Bits

No Parity

Speep Mode

Enabled/2 minutes

Stop Bits

1 bits

Tab. 4.1

Operating Parameters for the IR-2000HD

Decode Options
Carriage Return/Line Feed Disabled
Decode Mode

Multiple

Illumination

Enabled

Prefix/Suffix

Disabled

Reverse Constant(1D)

Disabled

Targeting

On Demand

Tab. 4.2

64

Decode Options for the IR-2000HD

A30808-X3247-M72-1-7619

Operator Guidelines
OGL:LMT BSS

4.3.1.2

OGL:IDF EVOLUTION

Using the 2D Code Reader


The following paragraph has been extracted by the 2D Code Reader User's Manual
(METHANETICS CORPORATION IR-2000TD HANDLE HELD IMAGE READER
USER'S GUIDE) and it informs the user about the use of the 2D code Reader device.
1.

Once the IR-2000HD has been powered on, pull the front trigger to illuminate the
targeting guides. Move the reader toward/away until the two targeting guides
converge to one (the reader will be about 4" away from the bar codes surface).
When converged and directed at the surface , the targeting appears as represented
in the Fig. 4.50:

Fig. 4.50

2D Code Reader Targeting

2. Center the targeting guides on either of the sample bar codes on the opposite page.
3. Do not release the trigger until a single short beep is heard.
4. When the reader emits a short beep, this indicates that it is operating properly and
has succesfully decoded the bar code. If the targeting shuts off without the single
confirming beep having been emitted, release the trigger. Retry steps 1-4. (In order
to reactivate the reader quickly depress the trigger).

A30808-X3247-M72-1-7619

65

OGL:IDF EVOLUTION

66

Operator Guidelines
OGL:LMT BSS

A30808-X3247-M72-1-7619

Operator Guidelines
OGL:LMT BSS

OGL:IDF EVOLUTION

5 Inventory Data Management


In this chapter the main procedures for managing the inventory data (for example the
procedure for creating a new nob_RIU) are described in detail. Each procedure is structured in steps. Each steps corresponds to an action requested to the user.

5.1

Procedure: Update of a nob_RIU


This procedure has to be applied in case a nob_RIU is newly to be installed or has to be
modified. The first common steps consist of the IDT file opening:
1. Start IDF Editor Evolution.
2. Select the open menu (see Fig. 5.1) and select the file to be opened (for example:
the default directory c:\Siemens\111_xx_yy\Upload is offered).

Fig. 5.1

A30808-X3247-M72-1-7619

Open selected File

67

OGL:IDF EVOLUTION

5.1.1
5.1.1.1

Operator Guidelines
OGL:LMT BSS

Step by Step Approach


In Case a Nob_RIU is Newly to Be Created
1. Create a new nob_RIU by selecting the N-record and pressing the right mouse
button and click on the appearing Create button (see Fig. 5.2).

Fig. 5.2

Insert a New Nob_RIU - Step 1

2. Select module to be added (see Fig. 5.3).

Fig. 5.3

Insert a New Nob_RIU - Step 2

3. Set SBS_Equipment_Position and click on the inventory button (see Fig. 5.4).

Fig. 5.4

68

Insert a New Nob_RIU - Step 3

A30808-X3247-M72-1-7619

Operator Guidelines
OGL:LMT BSS

OGL:IDF EVOLUTION

4. Insert inventory data (see Fig. 5.5).

Fig. 5.5

Insert a New Nob_RIU - Step 4

The FW Item Number, FW Functional Status, HW Item Number, HW Functional


Status and the Serial Number can be inserted manually or automatically detected (if
stored on the label of the module) by using the 2D-Code Reader connected to the
serial port of the PC.
The 2D-Code Reader (see Fig. 5.6) makes data input error free and fast.

Fig. 5.6

2D-Code Reader

The following panel (see Fig. 5.7) is shown when the user presses the Scan button.
The serial port where the 2D-Code Reader is installed must be specified (only the
first time the reader is used).

A30808-X3247-M72-1-7619

69

OGL:IDF EVOLUTION

Operator Guidelines
OGL:LMT BSS

Fig. 5.7

Port Setting for 2D-Code Reader

When the user presses the button on the 2D-Code Reader the HW/FW Item
Number, the Serial Number and the Extension level are detected and inserted into
the relevant fields.

5.1.1.2

In Case a Nob_RIU is Already Present and is to be Replaced


1. Edit the inventory data by selecting the I-Record and pressing the right mouse
button and click on the appearing Edit button (see Fig. 5.8).

Fig. 5.8

70

Replacement of a Nob_RIU - Step 1

A30808-X3247-M72-1-7619

Operator Guidelines
OGL:LMT BSS

OGL:IDF EVOLUTION

2. Edit inventory data (see Fig. 5.9).

Fig. 5.9

Replacement of a Nob_RIU - Step 2

The FW Item Number, FW Functional Status, HW Item Number, HW Functional


Status and the Serial Number nob_RIUs data can be inserted manually or can be
automatically detected (if present on the label of the module) by using the 2D-Code
Reader connected to the serial port of the PC.
The 2D-Code Reader (see Fig. 5.6) makes data input error free and fast.
The panel in Fig. 5.7 is shown when the user presses the Scan button. The serial
port where the 2D-Code Reader is installed shall be specified (only the first time the
device is connected).
When the user presses the button of the 2D-Code Reader the Item Number, the
Serial Number and the Extension level are detected and inserted into the relevant
fields.

5.1.1.3

In Case a Nob_RIU is Already Present and has to be Removed


1. Delete inventory data by selecting the S-Record and pressing the right mouse button
and click on the appearing Delete button (see Fig. 5.10).

A30808-X3247-M72-1-7619

71

OGL:IDF EVOLUTION

Operator Guidelines
OGL:LMT BSS

Fig. 5.10

Delete a Nob_RIU - Step 1

2. Confirm the deletion operation (see Fig. 5.11).

Fig. 5.11

5.1.2
5.1.2.1

Confirmation of the deletions operation

Automated Approach in Case the IDF File is imported from the RLC
Logistics: Inventory Data Delivered by RLC to the Project
The RLC (Logistic Center) can deliver the following inventory files on a per rack basis
represented in the "Fig. 5.12 IDFs Delivered with the BTS Equipment" . This is an
example of IDF Files in case the Network Element is the BS-240/241.

72

A30808-X3247-M72-1-7619

Operator Guidelines
OGL:LMT BSS

OGL:IDF EVOLUTION

Fig. 5.12

IDFs Delivered with the BTS Equipment

For every rack one floppy disk is provided which includes an inventory data file that
contains all the inventory objects defined for that rack.
All the inventory data are reported in the format "11" - ob_RIUs and nob_RIUs!.
The file name is composed by the serial number of the rack ("/" replaced against "_")
and the extension "IDF".
Structure:<Serial Number of the Rack ("/" replaced by "_")>+".IDF".

A30808-X3247-M72-1-7619

73

OGL:IDF EVOLUTION

Operator Guidelines
OGL:LMT BSS

In addition the RLC can prepare the inventory data of the network entity by downloading
the correct data as described in the next chapters. This is possible for all the NEs which
consist only of one rack (for example the BS-2x/6x, BSC, TRAU).
For rthe ack extensions of the BS-240/241 line this will not be possible due to the
missing core module (COBA).
Nevertheless this additional service is to be negotiated with the RLC.
Disk

Rack/Shelter

Disk 1 Base Rack

Serial Number

Filename

CN+/JD100001.IDF

CN+_JD100001.IDF

Disk 2 Extension Rack 1 CN+/JD100002.IDF

CN+_JD100002.IDF

Disk 3 Extension Rack 2 CN+/JD100014.IDF

CN+_JD100014.IDF

Disk 4 Service Rack 1

CN+/JD106604.IDF

CN+_JD106604.IDF

Disk 5 Service Rack 2

CN+/JD106605.IDF

CN+_JD106605.IDF

Tab. 5.1

Example of Filenames of IDFs Coming from the RLC

The following table gives an example of an Inventory Data File delivered for a BS60 (The
Output is structured for a better reading).
Filename: RX+_L2888888.IDF
HREMOTE INVENTORYV1.01
RX+_L2888888
SM01FP-0/0
FUSE-PANEL
IM0101010101
M11
SM01DUCOM-0/0
DUCOM2G
IM0101010102 B002 M11
SM01DUCOM-0/1
DUCOM2G
IM0101010102 B004 M11
SM01DUCOM-0/2
DUCOM2G
IM0101010102 B006 M11
SM01RXAMCO-0/0
M:RXAMCOG
IM0101010102 B008 M11
SM01RXAMCO-0/1
M:RXAMCOG
IM0101010102 B009 M11
SM01RXAMCO-0/2
M:RXAMCOG
IM0101010102 B010 M11
SM01RXAMCO-0/3
M:RXAMCOG
IM0101010102 B011 M11
SM01RXAMCO-0/4
M:RXAMCOG
IM0101010102 C008 M11
SM01RXAMCO-0/5
M:RXAMCOG
IM0101010102 C009 M11
SM01PA-0/0
HPAG
IM0101010108 C105 M11
SM01TPU-0/0
TPU2G
IM0101010108 C128 M11
SM01PA-0/1
HPAG
IM0101010108 C141 M11

74

SRI 3.0 08.02.199913:07:15


S
S30861-D11-X1-05/01

FUSE-PANEL RO+/JN129607

S30861-U566-X-02/01

DUCOM2G

RX+/K7106924

S30861-U566-X-02/01

DUCOM2G

RX+/K7106921

S30861-U566-X-02/01

DUCOM2G

RX+/K7106920

S30861-Q303-X200-05/01 M:RXAMCOG RO+/JO129078


S30861-Q303-X200-05/01 M:RXAMCOG RO+/JO129091
S30861-Q303-X200-06/01 M:RXAMCOG RO+/JO129057
S30861-Q303-X200-05/01 M:RXAMCOG RO+/JO129090
S30861-Q303-X200-05/01 M:RXAMCOG RO+/JO129084
S30861-Q303-X200-06/02 M:RXAMCOG RO+/JO129063
S30861-U528-X-02/02

HPAG

BM+/JO554304

S30861-U524-X-06/03

TPU2G

RO+/J7213417

S30861-U528-X-02/02

HPAG

BM+/JO551552

A30808-X3247-M72-1-7619

Operator Guidelines
OGL:LMT BSS

OGL:IDF EVOLUTION

SM01TPU-0/1
IM0101010108 C164
SM01PA-0/2
IM0101010108 C177
SM01TPU-0/2
IM0101010108 C200
SM01FAN-0/2
IM0101010108 E101
SM01DCPA-0/0
IM0101010108 F103
SM01DCTPU-0/0
IM0101010108 F119
SM01DCPA-0/1

TPU2G
M11
HPAG
M11
TPU2G
M11
FAN
M11
M:DCPA
M11
M:DCTPU
M11
M:DCPA

IM0101010108 F133
SM01DCTPU-0/1
IM0101010108 F149
SM01DCPA-0/2
IM0101010108 F163
SM01DCTPU-0/2
IM0101010108 F179
SM01FAN-0/1
IM0101010108 G 101
SM01BBSIG-0/0
IM0101010108 H103

M11
M:DCTPU
M11
M:DCPA
M11
M:DCTPU
M11
FAN
M11

M11 S30861-Q330X101-03/01
SM01BBSIG-0/1
M:BBSIG44
IM0101010108 H117 M11 S30861-Q330X101-03/01
SM01BBSIG-0/2
M:BBSIG44
IM0101010108 H131 M11 S30861-Q330X101-03/01
SM01MCLK-0/0
M:MCLK
IM0101010108 H187 M11 S30861-Q331X1-7/01
SM01CCTRL-0/0
M:CCTRL
IM0101010108 H211 M11 S30861-Q332X1-9/02
SM01LI-0/0
M:LI
IM0101010108 H235 M11 S30861-Q337X101-2/01
SM01ALCO-0/0
M:ALCO
IM0101010108 H259 M11 S30861-Q300X101-2/01
SM01GPSU-0/0
M:GPSU
IM0101010108 J271
M11
SM01FAN-0/0
FAN
IM0101010108 K 101 M11
SM01FRAACOM-0/0 F:ACOM
IM0101010102M11
M11
SM01FRABTS6-0/0
F:BTS6
IM0101010108M11
M11
SM01RBS60-0/0
R:BS60
IM0101010100M11
M11
FN:00001S:00036I:00036END OF IDF

A30808-X3247-M72-1-7619

S30861-U524-X-06/03

TPU2G

RO+/J7213427

S30861-U528-X-02/02

HPAG

BM+/JO553522

S30861-U524-X-06/03

TPU2G

RO+/J7213751

S30861-U426-X-05/01

FAN

CF+/JD123798

S30861-Q392-X-08/01

M:DCPA

RO+/J8152091

S30861-Q348-X-C2/01

M:DCTPU

CF+/JN143256

S30861-Q392-X-08/01

M:DCPA

RO+/J8152087

S30861-Q348-X-C2/01

M:DCTPU

CF+/JN143255

S30861-Q392-X-08/01

M:DCPA

RO+/J8152086

S30861-Q348-X-C2/01

M:DCTPU

CF+/JN143250

S30861-U426-X-05/01

FAN

S30861-Q330-X100-B1/02 M:BBSIG44

CF+/J9109375

S30861-Q330-X100-B1/02 M:BBSIG44

CF+/J9109580

S30861-Q330-X100-B1/02 M:BBSIG44

CN+/J9110528

S30861-Q331-X-6/03

M:MCLK

RO+/J4222283

M:CCTRL

RO+/J3213618

S30861-Q337-X100-2/01

M:LI

CN+/K3201648

S30861-Q300-X100-2/01

M:ALCO

CF+/K6149797

S30861-Q344-X-08/03

M:GPSU

CF+/JO123790

S30861-U426-X-05/01

FAN

CF+/KO138942

S30861-B221-X-01/01

F:ACOM

RX+/L2999999

S30861-B222-X-03/01

F:BTS6

RX+/L2888888

S30861-C24-X-02/01

R:BS60

CF+/JD123759

S30861-Q332-X-J1/03

75

OGL:IDF EVOLUTION

Operator Guidelines
OGL:LMT BSS

Example of an IDF file delivered with a BS-60 equipment


Note 1:
Since the RLC might not know the correct:
SalesUniqueName (e.g. NAD042S7449E);
the SBS_Equipment_Position within the Mounting Location (e.g. 010101) or;
the rack position within the Functional Address (e.g. 1 within "FAN-1/0").
of the delivered racks, those data might be set to default values which have to be
updated during final commissioning in the field using the IDF Edtor Evolution.
It this case the following default values are to be chosen:
SalesUniqueName

"Serial number of the rack" where "/" is removed


e.g. RX+L2888888

SBS_Equipment_Position

"010101"

e.g. 01010102B004

Rack position within Functional


Address

"0"

e.g. FAN-0/2

Tab. 5.2

Default Values within IDF of RLC

Note 2:
Since the IDFs delivered from the RLC contain all the inventory objects in format "11"nob_RIUs and ob_RIUs - the network element would report the ob_RIUs twice. Because
of that fact and because of the possibility that in the future some objects might became
an ob_RIU as well a function of the IDF Evolution is provided.
This function looks for all objects having format version 10 and checks whether there
is another entry in the IDF with the same functional address, but with format "11". ll the
objects with these characteristics are deleted in order to have only not redundant
ob_RIUs in the IDF file.

5.1.2.2

Procedures: How to put the Inventory Data into the Network Element
The RLC provides all inventory data the commissioner needs to enter in the Network
Element with an inventory data file on a rack basis together with the racks. Task of the
commissioner is now to create the complete nob_RIU (NOB) file that shall be downloaded to the Network Element at the end of all the elaborations.
There are two scenarios possible:
A new Network Elementshall be installed;
A rack extension is to be installed.
The steps to be performed are in principle the same. The instllation of a rack contains a
a subset of functions requested for the installation of a new Network Element (for
example a new BSC).
A completely new network element is to be installed:
The process is described as an example of the installation of a new BTS BS-240 configured with one base, one extension and one service rack.
Action requested:
1. Start IDF Editor Evolution;
2. Select and Open IDF file;

76

A30808-X3247-M72-1-7619

Operator Guidelines
OGL:LMT BSS

OGL:IDF EVOLUTION

3.
4.
5.
6.
7.
8.
9.

Set "SBS_Equipment_Position" of all the inventory objects (nob/ob_RIUs);


Replace all rack positions of Functional Addresses (only for BTSE) and save the file;
Export the IDF file as a NOB file;
Upload IDT from the BS-240;
Open the IDT;
Attach NOB file to the loaded IDF;
Remove all the redundant nob_RIUs, save the file, generate a NOB file and then
download the file to the Network Element.
10. Close the IDF Editro Evolution;
11. Download the NOB file to the Network Element from the LMT Evolution.
Each action is described in detail as follow:
1. Start IDF Editor Evolution;

Fig. 5.13

A30808-X3247-M72-1-7619

Put Inventory Data into N.E. - Step 1

77

OGL:IDF EVOLUTION

Operator Guidelines
OGL:LMT BSS

2. Select and Open the IDF file imported from the RLC;

Fig. 5.14

2.1

Select the file to be opened (the default directory c:\LMT_root\...\idf\upload is


offered)

Fig. 5.15

78

Put Inventory Data into N.E. - Step 2

Put Inventory Data into N.E. - Step 2.1

A30808-X3247-M72-1-7619

Operator Guidelines
OGL:LMT BSS

OGL:IDF EVOLUTION

3. Set "SBS_Equipment_Position" of all the inventory data (nob/ob_RIUs):

A30808-X3247-M72-1-7619

Fig. 5.16

Put Inventory Data into N.E. - Step 3

Fig. 5.17

Put Inventory Data into N.E. - Step 3.1

Fig. 5.18

Put Inventory Data into N.E. - Step 3.2

79

OGL:IDF EVOLUTION

Operator Guidelines
OGL:LMT BSS

4. Replace all rack positions of Functional Addresses:

80

Fig. 5.19

Put Inventory Data into N.E. - Step 4

Fig. 5.20

Put Inventory Data into N.E. - Step 4.1

A30808-X3247-M72-1-7619

Operator Guidelines
OGL:LMT BSS

OGL:IDF EVOLUTION

Fig. 5.21

1. Save the file before exporting the NOB file otherwise the following message is shown.

Fig. 5.22

Put Inventory Data into N.E. - Step 4.2

Alert Message for Saving File

2. after saving the following message is shown:

Fig. 5.23

A30808-X3247-M72-1-7619

Confirmation of File Saved

81

OGL:IDF EVOLUTION

Operator Guidelines
OGL:LMT BSS

5. Export NOB file:

82

Fig. 5.24

Put Inventory Data into N.E. - Step 5

Fig. 5.25

Put Inventory Data into N.E. - Step 5.1

1. The default directory c:\LMT_root\...\idf\upload is available and the default name is


<salesuniquename>.nob.

A30808-X3247-M72-1-7619

Operator Guidelines
OGL:LMT BSS

OGL:IDF EVOLUTION

Fig. 5.26

Confirmation of NOB File Saved

2. it is not necessary to create the NOB file for downloading it to the Network Element.

Fig. 5.27

A30808-X3247-M72-1-7619

Alert Message for Exporting File

83

OGL:IDF EVOLUTION

Operator Guidelines
OGL:LMT BSS

6. Upload the IDT file from the LMT Evolution:

Fig. 5.28

84

Put Inventory Data into N.E. - Step 6

The parameters: DESTDIR and FILE are optional. The default values are:
- DESTDIR --> c:\LMT_root\...\idf\upload.
- FILE ---> BTSE.idt, TRAU.idt or BSC.idt

A30808-X3247-M72-1-7619

Operator Guidelines
OGL:LMT BSS

OGL:IDF EVOLUTION

7. Select and Open the uploaded IDT file:

A30808-X3247-M72-1-7619

Fig. 5.29

Put Inventory Data into N.E. - Step 7

Fig. 5.30

Put Inventory Data into N.E. - Step 7.1

85

OGL:IDF EVOLUTION

Operator Guidelines
OGL:LMT BSS

8. Attach NOB file to the actually loaded IDF file:

86

Fig. 5.31

Put Inventory Data into N.E. - Step 8

Fig. 5.32

Put Inventory Data into N.E. - Step 8.1

A30808-X3247-M72-1-7619

Operator Guidelines
OGL:LMT BSS

OGL:IDF EVOLUTION

Fig. 5.33

Put Inventory Data into N.E. - Step 8.2

9. Remove all the eventual redundant nob_RIUs:

A30808-X3247-M72-1-7619

Fig. 5.34

Put Inventory Data into N.E. - Step 9

Fig. 5.35

Ask for Removing all Redundant nob_RIU

87

OGL:IDF EVOLUTION

Operator Guidelines
OGL:LMT BSS

Fig. 5.36

9.1

Save the file:

Fig. 5.37

88

Confirmation of Deletion

Put Inventory Data into N.E. - Step 9.1

A30808-X3247-M72-1-7619

Operator Guidelines
OGL:LMT BSS

OGL:IDF EVOLUTION

9.2

generate a NOB file (the default directory is c:\LMT_root\...\idf\upload and the


file name is <salesuniquename>.nob):

Fig. 5.38

A30808-X3247-M72-1-7619

Put Inventory Data into N.E. - Step 9.2

89

OGL:IDF EVOLUTION

Operator Guidelines
OGL:LMT BSS

9.3

Generate the file to download it to the Network Element (the default directory
c:\LMT_root\...\idf\download and the default file name is BTS_NRIU):

Fig. 5.39

90

Put Inventory Data into N.E. - Step 9.3

A30808-X3247-M72-1-7619

Operator Guidelines
OGL:LMT BSS

OGL:IDF EVOLUTION

10. Close the IDF Editor Evolution:

Fig. 5.40

A30808-X3247-M72-1-7619

Put Inventory Data into N.E.- Step 10

91

OGL:IDF EVOLUTION

Operator Guidelines
OGL:LMT BSS

11. Download the NOB file from the LMT Evolution to the Network Element (the default
directory is c:\LMT_root\...\idf\download):

Fig. 5.41

92

Put Inventory Data into N.E. - Step 11

A30808-X3247-M72-1-7619

Operator Guidelines
OGL:LMT BSS

OGL:IDF EVOLUTION

Tasks to be performed for inserting the inventory data into the Network Element:
Although a lot of inventory data is automatically provided by the main important boards
implemented as ob_RIUs additional data related to the nob_RIUs have to be stored in
the core module of the Network Elements. The nob_RIU data are provided by the
Logistic Center in IDF file format related to each rack.
The following procedure describes in which way the inventory data are transferred to the
Network Element.

1) Start IDF Evolution

LMT

IDF
Editor

2) Open IDF of first rack


e.g. RX+_L2888888.IDF

LMT

IDF
Editor

b
LMT

IDF
Editor

3) Set SBS _Equipment_Position of all inventory objects


e.g. SET SBS_Equipment_Position=010305
4) Replace all rack positions of Functional Addresses

LMT

IDF

Editor

Another rack to be added


?

YES

IDF

Editor

b
LMT

Fig. 5.42

5) Export nob_RIU file

LMT

NO

2) Open IDF of next rack


e.g. CN+_JD100002.IDF

Pre-Processing of IDFs of Delivered Racks

The replacement of all the Rack Positions and SBS_Equipment_Positions of all inventory objects is especially relevant for the nob_RIUs in order to have there the right data.
For ob_RIUs this data is generated bautomatically by the Network Element.
In order to enable the Network Element to process the right data it is mandatory to set
the following data: SBS_Equipment_position, SalesUniqueName and typeOfBTSE (for
BTSE only) in advance.

A30808-X3247-M72-1-7619

93

OGL:IDF EVOLUTION

Operator Guidelines
OGL:LMT BSS

Establish connection to NEy

LMT

Set SBS_Equipment_Position
e.g. SBS_Equipment_Position =010305

LMT

b
LMT

Set SalesUniqueName
e.g. SalesUniqueName=AD042S7449E
6) Upload IDT from NEy

LMT

IDF

Editor

IDF

Editor

7) Open IDT

LMT

b
LMT

8) Attach nob_RIU file of first (or next) rack


e.g. e.g. RX+L888888.nob

Another rack to be added


?

YES

NO

IDF

Editor

9) Remove all redundant nob_RIUs

LMT

IDF

Editor

5) Export of nob_RIU file


e.g. AD042S7449E.nob

LMT

Fig. 5.43

94

Import of modified nob_RIU for the Racks in the Network Element IDF file

A30808-X3247-M72-1-7619

Operator Guidelines
OGL:LMT BSS

OGL:IDF EVOLUTION

IDF

Editor

10) Close IDF Evolution

LMT

11) Download nob_RIU file to the Ney


e.g. AD042S7449E.nob

LMT

Check IDF via Upload and Editing the IDF again


(optional)

LMT

Fig. 5.44

Download of the modified nob_RIU File to the related Network Element

A rack shall be extended:


The process for adding a new rack to an existing one is a subset of the process already
described.
The configuration of the "SBS_Equipment_Position" and "SalesUniqueName" is not
necessary for the installation of a new rack, for the reason that these informations are
provided during the commissioning of the already existing equipment.
The download of the modified NOB file to the Network Element does not require modifications.
A new device (for example a COBA/COSA board) shall be installed:
If a new device (for example a COBA board) shall be installed,it is necessary to considered two different cases:
- The device is implemented as an ob_RIU (for example the COBA board):
- The device is implemented as a nob_RIU (for example a FAN).

Ob_RIU:
The Network Element automatically provides the inventory data after the physical
recovery of the module. No administration of inventory data is requested. It makes
sense to upload the latest version of the IDF file for backup purposes.

Nob_RIU:
The following steps shall be executed:
- From the LMT Evolution upload the IDT file stored in the Network Element and store it
in a directory accessible also from the IDF Editor Evolution;
- Open the IDT file from the IDF Editor Evolution;
- Selects the corresponding N record and add manually the requested inventory data.
This action can be executed also automatically with the support of the 2D-Code-LabelReader device.
- Export the IDT file in as a NOB file and save it in a local directory.
- Close the IDF Editor Evolution.
- Download ther NOB file to the Newtork Element form the LMT Evolution.
A device (for example a CU) shall be replaced:
If a device like a CU or FAN shall be replaced the following two cases shall be considered:

A30808-X3247-M72-1-7619

95

OGL:IDF EVOLUTION

Operator Guidelines
OGL:LMT BSS

- The device has been implemented as a ob_RIU (for example a CU, TPU);
- The device has been implemented as a nob_RIU (for example a FAN).

Ob_RIU:
In case of an ob_RIU the system automatically provides the inventory data after the
physical recovery of the replaced device. No administration of inventory data is
requested. It is useful to upload from the Network Element the more recent version of
the IDF file for backup purposes.

Nob_RIU:
In case of a nob_RIU the following steps shall be executed:
- From the LMT Evolution upload the IDT file stored in the NEtwork Element and stores
it in a local directory accessible also from the IDF Editot Evolution;
- Start the IDF EDitor Evolution;
- Open the IDT file;
- Edit the I-Record and replace the inventory data.
- Export the file as a NOB file;
- Store the NOB fle in a local directory accessible also from the LMT Evolution;
- Close the IDF Editor Evolution;
- Download the NOB file to the Network Element from the LMT Evolution.

5.1.3

Export IDF File for Backup


1. Export the IDF file for backup and forward it to the inventory system (see Fig. 5.45).

Fig. 5.45

96

Export IDF File for backup purpose - Step 1

A30808-X3247-M72-1-7619

Operator Guidelines
OGL:LMT BSS

OGL:IDF EVOLUTION

2. Select the file name (the default directory is : C:\Siemens\IDF111_xx_ yy\Upload.


The default file name is: <salesuniquename>.idf - see the Fig. 5.46.

Fig. 5.46

Export the IDF File - Step 2

3. Ack message (see Fig. 5.47).

Fig. 5.47

A30808-X3247-M72-1-7619

Export IDF File - Step 3

97

OGL:IDF EVOLUTION

5.1.4

Operator Guidelines
OGL:LMT BSS

Export NOB for Downloading to the Network Element


1. Export NOB (see Fig. 5.48).

Fig. 5.48

Export NOB - Step 1

2. Select the file name (the default directory is: C:\Siemens\IDF111_xx_ yy\download.
The default file name is: <salesuniquename>.nob - see the Fig. 5.49).

Fig. 5.49

98

Export NOB - Step 2

A30808-X3247-M72-1-7619

Operator Guidelines
OGL:LMT BSS

OGL:IDF EVOLUTION

3. Confirmation of the creation of the NOB file; (see Fig. 5.50).

Fig. 5.50

Export NOB - Step 3

4. Ack message (see Fig. 5.51).

Fig. 5.51

A30808-X3247-M72-1-7619

Export NOB - Step 4

99

OGL:IDF EVOLUTION

100

Operator Guidelines
OGL:LMT BSS

A30808-X3247-M72-1-7619

Operator Guidelines
OGL:LMT BSS

OGL:IDF EVOLUTION

6 Appendix
6.1

Use of the IDF Editor Evolution within RC Scripts


In order to use the IDF Editor Evolution within a Solaris script, the user shall fulfill the
requirements stated in the Readme.txt file that can be found in the related installations
folder.
Once all the requirements have been fulfilled, he has to write, as header of the script file,
some lines that set the JAVA_HOME local variable:
#!/bin/sh
JAVA_HOME=/usr/j2sdk1.4.2
export JAVA_HOME
At this point he can use IDF Evolution application like:
"$JAVA_HOME/bin/java" -cp ./CSVExcelReader.jar:./comm.jar:./commons-codec-1.1.jar:./log4j1.2.7.jar:./idf-evolution-obf.jar com.siemens.idf_editor.editor.IDFEvolution args1, args2
The last line has three colors:
Black: this part should not change;
Red: this part can be set as local variable in order to avoid writing each time all jar
files;
Blue: represent a list of arguments.
Argument description:
None argument: IDF Evolution starts the GUI;
File_name, removeRNCredundancies: perform the Remove RNC redundancies
function over an IDF or IDT file.

The second argument will be check as case insensitive, so writing copyinformation or


CoPyInfOrmatION will be the same. This has been decided to help the user while writing
the script under Solaris.
Example:
1. The user should import the SN List and save it as a NOB file;
2. The user downloads the NOB file to the Network Element;
3. The user upload the IDT file (filename.idt) and performs copy information and
remove the eventual redundancies.
In order to execute the last step, the user can also launch a script like for example the
following one:

A30808-X3247-M72-1-7619

101

OGL:IDF EVOLUTION

Operator Guidelines
OGL:LMT BSS

#!/bin/sh
# Set JAVA_HOME so that the java executable file can be
launch.
# For example if java executable is located into
/usr/j2sdk1.4.2/bin/java you can split as follow
# JAVA_HOME=/usr/j2sdk1.4.2 and the execution line (refer to
the last line of this script) will be "$JAVA_HOME/bin/java"
# or JAVA_HOME=/usr/j2sdk1.4.2/bin and "$JAVA_HOME/java"
#########SETTING JAVA_HOME
JAVA_HOME=/usr/j2sdk1.4.2
export JAVA_HOME
# The next line is obmitteed because use the flag -cp (for expert user: you can
use the CLASSPATH variable instead of -cp)
#export CLASSPATH=./CSVExcelReader.jar:./comm.jar:./commons-codec1.1.jar:./log4j-1.2.7.jar
# Setup the JVM
#####################################
##
COPY INFORMATION
##
#####################################
"$JAVA_HOME/bin/java" -cp ./CSVExcelReader.jar:./comm.jar:./commons-codec-1.1.jar:./log4j-1.2.7.jar:./idf-evolution-obf.jar com.siemens.idf_editor.editor.IDFEditor
cpi filename.idt
#####################################
##
REMOVE RNC REDUNANCIES
##
#####################################
"$JAVA_HOME/bin/java" -cp ./CSVExcelReader.jar:./comm.jar:./commons-codec-1.1.jar:./log4j-1.2.7.jar:./idf-evolution-obf.jar com.siemens.idf_editor.editor.IDFEditor
rm filename.idt

102

A30808-X3247-M72-1-7619

Operator Guidelines
OGL:LMT BSS

OGL:IDF EVOLUTION

Abbreviations

BSC

Base Station Controller

BTS

Base Transceiver Station

CU

Carrier Unit

FW

Firmware

IDF

Inventory Data File

IDT

Inventory Data Table

JRE

Java RunTime Environment

NEy

Network Entity

RLC

Regional Logistic Center

RNC

Radio Network Controller

TRAU

Transcoding and rate Adaptation Unit

A30808-X3247-M72-1-7619

103