Process & Workflow
Repeatable multi-step activities
Bundle → Layer → Finding → Questions Incomplete
3 bundles · 8 layers · 0 findings · 0 questions
definition The repeatable model of the work
processModel
steps, gateways and sequence flow
roleAssignment
which roles perform which steps
stateModel
allowed states and transitions of the governed thing
execution Running the model in the world
caseInstance
one running occurrence of a process
stepPerformance
executed steps recorded as acts
exceptionHandling
deviations, escalations and compensations
improvement Learning from executions
measurement
cycle times, throughput and conformance of instances
revision
versioning and change of definitions
Note: Legacy card: layers named, findings and questions never written.
Classifiers Filled
- Family
- World Models
- Category
- Activities and processes
- Entry kind
- standalone-mm
- Navigation path
- NAV.ACT.PRC
- Domain
- ACT.PRC
- Industry
- Cross-industry
- Tags
- processworkflowact.prc
- Also called
- K3
What it is Derived, awaiting review
This meta-model describes repeatable multi-step activities: the process definitions that say how work flows through steps, roles and states, and the running instances that follow (or deviate from) those definitions.
Note: First sentence of the legacy card introduction.
Why it exists Filled
Repeatable multi-step activities
Distinguishing features Missing, in the backlog
Not described yet. This gap is in the card backlog.
What robots and AI may and may not do Missing, in the backlog
Not described yet. This gap is in the card backlog.
Moral aspects Missing, in the backlog
Not described yet. This gap is in the card backlog.
Owners Filled
Steward
The process owner, an organization or an individual agent, owns definitions and their instances' records.
Links to other meta-models Filled
references
- world.actAction - every step execution resolves to an atomic act
- world.functionAndCapability - roles state capability requirements resolved against agent capabilities
- world.practiceMethodAndProcedure - processes operationalize codified methods and procedures
- world.organization - the process owner and the organizations supplying performers
imports
- bpmn - ALIGN: notation and execution semantics for the process model layer
- cmmn - ALIGN: case management semantics for weakly structured workflows
requires
- vr.wm-act-002
- vr.wm-act-009
- vr.wm-per-009
What else AI and robots need to interact with it Incomplete
Identity and identifiers required Missing, in the backlog
Not described yet. This gap is in the card backlog.
Direct properties not applicable Not applicable
Not applicable
Institutional or informational subject: no invented physical properties.
Recognition optional Missing, in the backlog
Not described yet. This gap is in the card backlog.
Capabilities and actions required Derived, awaiting review
- processDefined: a new process definition or version was published
- instanceStarted: an execution of a process began for a subject
- stepCompleted: a step within an instance finished, with performer and outcome
- deviationRaised: an execution departed from its definition and the departure was recorded
- instanceCompleted: an execution reached a terminal state
- processRevised: a definition was changed and a new version released
Legacy events listed as state transitions.
Hazards and failure modes optional Missing, in the backlog
Not described yet. This gap is in the card backlog.
Standards and interfaces required Derived, awaiting review
- definitionAccess: a consumer reads process definitions and versions, without execution data
- executionMonitoring: an authorized party observes instance states and step completions for defined processes
- benchmarkExchange: aggregated cycle-time and conformance measures are shared in de-identified form
- swimlaneView: the definition arranged by role; omits execution history
- statusBoard: live instances by state and age; omits step-level detail
- performanceDigest: throughput, cycle time and deviation rates per version; omits individual cases
Context of use required Filled
- Consumers gain access through owner-granted contracts under the catalogue's ownership and access models (S1/S2), with audit via S4.
Sources Missing, in the backlog
Not described yet. This gap is in the card backlog.
Open questions
- Superseded by a researched world model? Map this legacy card to its successor or retire it.
Machine files
Provenance
legacy MMAS card (world-models v0.2) · legacy
Built from: models/world-k3-process-and-workflow/spec.yaml, models/docs/activity-work/K3-process-and-workflow.md