How BPM and Low-code platforms help automate processes, cut costs, and accelerate the digital transformation of your business.
Watch on YouTube Watch on Rutube ___________________________________________ Companies every yearlose20-30% of revenue because of inefficient manual processes and duplicated tasks. They lead to downtime, errors, slow request handling, and long approvals.
To solve the problem, companies implement BPM. A new but steady trend in the CIS market is growth low-code solutions in the BPM segment up to 60% per year.
YouTube
BPM is the approach and class of systems, which allow: - model the company's processes: sales, procurement, service, and HR management; - automate task execution: approvals, notifications, integrations; - manage efficiency: seeing bottlenecks, KPI, and execution time.
The process is described not "in employees' heads," but as schemas - BPMN or a flowchart that the system executes automatically. BPMS implementation makes business process development flexible and visual.
Low-code is development approach, where: - employees create applications, forms, reports, and integrations visually, without manual coding; - there is ready-made blocks: "send an email", "call an API", "write to 1C"; - code is needed only for complex logic or custom integrations.
When the approaches are combined, you get platform, which: - allows draw the process, which the system will execute; - provides interface and data builder, to assemble the needed forms, reports, and dashboards; - supports integrations with other systems through ready-made connectors.
| View | Focus | Content | Use cases | Examples |
|---|---|---|---|---|
| Classic BPM systems (BPMS) | Clearly formalized processes with a sequence of steps, roles, and deadlines | Visual process editor (BPMN), task routing, SLA monitoring, reports | Document management, procurement, approvals, and credit processes | ELMA365, Docsvision |
| Case Management - case management systems | Flexible, loosely structured processes that unfold differently depending on the situation | Customer / case record, a set of rules, and routes determined during the process | Customer service, claims, legal work, healthcare | Comindware Tracker |
| Low-code BPM platforms are universal builders | Processes and building custom applications around them | Builders for processes, forms, and interfaces, data and reference management, API integrations, CRM, HR, and ServiceDesk templates | Rapid assembly of internal services, portals, and tailored CRM / HR systems | Citeck ECOS |
| Business rules management systems (BRMS / BRMS) | Separate logic and rules from process code so they can be managed independently | A rules engine where the user defines "if-then" conditions in plain language, with rule versions | Pricing, calculations, scoring, and regulatory requirements where only the rules change, not the process | Business Rules module in Comindware |
| Industry-specific BPM solutions | Preconfigured processes and interfaces for a specific industry | Ready-made templates for a bank, insurer, manufacturer, or government agency | Rapid deployment of an off-the-shelf solution with minor customization | Industry-specific packages based on ELMA, Citeck, and Docsvision |
- Visual modeling. An analyst or manager opens the web interface and uses drag-and-drop to draw the process diagram, usually in BPMN notation: start -> tasks -> conditions -> end. - Role definition. The workflow diagram immediately specifies assignees - roles, departments, groups - and their permissions. - Templates. The platform offers ready-made templates for standard processes: contract approval and employee onboarding.
- Cards and forms. Using the builder, a specialist creates data entry forms: requests, contracts, invoices. - Reference data. The analyst configures classifiers, lists of employees, counterparties, and products. - Low-code builder. A designer can add fields, buttons, and display rules on their own.
- Routes and conditions. The analyst defines the conditions for routing processes along different branches: "if the customer has not confirmed the request -> contact them manually for approval". - SLA and deadlines. Each task has an execution time, reminders, and escalation. - Business rules. Some systems include a separate rules engine (BRMS): a manager expresses "if-then" rules in business language.
- Connectors. The platform includes ready-made blocks for connecting with 1C, CRM, email, electronic signatures, and government services. - API / scenarios. If there is no standard connector, the analyst configures the call REST/ SOAP through a visual editor, and the developer writes a short script if needed.
- Automatic launch. The process starts from an event - a request, an incoming document, a date - or manually. - Task assignment. The system assigns tasks to performers on its own, sends notifications by email / messenger, and inserts the required forms. - Automation of actions. Some steps are performed automatically: calculation, validation, email sending, and system logging.
- Event log. Logs every action: who did what and when. - Dashboards and reports. Managers can see KPI: completion time, employee workload, and bottlenecks. - Changes on the fly. If needed, the analyst can change the workflow or rules without stopping the entire system.
- Process analytics. The system collects statistics on process instances and identifies delays. - Iterations. A manager can quickly make improvements through the same visual designer. - Scaling. A single platform can launch new processes and connect departments.
1. Drew the process "Contract approval". 2. Configured the request form and roles. 3. Set conditions: amount > X -> additional approval. 4. Connected 1C to load details. 5. Launched - the system automatically assigns tasks and tracks deadlines. 6. Let's look at a report on timelines and bottlenecks. 7. We change the route / rules in the interface - changes are applied to the system immediately.
Accelerating implementation and changes - Launch speed. A new process or service can be assembled in weeks, not months, because a visual builder is used instead of pure code. - Fast response. If the law or market conditions change, a business analyst can update routes and rules without involving developers. Reduced dependence on developers and IT - Before 70-80 % standard changes in such systems are made by business users themselves. - Less backlog in IT, lower costs for external integrators.
Flexibility and adaptability - Can be handled as strictly regulated processes - procurement, approvals, and loosely structured cases - customer inquiries, complaints. - The system supports Scaling: dozens of processes can run on one platform across different departments.
Transparency and control - All processes, tasks, and deadlines are visible in real time on dashboards. - KPI, SLA, and bottlenecks are shown in clear reports, which increases process quality. - Easy audit: every step and decision is recorded in the event log.
Lower costs and higher efficiency - Less manual work: requests, approvals, and notifications are handled automatically. - Reduction errors through standardization. - Return on implementation - 6-12 months through savings in time and payroll costs.
Improving customer service - Fast handling of requests and inquiries that allows double the customer base in 6 months. - A unified data system and fewer lost documents. - The ability to quickly build customer portals and Low-code-based mobile apps.
Import independence and a unified stack CIS BPM / Low-code platforms - ELMA365, Docsvision, Citeck ECOS, Comindware - fill the niche of Western solutions. This is: - reduces the risks of support unavailability and currency fluctuations; - increases trust from regulators, partners, and customers. Built-in integrations The system includes ready-made connectors for 1C, CRM, email, EDI, and government services.
They are configured visually, without developing large integration modules.
BRMS is a software platform that enables: store and manage business rules separately from application code; - formulate "if ... then ..." rules in business-friendly language, not programming language; - execute centrally these rules with the engine, and apply them in different processes and applications. Instead of hardcoding the logic "if loan amount > 1 million -> approved by the director" into code, you define it in BRMS.
When rules change, you update them in the BRMS, and all connected systems immediately start working under the new conditions.
This is a central database where all rules are stored in a structured form. The repository is needed for: - creating a single source of truth - no duplicate rules across different applications; - storing all versions and change history; - grouping rules by category: loans, rates, limits.
- Graphical editor / DSL. An interface where a business analyst or manager defines if-then rules in plain language or as decision tables. - Support for different formats: decision tables, decision trees, scripts, BPMN-like blocks. With these tools, you can: - create rules without programming; - change logic quickly; - easily align rules across the company.
This is the component that executes rules in real time. It ensures logic is executed centrally and consistently across all systems. Its functions: - loading rules from the repository; - applying conditions to input data; - returning a decision: "approve", "agree", "reject"; - optimization - compiling / caching rules for high performance.
- Rules management workflow. This is a built-in "design -> testing -> publication" process. - Roles and permissions. A system that defines who can create, approve, and launch processes. - Version control provides transparency, change auditing, and the ability to roll back to a previous version.
These are interfaces through which external systems - BPM, CRM, ERP - call the rule engine. Their can be connected in REST, SOAP, MQ, and connectors for popular platforms. The interfaces make it possible to: - connect multiple applications to a single rule set; - ensure high performance and scalability.
They create an environment where "draft" rules can be run on test data. It allows you to: - check algorithm correctness and avoid production errors; - compare the results of the old and new rule versions; - see how the outcome changes when different decisions are made.
- Execution log. Records which rule was triggered, with what data, and what the result was. - Dashboards. Show usage frequency, response time, and number of triggers. - Audit. The ability to prove to a regulator or customer which rule was used to make the decision.
- If order amount > 500,000 rubles, then director approval. - If customer age < 25 and credit history is clean, then scoring = "low risk". - If stock < N, then automatically create a purchase order.
Creating and storing rules Business analyst or manager opens the BRMS web interface. In the visual editor, through decision tables, decision trees, and the "if - then" pseudolanguage, it defines conditions: for example, "if the customer does not respond for more than 2 days -> cancel the order".
Rules are stored in the repository - a central repository that stores categories, versions, and change history.
Version and lifecycle management
A new rule goes through approval workflow: draft -> test -> publish. BRMS includes a permissions system: who can create, approve, and publish.
All changes are logged: you can see who changed the algorithm and when, and roll back to an earlier version.
Before going live, the rule can be run on test data.
A specialist can compare the results of the old and new rule versions.
This is reduces the risk of errors and allows the effect of changes to be predicted.
Integration with external systems is provided by BRMS API, REST, SOAP or ready-made connectors.
Any application - a BPM system, CRM, ERP, or website - can, if needed, invoke the rules engine with a set of input data.
Integration can be synchronous, when the response comes immediately, or asynchronous - through a message queue.
When a request comes in, rules engine: - loads the current rules from the repository; - matches input data against conditions; - executes the required branches - decision tables and trees; - returns the result - "approve the loan", "get director approval", "set tariff X".
All of this happens centrally and consistently for all connected systems.
BRMS monitoring and audit logs every trigger: which rule was applied, with what parameters, and what the result was.
Built-in dashboards show: - call frequency; - percentage of successful / rejected decisions; - engine response time.
This is needed for control, performance analysis, and an evidentiary basis for regulators.
If a tariff, limit, or regulation changes, the business user simply updates the rule in the BRMS.
All connected applications automatically start operating under the new conditions - without code changes or system recompilation.
In the BRMS, the rule is defined as "if amount > 500,000 → approval by the director".
When approving a contract, the BPM system sends parameters to BRMS.
The rules engine checks the condition and returns "director approval required".
The BPM system automatically starts the process branch for the director.
When the limit changes, the analyst updates the number in the BRMS, and the processes immediately run under the new rules.
Reducing the cost of logic changes - Changes to business rules, requirements, rates, and limits in BRMS happen faster and easier, than if the logic had to be changed in the source code of several applications.
This reduces the time and resources needed for refinements by 30-60%. - The ability to manage rules visually reduces the load on the IT team and allows you to respond quickly to changes without rewriting code.
Greater flexibility and faster adaptation - When external conditions change - market, legal, or regulatory - the business can adjust rules on the fly without waiting for long technical cycles. - BRMS helps quickly test and deploy new rules. This al 20-50% reduces decision-making time.
Reduced dependence on developers / the IT department Rules are defined and changed by business users or analysts, not just programmers. This reduces "bottlenecks," allows2-5 times faster deploy new rules and bring changes to market. Unified, centralized decision logic - Rules are stored in a single repository, and the rules engine executes them consistently across all systems where they apply.
This is reduces the risk of discrepancies and errors due to mismatched logic implementations. - By versioning rules and logging their changes, the system can be rolled back. - The logic is transparent, so you can see which rule was applied in a specific situation, which important for audit and control. Improved decision quality and fewer errors - Automatic rule execution eliminates human error.
For example, developers can make mistakes by implementing a rule incorrectly, while BRMS minimizes such risks. This reduces the number of errors in business decisions by 30-70%, especially in scenarios with many conditions and exceptions. - The ability to test and simulate rules before publishing makes it possible to see how a rule behaves in different scenarios and avoid unexpected errors.
Compliance with standards and regulatory requirements - In industries where regulators frequently change rules, laws, and standards, BRMS enables fast adapt. - Automating compliance checks with rules helps reduce the risk of fines and reputational damage. Improved operational efficiency - BRMS automates many decisions that were previously made manually.
This saves time and resources. Return on investment - 6-12 months in moderately complex projects, especially when there are many rules and they change often. - An automated rule-based decision instead of lengthy manual review makes it possible to faster respond, and serve customers and partners.
Predictability and stability - When rules are centralized, the business can predict how the system will respond to changes. - BRMS reduces variation in decisions across departments or systems because one rule applies everywhere. Automated management systems give the business speed, flexibility, and transparency, reduce costs, and make it possible to focus on growth and innovation.
The CIS BPM and Low-code platform market is growing, and these systems are becoming a key factor in competitiveness and sustainable growth.