The ADP Management window can be accessed in the following ways:

ADP tasks can be defined in the following ways:

The Tasks tab on the ADP Management window lists the created ADP tasks in a table with the following columns and functions:

 

The Log tab shows the logging information for the ADP tasks.

 

The step 1 window of configuring an ADP task is shown below:

If you are creating a new ADP task for purely output purposes, you can skip this step by clicking the Next button.

The table lists all the file folders to be monitored by this ADP task.

 

The table has the following columns and functions:

PCAP data type option include time zone offset correction.

Cell configuration data type options allows user to define target project. In case when target project is not specified new project is automatically created using monitored ADP folder name. In case ‘NetworkConfig Text File (Delimited)’ data type is selected user will need to specify mapping configuration to be used in automatic import.

GIS options allows user to define target project and target geo area. In case when target project or target area are not specified new project and target area are automatically created using monitored ADP folder name. ‘Default GIS maps for display and report’ check box if selected would select respective option in Project Properties - GIS Settings to automatically include imported GIS to Data Explorer and Report Builder Map View. Additionally, user may select ‘Convert and save GIS as UDR’ option for automatic conversion of closed area polygons to UDR. UDR cluster index used as reporting reference will be automatically generated for all UDRs created via ADP.

 

In order to monitor multiple projects and multiple datasets automatically, it is recommended that the monitored folder be set up according to the following structure:

If no project sub-folders are under the monitored folder, TEMS Discovery will create the following default project and default datasets:

Also, TEMS Discovery will automatically create the following two sub-folders after execution of an ADP task:

You should never manually place any log files to be processed under the Imported or the FailedToImported folders.

 

Task can be distributed across distributed network. If you would like to utilize processing resources from other computers on the same network to help process new monitored data files when this computer is busy, turn this option on.

Member of Distributed Network. If you want to add or modify the distributed network information, click this button to access the necessary dialog.

Auto assignment of Cell Configuration Index. Cell configuration index is used as selection reference in Map View reporting element. Auto assignment of CCI was made to be independent from order of cell configuration import. CCIs are dynamically updated by alphanumerical order whenever new configuration is loaded, regardless if ADP or manual import method was used. Appropriate cell configuration names must be used to ensure preferred indexing, e.g. 1_NR.., 2_LTE.., 3_WCDMA, etc.

Send log file execution history every <x> hours. Automatically emails ADP task execution history with specified periodicity to selected email recipients.

Enable File Checks. If enabled, Enterprise ADP option will run additional log file integrity checks and prevent processing of corrupt or incomplete log files.

FTP Setting. If you have selected FTP as the Host type, clicking the button in the Browse column will bring you to the FTP Setting window.

Select the Select a folder to be monitored or the Select a backup folder radio button before selecting a folder to be monitored or selecting a backup folder from the folder browser by highlighting the folder.

When you click OK, TEMS Discovery will try to connect to the FTP server with the information you provided and check whether at least one set of project/dataset folders is available under the Project root folder being monitored.

FTP data drop folders may be automatically deleted in TEMS Discovery Enterprise setup by enabling ‘Delete data drop folder upon download’. Data drop folders will be automatically deleted once all log files are downloaded, unless data is dropped directly to FTP monitored (root) folder.

 

The step 2 window of configuring an ADP task is shown below:

This window has two tree views showing projects and datasets that can be selected as the output data source.

The left side tree view shows the current project and dataset folders under the monitored Project Root Folder of this task. The right side tree view shows the output from the existing projects/datasets. When you select/unselect a tree node on one tree, TEMS Discovery will automatically select or unselect the corresponding node on the other tree if there is one on the other tree.

Download & Show monitored FTP project/dataset names. If you have an FTP folder to be monitored by this task, enable this checkbox (it is unchecked by default). If your computer is connected to the network and you want to make a specific tree node selection, checking this option will direct TEMS Discovery to connect to the FTP server and download the current project and dataset subfolder names from the monitored FTP folder. (If the network or the FTP server is slow and/or the folder has many subfolders, it could take a while for Discovery to download all the information.)

The step 3 window of configuring an ADP task is shown below:

 

Check Time. These settings tell TEMS Discovery when to check the project/dataset for the defined time interval to generate the output by using one of the following options:

o ‘At’ sub-option to trigger output at a certain time of day

o ‘In <number> minutes after the last file of batch is imported’ sub-option to trigger output in specified number of minutes after the last measurement data file of a batch is imported. Note that in case when the time gap between dropping the log files to the ADP monitored folder is longer than batch wait time, log files received at a later time will be placed in a separate batch for which separate output will be generated.

o ‘In <number> minutes after each file is imported’ sub-option to trigger output in specified number of minutes after importing each measurement data file.

