PwC UK: Enterprise Services Architecture

Download Report

Transcript PwC UK: Enterprise Services Architecture

Enterprise Services Integrated
Architecture
[ESIA]
Viv Noot
PwC
ESIA - Services Architecture
A quick introduction….
• Viv Noot – [email protected]
• Senior Manager responsible for Architectures
•
Background at PW/PwC
• Lotus Notes: implementation UK, EMEA
• Merger: PW Notes lead
• EMEA Standards + Projects: Notes
• Global Standards + Projects: Standards; Architecture
• UK: E-Business Technology Integration; Architectures
ESIA – Services Architecture
Slide: 2
Agenda for this session
• Why architecture?
• ESIA in words
• ESIA scenarios
• ESIA context
• ESIA model
• ESIA status
• ESIA conformity and benefits
ESIA – Services Architecture
Slide: 3
An architecture provides the framework that ensures
individual activities achieve a coherent result.
Statistics:
•Number of rooms: 160
•Cost: $5,500,000
•Date of Construction: 1884 - September 5, 1922
•Number of stories: prior to 1906 Earthquake – 7
•Number of acres: originally 161.919
•Number of basements: 2
•Heating: Steam, forced air, fireplaces
•Number of windows:approx. 10,000
•Number of doors: doorways 467 approx., 950 doors
•Number of fireplaces: 47
•Number of chimneys: presently 17
•Number of bedrooms: approx. 40
•Number of kitchens: 5 or 6
•Number of staircases: 40, total of stair steps - 367
•Number of skylights: approx. 52
More Statistics:
•65 doors lead to blank walls
•13 staircases lead nowhere
•24 skylights in floors
Division of Labour
Builders: 147
Architects: 0
Blueprints available: None. Mrs. Winchester
never had a master set of blueprints, but did
sketch out individual rooms on paper and even
tablecloths!
This staircase leads to a ceiling.
ESIA – Services Architecture
Source: www.winchestermysteryhouse.com
Slide: 4
Adopting a service oriented approach for the delivery of
business solutions is consistent with the firm’s vision.
• ESIA models the technology constructs behind e-tising the firm
• ESIA describes delivering services, not applications, to the firm’s user
communities.
• ESIA promotes separating business process from application functionality
– facilitating process optimisation.
• ESIA proposes the abstraction of generic functions to shared enabling
services, driving componentisation, consistency and re-use.
• ESIA helps increase flexibility, speed and agility while reducing costs.
• ESIA is one part of an Enterprise Architecture that includes infrastructure
architecture and business architecture.
ESIA – Services Architecture
Slide: 5
ESIA provides a context for the IT activities underway within
the firm.
• ESIA is an architectural model – it is not a programme of work.
• It aims to provide a framework that allows IT initiatives to be
viewed in the context of what the firm wants technology to
deliver.
• ESIA offers a holistic view of technology within the firm and
provides a mechanism to test how well individual initiatives are
aligned with the strategic direction.
ESIA – Services Architecture
Slide: 6
Scenario: establishing a new client using an applications
model might involve seven activities.
Register prospect in Sales Tracking
Enter and “test” prospect in Acceptance and
Continuance system
Enter and check client in Independence
system for conflicts of interest and required
internal disposals
Enter new client in to Finance systems to
obtain billing number and client code.
Create new client in Engagement System
Create new client in Customer System
Create new client in Staffing System
ESIA – Services Architecture
Slide: 7
Scenario: establishing a client using a services model might
require two user activities.
Register a prospect in the “Prospective Client
Service”
Convert a prospect to a new client using the
“Prospect Conversion Service”.
ESIA – Services Architecture
Slide: 8
ESIA is one face of a four-sided pyramid that includes the
Business, Standards and Principles.
=
User
Communities
Interaction
Services
Process
Interface
Enablement
Functional
Infrastructure
Architecture
Data
Support
Services
Information
Architecture
Enterprise Services Integrated
Architecture
ESIA – Services Architecture
Slide: 9
ESIA.Services is one component in the portfolio – supported
by Principles, Business Requirements + Standards
Delivers tailored
services to users, rather
than silo applications.
Delivers the business
requirements and
organisation that must
be addressed by the
architectures and
standards.
Enterprise
Services
ESIA.Services
Architecture
Principles
ESIA.Infrastructure
Delivers the hardware,
networks, software and
monitoring systems –
the “pipes and sewers”
ESIA – Services Architecture
ESIA.Information
Business
Drivers.
Delivers the framework
for organising data,
content, and
information for
accessibility and value.
Slide: 10
ESIA.Services delivers tailored services to users – mapped to
one or more functional systems and delivered using shared
enabling components.
User
Communities
Interaction Services
Tailored Services
Business Process Services
Service / Function Interface
Functional Services
Enablement Services
Support Services
Data Services
ESIA.Infrastructure
ESIA – Services Architecture
ESIA.Information
Slide: 11
ESIA is a highly componentised model that allows functions
from applications to be aggregated and presented as discrete
services to the users.
Alumni
Suppliers
AlliancesUser
Staff
Communities
Clients
Prospects
Interaction Services
Other
Portal
PMI
Workflow
EDM
ClientServices
T&E
Billing New
Tailored
Travel
Business
Business
Business ProcessRules
Services
Process
Hosting
Service / Function
Interface
BAPI
XML
Other
User
Support
Process
Support
Middleware
ED
Search
CRM Functional
Orbit
Oasis Services
GFS
Enablement Services
Systems
Support
I’structure
Support
Support Services
Data Data Services
Data
ESIA – Services Architecture
Slide: 12
Practicalities: ESIA and the Portal: the tabs reflect business
processes.
Set up a prospective client
This service helps you set up a prospective client.
You will be asked to enter the basic details of the prospect, and
you will e issued with a prospect reference number that can be
used to transfer the details when a sale is realised.
Set up a Prospective client
Functional + Data
Services
Service/Function I/face
Enablement Services
1. Register prospect .
SAM interface
EDM / Middleware
Data update + response
2. Prospect suitability.
Acceptance interface
EDM / Middleware
Data update + response
3. Independence check
Independence interface
EDM / Middleware
Data update + response
4. Report to user
User service interface
Business Process Svcs
ESIA – Services Architecture
Slide: 13
Conformity: these categories allow an application to be
measured against ESIA and a compliance plan created.
Connectivity
System Information
Registry (EDM)
Security
Presentation
User
Communities
Services
Interaction Services
Process
Search
Process Automation
Tailored Services
Interfaces
Infrastructure
Business Process Services
Support
Service / Function Interface
Functional Services
Enablement Services
Support Services
Data Services
ESIA – Services Architecture
Slide: 14
Core: Process
• ESIA: Does the application have documented business
processes that it aims to address?
• Benefit: Accessibility and transparency.
• Benefit: Facilitates process optimisation
• Benefit: Identifies duplicative processes
• Benefit: Supports process automation
• ESIA: Does the application have documented business rules
that govern these processes?
• Benefits: As above.
ESIA – Services Architecture
Slide: 15
Enablement: Security (Authentication and Authorisation)
•
•
•
•
Does the application perform its own authentication?
Does the application use the GUID for authentication?
Does the application perform its own authorisation?
Does the application use its own directory store for attributes used for
authorisation?
• ESIA: Does the application use PMI for authentication?
• Benefit: Consistency
• Benefit: Single point of audit
• Benefit: Standard approach
• Benefit: Reduces custom coding
• ESIA: Does the application use the PMI for authorisation?
• Benefits: As above
• ESIA:Does the application use standard attributes from the ED for
authorisation?
• Benefits: As above.
ESIA – Services Architecture
Slide: 16
Enablement: System Information Library (formerly known as EDM)
• Does the application have a documented data owner?
• Does the application have documented data expiration rules?
• Does the application store data that is also stored in other systems?
• Does the application have a documented data structure?
• Does the application have documented data definitions?
• Does the application have documented list of transformations needed for
connectivity with other applications?
• ESIA: Has the application’s data been recorded in the SIR?
• Benefit: Accessibility + transparency – enables optimisation
• Benefit: Single point of reference
• Benefit: Consistency and harmonisation
• Benefit: Change impact analysis
• Benefit: Clarity of ownership
• Benefit: Maps the data, processes, applications, owners in PwC context
• Benefit: Facilitates re-use.
ESIA – Services Architecture
Slide: 17
Enablement: Connectivity + Interfaces
• Does the application only provide dedicated interfaces for
connectivity to other applications?
• ESIA: Does the application use the messaging service for
connectivity to other applications?
• Benefit: Reduced spaghetti.
• Benefit: Re-usable connectors.
• Benefit: Consistency + control
• ESIA: Does the application support XML messages?
• Benefit: Industry standard
• Benefit: Focus expertise.
• Benefit: Flexible and extensible.
ESIA – Services Architecture
Slide: 18
Enablement: Process Automation
• Does the application use its own workflow technology?
• ESIA: Can the functions performed by the application be initiated
by an external Process Automation system?
• Benefit: Allows multiple applications that fulfil a single process to be
rendered as a service.
ESIA – Services Architecture
Slide: 19
Summary: conforming to ESIA offers significant benefits
across the spectrum of IT activities.
• Consistency
• User experience
• Business process transparency + optimisation
• Reduced custom coding
• Reusability
• Harmonisation
• “Audit-ability”
• Focused skills
• Market skills
• Risk management.
• These benefits are delivered in different areas as initiatives
conform to different aspects of the ESIA model
ESIA – Services Architecture
Slide: 20