Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migration of unmigrated content due to installation of a new plugin

GUI

Mockup
13
work by resource
work by resource
1Version13
Namework by resource

Use example

With resource

Main actor: Worker

  1. Scanned resource with product='unpainted window frame', number=WF-01, quantity=1
  2. The system recognized the resource to be related to order ORD-01, the system detects that the resources product is in the input of the painting operation so it displays the context of the resource and operation details.
  3. Noticed that there are some notes in the description that this is a custom job so he scans the 'View attachment' action code.
    1. Browsed the document by scanning the scroll action codes, this window is to be painted in two colors.
    2. Scanned the back action and returns to the main screen.
  4. Noticed that in the inputs two paint pigments have been added instead of the usual one pigment.
  5. Scanned the Scan inputs action.
    1. Scanned how much pain we actually used
    2. Scanned the resource with product='unpainted window frame', number=WF-01 that it has been actually consumed
    3. Scanned the back action
  6. Scanned the Scan output action.
    1. Scanned create resource
      1. Scanned resource number=WF-01
      2. Scanned 'painted windows' products number
      3. Scanned warehouse 'painting station PS1 output'
    2. Scanned the resource number to note its quantity
    3. Scanned back action
  7. Scanned stop work code

With just an order

Main actor: Worker

Very similar to the 'with resource' scenario but instead of scanning the resource to determine the context we scan an orders number. The operation is determined by the work station.

Workflow

Gliffy
namework progress workflowversion17