Oracle v. Rimini Street Lawsuit Verdict: Good for Third-Party Maintenance

Earlier this month, the jury in Las Vegas reached its verdict in the Oracle v. Rimini Street lawsuit, a closely-watched case involving third-party maintenance (3PM) in the enterprise software industry.

Although the jury awarded Oracle approximately $50 million in damages, the amount was far below what Oracle expected. Moreover, the jury found that Rimini Street’s copyright infringement was “innocent,” not “willful,” that Oracle suffered no lost profits as a result, and that neither Rimini Street nor its CEO, Seth Ravin, engaged in any tortious business conduct.

Assuming the jury’s verdict stands up against potential appeals, the case sets an important precedent for how 3PM providers should operate to ensure they are not violating the intellectual property rights of software owners. We expect customer use of third-party maintenance will increase as a result of this verdict.

Read this entire post on the Strativa blog: Oracle v. Rimini Street Verdict Clarifies Ground Rules for Third-Party Maintenance

Sage Puts Stake in the Cloud with Sage Live

Sage is one of the world’s largest providers of business applications for small and midsize organizations. Now in the cloud it has taken a big step forward, launching Sage Live, a built-from-scratch accounting system on the Salesforce.com platform.

This post outlines key features of Sage Live, the challenges it will face, and recommendations for potential buyers.

Read this post on the Strativa blog:  Sage Puts Stake in the Cloud with Sage Live

AscentERP Rises in the Cloud ERP Market

AscentERP is a cloud ERP provider building on the Salesforce platform, with a focus on manufacturing and wholesale distribution companies. Though not as well-known as other ERP providers on the platform, the company is doing some interesting work within its industry focus.

This post provides an update to our previous coverage of AscentERP.

Read this post on the Strativa blog:  AscentERP Rises in the Cloud ERP Market

FinancialForce Expands Its Footprint in Cloud ERP

FinancialForce continues to show strong momentum in the cloud ERP market, and it is building out its product capabilities in interesting ways.

In this post, we provide an update on FinancialForce, based on interviews we conducted with its executives at Dreamforce, the annual conference for users of Salesforce.com. We also provide recommendations for buyers considering FinancialForce.

Read this post on the Strativa blog: FinancialForce Expands Its Footprint in Cloud ERP

Rootstock's Momentum in Cloud ERP

Rootstock Software is an up-and-coming cloud manufacturing ERP provider, built on the Salesforce.com platform. Last year, I covered Rootstock in a post about four ERP systems in the Salesforce ecosystem. This year, the annual Dreamforce conference gave me the opportunity to interview Rootstock executives and customers about the progress the firm has made over the past year.

In short, Rootstock is showing good momentum, nearly doubling its publicly announced customer count over the past 18 months. It is also building out its product offerings by developing its own native accounting applications and extending its business intelligence capabilities utilizing Salesforce Wave Analytics.

Read the full post on the Strativa website: Rootstock Rounding Out Its Cloud ERP Offerings.

Kenandy Has a Contrarian View Toward Two-Tier ERP

Salesforce.com is proving to be a popular platform for developing ERP systems, and its annual user conference, Dreamforce, has been a great way to catch up with all of them in one place.

Last year, I provided an update on the four ERP providers building on the Salesforce platform in a single post. This year, I want to provide an update on these, starting with Kenandy.

Unlike cloud-only ERP providers such as NetSuite and Plex, Kenandy is not interested in a "two-tier ERP strategy." The strategy of "two-tier" refers to the targeting of small divisions or operating units of larger companies that are running Tier 1 solutions, typically SAP or Oracle, at headquarters and in larger divisions. The cloud provider then targets its ERP solution for smaller divisions of the company with integrated to the corporate system, usually for shared services such as financials, central order processing, or cross-company supply chain management. NetSuite points to customers such as Jollibee Foods and NBTY (China) Trading Company as multinational companies implementing NetSuite in a two-tier strategy. Similarly, Plex boasts of Caterpillar and Inteva Products as success stories in two-tier ERP.  

Going against this trend, Kenandy executives say that, although they will not turn away two-tier opportunities, they would rather work in what they consider a more strategic role with customers. This means targeting (1) large enterprises for a complete ERP solution, or (2) serving as a more agile "orchestration" solution for new lines of business within large enterprises.

Read the full post on the Strativa website: Kenandy: Against the Tide of Two-Tier ERP

More Than a Deployment Option: SaaS Is a Business Model

With the increasingly popularity of software as a service (SaaS), enterprise software vendors today cannot afford to be without a cloud strategy. As a result, traditional vendors have introduced various forms of hosted, hybrid, and SaaS deployment options. These co-exist alongside the vendor’s traditional on-premises license model.

But software as a service is more than just another deployment option, another way to consume software. SaaS is a business model. SaaS not only affects the product: it should drive the nature of how the provider does business, from how the product is developed and maintained to how it is sold, implemented, and supported. It should permeate the very culture of the provider’s organization.
How should the business model of a SaaS provider be different from that of a traditional software vendor? There are at least six aspects.

Read the rest of this post on the Strativa blog: Beyond Deployment Options: SaaS as a Business Model.

Big Changes at Microsoft Dynamics

In a letter to Microsoft employees today, CEO Satya Nadella announced a major restructuring of its business, including what is essentially a disbanding of Microsoft Business Solutions (MBS), the group responsible for Microsoft Dynamics.

• Dynamics product development teams will now report up into the new Cloud and Enterprise unit (see above)
• Dynamics sales and partner relationship organizations will now report to Kevin Turner, Microsoft’s Chief Operating Officer
• Dynamics marketing functions will now be handled directly by Microsoft’s CMO, Chris Capossela, and his team.

Now, some observers and some competitors will be tempted to say that Microsoft is abandoning its Dynamics products. But, in our view, it would be more accurate to say that the Dynamics products are becoming a more integral part of Microsoft’s overall portfolio. There are three arguments in favor of this positive view of Dynamics.

Read the full post on the Strativa blog:  Microsoft Unbundles Its Dynamics Business Unit

The Problem with ERP Requirements Templates

Companies undertaking a new ERP vendor selection often begin the effort by using a standard template of ERP system requirements. Though requirements checklists may appear to be a time-saving way to get to a requirements specification, this approach can actually make the project longer and cost more than it should. Moreover, use of requirements templates can actually lead to the wrong ERP system being selected.

In this post, we identify the problems with the use of ERP requirements templates and outline a better way for specifying requirements for new ERP systems.

Read the rest of this post on the Strativa blog: The Problem with ERP Requirements Templates.

Oracle Sued by Customer over Source Code Access

Oracle was hit by a customer lawsuit earlier this month in conjunction with its MICROS Systems business, which Oracle acquired in 2014.

The dispute involves access to the source code for the MICROS Open Commerce Platform.  Aero maintains that when it licensed OCP, MICROS (not yet acquired by Oracle) knew that Aero intended to build customizations and new features to integrate with OCP.

Aero alleges that MICROS personnel represented that Aero would have ongoing access to OCP source code in order to build its customizations and maintain them going forward.

Although we do not yet know all of the facts, there is a lesson in this case for companies seeking to become digital businesses.

Read the rest of this post on the Strativa blog:
Oracle Sued by Customer over Access to MICROS Source Code