Wednesday, September 16, 2026
No Result
View All Result
Future News 24
Advertisement
  • Home
  • AI Research
  • Platforms
  • Ethics
  • Developer AI
  • Industry
  • Data Science
  • Emerging Tech
  • Quantum
  • BioTech
  • Decentralized
  • Home
  • AI Research
  • Platforms
  • Ethics
  • Developer AI
  • Industry
  • Data Science
  • Emerging Tech
  • Quantum
  • BioTech
  • Decentralized
No Result
View All Result
Future News 24
No Result
View All Result
Home AI Platforms & Apps

Integrating Context-Conscious Video AI Brokers Into Enterprise Workflows

Future News 24 by Future News 24
July 18, 2026
in AI Platforms & Apps
0 0
0
Integrating Context-Conscious Video AI Brokers Into Enterprise Workflows
0
SHARES
0
VIEWS
Share on FacebookShare on Twitter


A video analytics AI agent that may understand, cause, and act based mostly on huge quantities of video footage should be built-in with present workflows and purposes to be helpful. These embody content material administration methods, messaging platforms, databases, ticket queue, and escalation paths.

This integration is difficult as a result of video methods, enterprise information bases, and operational instruments are normally siloed. Builders must seize person intent, retrieve the proper organizational context, generate structured reviews, and route findings into downstream methods.

In a earlier put up, we defined the way to enrich video evaluation with doc information utilizing NVIDIA Blueprints. This put up continues with the subject and explains the way to unlock the flexibility to not simply analyze video, however to programmatically act on these analyses by introducing NVIDIA NemoClaw. You’ll discover ways to:

Prolong VSS for guided, context-aware video evaluation

Orchestrate the VSS and RAG blueprints as a composable service utilizing NVIDIA NemoClaw

Generate structured reviews enriched with organizational and reference information

Construct multistep workflows the place video evaluation feeds into different enterprise processes

Deploy and scale this resolution throughout enterprise environments

This method is the following step in context-aware video AI brokers, which includes shifting from “What does this video present?” to “What ought to we do about what this video reveals, and the way will we coordinate that motion at scale?”

What are NVIDIA NemoClaw and NVIDIA Blueprints?

NVIDIA NemoClaw is a set of open blueprints for constructing autonomous brokers. It allows the ecosystem to construct domain-specialized, always-on brokers which can be safer, quicker, and function extra value effectively throughout digital and bodily workflows. 

NVIDIA Blueprints are customizable reference workflows for constructing agentic AI pipelines at enterprise scale. They mix specialised microservices, optimized fashions, and composable APIs to speed up time-to-value whereas sustaining modularity. Along with NemoClaw, the primary blueprints used on this put up are:

How does VSS seize intent, retrieve information, and generate reviews from video?

VSS offers guided, context-aware video evaluation via a set of instruments constructed into the agent. Human-in-the-loop (HITL) prompts seize what the person needs earlier than any processing begins. The agent retrieves the related organizational information and produces a structured, timestamped report. 

When mixed with NVIDIA NemoClaw blueprints for constructing autonomous brokers, this method can transcend easy video evaluation to programmatically act on these analyses. This unlocks the flexibility to generate tickets, examine patterns throughout a number of sources, draft revised procedures, escalate anomalies, and feed outcomes into downstream workflows.

Three agent instruments work collectively to make this occur:

Lengthy video abstract (LVS) video understanding device: Performs lengthy video summarization with obligatory HITL parameter assortment. Customers interactively specify the state of affairs (what the video is about), occasions of curiosity (what to detect), objects of focus (what to trace), and an elective knowledge-retrieval question.

Data retrieval (frag) device: Calls the RAG Blueprint to retrieve organization-specific context from paperwork, insurance policies, reference knowledge, and information bases. The RAG Blueprint handles embedding, reranking, and vector search internally.

Report era device: Produces a structured report combining the video evaluation with the retrieved context, full with timestamps, narrative evaluation, and citations. It may use HITL to let the person affirm or edit the immediate earlier than the report is generated.

Collectively, these instruments acquire person intent via HITL, question the RAG Blueprint for contextual information, course of the video with that context, and hand off to the report era device for formatted output.

Producing assessments and advisable actions from a video

To display this course of, we’ll create a “wholesome consuming coach” that analyzes meals movies to evaluate a person’s consuming habits and return concrete, tracked subsequent steps they’ll act on. The method is detailed within the following sections.

Person uploads a video and specifies what to investigate

To begin, a person uploads a meal preparation video via the VSS interface (Determine 1).

