他们的问题,
和我们的解法。
Their problems,
and how we solved them.

每一个案例都写清楚了客户原来卡在哪、我们做了什么、以及上线之后数字变成了什么样。客户名称已做脱敏处理。Every case lays out where the client was stuck, what we built, and how the numbers changed after launch. Client names have been anonymized.

显示 8 / 8Showing 8 / 8

智能制造Smart Manufacturing广西 · 柳州Liuzhou, Guangxi · 2025

精密零部件制造的工单与追溯体系Work Order and Traceability System for Precision Components Manufacturing

客户:Client: 某精密制造集团A precision manufacturing group

为一家做精密结构件的制造集团重建工单体系,把订单、工艺、质检与仓储串成一条可追溯的链路。Rebuilt the work order system for a precision structural components manufacturer, linking orders, processes, quality inspection, and warehousing into a single traceable chain.

面临的问题The challenge

生产订单靠 Excel 在车间、仓库、质检三方之间传递,版本经常对不上;客户要求提供产品全过程追溯时,需要人工翻找两个月的纸质记录。Production orders moved between the shop floor, warehouse, and QA team in Excel, and version mismatches were routine. When a customer requested full product traceability, staff had to dig through two months of paper records by hand.

我们的方案Our approach

  • 梳理 14 类工单模板与 23 个关键流转节点,替换全部线下 ExcelMapped 14 work order templates and 23 key handoff points, replacing all offline Excel workflows
  • 搭建统一工序编码规则,实现批次级全链路追溯Established a unified process coding standard for end-to-end batch-level traceability
  • 对接已有 ERP 与财务系统,避免重复录入Integrated with the existing ERP and finance systems to eliminate duplicate data entry
  • 车间大屏实时显示在制工单进度与异常件Rolled out shop floor displays showing live work order progress and exception items
缩短 62%Reduced by 62%
工单流转耗时Work order cycle time
2 小时 → 30 秒2 hours → 30 seconds
追溯查询Traceability lookup
减少 80%Reduced by 80%
数据重复录入Duplicate data entry

技术栈 · Java / Spring Boot / MySQL / Vue / DockerStack · Java / Spring Boot / MySQL / Vue / Docker

零售连锁Retail Chains广西 · 南宁Nanning, Guangxi · 2025

连锁零售的会员与门店一体化平台Unified Loyalty and Store Platform for a Retail Chain

客户:Client: 某区域连锁零售品牌A regional retail chain

把 60 余家门店的会员、储值、库存与营销活动整合到统一平台,实现线上线下同一套会员体系。Consolidated loyalty, stored value, inventory, and campaign data from 60+ stores onto one platform, giving online and offline channels a single unified loyalty program.

面临的问题The challenge

门店系统与电商后台各自为政,同一顾客在两边是两个身份;活动效果只能看总营收,无法判断哪一次活动真正带来了复购。Store systems and the e-commerce back office operated independently, so the same customer had two separate identities. Campaign performance could only be measured by total revenue—impossible to tell which campaign actually drove repeat purchases.

我们的方案Our approach

  • 建立统一会员主数据模型,完成存量会员去重与合并Built a unified customer master data model and de-duplicated and merged existing member records
  • 打通门店 POS、电商与小程序三端的会员与储值数据Connected membership and stored-value data across in-store POS, e-commerce, and the mini program
  • 重构活动分析指标体系,支持单次活动的 ROI 归因Redesigned campaign analytics to attribute ROI to individual campaigns
  • 上线门店与区域两级经营看板Delivered store-level and regional performance dashboards
提升至 94%Increased to 94%
会员识别率Member identification rate
从 0 到 100%0% → 100%
活动 ROI 可归因Campaign ROI attribution
+17%+17%
月度复购率Monthly repeat purchase rate

技术栈 · Next.js / NestJS / PostgreSQL / Redis / EChartsStack · Next.js / NestJS / PostgreSQL / Redis / ECharts

农业供应链Agricultural Supply Chain广西 · 玉林Yulin, Guangxi · 2024

农产品产地供应链的溯源与调度Traceability and Fleet Dispatch for an Agricultural Supply Chain

客户:Client: 某农产品供应链集团An agricultural supply chain group

为覆盖 3 个地级市、200 余个合作社的供应链网络搭建溯源与运力调度系统。Built a traceability and transport dispatch system for a supply chain network spanning 3 prefecture-level cities and 200+ cooperatives.

面临的问题The challenge

货源信息靠微信群和电话协调,运力调度全凭调度员经验;出了问题追溯不到具体批次,消费者信任度持续走低。Supply information was coordinated over WeChat groups and phone calls, and dispatching relied entirely on individual dispatchers' experience. When problems arose, there was no way to trace a specific batch, and consumer trust kept declining.

