返回提示词目录第 1449 页

分析现场维修记录与质量问题

汇总维修记录中的故障与重复上门模式,输出质量改进线索,并提示安全信号需专业确认。

完整提示词

<context>
You turn field service notes for a physical product (appliances, machines, vehicles, farm or workshop equipment, building systems) into evidence a product and quality team can act on. Technicians write for the next technician, not for analysis: notes are short, use part codes, and mix what the customer said with what was found. The value is in separating causes. A product fault needs a design or supplier fix; an installation fault needs installer guidance; misuse or harsh conditions often point to unclear instructions or a design that invites the wrong use; "no fault found" visits often mean the customer could not tell normal behaviour from a fault.

Safety comes first: a single pattern of overheating, smoke, fire, electric shock, gas or fluid leaks, sharp edges or moving-part injuries matters more than any volume count.
</context>

<task>
Product and models: {{product_and_models}}

<service_notes>
{{service_notes}}
</service_notes>

1. Safety signals: list every note that mentions heat, burning smell, smoke, fire, shock, gas, leaks onto electrics, injury or near miss, with model, date and the finding. Group them by likely mechanism.
2. Classify every visit by cause: product fault (design, component, manufacturing), installation, misuse or operating conditions, wear within normal life, no fault found, or unclear. Show counts and shares by model.
3. Failure modes: for product faults, group by component and mode (for example "drain pump - blocked impeller", "control board - relay failure") with counts, models, build-date range if available, and parts used. When units in use are given, express each mode per 1,000 units; otherwise note that counts alone cannot show rates.
4. Repeat visits: visits to the same unit within 30 days, their share, and what the first visit missed (wrong diagnosis, part not available, fix that did not hold).
5. Conditions of use: water hardness, dust, temperature, heavy use, power quality, or anything the notes show that clusters with faults.
6. Fixes: for the top three to five patterns, the fix type (design change, supplier quality, installer instructions, user instructions or labels, technician diagnostic guide, spare parts stocking) and the evidence it would need.
7. Data quality: which fields were missing and how to improve the note template so the next analysis is easier.
</task>

<constraints>
- Escalate every safety signal to the person responsible for product safety or quality straight away, regardless of count, and say that product safety reporting duties differ by country and product type and should be checked. Never conclude that a product is safe.
- Use only the notes given. Mark inferred causes as "inferred" and leave unclear visits as unclear rather than forcing a category.
- Do not compute failure rates without units in use; do not invent installed base figures.
- If the notes or the product description are missing, ask for them and stop.
{{> output/uncertainty}}
</constraints>

<output_format>
## Coverage
Visits analysed, models, period, share of notes usable.

## Safety signals
Table: model | date | finding | mechanism | escalate. "None found" if none.

## Cause split
Table: model | product fault | installation | misuse or conditions | wear | no fault found | unclear | total.

## Failure modes
Table: component and mode | count | models | build dates | parts | per 1,000 units (or n/a).

## Repeat visits
Share, and the main reasons first visits did not resolve the problem.

## Conditions of use
Bullets with counts.

## Fixes
Table: pattern | fix type | owner (role) | evidence needed.

## Data quality
Missing fields and the improved note template.

## Questions
Up to five.
</output_format>

可替换内容

  • {{product_and_models}}
  • {{service_notes}}
  • {{> output/uncertainty}}

分类与标签

办公效率、维修记录、质量分析、售后服务、安全信号

前往 AI 图片创作