02-11-2012, 08:05 AM
1.1 Project Summary:
The Project is about to make online application manageable by the product sailing company who provides the service on the product after the delivery of the product.
By this app., it will be useful for managing the product’s records, customer’s records for the company.
It’ll be the interactive to the user i.e. customer in a way that s/he can get the info of the product during the service period.
And further s/he can have the message or the mail to get the ready product from the service center as soon.
Throughout this app it’ll be easier to the company and beneficial too, by gaining the customer’s satisfaction.
The organizations which focus on customer’s satisfaction can earn the satisfaction of the customer by providing such a good and transparent Service center management system which makes the whole system talking to the user. And thus, the user can get expected outcome from the organization.
1.2 Purpose:
The objective of the app we are creating is about the easy going solution way for customer and where for the organization it will be easier to provide the services to the customer in better way.
We just want to make the process of service providing to the customer easier for both organization and customer.
1.3 Scope:
Currently there is no generalized system which can be used as a whole in service center. So, everyone has to keep different system for each and every component.
So we are going to develop a system which can be used as generalized system which can be used in each and every area of the service center.
After developing this application, this application will use as a vast application in service center area where more types of products are available for the service.
1.4 Technology and Literature Review:
The front end used in our project is Servlet JSP and the back end used is MY SQL.
Tools used are NetBeans 6.9, MySQL and Adobe Dreamweaver.
We will follow the Iterative Model for developing this Project and the whole the Project will be developed using the SDLC scenario.
Currently there is no generalized system which can be used as a whole in service center. So, everyone has to keep different system for each and every component.
So we are going to develop a system which can be used as generalized system which can be used in each and every area of the service center.
Further, in current system, there is no facility for the user to know their part’s status when it is in service station.
We will provide this function in our application. So, user can view part’s status any time from our web application. By just typing the Customer_ID the customer can get the situation, in which his/her product is now there in service center.
This application has almost four modules:
i. Customer module
ii. Part submission module
iii. Service module
iv. Admin module
Further, it can have replacement module and carry forward module also.
i) Customer Module:
In customer module there are basic details of customer like name of customer, address, contact no etc.
In this module, customer can check the status of his part which is submitted to the desk. For that, user has to enter his acknowledgment sleep number or say Customer_ID, and he can know the current status of his product or the part of the product.
The customer can get the message or mail to come and to take his product back after being serviced from the service center as soon.
ii) Part Submission Module:
In part submission module, part is submitted to desk for service. Form is filled by the employee with the customer detail and symptoms of the part.
In this form there are product details like product name, product serial no., manufacturing date, and expiry date is included. Whether the product is in warranty or not and all other things that are needed can be seen on the desk.
iii) Service Module:
Symptoms details are carried forward to the technical department for further assistance for resolving the problem in the part. The problem is derived from the symptoms described by the user at the desk.
In service module, part is serviced or it is repaired as symptoms shown in the desk part. During and after servicing the part, status is updated to customer module and given back to the desk.
During this if the problem is insolvable then the part or the product is sent for the Replacement by taking the permission of Admin.
iv) Replacement Module:
The part which is not repair and need to replace is sent to the replacement module.
In this replacement module the old part will replace with new part so old part no. needs to replace with the new product no.
v) Admin Module:
The service system administrator is used to maintain the references data used by the service management system software. The process and utilities for the service management system are also contained in the system.
In admin module various types of information related to Employee Information, product information, customer information will be stored. Admin is there to manage all the details of the Service Center. Admin can add the products or delete the products; also he can add the employs as well.
First when, product is manufactured, admin can add that product for the automatic warranty status details. Product’s warranty can extend through the retail invoice of the customer. Also, service charge of in warranty and out warranty can be derived by the admin. Admin can take replacement and can change replaced part warranty period as per the old part warranty period.
