In this section, it is possible to perform general parameterizations and those regarding resources, communication, timesheet and project status report. To do that, the following subsections are available:
In this section, it is possible to perform the following configurations:
Project
|
Security
|
This field will be displayed with one of the options selected by the system, according to the configurations set in the general parameters of the system, however, it is possible to edit it. In that case, select one of the following options to define how the project security will be:
▪Public: Any user with access to SE Project will also have access to the project data. ▪Restricted: Access to the project will be restricted to the following members: project leader, program approvers (if this step is configured), responsible for project task, stakeholders and allocated resources. |
Time format
|
The time format configuration performed in the project type will be displayed.
|
Default task type
|
This field will be filled out by the system with the default task type defined on the project type, but it is possible to edit it. In this case, select the type that will classify the tasks that will be added to the project through SE GanttChart.
|
Color
|
Select the color that will identify the project in the resource allocation schedules.
|
Pattern
|
Select the pattern that will identify the project in the allocation schedules of the resources.
|
View profile
|
This field is filled out with the default view profile set in the project type, but it is possible to edit it. In that case, select the view profile that will be applied to the SE GanttChart visions of the project. Use the other buttons next to the field to view the selected view profile data, restore the profile to the record settings and clear the field.
|
Schedule from
|
Select one of the options to configure how the project schedule will be defined: from the project Start date or End date. Ideally, the definition of the project schedule should be made from the planned start date, but in some cases, it is best to make this definition as of the end date, such as when it is of uttermost importance that the project is completed on a specific date.
|
Enable automatic recalculation of schedule
|
This option will be displayed checked or unchecked according to the definitions set in the project type; however, it is possible to edit it. In that case, check this option for the project schedule to be recalculated automatically. Note that this option will only be available if the time format is set to Days.
|
Allow this project to be edited by the responsible in charge of the macro-project?
|
If the project in question is a subproject, check this option for the leader of the upper level project (master project) to also be allowed to make changes to the project in question.
|
Generate automatic identifier in the tasks
|
This option will be displayed checked or unchecked according to the definitions set in the project type; however, it is possible to edit it. Check this option so that the project tasks ID # (SE GanttChart) is generated by the system. In that case, the system will generate a sequential number to identify the tasks; and it may not be edited. Uncheck it so that the task ID # can be edited, allowing the user to enter a number or code to identify the task.
|
Allow the allocated resources to perform tasks
|
Check this option so that resources allocated to the tasks of this project can inform the actual percentage of their execution and close the tasks.
|
Allow the process status to be changed according to the change in the project status
|
Check this option to allow editing the status of the processes (Workflow, Incident, Problem) with which the project is associated. The status will be edited when the Cancel, Postpone, and Reactivate actions are executed in the project and when the association between project and instance is blocking.
Note: To automatically reactivate the project, the process instance must be manually reactivated. The explanation will be stored in the process history, as well as the information that the status was automatically edited through the SE Project integration.
|
Schedule
|
If the time format of the project is "Hours", through this section it will be possible to edit the time settings made on the project type Schedule tab. To do that, define whether the options for the schedule calculation basis will be used and whether the duration will be directed by effort or not.
|
Finance
In this section, it is possible to define how the financial values related to the project will be calculated. The displayed fields will be filled out according to the configurations set in the project type; however, it is possible to edit them.
Field
|
Cost configuration/Revenue configuration
|
In these fields, select one of the following options:
▪Variable: The system will consider the cost/revenue values and the resource values in the calculation of the total values of the project. ▪Fixed: The system will only consider cost/revenue values in the calculation of the total values of the project, regardless of the resource values. |
Classify costs as Capital/Operational
|
Check this option to define that the project costs will be classified and then, select one of the options to define a default classification for the costs in the project: Unclassified, Operational (OPEX) or Capital (CAPEX). This classification will be displayed in the Finance section.
|
Block editing of financial values after project closure
|
Check this option to indicate that, after closure, it will not be possible to edit the values for the project costs and revenues. If this option is not checked, after the project closure, it will still be possible to update the values of its costs and revenues as necessary.
|
EVM
|
In this section, it is possible to configure the frequency that will be used to calculate the EVM. To do that, check the Specific configuration option and then, enter the number of days, weeks or months that will be used in the calculation and whether the planned or replanned values will be used as a base.
|
|
Use this section to perform the configurations regarding the resources to be allocated to the project tasks. The available subsections must only be completed after allocating resources to the project tasks. They are:
Cost
Allows adding the planned costs related to the resources involved with the project. To do this, click the button on the side toolbar and fill out the following fields of the screen that will open:
Field
|
Date
|
Select the date from which the planned cost will be valid.
|
Resource
|
Select the resource allocated to the task which the cost being added refers to. Use the other buttons next to the field to view the data of the selected resource and clear it.
|
Hourly rate
|
Enter the normal, overtime and weekend working hourly cost of the previously selected resource.
|
Use the other buttons from the side toolbar to edit or delete the planned cost from the resource selected in the list of records.
Billing
Allows adding the planned billings related to the resources involved with the project. To do this, click the button on the side toolbar and fill out the following fields of the screen that will open:
Field
|
Date
|
Select the date from which the planned billing will be valid.
|
Resource
|
Select the resource allocated to the task to which the billing being added refers. Use the other buttons next to the field to view the data of the selected resource and clear it.
|
Hourly rate
|
Enter the normal, overtime and weekend billing hourly cost of the previously selected resource.
|
Use the other buttons from the side toolbar to edit or delete the planned billing from the resource selected in the list of records.
Functional role
It allows associating the functional roles that can be taken by the resources involved with the project and their respective planned values. To do this, click the button on the side toolbar and fill out the following fields of the screen that will open:
Field
|
Date
|
Select the date from which the functional role will be exercised in the project.
|
Functional role
|
Select the functional role that will be played by a resource in the project.
|
Hourly rate
|
Enter the cost of the normal, overtime and the weekend working hour rate of the previously selected functional role.
|
Use the other side toolbar buttons to edit or delete the functional role selected in the list of records.
User X Role
It allows associating the resources of the nonproject task with the functional roles that they will exercise. To do this, click the button on the side toolbar and fill out the following fields of the screen that will open:
Field
|
Task
|
Select the project task for which you wish to define a functional role.
|
Resource
|
Select the resource allocated to the previously selected task, for which you wish to define a functional role.
|
Functional role
|
This field will be filled out by the system with the functional role that the user is associated with; however, it is possible to edit it. In that case, select a functional role which the user is associated with and which they will play in the project.
|
Use the other buttons on the side toolbar to edit or delete the association of a user who plays a determined functional role to a selected task in the list of records.
|
In this section, it is possible to configure the automatic email sending when certain actions/steps are performed in the project. The options in the Enable automatic e-mail sending for: list are displayed, marked or unmarked according to the settings made in the general parameters, but it is possible to edit them.
Project step
|
Who receives the e-mail
|
Project approval
|
▪Pending sequence approvers |
Project rejection
|
▪User responsible for the project ▪Team members responsible for the project |
Task execution
|
▪User responsible for the task ▪Team members responsible for the task |
Allocation notification on task being executed
|
▪Resources allocated to the task |
Task verification
|
▪User responsible for the upper level task (summary or project) ▪Team members responsible for the upper level task (summary or project) |
Task failure
|
▪User responsible for the task ▪Team members responsible for the task |
Task closure notification
|
▪User responsible for the upper level task (summary or project) ▪Team members responsible for the upper level task (summary or project) |
Project revision approval
|
▪Pending sequence approvers |
Project revision rejection
|
▪User responsible for the project ▪Team members responsible for the project |
Revision acknowledgment
|
▪Users configured to receive revision acknowledgment |
Task execution approval
|
▪Pending sequence approvers |
Task execution failure
|
▪User responsible for the task ▪Team members responsible for the task |
Project closure approval
|
▪Pending sequence approvers |
Project closure rejection
|
▪User responsible for the project ▪Team members responsible for the project |
Project closure
|
▪User responsible for the project ▪Team members responsible for the project |
Project closure notification
|
▪User responsible for the project ▪Team members responsible for the project ▪User responsible for the task of the project ▪Team members responsible for the task of the project ▪Project planning approvers ▪Project closure approvers ▪Stakeholders |
Rescheduled date notification
|
▪Users configured to receive task date change notification |
Timesheet approval
|
▪Pending sequence approvers |
Timesheet rejection
|
▪User who performed the timesheet |
Cancelled project
|
▪User responsible for the project ▪Team members responsible for the project ▪User responsible for the upper level projects and programs ▪Team members responsible for the upper level projects and programs ▪Resources allocated for tasks of the project ▪User responsible for the task of the project ▪Team members responsible for the task of the project |
Postponed project
|
▪User responsible for the project ▪Team members responsible for the project ▪User responsible for the upper level projects and programs ▪Team members responsible for the upper level projects and programs ▪Resources allocated for tasks of the project ▪User responsible for the task of the project ▪Team members responsible for the task of the project |
Reactivated project
|
▪User responsible for the project ▪Team members responsible for the project ▪User responsible for the upper level projects and programs ▪Team members responsible for the upper level projects and programs ▪Resources allocated for tasks of the project ▪User responsible for the task of the project ▪Team members responsible for the task of the project |
|
In this section, it is possible to configure when those involved in the project will be notified of the due date of the deadline for the execution of its tasks, by means of "My tasks" email notification. For that, fill in the following fields:
Field
|
Notify before due date
|
Check this option for the responsible party to be notified before the day on which the deadline to execute the task expires. Use the Notify before field to enter how many days in advance the notification will be sent.
|
Notify on due date
|
Check this option for the responsible party to be notified on the day the deadline to execute the task expires.
|
Notify after due date
|
Check this option for the responsible party to be notified after the day on which the deadline to execute the task expired. Use the Notify after field to enter how many days the notification will be sent after the expiration deadline, and in the Frequency field, in days, the frequency in which the notification will be sent.
|
Subordinates' tasks
|
Check this option to define who will be notified about the deadline to execute the task referring to the project through the "Subordinate task" (SE Configuration) email notification. Fill out the following fields:
▪Notify leader of responsible user: Check this option for the leader of the responsible user to receive the execution status notification of the task referring to the project. ▪Specific user: Check this option and, in the User field that will be enabled, select a specific user who will receive the task execution referring to the project. ▪Go up to __ level(s): Enter which levels above the responsible user's leader level, will be notified about the task execution referring to the project. ▪Frequency: Enter the number of day(s) past due that the system will go up the hierarchy until it reaches the configured level. |
|
This section will display the configurations referring to the task timesheet, performed in the project type; however, it is possible to edit them. Refer to the Timesheet section for a detailed description of the displayed fields.
The configurations set on this tab will only work correctly if the SE Time Control component is part of the solutions acquired by your organization. These configurations will impact the "Timesheet" screen. Refer to this component specific documentation for further details about the timesheet.
|
|
In this section, the system will display the status report templates that have been associated with the project type. On the side toolbar, the following buttons are available:
|
Click on this button to associate a status report template with the project. On the screen that will be opened, locate and select the status report template and save the selection. Use the CTRL or SHIFT keys on the keyboard or the checkbox next to each record to select more than a status report template at a time.
|
|
Click on this button to delete the report template association from the project type. Select the desired record before clicking on the button.
|
|
Click on this button to view the data of the status report template selected in the list of records.
|
|
Click on this button so that when there is more than one status report template associated with the project type, it is possible to set the status report template selected in the list of records by default.
|
|
Click on this button to configure the external sharing for a status report. Select the desired record before clicking on the button. On the screen that will open, in the Who do you wish to share it with? field, enter departments, positions, teams and users of the system that has an email configured, as well as, emails from parties who do not have access to SE Suite, for which you wish to send the sharing link. In the Share message field, enter the message that will appear in the body of the email that will be sent with the sharing link. After that, save the record.
|
|
Click on this button to update the listing of status report templates in this section to match the listing of status report templates associated with the project type. Note that by clicking on this button it only adds/deletes the report templates according to the project type, but it makes no changes to the default status report template.
|
In the "Automatic?" column, it is possible to configure if the project status reports will be generated automatically. To do that, enable the field corresponding to the report you wish to generate automatically. Note that this option is only available if, on the Scheduling tab of the status report template data screen, the recurrence for its automatic generation has been configured. If the "Automatic?" option is not enabled, the project status report must be generated manually, through the Status report section, in project tracking.
▪If the report in question has external sharing configured and this option is enabled, the external access link to the status report will be sent by email according to the recurrence configured on the Scheduling tab. ▪The automatically generated reports can be viewed from the tracking data screen or by the third quadrant of the main screens, which display the details of the project. |
|
This section will only be displayed if the automation with SE Audit is configured in the project type. Check the Requires tracking option for the system to track all the occurrences and incidents associated with the audits created from the projects based on this template. Next, select, in the respective field, the responsible team for tracking occurrences (the members of the selected team will receive the Occurrence tracking) and enter the deadline in days for the closure of all occurrences associated with the audit.
|
|