DESC:CROSS REFERENCE TO RELATED APPLICATION
This application is based on and derives the benefit of Indian Provisional Application 202311068057 filed on 10th October, 2023, the contents of which are incorporated herein by reference.
TECHNICAL FIELD
[001] Embodiments disclosed herein relate to complaint management systems for Original Equipment Manufacturers (OEMs), and more particularly to methods and systems for registering and managing Original equipment manufacturer (OEM) complaint(s) from users of agricultural vehicles.
BACKGROUND
[002] Generally, managing various OEM complaints in offline mode may be ineffective in providing sufficient customer support due to several limitations, such as branch-specific coverage, servicing distant areas, software updates, the need for onsite installation, and limited data access for the head office or headquarters team. Additionally, there is no efficient system for capturing real-time OEM failures, which can cause delays in the processing of OEM complaints by service engineers. Moreover, this can complicate the maintenance of complaint records, making it difficult to take timely action to resolve failure issues.
[003] Hence, there is a need in the art for solutions which will overcome the above mentioned drawback(s), among others.
OBJECTS
[004] The principal object of embodiments herein is to disclose systems and methods for registering and managing Original equipment manufacturer (OEM) complaint(s) from users of agricultural vehicles.
[005] Another object of embodiments herein is to disclose systems and methods for registering one or more complaints related to the OEM through a Customer Data Management System (CDMS) architecture.
[006] Another object of embodiments herein is to disclose systems and methods for enabling one or more authorized client devices to interact with the CDMS architecture for registering the one or more complaints related to OEM.
[007] Yet another object of embodiments herein is to disclose systems and methods for generating one or more complaint reports related to the OEM at a CDMS- customer care management (CDMS-CCM) portal and a Head Office (HO) portal.
[008] Another object of embodiments herein is to disclose systems and methods for auto-generating one or more messages (such as, but not limited to, emails, SMS, instant messages, and so on) in relation to the one or more registered OEM complaints and communicating thereof to the one or more authorized client devices, one or more devices associated with the CCM, and one or more devices associated with the HO.
[009] These and other aspects of the embodiments herein will be better appreciated and understood when considered in conjunction with the following description and the accompanying drawings. It should be understood, however, that the following descriptions, while indicating at least one embodiment and numerous specific details thereof, are given by way of illustration and not of limitation. Many changes and modifications may be made within the scope of the embodiments herein without departing from the spirit thereof, and the embodiments herein include all such modifications.
BRIEF DESCRIPTION OF FIGURES
[0010] Embodiments herein are illustrated in the accompanying drawings, throughout which like reference letters indicate corresponding parts in the various figures. The embodiments herein will be better understood from the following description with reference to the following illustratory drawings. Embodiments herein are illustrated by way of examples in the accompanying drawings, and in which:
[0011] FIG. 1 depicts a block-diagram of a system utilizing a client data management system (CDMS) architecture for registering and managing big data related to one or more Original equipment manufacturer (OEM) complaints, according to embodiments as disclosed herein;
[0012] FIG. 2 is a flowchart depicting a method for OEM complaint generation and registration through the system, according to embodiments as disclosed herein;
[0013] FIG. 3 depicts a method for registering OEM complaints through the system, by a client device, according to embodiments as disclosed herein;
[0014] FIG. 4 depicts an auto-generated complaint registration form and an auto-generated email transmitted to an authorized client device, a CDSM-CCM client device, and a head office (HO) client device, according to embodiments as disclosed herein; and
[0015] FIG. 5 depicts an OEM complaint report generated by the system (1000) for accession by the CDSM-CCM client device, and the HO client device, according to embodiments as disclosed herein.
DETAILED DESCRIPTION
[0016] The embodiments herein and the various features and advantageous details thereof are explained more fully with reference to the non-limiting embodiments that are illustrated in the accompanying drawings and detailed in the following description. Descriptions of well-known components and processing techniques are omitted so as to not unnecessarily obscure the embodiments herein. The examples used herein are intended merely to facilitate an understanding of ways in which the embodiments herein may be practiced and to further enable those of skill in the art to practice the embodiments herein. Accordingly, the examples should not be construed as limiting the scope of the embodiments herein.
[0017] The words/phrases "exemplary", “example”, “illustration”, “in an instance”, “and the like”, “and so on”, “etc.”, “etcetera”, “e.g.,”, “i.e.,” are merely used herein to mean "serving as an example, instance, or illustration. Any embodiment or implementation of the present subject matter described herein using the words/phrases "exemplary", “example”, “illustration”, “in an instance”, “and the like”, “and so on”, “etc.”, “etcetera”, “e.g.,” , “i.e.,” is not necessarily to be construed as preferred or advantageous over other embodiments.
[0018] Embodiments herein may be described and illustrated in terms of blocks which carry out a described function or functions. These blocks, which may be referred to herein as managers, units, modules, hardware components or the like, are physically implemented by analog and/or digital circuits such as logic gates, integrated circuits, microprocessors, microcontrollers, memory circuits, passive electronic components, active electronic components, optical components, hardwired circuits and the like, and may optionally be driven by a firmware. The circuits may, for example, be embodied in one or more semiconductor chips, or on substrate supports such as printed circuit boards and the like. The circuits constituting a block may be implemented by dedicated hardware, or by a processor (e.g., one or more programmed microprocessors and associated circuitry), or by a combination of dedicated hardware to perform some functions of the block and a processor to perform other functions of the block. Each block of the embodiments may be physically separated into two or more interacting and discrete blocks without departing from the scope of the disclosure. Likewise, the blocks of the embodiments may be physically combined into more complex blocks without departing from the scope of the disclosure.
[0019] It should be noted that elements in the drawings are illustrated for the purposes of this description and ease of understanding and may not have necessarily been drawn to scale. For example, the flowcharts/sequence diagrams illustrate the method in terms of the steps required for understanding of aspects of the embodiments as disclosed herein. Furthermore, in terms of the construction of the device, one or more components of the device may have been represented in the drawings by conventional symbols, and the drawings may show only those specific details that are pertinent to understanding the present embodiments so as not to obscure the drawings with details that will be readily apparent to those of ordinary skill in the art having the benefit of the description herein. Furthermore, in terms of the system, one or more components/modules which comprise the system may have been represented in the drawings by conventional symbols, and the drawings may show only those specific details that are pertinent to understanding the present embodiments so as not to obscure the drawings with details that will be readily apparent to those of ordinary skill in the art having the benefit of the description herein.
[0020] The accompanying drawings are used to help easily understand various technical features and it should be understood that the embodiments presented herein are not limited by the accompanying drawings. As such, the present disclosure should be construed to extend to any modifications, equivalents, and substitutes in addition to those which are particularly set out in the accompanying drawings and the corresponding description. Usage of words such as first, second, third etc., to describe components/elements/steps is for the purposes of this description and should not be construed as sequential ordering/placement/occurrence unless specified otherwise.
[0021] Embodiments herein achieve systems and methods for registering one or more OEM data related to customer complaints to a CDMS-CCM (Customer Data Management System-Customer Care Management) portal and a HO (Head office) portal and managing effectively the one or more OEM data in order to determine one or more OEM failures in real time by the CCM and the HO. Referring now to the drawings, and more particularly to FIGs. 1 through 5, where similar reference characters denote corresponding features consistently throughout the figures, there are shown embodiments.
[0022] FIG. 1 depicts a block diagram of a system 1000 for registering and managing big OEM data related to one or more customer complaints. Original Equipment Manufacturer (OEM) refers to a company that produces parts, components, or products that are used in another company's end product. OEMs are integral to various industries, such as automotive, electronics, and machinery, as they supply high-quality components that are often branded and resold by another company under its name. OEM data refers to the vast amount of information generated throughout the lifecycle of an OEM product. This includes technical specifications, manufacturing details, performance metrics, and customer usage data. OEM data is critical for optimizing production, ensuring product quality, enhancing maintenance and repair services, and improving customer experience. It is also instrumental in managing warranty claims, handling customer complaints, and providing real-time insights into potential product issues. Access to this data allows manufacturers to make informed decisions, improve product designs, and enhance operational efficiency.
[0023] The system 1000 comprises one or more devices 102A and 102B (which further comprises one or more application interfaces), an application server 104, a database 106 in communication with the application server 104, and a communication network 108. The communication network comprises a security gateway. In an example embodiment, the security gateway includes a firewall. The firewall is an essential component of any security framework, eliminating the uncertainty of host-level protection by delegating it to a network security device. Firewalls, particularly Next Generation Firewalls, are designed to block malware and application-layer threats. With built-in intrusion prevention systems (IPS), these advanced firewalls can swiftly and efficiently identify and respond to external threats across the entire network. They enable the implementation of policies to enhance network protection and conduct rapid assessments to detect and neutralize invasive or suspicious activities, such as malware. The Application interfaces of the client devices and the application server 104 interacts with each other via the communication network 108. The communication network 108 can be at least one of the Internet, a wired network (a Local Area Network (LAN), a Controller Area Network (CAN) network, a Universal Asynchronous Receiver/Transmitter (UART), a bus network, Ethernet and so on), a wireless network (a Wi-Fi network, a cellular network, a Wi-Fi Hotspot, Bluetooth, Zigbee, and so on. The Application server 104 and the database 106 may be at least one of a standalone server, a server in a cloud-based environment or a remote server.
[0024] According to the embodiments herein, the one or more client devices comprise one or more complaint registration client devices 102A associated with the OEM complainants and the devices associated with the CDMS-CCM and the Head office (HO) of the OEM hereinafter referred as one or more CDMS-CCM devices, or one or more client devices 102B. The terms “the one or more complaint registration client devices” and the term “client OEM complaint generation devices” have been used interchangeably and have been assigned the reference numeral 102A. The one or more devices connected to CDMS-CCM and HO portals which are also referred as the one or more OEM complaint receiver devices have been referred in the Drawings as 102B. The one or more client devices can be devices with communication facility and/or a device with communication facility, designed to support an OEM complaint application within the Application interface. Examples of the client devices may be, but not limited to, a mobile phone, a smart phone, a computer, a portable computer, a computing device, a wearable device, a tablet, and so on. The one or more complaint registration client devices communicate with the Application server 104 over the communication network 108. OEM data related to customer complaints can be registered through the application interface of the one or more complaint registration client devices 102, wherein the application interface is linked to a CDMS-CCM or/and a HO portal. The OEM data can be further communicated to a controller 110 of the remote Application server. Further, the OEM data can be encrypted by an encryption mechanism 109 before being transmitted to the controller 110, wherein the encryption mechanism can be such as, but not limited to, an SSL, a TSL encryption mechanism, and so on. The controller 110 may be a general purpose controller, such as a central processing unit (CPU), an application processor (AP), or the like, a graphics-only processing unit (such as a graphics processing unit (GPU), a visual processing unit (VPU)), and/or an AI-dedicated processor such as a neural processing unit (NPU).
[0025] The Application server 104 comprises the controller 110, an authorization controller 112, a presentation controller 114, a validation controller 116, a secured business controller 118, and a DAO controller 120. The controller 110 comprising a Model-view-controller (MVC) application, controls the interaction between the one or more complaint registration client devices, one or more CDMS-CCM devices, and one or more HO devices. The controller 110 comprises a flow control logic for the MVC application in order to determine one or more responses for transmitting to the one or more complaint registration client devices that are sending requests to the application server 104. The flow control logic is used for controlling the OEM complaint data through the authorization controller 112 to check the authority of the client to access the data. The flow control logic is used to restrict the complaint registration clients from accessing only the data related to the clients’ complaint(s) and not to complaint(s) from other clients, thereby keeping the records/complaints/data confidential. Further, the CDMS-CCM portal and/or HO portal can access all the records to get help in further decision making.
[0026] In an example herein, the request sent by a complaint registration client device to the Application server 104 can be a request for accessing the CDMS-CCM portal and/or HO portal by a browser on the complaint registration client device 102.
[0027] The authorization controller 112 authenticates the one or more complaint registration client devices 102, before authorizing the one or more complaint registration client devices to link to the CDMS-CCM portal and/or to the HO portal. Further, the authorization controller 112 authenticates the one or more CDMS-CCM client devices, and the one or more HO client devices requesting for access to the one or more OEM data of customer complaints, before providing access to the one or more OEM data of customer complaints. In an example embodiment, the authentication process includes verification with passwords, usernames, biometrics, one-time passwords, and so on. In an embodiment herein, the authentication includes providing access to only one session or transaction. A user account can use a security context that the OEM complaint registration system 1000 uses to enforce security when a thread attempts to access a securable object. This security context can include the user security identifier (SID), group memberships, user privileges, and so on. A user can establish a security context by presenting credentials for authentication. The one or more complaint registration client devices 102A are configured to receive registration of the one or more OEM complaints by authenticating the one or more complaint registration client devices 102A and providing a complaint registration page of one of scanning and entering an input, the input comprising the one or more OEM complaints and one or more media related to failed machinery parts in the agricultural vehicles.
[0028] The presentation controller 114 provides the one or more OEM data related to customer complaints from the application interface of the one or more client OEM complaint generation devices to the one or more client OEM complaint receiver devices, such as the CDMS-CCM client devices and the HO client devices. Further, the presentation controller 114 is configured to convert one format of data to another format of data using data operations such as, but not limited to, data compression, data encryption & decryption, data conversion, and so on, in a situation where the complaint generation devices and complaint receiver devices understand different formats.
[0029] The validation controller 116 facilitates communication between the controller 110 and a presentation layer. Additionally, the service layer can comprise one or more business logics. The validation controller 116 includes one or more validation logics in order to facilitate communication between the controller 110 and the persistent layer. Embodiments herein disclose the implementation of automated checks and validations to ensure data accuracy during OEM complaint processing, such as verifying chassis numbers and customer details against the database and validating OEM team details to ensure proper routing of complaint data to the appropriate OEM team for resolution. Additional attributes verified during data insertion include: a data type check, which confirms that the entered data adheres to the correct type (e.g., numeric fields reject non-numeric entries); a code check, which ensures that a field contains a valid value or follows specific formatting rules (e.g., validating postal codes or country codes); a format check, which ensures that data, such as dates, are entered in a predefined format (e.g., "YYYY-MM-DD" or "DD-MM-YYYY"); a consistency check, which ensures data is logically consistent (e.g., confirming a delivery date is after the shipping date); and a uniqueness check, which ensures that fields like IDs or email addresses are unique, preventing duplicate entries in the database.
[0030] The secured business controller 118 is configured to coordinate the input from the one or more devices and data from the database to the controller 110. The secured business controller 118 can process one or more logical operations. The one or more logical operations would be with respect to preparing records of the OEM complaints in a suitable form such as, but not limited to, a tabular format, a graphical format, and so on, to present it to one or more authorized people such as, but not limited to, management, the technical team, and so on.
[0031] The DAO controller (Data Access Object controller) 120 creates a class for each table in the database, which can be used for separating object persistence and data access logic. Examples off the column headers of the table can be, but not limited to, product, OEM name, problem, time of failure detected, location, comments/additional notes, and so on. Examples of the classes can be, but not limited to, one or more categories of products, name of OEM, product type, product model, location, and so on.
[0032] The database 106 comprises the one or more OEM data related to one or more customer complaints, currently open complaints, closed/resolved complaints, and so on. Further, the database 106 stores a plurality of information related to a plurality of customer equipments, wherein the plurality of information may include such as, but not limited to, a plurality of equipment identification means such as, but not limited to, a serial number, vehicle chassis numbers for the respective customers. Furthermore, the database 106 contains a plurality of contact means in relation to the CCM and the HO such as, but not limited to, email IDs, phone numbers, and so on. The database 106 includes one or more computer-readable storage media and non-volatile storage elements. Examples of such non-volatile storage elements may include magnetic hard discs, optical discs, floppy discs, flash memories, or forms of electrically programmable memories (EPROM) or electrically erasable and programmable (EEPROM) memories. In addition, the internal storage unit may, in some examples, be considered a non-transitory storage medium. The term “non-transitory” may indicate that the storage medium is not embodied in a carrier wave or a propagated signal. However, the term “non-transitory” should not be interpreted to mean that the memory is non-movable. In some examples, the memory can be configured to store larger amounts of information than the memory. In certain examples, a non-transitory storage medium may store data that can, over time, change (e.g., in Random Access Memory (RAM) or cache).
[0033] Further, embodiments herein disclose the use of a Data Access Object (DAO) design pattern for handling data interactions within the system. The DAO design pattern serves as a structured framework for managing data retrieval and storage from a database or other data sources. This design pattern abstracts the underlying complexities of data storage and retrieval, providing a standardized interface for developers to interact with the data, thereby facilitating a more organized and efficient system architecture.
[0034] Embodiments herein disclose a method for handling concurrent OEM complaint submissions by multiple users, wherein the server processes the data in parallel while ensuring the order of complaint recording using a FIFO (First In, First Out) approach during database insertion. These complaints are made accessible to relevant Dealers, CCMs, and Head Office users through their respective portals, with Dealers viewing complaints submitted by their employees, CCMs accessing complaints from dealerships within their territory, and Head Office users viewing complaints from dealerships across India. The application server 104 enforces data access permissions based on the user's organizational hierarchy. Further embodiments herein disclose techniques for optimizing system performance, including index optimization to enhance update speed by reviewing and adjusting indexes based on dataset update patterns, and parallel processing to improve performance for large datasets by splitting the data into smaller parts and distributing update operations across multiple processing units or nodes using distributed databases, multiprocessing, or multithreading technologies, depending on the specific environment.
[0035] Embodiments herein disclose a method for processing OEM complaints submitted by users through the one or more client devices, wherein the application server processes each complaint request concurrently when multiple users create complaints simultaneously. To ensure that complaints are recorded in the order they are received, the system employs a FIFO (First In, First Out) approach during database insertion. This guarantees that the order of complaint submission is maintained, regardless of concurrent complaint processing.
[0036] According to the embodiments herein, the users submit the OEM complaints via the one or more complaint registration client devices 102A, where the OEM data undergoes validation before being processed and synced to the application server 104. After validation, the application server 104 generates an automated complaint form with a unique identification number. The application server 104 sends an email, including the auto-generated complaint form and any defect images, to an appropriate OEM team for a specific region. The OEM team is responsible for resolving the OEM complaints. The complaint reports generated are accessible to entities connected to the OEM, such as, but not limited to, dealers, CCMs, head office personnel, and the like.
[0037] The application server 104 is configured to automatically generate one or more OEM complaint forms based on the submitted complaints and transmit messages along with the generated complaint forms to one or more OEMs for resolving the complaints. The OEMs resolve the complaints by either creating a ticket or assigning a technical person to address and close the complaints. Additionally, the server generates complaint reports that include details of each complaint, which are accessible to users, OEMs, and CDMS-CCM/HO devices 102B. The CDMS-CCM/HO devices 102B analyze multiple component failures in the complaint reports and periodically notify the respective OEMs regarding the types of complaints. The one or more CDMS-CCM/HO devices 102B is configured to analyze the one or more complaint reports and notify the respective OEMs periodically based on at least one geographical region. These steps are further detailed below.
[0038] FIG. 2 is a flowchart depicting a method for OEM complaint generation and complaint registration through the system 1000, according to the embodiments herein. At step 210, one or more OEM complaints are registered through the one or more complaint registration client devices 102A. In an example, the users can register the OEM complaints through a CDMS service advisor App with media of the failed parts. The one or more complaint registration client devices 102A generate the one or more OEM complaints. The one or more OEM complaints as generated are thereafter communicated to the controller 110 of the application server 104 via the communication network 108. At step 220, the application server 104 generates one or more OEM complaint reports at the CDMS-CCM portal followed by step 230, wherein the application server 104 generates the one or more OEM complaint reports are generated at the HO portal. When a user raises a complaint through the client devices, the OEM data is validated and synced to the application server 104. A unique complaint number is then assigned, and an automated email is sent to the appropriate OEM team for the specific region. An auto-generated complaint form, along with any defect images, is included in the email for further action. At step 240, the controller 110 auto-creates one or more OEM claim forms with the media of the failure parts. At step 250, one or more messages (such as, but not limited to, an email, a SMS, an instant message, and so on) with respect to one or more OEM claims/complaints is auto generated and transmitted to one or more authorized OEM contact information, as determined by an authorization controller 112 of the application server 104. At step 240, one or more OEM team receiving the one or more OEM claim, can generate ticket(s) assigning a service provider to resolve one or more complaints related to the one or more OEM claims. The various actions in method 2000 may be performed in the order presented, in a different order or simultaneously. Further, in some embodiments, some actions listed in FIG. 2 may be omitted.
[0039] FIG. 3 illustrates a method 3000 for registering OEM complaints through the system 1000, by one or more complaint registration client devices 102A. At block 301, OEM complaint in a CDMS service tap is selected for scanning or entering an input for authentication, wherein the input is such as, for example, without limitation, a chassis number. At block 302, a complaint registration page is provided by the complaint registration client device 102A. A plurality of data related to customer identity, OEM identity (such as without limitation OEM part, OEM make, OEM serial number and so on), one or more complaints are entered in the complaint form. At block 303, one or more medias of the failed machinery parts are uploaded, and the complaint registration page is saved.
[0040] FIG. 4 depicts an auto-generated complaint registration form and an auto-generated email notification having the complaint registration form including engineer’s feedback is transmitted to an authorized complaint registration client device 102A and CDSM-CCM/HO devices 102B, according to the embodiments herein.
[0041] FIG. 5 depicts an OEM complaint report generated by the application server 104 including third party dealer information of CCM client and/or HO client, customer information, customer complaint and engineer’s observation, wherein the OEM complaint report is stored in the database 106, according to the embodiments herein.
Use-case scenario:
[0042] In an example, a farmer in Punjab experiences a tire malfunction on their tractor and uses a mobile application provided by the CDMS-CCM/HO to submit a complaint. Through the application, the farmer can enter the complaint details, such as the type of equipment (tractor tire), a description of the issue (a puncture or excessive wear), and upload pictures of the damaged tire. Once the complaint is submitted, the system validates the information, ensuring it is accurate and complete before forwarding it to the central application server for processing.
[0043] After the complaint data is validated, the system generates an automated complaint form with a unique identification number for tracking. This form, along with any defect images, is sent via email to the appropriate OEM team responsible for handling issues in the farmer’s region (Punjab). Simultaneously, the complaint is logged in the system, making it accessible to dealers, customer care managers (CCMs), and head office personnel across India. For example, if the tractor manufacturer’s head office in Maharashtra wants to monitor the resolution process, they can access the system to track the complaint. The system ensures that the OEM team in Punjab is notified and can take swift action to resolve the issue, ensuring a transparent process for the OEM, the CDMS-CCM/HO, and the user (dealers, farmers, etc), regardless of the user’s location in India.
[0044] The embodiments disclosed herein can be implemented through at least one software program running on at least one hardware device and performing network management functions to control the network elements. The network elements shown in FIG. 1 include blocks which can be at least one of a hardware device, or a combination of hardware device and software module.
[0045] The embodiment disclosed herein describes an OEM complaint registration management system and a method of registering OEM complaint at a remote Server. Therefore, it is understood that the scope of the protection is extended to such a program and in addition to a computer readable means having a message therein, such computer readable storage means contain program code means for implementation of one or more steps of the method, when the program runs on a server or device or any suitable programmable device. The method is implemented in at least one embodiment through or together with a software program written in e.g., Very high speed integrated circuit Hardware Description Language (VHDL) another programming language, or implemented by one or more VHDL or several software modules being executed on at least one hardware device. The hardware device can be any kind of portable device that can be programmed. The device may also include means which could be e.g., hardware means like e.g., an ASIC, or a combination of hardware and software means, e.g. an ASIC and an FPGA, or at least one microprocessor and at least one memory with software modules located therein. The method embodiments described herein could be implemented partly in hardware and partly in software. Alternatively, the invention may be implemented on different hardware devices, e.g., using a plurality of CPUs.
[0046] The foregoing description of the specific embodiments will so fully reveal the general nature of the embodiments herein that others can, by applying current knowledge, readily modify and/or adapt for various applications such specific embodiments without departing from the generic concept, and, therefore, such adaptations and modifications should and are intended to be comprehended within the meaning and range of equivalents of the disclosed embodiments. It is to be understood that the phraseology or terminology employed herein is for the purpose of description and not of limitation. Therefore, while the embodiments herein have been described in terms of embodiments, those skilled in the art will recognize that the embodiments herein can be practiced with modification within the scope of the embodiments as described herein.
,CLAIMS:We claim,
1. A system for managing one or more OEM complaints from at least one user of at least one agricultural vehicle, the system comprising:
one or more complaint registration client devices (102A) and one or more Customer Data Management System-Customer Care Management/Head Office (CDMS-CCM/HO) devices (102B),
wherein the one or more complaint registration client devices (102A) and the one or more CDMS-CCM/HO devices (102B) are communicatively coupled to an application server (104) via a communication network (108),
wherein the at least one user registers the one or more OEM complaints through the one or more complaint registration client devices (102A),
wherein the application server (104) is configured to:
auto-generate one or more OEM complaint forms based on the one or more complaints;
auto-transmit one or more messages along with the one or more OEM claim forms to one or more OEMs for resolving the one or more complaints, wherein the one or more OEMs resolve the one or more complaints by one of creating a ticket and assigning a technical person to close the one or more complaints; and
generate one or more complaint reports comprising details of each of the one or more complaints, wherein the generated one or more complaint reports are accessible to one or more of the at least one user, the one or more OEMs, and the one or more CDMS-CCM/HO devices (102B), wherein the one or more CDMS-CCM/HO devices (102B) analyses a plurality of component failures in the one or more complaint reports and notifies respective OEMs periodically regarding types of the one or more complaints.
2. The system as claimed in claim 1, wherein the one or more CDMS-CCM/HO devices (102B) is configured to analyze the one or more complaint reports and notify the respective OEMs periodically based on at least one geographical region.
3. The system as claimed in claim 1, wherein the application server (104) comprises a Model-view-controller for:
controlling interaction between the one or more complaint registration client devices (102A) and the one or more CDMS-CCM/HO devices (102B),
determining one or more responses to be transmitted to the one or more complaint registration client devices (102A);
controlling OEM data related to the one or more OEM complaints through an authorization controller (112) to check authority of the one or more clients to access the OEM data; and
restricting an access to the OEM data based on a type of one or more clients.
4. The system as claimed in claim 1, wherein the one or more complaint registration client devices (102A) are configured to receive registration of the one or more OEM complaints by:
authenticating the one or more complaint registration client devices (102A); and
providing a complaint registration page for one of scanning and entering an input, wherein the input comprises the one or more OEM complaints and one or more medias related to failed machinery parts.
5. The system as claimed in claim 1, wherein the OEM data related to the one or more complaints is registered through an application interface of the one or more complaint registration client devices (102A), wherein the application interface of the one or more complaint registration client devices (102A) is linked to one or more of a CDMS-CCM and a HO portal.
6. The system as claimed in claim 1, wherein the application server (104) comprises a presentation controller (114) configured to:
provide the OEM data related to the one or more OEM complaints from the application interface of the one or more complaint registration client devices (102A) to the one or more CDMS-CCM/HO devices (102B); and
convert the OEM data from one format to another using one or more data operations.
7. The system as claimed in claim 1, wherein the system comprises a database (106) comprising the OEM data related to the one or more OEM complaints.
8. The system as claimed in claim 7, wherein the system comprises a Data Access Object (DAO) controller (120) configured to create a class for each table in the database (106) for organizing the OEM data related to the one or more OEM complaints.
9. The system as claimed in claim 1, wherein the system is configured to perform automated checks and validations during OEM data insertion, and validating OEM team details to ensure that the OEM complaint data is transmitted to an appropriate OEM team for resolution.
10. The system as claimed in claim 9, wherein the automated checks and validations comprise:
a data type check to ensure that fields accept only a correct data type;
a code check to verify that specific fields are selected from a predefined list of valid values or conform to formatting rules;
a format check to ensure that the OEM data are entered in a predefined format;
a consistency check to confirm logical coherence between data entries; and
a uniqueness check to ensure fields are unique within the database.
11. The system as claimed in claim 1, wherein the system is configured to enforce data access permissions to users based on an organizational hierarchy.
12. The system as claimed in claim 8, wherein the DAO controller (120) further comprises an index optimization mechanism configured to review and adjust database indexes based on dataset update patterns to enhance the speed and efficiency of database updates.
13. The system as claimed in claim 8, wherein the DAO controller (120) employs one or more parallel processing techniques for handling large datasets, wherein the large datasets are divided into smaller parts.
14. A method for managing one or more OEM complaints from at least one user of at least one agricultural vehicle, the method comprising:
registering one or more OEM complaints, by the at least one user, through the one or more complaint registration client devices (102A);
auto-generate one or more complaint forms based on the one or more complaints;
auto-transmit one or more messages along with the one or more OEM claim forms to one or more OEMs for resolving the one or more complaints, wherein the one or more OEMs resolve the one or more complaints by one of creating a ticket and assigning a technical person to close the one or more complaints; and
generate one or more complaint reports comprising details of each of the one or more complaints, wherein the generated one or more complaint reports are accessible to one or more of the at least one user, the one or more OEMs, and the one or more CDMS-CCM/HO devices (102B), wherein the one or more CDMS-CCM/HO devices (102B) analyses a plurality of component failures in the one or more complaint reports and notifies respective OEMs periodically regarding types of the one or more complaints.
15. The method as claimed in claim 14, wherein the method comprises periodically notifying the respective OEMs, by the one or more CDMS-CCM/HO devices (102B), based on at least one geographical region.
16. The method as claimed in claim 14, wherein the method comprises utilizing a Model-view-controller framework in the application server (104) for:
controlling interactions between the one or more complaint registration client devices (102A) and the one or more CDMS-CCM/HO devices (102B);
determining one or more responses to be transmitted to the one or more complaint registration client devices (102A);
controlling the OEM data related to the one or more OEM complaints through an authorization controller (112) to pre-verify authority of the one or more clients to access the OEM data; and
restricting access to the OEM data based on the type of the one or more clients.
17. The method as claimed in claim 14, wherein receiving the registration of the one or more OEM complaints by the one or more complaint registration client devices (102A) further comprises:
authenticating the one or more complaint registration client devices (102A); and
providing a complaint registration page for scanning or entering an input, wherein the input comprises the one or more OEM complaints and one or more media related to failed machinery parts.
18. The method as claimed in claim 14, wherein the OEM data related to the one or more complaints is registered through an application interface of the one or more complaint registration client devices (102A), and the application interface is linked to one or more of a CDMS-CCM and a HO portal.
19. The method as claimed in claim 14, the method further comprising:
providing, by a presentation controller (114), the OEM data related to the one or more OEM complaints from the application interface of the one or more complaint registration client devices (102A) to the one or more CDMS-CCM/HO devices (102B); and
converting the OEM data from one format to another using one or more data operations.
20. The method as claimed in claim 14, further comprising:
storing, by a database (106), the OEM data related to the one or more OEM complaints.
21. The method as claimed in claim 19, further comprising:
creating, by a Data Access Object (DAO) controller (120), a class for each table in the database (106) for organizing the OEM data related to the one or more OEM complaints.