8.55 62.138
1) Update Nokia 4G parser as following:
   a) Solve the special cases (which may lead to errors) when the 4G Cells and Neighbors declarations (source) are not datafilled continously [all Cells declared @ same eNB OR all Neighbors declared @ same Source Cell);
   b) In order to maintain continuity, (re)build internally the database related to eNodeB_Ids from the values detected into 4G Cells database in case that the related eNodeBs have not been already exported into the snapshot file;

8.54 62.137
1) Once the SILENT MODE session is finished properly, display the content of the SILENT MODE results file into a dedicated window for sveral seconds;;
2) Update the parameters/syntax for M1.2 () while working in SILENT MODE, as following:
   => By default we have "0" values for P6,P9,P12,P15 => All cells are represented with the same color corresponding to its Technology and frequency layer;
   => For more details please see the last version of the RunSilent_Syntax.xls [V1.19] -> http://www.agileto.com/pro/RunSilent_Syntax.zip
3) Update the parser for Huawei 3G in order top extract the 3G Cells LAC info for the Remote Cells declaration + several other 'bug solver' improvements;

8.52 62.135
1) Add a new option (button) in order to execute the 'SILENT MODE' from Agileto's interface, additionally to the MS DOS command line;
2) Upgrade the 'SILENT MODE' by updating the syntax for all the modules (already supported) in order to accommodate the 5G technology, too;
   => For more details please check the new file RunSilent_Syntax.xls available @ http://www.agileto.com/pro/RunSilent_Syntax.zip
3) Add more options available when detecting another (previous) Agileto instance is already running during the lunch time;
4) 'Upgrade M4.1 (Network Optimisation based on Drive Tests) & 5.1 (Map Cells KPIs into MapInfo and GoogleEarth) as following:
   => Modify the structure of the output Google Earth generated files in order to get full compatibility (including the legends) even when these files are transfered/copy on another PC;
5) When providing the external Neighbors file (*.csv) as input, modify the standard strings allocated for the Neighbors Cells according with the technology having the prefixes "source" and "target" included, as following:
   => Remember that per Technology each Cell is unique identified over the entire network by the following 2 info:
   2G: LAC + CId
   3G: RncId + CId
   4G: eNBId + CId
   5G: gNBId + CId
   => The neighbors declaration file should have included into its header the following (4) standard strings, as per the examples below:
      a) 5G-5G: "sourcegNBId" , "sourceCId" , "targetgNBId" , "targetCId" 
      b) 4G-3G: "sourceeNBId" , "sourceCId" , "targetRncId" , "targetCId"
      c) 3G-2G: "sourceRncId" , "sourceCId" , "targetLAC" , "targetCId"

8.45 62.126
1) Fix a bug/limitation in order to accomodate 4G + 5G DL_ARFCN numbers which may overpass the maximum integer number [32767];

8.45 62.125 => MILESTONE REACHED!
1) Replace Agileto PRO Edition logo [2G-3G-4G] with [Mobile NW] which means it supports now all types of the Mobile Networks [2G/3G/4G/5G];
2) Update Neighbors mapping in GE => both M3.1 (OMC dump file[s] to -> MapInfo + GoogleEarth) + M3.2 (Neighbors -> MapInfo & Google Earth) by a common routine, as following:
   2.1) Per Source Cell:
      A: Update/correct the "Summary" neighbors info per source Cell by including as well the Cells which are not detected into Agileto database (ex: cases where the cells are detected only into OMC snapshot);
      B: Include into GE Neighbors left pannel ALL the Target Neighbors Cells including those which do not have Geographically coordinates [as folder & description] with short summary info about the Neighbor target Cell;
   2.2) Per Target Cell:
      C: Include the Cell Target Freq Layer Number [ARFCN] into the Cell Target "summary" info;

8.42 62.123
1) Update M3.2 (Neighbors -> MapInfo & Google Earth) to support 5G Technology, too.
   => It was improved M3.1 (OMC dump file[s] to -> MapInfo + GoogleEarth [neighbors converter]) too, as following:
   In Google Earth are displayed only the Source Cells which have Neighbors declarations AND at least one neighbor has valid coordinates in Agileto database;

8.42 62.122
1) Update M1.3 (NW boundary -> Border Cells evaluation 2G/3G/4G/5G) to support 5G Technology, too.
2) Update M2.2 (3G(PSCs) / 4G(PCIs) / 5G(PCIs) allocation -> Audit + Optimisation) to support 5G Technology, too.

8.42 61.220
1) Add into Agileto database for each Technology [3G/4G/5G] the New info representing the Total number of frequencies detected (which are presented into the last database Cell comment that contains all the frequencies DL ARFCN detected);
2) Update M1.2 (Generate NW cells/sites objects in MI + GE) as following:
   => Add 2 New options which allow the user to select if M1.2 is executing Goole Earth mapping of the following two sections, too:
      1) Border Cells (related to M1.3)
      2) BCCH/PSC/PCI(4G/5G) Allocation and Conflict (related to M2.2 and M2.3)
3) Update M5.1 (Map Cells KPIs into MapInfo and GoogleEarth) as following:
   3.1) Display now the KPIs values in Google Earth near the edge of the Cells radius (which may be variable) rather then to the standard fix Cells radius like it was before;
   3.2) Beside the Cell_Name option, accept as IDs inputs for the Keys Cells reference 2 parameters for all Technologies, as following:
        2G: LAC + CId   'Existing
        3G: RncId + CId 'NEW
        4G: eNBId + CId 'NEW
        5G: gNBId + CId 'NEW
      => By using these new options the following advantages are obtained:
      a) Total Processing time is significant decreased comparing with the Cell_Name option (very important when dealing with large networks);
      b) The Reference Keys presented above are already present into different KPIs reports provided by all operators/vendors tools and do not require additionally manipulations;

8.41 61.216
1) Update M1.2 (Generate NW cells/sites objects in MI + GE) in order to support 5G Technology, too;
2) Update M5.1 (Map Cells KPIs into MapInfo and GoogleEarth) in order to support 5G Technology, too;

8.41 61.214
1) Update M1.1 (Generate and update Agileto's database), as following:
   => Support now Agileto database creation/update for 5G technology too, from External Excel file;
   (New!) 5G Technology tab is now available to select and import the desired 5G data;
2) Update Agileto (Excel) database template file to version [2.1];

8.40 58.210 => MILESTONE REACHED!
1) Start the foundation and support for the 5G Technology:
   => New Agileto Mobile Network database template file [version 2.0] is now provided and auto-updated via internet, with support for the 5G Technology!
2) Update M1.1 (Generate and update Agileto's database), as following:
   => Prepare and accept the new Agileto template database file [version 2.0], by keeping the backward compatibility with 2G/3G/4G;

8.34 58.208
1) Update Agileto parser for NOKIA (2G & 3G) OSS export dump files, as following:
   => Extract additionally the Cell Names + LAC of the Target 2G2G & 3G3G & 3G2G Neighbors declarations; This leads to get into Agileto database and output reports the real 2G & 3G Cell Names + LAC even for the External (2G & 3G) Cells Declarations;
2) Update M2.1 (Audit & Sanity check) for 2G & 3G Technologies, as following:
   Perform advance checking for each (2G2G/3G3G/3G2G) Target Cell neighbors basic parameters and the discrepancies detectected are notified for correction in:
   1.a) Into the summary Audit & Sanity Check file (*.xls) at the end of the row data, presenting the total number of discrepancies detected for each Technology,
   1.b) Into the neighbors output files (*.csv) presenting the Target parameter neighbor dicrepancy detected into new columns [Current versus Expected], as following:
        2G -> "ParamT Discr: bcch/ncc/bcc"
        3G -> "ParamT Discr: UARFCN/PSC/LAC"

8.34 58.205
1) Update the parser for Huawei 2G dumps exported via Nokia OSS (NetAct):
   => Add support for Huawei RAN BSC6910, too;
   
8.34 58.204
1) Update M2.1 (Audit & Sanity check) as following:
   => For 2G Technology, update the output 2G2G neighbors declaration file (*.csv) with a new column (ParamT Discr: bcch/ncc/bcc) which emphasize all the neighbors declarations detected in discrepancy between the 2G Target cells concerning the info: bcch/ncc/bcc;
   => Additionally, for the purpose of warning that at least one such of case is detected, the total number of 2G2G neighbors detected in discrepancy will by now available & presented at the end into the final Audit & Sanity Check Excel file (*.xls);
2) Update the parser for Nokia OSS 2G export dump files:
   => To overcome the irregular way how the neighbors are declared into the dump file (when they are not declared continuously) and to avoid missinterpretations on the final results and the neighbors mapping on Google Earth too, proceed to sort always the 2G2G Neighbors declarations based on the same Source Cell (which will be reflected into the M2.1 outputs, too);

8.34 58.202
1) Update Nokia 2G dump parser by taking into account the new option about how the BCCH channel is marked between multiple TRXs available on the same cell/sector ("MBCCHC" in addition to "MBCCH")

8.34 58.201
1) Correct a bug in order to ensure compatibility with the old Agileto PRO Edition users + the new users moving from the obsolete Agileto GOLD Edition to the new Agileto PRO Edition;

8.33 58.199
1) Upgrade M3.2 (Neighbors/HandOvers -> MapInfo & Google Earth) interface by adding a new 'flag' option, as per mentioned below:
   => Add the new input 'flag' related to the Nb/HO declarations, as to be continuously reported - or NOT (randomly) - to the same Source Cell;
   If the user sets the input 'flag' Nb/HO as NOT declared continuously to the same Source Cell, that means the input data Nb/HO were exported randomly into the *.csv file, therefore a sorting operation is performed initially by Agileto tool based on the Source Cell reference data in order to get the Nb/HO declarations continuously reported to the same Source Cell;

8.33 58.197
1) Upgrade M3.2 (Neighbors/HandOvers -> MapInfo & Google Earth) interface to accept as alternative inputs the OMC HandOver (HO) counters, too.
   OMC HO inputs are:
      1) HO Success (Mandatory)
      2) HO Attempts (Optional)
      3) Neighbors (Nb) Reference file (Optional)
   OMC HO outputs are:
      1) Google Earth HO lines for each reference Cell toward the target Cells presenting [divided into IntraFreq/InterFreq/InterRAT]:
         A) HO Success + Failure weight [%] among all the target Cells
         B) HO Success + Failure rates
         Obs: If Neighbors (Nb) Reference file is provided as input then the HO and Nb comparison is performed and:
         C) HO not detected in Nb -> are presented in Red color (Nb missing);
         D) Nb not detected in HO -> are presented in Black color (Nb redundant);
      2) OMC HO (*.csv) updated files including the info presented at the point 1) above;

8.33 58.194
1) Update M3.1 (OMC dump file[s] to -> MapInfo + GoogleEarth [neighbors converter]) to get properly executed in Silent Mode as an M2.1's option (read as appropriate the Reference Cells' Radius & Delta).
2) Update Agileto algorithms which get the 3G/4G Cells' frequency layers from the OMC input files to overcome an error which may occur in case that 3G/4G Cells frequencies - by mistake - are NOT declared properly (="0") into OMC input files;

8.33 58.192
1) Update M3.2 (Neighbors database -> MapInfo & Google Earth) and prepare its foundation in order to accept as input Handover counters, too;

8.33 58.191
1) Insert additionally references into the OMC 4G processing data algorithm (focused on 2G External Cells) to help identifying the location into the module where an error may occur;

8.33 58.190
1) Update Agileto OMC 4G processing data algorithm by removing from the Final set of 2G/3G/4G Cells the following external (fake) Cells declared @ OMC by mistake:
   2G: CId=0 + LAC=0
   3G: RncId=0
   4G: eNodeBId=0
2) Update the algorithm which read Agileto database 2G/3G/4G in order to "reset" properly the variables which trigger the way how the data is loaded;

8.33 58.188
1) Update M2.1 (Audit & Sanity check) for all technologies (2G/3G/4G) as following:
   If on the same Agileto session the module M2.1 is executed multiple times on the same technology (2G/3G/4G) for different OMC input files, there are evaluated the reciprocity neighbors declarations between the Reference (previous) & Current OMC inputs;
   => This case the following Neighbors summary info [for both Ref + Crt] are presented into the "Current" Audit & Sanity check *.xls file:
   A) Total Number of Neighbors declarations;
   B) External Number of Neighbors detected;
   C) Reciprocally Number of Neighbors detected;
   D) Time spent by Agileto to evaluate the External Neighbors reciprocity [mm:ss].
2) Insert multiple references (steps) into the 4G Technology parser(s) which are displayed in case that an error occured;
   These references help in troubleshooting to identify the location into the module where the error occured;

8.33 58.186
1) Update M2.1 (Audit & Sanity check) for 2G/3G/4G to avoid an error which may occur if Agileto database is open when the module M2.1 is executed;

8.33 58.183
1) Update M1.4 (View Agileto outputs) and improve the Management and Interaction between Agileto & Excel;

8.33 58.182 => MILESTONE REACHED!
1) Accept the installation of Agileto PRO Edition on the latest PCs which have the storage type SDD instead of traditionally HDD;
2) Discriminate properly the User's Operation System between Windows 10 & Windows 11 as far as both of them share the same Windows major (10) & minor (0) releases;
3) Update the behaviour of the Silent Mode command, as following:
   Add the new optional third parameter ("Wait") to be used into the command string which launch Agileto in Silent Mode (after the Silent Mode command file), which instruct Agileto to "Wait" until the completion of the existing Silent Mode session and then start automatically the new demanded Silent Mode session;
   Example: "Updater.exe RunSilent,C:\Agileto\Orange\RunSilent_Example.csv,Wait"

8.32 58.182
1) Prevent entering into Agileto 4G database cases where eNodBId=0 which may occur when 'fake' neighbors 4G4G are detected into OMC dumps and the target 4G Cell has eNodeBId=0;
2) Accept into Agileto 3G database cases where CId=0 (it must have only RncId <> 0);

8.31 58.180
1) Due to the persinstent error type "Out of range" linked to the duplicated cells detected into Agileto database, revert back temporary to sort always the 2G/3G/4G Cells each time the currently module is executed in 'Silent' mode, without skipping this process as it was not managed properly. 

8.31 58.179
1) Correct/Update the Exit from Agileto 'Silent' mode status, as following:
   A) If the user attempts to abort/quit the 'Silent' mode then a pop-up request is asking to choose the way to quit: Immediatelly (distroy the current 'Silent' mode session) OR Properly (when the module ongoing has been completed followed by the Summary results printing);
   B) If all the modules from the 'Silent' mode have been executed then the exit from the 'Silent' mode is done automatically without any request to user feedback (the summary results are printed into the 'Silent' mode results file);

