You are on page 1of 93

GERAN

Operator Guidelines
OGL:LMT BSS

OGL:IDF EVOLUTION
A50016-G5100-A072-01-7619

OGL:IDF EVOLUTION

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 2006


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.

Id:0900d8058007469a

A50016-G5100-A072-01-7619

OGL:IDF EVOLUTION

Table of Contents
This document has 93 pages.
Reason for Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
1
1.1

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Purpose of the IDF Evolution tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

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 Evolution Installation . . . . . . . . . . . . . . . . . . . . . . . . .
Sun Java Runtime Environment (JRE) Installation . . . . . . . . . . . . . . . . . . .
JRE software for Solaris Platform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
JRE software for Windows Platform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Java Communication API Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
IDF Evolution Uninstallation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Hints in Case of Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

12
12
12
13
14
15
15
15
17
22
23
23

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

Fundamentals of the IDF Evolution. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


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

24
24
24
26
27
27
27
27
28
29
29

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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

30
30
30
31
32
32
33
33
34
35
36
37
39
40
40
41

A50016-G5100-A072-01-7619

Id:0900d8058007469a

OGL:IDF EVOLUTION

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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41


Export IDF Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Export NOB Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
View Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
All, nob_RIus, ob_RIUs commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
HW Table Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Insert Record Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Delete Record Command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Modify Record Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Options Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Select On Click . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Hide ASCII File window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Look and Feel Command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Switch Application Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Tools Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Set Scanner Port Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Help Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Help Contents Command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
About IDF Evolution Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Pop Up Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Root Pane Pop Up Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Create . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Inventory Panel Pop Up Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Delete. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Edit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
2D Code Reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
METHANETICS CORPORATION IR-2000 . . . . . . . . . . . . . . . . . . . . . . . . . 60
Hardware Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Using 2D Code Reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62


Procedure: Update of a nob_RIU. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Step by Step Approach . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
In Case a Nob_RIU is Newly to Be Created . . . . . . . . . . . . . . . . . . . . . . . . 62
In Case a Nob_RIU is Already Present and is to be Replaced . . . . . . . . . . 65
In Case a Nob_RIU is Already Present and has to be Removed. . . . . . . . . 66
IDF File imported from RLC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Logistics: Inventory Data Delivered by RLC to the Project . . . . . . . . . . . . . 67
Procedures: How to put the Inventory Data into the Network Element . . . . 71
Export IDF File for Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Export NOB for Downloading to the Network Element. . . . . . . . . . . . . . . . . 92

Id:0900d8058007469a

A50016-G5100-A072-01-7619

OGL:IDF EVOLUTION

List of Figures
Figure 1
Figure 2
Figure 3
Figure 4
Figure 5
Figure 6
Figure 7
Figure 8
Figure 9
Figure 10
Figure 11
Figure 12
Figure 13
Figure 14
Figure 15
Figure 16
Figure 17
Figure 18
Figure 19
Figure 20
Figure 21
Figure 22
Figure 23
Figure 24
Figure 25
Figure 26
Figure 27
Figure 28
Figure 29
Figure 30
Figure 31
Figure 32
Figure 33
Figure 34
Figure 35
Figure 36
Figure 37
Figure 38
Figure 39
Figure 40
Figure 41
Figure 42
Figure 43
Figure 44
Figure 45

A50016-G5100-A072-01-7619

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


JRE Solaris Download: Choice of the Version. . . . . . . . . . . . . . . . . . . .
JRE Solaris Download: License Agreement . . . . . . . . . . . . . . . . . . . . .
JRE Solaris Download: Choice of the SW . . . . . . . . . . . . . . . . . . . . . . .
JRE Installation:Welcome Window (Windows Version) . . . . . . . . . . . . .
JRE Installation: Software License window (Windows Version) . . . . . .
JRE Installation: Installshield Wizard Window . . . . . . . . . . . . . . . . . . . .
JRE Installation: Setup window (Windows Version) . . . . . . . . . . . . . . .
JRE Installation: Installation window - phase 1 (Windows Version). . . .
JRE Installation: Installation window - phase 2 (Windows Version). . . .
JRE Installation: Installation window - phase 3 (Windows Version). . . .
JRE Installation: End Icon (Windows Version). . . . . . . . . . . . . . . . . . . .
Example of IDF Evolution Startup Window . . . . . . . . . . . . . . . . . . . . . .
File Types Graphical Representation. . . . . . . . . . . . . . . . . . . . . . . . . . .
Example of Exporting C_IDF or C_TXT file . . . . . . . . . . . . . . . . . . . . . .
IIDF Evolutions File Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
IDF Evolution Main Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Title Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Menu Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tool Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Root Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Inventory Panel. Only OB RIUs are Displayed. . . . . . . . . . . . . . . . . . . .
ASCII Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Status Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
File Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Open Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Open Dialog Box Example with Windows XP OS . . . . . . . . . . . . . . . . .
Close Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Save Command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Save As Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Attach Command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Set SBS_Equipement_Position Command . . . . . . . . . . . . . . . . . . . . .
Set SBS_Equipement_Position Dialog Box . . . . . . . . . . . . . . . . . . . . . .
Set F.A. RACK_Position Command . . . . . . . . . . . . . . . . . . . . . . . . . .
Set RACK_Position (Functional Address) Dialog Box . . . . . . . . . . . . . .
Remove nob_RIUs Command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Search Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Search Dialog Box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Search Dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Exit Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Export Menu (in this example an IDF file has been opened). . . . . . . .
C_IDF Export Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Export C_TXT Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Export IDT Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Export IDF Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Id:0900d8058007469a

15
16
16
17
18
18
19
19
20
20
21
21
22
24
25
25
26
27
27
27
27
29
29
29
30
31
31
32
32
33
33
34
34
35
35
36
37
38
38
39
40
40
41
41
42

OGL:IDF EVOLUTION

Figure 46
Figure 47
Figure 48
Figure 49
Figure 50
Figure 51
Figure 52
Figure 53
Figure 54
Figure 55
Figure 56
Figure 57
Figure 58
Figure 59
Figure 60
Figure 61
Figure 62
Figure 63
Figure 64
Figure 65
Figure 66
Figure 67
Figure 68
Figure 69
Figure 70
Figure 71
Figure 72
Figure 73
Figure 74
Figure 75
Figure 76
Figure 77
Figure 78
Figure 79
Figure 80
Figure 81
Figure 82
Figure 83
Figure 84
Figure 85
Figure 86
Figure 87
Figure 88
Figure 89
Figure 90
Figure 91
Figure 92

Export NOB Command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42


View Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
All Records view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
View nob_RIUs records . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
View only ob_RIU Records . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Hardware Table Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Insert Record panel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Delete Record panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Modify Record panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Modify Record panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Options Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Select on Click Option Enabled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Select on Click Option Disabled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Hidden ASCII window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Look and Feel Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Switch Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Tools Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Communication Scanner Port Dialog Box. . . . . . . . . . . . . . . . . . . . . . . . 53
Error dialog box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Help Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Help window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
About IDF Evolution window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Create command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
New NOB_RIU panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Panel for inserting the requested inventory data . . . . . . . . . . . . . . . . . . 57
Delete command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Edit command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Edit Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
2D Code Reader Targeting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Open selected File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Insert a New Nob_RIU - Step 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Insert a New Nob_RIU - Step 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Insert a New Nob_RIU - Step 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Insert a New Nob_RIU - Step 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
2D-Code Reader. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Port Setting for 2D-Code Reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Replacement of a Nob_RIU - Step 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Replacement of a Nob_RIU - Step 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Nob_RIU deletion - Step 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Confirmation of the deletion operation . . . . . . . . . . . . . . . . . . . . . . . . . . 67
IDFs Delivered with the BTS Equipment. . . . . . . . . . . . . . . . . . . . . . . . . 67
Put Inventory Data into N.E. - Step 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Put Inventory Data into N.E. - Step 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Put Inventory Data into N.E. - Step 2.1. . . . . . . . . . . . . . . . . . . . . . . . . . 73
Put Inventory Data into N.E. - Step 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Put Inventory Data into N.E. - Step 3.1. . . . . . . . . . . . . . . . . . . . . . . . . . 74
Put Inventory Data into N.E. - Step 3.2. . . . . . . . . . . . . . . . . . . . . . . . . . 74

