Skip to content

Beyonetix OS module

ENGIVERITY verifies bills of materials before production starts

Every line is checked against standards text, material rules and more than 50 million intelligent rules. Every finding carries evidence, the rule and a traffic light, and the release stays with you.

In short

ENGIVERITY is the Beyonetix OS module for checking bills of materials, drawings and product data. It is made for design, quality and purchasing teams in manufacturing companies.

Updated: November 2026

What it is for and who uses it

Find errors early, while they are still cheap

A common rule of thumb says an error becomes roughly ten times more expensive with each stage of development, from design to the field. Most bill of materials errors arise early and only show up in assembly or at the customer.

ENGIVERITY steps in before production. The module reads your data, checks it and presents every finding so that a person can follow it and decide.

  • Design: gets findings right at the line and in the drawing view.
  • Quality: releases versions and has the report and log at hand.
  • Purchasing: sees bought-in parts and data sheets tied to the verified lines.
  • Project management: follows requirements and proof status per project.
Beyonetix

Functions

Load, check, decide, report

The core of the module. From the file to the report, every step stays visible.

Loading a bill of materials Spreadsheet, XML or JSON. You pick a load profile, check the file beforehand and get a column mapping suggested. The load report stays on file.
Fixed rule set It checks tree structure, part numbers, duplicates, master data per line, quantities and units, references to drawing and change, and configuration and variant. Every rule names its severity and source.
Four signals Expert rules, standards context from the knowledge search, rules learned from your data and a distance comparison for outliers. The signals stay visible as separate findings and are never merged into one score.
Traffic light with evidence Every generated explanation is checked sentence by sentence against the context used and gets a traffic light: supported, not derivable or contradictory. In doubt it reads not derivable.
Not verifiable If a field is missing from the export, the check reads not verifiable. The data gap list shows which missing field blocks which check.
Deciding and releasing Confirm or dismiss findings, with a mandatory reason when dismissing. Releaser and reviewer are different people, and there is no automatic release.
Release report Report on screen and as a PDF, with the version, a balance per rule and the data gap list. The original stays unchanged.
Return to the source system The return file takes corrections back, with a difference log.
Compare versions, where used Two versions can be compared, also across projects: new, removed, changed, each in plain text. The use of a part shows paths and total quantity per product. Both come as PDF and workbook.

Functions

Drawings and CAD

Drawings are often the second source of truth. ENGIVERITY places them next to the bill of materials.

Drawing comparison The drawing is laid against the bill of materials: number, index, parts, quantities, balloon count and title block. The result is a warning at most. Not every sheet can be reconstructed exactly, so hints stay hints.
Drawing workstation View drawings, read dimensions and discuss findings at the position. For each sheet you see how reliable the evaluation is.
Drawing to CAD Drawings, scanned ones from 150 dpi as well, can be converted and checked against the list. A 2D preview with layers and a correction layer are included.
STEP import and assembly scene You read in geometry in STEP format and see it as an assembly.

Functions

Project, design and purchasing

After the check the data stays in the project and carries on into purchasing.

Project file Bills of materials, drawings, findings and decisions of a project in one place, with project list, search and status.
Requirements and proof status Requirements can be drafted from the contract text, and you review and confirm them. For each requirement you see proof type and status and can hold target values against the latest version. Whatever cannot be judged automatically shows as not verifiable.
Required documents A list of documents per industry package with deadlines and reports by topic. The bundle for hand-in is a zip file with checksums.
Suggestion from a reference On request ENGIVERITY suggests bill of materials lines from a reference. Every line is checked itself before it is shown, and you make the call.
Bought-in parts and data sheets Candidates for bought-in parts with key values and their source, a verdict per requirement and a ranking. You store data sheets separately per tenant and link them to manufacturer and supplier.
Measurement data and migration Measurement data belongs to the project and sits next to the bill of materials. You take over existing data and exports from product data and merchandise systems as files.

Functions

Agent-based document processing in shadow mode

Read, check and present documents without anything reaching the target system that no person has confirmed.

Read, check, confirm, prepare documents Delivery notes, withdrawal lists, hand-written slips, quotations, order confirmations and invoices are read in two independent passes and checked against the mirrored data of your ERP. Every uncertain spot goes to a person together with the scan excerpt. Confirmed documents are prepared as a posting, in shadow mode as a preview.
Shadow mode as the starting state All document types first run alongside your current process. The handover only creates a preview, and all formats carry the label provisional. Only the administration can switch to live operation, with a reason and a log entry.
Cleaning up the article master A check run over the mirrored article master finds duplicate parts, numbers assigned more than once, manufacturer numbers in free text and missing mandatory details. Every suggestion comes with a one-sentence reason. People decide, and import files result from it.
Assistant in ENGIVERITY The assistant answers questions about a bill of materials and about the product. Every answer is checked sentence by sentence against the context. You can ask by voice, receive files as an answer and ask from within any object.

