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 DYNAMICALLY CREATING
A WORK ORDER”
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 DYNAMICALLY CREATING A WORK
ORDER
TECHNICAL FIELD
[0001] Embodiments of the present disclosure generally relate to work order management. More particularly, embodiments of the present disclosure relate method and system for dynamically creating a work order.
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] Recently, there has been a great expansion of on-demand service environments in all areas of life. All such businesses are dependent on various resources such as service professionals like field professionals, help desk or customer service operators, insurance assessors, business consultants, etc., and their available work hours. Other resources may include vehicles, tools and equipment, spare parts, office space (e.g., meeting rooms), etc. The service tasks are usually initiated by customer requests, and typically cannot be precisely predicted on the micro-level, as there is no way to know when a customer will call and request assistance. Further, as the use of third-party vendors continues to increase within the service and work order industry, the necessity of a strong communication network is apparent.

[0004] For the same reason, various Customer relationship management (CRM) software platforms have been developed and deployed to manage the resources and exchange of the information between such resources. Customer relationship management (CRM) is the combination of technologies, practices, and strategies that companies use to manage and analyse customer/client and/or lead interactions and data throughout the customer life cycle. The objective is to improve customer service relationships and assist in customer retention and drive sales growth. CRM systems compile customer data across different channels, or points of contact, between the customer and the company, which could include the company's website, telephone, live chat, mail, marketing materials, social networks and like others. CRM systems can give customer-facing staff members’ detailed information on customers' personal information, order history, preferences, and concerns.
[0005] Moreover, the Electronic Data Interchange (“EDI”) process has been developed to aid in the interchange of information to expedite business transactions by specifying a consistent data interchange format in a predefined order. Yet, in practice, how each work order site deals with its external environment, i.e., vendors, CMs, customers, has often been archaic and inconsistent.
[0006] For example, a standard process involves receiving a request from a customer / channel, which includes all mandatory information from the customer that is required for processing the task, booking an appointment for the task, determining the relevant third-party vendor, creating a work order, assigning to the professionals / third party vendors, invoicing and so on.
[0007] However, there has been instances where channels / customers are not available with the mandatory information such as (but not limited to) booking appointment beforehand but there is quite a possibility that the information will be available by the time of installation. For example, if a task at channel’s end is in progress which on completion will provide an output which might be used as an information during the installation. Even if the procured channel affirms that it will

incorporate appointment booking capability, it might be subject to delay due to tight service level agreements (SLAs) and development operations (DevOps) lifecycle at their end. However, waiting for availability of such a capability will delay the process of installation since a significant time would be required for the process / ramping up of the business requirements by the vendor which is not appreciated by the channel partners.
[0008] In some other instances, there are multiple vendors who can take up the installation process at a later stage in case an allocated vendor is unavailable / incapable of completing the installation workflow. However, for these alternate vendors to be able to take up the installation order, all the workflows are required to be created redundantly, even in the instances where the alternate vendors are complicit with the original workflows.
[0009] Clearly such a process has various disadvantages such as for example, reduced essence of adaptability, flexibility, and inclusivity in cross-platform Service Oriented Architecture (SoA).
[0010] Further, over the period of time various solutions have been developed to overcome the abovementioned problems. However, there are certain challenges with existing solutions. The conventional enterprise solutions do not have the capability to cater to a next phase task before completing the mandatory fulfilment of previous phase task.
[0011] Thus, there exists an imperative need in the art to enhance functionality while maintaining the cross-platform inclusivity of the work order, which the present disclosure aims to address.
SUMMARY

[0012] 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.
[0013] An aspect of the present disclosure may relate to a method for dynamically creating a work order. The method comprises receiving, by a transceiver unit, a task fulfillment request associated with a work order. It is to be noted that the work order comprises one or more work order parameters. The method further comprises identifying, by the identifier unit, a target task based on the task fulfillment request. The method further comprises identifying, by the identifier unit from a database, a set of vendor profiles based on the target task. It is to be noted that each vendor profile from the set of vendor profiles at least comprises one or more predefined vendor workflow configurations. The method further comprises determining, by the analysis unit, a first vendor profile from the set of vendor profiles based on the one or more work order parameters. The method further comprises fetching, by the retrieving unit from the database, a target predefined vendor workflow configuration associated with the first vendor profile. The method further comprises generating, by the generator unit, the work order comprising the target task based on the target predefined vendor workflow configuration. The method further comprises allocating, by the analysis unit, the work order to the first vendor profile from the set of vendor profiles. The method further comprises identifying, by the identifier unit, a work order status associated with the work order based on allocating the work order to the first vendor profile. It is to be noted that the work order status is at least one of a work order complete status and a work order incomplete status. And, the method further comprises dynamically creating, by the generator unit, the target work order associated with the first vendor profile based on the work order complete status.
[0014] In an exemplary aspect of the present disclosure, the one or more predefined vendor workflow configurations comprises at least one of a fetch appointment slot

configuration, a book appointment slot configuration, and a create workflow order configuration.
[0015] In an exemplary aspect of the present disclosure, the work order complete status is identified by the identifier unit in an event an available vendor status associated with the first vendor profile is detected by the identifier unit and the work order incomplete status is identified by the identifier unit in an event an unavailable vendor status associated with the first vendor profile is detected by the identifier unit.
[0016] In an exemplary aspect of the present disclosure, the method further comprises determining, by the analysis unit, a second vendor profile from the set of vendor profiles, based on the one or more work order parameters in an event the work order incomplete status is detected. The method further comprises allocating, by the analysis unit, the work order to the second vendor profile from the set of vendor profiles based on the work order incomplete status.
[0017] In an exemplary aspect of the present disclosure, the one or more work order parameters comprises at least one of a Product identifier (ID), an Agent identifier (ID), a Bill of Quantity (BOQ) code, and a Stock Keeping Unit (SKU) code.
[0018] In an exemplary aspect of the present disclosure, the dynamically creating by the generator unit, the target work order associated with the first vendor profile based on the work order complete status, further comprises automatically assigning, by the generator unit, at least one professional associated with the first vendor profile. It is to be noted that the at least one professional is selected by the generator unit based on a credibility score and an accountability score of the at least one professional. The dynamically creating by the generator unit of the method further comprises determining, by the generator unit, a positive task completion status for the target task associated with the first vendor profile and assigned to the at least one professional. The dynamically creating by the generator unit of the method