8.30 58.179
1) Agileto new 'Silent' mode options/features are provided, as following:
   A) Before starting a new Agileto 'Silent' mode session always exit automatically the eventually ongoing Agileto session in order to reset/release/(re)initialize to minimum the memory allocation;
   B) If the user chose to abort/quit Agileto 'Silent' mode it is given to him two options:
      B.1) Quit 'Silent' mode immediatelly -> The current 'Silent' mode session is destroyed and a new fresh Agileto 'normal' session is started;
      B.2) Quit 'Silent' mode properly     -> The current 'Silent' mode session is aborted after the ongoing working module is completed.
2) Update M2.1 (Audit & Sanity check) as following:
   A) Generate always Neighbors_External_2G2G/3G3G/4G4G.csv files which contain only the External Neighbors declarations detected;
   B) Update the algorithm which check the External Neighbors reciprocity in order to optimise (decrease) overall post-processing time.

8.29 58.177
1) Update Agileto's parsers for Nokia & Huawei (3G + 4G) in order to minimise overall post-processing time and release unnecessary memory to avoid "Out of Memory" error which may occur on huge input data;

8.29 58.174
1) Update M2.1 (Audit & Sanity check) by upgrading the algorithm which check the 2G2G/3G3G/4G4G 'External' neighbors reciprocities in order to be overcome "Out of Memory" error when huge input data is provided;
   Additionally to the update process of the standard Neighbors declarations files (Crt + Ref) there is generated for each case (Crt + Ref) another New smaller and dedicated External Neighbors file, as following:
   External_Neighbors-XGXG-Crt/Ref.csv [where XGXG -> may be 2G2G/3G3G/4G4G]

8.29 58.173
1) Update M2.1 (Audit & Sanity check) by upgrading the algorithm which check the 2G2G/3G3G/4G4G 'External' neighbors reciprocities in order to be faster and deal better with huge input data;
   The time spent only to check the 'External' Neighbors reciprocities is written into the brackets [mm:ss] into M2.1 Summary output which mention the path to the Reference neighbors declarations file;
2) Keep always the detected 'Duplicated' Cells file if it is generated in Silent Mode (do no more delete it in some circumstancies like when NoChange is detected on Agileto database!)

8.29 58.171 => MILESTONE REACHED!
1) Update M2.1 (Audit & Sanity check) for each 2G/3G/4G Technology by checking if the output 2G2G/3G3G/4G4G 'External' neighbors declarations detected are Reciprocally based on the similar (*.csv) neighbors (2G2G/3G3G/4G4G) file(s) generated on the same Agileto instance during the previous time when M2.1 was executed for the same technology (2G/3G/4G);
   Both neighbors (*.csv) files are updated with the Neighbors 'External' reciprocity status and the reference neighbors file is written at the end of the data into the current M2.1 output Summary Audit & Sanity check file (*.xls).
2) Fix a bug and update the algorithm which minimise overall processing time in Silent Mode by preventing to execute unnecessary sorting Agileto database 2G/3G/4G Cells operation(s);

8.29 58.168
1) Upgrade Agileto's parser for Huawei 4G OMC dump file (*.xml) exported via NOKIA OSS (NetAct) in order to be totaly independent of the way the data is organized/exported inside the (*.xml) file;
2) Minimise overall processing time in Silent Mode by preventing to execute unnecessary sorting Agileto database 2G/3G/4G Cells operation(s) in case that the previous executed module didn't modify Agileto database;

8.29 58.166
1) Upgrade Agileto's parser for Huawei 3G OMC dump file (*.xml) exported via NOKIA OSS (NetAct) in order to be totaly independent of the way the data is organized and exported from OSS [which may NOT be always continuously to the same source element(s)];
2) Update M2.1 (Audit & Sanity check) for 3G Technology and mark [1] as 'External' neighbor the last column into 3G3G *.csv neighbors declarations for all the vendors, in order to identify quickly "unidirectional" neighbors, especially to be verified at the border between two different vendors;

8.29 58.164
1) Update M2.1 (Audit & Sanity check) for 2G technology and mark [1] as 'External' neighbor the last column into 2G2G *.csv neighbors declarations for all the vendors, in order to identify quickly "unidirectional" neighbors, especially to be verified at the border between two different vendors;
2) Update M2.1 (Audit & Sanity check) for all 2G/3G/4G technologies and display the progress of writing each type of the neighbors into *.csv files (as far as it may take some time if the input OMC input files have big size;
3) Update internal Agileto's 2G/3G/4G Cell Codes in order to contain multiple info, as following:
   2G: FrqBand & LAC.CId + "_" + SectorId
   3G: FrqBand & RncId.CId + "_" + SectorId & FrqLayer
   4G: FrqBand & eNBId.CId + "_" + SectorId & FrqLayer
4) To avoid false 4G Cells detected as duplications, when it is generated the 4G Global_CId allocate by default 3 digits for the CId (Global_CId = eNBId & "XYZ", where "XYZ" is CId on 3 digits);
   (For special cases when CId > 999 then we get directly: Global_CId = eNBId & CId);

8.29 58.162
1) Upgrade Agileto's parser for NOKIA 3G OMC dump file (*.xml) as following:
   1.a) Process the data totally independent of the way the OMC (*.xml) file has been exported from OSS and the information is organized inside it;
   This upgrade will overcome Agileto's outputs missing data especially related to the 3G3G + 3G2G neighbors declarations when they are not declared continuously related to the same 3G Source Cell;
   1.b) Add supplementary into M2.1 (Audit & Sanity Check) 3G3G + 3G2G neighbors outputs the mark info [1] as the last column presenting if inconsistency Target Cells parameters are detected among multiple neighbors pointing to the same Target 3G/2G Cells;
2) Fix a bug when running M2.1 (Audit & Sanity Check) on 4G Technology, to prevent an error which may occur in special cases which may lead to huge numbers (milions) of cases for the 4G discrepancies detected that need to be reported; 
   Escape (temporary) the treatment for the huge number of the 4G discrepancies detected but complete the execution of the module (M2.1) with all the other results available.
3) Upgrade M2.1 (Audit & Sanity Check) for the Huawei 4G with the same option like for the Nokia 4G which has been added recently, as per below:
   Add a new column into the 4G2G/4G3G/4G4G neighbors detailed files (*.csv) which mark [1] the neighbors declarations toward 2G/3G/4G Target Cells which are not defined properly @ eNodeB level;

8.29 58.158
1) Correct a bug to prevent an error which may occur in special cases where eNodeBs may have NO External 2G/3G/4G Cells declarations;

8.29 58.157
1) Update Agileto's own database + all the other *.xls automatic reports to be into the highest User's Excel format available in order to potentially accomodate more than 65,000 rows of data (up to 1,048,576) if necessary;
2) Improve further the algorithms to process OMC 4G data read from *.xml input files in order to decrease processing time (special improvement for huge amount of input OMC data files);
3) New outputs are now available for M2.1 (Audit & Sanity Check) in 4G Technology:
   3.1) There is a new column added to the end of the 4G4G *.csv neighbors declarations which mark [1] only the neighbors to "External" 4G Cells (which means the target cells are not declared as regular 4G Cells @ eNodeB level into all the input OMC files);
   3.2) In case 4G2G/4G/3G/4G4G neighbors declarations are detected without proper declaration of the target 2G/3G/4G Cells as 'External' @ eNodeB level, the following outputs are available (ONLY FOR NOKIA 4G):
      a) New *.xls files presenting the missing 2G/3G/4G Target Cells declarations @ eNodeB level;
      b) It was added a new column into the 4G2G/4G3G/4G4G neighbors detailed files (*.csv) which mark [1] the neighbors declarations toward 2G/3G/4G Target Cells which are not defined properly @ eNodeB level;

8.28 58.153
1) Improve the management for processing OMC 4G data after the OMC 4G file(s) have been loaded into memory (to increase the overall post-processing speed); 
2) Display additionally OMC 4G data processing progress evolution for different elements;

8.28 58.152 => MILESTONE REACHED!
1) Complete support to post-process the Huawei 4G dumps (*.xml) exported via Nokia OSS (NetAct) [manually or automatically];
The objects (11) to be exported for Huawei 4G:
   ENODEBFUNCTION
   CNOPERATORTA
   CELL
   PDSCHCFG
   EUTRANEXTERNALCELL
   UTRANEXTERNALCELL
   GERANEXTERNALCELL
   EUTRANINTRAFREQNCELL
   EUTRANINTERFREQNCELL
   UTRANNCELL
   GERANNCELL
2) Improve the algorithms to read the data extracted from *.xml OMC dumps in order to increase the post-processing speed.
3) Prevent errors which may occur when the total number of 3G frequency layers detected into OMC files becomes > 10 (Max Frq layers = 20).
Remember Agileto's 3G frequency layers automatic allocation:
   a) 2GHz band:   -> Max 11 layers: (1-6) + (16-20)
   b) 900MHz band: -> Max  9 layers: (7-15)

8.26 57.149
1) Improve the memory allocation algorithms to keep at minimum the general PC's memory usage in order to deal better with multiple OMC input *.xml files;
2) Support for new Huawei 3G version (6910) - in addition to 6900 - *.xml files exported automatically via NOKIA OSS (NetAct);

8.25 57.146
1) Fix several bugs which lead to errors in some cases when the Huawei 2G/3G exported *.xml files via NOKIA OSS (NetAct) do not contain inside all the requested objects;

8.25 57.145
1) Improve the management of loading multiple OMC snaphot files in order to gain post-processing time;
2) Fix several bugs which could occur in several cases after implementing the support for parsing Huawei 2G + 3G (*.xml) dumps exported via Nokia OSS (NetAct);

8.24 57.144 => MILESTONE REACHED!
1) Complete support to post-process the Huawei 3G dumps (*.xml) exported via Nokia OSS (NetAct) [manually and automatically];
The objects (8) to be exported for Huawei 3G:
   URNCBASIC
   UCELL
   UPCPICH
   UEXT3GCELL
   UEXT2GCELL
   UINTRAFREQNCELL
   UINTERFREQNCELL
   U2GNCELL
The objects (8) to be exported for Huawei 2G (to remember) -> which has now support for automatic exports, too:
   BSC
   BTS
   GCELL
   CELLBIND2BTS
   GTRX
   GTRXDEV
   GEXT2GCELL
   G2GNCELL
2) Accept in Silent Mode commands as input for the reference OMC file the special category of strings (*.xml OR *.txt) which should be provided at the end of the input Path in case that the flag/parameter to load all OMC files from the same directory is selected [1];
This input will instruct Agileto tool to load as OMC input files all the same type of files detected at the input path provided [ahead of these special strings];
Example: C:\Agileto\DEMO_OMC_DUMP\OMC_Snapshots\3G\*.txt => will take as OMC input files all *.txt files detected at the path C:\Agileto\DEMO_OMC_DUMP\OMC_Snapshots\3G
3) Optimise the algorithms to process the data extracted from OMC *.xml files in order to gain processing time;

8.23 56.138
1) Update the parser for Huawei 2G dumps exported via NOKIA OSS (NetAct) in order to reflect properly the 2G2G Neighbors declarations which are exported sometimes not continuously related to the same 2G source cell;

8.22 56.137 => MILESTONE REACHED!
1) Complete support to post-process the Huawei 2G dumps (*.xml) exported via Nokia OSS (NetAct);
2) Add on Agileto Main Progress form the option to Hide/Show the Secondary Progress form evolution;
3) Update M2.1 module (Audit + SanityCheck) for 2G Technology in order to display and save the results which present the External 2G Cells declarations detected in discrepancy (BCCH/NCC/BCC) with the same 2G Cells' attributes declared @ their BSC reference;
4) Improve the management accuracy of the output summary results after running in Silent Mode;

8.21 56.132
1) Update the parsing of NOKIA 2G/3G/4G OSS dumps (*.xml) by accepting into the standard exported classes (objects) the special standard strings added as prefix while performing automatically OSS exports (via NetAct);
2) Update Agileto's Updater to the new version (2.44) that is corelated with the new Agileto version which improve the upgrading process in order to avoid 'infinite' loops by updating initially Updater.exe from the server, after a number of update attempts;
3) Improve the functionality for the Multi-Users case (improve algorithms and eliminate different bugs);

8.19 56.125
1) Improve the functionality and stability for the Multi-Users case when multiple users ( > 1 ) are using simultaneously Agileto tool, including the process of upgrading;

8.18 56.124
1) Correct a bug to allow the End user to send a feedback by pressing the "Feedback" button (through Agileto Communicator tool);
2) Add additionally info into the Licence related to the optional data concerning the "Maintenance" + "SilentMode" + "Multi-Users";
3) Add a new option which may allow to load automatically a new Licence if the validity of the existing Licence drops below 15 days and a New Licence is available on the server;
4) For the special case when Agileto is running in "Silent Mode" and it is not completed properly (ex: the user for some reasons "kills" Agileto.exe process from the Windows Tark bar) the next time when Agileto is started it will start working again in "Silent Mode" in order to execute again automatically the last command (*.txt) file which has not been completed the last time. To avoid this situation the user may use one of the following two options:
   A) Delete or Rename the original 'command' "RunSilentMode_file.txt";
   B) Execute from the DOS command prompt pointer the following command (without brackets): < Updater.exe CleanSilentMode >

8.17 56.123
1) Update the option to process ALL OMC input files detected into the same folder/subfolder(s), as following:
Get automatically the reference info (Technology + Vendor) detected into the SMALLEST (as size) and VALID input OMC file, while discarding automatically without warning OMC Atypic message notifications all the others OMC dump files not validated;
2) Update and improve the concept of Agileto Multi-Users working simultaneously on the same PC according with the Max Number granted by the Licence [V3.52];

8.15 56.120
1) Update the special cases of reading Agileto's database (2G/3G/4G data do NOT loading) in order to avoid displaying error messages;

8.15 56.119
1) Improve the communication between Agileto and Excel by a smarter management which should avoid certain "issues" reported by some users to occur "randomly";
2) Detect and close automatically specific Excel files if they are already open in different Excel instances, in case they need to be generated/updated by Agileto tool;
3) Update M4.1 (Network Optimisation based on Drive Tests) as following:
3.A)-> When opening the Drive Test results in either MapInfo or Google Earth, open automatically the layers representing the Sites and the Cells belonging to the specific Drive Test Technology and Frequency layer;
3.B)-> Add the Drive Test Legends and logo which are now visible into MapInfo Drive test results, too;
3.C)-> Generate for Google Earth two (2) sets of the output Drive Test legends and logo, as following:
  3.C.1: One set that is attached to the Drive Test Lat/Lon boundary limits -> This set may be switched ON/OFF from the 'Summary' folder (used for the printing option directly from Google Earth menu);
  3.C.2: One set that is attached to the Display on Screen edge boundaries limits -> This set may be switched ON/OFF from the 'Agileto' and "Legend" folders (used for the regular display on screen option in Google Earth);