Screenshot of the VSS web interface showing an upload panel where a user can drag and drop or browse to select a breakfast video file to ingest into the system.
Screenshot of the VSS web interface showing an upload panel where a user can drag and drop or browse to select a breakfast video file to ingest into the system.
Determine 1. Within the VSS person interface, you possibly can drag and drop a video to add it into the system

NemoClaw then begins the workflow. It reads the vss-generate-video-report-rag ability definition (SKILL.md) to study which parameters the evaluation wants and arms the request to the VSS agent, which walks the person via a brief sequence of HITL prompts of their terminal (Determine 2).

Screenshot of a terminal session in which the user answers NemoClaw’s human-in-the-loop prompts, specifying the scenario, events, objects, and reference knowledge to retrieve before the video is analyzed.
Screenshot of a terminal session in which the user answers NemoClaw’s human-in-the-loop prompts, specifying the scenario, events, objects, and reference knowledge to retrieve before the video is analyzed.
Determine 2. The guided NemoClaw HITL interplay that captures intent earlier than processing begins on the user-side terminal 

The prompts ask what to investigate, the state of affairs, the occasions of curiosity, the objects to trace, and an elective RAG Blueprint question for the reference information to retrieve, such because the dietary or regulatory pointers. Capturing this intent up entrance scopes the evaluation to what the person really cares about earlier than any video is processed. For automated batch runs, these solutions might be equipped programmatically as a substitute of interactively.

NemoClaw orchestrates VSS and the RAG Blueprint

Subsequent, with the parameters confirmed, NemoClaw orchestrates the pipeline. The LVS video understanding device first queries the RAG Blueprint for the related dietary pointers, and the RAG Blueprint returns the matching reference paperwork, dealing with the vector search internally. 

It then passes these parameters, the video, and the retrieved context to the LVS service, which summarizes the video hierarchically and weaves the reference information into its findings. The report era device combines the consequence right into a structured, timestamped report that features detected occasions with timestamps, a story evaluation grounded within the reference materials, citations to the related supply paperwork, and concrete advisable actions. 

Determine 3 reveals this orchestration within the NemoClaw terminal, together with the agent’s reasoning and power calls.

Screenshot of the NemoClaw terminal displaying the agent’s reasoning trace and tool calls as it orchestrates the pipeline, invoking VSS for video analysis and the RAG Blueprint to retrieve nutritional guidelines.
Screenshot of the NemoClaw terminal displaying the agent’s reasoning trace and tool calls as it orchestrates the pipeline, invoking VSS for video analysis and the RAG Blueprint to retrieve nutritional guidelines.
Determine 3. The NemoClaw terminal reveals the orchestration of VSS and the RAG Blueprint, together with the agent’s reasoning and power calls

NemoClaw creates a Jira ticket 

NemoClaw reads the completed report and turns it into coordinated motion. It presents the finished evaluation with hyperlinks to the Markdown and PDF reviews and the video playback, a abstract of why the meal is wholesome, and advisable subsequent steps (Determine 4). It then robotically creates a Jira ticket that summarizes the findings and the advisable dietary changes, with an applicable precedence and project so the motion gadgets are tracked to completion (Determine 5).

Screenshot of the NemoClaw terminal after the breakfast analysis completes. It lists download links for a Markdown report, a PDF report, and the video playback, then explains why the breakfast is healthy (minimally processed ingredients, whole grains such as oats, good hygiene practices) and lists actionable next steps, ending with a note that it will now create a Jira ticket.
Screenshot of the NemoClaw terminal after the breakfast analysis completes. It lists download links for a Markdown report, a PDF report, and the video playback, then explains why the breakfast is healthy (minimally processed ingredients, whole grains such as oats, good hygiene practices) and lists actionable next steps, ending with a note that it will now create a Jira ticket.
Determine 4. The NemoClaw terminal presents the finished video evaluation, with hyperlinks to the Markdown and PDF reviews and the video playback, a abstract, and advisable subsequent steps earlier than the Jira ticket is created
Screenshot of a Jira ticket created automatically by NemoClaw. The ticket summarizes the video findings and lists recommended dietary next steps, with a priority and an assignee so the action items are tracked to completion.
Screenshot of a Jira ticket created automatically by NemoClaw. The ticket summarizes the video findings and lists recommended dietary next steps, with a priority and an assignee so the action items are tracked to completion.
Determine 5. The Jira ticket is robotically generated by NemoClaw, summarizing the findings and advisable subsequent steps

This downstream step generalizes properly past Jira. Relying on what the report accommodates, NemoClaw can even:

