Primary Menu

Navigation

Tag Archives | Change Management

Lean Tools and Technology in Lean Development

By on April 23, 2012 in General, Uncategorized

– Adapt technology to fit your People & Process; In some organisations it could be the opposite (Technology has to be mature first in accordance withTechnical Readiness Level process)

– Align organisation through simple visual communication More difficult for Engineering .

– Use powerful tools for standardization & organizational learning Lean organisation (reducing number of layers…)

at Toyota are the best exponents of Lean Development and since 1991 have identified 4 Critical Success Factors as follows:
  • Creating a strong vision to ensure that design engineers care about what the customer thinks of their future services and products
  • Limit the number of late design changes by striving for Perfect Drawings and Zero EC after production drawing release
  • Focus on precise and tightly scheduled industrialised drawing production to increase effectiveness
  • Focus on quality and cost of production itself to ensure build is with the cost bracket
0

Lean Product Development

By on April 19, 2012 in Information Technology, Lean Six Sigma, Uncategorized

People & Partners

– Chief Engineer Role in Development phase (misunderstood in Aerospace Industry)

§ Highly experienced in Product development, small team, clear technical authority over all internal & external Eng’s, Voice of the Customer, guardian of the specifications, not a Programme Manager.  Unity of leadership
§ Decide Product & trade off between design/ Manufacturing/ Suppliers & Customer Support/ ILS so that product fulfils all requirements
§ Identify & remove Development roadblocks internal & partners/suppliers
§ Dev. schedule, product recurring costs, product reliability & op costs,

– Balance functional expertise & Programme integration

§ Programme Plateau (early concept phase & integration tasks) or Functional Plateau
(Detail design phase, cross programme optimization & learning, standardization, product/process skills)
–  Develop towering technical competence
§ Proactive hiring, early experience in other functions: Manufacturing, Customer and  Support/
§ Link to HR (Expert network, competence Mgt, specific technology dev. skills,  process)

–  Suppliers/Partners integration into Product Development

–  Build in learning & Continuous Improvement

§ Companys’ culture are mainly based on history & diff. functions (customer value,
multicultural…)

– Build a culture to support Excellence & Relentless Improvement

0

Lean Product Development Model

By on April 18, 2012 in General, Uncategorized

Lean Process principles

1 Focus on what the Customer Values Product (processes to assess Value vs Customer requirement, starting from clear definition of Customer requirements) Process (Plateau & Phases)

2 Front load Development & explore thoroughly alternative solutions (max. design space) Early Development phase (time allocation, budget allocation, expert teams {rotating}) Structure compliance with Quality gates don’t reopen previous decisions. Simulation more rigorous, modeling, verification of design robustness, design reviews {multi company & multi function}, trade off curves for design alternatives including risk & opportunity assessments

3 Leveled Product Development process flow VSM, 7 wastes, multi-programs resources (planning & Mgt integrated with scheduled milestones, top to bottom & across functional interdependences)

4 Rigorous standardization Design guidelines & standards Catalogues (standards owners) & supporting data, Experts network => transfer of knowledge, lessons learned => design standards… software modular components

0

Lean Production

By on April 16, 2012 in General, Lean Six Sigma, Uncategorized

Toyota is the most documented Lean Company, talking about Lean Production.

 

1991 – The machine that changed the world – This was the first time Toyota opened it’s doors to external consultants based on the TPS (Toyota Production System) developed by Womack and the Massachusetts Institute of Technology. “The 5 Steps to Lean” (specify value, identify the value stream, make the value flow, let the customer pull, pursue perfection) were defined in this book.

1996 – Lean Thinking (Womack and Jones) – Easier to read, still based on TPS (Manu) with Case Studies

1997 – Concurrent Engineering Effectiveness – Jeff Liker and based on some of Toyota’s Engineering Principles

2002 – Lean Enterprise Value  –

2004 – The Toyota Way – Jeff Liker – Business Philosophy and 14 Management Principles

2006 – The Toyota Product Development System – Jeff Liker – based on the product development system not manufacturing. The product development system is the key behind the TPS and this is the first book that explores Toyota’s PDS and this is their main competitive advantage. Easier to replicate the TPS than the PDS. 13 Principles broken down, easy to read and you can dip in and out of the book.

2007 – Toyota Talent –  Jeff Liker – How to develop engineers

2007 – The Lean Product Development Guidebook –

 

0

Lean Engineering in Lean Six Sigma

By on April 12, 2012 in Information Technology, Lean Six Sigma, Uncategorized
– Manufacturing has a relatively small influence on the overall cost and quality of the product or service supplied.  Remember the Value Stream?
– When Lean principles are applied across all the functions in the value stream,   true competitive advantage can be gained. This is sometimes known as Lean Enterprise
– Lean Product Development demands an integrated multi-disciplined approach.

