In previous versions of Tachyon and SLA Platform, 1E Catalog handled normalization. This used rules that map source Programs and Features data into an accurate standardized form of Vendor, Title, Version and Edition (VTVE) fields. These normalized records can then be referred to with the same signature. Although the rules in the 1E Catalog cover most common software, there's always new software that needs to be manually mapped.
AI Powered Auto-curation first extracts the VTVE from varied raw Programs and Features data by removing excess data and extracting the relevant strings. The AI then standardizes the VTVE fields to a single, accurate form of representation. It also produces a numeric value called the confidence score. This score represents how confident the AI is in its prediction. This score is set to a high threshold through testing and validation across a large data set. This can be calibrated according to the variety of software data at a customer site to optimize the normalization rate, this is controlled by 1E through collaboration with customers.
You can enable AI Powered Auto-curation either during or after installation of Tachyon.
You can enable AI Powered Auto-curation either during or after installation of Tachyon.
AI is switched off by default in the Tachyon Setup, this is because the feature requires additional memory to run correctly. For more details please refer to the AI Installation requirements on this page.
During Tachyon setup you'll need to check the Enable AI-based auto-curation checkbox on the SLA and Catalog screen of the Tachyon Setup wizard. For more details please refer to the Tachyon Setup and Tachyon Setup: SLA and 1E Catalog.
The minimum total disk space required for the downloaded AI Package ZIP is 12.5 GB at installation.
While the downloaded AI Package is approximately 5 GB, the unzipped contents are approximately 12.5 GB and are extracted to C:\ProgramData\1E\SLA Platform\AI\
Please note, the required disk space reduces to 8.2 GB after the first Catalog sync.
The AI feature consists of an 1E-AIEngine.exe and AI model files contained in an AIPackage_<version>.zip. The 1E-AIEngine.exe uses the associated AI package files to run the AI. Because of the size of the package, it initially resides on the Catalog cloud to reduce the installer size.
When the AI feature is enabled:
You can review the Catalog sync progress in the following logs located at: C:\ProgramData\1E\Catalog\
A succesful sync should be similar to the example Catalog.UpdateService.log opposite.
[Info] T11 2020-01-31 15:45:48.567: Syncing AI Package with cloud [Info] T11 2020-01-31 15:45:48.756: Downloading AI Package version 184.108.40.2060 with cloud of size 4804685823 from url api/sync/aiengine?Version=220.127.116.110 [Info] T11 2020-01-31 15:45:48.772: Indexes re-creation started after Sync. [Info] T12 2020-01-31 15:58:25.929: Indexes are created successfully after Sync. [Info] T5 2020-01-31 16:30:47.930: Download complete. Comparing file hash.. [Info] T5 2020-01-31 16:31:07.120: Successfully synced AI Package version 18.104.22.1680 with cloud
When enabled, a new action called Process AIEngine is created. This is automatically run after the Sync Data action for a supported connector. The sync time for the Process AIEngine action depends on the number of distinct software records being processed, hardware and environment configuration.
You can see the Process AIEngine action in Settings→Monitoring→Process log.
You can review its progress using the Engine.log located at C:\ProgramData\1E\SLA Platform\
In the log you should see something similar to the opposite example.
2020-03-31 08:46:25.0274 INFO Action Process AIEngine starting! Jobs: 1/5 2020-03-31 08:46:25.0274 INFO ID=612d1b08-7eb7-4bf1-9c23-46dea29d9b6d Starting action: 11065 2020-03-31 08:46:25.0274 DEBUG [HubConnection] Adding notification '11065' to queue. Queue count:3. 2020-03-31 08:46:25.0274 INFO Folder's available in PreProcessAsync: output- True, input- True, tempDir- True, training- True 2020-03-31 08:46:25.0500 INFO Catalog web address: http://LAB.LAB.local/CatalogWeb/ 2020-03-31 08:46:25.0704 INFO Is higher version False, localVersion 22.214.171.1240, serverVersion 126.96.36.1990 2020-03-31 08:46:25.0704 INFO serverFileDetails.Base64filehash 0x853E29401B209301C9F9C4D381202C931816C871, modelFileDetails.Base64filehash 0x853E29401B209301C9F9C4D381202C931816C871 2020-03-31 08:46:25.0724 INFO Condition for download before checking: False 2020-03-31 08:46:25.0724 INFO Saving Model file hash (0x853E29401B209301C9F9C4D381202C931816C871) and version (188.8.131.520) 2020-03-31 08:46:25.1124 DEBUG [HubConnection] Notification sent '11064' 2020-03-31 08:46:25.1484 DEBUG [HubConnection] Adding notification '0' to queue. Queue count:2. 2020-03-31 08:46:25.1484 INFO Folder's available in ProcessAsync: output- True, input- True, tempDir- True, training- True 2020-03-31 08:46:25.1504 INFO Folder's available in Before Invoking AI EXE: output- True, input- True, tempDir- True, training- True 2020-03-31 08:46:25.1504 DEBUG [HubConnection] Notification sent '0' 2020-03-31 08:46:25.1504 INFO process started - 9636process name is 1E-AIEngine 2020-03-31 08:46:25.1504 INFO in wait for exit async 2020-03-31 08:46:25.1504 INFO In Read Async 2020-03-31 08:46:25.1724 DEBUG [HubConnection] Notification sent '11065' 2020-03-31 08:46:25.1967 DEBUG [HubConnection] Notification sent '0' 2020-03-31 08:51:05.5709 INFO Folder's available in After Invoking AI EXE: output- True, input- True, tempDir- True, training- True 2020-03-31 08:51:05.5709 INFO AI process completed with exit code: 0
If you see a red warning triangle in the Process log, this indicates a problem.
The most common reason for the Process AIEngine to fail is due to insufficient memory when it runs, refer to Increase in memory requirements on this page for details.
In this example, clicking on the red warning triangle displays an error message explaining that the Process AIEngine has failed.
You can review the AI logs at: C:\ProgramData\1E\SLA Platform\AI\Log_*.txt
The picture opposite shows an example of a failure logged due to insufficient memory. Log_*.txt
If the AI processing step does fail, the overall inventory consolidation will not. In the event of a failure, the AI processing step is skipped, making sure the rest of the process takes place as expected.
There are some changes to the SLA Inventory UI screens compared with Tachyon 4.1 and SLA Platform 3.3. These screens also differ if AI Powered Auto-curation is enabled or disabled.
The process of setting up connectors, creating inventory repositories and running the basic inventory consolidation remains the same as previous versions of Tachyon.
You can access the Basic Summary screen using the Inventory app and by choosing SLA Inventory from the left-hand menu. The data in this screen is updated by the Basic Inventory Consolidation process.
The Summary table now includes software records curated by AI. The first column in the table shows the total Records Collected. The next three columns are:
The numbered links in brackets allow you to drill down to more detailed screens.
You can access this screen by clicking on the number link in the Non-Normalized Records (With AI Suggestions) column of the Basic Summary screen. This screen shows AI predictions that have a low confidence score preventing them being automatically matched and normalized. These predictions should still be close to accurate, therefore making the task of manually adding rules to the Catalog much easier.
This screen has the following elements:
Shows a count of distinct software records to be identified, so you can keep track of progress.
Filters by application type.
Confidence scores for predictions are divided into three equal parts below the threshold. High, Medium and Low confidence relate to the ease at which the AI engine suggestions can be manually reviewed and added as rules.
Use this to add conditional filters for various fields on the Unidentified Software Records Table, for example you could filter on "Vendor Contains Micro" to return results based on Microsoft as a software vendor.
If the AI feature is disabled the Basic Summary screen will differ to when AI is enabled, note the difference in the Overview element.
Each row on this table corresponds to a distinct set of software records. There are four values Install Count, Source Data , AI Prediction , Confidence and a number of actions to perform for each distinct record. The values are:
|Install Count||The total number of records found with the same source data across the estate.|
|Source Data||ARP data extracted into Vendor, Title, Version, Edition, Colloquial Version and Licensable fields.|
|AI Prediction||The AI suggestion after attempting to extract Title, Version, Vendor, Edition, Colloquial Version and Licensable fields from source data, Licensability is set to a default of No on the suggestions table, this can be edited before adding.|
|Confidence||Abstracted to high, medium or low based on the exact numeric value for prediction confidence, these confidences values will always be lower than the threshold required to automatically normalize records.|
For each record the Actions are:
|Add||When clicked this will add records directly to 1E Catalog. This option is enabled if AI suggestions for a source Vendor, Title, Version and Edition (VTVE) are generated. In case the product is not Edition based then Vendor, Title and Version (VTV) suggestions are enough. After the record(s) is added to 1E Catalog then whenever you run the next Basic Inventory Consolidation then the same record(s) will be available in the Catalog Matched items.|
|Edit||Edit functionality is available for all unidentified records. When clicked, it opens a dialog where you can provide details for the selected software record. You also have the option to add this information to 1E Catalog.|
|Exclude||Exclude is available for all Unidentified Software Records except for Partially Matched and Secondary Application types of records. Once excluded, the items are moved to Secondary Applications. You can also Include it again until the next Basic Inventory Consolidation is run, afterwards the Include option will be unavailable and the item will become a part of Secondary Applications.|
You can explore these records to see what the AI has curated by clicking on the related links in the Basic Summary Report .
We have also introduced a new screen for AI suggestions for any software records that remain non-normalized. This is a replacement for the Best Match Screen which allowed you to add rules.