FORM 2
THE PATENTS ACT, 1970 (39 OF 1970) & THE PATENT RULES, 2003
COMPLETE SPECIFICATION
(See section 10 and rule 13)
“METHOD AND SYSTEM FOR MANAGING A WORK
ORDER FLOW”
We, Jio Platforms Limited, an Indian National, of Office - 101, Saffron, Nr. Centre Point, Panchwati 5 Rasta, Ambawadi, Ahmedabad - 380006, Gujarat, India.
The following specification particularly describes the invention and the manner in which it is to be performed.

METHOD AND SYSTEM FOR MANAGING A WORK ORDER FLOW
FIELD OF INVENTION
[0001] Embodiments of the present disclosure generally relate to customer relationship management systems. More particularly, embodiments of the present disclosure relate to method and system for managing a work order flow.
BACKGROUND
[0002] The following description of the related art is intended to provide background information pertaining to the field of the disclosure. This section may include certain aspects of the art that may be related to various features of the present disclosure. However, it should be appreciated that this section is used only to enhance the understanding of the reader with respect to the present disclosure, and not as admissions of the prior art.
[0003] In the fast-paced world of the telecom industry that is experiencing heavy growth and competition, meeting customer demands is of utmost importance. This also leads to increased expectations from customers for better quality service and quick turnaround time. One key aspect of this is ensuring that orders are processed and approved in a timely and efficient manner.
[0004] To meet these demands, orders are created when customers raise service or product orders through company portals such as Customer Relationship Management (CRM) systems via Sales Channels. Traditionally, sales orders in the telecom industry follows a linear approval process. In today's business world, handling work orders often requires many layers of approvals and checks, making the process quite complex. As businesses grow and their needs change, the traditional way of managing these workflows using hard-coded solutions becomes inefficient and prone to mistakes.

[0005] For example, when a company needs to approve new customer accounts or process requests to switch service providers, it might need approvals from multiple departments and external agencies. These approvals might need to happen at the same time, depend on certain conditions, or require re-checking previous stages based on new information.
[0006] Existing systems often can't handle this complexity well. Managing these workflows with code can lead to major maintenance problems and increase the chance of errors. As business requirements change, the code needs constant updating, which is time-consuming and can introduce new issues.
[0007] Thus, there is a need for a more flexible and scalable way to manage these work order approvals.
SUMMARY
[0008] This section is provided to introduce certain aspects of the present disclosure in a simplified form that are further described below in the detailed description. This summary is not intended to identify the key features or the scope of the claimed subject matter.
[0009] An aspect of the present disclosure may relate to a method for managing a work order flow, the method comprising receiving, by a transceiver unit, one or more work processes associated with the work order. The method comprises identifying, by an identification unit, one or more process at a same level as said process. The method comprises determining, by a processing unit, a completion status of the one or more same level process. The method comprises receiving, by the transceiver unit, an approval response for a next milestone associated with the work process, wherein the approval response is generated based on determination of the completion status of the same level process, and wherein the generated approval response comprises a status of completion of the one or more same level

process. The method comprises detecting, by an analysis unit, a status of the approval response. The method comprises performing, by the analysis unit, an action based on the detected status of the approval response and a predefined mandate parameter associated with the one or more work processes.
[0010] In an exemplary aspect of the present disclosure, wherein in an event a value of the predefined mandate parameter is positive and the status of the approval response, associated with the same level work process, is a pending status, the action comprises waiting, by the processing unit, for a time period till each of the plurality of same level processes are completed; and upon completion of each of the plurality of same level processes, executing, by the processing unit, the next process associated with the work order.
[0011] In an exemplary aspect of the present disclosure, wherein in an event a value of the predefined mandate parameter is positive and the status of the approval response, associated with the same level work process, is a complete status, the action comprises executing, by the processing unit, the next process associated with the work order.
[0012] In an exemplary aspect of the present disclosure, wherein in an event a value of the predefined mandate parameter is positive and the status of the approval response, associated with the same level work process, is one of a failure status and a require rework status, the action comprises triggering, by analysis unit, a notification for a POS (Point of Sale) to initiate one of a refund and a requirement of documents.
[0013] In an exemplary aspect of the present disclosure, wherein in an event a value of the predefined mandate parameter is negative and the status of the approval response, associated with the same level work process, is a complete status, the action comprises marking, by the processing unit, said one or more work process as completed.

[0014] In an exemplary aspect of the present disclosure, wherein the approval response is received from one of an Application Programming Interface (API), a user interface, and an inbound call.
[0015] In an exemplary aspect of the present disclosure, wherein the one or more processes associated with the work order are selected from one of: one or more processes in a sale order management system, one or more processes between one or more customers, one or more processes between one or more channel partners, one or more processes between a plurality of third-party service providers, and one or more processes between a plurality of third-party vendors.
[0016] Another aspect of the present disclosure may relate to a system for managing a work order flow, the system comprising a transceiver unit configured to receive one or more work processes associated with the work order. The system comprises an identification unit connected to at least the transceiver unit, wherein the identification unit configured to identify one or more process at a same level as said process. The system comprises a processing unit connected to at least the identification unit, wherein the processing unit configured to determine a completion status of the one or more same level process. The system comprises the transceiver unit connected to at least the processing unit, wherein the transceiver unit is further configured to receive an approval response for a next milestone associated with the work process, wherein the approval response is generated based on determination of the completion status of the same level process, and wherein the generated approval response comprises a status of completion of the one or more same level process. The system comprises an analysis unit connected to at least the transceiver unit, wherein the analysis unit configured to detect a status of the approval response. The system comprises the analysis unit is further configured to perform an action based on the detected status of the approval response and a predefined mandate parameter associated with the one or more work processes.
[0017] Yet another aspect of the present disclosure may relate to a non-transitory computer readable storage medium storing instructions for managing a work order

flow, the instructions include executable code which, when executed by a one or more units of a system, causes a transceiver unit of the system to receive one or more work processes associated with the work order. Further, the instructions include executable code, which when executed causes the identification unit of the system to identify one or more process at a same level as said process. Further, the instructions include executable code, which when executed causes the processing unit of the system to determine a completion status of the one or more same level process. Further, the instructions include executable code, which when executed causes the transceiver unit of the system to receive an approval response for a next milestone, associated with the work process. The approval response is generated based on determination of the completion status of the same level process. The generated approval response comprises a status of completion of the one or more same level process. Further, the instructions include executable code, which when executed causes the analysis unit of the system to: detect a status of the approval response; and perform an action based on the detected status of the approval response and a predefined mandate parameter associated with the one or more work processes.
OBJECTS OF THE INVENTION
[0018] Some of the objects of the present disclosure, which at least one embodiment disclosed herein satisfies are listed herein below.
[0019] It is an object of the present disclosure to provide a system that allows possibility of restructuring approval flow in sales orders.
[0020] It is another object of the present disclosure to provide a system that allows making a change or request an exception without going back to the previous stakeholder and therefore, without having to go through the tedious process of modifying code, providing binaries, testing in multiple environments, and waiting for planned events to deploy in production.

