Home / Process Improvement

Archive for the ‘Process Improvement’ Category

Does Automation Make Sense?

Thursday, June 4th, 2009 by ksmith

If you have a process for assembling or inspecting your parts, how do you know if automating the process makes sense?  Setpoint has been discussing this question with companies since 1992.  In our YouTube clip, Does Automation Make Sense, Clark walks through the issues a company needs to look at before automating a process.  In order to solve your problems, you need to know what they are.  Watch the video below as Setpoint discusses the steps of getting all the issues and opportunities out, setting a budget, determining your ROI (Return on Investment), and more so you can decide if automating is right for you.

Bookkeeping

Thursday, May 14th, 2009 by Setpoint

When I first started with Setpoint I did not know much about QuickBooks, accounts receivable, or accounts payables.  My boss was very good at explaining what to do and letting me figure things out on my own.

It has been very interesting for me to learn how a company can start with a drawing and go through the purchasing to receiving end to putting it together to making a project work.  My job is to take care of the invoices after we have received the product.  I make sure that it has been received and the amount we ordered is right and from there we start the process of putting the invoice in QuickBooks. 

When I first started there were some problem invoices that dated back over 1 year.  For the first 6 months I focused on getting every vendor paid and the problem invoices fixed so that now we do not have any outstanding problem invoices.  That has been my biggest accomplishment.  It’s so much easier to try to fix the problem when everyone remembers the situation. 

Some of the problems when I first started were that a payment wasn’t made to the right invoice.  So there was some confusion on both parties.  And because it was so late none of the sales people remembered if we had brought it back or what really happened.

Now that I have gotten to know the vendors I just call and ask for the person who knows me and am on a first name basis with them.  It’s easier because they know me and seem more willing to help with the problem.  At the first of the month we receive a statement with all outstanding invoices, this lets me know what I need to work on or if there is a problem. 

I enjoy my job and have loved getting to learn more about QuickBooks, accounts receivable and accounts payable.  It’s great to have this knowledge.

Virtual Companies

Monday, May 11th, 2009 by Brad

You read and hear a lot about virtual companies these days. What does it take to actually try and make one work?

At Setpoint, we are in a highly cyclical business.  We used to size our business based on the busy times and then try and tough it out during the slow times with out having to lay people off.  Every time you have to lay people off, it is very painful – not only for the people you have to let go, but it is difficult for those that remain. A couple of years ago we made a strategic decision to size our company for the lean times and use outsourcing techniques to handle the busy times, we decided to try and become a small base of key people that can wear many hats and outsource some functions that we believed could be more generic with proper management.

I had read many articles about the virtualization of the work force. One book that gives great insight is The Future of Work by Thomas W. Malone.

It is hard to make a virtual company work. Reading about it is one thing, putting it into action profitably has been much more difficult.

We used www.dice.com to help us filter and identify technical people that fit our needs.  We then used our best mentoring VP to sort through the resumes and set up discussions to find those that might match with our culture.

One thing we did instead of flying them out to meet with us was, we set up a 20 hour project they had to complete (we paid them for this) to see how they would do. We found out a lot by seeing how they solved that project. Like all people that work for a company – not all will be a fit for you or them, the sooner you find out the better for everyone involved.

We have needed many tools to help us make this concept work. One of the main tools we use many times a day is from www.37signals.com – it is called Basecamp. This is our main communication and file tool, it is a diary of all that is taking place and assignments given. We use concurrent licenses for our engineering software programs to give us flexibility to share licenses. www.twiddla.com helps in our concepting phase. Every engineer has a unique color they use so we can recognize who has done what. www.gotomeeting.com is used to host virtual meetings and share information. You will need a conferencing program so that many can join the daily conversations. Setpoint is considering IP phones so we can send phones to our virtual employees and have them just a local extension away.

As you start out with new people give them clear short work assignments to make sure you and they are a good fit with your culture. The key roles of some of your employees will have to change. They have to over communicate and not be afraid to call up and see how their distant team member is doing. One of worst things is to assume everything is going fine if you don’t hear from a virtual team member.

