Resources:
https://support.unifiedcompliance.com/cch-oem-vendor-api-quick-start-guide
View file name FINALUSEFederated Data License.pdf
Legacy
| View file | ||
|---|---|---|
|
| View file | ||
|---|---|---|
|
Artifact | Audience | Type | Status, Link/Location | |||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Legacy | New | |||||||||||||||||||||||
Pre-Agreement Documentation & Initial Outreach | ||||||||||||||||||||||||
Sales Brief
| Internal | Doesn’t exist As of 12/3/24 | Doesn’t exist As of 12/3/24 | |||||||||||||||||||||
Solution Brief OEM Program Overview (outgoing UC Sales guide to partners). One-page or webpage summary covering program benefits, features, and partnership terms.
| External | Written |
Needs updating As of 12/3/24 Jody is updating | Solution Brief Transition Guide: (OEM Conversion) How to transition from legacy to new. Additional features and benefits of full CCH license
| External | written | First Customer Call Deck | Written | Sales Enablement Training: Teach Partner sales team to sell UC in their productNeeds updating As of 12/3/24 Jody is updating | |||||||||||||||
First Partner Call Talking Points First call with UC team and potential partner to explain in detail the offering. Some technical and packages - takes 1-pager and provides more detail.
| External | written | TBD Q1 2025 | Written | Doesn’t Exist As of 12/3/24 | Doesn’t Exist As of 12/3/24 | ||||||||||||||||||
Standard OEM Agreement A legal template with clear licensing terms, updated by the legal team.
| External | Written | https://unifiedcompliance.sharepoint.com/:w:/s/CustomerSuccess/EUxLdYRBm_dPgGIX2TGV0iIBNaY4RsognimpvZdOaCjG0A?e=afA6BI
Current version as of 12/12 - still have a couple of points and questions to clarify. |
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?
| Internal | Written | No Change | Template in hubspot.
Archived OEM Agreement versions - do not use. -TBD | ||||||||||||||||
| OEM Federated Data License | External | No Change | Addendum in Contracts | Internal | written | In CCH account 26775 20241112_OEM Framework Families.xlsx
| In CCH account 26775 | ||||||||||||||||
Onboarding and Account Configuration Guide | ||||||||||||||||||||||||
Onboarding and Account Configuration Guide | ||||||||||||||||||||||||
Partner Onboarding Deck How to transition from legacy to new. Additional features and benefits of full CCH license
| External | Writtenwritten | ETA In progress as of 12/23/24 https://support.unifiedcompliance.com/cch-oem-vendor-api-quick-start-guide
| Net New Needed.ETA (will clone Legacy and remove some slides) As of 12/23/24 New (NextGen) OEM Partner - API Quick Start Guide
Partner Marketing
Marketing - Amanda | TBD Leverage Amazon info. See Mack etc 12/6/24 | TBD Leverage Amazon info. See Mack etc 12/6/24 | Public Customer References Marketing - Amanda | |||||||||||||||||
Initial Document Setup List of starting Authority Documents (IDs, names) for each ISV, referenced in the OEM agreement.
| Internal | written | In CCH account 26775 20241112_OEM Framework Families.xlsx
| In CCH account 26775 | ||||||||||||||||||||
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.
| Internal | Visual & Written | Legacy (CCH) OEM Partner - Set up Steps
| New (NextGen) OEM Partner - Set up Steps
| ||||||||||||||||||||
Sales Enablement Training Teach Partner sales team to sell UC in their product.
| External | written | TBD Q1 2025 | |||||||||||||||||||||
Partner Marketing
Marketing - Amanda CS - Dorothy Hunt | External | TBD Leverage Amazon info. See Mack etc 12/10/24 | TBD Leverage Amazon info. See Mack etc 12/10/24 | |||||||||||||||||||||
OEM Partners API Guide Step-by-step guide for generating API keys and accessing data via API endpoints.
| External | Written | Legacy (CCH) OEM Partner - API Quick Start Guide https://support.unifiedcompliance.com/cch-oem-partner-api-quick-start-guide | New (NextGen) OEM Partner - API Quick Start Guide Support Article in creation as of 12/3/24 | ||||||||||||||||||||
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 | External | Visual | TBD Low Priority | Will need updates based on scope change (i.e. leveraging legacy IDs in nextgen) as of 12/3/24 Support Article in creation as of 12/3/24 | ||||||||||||||||||
FAQs Commonly asked questions to guide OEM partners through their journey.
| External | Written | TBD API Quick start Quickstart 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 as of 12/3/24 Still needs to meet TBD | |||||||||||||||||||||
Sample Partner Journey for API Access Simple outline for an OEM Partner’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 | ||||||||||||||||||||
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 | WrittenTBD | Not created as of 12/3/24 | Not created as of 12/3/24 | ||||||||||||||||||||
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 | ||||||||||||||||||||
Success Stories | ||||||||||||||||||||||||
Public Partner References CS - Dorothy Hunt Marketing - Amanda | ||||||||||||||||||||||||
Potential Additional Prerequisites | ||||||||||||||||||||||||
UC Federated Data License Instructions for assigning Federated Data Licenses within the OEM account, defining access permissions and entitlements. What can we share from IP-restricted documents?
| Internal | Written | No Change | Template in hubspot.
| ||||||||||||||||||||
...
Content Providers
Resources
...
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. |
Resources:
https://support.unifiedcompliance.com/cch-oem-vendor-api-quick-start-guide
- templateView file name FINALUSEFederated Data License.pdf
- UC official as of 12/4/24 (needs to be put up on UC site)View file name NF Data License Agreement (2024-06-26).docx
Legacy
| View file | ||
|---|---|---|
|
| View file | ||
|---|---|---|
|