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