Electronic component and product revision management system

The engineer handles the components of the product and their approved substitutes. When the supplier changes or ceases to supply the component, it is apparent which products and tests need to be reviewed.

The product composition list, manufacturers' permitted components, software version and test requirements do not have a harmonised release basis. A line or test station can obtain information for different versions of the product.

How the solution works

  1. The manufacturer code is linked to the internal part and relevant product structures.
  2. The resulting supply or technical change shows the affected versions of the product and orders.
  3. Engineering identifies the need for evaluation, testing and customer approval.
  4. The alternative is approved with a specific application and validity limit.
  5. Purchase, production and testing process receive the change of approved version they need.

Key challenges

  • Bills of materials, component data and production revisions are managed separately
  • Components alternatives and supply changes are not under control as product changes

Solution capabilities

Product and component versions

The list of product compositions is linked to exact producer codes, program and control requirements references.

Manufacturer's Notices of Changes

The component stores the manufacturer's technical change or supply cut-off notices. Indicates the date of notification and the products in which the component is used.

Analysis of use

Versions of products using the component are identified, relevant orders and approvals are applied to them.

Technical evaluation of the alternative

Tests, restrictions and product-specific authorization are retained.

Communicating changes

The approved alternative and its validity limit achieves purchase, production and control.

Business context

Bills of materials, component data and production revisions are managed separately
The product composition list, manufacturers' permitted components, software version and test requirements do not have a harmonised release basis. A line or test station can obtain information for different versions of the product.
Components alternatives and supply changes are not under control as product changes
Lacking a component, the alternative is combined by letter and the permit does not reach all affected versions of the product, procurement and testing requirements. Purchase and production may rely on different replacement limits; later it is necessary to suspend use or repeat technical verification.
The replacement of the component does not cause surprises for the buyer
After the supply of the component is discontinued, the customer needs to know if the product, testing and delivery deadline will change. The visible influence of the replacement allows for a matching alternative before it is used in production. This helps to continue the supply and more accurately plan long-term orders while maintaining the necessary technical approvals.

Core features

  • Product and component versions
  • Manufacturer's Notices of Changes
  • Analysis of use
  • Technical evaluation of the alternative
  • Communicating changes

Key integrations

Product Life Cycle Management System (PLM)
Product structure, technical content and replacement status have been approved if this function is operated separately.
Enterprise resource planning system (ERP)
Supply demand, open orders and acceptance of an approved alternative.
Data sources for manufacturer components
Precise codes, technical documents and life cycle messages.
Quality and testing process
Assessment requirement and reasonable test result.
Electronics manufacturing execution system (MES)
Use and actual usage history allowed for a specific version of the product.

Potential impact (%)

The ranges indicate an illustrative relative change in the metric under the stated assumptions. Results depend on the starting position and actual use of the solution. Percentages for different metrics must not be added together.

Component replacement impact determination work

12–36%Decreasing

This illustrative scenario assumes that 30-60% of manual data entry and handover work can be addressed. That share is assumed to fall by 40-60%. Company data is needed to verify both the addressable workload and the resulting change.

A comparison of active engineering and procurement work for a similar number of changes.

Cases of uncertain alternative permit detected in production

5–25%Decreasing

This illustrative scenario assumes that 20-50% of missed actions can be identified through task and deadline tracking. That share is assumed to fall by 25-50%. Company data is needed to verify both the addressable share and the resulting change.

Stops are counted due to missing, outdated, or incorrectly transmitted confirmation.

Conditional calculation scenarios. The assumptions have not been validated against client measurements.

When this solution is relevant

  • The purchase finds a similar component, but its release for a specific version of the product is still being matched by letters.
  • The manufacturer's notification of the change or interruption of supply does not reach all products using that component.

Implementation requirements

For component changes, manufacturers' codes, usage in product versions and customer approval requirements are checked. The course of testing and temporary permissions is combined with the available product life cycle system while maintaining the validity limits of the change.

Further development options

  • Review of the effect of producer reports on open stock
  • Verification of the acceptance of a change in the client's permit

Frequently asked questions

Adapting the solution to your business