More than anything it is important to have frequent (at least daily) contact with your virtual people. We have done things to connect with our offsite members so they feel like they are working for a real company that cares for them. In Basecamp we have a picture of our facility. As we send messages back and forth through Basecamp we have our own pictures on the message to reinforce that there is a real person behind all of this action.

Your face to the customer has to remain with your employees. We have found that customers have to connect with employees – not virtual team members. It has to appear seamless to them.

We feel that we are making progress but it is a continual battle.  Is it better than carrying too many employees through a downtime in the cyclical nature of this business? For us, the answer is a definite yes.

We are still growing at being a company that has virtual team members and believe we still have many lessons to learn as we go down this path. We’d love to hear from any of you out there that can help Setpoint get there faster.

Disruptive Technologies and The Innovators Dilemma

Thursday, April 16th, 2009 by ScottP

I recently read the book The Innovators Dilemma by Clayton Christenson. I would not call it entertaining at all, in fact, I thought it was pretty good sleeping aid. That being said, I found the information and the subject matter extremely interesting. The book is based on the idea that very well run companies who are paying attention to their customers, investing in continuous improvement, and treating their employees well can suddenly and almost inexplicably fail and often go completely out of business. The amazing thing is that the very things that managers are doing “right” are frequently the exact things that cause a company to fail.

Christenson uses the disk drive industry as a study model. He says that biologists often study fruit flies because their life span is only several hours. Therefore they can study multiple life spans in a single research study. He claims that the computer hard disk drive industry is the closest thing in industry to a fruit fly. (Yes, I also found that amusing.) There are other industries that were studied as well. The author pointed to examples in the steam shovel industry, the motorcycle industry and the retail industry as well as others. He also introduced the term disruptive technology.

The claim is that a disruptive technology or idea is one that is less attractive in most areas than similar existing ones. Let me point to the 8 inch hard drive. This was a mature product. Manufacturers were continuing to improve its capacity and performance. They were responsive to their customer’s needs and invested in research. When the 5 ¼ inch drive came upon the market, the manufacturers existing customers (makers of main frames and large servers) had little interest in it. It had lower capacity and lower performance and was more expensive. Managers looked at this new disruptive technology and said, “Why would anyone want that, and why should we invest resources into it?”

The problem was that the customers for this new idea had not yet been found. The makers of small desk top PC’s were just coming over the horizon, and they loved the little underperforming overpriced orphan, so a few manufacturers started making them. As research on the smaller drives advanced, they began to approach and eventually surpass the performance of the larger drives. Suddenly they were attractive to the main frame and server manufacturers. Like getting hit with a surface to air missile, the big manufacturers were not prepared to compete in the new market and were shot out of the air. They never saw it coming, as the saying goes.

There is a solution fortunately. When a disruptive technology comes along that shows some promise, create a spinoff company. Make it self sustaining and self ruled. The new company must not be shackled to the traditions and “corporate culture” of the parent. The trouble is that large companies have big appetites and lots of traditions and expectations. In order for a $100 million company to grow 10 percent, they have to have $10 million in profit. A $100 thousand company only needs $10 thousand. A small company can afford to put resources into less mature technologies that a larger company could not.

Imagine yourself as a well trained competent and concerned manager. Of course your bonuses are based on the performance of your division. A well respected engineer comes to you and says, “I have this great idea. Take a look at this.” You look at “this” and agree that it is a great idea. You ask him, “What is the market for this idea? Who do you think will buy it?” He says he does not know exactly, but that some one would certainly want it. You say, “What do you think our annual sales would be if we made them?” He says that he is an engineer and has no idea, but it is a great idea. Because you respect the engineer, you take it to your sales people who talk to all your existing customers about it. Of course your existing customers have no interest in it. How much of your department resources are you willing to invest into this “great idea” that could otherwise be spent on improving existing products with accurate sales projections and known customers? (“Duh, I dunno” is not an acceptable answer.)

That’s it in a nutshell. Disruptive technologies come along all the time. The disk drive scenario played itself out about four times within ten to fifteen years. Hydraulic excavators replaced steam shovels with a nearly identical script although the time line was greatly stretched. Little Japanese motor bikes nearly wiped out the large American road bike industry at one point. By the way, how many large retailers have gone out of business or sold out to competitors in your life time? Think about it.

