EA Reference Model

1. EA Reference Model Version 1.0

2. What is an EARM? • Enterprise Architecture Reference Model • A diagrammatic structure • … on which we can model facets of the enterprise (Views) • …allowing As-is to To-be transition modelling • Also enables classifications (taxonomies) to be set up… • … which facilitate a structured set of technology policies and standards

3. Why do we need an EARM? • Need to view (complex) enterprise perspectives in a consistent way • …because we need to identify business aspects, not just technology solutions. • Need to split out business processes, organisation, information, flows, data, etc • …but need to see them laid out in a consistent way (not just whiteboarded) • Assists with time-based modelling – we can “play” animated transition stages • Allows us to categorise and populate policies & standards.

4. Why do we need an HA-specific EARM? • The standard EARMs (TOGAF etc) tend to be too technology-based • We need to reflect the complex of roadside – national – regional – central organisation. • We need something simple.

5. Customer Delivery Channels Suppliers / Partners / OGDs Basic EARM Structure Delivery Interfaces Business Infrastructure Service Management Corporate Management Collaboration Operational Management

6. Customer Delivery Channels Suppliers / Partners / OGDs “Business Speak” ”The outside world” – interaction between HA and partners, suppliers, Government Departments & Agencies, etc. There will be overlaps with Customer Delivery Channels (and advantages to be gained from similar/identical input & output channels) Customer interaction with the HA Business – may involve collection as well as delivery of data/information Delivery Interfaces The means by which input and output information is delivered, received and processed “at the front line”. Distinct from Delivery Channels, as it will include location types like RCCs, NTCC & other types of “front line” business environments. Office desktop environments are also included Business Infrastructure Service Management Corporate management Collaboration Services generally available to provide consistent handling (yet enable flexibility, e.g.personalisation) of both input and output information. Integration of: data, functions, services, technologies & applications components. Includes: Security, non-functional requirements, integration of individual business-led IS/IT solutions to fulfil IS/IT strategy. These functions form a virtual network of connections between services. • Allows us to group, position & exploit data which is: • Recognised as Corporate, (& therefore shareable) irrespective of location • Shared across the organisation (& therefore needs to be managed consistently) • Used and re-used (& therefore needs to be validated, made & kept consistent, accurate & available) • It has particular relevance in terms of • Business Intelligence, single (virtual) information repositories & their related Information management & supply services. • Corporate Reference Data Generic services, not system specific, but used by a number of specific business services. e.g. collaboration, shared documents, workflow, work management, reference information, directories, business rules. Operational Management Back Office functions, (geographical location not necessarily the driver here), corporate information processing services, line of business services & functions. As a more “joined up” way of working across the HA evolves, we need to consider which services/functions/information need to be reclassified as “collaborative & common services” The base organisation in terms of policies, processes, services, organisation, roles, etc upon which all other services are positioned and function.

7. Customer Delivery Channels Suppliers / Partners / OGDs “Techie Speak” The means by which users access/interface systems & information, e.g. PCs, laptops, barcode scanners, PDAs, phones, Intelligent Devices, etc. Unmanned Remote Devices & Roadside technologies need sub-categories in this area too. An area over which we may have no (or limited) control - e.g. suppliers, partners, Internet, the general public, Government, other agencies (e.g. police). Some technologies may be identical or similar to Customer Delivery Channel technologies. Devices operated for HA by suppliers may be placed here.. Delivery Interfaces Functionality allowing Delivery Channels to interface with systems & data - e.g. thin client device interface may be a Browser, but thick clients (e.g. workstations) contain local applications/data, which may may function independently or may use other services. Call centres, RCCs, NTCC environments would be described here. Business Infrastructure Service Management Corporate Management Collaboration Services generally available to provide consistent handling (yet enable flexibility, e.g.personalisation) of both input and output data, .e.g. Portals, Data Validation, Content Management, Input Services (OCR, ICR, electronic forms, etc.), Output Services (Print handling, electronic output, etc.) The IT Strategy should aim to simplify data capture, storage & use. Integration of data, functions, services, technologies & application components, should therefore be enabled, using tools such as: Single sign-on, EAI, messaging, business connectors, etc. These functions form a virtual network of connections between services. • Allows us to group/position data which is: • Recognised as Corporate, (& therefore shareable) irrespective of virtual or physical location • Shared across the organisation (& therefore needs to be managed) • Used and re-used (& therefore needs to be validated, made & kept consistent, accurate & available) • It has particular relevance in terms of • Data Warehouse(s) and their related Information management & supply services (eg ETL, marts, BI tools, etc). • Corporate Reference Data Generic services, not application specific, but related to applications, e.g. middleware, workflow, work management, publish-and-subscribe, directories, business rules, common code data stores. Many legacy application components have potential for re-engineering as re-usable, common business services (when business drivers open up the opportunities to do so). Operational management Whilst legacy systems cannot be placed here in the pure sense, we tend to place them here when representing the “Big Picture”, in recognition of their core qualities; transaction processing, business process & function/product specific handling capabilities. For HA, we would nominally place “Line of Business” applications here. When we want to drill down & explore each application though, we might examine the functions of the application mapped across all layers. The base of IT environments, Platforms, Communications, systems management and people upon which the Applications and services are positioned and function.

