<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Ryan Hsu</title>
    <description>The latest articles on DEV Community by Ryan Hsu (@ryan_hsu_wearedge).</description>
    <link>https://dev.to/ryan_hsu_wearedge</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3956029%2Fa0ab9f2d-13d3-4155-83a1-a27534b01118.jpg</url>
      <title>DEV Community: Ryan Hsu</title>
      <link>https://dev.to/ryan_hsu_wearedge</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/ryan_hsu_wearedge"/>
    <language>en</language>
    <item>
      <title>WearEdge Pro: An OPEA Manufacturing Five-Agent Suite for Frontline Operators</title>
      <dc:creator>Ryan Hsu</dc:creator>
      <pubDate>Thu, 28 May 2026 07:49:53 +0000</pubDate>
      <link>https://dev.to/ryan_hsu_wearedge/wearedge-pro-an-opea-manufacturing-five-agent-suite-for-frontline-operators-5afh</link>
      <guid>https://dev.to/ryan_hsu_wearedge/wearedge-pro-an-opea-manufacturing-five-agent-suite-for-frontline-operators-5afh</guid>
      <description>&lt;p&gt;Manufacturing operators often see early warning signs before enterprise systems&lt;br&gt;
do: an unusual gearbox sound, a quality defect, a label changeover mismatch, a&lt;br&gt;
work-instruction question, missing PPE, or a blocked walkway. These observations&lt;br&gt;
are valuable, but they often stay trapped in verbal handoffs.&lt;/p&gt;

&lt;p&gt;WearEdge Pro packages that frontline evidence into an OPEA-aligned&lt;br&gt;
Manufacturing Agent Suite. The submitted competition artifact is not an&lt;br&gt;
Android-only application. It is a Docker-runnable Web/API package with a&lt;br&gt;
browser demo console, five agent routes, Qdrant-backed RAG, official OPEA TEI&lt;br&gt;
embedding profile, guardrails, and evaluation evidence.&lt;/p&gt;

&lt;p&gt;The five agent routes are:&lt;/p&gt;

&lt;p&gt;Agent   Workflow    Target&lt;br&gt;
maintenance Predictive maintenance from M400 evidence   maintenance_work_order&lt;br&gt;
iqc Incoming and in-process quality checks  qms_quality_event&lt;br&gt;
changeover  SKU setup and first-piece verification  changeover_checklist&lt;br&gt;
wi  Released work-instruction guidance  wi_reference&lt;br&gt;
hazard  PPE, moving-parts, and walkway observations ehs_case&lt;br&gt;
The architecture follows an OPEA-style path:&lt;/p&gt;

&lt;p&gt;M400 / API evidence&lt;br&gt;
  -&amp;gt; Gateway&lt;br&gt;
  -&amp;gt; Manufacturing Megaservice&lt;br&gt;
  -&amp;gt; route registry&lt;br&gt;
  -&amp;gt; Dataprep&lt;br&gt;
  -&amp;gt; RAG / Retriever&lt;br&gt;
  -&amp;gt; Qdrant Vector DB&lt;br&gt;
  -&amp;gt; OPEA-compatible embedding service or official OPEA TEI profile&lt;br&gt;
  -&amp;gt; LLM adapter or deterministic demo path&lt;br&gt;
  -&amp;gt; deterministic evaluator&lt;br&gt;
  -&amp;gt; guardrails&lt;br&gt;
  -&amp;gt; bounded action card&lt;br&gt;
The most important design decision is route isolation. Maintenance must not&lt;br&gt;
issue safety clearance. Hazard observations must not invent final root cause.&lt;br&gt;
Quality must not release a lot. Changeover must not grant restart permission.&lt;br&gt;
Work-instruction guidance must stay tied to released source evidence.&lt;/p&gt;

&lt;p&gt;For OPEA evidence, the repository includes:&lt;/p&gt;

&lt;p&gt;Docker Compose base profile with Qdrant and the Manufacturing Gateway;&lt;br&gt;
OPEA-compatible /v1/embeddings profile;&lt;br&gt;
official OPEA TEI profile using Hugging Face TEI, opea/embedding:latest,&lt;br&gt;
TEI_EMBEDDING_ENDPOINT, and OPEA_TEI_EMBEDDING;&lt;br&gt;
OpenAI/OPEA-compatible LLM adapter boundary;&lt;br&gt;
GenAIEval-compatible route evaluation package;&lt;br&gt;
upstream OPEA RFC, comments, and a CI-green GenAIExamples PR.&lt;br&gt;
The evaluation package includes 15 cases across the five routes and verifies:&lt;/p&gt;

&lt;p&gt;action-card contract;&lt;br&gt;
integration target correctness;&lt;br&gt;
channel correctness;&lt;br&gt;
risk-level correctness;&lt;br&gt;
human gate correctness;&lt;br&gt;
guardrail pass;&lt;br&gt;
RAG source match;&lt;br&gt;
route isolation.&lt;br&gt;
The hardware evidence was captured on Google Cloud C3 c3-standard-4: a&lt;br&gt;
single-node, 4-vCPU, 16-GiB-RAM, no-GPU Intel Xeon host exposing AVX-512 and AMX&lt;br&gt;
flags. On that class of host, WearEdge validated the deterministic five-agent&lt;br&gt;
route benchmark, Docker/Qdrant E2E, OPEA-compatible embedding profile E2E, and&lt;br&gt;
official OPEA TEI profile E2E.&lt;/p&gt;

&lt;p&gt;The public repository is here:&lt;/p&gt;

&lt;p&gt;&lt;a href="https://github.com/davidmillerak2026-sys/wearedge-opea-manufacturing" rel="noopener noreferrer"&gt;https://github.com/davidmillerak2026-sys/wearedge-opea-manufacturing&lt;/a&gt;&lt;br&gt;
The upstream OPEA PR is here:&lt;/p&gt;

&lt;p&gt;&lt;a href="https://github.com/opea-project/GenAIExamples/pull/2462" rel="noopener noreferrer"&gt;https://github.com/opea-project/GenAIExamples/pull/2462&lt;/a&gt;&lt;br&gt;
WearEdge is still a prototype, not a certified safety or release controller.&lt;br&gt;
The important point is the platform pattern: one OPEA-aligned manufacturing&lt;br&gt;
suite can convert frontline evidence into bounded, auditable action cards&lt;br&gt;
across maintenance, quality, changeover, work instructions, and safety.&lt;/p&gt;

</description>
      <category>opea</category>
      <category>manufacturing</category>
      <category>rag</category>
      <category>edgeai</category>
    </item>
  </channel>
</rss>
