Yuqi Intelligent Enterprise IT infrastructure and systems integration
139 1891 4454 Contact Us
139 1891 4454 Contact Us
Enterprise · Software · Customization

Industry Software Development
Real workflows, connected systems.

Start with roles, business records and permissions. Define the workflows, interfaces, test evidence and operating handover for a maintainable business system.

book a business discovery see how logic becomes a system Schedule follows agreed scope
ERP / OA customization WMS / MES customization AI integration · enterprise knowledge base Legacy system integration
Source code · documentation · data dictionary delivered in full
key-role training + handover guide
Post-launch support as agreed
Scope
Workflow inventory
API
Interface contracts
Tests
Acceptance records
Guide
Operating handover
Illustrative business-discovery collaborationon-site discovery · real workflow capture
LIVE
Review
Requirements and exceptions
Confirm the scope before implementation
Pilot
A verifiable first release
Agree acceptance and rollback conditions
~/deploy · zsh
Six reference workflowsNot customer project results
M01 · manufacturing
precision MES
Scope review
M02 · healthcare
business platform
Scope review
M03 · logistics
multi-warehouse WMS
Scope review
M04 · retail
membership CRM
Scope review
M05 · education
education scheduling
Scope review
M06 · finance
corporate banking console
Scope review

Interface and deployment simulations below do not display customer systems or live production telemetry.

technology stack · selected for the environment, never locked inTECHNOLOGY OPTIONS · SCOPE REVIEW
01 · BUSINESS LOGIC

business logic is not a diagram,
it isone document completing its full journey.

A business flow is defined by the roles, systems and records a business document must cross. We map each hand-off between systems and the real work that happens between them.

SALES ORDER · JOURNEYthe complete journey of a sales order

Illustrative workflow from order to finance archive; nodes, roles, and systems are scoped per project. The backbone is customer → sales → warehouse → finance.

LANE 01 · Customer & sales LANE 02 · Planning & inventory LANE 03 · Production & fulfillment LANE 04 · Finance & archive 01 customer order Customer · Store / EDI 02 credit check Sales · ERP customization 03 inventory reservation Warehouse · WMS · batch / expiry 04 production scheduling Planning · MES · work order / BOM 05 pick and ship Warehouse · WMS + TMS 06 proof of delivery Driver · mini-program · e-signature 07 invoicing and reconciliation Finance · ERP · tax interface 08 archive to the knowledge base Knowledge base · AI · archive
Illustrative workflow: 8 nodes Illustrative workflow: 6 roles Illustrative workflow: 7 systems Illustrative workflow: 12 exception branches auditable end-to-end trace any node can be replaced independently
02 · CONVERSION ENGINE

Turn real workflowsinto a working system,
not another slide deck.

People work across teams, systems remain connected. We start with observable business actions and customer-owned rules, then turn them into a maintainable product.
01

business discovery turn actions into clear records

Observe representative roles and record normal work, exceptions and data ownership. Agree the discovery period and outputs before proposing system changes.

on-site shadowingrole action checklistexception branches SOPcurrent-state pain points
02

role and workflow modeling make responsibilities explicit

We model roles, records and state changes as a swimlane and data-flow diagram. Everyone can see who owns each decision and what the next system receives.

swimlane sequence diagramdata-flow diagramstate machinerole responsibility matrix
03

data boundaries keep ownership clear

A permission matrix defines who may read, change or share each record. Data ownership, sharing rules and audit trails are agreed before implementation begins.

permission matrixdata ownershipsharing rulesaudit trail
04

contract definition sign before build

We define the API, event and UI contracts before building. The team signs off on payloads, states, errors and acceptance rules so each module can evolve without breaking the others.

OpenAPIAsyncAPIevent contractacceptance rules
05

domain development modular and configurable

Divide work into modules with explicit dependencies, acceptance criteria and rollback conditions. Agree iteration milestones and review a runnable version at each stage.

domain modelconfigurationtwo-week iterationsCI/CD
06

