[{"data":1,"prerenderedAt":419},["ShallowReactive",2],{"site-info":3,"news-list":34},{"name":4,"nameEn":5,"legalNameEn":6,"shortName":7,"domain":8,"url":9,"slogan":10,"sloganEn":11,"description":12,"descriptionEn":13,"founded":14,"year":15,"icp":16,"contact":19,"social":29},"广西耗以数载科技有限公司","SOEONS","Guangxi Haoyi Shuzai Technology Co., Ltd.","耗以数载","soeons.com","https:\u002F\u002Fsoeons.com","锲而不舍 · 耗以数载","Built over years, not over quarters.","广西耗以数载科技有限公司（SOEONS）专注软件定制开发与数字化服务，为中小企业提供数字化咨询、系统定制开发、系统集成部署与长期运维支持，立足广西，面向东盟与西南市场。","SOEONS (Guangxi Haoyi Shuzai Technology Co., Ltd.) specializes in custom software development and digital transformation services. We provide small and midsize businesses with digital consulting, custom software development, systems integration and deployment, and long-term operations support—rooted in Guangxi and serving the southwest China and ASEAN markets.",2019,2026,{"text":17,"url":18},"桂ICP备2024029466号-2","https:\u002F\u002Fbeian.miit.gov.cn",{"phone":20,"mobile":21,"email":22,"address":23,"addressEn":24,"workingHours":25,"workingHoursEn":26,"mapNote":27,"mapNoteEn":28},"0775-XXXXXXX","1XX-XXXX-XXXX","chat@soeons.com","广西壮族自治区玉林市XXXX（待补充）","Yulin, Guangxi, China","周一至周五 09:00 – 18:00","Monday–Friday, 9:00 AM – 6:00 PM (CST)","玉林市","Yulin, Guangxi",{"wechat":30,"linkedin":33},{"label":31,"handle":32},"微信公众号","soeons","https:\u002F\u002Fwww.linkedin.com\u002Fcompany\u002Fsoeons",[35,107,193,257,308,363],{"slug":36,"title":37,"category":40,"date":41,"excerpt":42,"author":45,"body":47},"soeons-2026-mid-review",{"zh":38,"en":39},"耗以数载：SOEONS 七年交付复盘","Seven Years, Measured in Sustained Effort: A Look Back at SOEONS Deliveries","company","2026-09-18",{"zh":43,"en":44},"从 2019 年三个人到今天六十余人的技术团队，我们把过去七年交付的一百二十余个项目摊开来看，想弄清楚一件事：什么样的软件，才能真正陪企业走得更远。","From three people in 2019 to a technical team of more than sixty today, we laid out the 120-plus projects we have delivered over the past seven years to answer one question: what kind of software can truly grow with a business over the long run?",{"zh":46,"en":46},"oaken",[48,53,57,63,67,82,90,95,99,103],{"type":49,"text":50},"paragraph",{"zh":51,"en":52},"七年前我们在玉林租下第一间办公室的时候，接的第一个项目是一套进销存系统。客户是做标准件的小型工厂，报价三万八，工期六周。系统上线那天，仓库的老会计问我们：这个做完以后，还用Excel吗？我们说不用了。他当时没说话，三个月后主动打电话来说，仓库现在每天少加一次班。","When we rented our first office in Yulin seven years ago, our first project was an inventory management system. The client was a small factory making standard parts. The quote was ¥38,000, the schedule six weeks. On the day the system went live, the veteran accountant in the warehouse asked us: “Now that this is done, will we still need Excel?” We said no. He said nothing at the time, but three months later he called us himself to say the warehouse was now working one fewer overtime shift every day.",{"type":49,"text":54},{"zh":55,"en":56},"这件事后来变成了我们做事的起点。软件的价值不在于交付时那几屏漂亮的界面，而在于它接手了哪些原本压在具体某个人身上的重复劳动。今天回头看，一百二十余个项目里，活下来的系统有一个共同的特征：它们在交付时都不是最复杂的那个。","That moment became the starting point for how we work. The value of software lies not in the few polished screens at handover, but in the repetitive work it takes off the shoulders of specific people. Looking back today, the systems that have survived among those 120-plus projects share one trait: at the time of delivery, they were never the most complex option.",{"type":58,"text":59,"id":62},"heading",{"zh":60,"en":61},"活下来的系统长什么样","What Surviving Systems Have in Common","survivors",{"type":49,"text":64},{"zh":65,"en":66},"我们复盘后发现，被客户长期使用的系统有几个共同特征。第一，业务流程没有为了迁就软件而扭曲，而是软件去适应了真实流程——包括那些看起来很乱的流程。第二，接手了明确重复性工作，而不是提供一堆用不上的报表。第三，系统足够小，小到客户自己人敢改。","Our review found several shared characteristics among the systems clients keep using long term. First, business processes were not bent to fit the software; the software adapted to real workflows, including the messy-looking ones. Second, it took over clearly repetitive work rather than adding a pile of reports nobody used. Third, the system was small enough that the client's own staff felt comfortable making changes to it.",{"type":68,"items":69},"list",[70,73,76,79],{"zh":71,"en":72},"软件适配真实流程，而不是让流程迁就软件","Software adapts to real workflows rather than forcing processes to fit the system",{"zh":74,"en":75},"优先接手明确的重复性劳动，而不是堆砌报表","Take over clearly repetitive work first, instead of piling on reports",{"zh":77,"en":78},"系统规模控制在客户团队敢自己动手改的程度","Keep the system small enough that the client's team dares to modify it themselves",{"zh":80,"en":81},"上线后有人可问、有事可管、有版本可升","After launch, someone to talk to, clear ownership, and a path to upgrade",{"type":83,"text":84,"source":87},"quote",{"zh":85,"en":86},"我们不追求把系统做得复杂，而是追求让系统能被用起来、被用下去。","We don't set out to make systems complex. We set out to make them usable—and used for the long haul.",{"zh":88,"en":89},"oaken · 创始人","oaken, Founder",{"type":58,"text":91,"id":94},{"zh":92,"en":93},"我们在做的改变","What We Have Changed","changes",{"type":49,"text":96},{"zh":97,"en":98},"七年间，我们拒绝了相当一部分看起来更赚钱的需求——那些要求在三个月内从零搭建一套完整 ERP 的项目。我们的经验是，在业务本身还没有跑顺的阶段上一套完整系统，最终往往是系统被闲置。","Over the past seven years, we turned down a fair number of seemingly more profitable opportunities—projects that asked for a complete ERP built from scratch in three months. In our experience, deploying a full system before the business itself has settled into a rhythm usually ends with the system sitting idle.",{"type":49,"text":100},{"zh":101,"en":102},"因此从两年前开始，我们会主动把咨询业务和开发业务分离开来卖：先诊断，再设计，最后才决定要不要做。很多客户在诊断阶段就决定不做了——这对我们是损失，但对他们是节省。","So two years ago, we began selling consulting and development separately: diagnose first, design next, and only then decide whether to build. Many clients decide not to proceed at the diagnosis stage. That costs us revenue, but it saves them money.",{"type":49,"text":104},{"zh":105,"en":106},"接下来的一年，我们会继续把重心放在已经交付客户的系统上：更多的巡检、更快的响应、更小步的迭代。七年不算长，「耗以数载」这件事，我们打算继续做下去。","Over the coming year, we will keep our focus on the systems we have already delivered: more frequent inspections, faster response, and smaller iterations. Seven years is not long, and we intend to keep spending our years on exactly this.",{"slug":108,"title":109,"category":112,"date":113,"excerpt":114,"author":117,"body":120},"sme-digitalization-myths",{"zh":110,"en":111},"中小企业数字化最常踩的五个坑","Five Common Pitfalls in SME Digitalization","insight","2026-08-12",{"zh":115,"en":116},"预算有限、需求模糊、人员流动快——这是中小企业的真实处境，也决定了他们的数字化不能照搬大公司的路径。","Limited budgets, vague requirements, and rapid staff turnover—these are the realities small and midsize businesses face, and they mean SMEs cannot simply copy the paths taken by large corporations.",{"zh":118,"en":119},"李文博","Li Wenbo",[121,125,130,134,138,143,154,159,163,167,172,176,180,185,189],{"type":49,"text":122},{"zh":123,"en":124},"过去两年我们接触了大量中小企业数字化需求，其中相当一部分在启动阶段就出现了偏差。这五个坑几乎覆盖了我们见到的所有失败案例。","Over the past two years we have worked on many digitalization requests from SMEs, and a considerable share went off track right at the start. These five pitfalls account for nearly every failed case we have seen.",{"type":58,"text":126,"id":129},{"zh":127,"en":128},"一、先买系统，后想清楚要解决什么","1. Buying the System Before Defining the Problem","myth-1",{"type":49,"text":131},{"zh":132,"en":133},"最常见的剧本是：听说某个系统不错 → 找供应商报价 → 挑功能最多的那个 → 上线后发现跟自己的业务流程对不上。采购顺序错了，后面所有投入都会打折。","The most common script: hear that a certain system is good → ask vendors for quotes → pick the one with the most features → discover after go-live that it doesn't match your workflows. Get the buying order wrong, and every dollar that follows is discounted.",{"type":49,"text":135},{"zh":136,"en":137},"正确的顺序是反过来的：先找到那个每天都在消耗团队时间的环节，把它量化出来，再去找能解决它的方案。没有第零步，方案对比就只是在比功能表。","The right order is the reverse: first identify the step that drains your team's time every single day, quantify it, and then look for a solution that addresses it. Without that step zero, comparing proposals is just comparing feature lists.",{"type":58,"text":139,"id":142},{"zh":140,"en":141},"二、试图一次性覆盖全部业务","2. Trying to Cover Every Business Process at Once","myth-2",{"type":68,"items":144},[145,148,151],{"zh":146,"en":147},"先打通一个环节，形成闭环，再向两端延伸","Connect one process end to end first, then extend outward in both directions",{"zh":149,"en":150},"宁可做一个用起来的小系统，也不要一个没人敢用的全系统","Better a small system people actually use than a comprehensive one nobody dares to use",{"zh":152,"en":153},"每次扩展都应当由前一阶段的真实使用数据驱动","Every expansion should be driven by real usage data from the previous phase",{"type":58,"text":155,"id":158},{"zh":156,"en":157},"三、把数字化当成一次性项目","3. Treating Digitalization as a One-Off Project","myth-3",{"type":49,"text":160},{"zh":161,"en":162},"系统上线不是终点。我们统计过客户上线后三个月内的活跃度，通常在第二周会有一个明显的下坠——这不是系统不好用，而是没有人负责让它继续好用。","Go-live is not the finish line. When we tracked activity in the first three months after launch, we typically saw a sharp drop in the second week—not because the system was hard to use, but because no one was responsible for keeping it that way.",{"type":49,"text":164},{"zh":165,"en":166},"预算里必须留出运营的部分。这笔钱花的回报率，通常比多开发两个模块高得多。","The budget must include an operating share. That money typically delivers a much higher return than building two more modules.",{"type":58,"text":168,"id":171},{"zh":169,"en":170},"四、忽略数据迁移","4. Overlooking Data Migration","myth-4",{"type":49,"text":173},{"zh":174,"en":175},"历史数据不干净是常态。字段缺失、编码不一致、同一件事在系统里有三种写法。我们见过太多项目在上线前一天卡在数据清洗上，拖期三周。","Dirty historical data is the norm: missing fields, inconsistent codes, the same thing recorded three different ways. We have seen far too many projects stall on data cleansing the day before go-live, pushing the launch back three weeks.",{"type":49,"text":177},{"zh":178,"en":179},"数据迁移应当被当作一个独立的、有专人负责的工作项排进计划，而不是上线前的最后一道工序。","Data migration should be planned as a standalone workstream with a dedicated owner, not treated as the last step before launch.",{"type":58,"text":181,"id":184},{"zh":182,"en":183},"五、选了没有人的供应商","5. Choosing a Vendor Without the People","myth-5",{"type":49,"text":186},{"zh":187,"en":188},"软件公司和软件最大的区别在于：软件公司会在你上线三年后还在。换供应商的成本，远不止数据迁移那几周。","The biggest difference between a software company and software is this: a software company will still be there three years after you go live. The cost of switching vendors goes far beyond the few weeks of data migration.",{"type":49,"text":190},{"zh":191,"en":192},"在签合同前问三个问题：你们交付过什么规模的项目？上线一年后你们还管吗？出了问题谁在第一时间响应？这三个问题的答案，比报价单更能说明未来三年。","Before signing, ask three questions: what scale of project have you delivered? Will you still be supporting us a year after launch? Who responds first when something goes wrong? The answers will tell you more about the next three years than any quote.",{"slug":194,"title":195,"category":198,"date":199,"excerpt":200,"author":203,"body":206},"asean-cross-border-digitalization",{"zh":196,"en":197},"广西区位优势下的跨境数字化：从玉林出发","Cross-Border Digitalization from Guangxi: Starting in Yulin","industry","2026-07-05",{"zh":201,"en":202},"RCEP 生效以来，广西的通道价值被重新定价。我们把过去两年在越南的试点经验整理成三点观察。","Since RCEP took effect, Guangxi’s value as a corridor has been revalued. We distilled two years of pilot experience in Vietnam into three observations.",{"zh":204,"en":205},"韦晓芸","Wei Xiaoyun",[207,211,215,220,224,235,240,244,249,253],{"type":49,"text":208},{"zh":209,"en":210},"2024 年我们接了第一个在越南经营的中资客户。客户总部在玉林，工厂在海防，用的是同一套在国内已经跑顺的 ERP，但越南工厂的工单还停留在纸单上。","In 2024 we took on our first Chinese-owned client operating in Vietnam. The headquarters is in Yulin, the factory in Hai Phong, and the company runs the same ERP that already works well in China—yet work orders at the Vietnam factory were still on paper.",{"type":49,"text":212},{"zh":213,"en":214},"这个项目让我们意识到，跨境数字化的核心问题不是「要不要国际化」，而是「哪些东西必须统一，哪些东西必须分开」。","The project made one thing clear: the core question in cross-border digitalization is not whether to go international, but what must be standardized and what must be kept separate.",{"type":58,"text":216,"id":219},{"zh":217,"en":218},"观察一：主数据要统一，流程要本地化","Observation 1: Standardize Master Data, Localize Processes","obs-1",{"type":49,"text":221},{"zh":222,"en":223},"跨境企业最容易犯的错，是把国内整套系统原样复制一份到海外。结果是编码规则、审批层级、税务口径全部错位。","The most common mistake cross-border companies make is copying the entire domestic system overseas as-is. The result is misaligned coding rules, approval levels, and tax treatments.",{"type":68,"items":225},[226,229,232],{"zh":227,"en":228},"物料编码、客户档案、组织结构保持统一，保证数据可比","Keep material codes, customer records, and organizational structure unified so data stays comparable",{"zh":230,"en":231},"审批流、税务单据、薪酬口径按当地法规与习惯本地化","Localize approval workflows, tax documents, and payroll rules to local regulations and customs",{"zh":233,"en":234},"界面语言、货币、时区在配置层解决，不做代码分支","Handle language, currency, and time zones through configuration, not separate code branches",{"type":58,"text":236,"id":239},{"zh":237,"en":238},"观察二：数据出境要提前设计","Observation 2: Design Cross-Border Data Transfer Upfront","obs-2",{"type":49,"text":241},{"zh":242,"en":243},"我们踩过的坑是：先做了跨境同步，再去补合规。这条路走不通。数据出境的路径、加密方式与审计留痕，必须在架构阶段就确定，而不是上线前找法务补。","The pitfall we ran into: building cross-border syncing first and patching in compliance afterward. That approach doesn't work. Data transfer paths, encryption methods, and audit trails must be decided at the architecture stage, not bolted on by legal before go-live.",{"type":58,"text":245,"id":248},{"zh":246,"en":247},"观察三：跨境系统的可用性标准要更高","Observation 3: Cross-Border Systems Need Higher Availability Standards","obs-3",{"type":49,"text":250},{"zh":251,"en":252},"网络链路不稳定是跨境环境的常态。系统在设计时就要假设「网络会断」，具备本地缓存与断点续传能力，否则每一次跨国会议都会变成一次故障复盘。","Unstable network links are a fact of life in cross-border operations. Systems must be designed on the assumption that the network will drop, with local caching and resumable transfers—otherwise every cross-border meeting turns into an incident review.",{"type":49,"text":254},{"zh":255,"en":256},"广西的区位让这件事在物理上更近了一层。对我们来说，这意味着同一个项目团队可以在一天之内同时出现在玉林和越南的现场——这在几年前是不可想象的。","Guangxi’s location brings this physically closer. For us, it means the same project team can be on site in Yulin and in Vietnam on the same day—something that was unthinkable just a few years ago.",{"slug":258,"title":259,"category":262,"date":263,"excerpt":264,"author":267,"body":270},"soeons-new-office-nanning",{"zh":260,"en":261},"SOEONS 玉林研发中心正式启用","SOEONS Yulin R&D Center Officially Opens","announcement","2026-06-20",{"zh":265,"en":266},"公司新办公场地在玉林市启用，可容纳 80 人同时办公，并新增独立的产品实验室与演示中心。","Our new office has opened in Yulin, with space for 80 people, plus a dedicated product lab and demonstration center.",{"zh":268,"en":269},"公司行政","SOEONS Administration",[271,275,279,284,288,292,297],{"type":49,"text":272},{"zh":273,"en":274},"我们搬进了新办公室。新的场地在玉林市，面积约 1200 平方米，可以容纳 80 名同事同时办公。","We have moved into a new office in Yulin. The space covers about 1,200 square meters and can accommodate 80 colleagues at the same time.",{"type":49,"text":276},{"zh":277,"en":278},"这次选址我们特意留出了两个空间：一个是产品实验室，用于客户现场原型验证和真实场景测试；另一个是演示中心，客户可以直接在这里试用我们正在做的系统，而不用看 PPT。","When choosing the space, we deliberately set aside two areas: a product lab for on-site prototype validation and real-world scenario testing, and a demonstration center where clients can try the systems we are building directly, rather than sitting through a slide deck.",{"type":58,"text":280,"id":283},{"zh":281,"en":282},"我们为什么坚持要一间演示室","Why We Insisted on a Demonstration Room","demo-room",{"type":49,"text":285},{"zh":286,"en":287},"过去几年我们发现，很多项目卡住不是因为价格，而是因为双方对「要做成什么样」的理解不一致。一台能跑起来的原型，比二十页文档更能对齐认知。","Over the past few years we have found that many projects stall not over price, but because the two sides disagree on what “done” should look like. A working prototype aligns people far better than twenty pages of documentation.",{"type":49,"text":289},{"zh":290,"en":291},"演示中心的设备都基于我们客户的真实硬件环境搭建——包括常见的国产化终端与产线平板。客户在这里看到的运行效果，就是他工厂里会看到的效果。","Every device in the demonstration center is set up to match our clients’ real hardware—including the domestically made terminals and shop-floor tablets they commonly use. What clients see running here is what they will see in their own factories.",{"type":58,"text":293,"id":296},{"zh":294,"en":295},"接下来","What's Next","next",{"type":68,"items":298},[299,302,305],{"zh":300,"en":301},"持续招聘后端、前端与实施岗位","Continue hiring for backend, frontend, and implementation roles",{"zh":303,"en":304},"产品实验室将用于更多真实场景的原型验证","Use the product lab to validate prototypes across more real-world scenarios",{"zh":306,"en":307},"西南客户服务中心保持季度轮驻，保持对川滇黔客户的现场响应","Maintain quarterly rotations at our Southwest China client service center to keep on-site support for clients in Sichuan, Yunnan, and Guizhou",{"slug":309,"title":310,"category":112,"date":313,"excerpt":314,"author":317,"body":318},"data-dashboard-design-principles",{"zh":311,"en":312},"看板不是报表：中小企业数据可视化的四个设计原则","A Dashboard Is Not a Report: Four Design Principles for SME Data Visualization","2026-05-28",{"zh":315,"en":316},"我们复盘了交付过的二十余个经营看板，发现真正被每天打开的只有三个。差别不在技术，在设计。","We reviewed more than twenty business dashboards we have delivered and found that clients actually open only about three of them every day. The difference isn't technology—it's design.",{"zh":204,"en":205},[319,323,327,332,336,341,345,350,354,359],{"type":49,"text":320},{"zh":321,"en":322},"「做个数据看板」是我们接到过最多的需求之一。但交付之后，客户每天真的会打开的看板，平均只有三个。","“Build us a data dashboard” is one of the most frequent requests we receive. But after delivery, clients actually open only about three dashboards a day on average.",{"type":49,"text":324},{"zh":325,"en":326},"问题往往不在技术，而在没人定义过「看了之后要做什么决定」。","The problem usually isn't technical. It's that no one has defined what decision you are supposed to make after looking at it.",{"type":58,"text":328,"id":331},{"zh":329,"en":330},"原则一：每个数字都要绑定一个动作","Principle 1: Every Number Should Be Tied to an Action","p1",{"type":49,"text":333},{"zh":334,"en":335},"如果一个指标出现异常，看板上没有任何对应的处理指引，那它就没有存在的必要。好的看板会直接写清楚：超过什么阈值需要做什么。","If a metric goes off track and the dashboard offers no guidance on how to respond, it has no reason to exist. A good dashboard states plainly what to do when a threshold is crossed.",{"type":58,"text":337,"id":340},{"zh":338,"en":339},"原则二：先做口径，再做图表","Principle 2: Define the Metrics Before Building the Charts","p2",{"type":49,"text":342},{"zh":343,"en":344},"我们在项目早期一定要求客户把指标口径写下来：销售额含税还是不含税、退款怎么算、跨月订单归哪个月。口径不清时，画得再漂亮的图也只是把分歧可视化。","Early in every project, we require the client to write down metric definitions: is sales revenue before or after tax, how are refunds counted, which month do orders that span months belong to? Without clear definitions, even the most polished charts only visualize disagreement.",{"type":58,"text":346,"id":349},{"zh":347,"en":348},"原则三：分层而不是平铺","Principle 3: Layer, Don't Flatten","p3",{"type":49,"text":351},{"zh":352,"en":353},"老板看的是三行数字，一线看的是今天的待办。把所有指标平铺在一屏上，等于什么都没说。","Executives need three lines of numbers; frontline staff need today's to-do list. Flattening every metric onto a single screen says nothing to anyone.",{"type":58,"text":355,"id":358},{"zh":356,"en":357},"原则四：移动端优先","Principle 4: Design for Mobile First","p4",{"type":49,"text":360},{"zh":361,"en":362},"我们统计客户的实际打开场景，超过七成是在手机上看。看板的第一屏必须在竖屏手机上读完——这会倒逼你砍掉一半的指标，而那一半通常本来就不重要。","When we measured where clients actually open their dashboards, over 70% of views were on phones. The first screen must be readable on a phone in portrait mode—which forces you to cut half your metrics, and that half usually wasn't important anyway.",{"slug":364,"title":365,"category":262,"date":368,"excerpt":369,"author":372,"body":375},"soeons-sla-upgrade-2026",{"zh":366,"en":367},"运维响应标准升级：30 分钟内响应成为默认承诺","Upgraded Support Standards: 30-Minute Response Now the Default Commitment","2026-04-15",{"zh":370,"en":371},"从 2026 年 5 月起，所有在保项目的响应时效统一为 30 分钟内响应、4 小时内给出处理方案。","Starting in May 2026, every project under an active support contract will get a guaranteed response within 30 minutes and a resolution plan within 4 hours.",{"zh":373,"en":374},"莫思颖","Mo Siying",[376,380,384,389,406,411,415],{"type":49,"text":377},{"zh":378,"en":379},"从 2026 年 5 月 1 日起，我们对所有在保项目统一升级运维响应标准：严重故障 30 分钟内响应、4 小时内给出处理方案与预估恢复时间。","Effective May 1, 2026, we are upgrading support response standards across all projects under active warranty: for critical incidents, we will respond within 30 minutes and provide a resolution plan and estimated recovery time within 4 hours.",{"type":49,"text":381},{"zh":382,"en":383},"过去我们对不同规模的项目有不同的响应约定，实践中发现这经常让客户在关键时刻需要先做一轮商务沟通才能获得帮助。响应时效不应该取决于合同金额。","Previously, response terms varied by project size, and in practice this often meant clients had to go through a round of commercial negotiations before they could get help at a critical moment. Response times should not depend on contract value.",{"type":58,"text":385,"id":388},{"zh":386,"en":387},"具体包含什么","What It Covers","details",{"type":68,"items":390},[391,394,397,400,403],{"zh":392,"en":393},"7×24 监控告警，故障自动通知到值班工程师","24\u002F7 monitoring and alerting, with incidents automatically routed to the on-call engineer",{"zh":395,"en":396},"严重故障 30 分钟内响应，4 小时内出具处理方案","Response within 30 minutes for critical incidents, with a resolution plan within 4 hours",{"zh":398,"en":399},"每月一次例行巡检并输出巡检报告","A monthly health inspection with a written inspection report",{"zh":401,"en":402},"每季度一次灾难恢复演练并出具演练报告","A quarterly disaster recovery drill with a written drill report",{"zh":404,"en":405},"备份策略按客户要求调整，默认每日全量 + 增量","Backup policy tailored to each client, defaulting to daily full plus incremental backups",{"type":58,"text":407,"id":410},{"zh":408,"en":409},"背后做了什么","What Went Into the Upgrade","behind",{"type":49,"text":412},{"zh":413,"en":414},"升级响应标准的前提是值班能力真的跟得上。为此我们在过去一年重做了监控体系：统一告警入口、值班排班系统、以及每个客户独立的健康度看板——任何时候打开，都能看到每个系统在最近 24 小时内的真实状态。","Upgrading response standards only works if on-call capacity can actually keep up. To get there, we rebuilt our monitoring over the past year: a single alert entry point, an on-call scheduling system, and a dedicated health dashboard for each client—open it at any time and you see the real status of every system over the past 24 hours.",{"type":49,"text":416},{"zh":417,"en":418},"软件的生命周期比合同长。我们的合同也是。","Software outlives its contract. So do ours.",1793453940881]