(By default both sets mentioned above are visible => The end user should select the set according with its own needs)

8.15 56.117
1) Update M5.1 (Map Cells KPIs into MapInfo and GoogleEarth) concerning the MapInfo legend files as following:
Generate KPIs legend files (*.bmp) as 24 bit depth format into MapInfo KPIs dedicated folders, to be available and display proprly as legends for MapInfo KPIs representations;
2) Add supplementary to the existing Google Earth Overlays screen images (Logo + KPIs legend) similar info linked to the Network limits (that may be switched ON/OFF from the 'Summary' folder) which may be copied or printed directly from Google Earth menu as an image;

8.14 56.115
1) Update/Rectify one input parameter for M5.1 (Map Cells KPIs into MapInfo and GoogleEarth):
Change the meaning for the second input KPI string which represents now the Suffix to be added to the KPI's Output folder name, in addition to the KPI Given Name string;
Exemple: If KPI_Name="CS_CDR" and KPI_Suffix="20220217" => KPI's Output Folder name ="CS_CDR-20220217";

8.14 56.113
1) Update M5.1 (Map Cells KPIs into MapInfo and GoogleEarth) to accept (optionally) as input - for both Normal and Silent modes - the KPI's output results Folder name, which may be now different than the KPI Name string value (like it was previously by default);
This way the end user may store the KPI's output results into a dedicated folder name, which could be a string that may include, as example: both the date and KPI Given Name, like -> "20220217_CS-DCR", while all the other KPI's outputs final results will always make reference only to the KPI Given Name (ex: "CS_DCR");
Create automatically the KPIs legend files pictures (*.gif) with suggestive names into MapInfo KPIs dedicated folders (to be available as legends for MapInfo KPIs representations);
2) Update M1.4 which brings now two new objects (pictures) to view in Agileto's MapInfo representations:
A) Agileto PRO Edition logo +
B) KPIs legends (similar like those presented in Google Earth);

8.14 56.110
1) Update M1.4 -> The section to view KPIs (in MapInfo and Google Earth) which may be now multiple selected from all KPIs which were previously generated;

8.14 56.109
1) Do no more show Agileto's Publicity Message (once) every new day in case it is detected a purchased Agileto Licence and the remaining number of validity days is > 15 [2 weeks];
2) Fix a bug which generates errors with the Newest Excel versions when generating the 2G/3G/4G Cells discrepancies while running M2.1;

8.13 56.108
1) Improve the algorithms which manage the loading and processing of the OMC input snapshot files in order do no more be necessary to load again the same OMC files per technology if they were already processed previously on the same Agileto instance;
This New smarter approach leads to an important overall gain in processing time, especialy visible for the large networks (big 2G/3G/4G OMC files).

8.13 56.103
1) Fix a bug which leads for some newest Excel versions to an error (Excel syntax incompatibility) while running M2.1 for 3G Technology;

8.13 56.102
1) Complete the support for the module M1.3 (2G/3G/4G Border Cells evaluation) to be executed in 'Silent' mode.
1.3,P_1,P_2,P_3,P_4,P_5,P_6
Module [Reference],Project Name [Optional] [Default="" -> ActiveProject] [String],2G ALL Cells to be considered (versus OMC) [Optional] [default=1] [1/0],3G ALL Cells to be considered (versus OMC) [Optional] [default=1] [1/0],4G ALL Cells to be considered (versus OMC) [Optional] [default=1] [1/0],Border Cells BeamWidth Increase (%) [Optional] [default=0] [0 to 50],Border Cells Distance (Km) [Optional] [default=7] [1 to 50]
=> The above [6] parameters are the parameters which the user should provide into the normal Agileto usage interface. All parameters [P_2 to P_6] are optionally. Below are presented some example commands:
1.3,DEMO_PROJECT,1,1,1,10,5
1.3,DEMO_PROJECT,0,0,0,,
2) Complete the support for the module M3.4 (ANR -> Automatic Neighbor Relation) to be executed in 'Silent' mode.
3.4,P_1,P_2,P_3,P_4,P_5,P_6,P_7,P_8,P_9,P_10,P_11,P_12,P_13,P_14
Module [Reference],Project Name [Optional] [Default="" -> ActiveProject] [String],Input Technology  (Source) [2/3/4] ,Source Cell Coverage Distance Type [1/0] ,Source Cell Coverage Distance Value [Single] ,Max Target Cell  Distance Type [1/0] ,Max Tatget Cell  Distance Value [Single] ,Impose Neighbors Reciprocity [1/0],2G OMC only Cells to be considered (versus ALL) [Optional] [default=0] [1/0] ,3G OMC only Cells to be considered (versus ALL) [Optional] [default=0] [1/0] ,4G OMC only Cells to be considered (versus ALL) [Optional] [default=0] [1/0] ,Path to the 2G Neighbors reference file [Optional] [String],Path to the 3G Neighbors reference file [Optional] [String],Path to the 4G Neighbors reference file [Optional] [String],Output Folder name results [Optional] [String]
=> The above [14] parameters are the parameters which the user should provide into the normal Agileto usage interface. It is provided the supplementary option to output all the results into a specific folder name provided as the last optional parameter [P_14]. The last 7 parameters [P_8 to P_14] are optionally. Below are presented some example commands:
3.4,DEMO_PROJECT,2,1,0.65,1,1.5,1,0,0,0,C:\Agileto\DEMO_PROJECT\MapInfo\Neigh_DB\2G-2G_Neighbors_Demo.csv,,,
3.4,DEMO_PROJECT,3,1,0.65,1,2.5,1,1,1,1,C:\Agileto\DEMO_PROJECT\MapInfo\Neigh_DB\3G-2G_Neighbors_Demo.csv,C:\Agileto\DEMO_PROJECT\MapInfo\Neigh_DB\3G-3G_Neighbors_Demo.csv,,To_Test
3.4,DEMO_PROJECT,4,1,0.7,1,3.5,0,0,0,0,C:\Agileto\DEMO_PROJECT\MapInfo\Neigh_DB\4G-2G_Neighbors_Demo.csv,C:\Agileto\DEMO_PROJECT\MapInfo\Neigh_DB\4G-3G_Neighbors_Demo.csv,C:\Agileto\DEMO_PROJECT\MapInfo\Neigh_DB\4G-4G_Neighbors_Demo.csv,
3.4,DEMO_PROJECT,4,0,1.3,0,3,1,0,0,0,C:\Agileto\DEMO_PROJECT\MapInfo\Neigh_DB\4G-2G_Neighbors_Demo.csv,C:\Agileto\DEMO_PROJECT\MapInfo\Neigh_DB\4G-3G_Neighbors_Demo.csv,C:\Agileto\DEMO_PROJECT\MapInfo\Neigh_DB\4G-4G_Neighbors_Demo.csv,

8.12 56.100
1) Insert into Google Earth outputs 'Summary' folder the info presenting which Cells 2G/3G/4G have been used into representation (OMC only or ALL);
2) Correct a bug in M2.2 which in fails to write the 3G/4G (PSCs/PCIs) labels into the final output results;
3) Complete the support for the module M3.2 (Neighbors database -> MapInfo & Google Earth) to be executed in 'Silent' mode:
3.2,P_1,P_2,P_3,P_4,P_5,P_6,P_7,P_8,P_9,P_10,P_11,P_12,P_13,P_14
Module [Reference],Project Name [Optional] [Default="" -> ActiveProject] [String],Path to External Neighbors declarations File *.csv [String],Source Technology [2/3/4],Target Technology [2/3/4],Source Cell Format = Cid + LAC/RncId/eNodeBId [1/0],Target Cell Format = Cid + LAC/RncId/eNodeBId [1/0],Source Cid Header [String],Source LAC/RncId/eNodeBId Header [String],Target Cid Header [String],Target LAC/RncId/eNodeBId Header [String],sib11orDch Header [Optional] [String],Priority Header [Optional] [String],Special Header [Optional] [String],Output Folder name results [Optional] [String]
=> The above [14] parameters are the parameters which the user should provide into the normal Agileto usage interface. It is provided the supplementary option to output all the results into a specific folder name provided as the last optional parameter [P_14]. The last 4 parameters [P_11 to P_14] are optionally. Below are presented some example commands:
3.2,DEMO_PROJECT,C:\Agileto\DEMO_PROJECT\MapInfo\Neigh_DB\4G-3G_Neighbors_Demo.csv,4,3,1,1,CellID_Source,eNBId_Source,CellID_Target,RNC_Target,,Neighbor Priority,,
3.2,DEMO_PROJECT,C:\Agileto\DEMO_PROJECT\MapInfo\Neigh_DB\3G-3G_Neighbors_Demo.csv,3,3,0,0,sourceCID,,targetCID,,sib11OrDchUsage,Neighbor Priority,,
3.2,DEMO_PROJECT,C:\Agileto\DEMO_PROJECT\MapInfo\Neigh_DB\3G-2G_Neighbors_Demo.csv,3,2,1,1,3G Cell_ID (Source),3G RNC_ID (Source),targetCID,targetLAC,sib11OrDchUsage,Neighbor Priority,,To_Test

8.11 56.097
1) Improve OMC 2G/3G/4G dump file's Vendor and Technology detection algorithm in order to minimize the total processing time;
2) Add for Agileto in Silent mode [M2.1] the new/last parameter [0/1] P_7 which allows to execute additionally M3.1 with the same OMC Input file like for M2.1;
2.1,P_1,P_2,P_3,P_4,P_5,P_6,P_7
Module [Reference],Project Name [Optional] [Default="" -> ActiveProject] [String],Path to OMC Input File [String],Input All OMC files same Folder [Optional] [default=0] [1/0],Input All OMC files SubFolder [Optional] [default=0] [1/0],Perform Border Cells Analysis [Optional] [default=0] [1/0],Output Folder name results [Optional] [String],Execute additionally M3.1 [Optional] [default=0] [1/0]
2.1,DEMO_OMC_DUMP,C:\Agileto\DEMO_OMC_DUMP\OMC_Snapshots\3G\RNC0105.txt,0,0,0,,1
2.1,DEMO_OMC_DUMP,C:\Agileto\DEMO_OMC_DUMP\OMC_Snapshots\3G\RNC0105.txt,0,,1,To Test,1

8.11 56.095
1) While generating Agileto *.xls outputs, ignore automatically Excel asking for *.xls compatibility with previous versions;
2) Hide Excel object (and its changes performed) by Agileto during the execution in 'Normal' mode (in addition to 'Silent' mode);
3) Add two new optional inputs for M1.2 while running in 'Silent' mode concerning the Border Cells evaluation, representing Antennas BeamWidth enlargement [%] + Distance [Km];
4) When performing M2.1 (Audit and SanityCheck) for 4G Technology, save the 2G/3G/4G Cells discrepancies files detected into the latest Excel format available [*.xlsx] (although the files' extension is *.xls) in order to overpass the possible limitations in nr of lines [~ 65000] which are into a standard *.xls file format;
5) Techno 3G: Improve the parser algorithm to load OMC dump file in order to extract all 3G frequencies available from the Remote Cells declarations too, in addition to the standard 3G Cells declared @ RNC level;
6) Techno 4G+3G: While processing OMC 4G dump file (M1.1 + M2.1) update Agileto's database 3G Cells LAC missing info from the 3G external cells declarations @ [4G] eNodeBs level;
7) Update Huawei OMC 3G [*.txt] Parser in order to read just a single *.txt file (Not all files like before) and align it with the same approach like for all the other vendors;

8.09 56.091
1) Hide Excel object (and its changes performed) by Agileto during the execution in 'Silent' mode;

8.08 56.091
1) In 'Silent' mode window add the new option to Ignore (or Not) the pop-up message concerning the Duplicated Cells detected into Agileto database;
2) When the user is selecting to get all the input OMC files from the same folder (and subfolders): => To gain processing time => Get the Reference (Technology and Vendor) from the smaller size OMC input file (which is not necessary OMC selected file);

8.07 56.089
1) Complete the support for the modules M2.4 (Network comparison between two OMC dump files) to be executed in 'Silent' mode:
2.4,P_1,P_2,P_3,P_4,P_5,P_6,P_7,P_8
Module [Reference],Project Name [Optional] [Default="" -> ActiveProject] [String],Path to REFERENCE OMC Input File [String],Path to NEW OMC Input File [String],Reference Input All OMC files same Folder [Optional] [default=0] [1/0],Reference Input All OMC files SubFolder [Optional] [default=0] [1/0],NEW Input All OMC files same Folder [Optional] [default=0] [1/0],NEW Input All OMC files SubFolder [Optional] [default=0] [1/0],Output Folder name results [Optional] [String]
=> The above [8] parameters are in fact the parameters which the user should provide into the normal Agileto usage interface. The last 5 parameters [P_4 to P_8] are optionally. It is provided the supplementary option to output all the results into a specific folder name provided as the last optional parameter [P_8]. Below are presented some example commands:
2.4,DEMO_OMC_DUMP,C:\Agileto\DEMO_OMC_DUMP\OMC_Snapshots\3G\RNC0105.txt,C:\Agileto\DEMO_OMC_DUMP\OMC_Snapshots\3G\RNC0105.txt,0,0,0,0,
2.4,,C:\Agileto\DEMO_OMC_DUMP\OMC_Snapshots\3G\RNC0105.txt,C:\Agileto\DEMO_OMC_DUMP\OMC_Snapshots\3G\RNC0105.txt,0,,,,Comparison

8.06 56.088
1) In 'Silent' mode add a button to 'Abort' the current processing list of the remaining Modules to be executed;
2) In 'Silent' mode add two options to show/hide the progress evolution of the Main/Secondary progress forms;
3) Complete the support for the modules M2.2 (PSC/PCI Audit and Optim) + M2.3 (BCCH Audit and Optim) to be executed in 'Silent' mode:
2.2,P_1,P_2,P_3,P_4,P_5,P_6
Module [Reference],Project Name [Optional] [default="" -> ActiveProject] [String],All Cells to be used  [Optional] [default=1] [0 -> only OMC Cells] [1/0],Ring Radius analysis Km [Optional] [default=15] [5 to 25] [Single],Reservation list [Optional] [String],Technology [Optional] [default=3] [3/4],Keep same PSC/PCI on Twin Cells [Optional] [default=1] [1/0]
=> The above [6] parameters are in fact the parameters which the user should provide into the normal Agileto usage interface. All [6] parameters are optionally. P_4 (Reservation list) is a string which contains the numbers separated by the star character "*". Below are presented some example commands:
2.2,DEMO_PROJECT,1,10,,3,1
2.2,,,,0*2*5,3,
2.2,,0,15,,4,

