Change to Project Management System

This project requires changes to be done to an existing project management system. The creation of a calendar/gantt chart of sorts is involved. Each project in the system needs to associate itself with a worktype. each worktype will be associated with a pipeline (stages of the project and the estimated timeline of each stage). When the user is adding the project, they will select from the worktypes created by the administrator. then they select the current stage of the project. The estimated start and end dates for the rest of the pipeline is then generated and displayed by the system. It is also put into the database for the project. As the project moves along, the “estimated?? start and end dates turn into “actual?? start and end dates ??" because as the project moves along we can stipulate the dates more precisely. Next to each “estimated end date?? the user must have the ability to make changes. So, if the project is running behind or ahead, the user will click on the estimated end date and make the adjustment (with a new estimated end date). This adjusts the dates associated with the other stages. When a stage change is made (project moves from one stage to another), the user must verify the actual end date. This changes the end date associated with that stage, and changes the est. start and end dates for the rest of the stages. The user should then have the ability to see this in a calendar view. It will show the project pipeline stages as a bar running across the calendar through the appropriate days. Each stage is a different color, and is properly labeled. The current stage should always be in red. The user can make changes to actual and estimated dates in this view as well. -------- A main calendar is also needed (to view all projects). A query will also need to be added to the search function on the page so users can search by worktype / stage. ## 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). ## Platform needs to work on the popular browsers, explorer, safari, firefox, camino, netscape, etc. the server is linux.