The MAIN purpose of the Service Portfolio is to describe services in terms of?

The Service Portfolio represents all services a provider manages across their full lifecycle - pipeline, catalog, and retired - and its main purpose is to articulate business value, demonstrating why each service is worth investing in and how it maps to business outcomes. This distinguishes it from technical documentation by keeping the focus on strategic justification and value realization rather than technical specifications.

Functionality describes the technical capabilities of a service and is captured in service design documentation; it is not the primary lens of the Service Portfolio, which focuses on business justification.

IT assets are tracked and managed through the Configuration Management System and CMDB, not through the Service Portfolio, which operates at the service and business value level.

Service Level Requirements are captured in Service Level Agreements and Operational Level Agreements within the Service Design process, not in the Service Portfolio.