Pass the CIPS Level 4 Diploma in Procurement and Supply L4M2 Questions and answers with ExamsMirror

Explanation

Assessing the risks by quantifying them should be done. Even with qualitative risk assessment, quantifying is still important since risks need to be prioritised.

Risk assessment can be qualitative or quantitative. Perform qualitative and perform quantitative risk analysis are two processes within the project risk management knowledge area, in the planning process group. While qualitative risk analysis should generally be performed on all risks, for all projects, quantitative risk analysis has a more limited use, based on the type of project, the project risks, and the availability of data to use to conduct the quantitative analysis.

Qualitative Risk Analysis

A qualitative risk analysis prioritises the identified project risks using a pre-defined rating scale. Risks will be scored based on their probability or likelihood of occurring and the impact on project objectives should they occur.

Probability/likelihood is commonly ranked on a zero to one scale (for example, .3 equating to a 30% probability of the risk event occurring).

The impact scale is organizationally defined (for example, a one to five scale, with five being the highest impact on project objectives - such as budget, schedule, or quality).

A qualitative risk analysis will also include the appropriate categorization of the risks, either source-based or effect-based.

Quantitative Risk Analysis

A quantitative risk analysis is a further analysis of the highest priority risks during a which a numerical or quantitative rating is assigned in order to develop a probabilistic analysis of the project.

A quantitative analysis:

- Quantifies the possible outcomes for the project and assesses the probability of achieving specific project objectives

- Provides a quantitative approach to making decisions when there is uncertainty

- Creates realistic and achievable cost, schedule or scope targets

In order to conduct a quantitative risk analysis, you will need high-quality data, a well-developed project model, and a prioritized lists of project risks (usually from performing a qualitative risk analysis).

Explanation

The Performance Specifications define what the system being designed must do, and not how it must do it. In this step a list of needs and wants should be created. The needs are customer requirements, while the wants are engineering desires. If a buyer adopts performance specification, the supplier will be free to choose how to make and deliver the product.

A technical specification document outlines how you’re going to address a technical problem by designing and building a solution for it.

A design specification is a detailed document providing a list of points regarding a product or pro-cess. For example, the design specification could include required dimensions, environmental fac-tors, ergonomic factors, aesthetic factors, maintenance that will be needed, etc. It may also give specific examples of how the design should be executed, helping others work properly (a guideline for what the person should do).

With conformance specification the buyer says what they want and how they want it and the supplier has to meet this

Detailed Explanation:An output specification defines the desired outcome or result of the procurement rather than specifying how the result should be achieved. A requirements brief outlines the goals, leaving flexibility for the supplier to propose solutions. Reference: CIPS Level 4, Output Specifications in Procurement.

Explanation

Kano model of excitement and basic quality (Kano et al, 1984; Berger et al, 1993; Matzler et al, 1996) brings a different perspective for the analysis of improvement opportunities in products and services because it takes in consideration the asymmetrical and non-linear relationship between performance and satisfaction. The Kano model classifies customers requirements in three categories (figure 3):

a) Basic Requirements (or Must-be requirement). The basic requirements fulfill the basic func-tions of a product. If they are not present or their performance is insufficient, customers will be extremely dissatisfied. On the other hand, if they are present or have sufficient performance, they don't bring satisfaction. Customers see them as prerequisites. For instance, for luxury automobiles, "air bags" are considered basic. A customer won't feel satisfied if the automobile has "air bag", however he/she will not buy it if “air bag” is not present.

b) Performance Requirements (or One-dimensional requirements). As for these requirements, satisfaction is proportional to the performance level – the higher the performance, the higher the customer's satisfaction will be and vice-versa. Gas consumption in automobiles is an example of these requirements. Usually customers explicitly demand performance requirements.

c) Excitement Requirements (or Attractive requirements). These requirements are key to cus-tomer satisfaction. If they are present or have sufficient performance, they will bring superior satisfaction. On the other hand, if they are not present or their performance is insufficient, customers will not get dissatisfied. For instance, a surprise gift at the end of a dinner in a restaurant will certainly bring satisfaction, but it will not cause dissatisfaction if not offered. These requirements are not demanded nor expected by customers.

Two other types of requirements may be identified in the Kano model: neutral and reverse ones. Neutral requirements do not bring either satisfaction or dissatisfaction. Reverse require-ments bring more satisfaction if absent than if present.

Diagram Description automatically generated

Explanation

According to US Department of the Navy, Benchmarking is a strategic and analytic process of continuously measuring an organisation's products, services, and practices against a recognised leader in the studied area.

Successful benchmarking will help you:

- Find who does the process best and close the gap

- Recognise the leading organisations in a process or activity

- Create performance standards derived from an analysis of the best in business

- Ensure that comparisons are relevant

- Measure your performance, your processes, and your strategies against best in business

- Measure business processes

- Assess performance over time

- Accelerate continuous process improvement (CPI)

- Establish more credible goals for CPI

- Establish actionable objectives

- Discover and clarify new goals

- Establish customer expectations of business standards set by the best suppliers in industry

- Help your organisation achieve breakthrough improvements

- Create a sense of urgency for change

- Increase customer satisfaction

- Become direction setting

- Provide a positive, proactive structured process

Benchmarking does not:

- Copy the other's processes

- Steal other business confidentiality

- Stop. Benchmarking is a continuous process.

Explanation

The specification that is produced too detailed will incur unnecessary cost because it does not allow suppliers to use their expertise in finding the most efficient way to produce it.

'No, because higher requirements in specification, the greater bargaining power of buying organi-sation': more detailed specifications could tighten the supplier base and potentially leave buying organisation with fewer potential supplier. This may reduce buyer's bargaining power in negotia-tion.

'Yes, because higher requirements will help buying organisation find the best supplier': in some circumstances, higher requirements will lead to smaller supplier base. In the worst scenario, there is no supplier who has capability to carry out those requirements

'Yes, because optimising the specification is the only method to achieve value for money': There are other methods to achieve cost saving and value for money, inter alia, volume concentration, relationship restructuring, etc.

Explanation

ISO/IEC 27001 is widely known, providing requirements for an information security management system (ISMS), though there are more than a dozen standards in the ISO/IEC 27000 family. Using them enables organizations of any kind to manage the security of assets such as financial infor-mation, intellectual property, employee details or information entrusted by third parties.

LO 3, AC 3.1

Detailed Explanation:Conformance specifications are highly detailed, covering exact materials, dimensions, tolerances, and technical drawings. They ensure precision in manufacturing and consistency between suppliers. Reference: CIPS Level 4, Specification and Contract Development.

Detailed Explanation:

Procurement teams bring valuable market insights, helping stakeholders understand supplier capabilities, potential risks, and alternative solutions. This knowledge ensures that specifications are both realistic and aligned with market conditions. Reference: CIPS Level 4, Specification Development and Supplier Collaboration.