January 6, 2006
CORE Application Team Meeting

Attendance: Kelley Conrad (Team Leader), Patti D’Avignon, Stacey DeBrot, Peggy Jacobks, Kathy Krentz, Brenda Mitcheltree, Darlene Peklar, Mary Smith, Patricia Werly
Absent: Beda DuBois, Terri Jourden

1. Minutes/Agenda
Kelley distributed an agenda and asked if there were any corrections to the Dec. 15 CORE meeting minutes. The minutes were approved with the following correction from Jean Roberts: under “5. Shadow Systems” - change the name of the FIT Implementation Team to FIT Implementation Oversight Committee.

2. CORE On-Site Consulting
Kelley announced the on-site consulting will take place on Feb. 2-3 (Thursday-Friday). It’s currently scheduled for 9-5, but she will try to get it changed to 8:30-4:30, which would be better for all team members.

3. Homework/Spreadsheet Issues

Kelley distributed four handouts: CORE Workshop Homework M-87 Demographic Data – People
M-87 Demographic Data – Organizations

Some CORE Team Decisions Needed
The first three items came from Carol Hogan (Datatel trainer). Kelley compiled the CORE Team Decision draft from her CORE training notes (with Carol Hogan). Kelley discussed the “Homework” pages with Kam (OIT) for clarification, and they concluded that Carol may have already added some of the columns to the M-87 Data spreadsheets that were referred to in the homework handout. The individual homework items were reviewed and discussed by team members today. The M-87 Data spreadsheets were also reviewed, and discussion included the importance and recognition of “code” vs. “data” fields, setting standards, developing protocol, identifying REQUIRED fields, and setting decision priorities and timelines (focusing on data needed for the first module implementation – Financial Services 6/01/06). It was suggested that another column be added for “Module Used” identification to help prioritize tasks. Several questions were raised and Pat suggested having Perry attend our next meeting via speaker phone to help resolve these items. Demographic data and code needs regarding: prefixes (i.e. Mr., Ms.), suffixes (i.e. Jr., Dr.), addresses (i.e. permanent, parent, mailing, billing), telephone numbers and other information were discussed at length. Pat warned against “customizing”, but she did feel that we should be able to set code standards, drop down box values and field lengths to meet our needs. Some of the issues outlined on the CORE Team Decision sheet were discussed. It was noted that some of these items aren’t really needed in “CORE”; however, many are critical to CORE and the financial module implementation. Team members are asked to review the demographic data spreadsheet items and determine needs and desires, especially within their respective departments/offices.

4. Facilities Report
Stacey reported that she has gathered most of the facility and location information needed in CORE. However, there are some data fields in CORE that she questions as they relate to MCC. This information is critical to CORE set-up. There was also discussion regarding the continued use of our current EMS facility management system. According to Kam in OIT, EMS will continue being used and plans include increased usage of this system by other departments (i.e. media). This is another concern to discuss with Perry, so we’re sure to include the necessary data for efficient use in both systems.

5. Next Steps
After discussion and clarification, the Team agreed on the following:

• Kathy will get the “default” codes that are in the Colleague CORE “training” application for everyone’s review. 
• Pat will get the legacy system codes that are currently used (for all team members). 
• Each team member should review the handouts and code lists, and bring their individual code and data recommendations to the next CORE meeting (Friday, Jan. 13 @ 8:30 a.m. in the President’s Conference Room). 
• This group will then discuss the separate proposals and prepare composite “Team” recommendations for each element, which each team member will then review with their respective department personnel and any other appropriate groups. 
• After discussion with departments, final recommendations will be formulated and sent to the FIT Oversight Implementation Committee.