Integration Packages Definitions and Services

  1. Definitions. All terms not otherwise defined in this Integration Packages Definitions and Services schedule shall have the same meaning as in the Agreement or the Support Packages Definitions and Services schedule, as applicable.
    1. “Ad-hoc Calls” means reoccurring calls between Company and with the Solutions Architect, Customer Success Manager, Delivery Manager, or Solutions Engineer on an established cadence or as reasonably scheduled between the parties to review priority integration issues that cannot wait for reocurring scheduled meetings.
    2. “Best Practice Consultation” means advice from a Solution Architect  regarding commonly used best practices by Bitmovin customers for successful integration, deployment, and ongoing use of the Bitmovin Solution.
    3. “Custom Prototypes” means customized examples of code or implementations reflecting specific customer use cases that may be used directly or with modification.
    4. “Delivery Manager” means a named technical resource responsible for managing complex integration projects across the Bitmovin team, coordinating the necessary resources to complete an Integration Package or SOW.
    5. “Feature Requests” means specific requests to change the Bitmovin Solution or the Bitmovin Technologies during or after the integration project. Bitmovin will estimate the required level of effort and may slot requests for delivery in an upcoming feature release if deemed to align with its product strategy. However, delivery timelines cannot be guaranteed until committed.
    6. “Integration Team Meeting” means reoccurring calls between Company and with the Solutions Architect, Customer Success Manager, Delivery Manager, or Solutions Engineer on an established cadence or as reasonably scheduled between the parties.
    7. “Onboarding Workshop” means a meeting between Company and a Customer Success Manager to assist in Company’s initial deployment or training of the Bitmovin Solution.
    8. “Prioritized Issues” means specific tickets submitted by the customer where Bitmovin and the Customer recognize they are of high priority due to a specific business or project impact. These tickets Bitmovin will take through bi-weekly solution prioritization to expedite engineering investigation and resolve where possible.
    9. “Standard Code Examples” means references to existing documentation and/or GitHub repositories to help the project team integrate common use cases.
  2. Integration Support Packages. Should Company purchase Integration Support subject to a valid Order Form, Company will receive the following one-time services for each respective Integration Support package:
Integration PackageBaseStandardComplex
DurationUp to:
  • 4 weeks, or
  • 24 person-hours
  • whichever occurs first
Up to:
  • 8 weeks, or
  • 68 person-hours
  • whichever occurs first
Subject to the terms of the SOW attached to a valid Order Form as Schedule 3
Onboarding WorkshopIncludedIncludedIncluded
HoursBusiness HoursBusiness HoursBusiness Hours
Targeted Response Times2 Business Days2 Business Days1 Business day
Consultative ServicesConfiguration guidance
General product guidance
Publicly available Documentation
Best Practice Consultation
Standard Code Examples
Configuration guidance
General product guidance
Publicly available Documentation
Best Practice Consultation
Standard Code Examples
Configuration guidance
General product guidance
Publicly available Documentation
Best Practice Consultation
Standard Code Examples
Custom Prototypes
Prioritized IssuesNot IncludedNot IncludedIncluded, subject to limitations base on:
  • Available Workarounds
  • Reasonable alternative means to meet requirements
Feature RequestsUnless defined within a SOW, all feature requests raised during the integration package duration will be provided to Bitmovin product management, utilizing Bitmovin’s product feature request process.
Unless defined within a SOW, all feature requests raised during the integration package duration will be provided to Bitmovin product management, utilizing Bitmovin’s product feature request process.Unless defined within a SOW, all feature requests raised during the integration package duration will be provided to Bitmovin product management utilizing Bitmovin’s standard product feature request process.
Bitmovin will use reasonable efforts to provide estimated delivery date in an attempt to meet Company’s requested due date.
Integration Team Solutions Engineer or Solutions Architect
Customer Success Manager
Solutions Engineer or Solutions Architect
Customer Success Manager
Solutions Engineer or Solutions Architect
Customer Success Manager
Delivery Manager
Communication during IntegrationDedicated Channel
Bi-Weekly integration team meeting
Dedicated Channel
Bi-Weekly integration team meeting
Ad-hoc calls as mutually agreed upon
Dedicated Channel
Bi-Weekly integration team meeting
Ad-hoc calls as mutually agreed upon

End of Bitmovin Integration Support Packages Definitions and Services

DATE: January 1, 2023