Requirement Properties

Negotiation requirements request additional information about a supplier company. For example, such information could include company history, structure, personnel or industry certifications. Supplier answers to requirements are used in combination with prices offered when evaluating competing responses.

Requirements can also be used internally by other evaluators, for example members of a collaboration team. Requirements are high-level questions that solicit information from suppliers who respond to a negotiation. This can include such information as history, corporate structure, and applicable certifications, among other things.

You can define new requirements for the negotiation or search for and add predefined questions.

Requirement Properties

When defining requirements for a negotiation, you use the requirement's properties to control its behavior. The following table lists the requirement attributes.

Property	Explanation
Section	The section containing the requirement.
Acceptable Value	The acceptable value for the parent which caused this requirement to be displayed.
Requirement	Name of this requirement.
Evaluation Stage	For two stage RFQs, requirements can be defined to a technical requirement section or a commercial requirement section. Requirements in the technical section are unlocked, unsealed, viewed and scored during the technical evaluation stage. Requirements in the commercial section are unlocked, unsealed, viewed, and scored during the commercial stage. The requirements in the commercial section cannot be unlocked until the technical evaluation stage is completed.
Revision	Indicates the current version of the requirement. Revisions are tracked for questions contained in the question library.
Requirement Text	The text for this requirement.
Level	Whether this requirement applies at the company level or at the site level.
Response	You can control the supplier's interaction with the requirement by specifying the response type. Suppliers do not have to respond to optional requirements. Suppliers must reply to required requirements. Suppliers can view but do not have to respond to display only requirements. Internal evaluators can view and score internal requirements.
Requirement Type	Specifies the format of the requirement question. You can define a: Simple text entry. List of values with a single possible selection (displayed as radio buttons). List of values with a multiple possible selections (displayed as check boxes). If you select either of the list options, you must also define the acceptable values for the list.
Value Type	The value type controls the data type that can be entered. There are six value types available: A text value accepts characters and numbers: A single line of text. Multiple lines of text in a text box. A numbers value accepts only numbers and the decimal point. Date values accept dates you select using the calendar picker. Date and time values use a date picker and time designations. A URL value type accepts a URL in the format http://url.name.here. URLs also accept https
Target	The optimum response value. This attribute is only displayed if Display Target is enabled.
Display Target	Indicates whether to display the target to the supplier. This attribute is only displayed it the requirement type is a text entry box..
Hint	Optional text prompting the supplier toward a response value.
Attachments from Supplies	Whether the supplier can submit attachments, and if so, whether they are optional or required. This attribute is only displayed if the requirement type is a text entry box..
Allow comments from suppliers	Whether suppliers can add comments to a response.
Scoring	Scoring indicates the method used to assign such scores: manually, automatically, or none. If you choose None, scores cannot be entered for responses, and no scoring calculations can be made. If you choose Automatic, the application scores responses when they are submitted by the supplier. The scores are based on the acceptable response values you must define. If you choose to manually score a response, you (or others) must enter scores once the negotiation is closed. Manually scored requirements can be scored by scoring team members.
Weight	The importance of this requirement relative to all other requirements. Any requirement being scored must have a weight assigned. Weights are used in conjunction with scores to calculate the requirement's (and requirement section's) weighted score. The sum of all requirement weights cannot exceed 100. You enable weights on the General tab of the Overview page. If weights are not allowed, the application uses the maximum score field to limit the maximum score allowed for each requirement.
Maximum Score	The maximum score indicates the maximum numeric score value which can be entered for a response to this requirement.
Knockout Score	A minimum score value that all responses must meet or surpass for that response to be shortlisted for awarding. When you begin awarding the negotiation, you apply the knockout score. All responses having a requirement response value that doesn't meet the knock out value are marked as not shortlisted for awarding.
Attachments	You can attach a file, a URL, or a text string. You can specify that the attachment is visible internally by collaboration team members, or by suppliers. When you upload an attachment, you marked its category: Internal to Sourcing. Miscellaneous. To Supplier.