further comprises verifying, by the generator unit, the positive task completion status for the target task. It is to be noted that the positive task completion status is verified based on completion of a set of predefined task steps by the at least one professional.
[0019] In an exemplary aspect of the present disclosure, the set of predefined task steps comprises at least one of a device procurement from warehouse, a service testing and a service verification.
[0020] Another aspect of the present disclosure may relate to a system for dynamically creating a work order. The system comprises a transceiver unit configured to receive a task fulfilment request associated with a work order. It is to be noted that the work order comprises one or more work order parameters. The system further comprises an identifier unit connected to the transceiver unit. The identifier unit is configured to identify a target task based on the task fulfillment request. The identifier unit is further configured to identify, from a database, a set of vendor profiles based on the target task. It is to be noted that each vendor profile from the set of vendor profiles at least comprises one or more predefined vendor workflow configurations. The system further comprises an analysis unit connected to at least the identifier unit, the analysis unit is configured to determine a first vendor profile from the set of vendor profiles based on the one or more work order parameters. The system further comprises a retrieving unit connected to at least the analysis unit, the retrieving unit is configured to fetch, from the database, a target predefined vendor workflow configuration associated with the first vendor profile. The system further comprises a generator unit connected to at least the retrieving unit, the generator unit is configured to generate, the work order comprising the target task based on the target predefined vendor workflow configurations. It is to be noted that the analysis unit is further configured to allocate the work order to the first vendor profile from the set of vendor profiles. It is further noted that the identifier unit is further configured to identify a work order status associated with the work order based on allocating the work order to the first vendor profile. It is

also noted that the work order status is at least one of a work order complete status and a work order incomplete status. It is to be noted that the generator unit is further configured to dynamically create a target work order associated with the first vendor profile based on the work order complete status.
[0021] Another aspect of the present disclosure may relate to a non-transitory computer readable storage medium storing instructions for dynamically creating a work order, 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 a task fulfilment request associated with a work order, the work order comprises one or more work order parameters. Further, the instructions include executable code, which when executed causes an identifier unit of the system to: identify a target task based on the task fulfilment request; and identify, from a database, a set of vendor profiles based on the target task, wherein each of the vendor profile from the set of vendor profiles at least comprises one or more predefined vendor workflow configuration. Further, the instructions include executable code, which when executed causes an analysis unit of the system to determine a first vendor profile from the set of vendor profiles based on the one or more work order parameters. Further, the instructions include executable code, which when executed causes a retrieving unit of the system to fetch, from the database, a target predefined vendor workflow configuration associated with the first vendor profile. Further, the instructions include executable code, which when executed causes a generator unit of the system to generate, the work order comprising the target task based on the target predefined vendor workflow configurations. Further, the instructions include executable code, which when executed causes the analysis unit to further allocate, the work order to the first vendor profile from the set of vendor profiles. Further, the instructions include executable code, which when executed causes the identifier unit to further identify, a work order status associated with the work order based on allocating the work order to the first vendor profile, wherein the work order status is at least one of a work order complete status and a work order incomplete status. Further, the instructions include executable code, which when executed causes the

generator unit to further dynamically create, a target work order associated with the first vendor profile based on the work order complete status.
[0022] Yet another aspect of the present disclosure may relate to a User Equipment
5 (UE) comprising a transceiver unit configured to send, to a system, a task fulfilment
request associated with a work order. It is to be noted that the work order comprises one or more work order parameters. The transceiver unit is further configured to receive, from the system, a work order status associated with the work order. It is further noted that the work order status is at least one of a work order complete
10 status and a work order incomplete status. It is emphasized that the work order
status is identified based on an allocation of the work order, by the system, to a first vendor profile from a set of vendor profiles. And the transceiver unit is further configured to send to the system, a sign-off to close the work order in an event the work order status is the work order complete status.
15
OBJECTS OF THE DISCLOSURE
[0023] Some of the objects of the present disclosure, which at least one embodiment disclosed herein satisfies are listed herein below.
20
[0024] It is an object of the present disclosure to provide a system and a method which allows the possibility of catering a next phase task such as a work order generation for installation purpose before completion of a previous phase task such as fetching and booking appointment slot.
25
[0025] It is another object of the present disclosure to provide a solution that maintains configuration of each vendor with other parameters and decide fulfilment of actions on the basis of availability within the system, during an installation process, such that an alternate vendor may be allocated the work order if required,
30 at any stage during the installation process.
9

[0026] It is a further object of the present disclosure to support ordering of telecommunication services regardless of the service type, service location, service provider or network topology.
5 [0027] It is a further object of the present disclosure to retrieve and store business
rules associated with the services that are provided by multiple vendors and channel partners.
[0028] It is yet another object of the present disclosure to provide a solution to
10 allow a cross-platform inclusivity of multiple vendors and channel partners for
performing a task based on capability and availability of the information.
DESCRIPTION OF THE DRAWINGS
15 [0029] The accompanying drawings, which are incorporated herein, and constitute
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
20 disclosure. Also, the embodiments shown in the figures are not to be construed as
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
25 to implement such components.
[0030] FIG. 1 illustrates an exemplary block diagram of a system for managing cross-platform inclusivity of multiple vendors/channel partners together, in accordance with exemplary embodiments of the present disclosure. 30
10

[0031] FIG. 2 illustrates an exemplary system architecture for managing cross-platform inclusivity of multiple vendors/channel partners together, in accordance with exemplary embodiments of the present disclosure.
5 [0032] FIG. 3 illustrates an exemplary block diagram of a system for dynamically
creating a work order, in accordance with exemplary implementations of the present disclosure.
[0033] FIG. 4 illustrates a method flow diagram for dynamically creating a work
10 order in accordance with exemplary implementations of the present disclosure.
[0034] FIG. 5 illustrates an exemplary flow chart of the process for dynamically creating a work order in accordance with exemplary implementations of the present disclosure. 15
[0035] FIG. 6 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.
20 [0036] The foregoing shall be more apparent from the following more detailed
description of the disclosure.
DETAILED DESCRIPTION
25 [0037] 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 embodiments of the present disclosure may be practiced without these specific details. Several features described hereafter may each be used independently of one
30 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
11

