Share

Supplier Package Workflow

Note:

For users with Fusion connected sites, references to the 'Items' workspace should be the 'Components' workspace.

The workflow shown in tab Status enables alignment of both the internal requestor of the package and its deliverables as well as the supplier's contact person and personnel. These stakeholders are defined in the Contacts section of the package and will receive automatic mail notifications on occurrence of relevant events. They will also find the given package in their My Outstanding Work list if an action is due on their side.

Note that notifications and requests are sent to both the selected supplier contact person as well as all other users defined by the supplier’s user group.

Definition

In the definition state, the requestor provides all information needed by the supplier to provide requested deliverables in time. This may include Items (and BOMs) and files to be shared as well as deliverables being requested. Such deliverables will be managed by sub processes that get created upon submission of the package. Target dates may be defined at this stage to set proper priority of deliverables and events of this collaborative process.

Submitted

Once the package gets submitted, the selected supplier will be notified about the new package. Additionally, a few things happen in the background:

  • New items that have been shared with the supplier inside of this package will have the supplier as an additional owner for the given revision.
  • The same applies for the template to allow suppliers the download of standard files defined by the template.
  • The deliverables that have been defined in the definition state will be created as well and are added as relationships to the package.

The Confirmed state indicates that the supplier has received the package.

Processing

The supplier can push the package to the processing state to indicate that he is currently working on the content of the package.

Shipped

To confirm the shipment of the goods that have been requested with the package, the supplier can make use of the shipped state.

Returned

For the case that information is missing for the supplier to handle the package accordingly it can be moved into the returned state. A comment is mandatory for this transition to ensure a correct response.

Completed

This state can be reached from several states inside of the supplier package workflow. All of them have one thing in common, the overall completion of the supplier package. Either by confirming that the shipped goods have arrived or that the supplier package is completed without further actions.

Cancelled

Reaching this state informs the owner about the transition and indicates that the package cannot be completed in its current state. The reason for this will be recorded in the mandatory comment that is needed to execute this workflow transition.

Was this information helpful?