Design Principles and Differentiation

English | 简体中文

Applies to DecisioWorks v1.4.0

Design Principles and Differentiation

DecisioWorks is differentiated by how it organizes production-decision capabilities for sustained use and evolution, rather than by feature count.

Core design principles

Data is business

The standardized data interface defines more than fields. It captures time, product, process-capacity, and material-readiness relationships, so business facts and structural constraints enter the computable chain together.

Good plans and good decisions have distinct responsibilities

GOCK creates high-quality plans within explicit data, constraints, and objectives. DecisioCore organizes objectives, rules, actions, explanations, and feedback so those plans can support production decisions. Web makes inputs, configuration, execution, and results visible, while DataSets provides industry scenarios and interface templates.

Clear responsibilities with governed linkage

Master planning, scheduling, material readiness, and local control each handle the problems suited to their scope. Release packages, plan-bias values, plan signals, and analysis feedback connect them without erasing their responsibilities.

Explicit objectives and rules

The objective system governs reusable concerns such as delivery, inventory, workload, waiting, and changeovers. Operational rule control (marginal_control) expresses site-specific experience, bottlenecks, and balancing rules. Solver behavior can therefore be configured, inspected, and reviewed.

Standard actions and capability orchestration

Data acquisition, constraint parsing, objective construction, solution generation, selection, evaluation, and dispatch are organized as standard actions. Scenarios compose these actions through recipes, so process changes do not require rebuilding the whole system.

Results become evidence; feedback drives evolution

Analysis exposes both aggregate indicators and object-level detail. Deviations, bottlenecks, and explanations can return to the next planning cycle, allowing the system to improve through real use.

Open, ecosystem-oriented, and evolution-friendly

Data sources, business rules, orchestration, model adapters, and user experiences can evolve independently. DecisioCore provides an open reference implementation that partners can understand, reuse, and extend, while manufacturers can keep growing their own decision models around real operations.

How this differs from common project delivery

Concern	Common project approach	DecisioWorks
Starting point	Pages and workflows first	Computable business and decision problems first
Data onboarding	Field mapping and system integration	Closed business semantics, relationships, and structural constraints
Rules	Accumulated project code	Layered structural constraints, reusable objectives, and site rules
Solver output	A planning table	Plans, indicators, explanations, audits, and feedback
Operational change	Modify the entire project chain	Adjust the responsible data, objective, rule, orchestration, or model layer
Reuse	Delivery centered on one project	Reusable interfaces, actions, models, and scenario templates
Ecosystem	Extension inside a closed system	Open interfaces and reference implementations for enterprise and partner integration

Positioning

DecisioWorks is a foundational production-decision capability toolkit for smart manufacturing and a capability node connecting manufacturers, industrial-software partners, consultants, industrial parks, and AI Agents.

It covers data onboarding, business representation, objective and rule configuration, model execution, result drill-down, and feedback. Partners can build industry solutions, applications, and delivery services on top of it, while manufacturers can retain operating knowledge as data templates, rule configurations, and scenario recipes.

Next: Architecture Overview · Component Responsibilities · Ecosystem Overview