- **Company size**
- Typically very large enterprises or organizations with significant IBM Z investments.
- **Industries**
- Financial services, insurance, government, large retail, healthcare payers/providers — sectors where IBM Z and z/VM consolidation is common.
- **Roles and personas**
- Mainframe systems programmers (z/VM)
- IBM Z infrastructure operations / NOC teams
- Linux on IBM Z platform teams
- Capacity and performance management teams
- **Primary pain points**
- Need to correlate z/VM hypervisor performance and Linux guest workload behavior
- Capacity planning (CPU, storage, paging/spooling)
- Reducing mean time to resolution for performance incidents
- **Qualification criteria (suitable fit)**
- Environment runs z/VM at meaningful scale (multiple Linux guests)
- Organization is using or is willing to adopt IBM Tivoli Monitoring / OMEGAMON operational models
- Requirement for z/VM-specific constructs and reporting (LPAR/workload views, minidisks, paging/spooling)
- **Deal disqualifiers (poor fit)**
- Absence of z/VM in the environment or reliance on alternative hypervisors (for example, KVM on IBM Z or distributed virtualization platforms)
- Requirement for public, self-serve pricing and rapid procurement without vendor engagement
- Organizational mandate to standardize on a single, cloud-native observability stack with minimal legacy tooling