Stages

Overview

Stages have two important functions in the production database:

1. Reflect the real-life status of a component

2. this can be used to calculate production yields & rates

   • e.g. proportion of components which reach a stage as a metric of production

3. A convenient tool to duplicate test information in a component data strucutre without ambiguity

   • tests are therefore associated to stages and the stage of the test was performed at must be defined for upload
     • e.g. IV tests and Visual Inspection tests appear multiple times in the database

Stages can be set without uploading a test. Tests must have a defined stage.

Stage Control and Permissions

Stage contol is implemented and functionality is differentiated across user roles (see general section on User Levels):

• executive (and below) users can advance a component to the next stage (defined by stage order)

  • executives cannot advance components more than one stage
  • executives cannot revert components to previous stages
  • executives cannot move components from stages flagged as final

• institute authority (and above) users can select any stage fro a component

Note

Users should be aware of limitations to user rights when intefacing with the production database via scripts (including commandline, notebooks, GUIs and web applications).

Stages Types

Stages can be flagged with a type for special cases:

Initial: This is the default stage for each new component registered

Final: When a component is set to a stage flagged as final it is not expected to be moved again. Only users with credentials above Institute Authority can move a component from a final stage.

Alternative: Alternative stages are used for subsets of components which may vary in production path

• e.g. (sub-)types of components or special productions batches

• For more information see below