Apriori Implementation Team - Minutes
February 13, 1996 (1:30 - 3:30)

Attending: Mike Kearney, Katie McGee, Emily Corse, Tony
Olejnik, Lila Shapiro, Kristin Nelson

- Meeting Agenda

Meeting Summary:
- apteam@sas is fully operational
- Summary of February 9th Restructuring Meeting by Katie
- Discussion of Lessons Learned from Princeton Site Visit
- Brainstorming to identify important issues for implementation plan
- Microsoft Project will be used for the project plan
- Emily will be the Plan Keeper


- Mike K. will distribute a skeleton copy of Kristen's minutes to use as 
a template for other  minute writers.
- Mike K. will contact CMU (Karen van Dusen) and Harvard (Annelise 
Martin) for their advice regarding whom to send to training. Katie will 
speak with her contact at Indiana.
-Lila and Katie will prepare a more complete list of roles and 
responsibilities for theSYSADMIN plan item.
- Emily and Kristen will prepare a more complete list of roles and 
responsibilities for the database admin plan item.

Meeting Details:

- February 9th Restructuring meeting (Katie)
   Pilot project has high visibility with senior management
   3 major items of discussion relating to primary support:
    Ability to escalate problems and inform managers
    Ability to share problem solving information across organizations
    Tracking contacts by individual users (1 user, 1  problem, multiple 

- Status of pilot project draft 'charge to the team' (Mike K)
   Mike K. sent high points of last weeks team discussion to Mike Eleey:
      Needs to be described as an ISC/SAS project, not First Call/SAS
      Need to examine carefully to remove ISC-centric terminology
      Need to add a formal plan to the list of deliverables

   Current status is that Mike E. will incorporate suggested changes made
by ISC staff and others, then forward the draft to the team for its
suggested changes. We will postpone our Thursday (2/15) deadline for
comments on the draft until we have had a chance to review the modified
version. Then we will hammer out our suggested 'final' version.

- Princeton Post Mortem
   Trip was worthwhile
    What we learned:
      Initial planning should concentrate on process
      Need for Unix expertise somewhere in the implementation made evident,
      particularly in the area of shell scripting (Apriori triggers).
      After discussion, it was agreed that the Unix expert did not need 
      to be the one attending Apriori implementation training.
      Implementation can work in a changing environment IF there is 
      continuity on the implementation team. Organizational, structural, 
      and process changes can be  
      accommodate much more easily than staff turnover on the team.
      Even places like Princeton have trouble delivering 'Help Desk' 

- Brainstorming for the Plan

   Affinity analysis ('group the postits') yielded the outline given below.

   Major discussion topic: what did this accomplish? Conclusions: some
consensus on major plan topics. Most important: we need to get the Project
scope items into the 'charge to the team', to the extent possible. We will have the
opportunity to do this when we 'have at' the draft. 

Project scope

Determine scope of support (faculty, staff, students, other clients for 
Define groups with informal interest in the project (friends)
Determine progress (success/failure) indicators
Define group(s) of people with formal interest in project
Determine necessary approval/signoffs
Obtain commitment of time by people with right skill set
Get final version of charge to team

External communications

Develop project web page for communication
Develop plan for communicating project status

Process Definition

Determine and document current support processes
Determine and document potential processes in a restructured environment
Determine commonalties and differences within pilot group and other groups

Desktop configuration

Determine desktop applications for access (e.g., X-clients?)
Determine hardware requirements
Determine printing needs
Determine local and remote access

System administration

Define roles & responsibilities of system administrator
Determine UNIX account initiation procedures & strategies
Develop backup & restore plan & strategies
Install AprioriDatabase Administration

Database Administration

Define roles & responsibilities of database administrator
Determine database account initiation procedures & strategies
Determine process for ongoing database maintenance
Configure Apriori

Database design

Determine process for reports generation
Identify the source of client data
Define process for client data updates
Determine clients & client users

Training, Support, Documentation

Attend Apriori administration training
Develop user training plan
Train users
Determine Documentation Needs 
Create documentation
Determine plan for ongoing user support

Minutes recorded by Mike Kearney.  Please notify of any changes.