KB007: Ursa Major Tier 2 (Commercial Recharge) Workflow

Scope: Billable Google Cloud Projects (Project Polaris Tier 2) Audience: Research Computing, Systems Team, PIs Last Updated: Feb 13, 2026

1. Overview

This workflow governs the provisioning of Google Cloud projects that require a Chart of Accounts (COA) for direct billing (e.g., projects using GPUs, Marketplace models, or exceeding Tier 1 caps).

2. The 8-Step Provisioning Process

Phase 1: Intake & Validation (Research Computing)

1. Request Received: PI submits request via ServiceNow.
2. Initial Triage: Research Computing (RC) validates the request as Tier 2 and informs the PI of the process. RC collects:
   • Technical Requirements (APIs, GPUs, etc.)
   • Full Chart of Accounts (COA) string.

Phase 2: Administrative Setup (Systems Team)

1. Ticket Handoff: RC creates a structured ServiceNow Task/Request for the Systems Team containing the project specs and COA.
2. MOU Issuance: Systems Team generates a Memorandum of Understanding (MOU) outlining the recharge rates and terms. This is sent to the PI for signature.
3. MOU Execution: PI signs and returns the MOU.

Phase 3: Technical Provisioning (Systems Team)

1. Project Creation: Upon receipt of the signed MOU, the Systems Team:
   • Provisions the GCP Project.
   • Configures Billing Export to the COA.
   • Sets up IAM bindings.
2. Completion Notice: Systems Team updates the ticket and notifies RC that the project is live.

Phase 4: Onboarding (Research Computing)

1. Researcher Handoff: RC contacts the PI to:
   • Confirm access.
   • Assist with initial setup (SDKs, Login).
   • Close the original request.

3. SLA & Responsibilities

• Research Computing: Front-line communication, technical scoping, onboarding support.
• Systems Team: Billing configuration, MOU legal/financial processing, infrastructure creation.
• PI: Fiscal responsibility and MOU execution.