![]() |
VOOZH | about |
We’re so glad you’re here. You can expect all the best TNS content to arrive Monday through Friday to keep you on top of the news and at the top of your game.
Check your inbox for a confirmation email where you can adjust your preferences and even join additional groups.
Follow TNS on your favorite social media networks.
Become a TNS follower on LinkedIn.
Check out the latest featured and trending stories while you wait for your first TNS newsletter.
Two recent surveys on artificial intelligence make the case that the value proposition for AI has achieved critical mass. According to PwC’s 2023 Emerging Technology Survey, 73% of U.S. respondents stated that their company has adopted AI in some business areas. In a recent Forbes Advisor survey, 64% of respondents said AI will improve customer relationships and increase productivity, with 60% expecting AI to drive sales growth.
However, as enterprises restructure business operations around predictive and generative AI to gain competitive advantage, they need to maximize the efficiency of their machine learning operations (MLOps) to deliver positive ROI. This is no small feat today, given that AI at scale means enterprises can have tens or hundreds of machine learning models (MLMs) in development, training or production at all times.
Without the right automation and self-service capabilities, the workflows supporting distributed MLOps at scale can hinder machine learning (ML) engineers from never-ending infrastructure and component management tasks. This prevents them from engaging in high-value work on models or the AI applications that their MLMs support.
Just as platform engineering emerged from the DevOps movement to streamline app development workflows, so too must platform engineering streamline the workflows of MLOps. To achieve this, one must first recognize the fundamental differences between DevOps and MLOps. Only then can one produce an effective platform engineering solution for ML engineers. To enable AI at scale, enterprises must commit to developing, deploying and maintaining platform engineering solutions that are purpose-built for MLOps.
Whether due to data governance requirements or practical concerns about moving vast volumes of data over significant geographical distances, MLOps at scale require enterprises to utilize a spoke-and-wheel approach. Model development and training occurs centrally, trained models are distributed to edge locations for fine-tuning on local data, and fined-tuned models are deployed close to where end users interact with them and the AI applications they leverage.
Here’s how many enterprises are approaching AI at scale:
Platform engineering solutions designed for MLOps at scale must address all of the following requirements:
The innovation economy enveloping the AI ecosystem introduces new components that improve the AI stack nearly daily. When developed properly, your ML platform engineering solution can harness powerful new technologies as they become available. To make this possible, your ML platform engineering solution must be managed as a product rather than as a project.
This requires treating the data scientists and ML engineers who engage with the platform as customers and assigning a dedicated product support team to manage the solution’s features backlog. The platform engineering product team must continuously improve the solution as requirements change and technology evolves.
Enterprises should hire engineers with MLOps experience to fill platform engineering roles appropriately. According to research from the World Economic Forum, AI is projected to create around 97 million new jobs by 2025. A growing number of these opportunities will be ML platform engineering roles.
Enterprises that adopt an MLOps platform engineering approach will provide a much-needed immediate boost to their operational efficiency and future-proof their AI program by ensuring their ML engineers will always be able to focus on the high-value data science work they were hired to perform.