Any Non-Windows Implementation Is Not RP 1210-Compliant

As of this writing, the Right to Repair (R2R) Memorandum Of Understanding (MOU) has been signed and this section has been modified. Therefore, TMC notes - within the spirit of the MOU - that any application implemented on anything other than on a fully functional Windows-based platform (including CE and other embedded Windows variants) is not  RP 1210-compliant. The reason that the previous sentence is necessary is that if TMC allowed non-Windows platforms to be RP 1210-compliant:

• OEMs that are signatories of the MOU could deploy an application on a non-Windows machine and still meet the letter of - but not the spirit of - the MOU in terms of being "RP 1210-compliant."

Here is an example of how this could create an unfair and proprietary situation for VDA vendors:

• VDA "Vendor #1" provides driver files to an OEM for their non-Windows platform and are not charged any money for inclusion.
• That OEM releases their application on the non-Windows platform with the drivers from "Vendor #1".
  • The OEM now has a working application, and has full control over other VDA vendors because the OEM has to perform work to add a competitive VDA's driver files to the OEM application.
• VDA "Vendor #2" wishes to be included and contacts the OEM that they have the drivers for that same non-Windows platform. The OEM says that it will cost them $500,000 to be ncluded and that the next release will not be out into the field for another nine months.