Tag Archives: streamline

Soapbox

Tips to Shrink your Shrinkage

By Carl Silverberg
No Comments

I had dinner last night with a friend who is a senior executive at one of the largest automobile companies in the world. When I explained the industry-accepted rate of 25-30% shrinkage in horticulture he said, “Are you kidding me? Can you imagine the story in the Wall Street Journal if I gave a press conference and said that we were quite content to throw away three out of every ten cars we manufactured?”

Yet, for all growers, operators and investors who complain about shrinkage, it’s an accepted part of the business. What if it wasn’t; what if you could shrink your shrinkage by 60% and get it down to 10% or less? How much more profitable would your business be and how much easier would your life be?

Let’s take the floriculture industry as our first example. You propagate chrysanthemums in February, they get repotted at the end of April and by the end of June, you might start to see some buds. In a very short time span your job changes from being a grower who manages 10,000 square feet of chrysanthemums to being an order taker. Over a period of eight weeks, you have to unload as many of those mums as possible. The sales team at Macy’s has more time to move their holiday merchandise than you do.

If you’re like most operations, your inventory tracking system consists of Excel spreadsheets and notebooks that tell you what happened in previous years so you can accurately predict what will happen this year. The notebooks give you a pretty accurate idea of where in the greenhouses your six cultivars are, how many you planted and which of the five stages they are in. You already have 30 different sets of data to manage before you add on how many you sell of each cultivar and what stage they were in.

The future of the industry is making data-driven decisions that free up a grower to focus on solving problems, not looking for problems.Then your first order comes in and out the window goes any firm control of where the mums are, what stage they’re in and how many of each cultivar you have left. A couple of hours after your first order, a second comes in and by the time you get back in touch, check your inventory, call back the buyer and she’s able to connect with you, those 2837 stage 3 orange mums are moving into stage 4. Only she doesn’t want stage 4 mums she only wants stage 3 so now you frantically call around to see who wants stage 4 orange mums very soon to be stage 5 mums.

And, the answer is often no one. What if you didn’t have your inventory count exact and now you have 242 yellow mums that you just found in a different location in your greenhouse and had you known they were there, you could have sold them along with 2463 other mums that you just located in various parts of your greenhouse.

It doesn’t have to be like that. We had a client in a similar situation, and they are on track to reduce their shrinkage to just a shade over 10%. The future of the industry is making data-driven decisions that free up a grower to focus on solving problems, not looking for problems.

And don’t think that shrinkage is an issue only in the purview of floriculture. It’s an even bigger problem for cannabis because of the high value of each crop. The numbers don’t sound as bad because unlike floriculture, you don’t have to throw out cannabis that’s not Grade A. You can always sell it for extract. But extract prices are significantly less per pound than flower in the bag.

Here’s how one grower explained it. “Because of the high value of the crop, and the only other crop I’ve worked with that high is truffles, you’re playing a much higher stakes game with shrinkage. Even if you try and salvage a bad crop by using all of the parts of the cannabis plant. Listen, the difference between Grade A and Grade C could be $1,000 for A while a pound of B/C is less than $400. If you produce a standard 180 to 200 pounds in your grow rooms, you’ve really screwed up. No operator is going to keep you if you just cost them $120,000.”

VinceSebald
Soapbox

Automation – Planning is Everything

By Vince Sebald
No Comments
VinceSebald

Automation of processes can provide great benefits including improved quality, improved throughput, more consistency, more available production data, notifications of significant events and reduced costs. However, automation can also be expensive, overwhelm your workforce, cause future integration problems and magnify issues that you are currently experiencing. After all, if a machine can do work 100 times faster than a human, it can also produce problems 100 times faster than a human. Whether it is a benefit or a scourge depends largely on the implementation process.

There are thousands of possible technology solutions for just about any production problem. The trick to getting results that will work for your company is to use good engineering practices starting from the beginning. Good engineering practices are documented in various publications including ISPE Baseline Guides, but there are common threads among all such guides. What will the system be used for and what problem is it intended to solve?

The key is implementing a system that is fit for your intended use. As obvious as it sounds, this is often the most overlooked challenge of the process. In the grand scheme of things, it is a MUCH better proposition to spend more time planning and have a smooth operation than implement a system quickly and fight it because it isn’t a good fit for the intended use. The industry is littered with systems that were prematurely implemented and complicate rather than simplify operations. Planning is cheap, but fixing is expensive.

The most important step to getting an automated system that will work for you is also the first:

Defining “what” you need the system to do: User Requirements

Automation Runaway
Once automation is in place, it can be a boon to production, but don’t let your systems get ahead of your planning! It can be difficult to catch up.

With decades of experience in the automation industry, I have seen systems in many industries and applications and it is universally true that the definition of requirements is key to the success of the automation adventure. To clarify, the user requirements are intended to define “what” the system is required to do, rather than “how” it will do it. This means that persons that may not be familiar with the automation technologies can still be (and usually are) among the most important contributors to the user requirements document. Often, the people most familiar with the task that you wish to automate can contribute the most to the User Requirements document.

Some of the components of a User Requirements document typically include:

  • Purpose: What will the system be used for and what problem is it intended to solve?
  • Users: Who will be the users of the system and what is their relevant experience?
  • Integration: Is the system required to integrate into any existing or anticipated systems?
  • Regulatory Requirements: Is the system required to meet any regulatory requirements?
  • Functions: What is the system required to do? This may include operating ranges, operator interface information, records generation and storage, security, etc.
  • Performance: How many units per hour are required to process?  What percent non-conforming product is acceptable?
  • Environment: What environment is the system required to operate in? Indoor, outdoor, flammable, etc.
  • Documentation: What documentation is required with the system to support ongoing maintenance, calibration, etc.?
  • Warranties/Support: Will you perform work in-house, or will the manufacturer support the system?

The level of detail in the User Requirements should be scaled to the intended use. More critical operations may require more detailed and formal User Requirements. At a minimum, the User Requirements could be a punch list of items, but a detailed User Requirements may fill binders. The important thing is that you have one, and that the stakeholders in the operation have been involved in its production and approval.Once completed, the User Requirements can be a very good document to have for prospective providers of solutions to focus their attention on what is important to you, the customer.

Equally important to the process is the idea of not over-constraining the potential solutions by including “how” the system will meet the requirements within the User Requirements. If it is required to use specific technologies for integration with other existing systems, it is appropriate to include that information in the User Requirements. However, if use of a particular technology (e.g. “wireless”) is not required, the inclusion may unnecessarily eliminate viable design options for systems that may address the requirements.

Once completed, the User Requirements can be a very good document to have for prospective providers of solutions to focus their attention on what is important to you, the customer. This helps to ensure that they focus their efforts in the areas that match your needs and they don’t waste resources (which translate to your costs) in areas that don’t have tangible benefits to you, the customer. It also gives you a great tool to “value engineer”, meaning that you can consider cutting design options that do not support the User Requirements, which can reduce project costs and timelines, keeping things lean and on track.

Further steps in the project are built around the User Requirements including system specifications provided by vendors, testing documentation and the overall turnover package. An appropriately scaled User Requirements document is a low cost, easy way to ensure that your automated system will serve you well for years to come. Alternatively, the lack of a User Requirements document is an all-too-common indicator that there may be challenges ahead including scope creep, missed deadlines and unacceptable long term performance.


Feel free to reach Vince at vjs@sebaldconsulting.com with any questions you might have.