[0021] It is yet another object of the present disclosure to provide a system that
facilitates a possibility to make runtime configurations using Command Line
Interface (CLI) or via UI. This means that approvals configurations can be made
5 dynamically in cache, without having to wait for a planned event.
DESCRIPTION OF THE DRAWINGS
[0022] The accompanying drawings, which are incorporated herein, and constitute
10 a part of this disclosure, illustrate exemplary embodiments of the disclosed methods
and systems in which like reference numerals refer to the same parts throughout the
different drawings. Components in the drawings are not necessarily to scale,
emphasis instead being placed upon clearly illustrating the principles of the present
disclosure. Also, the embodiments shown in the figures are not to be construed as
15 limiting the disclosure, but the possible variants of the method and system
according to the disclosure are illustrated herein to highlight the advantages of the
disclosure. It will be appreciated by those skilled in the art that disclosure of such
drawings includes disclosure of electrical components or circuitry commonly used
to implement such components.
20
[0023] FIG. 1 illustrates an exemplary block diagram of a computing device upon which the features of the present disclosure may be implemented in accordance with exemplary implementation of the present disclosure.
25 [0024] FIG. 2 illustrates an exemplary block diagram of a system for managing a
work order flow, in accordance with exemplary implementations of the present disclosure.
[0025] FIG. 3 illustrates a method flow diagram for managing a work order flow,
30 in accordance with exemplary implementations of the present disclosure.
7

[0026] FIG. 4 illustrates a system architecture for managing a work order flow, in accordance with exemplary implementations of the present disclosure.
[0027] FIG. 5A illustrates a flow diagram for a set of work processes associated
5 with an exemplary work order, such as a mobile number portability (MNP)
scenario, in accordance with an exemplary implementation of the present disclosure.
[0028] FIG. 5B illustrates a flow diagram for a set of work processes associated
10 with an exemplary work order, such as a mobile number portability (MNP)
scenario, in accordance with another exemplary implementation of the present disclosure.
[0029] FIG. 6 illustrates a flow diagram for managing a work order flow, in
15 accordance with exemplary implementations of the present disclosure.
[0030] The foregoing shall be more apparent from the following more detailed description of the disclosure.
20 DETAILED DESCRIPTION
[0031] In the following description, for the purposes of explanation, various specific details are set forth in order to provide a thorough understanding of embodiments of the present disclosure. It will be apparent, however, that
25 embodiments of the present disclosure may be practiced without these specific
details. Several features described hereafter may each be used independently of one another or with any combination of other features. An individual feature may not address any of the problems discussed above or might address only some of the problems discussed above.
30
[0032] The ensuing description provides exemplary embodiments only, and is not intended to limit the scope, applicability, or configuration of the disclosure. Rather,
8

the ensuing description of the exemplary embodiments will provide those skilled in
the art with an enabling description for implementing an exemplary embodiment.
It should be understood that various changes may be made in the function and
arrangement of elements without departing from the spirit and scope of the
5 disclosure as set forth.
[0033] Specific details are given in the following description to provide a thorough
understanding of the embodiments. However, it will be understood by one of
ordinary skill in the art that the embodiments may be practiced without these
10 specific details. For example, circuits, systems, processes, and other components
may be shown as components in block diagram form in order not to obscure the embodiments in unnecessary detail.
[0034] Also, it is noted that individual embodiments may be described as a process
15 which is depicted as a flowchart, a flow diagram, a data flow diagram, a structure
diagram, or a block diagram. Although a flowchart may describe the operations as
a sequential process, many of the operations may be performed in parallel or
concurrently. In addition, the order of the operations may be re-arranged. A process
is terminated when its operations are completed but could have additional steps not
20 included in a figure.
[0035] The word “exemplary” and/or “demonstrative” is used herein to mean serving as an example, instance, or illustration. For the avoidance of doubt, the subject matter disclosed herein is not limited by such examples. In addition, any
25 aspect or design described herein as “exemplary” and/or “demonstrative” is not
necessarily to be construed as preferred or advantageous over other aspects or designs, nor is it meant to preclude equivalent exemplary structures and techniques known to those of ordinary skill in the art. Furthermore, to the extent that the terms “includes,” “has,” “contains,” and other similar words are used in either the detailed
30 description or the claims, such terms are intended to be inclusive—in a manner
similar to the term “comprising” as an open transition word—without precluding any additional or other elements.
9

[0036] As used herein, a “processing unit” or “processor” or “operating processor”
includes one or more processors, wherein processor refers to any logic circuitry for
processing instructions. A processor may be a general-purpose processor, a special
5 purpose processor, a conventional processor, a digital signal processor, a plurality
of microprocessors, one or more microprocessors in association with a (Digital
Signal Processing) DSP core, a controller, a microcontroller, Application Specific
Integrated Circuits, Field Programmable Gate Array circuits, any other type of
integrated circuits, etc. The processor may perform signal coding data processing,
10 input/output processing, and/or any other functionality that enables the working of
the system according to the present disclosure. More specifically, the processor or processing unit is a hardware processor.
[0037] As used herein, “a user equipment”, “a user device”, “a smart-user-device”,
15 “a smart-device”, “an electronic device”, “a mobile device”, “a handheld device”,
“a wireless communication device”, “a mobile communication device”, “a
communication device” may be any electrical, electronic and/or computing device
or equipment, capable of implementing the features of the present disclosure. The
user equipment/device may include, but is not limited to, a mobile phone, smart
20 phone, laptop, a general-purpose computer, desktop, personal digital assistant,
tablet computer, wearable device or any other computing device which is capable
of implementing the features of the present disclosure. Also, the user device may
contain at least one input means configured to receive an input from at least one of
a transceiver unit, a processing unit, a storage unit, a detection unit and any other
25 such unit(s) which are required to implement the features of the present disclosure.
[0038] As used herein, “storage unit” or “memory unit” refers to a machine or
computer-readable medium including any mechanism for storing information in a
form readable by a computer or similar machine. For example, a computer-readable
30 medium includes read-only memory (“ROM”), random access memory (“RAM”),
magnetic disk storage media, optical storage media, flash memory devices or other types of machine-accessible storage media. The storage unit stores at least the data
10

that may be required by one or more units of the system to perform their respective functions.
[0039] As used herein “interface” or “user interface refers to a shared boundary
5 across which two or more separate components of a system exchange information
or data. The interface may also be referred to a set of rules or protocols that define
communication or interaction of one or more modules or one or more units with
each other, which also includes the methods, functions, or procedures that may be
called.
10
[0040] All modules, units, components used herein, unless explicitly excluded
herein, may be software modules or hardware processors, the processors being a
general-purpose processor, a special purpose processor, a conventional processor,
a digital signal processor (DSP), a plurality of microprocessors, one or more
15 microprocessors in association with a DSP core, a controller, a microcontroller,
Application Specific Integrated Circuits (ASIC), Field Programmable Gate Array
circuits (FPGA), any other type of integrated circuits, etc.
[0041] As used herein the transceiver unit include at least one receiver and at least
20 one transmitter configured respectively for receiving and transmitting data, signals,
information or a combination thereof between units/components within the system and/or connected with the system.
[0042] As discussed in the background section, the current known solutions for
25 sales order management at an organization level have several shortcomings such as
they do not allow possibility of restructuring approval flow in sales orders, are time-consuming, and require a tedious process of modifying code, whenever it is required to make a change in order, or for adding an exception therein.
30 [0043] The present disclosure aims to overcome the above-mentioned and other
existing problems in this field of technology by providing method and system of managing a work order flow. The present disclosure allows the possibility of restructuring approval flow in sales orders. This system provides an efficient and
11