Id:0900d8058007469a

A50016-G5100-A072-01-7619

OGL:IDF EVOLUTION

Figure 93
Figure 94
Figure 95
Figure 96
Figure 97
Figure 98
Figure 99
Figure 100
Figure 101
Figure 102
Figure 103
Figure 104
Figure 105
Figure 106
Figure 107
Figure 108
Figure 109
Figure 110
Figure 111
Figure 112
Figure 113
Figure 114
Figure 115
Figure 116
Figure 117
Figure 118
Figure 119
Figure 120
Figure 121
Figure 122
Figure 123
Figure 124
Figure 125

A50016-G5100-A072-01-7619

Put Inventory Data into N.E. - Step 4. . . . . . . . . . . . . . . . . . . . . . . . . . . 75


Put Inventory Data into N.E. - Step 4.1 . . . . . . . . . . . . . . . . . . . . . . . . . 75
Put Inventory Data into N.E. - Step 4.2 . . . . . . . . . . . . . . . . . . . . . . . . . 75
Error Message for Saving File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Confirmation of File Saved. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Put Inventory Data into N.E. - Step 5. . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Put Inventory Data into N.E. - Step 5.1 . . . . . . . . . . . . . . . . . . . . . . . . . 77
Confirmation of NOB File Saved . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Alert Message for Exporting File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Put Inventory Data into N.E. - Step 6. . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Put Inventory Data into N.E. - Step 7. . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Put Inventory Data into N.E. - Step 7.1 . . . . . . . . . . . . . . . . . . . . . . . . . 80
Put Inventory Data into N.E. - Step 8. . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Put Inventory Data into N.E. - Step 8.1 . . . . . . . . . . . . . . . . . . . . . . . . . 81
Put Inventory Data into N.E. - Step 8.2 . . . . . . . . . . . . . . . . . . . . . . . . . 82
Put Inventory Data into N.E. - Step 9. . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Ask for Removing all Redundant nob_RIU . . . . . . . . . . . . . . . . . . . . . . 82
Confirmation of Deletion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Put Inventory Data into N.E. - Step 9.1 . . . . . . . . . . . . . . . . . . . . . . . . . 83
Put Inventory Data into N.E. - Step 9.2 . . . . . . . . . . . . . . . . . . . . . . . . . 84
Put Inventory Data into N.E. - Step 9.3 . . . . . . . . . . . . . . . . . . . . . . . . . 84
Put Inventory Data into N.E.- Step 10 . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Put Inventory Data into N.E. - Step 11. . . . . . . . . . . . . . . . . . . . . . . . . . 86
Pre-Processing of IDFs of Delivered Racks. . . . . . . . . . . . . . . . . . . . . . 87
Import of modified nob_RIU in the IDF file. . . . . . . . . . . . . . . . . . . . . . . 88
Download of the modified nob_RIU File to the related Network Element 88
Export IDF File for backup purpose - Step 1 . . . . . . . . . . . . . . . . . . . . . 91
Export the IDF File - Step 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Export IDF File - Step 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Export NOB - Step 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Export NOB - Step 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Export NOB - Step 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Export NOB - Step 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

Id:0900d8058007469a

OGL:IDF EVOLUTION

List of Tables
Table 1
Table 2
Table 3
Table 4
Table 5
Table 6
Table 7

System Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Format Conversion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Default parameters for IR-2000HD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Decode Options for the IR-2000HD . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Example of IDF filenames received from RLC . . . . . . . . . . . . . . . . . . . . 68
Example of IDF file delivered with a BS-60 equipment. . . . . . . . . . . . . . 68
Default Values within IDF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Id:0900d8058007469a

A50016-G5100-A072-01-7619

OGL:IDF EVOLUTION

Reason for Update

Reason for Update


Issue History
Issue
01

Date
12/2006

Summary
New release BR9.0

Issue 1 for Release BR9.0 (12/2006)

A50016-G5100-A072-01-7619

Id:0900d805800eb164

Reason for Update

10

OGL:IDF EVOLUTION

Id:0900d805800eb164

A50016-G5100-A072-01-7619

OGL:IDF EVOLUTION

Introduction

1 Introduction
This manual describes the characteristics and functions of the IDF Evolution tool that
supports the inventory data management of the BSS Network Elements (BSC, BTS,
TRAU). Besides it supports the user through the many functions provided by the Graphical User Interface (GUI). The term Evolution is related to the enhancement of the IDF
tool supporting up to the BR7.0 release the user in the entire process of inventory data
management. IDF Evolution is the Siemens official name of the product.

1.1

Purpose of the IDF Evolution tool


The IDF Evolution is a very powerful software application supporting the 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 resources installed and configured
on each BSS Network Element (BSC, BTS, TRAU).
All the Least Replaceable Unit (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 supported by the Remote Inventory feature:

Hardware resources with an on-board memory on which PID is stored are called On
board memory RIUs (ob-RIUs);

Hardware resources without an on-board memory and consequently without PID are
called Not on board memory RIU (nob-RIU).

Inventory data related to ob-RIUs can be read automatically by the Remote Inventory
Scanning Procedure triggered by the 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 using the IDF Evolution
tool. The process consists of the following procedure: the file storing nob-RIU data (NOB
file) is uploaded on the LMT Evolution and stored in a local directory accessible also by
the IDF Evolution tool. From IDF Evolution the NOB file is then opened, modified by the
user and saved again. Then it is downloaded to the BSC from the LMT Evolution and
finally stored in a not volatile memory. IDF Evolution 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 it is available a suitable and ad-hoc installation procedure.

A50016-G5100-A072-01-7619

Id:0900d8058007455a

11

IDF Architecture and Installation Procedures

OGL:IDF EVOLUTION

2 IDF Architecture and Installation Procedures


This chapter describes the IDF Evolution hardware and software characteristics. It
contains also the description of the installation procedures.

2.1

System Requirements for Microsoft Windows


g The Installation of 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 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.

2.1.1

Hardware
The IDF Evolution tool is provided in two different hardware configurations, as follow:

12

Notebook configuration:
The notebook (for example a Siemens Scenic 510) shall be configured at least as
follow:
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.

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.

Id:0900d805800e7550

A50016-G5100-A072-01-7619

OGL:IDF EVOLUTION

2.1.2

IDF Architecture and Installation Procedures

Software
The IDF Evolution runs on Sun Java RunTime Environment (JRE) supported by the following Operative Systems:

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 Evolution application can be installed on a Personal Computer supporting one
of these operating systems in a local directory created by the user. At the end of the successful installation, the local directory 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 match this requirement).

A50016-G5100-A072-01-7619

Id:0900d805800e7550

13

IDF Architecture and Installation Procedures

2.2

OGL:IDF EVOLUTION

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


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

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

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

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

IA32 Windows
System Requirements 32-bit: SDK
J2RE

Table 1

14

Version

System Configurations

Id:0900d805800e7550

A50016-G5100-A072-01-7619

OGL:IDF EVOLUTION

2.3

IDF Architecture and Installation Procedures

Prerequisites for IDF Evolution Installation


To install the IDF Evolution application, the following software shall be installed:
1. Sun Java Runtime Environment (JRE) for Solaris or Windows platform;
2. Java Communication API;
3. IDF Evolution main application.
Sun Java Runtime Environment (JRE) program for Solaris can be downloaded from
Java Sun site http://java.sun.com.
Sun Java Runtime Environment (JRE) for Windows version 1.4.2.1, Java Communication API and IDF Evolution applications are available in the form of a compressed file
(for example the file: 10000.tar.z).
For any problem related to JRE or javacommunication Sun site http://java.sun.com is
the reference.

2.3.1

Sun Java Runtime Environment (JRE) Installation


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

2.3.1.1

JRE software for Solaris Platform


