In Ketura, a user simply means someone who has been given an account on the system. Most users will be given access to the system, but a project manager might also choose to create users to manage people without access to the system, such as subcontractors.
Who’s working on what, whenHolidays, training days, sickness, etc can have a big impact on a milestone or project schedule. Users’ availability to do useful work must therefore be specified if the system is to calculate accurate estimates of milestone and project plan completion dates. In Ketura, each user has an availability calendar to make this possible.
Ketura also needs to know the intended allocation of users’ time between the various active projects. This information is set in the allocation calendar for each user.
Working with users’ availability and allocation in Ketura is very quick and easy: a whole year of a user’s time is shown at once, and entire date ranges can be selected and altered at once.
As you would expect, Ketura makes readily available information about whether each team member has been able to spend the
intended amount of time on each project. This enables project managers to take corrective action by, for example, reducing
a team member’s less important duties so that he or she is able to focus more fully on a high-priority project.
ContactsKetura maintains a list of contacts. For each contact, you can store information such as the contact’s name, telephone number, postal address, email address and any comments concerning that contact. If an issue is created as the result of a customer reporting a problem or making a request, you may wish to record that fact by creating a contact for that customer and adding the contact to the list of contacts for the issue. This makes it easy, for example, to email all the contacts interested in an issue when the issue is resolved.
Note that Ketura automatically creates a contact for each user of the system.
