Integration Competence Center Positioning, Services

1
Integration Competence CenterPositioning,
Services Organisation

• Patrick Toenz
• t2b AG, Basel, www.t2b.ch CEO

2
Agenda

• Position of EAI
• Why a Competence Center ?
• ICCs Role, Integration Services, Interaction
  with IT Business Projects
• ICC internal Roles Responsibilities
• Resources Skills, Sourcing, Estimates
• ICC Set-up Timeframes

3
t2b AG

• Specialized on IT architecture and EAI
• Unique EAI Methodology
• Full EAI life-cycle support
• Decide
• Evaluate
• Design
• Implement

• Vendor independent consulting
• EAI expert pool with partner companies
• 5 EAI Methodology
• 12 SeeBeyond
• 18 TIBCO
• 10 MQ Series
• 8 WebMethods
• 3 MQ Integrator

4
EAI Positioning

• What does the company want to achieve with EAI ?

5
EAI Positioning

• Operational
• Create interfaces/backend-access faster
• Tactical
• Solve interface spagetti-network
• Single channel for external partners
• Strategic
• Manage data (knowledge) accross applications
• Finally do business process engineering
• Create the super-ERP

6
Assumption Strategic EAI

• Assumption 1 a company doing a strategic
  investment in EAI is shooting for a long term
  business advantage and plans to implement the
  total integration vision.
• Assumption 2 no company can implement this
  vision in one go.
• This requires a long term transformation process
  of IS architecture and IS development
  methodology.

7
Position of EAI actual planned
value
TBI Driving change to an event driven company
strategic
Managed service for integration and data
interchange
tactical
Technical solution for a technical problem
Single project approach
operational
complexity
8
Cultural Embedding ?

• Industry company
• Traditionalist vs. Process Leader ?
• Is IT a big part of the companys product ?
• Customer driven organization ?
• Process driven organization ?
• Internal Organization
• Functional structure ?
• Process structure ?
• Service culture ?
• The (technical) ICC cannot drive an
  organizations cultural change on its own.

9
Why a Competence Center ?

• Does EAI and integration require a separate
  specialized unit ?

10
EAI Tools Complexity Example 10 of SeeBeyond
functionality
11
Integration Know-how

• Everyone in IT has some integration experience
• Specialisation results in
• More detailed integration know how of a specific
  system (SAP, ORACLE, etc.)
• Cross system know-how (technology and data)
• Advanced/new technologies XML-Schema and
  transformations
• Use of best-practice integration approaches

12
Why a Competence Center?

• New, complex technology concept
• Concentrate high-skilled IT resources
• Build up integration tool know-how
• Run pilot projects
• Build up infrastructure
• Document best practices
• gt mid-term spread well-defined best practices to
  multiple ICC
• gt long-term drive integration skills to data
  process management level(s)

13
ICC Checkpoint 1

• EAI introduction requires a competence center
• Company needs to define position of EAI and the
  ICC
• Short term
• Vision
• Rough evolvement plan
• Supporting environment if ICC is a part of a
  corporate change process

14
Role of the ICC ?

• External View what service does the ICC provide
  to the organization ?

15
Integration Service Definition Example tactical
EAI

• Provide general purpose integration services for
  internal (A2A) and external (B2B) application
  integration, consisting of
• Definition and design of the integration backbone
• Consulting and engineering support to business
  app projects to enable them to hook in to the
  integration backbone (development)
• Secure and failsafe transport of data (backbone
  operations)
• Single and secure point for external data
  exchange (B2Bi)

16
Integration Services Interoperation Diagram
17
Integration Service Sample Service Level
Agreement

• SLAs to business app teams
• Integrating a new application
• response 2 days
• Analysis estimate 5-10 days
• Implementation 5-30 days depending on complexity
• Adding events from connected application
• Analysis estimate 2 days
• Implementation 2-5 days depending on complexity
• Adding a new site (geographically)
• Analysis estimate 5 days
• Implementation 5-60 days depending on
  requirement of local installations
• Operations 7x24h, 99 availabiltiy/month, Delay
  lt 1min for 99, lt10min for 100(Project
  specific SLAs for specific requirements)

18
Integration DevelopmentInteraction Diagram
19
ICC cost charging

• Make the use of the new technology financially
  attractive, e.g.
• General charges
• HWSW
• Basic operations service management
• Data architecture
• Charged to projects
• Integrations design development
• Support maintenance

20
ICC Checkpoint 2

• ICC belongs to
• application development
• IS architecture
• Data / knowledge management (strategic EAI)
• ICC should have
• Integration design authority (tactical EAI)
• Data standards authority (strategic EAI)
• Process design authority (strategic EAI)
• ICC services should be financially attractive in
  order to support spread of new integration
  method

21
ICC internal organization

• Roles and Responsibilities
• Tools

22
Integration Services ICC Roles
Data Process Mgmt
Integration Service
IntegrationConsulting
Architecture
Service Management
Consulting,Engineering Development
Business Application Owners
SLA
QA Mgr
EAI Oper. Support
Support Mgr
SLA
General Operations Support Organization
23
Integration Service Roles I
24
Integration Service Roles II
25
Integration Services ICC Roles Workload
Estimate year 2
Data Process Mgmt
Integration Service
5-20
Architecture
Service Management
5
Consulting,Engineering Development
Business Application Owners
SLA
60
5
QA Mgr
EAI Oper. Support
Support Mgr
5
10
SLA
5
General Operations Support Organization
26
ICC Implementation
27
Integration Service Is it possible to split
development operations ?

• Single point of contact
• Business units and application projects want to
  talk to 1 service responsible
• Technology too new/complex to draw exact lines of
  responsibility
• ICC internal split required
• Different business model for project teams and
  ongoing operations
• QA requires a separate organization

28
Integration Serviceproduct management
Customer Input
29
Integration service required Tools

• Classic Service Tools
• Ticketing system
• Service requests
• System generated problem handling requests
• SLA tracking
• EAI intranet site
• Service documentation
• Portfolio/dictionary search display
• System status interface to helpdesk/ ticketing
  system
• Specific EAI Tools
• systems portfolio management
• Interface meta-data dictionary

30
ICC rough timeframe

• explore evaluate setup use

6 months 6 months 6 months 6 months
31
ICC Checkpoint 3

• ICC requires
• Highly skilled resources
• Experienced Project Managers Developers
• Experienced Service Manager
• Senior Architect
• Tactical EAI Top management support
• Strategic EAI Top management lead
• Long term commitment

32
Thank you!