Overview
Plants
Families
Items
ECOs
Impacts
Record open

What it is

An app for product engineering change at a group with several plants.

Organize ECOs for BOM, process and specification, the impact by plant, approval by engineering, quality and planning, and the ERP item code, through an impact matrix, the ECO pane, an approval record, and linked profiles.

Who it's for

  • Industrial groups with several plants and a shared product file
  • Product engineering managers who open and lead the ECO
  • Quality and planning teams that issue a review and follow the rollout
  • Plant engineering teams that log the local impact

What you can do

  • Register plants, families and items, with an ERP code
  • Open an ECO for a BOM, a process or a specification
  • Log each plant's impact (low, medium or high)
  • Send the approval chain across engineering, quality, planning and the plants
  • Follow the rollout of the change at the plants
  • See the impact matrix (ECO by plant) and open the ECO pane with items and reviews
  • Follow deadlines on the calendar and each owner's load

App features

Product Engineering Change

The Product Engineering Change screen covers this part of the operation.

How it works

Set up plants, families, items and the engineering team.

Open the ECO with the change type and the items.

Each plant logs the impact.

Engineering, quality and planning issue the review and, after approval, the rollout is followed through close-out.

Indicators come from numeric fields on the ECOs table itself.

How to set up this template

  1. 1
    Click Use App

    Create your Jestor account and install Product Engineering Change. It works on desktop and mobile.

  2. 2
    Set up plants

    Set up plants, families, items and the engineering team.

  3. 3
    Open the ECO with the change type and

    Open the ECO with the change type and the items.

  4. 4
    Each plant logs the impact

    Each plant logs the impact.

Integrations and customization

The design supports desktop and mobile use. Plants, families, change types, impact levels and approval levels can be adapted to operations. No ERP master data for customers and suppliers, construction drawing revision, IT change, quality corrective action, SLA engine, ERP or PDM connector, or external integrations are included. ERP item and BOM codes are entered as text.

  • Adjust fields, categories, statuses and rules without code.
  • Add screens, reports and automations as the operation needs them.

And that's just the start: you can edit any part of this template and go much further just by asking Jestor's AI. Describe what you need, like a new field, automation, report or integration, and the AI builds or adjusts it for you, no code required.

Frequently asked questions

Do KPIs cross tables?

No. Indicators use only the ECOs table.

Does this app replace ERP master data or the construction drawing register?

No. It organizes product engineering change (BOM, process and specification) across plants. Customer, supplier and cost-center master data, and construction design revision, belong to other flows.

Is this app an IT change or a CAPA?

No. The ECO covers the product and the industrial process, with no system ticket and no quality corrective action.

Does the Review button change the status of the ECO?

No. In this design, the button only opens the detail or a form.

Are impact or deadlines calculated automatically?

No. Impact level, dates and cycle days are fields you fill in, with no formula.

Contact sales