Resources:
Legacy
Artifact | Audience | Type | Status, Link/Location | |||
|---|---|---|---|---|---|---|
Legacy | New | |||||
Pre-Agreement Documentation & Initial Outreach | ||||||
OEM Program Overview One-page or webpage summary covering program benefits, features, and partnership terms. – | External | Written | NEEDS REVIEW | |||
Sales Guide (Net New OEM) Talking points, pricing, and benefits specifically for OEM ISVs. – | Internal | written | TBD ETA 11/22/24 | |||
Transition Guide: (OEM Conversion) How to transition from legacy to new. Additional features and benefits of full CCH license – | External | written | TBD ETA 11/22/24 | |||
Sales Enablement Training: Teach Partner sales team to sell UC in their product. – | External | written | TBD Q1 2025 | |||
Standard OEM Agreement A legal template with clear licensing terms, updated by the legal team. Michael Maggio legal | External | Written | COMPLETED | TBD | ||
UC Federated Data License Setup Instructions for assigning Federated Data Licenses within the OEM account, defining access permissions and entitlements. What can we share from IP-restricted documents? Legal | Internal | Written | No Change | TBD | ||
OEM Federated Data License It needs to be incorporated in agreements.
Legal Review agreement with team. | External | No Change | TBD | |||
Initial Document Setup List of starting Authority Documents (IDs, names) for each ISV, referenced in the OEM agreement. Customer Success & Sales | Internal | written | In CCH account 26775 20241112_OEM Framework Families.xlsx UPDATING | In CCH account 26775 | ||
Onboarding and Account Configuration Guide | ||||||
Onboarding
| External | Written | ETA 12/2/24 https://support.unifiedcompliance.com/cch-oem-vendor-api-quick-start-guide NEEDS REVIEW | Net New Needed. ETA 12/2/24 New (NextGen) OEM Partner - API Quick Start Guide IN PROGRESS | ||
Cobranding Guidance | TBD Leverage Amazon info. See Mack | TBD Leverage Amazon info. See Mack | ||||
Account & Subscription Setup & Management Guide Step-by-step guide for creating, configuring, and maintaining OEM partner accounts within UC’s systems (CCH or other systems), detailing the process for Sales and Dev. CS, Sales, Dev/Product | Internal | Visual & Written | Legacy (CCH) OEM Partner - Set up Steps NEEDS TRIAL | New (NextGen) OEM Partner - Set up Steps NEEDS TRIAL | ||
OEM Partners API Guide Step-by-step guide for generating API keys and accessing data via API endpoints. Development & Support | External | Written | ||||
Schema Guide for Data Migration Visual and text documentation of the new data structures for each API endpoint, especially for transitions from old to new IDs and structures. | External | Visual & Written | TBD ETA 11/22/24 | |||
Sample Customer Journey for API Access Simple outline for an OEM customer’s end-to-end experience, covering account setup, API key access, and documentation handoffs. Use OEM Demo account. Customer Success & Product Management | External | Visual | TBD Low Priority | TBD Low Priority | ||
FAQs Commonly asked questions to guide OEM partners through their journey. Customer Support & Product Management | External | Written | TBD API Quick start Guide what endpoints will i be able to see what happens to save builds? Can I have CCH and OEM license? Meet after Thanksgiving Holiday? | TBD | ||
Billing, Invoicing, and Reporting | ||||||
Financial Reporting and Invoicing Guide Template and instructions for billing, invoicing, and financial reporting, tailored for OEM ISV partners. | External & Internal | Written | TBD | |||
Cross-Functional Collaboration and Handoff Processes | ||||||
Handoff Summary Key handoff points for each team (e.g., Sales, Dev, Finance), including communication tools, points of contact, and role responsibilities. | Internal | Visual & Written | Written TBD | Written TBD | ||
Content Providers
Resources
PlantUML - https://UCFNextgen.ai/public/plantuml/956
Content Provider agreement template (signed with redistribution rights and compensation requirements) | |
Content Provider subscription plan/add-on set up. | |
Content Provider account set up including CP designation in our backend for entitlement verification that UC has rights to redistribute their content and for usage reporting. Yes, an organization can be a Content Provider, ISV, and a reseller. | |
Content Provider entitlement set up in our backend for entitlement verification which ISVs and customer accounts are entitled to receive redistributed Content Provider content. | |
Content Provider renumeration based on subscription content usage. | |
Content Provider usage reporting by subscription plan with associated accounts, by AD with associated accounts and by Accounts with associated ADs. |