Archive for the ‘Success Skills’ Category

General Simulation Project Approach

Saturday, March 10th, 2012

People often wonder “When is the best time to incorporate simulation into a project?” The answer, without a doubt, is at the earliest possible moment — when an idea for a significant system change or major investment is first being discussed. While it is true that at this early point in a project there are many unknowns and often very little data, simulation can still provide significant value with often a very low level of effort. While the specific issues obviously vary based on the exact systems, at these early stages you are often looking for gross measures of capacity planning and throughput analysis, impact on other facilities, and early identification of potential problem areas.

With modern tools, you can often create high-level simulation models to study such issues in not much more time than it might take to develop a comparable spreadsheet. But instead of using a spreadsheet that is limited to often misleading static analysis and fairly simple relationships, simulation can take full account of the variation and complexity present in most real systems. And as the project concepts mature, the simulation can expand and mature along with it and continually provide value at each step of the project.

For example a project might go through phases with typical questions like these:

1. Early concept validation – How will this new system work? What is the estimated capacity and throughput? What impact will this have on existing facilities? How can I communicate potential issues to stakeholders?

2. High-level system design – What components should be included? What are realistic design objectives? Evaluation of trade-offs of various investments and level of capability provided. High-level bottleneck analysis. Identify “surprises” while they are still easy to deal with.

3. Detailed system design – What specific equipment should be used (e.g., degree and type of automation)? What procedures should be implemented? What reliability can be expected and how will that impact performance and costs?

4. Implementation –Does the system perform as expected and if not, why not and how can it be “fixed”? What is the optimal staffing? When is a “change order” worthwhile?

5. Start-up – What is the impact of learning curves? What are realistic expectations during transition to full capacity? How long will that transition require? What special procedures should be put in place during that transition, what is their cost, and how soon can they be phased out?

6. Operation – How to plan and schedule the intermediate and short-term facility operation? How to effectively deal with the variability present in all systems (e.g., equipment and personnel problems, demand variation, shifting priorities, …)? How well is the system performing on the actual demand as opposed to the originally anticipated or “optimal” demand?

7. System improvement/re-design – As the system reaches stable operation, new ideas, procedures, and technologies will occur. What would be the impact of incorporating changes? Which changes have the best ROI? How do the changes relate to each other?

Until next time … Happy Modeling!

Simulationist Bill of Rights

Saturday, February 27th, 2010

In the Simulation Stakeholder Bill of Rights I proposed some reasonable expectations that a consumer of a simulation project might have. But this is not a one-way street. The modeler or simulationist should have some reasonable expectations as well.

1. Clear objectives – A simulationist can help stakeholders discover and refine their objectives, but clearly the stakeholders must agree on project objectives. The primary objectives must remain solid throughout the project.
2. Stakeholder Participation – Adequate access and cooperation must be provided by the people who know the system both in the early phases and throughout the project. Stakeholders will need to be involved periodically to assess progress and resolve outstanding issues.
3. Timely Data – The functional specification should describe what data will be required, when it will be delivered and by whom. Late, missing, or poor quality data can have a dramatic impact on a project.
4. Management Support – The simulationist’s manager should support the project as needed not only in issues like tools and training discussed below, but also in shielding the simulationist from energy sapping politics and bureaucracy.
5. Cost of Agility – If stakeholders ask for project changes, they should be flexible in other aspects such as delivery date, level of detail, scope, or project cost.
6. Timely Review/Feedback – Interim updates should be reviewed promptly and thoughtfully by the appropriate people so that meaningful feedback can be provided and any necessary course corrections can be immediately made.
7. Reasonable Expectations – Stakeholders must recognize the limitations of the technology and project constraints and not have unrealistic expectations. A project based on the assumption of long work hours is a project that has been poorly managed.
8. “Don’t shoot the messenger” – The modeler should not be criticized if the results promote an unexpected or undesirable conclusion.
9. Proper Tools – A simulationist should be provided the right hardware and software appropriate to the project. While “the best and latest” is not always required, a simulationist should not have to waste time on outdated or inappropriate software and inefficient hardware.
10. Training and Support – A simulationist should not be expected to “plunge ahead” into unfamiliar software and applications without training. Proper training and support should be provided.
11. Integrity – A simulationist should be free from coercion. If a stakeholder “knows” the right answer before the project starts, then there is no point to starting the project. If not, then the objectivity of the analysis should be respected with no coercion to change the model to produce the desired results.
12. Respect – A good simulationist may sometimes make the job look easy, but don’t take them for granted. A project often “looks” easy only because the simulationist did everything right, a feat that in itself is very difficult. And sometimes a project looks easy only because others have not seen the nights and weekends involved.