2.3,P_1,P_2,P_3,P_4
Module [Reference],Project Name [Optional] [default="" -> ActiveProject] [String],All Cells to be used  [Optional] [default=1] [0 -> only OMC Cells] [1/0],Ring Radius analysis Km [Optional] [default=15] [5 to 25] [Single],Reservation list [Optional] [String]
=> The above [4] parameters are in fact the parameters which the user should provide into the normal Agileto usage interface. All [4] parameters are optionally. P_4 (Reservation list) is a string which contains the numbers separated by the star character "*". Below are presented some example commands:
2.3,DEMO_PROJECT,1,15,
2.3,,,,637*638*640
2.3,,0,5,

8.05 56.085
1) Update M3.1 the General Neighbors folder name (output) in Google Earth with the Name of the Input OMC file (in addition to the PROJECT_NAME);
2) Update M3.2 the General Neighbors folder name (output) in Google Earth with the Name of the Input *.csv file (in addition to the PROJECT_NAME);
3) Update the Window presentation progress in 'Silent' mode to reflect easier/better the progress evolution of the modules execution;
4) Complete the support for the module M3.1 (OMC dump file to -> MapInfo + GoogleEarth [neighbors converter]) to be executed in 'Silent' mode, by external commands. The syntax of the command contains 4 parameters separated by commas, as they are presented below with their meaning:
3.1,P_1,P_2,P_3,P_4,P_5
Module [Reference],Project Name [Optional] [Default="" -> ActiveProject] [String],Path to OMC Input File [String],Input All OMC files same Folder [Optional] [default=0] [1/0],Input All OMC files SubFolder [Optional] [default=0] [1/0],Output Folder name results [Optional] [String]
=> The above [5] parameters are in fact the parameters which the user should provide into the normal Agileto usage interface. It is provided the supplementary option to output all the results into a specific folder name provided as the last optional parameter [P_5]. The last 3 parameters [P_3 to P_5] are optionally. Below are presented some example commands:
3.1,DEMO_OMC_DUMP,C:\Agileto\DEMO_OMC_DUMP\OMC_Snapshots\3G\RNC0105.txt,0,0,
3.1,,C:\Agileto\DEMO_OMC_DUMP\OMC_Snapshots\3G\RNC0105.txt,0,,To Test

8.04 56.083
1) Complete the support for the module M2.1 (OMC dumps Audit & SanityCheck) to be executed in 'Silent' mode, by external commands. The syntax of the command contains 6 parameters separated by commas, as they are presented below with their meaning:
2.1,P_1,P_2,P_3,P_4,P_5,P_6
Module [Reference],Project Name [Optional] [Default="" -> ActiveProject] [String],Path to OMC Input File [String],Input All OMC files same Folder [Optional] [default=0] [1/0],Input All OMC files SubFolder [Optional] [default=0] [1/0],Perform Border Cells Analysis [Optional] [default=0] [1/0],Output Folder name results [Optional] [String]
=> The above [6] parameters are in fact the parameters which the user should provide into the normal Agileto usage interface. It is provided the supplementary option to output all the results into a specific folder name provided as the last optional parameter [P_6]. The last 4 parameters [P_3 to P_6] are optionally. Below are presented some example commands:
2.1,DEMO_OMC_DUMP,C:\Agileto\DEMO_OMC_DUMP\OMC_Snapshots\3G\RNC0105.txt,0,0,0,
2.1,DEMO_OMC_DUMP,C:\Agileto\DEMO_OMC_DUMP\OMC_Snapshots\3G\RNC0105.txt,0,,1,To Test

8.03 56.081
1) Complete the support for the module M1.1 (Generate and update Agileto's database) to be executed in 'Silent' mode, by external commands. The syntax of the command contains 13 parameters separated by commas, as they are presented below with their meaning:
1.1,P_1,P_2,P_3,P_4,P_5,P_6,P_7,P_8,P_9,P_10,P_11,P_12,P_13
Module [Reference],Project Name [Optional, Default="" > ActiveProject] [String],Input OMC / Excel file [1/0],Path to Input File [OMC/Excel] [String],Create Agileto databse type [New / Update common Cells / Update All Cells] [1/2/3],New Database: 3G Cells Local_Cid = RncId & Cid  [Optional, default=1] [1/0],Input All OMC files same Folder [1/0] ,Input All OMC files SubFolder [1/0] ,2G Sheet [String],2G Template [String],3G Sheet [String],3G Template [String],4G Sheet [String],4G Template [String]
=> The above [13] parameters are in fact the parameters which the user should provide into the normal Agileto usage interface. Up to the desired inputs (OMC dump files or External Excel file) the minimum number of mandatory parameters could be: 4 to 7, 9, 11 or 13. Below are presented some example commands:
1.1,DEMO_OMC_DUMP,1,C:\Agileto\DEMO_OMC_DUMP\OMC_Snapshots\3G\RNC0105.txt,1,1,0,0,,,,,,
1.1,DEMO_OMC_DUMP,0,C:\Agileto\DEMO_OMC_DUMP\MobileNW_Config\MobileNW_External_DB\DEMO_RNC105_3G-2G.xls,2,,,,,,Tech3G,DEMO_OMC_3G,,
1.1,,0,C:\Agileto\DEMO_OMC_DUMP\MobileNW_Config\MobileNW_External_DB\DEMO_RNC105_3G-2G.xls,2,,,,Tech2G,DEMO_OMC_2G,,,,

8.02 56.080
1) Complete the support for the module M1.2 (Generate NW cells/sites objects in MI + GE) to be executed in 'Silent' mode, by external commands. The syntax of the command contains 16 parameters separated by commas, as they are presented below with their meaning:
1.2,P_1,P_2,P_3,P_4,P_5,P_6,P_7,P_8,P_9,P_10,P_11,P_12,P_13,P_14,P_15,P_16
Module [Reference],Project Name [Optional, Default="" > ActiveProject] [String],Cell Ref Radius m [Single] [10 to 1000],Cell Radius Increment m [Single] [1 to 200],2G selected Region (BSC_Name / LAC / Cluster) [1/2/3],2G All Cells to Map [1/0],2G Cells Not in OMC Map in Grey [1/0],3G selected Region (RNC_Name / LAC / Cluster) [1/2/3],3G All Cells to Map [1/0],3G Cells Not in OMC Map in Grey [1/0],4G selected Region (TAC / Cluster) [1/2],4G All Cells to Map [1/0],4G Cells Not in OMC Map in Grey [1/0],Spatial 3G Google output [Optional, default=1] [1/0],Hide the Sites label [Optional, default=1] [1/0],Sites icon scale (size) [Optional, default=0.9) [0.1 to 5],Sites label scale (size) [Optional, default=0.7) [0.1 to 5]
=> The above [16] parameters are in fact the parameters which the user should provide into the normal Agileto usage interface, and the last 4 [P_13 to P_16] are optional. Below are presented some example commands:
1.2,DEMO_PROJECT,250,20,1,1,0,1,1,1,1,1,1,,,,
1.2,,100,10,2,1,0,3,1,0,2,1,0,,,,

8.01 56.079
1) Start the support for the CLI (Client Line Interface) - Running in Silent mode - which allows now the End User to execute from the command line different Agileto modules;
This new feature allows Agileto to be executed by scripts automatically & programatically at desired time stamps allowing the human to focus just on the results;
As example, during the night the scripts may retrieve OMC dumps + multiple KPIs from the Mobile Network and then automatically generate a fresh Agileto database map KPIs on MapInfo and Google Earth;
The same principle may apply for the automatization of the drive tests post-processing process which may occur automatically during the night followed by the Analysis & Optimisation activity;
Basically, all the manual human manipulation of different Agileto modules may be now automatically performed by scripts letting the human to focus only on what is really important;
As consequence, the new/updated Agileto's database would be generated automatically based on the OMC dumps which can let the Sites/Cells to be automatically mapped on MapInfo and Google Earth;

2) Starting with this new core version (8.01) we have completed the full support for the module M5.1 [KPIs] to be executed in 'Silent' mode, by external commands. The syntax of the command contains 21 parameters separated by commas, as they are presented below with their meaning:
5.1,P_1,P_2,P_3,P_4,P_5,P_6,P_7,P_8,P_9,P_10,P_11,P_12,P_13,P_14,P_15,P_16,P_17,P_18,P_19,P_20,P_21
Module [Reference],Project Name [Optional] [String],KPI Excel file [String],KPI Sheet [String],Technology [2/3/4],Key Cell Name [1/0],CellName / 2G_LAC [String / Long],GCId [Long] , Long],KPI Percentage [1/0],Represent All Cells [1/0],KPI Given Name [String],Reference Cell Radius Km [Single],Cell Radius Increment m [Integer],KPIs Ascending Order [1/0],Cell Radius Proportional with KPI [1/0],Reference KPI Proportional value [Optional] [single],Maximum Radius Proportional value [Optional] [single],KPI Threshold 1 [Optional] [Single],KPI Threshold 2 [Optional] [Single],KPI Threshold 3 [Optional] [Single],KPI Threshold 4 [Optional] [Single]
The above [21] parameters are in fact the parameters which the user should provide into the normal Agileto usage interface, and the last 6 [P_16 to P_21] are optional. The 'Project_Name' parameter [P_1] is optional and in case it is not provided, then Agileto will consider the last Active Project used by the user.
Agileto's execution in 'Silent' mode of a serie of similar commands is performed by using its Updater.exe with a DOS [CLI] command, following a very simple syntax [Updater.exe RunSilent,Path_To_RunSilentFile].
As example, after you upgrade Agileto to this new version, you may test this new functionality as following:
Let's assume that you have Agileto installed into the following directory [C:\Program Files (x86)\Agileto] where reside both Agileto.exe + Updater.exe; Then create the following text files into the same installation path:

A) RunSilent_Ex.txt -> which should contain the command lines - as presented above - to be executed. As reference you may copy inside the following content:
5.1,DEMO_PROJECT,C:\Agileto\DEMO_PROJECT\KPIs\DEMO_KPIs.xls,KPIs_3G,3,1,3G_Cell_Name,,CS_CDR,1,1,CS_DCR,0.25,20,1,1,,,,,,
5.1,,C:\Agileto\DEMO_PROJECT\KPIs\DEMO_KPIs.xls,KPIs_2G,2,0,2G_Cell_LAC,2G_Cell_ID,CS_RAB,0,1,CS_RAB,0.2,20,0,0,,,,,,
5.1,,C:\Agileto\DEMO_PROJECT\KPIs\DEMO_KPIs.xls,KPIs_4G,4,1,4G_Cell_Name,,DL_Throughput [Mbps],0,0,ThPut [Mbps],0.3,10,0,1,,,,,,

B) RunSilent_Cmd.bat -> which trigger the execution of the commands detected into RunSilent_Ex.txt file and which should have the following content:
C:\Program Files (x86)\Agileto\Updater.exe RunSilent,C:\Program Files (x86)\Agileto\RunSilent_Ex.txt

C) Execute the file RunSilent_Cmd.bat by double click with the mouse on it and you should start to see the evollution/progress of Agileto running in 'Silent' mode. 
Beside the progress evolution presented on the form, the final summary results [Success/Failure] of the Agileto's activity running in 'Silent' mode may be checked in details into the new file created:
RunSilent_Ex-Agileto_RunSilent_Results.txt

Further devellopments will follow soon for the other Agileto's modules. Enjoy it!

7.58 56.079
1) Correct a bug which occurs in M1.1 by very specific user input manipulations, concerning the options to update Agileto database from external Excel OR OMC snapshot files;

7.58 56.078
- Update the module M1.2 (Generate NW cells/sites objects in MI + GE) - V3.17:
1) Correct a bug which prevent to generate properly MapInfo 3G Workspace in V3.16;
2) Display properly [make it visible always] the Omnidirectional Cells [Antennas_BW=360degrees] in Google Earth, which due to their Antenna Height values [ex: 1m (for indoor cells)] were not previously visible;
3) Similar correction was applied to view [properly] the lines in Google Earth when visualizing the Neighbors, or the Conflict lines between the same "Beacon_Cells";
- Update Agileto's "About" menu which allow now to view Agileto's versions changes logs history;

7.57 56.076
- Update the module M1.2 (Generate NW cells/sites objects in MI + GE) - V3.16:
1) Beside the Site/Cells objects and the 'Beacon Cells', the module M1.2 generates now supplementary the 'Border Cells' too, for each Technology [2G/3G/4G] & frequency layer;
2) The unicity of the 2G/3G/4G Sites are evaluated now initially based on the Cells Coordinates, and if they are missing then based on the Cell's Site Name.
3) There are updated automatically data extracted from Agileto database in case they are missing, as following:
Cell's missing geographically coordinates are automatically updated during the calculations and representations in MapInfo & Google Earth, as following:
-> If the Cell's geographically coordinates are missing from Agileto database they are updated based on another cell's coordinates belonging to the same Site;
-> Cell's missing Azimuths are updated automatically too, if they are detected on the 'Twin' cell of the same site, based on the SectorId value.
-> For the 4G Technology, Agileto is extracting the SectorId [if it is missing] automatically as the last digit from the Cell Relative_CID;

7.56 56.071
- Update the module M1.2 (Generate NW cells/sites objects in MI + GE):
Beside the Site/Cells objects, the module M1.2 generates now supplementary [completly] the 'Beacon Cells' (Allocation & Conflict) for each Technology [2G/3G/4G] & frequency layer, as following [Google Earth]:
    2G -> BCCHs
    3G -> PSCs
    4G -> PCIs
With this representation of the 'Beacon Cells' (Allocation & Conflict), it is possible to quick visualise the [2G/3G/4G] Beacon Cells 'Index' planning and provide the correction/optimisation by M2.2 & M2.3, too.

7.56 56.069
1) Improve the support for MapInfo on 64 Bits [due to MapInfo's bug which is not created & working properly as an "object"]
2) Update Agileto's Updater to the new version 2.35;

7.53 56.068
- Double check verifications (on Project and Technology levels) concerning the matching of the Reference Cell Radius and Increment values;

