---
title: "Public Cloud Learning Sessions- Ollie Workflow and The Demand Process - 20240416 160113-Meeting Recording"
type: cloud-learning
source-type: video
category: "DevOps & SRE/06_CI_CD_GitOps"
tags:
  - Workflow
  - Demand-Process
  - Agile
date-added: 2026-04-14
video-source: "nas:///volume2/work/Public Cloud Learning Sessions/Public Cloud Learning Sessions- Ollie Workflow and The Demand Process - 20240416_160113-Meeting Recording.mp4"
audio-source: ""
status: summarized (Gemini 摘要)
---

# Public Cloud Learning Sessions- Ollie Workflow and The Demand Process - 20240416 160113-Meeting Recording

**Source:** NAS `/volume2/work/Public Cloud Learning Sessions/Public Cloud Learning Sessions- Ollie Workflow and The Demand Process - 20240416_160113-Meeting Recording.mp4`

**Type:** VIDEO | **Category:** 06_CI_CD_GitOps

**Status:** 🟡 Awaiting Whisper transcription → Summary

---

## Oli Workflow and Demand Process

The session covers the Oli workflow process for hyperscaler spend approval, demand management, and request fulfillment. The current mandate requires written approval from MUI or Shannon for any hyperscaler spend, regardless of the amount, for engineering lab space or commercial workload space. The Oli workflow process is being transitioned to the FinOps team under Tom Bice, who are working on integrating it into SMACs.

The base instructions for lab requests, commercial requests, and the general OLLI form guide are available in Confluence. *If justification details are not provided, requests are subject to immediate rejection.* The workflow process includes reviews by the presenter, the requester's manager, M5, lab services director, infrastructure M5, cloud services infrastructure, cloud services, and finally, approval by Shannon or Muwe. The requester is responsible for advocating for their workflow to be approved.

The request form pulls employee name and manager information from the corporate AD. The VP M5 level within their reporting structure requires validation that the workflow is properly requested, legitimate, raised for the right project and resourcing, and is budgeted. The organization is selected from a dropdown. Cost center information can be found in Talent Central. The workflow is geared towards engineering, with requests for budgetary review every six months. A critical field is whether the request is a budget increase or a new lab space. The cloud provider is selected, and if it's a budget increase, the existing account name is required. The project type is selected from a dropdown list. The region requested must be on the active regions list. Justification questions are submitted in the comment section.

The proposed workflow involves three steps: feasibility validation by FinOps, technical feasibility validation by cloud services, and budget availability validation by the FPNA team. The workflow then goes through the requester's leadership, manager, M5 VP level, and finally, the engineering chief product officers VP. The Oli system allows users to view their assignments and generate in-flight CSV reports. The reports provide information on workflow statuses, requesters, cost centers, monthly costs, and the current step in the process.

The ITIL framework divides business processes into service strategy, design, transition, operation, and improvement phases. The approval process is the first stage of request fulfillment. A master catalog of combined cloud products is being developed. Demand management is necessary to balance requests against available capacity. The OpenText way of fulfilling cloud requests is a request submission process.

The end-to-end process includes the approval stage, demand management, and definition work. Business units can submit requests directly into Octane or through a Qixi interface. The goal is to simplify the process for business units to identify and request services from the catalog. The master catalog of products and services will be embedded within SMACS. The Enterprise Iton project for the standard OT SMACS tenant is on hold. The ADM and ITOM Demand Planning Meetings capture what is needed, how many are required, and the release they are required in. The goal is for business units to self-select what they need 80% of the time. *Machines should do what machines can do, enabling an automated fulfillment process.*
