The following will help you understand how information flows between OEM (Dan) and other participants (for example Supplier) via IPD collaboration for logistics information on a component "Valve cover."
Prerequisites
a. Collaboration space created (Refer to Document collaboration for steps).
b. Needed workflow template loaded (Refer to Document collaboration for steps).
c. Files to be shared are already loaded (Refer to Document collaboration for steps).
d. Bill of material from SAP S/4HANA loaded (Refer to Development collaboration for steps).
e. Redline on "Component" created (Refer to Development collaboration for steps).
f. Workflow Added (Refer to Document collaboration for steps).
Steps
Part of collaboration space setup:
OEM has made a redline comment on the component "Valve Cover" on BOM and similar markup on the associated Visual file.


OEM has also made markup comment on the associated Visual file of the structure.


Participants in the collaboration space.
Once the OEM has loaded all the information needed, required participants are added. These users will ultimately participate in the collaboration process via workflow.
This involves loading of:
a. Suppliers who are pre-defined in the SAP Ariba system.
b. Users who are not coming from the SAP Ariba system but otherwise defined in the SAP IPD system.
Note
SAP Ariba system integration is not covered in this lesson. The information is for reference only to understand that EPD allows out-of-the-box setup with SAP Ariba.
Suppliers who are pre-defined in the SAP Ariba system will be shown based on search criteria and can be directly added to the collaboration space.


Workflow process between OEM and Supplier to drive collaboration.
SAP IPD workflows allow easy business process mapping into collaboration, thus allowing closed-loop digital threads between different participants. Below is an example process where the OEM engineer and Supplier are working together to capture the logistic information of "Valve Cover" in an existing Evo valve guard assembly.
Note
SAP S/4HANA process is not covered and is here for reference only.
The supplier got a notification that collaboration is initiated by OEM engineer, and a task is assigned.

Note
The notification can be sent to participant by e-mail as well, for example, Outlook.Via dedicated workflow tasks which have links to shared documentation plus redline and markups, Supplier can easily zoom into the "Valve cover" component and provide needed logistics information quickly.

After going through shared information Supplier can confirm that task and send the information on "Valve Cover" by either adding another redline/markup or on the workflow task.

OEM receives the workflow back, and reviews/approves.
Result
Via dedicated collaboration spaces OEM captures the responses from different suppliers/external users, thus enabling the selection of the most desirable Supplier without losing the digital thread.