1E 9.x (on-premises)

Values last updated 04 Mar 2022.

The physical memory required for AI Powered Auto-curation is based on the number of distinct software titles in your source data, that AI has to process that do not already have a match in the 1E Catalog. Use the accompanying table as a quick reference for the memory requirements needed by the AI.

If you're only using a System Center Configuration Manager connector for your source data, then use the below SCCM database query as a guide for how much extra RAM you need on the Tachyon web server before installing Tachyon.

SCCM database query Expand source

/*SCCM database query to get number of distinct software titles from SCCM database*/
USE [YourSCCMDBName]
GO
SELECT COUNT(*) AS 'Distinct Software Titles'
FROM (
        SELECT DISTINCT DisplayName0 AS Title FROM [v_ADD_REMOVE_PROGRAMS] WITH (NOLOCK)
        UNION
        SELECT DISTINCT [Caption0] AS Title FROM [v_GS_OPERATING_SYSTEM] WITH (NOLOCK)
) AS Titles

After installation, we recommend you use the below SLA-Data database query to double-check memory requirements. You will need to use the SLA query anyway, if you use a 1E connector (for Inventory Insights or Patch Success) either on its own, or with other connectors including SCCM. In this case, use the SLA-Data database query after installation and you have collected your source data.

SLA-Data database query Expand source

/*SLA query to get number of distinct software titles from SLA-Data database*/
USE [SLA-Data]
CREATE TABLE #Software
       (
              [SoftwareID]                      INT IDENTITY(1,1) PRIMARY KEY,
              [DataSource]                      NVARCHAR(255) COLLATE DATABASE_DEFAULT,
              [SoftwareIdent]                   NVARCHAR(MAX) COLLATE DATABASE_DEFAULT,
              [SoftwareIdent_Hash]                      VARBINARY(128),
              [Vendor]                          NVARCHAR(MAX) COLLATE DATABASE_DEFAULT,
              [Vendor_Hash]                                 VARBINARY(128),
              [Title]                           NVARCHAR(MAX) COLLATE DATABASE_DEFAULT,
              [Title_Hash]                      VARBINARY(128),
              [Version]                         NVARCHAR(MAX) COLLATE DATABASE_DEFAULT,
              [Version_Hash]                    VARBINARY(128),
              [ColloquialVersion]               NVARCHAR(MAX) COLLATE DATABASE_DEFAULT,
              [ColloquialVersion_Hash]          VARBINARY(128),
              [Edition]                         NVARCHAR(MAX) COLLATE DATABASE_DEFAULT,
              [Edition_Hash]                    VARBINARY(128),
              [NormalizedProductID]             INT
       );
SELECT * FROM #Software
EXEC [usp_ReportDataEx_se] 1, N'Software', N'#Software';
  
SELECT count(*) AS 'Distinct Software Titles'
FROM
(
SELECT DISTINCT [Title] FROM #Software
) a

DROP TABLE #Software

AI is switched off by default in the 1E Setup, this is because the feature requires additional memory to run correctly. For more details please refer to the AI Powered Auto-curation requirements.

During 1E setup you'll need to check the Enable AI-based auto-curation checkbox on the SLA and Catalog screen of the 1E Setup wizard. For more details please refer to the 1E Server Setup and SLA and 1E Catalog .

You can enable AI Powered Auto-curation after you've installed 1E, but before enabling check these pages for more details on the disk space and RAM requirements: 1E Server Setup and SLA and 1E Catalog .

Once you have confirmed the pre requisites to enable AI you should access the Settings → Configuration → Components and toggle the Enabled switch on the AI Engine row.

At the point when you enable AI, a popup will be displayed, shown opposite.

You can use the same Enabled toggle on the AI Engine row in the Settings → Configuration → Components page to turn off the AI Powered Auto-curation by sliding it to the left, off position.

The AI feature consists of an 1E-AIEngine.exe and AI model files contained in an AIPackage_<version>.zip.

The minimum total disk space required for the downloaded AI Package ZIP is approximately 13 GB at installation. This includes:

1E Catalog regularly checks it has the latest AI package synced from the 1E Catalog cloud. It downloads the AI Package ZIP (5GB) from the Cloud into the Download path folder.

Whenever the Basic Inventory Consolidation (BIC) process runs, with the AI Engine option enabled, the 1E-AIEngine.exe uses the AI package files to run the AI process.

When the 1E-AIEngine.exe is run, it uses a hash comparison of its current AI package, with the Catalog's ZIP.

SQL script to configure AIModelDeploymentPath setting Expand source

/* Script to change SLA Deployment Path for AI Package */
/* The value is copied from SLA-Shared to instance in SLA-Data when a new inventory repository is created */
/* Updating SLA-Shared means script is not required for each new repository */
/* Updating all values in SLA-Data means all repositories use the same value */

DECLARE @setting nvarchar(max), @oldvalue nvarchar(max), @newvalue nvarchar(max)
SELECT @newvalue = 'C:\ProgramData\1E\SLA Platform\AI'
SELECT @setting = 'AIModelDeploymentPath'

USE [SLA-Shared]
SELECT @oldvalue = [VALUE] FROM [dbo].[ProjectSetting]
WHERE [Group] = 'ProcessAIEngine' AND [Name] = @setting

UPDATE [dbo].[ProjectSetting] SET [Value]=@newvalue WHERE [Name]=@setting

SELECT DB_NAME() + '.dbo.ProjectSetting' AS 'Table', @setting AS 'Setting', @oldvalue AS 'Before', [Value] AS 'After' FROM [dbo].[ProjectSetting]
WHERE [Name]=@setting

USE [SLA-Data]
SELECT @oldvalue = [VALUE] FROM [dbo].InstanceSetting
WHERE [Group] = 'ProcessAIEngine' AND [Name] = @setting AND [InstanceID] = 1

UPDATE [dbo].[InstanceSetting] SET [Value]=@newvalue WHERE [Name]=@setting

SELECT DISTINCT DB_NAME() + '.dbo.InstanceSetting' AS 'Table', @setting AS 'Setting', @oldvalue AS 'Before', [Value] AS 'After' FROM [dbo].[InstanceSetting]
WHERE [Name]=@setting
GO

You can access the Basic Summary screen using the Inventory Insights 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:

FILTER BY

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.

Note

If the AI feature is disabled the Basic Summary screen will differ to when AI is enabled, note the difference in the Overview element.