Latest version of Sun Java Runtime Environment (JRE) program for Solaris and
Windows can be downloaded from Java Sun site (http://java.sun.com), usually JRE can
be found under J2SE download page as shown in Figure 1 below:

Figure 1

JRE Solaris Download: Choice of the Edition Version

JRE for Solaris software download 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 shown in next Figure 2:

A50016-G5100-A072-01-7619

Id:0900d805800e7550

15

IDF Architecture and Installation Procedures

Figure 2

OGL:IDF EVOLUTION

JRE Solaris Download: Choice of the Version

Then the License Agreement window (see next Figure 3) is displayed: Then the user
shall select the buttons: Accept and Continue.

Figure 3

JRE Solaris Download: License Agreement

The next Figure 4 shows the files storing the software to download. The choice between
64 or 32 bit depends on the type of Solaris Computer. The downloaded files name is
(for example):

16

j2re-1_4_2_03-solaris-sparc.sh for 32 bit;


j2re-1_4_2_03-solaris-sparcv9.sh for 64 bit.

Id:0900d805800e7550

A50016-G5100-A072-01-7619

OGL:IDF EVOLUTION

IDF Architecture and Installation Procedures

Figure 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 previous Figure 2.

2.3.1.2

JRE software for Windows Platform


JRE software version 1.4.2.1 for Windows is released together with IDF Evolution file.
The installation procedure checks automatically if JRE software is already installed on
the machine on which the IDF Evolution shall be installed.
In case 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 automatically the installation of JRE software.
Within the pop-up window the user is informed that JRE installation is permitted only to
the system administrator. On the contrary, JRE installation is aborted and consequently
IDF Evolution will not be installed.
The main panels automatically displayed to the user by JRE installation procedures are
described below.
Java Platform Welcome window (see next Figure 5) provides some installation notes.

A50016-G5100-A072-01-7619

Id:0900d805800e7550

17

IDF Architecture and Installation Procedures

Figure 5

OGL:IDF EVOLUTION

JRE Installation:Welcome Window (Windows Version)

Then Java Software License window is displayed to the user (see next Figure 6):

Figure 6

JRE Installation: Software License window (Windows Version)

The user can accept the license agreement by selecting I accept the terms in the
license agreement. In this case he/she shall click on the Next button to continue the
installation.
Then Installshield Wizard window is displayed to the user as represented in next Figure
7:

18

Id:0900d805800e7550

A50016-G5100-A072-01-7619

OGL:IDF EVOLUTION

IDF Architecture and Installation Procedures

Figure 7

JRE Installation: Installshield Wizard Window

At the successfully conclusion of the Preparing Setup procedure, Start of Setup is triggered as represented in next Figure 8:

Figure 8

JRE Installation: Setup window (Windows Version)

The next Figure 9, Figure 10 and Figure 11 show the installation phase.
Select Modify in the appearing window (see Figure 9) and click on the Next Button.

A50016-G5100-A072-01-7619

Id:0900d805800e7550

19

IDF Architecture and Installation Procedures

Figure 9

OGL:IDF EVOLUTION

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

Select Java 2 Runtime Environment (see Figure 10) and click on the Next Button.

Figure 10

20

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

Id:0900d805800e7550

A50016-G5100-A072-01-7619

OGL:IDF EVOLUTION

IDF Architecture and Installation Procedures

Figure 11

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

When the Installation procedure is completed successfully (as represented in next


Figure 12), the user clicks on the Finish button. The computer shall then be restarted.

Figure 12

JRE Installation: End Icon (Windows Version)

At the end of JRE software successful installation, the IDF Evolution startup procedure
asks the user a confirmation for continuing the software installation. For the purpose a
specific window is opened. If the user clicks the OK button, the installation procedure
continues automatically.

A50016-G5100-A072-01-7619

Id:0900d805800e7550

21

IDF Architecture and Installation Procedures

2.3.1.3

OGL:IDF EVOLUTION

Java Communication API Installation


The installation procedure checks if Java Communication API have been already
installed on the machine on which the IDF Evolution Application has to be installed.
In case Java Communication API have not been installed the user is asked by a specific
pop-up window to confirm the installation of API software. If the user confirms by clicking
the button OK the installation procedure starts the installation of the API software.
Only the system administrator has the permission to install Java Communication API.
On the contrary API installation is aborted but IDF Evolution installation is not interrupted. Without API some functionalities are not available, for example 2D code Reader.

g 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
Finally, the extracted comm.jar file shall be copied under the IDF Evolution folder too.
At the end of the IDF Evolution Application installation procedure, the user can start the
IDF Evolution application from his/her Windows startup File menu by clicking on a
graphical icon.
Start-up window is then opened as shown in the Figure 13, Example of IDF Evolution
Startup Window.

Figure 13

22

Example of IDF Evolution Startup Window

Id:0900d805800e7550

A50016-G5100-A072-01-7619

OGL:IDF EVOLUTION

2.3.2

IDF Architecture and Installation Procedures

IDF Evolution Uninstallation


In Solaris Environment: The user must uninstall the IDF Evolution removing the related
files.
In Windows Environment: The user shall select the Uninstall entry from the IDF Evolution start up menu. In case the IDF Evolution has been installed using Administrator
rights, the same rights must be used to unistall it.

2.3.3

Hints in Case of Error


The IDF Evolution logs information to trace debug info.
To collect information, the user must change the value of TraceLevel contained in IDF
Evolution properties file as follow:
Replace the line TraceLevel=0 with the new line TraceLevel=5
The result of this configuration action is the idfEvolution.log file. This file contains
useful information to support the analysis of the occurred problem.
For eventual additional problems also the Troubleshot.txt file can be an useful support.

A50016-G5100-A072-01-7619

Id:0900d805800e7550

23

Fundamentals of the IDF Evolution

OGL:IDF EVOLUTION

3 Fundamentals of the IDF Evolution


3.1

Purpose of the IDF Evolution


The IDF Editor 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) with the
addition of header and footer records;
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 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 Evolution Graphical User Interface (GUI). Menu and commands are
described in the chapter: "4 Menu and Commands".

3.2

File Formats
In Figure 14 below the files types that can be managed by the IDF Evolution are represented.

Figure 14

File Types Graphical Representation

The IDF 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

Table 2

Format Conversion

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 Figure 15 below.

24

Id:0900d80580074a0c

A50016-G5100-A072-01-7619

OGL:IDF EVOLUTION

Fundamentals of the IDF Evolution

Figure 15

Example of Exporting C_IDF or C_TXT file

Next Figure 16 shows the files managed by IDF Evolution.

Figure 16

A50016-G5100-A072-01-7619

IIDF Evolutions File Types

Id:0900d80580074a0c

25

Fundamentals of the IDF Evolution

3.3

OGL:IDF EVOLUTION

IDF Evolution Graphical User Interface (GUI)


Main Panel of the IDF Evolution is structured into seven component as represented in
next Figure 17 :
1. Title Bar;
2. Menu Bar;
3. Tool Bar;
4. Root Panel;
5. Inventory Panel;
6. ASCII window;
7. Status Bar.

1 - Title Bar

3 - Tool Bar

2 - Menu Bar

4 - Root
Panel

5 - Inventory
Panel

6 - ASCII Windows

7 - Status Bar
Figure 17

26

IDF Evolution Main Panel

Id:0900d80580074a0c

A50016-G5100-A072-01-7619

OGL:IDF EVOLUTION

3.3.1

Fundamentals of the IDF Evolution

Title Bar
The Title Bar shows the word: IDF Evolution - GSM as shown in Figure 18.

Figure 18

3.3.2

Title Bar

Menu Bar
The Menu Bar represented in next Figure 19 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.

Figure 19

3.3.3

Menu Bar

Tool Bar
Tool Bar represents the most used functionalities as icons. For each of them a tool tip
is associated as represented in next Figure 20.

Figure 20

3.3.4

Tool Bar

Root Panel
The Root Panel shown in Figure 21 displays 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 Figure 21):

SalesUniqueName: 11 alphanumeric characters which identify the Network


Element. It is a unique worldwide identifier assigned by Sales department;
NEyType: A = TRAU, C = BSC, S = BTS;
SystemSWVersion: 12 characters which identify the software version running on the
Network Element.