delivery and follow-through launch is not the finish line

Hand over the agreed source-code rights, documentation, deployment records and operating procedures. Define administrator training and subsequent support in the delivery scope.

source code delivered in fullrole traininghandover guidesupport window
03 · ARCHITECTURE

A system architecture thatkeeps changing parts replaceable.

No lock-in and no opaque core. The API + integration layer connects the delivered systems; the UI stays simple, while permissions, data and events remain observable to the customer team.
CORE integration bus v4.2 01 · EXPERIENCE customer portal / Web / mobile 02 · DOMAIN business modules 03 · CAPABILITY shared services 04 · FOUNDATION data / integration / security ERP / financeworkflow · data · SAP OA / workflowmobile · e-signature CRMSFA · membership MES / productionwork orders · BOM WMS / TMSDriver · mini-program · e-signature AI connectLLM · RAG · Agent AI servicesRAG · agent · knowledge Data platformwarehouse · BI IoT / edgePLC · telemetry · events SSOidentity · audit SYS-ARCH v4.2 10 NODES · 12 INTEGRATIONS

A delivered systemmust stay changeable.

Clear contracts, modular domains and observable integrations leave the customer with a system that can grow without a rewrite.

contract firstAPI, events and UI states are agreed before implementation.
domain modularityERP / OA / CRM / MES / WMS / AI, selected by domain.
integration busWebHook / MQ / iPaaS connect services, queues, files, SAP and existing systems.
evolvabilityVersioned modules, feature flags and A/B rollout make change safe.
permissions and auditRole × scope × action permissions, with audit evidence and operational BI.
04 · CAPABILITY

business capability matrix,
from front end to operations.

We make the system usable by people and maintainable by engineers. Every domain exposes clear CRUD behavior through a documented API and permission model.

frontend engineering

FRONTEND

Business-facing screens, forms and dashboards are built around real work, with responsive states and clear feedback for every action.

ReactVue 3TypeScriptTailwindEChartsdesign systemReactVue 3TypeScriptTailwindEChartsdesign system

backend services

BACKEND

The domain model, services, queues and storage are separated by contract. OpenAPI and AsyncAPI keep integrations reviewable and testable.

GoJava · Spring.NETPythongRPCKafkaGoJava · Spring.NETPythongRPCKafka

data engineering

DATA

Data pipelines, governance and reporting turn operational records into decisions. The delivered model remains auditable as the business grows.

FlinkDorisFlink SQLETLBIdata qualityFlinkDorislineageETLBIgovernance

AI engineering

AI

RAG, agent workflows and knowledge services connect AI to approved business data. Each AI capability is scoped, reviewable and tied to a useful task.

LLMRAGAgenttoolsguardrailsevaluationLLMRAGAgenttoolsguardrailsevaluation

mobile

MOBILE

Mobile flows are designed for field work, offline realities and clear role hand-offs across iOS and Android.

FlutterRNoffline cacheiOSAndroidfield flowsFlutterRNoffline cacheiOSAndroidfield flows

operations · SRE

DEVOPS

Kubernetes, CI/CD and observability keep releases repeatable. Delivery pipelines, alerts and runtime ownership stay visible to the team.

K8sCI/CDPrometheusalertsrunbooksSLOsK8sCI/CDPrometheusalertsrunbooksSLOs
request → API → service → dataillustrative throughput load test scoped
FRONTEND API GATEWAY SERVICES DATA Web portal React · forms Admin console Vue · permissions Mobile App Flutter · field work API gateway REST · events Order service Go · domain logic Inventory service Java · state machine Reporting service SQL · BI MySQL · Redis MySQL · Redis BI · RAG BI · RAG
frontend · order.ts

          
backend · handler.go

        

        
Test
Representative workload
Trace
Latency evidence
Agree
Availability objectives
Revert
Rollback evidence

      

    

  







  

    

      

        05 · WHAT YOU GET
        
