Validation FAIL: Escalation And Handover To CSM

When to use this

Use this module when:

• Standard validation was run during onboarding

• Cost WMAPE is 10% or higher on the standard validation dataset

• There is no explicit contract requirement to continue with deeper accuracy work

Do not use this module for customer reported issues after go live. Use: Customer Accuracy Issue: Recalibration With Customer Parts.

Inputs

You need:

• Validation results including Cost WMAPE value

• Standard validation dataset version used

• Slicer project file used and preset name used

• Validation G-code files and extractor outputs

• 3D Spark setup identifiers used (machine, material, process chain)

Outputs

You will produce:

• Evidence saved in CS_Internal in the correct onboarding folder

• A completion note that states FAIL, Cost WMAPE, dataset version, and “stopped per SOP”

• An internal handover message to CSM with the evidence folder link

Rules

Apply these rules:

• Do not rerun calibration or validation after FAIL unless the contract explicitly requires it

• Do not tweak slicer parameters to chase Cost WMAPE under 10%

• Do not add extra parts or datasets beyond the standard validation set

• CS Ops informs CSM. CSM decides next steps

Procedure

Do this:

• Stop work after you have a valid FAIL result

• Keep the slicer project and 3D Spark setup unchanged after the FAIL run

• Verify these artifacts are saved in CS_Internal:

  • Copy of the standard validation CAD set

  • Slicer project file used, with the customer preset saved inside the project

  • Exported validation G-code files

  • Extractor outputs for the validation G-code

  • 3D Spark validation result output including Cost WMAPE

• Write a CS Ops completion note in the evidence folder that includes:

  • Result: FAIL

  • Cost WMAPE: %

  • Dataset version:

  • Preset name:

  • Slicer name and version if available

  • 3D Spark identifiers: machine, material, process chain

  • Statement: “Accuracy target not achieved. Stopped per SOP. Await CSM decision.”

• Notify CSM internally with:

  • One line outcome: “Validation FAIL. Cost WMAPE = X%.”

  • Link to the CS_Internal evidence folder

  • One line reminder: “No further correction attempted per SOP.”

What CSM decides next

CS Ops does not decide. CSM chooses:

• Release with disclosure that cost accuracy target was not achieved

• Request contract scope change or paid correction work

• Start Customer Accuracy Issue: Recalibration With Customer Parts, but only after CSM collects customer parts and confirms scope
  Module: Customer Accuracy Issue: Recalibration With Customer Parts

Common mistakes

Avoid this:

• Trying to “fix it quickly” by changing parameters

• Running extra iterations without contract scope

• Writing a vague note without Cost WMAPE and dataset version