---
sourceDocument: Australia Asset Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/it-asset-management

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Asset Management

ft:clusterId :

    - itam

bundleId :

    - itam

workflow :

    - Technology


---

# Domain separation and lifecycle reports

# Domain separation and lifecycle reports {#ariaid-title1}

* Release version: Australia
* 
* Updated March 12, 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

There are certain domain separation aspects to consider when running software lifecycle
reports.

## Software Asset Management overview {#domain-sep-sam-lifecycle__section_wzv_gmr_znb}

In a domain-separated environment, the software lifecycle report is generated at the level at
which the Service Provider (SP) is managing compliance for their customers' environment.
Typically, the level at which reconciliation is run indicates such compliance, and the software
lifecycle report is generated at the same level.

The following table shows how the reconciliation should behave. In this example:  
* The SP is managing Cisco's software asset management (SAM) program at the Cisco corporate level. That means the lifecycle report must run at the Cisco corporate level.
* The SP is managing Walmart's SAM program for each Walmart division (US and Mexico). That means the lifecycle report must run at the Walmart division level.
{#domain-sep-sam-lifecycle__ul_ts5_1mr_znb}  
Here is the SP hierarchy:

* Cisco Corporate
  * Cisco USA
  * Cisco Mexico
  {#domain-sep-sam-lifecycle__ul_j1b_lgn_h4b}
* Walmart Corporate
  * Walmart USA
  * Walmart Mexico
  {#domain-sep-sam-lifecycle__ul_jhv_lgn_h4b}

{#domain-sep-sam-lifecycle__ul_x1j_3gn_h4b} {#domain-sep-sam-lifecycle__table_bf1_smr_znb__entry__3}

| Domain settings (reconciliation/ normalization) | Compliance reporting | Lifecycle report level |
|-|-|-|
| TOP/Cisco | True | Yes |
| TOP/Cisco/US | False |   |
| TOP/Cisco/Mexico | False |   |
| TOP/Cisco/Germany | False |   |
| TOP/Walmart | False |   |
| TOP/Walmart/US | True | Yes |
| TOP/Walmart/Mexico | True | Yes |
[ ]

{#domain-sep-sam-lifecycle__table_bf1_smr_znb}

If the SP sets up software models for Cisco corporate as well as Cisco Mexico, even though
their intent is to manage compliance for Cisco at the Cisco Corporate level, the lifecycle
report may show duplicate lifecycle records with the same install count.  
{#domain-sep-sam-lifecycle__table_pmt_h4r_znb__entry__6}

| Model domain |   | Date |   | Software Model | Domain |
|-|-|-|-|-|-|
| Cisco | SQL Server 2012 | 2014 | 10 | SQL Server 2012 | Cisco |
| Cisco Mexico | SQL Server 2012 | 2014 | 10 | SQL Server 2012 | Cisco |
| Walmart USA | SQL Server 2012 | 2014 | 5 |   |   |
| Walmart Mexico | SQL Server 2012 | 2014 | 20 |   |   |
[Table 1. Lifecycle report]

{#domain-sep-sam-lifecycle__table_pmt_h4r_znb}

To learn more about software lifecycles, see [Create software models in Software Asset Management classic](https://servicenow-prod.fluidtopics.net/kfKmznifMVOSMVTCzoV9aQ "Create a software model to add product details that are used to connect software rights you purchased with software installations discovered on your system."). To learn about domain separation path
setup, see [Domain separation setup and
administration](https://www.servicenow.com/docs/access?context=c_DomainSeparationSetup&version=australia&pubname=australia-platform-security&ft:locale=en-US)