what customers really receivesix durable outcomes.

      

      

        Source code is only the beginning. What customers receive is a working process, clear contracts, modular systems, ongoing support, ownership and embedded AI.
      

    

    

      
real workflow delivery
not slides, but the work.
On-site shadowing, role action checklists and exception SOPs turn real work into system-readable, executable and auditable rules.
DeliverableWorkflow inventory

      
integrable · no lock-in
a drop-in module.
Every layer has an API and event contract. Deploy the whole system or connect one module to an existing ERP, OA or CRM.
DeliverableInterface contract

      
extensible · built to grow
grow with your business.
Evolve from MVP to a full module set. New business lines, subsidiaries and overseas branches can be added without starting over.
DeliverableExtension boundaries

      
sustainable operation
maintainable after handover.
Health checks, observability and a named operating owner keep the system maintainable after launch; the review cadence is agreed per project.
DeliverableOperations manual

      
deep customization support
it's your code, in the end.
Document source-code and third-party licensing boundaries, deployment procedures and administrator permissions so the customer can maintain the agreed scope.
DeliverableOwnership handover

      
AI and knowledge base included
not a chatbot, but a workflow.
AI enters the workflow: assisted forms, approvals, contract extraction, report interpretation and knowledge-base answers, governed by existing data rules.
DeliverableAI acceptance

    

  







  

    

      

        06 · MODULES
        
business subsystems ·
choose what you need and tailor it to the context.

      

      
From ERP extensions, OA and CRM to MES / WMS, AI integration and an enterprise knowledge base, each module stands alone. Buy one or run a coordinated set; the existing systems on site always come before “building another one”.

      

    


    

      

        
ERP · master dataM-01

        
ERP extensions

        ERP · master data · SAP · Oracle
        
Extend the ERP around the customer's real process: master data, orders, finance, mobile work, reporting and MES/WMS integration, without replacing the core system.

        
  • domain model and master data
  • mobile + workflow + reporting
  • MES / WMS integration

        

      

      

        
OA · collaborationM-02

        
OA and workflow engine

        workflow · mini-program · e-signature · collaboration
        
Replace scattered messages with structured collaboration: requests, approvals, nodes, SLA, notifications and escalation, all available from the mobile app.

        
  • workflow model
  • roles, SLA and notifications
  • mobile + e-signature

        

      

      

        
CRM · customer growthM-03

        
CRM and sales automation

        toB · toC · marketing · membership
        
Manage leads, opportunities, customer pools and membership in one flow, with content and automation for marketing and clear role permissions for every team.

        
  • lead → opportunity → contract
  • customer tags, segments and follow-up
  • membership, marketing and analytics

        

      

      

        
MES · shop-floor executionM-04

        
MES · shop-floor execution

        shop floor · mobile · e-signature · manufacturing
        
Connect work orders, scheduling, equipment and quality traceability on the shop floor, then link the results back to ERP, PLM and WMS for one production picture.

        
  • shop-floor execution
  • equipment and OEE
  • quality traceability and SPC

        

      

      

        
WMS · TMSM-05

        
WMS / TMS warehouse and delivery

        Driver · mini-program · e-signature
        
Handle inbound and outbound warehouse operations, batches, expiry dates and multiple sites, then coordinate routes and final delivery from the same operational view.

        
  • RF / PDA warehouse operations
  • batches, multi-warehouse and expiry
  • routing and delivery

        

      

      

        
AI · connectM-06

        
AI integration · workflow embedding

        LLM · RAG · Agent · OCR
        
AI integrates into daily work: intelligent form filling, approvals, contract and document extraction, report interpretation and knowledge-base answers, all governed by existing data rules.

        
  • OCR (invoices / contracts)
  • RAG knowledge base
  • agent workflow

        

      

      

        
enterprise knowledge baseM-07

        
enterprise knowledge base

        RAG · documentation · SOP · permissions
        
