1. Safe roads, Reliable journeys, Informed travellers EA Reference Model Version 1.0

2. Safe roads, Reliable journeys, Informed travellers 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. Safe roads, Reliable journeys, Informed travellers 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. Safe roads, Reliable journeys, Informed travellers 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. Safe roads, Reliable journeys, Informed travellers Business Infrastructure Collaboration Operational Management Corporate Management Delivery Interfaces Customer Delivery ChannelsSuppliers / Partners / OGDs Service Management Basic EARM Structure

6. Safe roads, Reliable journeys, Informed travellers Business Infrastructure Collaboration Operational Management Corporate management Services generally available to provide consistent handling (yet enable flexibility, e.g.personalisation) of both input and output information. 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. 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 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. 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 Customer Delivery ChannelsSuppliers / Partners / OGDs Customer interaction with the HA Business – may involve collection as well as delivery of data/information ”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) Service Management 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. “Business Speak”

7. Safe roads, Reliable journeys, Informed travellers Business Infrastructure Collaboration Operational management Corporate Management 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.) 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). 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 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. 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. Customer Delivery ChannelsSuppliers / Partners / OGDs 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.. Service Management 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. “Techie Speak”

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

9. Safe roads, Reliable journeys, Informed travellers Infrastructure Collaborative & Common Services Core Processing Capabilities Corporate Information Integration Customer Delivery ChannelsSuppliers / Partners / OGDs Delivery Interfaces A Pictorial Representation of the EARM structure

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

11. Safe roads, Reliable journeys, Informed travellers Multiple Enterprises (the world we live in)

12. Safe roads, Reliable journeys, Informed travellers “Sliced” (multi-view) Enterprise Model Perspectives using the EARM