Explanation:

Business Process Management (BPM) is a discipline focused on designing, documenting, executing, monitoring, and continuously improving business processes to achieve operational excellence and business agility.

Option A (Correct): To monitor and control processes
BPM enables organizations to track process performance, ensure compliance, and control execution through defined rules, KPIs, and governance mechanisms. Monitoring is essential for identifying deviations and improvement opportunities.

Option C (Correct): To document processes
Clear and standardized process documentation is a core goal of BPM. It ensures transparency, shared understanding, compliance, onboarding efficiency, and serves as the foundation for analysis and optimization.

Option E (Correct): To measure processes
BPM relies on process measurement using KPIs such as cycle time, cost, throughput, and quality. Measurement is critical for data-driven decision-making and continuous improvement.

Why the other options are incorrect

Option B (Incorrect): To save processes
Simply storing or saving processes is not a BPM goal. While repositories exist, BPM focuses on managing and improving processes, not just archiving them.

Option D (Incorrect): To share processes
Sharing is a supporting capability, not a primary BPM goal. The objective is to enable improvement and governance, with sharing being a means rather than an end.

References:
SAP Help Portal – SAP Signavio Business Process Management Overview
SAP Learning – Business Process Management with SAP Signavio
SAP Documentation – BPM Lifecycle: Design, Model, Analyze, Improve

Explanation:

The BPMN (Business Process Model and Notation) token concept is a fundamental theoretical execution model. An imaginary "token" moves through the sequence flows of a process model, following the defined logic (gateways, events, tasks) to simulate and explain the runtime behavior of a single process instance. It clarifies how a case progresses, where parallel paths are taken, where the token waits at events, and how merging occurs. This conceptual tool is vital for validating that a process model is logically sound and executable.

Why the other options are incorrect:

B. Visualizes the distribution of information:
While tokens can carry data, their primary purpose is not to visualize information distribution. Data objects and data stores in BPMN are the explicit notation for visualizing information flow. The token is an abstract concept for path execution.

C. Shows IT-system support and automation potential:
This is the purpose of lane assignments (e.g., separating "Customer," "System," or "CRM Application" lanes) and task types (e.g., manual vs. service tasks), not the token concept. The token does not distinguish between manual and automated steps in its flow logic.

D. Determines a complexity score:
Process complexity is measured through metrics like Cyclomatic Complexity or by counting elements/gateways. The token concept is a simulation tool for understanding flow, not a quantitative scoring mechanism.

References:
OMG BPMN 2.0 Specification: The official standard defines the token semantics as the "theoretical foundation for the execution semantics of BPMN."