Download Design Win Management specifications.
- 5C1_DistributeProductList_V01_00_00
- PIP5C1_V11.00.00_DistributeProductList
- 5C2_RequestDesignRegistration_V01_00_00
- 5C2_RequestDesignRegistration_V01_01_00
- 5C2_RequestDesignRegistration_V01_02_00
- 5C2_RequestDesignRegistration_V01_03_00
- PIP5C2_V11.00.00_RequestDesignRegistration
- PIP5C2_V11.01.00_RequestDesignRegistration
- 5C3_CreateDesignWin_V01_00_00
- 5C3_CreateDesignWin_V01_01_00
- 5C3_CreateDesignWin_V01_02_00
- PIP5C3_V11.00.00_RequestDesignWin
- PIP5C3_V11.01.00_RequestDesignWin
- 5C4_DistributeRegistrationStatus_V01_01_00
- 5C4_DistributeRegistrationStatus_V01_02_00
- 5C4_DistributeRegistrationStatus_V01_03_00
- 5C4_DistributeRegistrationStatus_V01_04_00
- 5C4_DistributeRegistrationStatus_V01_05_00
- 5C4_DistributeRegistrationStatus_V01_06_00
- PIP5C4_V11.00.00_DistributeRegistrationStatus
- 5C5_QueryRegistrationStatus_B01.00.00A
- 5C6_NotifyOfDesignRegistrationRequest_V01_00_00
- PIP5C6_V11.00.00_NotifyOfDesignRegistrationRequest
- 5C7_Notify_OfDesignRegistrationConfirmation_V01_00_00
- PIP5C7_V11.00.00_NotifyOfDesignRegistrationConfirmation
- 5C8_NotifyOfWinClaimRequest_V01_00_00
- PIP5C8_V11.00.00_NotifyOfWinClaimRequest
- 5C9_NotifyOfWinClaimConfirmation_V01_00_00
- PIP5C9_V11.00.00_NotifyOfWinClaimConfirmation
- Cluster 5, Marketing Information Management, enables communication of marketing information, including campaign plans, lead information and design registration.
- PIPs for Segment 5C, Design Win Management (EC), enables design registration with suppliers, including requests for design-win registration at different phases of the design cycle and award of win based on predefined criteria.
| PIP | Title | Description |
|---|---|---|
| 5C1 | Distribute Product List | Provides the ability to notify partners of products eligible for design registration |
| 5C2 | Request Design Registration | Lets demand creators submit design registration requests -- as initial design registration documents or updates to existing design registrations -- and receive design registration responses from product providers |
| 5C3 | Create Design Win | Enables the demand creators to submit win claim requests and receive win claim responses from product providers at various stages of the design win process |
| 5C4 | Distribute Registration Status | Allows the product providers to send unsolicited notifications of design registration status changes to demand creators |
| 5C5 | Query Registration Status | Permits status requesters -- product providers or demand creators -- to request status of design registrations, including indicators of acknowledge, collaboration and continuation of submitted supplier business opportunities |
| 5C6 | Notify of Design Registration Request | Enables the demand creators submit design registration requests -- as initial design registration documents or updates to existing design registrations from product providers. |
| 5C7 | Notify of Design Registration Confirmation | Enables the product providers submit a responses to a design registration requests. |
| 5C8 | Notify of Win Claim Request | Enables the demand creators to submit win claim requests to the product providers at various stages of the design win process. |
| 5C9 | Notify of Win Claim Confirmation | Enables the product providers to provide a response to the demand creators win claim request at various stages of the design win process. |
| 5C1 | Distribute Product List |
|---|---|
| Provides the ability to notify partners of products eligible for design registration |
Business Process
The "Distribute Product List" Partner Interface Process (PIP) enables a provider to distribute a list of products eligible for design registration to a party needing differentiated products (demand creator). The following product types may be registered: key product, associated product, and development tools.
Before using this PIP to distribute a product list:
- A provider must have a strategic demand creation program.
- A provider must have defined a registration program for a demand creator based on terms and conditions, time frame for the registration, and target values that were previously agreed upon.
Upon receiving a list of eligible products, a demand creator may:
- Establish and maintain a list of eligible products, including an eligibility check that detects missing or erroneous product part numbers.
- Use PIP5C2, “Request Design Registration,” to submit a design registration.
Partners may communicate updates using this PIP or PIP5C2, “Request Design Registration.”
Should this transaction not complete successfully, the requesting partner executes PIP0A1, "Notification of Failure".
| 5C2 | Request Design Registration |
|---|---|
| Lets demand creators submit design registration requests -- as initial design registration documents or updates to existing design registrations -- and receive design registration responses from product providers |
Business Process
The "Request Design Registration" Partner Interface Process (PIP®) enables a party needing a differentiated product (demand creator) to request that a provider create or change a design registration. Such a request can occur at different stages of design registration definition or approval. For example, a request could be submitted as an initial design registration document or as an update to an existing design registration. Dates, confidence level, and detailed technical information can be changed as part of the updating and refining of a design registration. The following product types may be registered: key product, associated product, and development tools.
Upon receiving a design request, a provider assesses the request and responds by returning the design registration, the registration status, and other information. Status can be provided at either the core product level or complete (multiple parts) product level.
Registration status communicates the overall "stage" of a design win. A design win can either:
- Progress to accepted, win and production, or
- Be revoked
- Be pending
If a provider’s response to a design registration request is that the request is "pending,” the provider must later use, PIP5C4, "Distribute Registration Status," to resolve the pending status.
Before using this PIP:
- The two partners must have established terms and conditions for the design registration program.
- The provider must have provided a list of product eligible for design registration using PIP 5C1, "Distribute Product List."
Updates may be implemented with this PIP or PIP5C1, “Distribute Product List.”
Should this transaction not complete successfully, the requesting partner executes PIP0A1, "Notification of Failure".
| 5C3 | Create Design Win |
|---|---|
| Enables the demand creators to submit win claim requests and receive win claim responses from product providers at various stages of the design win process |
Business Process
The "Request Design Win" Partner Interface Process (PIP) allows a Demand Creator (who feels that previously agreed upon design metrics have been met) to submit a Win Claim Request. A Win Claim Request could be submitted at different stages of definition or approval by the Product Provider. If the Win Claim Request is accepted, the Product Provider commits to deliver the components specified in the Win Claim Request at the specified target resale price, in the estimated quantities, and on the indicated dates.
The PIP5C2, "Request Design Registration," is a precursor to this PIP, as a design registration must exist in order to submit or update a win claim.In order to start this PIP, the customer must have placed an order for a previously registered product with a Demand Creator and win metrics must be met. Key product, associated product, and development tools are all registerable. The Global Trade Item Number (GTIN) or Core Product Identifier has been provided via the PIP5C2, "Request Design Registration." A Win Claim could be submitted at multiple stages as the Design Win process advances. Five levels of win claim are available, as established by trading partners in a Trading Partner Agreement (TPA).
Should this transaction not complete successfully, the requesting partner executes PIP0A1, "Notification of Failure".
| 5C4 | Distribute Registration Status |
|---|---|
| Allows the product providers to send unsolicited notifications of design registration status changes to demand creators |
Business Process
The "Distribute Registration Status" Partner Interface Process (PIP) enables a provider to send an unsolicited design registration change to a party who has registered a design (demand creator). For example, a provider might send out updates for all registrations related to a sales representative in a specific territory. Registration status can be provided at the core product or the complete product levels.
If a business property is added or modified, requirements such as hierarchy, business property name, business property type, property definition, cardinality, constraints (if any), user notes (if any) are needed. If a code is changed, then code values and the source of the code values are also required.Registration status may be distributed at different stages of design registration definition or approval. Before using this PIP, the expectation is that the design registration has been created using PIP5C2, “Request Design Registration.” If a provider responds in PIP5C2, “Request Design Registration” that a request was "pending,” the provider must use this PIP to resolve the pending status.
Should this transaction not complete successfully, the requesting partner executes PIP0A1, "Notification of Failure"
| 5C5 | Query Registration Status |
|---|---|
| Permits status requesters -- product providers or demand creators -- to request status of design registrations, including indicators of acknowledge, collaboration and continuation of submitted supplier business opportunities |
Business Process
The "Query Registration Status" Partner Interface Process (PIP) enables a party to query for and obtain the status of a design registration from another party. The query and response process can work two ways:
- A party who has registered a design (demand creator) queries a provider for the status of a design registration, and the provider responds.
- A provider queries a demand creator for the status of a design registration, and the demand creator responds.
Registration status can be provided at the core product or the complete product levels.
Registration status may be distributed at different stages of design registration definition or approval. However, before using this PIP, a design registration must have been created using PIP5C2, “Request Design Registration.”
The query process begins when the requesting party sends a registration status query to the responding party. To facilitate communications, the query document includes both query constraint lines and incomplete results lines. After processing the query, the responding party completes the results lines and returns the information to the requesting party.
Should this transaction not complete successfully, the requesting partner executes PIP0A1, "Notification of Failure".
| 5C6 | Notify of Design Registration Request |
|---|---|
| Enables the demand creators submit design registration requests -- as initial design registration documents or updates to existing design registrations from product providers. |
Business Process
The "Notify of Design Registration Request" Partner Interface Process (PIP®) enables a party needing a differentiated product (demand creator) to request that a provider create or change a design registration. Such a request can occur at different stages of design registration definition or approval. For example, a request could be submitted as an initial design registration document or as an update to an existing design registration. Dates, confidence level, and detailed technical information can be changed as part of the updating and refining of a design registration. The following product types may be registered: key product, associated product, and development tools.
Upon receiving a design request, a provider assesses the request and responds by returning the design registration, the registration status, and other information. Status can be provided at either the core product level or complete (multiple parts) product level.
Registration status communicates the overall "stage" of a design win. A design win can either:
- Progress to accepted, win and production, or
- Be revoked
- Be pending
If a provider’s response to a design registration request is that the request is "pending,” the provider must later use, PIP5C4, "Distribute Registration Status," to resolve the pending status.
Before using this PIP:
- The two partners must have established terms and conditions for the design registration program.
- The provider must have provided a list of product eligible for design registration using PIP 5C1, "Distribute Product List."
Updates may be implemented with this PIP or PIP5C1, “Distribute Product List.”
Should this transaction not complete successfully, the requesting partner executes PIP0A1, "Notification of Failure".
| 5C7 | Notify of Design Registration Confirmation |
|---|---|
| Enables the product providers submit a responses to a design registration requests. |
Business Process
The "Notify of Design Registration Confirmation" Partner Interface Process (PIP®) enables a party needing a differentiated product (demand creator) to request that a provider create or change a design registration. Such a request can occur at different stages of design registration definition or approval. For example, a request could be submitted as an initial design registration document or as an update to an existing design registration. Dates, confidence level, and detailed technical information can be changed as part of the updating and refining of a design registration. The following product types may be registered: key product, associated product, and development tools.
Upon receiving a design request, a provider assesses the request and responds by returning the design registration, the registration status, and other information. Status can be provided at either the core product level or complete (multiple parts) product level.
Registration status communicates the overall "stage" of a design win. A design win can either:
- Progress to accepted, win and production, or
- Be revoked
- Be pending
If a provider’s response to a design registration request is that the request is "pending,” the provider must later use, PIP5C4, "Distribute Registration Status," to resolve the pending status.
Before using this PIP:
- The two partners must have established terms and conditions for the design registration program.
- The provider must have provided a list of product eligible for design registration using PIP 5C1, "Distribute Product List."
Updates may be implemented with this PIP or PIP5C1, “Distribute Product List.”
Should this transaction not complete successfully, the requesting partner executes PIP0A1, "Notification of Failure".
| 5C8 | Notify of Win Claim Request |
|---|---|
| Enables the demand creators to submit win claim requests to the product providers at various stages of the design win process. |
Business Process
The "Notify of Win Claim Request" Partner Interface Process (PIP) allows a Demand Creator (who feels that previously agreed upon design metrics have been met) to submit a Win Claim Request. A Win Claim Request could be submitted at different stages of definition or approval by the Product Provider. If the Win Claim Request is accepted, the Product Provider commits to deliver the components specified in the Win Claim Request at the specified target resale price, in the estimated quantities, and on the indicated dates.
The PIP5C2, "Request Design Registration," is a precursor to this PIP, as a design registration must exist in order to submit or update a win claim.In order to start this PIP, the customer must have placed an order for a previously registered product with a Demand Creator and win metrics must be met. Key product, associated product, and development tools are all registerable. The Global Trade Item Number (GTIN) or Core Product Identifier has been provided via the PIP5C2, "Request Design Registration." A Win Claim could be submitted at multiple stages as the Design Win process advances. Five levels of win claim are available, as established by trading partners in a Trading Partner Agreement (TPA).
Should this transaction not complete successfully, the requesting partner executes PIP0A1, "Notification of Failure".
| 5C9 | Notify of Win Claim Confirmation |
|---|---|
| Enables the product providers to provide a response to the demand creators win claim request at various stages of the design win process. |
Business Process
The "Notify of Win Claim Confirmation" Partner Interface Process (PIP) allows a Demand Creator (who feels that previously agreed upon design metrics have been met) to submit a Win Claim Request. A Win Claim Request could be submitted at different stages of definition or approval by the Product Provider. If the Win Claim Request is accepted, the Product Provider commits to deliver the components specified in the Win Claim Request at the specified target resale price, in the estimated quantities, and on the indicated dates.
The PIP5C2, "Request Design Registration," is a precursor to this PIP, as a design registration must exist in order to submit or update a win claim.In order to start this PIP, the customer must have placed an order for a previously registered product with a Demand Creator and win metrics must be met. Key product, associated product, and development tools are all registerable. The Global Trade Item Number (GTIN) or Core Product Identifier has been provided via the PIP5C2, "Request Design Registration." A Win Claim could be submitted at multiple stages as the Design Win process advances. Five levels of win claim are available, as established by trading partners in a Trading Partner Agreement (TPA).
Should this transaction not complete successfully, the requesting partner executes PIP0A1, "Notification of Failure".