Agents in document processing

How agents work in Beyonetix OS is described under agent platform. Document processing in ENGIVERITY runs as an agent. The page Document processing with agents describes the flow and the rules for uncertain values.

A field counts as certain when both reading passes return the same value, their certainty is above the threshold, the document carries no conspicuous mark, the field is legible and the check against your data passes. A person sees every other field.

Functions

Rule maintenance and learning

The rule set is yours. You see what runs and control what counts.

Rule studio View rules, switch them off or override their severity. Official code lists are available as rule tables.
Learned rules A run over your data delivers candidates for new rules. A rule becomes active only after a person has accepted it.
Outliers by neighbour comparison A reference set is built from your data, and ENGIVERITY compares lines against it by distance.
Standards library and knowledge index The search runs over the knowledge base. You store your own standards texts separately per tenant.

Functions

Operation, rights and proof

When an audit asks who saw and changed what, the answer is in the system.

Tenant separation The data of several tenants is kept apart and filtered per tenant.
Roles and permissions Rule maintenance, quality assurance, bill of materials authors and platform administration each have their own permissions.
Access log The log shows who saw and changed what, and when. The access list names who has access today.
Manual and validation file The user manual and test evidence come as files from the same source as the help in the product.
Usage counter Usage is counted per tenant. There is no fixed pricing model yet.

The check in three numbers

A run with your own bill of materials shows how ENGIVERITY checks in your case.

50M+ intelligent rules for structure, master data, materials, standards references and life cycle
4 independent signals that stay visible as separate findings
3 traffic-light levels per statement: supported, not derivable, contradictory

Process

From the project file to the proof

This is how a project runs in ENGIVERITY.

1 Set up the project You create the project file and, if needed, add the contract text. Requirements are drafted from it, and you review and confirm them.
2 Load the bill of materials You pick a load profile and have the file checked as a dry run. The load report records what happened to every line.
3 Start the check run Fixed rules, standards context, learned rules and the neighbour comparison run side by side. Every finding carries evidence and a traffic light.
4 Decide on the findings You confirm a finding or dismiss it with a reason, one by one or in bulk. You check drawings against the bill of materials at the same time.
5 Release the version A second person releases the version or sends it back with a reason. The release report is available on screen and as a PDF.
6 Return and document The return file brings the corrections back into the source system with a difference log. Version comparison and where-used analysis show what has changed.

Technical details

What ENGIVERITY reads, outputs and separates

Details on the state of functions, November 2026.
PropertyDetail
Load formats Spreadsheet, XML, JSON, exports from product data and merchandise systems as files, STEP for geometry
Outputs Findings list, data gap list, release report as PDF, comparisons and where-used report also as workbook
Return path Return file to the source system with a difference log
Release Two different people, a reason for rejection and for dismissing
Tenants Separate data per tenant, own standards texts and data sheets per tenant
Proof Access log, access list, manual and validation file
Access In the browser, operating mode according to your requirements, clarified with you beforehand

A person always has the final say

ENGIVERITY makes no decision on its own. A finding can be dismissed, and dismissing it needs a reason. A version goes out only after a second person has released it.

The module checks existing bills of materials and drawings. On request it suggests lines from a reference that you confirm or dismiss. It does not replace your PDM, PLM or ERP and only needs their exports.

Which operating mode fits your requirements we clarify with you beforehand. More on this under sovereign infrastructure.

Frequently asked

Frequently asked questions about ENGIVERITY

What is ENGIVERITY?

A verification layer for bills of materials, drawings and product data that starts before production. Every finding carries a traffic light and evidence, and a person makes the decision.

Does ENGIVERITY replace my PDM, PLM or ERP?

No. ENGIVERITY only needs the export formats of those systems and brings corrections back through a return file.

Which file formats can I load?

Spreadsheets, XML and JSON, plus exports from product data and merchandise systems as files. You read in geometry in STEP format.

What does not verifiable mean?

A field is missing from the export, so the rule cannot be applied. ENGIVERITY guesses no value and lists the gap in the data gap list.

Who decides on the release?

Two different people: one reviews, one releases. Whoever dismisses a finding or rejects a version writes a reason.

Can ENGIVERITY process documents?

Yes, in shadow mode. Documents first run alongside your process, and the handover only creates a preview. The administration switches to live operation once the results match.

What does ENGIVERITY cost?

There is no fixed pricing model yet. After a short conversation about your bill of materials we calculate your case.

Request a consultation on ENGIVERITY

Bring a bill of materials of your own and let it run live.

Read on