Differenze tra le versioni di "PROJECTS"
| (17 versioni intermedie di 2 utenti non mostrate) | |||
| Riga 1: | Riga 1: | ||
| − | From the | + | {{draft}} |
| + | |||
| + | From the main menu it is possible to open the PROJECTS section. | ||
=== Orders === | === Orders === | ||
| Riga 5: | Riga 7: | ||
Only some user profiles (usually marketing/administrators/project managers, depending on the currently configured application settings) are given permission rights strong enough to create new orders and assign resources to them. | Only some user profiles (usually marketing/administrators/project managers, depending on the currently configured application settings) are given permission rights strong enough to create new orders and assign resources to them. | ||
| − | In order to | + | In order to start a project by adding new job tasks and assign resources (employees, budget) to them, it is necessary to create orders first. |
When an order is added for a previously created offer, many fields in the creation form will appear automatically filled up with the values provided earlier for the offer; all information missing or specific for the order can be provided in the designated fields. | When an order is added for a previously created offer, many fields in the creation form will appear automatically filled up with the values provided earlier for the offer; all information missing or specific for the order can be provided in the designated fields. | ||
| − | To create an order, click on the top left "Insert" button. | + | To create an order, click on the top left "Insert" button. It ls also possible to create an order from within the page of an already existing offer, through the "Create order" button. |
'''Mandatory fields''': | '''Mandatory fields''': | ||
* Customer | * Customer | ||
| − | * Type of order: select a value among the available choices, that are currently configured in the application settings; if no choice is appropriated, create a new one by clicking the '+' button on the right | + | * Type of order: select a value among the available choices, that are currently configured in the application settings; if no choice is appropriated, create a new customized one by clicking the '+' button on the right |
* Field / kind of activity | * Field / kind of activity | ||
* Description | * Description | ||
* State: the possible choices are Open - Closed - Stand by - Going to close. It is important to note that it won't be possible for the resources to add working hours to the order from their timesheets unless the state here is set to Open. | * State: the possible choices are Open - Closed - Stand by - Going to close. It is important to note that it won't be possible for the resources to add working hours to the order from their timesheets unless the state here is set to Open. | ||
| − | * Start date: use this field to set the first day from which working hours can be added in the timesheets by the assigned | + | * Start date: use this field to set the first day from which working hours can be added in the timesheets by the assigned employees |
* Project leader: select one person among the available choices, or add a new one by clicking the '+' button on the right | * Project leader: select one person among the available choices, or add a new one by clicking the '+' button on the right | ||
* Business unit manager: select the person in charge of the Business unit | * Business unit manager: select the person in charge of the Business unit | ||
| − | The Project leader and Business unit manager saved here are important pieces of information, because they will be the only users that Cometa will afterwards allow to give approval to the timesheets signed by the | + | The Project leader and Business unit manager saved here are important pieces of information, because they will be the only users that Cometa will afterwards allow to give approval to the timesheets signed by the employees working on the order and for the project, as well as to all their permits, licences requests and so on. |
'''Non-mandatory fields''': | '''Non-mandatory fields''': | ||
| − | * Amount: insert here the amount for the | + | * Amount: insert here the amount for the order. There is no constraint that the value provided here is the same as the whole amount of the offer. Therefore, a different (lower) value can be set here as it is possible to generate many orders for the same offer, splitting the initial amount (the total worth of the offer) into more parts. |
| − | * | + | * Workable days limit: maximum workable days limit for all the employees. If set, Cometa won't any longer allow to save working hours in the timesheets once the limit has been reached. This information may be useful in order to keep the progress of the work under control, especially for critical orders. By saving a limit lower than expected, as soon as Cometa will start preventing users from adding working hours in their timesheets the project manager will be informed and will be able to verify and promptly handle the situation, if necessary. |
| − | * | + | * Treatment of personal data: if the job order requires access to personal data, the flag must be set; it is possible to decide whether to fill in the Register of the treatment or not. By default, the compilation of the Register is not mandatory; in the customizations of Cometa, however, this can be modified. In that case, if the flag is set in the job order, Cometa will not allow to proceed further with the job order until the Register of the treatment has been saved. |
| − | * | + | * Priority |
| − | * | + | * Sector / type of activity |
| − | * | + | * Description |
| − | * | + | * Order number |
| − | * | + | * Order document |
| − | * | + | * Date of completion: if set, Cometa won't any longer allow the employees to save working hours in their timesheets after that date, even if the state of the job order is Open. |
| − | * | + | * Date of actual completion: this date can be set for information, it has no functional effects whatsoever though. |
| − | * | + | * Register of the treatment of personal data |
| − | * | + | * Job assignment signed: field to be set for information, with no functional effects |
| − | * | + | * Internal: use this flag if the job order is meant to manage only internal activities |
| − | * | + | * Availability: if flagged, a dedicated column in the timesheets will be enabled for the employees to save worked hours |
| − | * | + | * Daily allowance: if flagged, a dedicated field in the timesheets will be enabled |
| − | * | + | * Expenses rifatturabili: this option allows to charge the customer of the job order all the expense reimbursements of business trips. In the mobile app, it is possible to directly take pictures of receipts or invoices; this is especially useful when a trip lasts between different months, to allow the administration office to proceed with the reimbursement requests before the employee has come back to office. |
* Forza maturato: | * Forza maturato: | ||
* Cliente finale: Può esser utilizzato per censire l'utente finale a cui è in carico veramente la commessa. Per es se la commessa si riferisce ad una attività di appalto o subappalto. | * Cliente finale: Può esser utilizzato per censire l'utente finale a cui è in carico veramente la commessa. Per es se la commessa si riferisce ad una attività di appalto o subappalto. | ||
* Importo mensile fatturabile: utilizzato per i canoni. Importante anche per le commesse con canone annuale. | * Importo mensile fatturabile: utilizzato per i canoni. Importante anche per le commesse con canone annuale. | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
Versione attuale delle 08:43, 27 apr 2020
This page is currently a draft. -
Questa pagina è una bozza.
From the main menu it is possible to open the PROJECTS section.
Orders
The "Orders" section shows all the orders where the user is listed/assignated as a working resource. Only some user profiles (usually marketing/administrators/project managers, depending on the currently configured application settings) are given permission rights strong enough to create new orders and assign resources to them.
In order to start a project by adding new job tasks and assign resources (employees, budget) to them, it is necessary to create orders first. When an order is added for a previously created offer, many fields in the creation form will appear automatically filled up with the values provided earlier for the offer; all information missing or specific for the order can be provided in the designated fields.
To create an order, click on the top left "Insert" button. It ls also possible to create an order from within the page of an already existing offer, through the "Create order" button.
Mandatory fields:
- Customer
- Type of order: select a value among the available choices, that are currently configured in the application settings; if no choice is appropriated, create a new customized one by clicking the '+' button on the right
- Field / kind of activity
- Description
- State: the possible choices are Open - Closed - Stand by - Going to close. It is important to note that it won't be possible for the resources to add working hours to the order from their timesheets unless the state here is set to Open.
- Start date: use this field to set the first day from which working hours can be added in the timesheets by the assigned employees
- Project leader: select one person among the available choices, or add a new one by clicking the '+' button on the right
- Business unit manager: select the person in charge of the Business unit
The Project leader and Business unit manager saved here are important pieces of information, because they will be the only users that Cometa will afterwards allow to give approval to the timesheets signed by the employees working on the order and for the project, as well as to all their permits, licences requests and so on.
Non-mandatory fields:
- Amount: insert here the amount for the order. There is no constraint that the value provided here is the same as the whole amount of the offer. Therefore, a different (lower) value can be set here as it is possible to generate many orders for the same offer, splitting the initial amount (the total worth of the offer) into more parts.
- Workable days limit: maximum workable days limit for all the employees. If set, Cometa won't any longer allow to save working hours in the timesheets once the limit has been reached. This information may be useful in order to keep the progress of the work under control, especially for critical orders. By saving a limit lower than expected, as soon as Cometa will start preventing users from adding working hours in their timesheets the project manager will be informed and will be able to verify and promptly handle the situation, if necessary.
- Treatment of personal data: if the job order requires access to personal data, the flag must be set; it is possible to decide whether to fill in the Register of the treatment or not. By default, the compilation of the Register is not mandatory; in the customizations of Cometa, however, this can be modified. In that case, if the flag is set in the job order, Cometa will not allow to proceed further with the job order until the Register of the treatment has been saved.
- Priority
- Sector / type of activity
- Description
- Order number
- Order document
- Date of completion: if set, Cometa won't any longer allow the employees to save working hours in their timesheets after that date, even if the state of the job order is Open.
- Date of actual completion: this date can be set for information, it has no functional effects whatsoever though.
- Register of the treatment of personal data
- Job assignment signed: field to be set for information, with no functional effects
- Internal: use this flag if the job order is meant to manage only internal activities
- Availability: if flagged, a dedicated column in the timesheets will be enabled for the employees to save worked hours
- Daily allowance: if flagged, a dedicated field in the timesheets will be enabled
- Expenses rifatturabili: this option allows to charge the customer of the job order all the expense reimbursements of business trips. In the mobile app, it is possible to directly take pictures of receipts or invoices; this is especially useful when a trip lasts between different months, to allow the administration office to proceed with the reimbursement requests before the employee has come back to office.
- Forza maturato:
- Cliente finale: Può esser utilizzato per censire l'utente finale a cui è in carico veramente la commessa. Per es se la commessa si riferisce ad una attività di appalto o subappalto.
- Importo mensile fatturabile: utilizzato per i canoni. Importante anche per le commesse con canone annuale.