Back to guides
In-service

Update legacy products with confidence

An older product must be updated in the field or in series. A change in one BOM hits documentation, compliance and supplier. The value is seeing the full hit before you release a new revision to customers who already have the old one.

The update should hit the right products, not “all the old stuff”.

A gateway on the wall has lived for five years. You need to change firmware or a part. Which serials, which manuals and which certificates come along? Colleag.ai traces impact across BOM, documents and supplier. You will recognise the field ticket where half the fleet got the wrong pack.

The update should hit the right serial numbers

A gateway on the wall has lived for five years. You will change firmware or a part. Which units, which manuals and which certificates come along? “All the old stuff” is not an answer. The value is seeing the hit on the field before you release a revision to customers who already have the old one.

The change against what is actually out there

Colleag.ai traces impact across BOM, documents and supplier. You see what must come along, and what can stay. Then the field issue stops being half the park getting the wrong package.

The knowledge should stay with the product

Each update teaches you something about how the older product is actually built. That knowledge should not stay in the head of the person who packed the box. The next revision then does not start from zero.

Key benefits

  • Dependency mapping for products with incomplete documentation
  • Full impact tracing before committing to changes
  • Reduced risk when replacing obsolete components
  • Knowledge capture during every update cycle
  • Compliance status visibility for mature products

Read more

How do you update a product that has been in series for years when the knowledge sits in heads and in Monitor? Colleag.ai builds a dependency picture from the BOM, test records and change history. That is the capability, not one EOL scene. LCM knows status. PLM often lacks the documents. ERP has the old article.

Updating a product that has been in series for years is a capability, not a single EOL scene. The knowledge sits in the BOM, the test register, the change history and the person who left. Colleag.ai builds the dependency analysis from what exists, Monitor, git and SOPs, instead of opening a discovery project from zero.

LCM knows status. PLM is often missing the older documents. ERP has the old article. None of them tell you which tests and which customers move when you touch a part that has not moved in eight years.

How this differs from ERP, PLM, LCM and project systems

ERP
ERP shows the article still sells. It does not explain undocumented couplings.
PLM
PLM is empty where the original engineer never checked in.
LCM
LCM can say released. It does not map what breaks in the swap.
Project management systems
“Find out how this hangs together” is an epic. Here it is a question.

What Colleag.ai does here that those systems do not

  • Dependencies from what exists, not from who left
  • Impact across BOM, documents and compliance
  • The same flow as new development, not a side project

See it in action

Book a 30-minute demo and see how Colleag.ai handles this for your team.

Book a demo