BOM Collections (Formerly BOM Groups)

[ptc-2219781]

Hello Windchill Product Analytics Community,

We are currently working on the implementation of BOM Collections in Windchill Product Analytics. The BOM Collection functionality will be very similar to the functionality in Insight and EMARS known as BOM Groups.

In the BOM Collection functionality users will be able to:

1) Create a BOM Collection

2) Add BOMs to the collection

3) Remove BOM from the collection

4) Add Individual BOM Reports to the collection (BOM Status Report, Material Content Reports, REACH Reports)

5) Add BOM Summary Reports to BOM Collection

6) Send Reports to Queue

While we would love the implement all the functionality and reports overnight reality is that we will have to prioritize the implementation.

Based on conversations with customers we have identified the following priority for implementing the reports:

1) Data Completeness Reports, this report will identify the unreported parts in the BOM Collection

2) Custom SoC, this report allows the user to identify a custom list of substances and thresholds and then identify the parts that contain these substances.

3) BOM Collection Summary (see posted document)

4) BOM Status reports

5) Material Content Reports

6) REACH Reports

We are still weighing out the most critical items for implementation. Could individuals please let me know their needs and the importance of using the Custom SoC Report?

Please let me know your thoughts on prioritization. Also if there are other reports you would like to run against BOM Collections let me know this also.

[vranganathan]

Is there any limitation on size of BOM collection (number of BOMs in the collection)?

[ShrikantSolanke]

Hi Varathan,

As such there is no limit on size of BOMs in BOM Collection set in WPA. User are able to add as many of BOMs in BOM Collection at multiple of 1000 BOMs at one time.

Actually report generation time is directly proportional to the total flat bom lines across all BOMs in the BOM Collection.

e.g., If 5 BOM is added in BOM Collection in which each BOM has 50 leaf parts (CPN) then resulted flat bom lines is equal to 250 (each bom has around 50 bom lines so 50 *5).

So according to that we had tested maximum number of BOMs from BOM Collection successfully as follows –

• RDR Part Sourcing Summary Report: Report generated with 3 million flat bom lines.
• EC Data Completeness Report: Report generated with 0.5 million flat bom lines.

[MarkWilliford]

Varathan

In addition to the information provided by Shrikant, there are available configuration parameters related to the generation of BOM Collection reports that could be useful for tuning the application for specific needs. Please refer to the Configuration Guide chapter titled "Configuring the Background Job Processing for a BOM Collection Report" for more details on these configuration points and troubleshooting recommendations.

Mark