problems discussed above. Some of the problems discussed above might not be
fully addressed by any of the features described herein. Example embodiments of
the present disclosure are described below, as illustrated in various drawings in
which like reference numerals refer to the same parts throughout the different
5 drawings.
[0038] The ensuing description provides exemplary embodiments only, and is not
intended to limit the scope, applicability, or configuration of the disclosure. Rather,
the ensuing description of the exemplary embodiments will provide those skilled in
10 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 disclosure as set forth.
15 [0039] It should be noted that the terms "mobile device", "user equipment", "user
device", “communication device”, “device” and similar terms are used interchangeably for the purpose of describing the disclosure. These terms are not intended to limit the scope of the disclosure or imply any specific functionality or limitations on the described embodiments. The use of these terms is solely for
20 convenience and clarity of description. The disclosure is not limited to any
particular type of device or equipment, and it should be understood that other equivalent terms or variations thereof may be used interchangeably without departing from the scope of the disclosure as defined herein.
25 [0040] 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 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
30 embodiments in unnecessary detail. In other instances, well-known circuits,
12

processes, algorithms, structures, and techniques may be shown without unnecessary detail in order to avoid obscuring the embodiments.
[0041] Also, it is noted that individual embodiments may be described as a process
5 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
10 included in a figure.
[0042] 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
15 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
20 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.
[0043] As used herein, an “electronic device”, or “portable electronic device”, or
25 “user device” or “communication device” or “user equipment” or “device” refers
to any electrical, electronic, electromechanical, and computing device. The user
device is capable of receiving and/or transmitting one or parameters, performing
function/s, communicating with other user devices, and transmitting data to the
other user devices. The user equipment may have a processor, a display, a memory,
30 a battery, and an input-means such as a hard keypad and/or a soft keypad. The user
equipment may be capable of operating on any radio access technology including
13

but not limited to IP-enabled communication, Zig Bee, Bluetooth, Bluetooth Low
Energy, Near Field Communication, Z-Wave, Wi-Fi, Wi-Fi direct, etc. For
instance, the user equipment may include, but not limited to, a mobile phone,
smartphone, virtual reality (VR) devices, augmented reality (AR) devices, laptop,
5 a general-purpose computer, desktop, personal digital assistant, tablet computer,
mainframe computer, or any other device as may be obvious to a person skilled in the art for implementation of the features of the present disclosure.
[0044] Further, as used herein, a “processing unit” or “processor” or “operating
10 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 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
15 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, 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
20 processor.
[0045] As used herein, “a user equipment”, “a user device”, “a smart-user-device”, “a smart-device”, “an electronic device”, “a mobile device”, “a handheld device”, “a wireless communication device”, “a mobile communication device”, “a
25 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 phone, laptop, a general-purpose computer, desktop, personal digital assistant, tablet computer, wearable device or any other computing device which is capable
30 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
14

a transceiver unit, a processing unit, a storage unit, a detection unit and any other such unit(s) which are required to implement the features of the present disclosure.
[0046] As used herein, “storage unit” or “memory unit” refers to a machine or
5 computer-readable medium including any mechanism for storing information in a
form readable by a computer or similar machine. For example, a computer-readable
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.
[0047] As used herein “interface” or “user interface refers to a shared boundary
across which two or more separate components of a system exchange information
15 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.
20 [0048] 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 microprocessors in association with a DSP core, a controller, a microcontroller,
25 Application Specific Integrated Circuits (ASIC), Field Programmable Gate Array
circuits (FPGA), any other type of integrated circuits, etc.
[0049] As used herein the transceiver unit include at least one receiver and at least
one transmitter configured respectively for receiving and transmitting data, signals,
30 information, or a combination thereof between units/components within the system
and/or connected with the system.
15

[0050] As discussed in the background section, the current known solutions have
several shortcomings. The present disclosure aims to overcome the above-
mentioned and other existing problems in this field of technology by providing
5 method and system of dynamically creating a work order.
[0051] FIG. 1 illustrates an exemplary block diagram representation of a system
for managing cross-platform inclusivity of multiple vendors [112]/channel partners
together, in accordance with exemplary implementation of the present disclosure.
10 As shown in FIG. 1, the system [100] is also responsible for dynamically
implementing a next phase workflow without requiring creation of the previous phase workflow within a service work order. Thus, the system [100] is also responsible for implementing dynamic creation of the work order.
15 [0052] The system [100] comprises at least one processing unit [102] and at least
one storage unit [104]. Also, all the components/ units of the system [100] are assumed to be connected to each other unless otherwise indicated below. Also, in FIG. 1 only a few units are shown, however, the system [100] may comprise multiple such units or the system [100] may comprise any such numbers of said
20 units, as required to implement the features of the present disclosure. Further, in an
implementation, the system [100] may be present in a user device to implement the features of the present disclosure. The system [100] may be a part of the user device / or may be independent of but in communication with the user device (may also referred herein as UE). In another implementation, the system [100] may reside in
25 a server or a network entity. In yet another implementation, the system [100] may
reside partly in the server and partly in the user device.
[0053] The system [100] is configured for allowing creating of workflow without
requiring executing any other previously performed workflows, with the help of the
30 interconnection between the components/units of the system [100].
16

[0054] In more detail, the present disclosure manages various workflows within a
work order management system, between a plurality of customers [106], a plurality
of channel partners [108], a plurality of third-party service providers [110] and/or
vendor(s) [112]. In a preferred embodiment, the system [100] includes an enterprise
5 management component [114] configured in a central server [116]. As shown
herein, the enterprise management component [114] comprises a plurality of sub-components that manage end-to-end workflow information such as order submission [118], vendor management [120], appointment booking [122], work-order fulfilment [124], scheduling, inventory, etc. The system [100] is in such case
10 accessible by various users, members of the system [100], such as for example,
vendors [112], channel partners, resources, administrators, having predefined privileges allocated to each of the users. In a preferred embodiment, the customers [106], channel partners [108] are connected to the sever [116] by a communication medium [126].
15
[0055] In order to allow creation of workflows dynamically, the processing unit [102] of the system [100] is configured to create a later stage workflow without requiring to create a new workflow for the same. Preferably, each of the workflows of such a system has a common configurations and parameters. In embodiments of
20 the present disclosure in which multiple vendors [112] / service providers
participate, some of the benefits of the present disclosure include economies of scale are enabled, rationalization of procurement and inventory, rationalization of distribution and logistics facilities, and facilitation of the development of an industry-wide standard.
25
[0056] The storage unit [104] is configured to store a plurality of computer readable program instructions thereon for causing the processing unit [102] to carry out aspects of the present disclosure for each of the sub-components of the enterprise program that manage end-to-end workflow information such as order submission,
30 vendor management [120], appointment booking [122], work-order fulfilment
[124], scheduling, inventory, etc.
17

