Service Portfolio functionalities
The scope of portfolio management must include at a minimum:
· Services
· Products
The portfolio management sscope include Porfolio, Services, Applications, Product and Programs from Portfolio perspective, gather all relevant information in same process and screen, integrated with all practices.
Portfolio
Services
Applications
Product
Programs
______________________________________________________________________________________________
The ability to relate or link products and applications to services, supporting both a one-to-many and many-to-many relationship.
Yes, the platform allow link in the services link applications, products and programs.
Service à Applications
Service à Products
Service à Programs
______________________________________________________________________________________________
Links products, applications, and services to the CI database and the underpinning components (CIs).
Yes, in the Portfolio process the customer can link all products, applications, services and components
Configuration Itens
Applications
______________________________________________________________________________________________
Shares with or links live/current versions of products and services with service catalog management.
Yes, the customer can define version of products and services for each services / product available. After create a new version its possible define when new version will be released without impact on customer.
______________________________________________________________________________________________
Allows for the identification of key stakeholders; examples of this can include but are not limited to:
· Service owners, product owners, and application owners
· Regarding services, allows for joint owners representing IT and the business/customer
· Related to all products, applications, and services:
o Authorizing or approval stakeholders
o Consumer groups (internal and external)
o Customer stakeholders
o Support stakeholders
Yes, there are all tabs for set all information:
Service Owner: (Business Owner Person or Group)
Product Owner: (Skill Resource)
Application Owner: (Skill Resource)
IT Owner: (IT Owners)
Stakeholders – (Business Case)
Customer Groups – (Business Case)
Consumer Stakeholders – (Business Case)
Support Stakeholder – (Business Case)
Vendor Stakeholders – (Business Case)
______________________________________________________________________________________________
Enables the collection and documentation of critical elements or attributes for services, products, and applications; examples of this information can include but are not limited to:
· User/customer/business requirements
· Descriptions
· Value proposition
· Entitlements
· Service level targets
· Criticality (as they relate to or support vital and critical business functions)
· Dependencies with other services and products
· Internal service provider resource information for development, maintenance, delivery, management, and/or support
Yes, all information can be filled on Portfolio/Service setup page can be added all elements like:
· User/customer/business requirements
· Descriptions
· Value proposition
· Entitlements
· Service level targets
· Criticality (as they relate to or support vital and critical business functions)
· Dependencies with other services and products
· Internal service provider resource information for development, maintenance, delivery, management, and/or support
· External vendor resource and contract information for development, maintenance, delivery, management, and/or support
______________________________________________________________________________________________
Allows for the link or reference between services to business processes and functions.
Yes, it does. The customer can link all business process related with Service.
______________________________________________________________________________________________
The ability to capture or link business assessment information to services, products, and applications to assist in the authorization of requirements and requested revisions or updates; examples of this can include but are not limited to:
· Business cases and charters
· Budget and resources
· Expected TSO and ROI information
· Risk assessment and risk management measures
Yes, on Business Case and Financial Tab, can be configurated all information including attachments.
______________________________________________________________________________________________
The ability to link services to service continuity or disaster recovery plans.
Yes, it does linking Continuity Plan to be started automatically when configurated Continuity Process + Knowledge Assets Recovery Plans
______________________________________________________________________________________________
Enables and supports various life cycle stages for products and services; examples of this can include but are not limited to:
· The pipeline: future/pre-live for new services and products or planned revisions to existing ones
· Active, live, in use
· Retired from use
Supports different statuses within the life cycle stages; examples of this can include but are not limited to:
· In review
· Authorized/not authorized
· In planning
· In development
· In testing
· Stakeholder sign-off
Yes, on Portfolio Pipeline there are all Portfolio stages:
And all life cycle:
______________________________________________________________________________________________
Enables and supports versioning control and allows for multiple versions of products, applications, and services to be in the same life cycle stage at the same time, where necessary.
Yes, it does using version functionality. All information will be copied as version “N” and after all workflow can replace the current portfolio/service version
______________________________________________________________________________________________
Links products, applications, and services to vendor and contract records.
Yes, it does, just need to define on setup menu :
Services
Applications:
Contract / Vendor Record
Products
______________________________________________________________________________________________
Links or applies service level agreements (SLAs) to services in all life cycle stages.
Links or applies underpinning agreements to products and services such as operational-level agreements or contracts.
Yes, it does using Service Level Requirements, Contract (underpinning contracts and Support Services tab
Service Level Requirements
Contracts
______________________________________________________________________________________________
For life cycle management purposes, the ability to link products, applications, and services in all life cycle stages to at a minimum:
· Projects and programs
· Release and deployment plans/records
· Changes
Yes, it does. On Portfolio setup can be configurated all related itens like requests, incidents, continuity plans, capacity, release/deployments, products, programs/projects;
______________________________________________________________________________________________
Integrates with workflow management to standardize the flow of work moving new or changing services, applications, and products through the pipeline into production and from production to retirement
Yes, using the field “Date of Deployment”, can be changed the status for production and set as available using workflow or workflow automation;
______________________________________________________________________________________________
For support purposes, the ability to link products, applications, and services, in all life cycle stages to at a minimum:
· Incidents
· Problems
Yes, it does. When an specific incident or problem can link Services, (Products and Applications) via Kanban or CMDB
______________________________________________________________________________________________
The ability to identify and track costs related to the life cycle management of services and products from the pipeline through retirement and link this information to financial management.
Yes, it does using link with financial attributes.
