Statement of work

1.Entity Extraction API

1 Description of service

We offer Software as a Service solutions with modern cloud infrastructures. Our API services are designed to integrate with our customers’ cloud and on-premise solutions. ISR Information Products AG offers business and technical services as Software as a Service subscriptions on the Amazon Web Services Marketplace. All our services offer REST APIs for easy integration. Our customers, partners and solution providers can use our services with low investment because they have low-cost pay-per-use licenses.

Our offer is based on the powerful Amazon Webservices, AWS for short, infrastructure and the associated scalability with hosting in the available regions of AWS.

Buildsimple currently supports the following AWS regions:

EU (Frankfurt) eu-central‑1 rds.eu-central‑1.amazonaws.com HTTPS
USA East (Northern Virginia) us-east‑1 rds.us-east‑1.amazonaws.com HTTPS

Bestfit payment models such as “pay per use” or plannable packages guarantee the necessary flexibility.

The Entity Extraction API is a business service for reading predefined data from German and English documents. A complete list of all potentially extracted entities can be found in the API documentation. The service uses a deep learning-based approach to identify the business type of each document and determine the correct neural network that can be read to business units from the document. Supported business types of documents are invoices and contracts. The result of the extraction process is a JSON stream that can be pulled from the AWS memory by a separate API call. Optionally, we provide our partners with callback functionality to be notified immediately when the result is generated, so that no query for results is required.

1.1 Technology

We use deep learning technologies to classify documents, extract entities and validate possible outcomes. Through this machine learning approach, the quality of the extraction is not affected by different document layouts. Neural networks are based on weighted decision processes from trained models, including our invoice and contract documents. Buildsimple used a very large number of different invoice and contract documents to achieve well-trained models and high extraction quality for new and unknown documents compared to layout-based extraction products. Continuous training processes guarantee a continuous improvement of our extraction quality.

1.2 Supported file types

You can upload one of the following file types using the API: PDF, TIF, JPG. If an unsupported file type has been uploaded, the service will not produce a valid result and the caller will receive an error code. The file size must not exceed 10 pages and 10 MB.

1.3 Classification

When a document is uploaded via the API, it is automatically classified into one of the document types defined by the customer. The upload API allows you to specify the document type by setting a document type parameter. Details are described in the API documentation.

1.4 Languages

The Entity Extraction API supports the extraction of documents in German and English. Other languages can be activated after consultation with Buildsimple.

1.5 Quality of Extraction

The extraction quality varies due to several factors.

The quality of the images, scans, or digital documents affects the OCR result that forms the basis for entity extraction. Documents in different languages lead to different qualities. Since we do not know the input documents, we cannot guarantee a certain extraction quality.

1.6 Result of the classification process

The result is provided as a JSON object for a duration of 8 hours and can be queried via a separate REST API call. After the 8‑hour retention period has expired, the extraction result is irrevocably deleted. Access to the extraction result is secured by authentication with the AWS token and its connection to the AWS account of the customer or partner.

1.7 Storage of Data

In addition to storing the extraction result for 8 hours as mentioned in point 16.6, document information is temporarily stored during processing to perform the various processing steps. The data cached for the processing of a document are irrevocably deleted immediately after the successful processing of a document. If a technical error occurs during the processing of a document, the buffered data is irrevocably deleted after one hour. It is guaranteed that the data will never be stored permanently after a document has been processed.

1.8 Encryption

The entire communication and processing chain within the AWS infrastructure is encrypted using SSL and HTTPS.

1.9 Marketplace Accounts

To subscribe to the Entity Extraction API via external marketplaces, such as the Amazon Webservices Marketplace or the Syncier Marketplace, the respective accounts are a prerequisite for the marketplace systems, since the usage is billed via the marketplace.

1.10 Further Requirements and Obligations for Cooperation

An active Internet connection is required to use the API. The customer / partner has access to the AWS Cloud and its API gateway.

The customer/partner provides a competent and authorized contact person for support questions.

The customer / partner independently monitors the consumption of a concluded package contract. ISR Information Products AG does not proactively inform about the achievement of a package limit.

The customer/partner undertakes not to intentionally transmit faulty documents to the API or intentionally use the API incorrectly.

The customer / partner is responsible for the transferred data / documents.

If one or more of the conditions stated here should not apply, ISR Information Products AG is not obliged to provide the service described with the agreed service levels.

