Cracks on the jet engine is a closed-end problem. A typical problem solving process has 8 steps:
Step 1: Define the Problem
- What is the problem?
- How did you discover the problem?
- When did the problem start and how long has this problem been going on?
- Is there enough data available to contain the problem and prevent it from getting passed to the next process step? If yes, contain the problem.
Step 2: Clarify the Problem
- What data is available or needed to help clarify, or fully understand the problem?
- Is it a top priority to resolve the problem at this point in time?
- Are additional resources required to clarify the problem? If yes, elevate the problem to your leader to help locate the right resources and form a team.
- Consider a Lean Event (Do-it, Burst, RPI, Project).
- Ensure the problem is contained and does not get passed to the next process step.
Step 3: Define the Goals
- What is your end goal or desired future state?
- What will you accomplish if you fix this problem?
- What is the desired timeline for solving this problem?
Step 4: Identify Root Cause of the Problem
- Identify possible causes of the problem.
- Prioritize possible root causes of the problem.
- What information or data is there to validate the root cause?
Step 5: Develop Action Plan
- Generate a list of actions required to address the root cause and prevent problem from getting to others.
- Assign an owner and timeline to each action.
- Status actions to ensure completion.
Step 6: Execute Action Plan
- Implement action plan to address the root cause.
- Verify actions are completed.
Step 7: Evaluate the Results
- Monitor and Collect Data.
- Did you meet your goals defined in step 3? If not, repeate th 8-Step Process.
- Were there any unforeseen consequences?
- If problem is resolved, remove activities that were added previously to contain the problem.
Step 8: Continuously Improve
- Look for additional opportunities to implement solution.
- Ensure problem will not come back and communicate lessons learned.
- If needed, repeat the 8-Step Problem Solving Process to drive further improvements.
ANA has already known what is going on, the next step they should adopt is collecting more infor-mation on the problem. If the airline is hurry to the solution, it may choose 'Generate options ad-dressing the issue'. The crack on turbine blade can be welded, or the airline replaces a new blade. However, jumping to solution without knowing the root cause does not completely solve the prob-lem. The root cause is unaddressed, then it may occur in the future. Therefore, the airline should still collect information to find the root cause, then remove it.
Reference:
LO 1, AC 1.1

Risks like natural disasters - fire, flood, or weather-related event, and cyber-attacks can disrupt the supply chain seriously. Threats and disruptions mean a loss of revenue and higher costs, which leads to a drop in profitability. And businesses can't rely on insurance alone because it doesn't cover all the costs and the customers who move to the competition. Risks must be identified early and supplier should have a plan that ensures continuous operations during disasters.
There are several steps many companies must follow to develop a solid business continuity plan. They include:
- Business Impact Analysis: Here, the business will identify functions and related resources that are time-sensitive. (More on this below.)
- Recovery: In this portion, the business must identify and implement steps to recover critical business functions.
- Organization: A continuity team must be created. This team will devise a plan to manage the disruption.
- Training: The continuity team must be trained and tested. Members of the team should also complete exercises that go over the plan and strategies.
Reference:
LO 3, AC 3.2

In marketing, a customer value proposition (CVP) consists of the sum total of benefits which a vendor promises a customer will receive in return for the customer's associated payment (or other value-transfer).
Value analysis is concerned with existing products. It involves a current product being analysed and evaluated by a team, to reduce costs, improve product function or both. Value Analysis exercises use a plan which step-by-step, methodically evaluates the product in a range of areas. These include costs, function, alternative components and design aspects such as ease of manufacture and assembly.
Value engineering is concerned with new products. It is applied during product development. The focus is on reducing costs, improving function or both, by way of teamwork-based product evalua-tion and analysis. This takes place before any capital is invested in tooling, plant or equipment.
In this scenario, the company's objective is cost reduction, then value analysis or value engineering is more likely to be applied. The products are existing, so value analysis is the best option.
LO 3, AC 3.4

In sales and marketing, market segmentation is the process of trying to understand clusters of cus-tomers in terms of their buying behavior and their buying characteristics. There are some traditional segmentation approaches: geography, demography, types of industry and the benefits. Then there are newer segmentation approaches: behavioral, situational, and psychographic.
Procurement professionals can learn market segmentation from sales and marketing. Segmenting the market can help them to shape and manage the supply market effectively. According to Michael Porter, a market can be segment with array of products and buyers.

Source: Porter, Michael E.. Competitive Advantage: Creating and Sustaining Superior Performance (p. 234). Free Press. Kindle Edition.
In the scenario, the products that Dana needs to source is distinct in their features. The best way is to segment the market by product varieties.
Reference:
LO 2, AC 2.1

The writing of a complex specification should be treated as a project because it requires the brain power from different stakeholders. Many tools and processes of project management can be applied to complex specification development. Before engaging with the stakeholders and implementing the project, the project initial document should developed.
A Project Initiation Document (PID) is one of the most important components of project manage-ment, which forms the foundation for a company project. It is a reference point during the entire project, for the client as well as for the project team.
A PID bundles documentation into a logical reference work that collects all important information needed to start and run a project from a good foundation. After that, Project Initiation Document must be transferred to all stakeholders, including business sponsors.
This forms the basis for the project management. The documentation from which the PID is com-posed include the business case in which the project's justification can be found, the communica-tion plan and the project plan.
The PID is composed out of collected information and includes, among others, the following com-ponents:
- Project goal(s); what do you want to achieve with the project?
- Project size; how large is the project, how long does it take and how many people are involved?
- Project organisation; who are involved in the project, what are their tasks, responsibilities and authority?
- Limits and risks; what can cause a project to stagnate and are there risks related to the project?
- Stakeholders; who has a stake in the success of the project?
- Project checks and frame reporting; by carefully taking into account evaluation moments, it is clear to everyone what sample tests can be carried out during the process.
In addition, it is important that the Project Initiation Document also contains the following infor-mation:
- The background and occasion of the project, which together provide information about the con-text.
- The project organisational structure, which describes who has which management responsibility in the project.
- The project quality plan, describing who controls the quality of the products to be delivered and how it will take place.
- The total project planning, including the duration of all activities.
- The exception process, which describes how exceptions are dealt with and the steps of the escalation procedure.
- The risk log, including the measures that will be taken when there are unforeseen risks.
- The documentation structure of the project, in which the encoding and storage of all documents and products to be provided by the project has been recorded in advance.
Reference:
- CIPS study guide page 148
- Project Initiation Document (PID), a project management tool | ToolsHero LO 3, AC 3.3