Manufacturing & Operations covers the full arc from product definition to production settlement. At its foundation is a governed item master holding every raw material, component, sub-assembly, finished good, phantom grouping, consumable and packaging item a business handles, each with specifications, revision state, make-or-buy designation, weights, lead times, safety stock and standard cost. On top of this sit multi-level bills of materials, held as engineering, manufacturing, as-built and service variants with effectivity windows, and routings that describe the operation sequence, setup and run times, and work centre for each step of production.

The module plans and executes against those definitions. Material requirements planning explodes demand through the BOM, nets it against stock and open supply, and proposes make, buy and transfer actions. Work orders instantiate a BOM and routing into a live production order with a controlled status lifecycle. Shop floor control captures operation start and completion, material issue, scrap and time. Production scheduling produces Gantt-ready plans by work centre with automatic conflict detection, while capacity planning surfaces bottlenecks and runs what-if simulation. Quality inspection governs incoming, in-process and final checks, and multi-warehouse bin management with stock transfers keeps inventory positions accurate. Cost roll-up ties the whole structure back to a defensible unit cost.

The conceptual heart of the module is the distinction between an item defined once and an item used many times. Every part, however often it appears, exists as a single master record; each place it is consumed is a reference to that record rather than a copy. Change the description, specification or cost of a resistor used in fifty assemblies and the change is felt everywhere at once, with no duplication to reconcile. This reference-and-instance relationship is what makes a large product portfolio tractable.

A bill of materials expresses how items combine into something larger. It is inherently recursive: a finished good contains sub-assemblies, which contain further sub-assemblies, down to raw material, and the structure is walked both downward to explode a product into its components and upward to answer where a given part is used. Because the same parent can be described more than one way for different purposes, each BOM is a distinct version carrying its own effectivity dates and approval state, so engineering intent and shop floor reality can differ deliberately and traceably.

Alongside structure sits process. A routing defines the ordered operations that turn components into the parent, each operation tied to a work centre with finite capacity. Around both, the sourcing picture is captured through manufacturer parts and an approved vendor list, recording who makes and who supplies each item, at what price and lead time, and in what standing. Overlaying everything is revision and change control: items and structures carry a revision history, and any deliberate change flows through a formal engineering change order that records what is affected and who approved it.

Product introduction begins in the item master, where a new part receives a system-generated, non-descriptive part number and its specifications, category, unit of measure and initial revision. Engineers then assemble its bill of materials line by line, attaching quantities, reference designators, approved substitutes and find numbers, with circular references prevented at entry. A cost roll-up is triggered to sum component costs bottom-up through every level, honouring make-or-buy sourcing and preferred vendor pricing, and the resulting unit cost is cached against the BOM version.

Change is handled through the engineering change order. A proposed change is raised against the affected items, routed through a role-based approval chain, and on approval implemented so that item revisions advance and the change is recorded against the structures it touched. Production runs its own cycle: demand from sales orders and forecasts is planned through MRP, planned orders are firmed into work orders that explode their material and operation requirements, and those orders move through release to the shop floor. Operators start and complete operations, issue and back-flush material, and report scrap; the order promotes itself through in-progress to complete as its operations finish. Quality inspections gate incoming, in-process and final stages, and stock transfers move material between warehouses and bins as production consumes and replenishes it.

The module carries the depth that separates a real manufacturing system from a parts list. Bills of materials are genuinely multi-level and indented, with quantities cascaded correctly across sub-assembly boundaries and a materialised path that makes subtree retrieval and where-used impact analysis fast even on deep structures. Phantom assemblies are handled properly: they exist in the engineering view for logical grouping and appear in work instructions and cost roll-up, yet are transparent to material planning and procurement, so they never generate spurious demand.

Costing is multi-element and multi-currency. Material, labour, overhead and tooling are tracked separately per item with effectivity dates, rolled up bottom-up into a full cost breakdown per BOM version, and converted to a base currency using the same exchange rate source the finance modules use, so a manufactured cost reconciles to the ledger. Quality inspection records per-characteristic measurements against specification limits and derives pass or fail automatically, supporting incoming, in-process and final regimes. Units of measure are first-class, with defined conversion factors so a component bought by the kilogram and consumed by the gram is always reconciled. Approved vendor lists carry a standing lifecycle from approved through conditional to disqualified, with preferred-vendor selection feeding costing, and manufacturer part numbers preserve the cross-reference between an internal item and the specific parts the market actually sells, including discontinued and not-recommended-for-new-design status.

The module is deeply wired into the rest of the suite rather than standing apart. Its tightest relationship is with Accounting & Control: item master parts map to inventory, approved vendors resolve to suppliers, procurement against the vendor list raises supplier invoices, and work order completion posts the consumed material and labour as cost of goods sold and work-in-progress journal entries, so production activity valued on the shop floor lands in the general ledger without re-keying.

Commercially, it connects to Marketing & Sales, where accepted quotes and customer orders reference manufactured items and become the demand signal that MRP plans against, with quote approval and workflow automation upstream of the work order. It draws on Business Relations so that manufacturers and vendors are the same companies and contacts the CRM already knows. Engineering drawings, datasheets, specifications and change-order supporting files are held in Document Management and linked to items and ECOs rather than duplicated. And through the suite's finance bridges it participates in intercompany elimination, tax and revenue automation, so a group that manufactures across legal entities sees consolidated, correctly eliminated results.

AI Workers are first-class users of the module, not a bolt-on assistant. They answer conversational questions against live production data, resolving requests such as which assemblies use a part flagged as not recommended for new design, which work orders are behind on a bottlenecked work centre, or how a proposed substitute changes rolled-up cost, and they execute actions directly: raising a work order from a BOM, triggering a cost roll-up, firming a planned MRP order, or initiating a stock transfer to cover a shortage.

They monitor continuously for the exceptions that matter, flagging capacity overloads above threshold, material shortages against released orders, quality results outside specification limits, and preferred-vendor price movements that shift a product's cost. They read documents, extracting part attributes, prices and lead times from datasheets and vendor quotations into the item master and approved vendor list. They provide decision support by simulating capacity what-ifs and comparing cost across BOM versions. And they act as named nodes in the module's governed workflows: an AI Worker can sit in an engineering change order approval chain or a quality disposition, applying encoded rules, approving what is clearly within policy and escalating what is not, with every action recorded under its own identity in the same audit trail as any human approver.