From master data to the work order,
one system of record for production

OMENTA is a web-based manufacturing ERP for manufacturers. It is set up on the plant's production model and keeps master data, product definitions (bill of materials or specification), production resources (work centres, operations, capabilities, calendar, SOPs), sales and purchase orders and work orders in one system of record. It publishes its data for planning to OPLAN, Grupas's planning application.

The production environment is chosen at set-up: discrete only, process only or mixed. Each item card carries its own production strategy (MTS make-to-stock, MTO make-to-order, ETO engineer-to-order). Operations have one of five process flow types — discrete, batch, continuous, line and project — and if a product's SOP mixes several, the product is made in mixed mode. 13 sector profiles (metal, plastics, food, textiles, chemicals, automotive, machinery, electronics, furniture, packaging, pharma, building materials, general) suggest defaults and product attribute templates.

The identity of products such as coils, profiles or bars is their own specification: alloy, temper, dimensions, tolerance. Attributes are defined once in the dictionary; a product template sets which attribute is asked in which order and from which pattern code and name are derived. On the variant screen you pick axis values, preview the combinations and create up to 500 cards in one run. A BOM line can link to material by a specification condition instead of a code (ALASIM=3003; KALINLIK>=0,5); the work order then finds the items that meet it.

OMENTA is the system of record (master data, orders, work orders), OPLAN the planning system. Data flows one way: OMENTA publishes 23 data sets through its token-protected data service and OPLAN pulls them at start-up. The one exception is the delivery date: OPLAN proposes a confirm date based on capacity; the proposal moves the line to "awaiting approval" and the order only becomes firm when sales approves it. OMENTA also works without OPLAN: confirm dates can be entered manually or by CSV.

An order line has two dates: the wish date sales received from the customer and the confirm date planning can give. The line first waits in Customer Requests; with a confirm date it moves to Awaiting Approval, on sales approval it drops into Orders To Plan and once a work order is opened it appears in Active Work Orders. The stage is derived from these fields; if the confirm date changes, the sales approval drops and is requested again.