Cordys PAAS – Business Operations Platform

At the Informa Smart cities and Cloud event in October, I met Joe Allott, Principal solutions architect at Cordys

I have been tracking Cordys for a while after an initial meeting a few years ago, so this is a good time for a brief post following my meeting with Joe

Firstly, some overview bullet points and then my analysis below

  • Key areas: The key areas for Cordys are – Being a Cloud enabled software platform and providing a Single stack solution
  • Who is the solution addressed to: Through a channel to entreprises or service providers (with data center capacity, telecom service provider etc) end esure, banking customers. Also targeting specific verticals – Insurance, Banking, energy etc
  • What is the Differentiation: Single stack, on premise, cloud , Single product or part of it (provisioning ) , Highly agile, Visually modelled with drag and drop in a browser environment.
  • Use cases: KPN telco order management, powel systems, zurich

 

Analysis: 

The above is common to many cloud platforms. I wanted to know what is unique about the Cordy’s platform.

My analysis is as follows: Cordys comes from the background of Baan systems which gained some traction in the ERP era.

IDC says - “Cordys BOP is suitable for process projects ranging from simple to the most sophisticated.”

The Cordy’s BOP ( Business Operations Platform) enables Business Process Management, SOA Integration and a Composite Applications framework in one single platform which can be deployed on-premise or in the cloud. It includes business process design, execution, monitoring and improvement. It is designed to help business managers to  align business process implementations with company goals. It also facilitates organizational improvement , control and visibility into process metrics and real-time business activity.

The goal is to bring the business and IT worlds together.

Thus, the core value proposition is based on the Cordy’s BOP model which creates a process layer on top of existing enterprise systems and talks via web services and connectors to existing core investments. This task involves orchestrating across different systems, Master data management and other functions which create the process layer that acts as a glue.

Thus, I agree with the IDC analysis that the core proposition is the BOP (the ability to create a process layer across the enterprise assets)

 

 

I think this fits in well with their origins (Baan/ERP) and one could look at it as combining the classic enterprise (ERP) functionality with a process layer and deploying via the Cloud.