who “owns” the data? who “owns” the data? dr. joy hatch harford community college educause...
TRANSCRIPT
Who Who “Owns”“Owns” the Data? the Data?
Dr. Joy HatchDr. Joy HatchHarford Community CollegeHarford Community College
EDUCAUSE Southeast Regional Conference
Who Owns the Data?Who Owns the Data?Things to DiscussThings to Discuss
• ERP Implementations
• HCC Background
• HCC Experience
• What Worked
• What Did not Work
• Lessons Learned
ERP ImplementationERP ImplementationTypical ImplementationTypical Implementation
• Technology staff does all the work
• End-user provides guidance
• Nights turns into weeks of extra work
• Lasts 18-36 months
ERP ImplementationERP ImplementationAnyone Can Do ThisAnyone Can Do This
“There is no shortage of literature on how to put together an implementation team and deploy hardware and software to support your administrative processes.”
Lea Pennock and Rick BuntEDUCAUSE QUARTERLY
HCC Selected HCC Selected a Different a Different
RouteRoute
BackgroundBackgroundHarford Community CollegeHarford Community College
• Located in Bel Air, Maryland(one hour north of Baltimore)
• Only Higher Education Institution in the County
• 5,541 FT Credit Students
• 15,252 Non-Credit Students
• AA Degrees and Certificates
BackgroundBackgroundTechnology StaffTechnology Staff
• Desktop Support /AV- 7• Network - 3• Telecomm - 1• Web - 1• Application Developers - 2• Banner Support - 1• DBA - 1
BackgroundBackgroundAdministrative SystemsAdministrative Systems
• In-house Program (1980’s)
• CUFFS
• SCT/Banner (1996-98)– Implementation Start - 1996–Human Resources - 1997–Student - 1997–Finance/Development - 1998
Banner Banner Implementation DecisionsImplementation Decisions
• Decision made to move the responsibility for conversion from IT to the users
• No changes to the database
• Process took approximately 30 months
BannerBannerUser InvolvementUser Involvement
• Users made decisions–What data to convert
–Which fields converted to what
–How to implement and what process to put in place
–What security should be implemented
BannerBannerTechnology InvolvementTechnology Involvement
• IT Provided–Programming Assistance
–Technical Procedures
–Patches and Updates
–Database Integrity
–Data Backups
–“Someone to Talk to”
BannerBannerNew ImplementationsNew Implementations
• Users are testing the new release (Banner 7) now
• Users will create their own test plans (some better than others)
• Users resolve any problems and find a resolution
BannerBannerLuminus DecisionLuminus Decision
• Banner Web Portal
• Currently investigating and talking with other schools
• Will not proceed without user’s approval and buy-in
BannerBannerImplementation StoriesImplementation Stories
• Student Module–Well implemented
–Makes use of all available options
–Online services deployed
–On top of changes/problems
–Very detailed testing plans
BannerBannerImplementation StoriesImplementation Stories
• Human Resources–First to implement–Still has some issues
• Finance–Last to implement–Several processes still done
manually–Requires lots of support
BannerBannerImplementation StoriesImplementation Stories
• Development–Badly implemented due to
personnel changes–Almost needs to start over
• Common Modules–SSN Conversion
What is What is happening happening TODAY?TODAY?
Current StatusCurrent StatusUsers are the SPECIALISTSUsers are the SPECIALISTS
• Totally responsible for data–Test new releases
–Correct Problems
–Change Processes
–Call SCT/Banner for Support
–Purge Data
–Determine Permissions
Current StatusCurrent StatusIT is the SUPPORTIT is the SUPPORT• Provide technical support–Programming Assistance–Patches and Updates–Database Integrity–Data Backups–Security Changes–Basic/Common Training–Some Reporting
Who Owns the Data?Who Owns the Data?What WorkedWhat Worked
• Got users involved
• Required less technology personnel
• Users truly KNOW the data
• User testing of new releases provided smooth transition
Who Owns the Data?Who Owns the Data?What Did NOT WorkWhat Did NOT Work
• Staffing can determine the failure or success
• Testing process may not be thorough
• Training is left to the end users - often does not happen
Who Owns the Data?Who Owns the Data?Problems RemainingProblems Remaining
• Reporting–Changing reporting software–Conversion of reports and user
training still happening
• Security–Not consistent across modules
• Training–No established plan
Who Owns the Data?Who Owns the Data?Lessons LearnedLessons Learned
• Get users involved EARLY(especially with process changes)
• Less technology support/ personnel will be needed
• Users will KNOW their data
• Level of uncertainty is always present