As a rule, these cooperation obligations are provided in a quality that enables ISR Information Products AG to fulfil its contractual obligations without additional effort. ISR Information Products AG shall not be liable for delays in the provision of services and/or violations of the agreed service levels which are attributable to the non-fulfilment of the cooperation obligations by the partner/customer or which are not attributable to ISR Information Products AG.

1.11 Terms of contract

The contract duration varies depending on the billing model selected.

1.11.1 Pay per use billing model

The pay-per-use billing model has no predefined contract term. The customer/partner pays exactly for each processed document. The contract can be terminated at any time. A separate termination is not necessary.

1.12 Processing

1.12.1 Individual agreement

In the case of an individual contractual agreement, invoicing shall be effected via a monthly invoice from ISR Information Products AG. If the pay-per-use model is used, ISR Information Products AG consolidates the documents processed in one month, which form the basis for the monthly invoice. In the case of the use of a package quota, invoicing is carried out directly upon conclusion of the contract by means of an invoice for the package concerned.

1.13 Licensing

Apart from licensing the Entity Extraction API, ISR Information Products AG does not charge any license fees for the use of the API. The license is included in the respective contract, see point 5. All software products used are subject to the respective license conditions of the manufacturer.

1.1 Services

1.14.1 System Management & System Monitoring

The continuous monitoring of the system status by our DevOps team enables the early detection of critical server system states. In this context we carry out the following inspections:

Continuous, central monitoring of services
System event log control for critical system states and scaling of services
Control disk usage, processor and memory utilization

We monitor the services with AWS CloudWatch. The services are automatically scaled by Amazon Web Services based on the parameters defined by ISR Information Products AG.

1.14.2 Customer and Partner Support

The license price includes access to the ISR community, FAQs and a knowledge platform available to our customers and partners.

1.14.3 Incident Management (Service Interruption)

In the event of an incident, the Service Desk employee carries out the technical diagnosis and immediately tries to find a solution with the help of a knowledge database. The successful solution and the solution steps are documented and the incident is closed after the fault has been rectified. The customer is informed about the correction of the error. If an immediate solution is not possible, all previous measures are documented and the process is forwarded to subsequent instances (2nd level support or AMS). If the incident is forwarded, the Service Desk proactively monitors the incident over the entire service period to ensure compliance with the agreed service levels on the basis of a defined escalation process. Once an incident has been successfully resolved and the ticket has been closed in the system, the customer is informed.

1.15 SLA’s

1.15.1 Availability of the API

Despite the robust Amazon Web Services cloud infrastructure and comprehensive service quality assurance by ISR Information Products AG as well as uncontrollable quality gates, 100% uninterrupted availability of the Entity Extraction API cannot be guaranteed. The software development and operational processes of ISR Information Products AG guarantee a very high quality and stability of our services, so that we can reduce system downtimes to a minimum.

ISR Information Products AG cannot guarantee the availability of the API if the Amazon Web Services infrastructure is not fully or partially available.

The Amazon Web Services Infrastructure enables ISR Information Products AG to install new versions, patches and bug fixes without interruption. An interruption of the service is not required.

2.Classification API

2 Description of service

We offer Software as a Service solutions with modern cloud infrastructures. Our API services are designed to integrate with our customers’ cloud and on-premise solutions. ISR Information Products AG offers business and technical services as Software as a Service subscriptions on the Amazon Web Services Marketplace. All our services offer REST APIs for easy integration. Our customers, partners and solution providers can use our services with low investment because they have low-cost pay-per-use licenses.

Our offer is based on the powerful Amazon Webservices, AWS for short, infrastructure and the associated scalability with hosting in the available regions of AWS.

Buildsimple currently supports the following AWS regions:

EU (Frankfurt) eu-central‑1 rds.eu-central‑1.amazonaws.com HTTPS
USA East (Northern Virginia) us-east‑1 rds.us-east‑1.amazonaws.com HTTPS

Bestfit payment models such as “pay per use” or plannable packages guarantee the necessary flexibility.

The Classification API is a business service for classifying your business documents such as invoices and contracts. Our service provides an asynchronous API for document classification via two REST interfaces for document upload and result retrieval. The resulting document type is displayed in JSON format. A list of supported document classes and languages can be found in the API documentation.

2.1 Technology

