Content as a Service Scope and Services Description

Content as a Service Scope and Services Description

  1. Content as a Service (CaaS) Description
    During the CaaS Term, MindTickle will provide content services that can be broadly classified as:

    1. Content planning and review – Recommend appropriate output format, best practices and structure.
    2. Content development – Develop content that is compatible with the MindTickle Platform.
    3. Content migration – Assist with content migration on the platform.
  2. Deliverables 
    The final deliverables for every project will be in either one or combination of the below formats depending on the individual project:

    1. PowerPoint Deck (.PPTX)
    2. Videos (.mp4)
    3. Portable Document Format (.PDF)
    4. Word Documents (.DOCX)
    5. SCORM (.ZIP)
  3. Process 
    MindTickle will follow the process below to deliver each project to the Customer. Each of the steps below will have a Customer review and sign-off process before proceeding with the next step.

    1. Requirement gathering – Customer will explain the requirement, learning objective, learner profiles, and expectations around the module/project.
    2. Query resolution and output format – Customer will address MindTickle’s queries and brainstorm to finalize the desired output format to meet the training objectives.
    3. Content walkthrough – Customer provides a walkthrough of the content, addresses MindTickle’s queries, and provides a go ahead to start with the development.
    4. Content structure – MindTickle recommends a structure for the project
    5. Content design or development – MindTickle designs or develops content according to the project requirements.
  4. Assumptions for hourly bundle engagement
    1. MindTickle will maintain timesheets that will be shared regularly with the Customer to provide visibility on the hours consumed as well as the balance number of hours.
    2. The total number of consumed hours will not exceed the total CaaS Hours, except with the Parties’ mutual agreement as set forth in a separate Order or a change order as executed by the Parties.
    3. The Customer will provide the required subject matter expert support and the source content required for any content development project.
    4. For any project that will require professional voice-over recording services:
      1. MindTickle will provide sample(s) to the Customer. Once Customer approves the voice-over sample as well as the voice-over script, MindTickle will proceed with the recording.
      2. If there are any errors in the pronunciation and these are highlighted within 3 working days of voice-over delivery, the same will be re-recorded by the voice-over artist at no additional cost. However, re-recording resulting due to any changes to the voice-over script will require additional effort investment and additional Fees would be charged.
  5. Assumptions for dedicated resource engagement
    1. The maximum hours per working day and week shall be restricted to as specified in the Order. Any balance unused hours shall not be carried forward to the next day or week.
    2. The dedicated resource shall provide an estimate of the time required for completing the work post content analysis phase. The development plan shall continue as per the provided estimates, unless there is a change in the scope of work or re-prioritization of work by the customer.
    3. The dedicated resource shall be entitled to personal time off for 2 days every month.
  6. Project timelines for hourly bundle engagement
    1. On sharing a requirement, the Customer will provide MindTickle, with a lead time of 5 working days to start working on the requirement.
    2. The timeline for every project/task will be defined and communicated to the Customer by MindTickle following the “Query Resolution and Output format” step of the process.
    3. For projects/tasks with fixed, predefined timelines by the Customer, the Customer will notify MindTickle at the earliest date possible. MindTickle will then analyze the requirement, complete the “Query Resolution and Output format” step, and share the projected timeline to complete the project/task. If the projected timeline shared by MindTickle does not meet the target timeline required by the Customer, MindTickle and Customer will discuss and agree upon one or combination of more than one of the below options:
      1. Explore the possibility of adding an additional resource on the project to pull the expected timeline for completion. This can be explored only if –
        • There is an available lead time of minimum fifteen (15) business days before a resource needs to be added; and
        • The duration for which the additional resource is required is fixed and agreed upon.
      2. Decide on the minimum viable output to be delivered within the target timeline
      3. Explore the possibility of changing the output format in order to reduce the time investment required in development
    4. All timelines communicated by MindTickle will be based on budgeted Customer review timelines and project steps as set out in the project schedule.
  7. Acceptance Criteria
    • Customer shall have the right to review a deliverable within ten (10) calendar days of receipt of subject deliverable from MindTickle to check it complies with the specifications mutually agreed to by Customer and MindTickle. All the Customer feedback will be provided via email or in a format/template shared by MindTickle.
    • Before the end of the ten (10) calendar day review period, Customer shall respond to MindTickle in writing whether the subject deliverable is accepted by Customer.
    • If Customer does not respond to MindTickle in writing within the ten (10) calendar day review period, subject deliverable shall be deemed accepted by Customer.
    • If the Customer does not accept subject deliverable, then Customer shall provide detailed feedback specifying the required changes and reasoning in writing within the ten (10) calendar day review period.
    • Upon receipt of the detailed feedback, MindTickle shall make reasonable effort to revise subject deliverable and resubmit for review and acceptance.
    • Customer agrees to a total of two review cycles for each deliverable in scope.
    • If after a total of two attempts the deliverable fails to materially comply with the specifications, then Customer may reject the subject deliverable.
    • Customer shall receive a credit or refund, as mutually agreed upon by both Parties, of sums owed or paid, as applicable, for the development of the rejected deliverable.

MSIRobot