Introduction

BizOps Engine is the workflow automation product inside the BizOps suite. It lets teams design, configure, and run business operations workflows as visual graphs of steps — from signal ingestion and AI-assisted analysis through to remediation and hand-off actions.

What is BizOps Engine?

BizOps Engine organizes automation under a stable hierarchy:

Entity	Role
Project	Portfolio bucket for related automation (domain, criticality, status)
Process	Logical automation stream inside a project (trigger type, owner, health)
Job	Runnable configuration instance under a process (version, environment, runtime status)
Workflow	The step graph persisted for a job — steps, edges, metadata, and optional viewport

Unlike generic IT automation, BizOps Engine is oriented around business operations: triage, verification, remediation dry-runs, data ingestion into analytics stores, and outcome tracking.

Key Features

• Project → Process → Job hierarchy — Keep automation organized by business domain and ownership.
• Visual workflow canvas — Author directed graphs of steps with a catalog-driven palette.
• Action-type catalog — Configure steps from shared action definitions (source, logic, HTTP, remediation, and more).
• Step data hydration — Large or reusable payloads can be stored separately and merged at load time.
• Execution history — Inspect run traces, step outputs, and cycle history for each job.
• Microfrontend delivery — Runs inside the Qinfinite shell or standalone for local development.
• Orchyron-ready plugins — Action catalog bindings support plugin deployment for on-prem or Kubernetes execution.

How Automation Works

START

Create Project

Define the business portfolio and criticality

Add Process

Describe the automation stream and trigger style

Build Job Workflow

Place steps from the action catalog and connect edges

Run and Review

Execute the job and inspect step-level history

END

From project setup to monitored execution in one continuous authoring path.

How It Fits in BizOps

Capability	Product	What it does
Design and run business workflows	BizOps Engine	Projects, processes, jobs, action catalog, execution history
Visualize KPIs and operational health	Dashboard Hub	Hubs, dashboards, widgets, publish, and personal layouts
Platform outcome model	Platform BizOps	Business impact framing across the Operate pillar

Dashboard Hub can consume BizOps-oriented data sources so workflow outcomes and operational metrics appear on the same decision surface.

Demo Scenario

The engine ships with a mock end-to-end narrative used for UI walkthroughs:

Kafka OTel Stream → AI Debug Scenario → Kill Process (Dry Run)

This path demonstrates source → logic → remediation configuration and deterministic run logs. It is simulation only unless your deployment wires real Kafka, AI, or process-control backends.

Next Steps

• Navigating BizOps Engine — Screen tour and route map
• Projects, Processes, and Jobs — Entity model in detail
• Building Workflows — Steps, edges, and configuration
• Architecture — Client, API, catalog, and execution shape