Create tickets for the findings, with the proper precedence and project.

Escalate or summarize patterns that emerge throughout a number of runs.

Bundle supporting proof for evaluate or compliance.

Route gaps to the suitable follow-up workflow.

At this level, the report is now not a static doc. It turns into the set off for coordinated motion throughout the methods your workforce already makes use of.

Determine 6 reveals the structure in 4 layers:

Orchestration: The NemoClaw agent, the vss-generate-video-report-rag ability, and the HITL prompts

VSS agent: Instruments embody video I/O, search, understanding, LVS, information retrieval, and report era. Data retrieval is a part of the agent, not a separate extension

RAG Blueprint: NVIDIA RAG API, Milvus vector database, NVIDIA Nemotron reranking NIM, and the listed reference and organizational paperwork

 LLM fusion: Enrichment of the VSS-provided abstract with the context retrieved via the RAG Blueprint

Information flows downward via the system, with the agent’s instruments orchestrating calls to the LVS service and the RAG Blueprint, each of which feed into the report era device for remaining output.

Layered architecture diagram with NemoClaw at the top orchestrating the vss-frag skill, the VSS Agent core and its frag tools, and the RAG Blueprint. Arrows show data flowing from orchestration through video analysis and retrieval into report generation.
Layered architecture diagram with NemoClaw at the top orchestrating the vss-frag skill, the VSS Agent core and its frag tools, and the RAG Blueprint. Arrows show data flowing from orchestration through video analysis and retrieval into report generation.
Determine 6. Structure of VSS 3.1 and the RAG Blueprint orchestrated by NemoClaw

deploy the VSS agent with information retrieval

Observe the steps under to implement the answer to your personal workflow.

Conditions

NVIDIA GPU(s) with not less than 24 GB VRAM

Docker Engine plus Docker Compose v2

NGC API key (ngc.nvidia.com)

NVIDIA Construct API key (construct.nvidia.com)

RAG Blueprint deployed and reachable from the agent (its server URL accessible), and its assortment title

NemoClaw put in (for programmatic entry)

Step 1: Clone the VSS repo and authenticate with NGC

git clone https://github.com/NVIDIA-AI-Blueprints/video-search-and-summarization.git ~/vss-public
cd ~/vss-public
echo “$NGC_CLI_API_KEY” | docker login nvcr.io –username ‘$oauthtoken’ –password-stdin

Step 2: Configure the setting

Edit the LVS profile .env file, deploy/docker/developer-profiles/dev-profile-lvs/.env. All of the variables exist in that file, besides the RAG_ values, which the agent’s RAG config reads and also you add your self.

# Deployment choice
MODE=2nd
BP_PROFILE=bp_developer_lvs
HARDWARE_PROFILE=H100 # H100, L40S, RTXPRO4500BW, RTXPRO6000BW, DGX-SPARK, IGX-THOR, AGX-THOR, or OTHER

# LLM / VLM placement
LLM_MODE=local_shared # local_shared runs LLM and VLM on one GPU; use ‘native’ for separate GPUs
VLM_MODE=local_shared
LLM_DEVICE_ID=’0′
VLM_DEVICE_ID=’0′

# Paths (you MUST set these)
VSS_APPS_DIR=”/vss-public/deploy/docker”
VSS_DATA_DIR=”/vss-apps-data”
HOST_IP=”

# Agent picture + config
VSS_AGENT_VERSION=3.2.0
# Allow information retrieval (frag): level at config_rag.yml (default config.yml has it off)
VSS_AGENT_CONFIG_FILE=./deploy/docker/developer-profiles/dev-profile-lvs/vss-agent/configs/config_rag.yml

# Credentials
NGC_CLI_API_KEY=’nvapi-…’
NVIDIA_API_KEY=’nvapi-…’

# RAG Blueprint connection (learn by config_rag.yml)
RAG_SERVER_URL=’http://:8081/v1′
RAG_API_KEY=”
KNOWLEDGE_COLLECTION=”

Setting VSS_AGENT_CONFIG_FILE to config_rag.yml allows the frag knowledge-retrieval device. These three RAG_ values are the one RAG settings the agent wants: it calls the RAG server’s search endpoint, and the RAG Blueprint handles embedding, reranking, and vector search internally. Configure the vector database, embedding, and reranker on the RAG Blueprint deployment itself, following its personal documentation.

Step 3: Deploy the VSS stack

Create the info directories the bind mounts want, then carry up the stack. The compose profile is chosen robotically from COMPOSE_PROFILES within the .env file.