[0057] The system [100], wherein all the components are assumed to be connected to each other in a manner as obvious to the person skilled in the art for implementing features of the present disclosure. 5
[0058] Referring to FIG. 2, an exemplary architecture [200] of a system or
manging cross-platform inclusivity of multiple vendors [112]/ channel partners
[108] together is shown, in accordance with exemplary embodiments of the present
disclosure. In an exemplary embodiment, the architecture [200] may include sub-
10 components of the system [100] (as shown in FIG. 1) of the current disclosure. In
another embodiment, the architecture [100] may be used to implement the steps of
method [400] (as shown in FIG. 4) for dynamically creating a work order along
with the system [300] (as shown in FIG. 3) which is based on the architecture [200]
of the system. In a preferred embodiment, the architecture [200] of the system
15 comprises a plurality of components. For example, and by no way limiting the scope
of the present subject matter, the system architecture [200] (as shown in FIG. 2)
comprises an evolved packet core (EPC) [226], a fulfilment management system
(FMS) [228], a plurality of channels [230], a load balancer [232], a customer
relationship manager (CRM)/ customer engagement manager (CEM) server [234]
20 comprising a plurality of micro-services and a database [236]. The channels [230]
are configured to provide input data to the CRM server [234] through a load
balancer [232]. In an embodiment, some examples of the channels include but are
not limited to a POS [230A], a data management platform DMP [230B], a
SELFCARE [230C] and a CRM user interface (UI) [230D]. Further the CRM [234]
25 is associated with Data Information Framework (DIF) [244]. It is to be noted that
the workflow engine is mix of generic configurations and it also provides space for
custom logic so that all the milestones / order journeys can be autonomous and
segregated.
30 [0059] Referring to FIG. 3, an exemplary block diagram of the system [300] for
dynamically creating a work order, is shown, in accordance with the exemplary
18

implementations of the present disclosure. The system [300] is similar to system
[100]. The system [300] comprises at least one data base [301], at least one
transceiver unit [302], at least one identifier unit [304], at least one analysis unit
[306], at least one retrieving unit [308], and at least one generator unit [310]. Also,
5 all of the components/ units of the system [300] 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. 3 only a few units are shown, however, the system [300] may comprise multiple such units or the system [300] may comprise any such numbers of said
10 units, as required to implement the features of the present disclosure. Further, in an
implementation, the system [300] may be present in a user device/ equipment (may also referred herein as a UE) to implement the features of the present disclosure. The system [300] may be a part of the user device / or may be independent of but in communication with the user device. In another implementation, the system
15 [300] may reside in a server or a network entity. In yet another implementation, the
system [300] may reside partly in the server/ network entity and partly in the user device.
[0060] The system [300] is configured for dynamically creating a work order, with
20 the help of the interconnection between the components/units of the system [300].
It is to be noted that the work order may include but limited to the order of
installation given to the vendor [112] for business requirements. In one 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
25 personnel, required materials, deadlines, and instructions. Such tasks may be the
one or more work processes associated with the work order.
[0061] The transceiver unit [302] is configured to receive a task fulfillment request
associated with a work order. In an exemplary implementation, the task fulfillment
30 request may be received from the vendor. It is to be noted that the work order
comprises one or more work order parameters. It is to be noted that the one or more
19

work order parameters may comprise at least one of a Product identifier (ID), an Agent identifier (ID), a Bill of Quantity (BOQ) code, and a Stock Keeping Unit (SKU) code. It is further noted that these parameters are decided based on the type of work, assigned professional, deadline, priority level, etc. 5
[0062] The identifier unit [304] is configured to identify a target task based on the task fulfillment request. The target task includes but may not be limited to a fetch appointment slot, a book appointment slot, a create workflow order. The identifier unit [304] may analyze the task fulfillment request to identify the target task. The
10 identifier unit [304] is further configured to identify, from a database [301], a set of
vendor profiles based on the target task. It is to be noted that each of the vendor profile from the set of vendor profiles at least comprises one or more predefined vendor workflow configuration. The identifier unit [304] may analyze the database [301] based on the target task to identify the vendors [112]. It is further noted that
15 the one or more predefined vendor workflow configurations comprises at least one
of a fetch appointment slot configuration, a book appointment slot configuration, and a create workflow order configuration. The fetch appointment slot configuration refers to a workflow for retrieving available slots for appointments. The identifier unit [304] may communicate with a calendar, and the like tools to
20 identify the available slots. The book appointment slot configuration refers to a
workflow for making a booking in a slot from the available slots for appointments. The create workflow order configuration refers to defining an overall workflow for appointment scheduling. The identifier unit [304] is further configured to identify the work order complete status in an event an available vendor status associated
25 with a first vendor profile is detected by the identifier unit [304]. The identifier unit
[304] is further configured to identify the work order incomplete status in an event an unavailable vendor status associated with the first vendor profile is detected by the identifier unit [304].
30 [0063] The analysis unit [306] is configured to determine the first vendor profile
from the set of vendor profiles based on the one or more work order parameters.
20

The analysis unit [306] is further configured to determine a second vendor profile
from the set of vendor profiles based on the one or more work order parameters in
an event the work order incomplete status is detected. It is to be noted that the
analysis unit [306] may assess the one or more work order parameters in the work
5 order incomplete status to determine the second vendor profile. It is important to
note that the first vendor profile and the second vendor profile are indicative of the profile of companies/ organizations (let’s say A and B) whose profile may include characteristics like vendor identification number, appointment number, product identification number, etc. upon which the workflows are applicable. The only
10 difference in the profile of A and B is that the former adds appointment functionality
while the latter is complacent with the appointment booking flow. The analysis unit [306] is further configured to allocate the work order to the second vendor profile from the set of vendor profiles based on the work order incomplete status. The analysis unit [306] may evaluate the work order incomplete status and allocate the
15 work order to the second vendor profile.
[0064] The retrieving unit [308] is configured to fetch, from the database [301], a
target predefined vendor workflow configuration associated with the first vendor
profile. To fetch the target predefined vendor workflow configuration, is further
20 configured to access the first vendor profile in the database [301].
[0065] The generator unit [310] is configured to generate the work order
comprising the target task based on the target predefined vendor workflow
configurations. The steps of generation may include creating a sequence of steps in
25 the workflow. These steps represent the actions required for processing the work
order.
[0066] It is to be noted that the analysis unit [306] is further configured to allocate
the work order to the first vendor profile from the set of vendor profiles. It is further
30 noted that the identifier unit [304] is further configured to identify a work order
status associated with the work order based on allocating the work order to the first
21

