Skip to main content

Vendor Performance in Service Portfolio Management

$248.00
Who trusts this:
Trusted by professionals in 160+ countries
When you get access:
Course access is prepared after purchase and delivered via email
Your guarantee:
30-day money-back guarantee — no questions asked
Toolkit Included:
Includes a practical, ready-to-use toolkit containing implementation templates, worksheets, checklists, and decision-support materials used to accelerate real-world application and reduce setup time.
How you learn:
Self-paced • Lifetime updates
Adding to cart… The item has been added

What does the Vendor Performance in Service Portfolio Management course cover?

Vendor Performance in Service Portfolio Management is covered here in 8 modules: Defining Service Portfolio Boundaries and Vendor Inclusion Criteria, Contractual Frameworks and Performance Obligations, Performance Monitoring and Data Collection Infrastructure and 5 more. The outline lists 48 specific topics, opening with establishing minimum service uptime requirements (e.g., 99.95% SLA) as a threshold for vendor eligibility in the portfolio.

How do you approach Vendor Performance in Service Portfolio Management step by step?

The work is sequenced in 8 stages. It starts with Defining Service Portfolio Boundaries and Vendor Inclusion Criteria, moves through Contractual Frameworks and Performance Obligations and Performance Monitoring and Data Collection Infrastructure, and ends at Integration with Enterprise Service Management Ecosystems. Each stage carries its own topic list, so the sequence is followed rather than summarised.

What is in Module 1 of the Vendor Performance in Service Portfolio Management course?

Module 1 is Defining Service Portfolio Boundaries and Vendor Inclusion Criteria. It works through establishing minimum service uptime requirements (e.g., 99.95% SLA) as a threshold for vendor eligibility in the portfolio., deciding whether to include multi-sourced vendors for the same service category (e.g., multiple cloud providers) and defining failover protocols., documenting geographic service delivery constraints, such as data residency laws, that exclude.

How is the Vendor Performance in Service Portfolio Management course delivered?

The Vendor Performance in Service Portfolio Management course is fully self-paced with immediate online access after enrolment. Access does not expire and future updates are included at no cost. It can be taken on any device, and a certificate of completion is issued by The Art of Service when you finish.

How much does the Vendor Performance in Service Portfolio Management course cost?

The Vendor Performance in Service Portfolio Management course is $248 as a one time payment. There is no subscription, no per seat licence and no hidden fee. Enrolment carries a 30 day satisfied or refunded guarantee, so it can be assessed in full before you commit.

Closely related courses: Vendor Portfolio Toolkit, Vendor Relationships in Service Portfolio Management, Vendor Negotiations in Service Portfolio Management, Vendor Contracts in Service Portfolio Management.

More answers: what you get with every course, refund policy, all help answers.

This curriculum spans the design and operationalization of vendor performance management across a multi-year service portfolio lifecycle, comparable in scope to an enterprise-wide governance program integrating procurement, IT operations, and risk management functions.

Module 1: Defining Service Portfolio Boundaries and Vendor Inclusion Criteria

  • Establishing minimum service uptime requirements (e.g., 99.95% SLA) as a threshold for vendor eligibility in the portfolio.
  • Deciding whether to include multi-sourced vendors for the same service category (e.g., multiple cloud providers) and defining failover protocols.
  • Documenting geographic service delivery constraints, such as data residency laws, that exclude otherwise qualified vendors.
  • Setting financial viability benchmarks (e.g., three-year audited statements) to assess vendor sustainability.
  • Requiring standardized API access and integration capabilities as a precondition for inclusion in the service catalog.
  • Creating exclusion rules for vendors with unresolved audit findings from previous enterprise engagements.

Module 2: Contractual Frameworks and Performance Obligations

  • Negotiating penalty clauses for SLA breaches that are enforceable without requiring legal arbitration.
  • Specifying exact metrics for service responsiveness, such as mean time to acknowledge (MTTA) and resolve (MTTR), in contract annexes.
  • Requiring vendors to submit quarterly performance data using the enterprise’s defined KPI taxonomy.
  • Defining ownership and access rights to service-related data generated during contract execution.
  • Embedding right-to-audit clauses with 10-day notice periods and access to operational logs.
  • Requiring subcontractor disclosure and approval processes to maintain accountability chains.

Module 3: Performance Monitoring and Data Collection Infrastructure

  • Integrating vendor-provided monitoring tools (e.g., cloud provider consoles) into centralized observability platforms.
  • Standardizing time-series data formats across vendors to enable cross-service performance benchmarking.
  • Deploying synthetic transaction monitoring to validate end-user experience independently of vendor reporting.
  • Configuring automated alerts for SLA threshold breaches with escalation paths to vendor management teams.
  • Validating vendor-reported uptime against internal network probe data to detect reporting discrepancies.
  • Assigning dedicated data stewards to reconcile performance data discrepancies before performance reviews.

Module 4: Scoring Models and Vendor Performance Evaluation

  • Weighting KPIs by business impact (e.g., incident resolution time weighted higher than documentation completeness).
  • Applying normalization techniques to compare vendors across different service categories on a unified scorecard.
  • Adjusting performance scores for external factors such as regional outages beyond vendor control.
  • Setting thresholds for performance degradation that trigger formal performance improvement plans (PIPs).
  • Using rolling 12-month performance data to minimize seasonal bias in annual evaluations.
  • Requiring third-party validation of self-reported metrics for high-risk services (e.g., payment processing).

Module 5: Governance and Escalation Protocols

  • Establishing a cross-functional vendor review board with procurement, legal, and IT representation.
  • Defining escalation paths for unresolved SLA breaches, including executive-level mediation.
  • Requiring vendors to attend monthly performance review meetings with documented action items.
  • Implementing a formal dispute resolution process for contested performance assessments.
  • Assigning internal ownership for each vendor relationship to ensure consistent governance oversight.
  • Requiring root cause analysis (RCA) submissions for critical incidents within five business days.

Module 6: Risk Mitigation and Contingency Planning

  • Conducting annual business impact analyses to identify single points of vendor failure in critical services.
  • Maintaining minimum viable in-house capabilities to operate key services during vendor transition periods.
  • Requiring vendors to maintain documented disaster recovery plans aligned with enterprise RTO/RPO standards.
  • Staging quarterly failover tests for mission-critical vendor-managed systems.
  • Identifying and pre-qualifying alternative vendors for rapid onboarding in case of contract termination.
  • Requiring cyber insurance coverage minimums (e.g., $10M) and validating policy terms annually.
  • Module 7: Continuous Improvement and Vendor Lifecycle Management

    • Scheduling bi-annual business reviews to assess strategic alignment and innovation contributions.
    • Requiring vendors to submit roadmaps for service enhancements tied to enterprise IT strategy.
    • Implementing a phased offboarding process that includes knowledge transfer and data migration.
    • Using performance trends to renegotiate contract terms or initiate competitive rebidding.
    • Archiving performance records for terminated vendors to inform future sourcing decisions.
    • Establishing feedback loops to incorporate business unit input into vendor evaluation criteria.

    Module 8: Integration with Enterprise Service Management Ecosystems

    • Mapping vendor-managed services to the enterprise CMDB with ownership and dependency attributes.
    • Enforcing incident management integration so vendor-resolved tickets appear in the central ticketing system.
    • Requiring vendors to adopt enterprise change advisory board (CAB) processes for production changes.
    • Syncing service catalog entries with financial management systems for accurate chargeback reporting.
    • Automating service provisioning workflows that trigger vendor activation upon approval.
    • Aligning vendor reporting cycles with enterprise fiscal periods for consolidated performance reporting.