2.1 Program Administrator (PA) - Each Lab and Program will establish procedures for selecting the PA for their organization.
All users with the role of PA have the ability to take and assign ownership of any proposals where their organization is the lead. By taking ownership, PAs will have the ability to read and edit the proposal. PAs will always be able to read any proposals where their home organization is the lead.
2.2 Administrative Support Team (AST) -Designate those administrators here that are expected to work on this proposal.
For an administrator that is not a PA to have the ability to work on a proposal, they must be selected here. For proposals where more than one Lab or Program are participating, all adminstrative staff from the participating organizations added in Question 1.7 will be available for selection here.
3.1 UCAR Proposal Team Members - UCAR team members may be added with roles as either a Co-PI, Co-I, Collaborator or Other Personnel.
Selection of UCAR staff here will allow selection of that individual on the budget entry with associated salary information. The staff entry on the budget will allow for the addition of all staff from the home organization. In order to add participants from another UCAR organization, add the organization in Question 1.7 and add the individuals participating on Question 3.1.
3.2 Non UCAR Team Members - This allows entry of team members to be added with contact information and their role in the proposal. Note that the PandA System is for UCAR internal users only.
3.3 Student Involvement (Undergraduate, Graduate and Post Doc) - This data is needed for PACUR and the NSF Post-Doc Mentoring Plan if required.
3.4 Foreign Persons