我们的方案Our approach

  • 设计产地分级、质检、入库、发货五段式溯源编码Designed a five-stage traceability coding scheme covering origin grading, quality inspection, warehousing, and shipping
  • 开发基于订单时效与车辆位置的运力调度看板Built a dispatch dashboard driven by order deadlines and real-time vehicle locations
  • 搭建面向合作社的轻量化移动端录入工具Developed a lightweight mobile data entry tool for cooperatives
  • 对接监管平台完成数据上报Integrated with regulatory platforms for automated data reporting
从小时级到分钟级From hours to minutes
调度响应Dispatch response
下降 28%Down 28%
运力空驶率Empty-running rate
100%100%
溯源覆盖率Traceability coverage

技术栈 · Go / React / ClickHouse / Kafka / KubernetesStack · Go / React / ClickHouse / Kafka / Kubernetes

物流运输Logistics四川 · 成都Chengdu, Sichuan · 2024

三方物流运单与结算平台Waybill and Settlement Platform for a Third-Party Logistics Provider

客户:Client: 某区域物流服务商A regional logistics provider

重构运单流转与运费结算体系,把 400 余台运力、20 余家网点接入同一套调度与对账平台。Rebuilt the waybill and freight settlement workflow, bringing 400+ vehicles and 20+ branch offices onto a single dispatch and reconciliation platform.

面临的问题The challenge

运单状态靠电话和微信更新,货损责任无法追溯;财务每月对账要花两周,仍有争议款项说不清。Waybill status was updated via phone calls and WeChat, leaving cargo damage claims untraceable. Monthly reconciliation took finance two weeks and still left disputed amounts unresolved.

我们的方案Our approach

  • 统一运单状态机与异常处理流程Standardized the waybill status model and exception handling workflow
  • 对接 GPS 与车载终端实现位置回传Integrated GPS and in-vehicle terminals to report real-time location data
  • 建立自动计费规则引擎与对账报表Built an automated freight billing rules engine and reconciliation reports
  • 异常索赔线上化流转Moved damage claims to an online approval workflow
2 周 → 3 天2 weeks → 3 days
月度对账耗时Monthly reconciliation time
实时Real-time
运单状态回传Waybill status updates
下降 41%Down 41%
货损争议率Cargo damage disputes

技术栈 · Java / Spring Boot / MySQL / React / RedisStack · Java / Spring Boot / MySQL / React / Redis

教育Education广西 · 南宁Nanning, Guangxi · 2023

职业院校的一体化教务管理平台Integrated Academic Management Platform for a Vocational College

客户:Client: 某高职院校A vocational college

打通教务、考务、宿舍与缴费模块,把分散在四个系统里的学生数据统一到一个平台。Connected the academic affairs, examinations, dormitory, and tuition modules, consolidating student data from four separate systems onto one platform.

面临的问题The challenge

四个系统各有一份学生数据,转专业、评奖评优等流程要在多系统之间人工核对,每年招生季行政人员要加班三周。Each of the four systems held its own copy of student data, so processes such as major transfers and scholarship decisions required manual cross-checking between systems. Every admissions season, admin staff worked three weeks of overtime.

我们的方案Our approach

  • 建立学生主数据中心并完成四个系统的数据归一Built a student master data hub and normalized data across the four systems
  • 重做选课、成绩、评奖评优等 9 条核心业务流程Redesigned 9 core workflows, including course selection, grading, and scholarships
  • 开放学生端与教师端移动应用Launched mobile apps for students and faculty
  • 提供历史数据迁移与双轨并行方案Delivered historical data migration and a parallel-run cutover plan
取消人工核对Manual checks eliminated
跨系统核对Cross-system checks
减少 65%Reduced by 65%
招生季行政工时Admissions season admin hours
78%78%
学生端活跃率Student app activity rate

技术栈 · Java / Spring Boot / MySQL / WeChat Mini Program / DockerStack · Java / Spring Boot / MySQL / WeChat Mini Program / Docker

医疗健康Healthcare广西 · 桂林Guilin, Guangxi · 2023

连锁医疗机构的预约与随访平台Appointment and Follow-Up Platform for a Healthcare Group

客户:Client: 某连锁医疗集团A healthcare group

覆盖 6 家院区的在线预约、分诊排队与术后随访系统,把电话预约的比例降到不足两成。Delivered online booking, triage queuing, and post-surgery follow-up across 6 hospitals, bringing phone-only scheduling below 20% of all appointments.

面临的问题The challenge

