2. Who We Are
ï§ Peter Murphy
â Project Manager, Major League Baseball, Commissioner's Office
â Project Management, Collaborative solutions
â peter.murphy@mlb.com
ï§ Smriti Kapuria
â Technology Manager, Prolifics User Experience Practice
â UX designer, Developer, Architect, Ceramicist
â skapuria@prolifics.com
2
3. Agenda
ï§ About MLB Commissionerâs office
ï§ Collaboration Needs of business groups
ï§ Adoption of IBM Connections as a social platform
ï§ MLBâs own solution : Customize and extend IBM Connections
ï§ Key Components of solution architecture
ï§ Interesting features and challenges
ï§ The road ahead..
3
4. About MLB Commissionerâs office
ï§ What is MLB ?
âą Baseball Office of the Commissioner(BOC)
âą Major League Baseball Advanced Media (MLBAM)
âą MLB Network
ï§ Business of Baseball - About the Commissioner's office
â Game Regulations
â Player Contracts
â Corporate Sponsorships
ï§ Role of MLB IT group at the Commissionerâs office
â Diverse Group
â Supports BOC and clubs
â Wide Spectrum of services â security, collaboration, application development
4
6. Business Groups
And the way they conduct their business
ï§ Introduction to a few different business groups
â Department Based â Finance, Ticketing, IT, Legal
âą Social Collaboration
â Event Based â Industry Meetings, World Series
âą Content sharing
â Baseball Function Based â Official Scorers, Umpires
âą Social Collaboration, Content sharing
â Program Based â RBI, Urban Youth Academy
âą Process Management
6
7. Collaboration Needs of Business Groups
Basic Ideas of structure and information sharing
ï§ Business groups are structured for information sharing and collaboration
â with in each group as a community
â with external entities
âą Clubs
âą Vendors
âą Sponsors, etc.
ï§ Different types of social needs
â Facilitate collaboration between clubs
â Provide centralized information to conduct business
â Periodic Notification of content and information
â Expose dynamic and historic ticketing data from several systems
7
9. Social Collaboration Eco-system
ï§ The solution is implemented as multiple restricted communities
ï§ Each with its own unique user group
ï§ Users interface with Connection features within their community
â Wikis
â Files
â Blogs
â Activities, etc.
ï§ Each community has a set of owners that administer their community
ï§ Connections administrators
â Moderate content
â Use Metrics for reporting
â Create communities
9
10. Communities, Users and Functions
and it all comes together!
ï§ Each business group uses their Community as a collaboration platform
ï§ Community is the hub for information and resources to run their business effectively
ï§ Functions such as blogs, calendar and forums facilitate communication
ï§ Community wikis, blogs, files provides centralized access for business artifacts
ï§ Community members set-up preferences to receive emailed notifications of updates
ï§ Sub Communities are created for sub groups of users for targeting content and
communication
â One example is executives of a business group are members of a sub-community
â In some cases, regional users/groups also have their own sub-communities
10
14. MLBâs own solution
Customize and extend IBM Connections
ï§ How we got to creating custom widgets on IBM Connections?
ï§ Custom Widgets, Custom community themes..
ï§ Several communities created custom community widgets in addition to out-of-the-box
ï§ Some examples are Polls, File Viewer, Ticketing widgets
ï§ Communities expose dynamic aggregated data from different systems through such widgets
ï§ An interesting scenario of Workflow Management with IBM Connections
14
15. MLBâs own solution
Job Request and Workflow Management with IBM Connections
ï§ This solutions utilizes Community Activities in IBM Connections to track job requests
ï§ New requests are created with a third party tool
ï§ Approved requests are added as an activity in IBM Connections using Connections API
ï§ Community Owners can quickly view and assign incoming job requests to members
ï§ 3 custom widgets are created to set-up the Workflow Management dashboard
â view new job requests
â view schedules of members
â view upcoming due dates of tasks
ï§ All of these widgets use Community Activities Connections API to maintain a cohesive
solution
ï§ A mobile view for each of this functions is also provided
15
18. Solution Architecture
ï§ Current implementation of IBM Connections uses a medium topology
ï§ The environment is configured for high availability
ï§ User management scenarios
â A TDI script is used for onboarding users in Connections via LDAP
â The user is synchronized with the LDAP and Portal implementations
ï§ Cognos is configured to run with IBM Connections to provide metrics and reporting
18
19. Interesting Features and Challenges
ï§ Notifications
â a fine balance between voluntary socialization and business needs of information
sharing
ï§ Are Community members following the right content?
â For notifications and preferences!
ï§ Dynamic user base
â Clubs and userâs name change frequently that needs to be maintained regularly
ï§ Challenges with content moderation
ï§ Files and tagging as information sharing is an important need
19
20. Business Benefits
ï§ Better communication
â Between the central office and the clubs
â Between clubs themselves
â Between various support staff such as official scorers
ï§ Better notifications
â Community members are better informed about new content and changes to existing
content. No longer need to hunt and peck for latest content.
20
21. The road ahead..
ï§ Newly deployed Connections 4.5 environment
ï§ Connections Content Manager evolution
ï§ Enterprise document manager consideration
ï§ Forms features(survey, polls etc.) through Feature pack
ï§ Happy Marriage between Connections and Portal
21
22. ï§ Access Connect Online to complete your session surveys using any:
â Web or mobile browser
â Connect Online kiosk onsite
22