The Application Manager is the user with the highest level of rights in the Cerri Project application. Configuring and managing Cerri Project requires a deep understanding of the application.
Before starting with Cerri Project, the application manager must define several key parameters:
- Main and secondary currencies:
- The currency of a Projects database cannot be changed once documents have been created in the database.
- Workload unit:
- In the Timesheets and Projects databases, it is possible to choose between days and hours as the unit of time measurement.
- The units of these databases may differ.
- By default, the unit is 'Hours' in the Timesheets database and 'Days' in the Projects databases.
- The unit cannot be changed once documents have been created in a database.
Initial Setup (mandatory for on-premises only)
The initial setup is performed once per database after its creation by the administrator.
It consists of:
- Linking the new database to the 'Portfolio' database (the 'Portfolio' database is the only one not linked).
- Creating or modifying the mandatory setup documents.
Resources Administration
Resources administration involves the creation of new resources (users) and, if necessary, companies and groups.
- One Resource document is required for each user of the application.
- A resource may be created even if there is no corresponding user. For example, a generic resource can represent a customer, project leader, or developer in a project template.
- Use the 'Resource' document to specify the resource's license, rates, and distribution profile (among other details).
- Use the Company document to group resources by company. If company rates are used, ensure companies and the corresponding Rates setup documents are created before adding resources.
- The Group document (on-premises only) allows defining Company Directory groups for document distribution and access rights. This is especially useful when the company's address book contains a large number of groups.
Additional Setup
The additional setup involves creating optional setup documents and, potentially, the customizing databases.
The application manager can create (or delegate the creation of) document templates and project templates.
Project Templates
Projects templates are reusable elements that can save project leaders significant time.
- Each defined project template may include a set of documents that already contain data. This enables the automatic inclusion of partially filled-out documents in new projects created from the template.
- Any kind of document, such as a Microsoft® Office document, can be attached to a template, offering maximum flexibility and reusability.
Monitoring
During normal database operations, issues may arise when agents process documents, especially in the 'Projects' and 'Timesheets' databases.
Examples:
- A user inputs time on a task through their timesheet that has been deleted.
- A resource inputs time on a task through their timesheet after they are no longer assigned to it.
In such cases, a specific document is flagged as a problem and displayed in a designated view. This allows for the detection and reprocessing of these documents. Usually, the documents must be corrected manually before being reprocessed.