vendor profile. The identification of the work order status is based on the allocation
of the work order to the first vendor profile. It is also noted that the work order
status is at least one of a work order complete status and a work order incomplete
status. It is to be noted that the identifier unit [304] may monitor the work order.
5 When the identifier unit [304] identifies the available vendor status, the identifier
unit [304] may identify it as the work order complete status. When the identifier unit [304] identifies the unavailable vendor status, the identifier unit [304] may identify it as the work order incomplete status. It is to be noted that the generator unit [310] is further configured to dynamically create a target work order associated
10 with the first vendor profile based on the work order complete status. Dynamic
creation may refer to a constant update in the first work order. It is emphasized that to dynamically create the target work order associated with the first vendor profile based on the work order complete status, the generator unit [310] is further configured to automatically assign, at least one professional associated with the first
15 vendor profile. The at least one professional is selected by the generator unit [310]
based on a credibility score and an accountability score of the at least one professional. It is to be noted that the credibility score of the at least one professional is given by evaluating the trustworthiness and reliability of the at least one professional based on its expertise and past performance. Similarly, the
20 accountability score of the at least one professional is given by evaluating the at
least one professional’s responsibility in handling tasks, meeting the assigned deadlines, and addressing the issues in a transparent manner. Moreover, the generator unit [310] is further configured to determine a positive task completion status for the target task associated with the first vendor profile and assigned to the
25 at least one professional. Additionally, the generator unit [310] is further configured
to verify the positive task completion status for the target task, wherein the positive task completion status is verified based on completion of a set of predefined task steps. The generator unit [310] may review and confirm the positive task completion to ensure it aligns with the target task. It is to be noted that the set of
30 predefined task steps comprises at least one of a device procurement from
warehouse, a service testing, and a service verification.
22

[0067] Referring to FIG. 4, an exemplary method flow diagram [400] for
dynamically creating a work order, in accordance with exemplary implementations
of the present disclosure is shown. In an implementation the method [400] is
5 performed by the system [300]. Further, in an implementation, the system [300]
may be present in a server device to implement the features of the present disclosure. Also, as shown in FIG. 4, the method [400] starts at step [402].
[0068] At step [404], the method [400] comprises receiving, by a transceiver unit
10 [302], a task fulfillment request associated with a work order. It is to be noted that
the work order comprises one or more work order parameters. It is to be noted that
the one or more work order parameters may comprise at least one of a Product
identifier (ID), an Agent identifier (ID), a Bill of Quantity (BOQ) code, and a Stock
Keeping Unit (SKU) code. It is further noted that these parameters are decided
15 based on the type of work, assigned professional, deadline, priority level, etc.
[0069] At step [406], the method [400] comprises identifying, by the identifier unit [304], a target task based on the task fulfillment request.
20 [0070] At step [408], the method [400] comprises identifying, by the identifier unit
[304] from a database [301], a set of vendor profiles based on the target task. It is to be noted that each vendor profile from the set of vendor profiles at least comprises one or more predefined vendor workflow configurations. In an exemplary aspect of the present disclosure, in the disclosed method, the one or more
25 predefined vendor workflow configurations comprises at least one of a fetch
appointment slot configuration, a book appointment slot configuration, and a create workflow order configuration.
[0071] At step [410], the method [400] comprises determining, by the analysis unit
30 [306], a first vendor profile from the set of vendor profiles based on the one or more
work order parameters.
23

[0072] At step [412], the method [400] comprises fetching, by the retrieving unit [308] from the database [301], a target predefined vendor workflow configuration associated with the first vendor profile. 5
[0073] At step [414], the method [400] comprises generating, by the generator unit [310], the work order comprising the target task based on the target predefined vendor workflow configuration.
10 [0074] At step [416], the method [400] comprises allocating, by the analysis unit
[306], the work order to the first vendor profile from the set of vendor profiles.
[0075] At step [418], the method [400] comprises identifying, by the identifier unit [304], a work order status associated with the work order based on allocating the
15 work order to the first vendor profile. It is to be noted that the work order status is
at least one of a work order complete status and a work order incomplete status. In an exemplary aspect of the present disclosure, the work order complete status is identified by the identifier unit [304] in an event an available vendor status associated with the first vendor profile is detected by the identifier unit [304] and
20 the work order incomplete status is identified by the identifier unit [304] in an event
an unavailable vendor status associated with the first vendor profile is detected by the identifier unit [304].
[0076] At step [420], the method [400] comprises dynamically creating, by the
25 generator unit [310], the target work order associated with the first vendor profile
based on the work order complete status. In an exemplary aspect of the present
disclosure, the dynamically creating by the generator unit [310], the target work
order associated with the first vendor profile based on the work order complete
status, further comprises automatically assigning, by the generator unit [310], at
30 least one professional associated with the first vendor profile. It is to be noted that
the at least one professional is selected by the generator unit based on a credibility
24

