Artificial Intelligence #
Across industries, decision-making starts with understanding what is changing and why. Industrial organizations collect data that informs decisions across their operations. This data helps prevent production stoppages, diagnose vehicle faults, explain drops in data-center performance, and adjust pricing as supply and demand shift. However, interpreting that data still requires specialist time, and collecting more data does not mean teams can act on it. General-purpose language models like Claude or ChatGPT can help analyze data. However, processing long histories across hundreds of operational metrics as text or images can consume large numbers of tokens, which increases cost.
To help organizations act on this data, Aionic Labs is developing temporal foundation models, including OpenTSLM, an open source family of time-series language models (TSLMs). These models interpret operational measurements, from equipment sensor data to supply and demand, alongside context such as maintenance records, market news, and an engineer’s observations. In doing so, TSLMs help systems recognize emerging problems in recent measurements. Experts can then ask follow-up questions to understand what changed and assess how to respond. TimeNet, the shared data infrastructure for time-series data, provides one format and API to find, build, and load the datasets used to train and evaluate these models. Together, they help organizations understand how their systems change and act before problems become costly.
OpenTSLM is now available in Amazon SageMaker JumpStart, so you can deploy the model in your own AWS environment. This post explores how Nexthink and Aionic Labs are bringing this capability to proactive IT assistance, then shows how to deploy OpenTSLM and adapt it to your own data using TimeNet.
A customer example: Proactive IT support at Nexthink #
Nexthink and Aionic Labs are building toward a digital workplace where employees get help before they need to ask for it. At the center is Spark, Nexthink’s personal IT agent, enhanced with time-series language models that connect device telemetry and context to the problems employees experience. Spark turns that understanding into action: it checks the likely issue, guides the employee through an appropriate fix, and follows up on the result. Proactive assistance becomes part of keeping work moving.
The workflow combines recent device time-series, such as CPU activity, memory use, available disk space, application stability, and connectivity, with timestamped events and device and software context. The TSLM receives the numerical measurements alongside this text context and interprets how the signals change over the observation window.
The TSLM provides Spark with three outputs:
- State summary: Explains the likely issue and the supporting signal patterns, connecting device behavior with the employee’s experience.
- Recommended action: Specifies checks to confirm the issue and a practical action for Spark to offer the employee.
- Expected outcome: Describes the intended improvement and how Spark checks the result.
Device telemetry and context support investigation of a range of issues, including slow performance under high CPU or memory load, recurring application freezes or crashes, and files that fail to synchronize. Resource usage, application events, storage measurements, and connection activity provide different pieces of evidence. Combined with device configuration and software versions, they give the TSLM a broader basis for explaining the employee’s experience and directing Spark’s next checks.
In the illustrative low-disk example in Figure 2, the TSLM connects declining free space, a rising disk queue, and more frequent application hangs with likely employee symptoms, such as a slow computer or difficulty saving files. Spark checks how much space is left and whether temporary files can be removed using an IT-approved cleanup. If the checks confirm that a cleanup is appropriate, Spark shows the employee what it proposes to remove and asks for confirmation. After the employee confirms, Spark runs the cleanup, checks the space now available, and asks whether the problem has improved. If the issue persists, Spark offers to pass the findings to IT support.
TSLMs understand how systems change and help people act on that understanding. For Spark, this means recognizing emerging IT problems and guiding employees toward a solution. The same approach brings time series intelligence to manufacturing, energy, and connected products, turning measurements and context into explanations and intelligent decisions.
Solution overview #
The architecture in Figure 3 provides a reusable deployment pattern for time-series applications. SageMaker JumpStart supplies the model discovery and deployment path.
SageMaker JumpStart is a machine learning (ML) model hub that accelerates your ML journey. With SageMaker JumpStart, you can evaluate, compare, and deploy pretrained foundation models (FMs), including the newly available OpenTSLM model. As part of the AWS AI offerings, SageMaker JumpStart provides customizable ML solutions which you can deploy to Amazon SageMaker AI inference endpoints within your AWS infrastructure. It complements Amazon Bedrock, which offers serverless API foundation model inference along with features like customizations, knowledge bases, agents, and guardrails.
Key technical benefits of SageMaker AI and SageMaker JumpStart include:
- Pre-built inference containers – AWS Deep Learning Containers with GPU acceleration, so you can serve the model without building your own image.
- Automatic scaling endpoints – Managed infrastructure scales compute resources based on request volume and latency requirements.
- Inference API – SageMaker real-time inference endpoints with standardized API calls, SDK, and AWS Identity and Access Management (IAM) integration.
- Integrated monitoring – Built-in metrics for throughput, latency, and resource utilization with an Amazon CloudWatch integration.
- Enterprise security – Amazon Virtual Private Cloud (VPC) deployment with IAM access control and network isolation options.
The model in SageMaker JumpStart is OpenTSLM-Flamingo. It combines the Gemma 3 4B language model with a time-series encoder and cross-attention layers that let the language model attend to the encoded series. The model has 5.24 billion parameters in total, stored in bfloat16, so its weights take about 10.5 GB of GPU memory.
An application prepares numerical time series and text context, invokes the SageMaker endpoint, and receives the model’s response. The application can present that response to an expert or use it as input to another workflow.
This separation allows the application to control the observation window, select relevant signals, and validate the response before using it. It also makes the model independently adaptable: a new checkpoint can be evaluated against representative cases before the application switches to it.
In addition, we show a tutorial that fine-tunes a pretrained OpenTSLM checkpoint from Hugging Face using ARFBench data loaded through TimeNet. The notebook submits a SageMaker training job that loads ARFBench through TimeNet and fine-tunes the model. Amazon Simple Storage Service (Amazon S3) stores the resulting model artifact, which is then deployed to a separate SageMaker real-time inference endpoint for evaluation.
Prerequisites
For the deployment walkthrough, use an AWS account with an [Amazon SageMaker AI domain](https://docs.aws.amazon.com/sagemaker/latest/dg/onboard-quick-start.html) and a [SageMaker AI execution role](https://docs.aws.amazon.com/sagemaker/latest/dg/sagemaker-roles.html). The role must be able to create SageMaker models and endpoints in a supported Region, for example a role with the `AmazonSageMakerFullAccess` managed policy. The quick setup for single users creates both. The managed policy grants broad permissions to get started. For production, use a policy that grants only the permissions you need, as described in [Amazon SageMaker AI identity-based policy examples](https://docs.aws.amazon.com/sagemaker/latest/dg/security_iam_id-based-policy-examples.html). OpenTSLM runs on a single GPU with at least 24 GB of memory and bfloat16 support, and we recommend 32 GB of host memory. The default instance type is `ml.g6.2xlarge` (one NVIDIA L4 GPU with 24 GB of memory, 32 GB of host memory). In SageMaker JumpStart, OpenTSLM also supports `ml.g6.4xlarge`, `ml.g6.8xlarge`, `ml.g5.2xlarge`, `ml.g5.4xlarge`, `ml.g5.8xlarge`, `ml.g6e.xlarge`, and `ml.g6e.2xlarge`. In the [Service Quotas console](https://console.aws.amazon.com/servicequotas/home/services/sagemaker/quotas), check your quota for “`ml.g6.2xlarge` for endpoint usage”, or for the instance type you choose. You need a quota of at least 1. If it’s lower, [request an increase](https://docs.aws.amazon.com/servicequotas/latest/userguide/request-quota-increase.html). See the OpenTSLM JumpStart model card for the model access requirements.
For fine-tuning, use [JupyterLab in Amazon SageMaker Studio](https://docs.aws.amazon.com/sagemaker/latest/dg/studio-updated-jl.html) or a local Jupyter environment with [AWS credentials configured](https://docs.aws.amazon.com/cli/latest/userguide/cli-chap-configure.html) to run the accompanying notebook, which submits the training job. The notebook uses the SageMaker default S3 bucket and an execution role. Fine-tuning runs on `ml.g7e.2xlarge`, so also check your quota for “` ml.g7e.2xlarge` for training job usage”. Training runs on the job’s managed GPU instance. The notebook itself does not need a GPU. Obtain access to the selected Hugging Face checkpoint where required.
Deploy OpenTSLM with SageMaker JumpStart
To deploy OpenTSLM in SageMaker Studio, complete the following steps:
-
In SageMaker Studio, choose Models in the navigation pane, thenJumpStart models .
-
Search for “OpenTSLM” and choose OpenTSLM-Flamingo Gemma 3 4B . The model page shows the model ID, the license, and the request and response format.
-
Choose Deploy .
-
On the Deploy model to endpoint form, review the Gemma Terms of Use underLicense agreement and select the checkbox to accept the end user license agreement (EULA). Keep the default instance type,
ml.g6.2xlarge, or choose another supported instance type. Then chooseDeploy .