Welcome to the AIM2 (Automated Issue Management) Product Issue

Management Fast Track course. This course is designed for anyone who
works with AIMs and will teach you how to use the new AIM2 application
within the current AIM process.

This course includes interactive lessons and self-study reading which you
can complete as you require, the system will remember your last position in
the course. At the end of the course is a short quiz which you must pass with
a score 60% or higher to achieve course completion. It is not necessary to
complete all of the course content prior to attempting the quiz.

The Glossary includes descriptions of common terms and the PLM Support
details are available on the Help page. Use the Contents icon or the menu
on this page to navigate.

AIM is over 25 years old and used by thousands of people in Jaguar Land
Rover.
A project team including people from across the business together with the i-PLM programme
team have been working to create a more up-to-date solution to satisfy our current and future
business needs.

From Quarter 3 2015, AIM will be replaced by AIM2 with a phased roll-out based on vehicle
platforms.

Users will use this tool to manage existing AIMs that have not yet been migrated into ENOVIA.

Some factors related to the AIM tool are:

delivers robust reporting providing confidence to proceed

It has well established process to understand Programme Product Issues.

However...

1 in 5 AIMs 're-opened' after being Pended or Closed

1 in 7 AIMs remain at Open state for more than 3 months
Unclear Problem Definition & Issue Impact
Most AIMs are raised without associated Prevent Recurrence

The AIM2 tool will be available via the i-PLM solution ENOVIA. ENOVIA offers an integrated
solution allowing JLR to maintain a "single source of the truth".
In the future, this will be achieved with live links to the Bill of Materials, Vehicle and Engine
Programmes, Parts and Changes. From the ENOVIA AIM2 homepage, you will be able to create
and manage your AIMs.
Click a subject to learn more about AIM2
BenefitsFeaturesWhen should I raise an AIM?Sources of New IssuesTypes of AIMAIM Response
Types

Benefits

Seamless integration of Tools and objects in ENOVIA allows improved communication

of all Product Issue related information. Data can be updated and be available
immediately for consumption by teams located in different areas of the business working
on the same issue. A large library or archive of Issues allows JLR to ensure that time is
not spent working on previously raised issues and duplication of effort is reduced.
Robust actions for Prevent Recurrence management
Reduction of TGW and improvement in Customer Satisfaction
Improved communication through integrated tools leading to reduced re-work
Improved robust process providing timely closure of AIMs

Features

Better integration with other systems

More accurate reports
Many features and field descriptions you'll recognize from the existing system
Prevent Recurrence embedded into process and approach
Product AIMs integrated into 'single version of the truth' ENOVIA
AIMs directly linked to Parts, Changes and BoM
Connect Project Teams with Validated data
'On Demand' reporting of AIMs
AIMs linked to Vehicle Programmes and Cycle Plan

When should I raise an AIM?

It is very important for all users to know in which cases they should or should not raise an AIM.
Raise an AIM when:

a vehicle, system or component fails to meet a functional target

a vehicle, system or component does not meet manufacturing targets
a conflict of functional targets exist that requires technical resolution
there is any product related concern that, in your opinion, will result in Things Gone
Wrong (TGW)

Do not to raise an AIM when:

you want to highlight a problem with a business process

you want to use it as request for facilities, properties or resource
you cannot define the problem - Don't raise an AIM just to cover a worry

Sources of New Issues

A Product Issue or AIM can be raised at any time in the lifetime of a Vehicle or Engine
Programme. There are some differences depending on the Programme affected.

New Model Programmes (NMP)
All future Jaguar Land Rover Vehicle Programmes that are recognised on the corporate
Cycle Plan and in Programme Central.
Between <PS> and <J1> Gateways.
Current Model Programmes (CMP)
Ownership of vehicle change has been passed to the operating plant. The Vehicle
Programme is in Production phase.
Post <J1> Gateway.

Types of AIM
There are 6 types of AIM that can be raised by the Originator:
Design
For example, issues relating to:

CoC Engineering or Vehicle Engineering,

Vehicle Packaging,
Plant Vehicle Teams (PVT),
PD Launch Team issue

Manufacturing
For example, issues relating to:

Manufacturing Engineering - Process, facilities, VCATS, Build Cards (AME/CME)

Plant Launch - Pre-production assembly issues - car not built to process

Stampings - Stamping feasibility, stamping facility and stamped parts quality issues

DMBI - Tolerance analysis issues

MP&L
For example, issues relating to:

Logistics,
Parts packaging,
Stillages,
Dunnage

PD Ops
For example, issues relating to:

Spec/Prod Info - BoM issues, configuration

Programme Management - Programme assumption issues, Spec mis-build or validation
issues. Purchasing issues

Supplier Parts Quality (SPQ)

For example, issues relating to current production car part quality issues - Plant Quality.
Supplier Technical Assistance (STA)
For example, issues relating to Pre-production car part quality issues.
AIM Response Types
When investigating AIMs, the Problem Solving Team needs a thorough understanding of the
problem itself to deliver Emergency, Interim and Permanent actions to resolve it. The following
actions and statements will allow a problem solving team to fully define and understand the issue.
Who is suffering and from what (the customer and the symptom)? - Emergency Response
Action (ERA)

Urgent response deployment to ensure the customer and business are protected and the
impact of the problem is contained. It is not always necessary to have an ERA nor is it
always possible to provide one
Need to know the symptom and a basic understanding of the impact of this symptom on
the customer and business
It is about the pace of a response, to understand the potential duration and magnitude of
the problem and isolate customer from the symptom.('What action/s will be carried out
immediately in the first 15 minutes of responding to the symptom?')

What is wrong with what and how much? - Interim Containment Action (ICA)
A Precise Problem Definition

An understanding of the problem is required - magnitude, severity, location, size of the

problem and any associated trend, pattern
A process / adjustment introduced to keep things moving, a temporary sticking plaster to
allow business to continueWorks against the problem symptoms and not the root cause

Root Cause Analysis & Escape Point Analysis - Permanent Corrective Action (PCA)
A thorough understanding of the Root Cause of the problem in conjunction with an Escape Point
Analysis - where in the process was the problem allowed to escape?
A PCA is the best available action that:

eliminates the Root Cause

removes the problem Symptom by removing the problem itself
closes or 'plugs' the Escape Point of a problem
Remove the ICA when testing and implementing the PCA

Prevent forever robust countermeasure and standard future detection event - Prevent
Recurrence Action (PRA)
For the PRA, we like to think in terms:

Prevent Recurrence Forever: update Standards, FMEAs, Design Changes and Compliance
Plans, etc. to ensure that this never happen again in the future of the company
Prevent Recurrence Replication: who else at Jaguar Land Rover is suffering same or
similar issues?Capture learning in corporate memory to prevent issue ever happening
again