does microsoft understand business integration
Download
Skip this Video
Download Presentation
Does Microsoft Understand Business Integration?

Loading in 2 Seconds...

play fullscreen
1 / 18

does microsoft understand business integration - PowerPoint PPT Presentation


  • 190 Views
  • Uploaded on

Does Microsoft Understand Business Integration?. Simon Thurman Architect [email protected] http://blogs.msdn.com/businessvalue. Objective. Try and answer the question  Explain thinking and approaches Any feedback email or comment on blog. Agenda. Is there a problem? Definitions

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

PowerPoint Slideshow about 'does microsoft understand business integration' - daniel_millan


An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
does microsoft understand business integration

Does Microsoft Understand Business Integration?

Simon Thurman

Architect

[email protected]

http://blogs.msdn.com/businessvalue

objective
Objective
  • Try and answer the question 
  • Explain thinking and approaches
  • Any feedback email or comment on blog
agenda
Agenda
  • Is there a problem?
  • Definitions
  • Approaches
    • Integration Model (technology)
    • Composite Applications (architecture)
    • OBA (productivity)
  • Limitations
  • Benefits
problem one of
Problem (one of...)
  • Unlock value of existing assets
    • Gartner ‘The Knowledge Worker Investment Paradox’
    • 50% - 75% of information directly from people
    • >80% of information not accessible to enterprise as a whole
    • Individual owns the key resource, what happens when they leave?
results gap
‘Results Gap’
  • Business Users live in 2 worlds
    • Productivity Applications
      • Adhoc, unstructured, individual/group processes
      • E.g. Excel, Word, Outlook, ...
    • Business Applications
      • Structured, rigid, stovepipe
      • E.g. CRM, ERP, ...
  • Space between what existing productivity tools offer and what really happens
what s required
What’s Required
  • Process
    • Integrate multiple Business Applications
    • Align Business Processes with daily work
  • Information
    • Timely access to the right information
    • One version of the truth
  • Applications
    • Use existing, familiar desktop apps
definitions
Definitions
  • Interoperability
    • Interoperability is connecting people, data and diverse systems. The term can be defined in a technical way or in a broad way, taking into account social, political and organizational factors.
  • Integration
    • Integration is a process of combining or accumulating.

Interoperability makes Integration easier

interoperability and integration model
Interoperability and Integration Model

Architectural Model

Technology

View

Programming Model

Message Format

Data Format

Transport Protocol

integration capability model
Integration Capability Model

Business View

Business Process

Line Of Business

Information Repository

capability and technology alignment
Capability and Technology Alignment

Business Process

Architectural Model

Programming Model

Line Of Business

Message Format

Data Format

Information Repository

Transport Protocol

software services
Software + Services
  • SOA
    • Architectural Approach
  • SaaS
    • Simply a delivery mechanism
  • S+S
    • Device software
    • Capability exposed as a service
      • On premise
      • Cloud
composite applications
Composite Applications
  • Assembled artefacts to fulfil business capability
  • Deployed independently and granular
    • Components
    • Containers

Presentation Layer

Productivity Layer

Application Layer

Data Layer

limitations
Limitations
  • Not all Capabilities are modular
    • Many are contained within a monolithic app
    • Not completely at an SOA
  • Transference of Control and Ownership
  • Modelled process do not implement all activities, e.g. Human intervention
  • Difference between managing documents and business processes
    • Transactional v Collaborative
    • Structured v Unstructured
    • Formal v Adhoc
    • Rigid v Dynamic
purpose benefit
Purpose/Benefit
  • Reuse
    • Reduce cost
    • Ensure consistency, e.g. Single view (and version) of the truth
    • Leverage already deployed software, e.g. Office
  • OBA bridges structures and unstructured
  • Office platform deployed
    • Container for components
business value
Business Value
  • Broaden availability of Information and Capability
    • Improve view of data which results in a greater level of understanding, e.g. “Managing the amber”
  • Exception based processing
    • Naturally supports human intervention
  • Shorten business process cycles
  • Regulatory compliance
  • Alignment of systems with the business
    • Systems become an enabler to change
summary
Summary
  • Reference architectures to build OBA
    • http://www.microsoft.com/architecture/
    • http://msdn.microsoft.com/oba/
  • Feedback:
ad