TimeSheet System was developed for corporate control and analysis of time spent by employees for projects, projects expenses and profit.
You can create account for each employee in your company and set him access permissions. Also you can create users groups and set permissions for them as well. Users have additional (hidden) fields in the database accessible for managers and administrators, like hour price, work week in hours, holiday duration in days, etc. Separately user can have permissions set for different global menu items like "Fill Hour-Declaration", "Edit Projects List", "Reports" and others.
The basic feature of the System is acquisition of information from employees about work during a week. Each employee can have several projects assigned, and can book certain hours on projects defined by manager during a specified time period. Apart from hours declaration allows filling in distances in kilometers (if needed or paid) or business travel expenses (hotels, meal, etc.). Each declaration can be finally approved and attached to a certain invoice.
System has built-in simple interface for declarations overview. Normal users can see their hours, project managers can see hours booked on according projects and line managers can see all hours of their users.
Edit activities list
Work on certain Project can include several activities like ‘Specification agreement’, ‘Schematics development’, ‘PCB Layout’ etc. All this can be taken into account within the system.
Each user declaration must be approved by line manager which must be set individually for each user. Approved declaration becomes locked and blocked for user editing.
The System operates the following categories used for user-projects binding:
- Customer - contains all the client information, top-level object in the hierarchy;
- Project - object allowing directly assigning users/groups and work activities.
Almost every object type in the database can be used for data analysis and reports generation. It is possible to create report templates, as long as report instances. Report results generated remain in the database so they can be reviewed after.
Languages, Libraries and Object models used