In order to be admitted to a project it is normal for a new project team member to be asked to sign a version of the Base NDA that specifically includes the project being read into by the project lead.
The project level NDA is required in order that there be NO AMBIGUITY with regards to the responsibilities of the signatories over the confidentiality of the information passed as it is likely to include at some stage elements of the unprotected IP of the project.
At this point the access to the information about a project is restricted to the members of that project and under their control as to what is being recorded or not.
It is perfectly feasible for a project to complete the entire process without recording any unprotected IP on the PIPE system. Where such unprotected IP is recorded PIPE is under the same obligation as any other signatory of a Project NDA to treat the information so covered as confidential.
Due to the nature of the NDAs that PIPE has signed in the process of accepting projects we are restricted in what we can say within a public forum.
If you are a signed in PAN member then you already know the answer to this question and will have access to disclosures, potential project involvements and projects with which you are working.
Within the public domain all we can say is that there a wide variety of projects that come through the system from universities and research establishments across Europe, the UK and Switzerland, which relate to diverse problems and proposals for their solution using fresh R&D IP output.
If you want to know more then you will have to go through the AML / KYC procedures and sign into at least the general NDA governing the confidentiality of the date to which you may be exposed.
As a project you have several routes open to you to find an associate to assist you.
1: By registering the skills required for such an associate, the system can skill match to associates already known to the system and start the search for additional resources externally.
2: By publishing a 'help wanted' within the system to advertise the fact that you are looking in case you need to remind associates to update their own skill definition. This is useful as the skills taxonomy grows by the process of additional disclosures and projects coming onto the system, and associates may have not marked up the skill they posses simply because it was not an option to do so previously and they had not thought to do so. Ironically this is a greater problem where the associate has 'unconscious competence' i.e. it is so natural that they may forget that it is not common.
3: By finding the associate yourself from your own networking and then getting them to become an associate so you can rope them in.