Bookmarks

    Nothing saved yet. Use the bookmark on any article. Bookmarks are kept on this device only: they stay private and work without an account.

    Settings

    Appearance

    Reading mode

    Font size

    Content width

    Line spacing

    Keyboard shortcuts

    /
    Search
    j k
    Next / previous story
    ← →
    Previous / next section (columns)
    b
    Bookmarks
    s
    Settings
    r
    Columns / scroll
    t
    Light / dark

    Saved in this browser only.

    Ping2Prompt
    Subscribe to the Weekly Brief Sign in
    Ping2Prompt story card: Confluent adds IBM time-series models as built-in Flink functions. Release, Hugging Face.

    Confluent adds IBM time-series models as built-in Flink functions

    Hugging Face

    IBM time-series models now built into Confluent

    IBM's time-series foundation models now run natively inside Confluent as built-in functions, both in the cloud and on premises. The announcement says the models have more than 50 million downloads.

    Forecasting and anomaly detection from Flink SQL

    With Apache Flink, teams can apply forecasting, anomaly detection and semantic intelligence to streaming data using SQL. The post describes two functions:

    • AI_FORECAST uses a pretrained model to forecast demand across products and stores; the example gives a 28-day forecast with a P10–P90 range, refreshed as new sales data arrives.
    • AI_DETECT_ANOMALIES builds an expected range for each series from its recent history and compares each new reading against it at a confidence level the team chooses.

    Anomaly detection needs no separate model per series. IBM says a pretrained model gives a common starting point across many series, and teams can fine-tune it or combine its output with other data and business logic. The family has four models; the post names the TTM model in its manufacturing example.

    The use cases are scenarios, not measured results

    The post's examples are manufacturing quality control and setpoint optimization, retail sales anomaly detection, store-level demand forecasting and reorder points, and card-payment fraud signals. These are illustrative scenarios, not reported results. In the manufacturing case, TTM reads SCADA telemetry and QA measurements every 10 minutes and forecasts the share of tubs in spec four hours ahead.

    Running the models on CPUs in Cloud or on premises

    In Confluent Cloud the models are fully managed, with nothing to deploy. On premises they run in your own infrastructure through Confluent Platform for Apache Flink. The models run on CPUs without requiring GPUs. IBM says they are small enough to run on standard CPUs next to the streaming pipeline, which can reduce the need for dedicated GPU infrastructure.

    Who should try in-stream forecasting

    If you already run Flink SQL on Confluent and keep sensor, sales or payment series, these functions let you test forecasting without standing up a separate model service. Try them on one of your own series and check the output against known history before you rely on it.

    What IBM and Confluent have not stated yet

    The post as provided does not state pricing, licensing, availability dates or which Confluent releases are needed, and the text is cut off. Check the Confluent and IBM documentation before planning a rollout.

    Sources


    This story was produced with AI assistance from the sources listed above and fact-checked against them before publication. Read our editorial methodology and the corrections log. Spotted an error? Email [email protected].

    Continue

    Share on Bluesky · Mastodon · Email ·

    Discussion