Skip to content
English
Contact us
  • There are no suggestions because the search field is empty.

Content Bundle Description Continuous Monitoring

Feature descriptions and license conditions

1. Purpose

Continuous Monitoring Content Bundles enables customers to operate a defined number of controls within the zapAnalytics platform in a Continuous Monitoring setup.

The Content Bundles are designed to:

  • execute controls on a recurring basis (typically monthly),
  • monitor business and compliance risks across organizational units.

2. Concept Overview

Continuous Monitoring Content Bundles are based on three core principles:

  1. Licensed Control Set
    The customer purchases a Control Set containing a defined control volume (e.g. 50 controls).
  2. Continuous Execution
    Controls are executed repeatedly over time (e.g. once a month).
  3. Operationalization via Control Instances
    Controls are applied to specific business contexts without modifying the underlying logic.

3. Scope

This product description defines:

  • the purpose and functional scope of Continuous Monitoring Content Bundles
  • the features available for activation by a Content Bundle depending on the Agent Team

This product description does not define:

  • generic features or requirements of zapAnalytics, which can be found in the Product Description zapAnalytics
  • general zapAnalytics license conditions and cooperation obligations, which can be found in the Product Description zapAnalytics
  • generic features or requirements of zapHome
  • generic capabilities or requirements of zapAgents or Agent Teams
  • Customer Success services
  • Training and Consulting services
  • Custom Development services

These are not part of Continuous Monitoring Content Bundles. They are defined in their respective product descriptions.

4. Definitions

4.1 Control

A control is a recurring monitoring logic executed within the zapliance zapAnalytics platform to identify relevant findings in business or compliance processes.

Controls are typically based on:

  • zapliance standard indicators, or
  • custom-developed indicators (if separately commissioned)

4.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 execution frequency are defined in the commercial agreement.

The licensed Control Set represents a usage entitlement (“voucher model”) to run the defined controls during the subscription period.


4.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 (analysis logic)
  • 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.


4.4 Execution Cycle

An execution cycle defines the recurring interval at which downloads, data processing, and result generation may be automatically executed via batch run. The execition cycle period is defined in the commercial agreement. If the commercial agreement provides a frequency restriction, the listed frequency is considered the minimum. 

5. Control Set Management

The licensed Control Set defines which controls are executed via Continuous Monitoring Content Bundles. The Control Set may contain:

  • standard controls provided by zapliance
  • custom-developed controls previously delivered to the customer

The customer and zapliance jointly define the initial composition of the Control Set.

Control Set Changes

Standard controls included in the Control Set are not permanently fixed and may be replaced by other standard controls within the licensed control volume. The frequency of such Control Set changes is defined in the commercial agreement.

Custom-developed controls may also be included in the Control Set once they have been delivered as part of a separate custom development project.

The modification or development of custom controls is not part of the subscription and constitutes a separate service. 

6. Operational Model

Typical execution flow:

  1. Selection of Control Set
  2. Creation of Content Bundle
  3. Definition of Control Instances
  4. Data extraction and processing
  5. Result generation per Control Instance
  6. Storage and comparison
  7. Evaluation and analysis

The system generates results per Control Instance, enabling granular monitoring.

7. Subscription Coverage

Included in the subscription

Continuous Monitoring Content Bundles provide the right to execute the licensed Control Set within the agreed execution cycle (e.g. 50 controls / month). The Control Set might include:

  • standard controls
  • custom-developed controls (once delivered)

It also includes the right to select the standard controls to be included in the initial Control Set and subsequent Control Set changes as described above.

Not included in the subscription

The subscription does not include the development of custom controls. Custom indicator or control development:

  • is a separate service
  • is handled as a dedicated development project
  • is estimated and charged independently

Custom-developed controls:

  • must be created through a separate development engagement
  • are delivered as ready-to-use Content Bundles
  • can then be executed within the subscription

8. Customer Responsibilities and License Conditions

The following general prerequisites apply when using the Content Bundle:

  • the contractually agreed zapHome setup must be deployed and operational
  • the zapAnalytics environment must be available
  • the agreed Agent Team must be operational
  • the availability of the agreed SAP data scope must be ensured
  • Control Set must be defined together with zapliance
  • Control Instances must be defined and maintained
  • all necessary technical, organizational, and governance requirements must be fulfilled

The use of the Content Bundle is governed by the commercial agreement details, including:

  • the zapHome setup
  • the selected Agent Team
  • the agreed project type
  • the agreed project scope (SAP clients, company codes, fiscal years, frequency)
  • the agreed service start date, service period and minimum term

Any restrictions regarding SAP data scope, analysis scope, output scope or frequency defined in the commercial agreement apply to the Content Bundle.

In the event of any conflict between this product pescription and the commercial agreement, the commercial agreement shall prevail. 

