To check why the score was low, you need send tuning log and recent header file to [email protected], you can find the tuning log files under D:\ACTIMIZE\IFM_TEMP\tuning_log in AIS Server.

TUNING LOG
The tuning log files are organized by date, with the base activity, date, hour, and AIS instance mentioned in the log file name (e.g., “TuningLog_W_IDT_2018_09_17_14_4_1_cad1656fa6d3d3151b258156ba721815.csv” contains web internal transfer transactions on September 17, 2018 from 14:00-15:00 on AIS instance)

So as a first step, you should collect all of the log files for the relevant base activity (e.g., corresponding to Channel : ECCE, Transaction Type : FT0104) on the date when the questioned transaction happen, and focus particularly on the hour. Then you need to find the relevant record(s) within the log files.

Probably the simplest approach is to unzip the relevant log files and search for the transaction key.
Here are the usual base activity code which you can refer to in accordance to the following filename:
TuningLog_W_IDT_2018_09_17_14_4_1_cad1656fa6d3d3151b258156ba721815.csv
W_LIN = Login activity
W_IDT = Internal transfer
W_EDT = Domestic transfer

RECENT HEADER FILE
Along with the tuning log files , there are also files called tuning header files. Typically the names of these files starts with “TuningLogHeader” rather than “TuningLog”, they get created/recreated when the server is restarted and stored in the same directory as the log files (or not very far from it). They contain the field names for each of the fields in the tuning log. Since the columns can change over time (as new functionality is added to the solution or fixes are introduced), it’s best to use the header file as close in time to the log file as possible.