Enterprise Technology Architecture: Operations platform plus Transformation platform

1
Enterprise Technology ArchitectureOperations
platformplusTransformation platform

• Peter Keen
• 09/04

2
Key principles

• Shift from concept of the enterprise
  architecture a single blueprint for integration
  of internal systems to a plan more analogous to
  a city zoning and ordinance plan Operations
  platform as the platform for efficient
  large-scale applications and enterprise
  information coordination linked to and from a
  Transformation platform designed for rapid,
  flexible innovations in services and processes.
• The strategy in combining the advantages of the
  OA and TA is to set a clear boundary between the
  two types of system, exploiting the new
  generation of proven tools to link them Web
  services plus interfacing and integration
  technology

3
Platform strategy
Operations Platform
Transformation Platform
Access front-end
Browsers
4
Transformation Platform strategy
Operations Platform
Architecture boundary wall
Messaging across the wall
Transformation Platform
Provisioning Boundary
Services access front-end
5
Operations base legacy systems and (generally)
systems disintegration
Too complex to even represent Legacy systems that
are just holding together Middleware muddle and
growth Multiple standards Dysfunctional
contracting rules And youre going to
Web-enable this????
6
Operations Platform strategy
Operations Platform
Policies with teeth NO changes/additions/Web-enabl
ing within the Operations platform Link via new
generation interface tools across the boundary
(XML, SOAP) Build the Transformation Platform
this side of the Boundary Wall
Architecture boundary wall
7
Transformation Platform strategy
Modular services based on 90-180 day venture
rule Self-integrating via Foundational Web
Services (HTTP, XML, SOAP) and sharp interfacing
tools/standards (Java and offspring, C,
etc.) Build large applications out of small
self-standing modular components Brand at the
browser
Operations Platform
Transformation Platform
Provisioning Boundary
Services access front-end
8
Transformation platform
Operations platform
Modular services 90-180 days Focused
deliverable Beachheads -- beyond
pilots Self-integrate viaWeb services Phase risks
M1, M2, M3.Service A Priority target BPM
Secure, high bandwidth VPN
Web Services Foundational Standards and Tools
Services access front-end
9
Services access front-end
Transformation Platform
Provisioning Boundary
Put all security at this front-end Enterprise
directory management Public Internet, dial-up
access only as far as the provisioning
boundary Establish browser as brand
10
Does this approach work?

• Yes
• Rapidly emerging as the only sensible blueprint
  for balancing innovation and operations, new and
  old
• Many organizations implementing it carefully
• Conservation International, Budget Rent a Car.
  Wachovia financial services
• Government agencies in Australia, HK, Denmark,
  U.S. Navy synchronizing 22 major platforms
• Common themes
• Be selective about Web Services -- Not ready for
  prime time
• Use Foundational stable, proven, robustHTTP,
  XML, SOAP
• Architect for Transitional --coming soon out
  of the lab/pilot stage and clearly on the way to
  Foundational UDDI, WDSL, etc.
• Watch Emergent -- proposed
• Major concern is security keep the network
  closed except to key partners

11
A bonus

• By fencing off the back-end Operations Platform,
  agencies can handle legacy muddles as an economic
  agenda
• Gain-sharing deals with vendors, hosting firms
• Systems divestment options
• Hosting, Outsourcing and Co-sourcing
• Annuity contracting for variable cost services
• Get away from the massive systems application
  burden and concomitant contracting tradition
• Modular services built in independent layer of
  the Enterprise Architecture instead of
  large-scale Web-enabling projects
• Hedge risk if module 1,2,3 and 4 work but 5
  fails, still have 1-4, and can self-integrate
  them into a generic service
• 90-180 day ventures mean results flow instead of
  the 5-year wait, often a 5-year disappointment or
  write-off