effective way of making a change or requesting an exception without going back to
the previous stakeholder. By using this system, the administrator can make runtime
configurations by using Command Line Interface (CLI) or via UI. This means that
approvals configurations can be made dynamically in cache, without having to wait
5 for a planned event.
[0044] The present invention provides a solution may be handle complex scenarios,
adapt to changing requirements, and reduce the maintenance burden. The present
invention provides a method for efficiently managing work order flows using a
10 structured and configurable system. It uses different units to manage various stages
of the approval process, ensuring everything runs smoothly and efficiently.
[0045] FIG. 1 illustrates an exemplary block diagram of a computing device [100] upon which the features of the present disclosure may be implemented in
15 accordance with exemplary implementation of the present disclosure. In an
implementation, the computing device [100] may also implement a method for managing performance data of a node in a network utilising the system. In another implementation, the computing device [100] itself implements the method for managing performance data of a node in a network using one or more units
20 configured within the computing device [100], wherein said one or more units are
capable of implementing the features as disclosed in the present disclosure.
[0046] The computing device [100] may include a bus [102] or other communication mechanism for communicating information, and a hardware
25 processor [104] coupled with bus [102] for processing information. The hardware
processor [104] may be, for example, a general-purpose microprocessor. The computing device [100] may also include a main memory [106], such as a random-access memory (RAM), or other dynamic storage device, coupled to the bus [102] for storing information and instructions to be executed by the processor [104]. The
30 main memory [106] also may be used for storing temporary variables or other
intermediate information during execution of the instructions to be executed by the processor [104]. Such instructions, when stored in non-transitory storage media
12

accessible to the processor [104], render the computing device [100] into a special-
purpose machine that is customized to perform the operations specified in the
instructions. The computing device [100] further includes a read only memory
(ROM) [108] or other static storage device coupled to the bus [102] for storing static
5 information and instructions for the processor [104].
[0047] A storage device [110], such as a magnetic disk, optical disk, or solid-state drive is provided and coupled to the bus [102] for storing information and instructions. The computing device [100] may be coupled via the bus [102] to a
10 display [112], such as a cathode ray tube (CRT), Liquid crystal Display (LCD),
Light Emitting Diode (LED) display, Organic LED (OLED) display, etc. for displaying information to a computer user. An input device [114], including alphanumeric and other keys, touch screen input means, etc. may be coupled to the bus [102] for communicating information and command selections to the processor
15 [104]. Another type of user input device may be a cursor controller [116], such as
a mouse, a trackball, or cursor direction keys, for communicating direction information and command selections to the processor [104], and for controlling cursor movement on the display [112]. The input device typically has two degrees of freedom in two axes, a first axis (e.g., x) and a second axis (e.g., y), that allow
20 the device to specify positions in a plane.
[0048] The computing device [100] may implement the techniques described herein using customized hard-wired logic, one or more ASICs or FPGAs, firmware and/or program logic which in combination with the computing device [100] causes
25 or programs the computing device [100] to be a special-purpose machine.
According to one implementation, the techniques herein are performed by the computing device [100] in response to the processor [104] executing one or more sequences of one or more instructions contained in the main memory [106]. Such instructions may be read into the main memory [106] from another storage medium,
30 such as the storage device [110]. Execution of the sequences of instructions
contained in the main memory [106] causes the processor [104] to perform the
13

process steps described herein. In alternative implementations of the present disclosure, hard-wired circuitry may be used in place of or in combination with software instructions.
5 [0049] The computing device [100] also may include a communication interface
[118] coupled to the bus [102]. The communication interface [118] provides a two-way data communication coupling to a network link [120] that is connected to a local network [122]. For example, the communication interface [118] may be an integrated services digital network (ISDN) card, cable modem, satellite modem, or
10 a modem to provide a data communication connection to a corresponding type of
telephone line. As another example, the communication interface [118] may be a local area network (LAN) card to provide a data communication connection to a compatible LAN. Wireless links may also be implemented. In any such implementation, the communication interface [118] sends and receives electrical,
15 electromagnetic or optical signals that carry digital data streams representing
various types of information.
[0050] The computing device [100] can send messages and receive data, including
20 program code, through the network(s), the network link [120] and the
communication interface [118]. In the Internet example, a server [130] might
transmit a requested code for an application program through the Internet [128], the
ISP [126], the local network [122], the host [124] and the communication interface
[118]. The received code may be executed by the processor [104] as it is received,
25 and/or stored in the storage device [110], or other non-volatile storage for later
execution.
[0051] Referring to FIG. 2, an exemplary block diagram of a system [200] for
managing a work order flow, in accordance with the exemplary implementations of
30 the present disclosure, is shown. The system [200] comprises at least one
transceiver unit [202], at least one identification unit [204], at least one processing
14

unit [206], and at least one analysis unit [208]. Also, all the components/ units of
the system [200] are assumed to be connected to each other unless otherwise
indicated below. As shown in the figures all units shown within the system should
also be assumed to be connected to each other. Also, in FIG. 2, only a few units are
5 shown, however, the system [200] may comprise multiple such units or the system
[200] may comprise any such numbers of said units, as required to implement the
features of the present disclosure. Further, in an implementation, the system [200]
may be present in a user device to implement the features of the present disclosure.
The system [200] may be a part of the user device / or may be independent of but
10 in communication with the user device (may also referred herein as a UE). In
another implementation, the system [200] may reside in a server or a network entity. In yet another implementation, the system [200] may reside partly in the server/ network entity and partly in the user device.
15 [0052] The system [200] is configured for managing a work order flow, with the
help of the interconnection between the components/units of the system [200].
[0053] In operation, in one example, the transceiver unit [202] may be configured to receive one or more work processes associated with the work order. The present
20 disclosure encompasses that the transceiver unit [202] unit is responsible for
receiving one or more work processes associated with a specific work order. Such work processes, as would be understood, may be tasks or steps that need to be completed as part of the work order. In one example, the work order may be a formal document or digital record that outlines specific tasks to be completed,
25 including details such as task descriptions, assigned personnel, required materials,
deadlines, and instructions. Such tasks may be the one or more work processes associated with the work order.
[0054] For example: In a sales order management system, for a work order
30 pertaining to sales order, the work processes could involve tasks such as order entry,
invoicing, shipping, and payment processing. In one example, in the context of the
work order relating to purchase of a Subscriber Identity Module (SIM) card,
15