7.51 56.067
- Check periodically if a new Agileto version is available and update it automatically;
- Update the module M4.1 (Network Optimisation based on Drive Tests):
1: -> Retrieve the 3G/4G Input Frequency layers options [which are recorded now on a project basis rather than the last Project analysis];

7.50 56.064
- Update the module M1.2 (Generate NW cells/sites objects in MI + GE):
Update 4G layers to be represented according with their layer values and not with their order detected into Agileto database;
- Update the module M3.2 (Neighbors database -> MapInfo & Google Earth) & M3.1, too;
Propagate the New Max accepted 3G/4G frequency layers [from 10 to 20] into routines related to the neighbors representations for each layer;

7.50 56.062
- Fix a routine (bug/issue) which provide while importing OMC 4G dumps/snapshots files several 4G Cells duplications in Agileto database and consequently further errors.

7.50 56.061
- Update the module M1.2 (Generate NW cells/sites objects in MI + GE):
1: -> Add more flexibility for the Agileto's User to represent the Cells in MapInfo & Google Earth by providing now two input parameters: Cells Radius and Increment;
Beside the Cells Reference Radius lenght [3G_F1] add the second input parameter "Delta Radius" representing the difference [increment] in radius between two frequency layers;
- Update the module M5.1 (Map Cells KPIs into MapInfo and GoogleEarth):
1: -> Update the routine in order to be compatible with the New Cells representations mentioned above by providing two input parameters: Cells Radius and Increment [Delta Radius];
- Update all Agileto modules which provide representations of the cells in MI & GE by geting automatically the Cells Radius and Increment parameters which are now saved on a project basis.

7.49 56.059
- Update Agileto's routines to support MapInfo & Google Earth Site/Cells objects generation by the new approach of increasing the Max Frequency layers accepted from 10 to 20;

7.48 56.057
- Add a new Form which is presenting all the OMC files to be loaded at once, if such of option is selected;
- Propagate the new Max frequency layers accepted [from 10 to 20] to other routines in order to be reflected properly on M1.2 (Generate NW cells/sites objects in MI + GE);

7.48 56.055
1) While processing an input OMC dump file, display on the General window progress barr the Technology + Vendor that were detected;
2) Update Agileto's Updater to the new version 2.30;
3) Start to create specific routines to improve the analysis of the drive test -> Module 4.1 (Network Optimisation based on Drive Tests)

7.47 56.053
1) Update multiple routines in order to properly propagate the increasing number of Max 3G layers accepted from 10 to 20, as following:
'3G -> 2Ghz band has standard allocated layers [1 to 6] + [16 to 20]
'3G -> 900MHz band has standard allocated layers [7 to 15]
2) To support the point 1) above, optimize functions/routines by dinamically allocation of the memory instead of using the Maximum values defined for different elements;
This update has the purpose to avoid 'Overflow' in memory allocation while working/importing big amount of data (cells) especially from very large OMC snapshots files;
3) Update Agileto's Updater to the new version 2.20; This new version will allow a better control over updating by Agileto of its last available Updater.exe version.
4) Change Agileto\About Main menu and update "Get Help..." option which will redirect now the user toward Agileto_Help.pdf document.

7.46 56.052
- Agileto's Updater (.exe) file has been updated to the new version (2.19).
Correct a bug which prevents Agileto in certain conditions to not work properly.

7.44 56.052
- Agileto's Updater (.exe) file has been updated to the new version (2.17).
This new update allows now the user to see on another "Progress barr" window what is the progress, time requested/remaining until is completed the load of an OMC *.xml snapshot file. 

updater
7.43 56.051
- When importing Nokia 2G/3G/4G dumps display the status of the standard 'Tables' if anyone is missing, and let the User the option(s) to select if he wants to continue.
- Modify Agileto to resume instead to Exit automatically in case it is not provided as input a valid OMC *.xml snapshot file;
- Update support for MapInfo on 64 Bits by letting the End User the option to apply or not the "workaround" on dedicated CheckMark which may be found on Agileto\About Main menu.

7.42 56.048
- Increase from 10 to 20 the Maximum number of 3G and 4G Frequency layers that can be accomodated by Agileto [read from its database or extracted from OSS dump files) in this way:
A) 3G Technology (to keep backward compatibility):
   11 layers [1 to 6] and [16 to 20] are now available for 2GHz band (against 6 layers previously [1 to 6]);
    9 layers [7 to 15] are now available for 900MHz band (against 4 layers previously [7 to 10]);
B) 4G Technology:
   20 layers [1 to 20] are now available (against 10 layers previously [1 to 10])

7.42 56.046
- Fix several errors/bugs ocuring during the parsing of the Nokia 2G & 3G OSS snapshot/dumps files;

7.42 56.043
- Update the parser for Nokia 3G dump *.xml in order to cope with the special case(s) mentioned below:
NodeB_Id is not unique over the entire 3G Netork and there may be cases with two NodeBs on different RNCs sharing the same NodeB_Id;

7.42 56.042
- Update the parser for Nokia 2G dump *.xml in order improve the detection of the 2G cell BCCH channel (ARFCN) from TRX database based on the 'channel0Type' parameter;
On the previous version was set to TRUE the Trx frequency as BCCH when the parameter was = 4; now it has been added the option to have the value = "MBCCH"

7.42 56.041
- Update the module M4.1 (Network Optimisation based on Drive Tests):
1: Check the format of the External Neighbors declarations file (*.csv) and notify by a pop-up message if it does not match the right format or if its parsing failed;

7.42 56.040
- Update the support for MapInfo Professional on 64 bits due to a MapInfo's bug which do not behave as expected when is created as an object with the function CreateObject("MapInfo.Application.x64");
To overcome this issue it is provided a 'Workaround' in order for Agileto to still be able to generate automatically all MapInfo *.TAB files for the Sites/Cells but with the drawback of creating a new visible MapInfo instance which remain open even after the process is finished.
This specific case (MapInfo on 64 bits) it is recomended that before generating the Sites/Cells in MapInfo (M1.2 & M5.1) to close any other open MapInfo instance.

7.42 56.039
- Improve the support for Google Earth (Pro) on different intallations 32/64 bits

7.42 56.038
- Improve the support for MapInfo Professional on 64 bits

7.42 56.037
- Update the module M2.2 (3G/4G PSC/PCI allocation Audit and Optimisation):
1: Improve the algorithm (Button on Form) which Map with different collors the circles/lines in Google Earth representing the PSCs/PCIs (3G/4G Cells) -> Allocation & Conflict;
- Update the module M2.3 (2G BCCH allocation Audit and Optimisation):
1: Improve the algorithm (Button on Form) which Map with different collors the circles/lines in Google Earth representing the BCCHs (2G Cells) -> Allocation & Conflict;

7.42 56.035
- Update the module M2.2 (PSC/PCI allocation Audit and Optimisation):
1: Add the New option to select if during the optimum PSCs/PCIs allocation over the entire 3G/4G Mobile Network to keep (or Not) the same PSCs/PCIs like for the CoSector Twin Cells PSC/PCI allocation;

7.42 56.032
- Update the module M2.2 (PSC/PCI allocation Audit and Optimisation):
1: During the evaluation of the PSCs/PCIs optimim allocation over the entire 3G/4G Mobile Network keep the same PSCs/PCIs like for the CoSector Twin cell PSC/PCI allocation;

7.42 56.031
- Update the module M2.2 (PSC/PCI allocation Audit and Optimisation):
1: Improve the evaluation of the PCSs/PCIs optimum allocation algorithm over the entire 3G/4G Mobile Network;
This approach is based on the Site Priority concept which is evaluated based on how many sites are detected inside a circle area radius (Km) of each site and its Inter-Sites average distance area for all the sites detected inside that area;
- Update the module M2.3 (2G BCCH allocation Audit and Optimization):
1: BCCHs Audit process is extended to the evaluation of BCCHs optimum allocation over the entire 2G Mobile Network in order to maximize the distance for the BCCH CoChanel reusage and avoid coBSIC case, too;
This approach is based on the Site Priority concept which is evaluated based on how many sites are detected inside a circle area radius (Km) of each site and its Inter-Sites average distance area for all the sites detected inside that area;

7.42 56.029
- Update the module M1.1 (Generate and update Agileto's database):
A warning message is pop-up to prevent the input external Excel file name reserved by Agileto tool: "MobileNW_Config.xls" or "MobileNW_Config_Template.xls"

7.42 56.028
- Update the module M2.2 (PSC/PCI allocation Audit and Optimisation):
Add a new function (button) to Map in Google Earth the 3G/4G allocations PSCs/PCIs and generate 3G/4G Beacon_Cells:
1: Allocation -> Draw points with the same color for the 3G/4G Cells sharing the same PSC/PCI;
2: Conflict -> Draw color lines between each 3G/4G Cell and the closest 3G/4G Cell sharing the same PSC/PCI;

7.42 56.027
- Update the module M1.2 (Generate NW cells/sites objects in MI + GE):
1: -> Insert a new "Beacon_Cells" layer in addition to already existing Mobile_NW technology layers (2G/3G/4G);
This new layer (Beacon_Cells) presents on Google Earth map the Beacons 2G/3G/4G (BCCH/PSC/PCI) Allocation and Conflict evaluation results generated by the new options added to the related Modules M2.2 and M2.3;
- Update the module M2.3 (2G BCCH allocation Audit and Optimization):
Add a new function (button) to Map in Google Earth the 2G allocations BCCHs and generate 2G Beacon_Cells:
1: Allocation -> Draw points with the same color for all the 2G Cells sharing the same BCCH;
2: Conflict -> Draw color lines between each 2G Cell and the closest 2G Cell sharing the same BCCH;

7.42 56.025
- Update the module M4.3 (Process Drive Test log files [NEMO, TEMS]):
1: Correct the previous NEMO (*.nmf) parser limitation in order to read & include as well the data related to the last RF server reported into one measurement reported line;

7.42 56.024
- Update the module M4.1 (Network Optimisation based on Drive Tests):
1: Perform autocomplete column correspondence (prefill) with the Latitude/Longitude/Timestamp inputs into the form if the Drive Test input file (*.csv) has the standard names allocated for these columns;

7.42 56.023
- Update the module M4.1 (Network Optimisation based on Drive Tests):
1: Update the parser which read the input Drive Test data file in order to discard the abnormal lines where expected data is missing;

7.42 56.022
- Update Agileto core module (responsible in working with Excel):
1: Set to 3 the default number of sheets for a new Excel workbook which will mitigate the issues encountered on some Agileto output results in Excel;

7.41 56.022
- Update the module M4.1 (Network Optimisation based on Drive Tests):
1: Minor correction in order to overcome some Excel output missing data due to some unexpected behaviour generated by specific MS Excel versions;

7.41 56.021
- Update the module M4.3 (Process the Drive Test log files [NEMO, *.nmf]):
1: Correct a (missing) text syntax from the code which generate an error in some cases;
2: Upgrade the NEMO parser and the data collection in order to be independent of the *.nmf file version;

7.41 56.020
- Update the module M1.1 (Generate and update Agileto's database):
1: Update the parser for NSN 4G dump *.xml in order to retrieve the 4G cells pMaxOwnCell (pRefSignal) either from the standard table "LNCEL" or from the new table called "SIB" up to the dump version;
2: Correct the options/keys available into the window/form which allows to update Agileto's 3G cells database based on the external Excel file;

7.41 56.018
- Update the parser for NSN 2G dump *.xml in order to extract the 2G cell BCCH channel (ARFCN) from TRX database based on the 'channel0Type' parameter and not anymore on 'preferredBcchMark' which is optional;

7.41 56.017
- Update the parser for the new NSN 4G dump *.xml in order to retrieve the 4G cells "earfcnDL" frequencies from another new table called "LNCEL_FDD";

7.41 56.016
- Update the module M1.1 (Generate and update Agileto's database):
1: Add the new option to Export & Import Agileto Templates (2G/3G/4G) when generating/updating the database based on external Excel files;
This new option will allow to distribute the same templates along different engineering teams in order to speed up the working process and to have the same Agileto references;

7.41 56.015
- Update the module M1.1 (Generate and update Agileto's database):
1: Correct a small error to update properly Agileto's 3G database for all DL_UARFCNs values (written as a standard comment at the end of the cells declarations) when importing cells from an External Excel file where the input frequencies are given as DL_UARFCN numbers;
- Update the module M4.1 (Network Optimization by using the Drive Test):
1: Improve the accuracy of detecting the Wrong Planning allocation Cells Index (BCCH/PSC/PCI) by grouping under the same Wrong Planning Case detected all the Target Cells detected and sharing the same Cell Index;
Under the new mechanism all the Wrong Planning cases detected are generated and displayed in Google Earth very intuitive by presenting under each specif case all the Source and Target cells;

7.41 56.013
- Update the module M4.1 (Network Optimization by using the Drive Test):
1: Overcome [with a notification message] the error generated by the special case when no GPS info is detected into the Drive Test file;

7.41 56.012
- General improvements + reminder that Agileto BASIC licence does not support all features and outputs like the ENHANCED licence;

7.41 56.011
- Update the module M4.1 (Network Optimization by using the Drive Test):
1: Improve the accuracy of detecting the Wrong Planning Index allocation (BCCH/PSC/PCI) which lead in some particular cases to errors in execution;

7.41 56.010
- Update the module M4.3 (Process Drive Test log files [TEMS, Nemo]):
Generate the Summary Post-processing file containing all the details regarding the Inputs and Outputs;
- Update the module M2.3 (2G BCCH allocation, Audit and Optimization):
When evaluating the Bands2G_limits for each band exclude the 2G cells which do not have datafilled the Geographically Coordinates (Latitude + Longitude);

7.41 56.008
- Always allow the upgrade for free (with a valid Licence) from Agileto GOLD Edition (freeware) to Agileto PRO Edition (professional):
It is now allowed always to acquire online an Agileto PRO Edition 'BASIC' Licence although a valid Agileto GOLD Edition licence is still detected into the system;

7.40 56.008
- Agileto's Updater (.exe) file has been updated to the new version (2.16) by improving Agileto Communicator exchange messages process for the end user.
If the end user already answered to a certain message received from Agileto team then do not more display that message until a new message is received;

7.39 56.008
- Agileto's Updater (.exe) file has been updated to the new version (2.15) which helps transmitting Agileto's user feedback;
If multiple feedbacks are sent by an Agileto's user while there is no internet access, all the feedbacks are concatenated and transmitted automatically in a single message when the internet access becomes available;

7.38 56.008
- Agileto's Updater (.exe) file has been updated to the new version (2.14) which may be executed to download and install the tool automatically;

7.37 56.008
- Correct a small bug in order to update properly into Agileto database the info when 2G database has been updated;
- Agileto's Updater (.exe) file has been updated to the new version (2.13);

7.36 56.006
- Minor update to reflect in 'About' section (under the version: Core + Engine) Agileto PRO Edition tool worldwide usage;
Ping the worldwide Flag Counter usage with a new counter dedicated only for Agileto PRO Edition (FC_PRO.gif);

7.36 56.005
- Agileto's Install (.exe) file has been updated to the new version (2.2);
- Agileto's Updater (.exe) file has been updated to the new version (2.12);

7.35 56.005
- Agileto's Help file has been upgraded to the new version (7.19) in order to perform small corrections + video training links updates for the modules M2.1, M2.4, M3.2, M3.4;

7.34 56.005
- Update the module M2.4 (Network comparison between two OMC dump files):
1: For the better reference on 3G technology include into the final Audit results the following new 3G Cells info: LAC/PwrCPich/MaxTxPwr;

7.34 56.004
- On Huawei 2G dump files (CFGMML *.txt) extract additionally 2G Site Name info corresponding to all 2G Cells declarations @ BSC level;
- After executing the modules M2.1 (OMC dumps Audit & SanityCheck) and M2.4 (Network comparison between two OMC dumps) open minimized in background Windows Explorer at the path location where the results have been saved;

7.34 56.003
- Agileto Help file has been updated to the new version (7.18) reflecting better the following modules:
a) M3.2 (Neighbors database -> MapInfo & Google Earth);
b) M3.4 (Automatic Neighbor Relation).

7.33 56.003
- Update the module M3.4 (ANR: Automatic Neighbor Relation):
1: Generate a dedicated output folder results based on the run time + other minor corrections;

7.33 56.002
- Update the module M3.4 (ANR: Automatic Neighbor Relation):
1: Add multiple input options which allows ANR to:
1.a) Modify the Coverage Points (P2,P3,P5,P6,P7,P8) settings [Distance & Azimuth];
1.b) Generate the neighbors reciprocally [case of IntraTechnology];
2: Generate the summary ANR file (*.txt) containing all the main Inputs/Outputs parameters for the future reference;

