Choosing process and batch software: test formulas, yields and genealogy

A process-manufacturing shortlist should begin with one familiar batch, its formula revision and the records created around it. Prepare a synthetic example rather than upload confidential recipes during early sales demonstrations. Include a normal run and an exception that currently forces people into spreadsheets. The purpose is to test decisions and records, not to collect attractive dashboard screenshots.

Separate the formula from the package

Describe whether a bulk product becomes several pack sizes, whether intermediates feed later batches, and which unit conversions people use. Ask the demonstrator to scale a recipe and change one permitted ingredient. Identify who can approve the change and which revision remains attached to the completed batch. An experimental formula should not become a production instruction accidentally.

BatchMaster’s production documentation describes linked batch jobs and adjustments to formulas and packaging bills. Vicinity describes a Dynamics extension for formula-driven production. These establish examples of vendor scope, not evidence that every edition handles your exceptions.

Follow actual quantities and costs

Use different planned and actual outputs. Account for ingredient losses, partial containers, by-products and rework where they occur in your plant. Ask how the system records the discrepancy and whether a later adjustment changes historical cost. Require the demonstrator to explain the denominator used for yield: purchased weight, consumed quantity and saleable output answer different questions.

Separate production costs from selling price. Material, labor, overhead and packaging allocations should have documented rules. Compare proposals only after establishing what each quoted module calculates and what remains in another system.

Trace a held ingredient and a split shipment

Receive two ingredient lots, place one on quality hold and attempt to allocate it. Then produce a batch using the released lot, divide it into finished outputs and ship to two customers. Trace one ingredient forward and one shipment backward. Inspect corrections, permissions and links to test results. A traceability screen does not itself establish regulatory compliance; the organization must define and validate its required procedures.

Finish with the system boundary

Identify who owns purchasing, inventory, production and financial postings. For an ERP extension, document the exact host product and supported versions. Request the connection method, error handling and support owner for every handoff.

Conclude with a bounded pilot and a linked export of formulas, revisions, consumption, outputs and quality records. Record unknown requirements explicitly. Written implementation scope, migration effort and ongoing operating costs belong beside the feature comparison before a purchasing decision.