DNN Timesheet Upgrade

Create enhancements to existing DotNetNuke module source code. Take existing timesheet module and add new input and review interfaces. Must take module that has single day time entries and expand it to input time for multiple days/projects on single interface. Must be able to create more robust timesheet view/approval screens. Addition of new fields in timesheet module that can interface with user profile in dotnetnuke. The final project must be in a DotNetNuke module install package that can be easily installed on a new portal with one step. ## Deliverables I have purchased an existing DotNetNuke module called TimeXP. Please see working module at? <[login to view URL]> I would like to make some significant enhancements to the module to help my business. I would like to take the existing time input screen and have it allow a complete table to input time for the entire week at once, instead of one project/day at a time. So there needs to be the ability to select multiple projects on one day and for all the days of the week. Would prefer the ability to select whether to add another project entry for the day. I would like to add a field to the timesheet submission that is a vehicle field. This should be able to assigned as a default value by user. So in user properties you can assign a default vehicle and if the user is submitting time by default that vehicle is selected. There may not be a vehicle for a job so the ability to submit without a vehicle is needed. Also, I would like a check box that allows me specify whether maintenance is required, if this box is selected then a template email goes out to the superadmin user (see below) stating that maintenance is required and the vehicle id. Finally, there should be a field next to the vehicle used allowing input is current mileage. Similar to the project? manager? role currently in the module, I would like a foreman user group that can submit timesheets for any worker. Like it currently does, the timesheet should show who submitted the time in the audit trail. The second important enhancement to the project is a robust review and approval process. Currently the module has a project manager role that can review timesheets for employees assigned to a project and approve them. I would like to make it so a project manager does not have to be assigned to a project. There should be multiple project managers, all of which can view and approve timesheets. I would like one approval screen that shows all submitted timesheets for a weekly time period, in a table showing employee name, list of projects they submitted time for and the total hours for each project for that week. I would like the ability to drill in on a user's timesheets and go to the full detailed timesheets. I would like the project managers to be able to edit that timesheet in the detail screen and for their changes to be documented, similar to how the module currently works where there is an audit trail. Back on the review screen, I would like each project manager to have a column with a checkbox to approve timesheets. They should be able to check/deselect one at a time or at the top of the column a check all/uncheck all button. Finally, a project administrator group should be able to override all project manager functions, sort of a super project admin that can override all. The super admin should be a role that a user can be assigned to. Same with foreman and project manager. Whenever a? user is assigned to the project manager role then that user should have a column in the review screen. The review and approval process is necessary before the timesheet is finally submitted, similar to the process that currently exists in the TimeXP module. Once all the project managers have reviewed and approved the timesheet then it can be submitted. There should be an audit trail showing who reviewed and approved, just like the module currently does but with all the project managers. Finally, I would like all source code. Also, with the source code I would like the module in the DotNetNuke module installation package. I should be able to take the installation package zip file to a clean installation of DotNetNuke and simply install the module through the module install screen in DotNetNuke. Make sense?