Figure 21

A50016-G5100-A072-01-7619

Root Panel

Id:0900d80580074a0c

27

Fundamentals of the IDF Evolution

3.3.5

OGL:IDF EVOLUTION

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 are displayed with 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 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 displayng data in the Inventory
Panel can be chosen as represented in Figure 22; 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.

g 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.
The I records consist of the following elements as represented in Figure 22:

28

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.

Id:0900d80580074a0c

A50016-G5100-A072-01-7619

OGL:IDF EVOLUTION

Fundamentals of the IDF Evolution

Figure 22

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 panel tree as represented in next Figure 23. This last
option can be disabled by the user as described in 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.

Figure 23

3.3.7

ASCII Window

Status Bar
Status bar shows the complete path_name of the opened file. When no file is opened
the status bar is hidden as represented in next Figure 24.

Figure 24

A50016-G5100-A072-01-7619

Status Bar

Id:0900d80580074a0c

29

Menu and Commands

OGL:IDF EVOLUTION

4 Menu and Commands


In this chapter the menu and commands provided by the Graphical User Interface (GUI)
are described.

4.1

Menu Bar
The Menu Bar consists of the following seven menus as represented in next Figure 25:
1.
2.
3.
4.
5.
6.
7.

4.1.1

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

File Menu
Next Figure 25 below shows the file menu and its commands.

Figure 25

30

File Menu

Id:0900d805800e7a3b

A50016-G5100-A072-01-7619

OGL:IDF EVOLUTION

4.1.1.1

Menu and Commands

Open Command
The user can open a stored IDT, IDF or ZDT file by clicking the menu command
File\Open or the corresponding icon in the Tool Bar. See next Figure 26.

Figure 26

Open Command

Input: The user types the <file> pathname;


Output: The file is opened.
Remarks:
The Open command displays the Open dialog Box. If the file specified by the pathname
does not exist, the user shall verify the correctness of the filename. In case the Operative System is Windows XP, the Open dialog Box is represented in next Figure 27.
If the IDF Evolution finds a format error the input file is not opened and an error dialog
box is displayed in which a short explanation of the errors possible causes is given.
When the user opens an IDT, an IDF or a ZDT file the related data are displayed according to the selected View menu item.
When the selected file is a ZDT file, according to the chosen View menu items, the user
has to click the left mouse button on the related N record to retrieve S and I records.

Figure 27

A50016-G5100-A072-01-7619

Open Dialog Box Example with Windows XP OS

Id:0900d805800e7a3b

31

Menu and Commands

4.1.1.2

OGL:IDF EVOLUTION

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

Figure 28

Close Command

Command: close
Purpose: the opened loaded file is closed.
Remarks:
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 Evolution automatically saves all
changes before closing it.

4.1.1.3

Save Command
This command saves all changes made in the opened file by clicking the menu
command File\Save or by the corresponding icon in the Tool Bar (see next Figure 29).

Figure 29

Save Command

Command: Save;
Purpose: All actions executed by the user are saved.
Remarks:
This command saves the current file without changing opened file pathname.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.

32

Id:0900d805800e7a3b

A50016-G5100-A072-01-7619

OGL:IDF EVOLUTION

4.1.1.4

Menu and Commands

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

Figure 30

Save As Command

Command: Save as;


Purpose: the opened file is saved with a new pathname or as a NOB file if the opened
file is a Csv file.
Remarks:
The menu command File\Save as is enabled only if the user has made changes in the
current opened file and are disabled after saving it.

4.1.1.5

Attach Command
This command attaches a NOB file to an IDT or an IDF file. The user shall click on the
command File\Attach or on the corresponding icon in the Tool Bar (see Figure 31
below).

Figure 31

Attach Command

Input: saved NOB file;


Output: inventory objects of the input file are attached.

A50016-G5100-A072-01-7619

Id:0900d805800e7a3b

33

Menu and Commands

OGL:IDF EVOLUTION

Remarks:
This command is enabled only for IDT or IDF files and displays Open dialog Box.
If the file specified by the pathname does not exist, the user reenters correct file name.
If the IDF Evolution finds a format error the input file is not attached.
Not all the inventory objects are attached, but only those that have not been already registered, in the current file, as nob_RIUs or as ob_RIUs with their format different from
D.The total number of attached objects is displayed after the command execution. If the
original file is an IDF the footer record is automatically updated.If all the inventory objects
have been attached, File\Save menu command, File\SaveAs menu command and the
toolbar save button are enabled.

4.1.1.6

Set SBS_Equip_Pos Command


This command replaces all SBS Equipment Positions within Mounting Position. The
user clicks on the menu command File\Set SBS_Eq_Pos and the panel: Set
SBS_Equipment_Position is opened (see next Figure 32).

Figure 32

Set SBS_Equipement_Position Command

The user types the SBS Equipment Position (it is made by the first six bytes of Mounting
Position field) and clicks on the button Replace All. All positions are replaced with the
new ones inserted by the user. See next Figure 33.

Figure 33

Set SBS_Equipement_Position Dialog Box

Command: Set SBS_Eq_Pos;


Purpose: It replaces all SBS Equipment Positions.

34

Id:0900d805800e7a3b

A50016-G5100-A072-01-7619

OGL:IDF EVOLUTION

Menu and Commands

The user replaces all SBS equipment positions, present in the Mounting Position field of
all 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.
For example: "010101"+"02B004" 01010102B004.
The total number of replaced objects is displayed after the command execution.
If any inventory object has been replaced, File\Save menu command and toolbar save
button are enabled.

4.1.1.7

Set Functional Address Rack Position Command


This command replaces all rack positions within the Functional Addresses. The user
clicks on command File\Set RACK_Pos (see next Figure 34).

Figure 34

Set F.A. RACK_Position Command

The panel: Set RACK_Position (Functional Address) is opened as shown in Figure 35


below. The user types the new rack positions and clicks on the button Replace All. All
data are replaced with the new ones.

Figure 35

Set RACK_Position (Functional Address) Dialog Box

Command: Set F.A. RACK_Pos;


Purpose: It replaces all rack positions.

A50016-G5100-A072-01-7619

Id:0900d805800e7a3b

35

Menu and Commands

OGL:IDF EVOLUTION

Remarks:
Set F.A. Rack Position command is enabled only for IDT and IDF file.
The user replaces all rack positions,in the Functional Address field of all S-records, with
the new Rack Position Number specified within the dialog box. The permitted value is a
digit from 0 to 9.
The total number of replaced objects is displayed after the successful commands execution.
When all data have been replaced, File\Save menu command and toolbar save button
are enabled.
The field Functional Address is the logical address of the inventory object and it consists
of name, rack position and module number, like for example the following:
FAN-0/1 with rack position=0 and module number = 1

4.1.1.8

Remove NOB RIUs Command


This command removes all redundant Nob_RIUs inventory data stored in the opened
IDT or IDF file (see next Figure 36 below). The algorithm processes the Functional
Address information.

Figure 36

Remove nob_RIUs Command

Command: Remove nob_RIUs;


Purpose: It removes all redundant nob_RIUs.
Remarks:
All nob_RIUs stored in the current opened file which have the same Functional Address
of an ob_RIU object, with format different from D, are removed.
This command is very useful because all inventory data imported from the logistic center
(RLC) are considered as nob_RIUs. So, the same device could be reported as ob_RIU
or as nob_RIU.
The total number of removed objects is displayed after the commands execution. In
case the original file is an IDF the footer record is automatically updated.

36

Id:0900d805800e7a3b

A50016-G5100-A072-01-7619

OGL:IDF EVOLUTION

4.1.1.9

Menu and Commands

Search Command
This command triggers a quick module search as represented in next Figure 37 below:

Figure 37

Search Command

Command: It permits a quick searching of Serial Number or Functional Address;


Purpose: It finds records in the opened file.
Remarks:
The search function is enabled for IDT, IDF and NOB files;
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


When the user clicks on SerialNumber button, the Search panel is opened as represented in Figure 38.
For example the user has the possibility to search those modules with Serial
Number like XIL/K3221159 or starting with XIL/K simply typing the serial number or
the initial part of serial number.

