Work Order/Trouble Ticket system

The purpose of this project is to develop an automated system where customers can submit trouble tickets, work orders can be generated and every step of the process can be tracked. The "system" will have an end-user, administrative and technician "front ends". The "system" should be developed in ASP, VB and MS-SQL. Database tables and relationships have already been developed in Microsoft Access. The end user/customer, technician and parts database tables will be used for other modules which will include lead tracking and sales quote generating modules. The system should be designed in such a way so that it can be used by multiple departments and/or companies. (Each with a different work order, etc.) The purpose of this project is to develop an automated system where customers can submit trouble tickets, work orders can be generated and every step of the process can be tracked. The "system" will have an end-user, administrative and technician "front ends". The "system" should be developed in ASP, VB and MS-SQL. Database tables and relationships have already been developed in Microsoft Access. The end user/customer, technician and parts database tables will be used for other modules which will include lead tracking and sales quote generating modules. The system should be designed in such a way so that it can be used by multiple departments and/or companies. (Each with a different work order, etc.) The front end and various "pages" are to be accessed via a simple website. A sample work order will be supplied of how we want the work orders to be generated for printing. ## Deliverables 1) Complete and fully-functional working program(s) in executable form as well as complete source code of all work done. 2) Deliverables must be in ready-to-run condition, as follows (depending on the nature of the deliverables): a) For web sites or other server-side deliverables intended to only ever exist in one place in the Buyer's environment--Deliverables must be installed by the Seller in ready-to-run condition in the Buyer's environment. b) For all others including desktop software or software the buyer intends to distribute: A software installation package that will install the software in ready-to-run condition on the platform(s) specified in this bid request. 3) All deliverables will be considered "work made for hire" under U.S. Copyright law. Buyer will receive exclusive and complete copyrights to all work purchased. (No GPL, GNU, 3rd party components, etc. unless all copyright ramifications are explained AND AGREED TO by the buyer on the site per the coder's Seller Legal Agreement). * * *This broadcast message was sent to all bidders on Monday Aug 15, 2005 12:47:11 PM: Several of you have asked similar questions, here are the answers to most of them. If you need me to clarify anything else please send me the questions. I do not mind the questions if it means that the project will be completed to our liking. 1. We would like to receive the finished product as a "MicroSoft Installer Package" so that we can install it on our server. 2. The preferable languages should be ASP.NET and VB.NET using Microsoft SQL Server. We DO NOT run MySQL nor do we want the program developed in PHP. 3. The entire product will be accessable via MS-Explorer, Firefox, etc. 4. We would prefer to make the login piece secure using HTTPS, or some other secure method of transferring the login information. 5. We DO NOT have a staging server. Everything should be created and tested using sample customer data and on your staging/development serv ers. 6. This is the first phase of a multiple phase project. Additional coding projects will be awarded to the coder that wins this contract if they do a good job. (We will be adding a sales quotation module in the near future) 7. The forms that will be created for the technicians are to be a template that can be printed out. We will supply a sample of our current work order form in Word format. A work order is a printed trouble ticket that has space for the technician to write a detailed description of the work done and which the customer signs once the work is completed. Imagine a service technician that goes to your home, the paper you sign is a work order. 8. What is meant by "other departments/companies" is that we have other parts of our company that do different types of work and are kept seperate for internal purposes. (Different technicians and administrators and different customers) In the event that we decide to use the ticketing system for one of these other companies we would like to keep the data for the different "companies" seperate from each other. In some cases the customer data MAY be the same, in other cases it may NOT be the same. There should be a way of indicating whether or not it should create seperate tables in the adminstrative page. ## Platform Windows based server, program should be written in ASP and Visual Basic with Microsoft SQL. The front end will be accessed via HTML. Color scheme should be the same as our current website (This will be a link on our website) [login to view URL]