Skip to content
Vienna and Carinthia, November 15 to 20

Choose a production context.

Injection molding

  • Short shots across a product family

    Question to investigate
    Which recorded conditions differ between accepted and short-shot runs of one part?
    Evidence to connect
    Inspection results, press settings, part and mold identity, material lots, timing.
    A useful next step
    A supported comparison for the engineer; an earlier-warning test if history allows.
  • Rejects after a tool change

    Question to investigate
    Did rejects change with the tool or setup, and what else changed?
    Evidence to connect
    Tool and maintenance records, production logs, material context and inspection results.
    A useful next step
    Separate competing explanations and attach the evidence to the agreed engineering review.
  • Moisture and drying questions

    Question to investigate
    Are recorded drying conditions or material differences associated with reject changes?
    Evidence to connect
    Material lots, dryer records where available, process conditions and quality outcomes.
    A useful next step
    Identify which comparisons the records support and where checks are needed first.

These examples illustrate questions and possible evidence. The actual data, method and scope depend on the process and the problem.

Connect the evidence that changes the decision.

  • Quality and inspection

    Defect codes, pass/fail results, measurements, test records and inspection history show the outcome to explain.

  • Production and material context

    Part, lot, order, equipment, material and production timing establish which conditions belong to that outcome.

  • Process and maintenance

    Recorded parameters, tool changes, maintenance and operating context can help identify useful comparisons.

  • Response and ownership

    Alerts, review tasks and recorded decisions keep a finding connected to the people expected to act.

You do not need every possible source, only enough relevant evidence for the question being tested.

Start with the question, not a complete data checklist.

Tell us what you need to understand, anticipate or improve. We will work through the records and checks that would make that question answerable.

Book a Call

Bring one quality problem.

Finding the right fit

Are these the only manufacturing processes you work with?

No, they illustrate the quality questions and production contexts in this focus. The broader fit is a component manufacturer with meaningful quality loss, relevant checks and a team responsible for improvement.

Do we need an advanced analytics team?

No, your team may work with spreadsheets or separate system views. What matters is the quality question, the recorded evidence and the people who can validate what it means.

Do we need sensors on every machine?

No, start with the records relevant to the use case. Some questions need only inspection, test and production history; others need more detailed process measurements.

What does a useful starting dataset contain?

Usually a quality result and a way to connect it to the relevant part, lot or production period. There is no universal field list to satisfy before a conversation; we assess further context together.

Are these examples delivered customer projects?

No, they are illustrative use cases. The Case studies section describes delivered work and labels the evidence behind any figures.

Different Process? Bring the Question Anyway.

We will help you find a useful starting point and the evidence to test it.

Book a Call

Or write to info@datansh.com