{"id":340,"date":"2026-07-11T00:26:20","date_gmt":"2026-07-10T21:26:20","guid":{"rendered":"https:\/\/bimpsoft.com\/blog\/?p=340"},"modified":"2026-07-13T10:09:43","modified_gmt":"2026-07-13T07:09:43","slug":"dscrete-process-manufacturing-one-system","status":"publish","type":"post","link":"https:\/\/bimpsoft.com\/blog\/en\/2026\/07\/11\/dscrete-process-manufacturing-one-system\/","title":{"rendered":"Running Discrete and Process Manufacturing in One System"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">Most manufacturing software picks a side early. Some platforms are built around discrete manufacturing: countable, assembled units with a bill of materials and a routing. Others are built around process manufacturing: a recipe, a formula, a batch that can&#8217;t be un-mixed once it&#8217;s made. Very few are built to handle a company that does both, which is a more common situation than the software market seems to assume.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A device manufacturer that assembles electronics but also formulates a protective coating. A food producer that batches a sauce and then assembles it into a packaged kit. A drone manufacturer that mixes a composite resin for the airframe and bolts together the electronics that go inside it. None of these companies fit neatly into &#8220;discrete&#8221; or &#8220;process.&#8221; They need both, in the same system, without maintaining two separate tools that don&#8217;t talk to each other.<\/p>\n\n\n\n<div class=\"wp-block-rank-math-toc-block\" id=\"rank-math-toc\"><h2>Table of Contents<\/h2><nav><ul><li><a href=\"#why-the-two-modes-dont-mix-by-default\">Why the two modes don&#8217;t mix by default<\/a><\/li><li><a href=\"#where-the-seams-show-up\">Where the seams show up<\/a><\/li><li><a href=\"#phantom-assemblies-and-formulas-that-never-touch-a-shelf\">Phantom assemblies and formulas that never touch a shelf<\/a><\/li><li><a href=\"#what-a-hybrid-capable-structure-actually-needs\">What a hybrid-capable structure actually needs<\/a><\/li><li><a href=\"#why-this-matters-more-as-you-scale-not-less\">Why this matters more as you scale, not less<\/a><\/li><\/ul><\/nav><\/div>\n\n\n\n<h2 id=\"why-the-two-modes-dont-mix-by-default\" class=\"wp-block-heading\">Why the two modes don&#8217;t mix by default<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The difference isn&#8217;t cosmetic. Discrete manufacturing produces distinct, countable units that can, in principle, be taken apart again: a screw removed, a bracket unbolted. Process manufacturing is irreversible: once flour, water, and yeast become dough, there&#8217;s no un-mixing them. That single difference cascades into everything downstream.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A discrete bill of materials is a structured list of parts and quantities, versioned, with each component traceable back to its own lot or serial number. A process formula is a percentage-based recipe, where the core planning problem is yield loss and unit conversion, not component-level traceability. Quality control differs too: discrete manufacturing checks assembly tolerances and functional tests; process manufacturing checks temperature, viscosity, and contamination. Build software around one mental model and the other one gets bolted on as an afterthought, usually with visible seams.<\/p>\n\n\n\n<h2 id=\"where-the-seams-show-up\" class=\"wp-block-heading\">Where the seams show up<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The most common failure point is the moment a discrete product contains a process-manufactured component, or vice versa. A drone&#8217;s airframe might start as a resin formula, cured into a shape, and then become one line item in a discrete bill of materials alongside the flight controller and motors. If your system treats formulas and BOMs as fundamentally different objects that can&#8217;t reference each other, someone ends up tracking that link manually, usually in a spreadsheet sitting next to the &#8220;real&#8221; system.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The same problem shows up in costing. A discrete BOM rolls cost up from individual component prices. A process formula rolls cost up from an ingredient percentage and a batch yield, which means an unexpected amount of scrap or a lower-than-planned yield changes the true cost per unit in a way a simple parts list never has to account for. A system built only for one mode tends to handle the other mode&#8217;s costing logic poorly, if at all.<\/p>\n\n\n\n<h2 id=\"phantom-assemblies-and-formulas-that-never-touch-a-shelf\" class=\"wp-block-heading\">Phantom assemblies and formulas that never touch a shelf<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Both modes share one underappreciated concept: things that exist on paper but never get stocked as a standalone item. In discrete manufacturing, this is a phantom assembly, a sub-assembly that exists in engineering&#8217;s structure for clarity but is built and consumed in the same operation, never sitting in inventory on its own. In process manufacturing, the equivalent is an intermediate batch that&#8217;s mixed and immediately consumed downstream rather than bottled and shelved.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A system that only models one of these concepts forces the other one to be faked, usually with a dummy inventory item that has to be manually zeroed out after every run. It&#8217;s a small thing until you&#8217;re running it at volume, at which point it becomes a source of phantom stock and reconciliation headaches.<\/p>\n\n\n\n<h2 id=\"what-a-hybrid-capable-structure-actually-needs\" class=\"wp-block-heading\">What a hybrid-capable structure actually needs<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Handling both modes natively means a few specific things. The bill of materials engine needs to support both a structured parts list and a percentage-based formula, and let one reference the other when a process-manufactured item becomes a component in a discrete assembly. Routings need to support both discrete operations, tied to a work center and a cycle time, and process steps, tied to a vessel, a temperature curve, and a hold time. Traceability needs to work the same way in both directions: lot-based for a batch, serial-based for an assembled unit, and able to connect the two when one contains the other.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Costing has to roll up correctly regardless of which mode produced a given input, so that a discrete product with a process-manufactured sub-component gets an accurate total cost rather than a placeholder.<\/p>\n\n\n\n<h2 id=\"why-this-matters-more-as-you-scale-not-less\" class=\"wp-block-heading\">Why this matters more as you scale, not less<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">At low volume, workarounds are cheap. A dummy inventory item here, a manual spreadsheet reconciliation there, nobody really notices the cost. The problem compounds as product lines multiply and the number of components that cross between modes grows, because each workaround is a manual step that has to be repeated correctly, every time, by someone who remembers it exists.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This is the specific gap <a href=\"https:\/\/bimpsoft.com\/en\/\">Bimp<\/a> was built to close: a single specification and routing structure that treats discrete assembly and process formulation as two expressions of the same underlying model rather than two separate systems duct-taped together. For a manufacturer whose product genuinely crosses both, that&#8217;s less a nice-to-have and more the difference between a system that reflects how the product is actually made and one that requires a workaround for half of it.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Most manufacturing software picks a side early. Some platforms are built around discrete manufacturing: countable, assembled units with a bill of materials and a routing. Others are built around process manufacturing: a recipe, a formula, a batch that can&#8217;t be un-mixed once it&#8217;s made. Very few are built to handle a company that does both, [&hellip;]<\/p>\n","protected":false},"author":3,"featured_media":329,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[79],"tags":[],"class_list":["post-340","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-vyrobnytstvo-en"],"acf":[],"_links":{"self":[{"href":"https:\/\/bimpsoft.com\/blog\/wp-json\/wp\/v2\/posts\/340","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/bimpsoft.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/bimpsoft.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/bimpsoft.com\/blog\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/bimpsoft.com\/blog\/wp-json\/wp\/v2\/comments?post=340"}],"version-history":[{"count":4,"href":"https:\/\/bimpsoft.com\/blog\/wp-json\/wp\/v2\/posts\/340\/revisions"}],"predecessor-version":[{"id":383,"href":"https:\/\/bimpsoft.com\/blog\/wp-json\/wp\/v2\/posts\/340\/revisions\/383"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/bimpsoft.com\/blog\/wp-json\/wp\/v2\/media\/329"}],"wp:attachment":[{"href":"https:\/\/bimpsoft.com\/blog\/wp-json\/wp\/v2\/media?parent=340"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/bimpsoft.com\/blog\/wp-json\/wp\/v2\/categories?post=340"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/bimpsoft.com\/blog\/wp-json\/wp\/v2\/tags?post=340"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}