Glossary

English | 简体中文

Applies to DecisioWorks v1.4.0

Glossary

Terms retain the same meaning across data preparation, configuration, execution, and analysis. These definitions distinguish business meaning, field representation, and what a particular run actually applies. Code identifiers and interface status values retain their original names.

Term	Meaning
APS	Advanced Planning and Scheduling for production plans, resources, and operation sequences.
GOCK	The model and optimization layer that produces plans within explicit data, constraints, and objectives.
DecisioCore	The production-decision layer connecting data, objectives, rules, solving, analysis, and feedback.
DataSets	Industry scenarios and standardized data-interface instances.
Web Cockpit	The Web interface for inspecting data, configuration, execution, results, and evidence.
Recipe	A reusable orchestration configuration describing actions, parameters, dependencies, and execution order.
Standard Action	A basic execution unit with explicit input, output, state, error, and audit semantics.
Capability Registry	The mechanism used to discover, select, and invoke registered capabilities.
ContractReady	The data passes the applicable interface checks. Read the scope, version, and report; this does not establish that solving has completed.
SolverReady	A particular dataset-and-capability combination meets the integration requirements of its entry point or report. This does not establish a feasible solution or optimality for a new run.
Baseline Run	A complete run retained before adjustment for later comparison.
Rerun	A new run after changing a limited set of objectives, rules, or resource settings.
Structural Constraint	A constraint expressed by business facts such as routes, capacity, calendars, shifts, and BOM.
Objective Preference	A governed preference for delivery, load, inventory, waiting, changeovers, or another outcome.
Shop-floor Rule	An explicit control derived from operating experience, bottlenecks, priorities, or management agreement.
objective_system	The module governing objective items, direction, weight, scope, and audit information.
marginal_control / Operational Rule Control	The module expressing operational rules, bottlenecks, agreed policies, and experience-based controls. Existing material also calls it marginal control. Producing a rule proposal and applying it to solving are separate steps.
planning_system	The module organizing plan deviations, signals, releases, and cross-cycle linkage.
PlanBias	A plan-deviation value representing demand, capacity, material, or execution impacts.
PlanSignal	A signal routing deviations into objective, rule, release, or scheduling candidates. Receiving actions, configuration, and approval determine whether they are applied.
Release Package	A standard input containing confirmed tasks and conditions ready for downstream scheduling or execution.
Objective Material	A record of objective direction, unit, object granularity, and calculation semantics used for execution and audit.
Controlled Solving	Model execution within explicit data, constraints, objectives, rules, resource limits, and authorization scope.
Operation-level BOM	Material requirements tied to the consuming operation, with a material, consumption basis, and priority. The operation's planned time determines when the material is required.
Material Readiness	Whether a task has the required materials at the specified operation and time position.
Computable Business Semantics	Data whose objects, relationships, units, and constraints can enter an executable decision chain.

Data and Quantities

Term or field	Meaning
Standardized data interface	Shared manufacturing objects, field meanings, relationships, and exchange conventions. A database template is one concrete representation.
Data contract	Agreed input/output objects, types, units, and validation requirements. This is distinct from a commercial agreement; code identifiers containing contract retain their names.
Product	A finished item, intermediate item, or component used as a planning object.
Process route	Operations and their relationships for a product. A product may have several candidate routes.
Operation	A processing step. operation_number identifies it within a route; seqno expresses order. Equal sequence values impose no precedence by themselves.
Work center	An abstraction of a machine, machine group, team, subcontractor, or organizational resource. Hierarchy supports attribute inheritance, rules at different levels, and aggregate analysis.
Time unit	A discrete window relative to the planning origin. id is a reference, offset expresses sequence position, and scale is the duration in seconds.
time_unit.status	1 means normally available, 0 unavailable, and -1 special or optional. Configuration must define whether an optional period is used.
capacity.used	The fraction of a work center's period already occupied or unavailable, from 0 to 1, including maintenance accounted for on that basis. It is not utilization calculated from the new plan.
Output per cycle	For discrete processing, productivity is output from one processing cycle. For continuous processing it is output per unit time, with explicit units and conversion.
Batch size	Output quantity processed as a batch. In discrete processing it must be an integer multiple of output per cycle; it is not the multiplier itself.
OEE	Overall equipment effectiveness. The current template defaults to 100 and uses a percentage representation. Account for the loss once, through effective capacity or occupied time as defined.
Material consumption per output unit	Material required per unit of operation output. State the output basis and material unit; processing-cycle counts are not output quantities.
Cumulative receipt bounds	inventory_limit.upper_bound_acc/lower_bound_acc constrain cumulative receipts up to a time point, derived from opening inventory, flows, and stock requirements. They are not closing stock balances.
Material availability	Material available at a specified time. Period increments, cumulative supply, and inventory after consumption require distinct mappings.
Joint processing	A processing cycle produces related operation or product outputs, expressed through adaptor relationships.
Shared resource	Several work centers depend on the same limited resource. Express its dependencies, calendar, and usage conditions separately.
Planned output	planning_result.number is operation output, not a processing-cycle count. Adding outputs across operations does not establish finished-product delivery.

Execution and Evidence

Term	Meaning
Hard constraint	A condition that the current model requires a solution to satisfy.
Soft constraint	A condition whose violation is permitted and assigned a cost under an explicit rule.
Objective weight	A coefficient expressing a trade-off. Its weighted contribution is not elapsed time, output quantity, or actual cost.
Feasible solution	A candidate satisfying the current model's hard constraints. Review business facts and execution conditions before use.
Proven infeasible	The solver has proved that the current model and inputs admit no solution satisfying the hard constraints.
No feasible solution found	The search has not obtained a feasible candidate. This alone does not prove infeasibility.
Time limit reached	Search ended at its time limit, with or without a feasible incumbent.
Optimal solution	A solution with an optimality proof under the stated model, objective, and solver tolerances. A selected best candidate is not automatically optimal.
Worked example	A result derived manually under explicit assumptions, identified separately from an actual software run.

References: Data objects and fields · Data readiness · Runtime status and limits.