cpq.se
we help nordic small- and midsized manufacturers get started with tools for configuration, pricing and quoting
Get Started
Showing posts with label Tacton CPQ. Show all posts
Showing posts with label Tacton CPQ. Show all posts

Constraints, rules or relations - what's the difference?

Posted On Tuesday, October 8, 2019



In CPQ, there's a lot of talk about the way you describe how the products can be configured. Some vendors talk about constraints, some about rules, some try to get around it by calling it constraint rules (I'm looking at you Apptus!).

All in all though, who cares about what they are called? The more important question is how easy they are to set up and maintain.

Tacton calls it constraints. If you look up the word constraint, it's a limitation or restriction - which is actually a good way to think about it. Without constraints all combinations of all items in the product can be combined in any way the customer wants. With a constraint, you limit the way you can combine the product.

So if you have 100 rims and 100 tyres, and you want to describe the valid combinations of these - how do you do?

In Tacton, you try to figure out the natural law, of why they work together. So, why does a tyre work with a rim? Well, they obviously have to fit. So the width of the rim needs to match the width of the tyre. In Tacton language:

rim.width=tyre.width

And that's it. It's a natural law. It's true today, and it's true tomorrow. Most likely it's true in 10 years (if we haven't come to flying cars by then...). I want to point out, that usually, there's a number of constraints working together, so there's going to be constraints about diameters, materials, tyre patterns etc. But let's stick to one constraint for now.

So now you may be thinking, is there any other way? This seems to be the smartest way?

Yes, this is the smartest way - but there are many more ways you can do this. You can write relations, e.g.

tyre A works with rim A, B and D
tyre B works with rim C
tyre C works with rim D and E

This works. And sometimes this is the only way to describe the product (typically where things have to be tested to ensure it works). But this way stinks in general, because is the first relation true tomorrow? Maybe, maybe not. Who knows? So it becomes a very cumbersome way to describe things. Also, this is an easy way to get to 10,000 rules or more.

So, in summary. Ignore what the product description method is called. But do make sure it's easy to set up and maintain over time!

Tacton CPQ Enterprise vs. Tacton CPQ Professional

Posted On Thursday, September 26, 2019

Tacton CPQ is available in two editions – Tacton CPQ Enterprise and Tacton CPQ Professional.

The Professional Edition is an out-of-the-box solution with predefined industry-specific workflows, templates and processes. This typically meets the needs of small and medium businesses looking for the advantages of a standard CPQ solution.

The Enterprise Edition can be more tailored to meet specific business requirements and extends the functionality of Tacton CPQ with even more configurability.

So, what’s the big difference?

In Tacton CPQ there are different objects very much in the same fashion as you find in CRM-systems like Salesforce and Microsoft Dynamics. Standard objects are Account, Opportunities, Solutions, Approvals, just to name a few.

In Tacton CPQ Professional all necessary objects are already predefined but new objects can not be created, but the existing objects can be tailored. In Tacton CPQ Enterprise it is possible to create new objects.

So, what does this mean? 

Let me give an example…

Say that you have something called “Purchasing agreements” that gives certain customer an extra discount for selected pricelists. Both Tacton CPQ Professional and Tacton CPQ Enterprise supports pricelists, but if you want to add additional business logic to your pricing combining pricelist with account one way to do this would be to define a new object, a purchasing agreement object.

In practice this means that if the initial CPQ-analysis shows that there might be a need for one extra object there is usually no need to worry. If we wanted to solve a few “Purchasing agreements” we could extend the pricelist objects, add a few extra pricelists and the problem would have been solved. 

The real difference is when there is a need for multiple new objects to sort out complex business logic. So, rule of thumb is to move to Enterprise once such complexities gets too tricky.

There are a few limitations to Tacton CPQ Professional that one needs to take into consideration. In the table below we point out the major differences in the table below.


Tacton CPQ Professional
Tacton CPQ Enterprise
Advanced Configuration
X
X
Advanced Pricing
X
X
Simple document generation
X
X
Advanced document generation
-
X
CPQ Branding    
-
X
Workflows
X
X
Lead generation
-
O
Industry-standard User roles
X
X
Custom User roles
-
X
Business approvals
X
X
Technical approvals
X
X
Visualization
O
O
iPad App
O
X

Tacton CPQ Professional is set up based on years of CPQ-experience to give an out-of-the-box setup ready to tackle the common CPQ challenges. In the illustration below the standard workflow and supporting objects are displayed. To put it simple; if you need to define more blue or gray boxes Tacton CPQ Professional is not for you. If you think that your business operates like most businesses, you should probably get started with Tacton CPQ Professional. 



So, what about the price? Is there a difference? What do I need to pay?

We’ll let you do the math and give you a clue; if you pay the same amount of dough Tacton CPQ Professional will increase your number of users by 50 % compared with Tacton CPQ Enterprise.

It’s our firm belief that 90 % of small and medium business will be more than satisfied with Tacton CPQ Professional. After a CPQ Analysis workshop we can tell you for sure.
Powered by Blogger.
/

Get In Touch

Lyckan 7, 753 24 Uppsala, Sweden
+46 736 614 953
info@cpq.se

Contact Form

Names

Email

Message

© cpq.se. All Rights Reserved