A50016-G5100-A072-01-7619

Id:0900d805800e7a3b

37

Menu and Commands

OGL:IDF EVOLUTION

Figure 38

Search Dialog Box

The Search panel has the following structure:


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 Evolution searchs 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
When the user clicks on Functional Address button, the Search panel is opened as
represented in next Figure 39. For example, the user has the opportunity to search
all modules, in the current opened file, with Functional Address CU-0/0.
The inserted value is the substring IDF Evolution has to look for in the Functional
Address fields.
The Search panel has the following structure:

Figure 39

38

Search Dialog box

Id:0900d805800e7a3b

A50016-G5100-A072-01-7619

OGL:IDF EVOLUTION

Menu and Commands

Find Next:
This button repeats the search up to the end of the file;
Cancel:
This button closes the panel.

4.1.1.10

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

Figure 40

Exit Command

Command: Exit;
Purpose: It closes the IDF Evolution application.
Remarks:
The user can select the Exit command anytime in order to suspend the program execution.
The Exit command closes the opened file. In case opened file has been modified, it is
automatically saved.

A50016-G5100-A072-01-7619

Id:0900d805800e7a3b

39

Menu and Commands

4.1.2

OGL:IDF EVOLUTION

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 next Figure 41).

Figure 41

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 next Figure 42.

Figure 42

C_IDF Export Command

Command: Export C_IDF;


Purpose: This command converts opened ZDT file is converted in C_IDF file format.
Remarks:
This command exports the opened file in Central IDF format together with an header and
footer record providing information about the format type, the creation time and the
number of records contained in the file.

40

Id:0900d805800e7a3b

A50016-G5100-A072-01-7619

OGL:IDF EVOLUTION

4.1.2.2

Menu and Commands

Export C_TXT Command


This command exports the currently opened file in Central TXT (C_TXT) format as represented in next Figure 43.

Figure 43

Export C_TXT Command

Command: Export C_TXT;


Purpose: Current file is converted in C_TXT format.

4.1.2.3

Export IDT Command


This command exports current opened file in IDT format. The user shall click on the
menu command Export\IDT or on the corresponding icon in the Tool Bar (see Figure
44).

Figure 44

Export IDT Command

Command: Export IDT;


Purpose: Conversion of an IDF file in IDT format.
Remarks:
This command displays the SaveFileAs dialog Box, which enables the user to specify
the filename of the exported file. Default filename is retrieved from Sales Unique Name.
An IDT file derives from the IDF file with the deletion of header and footer records.
The command is enabled only if an IDF file has been opened.

A50016-G5100-A072-01-7619

Id:0900d805800e7a3b

41

Menu and Commands

4.1.2.4

OGL:IDF EVOLUTION

Export IDF Command


This command exports an IDT file in IDF format. The user shall clicks on the menu
command Export\IDF or on the corresponding icon in the Tool Bar (as represented in
Figure 45).

Figure 45

Export IDF Command

Command: Export IDF


Purpose: Conversion of an IDT file in IDF format.
Remarks:
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 Sales
Unique Name.
An IDF file derives from an IDT file adding an header and footer record.
The 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, IDF Evolution creates the file.

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 corresponding icon in the Tool Bar (see the
Figure 46).

Figure 46

Export NOB Command

Command: Export NOB;


Purpose: Export of nob_RIUs data.

42

Id:0900d805800e7a3b

A50016-G5100-A072-01-7619

OGL:IDF EVOLUTION

Menu and Commands

Remarks:
This command exports nob_RIUs data of the current opened file.
The command is enabled for an IDT or an IDF file storing nob_RIUs and only if the
current opened file is saved. Besides it 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 Sales Unique Name.
If the file specified by pathname does not exist, IDF Evolution creates the file.
The user creates a copy of the exported file in an hidden directory, with a fixed filename,
visible only by the LMT Evolution during the NOB file download to the related Network
Element (BSC, BTS, TRAU).

4.1.3

View Menu
In this chapter the View menu is described in detail.

Figure 47

4.1.3.1

View Menu

All, nob_RIus, ob_RIUs commands


These commands permits view all records, only ob_RIUs records or only nob_RIUs
records of current opened file as represented in Figure 47 above.
Command: View\All, View\ob_RIUs or View\nob_RIUs;
Purpose: Visualize specific records of inventory data stored in opened file.
Remarks:
View menu is enabled for IDT, IDF and ZDT file. For a specific ZDT file, when the user
selects a different Network Element, from the root panel, the view selection is restored
to default value.
Inventory data (All, ob_RIUs or nob_RIUs) that match the filled conditions are displayed.
To distinguish the different type of the displayed records, nob_RIUs S-I records are displayed in bold, ob_RIUs S-I records with an error in PID contents are display in different
colors (see next Figure 48).
The user can choose between following alternatives:

All: It displays all records of current file;

A50016-G5100-A072-01-7619

Id:0900d805800e7a3b

43

Menu and Commands

OGL:IDF EVOLUTION

Figure 48

nob_RIUs: It displays, in the Inventory Panel, nob_RIUs records of currently opened


file. Nob_RIUs S-I records are displayed in bold as represented in Figure 49.

Figure 49

44

All Records view

View nob_RIUs records

Id:0900d805800e7a3b

A50016-G5100-A072-01-7619

OGL:IDF EVOLUTION

Menu and Commands

ob_RIUs: It displays only ob_RIUs records of the current opened file. Ob_RIUs Irecords with an error in PID contents are displayed in different colors as represented
in next Figure 50.

Figure 50

View only ob_RIU Records

View\Display N records, View\Display N-S records and View\Display N-S-I records


permits also user to expand/reduce the inventorys tree.

Display N records: the inventorys tree is reduced up to its root node;


Display N-S records: the inventorys tree is reduced up to display all records structure records of current file;
Display N-S-I records: this command expands the tree so that both structure and
inventory records are displayed.

A50016-G5100-A072-01-7619

Id:0900d805800e7a3b

45

Menu and Commands

4.1.4

OGL:IDF EVOLUTION

HW Table Menu
This menu contains commands that allow the user to modify nob-RIUs inventory data
as represented in Figure 51;

Figure 51

Hardware Table Menu

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

4.1.4.1

Insert Record Command


When the user selects the command HW Table\Insert record the Insert record panel represented in Figure 52 is opened.
The user shall fill the Network Element Type, the Functional Address, the Functional
Address Type and the Mounting Position field in the panel.

Figure 52

46

Insert Record panel

Id:0900d805800e7a3b

A50016-G5100-A072-01-7619

OGL:IDF EVOLUTION

Menu and Commands

When the user clicks on Insert button, nob_RIU filled data are inserted.The cancel
button deletes the operation.
NE Type:
The user selects the BSS Network Element (BSC, BTS, TRAU);
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 can create a new one by typing the new NEy Type name in the combo
box.
Functional Address:
The user fills the Functional Address of the nob_RIU the user wants to insert.
Functional Address Type:
The user fills the Functional Address Type of the nob_RIU the user wants to insert.
Mounting Position:
The user fills the second part of the mounting location.
Insert:
If all requirements are verified this button triggers the insertion of the record in the basic
nob_RIUs table of that Network Element.

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.

A50016-G5100-A072-01-7619

Id:0900d805800e7a3b

47

Menu and Commands

4.1.4.2

OGL:IDF EVOLUTION

Delete Record Command


When the user selects the command HW Table\ Delete record, the Delete record panel
is opened (see next Figure 53). The user can delete an existing nob_RIU object.
The user selects the Network Element Type, the Functional Address, the Functional
Address Type and the Mounting Position of the nob_RIU that shall be deleted.

Figure 53

Delete Record panel

The Delete Record panel is so structured:


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

all data shall be inserted;

Cancel Button:
This button closes the window without deleting filled nob_RIU.

48

Id:0900d805800e7a3b

A50016-G5100-A072-01-7619

OGL:IDF EVOLUTION

4.1.4.3

Menu and Commands

Modify Record Command