Check by. These settings tell TEMS Discovery how to check the data, by Data processing time or by Data collection time.

At the check time, the active ADP task will check the project/dataset selected at Step 2 up to the beginning of the start time interval and generate the output as defined by the task.

If the Check by option is set to Data collection time, the delayed by hours value will be added. For example, if the delayed by hours value is 6, then the time range of a day's data will be 6 AM to 6 AM on the following day.

Date Range. These settings tell TEMS Discovery what date range should be considered when generating the output. For example, if you have data in the project/dataset as old as January 1, 2010, but you only want to generate output from March 1, 2010, you can set the starting date as March 1, 2010. Note that you can define a more flexible date range by defining the number of hours to look back from the check time.

Once an ADP task with an output option set is activated and TEMS Discovery keeps running on the computer, TEMS Discovery will try to generate the output based on the settings every day at the Check time. TEMS Discovery will keep track of which days’ data have been processed for output. If you stop and restart a task that has generated some output for some days, TEMS Discovery will ask whether you want to re-generate the output from the Start date.

 

 

 

Normally TD will output all files to used-defined output folder. The project name will be concatenated in the output file name. If you like to group output files by each project, you shall check this option. A subfolder will be created for each project and the output files will be saved in each subfolder respectively.

The step 4 window of configuring an ADP task is shown below:

User may select up to four different type of output for Measurement Data (Report, Problem Summary, Batch PDF, Map Export and Tabular Export) and one for Statistic Data (Report). For measurement data Report or Problem Summary output user should select one or more report templates and specify output folder.

For measurement data Batch PDF, Map Export or Tabular Export output user should select one of previously defined Batch PDF, Map Export or Tabular Export configurations respectively (see further under Batch Configuration, Tabular Export Configuration and Map Export Configuration) and specify output folder. User may edit selected configuration directly from ADP Task Configuration window for any last-minute changes.

 

Measurement Data Report, Batch PDF and Map Export output may also be automatically emailed to users specified in Email Template sub-option.

‘Preferred Thread Allocation’ option of ADP Task Configuration allows users to specify preferred number of processing threads per ADP task. Number of allocated threads determines relative task priority. Additionally, preferred thread allocation will prevent processing delays in scenario when tasks started early consume all available resources until all of their log files are processed. Preferred thread allocation is applicable to all data types (drive test log files, cell configuration files, GIS files, TD configuration files). Any unused processing resources after completion of file import are always returned to the common pool of resources, i.e. thread assignment per task is never permanent.

 

 

'Utilize Excess Resources’ sub-option determines if ADP task will use any additional processing resources, if available. Excess resources are allocated on first come, first served basis. In case when 'Utilize Excess Resources’ check box is unselected, preferred thread allocation will be used as hard floor in terms of processing threads which may be useful to prevent ADP tasks with large of number small log files syphons all idle processing resources and facilitate more even and predictable report generation time independent from system utilization.

Example 1 depicts scenario in which total of 10 processing threads is shared by 3 active ADP tasks defined with ‘Preferred Thread Allocation’ set to 2, so assuming all 3 detected file queues are populated, each task will get allocated 2 processing threads with remaining 4 threads distributed on first come, first served basis. In example 2, total number of threads specified by preferred allocation (12 = 3x4), is greater than total number of available threads, in which case threads will be allocated on best effort basis, i.e. one task will get requested 4, while other two will get 3 processing threads.

Original ADP implementation allowed for monitoring of only one type of information per monitored folder and ADP task. Flexibility of data content scanning was increased since then so that automatic import of all data types under a single monitored folder is allowed by defining one sub-task for each distinct data type.

Selection of different data types sharing same file extension is prevented in single monitored folder setup, e.g. .txt and .zip extensions are in this case reserved for network configuration and drive test data type import respectively. Recommendation is to use 'Common supported formats’ Data Type selection for drive test data in multi sub-task setup as it covers all major formats including .zip archives.

 

'Log File Execution History’ is an Enterprise feature providing near real-time ADP service execution statistics. Service execution statistics are generated by selecting ‘Show Statistics’ button for the time period selected using ‘Show for last X hours’ or ‘Show for dates from X to Y’ radio button options including all file types and ADP generated reports. Detailed (per file) statistics are generated for processing states selected under ‘Status filter for listing files’ check box range by selecting ‘List Files’ button.

Detailed file list may be filtered per column supporting filtering per file name/extension (e.g. .xls or .xlsx for ADP generated reports) and ADP task name. ADP service execution statistics and per file details may be exported for selected time period in .csv format by selecting Export button.

Per ADP task service execution statistics including list of log files that failed processing may be additionally delivered by email every 1-24 hours to users subscribed via ‘Send log file execution history every X hour(s)‘ option under ‘ADP Task Configuration’.