Dynamics ERP for Craft Beer Production

Craft brewers have a number of system requirements that are typical of many manufacturers looking to deploy an ERP system: material planning, cradle to grave lot traceability, bar-codes for materials handling, production scheduling, etc. However, there are many business processes that are very unique to this burgeoning industry. As breweries begin to grow in size and sophistication, they encounter an increasing need to start managing and controlling their unique processes within the ERP system, as opposed to relying on manual and home-grown systems.

With eight years of experience working in this arena, Tridea has partnered with our clients to solve a number of these unique challenges by utilizing tools available within the Dynamics ERP software systems.  Below are a few examples of requirements that craft brewers may face, along with the solutions to those challenges. 

Tracking Barrel Aged Beer

Small batches of special beer creations are often aged in barrels, which may be stored in a warehouse for extended periods of time and even transferred to different locations prior to being packaged and made available for sale. As the size of a “barrel program” grows, it can be challenging to keep track of:

1) What beer is currently stored in which types of barrels?

2) Where the barrels are located?

3) What types of beer have passed through a given barrel in the past? (thus establishing a “flavor profile”)

With Dynamics AX, we have used the concept of “License Plate Numbers” (LPNs) to assign a unique ID to each of these barrels. We can then track the beer that is assigned to an LPN, track the location and movements of the LPN, and also see a history of how many times a barrel has been used and what types of beers were stored in the barrel.

 

Blending of Batches in a bright tank (“brite tank”)

Bright tanks are where clarified beer is stored after it has been filtered and before it gets bottled or placed in a keg / cask.  It is not uncommon for a quantity of beer from one production batch to remain in a bright tank when a new production batch is added to the tank. As a result, two separate batches of beer that would ordinarily be tracked with two distinct lot numbers, have now effectively become blended into a single “combined” batch, which is then packaged and sold to customers. We have developed an automated routine to merge these batch numbers to reflect the blending of the beer in the bright tank, allowing for a more accurate and true lot traceability.

 

Batch Processing Resulting in the Production of Both Filtered Beer and Unfiltered Beer

In some cases, during the course of producing a filtered beer, a quantity of unfiltered beer is taken out of the tank prior to filtering. Sometimes, this might even be a last-minute decision that is made after the production order has been started. This unfiltered beer might then be barrel-aged or have special ingredients added to it in order to produce a batch of a special limited offering product. Because the process manufacturing functionality within Dynamics AX allows for the creation of co-products on a single production order, we can easily use one production order to produce both the unfiltered and filtered beer, and accurately track them as two distinct products.

 

Integration to Brewing Systems

Because brewers need to swiftly make decisions about which brew systems, fermentation vessels, and bright tanks to use, it is important for them to interact directly with the ERP system if we are to maintain timely and accurate information about the production process. Leveraging MS Dynamics’ strong integration tools, we have been able to build integration points that can take direct feeds from the brewing system (example: quantities of malt that flow into the brew system from a silo can feed directly to the ERP production order, quantities of filtered beer flowing through a filter outlet into a bright tank are fed directly to the production order). We have also built touch-points allowing for brewers to manually record transactions in the brewery floor systems that then get integrated to the ERP system.

 

This article was written by Matthew Boese, Partner at Tridea Partners, a Gold Certified Microsoft Dynamics Partner serving Southern California.

Document Management, ERP and the Life Sciences Industry

We were recently engaged by one of our Microsoft Dynamics ERP clients in the life sciences industry to help them evaluate document management systems.  Going into the meeting, I didn’t know what to expect for the key requirements as document management can mean so many different things to so many different people.  Furthermore, depending on the function or department asking the request, it can have different meanings; we were meeting with the executives from the sales, contracts and finance teams.  Finance often looks for automated purchasing and AP document management, while sales is looking to manage different contracts and agreements, and regulatory needs to implement an electronic document submission system.  We often see that the human resources team also has their unique requirements for document management.  As the meeting unfolded, the CFO was truly interested in purchasing a platform that could not only support this team’s roles and document management requirements, but also expand to other departments and create efficiency by becoming “paperless” throughout the organization.  As the conversation ended, we saw the same common themes that surround document management requirements for the life sciences community including the following:

Compliance – Getting a document management system that has been or can easily be validated.  For life sciences companies this process is otherwise very time consuming and costly as they need to comply with FDA regulations including cGMP and 21 CFR Part 11.  This is true for their ERP system as well.

Workflow – By removing paper and manual processes, the workforce can get things done much quicker and be much more efficient as opposed to pushing paper.

Document Submission – Very unique to the industry and very important to the FDA, life sciences companies are concerned about adhering to proper electronic document submission policies and formats when submitting regulatory documents for FDA approval.  Therefore, the document management system needs to address this requirement or at least be compatible with this process.

Collaboration – Today’s organizations have many different software systems producing many different forms of information, including the ERP system.  Therefore it is increasingly important to be able to view, share and interact with this important information.

Compatibility – All companies have a host of other applications used in their everyday business processes, most notable their ERP and business applications.  The document management system needs to integrate well with these processes as it’s inevitable that many of them will begin or end at this document management system.

Our team at Tridea Partners has seen many of these projects and there are many different systems to address the needs in today’s market.  When selecting that enterprise document management system, all of the above requirements should be reviewed.

Written by Andy Collins, Partner at Tridea Partners. Tridea Partners is a Microsoft Dynamics Gold Certified Partner Seriving the Southern California and Salt Lake City regions.