+ All Categories
Home > Documents > ERM System Acquisition and Implementation A Case Study Presented to the Oct. 14, 2008.

ERM System Acquisition and Implementation A Case Study Presented to the Oct. 14, 2008.

Date post: 27-Mar-2015
Category:
Upload: nathan-gibbs
View: 216 times
Download: 1 times
Share this document with a friend
Popular Tags:
12
ERM System Acquisition and Implementation A Case Study Presented to the Oct. 14, 2008
Transcript
Page 1: ERM System Acquisition and Implementation A Case Study Presented to the Oct. 14, 2008.

ERM System Acquisition and Implementation

A Case Study

Presented to the

Oct. 14, 2008

Page 2: ERM System Acquisition and Implementation A Case Study Presented to the Oct. 14, 2008.

Troutman Sanders LLP

• International law firm with 685 attorneys and 12 offices in North America, Europe and Asia

• Founded in 1897• Clients range from Fortune 500 companies to

small businesses; non-profit organizations to individual entrepreneurs; multinational corporations to federal and state agencies

• Over 40 areas of legal practice

Page 3: ERM System Acquisition and Implementation A Case Study Presented to the Oct. 14, 2008.

Requirements

• Forced entry and validation of client/matter numbers

• Accessibility to on-line services if validation software down

• Password management

• Ability to track usage of electronic subscriptions

Page 4: ERM System Acquisition and Implementation A Case Study Presented to the Oct. 14, 2008.

Key Points of Analysis

• Features

• Security

• User Friendly

• Customer Service

Page 5: ERM System Acquisition and Implementation A Case Study Presented to the Oct. 14, 2008.

Results

• Recommend OneLog

• Not implemented

Page 6: ERM System Acquisition and Implementation A Case Study Presented to the Oct. 14, 2008.

Implementation

• Given go-ahead with one month • Brief review of options• Set-up, installation and training• Develop instructional materials• Go-live

Page 7: ERM System Acquisition and Implementation A Case Study Presented to the Oct. 14, 2008.

Problems at Implementation

• Cultural change• E-mail• Passwords not known• Perceived loss of functionality• Isolated issues

Page 8: ERM System Acquisition and Implementation A Case Study Presented to the Oct. 14, 2008.

User Experience

Page 9: ERM System Acquisition and Implementation A Case Study Presented to the Oct. 14, 2008.
Page 10: ERM System Acquisition and Implementation A Case Study Presented to the Oct. 14, 2008.
Page 11: ERM System Acquisition and Implementation A Case Study Presented to the Oct. 14, 2008.

Administrative Features

• License enforcement• Detailed reporting• Real time usage analysis• Disconnect users• Password expiration• View unused resources• Costs/time or pages viewed• Administrative testing

Page 12: ERM System Acquisition and Implementation A Case Study Presented to the Oct. 14, 2008.

Success?

• Forced entry & validation – recovery greater than predicted

• Accessibility – software down, access to resources available

• Password management – primarily used for trouble-shooting

• Tracking usage – limited use currently


Recommended