Open Group OGIT-101 Certification Exam Syllabus

- Explain the purpose of the Product Portfolio functional component.
- Explain the Digital Product data object.
- Explain the following Product Portfolio functional criteria:

• Must include all Digital Products managed by the organization.
• Shall review input from organizational strategy, consumers, and market sources to propose portfolio changes that decide whether to keep, retire, increase, or decrease investment.
• Shall support strategic funding and defunding activities at a portfolio level, and infer decisions on all contained Digital Products.
• Shall compare Digital Products with similar ones to identify rationalization opportunities.
• Must provide, via specific Product Designs and Product Releases, Service Offers describing the contract, rules, warranty, and other consumer-based attributes used to establish a contract.
• Should aggregate all metrics from dedicated resources, dependencies, and consumption to include total costs, performance, consumption, capacity, resources, risks, benefits, quality, fitness-for-purpose, etc.

- Explain the purpose of the Product Design functional component.
- Explain the Product Design data object.
- Explain the following Product Design functional criteria:

• Shall be the system of record (authoritative source) for all Product Designs.
• Shall maintain the design of the integrations (and related data flows) of the Digital Product with other Digital Products (to understand dependencies and integrations with other products).
• Shall maintain the design of operational and support features of a product, including the support model, monitoring, and design for self-service (designing service interactions through the Service Offer Catalog).
• Shall document instrumentation so that empirical data can be captured to measure how the digital services are performing, rather than relying only on anecdotal input from the user community.
• Shall document how the Digital Product complies with the non-functional requirements, including security, privacy, legal, etc. (Secure, Privacy and Compliance by Design).

- Explain the purpose of the Release Composition functional component.
- Explain the Product Release data object.
- Explain the following Release Composition functional criteria:

• Shall manage the Product Release and Product Release Blueprints for delivering new or changed services to the Fulfillment functional component to facilitate a smooth transition to digital operations.
• Shall create the Product Release and the associated Product Release Blueprint used by the Fulfillment functional component to create an instance (or deployment) of the Digital Product that, for example, will be utilized by the Test functional component.
• Shall include the templates for the associated Service Offers (as part of the Product Release Blueprint).
• Shall include the templates and definitions for the configuration of Service Monitors executed by the Monitoring functional component (monitoring as code).

- Explain the purpose of the Fulfillment Orchestration functional component.
- Explain the Desired Product Instance data object.
- Explain the following Fulfillment Orchestration functional criteria:

• Shall create a Desired Product Instance based on a template in the Product Release package if the Order is a request for a new product system.
• Should modify the associated Desired Product Instance for all consumer Subscriptions to the service in order to track service delivery.
• Shall create the Actual Product Instance as a copy of the Desired Product Instance within the Configuration functional component.
• Can trigger fulfillment automation systems to enable fulfillment of (parts of) the service.
• Shall orchestrate the implementation of the various Change Orders across the fulfillment systems, or track and manage manual change task implementation to fulfill the Orders.

- Explain the purpose of the Configuration functional component.
- Explain the Actual Product Instance data object.
- Explain the following Configuration functional criteria:

• Shall manage the lifecycle of the Actual Product Instance.
• Shall create Actual Product Instance(s) and underlying system(s) based on the Desired Product Instance in the Fulfillment Orchestration functional component.
• Shall serve as the data store for the realization of the service in the production environment.
• Shall calculate and provide the business impact of the Incident to help in the prioritization process.
• Shall calculate and provide the business impact of the Event to help in the prioritization process

• Shall aggregate and provide a unified service catalog through the Consumption Experience functional component.
• Shall enable the grouping of different Service Offers into a single consumption experience.
• Shall drive consumption through Service Offer Catalogs and help identify prices and options for selection.
• Shall contain all Offers available to consumers and provide this information to the Consumption Experience functional component.
• Shall define whether the Service Offer be fulfilled as a Request Order or Change Order.

• Shall calculate the chargeback (or showback) of consuming/subscribing a service to a subscriber/consumer
• Shall consolidate the charges from all subscribed services once Usage is collected for the given billing period
• Shall send the subscribed service charges to the Product Portfolio functional component for an Actual Product Instance if a Product Portfolio functional component exists
• Should send a Chargeback Record for approval and an internal reconciliation request to the finance function if a Finance function (external to IT) exists
• Shall provide cost consumption information at the service level to consumers through the Consumption Experience engagement portal
• Can take actual Usage into consideration when calculating the charge of consuming a service

• Shall confirm that consumer access to the catalog items data is in line with defined entitlements and attached to user identities
• Shall break the service order down into the appropriate fulfillment change request(s) and provide these to the Fulfillment Orchestration functional component via the Change functional component and create the Subscriptions for these services upon their successful fulfillment
• Should send the instances of the Service Contracts to the Service Level functional component if a Service Level functional component exists
• Shall provide Subscription information for the creation of the associated Chargeback Contract
• Shall provide information to the consumer on the fulfillment status

• Shall create a Service Contract (instance) and start measuring it once a Subscription is instantiated if the Order functional component exists
• May instantiate a Service Contract from a Service Contract (template) originating from the Offer functional component
• Shall manage the Service Contract lifecycle (create, store, and maintain)
• Shall create reports on the Service Contracts to show the quality of service per the Service-Level Objectives (SLO)
• Shall manage the lifecycle (create, store, and maintain) of Key Performance Indicators (KPI)

• Identify the Backbone data objects which support or are affected by the Consume value stream (Service Offer, Subscription, Desired Product Instance, Actual Product Instance, Service Contract, Chargeback Contract).