Manufacturing
| Site: | Learn at Merupu AI |
| Course: | SamvraCore ERP |
| Book: | Manufacturing |
| Printed by: | Guest user |
| Date: | Tuesday, 27 October 2026, 7:30 AM |
Description
Bills of materials, work centers and production work orders.
1. The Manufacturing Module at a Glance
SamvraCore ERP's Manufacturing module turns raw materials and components into finished products through three connected building blocks: the Bill of Materials (BOM), Work Centers, and Work Orders. These are surfaced in the frontend through BOMListPage and BOMDetailPage, WorkCentersPage, and WorkOrdersPage with WorkOrderDetailPage.
The BOM defines what goes into a product, work centers define where and with what resources production happens, and work orders manage the actual production runs. Work orders combine routing, material issue, and operation tracking, tying the material definition and the resource definition together into a run that can be executed and tracked.
The backend exposes these through manufacturing endpoints for the bill of materials and its components, for work centers, and for work orders, including explicit actions to start, complete, and cancel a work order. This structure mirrors a conventional discrete-manufacturing model: engineering maintains BOMs, operations maintains work centers, and the shop floor executes work orders.
A typical lifecycle: an engineer defines a BOM for a finished product listing its components and quantities; operations sets up the work centers that will perform the production; and when demand arises, a planner creates a work order, optionally from the BOM, and advances it through its status workflow as the product is built. Each block is reusable, so one BOM and one set of work centers support many work orders over time.
2. Defining a Bill of Materials
A Bill of Materials defines a product's assembly structure: the components required to build a finished item. In SamvraCore each BOM lists its components, and every component line carries a quantity and a unit of measure, so the BOM states precisely how much of each input is needed and in what units.
A BOM also has an active or inactive status. This lets an organisation retire or supersede an assembly definition without deleting it, keeping historical BOMs available while directing new production to the current active version.
BOM components are managed through dedicated endpoints under a BOM, so components can be added and maintained as a child collection of the parent BOM. The BOMDetailPage provides the detailed view where this component structure is seen and edited, while BOMListPage gives the overview across all defined BOMs.
A worked example: a finished assembly is defined with several component lines, each naming a component product, the quantity consumed per finished unit, and the unit of measure for that quantity. Once complete and marked active, this BOM becomes the recipe that work orders draw on. If the design changes, a revised BOM can be created and activated while the old one is marked inactive, preserving the record of how earlier units were built.
3. Multi-Level BOMs and Material Cost
SamvraCore's Bill of Materials supports more than flat single-level recipes: it provides multi-level BOM support through sub-assemblies. A component of one BOM can itself be a manufactured item with its own BOM, allowing complex products to be modelled as a hierarchy of assemblies and sub-assemblies rather than one long flat list.
This multi-level structure mirrors how real products are built, where major sub-components are assembled first and then combined into the final product. Modelling sub-assemblies explicitly keeps each level's component list focused and reusable, since a common sub-assembly can appear in several higher-level products.
The BOM also provides material cost calculation. Because each component line specifies a quantity and unit of measure, the BOM can roll up the cost of the materials that make up the product. This gives a material-cost view of the assembly derived from its component definition.
A worked example: a finished product's BOM references a sub-assembly as one of its components; that sub-assembly has its own BOM listing its parts and quantities. The multi-level structure lets the finished product's definition stay concise while the full component breakdown is still captured through the nested sub-assembly, and material cost calculation reflects the components consumed.
4. Work Centers as Manufacturing Resources
Work Centers define the manufacturing resources that carry out production, managed through the WorkCentersPage. A work center represents a station, machine, or group of resources where production operations are performed.
Each work center tracks capacity and efficiency, giving a measure of how much the resource can process and how effectively it operates. Work centers also carry cost rates per hour, so the time spent in a work center can be associated with a cost. Like BOMs, work centers have an active or inactive status, allowing a resource to be taken out of planning without being deleted.
Work centers are assigned to work orders: a production run references the work center or centers where its operations take place. This connects the resource definition to actual production, so the organisation knows which resources a given work order consumes.
A worked example: an organisation defines several work centers, each with its capacity, efficiency, and hourly cost rate. When a work order is created, it is given work center assignments that determine where its operations will be executed. A work center that is being serviced or decommissioned can be set to inactive so planners do not route new work orders to it, while its historical assignments remain intact.
5. Work Orders and Their Status Workflow
Work Orders manage production runs and are the execution layer of the Manufacturing module, surfaced in WorkOrdersPage and WorkOrderDetailPage. A work order can be created from a BOM so it inherits the assembly definition, or created manually when needed.
Work orders follow a defined status workflow: Draft, then Confirmed, then In Progress, then Completed. A work order starts in Draft while it is being prepared, is Confirmed when it is ready to proceed, moves to In Progress once production begins, and reaches Completed when the run is finished. The backend provides explicit transition actions to start, complete, and cancel a work order, so these status changes are driven through dedicated operations rather than free-form edits.
During a run, a work order supports production quantity tracking, recording how much has been produced, and it carries work center assignments that place its operations on specific resources.
A worked example: a planner creates a work order from a finished product's BOM, leaving it in Draft while details are confirmed. The work order is then confirmed and, when the shop floor begins building, started so it moves to In Progress. As units are built, production quantity is tracked against the order. When the run finishes, the work order is completed; if the run must be abandoned, it can instead be cancelled through its dedicated cancel action.
6. Material Consumption, Routing, and Operation Tracking
Work orders are where the BOM and work centers come together on the shop floor. A work order supports routing, material issue, and operation tracking, describing the sequence of operations, the issuing of materials to the run, and the progress of those operations.
Material handling is captured through material issue and material consumption tracking. As a production run proceeds, the components defined in the BOM are issued to the work order and their consumption is tracked, so the materials used by a run are recorded against it. This connects manufacturing to the inventory module, where issuing stock to consumption is one of the recognised stock movement types.
Operation tracking follows the individual operations that make up the run, and routing defines how the work moves through the assigned work centers. Together these let an operator see what has been done and what remains for a work order.
A worked example: a confirmed work order is started and its materials are issued according to its BOM; as operations are performed at their assigned work centers, operation tracking records progress and production quantity accumulates. Material consumption is tracked against the order so the actual inputs used are known, and when all operations are finished the work order is completed. Because work centers carry hourly cost rates and the BOM supports material cost calculation, the run links both resource time and material inputs back to the production it delivered.