Uses of Specification Categories

[Mahesh_Krishnan]

Hello All:

I understand what Specification Categories do and how they link to Model Categories to drive the creation of CIs and Assets. If we are not interested in the inventory management and management of the CIs and are using OMT purely for order decomposition and integrating with source order systems is the creation of unique Specification Categories useful. I am looking for real-life examples of how you have used the categories to drive fulfillment flow so that I can get some ideas.

Thank you in advance for your time!

Mahesh

[ShashankInamdar · Accepted solution]

Hi @Mahesh_Krishnan ,

Keeping aside the CI/Asset part, Specification Category is useful when defining invocation conditions for the Orchestration Subflows (in Decision Tables).

Creation of unique specification categories does not need to be per product/service/resource specification. A classic example of when Spec Category is useful is when you have two different types of group of products which have dissimilar fulfillment flows, but all products within the group have the same fulfilment flows.

In such a case, when defining the invocation conditions for all products belonging to the same group will need only one entry in the decision table if the Spec Category is used as against defining it per specification.

Thus, in the example quoted for two unique group of products you will end up having only two entries in the Decision table.

This can extend to other logic as well whereever all products belonging to the same group gets the same treatment, such as in Jeopardy Management, Fallouts, OMT-FSM integration, etc. Thus, saving a lot of effort and maintenance.