Process-Aware Information System (PAIS) & BPMS

A Process-Aware Information System (PAIS) is any software system that manages and executes operational processes involving people, applications, and information sources on the basis of explicit process models (sources/2018-dumas-fundamentals-of-bpm, ch. 9).

Taxonomy of PAIS (§9.1)

Domain-specific PAIS — ERP, CRM, etc. Process logic is embedded in the application.
Process-agnostic PAIS — BPMS (Business Process Management System). Process logic is explicit, modifiable, enacted by a generic engine.
ACNS (Ad-hoc Case Notification System) — hybrid for knowledge work.

BPMS architecture (§9.1.3)

Typical components:

Execution engine — interprets executable process models and drives case progression.
Worklist handler — routes human tasks.
Administration & monitoring tools — runtime dashboards, audit.
Model repository — versioned process models.
External system connectors — integrations to ERP, CRM, messaging, etc.

Advantages of introducing a BPMS (§9.2)

Workload reduction
Flexible system integration
Execution transparency
Rule enforcement

Challenges (§9.3)

Technical — integration with legacy systems, data mapping.
Organisational — change management, resistance to standardisation.

Relation to APM

PAIS/BPMS is the pre-agentic execution infrastructure that APM reshapes. sources/2026-calvanese-agentic-bpm-manifesto (challenge A3) asks how a legacy ABPMS exposes itself as an agent — a research challenge about wrapping existing BPMS components so that agentic oversight can be layered on top.

A BPMS's rule-enforcement role maps onto operational framing; APM adds a normative-framing layer above that.

concepts/bpm-lifecycle · frameworks/bpmn · concepts/agentic-bpm · concepts/framed-autonomy