[{"data":1,"prerenderedAt":293},["ShallowReactive",2],{"docs-doc-\u002Fdocs\u002Fconcepts\u002Fmetrics":3,"docs-live-paths":242},{"id":4,"title":5,"body":6,"description":228,"extension":229,"meta":230,"navigation":237,"path":238,"seo":239,"stem":240,"__hash__":241},"content\u002Fdocs\u002Fconcepts\u002Fmetrics.md","经营指标体系 · 口径字典",{"type":7,"value":8,"toc":217},"minimark",[9,21,25,40,45,49,56,59,81,90,94,101,116,125,128,135,151,159,162,169,172,178,184,190,193],[10,11,12],"blockquote",{},[13,14,15,16,20],"p",{},"本文说明衍数「账目口径一致」「AI 数据解读有据」这两项能力的共同基础：一套",[17,18,19],"strong",{},"口径统一的经营指标体系","。包括它是什么、如何约束 AI、如何沉淀为可带走的企业资产。",[22,23,24],"h2",{"id":24},"一句话定义",[13,26,27,28,31,32,35,36,39],{},"衍数内置一套",[17,29,30],{},"经营指标体系（口径字典）","，作为",[17,33,34],{},"规则层（衍枢）的核心资产","：将企业关键经营词汇——销售额、毛利、客单价、损耗率、渠道利润——分别定义为",[17,37,38],{},"全平台唯一的权威口径","。报表、看板、AI 数字员工引用同一指标时，使用的是同一份定义。",[10,41,42],{},[13,43,44],{},"它不属于界面层，也不属于数据管道，而是「什么是一个对的数」的定义层——界面按它展示、数据按它计算、AI 按它引用。",[22,46,48],{"id":47},"它如何支撑账目口径一致","它如何支撑「账目口径一致」",[13,50,51,52,55],{},"「零售说赚、批发说赚、财务说没赚」的症结，是",[17,53,54],{},"各张表对「赚」的定义不一致","：有的扣运费、有的未扣，有的按开票、有的按回款。",[13,57,58],{},"指标体系通过三条规则消除这种不一致：",[60,61,62,69,75],"ol",{},[63,64,65,68],"li",{},[17,66,67],{},"同一词汇 = 同一数字","：报表、看板、AI 问答中出现的「销售额」，指向同一份定义与同一组数据，不会随展示位置而漂移。",[63,70,71,74],{},[17,72,73],{},"比率按财务逻辑计算","：例如「各门店平均毛利率」，系统按「总毛利 ÷ 总营收」整体计算，而不是先算单店再平均——计算结果与财务部门的口径一致。",[63,76,77,80],{},[17,78,79],{},"枚举状态有统一词典","：订单状态、操作类型各有一份权威词典，避免在不同系统中复制粘贴导致漂移。",[10,82,83],{},[13,84,85,86,89],{},"效果：",[17,87,88],{},"报表中的「销售额」「毛利」，与 AI 数据解读、财务核算引用的是同一份定义。"," 这是「账目口径一致」的技术基础。",[22,91,93],{"id":92},"它如何约束-ai-的数据解读","它如何约束 AI 的数据解读",[13,95,96,97,100],{},"通用模型具备通用知识，却不了解",[17,98,99],{},"特定企业的口径","——例如「销售额」是否包含取消订单、「毛利」是否分摊损耗。若 AI 按通用做法计算企业财务数据，即会产生偏离实际的结论。",[13,102,103,104,107,108,111,112,115],{},"衍数将指标体系作为 AI 的",[17,105,106],{},"企业口径依据","：AI 解读数据时",[17,109,110],{},"引用指标字典的权威定义","，回答中的每个数字指向定义与来源。它表述的「上周毛利下降」基于",[17,113,114],{},"企业内部口径、取自企业数据","计算，并可下钻验证。",[10,117,118],{},[13,119,120,121,124],{},"换言之：",[17,122,123],{},"AI 不是套用通用知识推测企业经营，而是按企业定义的口径、基于企业数据计算。"," 这正是基于企业口径的数据解读，与通用大模型随性作答的本质区别。",[22,126,127],{"id":127},"它如何沉淀为数据资产",[13,129,130,131,134],{},"分散的数据本身不是资产，",[17,132,133],{},"口径一致的指标字典才是","：",[136,137,138,141,148],"ul",{},[63,139,140],{},"报表、驾驶舱、AI 引用同一套口径 → 今天的分析成果明天可复用；",[63,142,143,144,147],{},"指标定义（含公式、口径、适用维度）沉淀在字典中 → 人员变动、新增模块、制作新报表，",[17,145,146],{},"口径不需要重新定义","；",[63,149,150],{},"这套字典是企业经营的表达资产，随系统归属于企业，可随项目迁移。",[10,152,153],{},[13,154,155,156],{},"报表可视为「易耗品」，指标体系则是「资产」：报表生成后即可归档，指标则随使用持续积累价值。",[17,157,158],{},"人员会变动、系统会更换，沉淀在衍数中的指标字典，是可随企业迁移的核心资产。",[22,160,161],{"id":161},"平台已预置行业常用指标",[13,163,164,165,168],{},"从零开始时，企业",[17,166,167],{},"无需自行设计一套口径","——衍数已预置行业常用指标（销售额 \u002F 订单量 \u002F 毛利 \u002F 库存 \u002F 损耗 \u002F 渠道利润等，按业务域组织），选择模板即自带。企业要做的是在预置基础上按自身业务调整或补充，而非从零定义。",[22,170,171],{"id":171},"常见疑问",[13,173,174,177],{},[17,175,176],{},"指标体系和「报表」有何区别？","\n报表是「指标 × 维度」的一次查询配置（生成后即可归档）；指标体系是这些指标的定义资产（长期复用）。报表引用字典中的指标，不重复定义口径——这是全平台口径不分裂的原因。",[13,179,180,183],{},[17,181,182],{},"能定义自己的指标吗？","\n可以。平台支持在预置指标之上新增自定义指标（含公式与口径），纳入字典统一管理。",[13,185,186,189],{},[17,187,188],{},"AI 给出的数字能否验证？","\n可以。AI 数据解读引用字典口径并指向来源，关键数字可下钻至明细——并非不可核查的结论。",[22,191,192],{"id":192},"相关阅读",[136,194,195,203,210],{},[63,196,197,198],{},"想了解它在平台三层中的位置 → ",[199,200,202],"a",{"href":201},"\u002Fdocs\u002Fintro\u002Fframeworks","平台架构：衍景 · 衍枢 · 衍流 + AI",[63,204,205,206],{},"想理解「账目口径一致」的完整逻辑 → ",[199,207,209],{"href":208},"\u002Fdocs\u002Fintro\u002Fvalue","衍数能解决什么问题",[63,211,212,213],{},"想配置引用指标的分析 → ",[199,214,216],{"href":215},"\u002Fdocs\u002Fguide\u002Fcrud","使用指南 · 配置通用管理列表",{"title":218,"searchDepth":219,"depth":219,"links":220},"",2,[221,222,223,224,225,226,227],{"id":24,"depth":219,"text":24},{"id":47,"depth":219,"text":48},{"id":92,"depth":219,"text":93},{"id":127,"depth":219,"text":127},{"id":161,"depth":219,"text":161},{"id":171,"depth":219,"text":171},{"id":192,"depth":219,"text":192},"同一业务词汇在各处为何是同一个数字、AI 数据解读为何不随意——指标字典、口径权威与可持续沉淀的数据资产。","md",{"audience":231,"type":232,"section":233,"pr_order":234,"role":235,"duration":236},"public","concept","核心概念",5,"老板 \u002F 实施搭建者","约 5 分钟",true,"\u002Fdocs\u002Fconcepts\u002Fmetrics",{"title":5,"description":228},"docs\u002Fconcepts\u002Fmetrics","iRZZdJxmJ_l-kFE_K6qqIjUjJUytA3_fK_BQbyNhlcM",[243,245,247,249,251,252,254,256,258,260,262,264,265,267,269,270,272,273,275,277,279,281,283,285,287,289,291],{"path":244},"\u002Fdocs\u002Fconcepts\u002Fai",{"path":246},"\u002Fdocs\u002Fconcepts\u002Fai-team",{"path":248},"\u002Fdocs\u002Fconcepts\u002Fcore",{"path":250},"\u002Fdocs\u002Fconcepts\u002Fflux",{"path":238},{"path":253},"\u002Fdocs\u002Fconcepts\u002Fview",{"path":255},"\u002Fdocs\u002Fdemo-center",{"path":257},"\u002Fdocs\u002Fdeploy\u002Foverview",{"path":259},"\u002Fdocs\u002Ffaq",{"path":261},"\u002Fdocs\u002Fglossary",{"path":263},"\u002Fdocs\u002Fguide\u002Fai-kb",{"path":215},{"path":266},"\u002Fdocs\u002Fguide\u002Fdb-connect",{"path":268},"\u002Fdocs\u002Fguide\u002Fmodel-gen",{"path":201},{"path":271},"\u002Fdocs\u002Fintro\u002Foverview",{"path":208},{"path":274},"\u002Fdocs\u002Fintro\u002Fwhy",{"path":276},"\u002Fdocs\u002Fmechanism\u002Fai-employee-task",{"path":278},"\u002Fdocs\u002Fmechanism\u002Fdata-flux",{"path":280},"\u002Fdocs\u002Fmechanism\u002Fmetrics-contract",{"path":282},"\u002Fdocs\u002Fmechanism\u002Fpermission",{"path":284},"\u002Fdocs\u002Fmechanism\u002Fpublish",{"path":286},"\u002Fdocs\u002Fquickstart\u002Fclone-template",{"path":288},"\u002Fdocs\u002Fquickstart\u002Fdemo-30s",{"path":290},"\u002Fdocs\u002Fquickstart\u002Ffive-minutes",{"path":292},"\u002Fdocs\u002Fsystem\u002Foverview",1788586879702]