score and an accountability score of the at least one professional. It is to be noted
that the credibility score of the at least one professional is given by evaluating the
trustworthiness and reliability of the at least one professional based on its expertise
and past performance. Similarly, the accountability score of the at least one
5 professional is given by evaluating the at least one professional’s responsibility in
handling tasks, meeting the assigned deadlines, and addressing the issues in a transparent manner. The dynamically creating by the generator unit [310] of the method [400] further comprises determining, by the generator unit [310], a positive task completion status for the target task associated with the first vendor profile and
10 assigned to the at least one professional. The dynamically creating by the generator
unit [310] of the method [400] further comprises verifying, by the generator unit [310], the positive task completion status for the target task associated with the first vendor profile and assigned to the at least one professional. It is to be noted that the positive task completion status is verified based on completion of a set of predefined
15 task steps by the at least one professional. The positive task completion status is
verified based on completion of a set of predefined task steps. In an exemplary aspect of the present disclosure, the set of predefined task steps comprises at least one of a device procurement from warehouse, a service testing, and a service verification. The device procurement from warehouse refers to using a device to
20 facilitate and streamline the positive task completion. The service testing refers to
checking the quality of the positive task completion. The service verification refers to verifying whether the semantic, function and the like are in accordance with the requirements of the user.
25 [0077] In an exemplary aspect of the present disclosure, the method further
comprises determining, by the analysis unit [306], a second vendor profile from the set of vendor profiles, based on the one or more work order parameters in an event the work order incomplete status is detected. It is important to note that the first vendor profile and the second vendor profile are indicative of the profile of
30 companies/ organizations (let’s say A and B) whose profile may include
characteristics like vendor identification number, appointment number, product
25

identification number, etc. upon which the workflows are applicable. The only
difference in the profile of A and B is that the former adds appointment functionality
while the latter is complacent with the appointment booking flow. The method
further comprises allocating, by the analysis unit [306], the work order to the second
5 vendor profile from the set of vendor profiles based on the work order incomplete
status.
[0078] Thereafter, the method [400] terminates at step [422].
10 [0079] FIG. 5 illustrates an exemplary flow chart of the process [500] for
dynamically creating a work order in accordance with exemplary implementations of the present disclosure. In an implementation the process [500] is carried by the system [300] (as shown in FIG. 3) and the system [100] (as shown in FIG. 1) that are implementing the steps of method [400] (as shown in FIG. 4) for the
15 implementation of the present disclosure. The process [500] comprises receiving a
request for a fulfilment task to be performed. In an embodiment, the fulfilment task is a target task. In an embodiment, the fulfilment task may be provided by a customer who may be an individual, a corporate or a group. In some other embodiments, the task may be provided by a channel partner of the work order who
20 is already performing an activity within the work order adapted to be completed in
sometime.
[0080] Thereafter, appointment fetching workflow is created for the customer to perform the desired task at a desired time interval. Then, an appointment slot is
25 booked for a selected third-party service provider [110] or the vendor [112] having
a predetermined configuration depending upon the parameters and configuration of the workflow/product/process to be performed/installed by the third-party vendor. It is to be noted that a work order is created/generated for the fulfilment of the workflow by the selected vendor. In some embodiments, where the selected vendor
30 is either incapable of or, unable to complete the work order, the process involves
finding an alternate vendor who is complicit with the workflows completed earlier.
26

Thus, the process [500] helps in avoiding the need of creating and completing
workflows that ideally needs to be completed before the work order generation
workflow. The said feature allows saving time, as well as provide flexibility to the
vendors [112], channel partners [108] and avoids need of last-minute delays by the
5 system(s) [100], [200] and [300]. In some other embodiments, where the
appointment booking workflow is not creatable due to absence of mandatory information by the channel partner, the process involves receiving the information available by the channel partner. Thus, the workflow related to completion of work order is processed.
10
[0081] Such a process [500] has been depicted in the flowchart of Fig. 5 where the process [500] starts at box B1. Word order creation/generation is followed by assignment of a professional at box B2. At box B3, the process [500] involves procuring device from a warehouse. Thereafter, box B4 signifies reaching of the
15 professional at the customer’s premises. Box B5 involves allocation of a serial
number to the professional on completion of task followed by service testing and verification of task completion at box B6. The customer eventually signs off as the work completes at box B7, at step [316].
20 [0082] The present disclosure can be implemented on a computing device [600] as
shown in FIG. 6. The computing device [600] implements the present disclosure in
accordance with the CRM/CEM system architecture (as shown in FIG. 2). In an
embodiment of the present disclosure, the computing device [600] may reside in
the system [100] (as shown in FIG. 1) and system [300] (as shown in FIG. 3).
25
[0083] FIG. 6 illustrates an exemplary block diagram of the computing device
[600] upon which the features of the present disclosure may be implemented in
accordance with exemplary implementation of the present disclosure. In an
implementation, the computing device [600] may also implement a method [400]
30 (as shown in FIG. 4). for dynamically creating a work order utilising the system.
In another implementation, the computing device [600] itself implements the
27

method [400] for dynamically creating a work order using one or more units configured within the computing device [600], wherein said one or more units are capable of implementing the features as disclosed in the present disclosure.
5 [0084] The computing device [600] may include a bus [602] or other
communication mechanism for communicating information, and a hardware
processor [604] coupled with bus [602] for processing information. The hardware
processor [604] may be, for example, a general-purpose microprocessor. The
computing device [600] may also include a main memory [606], such as a random-
10 access memory (RAM), or other dynamic storage device, coupled to the bus [602]
for storing information and instructions to be executed by the processor [604]. The
main memory [606] also may be used for storing temporary variables or other
intermediate information during execution of the instructions to be executed by the
processor [604]. Such instructions, when stored in non-transitory storage media
15 accessible to the processor [604], render the computing device [600] into a special-
purpose machine that is customized to perform the operations specified in the
instructions. The computing device [600] further includes a read only memory
(ROM) [608] or other static storage device coupled to the bus [602] for storing static
information and instructions for the processor [604].
20
[0085] A storage device [610], such as a magnetic disk, optical disk, or solid-state
drive is provided and coupled to the bus [602] for storing information and
instructions. The computing device [600] may be coupled via the bus [602] to a
display [612], such as a cathode ray tube (CRT), Liquid crystal Display (LCD),
25 Light Emitting Diode (LED) display, Organic LED (OLED) display, etc. for
displaying information to a computer user. An input device [614], including
alphanumeric and other keys, touch screen input means, etc. may be coupled to the
bus [602] for communicating information and command selections to the processor
[604]. Another type of user input device may be a cursor controller [616], such as
30 a mouse, a trackball, or cursor controller direction keys, for communicating
direction information and command selections to the processor [604], and for
28

