AL Problem Solving Process Manual - Updated 10 - May 2016
AL Problem Solving Process Manual - Updated 10 - May 2016
AL Problem Solving Process Manual - Updated 10 - May 2016
Issue No: 3
Page: 1 of 72
Its inherent strength rests with its clear demarcation for selection of methodology
for various complexity levels of problems, right from simple to complex, studied along with
its impact to the organization. This is achieved by involving various stakeholders across the
organization & beyond to improve quality, productivity, safety, service levels, efficiency,
morale, reduce cost, lead time with positive impact on environment. It emphasizes on a
systematic project management approach with the top leadership drive.
Issue No: 3
Page: 2 of 72
INDEX
Issue No: 3
Page : 04 of 72
As per the description & methodology, selection matrix given below, refer fig 1.1 & 1.2
Problem solving methodology has been classified into the given four approaches based on
the nature of problem to be solved. Details are given below.
Just Do It (JDI): To address ‘surface level’ problems within the process owner’s span of
control which are basic, small & easy to solve, where root cause/s & solution/s are both
known.
Keiken, Kan, Dokyo (KKD): To address, next higher level of complexity issues compared to
JDI, which are small & easy within process owner’s span of control where the root cause/s
are known, but solution/s are not sure, and hence have to be identified & verified. It is
carried out with a 4 step systematic approach.
Basic Problem Solving (BPS): To address next higher lever of complexity issues compared to
KKD. Seven step PS approach will be used and normally Seven QC tools required to verify
the Root Cause among the known potential Causes.
Advanced Problem Solving (APS): To address next higher lever of complexity issues
compared to BPS with significant impact at a plant function / corporate function level. Seven
step PS approach will be used and normally Statistical tools required to verify the Root
Cause among the known potential Causes.
Deep Dive Projects: To address higher complexity problems with significant impact at
organizational/business/SBU/customer level (multi plant/location/function level). It will also
be Seven step PS approach with Usage of Statistical tools to identify Root Causes. This will
also require higher stake holder involvement due to large scope of Problem.
Procedure No (as per TS) : CQ/LSS/001/V2
Issue No: 3
Page : 05 of 72
AL-PS can be explained by the analogy of an ‘apple tree’ as given in figure 1.1 below, where
the height of the tree can be understood as the ‘complexity’ of the problem, and the apples
at various heights denotes the ‘opportunity’ available. The approaches alongside describes
the ‘vehicle or the effort’ required to tap those opportunities from the ground level.
Fig 1.1
Fig 1.2 explains the classification of the problems/opportunities for improvement under four
categories (JDI, KKD, BPS, APS, DD) based on Impact and Complexity.
Fig 1.2
Procedure No (as per TS): CQ/LSS/001/V2
Issue No: 3
Page: 06 of 72
Seven steps of Problem Solving (BPS, APS, Deep Dive): Any problem, which uses APS, BPS &
Deep Dive methodology will follow the below seven steps. This will ensure Standardization
and effectiveness in problem solving. Deliverables of Seven Steps are explained as follows.
Stakeholders Involved: LSS BB, HODs, Sponsors, Plant/Function Head, LSS MBB
2. Problem Identification & Classification (ALPS)
Procedure No (as per TS) : CQ/LSS/002/V2
Issue No: 3
Page : 08 of 72
Objective: To identify the key impact projects based on Voice of Customer (VOC)/Voice of
Business (VOB) and selection of right problem solving approach to resolve identified
problems to meet Business Goals.
Process Flow:
Start
Impact > 0
Complexity < 20
Rate &
Scrutinize To be taken as
through 2 X 2 JDI or KKD Project
PS matrix
B A
Procedure No (as per TS) : CQ/LSS/002/V2
Issue No: 3
Page : 09 of 72
B A
Impact > 0
Complexity > 20 <= 40
Impact > 0
Complexity > 40
80
Impact > 40
Complexity > 40
To be taken up
Revisit scope
as APS Project To be taken up as
Deep dive Project
End
Criteria for identification: The 2X2 project selection filter consists of two criteria of Impact &
complexity, which are drilled down to several dimensions each with certain weightage to all.
The user is expected to fill the rating column based on the current level of understanding
about the problem with rating to be done as per the rating scale given below without
omitting any column. Refer fig 2.1, 2.2, 2.3 for the templates & refer annexure 1.
1. 1 – Low
2. 3 - Medium
3. 9 - High
Procedure No (as per TS) : CQ/LSS/002/V2
Issue No: 3
Page : 10 of 72
Degree of process
C4 15 3 Manual Semi or Partially mechanized Fully mechanized
mechanization
Policy management at
Daily work Policy management at
C6 Source of the project 25 1 Function or Plant or
management Department level
Corporate level
Complexity Score 38%
I4 Gap between target and actual 20 3 Less than 25% Between 25% to 50% Greater than 50%
Fig 2.1
Procedure No (as per TS) : CQ/LSS/002/V2
Issue No: 3
Page : 11 of 72
Fig 2.2
Procedure No (as per TS) : CQ/LSS/002/V2
Issue No: 3
Page : 12 of 72
Just Do It (JDI) approach: To address ‘surface level’ problems within the process owner’s
span of control which are basic, small, easy, quick to solve, where root cause/s & solution/s
are both known.
Problems can be identified from Gemba observations, DWM which can be completed
without formal budget, does not create a known risk to the business/customer, and if it fails
can easily be reversed. Scope is confined to single or set of actions with less complexity.
Although formal training & CFT are not mandatory, the process owner can use basic tools
such as process mapping to understand process, along with sound process knowledge to
complete the process improvement. Projects can be registered after successful completion
of the actions & achieving desired result.
Keiken, Kan, Dokyo (KKD) approach: To address next higher level of complexity issues
compared to JDI, which are small, easy, quick to solve within process owner’s span of
control where the root cause/s are known, but solution/s are not sure, hence may require
moderate level of analysis for the best solution identification.
Problems can be identified from Gemba observations, DWM. The knowledge may be own or
sought from experts. Although formal training & CFT is not mandatory, the process owner
and manager utilize basic tools such as process flow diagram etc, along with sound process
knowledge, collective experience, wisdom, intuition, guts to make the improvement. Scope
of the project is confined to set of actions.
7 QC tools can be used to understand process behavior, not mandatory. It is carried out with
a 4 step systematic approach.
Procedure No (as per TS) : CQ/LSS/002/V2
Issue No: 3
Page : 13 of 72
1. To reduce tool cost by changing the insert for grinding operation based on past
successful trials in similar product segment/category in other plants;
2. To reduce power consumption by removing the interface between the main & auxiliary
systems in machines;
3. To reduce consumable consumption by salvaging through filters to separate the oil from
the burr in shop floor.
Basic Problem Solving (BPS) approach: Problems identified from Gemba observations,
DWM, PM (occasionally) from a process, scope within span of control of project leader,
done along with CFT with moderate level of data collection & analysis. Scope could be
confined to one operation/one machine with higher level of complexity compared to KKD.
Prior project registration is compulsory. Root cause and solutions identified through
structured and systematic data collection, application of basic QC tools for analysis decision
making with a CFT & time bound approach with significant function/plant level impact.
The project may need investment for improvements depending on the analysis and can be
validated quickly within short time period. Formal full time training(two days) include,
problem solving process overview along with Q7 and other basic problem solving tools &
application with emphasis during the project on observation at Gemba or at the point of
failure, data collection and analysis, close monitoring. Team constitutes a leader who has
been formally trained, along with 2-4 other CFT members depending on the requirement.
1. To reduce rework in Journal grinding operation from 500 to 100 PPM in Cam shaft line;
2. To reduce tie member mounting hole offset ppm in from 15000 to 5000 PPM in Lynx;
3. To reduce rework in Block Rough Machining line due to 250 angular drill breakage issue
from 5000 to 2000 ppm.
Procedure No (as per TS) : CQ/LSS/002/V2
Issue No: 3
Page : 14 of 72
Advanced Problem Solving (APS) approach: Problems identified from DWM, PM, KRA Gaps,
Internal customer complaints, Field issues, Warranty failures which requires higher
statistical tools for data analysis. Formal training program(6 days) include problem solving
process overview with other basic & advanced problem solving tools & application with
emphasis on observation at Gemba or at the point of failure along with data collection &
statistical analysis. Team constitutes a leader who has been formally trained, along with 4-6
other CFT members depending on the requirement.
The project can be with investment depending on the requirement, and can be validated
within a reasonable time period. Prior project registration is compulsory. Root cause and
Solutions identified through structured and systematic data collection, application of
statistical tools for analysis, wherever required advanced statistical tools for decision making
with a CFT & time bound approach. Scope could be confined to multiple processes within a
plant/function with significant plant/corporate function level impact
Problems identified from PM, KRA Gaps, Customer complaints, Field issues, Warranty
failures with extensive field investigation & analysis involving multiple stakeholders. Formal
training of approx. 10 days, include advanced statistical problem solving tools & application
with emphasis on observation at Gemba or at the point of failure along with data collection
& advanced statistical analysis. Team constitutes a leader who has been formally trained,
along with 6-8 other CFT members depending on the requirement.
Prior project registration is compulsory. Root cause and Solutions identified through
structured and systematic data collection, application of statistical tools for analysis,
wherever required advanced statistical tools for decision making with a CFT & time bound
Procedure No (as per TS) : CQ/LSS/002/V2
Issue No: 3
Page : 15 of 72
approach. Scope could be confined to multiple processes, multiple locations & stakeholders
with significant organizational impact. The project may need investment for improvements
depending on the analysis, and can be validated within a considerable time period.
1. To eliminate Synchro ring failures in Gear Box in all Boss & Ecomet models;
2. To reduce FPV due to clutch failures in all Goods & Passenger models.
Process Responsibility: HOD, Sponsor, Project leader, LSS BB, LSS MBB
Process deliverable:
Issue No: 3
Page : 18 of 72
Objective: To provide appropriate problem solving training to management staff as per the
standard ALPS problem solving curriculum designed by AL Central quality team depending
on business needs
Process Flow: As described below for BPS, APS, Deep dive projects Fig 3.1, JDI/KKD project
identification is in Fig 3.2, Champions Training Fig 3.3, Refresher capsule training Fig 3.4,
refer annexure 2 for training preparation checklist
Start
Project identification
by Sponsor/HOD
C
Procedure No (as per TS) : CQ/LSS/003/V2
Issue No: 3
Page : 19 of 72
End
Fig 3.1
Procedure No (as per TS) : CQ/LSS/003/V2
Issue No: 3
Page : 20 of 72
Start
Gemba visit/Issues
highlighted by Customers
End
Fig 3.2
Procedure No (as per TS) : CQ/LSS/003/V2
Issue No: 3
Page : 21 of 72
Start
End
Fig 3.3
Procedure No (as per TS) : CQ/LSS/003/V2
Issue No: 3
Page : 22 of 72
Start
End
Fig 3.4
Process Responsibility: Plant Function or Corporate Function Head, Head - HR, LSS BB, LSS
MBB
Stakeholders Involved: Sponsors, HODs, Plant Head / Corporate Function Head, Head – HR,
LSS BB, Project Leaders, MBB & Head - LSS
Process deliverable:
Issue No: 3
Page : 24 of 72
Objective: To register the Problem Solving projects with a unique project identification
number in the PS project bucket for reviewing, monitoring & support
Process Flow: As described below, for BPS, APS, Deep Dive ref fig 4.1, for JDI / KKD refer fig
4.2
Start
End
Fig 4.1
Procedure No (as per TS) : CQ/LSS/004/V2
Issue No: 3
Page : 25 of 72
Start
End
Fig 4.2
Examples:
Issue No: 3
Page : 26 of 72
Stakeholders Involved: Sponsors, HODs, Plant Head, Black Belt, Project Leaders, MBB,
External Consultant
Process Deliverable:
Issue No: 3
Page : 28 of 72
Process Flow: As described below for BPS, APS in Fig 5.1, for Deep Dive in Fig 5.2
Start
Project
Project review Project support
review by LSS
by LSS BB with taken with CFT, BB, BB with
Sponsor/HOD Sponsor, HOD Sponsor/HOD
Cannot
be
Progress as per Plan revived
Can be revived
Project
short
Refinements required
closure
Project review
by LSS MBB /
PH
No refinement required
End
E
Procedure No (as per TS) : CQ/LSS/005/V2
Issue No: 3
Page : 29 of 72
End
Fig 5.1
Procedure No (as per TS) : CQ/LSS/005/V2
Issue No: 3
Page : 30 of 72
Start
Project
Project review Project support
review by LSS
by LSS BB with taken with CFT, BB, BB with
Sponsor Sponsor, HOD Sponsor
Cannot
be
Progress as per Plan revived
Can be revived
Project
short
Refinements required
closure
Project review by
LSS MBB ,Vertical
Head & CQ Head
No refinement required
End
Project closed
Fig 5.2
Procedure No (as per TS) : CQ/LSS/005/V2
Issue No: 3
Page : 31 of 72
Project Duration standard: Within 3 months from Project Start Date (PSD) for BPS projects,
Within 6 Months from PSD for APS/BB/Deep Dive Projects. Process Review Timelines:
Who / Review
Role
Reviewer Frequency
Review project progress w.r.t plan, conducts project
Atleast
LSS BB tollgate reviews, checks for correct application of 7 step
Fortnightly
PS methodology & complex statistical tools
Review project trend, technical direction & support
Atleast
Sponsor requirements for carrying out improvements to meet
Fortnightly
project charter target
Steers PS journey in the organization, build BB capability
Interim review and approves project for closure during Atleast
MBB
closure review, validates correct application of seven Monthly
step PS methodology & complex statistical tools
Reviews with BB for the overall status of PS deployment,
HOD/PH/Top reviews individual projects on need basis, Intervenes Atleast
Management wherever required, Reward & Recognize outstanding Monthly
project work
Tollgate Reviews:
Stakeholders Involved: Sponsors, HODs, Plant Head, LSS BB, Project Leaders & LSS MBB.
Process Deliverable:
Issue No: 3
Page : 33 of 72
Objective: To get PS project financial savings vetted by Finance to enable authorization for
formal project closure & declaration to the top management
Process Flow: As described below for JDI, KKD, BPS, APS, Deep Dive in Fig 6.1
Start
by Finance
executive
No refinement required
Authorization
review by
Head - Finance
F
Procedure No (as per TS) : CQ/LSS/006/V2
Issue No: 3
Page : 34 of 72
End
Fig 6.1
Issue No: 3
Page : 35 of 72
Stakeholders Involved: Sponsors, Plant Head, Black Belt, Project Leaders, MBB, Financial
Controller, HODs, Steering committee, VP, Head CQ, President – Operations.
Process Deliverable:
Issue No: 3
Page : 37 of 72
Objective: To ensure that the closure requirements of the PS project is met as per the ALPS
closure standards
In Scope: Applicable to all executives undergoing BPS, APS, Deep Dive projects
Start
G H
Procedure No (as per TS): CQ/LSS/007/V2
Issue No: 3
Page : 38 of 72
G H
No refinement required
No refinement required
End
Fig 7.1
Issue No: 3
Page : 39 of 72
Stakeholders Involved: Sponsors, HODs, Plant Head, Black Belt, Project Leaders, MBB,
Vertical Head, CQ Head.
Process Deliverable:
Issue No: 3
Page : 41 of 72
In scope: Applicable to all PS trained executives who have completed BPS, APS & Deep Dive
projects
Process Flow: As described below for BPS, APS & Deep Dive training completion in Fig 8.1,
APS & Deep Dive Certification in Fig 8.2
Start
End
Fig 8.1
Procedure No (as per TS) : CQ/LSS/008/V2
Issue No: 3
Page : 42 of 72
Start
Unsuccessful
Conduct of
Mentoring to
Written Exam
candidates
by ALCQ
Successful
End
Fig 8.2
Project Closure norms:
Issue No: 3
Page : 43 of 72
BPS Program :
`
Procedure No (as per TS) : CQ/LSS/008/V2
Issue No: 3
Page : 44 of 72
Issue No: 3
Page : 45 of 72
http://alportal/sites/AL/Document%20Library/1/CORPORATE/GB%20Certification%20Process.pdf
Process Responsibility: BB
Stakeholders Involved: Sponsors, HODs, Plant Head, BB, Project Leaders, MBB, Top
Management
Process Deliverable:
Issue No: 3
Page : 47 of 72
Objective: To submit PS MIS reports (Plan Vs Actuals) to management for information &
necessary action wherever required as per management guidelines
MIS Reports:
Start
End
Process Ownership: BB for BPS, APS, Deep Dive projects, CQ TQM for JDI and KKD
Stakeholders Involved: BB, Coordinator, HODs, Sponsors, PH, MBB, Top management,
Process deliverable :
Issue No: 3
Page : 49 of 72
Objective: To check the sustenance status of completed projects for specific time period and
report to management
In scope: Applicable to all closed BPS, APS & Deep dive projects
Frequency: Quarterly
1. Closed BPS Projects for subsequent 6 months from project closure month
2. Closed APS, Deep dive projects for subsequent 12 months from project closure
month
Start
I
Procedure No (as per TS) : CQ/LSS/010/V2
Issue No: 3
Page : 50 of 72
Not sustained
Conduct
of Audits
Cases reported to BB
Sustained
Consolidated MIS to PH
End
Fig 10.1
Stakeholders Involved: Sponsors, HODs, Plant Head, BB, MBB, Top management
Process deliverable:
Issue No: 3
Page : 52 of 72
Objective: To reward & recognize the effort of teams/ individuals for outstanding LSS/PS
project work completion and to further spread the culture of excellence
Scope: Applicable to all executives for closed BPS, APS & Deep Dive projects as per the
specified time period of the competition
Details & Categories of competition : Leadership Excellence Awards for Problem Solving
(LEAPS)
Issue No: 3
Page : 53 of 72
Start
Meeting norms
Meeting norms
J
Procedure No (as per TS) : CQ/LSS/011/V2
Issue No: 3
Page : 54 of 72
End
Stakeholders Involved: Sponsors, Plant Head, BB, Project Leaders, MBB, HODs, other
invitees, Top Management
Process Deliverable:
Issue No: 3
Page : 56 of 72
Objective: To provide clarity to all stake holders involved in Problem Solving deployment in
plant or function
Plant Function/
Corporate Function
Champion
Master Black
HODs Finance Head
Belt
Project Leaders
Project CFT
members
PS Deployment Stakeholders:
Issue No: 3
Page : 57 of 72
3. Project Sponsor:
Issue No: 3
Page : 58 of 72
5. Plant Champion:
Issue No: 3
Page : 59 of 72
a. Track the overall PS objectives of the plant and report to the management
periodically;
b. Monthly MIS reporting of all PS projects to MBB, PH, Sponsors, with the overall big
picture of PS deployment in the plant/function;
c. Act as an enabler for the business by identification of right PS projects to achieve
plant/function business goals;
d. Enable project selection discussions with steering committee, sponsors & PH, to
ensure the right key pain areas are selected as PS projects;
e. Initiate & enable interim and closure project reviews with Sponsor, PH, MBB
periodically to achieve the project closure & savings target;
f. Conduct PS trainings for creation of new belts & refresher trainings periodically to
sustain the PS momentum in the plant/function;
g. Support project leaders with the deployment of relevant PS tools for the project to
enable achieve the desired objectives;
h. Spearhead & drive important PS events & competitions in the plant/function;
highlight, reward & recognize key PS achievement in the plant;
i. Communicate and share success stories of key PS project achievements & closures
with all stakeholders to continually improve the motivation & ownership levels.
7. Steering Committee:
Issue No: 3
Page : 60 of 72
8. Financial Controller:
a. Approve the pre-project financial savings during the Problem Identification phase of
the PS project;
b. Review financial benefits & validate savings of the PS project as part of control
phase;
c. Scrutinize & provide on time financial approvals related to overall new investment as
part of the project, project trials, Reward & Recognition schemes related to ensure
steady progress in the overall PS deployment in the plant/function.
Issue No: 3
Page : 62 of 72
Acronyms Used
No Acronym Expansion
1 AGM Assistant General Manager
2 AL Ashok Leyland
3 APS Advanced Problem Solving
4 BB Black Belt
5 BPS Basic Problem Solving
6 CFO Chief Financial Officer
7 CFT Cross Functional Team
8 CP Corporate Plan
9 CQ Central Quality
10 DD Deep Dive
11 DGM Deputy General Manager
12 EMS Environment Management System
13 FH Functional Head
14 GB Green Belt
15 GM General Manager
16 HD Help Desk
17 HoD Head of Department
18 HR Human Resources
19 JDI Just Do It
20 KKD Keiken Kan Dokyo (Experience Intuition Guts)
21 LSS Lean Six Sigma
22 MBB Master Black Belt
23 MD Managing Director
24 MIS Management Information Systems
25 OSHAS Occupational Health and Safety Advisory Services
26 PH Plant Head
27 PMS Performance Management System
28 PPT Power Point presentation
29 PS Problem Solving
30 PSD Project Start Date
31 R&R Reward & Recognition
32 RYG Red Yellow Green
33 SVP Senior Vice President
34 TEI Total Employee Involvement
35 TQM Total Quality Management
36 TS Technical Specification
37 VP Vice President
Procedure No: -
Issue No: 3
Page : 63 of 72
APS/Deep Dive
4 4 32 4 67
Tollgate Review Checklist
5 3 27 5 68 JDI Template
6 3 37 6 69 KKD Template
7 6 40 7 70 BPS A3
8 6 40 8 71 APS A3
Issue No: 3
Page : 64 of 72
Annexure no 1
Selection grid - Problem solving methodology
Degree of process
C4 15 3 Manual Semi or Partially mechanized Fully mechanized
mechanization
Policy management at
Daily work Policy management at
C6 Source of the project 25 1 Function or Plant or
management Department level
Corporate level
Complexity Score 38%
I4 Gap between target and actual 20 3 Less than 25% Between 25% to 50% Greater than 50%
Issue No: 3
Page : 65 of 72
Time & Action calendar - PS GB Training Part 1 Ennore - 07th Jun to 09th Jun 2015 5-Jun-15
S.No Activity Responsibility Cut off RYG Status Deadline Actuals Remarks
1 APS big banner finalization Saravana 45 Completed 21-Apr 21-Apr -
2 APS small banner content finalization Saravana 45 Completed 21-Apr 21-Apr -
3 Banner ordering - Required nos Saravana 40 Completed 26-Apr 26-Apr -
Pre-Training -
4 Date finalization with Plant Head Raj 38 Completed 28-Apr 28-Apr -
5 Consultant availability - finalization Sachin 36 Completed 30-Apr 30-Apr -
6 Venue availability - finalization Saravana 34 Completed 2-May 2-May -
7 Mail from PH seeking projects & candidates nominations for LSS Training Raj 33 Completed 3-May 3-May -
8 Seek Travel plan from Hemant Sachin 32 Completed 4-May 4-May -
9 Mail to ALIMS for PC approval with Minitab 16.0 installation Saravana 28 Completed 8-May 8-May -
21 GB Training material part 1 & 2 ordering, as applicable Saravana 20 Completed 16-May 16-May -
22 Training kit transportation to ALCOB including catapult Sreedhar/Saravana 19 Completed 17-May 17-May -
23 Projects finalization with LSS Steering Committee Raj 18 Completed 18-May 18-May -
24 Participants finalization with Sponsors, Shop Heads Raj 18 Completed 18-May 18-May -
25 Projects finalization with PH Raj 17 Completed 19-May 19-May -
26 Project Charter readiness of all participants Raj 15 Completed 21-May 21-May -
27 Mail from PH to all GB's for GB Training Raj 14 Completed 22-May 22-May -
28 GB Material Collection from ALCOB (Cab booking to be done) Raj 14 NA 22-May 22-May -
29 Pre-Training session by BB to all participants, along with Training material distribution Raj 13 Completed 23-May 23-May -
30 GB Material distribution to all GB's Raj 13 NA 23-May 23-May -
31 Consultant interim/final closure review schedule - Tentative dates - mail circulation Raj 12 Completed 24-May 24-May -
32 Photo arrangement (Internal) Saravana 11 Completed 25-May 25-May -
33 Provide Minitab supporting files to helpdesk Saravana 10 Completed 26-May 26-May -
34 Mail to participants about training with dates, breaktimings emphasizing on shift planningRaj
accordingly 8 Completed 28-May 28-May -
35 Mail to GB's for Interim Review by Hemant Raj 7 Completed 29-May 29-May -
36 Training Conference room - IT Readiness (Projector+Minitab 16.0+Supporting files) Saravana 7 Completed 29-May 29-May -
a Projector
b Minitab
c Minitab supporting files
d LAN Connectivity
e Collar mike
c Uploading minitab supporting files in all the systems
37 Training Room Arrangement - Saravana 7 Completed 29-May 29-May -
a Check for room cleanliness - Estate maintenance
b Check for power junction box working - Electrical
c Check for A/c working- Electrical
f Check for room lighting- Electrical
g Check for boards - Office Service
h Drinking water bottles - Admin off boy
i Check for chairs condition- Office service
j Board marker pens - Office service
k Spare batteries - AA, AAA - Self
38 Seek Cab approval if required for things shifting from ALCOB Raj 6 NA 30-May 30-May -
39 Agenda finalization with timing, faculty details etc Raj 6 Completed 30-May 30-May -
40 Send mail to other plant BB's for Interim review slots Raj 6 Completed 30-May 30-May -
41 Training exercises finalization with Consultant Raj 5 Completed 31-May 31-May -
42 New Training exercises - Procurement (If any) Raj 4 Completed 1-Jun 1-Jun -
43 Quiz paper Part 1 - readiness Raj 4 Completed 1-Jun 1-Jun -
44 Agenda print outs for participants Raj 3 NA 2-Jun 2-Jun -
45 Check with hemant on the available time slots for interim review day wise Raj 3 Completed 2-Jun 2-Jun -
46 Training kit transportation to ENR including catapult Raj 2 NA 3-Jun 3-Jun -
47 Lunch, Snacks with Cups arrangement with Timing - Communication to Canteen, HR Saravana 2 Completed 3-Jun 3-Jun -
48 Communication to Security about the program Saravana 2 NA 3-Jun 3-Jun -
49 Mail to helpdesk for additional IT support on Day 1 Saravana 2 Completed 3-Jun 3-Jun -
50 Banner location - finalization Saravana 2 Completed 3-Jun 3-Jun -
51 Group photo location - Finalization Saravana 1 Completed 4-Jun 4-Jun -
52 Reminders to PH, Invitees - a day or two before training commencement Raj 1 Completed 4-Jun 4-Jun -
53 Reminders to canteen Saravana 1 Completed 4-Jun 4-Jun -
54 Reminders to participants Raj 1 Completed 4-Jun 4-Jun -
55 Attendance sheet - readiness Saravana 1 Completed 4-Jun 4-Jun -
56 Training accessories receipt & readiness at venue Saravana 0 Completed 5-Jun 5-Jun -
57 Day wise attendance circulation to Top management - Day 1 Raj 0 Completed 5-Jun 5-Jun -
58 Day wise attendance circulation to Top management - Day 2 Raj -1 6-Jun 6-Jun -
59 Day wise attendance circulation to Top management - Day 3 Raj -2 7-Jun 7-Jun -
60 Feedback form - readiness Raj -2 Completed 7-Jun 7-Jun -
Procedure No: -
Issue No: 3
Page : 66 of 72
# Check points
1 Project adequately defined and has strong linkage to the company improvement objectives and goals
2 Scope of the project is defined adequately. It is neither too big nor too small.
3 Project Charter - Measure(s) and benefits are quantified, Timelines clearly defined
4 Financial savings appropriate as per company guidelines for BB/GB
Targets are set with improvement of about 70% over current performance or adequate difficulty level but is
5
achievable or suitable benchmarking done to fix targets
6 Is the project approved by Sponsor and/or Champion, Financial controller as applicable?
7 CFT members are appropriate and committed for the time
8 Is the approved project charter shared with CFT and their reporting managers by Sponsor
Belt trained (or under training). He/she possess appropriate understanding of capability to understand the
9
process to be improved.
10 Field visit & CFT review plan completed
11 Voice of Customer collected
# Check points
1 Gemba visit & Problem redefinition completed
2 Process flow diagram are completed with Xs and Ys identified
3 Field visits & CFT reviews undertaken as per plan
4 Awareness creation initiatives undertaken
5 Check sheet completed
6 Baseline establised using control charts
Data collection plan for X's formulated / New data collection processes introduced / Automated (if past data
7
not available/reliable)
# Check points
1 Data collection & Stratification completed
2 CFT meetings as per plan
3 Fish bone / affinity / tree diagram / Why-Why analysis completed
4 The relationship of Xs and Ys is validated using QC tools
5 Root cause/s identified
6 Project metric trend is continuously monitored as per planned frequency
7 Project metric trend is shared with CFT regularly and updated in Gemba
# Check points
1 Solution Selection completed
2 Risk analysis completed
3 Cost/benefit analysis of optimal solution(s).
4 New and improved process ('should be') maps developed.
5 Small-scale pilot for proposed improvement(s).
6 Pilot data collected and analyzed suing Q7 tools - Before Vs After
7 Improved process ('should be') maps modified based on pilot data and analysis.
Solution implementation plan established, including schedule/work breakdown structure, resources, risk
8
management plan, cost/budget, and control plan. Contingency plan established.
9 CFT meetings as per plan
# Check points
1 Pareto - Before Vs After to be completed
2 Control charts - Before Vs After (full scale implementation)
3 Histogram - Before Vs After
4 CFT meetings as per plan
# Check points
1 SOP/WI completed
New process steps, standards, and documentation are integrated into quality, enviroment, safety system
2
documentation
Operating procedures are consistent. Knowledge gained on process is shared and institutionalized (hor
3
deployment).
4 Mistake proofing, automation as applicable completed
5 Response plans established, understood, and deployed.
6 Sustenance audit/monitoring plan - established
(Project Closure) Transfer ownership and knowledge to process owner and process team tasked with the
7
responsibilities.
# Check points
1 VOC - After improvement obtained
2 Sponsor/PH feedback obtained
3 Financial savings vetted
4 Way forward - Future improvement projects related to project scope/actions identified
5 Lessons learnt, Acknowledgements, Tools used - completed
6 One page Executive summary - completed
Procedure No: -
Issue No: 3
Page : 67 of 72
2 New process steps, standards, and documentation are integrated into quality, enviroment, safety system documentation.
3 Operating procedures are consistent. Knowledge gained on process is shared and institutionalized (horizontal deployment).
4 Mistake proofing, design change, automation as applicable completed.
5 Response plans established, understood, and deployed.
6 Sustenance audit/monitoring plan - established.
7 (Project Closure) Transfer ownership and knowledge to process owner and process team tasked with the responsibilities.
Issue No: 3
Page : 68 of 72
Issue No: 3
Page : 69 of 72
Issue No: 3
Page : 70 of 72
Annexure no 7 – BPS A3
AFTER EDM
RELEASED RELAY
SHAFT MTG HOLE
70% of overall frame assembly rework is contributed by hole off set issue in DIA INCREASED
cheetah models, while the remaining 30% contributed by other models FROM 35.0MM TO
39.5MM
2. Observation: Cause Validation(For critical causes):
1) Histogram - FSM Dimensions
6. Standardize:
Why-Why Analysis
Baseline:
Issue No: 3
Page : 71 of 72
Annexure no 8 – APS A3
KPOVs
KPIVs (Xs) C/U Process
(Ys)
MB drive Parameter
Carrier Frequency
Carrier
X1 C
Supply Frequency. Frequency SMPS Pareto Chart of the Standardized Effects
SMPS (response is SMPS Voltage, Alpha = 0.05)
Frequency Constant A B
C
Supply Fz
A cceleration
X3 Acceleration C B
Term
AC
Inference : 1200Ton press breakdown is the major contributor in B). Factory setting value of above parameter in the variable frequency drive.
month July-Aug'14 due to ADC (Auto Die Change) problem. S. NO. Parameter Current Value Min/Max Range C
B). Nos. of ADC occurs and nos. of ADC failed in month July-Aug'14
1 Carrier Frequency 3 KHz 1-15 (KHz) Inference:
0
A, B1& AC2are significant
3 4
after
Standardized Effect
5
reducing
6 7
the model.
observaed.
Date Nos. of ADC ADC Failed Date Nos. of ADC ADC Failed 2 Supply Frequency 40 Hz 0~400 Hz C). Main effect & Interaction plot found after DOE analysis.
8July'14 1 0 16Aug'14 3 1 3 Acceleration 5 Sec 0-6000 (Sec) Main Effects Plot for SMPS Voltage Interaction Plot for SMPS Voltage
12July'14 1 0 18Aug'14 2 0 Data Means Data Means
C). Analysis of variable data. Plotting of graph with different variables and Carrier Fz Supply Fz 30 40 1 5
15July'14 1 1 20Aug'14 2 2 23.96 24.0 Carrier Fz
regression analysis. 23.92 1
16July'14 1 0 22Aug'14 2 2 23.88 Carrier Fz
23.9
3
23.84 23.8
23.80 Carrier Fz
Mean
21July'14 1 0 26Aug'14 1 1 Multi-Vari Chart for SMPS VOLT by Carrier Fz. - Acceleration 1 3 30 40 24.0 Supply 1Fz
330
23.9
30 35 40 Acceleration Supply Fz 40
22July'14 2 1 27Aug'14 1 1 23.96 23.8
1 5 Car r ier Fz. 23.92
1 23.88
24.00
23July'14 2 1 2 23.84
3
23.80 Acceleration
23.95
1 5
28July'14 3 3
SMPS VOLT
23.90
2Aug'14 1 1 Nos of ADC failure
Inference: 1. Interaction plot between carrier frequency & acceleration having strong
23.85
B/d fz in % = ------------------------ X100 relationship.
23.80
6Aug'14 1 1 Nos. of ADC occurs 2. Carrier frequency & supply frequency are significant in main effect.
23.75
7Aug'14 1 1 D). Through the response optimizer we will found the best suited value for
= 54.8 % 23.70
11Aug'14 2 1 30 35 40
maximum of 24 VDC.
Supply Fz Optimal Carrier Supply F Accelera
13Aug'14 2 0 D High
Cur
3.0
[1.0]
40.0
[30.0]
5.0
[1.0]
Panel variable: Acceleration 1.0000 Low 1.0 30.0 1.0
14Aug'14 1 0
2. Observation: Composite
Desirability
1.0000
A). During the Auto Die Change, machine stopped and the reason
behind was fluctuation of Switched mode power supply (SMPS)
SMPS Vol
voltage. Ideally it should be 24VDC. During ADC SMPS voltage Maximum
y = 24.030
founded fluctuate upto 23.6VDC. d = 1.0000
Inference: Best suited value of Carrier fz, supply fz & acceleration are 1, 30
•Auto Di e Cha nge Stopped & 1 respectively for getting 24 VDC.
Why S. NO. Parameter Current value Modified Value
3 KHz 1 KHz
Inference : Analysis of regression equation shows that all the variable factors 1 Carrier Frequency
•PLC getti ng OFF/ON are significant for Switched mode power supply voltage.
Why 40 Hz 30 Hz
2 Supply Frequency
4. Action : 3 Acceleration 5 Sec 1 Sec
• Switched mode power
supply (SMPS) 24VDC 5. Check :
A). After the regression analysis found all 3 variables are significant. Then
Why getting fluctuate Variable frequency drive parameter modified and checked the SMPS Voltage
DOE (Design of experiment) result & response optimizer gives the better
during ADC.
output for making decision.
And Auto Die Change checked in Apr-May'15
B). Switched mode power supply (SMPS) voltage observation during
Histogram of SMPS VOLT
ADC. 23.9
25 24.1
Histogram of SMPS VOLT
23.9 20
25 24.1
Frequency
20 15
Frequency
15
10
10
5
5
0
0 23.9 24.0 24.1
23.6 23.7 23.8 23.9 24.0
SMPS VOLT SMPS VOLT
Inference: Switched mode power supply (SMPS) Voltage value found Inference :
significant low (upto 23.6VDC). 1. Switched mode power supply voltage increased from 23.6VDC to 24VDC.
C). Comparision of Switched mode power supply (SMPS) voltage during
Auto Die Change between others Press Machines. Pareto Chart of the Standardized Effects 2. Auto Die Change Breakdown failure % reduced from 54.8% to 0 %
(response is SMPS Voltage, Alpha = 0.05)
2.306 6. Standardization:
Factor Name
A A Carrier Fz
B Supply Fz 1. Variable frq. drive parameter modified & saved in electrial drawing.
B C A cceleration
2. Variable frq. drive mounting position shifted from its original position as a
AC
parmanent counter measure so that the effect of Moving bolster alternate
Term
AB
frequency drive magnetic field will not effect the Switched mode power
ABC supply voltage.
BC 7. Conclution :
C
1. Auto Die Change breakdown frequenc y reduc ed from 54 % to 0 %.
0 1 2 3 4 5 6 7
Standardized Effect 2. Suc c essfully adheranc e of c yc le time for ADC in press line.
Inference: Result shows difference among the SMPS Volt means of 3 3. Manual approac h eliminated for ADC.
Inference: We can omit BC, ABC & AB one by one as the P value above 0.05.
different presses machine are significant. 4. Oppurtinity cost saving of around Rs.-2,40,000 / Year.
Procedure No: -
Issue No: 3
Page : 72 of 72
Project Metric & UoM Project Baseline Project Target Achieved Description of Key improvement actions
Total
Expected date of
Hor.deployment description Completion status Pending Remarks (if any)
completion if pending
Project Leader sign with Sponsor sign with HOD sign with Checked by with Authorised by with
designation & date designation & date designation & date designation & date date, designation & seal
Thank You