Conducting locally and globally a network of partners is a hard task for every actor and especially for the company that initiates a product development project which necessitates close collaboration of partners. Some of these difficulties concern the run of the partners' network while others are associated with the run of the project itself and finally others are related to the information asymmetry between various partners (see Arend in [1]). Managers have to cope with them all. But, generally when a difficulty appears it is sourced somewhere else upstream in the process. We focus our study on one of these potential sources which is the product architecture. The idea is to use the product architecture and technical data, even incomplete, to identify the architecture of the network of partners as early as possible during the product development project. It allows clever negotiations and better definition of product & data exchanges protocols between future partners, aiming both at supporting the best the global product development project.