"LEAN" thinking

"A systematic approach to identifying and eliminating the Eight Wastes (which are considered non - (customer) value adding activities) through continuous improvement by flowing the product at the 100% pull of the customer"

Eight Wastes:

Waiting:

• Description: There is a stoppage in the item/work within the process.
• Manufacturing samples: Instrument stoppage, bottlenecked tasks, apparatus substitution
• Office and Service examples: System interruptions, system reaction intervals, authorizations, data from clients

Defects:

• Meaning: Every type of scrap, faults, mistakes or rectification caused by improper completion of initial work.
• Manufacturing Instances: Construction of flawed pieces, leftovers or excess.
• Service/Office samples: Information input inaccuracies, scheme mistakes, work modification orders and bill miscalculations.

Unneeded Processing:

• Explanation: Wasting time on steps that are not required.
• Manufacturing samples: Incorporating superfluous phases to develop the parts, ineffective handling because of inadequate implements and product design.
• Service/Office illustrations: Re-entering information, unneeded reproductions, needless or unwarranted reports.

Inventory:

• Meaning: All items that are in surplus, all methods of batch processing. Manufacturing beyond what client require.
• Manufacturing samples: All extra inventory, group handling.
• Service/Office instances: Office materials, marketing brochures, batch processing transactions.

Excessive Motion:

• Description: Movement of individuals.
• Manufacturing illustrations: Reaching for, searching for, or piling parts, tools, etc.
• Service/Office examples: Traveling to/from photocopier, central filing, fax machine or other offices.

Transportation:

• Explanation: Shifting of work or correspondence from one phase to the next phase in the procedure.
• Manufacturing samples: Transfer supplies, pieces, or completed merchandise into and out of storage.
• Service/Office instances: Shifting of paperwork from location to location, room to room or folder to folder.

Overproduction:

• Description: Creating extra, earlier, or quicker than is needed by the subsequent individual.
• Manufacturing examples: Merchandise piling up at a sluggish downstream pace.
• Service/Office instances: Laser printing correspondence earlier than it is actually required, buying pieces earlier than they are wanted, providing paperwork earlier than required by the subsequent individual.

Underutilized Employees:

• Explanation: Workers' inventiveness, concepts, and aptitudes are not entirely employed.
• Manufacturing instances: Overlooking concepts, talents, and enhancements by not pay attention to personnel.
• Service/Office examples: Restricted worker power and accountability for rudimentary jobs, management command and control

PLM Best Practices

PLM Best Practices

Below are some best practice guidelines that may ease the implementation process, getting your PLM system up and running faster and easier.

• Develop iteratively 
  Although it is always best to know all the requirements in advance, this is often an unrealistic goal. Therefore, do not spend an inordinate amount of time upfront on requirements and design without user validation.
• Manage Requirements 
  Always keep in mind the requirements set by the users.
• Model Visually 
  Utilize diagrams and mock ups as models. Create visual prototypes and get user validation before developing any method code. Don't spend a significant amount of time developing specs without prototyping the solution.
• Use Components
  Breaking down large projects into manageable pieces. Look for "Small Wins" that provide business value.
• Verify Quality 
  Always make testing a major component of the project.
• Control Change 
  Ensure that changes are synchronized and verified constantly.
• Divide Implementation into Phases
  Create phases that provide business values and can be deployed independently. Build a plan for each of these phases that includes goals and be sure to give priority to important or high risk items.
• Use References 
  
• Use Cases as a Foundation 
  You will most likely write two types of use cases: High Level and Detailed. These Use Cases are a foundation for documentation, training material, and test plans.

Project Manager

A project manager is a professional in the field of project management. Project managers can have the responsibility of the planning, execution and closing of any project, typically relating to construction industry, architecture, aerospace and defense, computer networking, telecommunications or software development.

1.     Focus on customer needs

The single biggest success factor for a project is whether it delivers what the customers really need. Not only will that create a happy customer, it will also dramatically increase your success as a project manager. The tricky part is that customer needs aren’t necessarily synonymous with what the customers say they want. Outstanding project managers focus on the customer’s real needs and seek to uncover the reasons behind the requirements. They do that through enquiry and by consistently learning about the client’s business.

