IBM license compliance: architecture process and 30-minute scan configurationIssue <!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } IBM sub-capacity requirements mandate that hardware capacity scans be performed every 30 minutes. The Devices to scan section under IBM license compliance defaults the scan frequency to 30 minutes for gathering hardware capacity. This knowledge article describes the 30-minute scan configuration and default settings for IBM license compliance and explains the architecture process that supports it. Release<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } All Resolution<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Architecture process flow overview IBM Authorised SAM Provider (IASP) integrations Discovery ServiceNow File-Based Discovery identifies IBM component installations across the environment. However, some required details — such as file names, file maps, and file set content — may not always be fully available within ServiceNow. IASPs supplement this gap by: Providing enriched file and component details through extension tablesManually normalising entries found in the Unidentified Filenames table. This helps verify a more complete and accurate discovery of IBM software components. Classification ServiceNow uses IASPs to classify IBM component installations accurately. As part of this process: IASPs retrieve entitlement data, discovered component installations, and prior classification information from the ServiceNow instance.IASPs then apply updated classification logic and push the new classification results back into ServiceNow.Data is sent via scripted REST APIs into Import Set tables and transformed into target tables in controlled batches of up to 1,000 records. This integration helps confirm consistent classification of IBM software. Synchronisation of new installations When new IBM component installations are discovered in ServiceNow, corresponding classification records must also be created. This synchronisation is handled automatically through a daily scheduled job, helping confirm that all newly discovered installations are included in the classification process without manual intervention. ⚠ SME: Verify whether a specific role (for example, itam_admin or sn_ibm_lc.admin) is required to view or configure the scheduled synchronisation job, and provide the full navigation path to access it. IBM usage calculation — how it works IBM licensing follows a High-Water Mark (HWM) model. This model determines licensing requirements based on the maximum resource usage observed over a defined period — typically 90 days — rather than average or current usage. High-Water Mark licensing Resource monitoring IBM tools continuously monitor resource consumption across the infrastructure, including metrics such as: CPU coresVirtual coresmemoryvirtual machine Infrastructure usage snapshots are typically captured every 30 minutes to help confirm accuracy and completeness. Daily peak calculation For each day, the highest resource usage observed for a given IBM product or classification is recorded. This helps confirm that even short-duration usage spikes are captured and accounted for. Infrastructure scanning IBM requires infrastructure snapshots to be collected every 30 minutes. ServiceNow supports this requirement by using different data collection strategies depending on the infrastructure type, helping confirm alignment with IBM compliance expectations.