Using Creative Thinking Every Day to Solve Problems

Thursday, April 9th, 2009 by Bryan

Who has heard of the acronym TRIZ?  Until a few months ago, it would have meant nothing to me except as four nicely arranged capital letters.  Honestly I still don’t know what the terminology of the acronym is because it is derived from a Russian phrase meaning “Theory of Solving Inventor’s Problems.”  I do, however, have a basic understanding of the principles of TRIZ and how to apply them.  TRIZ is a bunch of principles that can be used to solve any problem that you may encounter.  This applies to work, home, play, or anywhere else.  TRIZ was developed by G.S. Altshuller, a Russian, as a means to solve problems.  There are 40 TRIZ principles that can help you out.  You can Google TRIZ to find out more about TRIZ and its uses.  For now, I am going to relate a recent example where we have used the principles of TRIZ.

We are currently in the design phase on a fairly large machine.  Space and cost are issues with this project.  The machine will be building parts that have a very defined manufacturing process with many steps.  For us, we have mimicked the original process as best as we could.  Our machine started out with 3 dial tables, with each one costing a sizeable chunk of cash.  After laying out the machine and realizing that we had many open stations, we decided to change the order of operations, cleared this with our customer, and placed a particular operation up closer to the front of the process.  This allowed us to remove a dial table from the machine saving us some much-needed real estate, and a bunch of money. 

These principles have become a part of our culture here at Setpoint.  I am quite certain that when this decision was made we were not intentionally applying a TRIZ principle, even though we did.  The principle we applied was Merging.  We took a similar process and placed them side-by-side.

There are many more examples of where we solved a problem by applying a TRIZ principle on this project.  What we have learned is if you get to a place where you are stuck, pull up the TRIZ principles on the net and go through them one by one and see if one of them will help solve your problem.

A Day in Purchasing

Thursday, March 26th, 2009 by Malorie

A normal day in the purchasing department consists of many different tasks and in order to maintain accuracy they all must be followed.  From getting quotes to the actual order process there are many steps involved which seem to all be equally important.  It is so easy for me to skip some of the steps if I’m in a hurry or get interrupted.  When these crucial steps are overlooked I always regret it later because I can’t retrace my steps when an error or question arises.

One of our main focuses at Setpoint has been to make the Lean transformation and cut out as much waste as possible in our daily tasks and ongoing projects.  Purchasing is a huge part of Setpoint’s business so to cut out wastes is a huge deal and any savings that I can generate automatically goes to the bottom line as profit.  It’s a huge task that I want to achieve success at;  therefore I’m always thinking and looking at ways to change what I do to make it more efficient and achieve the same, if not better, results with myself, Setpoint, the vendor, and my customers being satisfied.

In the past five years that I have been in this department I have seen some dramatic changes for the better but I know it can still be better and leaner.  Success has yet to be achieved and that is my ongoing ultimate goal.

What Does the Customer Really Want?

Thursday, March 12th, 2009 by Clark

At Setpoint we follow the Mahan (Mahan Khalsa) culture of selling.  Following are some high level points we closely follow and practice in our daily business relationships with our clients.

Mahan selling is not a technique but rather a culture that establishes a partnership between Consultant and Client.  Too many times sales professionals spend an inappropriate amount of time advocating their products or service before even understanding what the client’s needs, issues and opportunities are.

Mahan selling focuses on understanding completely every aspect of the customer’s needs before trying to pitch a solution that may not be even close to what is needed.  By focusing efforts on the customers issues and opportunities, a sales professional can bring far more “value add” to the table and in the long run provide the solutions that exactly meet the customer’s needs.  Not kind of, or sort of…exactly.

The goal is to be in tune with the customer’s business issues and opportunities.  This can only be achieved by allowing the customer to express what these issues and opportunities are.  Too many times customers just want to know a number or be given a solution to what they perceive as “The” issue.

At closer examination, and with some sincere questioning by the sales professional, a complete, prioritized list of these issues and opportunities can be compiled.  The way to get to a solution that exactly meets your client’s needs is by a “No Guessing” approach to finding out what issues and opportunities your solution will solve or help the client take advantage of.

