QPR ProcessAnalyzer System Architecture
QPR ProcessAnalyzer is natively a cloud-based software, and also an on-premise installation is supported.
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.
File:QPR ProcessAnalyzer Architecture.png
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
Connections to QPR ProcessAnalyzer Server
All client connections to QPR ProcessAnalyzer Server are done using the QPR ProcessAnalyzer API (more information: QPR_ProcessAnalyzer Web Service API).
Database Connections
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).