Param Bedi VP Library amp Information Technology Bucknell University Mark Yerger Director Enterprise Systems Bucknell University Wednesday October 19 2011 Bucknell University ID: 782625
Download The PPT/PDF document "Keeping Pace: Mobile Application Strate..." is the property of its rightful owner. Permission is granted to download and print the materials on this web site for personal, non-commercial use only, and to display it on your personal computer provided you do not modify the materials and that you retain all copyright notices contained in the materials. By downloading content from our website, you accept the terms of this agreement.
Slide1
Keeping Pace: Mobile Application Strategy and Implementation
Param
Bedi
, VP Library & Information Technology,
Bucknell University
Mark
Yerger
, Director, Enterprise Systems, Bucknell University
Wednesday
, October 19, 2011
Slide2Bucknell UniversityBucknell University, located in Lewisburg, PA, is a highly selective, private university founded in 1846.450-acre campus includes more than 100 facilities
Approximately 3500 students, 360 faculty and 840 staff members
2
Slide3Our Story:Mobile Objectives & Strategy
Objectives
Provide a
managed
approach to both common and customizable mobile services
Maintain a close partnership between Library & IT and Communications to develop the following approach in late Spring 2010.Strategy HallmarksSupportableRisk-Informed
Brand Enabled/Consistent
Comprehensive and Flexible
Slide4Our Story:
SUPPORTABLE
Controlled growth
Web = Stable, existing support skills
“Apps” = Evolving, few support skills
Reuse existing services/contentGovernance for 3rd-party portfolio additions ensures:
Formal
hand-off to L&IT support
teams
Vendor contracts if needed
No Approval = Not part of the portfolio
Slide5Our Story: RISK-INFORMED
Exposing
intranet
content requires higher privacy/security scrutiny
Devices are “easier” to lose
BYOD = Fully secure?Mobile access to student’s schedule & gradesMobile access to view available lab computers
Governance for 3
rd
-party portfolio additions ensures:
Alignment with campus data
security standardsConscious acknowledgement exposures
Slide6Our Story: Brand Enabled/Consistent
Must adhere to
Bucknell
public and internal brand standardsDesign
Wording and organization of content Color paletteData security and stewardship Governance of 3rd-part applications
Includes branding approvals by both L&IT and Communications
Offices.
Slide7Our Story:Comprehensive and Flexible
Mobile web development
allows
for:
Easy conversion of
existing intranet and public web services to a mobile interfaceIncorporation of vendor or student-developed mobile web applicationsStrategy accounts for device-specific “apps” approval processes
“Hurdles” to meet prior to L&IT support
More restrictive data access requirements
Oversight of how they are marketed and what “niche” they are meeting for campus
Slide8MIT Mobile FrameworkJune 2010: Use framework
developed by MIT and
supported
through the
iMobileU (http://imobileu.org) community
Leverage existing technical capabilitiesWeb developer – 1 FTE for 20 daysInfrastructure – 0.5 FTE for 20 daysExtend and expand the existing
service
portfolio
July 2010:
Beta Launched for testing
September 2010: Basic services available with new “features” every few weeks.
July
2011:
Upgrade to v.2.2.7
Slide9Building Blocks of the BU Strategy
Public Applications
Internal Applications
Existing Web Application Entry Points
Intranet-Enabled (
my.bucknell
)
Non-Mobile Applications
Internet-Enabled (bucknell.edu) Non-Mobile Applications
Bucknell Core Infrastructure
(Platforms, Network, and Security)
Mobile Supportability and Security Risk Assessment
L&IT
Mobile Web Apps
Approved Third-Party Web Apps
Bucknell Mobile Framework -
m.bucknell.edu
Public Apps – Open Access
Launch
Intranet Apps - Log-In
Launch
Approved
Third-Party
Device-
Specific
Apps
Web
Svcs
Mobile Web Apps
Approved Third-Party Web Apps
Approved
Third-Party
Device-
Specific
Apps
Slide10Bucknell Mobile Web
http://m.bucknell.edu
Slide11Campus Service Examples
Library Services, Dining Services and others
Slide12ERP (BANNER) IntegrationFinal Grades, Schedule & Message Center
Slide13Our EnvironmentCustomizationsAuthentication: Integration with CAS SSO System
Styling: Bucknell Branding, List-Style Home Screen
Oracle DB package (Banner access)
Our Environment
Linux Virtual Server2GB RAM16GB Disk (Currently using < 5GB)
Apache Webserver 2.x with PHP 5.2+Developer SkillsetPHP plus the usual: XML, RSS, HTML, CSS, Javascript
Slide14Keeping Pace: |
Regularly review campus feedback (students key)
Actively collaborate with Div. of
Communications
Listen to industry trends and remain informed about the quickly evolving vendor and consumer marketOngoing strategy evaluation
essentialAre we still meeting our objectives?Are our assumptions still accurate?What are the trends that are now influencing campus?
Slide15Keeping Pace: GartNer’s Multi Strategy Approach
Gartner Webinar: 24 Aug 2011. Nick Jones, VP Distinguished Analyst: The
Trends Driving Your Mobile Strategy Now Through 2015
Slide16Keeping Pace: A Multi Strategy Approach Applied to Bucknell
B2E – Employee Facing Mobility
(1 – 4 Years)
Connectivity
Using Google for mail
Pervasive wireless access
No LTE yet
Collaboration
Messaging, social networking, blogging - but not controlled
Day to day business change
Floods, Facebook and Twitter (oh, my!)
Researching new ways to aggregate campus messaging
Slide17Keeping Pace: A Multi Strategy Approach Applied to Bucknell
B2E – Employee Facing Mobility (1 – 4 Years)
Role-specific solutions
Currently no solutions of this type in place
Targeting admissions and alumni and looking at academics first
Consumerization
Refining our policies about device use and security
Starting to ask – Why not BYOD?
Slide18Keeping Pace: A Multi Strategy Approach Applied to Bucknell
B2C
–
Consumer
Facing Mobility (
12
–
18 Months)
Tactical solutions
Bucknell Mobile Web – MIT mobile framework – only key services!
Targeting admissions and alumni and looking at academics first
Innovation
iBucknell
faculty engagement for experimentation
B2C – Consumer Facing Mobility (
1
–
3 Years)
Refining our policies about device use and security
Starting to ask – Why not BYOD?
Slide19Keeping Pace: 2011 - SupportabilityCurrent App
Portfolio - B2C:
Remain In-House or Move to Outsource?
Evaluated market surveys from the prior year
Most offerings did not add competitive advantagePresence ERP integration was major Bucknell mobile web “pro”.
Current Direction:No strategy change.Minor framework upgrade Summer, 2011. (v2.2.7)New services for fall leveraged across both portal and the mobile web
.
Start thinking more about B2E (office and classroom)
19
Slide20Keeping Pace: 2011 - Supportability
Bucknell non-authenticated mobile Traffic: 13 Aug 2011 to 12 Sept 2011
Bucknell
Public Mobile
Footprint
–
~42K visits – 13 OS
Slide21Keeping Pace: 2011 – SupportabilityFuture App Portfolio Planning:
Eye on Evolution of HTML
5
Won’t
be able to wait.Likely won’t eliminate the need for all appsContinued marriage of portal functions/gadgets out to the mobile web.
Current Direction: Oct 2011 – New m. feature to facilitate course selection processNov 2011 – RFP responses arrive
21
Slide22Keeping Pace: 2011 – RISK INFORMEDB2E and B2C
Mobile
app content is being controlled, but are device management policies keeping up?
Are we maintaining our device and data management standards as mobile devices proliferate?
Are we applying the same university/personal “desktop” security services to university/personal mobile devices? If not, ensure policy reflects a conscious decision to do this, otherwise, develop a plan to extend services.
22
Slide23Keeping Pace: 2011 – Brand Enabled/Consistent
Naming and search terms: How to find apps
Sourcing locations: Alternatives to Apple App Store
Marketing: Keep apps tied to the main university .
edu site and social media outlets.
Current Direction:Developed app-based (Android, iOS) versions of mobile webDid not
release – Need “
app communication
and sourcing strategy”
Awaiting RFP evaluation to finalize approach.
23
Slide24Keeping Pace: 2011 – Comprehensive and Flexible
RFP for device specific apps for strong ROI applications
Knowledge Worker Job Automation (fundraising and BI),
– B2E
Collaboration (classroom sharing, alumni interaction) – B2ETactical
solutions to remain competitive – B2C:High-end Consumer ExperiencesAdmissions “experience” self-toursAlumni events
Fundraising “experiences” as part of campaigns
Athletics
Current Direction:
Oct 2011 – RFP responses arrive. Planned direction by early 2012.
24
Slide25Questions?
Slide26THANK YOU