Product Description Agentic Team Solution Continuous Control Monitoring
License Coverage, Operating Model and Functionality of the Continuous Control Monitoring Subscription
|
Version |
2.0 |
Valid from |
25 September 2026 |
1. Governance Objective
The Continuous Control Monitoring Subscription enables the recurring execution of data-driven analyses within the zapliance zapAnalytics Platform to identify indications of potential risks, anomalies, and compliance issues.
It provides a scalable framework for continuous monitoring of business and compliance processes through the recurring execution of controls.
2. Target Users
Continuous Control Monitoring is intended to support organizations operating recurring controls as part of their governance, risk management and internal control framework.
Typical users are functions within the first and second line of defence that are responsible for the execution, supervision, evaluation or follow-up of control activities.
This may include, for example:
- internal control management
- compliance functions
- risk management functions
- accounting functions
- control owners and other business functions with control responsibilities
Continuous Control Monitoring is not an Internal Audit solution. Organizations seeking to perform recurring audit activities should refer to the Continuous Auditing solution.
3. Accountability
zapliance provides information. The customer evaluates and decides.
Continuous Control Monitoring provides data-driven indications and supporting information based on predefined control logic and analysis rules.
The evaluation of these indications remains the responsibility of the customer.
The customer is responsible for determining whether a result represents a relevant finding, risk, control deficiency, compliance issue or other business concern, and for deciding on any actions to be taken.
Continuous Control Monitoring supports human decision-making but does not replace professional judgement.
4. Execution Model
Continuous Control Monitoring is based on recurring execution cycles.
An execution cycle defines the recurring interval at which downloads, data processing and result generation may be automatically executed via batch run.
Typical execution cycles may be:
- daily
- weekly
- monthly
Continuous Control Monitoring transforms one-time analyses into a continuous, repeatable monitoring process.
The selected execution cycle determines how frequently new data is processed and new indications are identified.
The selected execution cycle is defined in the commercial agreement.
5. Team Variants
Continuous Control Monitoring is available with the following Agent Teams:
| Agent Team | Availability for Continuous Control Monitoring |
|---|---|
| Werner | Available |
| Werner + Wilma | Available |
| Wickie + Wilma | Available |
Recommended configurations:
| Agent Team | Description |
|---|---|
| Werner | Standard configuration without AI-supported analysis. |
| Werner + Wilma | Standard configuration with AI-supported analysis. |
| Wickie + Wilma | Extended configuration with additional AI and integration capabilities. |
The features available for each Agent Team are defined in the corresponding Product Descriptions.
6. Core Concepts
6.1 Control
A control is a recurring monitoring logic executed within the zapliance zapAnalytics platform to identify relevant indications in business or compliance processes.
Controls are typically based on:
- zapliance standard indicators
- custom-developed indicators
Controls based on custom-developed indicators may also be included in the Control Set once they have been delivered as part of a separate custom development project.
6.2 Control Set
A Control Set defines the number of controls the customer is entitled to operate.
Example: A "50 controls" set allows running up to 50 controls per execution cycle.
The licensed Control Set may contain:
- zapliance standard controls
- custom-developed controls
The exact number of controls and the execution cycle are defined in the commercial agreement.
6.3 Control Instance
A Control Instance represents the operational application of a control within a defined business context.
A Control Instance is defined by the combination of:
- control
- company code or organizational unit
- control owner
- filters and business interpretation
It allows a single control logic to be reused across multiple contexts without changing the underlying code or analysis logic.
Controls only become operational through Control Instances.
7. Control Set Changes
Controls included in the Control Set are not permanently fixed and may be replaced by other controls within the licensed control volume, subject to the terms defined in the commercial agreement.
The frequency and conditions of such Control Set changes are defined in the commercial agreement.
8. Subscription Coverage
Included
- execution of the licensed Control Set according to the agreed execution cycle
- provision of recurring monitoring results
Not Included
- development of new indicators or controls
- modification of the underlying logic of existing standard or custom controls
- ad-hoc or on-demand analyses outside defined cycles
- system integration beyond agreed scope
9. Contractual Service Parameters
The following parameters are defined in the commercial agreement and determine the scope and operating model of the Continuous Control Monitoring subscription.
9.1 Service Configuration
| Service Configuration Parameter | Definition |
|---|---|
| Agent Team | Selected Agent Team and included functionality (Werner, Werner + Wilma, Wickie + Wilma) |
| Control Set | Number of controls included in the subscription |
| Execution Cycle | Frequency of recurring execution (e.g. daily, weekly, monthly) |
| SAP Scope | Included SAP systems, clients and company codes |
| Rollout Schedule | Planned activation schedule for controls and control groups |
9.2 Service Conditions
| Service Condition | Definition |
|---|---|
| Service Start Date | Date from which recurring execution begins |
| Contract Term | Duration of the subscription |
| Control Set Change Frequency | Frequency at which Control Set changes may be requested (e.g. monthly, quarterly, annually) |
| Required Notice Period |
Minimum notice period for requested Control Set changes (e.g. 30, 60 or 90 days) |
10. Result Presentation
Continuous Control Monitoring results are provided through dedicated reporting and analysis interfaces.
Depending on the selected Agent Team, results may be provided through:
- Power BI dashboards for visualization, filtering and analysis of monitoring results.
- AI-supported interfaces for the exploration, explanation and prioritization of monitoring results.
The available result presentation options depend on the selected Agent Team.
11. Change History
|
VERSION |
VALID FROM |
CHANGE |
STATUS |
|
2.0 |
25 September 2026 |
Added governance framework, execution model, team variants, core concepts, subscription coverage, contractual service parameters and result presentation. |
Active |