Service-Oriented Enterprise Architecture Workshop Report

Transcription

1 Service-Oriented Enterprise Architecture Workshop Report 23 rd April 2008 Dr Christopher J Harding Forum Director Tel (mobile) c.harding@opengroup.org Thames Tower Station Road Reading RG1 1LX UK

2 Background Two-hour workshop on Tuesday April 22 nd Explored use of TOGAF to do SOA through a simulated real-life scenario 24 April,

3 The Simulated Scenario Small manufacturing company suffers trading difficulties Attributes problems to poor enterprise architecture Has done successful small-scale SOA project Engages consultancy to develop architecture vision With expectation of future work to develop full architecture and implement Expects vision to be based on SOA Requires use of TOGAF for architecture work 24 April,

4 Workshop Objectives Act out a project meeting of the architecture consultancy Scope the work required to develop Vision and Full architecture By taking a first pass through phases B, C, D. 24 April,

5 What Was Achieved Understanding of Phase A Initial thoughts on Phase B But this was valuable! 24 April,

6 TB Fabrications 24 April,

7 Overview Family-owned firm Makes custom metal fabrications for the construction industry (staircases, balustrades, guttering, doors,..) Factory and offices in Glasgow, UK $50M turnover, 250 employees Business suffering due to poor enterprise architecture 24 April,

8 Mission To produce high-quality custom-designed metal fabrications for the building industry anything made of metal that the architect wishes to specify but cannot obtain off the shelf. 24 April,

9 Business Strategy Family owned and run Design and production at single site All work in-house - no sub-contracting Sell to trade customers architects and builders Product promotion to the public as well as to trade Advertising and sales through trade publications and the Internet Materials ordered to meet demand no significant stock holding 24 April,

10 Business Goals and Drivers Long-term goal Steady profit to support owners Short-term drivers Sales have been declining steadily No major change in business environment Good product and workforce Customer dissatisfaction due to long lead times and missed delivery dates More efficient operation based on better IT is seen as solution 24 April,

11 Opportunities and Constraints Opportunities Death of founder enables radical changes to be made Recent web-based system enabling customers to design and configure products is a success attributed to SOA Constraints New development means borrowing should be phased with return from initial phases Don t want to lay off staff 24 April,

12 Business Architecture Orders Delivery (Plant & Equipment) (IT) (HR) 24 April,

13 Business Architecture Orders Customer Base Sales Sales Accounts Customers Designs Design Manufac g Instruct ns Product Info Advertis g 24 April,

14 Business Architecture Delivery Suppliers Accounts Materials& Suppliers Goods Inward Purchases Suppliers Stock Inventory Production Jobs Manufac g Instruct ns Shipping Delivery Info Customers 24 April,

15 Information Systems Sales: Subscription to SAAS sales package Accounts: Proprietary accounts package CAD: Proprietary computer-aided design package Product Configurator: in-house-developed web services that enable customers to do their own product configuration via a graphic web interface. Order Processing: Proprietary package. Production: Miscellaneous metal-bashing machines. Some are interfaced via a LAN to a PC in Production Control, where attempts are made to keep track of throughput, etc. There is no integrated manufacturing system. Materials: Database of materials, suppliers, and stock levels Various: PCs with spreadsheets and documents. 24 April,

16 Information Systems Orders Sales Customer Base Sales Accounts Sales Accounts Customers Designs Design Manufac g Instruct ns Product Configurator Product Info Advertis g CAD 24 April,

17 Information Systems Delivery Suppliers Materials Accounts Accounts Materials& Suppliers Goods Inward Purchases Suppliers Stock Inventory Production Jobs Manufac g Instruct ns Shipping Delivery Info Customers Production Order Processing 24 April,

18 Technology Architecture Product Configurator Web Server CAD Workstations Misc PCs Sales Internet Firewall LAN Materials Production Control Order Processing Accounts 24 April,

19 Architecture Principles Standard Principles from TOGAF April,

20 The Architecture Process 24 April,

21 Phase A Input from TBFL as good as you d get But not sufficient to develop vision Business Scenario needed Understand requirements Identify stakeholders SMART objectives Vision for business and technical solution Scope not just operations we are Enterprise Architects For example, we could identify improvements to manufacturing processes and equipment 24 April,

22 Pain Points Customers complaints Long delivery times Missed delivery dates Difficulty of finding out what s happening with their orders Staff complain of lack of direction and control Since old Mr Anthony went He knew everyone, could sort out problems and get orders through (No complaints about being held up by suppliers) 24 April,

23 Analysis Lack of internal efficiency a serious problem Need to Cut cycle time Improve visibility Could be gaps in the business processes Order processing Planning and scheduling Supply chain management Silo operations needs fixing Could be hidden agendas (does don t want to lay off staff mean don t want to change?) 24 April,

24 Vision Consistent product-agnostic interface to customer Capability to track internally and report externally Visibility Of production processes to customer Of materials ordering processes to production Event/exception reporting Customer self-service (eg. for place/change order) 24 April,

25 Business Architecture Business process analysis is crucial Sales, design, production, etc. should be broken down into functions End-to-end processes that are made up of these functions should be identified The functions should be defined as business services The processes should be defined as compositions of these services 24 April,

26 Where s the SOA? No change to business scenario process for SOA No architectural algebra SOA vision emerges because architects understand SOA and what it can do for business operations SOA methods and artefacts used in later phases 24 April,

27 SOA Principles Service Orientation Service Composition Messaging Loose Coupling Service Discovery Service Virtualization 24 April,

28 Governance Data Architecture (meta-data) & Business Intelligence QoS Layer (Security, Management & Monitoring Infrastructure Services) Integration (Enterprise Service Bus) SOA Reference Architecture Channel B2B Consumers Business Process Composition; choreography; business state machines Service Consumer Services atomic and composite Service Components OO Application Custom Application Packaged Application Existing Application Assets Service Provider 24 April,

29 Conclusions 24 April,

30 Conclusions Practical Guide approach validated as far as possible, given that the workshop was not completed Understanding of SOA by architects more important than having SOA artefacts Workshop should be completed to derive full conclusions 24 April,

31 Final Thought Business Architecture Technology Architecture 24 April,

32 Service-Oriented Enterprise Architecture Workshop Thank you! 24 April,