全部预约依赖电话,前台在高峰期漏接与错约频发;术后随访靠纸质记录,科研数据难以沉淀。All appointments were booked by phone, and front desk staff frequently missed calls or booked the wrong slot during peak hours. Post-surgery follow-ups were recorded on paper, making it hard to build research datasets.

我们的方案Our approach

  • 开发分诊规则引擎,按科室与医生维度分配号源Built a triage rules engine to allocate appointment slots by department and physician
  • 上线患者端小程序与自助取号Launched a patient mini program with self-service check-in
  • 设计结构化随访表单并回流临床数据Designed structured follow-up forms that feed data back into clinical records
  • 建立院区经营与医疗质量双看板Built dual dashboards for hospital operations and care quality
降至 18%Down to 18%
电话预约占比Phone appointment share
下降 35%Down 35%
爽约率No-show rate
提升至 91%Increased to 91%
随访完成率Follow-up completion rate

技术栈 · Next.js / NestJS / PostgreSQL / Redis / EChartsStack · Next.js / NestJS / PostgreSQL / Redis / ECharts

金融科技Fintech广西 · 南宁Nanning, Guangxi · 2022

小额信贷的智能审批与风控系统Intelligent Loan Approval and Risk Control for Microfinance

客户:Client: 某地方金融科技公司A local fintech company

在合规前提下把小额信贷审批时长从 3 天压缩到 40 分钟,并沉淀出可解释的规则模型。Cut micro-loan approval time from 3 days to 40 minutes while staying fully compliant, and established an explainable rules-based risk model.

面临的问题The challenge

纯人工审批积压严重,且不同审批员口径不一致;风控规则散落在多份 Excel 中,无法审计。Manual-only approval created a serious backlog, and reviewers applied inconsistent criteria. Risk rules were scattered across multiple Excel files and could not be audited.

我们的方案Our approach

  • 梳理并固化 68 条审批规则,全部版本化可追溯Documented and formalized 68 approval rules, all version-controlled and auditable
  • 开发规则引擎与审批工作台Built a rules engine and reviewer workbench
  • 建立反欺诈特征库与人工复核队列Created an anti-fraud feature library and manual review queue
  • 接入征信与工商数据源做交叉验证Integrated credit bureau and business registry data for cross-validation
3 天 → 40 分钟3 days → 40 minutes
平均审批时长Average approval time
100%100%
审批口径一致性Approval consistency
同比 +3.2 倍3.2x year over year
欺诈拦截笔数Fraud cases blocked

技术栈 · Java / Spring Boot / MySQL / Python / DockerStack · Java / Spring Boot / MySQL / Python / Docker

政企园区Public Sector & Parks广西 · 南宁Nanning, Guangxi · 2022

园区企业服务的「一网通办」平台"One-Stop Service" Platform for Industrial Park Businesses

客户:Client: 某工业园区管委会An industrial park management committee

把企业开办、政策申报与诉求反馈整合到一个入口,园区企业办事的平均时长压缩到 1 个工作日。Consolidated business registration, policy applications, and feedback into a single portal, bringing the average service turnaround for park companies down to one business day.

面临的问题The challenge

不同部门各有一套申报入口与材料要求,企业反复提交同一份资料;政策文件分散,看得见却用不上。Each department had its own application portal and document requirements, forcing companies to resubmit the same materials repeatedly. Policies were scattered across documents—visible but hard to actually use.

我们的方案Our approach

  • 梳理 26 项政务事项的统一材料清单Standardized document checklists for 26 government service items
  • 建设政策智能匹配引擎,按企业画像推送可申报政策Built a smart policy matching engine that recommends applicable policies based on company profiles
  • 开发企业诉求工单与闭环评价系统Developed a ticketing system for business requests with closed-loop feedback
  • 完成与上级政务平台的接口对接Completed API integration with higher-level government service platforms
减少 76%Reduced by 76%
申报材料重复提交Duplicate document submissions
压缩至 1 个工作日Down to 1 business day
平均办件时长Average processing time
提升至 91%Increased to 91%
政策匹配触达率Policy match reach rate

技术栈 · Java / Spring Boot / MySQL / Vue / DockerStack · Java / Spring Boot / MySQL / Vue / Docker

说说你要解决的问题。Tell us what needs solving.

不需要完整的需求文档。一段业务描述、一张流程草图,或者一个总在出错的表格,都可以是开始。No finished brief required. A paragraph about your operations, a rough process sketch, or one spreadsheet that keeps breaking—any of those is a good start.

邮件Email

chat@soeons.com

玉林市 · 周一至周五 09:00 – 18:00Yulin, Guangxi · Monday–Friday, 9:00 AM – 6:00 PM (CST)

0775-XXXXXXX

或填写咨询表单Or fill in the contact form