<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:media="http://search.yahoo.com/mrss/" version="2.0"><channel><title>架构落地记</title><link>https://eaconsulting.cc/</link><atom:link href="https://eaconsulting.cc/feed.xml" rel="self" type="application/rss+xml"/><description>企业架构：从蓝图到能用的实践笔记</description><generator>Halo v2.26.1</generator><language>zh-cn</language><lastBuildDate>Thu, 10 Sep 2026 10:28:30 GMT</lastBuildDate><item><title><![CDATA[能力地图不是部门墙的翻版：拆能力最容易犯的四个错]]></title><link>https://eaconsulting.cc/archives/capability-map-four-mistakes</link><description><![CDATA[<img src="https://eaconsulting.cc/plugins/feed/assets/telemetry.gif?title=%E8%83%BD%E5%8A%9B%E5%9C%B0%E5%9B%BE%E4%B8%8D%E6%98%AF%E9%83%A8%E9%97%A8%E5%A2%99%E7%9A%84%E7%BF%BB%E7%89%88%EF%BC%9A%E6%8B%86%E8%83%BD%E5%8A%9B%E6%9C%80%E5%AE%B9%E6%98%93%E7%8A%AF%E7%9A%84%E5%9B%9B%E4%B8%AA%E9%94%99&amp;url=/archives/capability-map-four-mistakes" width="1" height="1" alt="" style="opacity:0;">能力地图是企业架构里「交付率最高、使用率最低」的产物。失效的原因通常不在方法论，而在拆分的第一步就走偏了：按部门拆、按系统拆、颗粒度不一致，以及只拆不用。]]></description><guid isPermaLink="false">/archives/capability-map-four-mistakes</guid><dc:creator>架构落地记</dc:creator><category>业务架构</category><pubDate>Thu, 10 Sep 2026 09:20:28 GMT</pubDate></item><item><title><![CDATA[架构图画了三个月，业务方还是看不懂：问题不在画工]]></title><link>https://eaconsulting.cc/archives/architecture-diagram-audience</link><description><![CDATA[<img src="https://eaconsulting.cc/plugins/feed/assets/telemetry.gif?title=%E6%9E%B6%E6%9E%84%E5%9B%BE%E7%94%BB%E4%BA%86%E4%B8%89%E4%B8%AA%E6%9C%88%EF%BC%8C%E4%B8%9A%E5%8A%A1%E6%96%B9%E8%BF%98%E6%98%AF%E7%9C%8B%E4%B8%8D%E6%87%82%EF%BC%9A%E9%97%AE%E9%A2%98%E4%B8%8D%E5%9C%A8%E7%94%BB%E5%B7%A5&amp;url=/archives/architecture-diagram-audience" width="1" height="1" alt="" style="opacity:0;">评审会上业务方看了三分钟，问「所以这个跟我们有什么关系」。常见反应是把图画得更细更全，但问题几乎从来不在画工——而在于这张图从一开始就没确定读者是谁。]]></description><guid isPermaLink="false">/archives/architecture-diagram-audience</guid><dc:creator>架构落地记</dc:creator><category>落地复盘</category><pubDate>Thu, 10 Sep 2026 09:20:28 GMT</pubDate></item><item><title><![CDATA[什么是人工智能原生架构？它与“系统接入大模型”有何不同？]]></title><link>https://eaconsulting.cc/archives/what-is-ai-native-architecture</link><description><![CDATA[<img src="https://eaconsulting.cc/plugins/feed/assets/telemetry.gif?title=%E4%BB%80%E4%B9%88%E6%98%AF%E4%BA%BA%E5%B7%A5%E6%99%BA%E8%83%BD%E5%8E%9F%E7%94%9F%E6%9E%B6%E6%9E%84%EF%BC%9F%E5%AE%83%E4%B8%8E%E2%80%9C%E7%B3%BB%E7%BB%9F%E6%8E%A5%E5%85%A5%E5%A4%A7%E6%A8%A1%E5%9E%8B%E2%80%9D%E6%9C%89%E4%BD%95%E4%B8%8D%E5%90%8C%EF%BC%9F&amp;url=/archives/what-is-ai-native-architecture" width="1" height="1" alt="" style="opacity:0;">接入大模型可以增加一个智能功能，人工智能原生架构则从任务、数据、交互和反馈机制开始重新设计系统。 一、两种建设思路的起点不同 系统接入大模型通常从既有功能出发，例如在知识库旁增加问答入口，或在流程中增加文本生成。系统主流程和数据结构基本不变。 人工智能原生架构则从用户目标和任务闭环出]]></description><guid isPermaLink="false">/archives/what-is-ai-native-architecture</guid><dc:creator>架构落地记</dc:creator><enclosure url="https://eaconsulting.cc/apis/api.storage.halo.run/v1alpha1/thumbnails/-/via-uri?uri=%2Fupload%2F97115722-6ade-48c6-9051-4fbf7c265504.png&amp;size=m" type="image/jpeg" length="754791"/><category>AI 与架构</category><pubDate>Wed, 29 Apr 2026 09:23:00 GMT</pubDate></item><item><title><![CDATA[企业引入大模型时，架构治理需要关注哪些风险？]]></title><link>https://eaconsulting.cc/archives/enterprise-ai-architecture-governance-risks</link><description><![CDATA[<img src="https://eaconsulting.cc/plugins/feed/assets/telemetry.gif?title=%E4%BC%81%E4%B8%9A%E5%BC%95%E5%85%A5%E5%A4%A7%E6%A8%A1%E5%9E%8B%E6%97%B6%EF%BC%8C%E6%9E%B6%E6%9E%84%E6%B2%BB%E7%90%86%E9%9C%80%E8%A6%81%E5%85%B3%E6%B3%A8%E5%93%AA%E4%BA%9B%E9%A3%8E%E9%99%A9%EF%BC%9F&amp;url=/archives/enterprise-ai-architecture-governance-risks" width="1" height="1" alt="" style="opacity:0;">大模型风险不是上线前做一次安全检查就能解决的问题，而需要贯穿数据、模型、知识、工具和运营全过程。 一、先区分内容风险与行动风险 回答不准确属于内容风险，错误调用系统则可能转化为行动风险。企业应根据人工智能能否接触敏感信息、影响业务决策或执行操作，对场景进行风险分级。]]></description><guid isPermaLink="false">/archives/enterprise-ai-architecture-governance-risks</guid><dc:creator>架构落地记</dc:creator><enclosure url="https://eaconsulting.cc/apis/api.storage.halo.run/v1alpha1/thumbnails/-/via-uri?uri=%2Fupload%2F77607517-5ccb-4065-8c9b-b5b6eef6e22b.png&amp;size=m" type="image/jpeg" length="799772"/><category>架构治理</category><pubDate>Tue, 21 Apr 2026 09:34:00 GMT</pubDate></item><item><title><![CDATA[人工智能时代，企业数据架构为什么需要重新设计]]></title><link>https://eaconsulting.cc/archives/enterprise-data-architecture-in-ai-era</link><description><![CDATA[<img src="https://eaconsulting.cc/plugins/feed/assets/telemetry.gif?title=%E4%BA%BA%E5%B7%A5%E6%99%BA%E8%83%BD%E6%97%B6%E4%BB%A3%EF%BC%8C%E4%BC%81%E4%B8%9A%E6%95%B0%E6%8D%AE%E6%9E%B6%E6%9E%84%E4%B8%BA%E4%BB%80%E4%B9%88%E9%9C%80%E8%A6%81%E9%87%8D%E6%96%B0%E8%AE%BE%E8%AE%A1&amp;url=/archives/enterprise-data-architecture-in-ai-era" width="1" height="1" alt="" style="opacity:0;">人工智能应用需要的不只是更多数据，还需要把结构化数据、文档知识、实时上下文和反馈记录组织成可持续的数据供给体系。 传统数据架构主要围绕业务系统、数据仓库和分析报表展开。数据经过采集、清洗和汇总后，为统计分析与经营管理提供支持。人工智能进入企业应用后，这套架构仍然重要，但已经不能覆盖全部数据需求。]]></description><guid isPermaLink="false">/archives/enterprise-data-architecture-in-ai-era</guid><dc:creator>架构落地记</dc:creator><enclosure url="https://eaconsulting.cc/apis/api.storage.halo.run/v1alpha1/thumbnails/-/via-uri?uri=%2Fupload%2F4b86ee7c-9534-4226-b54b-69d750d1d5b2.png&amp;size=m" type="image/jpeg" length="800161"/><category>应用与数据</category><pubDate>Sat, 7 Mar 2026 09:36:00 GMT</pubDate></item><item><title><![CDATA[人工智能进入企业架构后，真正改变了什么？]]></title><link>https://eaconsulting.cc/archives/ai-impact-on-enterprise-architecture</link><description><![CDATA[<img src="https://eaconsulting.cc/plugins/feed/assets/telemetry.gif?title=%E4%BA%BA%E5%B7%A5%E6%99%BA%E8%83%BD%E8%BF%9B%E5%85%A5%E4%BC%81%E4%B8%9A%E6%9E%B6%E6%9E%84%E5%90%8E%EF%BC%8C%E7%9C%9F%E6%AD%A3%E6%94%B9%E5%8F%98%E4%BA%86%E4%BB%80%E4%B9%88%EF%BC%9F&amp;url=/archives/ai-impact-on-enterprise-architecture" width="1" height="1" alt="" style="opacity:0;">人工智能不只是新增一个技术组件，它正在改变业务流程的设计方式、应用的交互边界以及数据的使用逻辑。 一、从辅助工具到企业能力 早期人工智能应用多以识别、分类和预测等单点模型出现，通常嵌入某个固定流程。生成式人工智能和智能体出现后，人工智能开始处理语言、知识和跨系统任务，逐渐成为可被多个应用调用的共享能]]></description><guid isPermaLink="false">/archives/ai-impact-on-enterprise-architecture</guid><dc:creator>架构落地记</dc:creator><enclosure url="https://eaconsulting.cc/apis/api.storage.halo.run/v1alpha1/thumbnails/-/via-uri?uri=%2Fupload%2Fcf3e83c6-e39e-449c-a7e6-0b7e11d6c675.png&amp;size=m" type="image/jpeg" length="864516"/><category>AI 与架构</category><pubDate>Sat, 7 Mar 2026 08:50:00 GMT</pubDate></item><item><title><![CDATA[企业架构究竟解决什么问题？]]></title><link>https://eaconsulting.cc/archives/enterprise-architecture-problems</link><description><![CDATA[<img src="https://eaconsulting.cc/plugins/feed/assets/telemetry.gif?title=%E4%BC%81%E4%B8%9A%E6%9E%B6%E6%9E%84%E7%A9%B6%E7%AB%9F%E8%A7%A3%E5%86%B3%E4%BB%80%E4%B9%88%E9%97%AE%E9%A2%98%EF%BC%9F&amp;url=/archives/enterprise-architecture-problems" width="1" height="1" alt="" style="opacity:0;">｜企业架构的真正价值不在于画出多少张图，而在于帮助企业在复杂变化中保持战略、业务与技术的一致性。 不少人第一次接触企业架构时，会把它理解成一套复杂的架构图：业务架构描述企业做什么，应用架构列出有哪些系统，数据架构梳理数据如何流转，技术架构则展示服务器、网络和技术平台。]]></description><guid isPermaLink="false">/archives/enterprise-architecture-problems</guid><dc:creator>架构落地记</dc:creator><enclosure url="https://eaconsulting.cc/apis/api.storage.halo.run/v1alpha1/thumbnails/-/via-uri?uri=%2Fupload%2Fwide_clean_slide_hero_banner_style_image_on_a_whit.png&amp;size=m" type="image/jpeg" length="524651"/><category>业务架构</category><pubDate>Tue, 10 Feb 2026 06:01:00 GMT</pubDate></item><item><title><![CDATA[从业务到技术：读懂企业架构的四个核心层次]]></title><link>https://eaconsulting.cc/archives/four-layers-of-enterprise-architecture</link><description><![CDATA[<img src="https://eaconsulting.cc/plugins/feed/assets/telemetry.gif?title=%E4%BB%8E%E4%B8%9A%E5%8A%A1%E5%88%B0%E6%8A%80%E6%9C%AF%EF%BC%9A%E8%AF%BB%E6%87%82%E4%BC%81%E4%B8%9A%E6%9E%B6%E6%9E%84%E7%9A%84%E5%9B%9B%E4%B8%AA%E6%A0%B8%E5%BF%83%E5%B1%82%E6%AC%A1&amp;url=/archives/four-layers-of-enterprise-architecture" width="1" height="1" alt="" style="opacity:0;">｜ 业务架构、应用架构、数据架构和技术架构并不是四套彼此独立的图纸，而是观察同一家企业的四个相互关联的视角。 谈到企业架构，人们经常会听到业务架构、应用架构、数据架构和技术架构这四个概念。它们看起来边界清晰：业务部门谈业务，研发团队管应用，数据团队建平台，基础设施团队负责技术底座。但在真实的企业建设]]></description><guid isPermaLink="false">/archives/four-layers-of-enterprise-architecture</guid><dc:creator>架构落地记</dc:creator><enclosure url="https://eaconsulting.cc/apis/api.storage.halo.run/v1alpha1/thumbnails/-/via-uri?uri=%2Fupload%2F%25E4%25BB%258E%25E4%25B8%259A%25E5%258A%25A1%25E5%2588%25B0%25E6%258A%2580%25E6%259C%25AF%25EF%25BC%259A%25E4%25BC%2581%25E4%25B8%259A%25E6%259E%25B6%25E6%259E%2584%25E5%259B%259B%25E5%25B1%2582%25E8%25A7%25A3%25E6%259E%2590.png&amp;size=m" type="image/jpeg" length="379036"/><category>业务架构</category><pubDate>Sat, 17 Jan 2026 06:32:00 GMT</pubDate></item><item><title><![CDATA[人工智能能力如何嵌入企业应用体系]]></title><link>https://eaconsulting.cc/archives/integrating-ai-into-enterprise-applications</link><description><![CDATA[<img src="https://eaconsulting.cc/plugins/feed/assets/telemetry.gif?title=%E4%BA%BA%E5%B7%A5%E6%99%BA%E8%83%BD%E8%83%BD%E5%8A%9B%E5%A6%82%E4%BD%95%E5%B5%8C%E5%85%A5%E4%BC%81%E4%B8%9A%E5%BA%94%E7%94%A8%E4%BD%93%E7%B3%BB&amp;url=/archives/integrating-ai-into-enterprise-applications" width="1" height="1" alt="" style="opacity:0;">企业引入人工智能的难点往往不是模型能否回答，而是它如何获得合适的信息、调用正确的系统并在权限范围内完成任务。 一、先选择嵌入模式 常见模式包括独立人工智能应用、嵌入式助手、共享人工智能能力平台和任务型智能体。独立应用上线较快，嵌入式助手更贴近工作场景，共享平台有利于复用，智能体则能够编排多个步骤。]]></description><guid isPermaLink="false">/archives/integrating-ai-into-enterprise-applications</guid><dc:creator>架构落地记</dc:creator><category>应用与数据</category><pubDate>Fri, 5 Sep 2025 09:26:00 GMT</pubDate></item><item><title><![CDATA[人工智能如何参与企业架构设计与运营]]></title><link>https://eaconsulting.cc/archives/ai-for-enterprise-architecture-operations</link><description><![CDATA[<img src="https://eaconsulting.cc/plugins/feed/assets/telemetry.gif?title=%E4%BA%BA%E5%B7%A5%E6%99%BA%E8%83%BD%E5%A6%82%E4%BD%95%E5%8F%82%E4%B8%8E%E4%BC%81%E4%B8%9A%E6%9E%B6%E6%9E%84%E8%AE%BE%E8%AE%A1%E4%B8%8E%E8%BF%90%E8%90%A5&amp;url=/archives/ai-for-enterprise-architecture-operations" width="1" height="1" alt="" style="opacity:0;">人工智能对企业架构最现实的价值，不是替代架构师，而是提高资料理解、关系分析、影响判断和持续运营的效率。 企业架构工作有一个长期矛盾：架构师需要理解战略、流程、系统、数据和技术之间的大量关系，但企业信息分散在制度文件、项目材料、系统台账、接口文档和人员经验中。当信息规模持续扩大，仅靠人工阅读和维护，很]]></description><guid isPermaLink="false">/archives/ai-for-enterprise-architecture-operations</guid><dc:creator>架构落地记</dc:creator><category>AI 与架构</category><pubDate>Mon, 18 Aug 2025 09:30:00 GMT</pubDate></item><item><title><![CDATA[企业架构建设为什么容易停留在“画图”阶段？]]></title><link>https://eaconsulting.cc/archives/beyond-enterprise-architecture-diagrams</link><description><![CDATA[<img src="https://eaconsulting.cc/plugins/feed/assets/telemetry.gif?title=%E4%BC%81%E4%B8%9A%E6%9E%B6%E6%9E%84%E5%BB%BA%E8%AE%BE%E4%B8%BA%E4%BB%80%E4%B9%88%E5%AE%B9%E6%98%93%E5%81%9C%E7%95%99%E5%9C%A8%E2%80%9C%E7%94%BB%E5%9B%BE%E2%80%9D%E9%98%B6%E6%AE%B5%EF%BC%9F&amp;url=/archives/beyond-enterprise-architecture-diagrams" width="1" height="1" alt="" style="opacity:0;">架构图只是表达工具。企业架构能否产生价值，取决于它是否进入投资、立项、设计、交付和运营的真实决策过程。 一、问题往往不在图，而在图之后 企业架构项目通常能够形成较为完整的现状图、目标图和演进路线，但项目结束后，成果却可能很少被业务部]]></description><guid isPermaLink="false">/archives/beyond-enterprise-architecture-diagrams</guid><dc:creator>架构落地记</dc:creator><enclosure url="https://eaconsulting.cc/apis/api.storage.halo.run/v1alpha1/thumbnails/-/via-uri?uri=%2Fupload%2F299ad651-6bb0-4fbc-85d2-98121c4a52d2.png&amp;size=m" type="image/jpeg" length="566330"/><category>落地复盘</category><pubDate>Tue, 22 Jul 2025 06:58:00 GMT</pubDate></item><item><title><![CDATA[企业架构建设的完整路径：从现状诊断到持续治理]]></title><link>https://eaconsulting.cc/archives/enterprise-architecture-development-roadmap</link><description><![CDATA[<img src="https://eaconsulting.cc/plugins/feed/assets/telemetry.gif?title=%E4%BC%81%E4%B8%9A%E6%9E%B6%E6%9E%84%E5%BB%BA%E8%AE%BE%E7%9A%84%E5%AE%8C%E6%95%B4%E8%B7%AF%E5%BE%84%EF%BC%9A%E4%BB%8E%E7%8E%B0%E7%8A%B6%E8%AF%8A%E6%96%AD%E5%88%B0%E6%8C%81%E7%BB%AD%E6%B2%BB%E7%90%86&amp;url=/archives/enterprise-architecture-development-roadmap" width="1" height="1" alt="" style="opacity:0;">企业架构不是一次性完成的顶层设计，而是一条从识别问题、形成目标、安排转型到持续治理的完整工作链路。 不少企业启动架构建设时，第一反应是先画一张总体架构图。图画出来以后，才发现真正困难的问题仍然没有答案：现有系统为什么如此复杂，哪些能力应该优先补齐，多个项目之间如何安排先后顺序，目标架构又由谁推动落地]]></description><guid isPermaLink="false">/archives/enterprise-architecture-development-roadmap</guid><dc:creator>架构落地记</dc:creator><enclosure url="https://eaconsulting.cc/apis/api.storage.halo.run/v1alpha1/thumbnails/-/via-uri?uri=%2Fupload%2F87b78e9a-b0dd-452f-a220-aada75d97f62.png&amp;size=m" type="image/jpeg" length="1006759"/><category>架构治理</category><pubDate>Sun, 13 Apr 2025 08:24:00 GMT</pubDate></item><item><title><![CDATA[企业架构如何支撑投资决策与项目组合管理]]></title><link>https://eaconsulting.cc/archives/enterprise-architecture-for-investment-decisions</link><description><![CDATA[<img src="https://eaconsulting.cc/plugins/feed/assets/telemetry.gif?title=%E4%BC%81%E4%B8%9A%E6%9E%B6%E6%9E%84%E5%A6%82%E4%BD%95%E6%94%AF%E6%92%91%E6%8A%95%E8%B5%84%E5%86%B3%E7%AD%96%E4%B8%8E%E9%A1%B9%E7%9B%AE%E7%BB%84%E5%90%88%E7%AE%A1%E7%90%86&amp;url=/archives/enterprise-architecture-for-investment-decisions" width="1" height="1" alt="" style="opacity:0;">企业架构只有进入投资决策和项目组合管理，才能把战略目标、业务能力与建设资源真正连接起来。 企业每年都会提出大量数字化建设需求，但预算、人员和实施能力始终有限。真正困难的往往不是判断某个项目是否有价值，而是在多个看起来都有价值的项目之间作出取舍。 如果项目评审主要关注单项需求是否合理、方案是否可行，就]]></description><guid isPermaLink="false">/archives/enterprise-architecture-for-investment-decisions</guid><dc:creator>架构落地记</dc:creator><category>架构治理</category><pubDate>Sat, 15 Jun 2024 08:43:00 GMT</pubDate></item><item><title><![CDATA[数字化转型不是系统建设：如何形成可持续的企业能力]]></title><link>https://eaconsulting.cc/archives/building-sustainable-digital-capabilities</link><description><![CDATA[<img src="https://eaconsulting.cc/plugins/feed/assets/telemetry.gif?title=%E6%95%B0%E5%AD%97%E5%8C%96%E8%BD%AC%E5%9E%8B%E4%B8%8D%E6%98%AF%E7%B3%BB%E7%BB%9F%E5%BB%BA%E8%AE%BE%EF%BC%9A%E5%A6%82%E4%BD%95%E5%BD%A2%E6%88%90%E5%8F%AF%E6%8C%81%E7%BB%AD%E7%9A%84%E4%BC%81%E4%B8%9A%E8%83%BD%E5%8A%9B&amp;url=/archives/building-sustainable-digital-capabilities" width="1" height="1" alt="" style="opacity:0;">系统上线可以有明确的完成日期，数字化能力却需要在业务运行中持续形成、检验和调整。 一、为什么“上线成功”不等于转型完成 企业容易把数字化转型拆解成若干系统建设项目，并用功能完成率、上线时间和预算执行情况衡量进展。这些指标适合管理项目，却不足以判断企业能力是否真正改变。]]></description><guid isPermaLink="false">/archives/building-sustainable-digital-capabilities</guid><dc:creator>架构落地记</dc:creator><enclosure url="https://eaconsulting.cc/apis/api.storage.halo.run/v1alpha1/thumbnails/-/via-uri?uri=%2Fupload%2F334c183b-f400-4374-9fa4-2a30d0fe9779.png&amp;size=m" type="image/jpeg" length="748489"/><category>业务架构</category><pubDate>Fri, 15 Mar 2024 08:34:00 GMT</pubDate></item></channel></rss>