Plenary talk on “The Lecturer's MIS Menu: Why Silver Service Is Off And Drive-Thru's In” given by Stephen Tanner at the IWMW 2002 event.
See http://www.ukoln.ac.uk/web-focus/events/workshops/webmaster-2002/sessions.html#talk-tanner
Unit-IV; Professional Sales Representative (PSR).pptx
IWMW 2002: The Lecturer's MIS Menu: Why Silver Service Is Off And Drive-Thru's In
1. The Lecturers MIS Menu:
Why Silver Service Is Off and
Drive Thru’s In
Stephen Tanner
Head of IT Services
2. Scene Setting
• Experiences of FE (with some HE)
• Delivering ‘management’ information to
lecturing staff
• Use of commercial systems with Web
components
3. Situation Pre 1998
• MIS as Dark Art
• Ownership & Trust?
• Mix of linked & disparate systems
• Only ‘timetabling’ for lecturers
4. Drivers for Change
• Change in management, change in culture
– Open attitude, open information
– Corporate responsibility
• Not ‘real’ world
– Tribal Systems
• Home grown exposures
– Year 2000
– Technology
– Complexity
– Individuals
5. Strategy
• Single integrated information source
• CIS not MIS
– Central management, local responsibility
• Openness and ownership
– Information triggers action
• Accessibility through simplicity
Systems to deliver?
6. Systems
• Integrate as far as possible
• Commercial partnership
• Best of breed for some
– timetabling
– HR
• All to have Web components
– Views onto same database
7. CURRICULUM
ENRENQS APPS
STUEXAM REGIS
ISR LINKS FEES
FD EBS
Cedar / FD
eFinancials
FD OLIB
Libraries
CCM Facility
Timetabling
MS
Great Plains
PWA HR
The System Components
8. CURRICULUM
ENRENQS APPS
STUEXAM REGIS
ISR LINKS FEES
FD EBS
Cedar / FD
eFinancials
FD OLIB
Libraries
CCM Facility
Timetabling
MS
Great Plains
PWA HR
Information Flows
Student
details
Staff,
Courses
Events
Staff
Payments
9. CURRICULUM
ENRENQS APPS
STUEXAM REGIS
ISR LINKS FEES
FD EBS
FD OLIB
Libraries
CCM Facility
Timetabling
MS
Great Plains
PWA HR
The Web Components
OLIB
WebView
eManager
Web
Timetables
Cedar / FD
eFinancials
EBS
Agent
10. The Silver service
• Information done just the way I like it
– Completely by someone else
or
– 100% Home grown
11. The Drive Thru
• Globally available
• DIY world
• Consistent menu
12. The Intranet Menu
• Library catalogue search
• Timetables by Course, Location & Lecturer
• Staff management inc Sickness and
Absence recording
13. EBS Agent – What’s on the
menu
• Student & course centric info
• On line reporting
• eRegisters
27. How did we sell it?
• Enrolment time
• Desktop reporting
• Attendance monitoring
31M ay 2002
report: fdClssLst V1.0
Class list - with photos
ZC37341
GNVQ INTER LEIS & TOUR (LEISURE)
A01/02
1102639 Alderson, Leejay 1097890 Andrews, Justin 1094979 Browning, Benjamin
1086771 Burbridge, Stephen 1098679 Burns, Ryan 1096190 Collins, James
1098197 Francis, James 1096475 Goddard, Matthew 1102453 Heywood, Victoria
1073536 Hynes, Zara 1097223 Larmie, Ashley 1102842 Matthews, James
Page 1 of 2
28. Hot Peppers
• Empowers those who want it
• Questions those who don’t
• THE position is…..
• Ownership , manual admin
• Nearly all UDI dbs gone
29. Cold Turkeys….
• You don’t send me datasets anymore
• Not exactly 100% uptake
– Still not working in ways lecturers do
– Generation gap
– Lecturers & Learning
– Not all want DIY world
– We still have phones
– IT isn’t everything
30. To keep the customer
satisfied…..
• Get the core good first
• Processes are key
• Support, handhold & cajole
• Reliable I & T
• Drip, drip & drip
• Responsive listening
31. Icing on the cake
• Automate more tasks
– End of year reports
– 3 missed classes letters / emails / SMS
messages?
• eProgressions
• Funding Reports
• Configurable screen fields
32. Future Dishes
• VLE (FD Learning Environment 2.2)
• eStudent Records
• Lecturer centric
• Merging of VLE + Agent
• Web based MLE
Editor's Notes
10,000 students
Management in inverted commas as much broader than that – about using It to assist and transform way lecturing staff interact with and use info – maybe that’s a bit grand to talk about radically doing that just yet..
Using web components since 1999
Senior management will key in all this
This is the way everyone’s going to do things
Tribal depts doing UDI
Old chestnut - Central systems didn’t reflect reality – that’s because they were central, (limited access to information specialists e.g. ac reg, support offices) and two way info exchange wasn’t there to improve quality & usefulness
Own separate databases but developed in absence of centre meeting needs
Old green screen forms
Skills limited
Too critical a part of business
For integrated read interoperable or on a bad day linked….
Integrated really meant same supplier
Student Records, Curriculum, Exams, Enquiries, Applications
Financials separate but linked same supplier
Didn’t have the resources nor believe that was the best way to deliver even if we did – good commercial companies should be market driven delivering what the best and majority of users want and quickly responding to those demands
Web views open up access – just views at this stage
Best of breed approach but with strong leaning towards one particular supplier – did have some historical element but they were only ones really talking the whole strategic vision
What difference are the web components going to make….?
Either wanted nothing to do with information or if did…
…support staff collected and presented on their desk
Their reports just how they liked them, if they wanted this column, this formatting, this colour they should have it their stats just how they liked them (if not saying what they wanted lets change the definition) or…
They built & maintained their own system
Lecturer built own GNVQ Tracking System
v.good but then retired……
All a bit labour intensive and a bit difficult to compare and contrast…..
Not so much McD but McE
Benefit of the web – securely available from any desktop
You have to go and get it – big culture change for many lecturing staff – anything admin was something someone else did
Limited menu but at least consistent wherever you go
Analogies with bland, unappetising, happy meals but can’t say they aren’t pervasive
Double secure logon
Mention options for courses along the top
Context specific – brings up course reports when looking at courses, students when
Administrator can check on status of auto-issued registers
Happy Meals with effigies of Senior Management Team
How many on my course, will it run?
SMT member gathering up teaching staff in quiet times to go to training
Rogues Gallery
In 3 years, (eRegisters piloting for 1), what’s worked…..
The culture is changing…..
Questions because everythings open, no excuses for not knowing/having access
Many lecturing staff complaining too little too basic & they’re right
Reduces admin load for trad support & registry staff but also teaching staff
GET SOME ACTUAL QUOTES & USAGE STATS
And what hasn’t……
Not integral but add on – don’t work primarily at a PC or with a laptop, not the first thing they reach for.
Quite what ways some lecturers do work I’m not exactly sure but only Partially delivering on all their information and manipulating that info needs
GET SOME ACTUAL QUOTES & NON USAGE STATS!
CORE RIGHT – integrated / interoperable systems, single source of information
PROCESSES KEY – Don’t duplicate paper systems but automate familiarity and add something. Going to have eRegisters, don’t have paper backups
SUPPORT
eRegisters was 1st application (after email) most teaching staff expected to use daily – developers didn’t appreciate how simple and slick had to be.
Many staff disliked in classrooms (uncomfortable & impatient)
Linked to push on attendance monitoring
Instant feedback, continuous support bod critical for explaining use & info issues
Initially had lecturing staff saying they hated it….was it the technology, the usability or the fact they knew registers were being checked up on……and then saying after a while they could see the benefits…..
RELIABLE I&T – information more often at fault than the technology – but if lecturers could see the systems were matching reality that gave it credability & ownership.
DRIP, DRIP – sell those benefits!
I’m doing a staff development session in 2 weeks time – staff ‘forget’ what’s there and what it can provide.
Trad depts have to keep reminding staff don’t call us but look here in future
RESPONSIVE LISTENING
Early eRegisters had clunky confusing interface, not helpful, unreliable.
Good ideas coming back from lecturing staff
Big advantage because Agent & Le share their interface – far less steep learning curve
Whole of Student Records like Financials goes completely web based away from current client server configuration
Lecturer centric – groups their courses, timetables, tutorials, schemes of work
Make merged Agent/VLE sufficiently interoperable with all web versions of main systems (resources, timetabling, financials, HR) and you have a full web MLE….under some definitions