Introduction.

The target users of the application are the service oriented software companies who want to properly administer their client projects, compare planned and actual dates and want the employees to register their time against the planned tasks in the projects in order to generate invoices to the clients automatically.

This document describes the use of the Projectmanagement application from the different project roles point of view, which are:

• Administrator: has full access over all projects
• Client Manager, Client Analyst: has full read access over the assigned project, can approve and can report time.
• Client Billing: who will receive the invoices.
• Provider Manager: has full access to the project he is member of.
• Provider Accounting: who can create invoices and send these to the Client Billing,or if not present to the Client manager.
• Provider Analyst, Provider Validator, Provider Functional Implementer, Provider Test Implementer are all provider team members who can register time on tasks.
  Demonstration data is provided with the component which is loaded with the ./ant run-install command. All mentioned demo login id's have the password 'ofbiz'.

Before we are going to the projectmanager roles, first  more about the system organization and the various system status values.

System organization.

The system is orgnized at the top level as 'Projects' which consist of 'phases' and phases consists out of 'tasks'.  This structure is mandatory: mo tasks without a related phase and no phase without a related project. The information is maintained at the task level only like estimated and actual hours,dates and the status. The information at the phase and project level is derived from the information at the task level: if all tasks are completed, the project is completed.

Another part of the system are the time sheets which are entered in a weekly period only. It is only possible to report on project tasks for projects of which the person is member of the project team, depending on security the member of the team can also add tasks (not phases) to the project.

Further is is possible to (re)assign tasks to the logged on user and to other persons in the project. 

Various Statusvalues explained. 

There are various status values in the system, they are in two groups, the Project status values and the timesheet status values these groups are pretty independant.

Timesheet Status. 

If a time sheet status is set to complete it is indicated the timesheet party has completed the entry of hors for that week and has no intention to add more hours for that period. The projectmanager can set the status back to 'in progres' to allow to correct errors.

Project Status. 

The project status is maintained at the person --> task level only. All other status values at the task, phase and project are derived values. If all assigned persons on a task set their status to complete, then the task will be complete. If all tasks on a phase are complete, the phase is complete, if all phases on a project are complete, the project is complete.

Task status 

The task status itself is also derived from all the persons/task status assigned to this task. This person/task status has 2 values only: 'Assigned' or 'completed' The assignment can also be removed or reassigned.

The possible task status values: 

1. No persons assigned to this task: the task status is 'unassigned'.
2. At least one person is assigned to this task: the task status is 'assigned'.
3. At least one person has registered time for this task: the task status is: 'in progress'
4. If all persons have set their personal status of the task to complete: the task status is: 'complete'  

Project administrator Role

The project administrator has full access over all projects, can perform all tasks of any projectmanager and additionally can:

• Create new projects and assign a project manager
•  maintain skill types
• maintain resources in the resources manager.The demo login id for this role is 'admin'.

Project manager Role.

The project manager is responsible for one or more projects and can perform the tasks of any project member and additionally can do the following functions:

1. Create or make sure a proper Resource list exist by selecting existing parties in the project resources tab.
2. Create a project with related phases and tasks or copy these from a template.
3. Add resources from the resourcelist to the project.
4. Add planned start and end/dates and estimated hours required (a scheduler is planned)
5. Start the project and let everybody register their time in the mytime option.
6. Monitor on a weekly basis the registered hours.
7. Monitor the planned versus actual dates in the project.
8. Create invoices at the end of the month from the entered timesheets

The demo login for this role is 'DemoEmployee1'.

Project participant Role.

The project participant can use the 'myTask' and 'myTime' functions and read all other information about the projects:

• assign and reassign tasks in projects he is a member of.
• enter time in a weekly time sheet to report about the worked hours.
• View all information about any project.
  Perhaps it is good to note here, that as many as is required, approval authorities can be added to the task and that without their approval the task cannot get into the completed status. In the 'mytask' tab the tasks are listed for which approval is required.

The demo login for this role is 'DemoEmployee2' for project 1.
The demo login for this role is 'DemoEmployee3' for project 2.
The demo login for this role is 'DemoCustomer1' for project 1.
The demo login for this role is 'DemoCustomer2' for project 2.

Project accounting Role.

The project accounting role consist out of the following activities:

• Be able to define the party rates and party rate types.
• Be able to create invoices from registered hours on projects which were not yet billed.
  

Please note that this is an application in development and comments are welcomed, either in Jira as a request or at the bottom of the page.