examples of work processes may include, but are not limited to, inputting
parameters like Task ID, Task Description, assigning Personnel (Employee ID),
assigning purchase order for Materials (Material ID, Quantity), setting deadlines
(Start Date, End Date), feeding Instructions, feeding Customer Information (Name,
5 Address, Contact), entering Order Details (Product ID, Quantity, Price), entering
customer Information (Customer ID, Document Type, Document Number, Expiry
Date), Billing Type (Post-paid, Prepaid, or Hybrid), Customer Category
(Individual, Outstation, or Foreigner), Customer Type (Retail, Enterprise,
Corporate).
10
[0055] In another example, upon receiving one or more work processes associated
with the work order, the system [200] may initiate an authentication before
proceeding with the next steps. For example, in the context of the above-provided
example of purchasing a SIM card, customer authentication may be performed
15 before initiating the work order flow management. In one example, the customer
may be required to provide identification documents for the same.
[0056] However, it may be noted that above-provided examples of work process
and work order are only exemplary, and in no manner is to be construed to limit the
20 scope of the present subject matter in any manner. Other examples of work order,
and corresponding work processes may also be considered, and would lie within the scope of the present subject matter.
[0057] Continuing with the present example, thereafter, the identification unit
25 [204], connected to at least the transceiver unit [202], may identify one or more
process at a same level as said process. The same level of a process herein refers to
same hierarchical level of the current process. The present disclosure encompasses
that the identification unit [204] identifies processes at the same hierarchical level
as the current process. As described previously, examples of the one or more
30 processes associated with the work order may include, but are not limited to, one or
more processes in a sale order management system, one or more processes between one or more customers, one or more processes between one or more channel
16

partners, one or more processes between a plurality of third-party service providers,
and one or more processes between a plurality of third-party vendors. In another
example, these processes can be selected from a range of applications, including
processes within a sales order management system, which may involve tasks such
5 as order entry, invoicing, shipping, and payment processing between one or more
customers and communication activities between one or more channel partners, which involve collaborative tasks such as order coordination between a plurality of third-party service providers, including, maintenance, and outsourced service operations between a plurality of third-party vendors.
10
[0058] Out of all the received work processes, associated with the work order, the identification unit [204] may identify one or more processes at same level. For example, in the context of the work order pertaining to purchase of a SIM card, examples of different hierarchical levels may include, but are not limited to,
15 Headquarter, billing location, and Authorised Signatory. In such case, all the work
processes may be categorised as to which department would be handling the work process. Based on the categorisation, processes at different levels may be identified.
[0059] Continuing further, the processing unit [206], connected to at least the
20 identification unit [204], may determine a completion status of the one or more
same level process. The present disclosure encompasses that the processing unit
[206] is to determine the completion status of one or more processes that are at the
same hierarchical level as the current process within the work order. This
determination involves assessing whether these parallel processes have been
25 completed, thereby enabling the system to make informed decisions regarding the
progression of the work order.
[0060] Thereafter, the transceiver unit [202] may receive an approval response for
a next milestone associated with the work process. The approval response may be
30 generated based on determination of the completion status of the same level
process. For example, the present disclosure encompasses that, after the processing unit [206] determines that one or more same level process has been
17

initiated/completed/failed, an approval response may be generated. Such approval
response may indicate a status of completion of the one or more same level process.
However, it may be noted that the generated approval response may include other
stratus fields as well, and such examples would also lie within the scope of the
5 present subject matter. Further, the next milestone refers herewith the critical
checkpoint following the completion and approval of a current work process. For
example, in a telecommunication company's workflow for deploying new network
infrastructure, the current work process might involve installing network hardware
in a central office. Once the installation is completed, the transceiver unit [202]
10 receives an approval response confirming the installation’s success. The analysis
unit detects this approval and performs the action of moving to the next milestone, which is testing and validating.
[0061] In one example, the approval response is received from one of an
15 Application Programming Interface (API), a user interface, and an inbound call.
[0062] The analysis unit [208] may then detect a status of the approval response.
Examples of such status include, but are not limited to, pending status, complete
status, failure status, and a require rework status. Such status may indicate the status
20 of the same level process, thereby allowing the system [200] to determine as to how
to progress with the subsequent milestones of the work order. The analysis unit
[208] thus ensures that the system can accurately assess the progress and status of
tasks within the work order management process based on the received approval
responses.
25
[0063] Thereafter, the analysis unit [208] may perform an action based on the
detected status of the approval response and a predefined mandate parameter
associated with the one or more work processes. The present disclosure
encompasses the analysis unit [208] to execute specific actions based on two main
30 factors: the status detected within the approval response and a predefined mandate
parameter linked to one or more work processes. The performing involves the
actions taken by the analysis unit [208] based on the detected status of the approval
18

response. The steps may include evaluating the detected status, comparing and executing the required actions based on the evaluation.
[0064] For example, if the status is 'approved', the system might automatically start
5 performance testing on the updated network nodes.
[0065] In an example, the action performed based on the approval response can
include moving to the next process if the status is approved, sending notifications
if additional approvals or rework are required, initiating corrective measures or
10 escalations in case of failures.
[0066] The predefined mandate parameter is a specific, pre-established condition
within the work order management system that guides decision-making processes.
Configured before the execution of work processes, it acts as a conditional variable
15 influencing how the system responds to various statuses of these processes.
[0067] In an event a value of the predefined mandate parameter is positive and the
status of the approval response, associated with the same level work process, is a
pending status, the processing unit [206] is further configured to wait for a time
20 period till each of the plurality of same level processes are completed. Upon
completion of each of the plurality of same level processes, the processing unit [206] may then execute the next process associated with the work order.
[0068] In an example, executing the next process involves initiating the task after
25 the previous task has been approved. This may include allocating resources for the
next task, assigning tasks to relevant teams or systems, initiating the required steps for the next phase.
[0069] Thus, in such cases, the processing unit [206] is programmed to terminate
30 its execution temporarily. The positive predefined mandate may indicate that a
process mandatorily needs to be completed. During this pause, it waits for a specified duration until all processes at the same hierarchical level are completed. Once each of these parallel processes successfully conclude, the processing unit
19

[206] resumes its operation and proceeds to execute the subsequent process associated with the work order.
[0070] As would be noted, such situations, as described above, may indicate that
5 the work process with positive predefined mandate parameter is crucial to be
completed, and the execution of the work order will be paused until all the same
level processes, with positive predefined mandate parameters, have been executed.
[0071] In another example, in event if the predefined mandate parameter is positive
10 and the approval response status for the same level work process indicates a
complete status, the processing unit [206] is further configured to execute the next
process associated with the work order. This means that upon determining that the
current level process is completed, and all conditions set by the mandate parameter
are satisfied, the processing unit [206] automatically advances to the next task in
15 the workflow.
[0072] In yet another example, in an event a value of the predefined mandate parameter is positive and the status of the approval response, associated with the same level work process, is one of a failure status and a require rework status, the
20 analysis unit [208] is further configured to trigger a notification for a POS (Point of
Sale) to initiate one of a refund and a requirement of documents. The triggering refers to automatic initiation of actions based on predefined conditions. The actions triggered may include sending notifications to relevant personnel, updating status in network management systems and the like. The notifications instruct the POS
25 system to initiate either a refund process or a request for additional documents (such
as certificates, customer service logs, network configuration files, or maintenance
records). This functionality ensures that appropriate corrective actions are promptly
taken in response to failed or incomplete processes, considering the positive
predefined mandate parameter and the necessity to complete the said work process.
30
[0073] In yet another example, in an event a value of the predefined mandate
parameter is negative and the status of the approval response, associated with the
20