A Lean product development process typically has four phases:

    1. Concept  The Vision for the product produced by the programme lead   who is a technical expert  and is responsible for the product   from concept to market
    2. System design   Set based concurrent engineering looks for all possible    problems and tries to resolve them early in the process. ‘Sets’   of possible solutions are generated (diverge) then gradually   narrow as learning and understanding increases i.e. design   converges. Progressively reducing specifications and   resolving ambiguity actually shortens development time.   The system design team will be multi-functional and often   located together.
    3. Detailed design.
    4. Proto type & tooling.

 

0

Lean Engineering

By on April 12, 2012 in Information Technology, Lean Six Sigma, Uncategorized

Manufacturing has a relatively small influence on the overall cost and quality of the product or service supplied.

Remember the Value Stream?

When Lean principles are applied across all the functions in the value stream, true competitive advantage can be gained.

This is sometimes known as Lean Enterprise Lean Product Development demands an integrated multi-disciplined approach.

0

Lean Engineering in Lean Six Sigma

By on April 8, 2012 in Information Technology, Lean Six Sigma, Uncategorized

Lean Six Sigma challenges for Service and Product Development are

  • Short life cycles for service offerings, products and technologies
  • Integrated development and quality approach with suppliers
  • Customer expectations becoming more demanding
  • Technology (hard/software) becoming increasingly complex
  • Extremely high requirements for service and manufacturability
  • High impact of poor OTOQOC performance on confidence
  • High costs of development of complex services and products
  • High cost of post design changes, amendments & failures

Short life cycles for both products and technologies.

[Comment: This requires dynamic changes in product designs be managed at the sub-assembly level and coordinated across product lines to gain the most synergy for our development efforts.]

Customers have rising expectations for quality of total service [Comment: Customers don’t care if the problem is a handset or service provider.]

Increasing number of product development projects.

[Comment: Nokia has chosen to compete in all technology areas.  Since technology has not yet consolidated around one or two standards, we face the need to innovate and refresh all product lines on a regular basis.  Most of our competitors are not attempting this same approach.]

Products must be capable of manufacture in the millions.

[Comment: Mistakes cannot be made in production, right the first time is essential or we will not effectively compete in this business.]

Reliance on component parts quality from suppliers.

[Comment: We do not control our own destiny for quality but must seek exceptional partners who can contribute to our overall effort on behalf of our customers.]

Software is complex and interoperability is essential & interoperability is essential.

[Comment: Again, “right the first time” is the rule for software as well as hardware.  We also rely heavily on standards and industry partnerships to assure that we maintain seamless integration between hardware manufacturers and service providers.]

 

 

0

Lean Six Sigma is applicable outside volume manufacturing

By on April 7, 2012 in Information Technology, Lean Six Sigma, Uncategorized
Volume manufacturing (automobiles) is where Lean thinking and tools were developed.
We use a volume manufacturing exercise (VSM)  to learn the techniques – we can visualise ‘things’ easier.
But Lean is not a ‘manufacturing’ concept, it is a volume concept.
Wherever you have volume you have processes which are dynamic.
Lean is being applied outside manufacturing; the potential is huge since for an advanced industrial economy:-
–80% non-manufacturing
–and of the 20% that is manufacturing, only 20% of that has prices driven by direct manufacturing labour.
0

Lean Six Sigma with Poka Yoke

By on April 6, 2012 in Lean Six Sigma, Uncategorized

‘Poka Yoke’ is a technique for eliminating errors, used by Black Belts for solution generation and preparing implementation;

such that it is …Impossible to make mistakes, …Inexpensive, …Very effective, …Based on simplicity and ingenuity.

“poka” means an inadvertent mistake, “yoke” means to prevent, it originates by mr. Shigeo Shingo (1909-1990) in Japan.

Error proofing is a very simple technique.

You should keep it in mind at all times, but particularly when you are designing the solution or the improvement

Ideally you should prevent all possibility of the problem occurring, elmination;

If you can’t do this, you should then try to

  • flag (identify quickly, every time the problem occurs),
  • facilitate (make it difficult to create the problem)
  • mitigate (reduce the effects when the problem does occur)

…in that order!

0

Lean Six Sigma Value Stream Mapping

By on April 3, 2012 in Information Technology, Lean Six Sigma, Uncategorized
During the Lean Six Sigma projects the Black Belts we learn them mapping a value stream, using symbols we understand, we have identified ways to reduce Lead time.
This means that the time spent on value add activities as a % of total time spent is increased,
But we haven’t changed any of the value add activities. We haven’t bought new high tech expensive equipment or tried to get people to work harder, we have simply improved the system.
We haven’t calculated benefits but you get the  feeling that the ‘future state’ system will perform better for OTOQD and cost.
We used a volume manufacturing example because it’s easier to visualise value streams with physical things; now let’s look at non-manufacturing.
0