An AI knowledge base for technical procurement

What the earlier substitution approval says

Suppose a buyer is considering part B in place of part A. A signed engineering note permits B in the assembly identified as revision R2. The approval is limited to R2. The current purchase request concerns R3. The note does not explain the technical reasoning behind the earlier decision.

The assistant can find the note and answer: “Engineering approved part B in place of A for assembly revision R2. The current request specifies R3. The approval found covers R2 only.” It provides a link to the signed document. The buyer can open it and send it to engineering with the current request.

The question is now specific: can part B also be used in R3? Engineering receives the earlier decision and can see what is different about procurement's new question. The buyer does not have to reconstruct the entire history or ask someone to find the old note again. The person responsible for the technical assessment still decides whether the substitute can be used in the new revision.

If the buyer also wants to understand why the earlier substitution was approved, they need to ask in this example. In other cases, the reasoning may be in the decision or an attached assessment. The assistant can then point to that passage so the next colleague returning to the purchase understands both the decision and its rationale.

Less time reconstructing old discussions

A new buyer sees an earlier order for part B, but that order alone does not explain where its use was permitted. The approval sits in a project folder with no link from the order. Connecting those materials lets the buyer open the decision without finding someone who remembers the case.

A knowledge base is useful when it helps turn a question in the buyer's own words into a specific recorded agreement. A colleague taking over the work also gets documents they can return to. If engineering later issues a new decision, whoever maintains the documentation should link it to the relevant assembly and earlier case so procurement can find it.

Use the change history in your existing system

Before commissioning a separate application, check your ERP or product documentation system. If decisions and their reasoning are already available against the part and assembly revision, a clearer view or better search may be enough.

Microsoft describes product versions and workflow-supported engineering changes in Dynamics 365 Supply Chain Management. These are examples of capabilities to investigate in the system you use.

A separate solution is worth considering when purchase information, the assembly revision, and the earlier decision live in different places. Connecting those sources can help a buyer find the note through their question and see which application it covers. Access to those materials should follow the employee's responsibilities and company rules.

If the part has already been confirmed and the employee needs availability and timing, that is a different task. Our article on an AI agent for spare-parts availability requests covers that work.

Connect engineering decisions with purchasing work

When buyers and engineers repeatedly reconstruct the same cases, Syntalith can help make recorded decisions accessible alongside new purchasing questions. We propose starting a Company Brain project with a selected group of parts and assemblies. In that project, we connect decision documents with the information buyers use to search, so they receive the source and a short explanation of the earlier approval's scope.

Engineering identifies the relevant materials and checks whether answers represent them accurately. Buyers assess whether the help lets them find an existing decision or prepare a focused question. Tell us about a recent purchase that sent the team looking for an earlier substitution approval. We can use it to discuss whether better access to the current system is enough or whether several sources need connecting. See Syntalith's pricing page for commercial information.