Yours

5.4: Project Management Considerations

Managing Technology Projects · LibreTexts

0%

Contents

    Text

    Size
    100%
    Theme
    Typeface
    Line length
    Spacing

    From LibreTexts, under CC BY 4.0, as the source states it; its equations are written in TeX, which the PDF shows typeset. This page at LibreTexts.

    First, some general observations:

    • Many companies start very late on compliance projects.
    • Sometimes an outside consultant needs to be the bearer of the news that compliance is not optional but is a necessity.
    • Starting late puts enormous pressure on the project team to meet a directive or regulation's deadline.

    Assuring BOM Compliance can be extraordinarily labor-intensive:

    • Chasing down certificates of compliance of parts from suppliers can consume a lot of resources and take a lot of time.
    • Assuring BOM Compliance by checking BOM roll-ups is an iterative process and is necessary to show progress and actionable exceptions.
    • Maintaining From-To lists (Non-compliant to Compliant) is desirable to ease the work of design teams.
    • There is a lot of paperwork requesting certificates of compliance of parts from suppliers, filing ECOs and MCOs to clean up the BOM, etc.

    Changes in part numbering

    This is a brief overview of some of the considerations associated with product part numbering and downstream effects on the work required of the project team.

    • Marketing/Sales order number (e.g., 12345)
      • Different approaches have been used. Many think it best to change the P/N, e.g., to 12345G (G suffix for “Green”) or 12345PF (as in Pb-Free)
      • However, some contracts with customers specify the part number, so changing the part number could be an issue.
      • Once you decide on how to handle the product part number, it is important to stick to your decision as it affects order management systems, Return Merchandise Authorization (RMA), other IT systems, etc. Changing the decision on this in the middle of the project, or worse toward the end of the project, can have a major impact.
    • Manufacturer P/N (e.g., 912345-xx-yy)
      • If xx=“Type” and yy=Rev, then define a new xx field to designate a RoHS assembly.

    High-level schedule

    This is an example of a high-level schedule for a company getting a late start on RoHS compliance. The full schedule with all relevant items would be considerably larger.

    Details of the schedule are discussed in text.
    Figure \(\PageIndex{1}\): High Level Schedule. (Copyright; Robert Slate, CIS 79 course materials)
    Accessibility Note
    1. Task 1: Determine applicable products, 5 days, starting 8/1/05, ending 8/5/05, no predecessors, Resources: Product Management.
    2. Task 2: Determine compliant SKU part numbering, 10 days, starting 8/8/05, ending 8/19/05, predecessor Task 1, Resources: Sales, Product Management.
    3. Task 3: Gather component certifications from suppliers, 150 days, starting 8/8/05, ending 3/3/06, predecessor Task 1, Resources: Operations.
    4. Task 4: Add certs to components in Agile data base, 140 days, starting 8/22/05, ending 3/3/06, predecessor Task 3SS+10 days, Resources: Component Engineering.
    5. Task 5: Create SKU BOM compliance tester tool, 10 days, starting 9/7/05, ending 9/20/05, no predecessor, Resources: PM.
    6. Task 6: Validate SKU Compliance (compliant BOM), 168 days, starting 9/21/05, ending 5/12/06, predecessor Task 5, Resources: PM, Quality.
    7. Task 7: Remove non-compliant components from AVL via MCO, 67 days, starting 12/14/05, ending 3/16/06, predecessor Task 6SS+60 days, Resources: Eng PM, Operations.
    8. Task 8: File ECOs for proto SKUs, 10 days, starting 3/17/06, ending 3/30/06, predecessor Task 7, Resources: Eng PM.
    9. Task 9: Assemble proto SKUs with replacement parts, 20 days, starting 3/31/06, ending 4/27/06, predecessor Task 8, Resources: Operations.
    10. Task 10: Eng test of changes SKUs, 15 days, starting 4/28/06, ending 5/18/06, predecessor Task 9, Resources: HW Eng, SQA.
    11. Task 11: Release ECOs to Manufacturing for compliant SKUs, 10 days, starting 5/19/06, ending 6/1/06, predecessor Tasks 10, 7, 6, Resources: Eng PM.
    12. Task 12: Manufacture compliant SKUs, 20 days, starting 6/2/06, ending 6/29/06, predecessor Task 11, Resources: Operations.
    13. Task 13: Archive proof of SKU compliance, 5 days, starting 6/2/06, ending 6/8/06, predecessor Task 11,6, Resources: PM.

    5.4: Project Management Considerations is shared under a CC BY 4.0 license and was authored, remixed, and/or curated by LibreTexts.