Control’s Force’s Engine is a service provided via internet, intranet, WAN and cloud computing. It receives XML messages that are provided with adaptors to its Depositor and processes current message based on context-aware analysis.
TW Engine correlates message A, B, C, D to three process instances
The context aware analysis is relied on Data-Centric Process Model (DPM) that describes message classes and relationships between them in respect to predefined holistic transaction type. Each XML message received by the Engine (message instance) represents one of the message classes described as the DPM nodes (control junction).
Examples of holistic transaction types:
- Purchasing – includes account payable and other business data provided with ERP processes initiated through Purchase Order;
- Selling – includes account receivable and other business data provided with ERP processes initiated through Sale Order;
- e/m-Commerce - includes business and geolocation data provided with merchants’, credit card and mobile payment providers’ processes initiated through Sale Order;
- Insurance claim – includes business data provided with claim management, invoice processing and other processes initiated through claim.
- Payroll - includes business data provided with HR, payroll calculation and other processes initiated with payroll request.
The Engine is provided with built-in DPM library. Each DPM is loaded by the Engine during its configuration as XML file. This file is changed as the message mapping is required.
Data inconsistency is detected by the Engine using very limited number of rules:
- Rules that detect bypass of the process risk (like ghost payment, ghost bank account or ghost item)
- Rules that detect data discrepancy (like overpricing or over-shipping).
- Rules that detect data loss and duplicates
Control’s Force provides utilities for DPM configuration and specification for data mapping.
Note: The message based transaction controlling is executed without process workflow definition.