7.32 56.001
- Update the module M3.4 (ANR: Automatic Neighbor Relation):
1: Improve the algorithm to approximate properly the Co-Site cells even when the cells do not have exactly the same coordinates which can lead to a distance error up to 30m;

7.33 56.000
- Update the module M3.4 (ANR: Automatic Neighbor Relation):
1: Improve the evaluation of the potential neighbors by introducing the following new algorithms:
a) evaluate better the Inter-Cell Distance to be considered for each Source Cell;
b) Evaluate new cases/points (P5/P6/P7) to be evaluated if they are falling inside BW of the target cells, as following:
 P5 -> on cell azimuth at the 3rd part of the distance [PtMainCvg] concerning the main coverage point P4;
 P6/P7 -> +/- half of the beamwidth against the cell azimuth at the distance 0.7 * PtMainCvg;

7.33 55.999
- Update the module M3.4 (ANR: Automatic Neighbor Relation):
1: If the Reference Neighbors files are provided as input then provide into the output ANR results the neighbors to be deleted (marked with "-1") in addition to the neighbors to be added (marked with "1");
- Update the module M3.2 (Neighbors database -> MI + GE converters):
1: Allow the better Google Earth neighbors representation after performing a comparison between two neighbor sets [Reference and New] with neighbors outputs in 3 categories, as following:
 A) Common neighbors [target cell color];
 B) Added Neighbors [red color];
 C) Deleted Neighbors [black color];
This is very suitable for the output of the ANR module (M3.4) which allows the translation of the input neighbors special column, as following:
 A) Value <> "1" or "-1" -> Neighbor line color is the same with the target cell color;
 B) Value = "1" -> Neighbor line color is overwrite as red;
 C) Value = "-1" -> Neighbor line color is overwrite as black;

7.33 55.996
1: Upgrade the support for the new 3G Huawei dump format (*.txt) related to 'UEXT2GCELL' declarations;

7.33 55.995
- Update the module M4.1 (Network Optimization by using the Drive Test):
1: Display the Drive Test progress evolution while generating the grid lines related to the spatial binning operation;

7.32 55.994
- Update the module M4.1 (Network Optimization by using the Drive Test):
1: Improve the Drive Test parsing and processing algorithms in order to overcome limitations which occur when selecting spatial binning with very low bin size [1m/2m] over very large geographical Drive Test area;

7.32 55.993
1: Support for using Google Earth Pro on 64 bit since it was free released on February 2018;

7.32 55.992
1: Update the last year core release (2018) + other minor upgrades.

7.31 55.992
1: Update the parsing of the OMC 2G dump files in order to accept the input files which do NOT include the 2G2G neighbors declarations;

7.31 55.991
- Update the module M3.4 (Network Neighbors Auto generation):
1: Add into the final neighbors results the Frequency Layers which the Source and Target neighbors cells belongs to;

7.31 55.990
- Update the module M2.1 (OMC/OSS dumps files -> Audit and Sanity Check):
1: Get all the neighbors declarations headers extracted from OMC/OSS dump files on the right format to be accepted directly as external neighbors declarations files;
- Update the module M3.4 (Network Neighbors Auto generation):
1: Add into the final neighbors results the clusters info which the Source and Target neighbors cells are belonging to;

7.31 55.988
- Update the module M4.1 (Network Optimisation by using the Drive Test):
1: Treat properly the special cases when NO measurements input data are provided for some Drive Test input lines -> Correct the previous approach which erronated made these cases to be displayed for ASet size with red points (corresponding to ASet=6);
- Update the module M2.2 (PSC/PCI Audit and Optimisation):
1: Add a New button on the form which allows to export in Excel all the PSCs/PCIs changes performed into the current session;
- Update the module M2.3 (BCCH Audit and Optimisation):
1: Add a New button on the form which allows to export in Excel all the BCCHs changes performed into the current session;

7.31 55.985
- Update the module M4.1 (Network Optimisation by using the Drive Test):
1: If one input technology is 2G the user can select how BSIC info data is provided (BSIC = 'NccBcc' join values OR BSIC = 8 * Ncc + Bcc);

7.31 55.984
1: Upgrade the parser algorithm for Ericsson 3G dump files (*.xml) in order to get the right RNC name(s) when this is not declared @ 'un:RncFunction' (as usualy);

7.31 55.983
1: Update the algorithm which process Ericsson 2G dump files (*.log) in order to correct duplicated cells in Agileto database coming from BSC 2G External cells declarations;

7.31 55.982
1: Agileto is accepting now (parsing successfuly) as input Ericsson 2G dump files in *.log formats;
- Update the module M4.3 (Process the Drive Test log files [Nemo, TEMS, etc]) for TEMS part, as following:
1: Introduce a new 'Rule' by two (2) new inputs related to the 'Reference Column Number' (1->activate the Rule [boolean:True/False] + 2->provide the Reference column number); 
When this Rule is activated the Output drive test file will NOT allow storing from the original drive test file two consecutive lines having the same info/data into the 'Reference Column Number'; This option is used usually to filter out the desired Messages (lines) which are repeated on the same Timestamp (usually the Reference column number = 1 [Timestamp]).

7.31 55.979
1: Agileto Help file has been updated (major update) to the version 7.17 (including support for the new develloped module M3.4 + other minor updates);

7.30 55.979
- Update the module M3.2 (Neighbors database -> MI + GE converters):
1: Evaluate automatically if the neighbors reciprocity are declared and display the results as appropiate in GE [add "S" (SingleWay) (when no reciprocity is detected)]
2: Allocate a special column [Special] where if a specific neighbor relation is detected with "1" then this neighbor will be represented in GE with a red line; very usefull when representing the comparizon between two set of the neighbors declarations;
- Update the module M3.4 (Network Neighbors Auto generation):
1: New option(s) created to provide as input for comparison the reference Neighbors declaration file(s). The optimum neighboring configuration is compared with the reference and the differences are flaged into the output file(s). The neighbors resulted this way may be mapped in GE with the module M3.2 (using the 'Special' field) and the "missing" neighbors will be displayed with red colors;

7.30 55.976
- Devellop a new approach when parsing Nokia *.xml dumps (2G/3G/4G) which leads to an important increase in speed while parsing the files; Example: Before the change a number of 6 *.xml Nokia 4G dump files took ~ 2.5 hours to process while now the same files take less than 7 minutes to complete!

7.30 55.974
- Update the module M3.2 (External Neigbors database => Google Earth):
1: Auto-Evaluate if the neighbors have the reciprocity declared and display negative results in GE [S->SingleWay (no reciprocity)];
2: Allocate a dedicated input column [Special] where if the neighbors are detected with the value = "1" they will be presented in GE with red lines to emphasize them; very usefull when representing the comparison between two set of the neighbors declarations;
- Update the module M3.4 (Automatic Neighboring evaluation):
1: New option created to provide as input for comparison the reference Neighbors declaration file(s). The final neighboring results will include additionally information presenting the comparison with the reference neighboring file(s) and the differences are written into a new columns & files. The neighbors resulted this way may be mapped in GE with the module M3.2 (using the 'Special' field) and the "missing" neighbors will be displayed with red colors;