We use deep learning technologies to classify documents. With this machine learning approach, the quality of the classification result is not influenced by different document layouts. Neural networks are based on weighted decision processes of trained models, also for our invoice and contract documents. Buildsimple uses a very large number of different invoice and contract documents to achieve high quality classification results for new and unknown documents compared to layout based classification products. Continuous training processes guarantee a continuous improvement of our classification quality.

2.2 Supported file types

You can upload one of the following file types using the API: PDF, TIF, JPG. If an unsupported file type has been uploaded, the service will not produce a valid result and the caller will receive an error code. The file size must not exceed 10 pages and 10 MB. Larger files must be transferred via a separate interface.

2.3 Classification

When a document is uploaded via the API, it is automatically classified into one of the document types defined by the customer. The upload API allows you to specify the document type by setting a document type parameter. Details are described in the API documentation.

2.4 Languages

The Classification API supports the classification of documents in German and English. Other languages can be activated after consultation with Buildsimple.

2.5 Quality of Extraction

Classification quality varies due to several factors.

The quality of images, scans or digital documents affects the OCR result, which is the basis for document classification.
Result that forms the basis for document classification.
Documents in different languages lead to different qualities.
Since we do not know the input documents, we cannot guarantee a certain quality of the classification result.

2.6 Result of the classification process

The classification result is provided as a JSON object for 72 hours and can be queried via a separate REST API call. After the 72-hour retention period, the classification result is irrevocably deleted. Access to the classification result is secured by authentication with AWS tokens and their connection to the customer’s or partner’s AWS account.

2.7 Data Storage

In addition to the storage of the 72-hour classification result referred to in point 16.6, document information is temporarily stored during processing in order to carry out the various processing steps. The data cached for the processing of a document are irrevocably deleted immediately after the successful processing of a document. If a technical error occurs during the processing of a document, the buffered data is irrevocably deleted after one hour. This guarantees that the data will never be stored permanently after a document has been processed.

2.8 Encryption

The entire communication and processing chain within the AWS infrastructure is encrypted using SSL and HTTPS. Cached document data is encrypted in sleep mode using a combination of server-side and client-side encryption.

2.9 Marketplace Accounts

To subscribe to the Classification API via external marketplaces, such as the Amazon Webservices Marketplace or the Syncier Marketplace, the respective accounts are a prerequisite for the marketplace systems, since the usage is billed via the marketplace.

2.10 Further prerequisites and obligations for cooperation

An active Internet connection is required to use the Classification API. The customer / partner has access to the AWS Cloud and its API gateway.

The customer/partner provides a competent and authorized contact person for support questions.

The customer / partner independently monitors the consumption of a concluded package contract. ISR Information Products AG does not proactively inform about the achievement of a package limit.

The customer/partner undertakes not to intentionally transmit faulty documents to the API or intentionally use the API incorrectly.

The customer / partner is responsible for the transferred data / documents.

If one or more of the conditions stated here should not apply, ISR Information Products AG is not obliged to provide the service described with the agreed service levels.

As a rule, these cooperation obligations are provided in a quality that enables ISR Information Products AG to fulfil its contractual obligations without additional effort. ISR Information Products AG shall not be liable for delays in the provision of services and/or violations of the agreed service levels which are attributable to the non-fulfilment of the cooperation obligations by the partner/customer or which are not attributable to ISR Information Products AG.

2.11 Terms of contract

The contract duration varies depending on the billing model selected.

2.11.1 Pay per use billing model

The pay-per-use billing model has no predefined contract term. The customer/partner pays exactly for each processed document. The contract can be terminated at any time. A separate termination is not necessary.

2.12 Processing

2.12.1 Individual agreement

In the case of an individual contractual agreement, invoicing shall be effected via a monthly invoice from ISR Information Products AG. If the pay-per-use model is used, ISR Information Products AG consolidates the documents processed in one month, which form the basis for the monthly invoice. In the case of the use of a package quota, invoicing is carried out directly upon conclusion of the contract by means of an invoice for the package concerned.

2.13 Licensing

Apart from licensing the Classification API, ISR Information Products AG does not charge any license fees for the use of the API. The license is included in the respective contract, see point 5. All software products used are subject to the respective license conditions of the manufacturer.

2.1 Services

2.14.1 System Management & System Monitoring

The continuous monitoring of the system status by our DevOps team enables the early detection of critical server system states. In this context we carry out the following inspections:

Continuous, central monitoring of services
System event log control for critical system states and scaling of services
Control disk usage, processor and memory utilization