When the user selects the command HW Table\Modify record (or the Alt +M keyboards
command), the Modify record panel is opened. It is represented in next Figure 54.
By means of it, the user can modify an existing nob_RIU object.
The user selects the Network Element, the Functional Address, the Functional Address
Type and the Mounting Position of the nob_RIU that shall be modified.

Figure 54

Modify Record panel

By clicking on the Modify button, the user modifies the Functional Address, the Functional Address Type and the Mounting Position of the selected nob_RIU. The panel represented in Figure 55 above is displayed.

Figure 55

Modify Record panel

The panel has the following structure:

A50016-G5100-A072-01-7619

Id:0900d805800e7a3b

49

Menu and Commands

OGL:IDF EVOLUTION

Modify Data button:


If all the conditions are verified, when the user clicks on this button, IDF Evolution
modifies the record in the basic nob_RIUs table of that Network Element.
Cancel Button:
This button deletes the nob_RIU modifications and closes the panel.

4.1.5

Options Menu
This chapter describes the Options Menu.

Figure 56

4.1.5.1

Options Menu

Select On Click
This functionality (see next Figure 56) 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 ASCII window of IDF Evolution.
Remarks:
SelectOnClick function is enabled for IDT, IDF, NOB, ZDT files. 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 Figure 57
and Figure 58).

50

Figure 57

Select on Click Option Enabled

Figure 58

Select on Click Option Disabled

Id:0900d805800e7a3b

A50016-G5100-A072-01-7619

OGL:IDF EVOLUTION

4.1.5.2

Menu and Commands

Hide ASCII File window


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

The ASCII content window is hidden

Figure 59

Hidden ASCII window

Command: Hide ASCII file window.


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

A50016-G5100-A072-01-7619

Id:0900d805800e7a3b

51

Menu and Commands

4.1.5.3

OGL:IDF EVOLUTION

Look and Feel Command


This functionality (see next Figure 60) allows the user to choose the Java Look and
Feels that depend on JRE installed version and supported Operating System.

Figure 60

Look and Feel Command

Command: Look & Feel.


Purpose: It changes IDF Evolution look and feel.

g It is recommended to select look and feel and then restart IDF Evolution in order to
have all application windows correctly displayed.

4.1.5.4

Switch Application Command


This command chooses the technology (GSM/UMTS) to which IDF Evolution belongs to
as represented in Figure 61.

Figure 61

Switch Command

g Switch Application command has currently no effect on GSM/UMTS application.

52

Id:0900d805800e7a3b

A50016-G5100-A072-01-7619

OGL:IDF EVOLUTION

4.1.6

Menu and Commands

Tools Menu
In this chapter the Tools menu and its commands are described.

Figure 62

4.1.6.1

Tools Menu

Set Scanner Port Command


The Set scanner port tool provides the configuration of the serial port to which the 2D
Label scanner is connected. When the user clicks on the Set Scanner port button, the
Communication scanner port dialog box is opened. It displays eight selectable ports: the
first fours are available only with Windows OS, while the last fours can be selected if the
supported OS is Solaris (see the Figure 63).

Figure 63

Communication Scanner Port Dialog Box

The Set button provides the configuration of the selected port. The Cancel Button closes
the dialog box.

Caution - Communication Port


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 case a wrong port is selected, the IDF Evolution displays an error
dialog box, while trying to get data, suggesting to change the port settings as represented in the Figure 64.

A50016-G5100-A072-01-7619

Id:0900d805800e7a3b

53

Menu and Commands

OGL:IDF EVOLUTION

Figure 64

4.1.7

Error dialog box

Help Menu
An On-line help is provided with the following buttons, as represented in next Figure 65:

Help Contents;
About IDF Evolution.

Figure 65

4.1.7.1

Help Menu

Help Contents Command


The Help Contents command supports the user in searching specific functionalities.
When the user clicks on it the Help panel is opened as represented in next Figure 66.
This panel provides the following facilities:

54

Table of Contents;
Index (not available in current release);
Search;
Favorites.

Id:0900d805800e7a3b

A50016-G5100-A072-01-7619

OGL:IDF EVOLUTION

Menu and Commands

Figure 66

4.1.7.2

Help window

About IDF Evolution Command


This command opens the About IDF Evolution window that visualizes the IDF Evolution
SW Version as represented in next Figure 67.

Figure 67

A50016-G5100-A072-01-7619

About IDF Evolution window

Id:0900d805800e7a3b

55

Menu and Commands

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


There is only one available pop up as represented in next Figure 68:

4.2.1.1

Create.

Create
This command provides user the possibility to insert a new nob_RIU in the inventory
panel of the current opened file. The user clicks on the right mouse button on the Nrecord (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.

Figure 68

Create command

Command: Create
Purpose: It creates a nob_RIU.
The user can create only nob_RIUs objects. 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:
When the user clicks on Create button, the New NOB_RIU panel is opened. Its purpose
is to make easier 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 next Figure 69.

56

Id:0900d805800e7a3b

A50016-G5100-A072-01-7619

OGL:IDF EVOLUTION

Menu and Commands

Figure 69

New NOB_RIU panel

By clicking the Inventory button the panel represented in Figure 70 is opened. The user
can insert all requested inventory data.
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).

Figure 70

Panel for inserting the requested inventory data

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


Scan:
This button permits the user to insert the FW Code, the HW Code and the Serial Number
using the 2D-Code_Reader device.

A50016-G5100-A072-01-7619

Id:0900d805800e7a3b

57

Menu and Commands

OGL:IDF EVOLUTION

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:

4.2.2.1

Delete a S-I record;


Edit an I record.

Delete
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 shown in the Figure 71 below.

Figure 71

Delete command

Command: Delete;
Purpose: It deletes a nob_RIU object.
Remarks:

The delete command is enabled only for IDT, IDF NOB files;
The user can delete only an existing nob_RIU object;
The IDF 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.

58

Id:0900d805800e7a3b

A50016-G5100-A072-01-7619

OGL:IDF EVOLUTION

4.2.2.2

Menu and Commands

Edit
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 next Figure 72.

Figure 72

Edit command

Command: Edit
Purpose: It modifies a nob_RIU Inventory record.
Remarks:

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.
To edit the Inventory data of an existing board, the panel shown in Figure 73 is opened
when the user clicks on the Edit button. The Item Number (FW, HW) field is enabled only
for the Network Element that supports PID format 11.

Figure 73

Edit Panel

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

A50016-G5100-A072-01-7619

Id:0900d805800e7a3b

59

Menu and Commands

OGL:IDF EVOLUTION

Scan:
It permits 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 data entry is made easier by means of a 2D Code Reader device that is supported
by IDF Evolution.
Data entry is necessary when:

A new nob_RIU shall be inserted;


An existing nob_RIU shall be modified;
An existing nob_RIU board shall be searched.

When data input for 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 information.
The 2D Code Reader used in the BSS system is the METHANETICS CORPORATION
IR-2000.

4.3.1

METHANETICS CORPORATION IR-2000


In this chapter a short description of the Methanetics Corporation IR-2000 is provided.

4.3.1.1

Hardware Setting
The application runs only if the IR-2000HD imaging reader parameters are set to their
default values.
The default values are specified 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

Table 3

60

Default parameters for IR-2000HD

Id:0900d805800e7a3b

A50016-G5100-A072-01-7619

OGL:IDF EVOLUTION

Menu and Commands

Decode Options
Carriage Return/Line Feed Disabled
Decode Mode

Multiple

Illumination

Enabled

Prefix/Suffix

Disabled

Reverse Constant(1D)

Disabled

Targeting

On Demand

Table 4

4.3.1.2

Decode Options for the IR-2000HD

Using 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):
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 next Figure 74 below:

Figure 74

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 successfully 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).

A50016-G5100-A072-01-7619

Id:0900d805800e7a3b

61

Inventory Data Management

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 operation executed by 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 Evolution.
2. Select the open menu and select the file to be opened (for example: the default
directory c:\Siemens\111_xx_yy\Upload is offered) as represented in next Figure
75.

Figure 75

5.1.1
5.1.1.1