8. Voice - Phone Email Text Messaging PDAs Specialised Eqpt Acquisition Metadata MI Data Mgmt Data Modelling End-User Access & Reporting Agent desktop appln Task interaction Security Admin & Mgmt 1. Customer Delivery Channels 2. Suppliers / Partners / OGDs IS/IT Taxonomy 1.1 Channel Environments 2. External Environment We need to detail Categorisations in terms of roadside technologies, ITS, etc here Remote access Delivery Interfaces 3.1 Workstation Environment 3.2 Office/ Presentation Servers 3.3 Contact & Operational Centres (e.g. RCC, NTCC) Web Browser Personal Productivity Corporate Access User developed applns Diary & Email Do we have any? 9. Business Infrastructure 8.Corporate Management 6. Service Mgt 4 & 5 Collaboration 6.6 Security 4.1 Input Services Authentication Authorisation Access Accounting Audit File Encryption Network Secrty Boundary Prtcn Anti-Virus 4.2 Output Services 4.3 Portals, Collaboration etc. 8.4 Management Information Image/Recognitn File Transfer Data Validation MMDI O/P Generation Bulk O/P Printers O/P Handling Electronic I/P Non-electronic I/P Doc Interchange Portals News svce Collaboration Webcasts Content Management 6.1E-Business svcs E-Commerce Exchanges Portals Supply Chain Intgtn 5.1 Workflow & Orchestration 5.2 Directories & Business Rules 8.5 Reference Data Ref.Data Supply Extract (from source systems) Transform Load Directory Servers Metadirectories Business Rules Enterprise Directories Infrastructure Directories Application Directories Workflow Work management Orchestration 6.2 B2B Integration Partner Mgt Stds based App Int 8.3 Data Exploitation 7. Operational Management 6.3 Co-ord & Control Extract/Use (from Warehouse) Process Coordtn Event & state Mgt Transaction Mgt Autonms Wflow Mgt 9.4 Sys Mgt Datacentre Mgt Office Mgt Systems Monitoring Performance Mgt Event Mgt Asset Mgt Problem Mgt Request Mgt Software Mgt Network Mgt 7.1 Strategic Applications 8.2 Data Warehouse COTS solutions Bespoke Solutions 6.4 Appl Integration Extract (from source systems) Transform Load Manage Application Access Transformation Synchronisation Security/Accss Ctrl Data Distribution 7.2 Local/Line of Business COTS solutions Bespoke Solutions 8.1 Corporate Database Engines 6.5 Data Mvmt & Exchg Messaging/Q’ing File Transfer Distrbtd Objct Svcs Intelligent Routing Handoff Conversn Security Proprietary mchnsms Replication Data Exchange Data Quality 9.2 Platforms 9.5 Communications 9.1 Datastores Hardware Op System Platform Placement Business Continuity Archiving Backup/Restore Local Area Networks Wide Area Networks

9. Infrastructure A Pictorial Representation of the EARM structure Customer Delivery Channels Suppliers / Partners / OGDs Delivery Interfaces Integration Collaborative & Common Services Corporate Information Core Processing Capabilities

10. These apply across all layers. Non Functional Requirements 10.10 Legal & Policy 10.9 Business Continuity 10.8 Maintainability 10.7 Usability 10.6 Interoperability 10.5 Integrity 10.4 Efficiency 10.3 Measurability 10.2 Availability 10.1 Development & Testing

11. Multiple Enterprises (the world we live in)

12. Perspectives using the EARM “Sliced” (multi-view) Enterprise Model