- 28 Jun 2022
- 3 Minutos para leer
- Impresión
- OscuroLigero
- PDF
April'22
- Actualizado en 28 Jun 2022
- 3 Minutos para leer
- Impresión
- OscuroLigero
- PDF
Automatic Condition Based Decisions
In the modern world, decision-making is an art. There are so many touchpoints where we need to make business decisions with varying impacts. As business processes and technology evolve, businesses are growing, and the volumes are increasing. At the same time, manual decision-making allows the control; however, looking at the volumes, there is a need to look at automation and create the right balance between the manual and automated decisions by factoring the cost-benefit analysis associated with each decision made.
For example, a purchase order may require different approval based on different amounts.
When the amount is less than $10000, the administration team will approve
When the amount is between $10000 - $1,000,000, the finance team will approve
When the amount is greater than $1,000,000, then CXO will approve
Considering the volume and lower risk, case 1 – purchase order approval below $10,000 would be an ideal candidate for automation, while case 3 - CXO approval for orders above $1,000,000 would be suitable for manual intervention, given the risk involved.
Businesses want to create and maintain control in decision-making. DL Asset Track™ has a feature named ' connector node,' which provides the ability to dynamically decide the next business entity that is expected to act based on pre-defined conditions.
Apart from bigger decisions, in day-to-day operations, there are multiple comparatively smaller decisions that stakeholders may take, such as:
- Sharing information based on the defined turnaround time (TAT), for example, sending an invoice after 'X' number of days.
- Acknowledge a particular task only when specific information is available. For example:
- Accepting a consignment only if QC status is 'passed.'
- Rejecting a consignment if QC status is 'faulty.'
- Acknowledge a task when a trusted business entity has sent the information, for example, accepting a delivery to the warehouse only when the transport team sends it.
- Raise a dispute when the delivery status is pending, and the transport team requests payment.
There are slightly complex decisions that a stakeholder needs to make, especially when raising a dispute. Most disputes are caused due to gaps in understanding or communication. Disputes are typically raised over e-mail, and it takes days to find the right stakeholder even to verify the authenticity of the dispute.
Stakeholders often wonder if there is a smarter & more reliable way to take such decisions as these are often redundant and require automation.
The DL Asset Track™ platform addresses these through a feature named 'automation setting,' which allows business entities to automate such decisions, streamline their business processes, and save valuable time by making an informed decision.
Salient Aspects
- Automatically decide the next business entity based on some pre-defined conditions.
- Automatically send an instance to the next business entity after 'X' min/hours/days.
- Automatically raise a dispute when a configured attribute value is found in an instance.
- Automatically allow sending, receiving, and rejecting an instance when a configured attribute value is found in an instance.
Steps
Configure Connector node
- Select a business entity in a workflow.
- Choose the next node as the connector node.
- Configure the properties of the connector node.
- Configure the conditions and select the next business entity for each condition.
Please click here to find more information.
Configure Automation Settings
- Select a business entity.
- Go to automation settings.
- Enable auto send, and configure time in minutes, hours, days, or custom.
- Enable auto delay, and configure time in minutes, hours, days, or custom.
- Enable auto dispute, select an attribute and configure the expected value based on which a dispute will be raised.
- Enable allow send, receive, reject, and select an attribute and configure the expected value based on which an event will be executed.
Please click here to find more information.