Access our channel Contact Us
English (US)

Hello, how can we help you?

Recent Searches: Closing an audit - Accessing a scope or working paper via link - Creating an audit plan - Creating an audit template

SoftExpert Project general parameters

 

Prerequisite

  • Access to the Configuration > General parameters (PR049) menu.

 

Introduction

The general parameters menu allows for setting the component's default configurations, applicable to all records created in your system. These configurations can aid in and facilitate the use of the available resources.

See how to configure the general parameters of SoftExpert Project:

 

Configuring the general parameters

1. Access the Configuration > General parameters (PR049) menu.

2. In the Project section, set the parameterizations referring to the projects that will be added in the system:

Parameter Checked Unchecked
Allow responsibility route to update automatically The responsibility route will be updated by the system whenever it is edited, while the project with which it is associated is under revision or approval. The responsibility route associated with the project will not be updated when it is edited.
Release the task executions that are not pending The Task execution (PR017) menu will display all the tasks that are under the logged user's responsibility in order for them to be executed. This user can only execute the tasks that are within the execution period and whose predecessor tasks have their execution duly closed. This parameter does not apply to the My tasks > Task execution menu.
The project ID # is read-only The ID # of new projects added in the system cannot be edited. In this case, an automatic number will be generated. If the type that will classify the project is configured to have a mask with permission for ID # change, this configuration will not be applied. The "ID #" field will be enabled for completion, except if the project type is configured to have a mask without permission for ID # change.
Set task verification as default All tasks that are added to the projects in the system will go through the verification step by default. If necessary, this configuration can be edited through the data screen of each task. The tasks added to the projects will not go through the verification step by default.
Allow entering retroactive dates in the execution of tasks When executing the task, it will be possible to enter start and/or end dates prior to the current date. When executing the task, it will not be possible to enter task start and end dates prior to the current date.
Allow entering retroactive percentages in the execution of tasks The executors of the task can enter an execution percentage lower than the one already inserted. The executors cannot enter an execution lower than the one already inserted for the task. In this case, only the project manager, through the Management > Project tracking (PR013) menu, can backtrack the inserted execution percentage.
Consider the actual percentage of the tasks in the calculation of the progress The system calculates the progress of the project on the basis of the values entered in the Actual % field of the tasks. The system automatically calculates the actual execution value on the basis of task duration, of the project structure, and of the weight of each task inside the project.

In the Revision subsection, define whether the projects must go through revision:

Revision

Enable control by project type Check this option so that it is possible to make revisions mandatory through the Revision tab of the project type. Thus, only the projects that have such configuration will be required to go through revision.
Mandatory to revise the project replanning Check this option so that all projects added in the system must necessarily go through revision. Define, right below, in the "Block in tracking" option, which project information can be edited only in the revision step.
Require completing the comments when starting a project revision Click on this option so that filling in the "Comments" field is mandatory for the creation of a new project revision or program revision. If this option is not checked, revisions can be added without the need for filling in this field.
Suspend project when starting a revision Check this option so that the project can be postponed automatically when a revision is started. This parameter can also be enabled through the project type data screen.
Block in tracking
  • Project schedule: check this option so that it is not possible to edit the dates of project tasks and project schedules. Editing other information, such as ID #, name, responsible parties, and attributes, will still be possible.
  • General project data and project schedule: check this option so that it is not possible to edit any general data information referring to project tasks and project schedules.

Display: [Elapsed time] [Time left till deadline] [Attention level]

Check the options corresponding to the project/task statuses that must display the elapsed time, the time left till deadline, and the attention level of the projects/tasks: Planned, Rescheduled, and/or Actual.

3. In the Indicator section, configure the indicators that will be used in portfolio and program viewing, as well as in the calculation of the attention level:

Configuration

Indicator configuration

Define the type that will be applied to the indicators of the projects of a certain portfolio or program:

  • Stabilize: select this option so that the calculation of the indicators referring to the deadlines, resources, and results of the projects is stable in relation to the configured value range; that is, the higher the score of the project, the worse its classification will be. Value ranges are configured in the Stabilize section.
  • Minimize: select this option so that the calculation of the indicators referring to the deadlines, resources, and results of the projects is considered as "The lower the better" in relation to the configured value range; that is, the higher its score, the worst its classification will be. Value ranges are configured in the Minimize section.
Score calculation

Define the calculation of the indicators referring to deadlines, resources, and results:

  • Optimistic: the system will consider the values that are equal or within the configured value range.
  • Pessimistic: the system will consider only the values that are greater or smaller than the values configured in the range; that is, if the achieved score is equal to the limit specified for the range, the project will be classified in the next range.

Stabilize

This section will only be enabled if the indicator configuration is Stabilize. In the Deadline (%), Costs/revenues (%), and Resource (%) sections, configure, as percentages, the following value ranges:

  • Good: first, define the value interval that will classify the projects (as to deadlines, resources, and results) as good. From these values, it is possible to set the other ranges of the indicator.
  • Acceptable: define the value interval that will classify the projects (as to deadlines, resources, and costs/revenues) as acceptable. These ranges take on values already set in the Good range.
  • Bad: define the value interval that will classify the projects (as to deadlines, resources, and costs/revenues) as bad. These ranges take on values already set in the Acceptable ranges.

Note that 5 value ranges are configured for this indicator configuration type.

 

Minimize

This section will only be enabled if the indicator configuration is Minimize. In the Deadline (%), Costs/revenues (%), and Resource (%) sections, configure, as percentages, the following value ranges:

  • Good: first, define the value interval that will classify the projects (as to deadlines, resources, and costs/revenues) as good. From these values, it is possible to set the other ranges of the indicator. 
  • Acceptable: define the value interval that will classify the projects (as to deadlines, resources, and costs/revenues) as acceptable. These ranges take on values already set in the Good range.
  • Bad: define the value interval that will classify the projects (as to deadlines, resources, and costs/revenues) as bad. These ranges take on values already set in the Acceptable ranges.

The indicators configured in this section can be tracked through the D (Deadline), R (Resources), and $ (Result) columns on the view screens of portfolios and programs.

 

4. In the EVM section, configure the earned value management indicators of the projects and their tasks, setting a generic frequency for their calculation:

  • Calculation frequency: enter the interval of days, weeks, or months in which EVM calculation must be performed for all projects.
  • Base value for the calculation: define whether the value to be used as basis for the EVM calculation will be the planned or the rescheduled value.
  • CPI (Cost Performance Index): fill in the value ranges that will classify the cost performance index as good, acceptable, or bad.
  • SCI (Schedule Cost Index): fill in the value ranges that will classify the schedule cost index as good, acceptable, or bad.
  • SPI (Schedule Performance Index): fill in the value ranges that will classify the schedule performance index as good, regular, or bad.
  • HPI (Human Performance Index): fill in the value ranges that will classify the human performance index as good, regular, or bad.

5. In the Integration section, configure the integration with the Risk component to manage the risks of the project:

Parameter Checked Unchecked
SE Risk Project risks will be added through the Risk component and associated with projects. The action type, risk type, risk, and strategy menus will be displayed in the system to allow for recording risks and their treatments, thus making it possible to associate risks with projects.

6. Click on the button to save the parameters.

 

Conclusion

The parameterizations set will be applied to all system records as of now!

Related articles:

Was this article helpful?

Index

Prerequisite Introduction Configuring the general parameters Conclusion

First steps

Advanced resources

New features