PLM

Plannedapp.erp.io/plm/changes

Change control

ECR, ECO, deviations, approvals and the change calendar appear in the sidebar. There is nothing behind them yet.

State
Not built
In the nav
Yes — misleadingly
Date
None committed
Meanwhile
Baselines and compare

What is there today

Nothing. The change section of the navigation — My Approvals, ECRs, ECOs, Deviations, Change Calendar — leads to placeholder pages. They exist because the navigation was built for the finished module and the sections are being filled in one at a time.

app.erp.io/plm/changes/ecos
Engineering change orders
Not built yet

This section is named in the navigation and has no behaviour behind it. Use baselines and structure compare in the meantime.

Not built yet
What the change section looks like today. The navigation is real; the page is a placeholder.

What change control would do

For clarity about what is missing rather than as a promise: change control is the process that takes a proposed change to a released product, routes it for review, records the decision, and applies it in a controlled way with an effectivity date. A change request proposes; a change order authorises and executes; a deviation permits a temporary departure without changing the design.

The reason it matters is that without it, a released structure can be edited by anyone at any time and the record of what the product used to be depends entirely on whether somebody remembered to take a baseline.

What to do in the meantime

  1. Baseline before and after any significant change. It is the only durable record of what a structure was. See Baselines.
  2. Use structure compare to produce the change list. It gives you the *what*; you supply the *why* and the *who approved it*.
  3. Run the approval outside the module. A work order in the Client Portal, a task in Projects, or a signed document in Sign — all of which record an approver and a date.
  4. Do not treat the placeholder screens as a queue. Nothing arrives in them.
If change control is a regulatory requirement for you, this module does not meet it

A controlled design process with recorded approvals and effectivity is a hard requirement in several industries. erp.io PLM does not provide one today, and no combination of baselines and tasks is equivalent to one for audit purposes. That is a reason to choose a different tool for that part of your process, and it is better to know now.

What this does not do

No ECR or ECO objects

Not built.

No approval routing

Not built.

No effectivity dates

Not built — and a prerequisite for real change control.

No change calendar

Not built.

No audit-grade design history

Baselines are snapshots, not a controlled record.

Questions

Is there a date?

No committed date. Ask before planning around it.

Will the placeholder pages be removed?

They are being replaced section by section as each is built.

Can we get change control elsewhere in the suite?

Not equivalently. Approvals exist in other modules; controlled engineering change does not.