same level work process, is a complete status. The processing unit [206] is further configured to mark said one or more work process as completed.
[0074] Referring to FIG. 3, an exemplary method flow diagram [300] for managing
5 a work order flow, in accordance with exemplary implementations of the present
disclosure is shown. In an implementation, the method [300] may be performed by
the system [200]. Further, in an implementation, the system [200] may be present
in a server device to implement the features of the present disclosure. Also, as
shown in FIG. 3, the method [300] starts at step [302].
10
[0075] At step [304], the method [300] comprises, receiving, by a transceiver unit
[202], one or more work processes associated with the work order. The present
disclosure encompasses the transceiver unit [202] unit is responsible for receiving
one or more work processes associated with the specific work order. In one
15 example, these work processes may be tasks or, steps that need to be completed as
part of the work order. In another example, the work order may be a formal document or digital record that outlines specific tasks to be completed, including details such as task descriptions, assigned personnel, required materials, deadlines, and instructions. Such tasks may be the one or more work processes associated with
20 the work order.
[0076] For example: In a sales order management system, for a work order pertaining to sales order, the work processes could involve tasks such as order entry, invoicing, shipping, and payment processing. In one example, in the context of the
25 work order relating to purchase of a Subscriber Identity Module (SIM) card,
examples of work processes may include, but are not limited to, inputting parameters like Task ID, Task Description, assigning Personnel (Employee ID), assigning purchase order for Materials (Material ID, Quantity), setting deadlines (Start Date, End Date), feeding Instructions, feeding Customer Information (Name,
30 Address, Contact), entering Order Details (Product ID, Quantity, Price), entering
customer Information (Customer ID, Document Type, Document Number, Expiry Date), Billing Type (Post-paid, Prepaid, or Hybrid), Customer Category
21

(Individual, Outstation, or Foreigner), Customer Type (Retail, Enterprise, Corporate).
[0077] In another example, upon receiving one or more work processes associated
5 with the work order, the system [200] may initiate an authentication before
proceeding with the next steps. For example, in the context of the above-provided
example of purchasing a SIM card, customer authentication may be performed
before initiating the work order flow management. In one example, the customer
may be required to provide identification documents for the same.
10
[0078] However, it may be noted that above-provided examples of work process
and work order are only exemplary, and in no manner is to be construed to limit the
scope of the present subject matter in any manner. Other examples of work order,
and corresponding work processes may also be considered, and would lie within
15 the scope of the present subject matter. The next milestone refers herewith the
critical checkpoint following the completion and approval of a current work process. For example, in a telecommunication company's workflow for deploying new network infrastructure, the current work process might involve installing network hardware in a central office. Once this installation is completed, the
20 transceiver unit [202] receives an approval response confirming the installation’s
success. The analysis unit [208] detects this approval and performs the action of moving to the next milestone, which is testing and validating the installed hardware.
[0079] At step [306], the method [300] comprises, identifying, by an identification
25 unit [204], one or more process at a same level as said process. The present
disclosure encompasses that the identification unit [204] identifies processes at the
same hierarchical level as the current process. As described previously, examples
of the one or more processes associated with the work order may include, but are
not limited to, one or more processes in a sale order management system, one or
30 more processes between one or more customers, one or more processes between
one or more channel partners, one or more processes between a plurality of third-party service providers, and one or more processes between a plurality of third-
22

party vendors. In another example these processes can be selected from a range of
applications, including processes within a sales order management system, which
may involve tasks such as order entry, invoicing, shipping, and payment processing
between one or more customers and communication activities between one or more
5 channel partners, which involve collaborative tasks such as order coordination
between a plurality of third-party service providers, including, maintenance, and outsourced service operations between a plurality of third-party vendors.
[0080] Out of all the received work processes, associated with the work order, the
10 identification unit [204] may identify one or more processes at a same level. For
example, in the context of the work order pertaining to purchase of a SIM card,
examples of different hierarchical levels may include, but are not limited to,
Headquarter, billing location, and Authorised Signatory. In such case, all the work
processes may be categorised as to which department would be handling the work
15 process. Based on the categorisation, processes at different levels may be identified.
[0081] At step [308], the method [300] comprises, determining, by a processing
unit [206], a completion status of the one or more same level process. The present
disclosure encompasses that the processing unit [206] is to determine the
20 completion status of one or more processes that are at the same hierarchical level
as the current process within the work order. This determination involves assessing whether these parallel processes have been completed, thereby enabling the system to make informed decisions regarding the progression of the work order.
25 [0082] At step [310], the method [300] comprises receiving, by the transceiver unit
[202], an approval response for a next milestone associated with the work process.
The approval response may be generated based on determination of the completion
status of the same level process. Further, the generated approval response may
include a status of completion of the one or more same level process.
30
[0083] For example, the present disclosure encompasses that, after the processing
unit [206] determines that one or more same level process has been
23

initiated/completed/failed, an approval response may be generated. Such approval
response may indicate a status of completion of the one or more same level process.
However, it may be noted that the generated approval response may include other
stratus fields as well, and such examples would also lie within the scope of the
5 present subject matter.
[0084] In one example, the approval response is received from one of an Application Programming Interface (API), a user interface, and an inbound call.
10 [0085] At step [312], the method [300] further comprises detecting, by an analysis
unit [208], a status of the approval response. Examples of such status include, but are not limited to, pending status, complete status, failure status, and a require rework status. Such status may indicate the status of the same level process, thereby allowing the system [200] to determine as to how to progress with the subsequent
15 milestones of the work order. The analysis unit [208] thus ensures that the system
can accurately assess the progress and status of tasks within the work order management process based on the received approval responses.
[0086] Thereafter, at step [314], the method [300] comprises performing, by the
20 analysis unit [208], an action based on the detected status of the approval response
and a predefined mandate parameter associated with the one or more work processes.
[0087] The present disclosure encompasses the analysis unit [208] to execute
25 specific actions based on two main factors: the status detected within the approval
response and a predefined mandate parameter linked to one or more work processes.
[0088] The performing involves the actions taken by the analysis unit [208] based
on the detected status of the approval response. The steps may include evaluating
30 the detected status, comparing and executing the required actions based on the
evaluation. For example, if the status is 'approved', the system might automatically start performance testing on the updated network nodes.
24

