factory Workflow Engine

The Control Center
for Your
Business Processes.

In technical control centers, systems react within milliseconds— automatically, rule-driven, and with complete traceability.
factory Workflow Software brings this principle to business processes: roles, permissions, and business rules are evaluated together— and translated into the most appropriate next actions.

Request a Demo Explore All Workflow Types ↓

Turning Information into Action

Information drives action. Whenever statuses, values, or responsibilities change, the workflow engine automatically determines and initiates the next appropriate step— whether it's a notification, approval, follow-up task, or escalation.

Governed by Rules, Flexible in Execution

Each next step is predefined by the workflow and evaluated against status, attributes, and access rights. Within the permitted options, users retain the flexibility to guide the process—for example, by choosing the next responsible role or specific assignee.

Business-Configurable

Standard workflows, task-specific processes, and business metric-driven triggers can be combined according to each process requirement. This enables the creation of workflow logic tailored to the object, the task, and the organization.

Built on Control Center Experience.

1

The consulting company project biz, affiliated with factory, contributes the expertise of Dr. Manfred Fitzner from technical control centers ℹ: SCADA systems, industrial control technology, and automation systems.

2

There, system states are captured, values are validated, and actions are triggered—rule-based, fast, and fully traceable.

3

The key question for factory: How can this principle be transferred to human-driven workflows— to roles, decisions, approvals, and business responsibility?

The factory solution: Make control center logic easy to use— for clear, pragmatic, and effective workflows.
The factory Answer

Control Center Principles for Workflows

→
People in the Driver’s Seat The assigned user controls the next step using the available options.
→
Rules Combined with Flexibility Defined workflows and individual process control work together.
→
Attributes as Triggers Budget, status, priority, or due dates trigger automated actions.
→
Actions Within the Process Notifications, approvals, or task dialogs are initiated at the right point in the workflow.
→
Permissions as Guardrails Only authorized roles and users are included in the process.
The Foundation

Three Layers. One Interaction.

Only when objects, workflow rules, and the permission model work together do actions emerge that are business-correct, object-relevant, and authorization-compliant.

1

Object Context

Every object carries business attributes—the "raw material" for every workflow decision.

  • Status, budget, priority
  • Owner, role
  • Due date, risk value
  • Organizational unit
2

Workflow Definitions

For each object type, stages, status transitions, notifications, and escalations are configured.

  • Allowed status transitions
  • Target roles & assignees
  • Budget thresholds & triggers
  • Approval & escalation rules
3

Permission Model

Which role may view, edit, approve, or block which attribute? The engine checks this automatically.

  • Attribute visibility by role
  • Edit & approval permissions
  • Automatic selection restrictions
  • Audit-proof logging
Workflow Building Blocks

Six Control Models. Usable Individually. Combinable.

factory Workflow Software supports different workflow control models— usable individually or connected with each other. This creates process control that fits the organization exactly.

1

Standard Workflow

Workflow stages and allowed status transitions are configured. With every transition, the engine automatically triggers the appropriate action.

Draft → Review → Approval → Order → Billing
2

Budget-Based Workflow

Approvals are controlled based on value thresholds. The engine automatically determines the responsible role and notifies the right person.

up to €9,999 → direct processing · €10–25k → department management · above €25k → executive approval
3

Assignee-Based Workflow

The assigned user selects the next person responsible—but only from the options allowed by the permission model. No unrestricted forwarding, but guided decision-making.

Select role → Select person → Engine handles notification, link, and form
4

Change-Triggered Workflow

Changes initiate actions. As soon as budget, status, priority, due date, or a metric reaches a defined trigger value, the responsible person is informed.

Budget > €1M → notify executive team · Error count rises → QA manager · Priority = high → project manager
5

Permission-Driven Workflows

The workflow engine incorporates the permission model: At every step, roles, assignees, and actions are guided according to the task and authorization level.

Processor → Cost planning · Manager → Budget approval · External user → Read-only access to selected fields
6

Workflow Orchestration

The engine combines all control models into one guided process. Object status, attributes, roles, permissions, and changes are evaluated together to determine the right next step.

Status + Attribute + Role + Permission + Trigger → Action

Combining All Workflow Types

Document follows a classic review and approval process. Project additionally triggers budget-based approvals. Task is automatically forwarded to an assignee when its status changes. Asset starts an escalation process when critical attribute changes occur. —
The factory Workflow Engine turns tables, attributes, roles, and status values into active process control.

Which Process Should the Workflow Software Control?

Send us a brief description of your use case. We will show you how the Workflow Engine can map and optimize your process.

Start Inquiry