[{"data":1,"prerenderedAt":199},["ShallowReactive",2],{"content-doc-\u002Fzh\u002Fusercase\u002Fbuilding-agent-driven-bmc-rd-workflow":3,"surround-\u002Fzh\u002Fusercase\u002Fbuilding-agent-driven-bmc-rd-workflow":197},{"_path":4,"_dir":5,"_draft":6,"_partial":6,"_locale":7,"title":8,"description":9,"company":10,"date":11,"logo":12,"logoDark":13,"body":14,"_type":189,"_id":190,"_source":191,"_file":192,"_stem":193,"_extension":194,"coverImage":79,"plainText":195,"authorNames":196},"\u002Fzh\u002Fusercase\u002Fbuilding-agent-driven-bmc-rd-workflow","usercase",false,"","基于 openUBMC 构建 Agent 驱动的 BMC 研发工作流","BMC 固件研发涵盖源码开发、构建部署、设备验证全链路，任务进度与验证证据分散零散、缺乏统一追溯机制。引入智能 Agent 虽可推进编码与工具调用，但任务跨阶段、会话中断仍需人工重复梳理衔接；同时 BMC 故障属于典型跨层问题，依赖多维度交叉核验，零散的工具调用无法形成可信闭环。因此，亟需一套支持断点续跑、操作可对账、以设备真实状态为验收标准的标准化研发工作流。","软通华方","2026\u002F10\u002F09","\u002Fcategory\u002Fusercase\u002Fbuilding-agent-driven-bmc-rd-workflow\u002Flogo.png","\u002Fcategory\u002Fusercase\u002Fbuilding-agent-driven-bmc-rd-workflow\u002Flogo-dark.png",{"type":15,"children":16,"toc":181},"root",[17,26,31,37,42,67,72,82,93,103,113,119,124,132,138],{"type":18,"tag":19,"props":20,"children":22},"element","h3",{"id":21},"一应用背景",[23],{"type":24,"value":25},"text","一、应用背景",{"type":18,"tag":27,"props":28,"children":29},"p",{},[30],{"type":24,"value":9},{"type":18,"tag":19,"props":32,"children":34},{"id":33},"二解决方案",[35],{"type":24,"value":36},"二、解决方案",{"type":18,"tag":27,"props":38,"children":39},{},[40],{"type":24,"value":41},"软通华方依托 openUBMC 资源模型、组件化开发与设备管理能力，构建了 openUBMC Agent Workflow。该工作流由四层协同：",{"type":18,"tag":43,"props":44,"children":45},"ul",{},[46,52,57,62],{"type":18,"tag":47,"props":48,"children":49},"li",{},[50],{"type":24,"value":51},"宿主 Agent 负责规划与工程判断；",{"type":18,"tag":47,"props":53,"children":54},{},[55],{"type":24,"value":56},"领域工作流通过 Skill 选择诊断、开发、构建、部署或验证路线；",{"type":18,"tag":47,"props":58,"children":59},{},[60],{"type":24,"value":61},"Target Runtime 基于 MCP 管理任务进度、目标连接、资源调度、变更记录与验收结果；",{"type":18,"tag":47,"props":63,"children":64},{},[65],{"type":24,"value":66},"工程环境提供源码\u002F构建能力与真实设备现场。",{"type":18,"tag":27,"props":68,"children":69},{},[70],{"type":24,"value":71},"工程师定义目标与验收条件后，各层协同自主推进分析、修复、构建、升级与实机验证。",{"type":18,"tag":27,"props":73,"children":74},{},[75],{"type":18,"tag":76,"props":77,"children":81},"img",{"alt":78,"src":79,"title":80},"image","\u002Fcategory\u002Fusercase\u002Fbuilding-agent-driven-bmc-rd-workflow\u002Fimg1.png","图 1：openUBMC Agent Workflow 全链路执行与职责分工",[],{"type":18,"tag":27,"props":83,"children":84},{},[85,91],{"type":18,"tag":86,"props":87,"children":88},"strong",{},[89],{"type":24,"value":90},"核心能力一：工程对象贯通",{"type":24,"value":92},"：基于 MDS 模型、MDB\u002FD-Bus 资源对象与北向接口映射，结合源码依赖与构建工具链，保证源码改动、固件制品与设备业务结果三者可追溯。",{"type":18,"tag":27,"props":94,"children":95},{},[96,101],{"type":18,"tag":86,"props":97,"children":98},{},[99],{"type":24,"value":100},"核心能力二：长流程断点续跑与多任务并发",{"type":24,"value":102},"：编译、重启等耗时环节后台运行，中断后可续接；同一任务内无依赖动作并行执行，多任务错峰开展，系统按依赖与资源统一调度。",{"type":18,"tag":27,"props":104,"children":105},{},[106,111],{"type":18,"tag":86,"props":107,"children":108},{},[109],{"type":24,"value":110},"核心能力三：可信执行闭环",{"type":24,"value":112},"：任务档案（Case）保存目标与阶段结果；变更日志（Mutation Journal）记录写操作并核验设备真实状态，避免超时误判；证据账本（Evidence Ledger）管理变更前后证据；任务验收（Closeout）以设备实测结果为准，达标才算闭环。",{"type":18,"tag":19,"props":114,"children":116},{"id":115},"三典型场景示例raid-控制器信息缺失修复",[117],{"type":24,"value":118},"三、典型场景示例：RAID 控制器信息缺失修复",{"type":18,"tag":27,"props":120,"children":121},{},[122],{"type":24,"value":123},"某项目 RAID 卡可识别但控制器信息不显示，日志显示 libsml_lsi.so 加载失败、错误码 4357，定位为适配库缺失。基于 openUBMC Agent Workflow 自动完成依赖修正、测试构建、固件升级及设备恢复，并校验适配库加载与接口状态，研发人员仅需处理核心决策与复杂异常，大幅削减机械值守与重复操作，显著提升故障修复与版本交付效率。",{"type":18,"tag":27,"props":125,"children":126},{},[127],{"type":18,"tag":76,"props":128,"children":131},{"alt":78,"src":129,"title":130},"\u002Fcategory\u002Fusercase\u002Fbuilding-agent-driven-bmc-rd-workflow\u002Fimg2.png","图 2：人工组织与 Workflow 自主推进对比",[],{"type":18,"tag":19,"props":133,"children":135},{"id":134},"四客户价值",[136],{"type":24,"value":137},"四、客户价值",{"type":18,"tag":43,"props":139,"children":140},{},[141,151,161,171],{"type":18,"tag":47,"props":142,"children":143},{},[144,149],{"type":18,"tag":86,"props":145,"children":146},{},[147],{"type":24,"value":148},"高效跨层研判",{"type":24,"value":150},"：统一任务目标串联领域知识、源码、接口与设备证据，并行分析快速收敛故障范围。",{"type":18,"tag":47,"props":152,"children":153},{},[154,159],{"type":18,"tag":86,"props":155,"children":156},{},[157],{"type":24,"value":158},"释放人力成本",{"type":24,"value":160},"：构建、升级、重连、核验等重复动作自动化，工程师专注高价值研发。",{"type":18,"tag":47,"props":162,"children":163},{},[164,169],{"type":18,"tag":86,"props":165,"children":166},{},[167],{"type":24,"value":168},"多任务并行调度",{"type":24,"value":170},"：利用编译、重启等待窗口并行推进其他任务，提升单位时间交付量。",{"type":18,"tag":47,"props":172,"children":173},{},[174,179],{"type":18,"tag":86,"props":175,"children":176},{},[177],{"type":24,"value":178},"沉淀工程资产",{"type":24,"value":180},"：排查逻辑、构建流程、验收规范固化为领域 Skill，同类任务直接复用，持续优化流程。",{"title":7,"searchDepth":182,"depth":182,"links":183},4,[184,186,187,188],{"id":21,"depth":185,"text":25},3,{"id":33,"depth":185,"text":36},{"id":115,"depth":185,"text":118},{"id":134,"depth":185,"text":137},"markdown","content:zh:usercase:building-agent-driven-bmc-rd-workflow.md","content","zh\u002Fusercase\u002Fbuilding-agent-driven-bmc-rd-workflow.md","zh\u002Fusercase\u002Fbuilding-agent-driven-bmc-rd-workflow","md","一、应用背景 BMC 固件研发涵盖源码开发、构建部署、设备验证全链路，任务进度与验证证据分散零散、缺乏统一追溯机制。引入智能 Agent 虽可推进编码与工具调用，但任务跨阶段、会话中断仍需人工重复梳理衔接；同时 BMC 故障属于典型跨层问题，依赖多维度交叉核验，零散的工具调用无法形成可信闭环。因此，亟需一套支持断点续跑、操作可对账、以设备真实状态为验收标准的标准化研发工作流。 二、解决方案 软通华方依托 openUBMC 资源模型、组件化开发与设备管理能力，构建了 openUBMC Agent Workflow。该工作流由四层协同： 宿主 Agent 负责规划与工程判断； 领域工作流通过 Skill 选择诊断、开发、构建、部署或验证路线； Target Runtime 基于 MCP 管理任务进度、目标连接、资源调度、变更记录与验收结果； 工程环境提供源码\u002F构建能力与真实设备现场。 工程师定义目标与验收条件后，各层协同自主推进分析、修复、构建、升级与实机验证。  核心能力一：工程对象贯通 ：基于 MDS 模型、MDB\u002FD-Bus 资源对象与北向接口映射，结合源码依赖与构建工具链，保证源码改动、固件制品与设备业务结果三者可追溯。 核心能力二：长流程断点续跑与多任务并发 ：编译、重启等耗时环节后台运行，中断后可续接；同一任务内无依赖动作并行执行，多任务错峰开展，系统按依赖与资源统一调度。 核心能力三：可信执行闭环 ：任务档案（Case）保存目标与阶段结果；变更日志（Mutation Journal）记录写操作并核验设备真实状态，避免超时误判；证据账本（Evidence Ledger）管理变更前后证据；任务验收（Closeout）以设备实测结果为准，达标才算闭环。 三、典型场景示例：RAID 控制器信息缺失修复 某项目 RAID 卡可识别但控制器信息不显示，日志显示 libsml_lsi.so 加载失败、错误码 4357，定位为适配库缺失。基于 openUBMC Agent Workflow 自动完成依赖修正、测试构建、固件升级及设备恢复，并校验适配库加载与接口状态，研发人员仅需处理核心决策与复杂异常，大幅削减机械值守与重复操作，显著提升故障修复与版本交付效率。  四、客户价值 高效跨层研判 ：统一任务目标串联领域知识、源码、接口与设备证据，并行分析快速收敛故障范围。 释放人力成本 ：构建、升级、重连、核验等重复动作自动化，工程师专注高价值研发。 多任务并行调度 ：利用编译、重启等待窗口并行推进其他任务，提升单位时间交付量。 沉淀工程资产 ：排查逻辑、构建流程、验收规范固化为领域 Skill，同类任务直接复用，持续优化流程。",[],[198,198],null,1791801268659]