A Risk Management Example

1. Product Manager or Program Manager notifies team that the product has not completed all requirements of internal qualification, and that the internal qualification schedule is jeopardizing customer shipment dates.

2a. Product Manager leads discussion with relevant members of the following internal groups (System Eng’g, Quality, Memory Systems Eng’g, Adv. Packaging Eng’g, Product Test Eng’g) to evaluate their confidence in releasing the sales item BOM to RISK status in advance of full compliance to scheduled internal qualification.

2b. Product Management ensures that (is responsible for) the BOM package is complete and accurate with or without Core Team involvement, inclusive of test programs, prior to MCO release.

• SKU Level only status change from DEV to RISK acceptable.
• For Product Assembly Level and below, BOM must be complete (preferably at CPROD or PPROD status since DEV status ECOs require only minimal signature approvals, allowing for possible incomplete or down rev designs) prior to change to RISK.
• If an item is changing to RISK status, all lower levels of that BOM (including low value, D items, etc) must be also be moved to RISK or ACT.
• Clarification: If an item is ACT, there must be at least one path (down to the silicon if applicable) that is ACT. If there is only one path, it must be ACT and not RISK.

3. Reliability continues to execute to Qual Plan (64-01-00009).

4. Requestor completes RISK status code request form and includes MCO number in Agile on Risk Form. Mandatory approvals required are stated in Section 6 of this procedure. Others may be requested as appropriate. Current status of product qual and compatibility must be provided. 5. Upon approval, Doc Control routes MCO to CCB as an IMPLEMENTED change.

• Document Control notifies subcontractor(s) of change
• Planning may need to link BOM