Discussing these expectations ahead of time can enhance communications and help ensure that the project is successful – a win-win situation that meets everyone’s needs.

Dave Sturrock
VP Products – Simio LLC

Simulation Stakeholder Bill of Rights

Wednesday, January 20th, 2010

The people who request, pay for, consume, or are affected by a simulation project and its results are often referred to as its stakeholders. For any simulation project the stakeholders should have reasonable expectations from the people actually doing the work.

Here I propose some basic stakeholder rights that should be assured.

1. Partnership – The modeler will do more than provide information on request. The modeler will assume some ownership of helping stakeholders determine the right problems and identify and evaluate proposed solutions.
2. Functional Specification – A specification will be created at the beginning of the project to help define clear project objectives, deadlines, data, responsibilities, reporting needs, and other project aspects. This specification will be used as a guide throughout the project, especially when tradeoffs must be considered.
3. Prototype – All but the simplest projects will have a prototype to help stakeholders and the modeler communicate and visualize the project scope, approach, and outcomes. The prototype is often done as part of the functional specification.
4. Level of Detail – The model will be created at an appropriate level of detail to address the stated objectives. Too much or too little detail could lead to an incomplete, misunderstood, or even useless model.
5. Phased Approach – The project will be divided into phases and the interim results should be shared with stakeholders. This allows problems in approach, detail, data, timeliness, or other areas to be discovered and addressed early and reduces the chance of an unfortunate surprise at the end of a project.
6. Timeliness – If a decision-making date has been clearly identified, usable results will be provided by that date. If project completion has been delayed, regardless of reason or fault, the model will be re-scoped so that the existing work can provide value and contribute to effective decision-making.
7. Agility – Modeling is a discovery process and often new directions will evolve over the course of the project. While observing the limitations of level of detail, timeliness, and other aspects of the functional specification, a modeler will attempt to adjust project direction appropriately to meet evolving needs.
8. Validated and Verified – The modeler will certify that the model conforms to the design in the functional specification and that the model appropriately represents the actual operation. If there is inadequate time for accuracy, there is inadequate time for the modeling effort.
9. Animation – Every model deserves at least simple animation to aid in verification and communication with stakeholders.
10. Clear Accurate Results – The project results will be summarized and expressed in a form and terminology useful to stakeholders. Since simulation results are an estimate, proper analysis will be done so that the stakeholders are informed of the accuracy of the results.
11. Documentation – The model will be adequately documented both internally and externally to support both immediate objectives and long term model viability.
12. Integrity – The results and recommendations are based only on facts and analysis and are not influenced by politics, effort, or other inappropriate factors.

Note that every set of rights comes with responsibilities. The associated stakeholder responsibilities are discussed as part of the Simulationist Bill of Rights.

Give these expectations careful consideration to improve the effectiveness and success of your next project.

Dave Sturrock
VP Products – Simio LLC

Human Judgment Beats Simulation

Wednesday, November 25th, 2009

Human Judgment, also known as Seat Of The Pants Analysis (SOTPA), is probably the least acknowledged but most widely used alternative to simulation. SOTPA is making decisions by instinct and feelings rather than using objective analytical tools. With SOTPA you never actually have to get out of your chair, or even spend any significant time to reach a decision.

I use SOTPA all the time and you probably do too.

