Presentation is loading. Please wait.

Presentation is loading. Please wait.

ESIA - Services Architecture Enterprise Services Integrated Architecture [ESIA] Viv Noot PwC.

Similar presentations


Presentation on theme: "ESIA - Services Architecture Enterprise Services Integrated Architecture [ESIA] Viv Noot PwC."— Presentation transcript:

1 ESIA - Services Architecture Enterprise Services Integrated Architecture [ESIA] Viv Noot PwC

2 ESIA – Services Architecture Slide: 2 A quick introduction…. Viv Noot – vivian.noot@uk.pwcglobal.comvivian.noot@uk.pwcglobal.com 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

3 ESIA – Services Architecture Slide: 3 Agenda for this session Why architecture? ESIA in words ESIA scenarios ESIA context ESIA model ESIA status ESIA conformity and benefits

4 ESIA – Services Architecture Slide: 4 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 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. More Statistics: 65 doors lead to blank walls 13 staircases lead nowhere 24 skylights in floors Division of Labour Builders: 147 Architects: 0 Source: www.winchestermysteryhouse.com

5 ESIA – Services Architecture Slide: 5 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.

6 ESIA – Services Architecture Slide: 6 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.

7 ESIA – Services Architecture Slide: 7 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 7

8 ESIA – Services Architecture Slide: 8 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”. 2

9 ESIA – Services Architecture Slide: 9 ESIA is one face of a four-sided pyramid that includes the Business, Standards and Principles. = Enablement Support Services Interaction Services Process Interface Functional Data User Communities Infrastructure Architecture Interface Standards Hardware Standards Software Standards Winning in The Marketplace Increase Profitability Best Place To Work The Business Buy / Build Global / LocalLeading Edge / Bleeding Edge OOTB / Customised Principles Business Architecture Information Architecture Enterprise Services Integrated Architecture

10 ESIA – Services Architecture Slide: 10 ESIA.Services is one component in the portfolio – supported by Principles, Business Requirements + Standards Enterprise Services Architecture ESIA.Infrastructure ESIA.Services Delivers tailored services to users, rather than silo applications. Delivers the hardware, networks, software and monitoring systems – the “pipes and sewers” Principles Business Drivers. Delivers the business requirements and organisation that must be addressed by the architectures and standards. ESIA.Information Delivers the framework for organising data, content, and information for accessibility and value.

11 ESIA – Services Architecture Slide: 11 ESIA.Services delivers tailored services to users – mapped to one or more functional systems and delivered using shared enabling components. Enablement ServicesSupport Services Interaction Services Tailored Services Business Process Services Service / Function Interface Functional Services Data Services User Communities ESIA.Infrastructure ESIA.Information

12 ESIA – Services Architecture Slide: 12 ESIA is a highly componentised model that allows functions from applications to be aggregated and presented as discrete services to the users. Enablement ServicesSupport Services Interaction Services Tailored Services Business Process Services Service / Function Interface Functional Services Data Services User Communities ED PMI EDM Middleware Hosting Workflow Search Staff Clients Prospects Alumni Suppliers Alliances User Support User Support Process Support Process Support Systems Support Systems Support I’structure Support I’structure Support Portal Other Billing New Client T & E Travel Business Process Business Process Business Rules Business Rules XML BAPI Other CRM Oasis GFS Orbit Data

13 ESIA – Services Architecture Slide: 13 Practicalities: ESIA and the Portal: the tabs reflect business processes. Set up a prospective client Business Process Svcs 1. Register prospect. 2. Prospect suitability. 3. Independence check 4. Report to user SAM interface Service/Function I/face Enablement Services Functional + Data Services EDM / MiddlewareData update + response EDM / Middleware Acceptance interface Independence interface User service interface Data update + response 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

14 ESIA – Services Architecture Slide: 14 Conformity: these categories allow an application to be measured against ESIA and a compliance plan created. Enablement ServicesSupport Services Interaction Services Tailored Services Business Process Services Service / Function Interface Functional Services Data Services User Communities Support Infrastructure Process Automation Services Process Presentation Search System Information Registry (EDM) Security Connectivity Interfaces

15 ESIA – Services Architecture Slide: 15 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.

16 ESIA – Services Architecture Slide: 16 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.

17 ESIA – Services Architecture Slide: 17 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.

18 ESIA – Services Architecture Slide: 18 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.

19 ESIA – Services Architecture Slide: 19 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.

20 ESIA – Services Architecture Slide: 20 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

21


Download ppt "ESIA - Services Architecture Enterprise Services Integrated Architecture [ESIA] Viv Noot PwC."

Similar presentations


Ads by Google