Smart Business Analytics Quick BI

Based on the multi-level cache strategy, it provides users with query responses ranging from milliseconds to sub seconds to achieve query acceleration, solve the problem of slow chart presentation or data analysis caused by excessive data volume or poor database performance, and improve customers' product experience.

• Excellent performance

  Users provide query responses from milliseconds to sub seconds.

• Simple configuration

  Through simple configuration on the dataset, you can experience a variety of acceleration methods, including result caching and extraction acceleration.

• Wide scene coverage

  Customers can combine multiple cache acceleration schemes to meet various complex data analysis scenarios.

This solution realizes centralized management and control of enterprise resources through the ability to open APIs and open webhooks event monitoring. The enterprise platform queries, deletes, publishes, offline, and moves report resources through the open API interface, At the same time, the report developer/administrator of the enterprise will send a notice to the enterprise system about the changes made to the works in the workbench of Quick BI through the customer's customized channel webhooks, so that the enterprise platform can sense the resource changes in Quick BI in a timely manner.

• Resource centralization

  Consolidate the work resources of QuickBI to the unified management and control platform of enterprise resources to achieve centralized management and control.

• Real time monitoring resource changes

  By monitoring events, enterprises can sense changes in resources and achieve security control.

• Improve decision-making and execution efficiency

  After the unified integration of the enterprise platform with the QuickBI work resources is completed, the work status can be changed only on the enterprise internal platform, without the need for process jump to improve efficiency

Enterprise system user-defined approval docking, the general process is: 1) When the applicant (Quick BI ordinary user) accesses report resources, initiate a "permission application"; 2) Quick BI sends the "permission application" notice to the customer's customized channel webhooks; 3) When the customer OA system receives the approval notice, it will be judged by its own business system and pushed to the designated approver; 4) After the approver completes the approval, the customer's OA system will call back the open approval API interface of Quick BI and notify Quick BI to make approval changes; 5) After the applicant (Quick BI ordinary user) accesses the resource again, the report can be viewed normally.

• Flexible development of approval process

  Customize the internal approval process of the enterprise to solve the problem of sensitive enterprise permissions.

• Centralized authority

  Permission approval is uniformly completed on the enterprise side, and when it is completed, it will notify Quick BI via callback. It is not necessary to complete the operation in the approval center of Quick BI.

• Approval Tracking

  The approval records can be traced in Quick BI, and the accounts with access rights can be viewed in time on the centralized authorization page.

Taking dual tenants (factory side tenants and dealer tenants) as an example, tenant A and tenant B respectively create two instance organizations in Quick BI. This scheme uses a login policy to strictly route, so that different tenants can complete login docking with Quick BI through their respective system SSO services under the condition of network isolation, And synchronize the account members of their respective systems to the organization of Quick BI. Thus, the A tenant account can log in to Quick BI through the A domain name, and can only access the A organization; The B tenant account can only access the B organization by logging into Quick BI through the B domain name.

• SaaS integration architecture

  For end customers, it is a SaaS form. Tenant 0 can allocate sub tenants and their account numbers as required.

• Data security isolation between tenants

  Different tenants can access different domain names. Their domain names can customize the login policy and synchronize members independently. Members can only access resources under the specified tenant.

• Highly customized integration

  It provides system level APIs to support tenant 0 to customize the integrated tenant management page.

• System level control

  A built-in tenant management platform is provided to support tenant addition, offline, account allocation, extension and other operations.

This scheme standardizes the visual analysis and rendering process, and pulls together different series of charts (statistics/relations/tables, etc.) and different technology stacks (G2/D3/L7, etc. And it has established an independent analysis layer (linkage/drilling/prediction, etc.), independently configured DSL and independent sandbox, solved the problem of seamless linkage analysis and resource isolation between open custom charts and official charts, achieved cross system analysis capability, and supported different interactive experiences of PC/mobile/TV and other multiple terminals.

• Straddle end

  The same ability supports the differentiated interaction experience of different ends.

• High performance

  Targeted rendering performance optimization under large amount of data.

• Capable

  Cross system interactive analysis, 1400+composable/configurable capability, which can finely control most functions and display details.