When I am in a hurry to go out and want to know if I should wear a jacket or bring an umbrella, I might take a quick look out the window, reflect on the season and yesterday’s weather, then make a decision. That’s SOTPA. I know that there is a high likelihood that I will be wrong, but I don’t want to take the time to do the weather channel research to get more objective information.

Human judgment beat simulation in this case. But not always.

When I am going on an all-day outside outing and have the same decision to make; the importance of being correct increases. In that situation I will take the time to consult at least two weather sources and even step outside for some direct research. With this objective analysis I can make a more informed decision. Although such an analysis is never perfect, including objective data in my analysis dramatically increases the likelihood that my decision will be correct.

Now let’s say I am a manager and my staff comes to me proposing purchase of a new piece of equipment to solve an important problem in my facility. They may give me technical specifications, maybe some manual or spreadsheet calculations, perhaps even show me a case study about how that equipment was used in another facility. The easy thing for me to do at that point is to make a SOTPA-based decision. After all, I must be pretty smart to get to be a manager, right? Right?? :) And I know THE BIG PICTURE. So who better than me to make the decision? And why should I need more information?

If you haven’t read it, I’d suggest you pause now and read the blog on Predicting Process Variability. Did you pass the test? Don’t feel bad, almost no one does. My facility is much more complicated than that one. If I cannot predict the performance of such a simple system, why should I expect that I can predict the impact of adding this proposed equipment to my facility?

“But I don’t have time to simulate.” I don’t have time to research weather when the penalty of being wrong is low, but I make the time to do it when the penalties are higher. With modern simulation tools you can often get valuable results in a short period of time. In two or three days you can often provide an objective analysis that can save a few hundred thousand dollars. Let’s see, invest $3000, save $200,000 … I think I can make the time for that. How about you?

Simulation beats human judgment when it matters.

When someone else uses SOTPA you might say they bent over and pulled the answer out of their… um, … er, shoe. “What was he thinking?” Don’t let that be you.

Reserve SOTPA for decisions that don’t matter. Use simulation for the decisions that do.

Dave Sturrock
VP Products – Simio LLC

Why Simulation is Important in a Tough Economy

Thursday, October 29th, 2009

Everyone wants to cut costs. No one wants to spend unnecessarily. When budgets are tight, software and software projects are an easy place to cut. Staff positions like Industrial Engineers are sometimes easier to cut or redeploy than production jobs. I suggest that following this reasoning to eliminate simulation projects is often short-sighted and may end up costing much more than it saves. Here are a few reasons why it may make sense to increase your simulation work now.

1) Minimize your spending. Cash is tight. You cannot afford to waste a single dollar. But how do you really know what is a good investment? Simulate to ensure that you really need what you are purchasing. A frequent result of simulations intended to justify purchases is to find that the purchases are NOT justified and in fact the objectives can be met using existing equipment better. A simulation may save hundreds of times its cost with immediate payback.

2) Optimize use of what you have. Could you use a reduction in cost? Would it be useful to improve customer satisfaction? I assume that your answer would always be yes, but even more so in difficult times. But how can you get better, particularly with minimal investment? Simulation is a proven way to find bottlenecks and identify often low-cost opportunities to improve your operation.

3) Control change. In a down economy you are often using your facilities in new and creative ways – perhaps running lean or producing products in new ways or in new places. But how do you know these new and creative endeavors will actually work? How do you know they will not cost you even more than you save? Simulation helps you discover hidden interactions that can cause big problems. Different is not always better. Simulate first to avoid costly mistakes.

4) Retain/improve your talent pool. Some people who might otherwise be laid off may have the skills to be part of a simulation SWAT team. By letting them participate in simulation projects, they will likely achieve enough cost reduction and productivity improvements that they more than pay for themselves. As an added bonus, the team will learn much about your systems, the people, and communication – knowledge which will improve their value and contributions long after the project is complete.

5) Reduce risk. You are often forced to make changes. How do you know they are the right changes? Will a little more, a little less, or a different approach yield better results? How do you measure? A strength of simulation is its ability to objectively assess various approaches and configurations. Substitute objective criteria for a “best guess”, and, in turn, reduce the risk associated with those changes. In a down economy it is more important than ever that you don’t make mistakes.

