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

Product Description Continuous Monitoring

1. Purpose

The Continuous Monitoring Subscription enables the recurring execution of data-driven analyses within the zapliance zapAnalytics Platform to identify risks, anomalies, and compliance-relevant findings. It provides a scalable framework for:

  • continuous data extraction
  • automated processing
  • structured result generation
  • repeatable analysis over time

2. Concept Overview

Continuous Monitoring is based on:

  • recurring execution cycles
  • standardized data processing logic (controls)
  • centralized result generation and storage
  • scalable data architecture depending on data volume
Continuous Monitoring transforms one-time analyses into a continuous, repeatable monitoring process.

3. Scope

This product description defines:

  • the purpose and scope of the the Continuous Monitoring Subscription

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

They are defined in their respective product descriptions, along with the applicaple license conditions, cooperation obligations and customer responsibilities. 

4. Definitions

4.1 Continuous Monitoring

Continuous Monitoring refers to the recurring execution of predefined analyses on business data within defined intervals.


4.2 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. 


4.3 Content Bundle
A Content Bundle represents the technical configuration (typically .zip file) used to execute Continuous Monitoring. It includes:
  • data extraction logic
  • data analysis logic (controls)
  • result generation logic

4. Subscription Coverage

Included
  • recurring data extraction from connected systems
  • recurring data processing
  • recurring generation of structured result datasets
  • enabling comparison across execution cycles (delta analysis)
  • provision of results for downstream consumption

Details of data extraction, processing, and result generation are governed by the Content Bundle Description Continuous Monitoring.

Not Included
  • development of new indicators or controls
  • modification of underlying logic
  • ad-hoc or on-demand analyses outside defined cycles
  • unlimited data processing beyond agreed limits
  • system integration beyond agreed scope

5. Data Volume and Output Architecture

Continuous Monitoring supports different data consumption models depending on data volume and system setup.

Small to Medium Data Volumes
For smaller datasets:
  • results can be provided as files (e.g. Parquet)
  • analysis can be performed using local tools (e.g. Power BI PBIX)

Large Data Volumes
For large datasets:
  • local file-based approaches may reach technical limits
  • performance constraints may occur
  • distribution of large files may be impractical

Scalable Architecture
For larger or enterprise-scale scenarios:
  • results are provided via centralized data storage (e.g. databases or data platforms)
  • structured querying and multi-user access is enabled
  • reporting tools connect directly to the data layer

Output Formats
Results may be provided as:
  • file-based datasets (e.g. Parquet)
  • structured database tables
  • integrated reporting datasets
The selected architecture depends on:
  • data volume
  • number of users
  • performance requirements

Technical Limits
Continuous Monitoring operates within defined technical limits. These include:
  • maximum data volume per execution cycle
  • system-specific performance constraints
The exact limits are defined in the commercial and technical specification.


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.