<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Enterprise Blueprint on AI Tools</title>
    <link>https://ait.bsc.es/maturities/enterprise-blueprint/</link>
    <description>Recent content in Enterprise Blueprint on AI Tools</description>
    <generator>Hugo</generator>
    <language>en</language>
    <atom:link href="https://ait.bsc.es/maturities/enterprise-blueprint/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Conversational Support Agent</title>
      <link>https://ait.bsc.es/blueprints/conversational-support-agent/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://ait.bsc.es/blueprints/conversational-support-agent/</guid>
      <description>&lt;h2 id=&#34;overview&#34;&gt;Overview&lt;/h2&gt;&#xA;&lt;p&gt;A tool-using support agent that answers questions against your own documentation and escalates when it cannot.&lt;/p&gt;&#xA;&lt;p&gt;This page shows the structure a blueprint detail page uses. The problem statement and component list below are real design context; the deployment and usage sections are placeholders.&lt;/p&gt;&#xA;&lt;h2 id=&#34;problem-addressed&#34;&gt;Problem addressed&lt;/h2&gt;&#xA;&lt;p&gt;Support teams answer the same documented questions repeatedly, while the genuinely novel cases — the ones that need a human — wait behind them in the same queue.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Document Triage Pipeline</title>
      <link>https://ait.bsc.es/blueprints/document-triage-pipeline/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://ait.bsc.es/blueprints/document-triage-pipeline/</guid>
      <description>&lt;h2 id=&#34;overview&#34;&gt;Overview&lt;/h2&gt;&#xA;&lt;p&gt;An offline batch pipeline that classifies and routes large document sets without an interactive latency budget.&lt;/p&gt;&#xA;&lt;p&gt;This page shows the structure a blueprint detail page uses. The problem statement and component list below are real design context; the deployment and usage sections are placeholders.&lt;/p&gt;&#xA;&lt;h2 id=&#34;problem-addressed&#34;&gt;Problem addressed&lt;/h2&gt;&#xA;&lt;p&gt;Bulk document classification is throughput work, but it is often built on interactive serving infrastructure, which wastes most of the available accelerator capacity.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Clinical Note Summarization</title>
      <link>https://ait.bsc.es/blueprints/clinical-note-summarization/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://ait.bsc.es/blueprints/clinical-note-summarization/</guid>
      <description>&lt;h2 id=&#34;overview&#34;&gt;Overview&lt;/h2&gt;&#xA;&lt;p&gt;Summarize clinical documentation into structured fields with human review built into the workflow.&lt;/p&gt;&#xA;&lt;p&gt;This page shows the structure a blueprint detail page uses. The problem statement and component list below are real design context; the deployment and usage sections are placeholders.&lt;/p&gt;&#xA;&lt;h2 id=&#34;problem-addressed&#34;&gt;Problem addressed&lt;/h2&gt;&#xA;&lt;p&gt;Clinical documentation is long, repetitive and time-consuming to review, but summarizing it automatically raises immediate questions of accuracy, auditability and data handling that a naive integration does not address.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