In summary, rather than thinking of the cost of simulation, you should think of what the investment in simulation today will save you today, tomorrow and every day following. Simulation is not a cost, it is an investment that may return one of the best ROIs available in a tough economy.

Dave Sturrock
VP Products – Simio LLC

Simulation and Strategic Management

Sunday, January 25th, 2009

Guest article from Marco Ribeiro

Corporations everywhere today face the huge challenge of surviving and growing in an extremely competitive environment. Markets are shaped and reshaped due to constant innovation, customer demands and fierce competition. All these forces demand that corporations continuously reinvent themselves trying to maintain competitive advantages that differentiate them from the competition.

Strategic planning in such an environment is a difficult challenge that corporations must overcome successfully. Corporate strategic planning deals with such complex issues as:

    * Understanding the market and its future trends – understand suppliers, competition, their competitive advantages and market positioning. Know the future trends that will shape the market.
    * Future resource allocation – how the corporation’s resources should be organized in order to maintain an efficient operation.
    * Scope of operations -in which businesses should the corporation operate, which ones should be dropped out
    * Diversification of the corporation’s business – should the corporation focus its operations in a small and related set of businesses or should it look to diversify to heterogeneous businesses
    * Future structure of the company – draw the boundaries of the corporation and determine how these boundaries will affect relationships with suppliers and customers

The strategy defined will address all these issues in detail and determine the future direction of the corporation.

Can we use simulation to support the strategic planning process?
Yes, we can. As Thomas Davenport and Jeanne Harris describe in their book: Competing on Analytics: The new Science of Winning, we will see an increasing demand and use of analytical technologies supporting corporation’s decision-making processes.

Simulation can play an important role by helping managers create models of their markets and processes and “toy” with them in order to get a deeper understanding. We can also use simulation to support such efforts as portfolio analysis and management, helping managers determine how to most effectively manage and configure their product life cycle. We can build models of processes and determine the most efficient configuration. Simulation is a valuable tool to test scenarios and make better business decisions.

Marco Ribeiro
LinkedIn Profile

Industrial Engineers are Happy

Sunday, January 18th, 2009

I just saw an interesting article written by the Institute of Industrial Engineers (IIE) citing a National Opinion Research Center study at the University of Chicago. According to that study, Industrial Engineering is one of the top ten occupations when rated by job satisfaction and overall happiness. I have long been an IE evangelist, because I feel it is a great career choice, but it never hurts to have some additional evidence.

The study goes on to evaluate compensation for each of those professions and concludes that IE’s are the third highest paid group out of those top ten happiest careers. While I think it is a mistake to choose a career primarily based on financial compensation, it is a nice bonus when a career that makes you happy also pays well.

Here is a short article summarizing the results: Industrial engineering for your mental health?

I’ve always felt that IE was one of the best career choices possible. And I think this is especially true in the field of simulation.

I personally try to visit a few high school classes each year to help students discover our profession and help motivate them to excel in the classes that they need to be successful in engineering. IIE can help you do this.

I urge you to also get involved with your local high schools and help spread the word.

Dave Sturrock
VP Products – Simio LLC

Six Sigma and Simulation: Part 1

Sunday, November 30th, 2008

By Jeff Joines (Associate Professor In Textile Engineering at NCSU)

This is a three part series on Six Sigma, Lean Sigma, and Simulation. The first blog will explain the Six Sigma methodology and the bridge to simulation analysis and modeling while the second and third parts will describe the uses of simulation in each of the Six Sigma phases and Lean Sigma (i.e., Lean Manufacturing) respectively.

