|
A. |
Attending Regional student meetings and making presentations on S-PACs (15
minutes minimum) |
|
B. |
Targeting large schools, medium-to-large schools that have never held an S-PAC, and
schools that held an S-PAC two or more years earlier; calling Student Branch officers and
Student Branch Counselors directly. |
|
C. |
Writing form letters to selected schools encouraging them to plan S-PACs (addressed to
Student Branch Counselor and Student Branch Chair) |
|
D. |
Maintaining contact with Regional PACE Coordinator and other sources of funding for
S-PACs |
|
E. |
Maintaining contact with Regional S-PAC Support Coordinator. |
|
F. |
Contacting RAB/SAC/SPAA Chair for Branch-related or RAB funding issues. |
|
A. |
S-PAC format |
|
B. |
Speaker selection (approves the roster of speakers, especially the national-level
speakers whose travel is reimbursed by SPAC) |
|
C. |
Selection of conference date, avoiding conflict with exams and major campus events. |
|
D. |
IEEE interfaces, Section, Area, and Region (requesting/obtaining funds/support, local
speakers, general participation, local engineering/industry support) |
|
E. |
Publicity techniques |
|
F. |
Ticket sales |
|
G. |
Interface with Department Chair or Engineering School Dean |
|
H. |
Answers questions about: |
|
|
- Size of committee and delegation of tasks |
|
|
- Faculty reception: participation, classes held at S-PAC or canceled |
|
|
- Ticket sales: when started, number sold (three weeks before conference) |
|
|
- Funding: contacts, problems, expenses |