Publications, Policy and Violations

Read the SAP Standard Application Benchmark Publication Policy to learn about practices for the publication of information related to SAP Standard Application Benchmarks.

Publication violations recognized by the SAP Benchmark Council workgroup are listed in the table below. The table includes a high-level description of the violation, corrections suggested by the workgroup, and reasons for accepting the ruling.

SAP Standard Application Benchmark Publication Guide

Want to learn more?

Contact us or call the SAP sales office nearest you.

Date of Workgroup Decision Violating Company Name

Description of the Violations

Suggested Correction Actions

Clarification of the Workgroup

5/5/2011 IBM In April, IBM violated the benchmark publication guidelines in an advertisement on their Web site. Price/performance statements were made with reference to SAP SD benchmark results Explicitly state that only TPC results are used for price/performance, not SAP. Refer to section 4.2.8 of the benchmark publication policy.
8/4/2010 IBM In February, IBM violated the benchmark publication guidelines in a presentation on their web site. Price/performance statements were made and the minimum data concerning the benchmarks mentioned was not provided. Remove the information related to price/performance and add the required minimum data. Refer to sections 1 and 4.2.8 of the benchmark publication policy.
7/3/2008 IBM In May, IBM violated the benchmark publication rules by including performance per watt information in conjunction with benchmark results on their public Web site. Remove the information related to power consumption from the web page Refer to section 4.2.2 of the benchmark publication policy.
6/5/2008 IBM In May, IBM published a presentation at an international event which violated the benchmark publication guidelines. Incorrect leadership statements were made and the minimum data concerning the benchmarks mentioned was not complete. Change the presentation Refer to chapter 1 and sections 4.1, 4.2 and 4.3 of the benchmark publication policy.
11/2/2006 IBM In October, IBM published a press release in which it violated the benchmark publication guidelines concerning the minimum data required. Change or remove the Web page. Refer to chapter 1 of the benchmark publication policy.
3/2/2006 HP In January, HP violated the benchmark publication by including pricing information in conjunction with a benchmark result on their public Web site. Change the Web site. Refer to sections 4.1 and 4.2 of the benchmark publication policy.
12/8/2005 Microsoft In November, Microsoft published a press release in which it violated the benchmark publication guidelines concerning the minimum data required. Change press release on the Web site. Refer to section 1.1 and 1.2 of the benchmark publication policy.
3/4/2004 IBM In February, IBM published a press release violating the fence claim rules. Change press release on the Web or remove it. Refer to section 4.11 of the benchmark publication policy.
6/11/2003 Oracle In May 2003, Oracle published benchmark information on a web page that contained misleading information, such as the new definition of benchmark categories and record results in these. The minimum data for comparing benchmark results was not included. Change the Web site. Refer to sections 4.1, 4.2 and 4.6 of the benchmark publication policy.
3/6/2003 IBM On February 7, 2003, IBM published a press release that included pricing information about the benchmarked system. Change the Web site. E209Section 4.8 (document version 2.3) of the publication policy stipulates that pricing information should not be included in a press release
SAP should not have approved of the press release
6/12/2002 IBM In May 2002, IBM did not include the minimum data for two benchmark results in an advertising campaign. Since the running campaign cannot be stopped, include minimum data in new advertisements. Refer to section 1 of the publication policy.
2/7/2002 Oracle In December 2001 and January 2002, three Oracle publications were found to be violating the publication guidelines by comparisons of different tests and misleading benchmark information. Since the running campaign cannot be stopped, include minimum data in new advertisements Refer to sections 4.1, 4.2, and 4.3 of the publication policy.
7/12/2001 Oracle In June 2001, a non-existing "Standard SAP SD Light Benchmark" was mentioned in a public presentation on Oracle's homepage. Change the Web site. There is no "Standard SAP SD Light Benchmark".
7/12/2001 Oracle In June 2001, Oracle compared two SAP Standard Application Benchmark results in a press release without stating the appropriate publication details. Change press release on the Web. Refer to section 1 of the publication policy.
7/12/2001 Oracle In June 2001, Oracle did not include the minimum data for two benchmark results in an advertising campaign. Since the running campaign cannot be stopped, include minimum data in new advertisements. Refer to section 1 of the publication policy.