Many enterprises are looking to standardize their AI environments around common platforms and controls. But operational workloads are showing why that does not necessarily mean relying on one model. For tasks that depend on accurate forecasts, optimization or consistent numerical outputs, a general-purpose model may not be the best fit, even if the company already uses it elsewhere. Enterprises should standardize governance and infrastructure where they can, without allowing platform consolidation to force operational workloads onto models that are poorly suited to them.
Recent examples make the distinction clearer.
Ant International uses its FalconTST 2.0 model to forecast cash flow and foreign-exchange needs for banks including Barclays, Citi, Deutsche Bank and Standard Chartered. The point here is accuracy in a financial task where small forecasting errors can affect currency exposure and how efficiently capital is used. Ant says the model has achieved forecast accuracy above 93% in deployments.
In Japan, NEC has launched an AI system for demand, inventory and supply-chain planning. It combines an LLM with machine learning and other specialized tools rather than relying on one model for the whole workflow.
Huawei and Yalong Hydro have deployed specialized models to forecast weather, water flows and power generation. These forecasts feed into power scheduling, plant operations and market decisions, making accuracy and reliability particularly important for day-to-day energy operations.
None of this means GenAI is being displaced. It points instead to a different role for it. A general-purpose model can still handle interaction, interpretation or coordination, while other models do the underlying operational work.
That creates a harder problem for enterprises trying to standardize their AI stack. A common platform can simplify procurement, governance and integration, but the challenge is keeping the environment manageable without forcing very different workloads through the same technical approach.
A More Flexible AI Stack
That separation between the interface and the model doing the work is becoming the more important shift.
NEC’s supply chain system is a good example. Rather than asking an LLM to handle numerical forecasting and optimization itself, the system combines it with machine learning and specialized AI tools for demand, inventory, and planning. Huawei and Yalong Hydro are taking a similar multi-model approach in energy, pairing specialist weather and hydrology models with broader AI systems and service agents across forecasting, power scheduling, plant operations and market risk.
In both cases, users do not need to interact separately with every model involved. A general-purpose AI layer can provide a common interface for the workflow, while specialist systems handle the underlying calculations and operational decisions. One common AI interface does not require one common model underneath.
That distinction matters for enterprises trying to simplify their AI environments. They can standardize how employees access AI, how systems are governed and how outputs are monitored without forcing every workload through the same technical approach.
IBM Research takes a similar view, developing different forecasting models for tasks such as sales, restocking, risk assessment and equipment monitoring after finding that no single model consistently performs best across different types of data. Gartner expects 40% of enterprise applications to include task-specific AI agents by the end of 2026, up from less than 5% in 2025, pointing to greater use of task-specific AI alongside general-purpose systems.
The result is not a collection of separate AI products. It is a layered stack with one common platform and different models handling different types of work.
What to Standardize, and What to Keep Flexible
As enterprises add specialized systems beneath common AI platforms, they need to manage that flexibility without creating a fragmented environment.
That is where standardization still matters. Governance, security, access controls and evaluation can remain common across the business, even if the model underneath changes depending on the workload. Microsoft recommends testing models on representative tasks and comparing factors such as accuracy, cost and latency before choosing one for production. AWS similarly recommends common infrastructure, security and governance layers while allowing teams to evaluate and select different models for different use cases.
Singapore is taking a similar approach. Its Model AI Governance Framework for Agentic AI calls for risk assessments, baseline testing, access controls and human accountability, including for third-party and multi-agent systems. The aim is to keep the same basic controls in place across different AI systems.
But flexibility has a cost. More models mean more integrations, testing, monitoring and vendors to manage. Without common controls, teams can end up with duplicate tools, inconsistent evaluations and systems that are harder to track or audit. Singapore’s latest framework reflects that concern, with specific guidance on managing risks from multi-agent systems and third-party agents as AI environments become more complex.
The challenge is to keep that flexibility without making the stack harder to govern.
Where Operators Should Draw the Line
For operators, the harder decision is what to standardize and what to leave open. Governance, security, access, monitoring and the employee-facing interface can stay consistent across the business, even if different systems are doing the work underneath.
Specialist models should only be added when they bring a clear benefit. If a forecasting or optimization system is materially more accurate, reliable or useful than the enterprise default, the extra complexity may be worth it. If the gain is small, another integration, vendor, and monitoring process may simply make the stack harder to manage.
That is why platform and model consolidation should be treated separately. Companies can simplify the number of platforms they run and keep common controls in place without insisting that every workload use the same model. The goal is not maximum consolidation. It is to keep the AI stack governable without compromising the performance of critical operational workloads.
More From Asia Tech Lens
Southeast Asia Needs the Right AI Model for the Right Job
Argues that cheaper Chinese model pricing doesn't mean lower total cost once language performance, reliability and compliance are priced in for a specific workload.
AI Middleware Promises Flexibility. In Asia, It Can Create Jurisdictional Lock-In
How middleware sold as model-flexibility can quietly lock in data routing and compliance architecture that's hard to unwind.
Agentic AI Can Act. Singapore’s New Rulebook Says: Prove You Can Stop It.
Covers Singapore's Agentic AI Governance Framework - bounded autonomy, audit capability, rollback - as a live model for how to govern AI systems that act.
China’s Compute Surplus Won’t Be Your Compute Surplus
China's data-center compute surplus won't become a regional utility because governance and vendor constraints keep it largely locked domestically.
The AI Battleground: How Southeast Asia Is Forging a New Path Between Open and Closed Models
Shows Southeast Asian institutions—OCBC, Malaysia's sovereign AI stack, Indosat/AIonOS, Grab and Shopee—already running open-source and proprietary models side by side rather than standardizing on one.