[0089] In an example, the action performed based on the approval response can
include moving to the next process if the status is approved, sending notifications
if additional approvals or rework are required, initiating corrective measures or
escalations in case of failures.
5
[0090] The predefined mandate parameter is a specific, pre-established condition
within the work order management system that guides decision-making processes.
Configured before the execution of work processes, it acts as a conditional variable
influencing how the system responds to various statuses of these processes.
10
[0091] In an event a value of the predefined mandate parameter is positive and the
status of the approval response, associated with the same level work process, is a
pending status, the processing unit [206] is further configured to wait for a time
period till each of the plurality of same level processes are completed. Upon
15 completion of each of the plurality of same level processes, the processing unit
[206] may then execute the next process associated with the work order.
[0092] In an example, executing the next process involves initiating the task after
the previous task has been approved. This may include allocating resources for the
20 next task, assigning tasks to relevant teams or systems, initiating the required steps
for the next phase.
[0093] Thus, in such cases, the processing unit [206] is programmed to terminate
its execution temporarily. The positive predefined mandate may indicate that a
25 process mandatorily needs to be completed. During this pause, it waits for a
specified duration until all processes at the same hierarchical level are completed.
Once each of these parallel processes successfully concludes, the processing unit
[206] resumes its operation and proceeds to execute the subsequent process
associated with the work order.
30
[0094] As would be noted, such situations, as described above, may indicate that
the work process with positive predefined mandate parameter is crucial to be
25

completed, and the execution of the work order will be paused until all the same level processes, with positive predefined mandate parameters, have been executed.
[0095] In another example, in event if the predefined mandate parameter is positive
5 and the approval response status for the same level work process indicates a
complete status.
[0096] In an event a value of the predefined mandate parameter is positive and the
status of the approval response, associated with the same level work process, is a
10 complete status, the processing unit [206] is further configured to execute the next
process associated with the work order. This means that upon determining that the
current level process is completed, and all conditions set by the mandate parameter
are satisfied, the processing unit [206] automatically advances to the next task in
the workflow.
15
[0097] In yet another example, in an event a value of the predefined mandate
parameter is positive and the status of the approval response, associated with the
same level work process, is one of a failure status and a require rework status, the
analysis unit [208] is further configured to trigger a notification for a POS (Point of
20 Sale) to initiate one of a refund and a requirement of documents. The triggering
refers to the automatic initiation of actions based on predefined conditions. The actions triggered may include sending notifications to relevant personnel, updating status in network management systems. This notification instructs the POS system to initiate either a refund process or a request for additional documents (such as
25 certificates, customer service logs, network configuration files, or maintenance
records). This functionality ensures that appropriate corrective actions are promptly taken in response to failed or incomplete processes considering the positive predefined mandate parameter and the necessity to complete the said work process. In yet another example, in an event a value of the predefined mandate parameter is
30 negative and the status of the approval response, associated with the same level
work process, is a complete status, the processing unit [206] is further configured to mark said one or more work process as completed.
26

[0098] Thereafter, the method terminates at step (316).
[0099] Referring to FIG. 4, an exemplary system architecture diagram [400] for
5 managing a work order flow, in accordance with exemplary implementations of the
present disclosure.
[0100] In an exemplary embodiment, the system architecture [400] may include sub-components of the system [200] (as shown in FIG. 2) of the current disclosure.
10 In another embodiment, the architecture [400] may be used to implement the steps
of method [300] (as shown in FIGg. 3) for dynamically creating a work order along with the system [200] (as shown in FIG. 2) which is based on the architecture [400] of the system [200]. In a preferred embodiment, the architecture [400] of the system 1comprises a plurality of components. For example, and by no way limiting the
15 scope of the present subject matter, the system architecture [400] (as shown in FIG.
4 ) comprises an evolved packet core (EPC) [402], a fulfilment management system (FMS) [404], a plurality of channels [406], a load balancer [408], a customer relationship manager (CRM)/ customer engagement manager (CEM) server [410] comprising a plurality of micro-services and a database [412]. The channels [414]
20 are configured to provide input data to the CRM server [416] through a load
balancer [418]. In an embodiment, some examples of the channels include but are not limited to an POS [420], a data management platform DMP [422], a SELFCARE [424] and a CRM user interface (UI) [426]. It is to be noted that the workflow engine is mix of generic configurations and it also provides space for
25 custom logic so that all the milestones / order journeys can be autonomous and
segregated.
[0101] The CRM [410] servers containing different micro services which cater to different APIs. Each microservices serves a particular context, for e.g.,
30 • COP_MS deals with order related APIs – submit order, query order,
modify order
27

• CIS instances deal with customer related APIs – create, modify or deactivate customer
• L2O instances deals with APIs that manages the lifecycle of leads and prospects
5 • OAM instance deals with the maintenance and operation of all the
microservice instances and communicate with outer products related to alarms, KPIs or other management, health check-up information
• Channels [406] from which, hit the APIs to servers e.g. RPOS (Point
of Sale) [420], Digital Marketplace (DMP) [422], Self-Care [424], CRM UI
10 [426] etc. These channels are connected to servers using load balancer or
FMS [404]. The channels [406] which are tightly coupled to CRM [410] e.g. CRM UI [426] communicates directly via Load balancer while other systems which belong to different product such as self-care, POS [420] communicates to servers using FMS [404]. The FMS [404] is a middleware which links two
15 different products and performs language translations or workflow
management.
• EPC (Enterprise Product Catalogue) [402], a centralised data repository
which drives BSS telecom operations and some network nodes too for e.g.,
5G charging system, called PCF.
20 • FMS (Fulfilment Management System) [404], a middleware, which acts a
mediator between two different products and at the same time, provides language translation. E.g., if one product understands SOAP protocol while other one understands RESTful services, FMS will translate the messages between these 2 nodes and ensure seamless communication.
25 • Databases [412] connected to servers which persist the business data related
to customers, orders, leads, prospects and server configurations
• SMP [428] – SMP [428] refers to Service Management Platform (SMP).
The services of SMP [428] work in tandem to provide workflow
management, customer assurance, resource assurance and service assurance
30 functions. The SMP [242] integrates with operations support systems
28

(OSS)/ business support systems (BSS) platforms like the customer relationship management (CRM) [410], etc
[0102] FIG. 5A illustrates a flow diagram for a set of work processes associated
with an exemplary work order, such as a mobile number portability (MNP)
5 scenario, in accordance with an exemplary implementation of the present
disclosure.
[0103] 1st Approval, [501] 2nd Approval [502], and 3rd Approval [503]: These are
the initial stages in the work order approval process where a set of levels of
10 validation and approval occurs. Although depicted as three subsequent levels in
FIG. 5A, it may be noted that the same is done only for the sake of clarity. Any number of subsequent levels of approvals may be performed in the work order.
[0104] 4th Approval stage [504]: Following the successful completion of a set of
15 approval, three in the present example as depicted in FIG. 5A, the work order may
then proceed to the next level, i.e., 4th Approval stage [504]. The identification unit
[204] may identify processes at the same hierarchical level as the current process.
As depicted in FIG. 5A, two processes may be there to be executed at 4th approval
stage [504], i.e., ‘A’ and ‘B’. Although only two processes have been depicted, it
20 may be noted that the same is done only for the sake of clarity. Any number of
processes may be there, and all such examples would lie within the scope of the
present subject matter.
[0105] Thereafter, the processing unit [206] may then determine the completion
25 status of the process ‘A’ and process ‘B’.
[0106] Based on an approval response of the process ‘A’ and process ‘B’, the work
order may proceed to next level, i.e., 5th Approval stage [505]. The approval
response may be generated based on determination of the completion status of the
30 process ‘A’ and process ‘B’.
29

