Boundaries of Large Systems Relative to Windchill Projects

Windchill Risk and Reliability 11.1

Description of the problem:

-Large system, consisting of multiple subsystems.

-Reliability data from multiple sources. (service data, surrogate data, test data)

-Rich mix of part types (electronic, mechanical, electromechanical, hydraulic, custom fabricated metal parts, etc)

-BOMs will be imported from excel

-System definitions and reliability data attached to parts within Windchill will be exported back out to either excel or delimited tables (csv, tab delimited, etc)

-BOMs for subsystems are still undergoing change

It's tempting to build one big project and create a system tree, using the power of Windchill to tie it all together; but, does it make sense to firewall the overall effort into sub-projects for ease of handling design changes and compartmentalizing the final export?

Would this be a good use of the "Common Library Project" concept within Windchill?