Reference: Supplier package creation
Note:
For users with Fusion connected sites, references to the 'Items' workspace should be the 'Components' workspace.
A Supplier Package can be created at any given time by any user who has the Supplier Packages [R/W] role. The main part will be the header section which contains these item details.
| Field | Description |
|---|---|
| Number | This will store an automatic number being generated by script |
| Supplier | Supplier who this package will be shared with |
| Template | The template that will be used to create the package, enabling to standardize data sharing and activity management |
| Type | Type of the package The type will be set by the selected template if left blank |
| Title | Title to describe the package The title will be set by the selected template if left blank |
| Remarks | Further description of the package and the purpose The remakrs will be set by the selected template if left blank |
| Shared Items | Items that will be shared will the supplier as soon as the package has been submitted |
| Submittal Date | This date will be set automatically when the package gets submitted to the supplier |
| Instructions | Gives the user clear instructions on the next steps. These instructions will be updated automatically throughout the workflow of the package. |
The other sections are:
Section |
Description |
|---|---|
Header |
The header section will display the most relevant information to describe the package. The most relevant information is the supplier, which therefore is a mandatory field for the package to be created. For the case that a template is used the fields, type, title and remarks can be left empty, as they will be automatically filled with the information that are predefined in the template. Another important part of the header section is the shared items picklist. This allows the user to share specific items with the supplier which gives them access to these inside of the Items and BOMs workspace. A unique number will be generated for each package upon creation. |
Contacts |
This section contains the main contact person from the supplier and from the internal perspective. If not entered during the creation of the package the Supplier Main Contact will be automatically taken from the selected supplier and the requestor contact person will be the creator of the package. |
Status & KPIs |
In here all related information is summarized to give a quick overview of the status of the package. Starting with the progress of the package itself to pending proposals and next due and completion dates. |
Notes |
Notes can contain everything that should be mentioned in the package that does not fit elsewhere. |
FTP Details |
For the case that files are shared somewhere else, this section can be used to give the supplier access to these files by adding the link to the file as well as the username and password needed to access it. |
Schedule |
Overview of the relevant dates for the package. These dates are the confirmation of the package, the shipment and arrival. The section tracks these dates and compares them with the target schedule and calculates the duration for each part of the process as well as the deviation days to better plan in the future. |
Item Counters |
This section shows the ratio of new, modified and repeated items that are shared with the supplier as well as their total numbers. |
Deliverables |
Up to five deliverables for the supplier can be entered here in the standard configuration of the template. By adding a title, details, a target date and if needed, a reference link, the supplier gets all the information he needs to fulfill this task. Note that the deliverables are in a draft as long as the package itself is in the Definition state. After submitting the package, the deliverables will be created. |
Deliverables Summary |
The deliverables summary helps to review the current progress of the tasks related to this package. Showing the overall ratio of completed deliverables, the next deliverable and its target date as well as the number of pending deliverables for this package. |
On Hold Status Details |
Whenever the package hits the on hold status the user that executed the transition, the date and the reason for it will be noted down in this section. Additionally, the days since the package has been set to is shown. |