• Written by Azhar Aliyar, Director

In practice, a system like AsscherAi, which lets a large organisation query its own data in natural language and get answers in real time, often falls short of its promise when it comes to deciding whether to use one model or routing between several, as the choice between these two options can lead to vastly different outcomes, and most people get this wrong by assuming it is a simple either-or decision.

What each option genuinely commits you to

The choice between using one model or routing between several is not just a technical decision, but a commitment to a particular approach to handling requests, as one model commits you to a fixed set of parameters and assumptions about the data, whereas routing between several models commits you to a more complex system that requires ongoing maintenance and updates, and most people underestimate the complexity of the latter option.

For example, a category manager comparing two suppliers may find that a single model is sufficient for simple queries, but as the queries become more complex, the need for routing between several models becomes apparent, and the organisation must be prepared to commit to the additional resources required to support this approach, including the purchase order table and the maintenance log.

The case where the other one is right

There are cases where using one model is the better choice, such as when the requests are relatively simple and the data is well-structured, as in the case of a shift supervisor checking the maintenance log, where a single model can provide quick and accurate answers, and the added complexity of routing between several models would be unnecessary, and in such cases, the organisation should not be afraid to use a single model, as it can be more efficient and cost-effective.

On the other hand, when the requests are complex and the data is diverse, routing between several models may be the better choice, as it allows the organisation to handle a wider range of queries and provide more accurate answers, and in such cases, the organisation should be prepared to invest in the necessary resources to support this approach, including the development of new models and the integration of existing ones, and more information on this topic can be found on our website.

The cost that only shows up later

One of the costs of using one model or routing between several that only shows up later is the cost of maintenance and updates, as the models require ongoing support to ensure they continue to provide accurate answers, and the organisation must be prepared to invest in the necessary resources to support this, including the development of new models and the integration of existing ones.

This cost can be significant, and organisations should not underestimate the resources required to support their chosen approach, as the cost of maintenance and updates can add up quickly, and the organisation must be prepared to budget for this, and contact us for more information on how to plan for this cost.

A way to decide without a six month evaluation

One way to decide between using one model or routing between several without a six month evaluation is to conduct a thorough analysis of the requests and the data, including the types of queries that will be made and the structure of the data, and to use this analysis to inform the decision, rather than relying on a prolonged evaluation period.

This approach requires a deep understanding of the organisation's needs and the capabilities of the models, but it can provide a more efficient and effective way to make the decision, and organisations should consider this approach when deciding between using one model or routing between several, and the following are some key factors to consider:

• the types of queries that will be made
• the structure of the data
• the resources available to support the chosen approach

What this does not do

This approach to deciding between using one model or routing between several does not provide a solution for all types of requests, and organisations should not assume that it will work for every type of query, as some requests may require a more bespoke approach, and the organisation must be prepared to adapt to these needs.

Furthermore, this approach does not eliminate the need for ongoing maintenance and updates, and organisations should not assume that once the decision is made, the work is done, as the models will continue to require support to ensure they provide accurate answers, and the organisation must be prepared to invest in the necessary resources to support this, and this is an ongoing commitment that requires careful planning and budgeting.