We’ve published several articles in this blog about expanding the functionality in Motive Integrator, refining our processes for Dealer System Certification, and even Self Certification. Our organization has made huge strides toward providing Subscribers and Publishers with the tools needed to effectively implement and test integrations.
We’ve talked before about how dealer systems integration is not just an IT thing. When designed well, integration between systems can deliver enormous business benefits to both dealers and OEMs.
When TiVo came along and freed people from the constraints of TV programming schedules, they were thrilled with the ability to watch shows “On Demand”. These days the concept of services or products being available “On Demand” is not only commonly understood, but increasingly it is expected. Now, in order to lower costs and satisfy customers, solutions of all sorts must be flexible, self-service and online.
A fundamental principle of Motive Integrator is to support the information needs of users in ways which improve efficiencies and offer flexibility during integration projects.
Our series on testing began last year and it’s time to pick this topic back up again with a new installment about the importance of Dealer Pilots. The Dealer Pilot phase is the last and final step in the certification process. It follows the completion of all Certification Testing and requires the deployment of the dealer system software for use by a dealer in live operations.
At Motive Retail we believe a formal certification process and program is critical for Automakers, DSPs and dealers.
In Part 3 of our Testing series, we talked about independent testing, specifically testing performed by DSPs. Perhaps the most critical aspect of an integration project is the coordinated testing (or Certification Testing) between both parties which so often is known for being cumbersome, slow and expensive.
Testing in any B2B integration initiative requires independent testing be performed by each “B”, i.e. the automaker and the DSP. It’s a critical aspect of any project as each party must take responsibility for testing its own integration code in advance of any coordinated / joint testing.
To begin, let’s talk about the types of testing needed when rolling out a new dealer systems integration . We group testing into 3 types or phases.
A third-party integration certification program which includes verification that the third-party dealer system complies with integration specifications provides great value to the automaker, the DSP and the dealers. A comprehensive testing process is the only way to ensure interfaces have been implemented correctly. Over the coming weeks, we will publish a number of posts on this topic, to highlight why testing is such an important element of any DSP integration program and how it can be implemented most effectively and efficiently. Our views on testing are informed by years of experience working with both OEMs and DSPs on dozens of integrations giving Motive a unique understanding of the perspectives, constraints and business objectives of both parties. Motive believes that for any certification program to be successful it must accommodate the needs of both sides. Look for upcoming posts about the nature of testing in a B2B integration program, the type of testing that is generally required and common pitfalls. We welcome your comments, questions and any anecdotes you may have from your experiences.