返回提示词目录第 1167 页

生产批次追溯与记录流程设计

设计原料到客户的批次编码、记录表及模拟召回流程,并列出需向监管方确认的事项。

完整提示词

<context>
Traceability means that, given a problem with one incoming material or one finished batch, you can quickly name every affected batch and every customer who received it, and nothing more. The common baseline is "one step back, one step forward": which supplier lots went into each of your batches, and which customers received each batch. Small makers lose this link in predictable places: mixing supplier lots in a shared bin, rework and leftovers added to a new batch, part-used materials, samples and giveaways, and online orders that record the product but not the lot. The tighter the lot (per day or per mix rather than per month), the smaller a recall, at the cost of more recording. A system is only proven by a timed mock recall: pick one supplier lot and one finished lot and trace both ways, then measure time taken and percentage of quantity accounted for. Many sectors (food, feed, cosmetics, toys, medical, automotive) have specific legal or customer rules on what to record and for how long.
</context>

<task>
Product and flow:
<product>
{{product}}
</product>

{{#current_records}}Current records and requirements:
<current_records>
{{current_records}}
</current_records>{{/current_records}}

{{#jurisdiction}}Jurisdiction: {{jurisdiction}}{{/jurisdiction}}

1. Map the flow from goods-in to dispatch and mark the points where lot identity can be lost (mixing, splitting, rework, part-used stock, returns).
2. Recommend the lot size and explain the trade-off between recall size and recording effort for this business.
3. Design a lot code format that is short, unique and readable on the label (for example date plus a sequence), and say where it appears: product, outer case, invoice or delivery note, order record.
4. Specify the records at each step: goods-in (supplier, supplier lot, quantity, date, your internal reference), production (which supplier lots went into which batch, quantities, rework added), stock (part-used materials kept labelled), dispatch (customer, batch, quantity, date).
5. Fit the records to the current tools; suggest the simplest change that closes each gap.
6. Write a mock recall test: one backward trace and one forward trace, a time target as `[CONFIRM]` if no requirement is given, the reconciliation of quantities, and how to record the result.
7. List points to confirm, including legal record-keeping duties and retention periods for this sector and place.
</task>

<constraints>
- Do not state legal traceability requirements, retention periods or recall time limits as fact unless given; mark them to confirm with the relevant regulator, trade body or customer.
- Design for the tools and staff described; do not require software the business does not have unless you explain the cost-benefit.
- Cover the awkward cases (rework, leftovers, samples, returns, online orders); they are where traceability fails.
- If the product is food, cosmetics, medical or for children, note that a recall plan and contact with the authority are separate duties beyond traceability.
</constraints>

<output_format>
## Traceability design
Flow with the risk points marked.
## Lot code format
Format, example and where it is shown.
## Records by step
Table: Step | What to record | Where | Who.
## Linking suppliers and customers
## Mock recall test
Steps, target time, reconciliation, result record.
## Points to confirm
</output_format>

可替换内容

  • {{product}}
  • {{#current_records}}
  • {{current_records}}
  • {{/current_records}}
  • {{#jurisdiction}}
  • {{jurisdiction}}
  • {{/jurisdiction}}
  • [CONFIRM]

分类与标签

办公效率、批次追溯、生产记录、模拟召回、供应链管理

前往 AI 图片创作