[0107] Upon determining that both the process ‘A’ and process ‘B’ are completed, and all conditions set by the mandate parameter are satisfied, the processing unit [206] automatically advances to the next task in the workflow.
5 [0108] As depicted in FIG. 5A, the value of the predefined mandate parameter may
be negative. Such negative predefined mandate parameter may indicate that
regardless of whether the 4th stage processes are completed or not, the work order
may proceed to the 5th stage. The processing unit [206] may mark said one or more
work process as completed.
10
[0109] In another example, it may be the case that the value of the predefined
mandate parameter may be positive. Such positive predefined mandate parameter
may indicate that such processes may mandatorily need to be completed. This has
been depicted in FIG. 5B. FIG. 5B illustrates a flow diagram for a set of work
15 processes associated with an exemplary work order, such as a mobile number
portability (MNP) scenario, in accordance with another exemplary implementation
of the present disclosure.
[0110] In such cases, when the status of the approval response, associated with the
20 process ‘A’ and process ‘B’, is a pending status, the processing unit [206] is further
configured to wait for a time period till process ‘A’ and process ‘B’ completes. Upon completion of the process ‘A’ and process ‘B’, the processing unit [206] executes the process at 5th approval stage [512].
25 [0111] In another example, when the approval response status for the process ‘A’
and process ‘B’ indicates a complete status, the processing unit [206] executes the process at 5th approval stage [512]. This means that upon determining that the current level process is completed, and all conditions set by the mandate parameter are satisfied, the processing unit [206] automatically advances to the next task in
30 the workflow.
[0112] FIG. 6 illustrates a flow diagram [600] for managing a work order flow, in accordance with exemplary implementations of the present disclosure.
30

[0113] At step S1: The process begins with the Milestone Processor responsible for
acknowledging the completion of previous milestones. This task is managed by the
transceiver unit [202], which is configured to receive information about the work
5 processes associated with the work order. These work processes may include tasks
or steps that need to be completed as part of the work order.
[0114] At step S2: Once the previous milestone is marked complete, the transceiver
unit [202] transitions to the milestone processor, which enters the approval phase.
10 The transceiver unit [202] receives and processes the approval request for the next
set of tasks within the work order.
[0115] At step S3: The identification unit [204] identifies processes at the same
hierarchical level as the current process. Examples include tasks within a sales order
15 management system such as order entry, invoicing, shipping, and payment
processing between one or more customers and communication activities between one or more channel partners.
[0116] At step S4: The system [200] enters a waiting phase after initiating an
20 approval request for a process within the work order. The system [200] remains in
this state until it receives an approval response. During this period, the system [200] may monitor various channels (e.g., automated systems, personnel input, external systems) to detect when an approval response is submitted.
25 [0117] At step S5: Once the approval response is received, the processing unit [206]
recognizes the incoming data or message that indicates whether the requested approval for the task or process has been granted or denied.
[0118] At step S6: The system [200] detected approval response to check if it is
30 successful. This involves assessing whether the response meets the predefined
criteria for success.
31

[0119] If the Response is Successful: The system [200] proceeds to Step S8, where it moves on to the next approval phase or process.
If the Response is Not Successful: The system [200] proceeds to Step S7 to handle the rejection or failure scenario. 5
[0120] At step S7: If the approval response indicates a failure or rejection, the system [200] takes corrective actions. In this step:
[0121] Execute CAF Rejection: The system [200] initiates a rejection process for
10 the Customer Application Form (CAF). This involves marking the form and the
associated process as rejected due to the unsuccessful approval. The rejection might be logged, and relevant records updated to reflect this status.
[0122] Trigger Notification for POS Refund: The system [200] sends a notification
15 to the Point of Sale (POS) system to initiate a refund process. This notification
informs the POS system that a refund needs to be processed for the customer due to the rejection. Alternatively, the system [200] might request additional documents if necessary to resolve the issues leading to the rejection.
20 [0123] At step S8: This involves preparing for the subsequent set of tasks or
processes within the work order that require approval. The system [200] then enters a waiting state where it monitors and waits for the response to the approval request for these new tasks. During this waiting period, the system [200] may continuously check for updates or responses from relevant entities (e.g., personnel, systems, or
25 automated responses).
[0124] At step S9: Once the system [200] receives the approval responses for the
tasks, it moves towards the final approval phase. This final response may come
from various sources, such as an API call, a user interface input, or an inbound call,
30 indicating the culmination of the approval process for the work order.
32

[0125] At step S10: The system [200] assesses the final approval response to determine its success. The process involves checking whether the final response meets the predefined criteria for a successful approval.
5 [0126] If the Final Response is Successful: The system proceeds to Step S11.
[0127] If the Final Response is Not Successful: The system proceeds to Step S13.
[0128] At step S11: Upon receiving a successful final approval response, the
10 system [200] marks the current approval milestone as complete. This step involves
updating the status of the work order to reflect the completion of the milestone.
[0129] At step S12: Following the completion of the current milestone, the system
[200] prepares to move on to the next milestone in the work order process. This step
15 involves transitioning from the recently completed tasks to the upcoming set of
tasks or processes. The system [200] reconfigures itself to handle the requirements and actions needed for the next milestone. This might include reassigning tasks, allocating resources, and setting up any necessary parameters for the next phase.
20 [0130] At step S13: If the final approval response indicates failure or is
unsuccessful, the system [200] takes corrective actions by executing a Customer Application Form (CAF) rejection. This step involves initiating a rejection process, which may include sending notifications to systems to inform them of the failure. Additionally, the system [200] triggers a notification for the Point of Sale (POS) to
25 initiate a refund process or take other appropriate actions.
[0131] As would be appreciated, the approaches of the present subject matter may
provide a number of technical advancements, such as the approval configuration,
which is designed to handle complex scenarios and minimize the need for
30 retrospective fixes through a streamlined release cycle. The approval configuration
includes the levels (Integer data type) and mandatory (Boolean data type) parameters maintained in each configuration.
33

[0132] As would be further appreciated, the technical execution of an approval item occurs in two phases:
• Approval Phase: When an order becomes eligible for approval, an approval
5 unit is activated. The separate units exist in the workflow for each approval
role, and the approval engine invokes the appropriate unit based on the role and actions performed during this phase can include the system invokes an API to an external system, receives a synchronous response, and acts according to the response code. Alternatively, it might stall the order and
10 wait for a callback response. In another example, a web hook is triggered,
or a scheduler is registered to perform activities at a predetermined time. The approval item might be directly marked as successful if there is no current business process for that item. The approval item can be exposed to a UI agent for manual intervention. If the is Mandatory flag is false, the
15 system sends the order to the next approval stage without waiting for the
current approval.
• Response Handling Phase: When a response (Success, Failure, or Rework)
is received from a UI agent or scheduled activity, a response handling unit
is activated. The separate units exist for each approval role, and the approval
20 engine invokes the appropriate unit upon receiving the approval verdict.
This unit marks the approval item as successful and proceeds the order to the next stage.
[0133] The present disclosure further discloses a non-transitory computer readable
25 storage medium storing instructions for managing a work order flow, the
instructions include executable code which, when executed by a one or more units
of a system [200], causes: a transceiver unit [202] of the system [200] to receive
one or more work processes associated with the work order. Further, the
instructions include executable code, which when executed causes the identification
30 unit [204] of the system [200] to identify one or more process at a same level as
said process. Further, the instructions include executable code, which when
34

