Follow with the “Incomes” menu, incoming financial movements and your customers and all the elements revolving around them, such as contracts, quotations, bills, catalogs …
Phone number of the client contact.The field is not numeric and lets you add textual information such as the extension number.
Levels of service agreements
Determines if you have levels of service agreements (SLA) with the client for this contract. This check box is an indication.
Intervention time
Periods during which services, contacts and interventions with the client will be possible. You can choose a time slot for weeks, Saturdays, as well as Sundays and holidays.
Section Progress
In the Progress section, determine the different dates and deadlines for the contract, notice, deadlines, payments …
A quotation is a proposal estimate sent to customer to get approval of what’s to be done, and how must the customer will pay for it.
On the quotation form, you can record all the information about the sent proposal, including attaching some file completely describing the proposal with details terms and conditions.
Transform quotation to order
A quotation can be copied into an order when corresponding document is received as customer agreement.
Bill lines section
This section allows to detail the quotation modality.
the financial gallery allows you to display in list form and by elements,
the different client quotation, invoices and orders recorded in ProjeQtOr,
per date, client or per type, partial, final and complete bill.
You can manage the turnover of the project at completion, and its consistency with the orders and invoices on the project.
A “Revenue management” section is visible on the projects screen in the Progress section after activation of the “Revenue management” module under the financial section.
The following information is then accessible:
The turnover at completion corresponds to the total amount that will be invoiced for this project.
Display of the sum of the project’s customer orders
Display of the sum of customer invoices for the project
Method of valuation of turnover
Method of valuation of turnover fixed
The turnover is fixed and is entered manually
Method of valuation of turnover variable
Variable over time depending on the activities
The turnover will then be calculated from the turnover of all the activities (not canceled) of the project and possibly of the sub-projects. In this case the activities will also have a turnover field to feed.
Projects with sub-projects will systematically have a “Variable” valuation mode, this mode will automatically consolidate the turnover of the sub-projects on the parent project.
Consistency with project orders and invoices
For projects with sub-projects, the sum of orders and invoices will consolidate the data of the sub-projects, that is to say, it will integrate the orders and invoices of the sub-projects in addition to the orders and invoices possibly on the project itself.
The sum of the orders is in red if it is lower than the turnover.
The sum of the invoices is in red if it is greater than the turnover.
Raise alerts
You can create definable alerts for projects in the “unit indicators” section:
Revenue upper than command’s sums
Revenue less than invoices sums
In order to integrate this evolution into the community version, without disturbing the users who do not need this functionality, we will condition the behavior:
In order to transcribe the current use of the validated cost, a global parameter will determine whether the turnover is automatically reported as validated cost on activities and projects.
Note
This functionality is only visible if the Revenue Management module is activated via the access rights menu in Modules management.
The Revenue Managment is a sub-module of the financial module.
This new module will activate / desactivate the management of OUs and everything related to the management of OUs (see below).
You can assign any catalog to a project, whatever its position in the structure, while maintaining the notion of inheritance on the sub-projects.
A “catalog used” field on the projects screen is available.
The OUs proposed on the activities of the project will systematically be the OUs of this catalogue.
When the “catalog used” field is populated (entered or edited) for a project, all subprojects (recursively) that had the same initial catalog value (or no value) are assigned the new catalog value.
The level of recursion stops at the first project that does not respect this rule.
When a catalog is created or modified to be attached to a project then the “catalog used” field of the project is updated, and the update is passed on to the sub-projects.
Important
Only profiles who have the right to modify the project catalog will be able to modify it, regardless of the project on which it is used.
Create a catalog
In the Finance menu Incomes section Catalog of work unit screen.
Click on to create a new catalog
Field
Treatment
Name
Name of the catalog.
Nomenclature
Code usually a reference shared with the customer.
Project
Project on which to use the catalog
Number of complexities
Maximum number of complexities, set in global parameters.
Complexities
Text fields to fill in the complexities of the catalog
Warning
If the number of complexity isn’t filled then the default number set in the global parameters is applied.
Then fill in the fields with the name of the complexities managed by this catalog.
Click on to open the pop-up windows and complete the complexity details.
You can fill in the following fields for each OU:
Reference
Description
Incomes
Deliverable
validity date
The description, incoming and deliverable fields are text editors in inline mode. Edit buttons appear when the cursor is in the field.
You can select an OU on an activity, only if the project has a Variable CA valuation mode.
We will inform the OU, its complexity and the number of units:
Entering the OU in the list of OUs in the catalog linked to the project. This will dynamically populate the list of OU complexities by displaying only those that have a charge and a price that is not zero but may be equal to zero.
Entering complexity
Entering the quantity number of work units
An activity will only be associated with a single OU / Complexity pair.
If OU is selected, complexity and quantity are mandatory, otherwise they are prohibited, i.e. not enterable.
The UO / Complexity / Quantity data will make it possible to value:
The validated load = load of the OU / Complexity x Quantity
The turnover of the activity = price of the OU / Complexity x Quantity
The validated duration = duration of the OU / Complexity x Quantity
Entering the validated duration will automatically calculate the validated end date if the validated start date is entered.
Note
This will only determine the planned duration of the activity if it is in “fixed duration” planning mode.
Otherwise, the schedule will determine the planned duration from the assigned load and the availability of assigned resources.
These 3 data (validated load, validated duration, CA) will then go into read-only since they are calculated.
If the OU’s expiry date has passed, an alert will be displayed on the activity, without this blocking the recording of the activity.
If the global parameter “Report of turnover on the validated cost of activities” is activated, the turnover entered or entered through the OU is recopied in the validated cost of the activity.
Exportation
You can export the data of the OUs used on the export of Activities.
There are as many columns as there are reference/complexity pairs defined in the OU catalog. This is only viable if you only export activities that only use the same catalog.
A mechanism ensures that exported activities all use the same catalog.
Modification of data
You can modify the catalog on the data of an OU, a Complexity or a Quantity however it is not possible to modify a unit of work from the catalog, if it is already used on an activity.
Re-calculation of validated data: validated load, validated duration and turnover
If resources are assigned, application of the variation in the assigned load, in proportion to the load assigned to each resource and updating of the “still to do” accordingly (without ever being able to become negative).
Tip
For example:
In the case of an OU whose complexity generates 5 days of load with a quantity of 1, if A is assigned for 2 days and B assigned for 3 days, if we double the quantity (and therefore the validated load) A is then assigned 4 days and B is assigned 6 days.
Habilitations
The concept of Project on the catalog is not essential, it is present to guarantee the management of rights: only profiles who have the right to modify the catalog of the project will be able to modify it, regardless of the project on which it is used.
A resource with a profile allowing him to instantiate a OU but who does not have the visibility of the costs can continue to instantiate an OU, the value of the turnover will not be displayed, nor the “price” column of the table units of work, regardless of whether the OU carries a charge or a duration (0 included).
Deletion of data
You can delete the catalog on the data of an OU, a Complexity or a Quantity however it is not possible to delete a unit of work from the catalog, if it is already used on an activity.
The validated load data, validated duration and CA become manually modifiable again
The calculated data is kept
The project turnover will be updated from the sum of the turnover of the project activities, whether this data is entered from an OU or entered manually.
The turnover of the activities and the UO, Complexity and Quantity data will only be accessible for “basic” activities (which do not have sub-activities). For “parent” activities, the turnover will be consolidated from the turnover of the sub-activities.
You can close an unit of work directly in the OU’s window.
In the Turnover section in Progress of the details area, the drop-down menu of the services ordered offers you the list of orders,
only if the project is an activity project, where the unit of work ordered is the same unit of work on the activity and where the complexity is consistent with that of the order.