controlling cursor controller’s [616] movement on the display [612]. 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 the device to specify positions in a plane.
5 [0086] The computing device [600] 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 [600] causes or programs the computing device [600] to be a special-purpose machine. According to one implementation, the techniques herein are performed by the
10 computing device [600] in response to the processor [604] executing one or more
sequences of one or more instructions contained in the main memory [606]. Such instructions may be read into the main memory [606] from another storage medium, such as the storage device [610]. Execution of the sequences of instructions contained in the main memory [606] causes the processor [604] to perform the
15 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.
[0087] The computing device [600] also may include a communication interface
20 [618] coupled to the bus [602]. The communication interface [618] provides a two-
way data communication coupling to a network link [620] that is connected to a
local network [622]. For example, the communication interface [618] may be an
integrated services digital network (ISDN) card, cable modem, satellite modem, or
a modem to provide a data communication connection to a corresponding type of
25 telephone line. As another example, the communication interface [618] 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 [618] sends and receives electrical,
electromagnetic, or optical signals that carry digital data streams representing
30 various types of information.
29

[0088] The computing device [600] can send messages and receive data, including
program code, through the network(s), the network link [620] and the
communication interface [618]. In the Internet example, a server [630] might
transmit a requested code for an application program through the Internet [628], the
5 ISP [626], the host [624], the local network [622] and the communication interface
[618]. The received code may be executed by the processor [604] as it is received, and/or stored in the storage device [610], or other non-volatile storage for later execution.
10 [0089] The present disclosure further discloses a non-transitory computer readable
storage medium storing instructions for dynamically creating a work order, the instructions include executable code which, when executed by a one or more units of a system, causes: a transceiver unit [302] of the system [300] to receive a task fulfilment request associated with a work order, the work order comprises one or
15 more work order parameters. Further, the instructions include executable code,
which when executed causes an identifier unit [304] of the system [300] to: identify a target task based on the task fulfilment request; and identify, from a database [301], a set of vendor profiles based on the target task, wherein each of the vendor profile from the set of vendor profiles at least comprises one or more predefined
20 vendor workflow configuration. Further, the instructions include executable code,
which when executed causes an analysis unit [306] of the system [300] to determine a first vendor profile from the set of vendor profiles based on the one or more work order parameters. Further, the instructions include executable code, which when executed causes a retrieving unit [308] of the system [300] to fetch, from the
25 database [301], a target predefined vendor workflow configuration associated with
the first vendor profile. Further, the instructions include executable code, which when executed causes a generator unit [310] of the system [300] to generate, the work order comprising the target task based on the target predefined vendor workflow configurations. Further, the instructions include executable code, which
30 when executed causes the analysis unit [306] to further allocate, the work order to
the first vendor profile from the set of vendor profiles. Further, the instructions
30

include executable code, which when executed causes the identifier unit [304] to
further identify, a work order status associated with the work order based on
allocating the work order to the first vendor profile, wherein the work order status
is at least one of a work order complete status and a work order incomplete status.
5 Further, the instructions include executable code, which when executed causes the
generator unit [310] to further dynamically create, a target work order associated with the first vendor profile based on the work order complete status.
[0090] The present disclosure also discloses a User Equipment (UE) comprising a
10 transceiver unit configured to send to a system [300], a task fulfilment request
associated with a work order. It is to be noted that the work order comprises one or more work order parameters. The transceiver unit is further configured to receive, from the system [300], a work order status associated with the work order. It is further noted that the work order status is at least one of a work order complete
15 status and a work order incomplete status. It is emphasized that the work order
status is identified based on an allocation of the work order, by the system [300], to a first vendor profile from a set of vendor profiles. And the transceiver unit is further configured to send to the system [300], a sign-off to close the work order in an event the work order status is the work order complete status.
20
[0091] Further, in accordance with the present disclosure, it is to be acknowledged that the functionality described for the various the components/units can be implemented interchangeably. While specific embodiments may disclose a particular functionality of these units for clarity, it is recognized that various
25 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 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
30 of the present disclosure.
31

[0092] As is evident from the above, the present disclosure provides a technically
advanced solution for dynamically creating a work order. The present disclosure
also provides a technically advanced solution for allowing plurality of vendors to
work on a common platform where the last-minute work-orders may be allocated
5 to vendors, if they are complicit with the previous stage workflows.
[0093] Moreover, the system(s) namely [100], [200], [300] and [500] may work in
tandem or independent of each other to carry out the object of the present disclosure.
The system(s) of the present disclosure are adapted to allow channel partners to
10 delay any workflow to as much as possible till the creation of work-order and
fulfilment of the task.
[0094] Thus, the system(s) are adapted to create, maintain, and execute a plurality of workflows selected from but not limited to fetching appointment slot from a
15 Service Management Platform (SMP) [242] (In-house work order CRM), book
appointment slot in the SMP [242] and create work order in the SMP [242]. The SMP [242] is a microservice based architecture which improves scalability and resiliency of the SMP [242]. The services of SMP [242] work in tandem to provide workflow management, customer assurance, resource assurance and service
20 assurance functions. The SMP [242] integrates with operations support systems
(OSS)/ business support systems (BSS) platforms like the customer relationship management (CRM), etc. Further, each of the workflows are executed based on one or more predetermined configuration parameters selected from but not limited to an Agent ID, a BOQ Code, an SKU Code, a Product ID, and the like. For e.g., a client
25 procures a POS vendor from a first company “A” having a vendor id VEND10001.
The vendor VEND10001 is currently undergoing development for adding book appointment functionality. Input parameters for the configuration may comprise: Product ID under consideration: P10024 BOQ Code for ODU: DEV00016 and SIM: DEV00015
30
[0095] Thus, based on above parameters, below workflows are applicable:
32

- Fetch Appointment Slot;
- Book Appointment Slot;
- Create Installation Work order.
[0096] On the other hand, another vendor, say VEND10002 from company B is complacent with appointment booking flow. Hence, in case, if vendor B is to be utilized for performing the task, and if the product parameters are same and vendor is complicit with all the existing parameters, configurations and workflows, the system(s) need to create only the below workflow:
- Create Installation Work Order.
[0097] 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 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.

