Published
Quality inspection plan and inspection result
EM-MFG-05 · em-mfg-05
Record what was checked, how, against which limits and with what outcome, so that release decisions rest on evidence.
Enterprise profiles Enterprise subject EnterpriseMFG
Bundle → Layer → Finding → QuestionsClassifiersWhat it isWhy it existsDistinguishing featuresWhat robots and AI may and may not doMoral aspectsOwnersLinks to other meta-modelsIdentity and identifiersDirect propertiesRecognitionCapabilities and actionsHazards and failure modesStandards and interfacesContext of useSources
Bundle → Layer → Finding → Questions Filled
2 bundles · 2 layers · 4 findings · 8 questions
Inspection plan What must be checked and how.
Characteristics and sampling
Characteristics, methods, limits and sampling rules.
Characteristics
Checked characteristics with methods and limits.
- Which characteristics, methods and limits does this inspection plan version require?
- Which item, routing operation or supplier does this inspection plan apply to?
Sampling
How many units are checked.
- Which sampling rule determined the sample size for this inspection lot?
Inspection record What was found and decided.
Results and decision
Measured values and the usage decision.
Results
Values per characteristic with units and instruments.
- Which results were recorded for each characteristic of this inspection lot, with units?
- Which instrument produced each measured value, and was it within its calibration interval?
- Who recorded the results of this inspection lot, and when?
Usage decision
Release or rejection based on the results.
- What usage decision was recorded for this inspection lot, by whom and on what evidence?
- Which nonconformance was opened for the out-of-limit results of this inspection lot?
Classifiers Filled
- Family
- Enterprise profiles
- Category
- Enterprise subject
- Entry kind
- subject
- Domain
- EnterpriseMFG
- Industry
- Manufacturing
- Tags
- EM-MFG-05W-INDsubjectInspectionPlanInspectionCharacteristicSamplingRuleInspectionLotInspectionResult
What it is Filled
What must be checked on incoming material, in process and on finished product: characteristics, methods, sampling and limits, and the recorded results with their usage decision. Audits and software tests are separate contours.
Why it exists Filled
Record what was checked, how, against which limits and with what outcome, so that release decisions rest on evidence.
Distinguishing features Filled
- The plan defines what to check, and the result records what was found.
- Results keep units, methods and instrument references.
- A usage decision is a separate record from the measured results.
- Audits of the management system and software tests are separate contours.
What robots and AI may and may not do Filled
Must not
- Record a release or rejection decision without an authorized person.
- Change measured values after they are recorded.
- Accept a supplier certificate in place of a required test.
Only with a human decision
- An authorized inspector or quality person must make usage decisions.
- Changes to limits in an inspection plan require quality approval.
May
- Summarize results against limits and flag out-of-limit values.
- Check that mandatory characteristics have results before a decision.
- Draft a usage decision proposal for a qualified person.
Moral aspects Filled
- Pressure to release can lead to falsified or skipped checks.
- Inspection results can be used to blame individual operators without context.
Who is affected
- Customers and end users
- Inspectors and operators
- Suppliers
Owners Filled
Steward
The head of quality who answers for inspection plans and release decisions.
Master systems
- Quality management system
- Laboratory information management system
- Manufacturing execution system
Links to other meta-models Filled
neighbor
- EM-OPS-03
- EM-OPS-05
- EM-MFG-02
- EM-MFG-06
- EM-RSK-02
- EM-TEC-08
references
- WM-ACT-033 - conceptual-candidate
- WM-MAT-008 - conceptual-candidate
- WM-MAT-007 - conceptual-candidate
What else AI and robots need to interact with it Filled
Identity and identifiers required Filled
- An inspection lot is identified by a number and references the material lot or order it covers.
- An inspection plan is identified by plan number and version.
Direct properties not applicable Not applicable
Not applicable
Enterprise record contour: physical properties belong to referenced world models.
Recognition required Filled
- Records show characteristics, limits, measured values with units and a usage decision.
- An inspection result must be distinguished from an audit finding and from a software test run.
Capabilities and actions required Filled
- The contour supports release decisions, supplier quality evaluation and trend analysis of characteristics.
Hazards and failure modes required Filled
- Releasing product on incomplete results can put unsafe product on the market.
- Uncalibrated instruments can make out-of-limit product look conforming.
Standards and interfaces optional Filled
- ISO publishes ISO 9001 with requirements for monitoring, measurement and release of products.
- ISO publishes the ISO 2859 and ISO 3951 sampling procedures for inspection by attributes and by variables.
Context of use required Filled
- The contour is used for incoming, in-process and final inspection.
- Food, medicines and medical devices add sector rules for release records.
Sources Filled
- ISO 9001: monitoring, measurement and release of products
- ISO 2859 and ISO 3951: sampling procedures for inspection
- ISO/IEC 17025: competence of testing and calibration laboratories
- ISO 9001:2015 Quality management systems - Requirements - Checked live (HTTP 200) on 2026-10-21.
- ISO/IEC 17025:2017 General requirements for the competence of testing and calibration laboratories - Checked live (HTTP 200) on 2026-10-21.
Open questions
- How are characteristics and limits versioned together with the item and the routing?
- How is a measured value linked to the instrument and its calibration status?
- Who may record a usage decision and on what evidence?
- Settle the boundary and the reuse, extend or new decision against the current specifications.
- Confirm the semantic crosswalk, rights and source mastership.
- Choose immutable references and run fixture checks before claiming publication readiness.
Machine files
Provenance
enterprise research programme · published-partial
Built from: enterprise/models/em-mfg-05/brief.json, ver-cy/world-models/card-supplements/em-mfg-05.json