We monitor the services with AWS CloudWatch. The services are automatically scaled by Amazon Web Services based on the parameters defined by ISR Information Products AG.

2.14.2 Customer and Partner Support

The license price includes access to the ISR community, FAQs and a knowledge platform available to our customers and partners.

2.14.3 Incident Management (Service Interruption)

In the event of an incident, the Service Desk employee carries out the technical diagnosis and immediately tries to find a solution with the help of a knowledge database. The successful solution and the solution steps are documented and the incident is closed after the fault has been rectified. The customer is informed about the correction of the error. If an immediate solution is not possible, all previous measures are documented and the process is forwarded to subsequent instances (2nd level support or AMS). If the incident is forwarded, the Service Desk proactively monitors the incident over the entire service period to ensure compliance with the agreed service levels on the basis of a defined escalation process. Once an incident has been successfully resolved and the ticket has been closed in the system, the customer is informed.

2.15 SLA’s

2.15.1 Availability of the Classification API

Despite the robust Amazon Web Services cloud infrastructure and comprehensive quality assurance of the service by ISR Information Products AG as well as uncontrollable quality gates, 100% uninterrupted availability of the Classification API cannot be guaranteed. The software development and operational processes of ISR Information Products AG guarantee a very high quality and stability of our services, so that we can reduce system downtimes to a minimum.

ISR Information Products AG cannot guarantee the availability of the API if the Amazon Web Services infrastructure is not fully or partially available.

The Amazon Web Services Infrastructure enables ISR Information Products AG to install new versions, patches and bug fixes without interruption. An interruption of the service is not required.

3.Document Verifier

3 Description of service

We offer Software as a Service solutions with modern cloud infrastructures. Our products and API services are designed to integrate with our customers’ cloud and on-premise solutions. ISR Information Products AG offers professional and technical services as Software as a Service subscriptions on the Amazon Web Services Marketplace. All our products offer REST APIs for easy integration. Our customers, partners and solution providers can use our services with low investment because they have low-cost pay-per-use licenses.

Our offer is based on the powerful Amazon Webservices, AWS for short, infrastructure and the associated scalability with hosting in the available regions of AWS.

Buildsimple currently supports the following AWS regions:

EU (Frankfurt) eu-central‑1 rds.eu-central‑1.amazonaws.com HTTPS
USA East (Northern Virginia) us-east‑1 rds.us-east‑1.amazonaws.com HTTPS

Bestfit payment models such as “pay per use” or plannable packages guarantee the necessary flexibility.

Document Verifier extracts all relevant data from unstructured documents. A dialog enables the verification and correction of the extracted data for quality assurance purposes. After approval by the auditor, the system makes the specialist data available to the subsequent systems such as ERP, CRM or specialist applications via an API.

3.1 Service elements

3.1.1 Access

Access to the application is via the following URLs:

https://verifier.buildsimple.de
https://verifier.us-east‑1.buildsimple.com

3.1.2 Receiving documents

The Document Verifier accepts image documents via a simple REST API. Alternatively, a user, e.g. the verifier himself, can transfer individual documents via a web browser.

3.1.3 Supported File Types

For files with more than 10 pages, only the first 10 pages are analyzed according to the Buildsimple Entity Extraction API performance specification.

REST Upload allows files up to 5 MB in size.

The following formats are supported: PDF, TIF, JPG.

3.1.4 Verification dialog

The documents are classified and technical properties are extracted. Which data is recognized depends on the document definition used. The document definition defines the document type with the domain properties.

The data determined by the Buildsimple Entity Extraction API is displayed in a dialog next to the original document. During the check, the selected properties are highlighted in the document so that the checker can compare them and correct the missing or incorrect data manually. Any verified documentation is re-introduced into the Entity Extraction API training data if the training function is activated, so that the extraction quality is continuously improved.

3.1.5 Provision of Verified Data

After completion of the manual verification process, the system provides the document with the properties via a REST API.

3.1.6 User Administration and Inbox

User management allows an administrator to register and manage additional users for the system. The inbox contains both personal and role-based documents to be verified.

3.1.7 User Profile

Every registered user has a user profile that contains all personal settings. Users can manage their accounts and delete their accounts.

3.1.8 Languages

The Document Verifier can be used in German and English.

3.1.9 Data Storage

After the manual verification process has been completed, the document is deleted. The result of the verification process is retained to be used for the Entity Extraction API course if the course function is activated. This data contains the OCR text and the corrected data units of the verified documents.