“Systems rarely perform exactly as predicted” was the starting line for the blog Predicting Process Variability and is the driving force behind most improvement projects. As stated, variability is inherent in all processes whether these processes are concerned with manufacturing a product within a plant, producing product via an entire supply chain complex or providing a service in the retail, banking, entertainment or hospital environment. If one could predict or eliminate the variability of a process or product, then there would be no waste (or Muda in the Lean World which will discussed in a third part) associated with a process, no overtime to finish an order, no lost sales owing to having the wrong inventory or lengthy lead-times, no deaths owing to errors in health care, shorter lead times, etc. which ultimately leads to reduced costs. For any organization (manufacturing or service), reducing costs, lead-times, etc. is or should be a priority in order to compete in the global world. Reducing, controlling and/or eliminating the variability in a process is key in minimizing costs.

Six Sigma is a business philosophy focusing on continuous improvement to reduce and eliminate variability. In a service or manufacturing environment, a Six Sigma (6?) process would be virtually defect free (i.e., only allowing 3.4 defects out of a million operations of a process). However, most companies operate at four sigma which allows 6,000 defects per million. Six Sigma began in the 1980s when Motorola set out to reduce the number of defects in its own products. Motorola identified ways to cut waste, improve quality, reduce production time and costs, and focus on how the products were designed and made. Six Sigma grew from this proactive initiative of using exact measurements to anticipate problem areas. In 1988, Motorola was selected as the first large manufacturing company to win the Malcolm Baldrige National Quality Award. As a result, Motorola’s methodologies were launched and soon their suppliers were encouraged to adopt the 6? practices. Today, companies who use the Six Sigma methodology achieve significant cost reductions.

Six Sigma evolved from other quality initiatives, such as ISO, Total Quantity Management (TQM) and Baldrige, to become a quality standardization process based on hard data and not hunches or gut feelings, hence the mathematical term, Six Sigma. Six Sigma utilizes a host of traditional statistical tools but encompasses them within a process improvement framework. These tools include affinity diagrams, cause & effects, failure modes and effective analysis (FMEA), Poka Yoke (mistake proofing), survey analysis (voice of customer), design of experiments (DOE), capability analysis, measurement system analysis, statistical process control charts and plans, etc.

There are two basic Six Sigma processes (i.e., DMAIC and DMADV) and they both utilize data intensive solution approaches and eliminate the use of your gut or intuition in making decisions and improvements. The Six Sigma method based on the DMAIC process and is utilized when the product or process already exists but it is not meeting the specifications or performing adequately is described as follows.

    Define, identify, prioritize, and select the right projects. Once selected to define the project goals and deliverables.
    Measure the key product characteristics and process parameters to create a base line.
    Analyze and identify the key process determinants or root causes of the variability.
    Improve and optimize performance by eliminating defects.
    Control the current gains and future process performances.

If the process or product does not exist and needs to be developed, the Design for Six Sigma (DFSS) process (DMADV) has to be employed. Processes or products designed with the DMADV process typically reach market sooner; have less rework; decreased costs, etc. Even though, the DMADV is similar to DMAIC method and start with the same three steps, they are quite different as defined below.

    Define, identify, prioritize, and select the right projects. Once selected to define the project goals and deliverables.
    Measure and determine customer needs and specifications through voice of the customer.
    Analyze and identify the process options necessary to meet the customer needs.
    Design a detailed process or product to meet the customer needs.
    Verify the design performance and ability to meet the customer needs where the customer maybe internal or external to the organization.

Both processes use continuous improvement from one stage back to the beginning. For example, if during the analyze phase you determine a key input is not being measured, new metrics have to be defined or new projects can be defined once the control phase is reached.

Now that we have defined six sigma, you may be wondering what is the bridge to computer simulation and modeling. Simulation modeling and analysis is just another tool in the Six Sigma toolbox. Many of the statistical tools (e.g., DOE) try to describe the dependent variables (Y’s) in terms of the independent variables (X’s) in order to improve it. Also, most of the statistical tools are parametric methods (i.e., they rely on the data being normally distributed or utilize our friend the central limit theorem to make the data appear normally distributed). Many of the traditional tools might produce sub-optimal results or cannot be used at all. For example, if one is designing a new process or product, the system does not exist so determining current capability or future performance cannot be done. The complexity and uncertainty of certain processes cannot be determined or analyzed using traditional methods. Simulation modeling and analysis makes none of these assumptions and can yield a more realistic range of results especially where the independent variables (X’s) can be described as a distribution of values. In Six Sigma and Simulation: Part 2, a more detailed look at how simulation is used in the two six sigma processes (DMAIC and DMADV) will be discussed.