9. Features Available by Agent Team

Continuous Monitoring Content Bundles can activate a range of management, SAP data extraction, data processing, and output functionalities. The specific features activated depend on the contractually agreed Content Bundle details such as Control Set and project stope, as well as the selected Agent Team.

Detailed feature descriptions can be found in this article: Product Description zapAnalytics

Note: Agent Teams Wolfgang and Wolfgang + Wilma are not capable of executing Continuous Monitoring Content Bundles.

Feature

Wolfgang

Werner

Wolfgang + Wilma

Werner + Wilma

Wickie + Wilma

Management

 

 

 

 

 

Workspace Management

❌

✅

❌

✅

✅

Workspace API Management

❌

✅

❌

✅

✅

Workspace User Management

❌

✅

❌

✅

✅

Project Creation

❌

✅

❌

✅

✅

Project Management

❌

✅

❌

✅

✅

Project Scheduler

❌

✅

❌

✅

✅

Database Management

❌

✅

❌

✅

✅

SAP Connection Management

❌

✅

❌

✅

✅

Data Extraction

 

 

 

 

 

One-off Standard SAP Data Extraction (Standard Download Plan)

❌

❌

❌

❌

❌

Continuous Standard SAP Data Extraction (Standard Download Plan)

❌

✅

❌

✅

✅

Custom SAP Data Extraction (Custom Download Plan)

❌

✅*

❌

✅*

✅*

Batched SAP Attachment Download

❌

✅

❌

✅

✅

Data Processing

 

 

 

 

 

Process Labeling

❌

✅

❌

✅

✅

One-off Standard Indicator Processing (Standard Processing Plan)

❌

❌

❌

❌

❌

Continuous Standard Control Processing (Standard Processing Plan)

❌

✅

❌

✅

✅

Custom Control Processing (Custom Processing Plan)

❌

✅*

❌

✅*

✅*

ML Algorithm-based Processing

❌

✅

❌

✅

✅

Batched SAP Data Processing

❌

✅

❌

✅

✅

Batched LLM Attachment Analysis

❌

✅

❌

✅

✅

Output

 

 

 

 

 

One-off Standard Outputs (Standard Result Plan)

❌

❌

❌

❌

❌

Continuous Standard Outputs (Standard Result Plan)

❌

✅

❌

✅

✅

Custom Outputs (Custom Result Plan)

❌

✅*

❌

✅*

✅*

Power BI Templates (.pbit)

❌

✅

❌

✅

✅

Source Files for Power BI Dashboards (.parquet)

❌

✅

❌

✅

✅

Excel File per Indicator with Marked SAP Documents

❌

✅

❌

✅

✅

Pseudonymization of Results

❌

✅

❌

✅

✅

Interfaces

 

 

 

 

 

Link to SAP Documents (Web GUI/Fiori) in Power BI Dashboards

❌

✅

❌

✅

✅

Wilma Link in Power BI Dashboards

❌

❌

❌

✅

✅

REST API Access

❌

✅*

❌

✅*

✅*

MCP Server Creation & Management

❌

❌

❌

✅

✅

Result Transfer to MCP Server

❌

❌

❌

✅

✅

Web Search (via Azure OpenAI)

❌

❌

❌

❌

✅

VAT ID Validation via Endpoint Connection (BZSt & VIESS)

❌

❌

❌

❌

✅

Legend:

✅ = Feature available in a Continuous Monitoring Content Bundle for this Agent Team. Activation depends on contractually agreed Content Bundle details (such as Control Set).

❌ = Feature not available in a Continuous Monitoring Content Bundle for this Agent Team.

✅* = Custom Feature available for this Agent Team as part of a Custom Content Bundle. Only activated if explicitly included in the commercial agreement. May require a custom development project that is charged separately.

Note on Custom Indicator / Control Development

The development of customer-specific indicators or controls tailored to individual business and compliance requirements within zapAnalytics constitutes a separate, dedicated development project not included in the Continuous Monitoring subscription.

Development process
  • Analysis and definition of functional, technical and stakeholder requirements in collaboration with the customer
  • Design and implementation of the indicator/control logic (Download Plan, Processing Plan, Result Plan)
  • Creation and delivery of all necessary content bundles
  • Technical testing and quality assurance
  • Validation of detection results with customer stakeholders
  • Refinement and optimization based on validation feedback
  • Deployment to the production environment and go-live support

 

Additional customer responsibilities apply.

Deliverable

A fully tested and production-ready custom control delivered as a Content Bundle for the zapAnalytics platform.

Costs

The development and implementation effort is estimated and charged in person-days based on the agreed scope and complexity of the requirements.


In addition to this Product Description, the Product Descriptions of all components included in the offer, contractual or commercial agreement apply.

The General Terms and Conditions (GTC) of zapliance in their currently valid version apply.