2.     Keep your promises

As a project manager is it absolutely essential that what you say and do is credible and that your clients and stakeholders trust you. When you take on an action or commit to a deadline – however big or small – always deliver it when you said you would. This is also true when it comes to chasing other people for the actions they take on. You will gain an enormous amount of respect for being effective, timely and reliable and it will be easier for you to plan and execute the project with minimal resistance. Set a good example in everything that you do.

3.     Be proactive

They key to success for any manager and leader is to be proactive and consistently focus your efforts and attention on the long-term as opposed to being reactive in the present moment. Too often we get caught up in urgent or unimportant activities and we procrastinate on the big important things such as planning and initiating the project properly, writing the business case, learning about our client’s business or taking the time to build strong relationships with our customers and team members. Don’t sit back and wait for things to happen. Take the initiative as a matter of course.

4.     Support your team

Your team is the project’s biggest asset so nurture it and enable each individual team member to thrive. Allow for people’s individuality, play to their strengths and give them the support they need to succeed. To build a great team, spend one-on-one time with people on a weekly basis. Ask them what you can do to help, what they worry about and how you can assist them in working more effectively. Never be afraid to ask questions and to lend a helping hand. One of your most important roles is to remove blockages so that your team can get on with its work.

5.     Delegate

If you are to add maximum value, you must learn to delegate. This will help you create space to concentrate on the big picture and on the strategic aspects of the project. Tracking timesheets, taking minutes and planning detailed work-streams are important aspects of a project, but it’s not important that you do them. Get a project administrator on board or train your senior team leads to take on a more senior role. Not only do you develop their skill set, you also free yourself up to focus on customer relationships, communication, team building and setting the vision.

6.     Challenge the status quo

It is no longer enough to turn up for work and deliver a project the way we used to. The global crisis has meant that everything is being scrutinized and that executives are constantly on the look-out for how we can deliver change in a better, cheaper and faster way. You need to challenge the status quo on a daily basis and help identify how the team can work smarter, what new technologies you can employ, which extra benefits you can deliver and how project processes can be improved.

7.     Stay calm under pressure

As a project manager you are under daily pressure to deliver, make decisions and sort out issues. You need set a great example by managing your state of mind and remaining calm when the pressure is on. Maintain a balanced perspective and think of solutions rather than placing blame or making knee-jerk decisions. In situations of conflict, take on the role of a mediator and convey both sides of the argument. Whatever you do, do it well; as the way you conduct yourself is the most you can ever expect from your team

CLASS : Credibility- Listening- Accountability- Style-Sell

PRE-SALES BRINGS CLASS TO THE SALES PROCESS

Great statement on the value of Pre-Sales in the selling process... The PreSales professional has been affectionately called “Doctor Demo” or “Demo Monkey”. The PreSales job title varies from company to company. From Sales Engineer to Solution Consultant... no matter what a PreSalesRep is called, they should consistently bring CLASS to the sales process.

In this case,
CLASS is more than an elegance of style, taste, and manner. CLASS is an acronym that stands for qualities and characteristics found in top PreSales professionals. The CLASS acronymn has been developed over several years of serving as a PreSales representative in addition to building several PreSales organizations. It is a simple way of describing the essence of a quality PreSales team member wherein each letter in the word CLASS stands for a desirable characteristic:

C - The “C” stands for Credibility. No doubt the PreSalesRep (PSR) represents their company’s products and/or services with greater depth and breadth than any other person on the sales team. Credibility is established with the prospect through the knowledge of products and solution opportunities offered by the PSR. The credibility the PSR builds allows them to have a relationship with the functional and technical interest parties of the potential customer. When a PSR establishes their credibility, additional benefits result... such as Confidence with Commitment to do what it takes to make the sale.

L - The “L” stands for Listener. A PSR may seem credible with lots of product and/or technical knowledge... but if he or she does not listen to the customer, the sale is less likely to be successful. A good PSR listens to the desires of the prospect and does an effective job of relating that information to the rest of the sales team. Listening is also crucial in the relationship between the Lead Sales Rep and the PSR, in order that the team functions effectively.