executed causes the processing unit [206] of the system [200] to determine a
completion status of the one or more same level process. Further, the instructions
include executable code, which when executed causes the transceiver unit [202] of
the system [200] to receive an approval response for a next milestone, associated
5 with the work process, wherein the approval response is generated based on
determination of the completion status of the same level process, and wherein the
generated approval response comprises a status of completion of the one or more
same level process. Further, the instructions include executable code, which when
executed causes the analysis unit [208] of the system [200]: to detect a status of the
10 approval response, and to perform an action based on the detected status of the
approval response and a predefined mandate parameter associated with the one or more work processes.
[0134] As is evident from the above, the present disclosure provides a technically
15 advanced solution for managing a work order flow. The present solution provides
a technically advanced solution for restructure of order. Overall, the proposed
system [200] allows possibility of restructuring approval flow in orders. By
implementing a more flexible and dynamic process that incorporates parallel
approvals and digital tools, telecom companies can meet the demands of today's
20 customers and improve their bottom line.
[0135] While considerable emphasis has been placed herein on the disclosed
implementations, it will be appreciated that many implementations can be made and
that many changes can be made to the implementations without departing from the
25 principles of the present disclosure. These and other changes in the implementations
of the present disclosure will be apparent to those skilled in the art, whereby it is to be understood that the foregoing descriptive matter to be implemented is illustrative and non-limiting.
30 [0136] Further, in accordance with the present disclosure, it is to be acknowledged
that the functionality described for the various components/units can be
35

implemented interchangeably. While specific embodiments may disclose a
particular functionality of these units for clarity, it is recognized that various
configurations and combinations thereof are within the scope of the disclosure. The
functionality of specific units as disclosed in the disclosure should not be construed
5 as limiting the scope of the present disclosure. Consequently, alternative
arrangements and substitutions of units, provided they achieve the intended functionality described herein, are considered to be encompassed within the scope of the present disclosure.
36

We Claim:
1. A method [300] for managing a work order flow, the method [300]
comprising:
receiving, by a transceiver unit [202], one or more work processes associated with a work order;
identifying, by an identification unit [204], one or more process at a same level as said process;
determining, by a processing unit [206], a completion status of the one or more same level process;
receiving, by the transceiver unit [202], an approval response for a next milestone associated with the work process, wherein the approval response is generated based on determination of the completion status of the same level process, and wherein the generated approval response comprises a status of completion of the one or more same level process;
detecting, by an analysis unit [208], a status of the approval response; and
performing, by the analysis unit [208], an action based on the detected status of the approval response and a predefined mandate parameter associated with the one or more work processes.
2. The method [300] as claimed in claim 1, wherein in an event a value of the
predefined mandate parameter is positive and the status of the approval response,
associated with the same level work process, is a pending status, the action
comprises:
waiting, by the processing unit [206], for a time period till each of the plurality of same level processes are completed; and
upon completion of each of the plurality of same level processes, executing, by the processing unit [206], a next process associated with the work order.
3. The method [300] as claimed in claim 1, wherein in an event a value of the
predefined mandate parameter is positive and the status of the approval response,

associated with the same level work process, is a complete status, the action comprises:
executing, by the processing unit [206], a next process associated with the work order.
4. The method [300] as claimed in claim 1, wherein in an event a value of the
predefined mandate parameter is positive and the status of the approval response,
associated with the same level work process, is one of a failure status and a require
rework status, the action comprises:
triggering, by analysis unit [208], a notification for a POS (Point of Sale) to initiate one of a refund and a requirement of documents.
5. The method [300] as claimed in claim 1, wherein in an event a value of the
predefined mandate parameter is negative and the status of the approval response,
associated with the same level work process, is a complete status, the action
comprises:
marking, by the processing unit [206], said one or more work process as completed.
6. The method [300] as claimed in any one of the claims 1 to 5, wherein the approval response is received from one of an Application Programming Interface (API), a user interface, and an inbound call.
7. The method [300] as claimed in claim 1, wherein the one or more work processes associated with the work order are selected from one of: one or more processes in a sale order management system, one or more processes between one or more customers, one or more processes between one or more channel partners, one or more processes between a plurality of third-party service providers, and one or more processes between a plurality of third-party vendors.
8. A system [200] for managing a work order flow, the system [200] comprising:

a transceiver unit [202] configured to receive one or more work processes associated with a work order;
an identification unit [204] connected to at least the transceiver unit [202], wherein the identification unit [204] configured to identify one or more process at a same level as said process;
a processing unit [206] connected to at least the identification unit [204], wherein the processing unit [206] configured to determine a completion status of the one or more same level process;
the transceiver unit [202] connected to at least the processing unit [206], wherein the transceiver unit [202] is further configured to receive an approval response for a next milestone associated with the work process, wherein the approval response is generated based on determination of the completion status of the same level process, and wherein the generated approval response comprises a status of completion of the one or more same level process;
an analysis unit [208] connected to at least the transceiver unit [202], wherein the analysis unit [208] configured to detect a status of the approval response; and
the analysis unit [208] is further configured to perform an action based on the detected status of the approval response and a predefined mandate parameter associated with the one or more work processes.
9. The system [200] as claimed in claim 8, wherein in an event a value of the
predefined mandate parameter is positive and the status of the approval response, associated with the same level work process, is a pending status, the processing unit [206] is further configured to:
wait for a time period till each of the plurality of same level processes are completed; and
upon completion of each of the plurality of same level processes, execute a next process associated with the work order.

10. The system [200] as claimed in claim 8, wherein in an event a value of the
predefined mandate parameter is positive and the status of the approval response,
associated with the same level work process, is a complete status, the processing
unit [206] is further configured to:
execute a next process associated with the work order.
11. The system [200] as claimed in claim 8, wherein in an event a value of the
predefined mandate parameter is positive and the status of the approval response,
associated with the same level work process, is one of a failure status and a require
rework status, the analysis unit [208] is further configured to:
trigger a notification for a POS (Point of Sale) to initiate one of a refund and a requirement of documents.
12. The system [200] as claimed in claim 8, wherein in an event a value of the
predefined mandate parameter is negative and the status of the approval response,
associated with the same level work process, is a complete status, the processing
unit [206] is further configured to:
mark said one or more work process as completed.
13. The system [200] as claimed in any one of the claims 8 to 12, wherein the approval response is received from one of an Application Programming Interface (API), a user interface, and an inbound call.
14. The system as [200] claimed in claim 8, wherein the one or more work processes associated with the work order are selected from one of: one or more processes in a sale order management system, one or more processes between one or more customers, one or more processes between one or more channel partners, one or more processes between a plurality of third-party service providers, and one or more processes between a plurality of third-party vendors.