Download Agileto Help

Agileto_Help_V1.53.docx
The purposes/usage/meaning of these folders and their associated files are presented
below, as following:
Audit_SanityCheck -> directory where the tool is storing the reports and the output
files after the 3G/2G Audit & „Sanity Check‟ is performed (M2.1 outputs);
Ex: OMC_ATT_20110325 -> it is an output directory generated by the tool
(with the module M2.1) by using as input the OMC 3G snapshot file
OMC_ATT_20110325.xml.
Call_Traces -> directory related to the network optimization (3G-3G/3G-2G
neighbors analysis/proposals -> M4.2 & M4.3) based on Call Traces containing:
CT_files -> directory where it is recommended to be stored the Call Traces
(*.xml/*.tab) files/directories [Input data for M4.2];
CT_Optimisation -> directory where the tool is storing the output reports for
the network optimization based on Call Traces (M4.2 outputs);
CT_PSC_Det -> directory where it is recommended to be stored the Call
Traces (*.txt file) containing PSC detected [Input data for M4.3];
CT_PSC_Det_Optim -> directory where the tool is storing the output reports
for the neighbors optimization based on PSCs detected (M4.3 outputs);
Drive_Tests -> directory related to the network optimization based on the Drive
Tests (module M4.1); this directory contains two subdirectories, one for inputs
(DT_Measurements) and another-one for outputs (DT_Optimisation), as following:
DT_Measurements -> directory where it is recommended to be stored the
Drive Tests (scanner/mobile) measurements data files [Input data for M4.1];
DT_Optimisation -> directory where the tool is storing the output reports for
the network/neighbors optimization based on the Drive Tests (M4.1 outputs);
GoogleEarth -> directory related to the representation in Google Earth formats of
different outputs like 3G & 2G mobile networks, Drive Test outputs, 3G->3G + 3G>2G + 2G->2G Neighbors, etc:
2G -> directory where the tool is storing in GoogleEarth formats the 2G Sites
& 2G Cells files (automatically generated & stored here by M1.2 & M5.1);
3G -> directory where the tool is storing in GoogleEarth formats the 3G Sites
& 3G Cells files (automatically generated & stored here by M1.2 & M5.1);
Drive_Tests -> directory where the tool is storing the output results of the
Drive Test Analysis/Optimisation generated in Google Earth format (M4.1);
Neigh_GE -> directory where the tool is storing the neighbors generated in
Google Earth format by different modules (M3.1, M3.2, M4.1, M4.2);
KPIs -> directory related to the module M5.1 -> this is a directory where it is
recommended to store all the KPIs files as inputs for the M5.1 (Generate MapInfo &
GoogleEarth cells/sites objects based on KPIs values);
MapInfo -> directory related to the representation in MapInfo of the 3G & 2G
mobile networks + their associated 3G->3G & 3G->2G Neighbors:
2G -> directory where the tool is storing the 2G MapInfo Sites & Cells tables
(automatically generated & stored here by M1.2 & M5.1);
3G -> directory where the tool is storing the 3G MapInfo Sites & Cells tables
(automatically generated & stored here by M1.2 & M5.1);
Page 25 of 183
www.agileto.com