Difference between revisions of "QPR ProcessAnalyzer System Architecture"

From QPR ProcessAnalyzer Wiki
Jump to: navigation, search
m (Ollvihe moved page QPR Software Products Architecture to QPR ProcessAnalyzer System Architecture without leaving a redirect)
 
(4 intermediate revisions by the same user not shown)
Line 1: Line 1:
QPR ProcessAnalyzer is natively a cloud-based software, and also an on-premise installation is supported.
+
QPR ProcessAnalyzer is natively a cloud-based software, and also an on-premise installation is supported. Users access the product through their PCs, laptops or tables on the Internet for the Web UI and the Excel UI.
 
 
As data security is always key, the architecture is built so that the data is protected when collected from the source. The data can be fetched from any source using integration interfaces whether they are located on premise or in the cloud. The analysis algorithms are located in SQL Server from where the analysis results are fed to the Excel or Web user interfaces.
 
 
 
Users access the product through their PCs, laptops or tables on the Internet for the Web UI and the Excel UI.
 
  
 
==System Architecture ==
 
==System Architecture ==
Line 11: Line 7:
  
 
QPR ProcessAnalyer consists of the following components:
 
QPR ProcessAnalyer consists of the following components:
* QPR ProcessAnalyzer web client: web-based user interface for QPR ProcessAnalyzer.
+
* '''QPR ProcessAnalyzer Web Client''': web-based user interface for QPR ProcessAnalyzer.
* QPR ProcessAnalyzer Excel client: An Add-on to Excel client used to manage QPR ProcessAnalyzer models, datatables, scripts and users.
+
* '''QPR ProcessAnalyzer Excel Client''': Add-on to MS Excel used to admininstrate QPR ProcessAnalyzer models, datatables, scripts and users.
* QPR ProcessAnalyzer ScriptLauncher: Tool to trigger QPR ProcessAnalyzer ETL scripts. QPR ProcessAnalyzer ScriptLauncher is a tool for fetching on-premise data and store to the cloud.
+
* '''QPR ProcessAnalyzer ScriptLauncher''': Tool to trigger QPR ProcessAnalyzer ETL scripts. QPR ProcessAnalyzer ScriptLauncher can be used for fetching on-premise data and store to the cloud.
* QPR UI Server: Component in the server which handles the web UI and stores dashboards.
+
* '''QPR UI Server''': Component in the server which handles the web UI and stores dashboards.
* QPR ProcessAnalyzer Server: Component to store the eventlog data in the memory and performs analytical calculations for the data.
+
* '''QPR ProcessAnalyzer Server''': Component to store the eventlog data in the memory and performs analytical calculations for the data.
* QPR UI database: database for the QPR UI Server.
+
* '''QPR UI database''': database for the QPR UI Server.
* QPR ProcessAnalyzer database: database for the QPR ProcessAnalyzer server.
+
* '''QPR ProcessAnalyzer database''': database for the QPR ProcessAnalyzer server.
  
 
== QPR ProcessAnalyzer Server API==
 
== QPR ProcessAnalyzer Server API==
 
All connections to QPR ProcessAnalyzer Server are done using the QPR ProcessAnalyzer API (more information: [[QPR ProcessAnalyzer Web Service API]]).
 
All connections to QPR ProcessAnalyzer Server are done using the QPR ProcessAnalyzer API (more information: [[QPR ProcessAnalyzer Web Service API]]).
  
== Database Connections ==
+
== Database Connection ==
 
QPR ProcessAnalyzer stores its data in an SQL Server database. Connection to the database uses .NET Framework Data Provider for SQL Server (SqlClient).
 
QPR ProcessAnalyzer stores its data in an SQL Server database. Connection to the database uses .NET Framework Data Provider for SQL Server (SqlClient).
  
Line 38: Line 34:
 
* Supply Chain Management systems
 
* Supply Chain Management systems
 
* Configuration Management Databases
 
* Configuration Management Databases
 +
 +
As data security is always key, the architecture is built so that the data is protected when collected from the source. The data can be fetched from any source using integration interfaces whether they are located on premise or in the cloud.

Latest revision as of 07:08, 12 September 2019

QPR ProcessAnalyzer is natively a cloud-based software, and also an on-premise installation is supported. Users access the product through their PCs, laptops or tables on the Internet for the Web UI and the Excel UI.

System Architecture

The following figure shows the QPR ProcessAnalyzer system architecture.

QPR ProcessAnalyzer Architecture.png

QPR ProcessAnalyer consists of the following components:

  • QPR ProcessAnalyzer Web Client: web-based user interface for QPR ProcessAnalyzer.
  • QPR ProcessAnalyzer Excel Client: Add-on to MS Excel used to admininstrate QPR ProcessAnalyzer models, datatables, scripts and users.
  • QPR ProcessAnalyzer ScriptLauncher: Tool to trigger QPR ProcessAnalyzer ETL scripts. QPR ProcessAnalyzer ScriptLauncher can be used for fetching on-premise data and store to the cloud.
  • QPR UI Server: Component in the server which handles the web UI and stores dashboards.
  • QPR ProcessAnalyzer Server: Component to store the eventlog data in the memory and performs analytical calculations for the data.
  • QPR UI database: database for the QPR UI Server.
  • QPR ProcessAnalyzer database: database for the QPR ProcessAnalyzer server.

QPR ProcessAnalyzer Server API

All connections to QPR ProcessAnalyzer Server are done using the QPR ProcessAnalyzer API (more information: QPR ProcessAnalyzer Web Service API).

Database Connection

QPR ProcessAnalyzer stores its data in an SQL Server database. Connection to the database uses .NET Framework Data Provider for SQL Server (SqlClient).

In addition to the system database, QPR ProcessAnalyzer can optionally use another database for SQL scripting for ETL (more information: ETL Scripting).

Connecting to Data Sources

QPR ProcessAnalyzer is designed and built for easy integration to a wide range of data sources. The power of the product comes from having different process information accessible from one point and where it can be analyzed from any angle.

For basic analysis, Event ID, Time Stamp and Attiribute data should be available from the data source. However, depending on the customer need the analysis can be expanded by other data where all provided information can be included in the analysis be it sales person, location, customer, sale amount, time stamp for start and end of sale. The data sources can include:

  • ERP systems e.g. SAP for Order to Cash and other processes
  • CRM systems e.g. Salesforce for sales process
  • Customer support systems e.g. Jira
  • Case Management Systems
  • Supply Chain Management systems
  • Configuration Management Databases

As data security is always key, the architecture is built so that the data is protected when collected from the source. The data can be fetched from any source using integration interfaces whether they are located on premise or in the cloud.