Source Release Functional Workflow Overview In PPAP-MetricStream, a valid user in either the SM or SQIE role can independently initiate a Source Release using the Create New Source Release link found on the SR Internal tab. 1
Initiate a Source Release PPAP-CQMS allows the SM or SQIE Initiate a Source Release. The Create New Source Release form will appear slightly different for each. The sections in RED must be completed before the Source Release can be submitted to the next step. If the SM performs the Initiate step, the mandatory sections must be completed before it can be submitted to the SQIE. The Source Release request will remain at DRAFT status until the SQIE completes the mandatory sections and submits it to the supplier. If the SQIE performs the Initiate step, the mandatory sections must be completed before the Source Release can be submitted to the supplier. In both cases, the Source Release has been initiated only after it has been submitted to the supplier. Now let s take a closer look at each section... 2
Section 1 - General Information Purpose: Identify the Business Unit for which the Source Release is being initiated. This is a mandatory section. Section 2 - VPI Programs Purpose: Determine if a VPI Program is necessary. If Yes, choose one or more appropriate VPI Programs from the pop-up list.. VPI Program values are specific to the BU selected in Section 1. Please see your BU Admin if you need to add a new VPI Program. 3
Section 3 - SR Submission Details Purpose: Record the part details, Supplier Site details, Reason for Submission, SR Supplier Submission Due Date and SR SQIE Submission Due Date.. 4
Section 4 Sourcing Team Information Purpose: Select the Sourcing Specialist / Manager who works directly with the Supplier. Once the SR is created, this person will receive system FYI notifications. If an SM is creating a SR, the system will automatically complete this section based on the SM s contact information as shown above. Otherwise, the section title remains red until the SQIE selects the appropriate SM. Section 5 SQIE Information Purpose: Select the SQIE responsible for working directly with the supplier to complete the review and approval of the PPAP. This section is mandatory for a SM to complete. If the PPAP was created by an SQIE, the system automatically completes this section as shown below. 5
Section 6 SR Submission Level Purpose: Select documents to be sent to Cummins (Submit) or made available if requested by Cummins (Retain). Note: This Section is optional for SMs but mandatory for SQIEs. Note: Any and all of these values can be updated as needed by either the SM or SQIE. Once the SR is created, only the SQIE can continue to update these values until the SR is approved and completed. 6
Section 7 Supplier Information Purpose: Select the appropriate SR Supplier Contact Name responsible for responding to the SR. This section is optional for the SM but mandatory for the SQIE. If there is more than one supplier contact in the list, the system will default all remaining supplier contacts to the CC: Email field to receive FYI notifications about the progress of the SR. Note: the values shown here come from those supplier users who have registered in the Supplier Portal for this specific Supplier Site ID (as entered in Section 3). If you do not see your contact in the list, please email the CQMS Supplier Registration Team and request that the supplier contact be added. (CQMSSupplierRegistration@cummins.com) 7
Section 8 Plant Information Purpose: It is required to select the appropriate plant(s) / contact(s) receiving the parts from this supplier. The system will automatically notify these plant contacts about the SR progress. Once you select a plant / contact value in the Plant Name field, the system will automatically populate the contact information. If you need to add more than one plant / contact use the Add Row link. To Add/Update values in the Plant Name list, contact the your BU Admin. Note: Only the plants associated with the Business Unit selected in Section 1 will be visible in this section. 8
Section 9 Deviation Approvals Purpose: Is a Deviation Approval required? This is not a mandatory section and the default answer is No. If Yes is selected, the Design Engineer Approval and VPC/VPI Program Manager Approval will change to mandatory. Both of these sections require that files be uploaded showing the written approval. General Attachments / General Comments Purpose: If you have additional files or comments you would like to share with others (including the supplier contact), include them here. 9
SR - Take Action Purpose: The final step to completing the Initiate SR step is to take action on a completed form. Click Type value. and the system will execute the Action The value for Action Type on this form defaults to a specific value depending on who is initiating the SR. SM SQIE is still required to review the SR and complete additional information before the Initiate SR step is complete. SQIE Initiate SR step is complete. Note: Clicking on the Save and Continue or Save and Exit buttons do not move the workflow forward. You must click on the button to move the workflow forward. 10
Once the Create New SR steps are completed and the button has been clicked, the system will generate a unique identifier called the Item ID (shown as Issue ID) and then the following system message: A new row will now appear under the My Related SRs dashboard. To confirm that the SR was initiated, review the SR Status. In the 2nd example below, the Initiate step was performed by the SM and requires the SQIE to do a final review (validate) before the Initiate Step is complete. In this case, the SQIE will see a new SR in their My Related SRs dashboard with a SR Status as Sent from SM and the SQIE Work To Do as Validate to Send to Supplier. SQIE has completed the PPAP Initiate Step. 11
The SR Initiation is completed once the Send to Supplier action has been completed by the SQIE. The newly created SR can be accessed through multiple portals shown below. My Tasks My Assignments My Related SRs The Workflow is now at the Supplier Response step. 12