stoplight

Any time you feel the conversation or sales cycle may not be going in the right direction, Mahan calls this a yellow light.  Our typical reaction to yellow lights in sales is similar to how we drive on the road.  Most people speed up and zoom right through the yellow caution lights.  In the Mahan culture we are encouraged to slow down for these yellow lights and express your concerns to the customer.

If we let the customer turn the so called yellow lights to green, rather than trying to hurry through the issues and do it ourselves, we will be more successful in finding a way to serve their needs.  In fact, if done correctly, having the customer solve the issues or yellow lights can usually create a more positive impression of you and your company’s ability to serve their needs.

 One of the main reasons we try to get an upfront list of issues and opportunities is because there is always a direct correlation between the customers likelihood of buying our solutions at a certain price and the number of issues and or opportunities we and the clients feel our solutions can solve or capitalize on.

So remember, never guess what the client’s needs are.  Ask clarifying questions on what their needs are.  Get out all the issues and opportunities they hope your solution will solve.  And always slow down for yellow lights in the sales cycle and allow the customer to turn any yellow lights to green.

Starting Up a New Machine

Thursday, February 19th, 2009 by Chad

First of all, be safe.  There may be a lot of different people working on the same project, so you might finish wiring the panels and pneumatics on the machine that someone else started.  After the machine is complete and before you power up the whole machine, start your check out by pulling all the fuses, circuit breakers and such one at a time.  This way you can check different parts of the machine at different times, which can save you from running into bigger problems.  If you just power up the machine without doing this step and there’s something wired wrong, you could create a problem throughout the entire machine.

When you power up the machine, check the voltage one step at a time by plugging in the fuses and circuit breakers for the area you are checking one by one.  Check each component for their power, check the D/C (direct current) power the same as the A/C (alternating current).  If it doesn’t smoke you did a Good Job!

If it does smoke, look for what smoked.  Look for blown fuses or circuit breakers and such.  Look for incorrect wiring or voltage.  If the problem is found, fix the problem.  If no problem is found it could be a defective part.

Troubleshooting is just that, looking for the problem and going step by step to find out what is causing the problem.  Each machine is unique and different, sizes and ranges of voltage can differ as well as components.

The Right Tool for the Job

Wednesday, January 21st, 2009 by Shayne

Though tools are expensive, it’s important to use the proper tools for the job you are doing.  If you don’t have the right tools you can run into many problems.  Rounded off or stripped out bolts, wrong sized holes, and broken taps are a few of the problems you may face.

Using the wrong tool for the job makes disassembling parts, or changing out parts difficult.  Also, the cost of replacing parts that may be ruined by using the wrong tools is avoided by using the proper tools.

Using power tools and air tools when possible is more efficient and can lower your costs in hours.  Who wants to stand around and build something using a hammer and nails when you can use a nail gun instead? 

Having the right tools for the job helps everybody deliver a quality professional product for their clients and reflects well on your company.

Lean Automation…the Engineers and Assembly Technicians

Wednesday, January 7th, 2009 by Warren

At Setpoint we have been building lean automated equipment for over 16 years.  One of the lessons we have learned is the importance for engineers and assembly technicians to work together to get the job done efficiently and give the customer the best possible quality, price, and on-time delivery.  Many times if the two don’t work together things tend to have to be redone, redesigned, or ideas scrapped all together.  I’ve seen this time and time again, which in turn affects the quality and price and doesn’t make anybody happy.

For many years I have maintained and assembled machines and have seen many designs and working environments that most design engineers aren’t even aware of.  Because of this experience that myself and other assembly technicians have we can often give insight to these facts.

Working together also makes installation easier and better.  Engineers don’t tend to think of having an easy connector to two parts of a machine so that they can be easily separated for shipping or how the air hoses or electrical components are connected so when the machine is prepared for shipping you don’t have to rewire part of it at install.  When examples such as these are not kept in mind during the design phase, the onsite installation can take much longer to get the machine up and running on the customers’ floor than need be, which costs us more and doesn’t look good to the customer.

So we all need to just get along!