MICROCHIP FRM-41036-137 Integrated Circuits Instructions

July 26, 2024
MICROCHIP

Product Material Compliance (PMC) Guide for FRM-41036-137

FRM-41036-137 Integrated Circuits

  1. Scope: All Microchip products
    a. ICs, modules, systems, boards, etc. (Includes new products and products undergoing REV).
    b. Dev Tools have a separate established process and are exempt from FRM-41036-137.

  2. Filling FRM-41036-137
    a. List all CPNs and, if applicable, all associated package codes that are affected.
    b. At least one of question 1 or 2 must be answered Yes or No.
    i. If one or more of the products are an IC or discrete, question 1 applies.
    ii. If one or more of the products are a module, system, board, or other complex product, question 2 applies.
    c. If either question is answered NO, then the PMC information MUST be acquired in a later step of the NPI/Rev process.
    i. If FRM-41036-137 is being filled during the last step of the NPI/REV process, the question(s) cannot be answered no, as the PMC information must be provided to the PMC team before the product can be RTP’d or REV’d.

  3. PMC team approval
    a. What is needed
    i. Track 1 (MPC) ICs and discretes: The material content declaration (MCD) or BOM is required for each package code being affected. FRM-50207 is the official template for providing BOM and/or MCD information (see below).
    1. If filling the form for a REV, then the PMC team likely have the required information. However, if the REV is changing the material composition of the package, then a new BOM and/or MCD will be required.
    2. If filling the form for new CPNs in existing package codes, the PMC team likely has the required information.
    3. If filling the form for new CPNs and new package codes, each new package code will need information sent to PMC team for review.
    a. Information can also be provided at the mask level, if applicable.
    ii. Track 2 (non-MPC) ICs and discretes: The MCD is required, in FRM-50207 format (see below). If an MCD is not available, and cannot be created, then a full set of up-todate PMC declarations (RoHS, REACH, China RoHS, etc.) is required.
    iii. Track 1 (MPC) modules: MCD is preferred. If MCD is not available, submit a Compliance Service Request (CSR) in eSign (see below).
    iv. Track 2 (non-MPC) complex products (boards, systems, etc.): MCD is preferred. If MCD is not available, submit a CSR in eSign (see below). If the BOM is not available or is too complex to process in CSR, a full set of up-to- date PMC declarations (RoHS,
    REACH, China RoHS, etc.) is required.
    b. How to acquire approval and signature
    i. If using Waterfall, the PMC team’s signature can be acquired via email (ESG_Assurance@microchip.com) with either a screenshot of the completed Waterfall page, or a completed copy of FRM-41036-137.
    ii. If not using Waterfall, the PMC team’s signature must be acquired via email (ESG_Assurance@microchip.com) with a filled copy of FRM-41036-137.

  4. Helpful links and tools
    a. FRM-41036-137: Product Material Compliance NPI and Rev Checklist
    b. FRM-50207: Product Compliance Data Collection Tool
    c. Compliance Service Request (CSR)

Read User Manual Online (PDF format)

Loading......

Download This Manual (PDF format)

Download this manual  >>

Related Manuals