Definitions, records, and execution

1. Define the kind of thing.

An entity definition describes a record type: identity, fields, units, relationships, lifecycle, allowed actions, and the forms people use. A Material type might require a name, category, specification reference, and review state. It is not any one material in inventory.

The same distinction applies to a Master Batch Record type. Its definition establishes the structure for ingredients, ordered instructions, measurements, and review. It does not itself specify the recipe for every product.

• Type: Master Batch Record
• Structure: ingredients, steps, limits, and review rules
• Change: require a new field or approval condition on records of this type

2. Author a specific record.

A record created under the published type holds concrete operating content. MBR-104 might specify a particular product, ingredient quantities, and a three-minute blending instruction. Its approved revision is the source used for the corresponding work.

Editing this recipe is a record revision. Adding a new mandatory field to the Master Batch Record type is a model change. The two changes can have different owners, review requirements, and consequences.

• Record: MBR-104
• Content: the recipe for a particular product
• Revision: Rev 8 effective; Rev 9 still a draft

3. Capture a particular execution.

Batch B-0934 records one instance of work performed against MBR-104 Rev 8. It captures the lots used, actual observations, operator confirmations, exceptions, and review decisions.

The instruction might call for three minutes of blending; the observation might be 3.1 minutes. Preserve both. Replacing the actual value with the target, or silently changing its source revision, would erase the distinction between intended and performed work.

• Execution: B-0934
• Source: MBR-104 Rev 8
• Evidence: actual inputs, observations, exceptions, and decisions

Review change at the right layer.

A proposed type change may affect record forms, required values, allowed actions, and verification. A recipe revision may affect instructions, training, and which future batches should use it. An execution correction concerns a particular historical event and needs its own authorized treatment.

The questions are practical: what is changing, what depends on it, who can approve it, and when does it take effect? Keep the original basis of completed work retrievable. Treat any intervention in work already underway as an explicit decision.

Use the same distinction beyond production.

The pattern applies to an inspection type, an approved inspection plan, and an inspection performed on a specific asset. It also applies to an installation-method type, an approved method record, and a field work package.

The record names change by industry. The separation of structure, approved content, and actual evidence is what lets the platform adapt without making those concepts ambiguous.