For Mainframe as a Service (MFaaS), you'd typically focus on capturing it as a service rather than individual hardware components.
Think of it this way:
Define the Business Service: First, record the actual business service the mainframe provides (e.g., 'Core Transaction Processing').
Model the MFaaS Offering: Then, capture the specific instance or subscription you have with the provider (e.g., you org's MFaaS Environment'). This is where you'd list contract details, allocated capacity, and SLAs.
Link Applications: Finally, map the individual applications that run on this MFaaS offering.
This approach focuses on what the business consumes and ensures you can track dependencies, even if you don't control the underlying physical mainframe.