3.1.10 Encryption

The entire communication and processing chain within the AWS infrastructure is encrypted using SSL and HTTPS.

3.1.11 Conditions and Commitments for Cooperation

3.1.11.1 Marketplace Accounts & Entity Extraction API

For subscribing to Document Verifiers via external marketplaces, such as Amazon Webservices Marketplace or Syncier Marketplace, the respective accounts are a prerequisite for the marketplace systems, since the billing for use takes place via the marketplace. The prerequisite for using the Document Verifier is also prior registration for the Entity Extraction API. The access information to the Document Verifier is transmitted to the user during the registration process of the Entity Extraction API.

3.1.12 Other Collaboration Requirements and Duties

An active Internet connection is required to use Document Verifier. The customer has a valid account for the Document Verifier. The customer independently monitors the consumption of a concluded package contract. ISR Information Products AG does not proactively inform the customer that a package limit has been reached.

The customer undertakes not to intentionally transmit faulty documents to the API or to use the API incorrectly.

The customer is responsible for the transferred data / documents.

Should one or more of the conditions stated here not apply, ISR Information Products AG is not obliged to provide the service described with the agreed service levels.

These cooperation obligations are generally provided in a quality that enables ISR Information Products AG to fulfil its contractual obligations without additional effort. ISR Information Products AG shall not be liable for delays in the provision of services and/or breaches of the agreed service levels which are attributable to the customer’s failure to meet its cooperation obligations or which are not attributable to ISR Information Products AG.

4.Splitting API

4 Description of service

Buildsimple offers Software as a Service solutions with modern cloud infrastructures. The API services are designed to integrate with customers’ cloud and on-premise solutions. Buildsimple, a division of ISR Information Products AG, offers business and technical services as software as a service subscriptions on the Amazon Web Services Marketplace. All services offer REST APIs for easy integration. Customers, partners and solution providers can use the services with low investment because they have low-cost pay-per-use licenses.

The offer relies on the powerful Amazon Webservices, AWS for short, infrastructure and the associated scalability with hosting in the available regions of AWS.

Buildsimple currently supports the following AWS regions:

EU (Frankfurt) eu-central‑1 rds.eu-central‑1.amazonaws.com HTTPS
USA East (Northern Virginia) us-east‑1 rds.us-east‑1.amazonaws.com HTTPS

The Splitting API is a business service for splitting business domain-oriented documents that previously existed in a continuous PDF document without any domain-oriented separation. The service provides an asynchronous API for document separation via two REST interfaces for document upload and results query. The separated domain-oriented documents are displayed in JSON format. The individual domain-oriented documents can then be called up separately using an additional API.

4.1 Technology

Buildsimple uses deep learning technologies to separate documents. With this machine learning approach, the quality of the result is defined by prior training of the customer’s business documents. Neural networks are based on weighted decision processes of trained models. Continuous training processes guarantee a continuous improvement of quality.

4.2 Supported file types

Customers can upload one of the following file types via the API: PDF. If an unsupported file type has been uploaded, the service will not produce a valid result and the caller will receive an error code. A special interface is available for transferring the files to the splitting API.

4.3 Splitting

When a document is uploaded via the API and the split process is triggered, it is automatically split into individual business documents based on the previously trained data. The splitting API distinguishes between the “first page” of a document and its possible subsequent pages. Details are described in the API documentation.

4.4 Languages

The splitting API supports the languages used by the customer during training. By default, Buildsimple supports German and English for OCR recognition, i.e. reading the text information in the document. Other languages can be activated by prior arrangement.

4.5 Quality of extraction

The quality varies due to several factors.

The quality of the images, scans or digital documents affects the OCR result, which is the basis for document separation.
Documents in different languages lead to different qualities
Quantity of trained documents
Quality of the training process of the training documents

Since Buildsimple does not know the input documents, Buildsimple cannot guarantee a certain quality of the result.

4.6 Result of the Splitting API

The result is provided for 72 hours as a JSON object and can be queried via a separate REST API call. After the 72-hour retention period, the result is irrevocably deleted. Access to the result is secured by authentication with AWS tokens and their connection to the customer’s or partner’s AWS account.

4.7 Storage of data

In addition to storing the 72 hour result referred to in point 16.6, document information is temporarily stored during processing in order to perform the various processing steps. The data temporarily stored for the processing of a document are irrevocably deleted immediately after the successful processing of a document. If a technical error occurs during the processing of a document, the temporarily stored data is irrevocably deleted after one hour. This guarantees that the data will never be stored permanently after a document has been processed.

