Notes from the Meeting:

1. ADMINISTRATIVE SYSTEMS: What does it take to go to a new system?
   • Training is an important issue from the beginning.
   • Integrated software requires a much larger investment of time and leadership on the functional side.
   • Nee to use the vendor to help review the re-engineering of processes.
   • Requires high level sponsorship of any technical project.

     "Shadow" systems developed over the years because of inadequacy of central systems, must be brought into the project.

2. IN HOUSE VS. COMMERCIAL SOFTWARE
   • Analysis and design are the same no matter the type of software.
   • Re-engineering is a major result of an integrated product.
   • Functional advise and support is critical to the process.
3. ACCESS: WEB access is a really important component. Vendors are in the process of developing products. Tailoring the product is important to maintaining the specific services of the institution.

4. DATA WAREHOUSING
   • Reporting can slow the system down. Data warehousing reduces the load by moving it to somewhere else.
   • Supports the decision making process of the users, so it is not necessary for the data to be real time.
5. PC VS. MAC: Everyone is dealing with mixed environments on campus.

6. ORGANIZATIONAL STRUCTURE IN THE IS
   • It is important to define the functional needs.
   • FTE does not apply to supporting projects anymore. Collaboration between the users and the technical staff is increasing.
   • Services to support users have to be strong but users cannot impinge on the time needed to do technical work.
   • Several schools are reorganizing to:
     be able to pay better
     reassign functions
     merge administrative and academic computing and networking.
   • Structure needs to support the demand and to reduce the "sacred cows" of the IS and the users.
   • The new environment of administrative computing is bringing groups together who haven't worked closely together in the past.
   • Are users becoming more sophisticated or are just their expectations rising?
7. WHAT CAN NWHEAT DO FOR US?
   • Explore group solutions to licensing software
   • Support workshops
     data warehousing
     recommend NWAAC have a large workshop on access, security, and user authentication allow NWHEAT members who are not members of NWACC be allowed to attend
8. SHOULD THE ADMINISTRATIVE COMPUTING SESSION CONTINUE IN THE NWHEAT MEETINGS?
   • expand and organize a more detailed administrative computing group
   • meeting will facilitate computing integration on campuses
   • help to identify and address customer relation issues
   • identify and address re-engineering issues
   • develop a mentoring program where staff can share in an organized fashion between schools.
   • review grant possibilities for organizational development that may be available to us as a collaborative group

stantonk@elwha.evergreen.edu
rellis@ups.edu
weisman@pacificu.edu
rminato@willamette.edu
kpitter@willamette.edu
barnold@willamette.edu
pietrasp@elwha.evergreen.edu
bairdd@elwha.evergreen.edu
rahnr@elwha.evergreen.edu
dasema@plu.edu
gump@vancouver.wsu.edu
greco@lclark.edu
dasema@plu.edu