Basf roadmap-2-global-st852
Upcoming SlideShare
Loading in...5
×
 

Basf roadmap-2-global-st852

on

  • 1,347 views

BASF: Our roadmap to a global Sametime 8.5.2 deployment....

BASF: Our roadmap to a global Sametime 8.5.2 deployment.
BASF is the world's leading chemical company, with about 105,000 employees and close to 385 production sites worldwide.
Until today BASF works with a heterogenous Sametime environment with different Sametime versions brought together in one community. The goal of this roadmap is to come to a homogenous Instant messaging and meeting environment with Sametime 8.5.2 as basis.
This presentation will focus on why on how BASF an IBM together designed a roadmap to come from this heterogenous environment to a homogenous global environment. It will be shown how we came to the architectural design and an implementation plan by first analysing the functional and non functional requirements.

Statistics

Views

Total Views
1,347
Views on SlideShare
1,347
Embed Views
0

Actions

Likes
0
Downloads
22
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    Basf roadmap-2-global-st852 Basf roadmap-2-global-st852 Presentation Transcript

    •  
    • Our Roadmap to a Global Sametime 8.5.X Deployment
    • Legal Disclaimer
      • The information contained in this publication is provided for informational purposes only. While efforts were made to verify the completeness and accuracy of the information contained in this publication, it is provided AS IS without warranty of any kind, express or implied. BASF shall not be responsible for any damages arising out of the use of, or otherwise related to, this publication or any other materials. Nothing contained in this publication is intended to, nor shall have the effect of, creating any warranties or representations from BASF or its suppliers or licensors.
      • This information is a summary of a study made by IBM in cooperation with BASF and BASF IT Services Holding GmbH.
      • IBM, the IBM logo, Lotus, Lotus Notes, Notes, Domino, Sametime and WebSphere are trademarks of International Business Machines Corporation in the United States, other countries, or both.
    • BASF – The Chemical Company The world’s leading chemical company
      • Chemistry is about every aspect of life.
      • We are connected to deliver intelligent and sustainable solutions.
      • Sales 2010: more than €63.800 mill.
      • Employees (Dec. 31, 2010): around 109.000
      • About 1.300 new patents filed (2009)
      • 6 Verbund sites and about 380 production sites
    • BASF IT Services Group
      • Wholly owned subsidiary of BASF
      • Largest IT service provider of the BASF Group
      • Among the leading IT service providers for the process industry in Europe
      • Sales 2010: Around 435 million Euros
      • Around 2.300 employees (Dec. 31, 2010)
      • Headquarters in Ludwigshafen/Rhein (Germany)
      • Locations in 10 countries across Europe
      • SAP Service Partner and SAP Special Expertise Partner
      • Certified under ISO 9001:2000 and ISO 27001:2005
      • IT Service Management according to ITIL
    • Content
      • Project Scope
      • Current Situation
      • Review
      • Functional Requirements
      • Non-functional Requirements
      • Architectural Design
      • Deployment
      • Q&A
    • Project scope Current Situation Review Preparation for Additional Demands Functional and Non-functional Requirements Architectural Overview Component Model Operational Model Architectural Decisions Deployment Sametime 8.5.x Environment
    • Keeping track Current Situation
    • History
      • 1993 Lotus Domino start in BASF
      • 2001 First SAMETIME server
      • 2004 Global standard: “IBM Lotus IM and Web Conferencing”
      • 2007 Second SAMETIME server
      • Sametime for all in EUROPE domain (60,000 users)
      • Upgrade Sametime server to R7.5.1 (2 servers)
      • Telephony integration - 30 lines (partnership IBM-ilink)
      • 2008 External meeting service
      • 2009 Telephony integration - enhancement project (120 lines)
      • 2010 Review
    • Current Situation Origin and actual situation
      • 7 Sametime servers in different versions
      • First installed as islands, later brought together in one community
      • All use Domino authentication
      • No clustering
      • 4 out of the 7 Sametime servers installed in the different mail domains (no separate Sametime domain)
    • Current Situation Some figures
      • Users
        • Registered: 106.000
        • Active IM users: 51.000
      • Meetings
        • Meetings/month 5.500
        • Meeting users/month 19.300
    • Keeping Track Current Situation Review
      • End 2009 – Begin 2010
      • Improvement Recommendations from Review:
        • High available, world wide consolidated Sametime 8.5.x infrastructure
          • Based on Websphere and Domino 8.5.x
          • Use of Sametime System Console
        • LDAP authentication (SSO – R8.5.x)
        • Notes 8.5.x with embedded Sametime 8.5.x
      Review
    • Keeping Track Current Situation Review Functional and Non-Functional Requirements Preparation for Additional Demands
    • Functional Requirements Description
        • Use Cases Overview
          • Presence and Awareness
          • Rich chat
          • Telephony Integration in Rich Chat
          • Video Integration in Rich Chat
          • Online Meetings
          • Telephony Integration in Online Meetings
          • Video Conference Integration in Online Meetings
          • Calendar Integration
      • Intended behaviour of the BASF global Sametime 8.5.x architecture.
        • Agreement: stakeholders - project team
        • Based on use cases
        • Purpose
          • Common understanding of system behavior
          • Design elements that support the required behavior
          • Identify test cases
          • Write user documentation.
          • Elements of a used case: Summary, Actors, Scenario
    • Functional Requirements Example of a use case
      • Presence and Awareness
        • Summary: Sametime users are able to select their presence status that will be published to the Sametime community, and to see the published presence status of other users in the Sametime community.
        • Actors:
          • Internal user, rich client
          • Internal user, browser client
          • Mobile user, Blackberry
          • Mobile user, iPhone
          • Mobile user, Android phone
          • External user
          • Sametime System
        • Scenario: The user starts connects to the Sametime system with a rich client or a web browser. He logs on to the Sametime system and sees the presence status of all his contacts in the contact list of the client. The user can select the presence status that is visible to all other users, and can exclude users from seeing his presence status. For the Notes embedded client, the presence status of Sametime users is also available in the views and documents of all Sametime enabled Notes applications (mail file, Domino Directory, etc.). The presence status of Sametime users shall be available in connect.basf (Lotus Connections) via the business card that is defined in Profiles. With upcoming versions of Lotus Connections additional features (e.g. LiveNames) are planned to be implemented. The presence status of Sametime users shall be available in the BASF Quickr places through the web interface. As a future requirement, the presence status of Sametime users shall be available in web applications (e.g.Portal, intranet pages, etc.).
    • Non-functional Requirements Description
      • The non-functional requirements:
        • Service Level Requirements
        • Non Runtime Requirements
        • System Constraints
        • May apply to:
          • the system as a whole
          • parts of the system
          • particular use cases.
      • Purpose:
        • specify required properties
        • define constraints
        • enable early system sizing and estimates of cost.
        • assess the viability
        • give a basis for designing the operational models.
        • provide input to the component design
    • Non-functional Requirements Results
        • Service Level Requirements
          • Capacity and Performance
          • Availability
            • IM: 99,9%
            • Meeting, telephony and video integration: 99%
            • DRP: setup in 2 datacenters
          • Security
            • Analysed and described
      Capacity
      • +/- 70.000 concurrent IM users
      • +/- 2.000 concurrent internal meetings
      • +/- 100 concurrent external meetings
      • Reference performance measurements have been done
      Availability
      • IM: 99,9%
      • Meeting, telephony and video integration: 99%
      • DR: setup in 2 datacenters
      Security
      • Analysed and described
      System Management
      • User priviliges (ST policies)
      • Software distribution
      • Monitoring (availability and capacity)
    • Non-functional Requirements Results
        • Non Runtime Requirements
          • Portability
          • Maintainability
          • Education
          • Test System
        • System Constraints
          • Business Constraints
          • Technical Standards
          • Technical Constraints
    • Keeping Track Current Situation Review Functional and Non-Functional Requirements Architectural Overview Preparation for Additional Demands
    • Architectural Design Architectural Overview
      • Overview of the main conceptual elements and relationships (subsystems, connections, users and external systems)
      • Represents the governing ideas and candidate building blocks of the architecture.
    • Keeping Track Current Situation Review Functional and Non-Functional Requirements Architectural Overview Component Model Preparation for Additional Demands
    • Architectural Design Component model
      • The structure of a system
        • Software components
          • Responsibilities
          • Interfaces
          • Relationships
          • the way they collaborate
      • Example (Community Services) in next slide
        • Component Relationship Diagram (see next slide)
        • Required Service Levels (Performance and capacity, availability, security, system management)
        • Design Rationale (Sizing)
        • Implementation Approach (OS, V/P)
        • Description - Responsibilities
    • Architectural Design Component model
    • Architectural Design Component model
    • Architectural Design Component model
      • “Buy in” services
        • DB2 database services
        • LDAP directory services
        • Websphere services
        • Load balance services
        • Telephony services
        • Video conferencing services
      • Test system
    • Keeping Track Current Situation Review Functional and Non-Functional Requirements Architectural Overview Component Model Operational Model Preparation for Additional Demands
    • Architectural Design Operational model
      • Describes:
        • The operational distribution of components onto nodes
        • The placement of nodes and users across locations
        • The connections between nodes (network, DNS, ports)
        • The system requirements (server sizing)
        • All this to achieve the system’s functional and non functional requirements within the constraints of technology, skills and budget.
    • Architectural Design Operational model
      • System diagrams:
        • Production system
        • Test system
      • Locations:
        • Datacenter: 2 sites (DR)
        • BASF Office: all BASF sites, home offices, mobile users
        • Non-BASF Office: Customers, business partners and BASF users without VPN access
    • Architectural Design Operational model: system diagram Prod Test 1
        • System console (cold standby might be added
      1 4
        • Community servers
      2 6
        • Standalone multiplexers
      2 4
        • Sametime Proxy servers
      2 6
        • Meeting servers
      2 2
        • SIP proxy servers (WAS proxy on same machine)
      2 2
        • Conference manager servers (WAS proxy on same machine)
      2 2
        • Packet switchers
      2
    • Keeping Track Current Situation Review Functional and Non-Functional Requirements Architectural Overview Component Model Operational Model Architectural Decisions Preparation for Additional Demands
    • Architectural Design Architectural decisions
      • Decisions about:
        • Structure of the system
        • The provision and allocation of function
        • The contextual fitness of the system
        • Adherence to standards.
      • Decisions:
        • Community services: Centralized
        • Community services will be setup as one cluster
        • LDAP: edirectory will be used
        • Meeting services: Centralized
        • DB2: Pure scale cluster
    • Result Current Situation Review Functional and Non-Functional Requirements Architectural Overview Component Model Operational Model Architectural Decisions Deployment Sametime 8.5.x environment Preparation for Additional Demands
    • Deployment
      • Strategy:
        • Setup new environment in parallel to the existing Sametime environment.
        • Test the new environment
        • On cutt-off date: switch user community from old to new system
      • Milestones and Schedule
        • T0 + 2 weeks Systems ready for implementation
        • T0 + 8 weeks Test System implementation completed
        • T0 + 13 weeks Production System implementation completed
        • T0 + 18 weeks Tests completed
        • T0 + 20 weeks Trainings completed
        • T0 + 20 weeks Cutoff
        • User Migration
    • Q&A
    • Contact Chris Van der Jonckheyd Senior Process and Application Consultant BASF IT Services N.V. Scheldelaan 600 Haven 725 B-2040 Antwerpen Phone +32 3 561 3042 Mobile +32 477 42 99 41 [email_address] www.information-services.basf.com