7.30 55.972
- Update the module M1.1 (Generate and update Agileto's database):
1: Change the input Keys background colors in Pink when no Key has been yet provided as input;
2: Activate as potential Key to be selected the field 'Cell_Name' only in case of updating Agileto's database based on the common cells detected in both inputs (External Excel + Agileto DB);
- Update the module M3.4 (Automatic Neighboring evaluation):
1: When evaluating the median Inter-Sites distance take only the sites which have the minimum Inter-Site distance < 7km in order to avoid izolated cases which are not representative;
2: Correct a type error into the algorithm (error: Long2G was typed as Long3G) which finally was leading to some missing potential neighbors;
- Update the module M4.1 (Network Optimisation by using the Drive Test):
1: Associate to the button "Join DT 'txt' files" the NEW function which join/merge all the *.txt/*.csv files from one directory into one single output file;

7.30 55.969
- Update the module M1.1 (Generate and update Agileto's database):
1: When generating Agileto's database based on external Excel file for each technology [2G/3G/4G]:
1.a) Provide dinamically with red colors (and bullets) the common fields (key) which need to be provided first by the user; afterwards the other columns/info may be provided but the common (key) fields will be emphasized with red color (Ex: Cell_Name or GlobalCID or LAC+CID or RncId+CellId);
1.b) Up to the Keys's status selection [LocalCID/CellName/...] enable/disable for the user input all the others columns associations (excepting the Keys);

7.30 55.968
- Update the module M3.4 (Automatic Neighboring evaluation):
1: Optimize the Source-Target neighbors detection when one is pointing to the other one and they are detected at a small distance compared with the median Inter-Cells distance;
2: Discard from the final results the Co-Cells Neighbors declarations (proposed by mistake into the previous version);

7.30 55.967
- Create the new module M3.4 (Automatic Neighboring evaluation):
1: This module will generate for the entire network (2G/3G/4G) the optimum neighbors relations based only on the Cells positions recorded into Agileto's database (Latitude/Longitude/Azimuth) + few other specific inputs which can be used with the default values or they can be changed by the user;
- Update the module M4.1 (Network Optimisation by using the Drive Test):
1: Eliminate from analysis the lines from the input Drive Test file which contains GPS values out of the normal range (Ex: -9999.9) which previously lead to an error;

7.30 55.964
1: Restore as M4.4 the old module "Neighbors Optimisation based on PSCs Detected (*.txt)";
2: Insert the new module M3.4 "Automatic Cells Neighbors 2G/3G/4G generation" -> Not yet enabled as the working is still on-going;
3: Change the Licence algorithms in order to accomodate the new modules;

7.27 53.952
1: Develop a new dedicated module M4.3 to Process the Drive Test log files (NEMO, TEMS, etc);
2: Agileto Help file has been updated (major update) to the version 7.15

7.26 53.022
- Update the module M4.1 (Network Optimisation by using the Drive Test):
1: Increase from 250 to 350 the Max Nr of Neighbors declarations per Cell/technology/frequency in order to accomodate such (rare) cases for some mobile operators;

7.26 53.021
- Update the modules M2.2 + M2.3 -> 2G(BCCH) / 3G(PSC) / 4G(PCI) Audit + Optimisation:
1: Evaluate automatically the 2G Optim BCCH by selecting into the analysis only the potential Target 2G Cells which don't have the same BSIC like the 2G Source Cell;
2: Provide a New option to input a *.txt file containing the set of 2G(BCCHs) / 3G(PSCs) / 4G(PCIs) reservation values (one value per line) which should not be automatically selected by the ordinary 2G/3G/4G cells;

7.25 53.017
- Update the module M4.1 (Network Optimisation by using the Drive Test):
1: Increase to (minimum) 6 decimals precision the Latitude & Longitude Drive Test measurement points to be used internally and displayed into output reports including MI & GE;

7.25 53.016
- Improve the spead parsing of the 4G Nokia *.xml dump file;

7.25 53.015
- Update the secondary Progress display form in order to overcome the particular error which raises when NO cases are to be displayed;

7.25 53.014
- Update the module M3.1 (MI neighbors changes -> OMC) for the 3G technology:
1: Convert better the 3G2G neighbors changes operated in MapInfo (*.csv) to OMC (*.xls);

7.25 53.013
- Update the module M2.4 (Network comparison between two dump files) for the 2G & 3G technologies:
Technology 3G:
1: Split more intuitive the background color for the summary 3G-3G IntraFr/InterFr + 3G2G neighbors related to the OLD dump file;
2: Reorganize the 3G3G and 3G2G detailed neighbors presentation;
Technology 2G:
1: Reorganize the 2G2G detailed neighbors presentation;

7.25 53.012
- Update the modules M3.1 + 3.2 (Generate Neighnors in MapInfo and Google Earth):
1: Display the second progress barr presenting the neighbors process evolution;

7.25 53.011
- Update the module M1.1 (Generate and Update Agileto database):
1: Store and update the 3G + 4G frequencies (DL-ARFCN) into Agileto database (as standard formatted comments) when these are provided as input from External Excel files;

7.25 52.9
- Update the module M1.1 (Generate and Update Agileto database):
1: Improve Agileto's database generation when getting the data from 'huge' External Excel files;
2: Display the second progress bar window when updating the Cells from an External Excel file;

7.25 52.7
- Update the end user experience while parsing the 2G Nokia *.xml OMC snapshot file:
1: Display supplementary into the title of the second progress bar the BSC name of the BSC who's data is reading (Sites/Cells/Trx/N2G2G);

7.25 52.6
- Update the support and parsing of the 2G NSN (Nokia) *.xml OMC snapshot file:
1: Agileto inputs accepted may be one or multiple 2G OMC *.xml Nokia files and each file may contain data from one or multiple BSCs;

7.25 52.5
- Add a dedicated button to view Agileto Outputs (equivalent to M1.4);
- Make visible the button to launch Agileto DEMO_PROJECT help file when the DEMO_PROJECT is selected as Agileto Active Project;

7.25 52.4
- Modify the way how the country Flags Agileto Worldwide usage image is displayed into Google Earth (GE), as following:
1: Make by default Not visible the Screen Overlay image displayed in GE presenting Agileto Worldwide usage;
2: Present into Agileto Worldwide usage image two (2) lines containing the most important 18 flags (countries) usage;

7.25 52.30
- Any user can monitor now Agileto worldwide usage into the related image (updated when Agileto is started and connected to internet) available into "About" tool's window;

7.22 52.30
- Anybody can monitor Agileto worldwide usage (updated) on the right-top area of the Google Earth window when loading different outputs generated by Agileto (Mobile Network, Drive Test, Neighbors, KPIs, etc); the results are based on the country's Flag counters (http://flagcounter.com) collected since 13en of March 2017;

7.22 51.999
- Improve the module M4.1 (Network Optimisation based on the Drive Test) as following:
1: Allow the user to modify the Standard Thresholds Legends for each Technology (2G:RSSI, 3G:EcNo/RSCP, 4G:RSRP/RSRQ) into the file "Config.txt" which should be located at the same tool's installation path location.
2: If the file "Config.txt" doesn't exist then it will be generated automatically by the tool with the default Legend threshold values for each metric when the module M4.1 will be running for the next time; afterwards, the user can modify the Legend thresholds into this file as per desired and the new threshold values will be used by the toll onward;

7.22 51.998
- Improve the module M2.2 to perform 4G(PCIs) analysis and optimisation allocation in extention to the existing 3G(PSCs) similar feature;

7.22 51.997
- Improve the support for processing the Drive Test files (*.txt/*.csv) which may result after exporting the data from the TEMS Drive Test log files (*.fmt);

7.22 51.996
- Update the parsing for ALU 3G snapshot file(s) by extracting the real RNC major version number since LTE & WCDMA common approach occured;

7.22 51.995
- Display the second progress barr while loading the the 3G OMC snapshot file(s) presenting the 3G Cells + 3G-3G/3G-2G Neighbors reading info;

7.22 51.992
- Update the parsing of the 4G NSN (Nokia) *.xml snapshot file by extracting into Agileto database all the 2G/3G/4G target Cells from the neighbors declarations even they were not declared @ eNB as refererence;

7.22 51.991
- Improve the parsing of the 4G NSN (Nokia) *.xml snapshot file by increasing the speed and the accuracy when presenting the 4G-4G neighbors Target attributes (eARFCN, PCI, TAC);

7.22 51.990
- Improve the support for processing the Drive Test  measurements [Mobile & Scanner] Nemo file (*.nmf), as following:
1: All the Nemo (*.nmf) files located on the same folder with the file selected will be processed automatically;
2: The output processing Drive Test file(s) will have the standard input Agileto DTO format and will get the name = directory name (where the selected file resides) + "_" + "M" or "S" (standing for Mobile or Scanner) + Technology (2G/3G/4G) + "_" + Frequency Number (DL);
- Update the parsing of the 4G Ericsson dump files (*.xml) as following:
1: Retrieve properly the Cell Ref TxPower;

7.22 51.988
- Update the parsing of the 4G Ericsson dump files (*.xml) as following:
1: Retrieve the real 4G PCI cells allocation instead of the PCI group allocation [like it was before];

7.22 51.987
- Improve the parsing of the 4G NSN (Nokia) *.xml snapshot file;
- Display the second Progress bar evolution while different eNBs info are read from the 4G *.xml snapshot file;

7.22 51.982
- Update and improve the parsing of the 4G Ericsson dump files (*.xml);

7.22 51.980
- Update the parsing of the 3G dump files as following:
1: Improve the detection of the DL_UARFCN numbers recorded inside of the 3G dumps in order to evaluate properly if a certain DL_UARFCN belongs to 900MHz or 2GHz band;
2: Improve the support for Ericsson (E//) dumps to detect properly RNC_Name(s) even when this info is missing from the RNC attributes deffinitions;

7.22 51.978
- Update the module M3.2 (Neighbors database -> MI + GE converters):
1: Represent properly for MI + GE all types of the IRAT neighbors, including: 2G3G + 2G4G + 3G4G;

7.22 51.977
- Recognise and work properly on the last versions of Windows 8 and Windows 10, too.

7.22 51.976
- Update the parser related to the OMC snapshot file 4G technology, vendor Alcatel-Lucent (ALU) as following:
1: Convert from binarry to decimal the TAC info related to the 4G Cells;
2: Convert from binarry to decimal the NCC + BCC info related to the 2G Cells declared as neighbors to the 4G Cells;

7.22 51.975
- Update the 'License Information' form to display Agileto's unique 'ID' which should be provided by the end user to Agileto sales team (to activate his license) when the License purchase process has been completed.

7.22 51.974
- Update the module M2.2 (PSC Allocation -> Audit & Optimisation):
1: Enable to copy the Cells info results from the form;
2: Color per sections the header line of the data exported in Excel from the data displayed into the form; 
- Update the module M2.3 (BCCH Allocation -> Audit & Optimisation):
1: Add into the the dedicated BCCH form the info related to the 2G Cell Names for the CoChannel/InfChannel/SupChannel (to be displayed additionaly when hover the mouse over the 2G CID|LAC boxes);
2: 2G Cell Names related to the CoChannel/InfChannel/SupChannel mentioned above will be exported into dedicated columns in Excel (if the export option in Excel of the data window is executed);
3: Color per sections the header line of the data exported in Excel from the data displayed into the form;

7.22 51.972
- Update the module M3.2 (Neighbors database -> MapInfo + GoogleEarth converter):
1: Correct a small bug into the input form to update properly the text presenting the 'Target' cell (instead of the 'Source');

7.22 51.971
- Multiple modules are affected as following:
1: Improve the accuracy/detection of the 2G/3G/4G cells into the database when it was selected the case to load only those Cells detected into OMC snaphot files;

7.22 51.970
- Update the module M1.3 (NW boundary -> Border Cells detection per techno):
1: Generate the Border Cells detected for each technology in Google Earth, too;
2: Update the code in order to display correctly the outputs results per each 4G frequency layer;
- Update the module M1.2 (Generate NW cells/sites objects in MI + GE): 
1: Insert a new "Border_Cells" layer in addition to already existing Mobile_NW technology layers (2G/3G/4G); this new layer (Border_Cells) may be calculated/updated anytime from the module M1.3 and it is usefully to detect and confirm visually the Border Cells (per technolgy) which should be provided with a specific class of parameters;

7.22 51.968
- Update the module M4.1 (NW Optimisation based on the Drive Test):
1: Improve the overall results presentation in MI & GE by rounding the metrics values to max two (2) digits after the decimal point; Ex: RxLev after aggregation may lead to the value = -81.2352435 => This case the value -81.24 will be presented (round to 2 digits);

7.22 51.967
- Update the module M4.1 (NW Optimisation based on the Drive Test) to:
1: Improve the Drive Test Audit's outputs especially related to the drive tests involving two technologies (ex: 4G->3G, 3G-2G) and consequently two input drive test files;
2: Improve the code in order to solve the issues related to the generation of the legends when under specific circumstances the legends were not displayed properly;

7.22 51.966
- Update the module M4.1 (NW Optimisation based on the Drive Test) in order to improve the accuracy output info (presented into Google Earth output files) related to the Drive Test Audit regarding the specific measurements points and their associated number of occurances for the following cases:
a) No GPS data
b) GPS Static measurements
c) No Source parameter data
d) No Target parameter data

7.22 51.965
- Update the module M4.1 (NW Optimisation based on the Drive Test) in order to solve a bug which leads to an error while reading the external database neighbors file provided as input;

7.22 51.964
- Update the module M4.1 (NW Optimisation based on the Drive Test) in order to analyse and buid properly the Drive Test Analysis (DTA) case, when NO spatial binning is selected;

7.22 51.963
- Update an internal routine which occasionally leads to an error while generating the mobile network Cells or KPIs (up to the specific PC configuration settings);

7.22 51.962
- Update the core of Agileto PRO Edition in order to deal better with the new Agileto DEMO_PROJECT just released (V2.00) wich is supporting now all the technologies (2G/3G/4G). For the best results please download and reinstall Agileto DEMO_PROJECT from: http://www.agileto.com/setup/Agileto_DEMO_PROJECT.exe;

7.21 51.962
- Update the module M3.2 (Neighbors database -> MapInfo + GoogleEarth converter) in order to correct a small bug which lead in some cases to present in GE the neighbors priorities as "0" instead of the real values;
- Improve the detection of the number of 3G & 4G cells into the tool's database in special cases when for some reasons the 3G LocalCellId or 4G GlobalCellId fields are not datafilled.

7.21 51.960
- Update the core of Agileto PRO Edition in order to display a sigle time per day the message through the Communicator;

7.20 51.960
- Update the module M2.1 (Audit & Sanity Check) for the Huawei 3G technology, as following:
1: Correct a bug in order to retrieve the real 3G Cells PCPICH values instead of the Minimum PCPICH values how were reported in some cases for the new 3G snapshot version files;

7.20 51.959
- Update the core of Agileto PRO Edition in order to display properly the messages transmitted through the Communicator;

7.19 51.959
- Update the module M4.1 (NW Optimisation based on the Drive Test) as following:
1: Minor changes into Google Earth file names display;
2: Associate the RSCP legend (instead of the EcNo legend) for the 3G Top1 coverage points cells presentation in Google Earth [to be similar like for the Full Coverage cell points presentation];
3: Adjust automatically the optimum GE zoom area in order to see all the cells related to all the links provided by the ActiveSet "RePlay" option;
- Update the embeded link to the GE video Agileto General presentation from youtube: https://youtu.be/OARXUx1hhrQ

7.19 51.957
- Modify the 2G cells layer GSM900 [F1] color from "blue" to "dark blue" in order to distinquish better the cell layers when many technologies [2G/3G/4G] and many frequency layers are displayed;
- Update the module M4.1 (NW Optimisation based on the Drive Test) in order to detect properly the specific Drive Test cases when one single input Drive Test file contains two technologies [Ex: 3G-2G];

7.19 51.955
- Update the module M5.1 (map cells KPIs into MapInfo and GoogleEarth) for the 2G technology in order to forbid selecting as input the KPI column until CID + LAC were not selected;
Notice: on 2G technology (for one mobile operator) the unique identification for one 2G cell is always given by: CID + LAC;

7.19 51.954
- Update Agileto software in order to support the parsing of the OMC snapshot file 4G technology, vendor Alcatel-Lucent (ALU);
- Correct the very special cases when the cells "0" were inserted into Agileto 2G/3G/4G database while running the module M1.1 (Generate/Update Agileto database);

7.19 51.952
- Update the module M4.1 (NW Optimisation based on the Drive Test) as following:
When loading the reference neighbors declarations from an external file or from an OMC snapshot file => select automatically as reference only the neighbors declarations which have the target cells on the same target frequency as per selected initially into the input parameters [exclude from reference all the other declarations].

7.19 51.951
- Update the module M4.1 (NW Optimisation based on the Drive Test) as following:
1: Modify/Update the link colors for the potential S(source)->T(target) neighbors cells combinations which do not meet the minimum "weight" criteria as following:
   a) [light Pink] -> S->T combination detected which are declared as neighbors (with Low Importance);
   b) [light Green] -> S->T combination detected which are NOT declared as neighbors (with Low Importance);
2: Correct a typing code error which leads to wrong output target 4G Cells Names/PCI into 4G-4G Neighbors analysis results;
- When decoding the OMC4G snapshot files evaluate the 3G Frequency layers associated with the new 3G cells declared into OMC4G snapshot files according with the 3G DL UARFCN frequencies values detected into Agileto 3G database (as per the standard Excell cell comment);

7.19 51.949
- Update the module M3.1 (OMC dump file to -> MapInfo + GoogleEarth [neighbors converter]) in order to support OMC input snapshot/dump files from all technologies [2G/3G/4G];

7.19 51.948
- Update the module M1.1 (Generate/Update Agileto database) in order to allow updating Agileto's database (2G + 3G + 4G) with priority based on the following External Excel inputs (in case they are provided they unique identify the cell into that technology):
1: 2G Technology: LAC + Cell_Id
2: 3G Technology: Rnc_Id + Cell_Id
3: 4G Technology: eNodeB_Id + Cell_Id

7.19 51.947
- Update the module M4.1 (NW Optimisation based on the Drive Test) by updating the following (cells) links colors presentations in Google Earth, as following:
1: Neighbors Proposals [NW Cell target legend color] -> Neighbors cells Sorce-Target Combinations detected into the Drive Test input file(s) by Agileto tool;
2: Neighbors Missing/Additions [Red] -> Neighbors proposed to be Added;
3: Neighbors Missing LI [light green] -> Neighbors missing with Low Importance which do not meet the minimum imposed weight criterias and they will be presented with the light green color;
4: Neighbors Deletions [light pink] -> Neighbors Declared which become candidates to be Deleted;
5: Overshooters [light green] -> Links between the Overshoor cell and all its associated Affected/Polluted Cells;

7.19 51.946
- Update the module M1.2 (Generate MapInfo & GoogleEarth cells/sites objects) by generating (in GE) a new NW Legend which presents the specific cells colors for all technologies [2G/3G/4G] and all frequency layers;
- Update the module M4.1 (NW Optimisation based on the Drive Test) in order to deal with the very special cases when no Cells associations/identifications can be performed based on the Project configuration file AND the Drive Test input measurements file(s); On these special cases the execution of the module is aborted;

7.19 51.944
- Update the module M4.1 (NW Optimisation based on the Drive Test) in order to support the 4G technology too; this new release may admit as inputs all kind of the Source-Target technology combinations [Ex: 4G-4G, 4G-3G, 4G-2G, etc];
- Update the parsing of the Huawei 3G snapshot files as following:
1: Collect the real neighbors declarations priorities (3G3G + 3G2G) if they are declared inside the snapshot (sometimes they are not declared); the neighbors declarations which have not declared the priorities inside of the snapshot file are presented/allocated by Agileto as the neighbors order declarations with negative sign; those priorities which are declared are presented accordingly;
2: Correct a bug which was translated sometimes in wrong/missing 3G neighbors target declarations when the 3G Cell RNC Target was different than the 3G Cell RNC Source.

7.19 51.942
- Update the module M3.2 (Convert Neighbors database *.csv into MapInfo and Google Earth formats) by accepting all types of input technology combinations [Ex: 4G4G, 4G3G, 4G2G, 3G4G, 3G3G, 3G2G, 2G4G, 2G3G, 2G2G]; 

7.19 51.940
- Update the module M2.4 (NW comparison between two OMC snapshots files) by checking and presenting (if detected) the main Cell parameters discrepancies between the Cells detected in both OMC snapshots (New vs Old) for each technology, as following:
2G: BCCH/BCC/NCC/Pwr
3G: PSC/LAC/UARFCN/PwrCPich
4G: PCI/TAC/eARFCN/PwrRef

7.19 51.939
- Update the module M2.4 (NW comparison between two OMC snapshots files) to support the 4G Technology (in addition to the 2G + 3G Technologies, already supported);

7.19 51.937
- Correct a bug which lead to 'Overflow' when loading OMC_4G snapshot file(s) containing a high number (>750) of eNodeB(s);

7.19 51.936
- 4G Technology: Improve the detection (into OMC4G snapshot files) of the External 2G/3G/4G cells declarations by an advanced searching method which will retrive whenever possible the CellName(s) <> Null Name (sometimes the Operators do not datafill the CellName info for some External Cells declarations); this improvement has a great impact on many results especially generated by the modules M1.1 (Generate/Update Agileto database) and M2.1 (Audit & Sanity Check); 

7.19 51.935
- Update the module M2.1 (Audit & Sanity Check) in order generate and present the discrepancies (CellsToUpdate-2G/3G/4G) detected on cells declarations for each technology [2G/3G/4G] with regards even to the Cell_Name; A new flag (Param mismatch) was introduced into the generated discrepancy files in order to signalize if the discrepancy detected is related to a parameter mismatch (other then the Cell_Name);

7.19 51.934
- Update the module M2.4 (NW comparison between two OMC snapshots files) for 2G Technology in order to:
Support the wrong Mobile Operator 2G Cells declarations @ BSCs levels, when the same 2G cells (LAC+CID) are declared multiple times in several BSCs (these special cases may be detected by Agileto after the execution of the modules M1.1 [Generate/Update Agileto database] or M2.1 [Audit & Sanity Check]);

7.19 51.933
- Update the module M2.4 (NW comparison between two OMC snapshots files) to support 2G Technology, too (in addition to the 3G Technology, already supported);

7.19 51.932
- Correct some errors which may lead to some eronated results after the execution of the module M2.1 (Audit & Sanity Check) in case of 4G technology;

7.19 51.931
- Update the module M2.4 (NW comparison between two snapshots) by adding the Cells detected Only into the Old OMC snapshot file at the end of the list presenting the Cells detected into the New OMC snapshot file;
- Perform a better/unique correlation between the 3G/4G frequencies [DL UARFCN/eARFCN] stored into OMC snapshot files and the frequency layers used by Agileto database [1 to 10]; the correspondence between the frequency layers used by Agileto database and the real 3G/4G frequencies stored into OMC snapshot files is written into a standard formatted comment on the first cell (in Excel column 1) after the last 3G/4G mobile network cells;

7.19 51.928
- Correct a mistake (case: OMC input file = 3G technology) which may lead to present wrong 3G-3G neighbors Target cells when they do not belong to the same RNC like the Source Cells;

7.19 51.927
- Correct a bug in the module M1.1 (Generate & Update Agileto database) which block it in some situations when updating Agileto database from an external Excel file;
 
7.19 51.926
- Update the module M1.1 (Generate & Update Agileto database); it is now possible to use the Cell_Name [2G/3G/4G] as the key reference when updating Agileto database from an external Excel file (previously the reference keys were related only to CId); 
- Update the module M2.4 (NW comparison between two snapshots) by correcting some special situations which may lead to errors when having as inputs two OMC ALU 3G technology files;

7.19 51.924
- Correct the errors which leads sometimes to generate duplications on 2G/3G/4G cells database;
- Upgrade the core routines which update on Agileto database (4G technology) all the eNodeBs names based on data retrieved from the input OMC snapshot file(s);

7.19 51.923
- Additional support for accepting Alcatel OMC input file(s) 2G technology in multiple formats;

7.19 51.920
- Provide additional support for Alcatel OMC input file(s) -> 2G technology;
- Upgrade the module M2.1 (OMC file Audit & Sanity Check) to support 4G technology;

7.19 51.915
- Upgrade the module M1.3 in order to calculate the "Border Cells" for the 4G technology, too.
- Upgrade the module M1.1 (Generate/Update Agileto database) to support OMC input files type = 4G technology, vendor = Huawei (*.xml);
- Add a new option to load all OMC snapshot files from the same directory AND subsequent subdirectories; this option is necessary to be used with Huawei input OMC 4G technology files [eNodeBs] which are stored in different subdirectories;

7.19 51.906
- Simplify the way of selecting as input the OMC snapshot files by accepting any of the OMC types *.xml/*.xcm/*.txt without being necessary to set in advance if the OMC file is of type *.txt or not;
- Upgrade the module M1.1 (Generate and update Agileto database) to support the 4G technology too, when using as input an external Excel database file; 

7.19 51.4
- Update the module M5.1 (translate cells KPIs into MapInfo and GoogleEarth representations):
1: Add a new input option into the form in order to generate All the Cells, including those which are not provided with valid KPIs values;
2: Modify some presentation KPIs colors in order to be better representative comparing with the legend colors;
3: Dispaly two (2) decimals after the point separator in MI and GE when the KPI selected is represented as percentage [%];

7.19 51.2
- Update the module M5.1 (translate cells KPIs into MapInfo and GoogleEarth representations) with some inputs into the form as well as some outputs; correct some erronated data displayed on Google Earth's Legend(s);

7.19 51.0
- Correct a small bug of typing 3G instead of 4G into the tool's code which lead sometimes to error(s)...

7.19 50.999
- Read and process the data related to the 4G technology from Agileto database (4G); update all the headers from Agileto database (2G/3G/4G) in order to be in line with the new template;
- Update the module M1.2 (Generate MapInfo & GoogleEarth cells/sites objects) in order to support the 4G technology, too;
- Update the module M5.1 (translate cells KPIs into MapInfo and GoogleEarth representations) in order to support the 4G technology, too;

7.19 50.994
- Insert automatically the 3G DL_UARFCN frecvencies (detected into OMC snapshot file) into Agileto 3G database (as a comment on a specific cell and with a predefined format); This news is making now available the DL_UARFCN info even when the OMC snapshot file is not provided as input. When comparing databases, if DL_UARFCN (3G) frequencies detected into Agileto database and the input OMC file do not match a warning message will be sent to the user in order to ask if to continue or to correct...

7.19 50.991
- Correct a bug which leads to wrong evaluations of the neighbors reciprocity in case of the OMC snapshot files for Huawei 3G technology;
- Update the module M2.3 (BCCH Audit & Optimisation) in order to display into the form the LAC info in addition to the CID for the unique indentification of the 2G cells;

7.19 50.989
- Update the module M2.1 (Audit & SanityCheck) regarding 2G technology; the output results (based on the OMC 2G input snapshot files) have been updated in order to detect abnormal situations when 2G cells (defined uniques by LAC + CID) have been declared in more than one BSC [cases of 2G cells duplications];
- Update the module M2.4 (Network/Neighbors comparison between two dumps) in order to accomodate multiple OMC snapshot input files (*.xml/*.xcm/*.txt) for both OMC input files [OMC_Old vs OMC_New]; the module checks automatically which is the technology carried into the OMC input files [Old vs NEW] and signalize if the user has selected for comparison different technologies;

7.19 50.983
- Provide the option to select multiple input OMC snapshot files of type *.xml/*.xcm [all the files from the same folder with the OMC snapshot selected  file]; however, only those files within the same folder carring the same technology [2G/3G/4G] and the same vendor will be processed;
- The outputs of the module M2.1 [Audit & Sanity Check] will be stored into a folder which will be created under a dedicated directory representing the technology [2G/3G/4G] carried into the OMC snapshot file(s);

7.19 50.981
- Update the module M1.1 (Generate & update Agileto database) to deal properly with the special cases when nrCells3G = 0;
- Update M1.1 in order to correct (dismiss) the display of the second progress window while generating a new 2G database based on the OMC 2G snapshot file];
- Update the module M5.1 (translate cells KPIs into MapInfo and GoogleEarth representations) by rounding the KPIs values to be presented/displayed with one digit after the decimal point;

7.19 50.978
- Update the module M1.4 (view KPIs representation) in order to present properly the technology [2G/3G/4G] KPIs available (already generated in advance);

7.19 50.977
- Update the module M5.1 (translate cells KPIs into MapInfo and GoogleEarth representations) in order to generate dedicated KPIs folders where the MI + GE files will be stored for a reference/future usage;
- Modify the module M1.4 (view KPIs representation) in order to accomodate the modifications introduced by M5.1;
- Prepare the 4G technology support in M1.4 + M5.1, too.

7.19 50.970
- Display a second progress bar while loading and sorting the 2G/3G/4G cells database;

7.19 50.967
- Update the module M1.2 (Generate MobileNW Sites/Cells objects in MI + GE) by preparing the support for the technology 4G;

7.19 50.965
- Display a second progress window barr presenting the evolution of the 'Border Cells' calculation (potentially used on the Audit & Sanity Check, too);
- Update the module M3.2 (Neighbors database -> MI + GE) in order to ask for the unique 2G cells identification based on CID + LAC (previous approach was only on 2G CID which potentially lead to errors);
- Update the module M4.1 (Network Optimisation based on the drive test) as following:
1: Accept OMC 2G snapshot file as input for the 2G-2G neighbors analysis;
2: The 2G neighbors may be provided into the external *.csv file by the combination 2G: LAC + CID for the unique 2G cell identification;
3: Display a notification message when wrong header file is used to provide the reference neighbors with focus on 3G-2G + 2G-2G analysis;

7.19 50.961
- Provide support for the module (M2.1) Audit and Sanity Check in order to accept as input OMC 2G snapshot files, too.

7.19 50.958
- Improve and update the Communicator tool in order to be alligned with the new user(s) feedback strategy;

7.18 50.958
- Improve the usage of "Google Earth Pro" with priority instead of "Google Earth" (if both are installed);
- Improve the module (M1.3) in order to calculate the "Border Cells" for the 2G technology, too.

7.18 50.955
- Use "Google Earth Pro" (if this is installed) instead of using the standard "Google Earth" for the visualisation of different related objects (mobile NW, drive test points, coverage areas, etc);
- Present into GE the drive test Top1 coverage areas @ cells levels as poligons instead of the 3D objects for the better visualization;
- Improve the module (M1.3) which calculate the 3G "Border Cells" to be more acurate and faster;

7.18 50.953
- Provide support to accept as input OMC snapshot file of type = 2G (additionally to 3G);
- OMC 2G support for Huawei file (*.txt);
- Agileto 2G cells database is now updated with BSC_Name info from the OMC 2G snapshot file;
- Provide a new input option to generate the 2G sites colored based on the new region selected as BSC_Name (additionally to LAC & Cluster);

7.18 40.950
- Provide support to extract the 3G Cell LAC info from ALU + NSN + E// snapshots, too. (previously it only supports HW type of the snapshot);
- Provide new input options to generate the sites colored based on the desired region selected as: RNC_Name / LAC / Cluster;
- Insert the 3G LAC info into the sites/cells MapInfo & Google Earth representations;

7.18 40.945
- Eliminate the bug which creates the 3G cells duplications when updating Agileto database based on the OMC 3G snapshots;
- Correct a bug which freeze the tool when generating Agileto database based on multiple Huawei OMC 3G snapshots (*.txt);

7.18 40.943
- Extract the Cell 3G LAC info from the snapshots (support initially only for Huawei) and integrate it into the tool inputs & outputs;
- Generate without errors the Google Earth network files by replacing automatically the special characters from the Antennas type fields;

7.18 40.939
- Perform the unique identification of the 2G cells by CID + LAC insted of only CID due to the fact that in some networks 2G CID may be duplicated but only in different LACs (reminder: 2G_GCI = MCC.MNC.LAC.CID);

7.18 40.936
- Update the Drive Test (DT) module in order to accept the DT and Neighbors declarations input files having the following 3 (character) separators: "Tab" OR ";" OR ",";
- If the Drive Test (DT) spatial bin aggregation is selected, increase the DT representation precision in order to get always the same reference grid position on a specific drive test area (this will be independent of the DT GPS input data);
- Correct a bug detected on the module treating the Drive Test Analysis (DTA) case;

7.18 40.35
- Calculate (additionally -> for each cell detected into the DT) the coverage ASet (ActiveSet) areas, and its associate coverage efficiency [CvgASet_A()];
- Generate additionally in Google Earth (for each cell) the poligon representing the coverage ASet (Active Set) area as per the measurements detected into the Drive Test;

7.18 40.34
- Generate in Google Earth (Areas_CellsCoverage) the poligons representing the coverage areas (Top1 / Full) as per the measurements detected into the Drive Test;
- Calculate for each cell detected into the Drive Test the coverage areas (Top1 / Full) and consequently the cell coverage efficiency;
[These results are recorded and stored inside the output Drive Test Optimisation file, into the sheet named "CrossSect+Coverge"]

7.18 40.33
- Add the GPS_Route points into MapInfo + Google Earth displays [they will be presented as black points];
- Modify the "Active Set" legend in Google Earth in order to reflect it as numbers instead of the intervals;

7.18 40.32
- Change the (Full) Cells coverage links color presentation into the Google Earth display in order to reflect the RSCP legend instead of the EcNo legend colors;
This change is valid only for the Full Cells coverage presentation; the TopX Cells Coverage presentation will continue to display the EcNo legend colors;

7.18 40.31
- When the auto-update of the tool is performed then display a message window containing the "change log" related to the last version(s);

7.17 40.31
- Provide support for using "Google Earth Pro" too, in addition to "Google Earth" ["Google Eart Pro" is free since 20ty of Jan 2015];
- Add the new input option to generate the output drive test points in Google Earth + MapInfo with the same size (by default the point size representation [in GE + MI] is to be bigger when the color is more closed to red in order to emphasize easier the issues along the drive test routes.

7.17 40.30
- Correct small bugs which generate errors while working on PSC and BCCH audit and optimisation;