5 Replies Latest reply on Jun 1, 2009 5:30 PM by Jason Capriotti

    Manufacturing Effectivity

    Jason Capriotti
      We are trying to map out our workflow and one thing that concerns us is the workflow transition from Engineering Release to Manufacturing Release.

      When we finish the drawings on an ECO in engineering, they go through "Review", then "Release". However, they would not be, or rather should not be viewable by the factory until the Mfg engineers have implemented the changes.

      So Revision A of a drawing is checked out, changes are made and it is checked in and submitted for "Review". Product Engineering signs off and the ECO with drawings transition to "Released" and the Revision goes to "B".

      Now the problem, should there be another state "Mfg Released"?

      The problem is that engineering may need to begin working on the drawing again for another ECO change, except that Mfg still needs to implement the previous ECOs changes. If we were to allow a transition from "Released" back to "Inwork" on an ECO to get ready for Rev C, Mfg could no longer transition the previous revision to "Mfg Released". They can sometimes sit on implementing drawing changes for months.... some of our drawings have 3 revisions waiting on Mfg to implement. Meanwhile, engineering has to keep on moving.

      Maybe this should be a checkbox somewhere saying its implemented in the factory? If so, can we keep the shop floor from seeing the newer revision until its checked?
        • Manufacturing Effectivity
          Ben Kalinowski
          We ran into a similar situation where a file was released in one country, but not in others.

          I ended up making a workflow for this but it was huge and unruly! What we really wanted was the ability to assign permissions based on a checkbox so that you could leave a file in 'Released', but still assign permissions for viewing - sort of a 3rd dimension to permissioning.

          We haven't seen a formal solution for this yet.
            • Manufacturing Effectivity
              Mathew Stevenson
              Set set up another workflow that links from Released (approved) which only Engineering see and we just send it to this workflow for All-Released (all approved) and then everyone sees the files
                • Manufacturing Effectivity
                  Jason Capriotti
                  What happenes when you want to revise the file again before it gets to "All-Release"?

                  Do states apply at the revision level? Meaning Rev A could be "Released" and Rev B could be "Inwork"? And therefore the shop would only see Rev A?
                    • Manufacturing Effectivity
                      Mathew Stevenson
                      We pull it back from All-Release workflow for changes it it goes back through our standard workflow for rev.'s. This is why we made a seperat workflow for this.
                        • Manufacturing Effectivity
                          Jason Capriotti
                          What does the shop see?

                          Our problem is engineering may have several revisions inwork that the shop hasn't implemented yet.

                          So the revisions and status may be:

                          E - Inwork (ECO in progress by engineering)
                          D - Approved (Engineering released but not shop effective)
                          C - Approved (Engineering released but not shop effective)
                          B - Released (This is what MFG is currently making)
                          A - Inactive

                          In the above example, MFG on the shop floor should only see Revision "B". Mfg engineering should see revisions "C" & "D" because they would be getting ready to implement the changes. Only product engineering would see all revisions inlcuding Revision "E".

                          Not sure how Enterprise can handle this, it seems the workflow is not revision specific, or is it?