ERP FOR MACALESTER: REPORT AND RECOMMENDATIONS
i. Lack of planned integration and efficient data-sharing
ii. Lack of Web applications for self-service, connecting other entities, etc.
i. Company viability vs. competing vendors
ii. Jenzabar plans for upgraded ERP system
iii. Anticipated costs of continued partnership with Jenzabar
iv. Jenzabar track record on execution and support
i. Twin Cities consortium, project launch in fall, 2002
ii. RFI, Macalester needs survey, Spring, 2003
iii. Presidents review, October, 2003, and system requirements process
iv. Vendor demos and costs
v. Evaluation by CFOs, CIOs and users
i. Functionality that supports efficiency
ii. Successful fit to Macalester's technology strategy
iii. Minimize risk and costs
i. Utilize new and familiar technologies to provide service and keep up with the competition with minimal expense
ii. Converge departments on integrated system unless
a. there is hard evidence of compromised mission-critical functionality AND
b. the area is of especially high strategic importance to college AND
c. data-sharing can be efficiently accomplished by other means.
iii. Consolidate technologies to simplify and minimize maintenance, support and staffing expense (minimize database, OS, hardware, report-writer diversity)
i. Migrating to [[system X]] with a 5 year budget of [[$ZZZZ]] OR
ii. Accept higher risk and some loss of functionality by
1. accepting JenzabarÕs product plan, adding JICS, CRMs and selected data marts
2. providing Web services by developing them in-house and integrating third-party products with Web programming capability
3. support improved business processes with additional database programming and system integration capability