Open selected File

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 Figure 76.

62

Id:0900d805800e7db5

A50016-G5100-A072-01-7619

OGL:IDF EVOLUTION

Inventory Data Management

Figure 76

Insert a New Nob_RIU - Step 1

2. Select module to be added as represented in Figure 77.

Figure 77

Insert a New Nob_RIU - Step 2

3. Set SBS_Equipment_Position and click on the inventory button. See Figure 78.

Figure 78

A50016-G5100-A072-01-7619

Insert a New Nob_RIU - Step 3

Id:0900d805800e7db5

63

Inventory Data Management

OGL:IDF EVOLUTION

4. Insert inventory data as shown in Figure 79.

Figure 79

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 makes data input error free and fast.

Figure 80

2D-Code Reader

The panel represented in Figure 81 is opened 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).

64

Id:0900d805800e7db5

A50016-G5100-A072-01-7619

OGL:IDF EVOLUTION

Inventory Data Management

Figure 81

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 as represented in next Figure 82.

Figure 82

Replacement of a Nob_RIU - Step 1

2. Edit inventory data.

A50016-G5100-A072-01-7619

Id:0900d805800e7db5

65

Inventory Data Management

OGL:IDF EVOLUTION

Figure 83

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 makes data input error free and fast.
The panel in Figure 81 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 next Figure 84.

Figure 84

66

Nob_RIU deletion - Step 1

Id:0900d805800e7db5

A50016-G5100-A072-01-7619

OGL:IDF EVOLUTION

Inventory Data Management

2. Confirm the deletion operation.

Figure 85

5.1.2
5.1.2.1

Confirmation of the deletion operation

IDF File imported from RLC


Logistics: Inventory Data Delivered by RLC to the Project
The RLC Logistic Center provides the following inventory files on a per rack basis represented in next Figure 86.

Figure 86

IDFs Delivered with the BTS Equipment

One floppy disk is provided for every rack; it includes an inventory data file that contains
all ob/nob-RIUs defined for that rack.
All data are reported in the format "11".
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".

A50016-G5100-A072-01-7619

Id:0900d805800e7db5

67

Inventory Data Management

OGL:IDF EVOLUTION

In addition, the Logistic Center prepares the inventory data of the network entity by
downloading the correct data as described in the next chapters. This is possible for all
the Network Elements which consist only of one rack (for example: BS-2x/6x, BSC,
TRAU).
For the rack extensions of BS-240/241 line this is not possible due to the missing core
module (COBA).
Nevertheless this additional service must be negotiated with the Logistic Centre.
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

Table 5

Example of IDF filenames received from RLC

The following table shows the Inventory Data File delivered for the BS-60 (The Output
is structured for a better reading).
Filename: RX+_L2888888.IDF
HREMOTE INVENTORYV1.01

SRI 3.0 08.02.199913:07:15

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

Table 6

68

S30861-D11-X1-05/01

FUSEPANEL

RO+/JN12960
7

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-X20005/01

M:RXAMCOG

RO+/JO12907
8

S30861-Q303-X20005/01

M:RXAMCOG

RO+/JO12909
1

S30861-Q303-X20006/01

M:RXAMCOG

RO+/JO12905
7

Example of IDF file delivered with a BS-60 equipment

Id:0900d805800e7db5

A50016-G5100-A072-01-7619

OGL:IDF EVOLUTION

Inventory Data Management

IM0101010102 B011

M11

S30861-Q303-X20005/01

M:RXAMCOG

RO+/JO12909
0

SM01RXAMCO-0/4

M:RXAMCOG

IM0101010102 C008

M11

S30861-Q303-X20005/01

M:RXAMCOG

RO+/JO12908
4

SM01RXAMCO-0/5

M:RXAMCOG

IM0101010102 C009

M11

S30861-Q303-X20006/02

M:RXAMCOG

RO+/JO12906
3

SM01PA-0/0

HPAG

IM0101010108 C105

M11

S30861-U528-X-02/02

HPAG

BM+/JO55430
4

SM01TPU-0/0

TPU2G

IM0101010108 C128

M11

S30861-U524-X-06/03

TPU2G

RO+/J7213417

SM01PA-0/1

HPAG

IM0101010108 C141

M11

S30861-U528-X-02/02

HPAG

BM+/JO55155
2

SM01TPU-0/1

TPU2G

IM0101010108 C164

M11

S30861-U524-X-06/03

TPU2G

RO+/J7213427

SM01PA-0/2

HPAG

IM0101010108 C177

M11

S30861-U528-X-02/02

HPAG

BM+/JO55352
2

SM01TPU-0/2

TPU2G

IM0101010108 C200

M11

S30861-U524-X-06/03

TPU2G

RO+/J7213751

SM01FAN-0/2

FAN

IM0101010108 E101

M11

S30861-U426-X-05/01

FAN

CF+/JD123798

SM01DCPA-0/0

M:DCPA

IM0101010108 F103

M11

S30861-Q392-X-08/01

M:DCPA

RO+/J8152091

SM01DCTPU-0/0

M:DCTPU

IM0101010108 F119

M11

S30861-Q348-X-C2/01

M:DCTPU

CF+/JN143256

SM01DCPA-0/1

M:DCPA

IM0101010108 F133

M11

S30861-Q392-X-08/01

M:DCPA

RO+/J8152087

SM01DCTPU-0/1

M:DCTPU

IM0101010108 F149

M11

S30861-Q348-X-C2/01

M:DCTPU

CF+/JN143255

SM01DCPA-0/2

M:DCPA

IM0101010108 F163

M11

S30861-Q392-X-08/01

M:DCPA

RO+/J8152086

SM01DCTPU-0/2

M:DCTPU

IM0101010108 F179

M11

S30861-Q348-X-C2/01

M:DCTPU

CF+/JN143250

SM01FAN-0/1

FAN

IM0101010108 G 101

M11

S30861-U426-X-05/01

FAN

M11 S30861Q330-X101-03/01

S30861-Q330-X100B1/02

M:BBSIG44

SM01BBSIG-0/0
IM0101010108 H103

Table 6

A50016-G5100-A072-01-7619

CF+/J9109375

Example of IDF file delivered with a BS-60 equipment

Id:0900d805800e7db5

69

Inventory Data Management

OGL:IDF EVOLUTION

SM01BBSIG-0/1

M:BBSIG44

IM0101010108 H117

M11 S30861Q330-X101-03/01

SM01BBSIG-0/2

M:BBSIG44

IM0101010108 H131

M11 S30861Q330-X101-03/01

SM01MCLK-0/0

M:MCLK

IM0101010108 H187

M11 S30861Q331-X1-7/01

SM01CCTRL-0/0

M:CCTRL

IM0101010108 H211

M11 S30861Q332-X1-9/02

SM01LI-0/0

M:LI

IM0101010108 H235

M11 S30861Q337-X101-2/01

SM01ALCO-0/0

M:ALCO

IM0101010108 H259

M11 S30861Q300-X101-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

S30861-Q330-X100B1/02

M:BBSIG44

CF+/J9109580

S30861-Q330-X100B1/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+/K320164
8

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+/KO13894
2

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

FN:00001S:00036I:00036END OF IDF

Table 6

Example of IDF file delivered with a BS-60 equipment

Since the Radio Logistic Centre might not know the following information:

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 the final commissioning in field with the support of IDF Edtor Evolution.
It this case the following default values shall be considered:
SalesUniqueName

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


e.g. RX+L2888888

SBS_Equipment_Position
Table 7

70

"010101"

e.g. 01010102B004

Default Values within IDF

Id:0900d805800e7db5

A50016-G5100-A072-01-7619

OGL:IDF EVOLUTION

Inventory Data Management

Rack position within Functional


Address
Table 7

"0"

e.g. FAN-0/2

Default Values within IDF

Note 2:
Since the IDFs delivered from 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 specific IDF Evolution function 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". All
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 fill 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 file that shall be downloaded to the
Network Element at the end of all the elaborations.
There are two scenarios possible:

A new Network Element is to be installed;


A rack extension is to be installed.