export VSS_DATA_DIR=/vss-apps-data
mkdir -p “$VSS_DATA_DIR”/data_log/{elastic/knowledge,elastic/logs,kafka,redis/knowledge,redis/log}
chmod -R 777 “$VSS_DATA_DIR/data_log”

cd ~/vss-public/deploy/docker
docker compose
–env-file developer-profiles/dev-profile-lvs/.env
-f compose.yml
up -d

The compose stack begins all infrastructure (VST, Redis, Elasticsearch, LVS, NIM) and the agent utilizing the RAG-enabled config. The dev-profile helper, ./deploy/docker/scripts/dev-profile.sh up –profile lvs –hardware-profile H100, does the identical and creates the info directories for you.

Step 4: Confirm that the companies are wholesome

Notice that the NIM could take 5 to fifteen minutes to load.

docker ps –format ‘desk {{.Names}}t{{.Standing}}t{{.Ports}}’
curl -sS http://localhost:8000/well being # VSS agent
curl -f http://127.0.0.1:38111/v1/prepared # LVS backend
curl -f http://127.0.0.1:8018/v1/well being/prepared # RT-VLM
curl -f http://127.0.0.1:30081/v1/well being/prepared # LLM NIM

NemoClaw setup

NemoClaw acts because the orchestration layer, configuring the sandbox, community coverage and ability so it might drive the total workflow.

Step 1: Run the NemoClaw installer 

From the repo root; NEMOCLAW_PROVIDER is required; use construct for NVIDIA-hosted fashions.

NEMOCLAW_PROVIDER=construct
NVIDIA_API_KEY=”$NVIDIA_API_KEY”
bash deploy/docker/scripts/nemoclaw/init_nemoclaw.sh demo

This single command handles the total setup: it onboards NemoClaw, configures the mannequin supplier, applies the VSS sandbox coverage (which grants the sandbox entry to the VSS agent on port 8000), installs the repo abilities—together with vss-generate-video-report-rag—into the sandbox as an OpenClaw plugin, and prints the OpenClaw UI URL. 

To make use of your individual OpenAI-compatible endpoint as a substitute (for instance an area vLLM):

NEMOCLAW_PROVIDER=customized with NEMOCLAW_ENDPOINT_URL and COMPATIBLE_API_KEY

Step 2: Check the end-to-end workflow

nemoclaw SANDBOX_NAME join
openclaw tui

The OpenClaw UI is now open. The following two actions occur inside that UI, not in your shell:

Sort /new and press Enter to start out a contemporary session.

Sort your request as a message and press Enter: I wish to generate a video abstract report for .

The agent then collects the evaluation parameters via the HITL prompts, generates the report with LVS and the RAG Blueprint, and may create a Jira ticket or ship notifications based mostly on the outcomes.

Latency and efficiency of the end-to-end pipeline

Including NemoClaw orchestration and HITL parameter assortment introduces minimal latency overhead. The HITL section is asynchronous—NemoClaw and human customers work together whereas the system stands by—so as soon as parameters are confirmed, video processing proceeds.

Horizontal bar chart titled "Runtime % by Component" showing VSS video analysis accounting for about 92% of end-to-end runtime, with NemoClaw at roughly 5.7%, Enterprise-RAG retrieval at 1.3%, and LLM fusion at 1.0%.
Horizontal bar chart titled "Runtime % by Component" showing VSS video analysis accounting for about 92% of end-to-end runtime, with NemoClaw at roughly 5.7%, Enterprise-RAG retrieval at 1.3%, and LLM fusion at 1.0%.
Determine 7. Runtime proportion by system part for the video evaluation to Jira action-item pipeline

How are industries and NVIDIA companions utilizing NemoClaw, VSS 3, and the RAG Blueprint?

The mixture of video understanding, information retrieval, and agentic orchestration unlocks new capabilities throughout industries. Right here is how companions are deploying this resolution.

Computacenter deployed the total DETECT → REASON → ACT pipeline on a Run:AI cluster for predictive upkeep, utilizing VSS 3 to investigate drone, borescope, and thermal inspection footage, RAG Blueprint for OEM context, and NemoClaw to auto-draft Maximo work orders—reducing footage-to-work-order time from 30–45 minutes to roughly 19 seconds throughout 4 asset courses.

VAST Information makes use of NemoClaw to orchestrate a real-time VSS pipeline on the VAST DataEngine, processing reside sport streams with VAST RAG over VastDB and vectors; constructed on the NVIDIA blueprint with cosmos-reason2 and Nemotron, it runs end-to-end on NVIDIA DSX AIR.

