Guild ControlPlane · Control Tower

GUEST

Prototype environment — all costs, events, users, and outcomes are simulated.

Architecture & Execution

Architecture & Execution

The layered pipeline, live data-retrieval workflow, and process-flow scenario traces — the technical blueprint and its execution.

Guild SystemsBoxAI analytics POC — technical architectureIBMwatsonx.ai + Apptio EBM | Guild Systems | POC Demo
PROVIDED BY BOX
Layer 1 — Box watsonx.ai sandbox
Box grants API credentials · Guild makes real API calls · real model responses · real token counts generated
Granite 3.1 8B
ibm/granite-3-1-8b-instruct
Text generation
Granite 3.1 2B
ibm/granite-3-1-2b-instruct
Summarisation
Granite Code
ibm/granite-3-1-8b-instruct-code
Code generation
Needed from Box
  • Sandbox API credentials (API key + project ID)
  • Confirmation of which Granite models are available in the sandbox
  • Rate card ($ per 1K tokens) or approval to use IBM public list pricing
JSON response payload per API call
(model_id · input_tokens · output_tokens · timestamp)
BUILT BY GUILD SYSTEMS
Layer 2 — Guild Systems API logging layer
Lightweight wrapper intercepts every API call · extracts key fields · writes enriched rows to data store
Identity
user_id · user_email
application_name · project_id
Model
model_id · api_call_id
timestamp · status
Token consumption
input_tokens · output_tokens
total_tokens
Computed cost
total_tokens × rate card
estimated cost ($)
Enriched log dataset
PROVIDED BY BOX — org mapping data (choose one source)
Layer 3 — Box org mapping data
Maps users to departments, cost centers, and budget owners · enables chargeback and showback in EBM
Box Admin Console
Export user list as CSV — includes email, department, cost center fields. Easiest option.
Azure AD / Okta
Directory sync export — full user → group → department hierarchy. Ideal if Box uses SSO.
Manual CSV from IT
Simple spreadsheet: user email · department · cost center · budget owner. Sufficient for POC.
Fields needed in the org mapping file
  • User email address (to join with API log user_id)
  • Department name
  • Cost center code (e.g. ENG-001, LEG-003)
  • Budget owner name
  • Monthly AI budget per department (optional but enables budget vs actuals view)
API logs + org mapping joined · rate card applied · cost allocated
BUILT BY GUILD SYSTEMS
Layer 4 — Apptio EBM
Cost allocation engine · chargeback · showback · budget vs actuals · AI governance reporting
Dashboard data feed
DEMO OUTPUT — WHAT BOX WILL SEE
Layer 5 — EBM dashboard views
Five interactive views demonstrating AI cost transparency, governance, and chargeback for Box
AI spend overviewBy userBy departmentBy modelBudget vs actuals ★
★ Budget vs actuals is the showstopper slide — shows projected overage by department with chargeback status, directly demonstrating AI governance and financial accountability.
POC Demo — Guild Systems & IBM Software  |  watsonx.ai + Apptio EBM  |  Illustrative architecture
Guild Systems

Guild ControlPlane

ControlPlane — AI Enterprise Governance & Intelligence System

Choose a Client Demo

Each client is a self-contained simulation context with independently seeded data, spend patterns, and governance rates.