4.8 Encryption

The entire communication and processing chain within the AWS infrastructure is encrypted using SSL and HTTPS. Cached document data is encrypted in sleep mode using a combination of server-side and client-side encryption.

4.9 Marketplace Accounts

To subscribe to the Splitting API via external marketplaces, such as the Amazon Webservices Marketplace or the Syncier Marketplace, respective accounts are a prerequisite for the marketplace systems, since the usage is billed via the marketplace.

4.10 Further prerequisites and obligations for cooperation

An active Internet connection is required to use the Splitting API. The customer / partner has access to the AWS Cloud and its API gateway, or to the Syncier Cloud and its API gateway.

The customer/partner provides a competent and authorized contact person for support questions.

The customer / partner independently monitors the consumption of a concluded package contract. Buildsimple does not proactively inform about the reaching of a package limit.

The customer/partner undertakes not to intentionally transmit faulty documents to the API or to intentionally use the API incorrectly.

The customer / partner is responsible for the transferred data / documents.

If one or more of these conditions should not apply, Buildsimple is not obliged to provide the described service with the agreed service levels.

These cooperation obligations are usually provided in a quality that enables Buildsimple to fulfill the contractual obligations without additional effort. ISR Information Products AG shall not be liable for delays in the provision of services and/or violations of the agreed service levels that are attributable to the non-fulfilment of the cooperation obligations by the partner/customer or that are not attributable to ISR Information Products AG.

4.11 Terms of contract

The contract duration varies depending on the billing model selected.

4.11.1 Pay per use billing model

The pay-per-use billing model has no predefined contract term. The customer/partner pays exactly for each processed document. The contract can be terminated at any time. A separate termination is not necessary.

4.12 Processing

4.12.1 Individual agreement

In the case of an individual contractual agreement, invoicing shall be effected via a monthly invoice from ISR Information Products AG. If the pay-per-use model is used, ISR Information Products AG consolidates the documents processed in one month, which form the basis for the monthly invoice. In the case of the use of a package quota, invoicing is carried out directly upon conclusion of the contract by means of an invoice for the package concerned.

4.13 Licensing

Apart from licensing the Splitting API, ISR Information Products AG does not charge any license fees for the use of the API. The license is included in the respective contract, see point 5. All software products used are subject to the respective license conditions of the manufacturer.

4.1 Services

4.14.1 System Management & System Monitoring

The continuous monitoring of the system status by our DevOps team enables the early detection of critical server system states. In this context we carry out the following inspections:

Continuous, central monitoring of services
System event log control for critical system states and scaling of services
Control disk usage, processor and memory utilization

We monitor the services with AWS CloudWatch. The services are automatically scaled by Amazon Web Services based on the parameters defined by ISR Information Products AG.

4.14.2 Customer and Partner Support

The license price includes access to the ISR community, FAQs and a knowledge platform available to our customers and partners.

4.14.3 Incident Management (Service Interruption)

In the event of an incident, the Service Desk employee carries out the technical diagnosis and immediately tries to find a solution with the help of a knowledge database. The successful solution and the solution steps are documented and the incident is closed after the fault has been rectified. The customer is informed about the correction of the error. If an immediate solution is not possible, all previous measures are documented and the process is forwarded to subsequent instances (2nd level support or AMS). If the incident is forwarded, the Service Desk proactively monitors the incident over the entire service period to ensure compliance with the agreed service levels on the basis of a defined escalation process. Once an incident has been successfully resolved and the ticket has been closed in the system, the customer is informed.

4.15 SLA’s

4.15.1 Availability of the Splitting API

Despite the robust Amazon Web Services cloud infrastructure and comprehensive quality assurance of the service by ISR Information Products AG as well as uncontrollable quality gates, 100% uninterrupted availability of the splitting API cannot be guaranteed. The software development and operational processes of ISR Information Products AG guarantee a very high quality and stability of our services, so that we can reduce system downtimes to a minimum.

ISR Information Products AG cannot guarantee the availability of the API if the Amazon Web Services infrastructure is not fully or partially available.

The Amazon Web Services Infrastructure enables ISR Information Products AG to install new versions, patches and bug fixes without interruption. An interruption of the service is not required.

Suggest Edit

Everything about security

Copy link
Powered by Social Snap