What are the advantages of actionable video AI?

The mixing of VSS 3, RAG Blueprint, and NemoClaw represents a basic shift in how enterprises can method video analytics. Video evaluation has sometimes produced static reviews. Understanding what occurred in a video required handbook interpretation and handbook motion initiation.

With this built-in resolution, video understanding is now a place to begin. Agentic orchestration interprets that understanding into coordinated motion—creating tickets, alerting groups, evaluating patterns, escalating anomalies, and feeding outcomes into downstream workflows.

The implications are vital:

Velocity: Response time drops from hours or days to minutes.

Scale: Analyze hundreds of movies throughout a number of sources and floor enterprise-wide patterns.

Consistency: Reference information (insurance policies, procedures, laws, pointers) is constantly utilized.

Accountability: Each determination is traced again to video proof and supply paperwork.

Automation: Routine workflows (alert era, ticket creation, documentation) run with out handbook intervention.

That is what enterprise-grade video AI appears like: specialised evaluation engines (the VSS and RAG blueprints) composed into general-purpose agentic workflows (NemoClaw) that embed organizational intelligence into each determination.

Get began with actionable, enterprise-grade video AI

Collectively, VSS, RAG Blueprint, and NemoClaw illustrate a broader architectural precept: no single mannequin or service is perfect for each drawback, however specialised methods composed via clear, well-defined APIs can ship capabilities that exceed the sum of their elements. This may be performed with out sacrificing the modularity, scalability, and governance that enterprise deployments demand.

The consequence reframes what video analytics is for. Relatively than terminating in a static report that waits on human interpretation, video understanding turns into the entry level to an orchestrated workflow—one which retrieves the related organizational information, grounds each conclusion in proof, and drives downstream motion robotically.

Enterprises can act on video insights as shortly as they’ll generate them, constantly and at scale. The footage is already being captured. The following alternative is to show it into coordinated, accountable motion, and the blueprints to take action at the moment are obtainable. Able to get began? Use the steps offered on this put up, swapping in your individual video supply and reference information, similar to inspection footage paired with OEM manuals, retail flooring cameras paired with merchandising insurance policies, or reside broadcasts paired with a rulebook.

Clone the VSS repo, deploy the VSS agent with information retrieval (frag) enabled, level the RAG Blueprint at your paperwork, and join NemoClaw to the system your workforce already makes use of, similar to Jira, Slack, a database or a ticket queue. Begin with one recurring loop from video to determination to motion, pilot it end-to-end, and develop from there.



Source link

Tags: AgentsContextAwareenterpriseIntegratingVideoWorkflows
Previous Post

Scaling Agentic AI Factories By means of Excessive Co-Design with NVIDIA BlueField

Next Post

Put together These 5 Property Earlier than Your AI Brokers Take On Extra Work

Next Post
Put together These 5 Property Earlier than Your AI Brokers Take On Extra Work

Put together These 5 Property Earlier than Your AI Brokers Take On Extra Work

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

Fetching latest news…
FUTURENEWS24
Live Feed
All
AI
Dev
Industry
Frontier
Updates in 60s
FN24 AI & Tech
View All →
Future News 24

The world's leading source for AI research, emerging technology, and the people building the future. Independent, rigorous, and always ahead.

CATEGORIES

  • AI Platforms & Apps
  • AI Research & Breakthroughs
  • BioTechnology
  • Data Science & MLOps
  • Decentralized Technology
  • Developer AI & Open-Source Ecosystem
  • Emerging Technologies & Innovations
  • Ethics & Policy
  • Industry & Business
  • Quantum Computing
  • Uncategorized

LATEST

  • [2602.13312] PeroMAS: A Multi-agent System of Perovskite Materials Discovery
  • GPT-6 Astra overview: code overview good points, privateness, and value
  • GPT-6 Astra: Options, Benchmarks, Pricing, and What’s New
  • About Us
  • Advertise with Us
  • Disclaimer
  • Privacy Policy
  • DMCA 
  • Cookie Policy
  • Terms and Conditions
  • Contact us

© 2026 Future News 24. All rights reserved.

Welcome Back!

Login to your account below

Forgotten Password?

Retrieve your password

Please enter your username or email address to reset your password.

Log In
No Result
View All Result
  • Home
  • AI Research
  • Platforms
  • Ethics
  • Developer AI
  • Industry
  • Data Science
  • Emerging Tech
  • Quantum
  • BioTech
  • Decentralized

© 2026 Future News 24. All rights reserved.

Website security powered by MilesWeb