We Claim:
1. A method [400] for dynamically creating a work order, the method [400]
comprising:
- receiving, by a transceiver unit [302], a task fulfillment request associated with a work order, wherein the work order comprises one or more work order parameters;
- identifying, by an identifier unit [304], a target task based on the task fulfillment request;
- identifying, by the identifier unit [304] from a database [301], a set of vendor profiles based on the target task, wherein each of the vendor profile from the set of vendor profiles at least comprises one or more predefined vendor workflow configurations;
- determining, by an analysis unit [306], a first vendor profile from the set of vendor profiles based on the one or more work order parameters;
- fetching, by a retrieving unit [308] from the database [301], a target predefined vendor workflow configuration associated with the first vendor profile;
- generating, by a generator unit [310], the work order comprising the target task based on the target predefined vendor workflow configuration;
- allocating, by the analysis unit [306], the work order to the first vendor profile from the set of vendor profiles;
- identifying, by the identifier unit [304], a work order status associated with the work order based on allocating the work order to the first vendor profile, wherein the work order status is at least one of a work order complete status and a work order incomplete status; and
- dynamically creating, by the generator unit [310], a target work order associated with the first vendor profile based on the work order complete status.
2. The method [400] as claimed in claim 1, wherein the one or more predefined
vendor workflow configurations comprises at least one of a fetch appointment

slot configuration, a book appointment slot configuration, and a create work flow order configuration.
3. The method [400] as claimed in claim 1, wherein the work order complete status is identified by the identifier unit [304] in an event an available vendor status associated with the first vendor profile is detected by the identifier unit [304]; and wherein the work order incomplete status is identified by the identifier unit [304] in an event an unavailable vendor status associated with the first vendor profile is detected by the identifier unit [304].
4. The method [400] as claimed in claim 1, wherein the method [400] further comprises:

- determining, by the analysis unit [306], a second vendor profile from the set of vendor profiles, based on the one or more work order parameters in an event the work order incomplete status is detected; and
- allocating, by the analysis unit [306], the work order to the second vendor profile from the set of vendor profiles based on the work order incomplete status.

5. The method [400] as claimed in claim 1, wherein the one or more work order parameters comprises at least one of a Product identifier (ID), an Agent identifier (ID), a Bill of Quantity (BOQ) code, and a Stock Keeping Unit (SKU) code.
6. The method [400] as claimed in claim 1, wherein dynamically creating by the generator unit [310], a target work order associated with the first vendor profile based on the work order complete status, further comprises:
- automatically assigning, by the generator unit [310], at least one
professional associated with the first vendor profile, wherein the at least one
professional is selected by the generator unit based on a credibility score
and an accountability score of the at least one professional;

- determining, by the generator unit [310], a positive task completion status for the target task associated with the first vendor profile and assigned to the at least one professional; and
- verifying, by the generator unit [310], the positive task completion status for the target task, wherein the positive task completion status is verified based on completion of a set of predefined task steps by the at least one professional.

7. The method [400] as claimed in claim 6, wherein the set of predefined task steps comprises at least one of a device procurement from warehouse, a service testing, and a service verification.
8. A system [300] for dynamically creating a work order, the system [300] comprises:

- a transceiver unit [302], the transceiver unit [302] is configured to receive a task fulfillment request associated with a work order, the work order comprises one or more work order parameters;
- an identifier unit [304] connected to at least the transceiver unit [302], the identifier unit [304] is configured to:

• identify, a target task based on the task fulfillment request, and
• identify, from a database [301], a set of vendor profiles based on the target task, wherein each of the vendor profile from the set of vendor profiles at least comprises one or more predefined vendor workflow configurations;

- an analysis unit [306] connected to at least the identifier unit [304], the analysis unit [306] is configured to determine, a first vendor profile from the set of vendor profiles based on the one or more work order parameters;
- a retrieving unit [308] connected to at least the analysis unit [306], the retrieving unit [308] is configured to fetch, from the database [301], a target predefined vendor workflow configuration associated with the first vendor profile; and

- a generator unit [310] connected to at least the retrieving unit [308], the generator unit [310] is configured to generate, the work order comprising the target task based on the target predefined vendor workflow configurations,
wherein the analysis unit [306] is further configured to allocate, the work order to the first vendor profile from the set of vendor profiles,
wherein the identifier unit [304] is further configured to identify, a work order status associated with the work order based on allocating the work order to the first vendor profile, wherein the work order status is at least one of a work order complete status and a work order incomplete status, and
wherein the generator unit [310] is further configured to dynamically create, a target work order associated with the first vendor profile based on the work order complete status.
9. The system [300] as claimed in claim 8, wherein the one or more predefined vendor workflow configurations comprises at least one of a fetch appointment slot configuration, a book appointment slot configuration, and a create work flow order configuration.
10. The system [300] as claimed in claim 8, wherein the identifier unit [304] is further configure to identify the work order complete status in an event an available vendor status associated with the first vendor profile is detected by the identifier unit [304], and wherein the identifier unit [304] is further configured to identify the work order incomplete status in an event an unavailable vendor status associated with the first vendor profile is detected by the identifier unit [304].
11. The system [300] as claimed in claim 8, wherein the analysis unit [306[ is further configured to:

- determine a second vendor profile from the set of vendor profiles based on the one or more work order parameters in an event the work order incomplete status is detected; and
- allocate the work order to the second vendor profile from the set of vendor profiles based on the work order incomplete status.

12. The system [300] as claimed in claim 8, wherein the one or more work order parameters comprises at least one of a Product identifier (ID), an Agent identifier (ID), a Bill of Quantity (BOQ) code, and a Stock Keeping Unit (SKU) code.
13. The system [300] as claimed in claim 8, wherein to dynamically create the target work order associated with the first vendor profile based on the work order complete status, the generator unit [310] is further configured to:

- automatically assign, at least one professional associated with the first vendor profile, wherein the at least one professional is selected by the generator unit [310] based on a credibility score and an accountability score of the at least one professional;
- determine, a positive task completion status for the target task associated with the first vendor profile and assigned to the at least one professional; and
- verify, the positive task completion status for the target task, wherein the positive task completion status is verified based on completion of a set of predefined task steps.

14. The system [300] as claimed in claim 13, wherein the set of predefined task steps comprises at least one of a device procurement from warehouse, a service testing, and a service verification.
15. A User Equipment (UE) comprising:
a transceiver unit [302], configured to:

send, to a system [300], a task fulfilment request associated with a work order, wherein the work order comprises one or more work order parameters; and
receive, from the system [300], a work order status associated with the work order, wherein,
the work order status is at least one of a work order complete status
and a work order incomplete status,
the work order status is identified based on an allocation of the work
order, by the system [300], to a first vendor profile from a set of vendor
profiles;
send, to the system [300], a sign-off to close the work order in an event the work order status is the work order complete status.