A - The “A” represents Accountability. Being accountable to both the sales team and prospect means doing what it takes to get answers when an important question arises about product functionality, technical capabilities, or service commitments. An effective PSR must be willing to diligently research the answers to questions. Providing well-researched, accurate answers trumps a spur-of-the-moment educated guess every time. It takes a team Attitude to win business; the PSR who proves his or her accountability to the team is truly an asset.

S - The “S” indicates Style. Style is that intangible presence the Sales Rep brings to the table. When the PSR has been brought in to support the sale, the PSR and the Sales Rep must work in tandem to represent the company and solutions for prospects. Style involves methodology—the manner in which information is relayed to the prospect. It includes identifying the level of simplicity or detail necessary to communicate that information. A PSR’s style should always convey Support and Sincerity and compliment the sales team.

S - The last “S” in CLASS stands for Selling. Never forget that the object is to eventually make the sale! An effective PSR should be intentional about focusing on the selling process. A prospect does not need all the answers to all the questions at once. A productive PSR participates in the sale rather than trying to control it. Keep this in mind with the previous qualities and you’ll end up being a strong selling influence with credibility, listening skills, accountability, and style.

In summary, the top notch PreSalesRep brings CLASS to the selling process and is a valuable asset to the sales team, the prospective customer, and the company he/she represents.

Source By William Champion.

Finally Succeeded - PLM Implementation!!

Most of PLM blogs tells these days whenever I come across any PLM blog posts about PLM, the first impression I get is that PLM Implementations are  real challenge to take and nothing but failures. There are many blogs which say where, why and how it fails. But there are no PLM blogs ever address these implementation failures or real needs/requirements of PLM Projects.

I get clear understanding that organizations need to implement PLM to address their challenges and later issues will be solved. Is it really true?

PLM Vendors, PLM Implementing teams and PLM Customers need to set a process of implementation usually, what should be the methodology? What should be the road map? Which people are required at many stages of PLM Implementation? Those I already mentioned in my previous posts.

Many have worked on various PLM tools over various domains; I worked in PLM implementation for Plant Design domain and I just want to highlight success stories of my two implementations after all discussions over failures, difficulties and limitations.

I have worked for a client in Energy and Plant Design domain, an EPC compnay, on

Enovia SmarTeam Implementation integration with CATIA V5 for Energy Plant Design industry: where I have got breakthrough and is stating as follow

Project & Technical Lead Role:
Participate in client discussions, understand problems faced by client and articulate same to internal stakeholders to develop effective solution.

>Bring in best practices of industry and provide options & Develop proposal.

>Prepare As-Is and To-be documentation, Technical Scope preparation.

>Provide inputs based on secondary research in Clients Environment.

>Give inputs on solutions; based on areas of expertise.

>Conduct product demonstration and Training on PLM product with Acceptance test Plan document and configuration as per Technical scope.

>Analyse the requirements by demonstrating strong process, solution & product knowledge, IT scenario, implementation and technology constraints, look at end to end perspective with implications in related functional & product areas.

>Lead solution in all engagements and review work of team members as per project schedule.

>Plan activities for configuration, conduct conference and prepare configuration and Project completion Report.

>Customer offline Technical Support & Troubleshooting
Accomplishments:
*Plant Design Layout methodology Establishment in ENOVIA SMARTEAM system,
*Full CATIA Catalogue Management with ENOVIA SMARTEAM,
*CATIA Piping Design Integration and Management with ENOVIA SmarTeam,
*CATIA HVAC, Electrical & Civil Structure Module ENOVIA SMARTEAM Integration
*Brought in Best working Methodology

It is almost two years project and after all initial difficulties, failures; the implementation  went successful and live 1.5 years back and still as of today it is working fine and I am very happy to state here that Implementing ENOVIA V5 SmarTeam and CATIA V5 integration in Energy and Plant Design domain is first in the history and its working fine.

Bye for now,

Anil Kumar J R