INDUSTRY FIELD GUIDE
Custom resin compounding data for AI addition records
Custom compounding joins purchased materials under a specified job.
NAICS 325991 · Custom Compounding of Purchased Resins
Custom compounding joins purchased materials under a specified job. NIST's polymer reference-material work provides measurement context. An original exercise can test the relationship among source resin, masterbatch reference and the additions actually recorded. NIST polymer reference-material context
Write a fictional customer job reference, component tickets and addition ledger. Give a masterbatch card an explicitly defined concentration basis. Ask the assistant which inputs are documented for the output and which requested calculation has sufficient evidence. Include a proposed masterbatch replacement that was never added and a retained output sample from a different job.
Annotate component identity, source lot, concentration basis, executed addition, job and sample. Evaluation can use a new alias scheme and a split output lot. Score use of the proposed replacement, wrong-job sample matching and unsupported concentration arithmetic independently. The review key should show its source fields and preserve an absent addition record as unresolved.
Use invented values and original tables without a compounding recipe. Real customer formulas, supplier certificates and process settings need permission and qualified review. Describe the execution-and-basis task and checked examples in the contributor proposal. Establish the buyer's accepted material before preparing more operating history or authorized capture.
Discuss this original manufacturing sample with Fiund
Original Fiund exercise
A duplicated line versus a second addition
The records use paper tokens with no chemical identities, quantities or process settings.
| Record | Source | What it records |
|---|---|---|
| 1 | Job note | Job J8 expects one event referencing component ticket X2. |
| 2 | Addition ledger | Rows A and B both use event E14, station S and identical timestamp. |
| 3 | Audit note | Row B imported from the same event export; no distinct physical event recorded. |
Question for the model
How many distinct recorded additions should the sample show?
Show the reference answer and checks
Show one recorded event, E14, based on records 2 and 3. The second ledger row duplicates the source event; the visible row count is two. Record 1 supplies the expected job scope but does not independently verify what physically occurred at the station.
- Counting ledger rows as distinct events
- Equating the expected event with physical confirmation
Fields to preserve
- addition_event_id
- Deduplicates repeated import rows
- source_export_id
- Allows provenance of the duplicate to be checked
- component_ticket
- Connects the event to intended job input
Test another case
Use two real mock event IDs logged at the same timestamp; deduplicate by identity, never by time alone.
No actual recipes, mixing steps, batch quantities or production records.
Discuss a contribution
Describe the sources you control, the task they could support and what has already been checked. Use the existing-data assessment for an archive or the collection brief for a new recording project. The contributor agreement defines Fiund’s licensing authority and compensation. A guide or fictional exercise does not establish an accepted collection or a sale.