This post briefly describes what data partitions are and what they can be used for, but most importantly, when you should NOT use them.

In short:    Data partitioning allows for the complete isolation of your application data between organizational boundaries.

What does that mean to you:

You cannot share any data across these boundaries. As far as application data is concerned, these partitions might as well run on different systems. If there is a need for business data to cross these boundaries, you should not use partitions but instead use the capabilities of the organizational model.

Data required by the system is being shared across partitions. The most prominent example is the data for AIF and batch processing. Metadata is being shared across partitions, which means you will run the same codebase for all partitions. Any customization will be available in all partitions.

For a more detailed description of data partitions, refer to these Microsoft TechNet links:

Potency is the concentration of an active ingredient and is typically expressed as a percentage of a batch or as a multiple of the standard or usual potency.

Process manufacturers purchase products that have a certain active ingredient; for example, a drum of raw material whose potency is 75 percent means that 75 percent of the material in the container is active. The balance is filler or an inactive ingredient such as water or some other stabilizer that makes storage, use and transfer of the active ingredient safe and possible.

What manufacturers really care about is how active the ingredient is: its potency. Process manufacturers pay their raw materials vendors based on the concentration of what they receive. All production recipes are based on a specific nominal concentration of the material being used; inventory is valued based on concentration.

Fullscope’s Process Accelerators for chemical, food and beverage and life sciences industries extend ERP system Microsoft Dynamics AX by adding a number of fields around potency to improve its definition and automate its use in the manufacturing process. Key among these fields is “base attribute,” a generic term that refers to the key active characteristic of the product. Another is whether the attribute is fixed (i.e., can it or can it not be altered after the value of the base attribute is set?). A third is “adjustment principle,” which indicates which type of potency calculation or concentration adjustment (difference additive, compensating ingredient, or filler) has been used for the recipe. Finally, how the attribute value is to be recorded (e.g., inventory receipt or lab verification) is documented.

At the formula level, the Process Accelerators allows a target concentration to be set with the Dynamics AX ERP system. If what is available in inventory does not meet the established concentration of the recipe during batch production, the Process Accelerator will suggest adjustments accordingly based on the actual concentration of the selected active ingredient.

In the process industries, there are three types of concentration adjustments: one is called “difference additive,” simply consuming more or less of a material based on its concentration; a second is called “compensating ingredient,” where a quantity of a second ingredient is added according to whether the concentration of the active ingredient is over or under specification. (For example, water is added to compensate for the level of acidic acid in vinegar production.)  The third adjustment is simply adding “filler.”   Consider prescription medication. An ibuprofen capsule may need to be 300 mg, but the active ingredient (i.e., ibuprofen) is not 300 mg. Filler is added to the active medicinal ingredient to comprise the 300 mg capsule.

Fullscope Process Accelerators use this information to provide Batch Balancing to speed and improve production. In Dynamics AX ERP, a batch formula is defined interactively based on the concentration of a key ingredient or ingredients. The Process Accelerator picks inventory lots based on current potency, automatically calculates the required active ingredient, determines the quantity needed for the compensating ingredient or filler, and finally creates a material consumption transaction based on the adjusted formula.

This is a very common scenario in the food industry, where, for example, a manufacturer is producing a batch of yogurt. If the butterfat content of the milk is more or less than required, a quantity of water or skim milk needs to be added. For a host of reasons, companies don’t want the operator to have to do the math for that calculation. Therefore, the Process Accelerators automate the process and makes it simple for the operator to come up with a properly balanced set of ingredients. As each batch is launched, each Process Accelerator provides a screen for the operator that shows every ingredient and its actual concentration. It shows batch number, quantity, and attribute value. Depending on which inventory batch or lot is selected, when the operator hits a button to balance batch ingredients, the system automatically rescales the formula based on the lots selected. This procedure helps ensure quality, reduce costs, and eliminate waste.

Watch Next Month for:  Potency Pricing, Lot Genealogy and Traceability, and Product Sequencing

When creating an Alert in Microsoft Dynamics AX ERP software, the field where you initially create the Alert affects your options when defining the Alert. For example, if you start defining the Alert on a date field, the options displayed are related to dates: “has been postponed until at the earliest,” “is set to an earlier date,” and “is due.” For numeric fields, available options include: “has decreased,” “has increased above,” and “has decreased below.” Alphanumeric fields options are “record has been created,” “record has been deleted,” “has changed,” and “is set to.”