Professional Development

Sunday, November 23rd, 2008

The annual Winter Simulation Conference (WSC) starts two weeks from today. Initially as a practitioner and then later as a vendor I have attended over 20 of these conferences in addition to dozens of other similar events. WSC is just one of many events that you could choose to attend. But why should you attend any of them?

All such events are not identical, but here are a few attributes of WSC that are often found in other events as well:

Basic tutorials – If you are new to simulation, this is a good place to learn the basics from experienced people.

Advanced tutorials – If you already have some experience, these sessions can extend your skills into new areas.

Practitioner papers – There is no better way to find out how simulation can be applied to your applications than to explore a case study in your industry and talk to someone who may have already faced the problems you might face.

Research – Catch up on state-of-the-art research through presentations by faculty and graduate students on what they have recently accomplished.

Networking – The chance to meet with your peers and make contacts is invaluable.

Software exhibits and tutorials – If you have not yet selected a product or you want to explore new options, it is extremely convenient to have many major vendors in one place, many of whom also provide scheduled product tutorials.

Supplemental sessions – Some half and full day sessions are offered before and after the conference to enhance your skill set in a particular area.

Proceedings – A quick way to preview a session, or explore a session that you could not attend. This serves as valuable reference material that you may find yourself reaching for throughout the year.

I think every professional involved in simulation should attend WSC or an equivalent conference at least once early in your career, and then periodically every 2-3 years, perhaps rotating between other similar conferences. If you want to be successful you have to keep your skills and knowledge up to date. And in today’s economy, a strong personal network can be valuable when you least expect it.

I hope to see you at WSC in Miami!

Dave Sturrock
VP Products – Simio LLC

Read My Project Report!

Sunday, November 16th, 2008

I read a lot, both for business and pleasure. But it seems I never have enough time. So when I sit down with a magazine, for example, most articles probably get less than a couple seconds of attention. Unless an article immediately captures my attention, I quickly move on to the next one. I know that I occasionally miss out on good content, but it is a way to cope with the volume of information that I need to process each day. Consider the implications when you are writing a project report for others to read…

We are all busy. When we are presented with information to read or review, we often don’t have time to wade through the details to see if the content merits our time.

Tell me the most important thing first! Give me the summary! How many times have you asked (or wished) for that?

At one point, it was common to give presentations by starting with an introduction, building the content, and ending with the conclusion – “the big finish”. While this is appropriate for some audiences, many people don’t want to take the time to follow such a presentation. Instead, they want to be presented with a quick overview and a concise summary first. They will then decide to read on if the overview has captured their interest and they need more information.

Think about your own experiences. When you have a document to read and you are not sure it is worth your time, what do you do? If you are like most people you will probably consider most, if not all of the following:
• Does the title look interesting?
• Do you know/respect the author?
• Scan the major headings or callouts for content of interest.
• Scan any pictures/diagrams for content of interest.
• Evaluate the summary or abstract.
While the order and details might differ slightly, at each stage of the above process if you are not convinced of the value of continuing, you will put the document aside. Only after the document has passed this gauntlet of tests, will you spend the time to seriously read the content.

What can we learn from this?

Content is not enough. The best content in the world is of little value unless it is read.

When you are preparing a project report, try to get inside the head of your target audience. If you expect that they will also have a process something like the above, spend adequate time on those parts. Take an extra minute to create an interesting title. Add major headings and callouts to help focus the reader’s attention. Add some figures to help convey and support your message. Have a good abstract and/or summary that is easy to find to help your audience quickly get the point of your report.

Write each report so everyone, including your busy stakeholders, will take the time to read it. Keeping these simple suggestions in mind will help you succeed at getting your message across.

Dave Sturrock
VP Products – Simio LLC