Product documentation
This topic explains the basic setup for Tender Management. In the Tender Management app, the area Settings is available. This menu provides access to the different setup entities included in the Tender Management solution.
The following paragraphs describe the Settings entities.
Tender Management > Settings > General Settings
The parameters of Tender Management are explained here.
A Risk Category can be part of a Risk Category Type. The background is that not all Risk Categories are relevant for all projects. For example, political risks are generally not relevant to domestic tenders.
Standard Risk Categories should be described here. To maintain a clear overview, we recommend using several Risk Categories.
Risk Categories might be connected to Risk Category Types. The Risk Category Execution might be relevant for all Risk Category Types.
Political Risks might apply only outside the EU.
If Risk Category Types are not used, all Risk Categories are always relevant.
Risks are always connected to a Risk Category. A Risk Category might be connected to a Risk Category Type. The complete list of Risk Categories and Risks might be copied to new Opportunities and Quotes or Revised Quotes according to the settings in the Parameters. If a Risk Category Type is connected to an Opportunity or to a Quote, only the Risks from the Risk Category that is connected to that Risk Category Type are copied.
Risks may allready have default values. These default values are optional. If these values are entered, they are copied to the Opportunities and Quotes where applicable. The values of a Risk can always be changed in the Opportunity or Quote, without changing the default value. 
The Default Weighting Factor and the Default Risk Score can be changed by entering a value or using the + or - buttons.
The most common entities for an approval procedure are Opportunities and Quotes. We advise starting the approval process setup with these entities. This means Opportunity and Quotes have to be added in entity Approval Entities.
To continue the set up, click open for example the record Opportunity. The Approval Entity form opens where you see the display name and the selected entity. In the bottom part of the window, you can enter the attributes. The attributes should have the exact field names as used in the entity.
Attributes are the entity fields used to determine approval requirements. For instance the Estimated Revenue or the Relative Risk Score might be an attribute.
The next step in setting up an approval procedure is to define Approval Sets. For every entity that should be approved at least one Approval Set should have been defined. It may be possible to run several approval processes for the same Opportunity or Quote, although this is not part of the normal procedure.
Open an approval set record in order to view or define the approval steps. When adding a new Approval Step the following details are required to be filled:
There is no limit to the number of steps that can be created. However, a large number of steps can make the process more difficult to manage if an approver rejects a step.
CPV (Common Procurement Vocabulary) codes are used to classify the subject of public procurement contracts using a standardized European classification system.
In Tender Management, CPV codes can be maintained and assigned to tenders to identify the products, services, or works covered by the tender. This ensures consistent classification and supports reporting and analysis
