Help › Production › Engineering

Engineering Change (ECN) and Product Configurator

1. What it is for

The Engineering window puts the product's technical definition (BOM, routing, technical drawing, work instruction) under control. A revision in effect cannot be changed in place; every change is made through an ECN (engineering change notice): draft → impact analysis → review and approval → in effect (new BOM version) → closing. The same window holds the product configurator: choosing colour/size/motor/options derives a rule-checked product code, BOM and price, which is added to a quotation or order as a line.

The window has four tabs: Changes (ECN) · Product revisions · Configurator · Configurator models. In the dock, as Engineering / Configurator, it sits in both the Production and the Sales group. The stock card also gets a Revisions tab.

2. ECN flow

• Draft: enter the title, change type (BOM, routing, drawing, specification, card field, mixed), reason (customer request, cost reduction, quality, supply problem, regulation, improvement, other), affected products, changeover rule and change lines. The number comes from the document series (ECN{yyyy}{0000}, e.g. ECN20260001). Only a draft can be edited.
• Change lines: replace / add / remove component, change quantity, replace / add / remove operation, technical document (new file, optional operation sequence) and card/specification field.
• Send for review: needs at least one line; the impact analysis is calculated automatically. If the ECN approval rule (ecn) is defined, a request opens in the Approvals queue.
• Approve / Reject: single approval (engineering approval permission) or the approval chain written on the ECN (users in order). Rejection needs a reason and returns the ECN to draft.
• Put into effect: an approved ECN writes the new BOM version (see §4). Close archives an ECN in effect; Cancel is for a draft or an ECN in review.

3. Impact analysis

The impact panel shows what the change touches today: open sales orders, open work orders, open supplier orders, the old component's stock and its value, affected framework contracts, other products using the old component outside the ECN (where-used) and the cost impact per unit / for the open quantity. It is a snapshot: the time and person are written; recalculate with Calculate impact when data changes. It is calculated automatically when sent for review; it is not recalculated for an ECN in effect or closed.

4. Going into effect and the changeover rule

An ECN put into effect does not change the current BOM of each affected product; it writes a new BOM version (variant differences are copied, technical documents move to the new revision) and moves the product's revision one letter forward (Rev.A → Rev.B). New work orders take the new version; open orders continue with the old version (a work order freezes its BOM when it is opened). The old version is archived.

• Immediately: can be put into effect right after approval.
• When the old component's stock is used up: while the old component has stock, putting into effect stops with 409; do it when the stock is used up or deliberately (deliberately put into effect before the old stock is used up). Meanwhile MRP marks new purchase proposals for the old component with an "ends with ECN" warning.
• From a specific lot: the starting lot is required (recorded for information).
• If an effective date is entered, the ECN cannot be put into effect before that date (409). When the date comes, it is put into effect by hand.

5. Revision lock

A product is put under engineering control with Start revision: its current active BOM becomes Rev.A. Technical documents can be added to the draft initial revision and it can be put into effect directly (only the initial revision goes into effect without an ECN). Once a revision is in effect that BOM is locked: saving in place on the Production › BOM screen, deleting the BOM, writing/deleting variants are rejected by the server with REVIZYON_KILITLI (422). BOMs of products not under control are changed freely as before.

6. Technical documents and work instructions

Technical drawing, work instruction, specification, PFMEA and process flow files are uploaded to the shared attachment store and bound to the revision; the binding is kept by operation sequence (0 = whole product), so it lands on the right operation even when the BOM version changes. The work order traveler prints a "Technical documents — Rev.X" section. For MES and the shop floor, GET /api/muhendislik/op-belge?emir=&op= returns the work instruction and technical drawing of the revision of that order's frozen BOM; on a phone, Engineering › Work document uses the same endpoint.

7. Product configurator

On the Configurator tab choose a model and tick the features. On every selection the server checks the rules (incompatible / requires) and shows the derived product code (code template + value code suffixes, at most 30 characters), the description, the derived BOM (rule BOM effects applied to the base product's active BOM), the price (base price or price engine + value effects, price source konfig), estimated cost/margin and the delivery promise (ATP). Save: a stock card and BOM are created and the product goes straight under engineering control (Rev.A); optionally a quotation or order is opened too. If the same selection is saved again the same code is used (no new card).

On the quotation and order entry screens the Configure button on the toolbar opens the configurator; the saved configuration is added to the open document as a line. The B2B portal can configure through the same API (/api/muhendislik/konfig/*).

8. Model designer

• Model: code, name, product family, base product (template BOM), base price (0 = price engine), code template (e.g. {aile}-{renk}-{motor}{opsiyon}) and description template.
• Features: code, name, single or multiple choice, required.
• Values: code, name, code suffix, price effect (amount or percent).
• Rules: the condition is written as feature=VALUE; a comma means AND, a vertical bar (|) means OR. Incompatible: condition and result cannot be chosen together. Requires: when the condition is chosen the result is required too. BOM and price rules add/remove/replace a component or change the price when the condition holds.
• A semicolon (;) cannot be used in text fields.

9. On a phone

On a narrow screen Engineering becomes three tabs: Configure (4-step wizard: model → selections → summary → save / quotation / order), ECN approvals (cards of ECNs awaiting approval or to be put into effect: Approve / Reject / Put into effect) and Work document (enter a work order and an operation sequence to open that operation's documents).

10. Permissions

In the role templates the Production role gets muhendislik and the Sales role gets konfigurator. An administrator can do everything. Every write is recorded in the audit log (muhendislik-audit.jsonl) and in the ECN trail.

11. FAQ and messages

Why does an old order use the old component? A work order freezes the BOM at the moment it is opened; an ECN does not change open orders. The new component comes with new orders. Was an ECN number skipped? Numbers are never reused; the number of a deleted or cancelled ECN stays empty.

Related guides: Production · MES · Planning · Delivery Promise · Pricing · Stock card · Mobile.