Chordiant v/s Pega
All,
I am looking for a document or post that can explain the similarities/differences between Chordiant & Pega (or the benefits of using Pega over Chordiant) to a client of mine interested in upgrading to Pega. I am sure most clients would have asked this question, so I want to utilise this research rather that build something from scratch. Client is currently using CDM 6.4 for decisioning.
It would be helpful if I can get some terminology assistance like Session Data Store in Chordiant is now Clipboard in Pega.
Regards,
Swapnil
Learning
IN
Hello Kashyap,
Kindly check some differences between pega and chordiant.
1. Type of Tool
Chordiant: Chordiant is a CRM tool. Customer Relationship Management tool. For example this tool can be used as a full fledged call center application tool. It handles end to end
activities, and captures everything provided some customization is needed.
Pega: Pega rules process commander is more of a business process management tool. This tool can be used to automate, any business process in an iterative manner. As the tool says, “Build for Change”.
It has a built in rules engine. Here in Pega every entity is called as a rule.
2. Flow or business process
Chordiant: Chordiant uses BPD (Business Process Diagrams) with its system tasks, client tasks and connectors to create a flow.
Pega: Process commander uses Process flows more like bpel standard flow shapes which we can use Visio to build. Each work item or a work object will have to move through
this process flow to complete its process.
3. Model layer
Chordiant: Chordiant uses Business Objects, Business Services, Backing beans to implement the business logic.
Pega: Process commander uses Activity, Property, class, decision tree, decision table, etc., to implement the business logic.
4. Development environments
Hello Kashyap,
Kindly check some differences between pega and chordiant.
1. Type of Tool
Chordiant: Chordiant is a CRM tool. Customer Relationship Management tool. For example this tool can be used as a full fledged call center application tool. It handles end to end
activities, and captures everything provided some customization is needed.
Pega: Pega rules process commander is more of a business process management tool. This tool can be used to automate, any business process in an iterative manner. As the tool says, “Build for Change”.
It has a built in rules engine. Here in Pega every entity is called as a rule.
2. Flow or business process
Chordiant: Chordiant uses BPD (Business Process Diagrams) with its system tasks, client tasks and connectors to create a flow.
Pega: Process commander uses Process flows more like bpel standard flow shapes which we can use Visio to build. Each work item or a work object will have to move through
this process flow to complete its process.
3. Model layer
Chordiant: Chordiant uses Business Objects, Business Services, Backing beans to implement the business logic.
Pega: Process commander uses Activity, Property, class, decision tree, decision table, etc., to implement the business logic.
4. Development environments
Chordiant: Chordiant can be developed using Rational Application Developer, Rational Software Modeller, and even a version eclipse can be used.
Pega: Process commander can be developed using its own developer interface.
5. Frameworks
Chordiant: Chordiant has a few frameworks like CCABE, Foundation Server, CDM, etc.,
Pega: Process Commander has a few frameworks like CPM, PegaCall, Smartbuild, etc.,
6. Presentation layer
Chordiant: Chordiant uses its client task in combination with chordiant jsf to build it users interface.
Pega: Process commander uses Harness, Section, HTML Fragment, jsp, HTML streams to build its user interfaces. All these are pega’s own rule types. Every entity in process commander is a rule.
7. Debugging options
Chordiant: Whatever utility is available in RAD, eclipse.
Pega: Process commander provides different tools like tracer, clipboard, DBTrace, PAL, etc.,
8. Owner
Chordiant: Chordiant was acquired by PegaSystems. So now its owner is PegaSystems. Chordiant is now called as Pega.
Pega: Process commander is owned by PegaSystems.
Kindly check the below link for your reference.
https://collaborate.pega.com/discussion/migrate-chordiant-pega
Hope this helps.
Thanks & Regards,
Hari Chalamala
Instellars
GB
I see that the answers you supplied are from this site address that has a comparision between Chordiant Foundation Server and Pega: http://www.pega4u.in/pega4u/2012/05/29/chordiant-foundation-server-vs-pega-process-commander/
I am however looking for a comparision more specifically with Chordiant Decision Management and Pega (DSM). Apologies if the question was ambiguous. So I will let this question remain not answered. Can anyone shed some light?