Turn customer documents, SOPs, process rules and permissions into a searchable knowledge base that supports reliable AI answers.

        
  • document governance and SOPs
  • knowledge search
  • permissions / versioning

        

      

      

        
data platform · master dataM-08

        
data platform · master data

        BI · data model · governance
        
Unify customers, products, orders and suppliers as governed master data, then use the data platform and BI to support decisions with one consistent view.

        
  • data governance
  • data platform
  • BI decision support

        

      

      

        
integration busM-09

        
integration bus · iPaaS

        API · events · iPaaS
        
Connect ERP, OA, CRM, MES, WMS, AI, the knowledge base, SRM, finance, HR and external systems through stable contracts and observable flows.

        
  • stable contracts
  • event-driven integration
  • monitoring and alerts

        

      

      

        
IoT · device accessM-10

        
IoT and device access

        PLC · telemetry · edge
        
Connect devices, PLCs, edge gateways and AGVs to collect telemetry, status and control signals in one operational flow.

        
  • device access
  • edge computing
  • real-time data

        

      

      

        
SRM · procurementM-11

        
SRM supplier collaboration

        supplier lifecycle · mobile · e-signature · procurement
        
Manage the supplier lifecycle from registration, quotation and tender through contracts, orders, reconciliation and payment, linked to ERP purchasing and finance.

        
  • supplier pool
  • sourcing and tendering
  • reconciliation and payment

        

      

      

        
expense · business travelM-12

        
Expense and business travel

        mobile · e-signature · finance
        
Coordinate travel requests, expenses and reimbursements with invoice OCR, budgets and approval rules, connected to the ERP finance module.

        
  • invoice OCR
  • budgets and approvals
  • finance interface

        

      

    

  







  

    

      
Scope
Requirements inventory

      
Build
Versioned delivery

      
Test
Recorded acceptance

      
Run
Operating ownership

    

  







  

    

      

        07 · TEAM
        
Engineering roles and delivery responsibilities

      

      
The following cards describe project roles, not named employees or credentials. Confirm the assigned people, responsibilities and required qualifications before work begins.

    

    

        
AR
Architecture
Project role
DDDSpring Cloudhigh concurrencycomplex business
Responsibilities confirmed per project
Define dependencies, interfaces and rollback boundaries.

      
APP
Applications
Project role
Yonyou NCKingdee EASSAP B1BPM
Responsibilities confirmed per project
Map application behavior to the confirmed workflow.

      
DATA
Data and AI
Project role
LLMRAGAgentprivate deployment
Responsibilities confirmed per project
Validate data access, quality and model-output boundaries.

      
INT
Data integration
Project role
Flinkmaster dataiPaaSBI
Responsibilities confirmed per project
Confirm data ownership, mapping and integration evidence.

      
UX
Client and UX
Project role
FlutterRNmini-programsiOS/Android
Responsibilities confirmed per project
Verify client, device, accessibility and role experience.

      
OPS
Platform operations
Project role
K8sCI/CDmonitoringdisaster recovery
Responsibilities confirmed per project
Define monitoring, change, incident and recovery boundaries.

      
PD
Product and design
Project role
B2B UXprototypingdesign systemsuser interviews
Responsibilities confirmed per project
Turn confirmed requirements into reviewable interaction and acceptance criteria.

      
BA
Business analysis
Project role
on-site discoverySOPprocess modelingdata ownership
Responsibilities confirmed per project
Record role actions, exceptions and acceptance evidence.

    

    

      

        
Roles
Named responsibilities

        
Access
Access matrix

        
Tests
Acceptance evidence

        
Guide
Support boundaries

      

      

        We support extensions for most business applications—standard ERP / OA / CRM / SRM / MES / WMS or a “legacy system” the customer has built over many years.
        We can enter at any stage, from frontend refactoring, module replacement, API expansion and performance tuning to AI integration and knowledge-base construction, with no stage too early or too late.
      

    

  







  

    

      

        08 · CASES
        
