[{"data":1,"prerenderedAt":1668},["ShallowReactive",2],{"blog-/blog/deepseek-private-deployment-guide":3,"blog-related-/blog/deepseek-private-deployment-guide":532},{"id":4,"title":5,"author":6,"body":7,"category":514,"cover":515,"date":516,"description":517,"extension":518,"meta":519,"navigation":520,"path":521,"readingTime":522,"seo":523,"stem":524,"tags":525,"__hash__":531},"blog/blog/deepseek-private-deployment-guide.md","DeepSeek 大模型私有化部署完整指南：硬件、成本与避坑要点","仙宫云技术团队",{"type":8,"value":9,"toc":494},"minimark",[10,19,24,27,55,59,62,157,163,167,172,175,201,205,208,230,234,237,259,263,266,270,281,285,296,300,311,315,318,400,403,407,440,444,447,467,476,479],[11,12,13,14,18],"p",{},"DeepSeek 在 2024-2025 年成为国内企业大模型私有化部署的首选之一。它开源、中文能力强、推理性能稳定，但真正落地时，企业最常问的三个问题是：",[15,16,17],"strong",{},"要什么硬件？花多少钱？怎么避坑？"," 本文给出 2026 年最新的实操答案。",[20,21,23],"h2",{"id":22},"一为什么企业要做-deepseek-私有化部署","一、为什么企业要做 DeepSeek 私有化部署？",[11,25,26],{},"调用 API 当然便宜，但当业务涉及以下任一情况，私有化部署几乎是唯一选择：",[28,29,30,37,43,49],"ul",{},[31,32,33,36],"li",{},[15,34,35],{},"数据敏感","：客户合同、医疗记录、财务凭证、研发资料这类数据不能出企业内网",[31,38,39,42],{},[15,40,41],{},"合规要求","：等保三级、金融监管、医疗行业合规，明确要求数据本地化",[31,44,45,48],{},[15,46,47],{},"成本临界点","：当 API 月调用量超过 5000 万 tokens，自建反而更便宜",[31,50,51,54],{},[15,52,53],{},"稳定性要求","：业务系统强依赖 AI，不能因为外部 API 限流或宕机而中断",[20,56,58],{"id":57},"二模型版本怎么选","二、模型版本怎么选？",[11,60,61],{},"DeepSeek 官方目前主要开源以下几个版本，企业可根据预算和场景选择：",[63,64,65,84],"table",{},[66,67,68],"thead",{},[69,70,71,75,78,81],"tr",{},[72,73,74],"th",{},"模型",[72,76,77],{},"参数规模",[72,79,80],{},"推荐场景",[72,82,83],{},"最低显存（FP16）",[85,86,87,102,116,130,144],"tbody",{},[69,88,89,93,96,99],{},[90,91,92],"td",{},"DeepSeek-R1-Distill-Qwen-7B",[90,94,95],{},"7B",[90,97,98],{},"客服、简单文档问答",[90,100,101],{},"16 GB",[69,103,104,107,110,113],{},[90,105,106],{},"DeepSeek-R1-Distill-Qwen-14B",[90,108,109],{},"14B",[90,111,112],{},"知识库 RAG、报告生成",[90,114,115],{},"32 GB",[69,117,118,121,124,127],{},[90,119,120],{},"DeepSeek-R1-Distill-Qwen-32B",[90,122,123],{},"32B",[90,125,126],{},"复杂推理、合同审阅",[90,128,129],{},"64 GB",[69,131,132,135,138,141],{},[90,133,134],{},"DeepSeek-V3",[90,136,137],{},"671B (MoE)",[90,139,140],{},"高级 Agent、企业核心场景",[90,142,143],{},"8×A100 80G 起",[69,145,146,149,151,154],{},[90,147,148],{},"DeepSeek-R1",[90,150,137],{},[90,152,153],{},"复杂推理、深度思考任务",[90,155,156],{},"8×H100 80G 起",[11,158,159,162],{},[15,160,161],{},"经验法则","：90% 的企业内部场景（客服、知识库、文档处理）用 14B-32B 蒸馏版就够了，不要一上来就追 671B 满血版，硬件成本会翻 10 倍以上。",[20,164,166],{"id":165},"三硬件配置参考2026-年价格","三、硬件配置参考（2026 年价格）",[168,169,171],"h3",{"id":170},"入门级7b-14b-模型","入门级（7B-14B 模型）",[11,173,174],{},"适合 30-50 人小团队、单一业务场景。",[28,176,177,183,189,195],{},[31,178,179,182],{},[15,180,181],{},"GPU","：1× RTX 4090（24GB）或 1× RTX A6000（48GB）",[31,184,185,188],{},[15,186,187],{},"CPU/内存","：32 核 / 128 GB",[31,190,191,194],{},[15,192,193],{},"存储","：2TB NVMe SSD",[31,196,197,200],{},[15,198,199],{},"整机预算","：6-15 万元",[168,202,204],{"id":203},"中型32b-模型","中型（32B 模型）",[11,206,207],{},"适合 100-500 人企业、多场景并发。",[28,209,210,215,220,225],{},[31,211,212,214],{},[15,213,181],{},"：2× A100 80G 或 4× RTX 4090",[31,216,217,219],{},[15,218,187],{},"：64 核 / 256 GB",[31,221,222,224],{},[15,223,193],{},"：4TB NVMe SSD",[31,226,227,229],{},[15,228,199],{},"：35-60 万元",[168,231,233],{"id":232},"旗舰级deepseek-v3r1-满血版","旗舰级（DeepSeek-V3/R1 满血版）",[11,235,236],{},"适合大型集团、高并发核心业务。",[28,238,239,244,249,254],{},[31,240,241,243],{},[15,242,181],{},"：8× H100 80G 或 8× A100 80G（NVLink 互联）",[31,245,246,248],{},[15,247,187],{},"：128 核 / 1TB",[31,250,251,253],{},[15,252,193],{},"：10TB+ NVMe SSD",[31,255,256,258],{},[15,257,199],{},"：200-400 万元",[20,260,262],{"id":261},"四推理框架怎么选","四、推理框架怎么选？",[11,264,265],{},"部署框架直接影响吞吐量和响应延迟。三个主流选择：",[168,267,269],{"id":268},"_1-vllm生产首选","1. vLLM（生产首选）",[28,271,272,275,278],{},[31,273,274],{},"优点：吞吐量高、支持 PagedAttention、连续批处理",[31,276,277],{},"缺点：配置稍复杂",[31,279,280],{},"适用：生产环境、高并发场景",[168,282,284],{"id":283},"_2-ollama最简单","2. Ollama（最简单）",[28,286,287,290,293],{},[31,288,289],{},"优点：一行命令启动、支持量化模型",[31,291,292],{},"缺点：单机性能有限，不适合高并发",[31,294,295],{},"适用：POC 验证、小团队内部使用",[168,297,299],{"id":298},"_3-sglang前沿","3. SGLang（前沿）",[28,301,302,305,308],{},[31,303,304],{},"优点：结构化生成快，工具调用场景表现好",[31,306,307],{},"缺点：生态相对新",[31,309,310],{},"适用：Agent 应用、复杂推理",[20,312,314],{"id":313},"五典型企业部署成本拆解","五、典型企业部署成本拆解",[11,316,317],{},"以一个 200 人制造企业部署 DeepSeek-R1-Distill-Qwen-32B 为例：",[63,319,320,333],{},[66,321,322],{},[69,323,324,327,330],{},[72,325,326],{},"项目",[72,328,329],{},"一次性",[72,331,332],{},"年化",[85,334,335,346,356,366,376,386],{},[69,336,337,340,343],{},[90,338,339],{},"硬件采购（2× A100）",[90,341,342],{},"45 万",[90,344,345],{},"-",[69,347,348,351,354],{},[90,349,350],{},"机房环境改造",[90,352,353],{},"5 万",[90,355,345],{},[69,357,358,361,364],{},[90,359,360],{},"部署实施服务",[90,362,363],{},"8-15 万",[90,365,345],{},[69,367,368,371,373],{},[90,369,370],{},"电费（24/7 运行）",[90,372,345],{},[90,374,375],{},"3-5 万",[69,377,378,381,383],{},[90,379,380],{},"运维与模型更新",[90,382,345],{},[90,384,385],{},"6-12 万",[69,387,388,393,398],{},[90,389,390],{},[15,391,392],{},"三年总成本",[90,394,395],{},[15,396,397],{},"约 75-90 万",[90,399,345],{},[11,401,402],{},"对照 API 方案：同样规模业务调用，按 0.001 元/千 tokens 估算，三年通常在 30-150 万之间——但数据出域、不可控、长期议价权弱。",[20,404,406],{"id":405},"六企业落地最容易踩的-5-个坑","六、企业落地最容易踩的 5 个坑",[408,409,410,416,422,428,434],"ol",{},[31,411,412,415],{},[15,413,414],{},"追求满血版","：90% 场景蒸馏版足够，盲目上 671B 浪费硬件",[31,417,418,421],{},[15,419,420],{},"忽视吞吐量测试","：部署完才发现并发 10 人就卡，前期没做压测",[31,423,424,427],{},[15,425,426],{},"没做模型评估","：直接选最火的，没用自家业务数据测准确率",[31,429,430,433],{},[15,431,432],{},"忽略 RAG 配套","：模型部署完没接知识库，用户体验和直接调 API 没区别",[31,435,436,439],{},[15,437,438],{},"缺乏运维计划","：模型发版迭代、显卡故障处理、效果回归没人管",[20,441,443],{"id":442},"七仙宫云的部署服务","七、仙宫云的部署服务",[11,445,446],{},"仙宫云已为多家制造、零售、医疗、金融企业完成 DeepSeek 私有化部署，提供：",[28,448,449,455,461],{},[31,450,451,454],{},[15,452,453],{},"部署前","：业务场景评估、模型选型、硬件方案、ROI 测算",[31,456,457,460],{},[15,458,459],{},"部署中","：硬件部署、模型推理优化、RAG 知识库集成、应用对接",[31,462,463,466],{},[15,464,465],{},"部署后","：员工培训、效果监控、模型版本升级、长期陪跑",[11,468,469,470,475],{},"如果你正在评估 DeepSeek 私有化部署，欢迎",[471,472,474],"a",{"href":473},"/contact","联系我们","获取免费方案评估。",[477,478],"hr",{},[11,480,481,484,485,489,490],{},[15,482,483],{},"相关阅读","：",[471,486,488],{"href":487},"/blog/enterprise-rag-guide","企业知识库 RAG 实战教程"," | ",[471,491,493],{"href":492},"/blog/traditional-enterprise-ai-challenges","传统企业 AI 落地的真实困境",{"title":495,"searchDepth":496,"depth":496,"links":497},"",2,[498,499,500,506,511,512,513],{"id":22,"depth":496,"text":23},{"id":57,"depth":496,"text":58},{"id":165,"depth":496,"text":166,"children":501},[502,504,505],{"id":170,"depth":503,"text":171},3,{"id":203,"depth":503,"text":204},{"id":232,"depth":503,"text":233},{"id":261,"depth":496,"text":262,"children":507},[508,509,510],{"id":268,"depth":503,"text":269},{"id":283,"depth":503,"text":284},{"id":298,"depth":503,"text":299},{"id":313,"depth":496,"text":314},{"id":405,"depth":496,"text":406},{"id":442,"depth":496,"text":443},"私有化部署",null,"2026-04-12","一篇文章看懂 DeepSeek-R1/V3 私有化部署所需的硬件、显存、推理框架选择、典型成本区间与企业落地常见坑，2026 年最新版。","md",{},true,"/blog/deepseek-private-deployment-guide",12,{"title":5,"description":517},"blog/deepseek-private-deployment-guide",[526,527,528,529,530],"DeepSeek","大模型私有化部署","本地化部署","vLLM","Ollama","CnUfK8LxNz_IpO364Os_X0FVfj8Hvm3vAdpqq6ePD7A",[533,787,1175],{"id":534,"title":535,"author":536,"body":537,"category":774,"cover":515,"date":775,"description":776,"extension":518,"meta":777,"navigation":520,"path":778,"readingTime":779,"seo":780,"stem":781,"tags":782,"__hash__":786},"blog/blog/enterprise-ai-private-deployment-mainstream-2026.md","60% 的企业已选择 AI 私有化部署，传统企业还在等什么？","仙宫云团队",{"type":8,"value":538,"toc":767},[539,542,545,548,554,558,561,572,575,585,595,601,604,607,610,616,622,628,632,638,643,646,651,658,663,666,692,697,700,704,709,712,715,718,720,725,728,731,734,736,740,743,746,752],[11,540,541],{},"去年，广东某制造集团的 IT 负责人找到我们，说起公司错失的半年时间。",[11,543,544],{},"2025 年初，集团高层已达成共识：要引入大模型，解决技术文档检索效率低的老大难问题。但方案迟迟没落地——有人担心员工把图纸上传到云端 AI，数据泄露怎么办？有人觉得国产模型还不成熟，再等等。等来等去，半年过去了，竞争对手的 AI 知识库已经上线三个月，新人培训周期从两个月缩短到不足一个月。",[11,546,547],{},"这家企业的遭遇并不罕见。",[11,549,550,551],{},"今天，摆在传统企业面前的问题，早已不是\"要不要做 AI\"，而是：",[15,552,553],{},"怎么做，才能安全？",[20,555,557],{"id":556},"行业拐点私有化部署正在成为标配","行业拐点：私有化部署正在成为标配",[11,559,560],{},"2026 年，企业 AI 落地进入了一个新阶段。",[11,562,563,564,567,568,571],{},"根据多份行业研究，目前国内企业级 AI 部署中，",[15,565,566],{},"私有化部署占比已超过 60%","，成为金融、政务、制造等核心领域的首选模式。中国大模型市场规模预计今年突破 ",[15,569,570],{},"700 亿元","，其中相当大比例来自企业私有化部署和定制化服务。",[11,573,574],{},"是什么让私有化部署从\"少数人的选择\"变成主流？三个力量同时在推动：",[11,576,577,580,581,584],{},[15,578,579],{},"监管压力。"," 2026 年 1 月 1 日起施行的《网络安全法》修订版，首次将 AI 安全写入法条。数据跨境管控更严，关键信息基础设施数据须境内存储，违规最高罚款从 50 万元上升至 ",[15,582,583],{},"1000 万元","。对于金融、医疗、政务等企业，把数据传到第三方云端 AI 服务，已经不只是技术风险，更是合规风险。",[11,586,587,590,591,594],{},[15,588,589],{},"硬件成本大幅下降。"," 过去谈大模型私有化，很多企业第一反应是\"买不起 GPU\"。但量化压缩技术的成熟改变了这一局面——通过 INT4/INT8 混合精度量化，",[15,592,593],{},"在普通服务器上即可运行百亿参数级别的大模型","，硬件成本相比两年前降低了约 70%。私有化部署的门槛，已经不是大企业的专属。",[11,596,597,600],{},[15,598,599],{},"开源模型生态成熟。"," DeepSeek-V3、Qwen3、ChatGLM 等国产开源大模型持续迭代，综合能力已可媲美商用模型。企业无需从零训练一个专属大模型，基于成熟开源模型做私有化部署和微调，既省钱又省时间。",[11,602,603],{},"三个条件同时具备，这就是为什么 2026 年私有化部署进入爆发期。",[20,605,606],{"id":606},"企业落地的三道坎",[11,608,609],{},"尽管大环境已经成熟，但很多企业依然卡在起步阶段。根据我们服务超过 50 家企业的经验，落地难通常集中在三个环节：",[11,611,612,615],{},[15,613,614],{},"选型难。"," DeepSeek、Qwen、Llama、ChatGLM……国内外可用的开源大模型超过数十个，每隔几个月就有新版本发布。企业 IT 团队往往花了大量时间研究模型参数，却不知道哪个适合自己的业务场景。制造业和零售业对模型的要求完全不同，同样是\"客服机器人\"，对话轮次、工具调用、多语言支持的侧重也各有差异。没有专业的场景分析，选型很容易走弯路。",[11,617,618,621],{},[15,619,620],{},"部署难。"," 模型选好了，怎么在公司服务器上跑起来？vLLM、Ollama、SGLang 这些推理框架怎么配置？显存不够用了怎么量化？RAG 检索系统怎么和内部文档对接？这些问题，需要算法工程师、运维工程师协作配合，对于大多数传统企业而言，这样的技术团队根本不存在。",[11,623,624,627],{},[15,625,626],{},"用起来难。"," 这是最容易被低估的一环。很多企业花钱买了咨询方案，把模型部署好了，却发现员工不会用，或者系统跟实际业务流程脱节，最终成了摆设。AI 落地不是\"跑通 Demo\"，而是要真正嵌入采购、客服、研发、运营等具体流程，才能产生可衡量的 ROI。",[20,629,631],{"id":630},"仙宫云的解法陪企业拿到结果","仙宫云的解法：陪企业拿到结果",[11,633,634,635],{},"仙宫云成立于 2021 年，从企业级软件起家，2023 年完成 AI 战略转型。我们不卖单纯的\"部署服务\"，而是提供从场景调研到员工培训的端到端交付——",[15,636,637],{},"因为我们知道，模型跑通只是开始。",[11,639,640],{},[15,641,642],{},"第一步：场景调研与选型",[11,644,645],{},"在正式报价之前，我们会先和企业做 2–4 小时的业务调研，梳理哪些场景 AI 价值最高、ROI 最快。然后横向评估 DeepSeek、Qwen、Llama 等主流模型，结合企业硬件现状，给出选型建议和 ROI 测算。企业不需要懂模型，只需要讲清楚业务目标。",[11,647,648],{},[15,649,650],{},"第二步：私有化部署与推理优化",[11,652,653,654,657],{},"在企业本地服务器或私有云完成全套部署，数据 ",[15,655,656],{},"100% 不出企业网络","。我们会做量化、并行推理、缓存等性能优化，确保模型响应速度满足业务需求。同时配合企业完成等保对接、数据加密和权限管理，满足金融、医疗等行业的合规要求。",[11,659,660],{},[15,661,662],{},"第三步：业务应用开发",[11,664,665],{},"部署完成后，我们基于企业实际业务开发应用层：",[28,667,668,674,680,686],{},[31,669,670,673],{},[15,671,672],{},"企业知识库","：打通内部文档、手册、规范，支持自然语言检索，实现\"问就有答\"",[31,675,676,679],{},[15,677,678],{},"智能客服","：多轮对话、工单生成、跨系统数据查询，7×24 小时响应",[31,681,682,685],{},[15,683,684],{},"AI Agent","：业务流程自动化，多工具调用，解放重复性人工操作",[31,687,688,691],{},[15,689,690],{},"文档智能","：合同审阅、报告生成、单据解析，提升文字处理效率",[11,693,694],{},[15,695,696],{},"第四步：培训与持续陪跑",[11,698,699],{},"上线不是终点。我们提供管理层赋能培训、员工 Prompt 技巧培训，以及季度运营复盘。新模型发布时，我们会第一时间评估是否值得升级并给出建议。这个阶段，我们更像企业的 AI 内部顾问，而不是外包供应商。",[20,701,703],{"id":702},"数字说话两个已落地的案例","数字说话：两个已落地的案例",[11,705,706],{},[15,707,708],{},"某大型制造集团（5000+ 员工）",[11,710,711],{},"痛点：技术文档分散，工程师查阅资料费时费力，新员工培训周期长达两个月。",[11,713,714],{},"方案：DeepSeek-R1 本地部署 + 工艺文档 / 设备手册 / 质检规范知识库，数据 100% 私有化存储。",[11,716,717],{},"成效：技术资料检索效率提升 60%，新人培训周期缩短 50%，3 个月完成交付。",[477,719],{},[11,721,722],{},[15,723,724],{},"某金融科技公司",[11,726,727],{},"痛点：信贷审批依赖人工，风险识别准确率不稳定，合规审计耗时长。",[11,729,730],{},"方案：私有化大模型 + 信用评估 / 欺诈检测 / 反洗钱应用，满足等保三级合规要求。",[11,732,733],{},"成效：风险识别准确率达到 95% 以上，审批效率提升 80%，5 个月完成交付并上线。",[477,735],{},[20,737,739],{"id":738},"现在入场正当其时","现在入场，正当其时",[11,741,742],{},"Gartner 预测，2026 年将有 40% 的企业级应用嵌入 AI 智能体——而一年前，这个比例还不到 5%。这不是一个缓慢的趋势，而是一次快速的分水岭。",[11,744,745],{},"硬件成本已经降到足够低，开源模型已经成熟到足够好，监管框架已经明确到可以照着执行。此刻入场，三个条件同时具备，再等下去，等来的只有竞争对手扩大的领先优势。",[11,747,748,751],{},[15,749,750],{},"仙宫云目前开放企业 AI 场景免费诊断服务。"," 无论你的企业还在观望、刚开始选型、还是已经部署遇到困难，欢迎通过邮件或企业微信联系我们，2 小时内响应，给出可落地的分析建议。",[28,753,754,761,764],{},[31,755,756,757],{},"商务邮箱：",[471,758,760],{"href":759},"mailto:info@xiangong.net","info@xiangong.net",[31,762,763],{},"地址：广东省东莞市",[31,765,766],{},"工作时间：周一至周六 9:00–18:00",{"title":495,"searchDepth":496,"depth":496,"links":768},[769,770,771,772,773],{"id":556,"depth":496,"text":557},{"id":606,"depth":496,"text":606},{"id":630,"depth":496,"text":631},{"id":702,"depth":496,"text":703},{"id":738,"depth":496,"text":739},"行业洞察","2026-05-07","2026年大模型市场规模预计突破700亿，私有化部署占比已超60%。本文结合最新行业数据，解析企业AI落地三大难题与仙宫云的端到端解法。",{},"/blog/enterprise-ai-private-deployment-mainstream-2026",5,{"title":535,"description":776},"blog/enterprise-ai-private-deployment-mainstream-2026",[783,784,526,785,672],"企业AI私有化部署","大模型私有化","AI落地","t02CWcLmcOQK7_BnGYzlVkBcCjPDZQ7C8ql_iUaxhUU",{"id":788,"title":789,"author":6,"body":790,"category":774,"cover":515,"date":1162,"description":1163,"extension":518,"meta":1164,"navigation":520,"path":492,"readingTime":1165,"seo":1166,"stem":1167,"tags":1168,"__hash__":1174},"blog/blog/traditional-enterprise-ai-challenges.md","传统企业 AI 落地为什么这么难？三个真实案例分析",{"type":8,"value":791,"toc":1138},[792,799,803,806,813,817,820,831,834,840,851,855,858,890,900,904,907,910,913,919,922,933,936,939,968,971,976,980,983,986,989,992,1006,1009,1016,1041,1044,1053,1057,1061,1064,1068,1071,1075,1082,1086,1089,1115,1121,1127,1129],[11,793,794,795,798],{},"DeepSeek 火了之后，老板们都在问\"我们怎么用 AI\"。但真正动手做的传统企业里，",[15,796,797],{},"有 70% 的项目在 6 个月内被搁置","。原因不是 AI 不行，而是落地路径选错了。本文用三个真实案例（已脱敏），讲清楚传统企业 AI 落地的难点和正确姿势。",[20,800,802],{"id":801},"案例一某制造集团的ai-客服折戟","案例一：某制造集团的\"AI 客服\"折戟",[168,804,805],{"id":805},"背景",[11,807,808,809,812],{},"一家年产值 50 亿的工业设备制造商，2024 年初决定上 AI。老板的诉求很明确：",[15,810,811],{},"\"我看别人都做 AI 客服，我们也来一套\"","。",[168,814,816],{"id":815},"第一次尝试失败","第一次尝试（失败）",[11,818,819],{},"公司 IT 部门花 30 万买了某 SaaS 厂商的\"通用 AI 客服\"。3 个月后下线，原因：",[28,821,822,825,828],{},[31,823,824],{},"客户问的都是\"3 号轴承能不能配 5 号设备\"这种专业问题",[31,826,827],{},"通用模型完全答不上来，只会说\"建议联系人工客服\"",[31,829,830],{},"客户体验比之前的电话客服还差",[168,832,833],{"id":833},"失败的根本原因",[11,835,836,839],{},[15,837,838],{},"\"AI 客服\"是结果，不是起点。"," 老板只看到别人有 AI 客服，没看到背后需要：",[28,841,842,845,848],{},[31,843,844],{},"完整的产品知识库（这家公司的产品手册散落在 5 个部门的硬盘里）",[31,846,847],{},"历史客服对话数据（之前都用电话，根本没数字化）",[31,849,850],{},"业务规则梳理（哪些问题可以自动回，哪些必须转人工）",[168,852,854],{"id":853},"第二次尝试成功","第二次尝试（成功）",[11,856,857],{},"仙宫云接手后，重新规划路径：",[408,859,860,866,872,878,884],{},[31,861,862,865],{},[15,863,864],{},"第 1 个月","：整理产品手册，建私有知识库",[31,867,868,871],{},[15,869,870],{},"第 2 个月","：部署 DeepSeek-32B + RAG，先给内部销售工程师用",[31,873,874,877],{},[15,875,876],{},"第 3 个月","：收集 500+ 真实问题，迭代 Prompt 和切片策略",[31,879,880,883],{},[15,881,882],{},"第 4 个月","：开放给经销商，验证准确率达 85%",[31,885,886,889],{},[15,887,888],{},"第 6 个月","：上线 C 端客服",[11,891,892,895,896,899],{},[15,893,894],{},"关键洞察","：传统企业上 AI，",[15,897,898],{},"先做内部工具，再做对外应用","。内部用户容忍度高，是 AI 应用最好的 POC 场景。",[20,901,903],{"id":902},"案例二某连锁零售的ai-推荐失灵","案例二：某连锁零售的\"AI 推荐失灵\"",[168,905,805],{"id":906},"背景-1",[11,908,909],{},"300+ 门店连锁餐饮品牌，想做\"AI 个性化菜品推荐\"。第三方乙方报价 80 万，承诺三个月上线。",[168,911,912],{"id":912},"失败点",[11,914,915,916,812],{},"3 个月后系统上线，但经理反馈：",[15,917,918],{},"推荐的菜还不如收银员根据天气和时段拍脑袋的准",[11,920,921],{},"复盘发现：",[28,923,924,927,930],{},[31,925,926],{},"训练数据只有近 6 个月销售记录，没有节假日、天气、促销变量",[31,928,929],{},"\"推荐\"这个动作没有融入门店实际运营流程，店员根本不看",[31,931,932],{},"没有 A/B 测试机制，无法证明\"AI 推荐 vs 人工推荐\"哪个更好",[168,934,935],{"id":935},"改进路径",[11,937,938],{},"仙宫云重新介入，把\"AI 推荐\"拆成三个更小的问题：",[408,940,941,950,959],{},[31,942,943,946,947],{},[15,944,945],{},"新菜上市预测","：基于历史数据预测某门店上新菜的销量，",[15,948,949],{},"辅助采购",[31,951,952,955,956],{},[15,953,954],{},"库存预警","：哪些菜品在哪些门店即将售罄/滞销，",[15,957,958],{},"辅助调拨",[31,960,961,964,965],{},[15,962,963],{},"门店选址洞察","：开新店时基于周边数据生成评估报告，",[15,966,967],{},"辅助决策",[11,969,970],{},"这三个场景都是\"AI 给建议，人做决策\"，门店运营效率提升 18%，年化收益约 2400 万。",[11,972,973,975],{},[15,974,894],{},"：传统行业不要追求\"AI 替代人\"，先做\"AI 辅助决策\"。决策权留给业务人员，反而推广得更顺。",[20,977,979],{"id":978},"案例三某三甲医院的合规死局","案例三：某三甲医院的合规死局",[168,981,805],{"id":982},"背景-2",[11,984,985],{},"某省级三甲医院想做 AI 病历助手，提升医生写病历效率（医生抱怨写病历占 30% 工作时间）。",[168,987,988],{"id":988},"三个月没动起来",[11,990,991],{},"不是技术问题，是数据问题：",[28,993,994,1000,1003],{},[31,995,996,997],{},"病历是核心医疗数据，根据《医疗机构病历管理规定》和等保三级要求，",[15,998,999],{},"绝对不能上公有云",[31,1001,1002],{},"院内 IT 团队没有大模型经验",[31,1004,1005],{},"厂商方案要求开放外网，被信息科一票否决",[168,1007,1008],{"id":1008},"解决方案",[11,1010,1011,1012,1015],{},"仙宫云的方案完全围绕\"",[15,1013,1014],{},"数据不出院","\"设计：",[408,1017,1018,1024,1029,1035],{},[31,1019,1020,1023],{},[15,1021,1022],{},"硬件","：在医院信息中心机房部署 2× A100 GPU 服务器",[31,1025,1026,1028],{},[15,1027,74],{},"：本地化部署 DeepSeek-R1-Distill-Qwen-32B + 医疗领域微调",[31,1030,1031,1034],{},[15,1032,1033],{},"应用","：与院内 HIS/EMR 系统对接，医生在熟悉的系统里使用 AI 辅助",[31,1036,1037,1040],{},[15,1038,1039],{},"合规","：通过院内信息安全审计、审计日志全留痕",[11,1042,1043],{},"效果：医生病历书写时间减少 50%，3 个月内全院推广。",[11,1045,1046,1048,1049,1052],{},[15,1047,894],{},"：合规要求严格的行业（金融、医疗、政务、能源），",[15,1050,1051],{},"私有化部署不是可选项，是必选项","。任何方案绕不过这一条。",[20,1054,1056],{"id":1055},"总结传统企业-ai-落地的三条铁律","总结：传统企业 AI 落地的三条铁律",[168,1058,1060],{"id":1059},"_1-不要从我要做-x开始要从我想解决-y开始","1. 不要从\"我要做 X\"开始，要从\"我想解决 Y\"开始",[11,1062,1063],{},"\"做 AI 客服\"是结果，\"客户咨询响应慢导致流失\"是问题。从问题出发才能选对路径。",[168,1065,1067],{"id":1066},"_2-先内部再外部先辅助再替代","2. 先内部，再外部；先辅助，再替代",[11,1069,1070],{},"内部工具是最好的 AI 试验田，员工反馈快、容错高。\"AI 替代人\"的项目失败率远高于\"AI 辅助人\"。",[168,1072,1074],{"id":1073},"_3-合规与数据安全是前置条件不是可选项","3. 合规与数据安全是前置条件，不是可选项",[11,1076,1077,1078,1081],{},"任何涉及客户/员工/经营数据的 AI 项目，",[15,1079,1080],{},"先想清楚数据怎么走、合规怎么过","。私有化部署是大多数传统企业的唯一答案。",[20,1083,1085],{"id":1084},"仙宫云的传统企业-ai-落地方法论","仙宫云的传统企业 AI 落地方法论",[11,1087,1088],{},"我们服务过的 50+ 传统企业，提炼出一套\"四阶段陪跑\"方法：",[408,1090,1091,1097,1103,1109],{},[31,1092,1093,1096],{},[15,1094,1095],{},"诊断期（2-4 周）","：业务调研 + AI 高价值场景识别",[31,1098,1099,1102],{},[15,1100,1101],{},"POC 期（4-8 周）","：选定 1-2 个场景小规模验证",[31,1104,1105,1108],{},[15,1106,1107],{},"推广期（2-3 个月）","：场景扩展 + 员工培训 + 流程嵌入",[31,1110,1111,1114],{},[15,1112,1113],{},"运营期（持续）","：效果监控 + 迭代优化 + 新场景挖掘",[11,1116,1117,1120],{},[15,1118,1119],{},"真正难的不是部署模型，而是把 AI 嵌入业务流程并让员工用起来。"," 这是仙宫云区别于纯技术乙方的核心价值。",[11,1122,1123,1124,1126],{},"如果你的企业正在评估 AI 落地路径，欢迎",[471,1125,474],{"href":473},"获取免费的场景诊断与可行性评估。",[477,1128],{},[11,1130,1131,484,1133,489,1136],{},[15,1132,483],{},[471,1134,1135],{"href":521},"DeepSeek 私有化部署完整指南",[471,1137,488],{"href":487},{"title":495,"searchDepth":496,"depth":496,"links":1139},[1140,1146,1151,1156,1161],{"id":801,"depth":496,"text":802,"children":1141},[1142,1143,1144,1145],{"id":805,"depth":503,"text":805},{"id":815,"depth":503,"text":816},{"id":833,"depth":503,"text":833},{"id":853,"depth":503,"text":854},{"id":902,"depth":496,"text":903,"children":1147},[1148,1149,1150],{"id":906,"depth":503,"text":805},{"id":912,"depth":503,"text":912},{"id":935,"depth":503,"text":935},{"id":978,"depth":496,"text":979,"children":1152},[1153,1154,1155],{"id":982,"depth":503,"text":805},{"id":988,"depth":503,"text":988},{"id":1008,"depth":503,"text":1008},{"id":1055,"depth":496,"text":1056,"children":1157},[1158,1159,1160],{"id":1059,"depth":503,"text":1060},{"id":1066,"depth":503,"text":1067},{"id":1073,"depth":503,"text":1074},{"id":1084,"depth":496,"text":1085},"2026-04-28","从制造、零售、医疗三个真实行业案例，分析传统企业 AI 落地的核心挑战与可行路径，帮助决策者避坑。",{},9,{"title":789,"description":1163},"blog/traditional-enterprise-ai-challenges",[1169,1170,1171,1172,1173],"企业AI落地","AI转型","制造业AI","零售AI","医疗AI","LkS3KZCh7u39y97nZw71AVsAs5WvLsLxPbtn4xjO8wM",{"id":1176,"title":1177,"author":6,"body":1178,"category":1656,"cover":515,"date":1657,"description":1658,"extension":518,"meta":1659,"navigation":520,"path":487,"readingTime":1660,"seo":1661,"stem":1662,"tags":1663,"__hash__":1667},"blog/blog/enterprise-rag-guide.md","企业知识库 RAG 实战：从文档到 AI 问答的 5 个关键步骤",{"type":8,"value":1179,"toc":1635},[1180,1187,1191,1197,1203,1264,1270,1274,1277,1281,1304,1308,1311,1331,1335,1338,1342,1345,1349,1369,1373,1419,1423,1429,1449,1452,1456,1459,1468,1473,1484,1488,1491,1495,1498,1518,1522,1530,1534,1537,1551,1555,1587,1591,1594,1620,1625,1627],[11,1181,1182,1183,1186],{},"\"我们公司有几万份 Word/PDF 文档，想做一个 AI 问答助手，新员工有问题直接问就能拿答案，可不可行？\"——这是仙宫云客户最高频的需求之一。答案是肯定的，技术路径就是 ",[15,1184,1185],{},"RAG（Retrieval-Augmented Generation，检索增强生成）","。本文拆解从 0 到 1 的 5 个关键步骤。",[20,1188,1190],{"id":1189},"一rag-是什么为什么不直接微调模型","一、RAG 是什么？为什么不直接微调模型？",[11,1192,1193,1196],{},[15,1194,1195],{},"RAG 的核心思想","：用户提问 → 先从企业文档库检索最相关的几段内容 → 把这些内容作为上下文交给大模型 → 大模型基于上下文生成回答。",[11,1198,1199,1202],{},[15,1200,1201],{},"对比微调（Fine-tuning）","，RAG 有三个企业级优势：",[63,1204,1205,1218],{},[66,1206,1207],{},[69,1208,1209,1212,1215],{},[72,1210,1211],{},"维度",[72,1213,1214],{},"RAG",[72,1216,1217],{},"微调",[85,1219,1220,1231,1242,1253],{},[69,1221,1222,1225,1228],{},[90,1223,1224],{},"知识更新",[90,1226,1227],{},"改文档即可",[90,1229,1230],{},"需要重新训练",[69,1232,1233,1236,1239],{},[90,1234,1235],{},"成本",[90,1237,1238],{},"低（无需 GPU 训练）",[90,1240,1241],{},"高（数据 + 算力）",[69,1243,1244,1247,1250],{},[90,1245,1246],{},"可追溯",[90,1248,1249],{},"答案能引用原文",[90,1251,1252],{},"黑盒输出",[69,1254,1255,1258,1261],{},[90,1256,1257],{},"数据安全",[90,1259,1260],{},"文档保留在向量库",[90,1262,1263],{},"知识被吸收进权重",[11,1265,1266,1269],{},[15,1267,1268],{},"结论","：90% 的企业知识库场景，用 RAG 比微调更合适。",[20,1271,1273],{"id":1272},"二step-1文档预处理最容易被低估的环节","二、Step 1：文档预处理（最容易被低估的环节）",[11,1275,1276],{},"垃圾进，垃圾出。RAG 效果上限被这一步决定。",[168,1278,1280],{"id":1279},"_21-文档收集与格式统一","2.1 文档收集与格式统一",[28,1282,1283,1286,1289],{},[31,1284,1285],{},"收集来源：Word、PDF、PPT、Markdown、Confluence、邮件归档",[31,1287,1288],{},"统一转 Markdown 或纯文本，保留标题层级",[31,1290,1291,1292,1296,1297,1296,1300,1303],{},"工具推荐：",[1293,1294,1295],"code",{},"unstructured","、",[1293,1298,1299],{},"Docling",[1293,1301,1302],{},"MinerU","（中文 PDF 表现好）",[168,1305,1307],{"id":1306},"_22-切片chunking策略","2.2 切片（Chunking）策略",[11,1309,1310],{},"切片大小直接影响检索精度：",[28,1312,1313,1319,1325],{},[31,1314,1315,1318],{},[15,1316,1317],{},"太大","（>1500 字）：检索粒度粗，无关内容多",[31,1320,1321,1324],{},[15,1322,1323],{},"太小","（\u003C200 字）：上下文不完整，模型无法理解",[31,1326,1327,1330],{},[15,1328,1329],{},"推荐","：500-800 字 + 50-100 字重叠（overlap）",[168,1332,1334],{"id":1333},"_23-元数据标注","2.3 元数据标注",[11,1336,1337],{},"每个切片附加元数据：来源文档、章节、更新日期、部门、权限等级。这些字段在检索阶段可以做过滤，比如\"只查财务部 2025 年之后的制度\"。",[20,1339,1341],{"id":1340},"三step-2向量化与向量数据库","三、Step 2：向量化与向量数据库",[11,1343,1344],{},"把文本切片转成向量，让\"语义相似度\"可以被计算。",[168,1346,1348],{"id":1347},"_31-中文-embedding-模型推荐","3.1 中文 Embedding 模型推荐",[28,1350,1351,1357,1363],{},[31,1352,1353,1356],{},[15,1354,1355],{},"bge-m3","（智源）：多语言、长文本、目前中文综合最佳",[31,1358,1359,1362],{},[15,1360,1361],{},"text2vec-base-chinese","：轻量，适合资源有限场景",[31,1364,1365,1368],{},[15,1366,1367],{},"OpenAI text-embedding-3-large","：闭源但效果稳定（数据出域慎用）",[168,1370,1372],{"id":1371},"_32-向量数据库选型","3.2 向量数据库选型",[63,1374,1375,1385],{},[66,1376,1377],{},[69,1378,1379,1382],{},[72,1380,1381],{},"数据库",[72,1383,1384],{},"适用场景",[85,1386,1387,1395,1403,1411],{},[69,1388,1389,1392],{},[90,1390,1391],{},"Milvus",[90,1393,1394],{},"大规模（千万级以上向量），生产首选",[69,1396,1397,1400],{},[90,1398,1399],{},"Qdrant",[90,1401,1402],{},"中小规模，部署简单，过滤能力强",[69,1404,1405,1408],{},[90,1406,1407],{},"Chroma",[90,1409,1410],{},"POC 验证、小团队",[69,1412,1413,1416],{},[90,1414,1415],{},"PostgreSQL + pgvector",[90,1417,1418],{},"已有 PG 基础设施，向量量级 100 万以内",[20,1420,1422],{"id":1421},"四step-3检索策略决定准确率的关键","四、Step 3：检索策略（决定准确率的关键）",[11,1424,1425,1426,484],{},"只用向量相似度（dense retrieval）远远不够。生产级 RAG 一定要做 ",[15,1427,1428],{},"混合检索",[408,1430,1431,1437,1443],{},[31,1432,1433,1436],{},[15,1434,1435],{},"向量检索","：找语义相似的切片",[31,1438,1439,1442],{},[15,1440,1441],{},"关键词检索（BM25）","：找精确匹配关键词的切片",[31,1444,1445,1448],{},[15,1446,1447],{},"重排（Rerank）","：用 bge-reranker 等模型对 Top-20 结果重新打分，取 Top-5",[11,1450,1451],{},"加上 Rerank 后准确率通常能再提升 15-25%，是性价比最高的优化点。",[20,1453,1455],{"id":1454},"五step-4prompt-设计","五、Step 4：Prompt 设计",[11,1457,1458],{},"RAG 的 Prompt 模板看似简单，细节决定效果：",[1460,1461,1466],"pre",{"className":1462,"code":1464,"language":1465},[1463],"language-text","你是企业知识助手。请严格基于以下\"参考资料\"回答用户问题。\n\n要求：\n1. 答案必须来自参考资料，不要编造\n2. 如果资料中没有相关信息，明确说\"知识库中暂无相关内容\"\n3. 回答末尾标注引用的来源文档\n\n参考资料：\n{retrieved_chunks}\n\n用户问题：{question}\n","text",[1293,1467,1464],{"__ignoreMap":495},[11,1469,1470,484],{},[15,1471,1472],{},"反幻觉的三个关键约束",[28,1474,1475,1478,1481],{},[31,1476,1477],{},"明确\"必须基于资料\"",[31,1479,1480],{},"给出\"无答案\"的退出路径",[31,1482,1483],{},"强制引用来源（用户也能验证）",[20,1485,1487],{"id":1486},"六step-5效果评估与迭代","六、Step 5：效果评估与迭代",[11,1489,1490],{},"很多企业上线 RAG 后没有评估机制，导致问题积累、用户流失。建议建立三层评估：",[168,1492,1494],{"id":1493},"_61-离线评估","6.1 离线评估",[11,1496,1497],{},"构建 100-500 条测试问答对，定期跑：",[28,1499,1500,1506,1512],{},[31,1501,1502,1505],{},[15,1503,1504],{},"召回率","：相关切片是否在检索结果 Top-K 中",[31,1507,1508,1511],{},[15,1509,1510],{},"答案准确率","：人工或大模型评分",[31,1513,1514,1517],{},[15,1515,1516],{},"拒答率","：无答案问题是否正确拒答",[168,1519,1521],{"id":1520},"_62-在线监控","6.2 在线监控",[28,1523,1524,1527],{},[31,1525,1526],{},"记录每个问答的：query、检索结果、最终答案、用户反馈（赞/踩）",[31,1528,1529],{},"重点关注被踩的问答，定位是检索失败还是生成失败",[168,1531,1533],{"id":1532},"_63-持续优化循环","6.3 持续优化循环",[11,1535,1536],{},"每周/每月迭代一次：",[28,1538,1539,1542,1545,1548],{},[31,1540,1541],{},"补充缺失文档",[31,1543,1544],{},"调整切片策略",[31,1546,1547],{},"优化 Prompt",[31,1549,1550],{},"升级 Embedding/Rerank 模型",[20,1552,1554],{"id":1553},"七企业-rag-落地的常见误区","七、企业 RAG 落地的常见误区",[408,1556,1557,1563,1569,1575,1581],{},[31,1558,1559,1562],{},[15,1560,1561],{},"以为上线就完事","：RAG 是持续运营产品，不是一次性项目",[31,1564,1565,1568],{},[15,1566,1567],{},"只用单一检索","：纯向量检索准确率上限低",[31,1570,1571,1574],{},[15,1572,1573],{},"忽略权限控制","：财务文档不能让所有员工查到",[31,1576,1577,1580],{},[15,1578,1579],{},"没做引用展示","：用户无法验证答案，信任度低",[31,1582,1583,1586],{},[15,1584,1585],{},"没建反馈闭环","：不知道哪里错、怎么改",[20,1588,1590],{"id":1589},"八仙宫云的企业知识库方案","八、仙宫云的企业知识库方案",[11,1592,1593],{},"仙宫云提供从大模型私有化部署到 RAG 应用的完整服务：",[28,1595,1596,1602,1608,1614],{},[31,1597,1598,1601],{},[15,1599,1600],{},"场景调研","：识别哪些文档值得做、用户高频问题摸底",[31,1603,1604,1607],{},[15,1605,1606],{},"数据治理","：文档清洗、敏感信息脱敏、权限分级",[31,1609,1610,1613],{},[15,1611,1612],{},"技术实施","：私有化部署 + Embedding 模型 + 向量库 + 应用界面",[31,1615,1616,1619],{},[15,1617,1618],{},"持续运营","：评估体系建设、效果迭代、新场景扩展",[11,1621,1622,1624],{},[471,1623,474],{"href":473},"获取企业知识库免费方案评估。",[477,1626],{},[11,1628,1629,484,1631,489,1633],{},[15,1630,483],{},[471,1632,1135],{"href":521},[471,1634,493],{"href":492},{"title":495,"searchDepth":496,"depth":496,"links":1636},[1637,1638,1643,1647,1648,1649,1654,1655],{"id":1189,"depth":496,"text":1190},{"id":1272,"depth":496,"text":1273,"children":1639},[1640,1641,1642],{"id":1279,"depth":503,"text":1280},{"id":1306,"depth":503,"text":1307},{"id":1333,"depth":503,"text":1334},{"id":1340,"depth":496,"text":1341,"children":1644},[1645,1646],{"id":1347,"depth":503,"text":1348},{"id":1371,"depth":503,"text":1372},{"id":1421,"depth":496,"text":1422},{"id":1454,"depth":496,"text":1455},{"id":1486,"depth":496,"text":1487,"children":1650},[1651,1652,1653],{"id":1493,"depth":503,"text":1494},{"id":1520,"depth":503,"text":1521},{"id":1532,"depth":503,"text":1533},{"id":1553,"depth":496,"text":1554},{"id":1589,"depth":496,"text":1590},"AI 应用","2026-04-20","深入讲解企业知识库 RAG（检索增强生成）的落地路径，包含文档预处理、向量化、检索策略、Prompt 设计、效果评估全流程。",{},10,{"title":1177,"description":1658},"blog/enterprise-rag-guide",[1214,672,1664,1665,1666],"向量数据库","大模型应用","智能问答","Y0G6dTIxg0ImOVUAy2MlgEoJR7edaGj3_G8mTRjzN5U",1778126192184]