The steps to be performed are in principle the same. The installation 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 described process is an example of the installation of a new BTS BS-240 configured
with one base, one extension and one service rack.
Action requested:
1.
2.
3.
4.
5.
6.
7.
8.
9.

Start IDF Evolution;


Select and Open IDF file;
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 Evolution;
11. Download the NOB file to the Network Element from LMT Evolution.
Each action is described in detail as follow:
1. Start IDF Evolution;

A50016-G5100-A072-01-7619

Id:0900d805800e7db5

71

Inventory Data Management

OGL:IDF EVOLUTION

Figure 87

72

Put Inventory Data into N.E. - Step 1

Id:0900d805800e7db5

A50016-G5100-A072-01-7619

OGL:IDF EVOLUTION

Inventory Data Management

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

Figure 88
2.1

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


offered)

Figure 89

A50016-G5100-A072-01-7619

Put Inventory Data into N.E. - Step 2

Put Inventory Data into N.E. - Step 2.1

Id:0900d805800e7db5

73

Inventory Data Management

OGL:IDF EVOLUTION

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

74

Figure 90

Put Inventory Data into N.E. - Step 3

Figure 91

Put Inventory Data into N.E. - Step 3.1

Figure 92

Put Inventory Data into N.E. - Step 3.2

Id:0900d805800e7db5

A50016-G5100-A072-01-7619

OGL:IDF EVOLUTION

Inventory Data Management

4. Replace all rack positions of Functional Addresses:

Figure 93

Put Inventory Data into N.E. - Step 4

Figure 94

Put Inventory Data into N.E. - Step 4.1

Figure 95

Put Inventory Data into N.E. - Step 4.2

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

A50016-G5100-A072-01-7619

Id:0900d805800e7db5

75

Inventory Data Management

OGL:IDF EVOLUTION

Figure 96

Error Message for Saving File

g 2. After saving the following message is shown:

Figure 97

Confirmation of File Saved

5. Export NOB file:

Figure 98

76

Put Inventory Data into N.E. - Step 5

Id:0900d805800e7db5

A50016-G5100-A072-01-7619

OGL:IDF EVOLUTION

Inventory Data Management

Figure 99

Put Inventory Data into N.E. - Step 5.1

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


name is <salesuniquename>.nob.

Figure 100 Confirmation of NOB File Saved

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

A50016-G5100-A072-01-7619

Id:0900d805800e7db5

77

Inventory Data Management

OGL:IDF EVOLUTION

Figure 101 Alert Message for Exporting File

78

Id:0900d805800e7db5

A50016-G5100-A072-01-7619

OGL:IDF EVOLUTION

Inventory Data Management

6. Upload the IDT file from the LMT Evolution:

Figure 102 Put Inventory Data into N.E. - Step 6

g 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

A50016-G5100-A072-01-7619

Id:0900d805800e7db5

79

Inventory Data Management

OGL:IDF EVOLUTION

7. Select and Open the uploaded IDT file:

Figure 103 Put Inventory Data into N.E. - Step 7

Figure 104 Put Inventory Data into N.E. - Step 7.1

80

Id:0900d805800e7db5

A50016-G5100-A072-01-7619

OGL:IDF EVOLUTION

Inventory Data Management

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

Figure 105 Put Inventory Data into N.E. - Step 8

Figure 106 Put Inventory Data into N.E. - Step 8.1

A50016-G5100-A072-01-7619

Id:0900d805800e7db5

81

Inventory Data Management

OGL:IDF EVOLUTION

Figure 107 Put Inventory Data into N.E. - Step 8.2


9. Remove all the eventual redundant nob_RIUs:

Figure 108 Put Inventory Data into N.E. - Step 9

Figure 109 Ask for Removing all Redundant nob_RIU

82

Id:0900d805800e7db5

A50016-G5100-A072-01-7619

OGL:IDF EVOLUTION

Inventory Data Management

Figure 110 Confirmation of Deletion

9.1

Save the file:

Figure 111 Put Inventory Data into N.E. - Step 9.1


9.2

A50016-G5100-A072-01-7619

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


file name is <salesuniquename>.nob):

Id:0900d805800e7db5

83

Inventory Data Management

OGL:IDF EVOLUTION

Figure 112 Put Inventory Data into N.E. - Step 9.2


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):

Figure 113 Put Inventory Data into N.E. - Step 9.3

84

Id:0900d805800e7db5

A50016-G5100-A072-01-7619

OGL:IDF EVOLUTION

Inventory Data Management

10. Close the IDF Evolution:

Figure 114 Put Inventory Data into N.E.- Step 10

A50016-G5100-A072-01-7619

Id:0900d805800e7db5

85

Inventory Data Management

OGL:IDF EVOLUTION

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

Figure 115 Put Inventory Data into N.E. - Step 11

86

Id:0900d805800e7db5

A50016-G5100-A072-01-7619

OGL:IDF EVOLUTION

Inventory Data Management

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

Editor

5) Export nob_RIU file

LMT

Another rack to be added


?

YES

IDF

b
LMT

NO

2) Open IDF of next rack


e.g. CN+_JD100002.IDF

Figure 116 Pre-Processing of IDFs of Delivered Racks

g The replacement of all 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 automatically 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.

A50016-G5100-A072-01-7619

Id:0900d805800e7db5

87

Inventory Data Management

OGL:IDF EVOLUTION

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

7) Open IDT

LMT

IDF

Editor

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

Figure 117 Import of modified nob_RIU in the IDF file

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

Figure 118 Download of the modified nob_RIU File to the related Network Element

88

Id:0900d805800e7db5

A50016-G5100-A072-01-7619

OGL:IDF EVOLUTION

Inventory Data Management

A rack shall be extended:


The process to add a new rack to an existing one is a subset of the process already
described.
The configuration of "SBS_Equipment_Position" and "SalesUniqueName" is not necessary for the installation of a new rack, for the reason that this information is 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 must be installed:
If a new device must be installed,it is necessary to consider two different cases:
- The device is implemented as an ob_RIU (for example the EDGE Carrrier Unit 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 device. 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 Evolution;
- Open the IDT file from the IDF 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 Evolution.
- Download the NOB file to the Network Element form the LMT Evolution.

A50016-G5100-A072-01-7619

Id:0900d805800e7db5

89

Inventory Data Management

OGL:IDF EVOLUTION

A device (for example a Carrier Unit) shall be replaced:


If a device (for example a Carrier Unit or a FAN) shall be replaced the following two
cases shall be considered:
- 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 Editor Evolution.
- Start the IDF Evolution;
- Open the IDT file;
- Edit the I-Record and replace the inventory data.
- Export the file as a NOB file;
- Store the NOB file in a local directory accessible also from the LMT Evolution;
- Close the IDF Evolution;
- Download the NOB file to the Network Element from the LMT Evolution.

90

Id:0900d805800e7db5

A50016-G5100-A072-01-7619

OGL:IDF EVOLUTION

5.1.3

Inventory Data Management

Export IDF File for Backup


1. Export the IDF file for backup and forward it to the inventory system as represented
in next Figure 119.

Figure 119 Export IDF File for backup purpose - Step 1


2. Select the file name (the default directory is : C:\Siemens\IDF111_xx_ yy\Upload.
The default file name is: <salesuniquename>.idf - see the Figure 120.

Figure 120 Export the IDF File - Step 2

A50016-G5100-A072-01-7619

Id:0900d805800e7db5

91

Inventory Data Management

OGL:IDF EVOLUTION

3. Ack message:

Figure 121 Export IDF File - Step 3

5.1.4

Export NOB for Downloading to the Network Element


1. Export NOB as shown in Figure 122 below:

Figure 122 Export NOB - Step 1

92

Id:0900d805800e7db5

A50016-G5100-A072-01-7619

OGL:IDF EVOLUTION

Inventory Data Management

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

Figure 123 Export NOB - Step 2


3. Confirmation of NOB file creation:

Figure 124 Export NOB - Step 3


4. Ack message:

Figure 125 Export NOB - Step 4

A50016-G5100-A072-01-7619

Id:0900d805800e7db5

93