A baseline is an answer, not an export

What it is, and what it is not

A named, frozen resolution — the structure as it resolved under stated conditions at a stated moment, captured as a first-class object with an owner and a reason.

It is not a snapshot of stored data. A copy of the BOM rows preserves a conditional statement rather than an answer, so comparing against it later reports every effectivity and variant decision as a difference. That is the failure that makes most baseline features useless within a year.

It is not an export either. A PDF or a spreadsheet is readable and uncomparable: nothing can diff it, nothing can traverse from it, and its relationship to the live structure is whatever somebody remembers.

The mechanism: freeze the answer, keep the conditions

A baseline stores the resolved line set and the conditions that produced it — the date, the unit range, the plant, the option selection, the revision policy. Both halves matter.

Storing the answer means the comparison is like-for-like: diffing today's resolution against a baseline compares two answers rather than an answer against a question. Storing the conditions means you can re-run the original resolution and confirm the stored answer, which is what makes a baseline evidence rather than an assertion.

Because resolution is deterministic, that confirmation actually works. Re-running a baseline's conditions against the revisions it named returns identical bytes. A baseline is therefore checkable in a way a snapshot never is — somebody can prove it was not edited.

Baselines are immutable once taken. Correcting one means taking another with a reason, which preserves the record that the first existed and what it said.

The failure it prevents

A contract manufacturer is qualified on a build in March. In November they ask what has changed since qualification.

Somebody exports the current BOM, finds the qualification pack, and diffs the two. The comparison returns sixty rows. Most are noise: re-sorted lines, a phantom expanded differently, and eleven lines appearing on one side only because the qualification covered the 240-volt variant and the current export was scoped to nothing at all.

A day later somebody has four real changes and no way to prove they found them all. The problem was never the diff — it was that one side was an export and the other was a resolution. Comparing a baseline against a current resolution returns four rows with reasons, in the time it takes to ask.

How it meets the rest of the product

Comparison treats a baseline as one side like any other, so comparing against a qualification, a first article or a released configuration is the ordinary compare operation rather than a special feature with its own screen and its own bugs.

Change impact can name baselines: a change affecting a structure that a customer qualification baselined is a materially different proposition from one that affects nothing frozen, and the reviewer sees that before approving rather than after a customer notices.

Requirements verification uses baselines as evidence anchors. A test result verifying a requirement against a specific configuration references the baseline rather than a description of it, which is what makes the it-still-applies question answerable when the product moves on.

Baselines are permission-scoped like any object, so a customer-confidential configuration is not visible to everyone who can see the product.

Taking one is cheap, which matters more than it sounds. A baseline that requires a ceremony gets taken at the three moments somebody remembered, and the useful ones are frequently the unremarkable moments nobody thought to mark — the configuration a supplier was quoting against, the state of a structure before a large restructure began.

How it meets your ERP

A baseline is engineering evidence and does not publish. Your ERP holds what is buildable now; a frozen historical answer has no consumer there, and pushing one across would create a record nobody maintains.

What does cross the seam is the comparison's usefulness. When a customer asks what changed since qualification, the answer names parts your ERP transacts — and the impact set carries their current stock and open orders, so the conversation about what to do is informed rather than purely historical.

Where a baseline underpins a contractual configuration freeze, that constraint is worth recording as an exclusion on mass changes. A bulk replacement sweeping up a frozen structure is the failure a configuration freeze exists to prevent, and the exclusion travels with the change.

Where the boundary is

A baseline records what was specified, not what was built. If the floor substituted an approved alternate on a particular unit, that belongs to as-built configuration and lives where the building happened — a baseline and a serial number's actual content are different questions.

It also does not enforce anything by itself. Freezing a configuration for a customer is a commercial commitment; the baseline is the evidence of what was agreed, and the enforcement is a mass-change exclusion and a review step that somebody has to configure deliberately.