System Flow

Below is an illustration of the system execution flow:

The steps described below complement the illustration of the flow above and will be more comprehensively detailed in the body of this manual.

1. During the registration period of proposals, the users of the units register the investment proposals and send them to the initial evaluation

2. During the initial evaluation period of proposals, managers access the registered proposals that depend on their evaluation, update the registration data if necessary, and make a decision on the approval or reject of each of the proposals:

   • If approved, the proposal will proceed to the next stage of the flow
   • If rejected, the manager must enter a justification for the action, the proposal will receive the status "Rejected", and its flow will be terminated

3. During the technical evaluation period of proposals, technical experts access the approved proposals that depend on their evaluation (registered for the technical area under their responsibility), update the registration data if necessary and then end with their overall technical opinion (favorable or not favorable). If an area enters an unfavorable opinion, the result for that project will be "not favorable". For the result to be favorable, all areas must be in accordance with the proposal. What will determine whether a project will follow the flow or not, will be the area that has control over the technical evaluation dashboard. Even if the result of a proposal is negative, it can continue with the flow, because what determines whether or not the proposal will follow is the final decision in the technical evaluation dashboard.

4. During the prioritization period of proposals, managers can access the prioritization functionality available in the side menu of the application and define the priority of each of the proposals that were approved in the technical evaluation. Prioritization can be done from 1 to N levels, with the possibility of performing several simulations before the closing of the scenario.

5. During the approval period, proposals will be forwarded to the approval committee they belong to. The approval process can be configured through the system settings. The approval will be sequential, that is, after the approval of the level 1 manager it will be automatically sent for approval by the level 2 manager, and so forth. After the approval of all levels of the elevation, the status of the proposal will be changed to "Approved".

6. After the approval of the proposal, additional information can be included for execution. This information is complementary to the information of the proposal form, as well as its questionnaire and attachments. An example of use is the inclusion of the project code created by the company's ERP, so we can associate commitment data and carried out via load by spreadsheet.

7. The execution stage allows the monitoring of the project in the financial context, as well as the sending of the project to ppm, in order to carry out the physical monitoring.

8. The closing step allows technical areas to be aware or fill out project closure forms. With this all, areas can participate in the closure of the project.