Reference workflows across six industries

      

      
These are reference requirements and acceptance paths, not completed customer projects, certifications or measured performance results.

    

    

      
manufacturing · MES
Manufacturing: work orders and traceability
Reference scope
Define work-order release, barcode reporting, quality records and ERP interfaces. Validate state changes and traceability with representative orders.
Scope
Requirements
Test
Acceptance
Record
Handover

      
distribution · WMS
Logistics: inventory and dispatch
Reference scope
Map warehouse ownership, inventory changes, picking waves and delivery receipts. Validate exceptions and reconciliation before rollout.
Scope
Requirements
Test
Acceptance
Record
Handover

      
healthcare · business platform
Healthcare: workflow and access boundaries
Reference scope
Define administrative workflows, data-sharing permissions and audit records. Clinical decisions and formal compliance assessments remain outside this illustrative scope.
Scope
Requirements
Test
Acceptance
Record
Handover

      
retail · CRM
Retail: membership and reconciliation
Reference scope
Connect member permissions, points, coupon redemption and store inventory. Validate duplicate events, reversals and reconciliation.
Scope
Requirements
Test
Acceptance
Record
Handover

      
education · academic operations
Education: scheduling and attendance
Reference scope
Define enrollment, scheduling constraints, attendance and settlement. Test conflicting bookings and corrections with representative scenarios.
Scope
Requirements
Test
Acceptance
Record
Handover

      
finance · business operations
Finance: risk workflow and audit records
Reference scope
Define customer classification, review tasks, risk events and reporting permissions. Certification and regulatory acceptance require separate formal assessment.
Scope
Requirements
Test
Acceptance
Record
Handover

    

  







  

    

      

        09 · DELIVERY
        
delivery rhythm · from the first conversation
to a system that grows stronger.

      

      
Agree discovery, interface review, pilot, rollout and support milestones for the actual scope. The timeline illustrates a delivery sequence, not a fixed duration or service-level guarantee.

    

    

      

        
on-site discovery timing scoped per project
PRE-DEV · ON-SITE
Observe the current work in an agreed window, record role actions, exception SOPs, system ownership and permission boundaries.
  • role action checklist
  • SOP + exception branches
  • data ownership and permissions

        
TIMING SCOPED

        
on-site shadowing

      

      

        
contract sign-off · contract v1

        
TIMING SCOPED

        
contract sign-off timing scoped per project
API · EVENT · DATA
Agree the API, events, data model and permission matrix before build. The signed contract makes responsibilities, acceptance and change control explicit.
  • OpenAPI + AsyncAPI
  • permission matrix v1
  • acceptance checklist

      

      

        
MVP launch week 3–6
MVP · LIVE
Launch the first usable slice, collect real feedback and expand the workflow in short, measurable cycles.
  • usable core workflow
  • feedback · iteration · release
  • production observability

        
TIMING SCOPED

        
MVP · staged launch

      

      

        
customer takeover · training

        
TIMING SCOPED

        
customer takeover handover timing scoped
HANDOVER · TRAINING
Source code, documentation, CI/CD and operating procedures are checked against the delivery list; the customer team takes ownership through guided handover.
  • source code and documentation
  • operations guide + runbook
  • role training

      

      

        
ongoing support support scoped per agreement
RUN · EVOLVE · SUSTAIN
We keep improving the system, governing change and supporting the operating team. New modules are added against the same contracts, not patched into a black box.
  • release support
  • change governance + review
  • extend modules as needed

        
LONG RUN

        
ongoing support

      

    

  



Illustrative sequence only. Duration, source-code rights, third-party licenses and maintenance are confirmed in the project scope.







  

    

      
        
        
        
        
        
      
      

        READY · WHEN YOU ARE
        
Bring your real workflows to life,
with a system your team can own.

        
Book a business discovery call with timing agreed for a practical, non-binding solution recommendation. Bring one workflow, one pain point or one system that needs to change.

        

          Book a discovery call 
          Contact Yuqi Intelligent