Organization Engine
People-centric org master data and reporting lines
- Dept tree, assignments and org chart view
- Posts / job types and reporting lines
- Tenant isolation for permission scopes and workflow assignees
Built on Six Engines and Dual Agents—with reports and big screens—supporting multilingual runtime and SaaS multi-tenant. Explore Six Engines · Dual Agents · Multi-language · SaaS Multi-tenant
Designed in three layers—data model, business process, and interface—as the shared foundation for seven product lines. Adopt a line for a given scenario, or one line at a time. Combined rollouts do not stand up a second organization or master-data set.
People-centric org master data and reporting lines
Across menus, data rows, page fields and reports
Business-model-driven forms and list pages
Flowable + BPMN 2.0 approval and business flows
Formatted reports, exports and big-screen dashboards
Model APIs, service registration and system channels
Products sit on this foundation:SRM Procurement、WMS Warehouse、MES Manufacturing、QMS Quality、CRM Customer Delivery. The operating side can combine PMS、EHR。View products
Design-time delivers modeling. Runtime delivers query output and API-based handling. They are not the same chat window.
Configuration and permissions are completed and published in design-time. Runtime can query and export, and can create data or complete reviews through business APIs. It does not write to the database directly and does not exceed the user's permissions.
Front and back ends are separate. Deployment can be private or in the cloud. Databases and clouds are chosen per project.
One-time modeling, multilingual operation; about 49 business language directories, which are enabled by the tenant, manually maintained translations, missing translations and falling back to the original text
Suitable for group subsidiaries, partner operations and multi-delivery centers in parallel
The engine and agent are ready to see the recent evolution or directly into the product landing
Common platform and agent questions—start here; still stuck? Contact us.
Organization, Permission, Form, Workflow, Report, and Integration—covering org master data, authorization, modeling/UI, approvals/flows, reporting/dashboards, and system connectivity.
The six engines are the shared foundation. Seven product lines sit on it and can go live one at a time. Combined use does not create a second organization, permission model, or master-data set. The agents sit on the foundation—design-time modeling, and runtime query, export, and handling—and are not a seventh engine.
Design-time uses natural language to build or change application categories, apps, modules, form models, and page or process configuration (⌘K assists scripts and SQL). Results must enter the designer for review before publish. Runtime, within authorization, answers questions as in-dialog text and charts or as Office, HTML, and Markdown, and creates data or completes reviews through business APIs. It does not write to the database directly and does not exceed the user's permissions.
Yes. About 49 language catalogs are built in; tenants opt in, with fallback to the source string. Delivered locales include Simplified Chinese, Traditional Chinese, and English.
Yes. SaaS multi-tenant covers the full lifecycle with tenant-level isolation—fit for multi-plant and multi-subsidiary groups.
Front and back ends are separate: Vue and Spring Cloud microservices, deployable with Docker or Kubernetes, or on-premises and in a private cloud. The edge is Nginx OpenResty and the gateway. The registry is Nacos. Processes use Flowable and BPMN 2.0. Databases and cloud are chosen per project.