Safe roads, Reliable journeys, Informed travellers
Upcoming SlideShare
Loading in...5
×
 

Safe roads, Reliable journeys, Informed travellers

on

  • 430 views

 

Statistics

Views

Total Views
430
Views on SlideShare
430
Embed Views
0

Actions

Likes
0
Downloads
4
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • The HA EA Framework is represented visually above and can broadly be broken down into the following areas: The core (dark blue) areas: Business Vision and Business Architecture: This drives from the HA Board strategy and capability maps, as well as the HA business plan. Below these high levels, we must link in the next level of capabilities (and when they are needed) and then decompose down into business organisation, function, service and process. Measurables, external drivers, business principles etc must also be captured. These will combine to drive the IS/IT principles (we already have these in published form via the HA CIO, and these will be mapped back to business principles. Major business change initiatives must be mapped into this area. The business architecture must be Directorate-independent, which in turn will allow it to be flexible and responsive to high level business change in the future. However, organisation models should reflect both current and planned organisation structure. AS-Is IS/IT Architectures We already have (to a certain extent) some models of Information Systems (“Applications”) and Corporate Metadata modelled, as well as a wealth of knowledge across the HA on current IS/IT. The task is now to model this and represent the range of IS/IT services presented. This can tell us a lot about our As-Is business architecture (in particular the “stovepiping” characteristic which tends to define both our current business and current technologies). Thus, the As-Is is key to back-engineering and analysing what replication of services (business and technology we already have). Slide 6 shows this aspect also. To-Be IS/IT Architectures To date, To-Be architectures have tended to be visions of future technology solutions, often physical (i.e. specific products and platforms), produced within projects and specific to each project’s business requirements. This has prolonged our “stovepipe” culture. The EA’s To-Be area addresses this deficit by providing a more conceptual and logical feel to future IS/IT. It will contain: An HA EA Reference Model (the EARM). This is a template upon which we can map both business and technology architectures out at various levels, providing consistency and understanding of context. You will see real world examples using the EARM on slides 8-12. An EA Technology Function Taxonomy/Catalogue – using as a background the EARM, a taxonomy of technology functions provides us with a ready made catalogue of distinct IS/IT services, for which technology policies and standards can be written and managed. 2a. The Technology Policies and Standards themselves, specifying recommended and mandatory technology products, versions, protocols, etc for each technology category. Standards will be organised to allow continual review of emerging technologies and “sunsetting” of obsolete standards. 3. Again, using the EARM, conceptual and logical models of enterprise or specific line of business perspectives on IS/IT can be modelled and used as target architectures to which physical architectures would aspire (see “Transformation Roadmaps” below). Transformation Roadmaps Building on the As-Is IS/IT Architecture models, the roadmaps will be developed to show how particular systems or families of systems and technologies must evolve to converge with the strategic vision of IS/IT services as defined in the To-Be architecture. This may be by way of timeline diagrams, or “animated” architectures showing how architectures will develop incrementally (or combinations of both). Alignment Layer On the face of it, the Alignment layer replicates (a) the lower level(s) of the business architecture and the upper level(s) of the IS/IT architecture to show how business service requirements will be met by IS/IT services. The layer must be consistent and usable irrespective of which service supplier it is used with. It is the area where we expect and manage consistent understanding and operation of IS/IT services aligned to the business. Note that of particular interest will be Non-Functional Requirements, which will be structured in a way most suited to reduction of cost and complexity in the area of service management and provision (as well as HA project management). Transition Management This area will document the programmes and projects which both impact the EA and are impacted by other projects and events in the EA. It will be an area of interface with such bodies as the Information project Board and Investment Control Framework. As and when the culture changes to capability-driven projects, the area may be used to examine “what-if” scenarios in terms of how projects/programmes might be scoped and implemented to get best value for money. Analysis This area will capture the “softer” aspects which will inevitably arise as we model both business and technology architectures. These will surface as issues, strengths, weaknesses, opportunities, threats, etc., and must be captured so that we can assimilate their impact on the enterprise (particularly business impact). Process & Governance This area will contain the EA Team’s formal documentation which describes their scope, their processes and roles and responsibilities in terms of defining, populating, maintaining, publishing and exploiting the EA.
  • Here is a representation of the structure in a top-down, line-of-sight business architecture. The representation covers three key areas (from top to bottom): Vision, Mission, Goals, Objectives and Measures. These are all directly referenceable in the HA Business Plan and associated Balanced Scorecard documents. To-Be Capabilities. This is the key new part of the Business Architecture. IT allows us to link (“align”) the more detailed function, process and information work usually carried out by projects with the higher level Vision, Goals, Measures, etc. It also allows us to develop Strategy (or to place Strategy plans that have already been published) so that, at a high level, we can see how we are going to achieve the capabilities (and when) and serves as a springboard for generating business policy. Business strategy, principles and policy will of course drive technology strategy, principles and policy. The more detailed To-Be Business Functions, (which may be thought of as high level processes), organisation structures, business information, lower level processes and functional /non-functional requirements. This area will be where projects contribute to the architecture as well as use it.
  • The use of POTIs and (EA) capabilities enables: Alignment of programme/project deliverables to Agency business plan Structured breakdown of project deliverables (POTI with As-is & To-Be views) Detailed business plan with visioned capabilities Mapped onto a timeline “ Amount” or “degree” of capability over time can be assessed Enabling governance of scope, priority, dependencies of future programmes

Safe roads, Reliable journeys, Informed travellers Safe roads, Reliable journeys, Informed travellers Presentation Transcript

  • Business Architecture Navigational Model Version 1.0
  • Transition Management Projects, Programmes, Change Management, Landscapes & Perspectives Analysis - Issues, SWOTs, Risks Process & Governance Ensuring use of EA Ensuring maintenance of EA QA, Maturity & continuous Improvement Alignment Layer Translating & meeting Business Requirements “ As-Is” IS/IT Architectures Physical Current + snapshots in time “ To-Be” IS/IT Architectures Conceptual/Logical The future vision for IS/IT Tech Policies & Standards Transformation Roadmaps Business Vision & Business Architecture HA Enterprise Architecture Framework - Business Architecture Ver. 0.0
  • Business Vision & Business Architecture Business Architecture Structure & Decomposition Reference Model Structure & Use Business Architecture Policy HA Business Architecture Major Components To-Be Business Capability Models Business Architecture Content Enterprise Capabilities Timeline As-Is Business Capability Models Click each area to explore in more detail
  • Business Mission & Goals Business processes Business information Business (service) Requirements (functional & non-functional) Business Objectives & Key Performance Measures Strategy (How…) DfT Vision & Goals Organisation Structure(s) To-Be Business Functions Critical Business issues To-Be CAPABILITIES Key Business Policies HA Business Architecture Overview This is the basic structure of the HA Business Architecture. Click each area To explore in more detail
  • Business Mission & Goals Business Objectives & Key Performance Measures DfT Vision & Goals The highest three levels of the structure represent information that is already published and mandated by the DfT and HA. The Business Architecture simply captures and interlinks these items with lower level detail. Critical Business issues (SWOTS etc) HA Business Architecture - Business Plan Areas e.g. EU and UK legislation, environmental drivers, budgetary restrictions, etc External drivers - high level SWOTs (Strengths, Weaknesses, Opportunities, Threats) Balanced Scorecard and capabilities matrix, representing the targets that HA Directors and their Directorates. Business Objectives and Key Performance Measures The published business plan and Board level aspirations for HA’s development in the longer term future. Highways Agency Business Mission and Goals External drivers and governance emanating from the Department for Transport DfT Vision and Goals Content Area of Structure
  • Business Mission & Goals Project A- Oriented Business Reqts Business Objectives & Key Performance Measures DfT Vision & Goals Project B- Oriented Business Reqts Project B- Oriented Business Reqts Project C- Oriented Business Reqts Project D- Oriented Business Reqts Project Requirements Some (inconsistent) references to Business Plan… Solutions & requirements are expressed inconsistently Business Mission & Goals HA Business Architecture Business Objectives & Key Performance Measures Strategy (How…) DfT Vision & Goals Critical Business issues To-Be CAPABILITIES Current situation – inconsistent project requirements delivered
    • Without a layer of “capabilities”, a lack of consistency in the way projects architect business solutions is evident:
    • “ Stovepipe” architectures around each project
    • Different languages (exacerbated by third party work)
    • Lack of consistent upward reference to prioritised business plans
    • All leading to more effort required to build business cases
    • By establishing a “capabilities” layer we establish:
    • A relationship to the business plan
    • A means of determining alignment to the business needs & business strategy.
    • A way of determining consistency in the language which projects express requirements & solutions.
  • Business (service) Requirements (functional & non-functional) To-Be Organisation Structure(s) To-Be Business Functions (High-Level Processes) Key Business Policies Projects Projects interact with the Business Architecture by working with more detailed Capabilities – i.e. Functions or high level process
    • Projects look to the Business Architecture for re-use opportunities – but also contribute to the detailed to-be vision by identifying new :
    • high level functions
    • processes
    • information
    • flows
    • required business services
    • organisation change
    • etc
    Click for More detail… HA Business Architecture Project Collaboration Area Business Mission & Goals Business Objectives & Key Performance Measures Strategy (How…) DfT Vision & Goals To-Be CAPABILITIES
  • Business Mission & Goals Capabilities (& when needed…) Business processes Business information Business (service) Requirements (functional & non-functional) Business Objectives & Key Performance Measures Strategy (How…) DfT Vision & Goals Organisation Structure(s) Core Strategy Enablers Customers & Stakeholders Financial Accountability Building & Sustaining Capability To-Be Business Functions Enterprise Timeline Critical Business issues (SWOTS etc) Case for Action (sense of urgency for change) Key Business Policies OLD (As-Is) Business Models Incident Mgt Traffic Mgt Information Mgt Infrastructure Mgt Common HA Business Architecture In More Detail Resource Mgt … using the HA EA REFERENCE MODEL Using Non-Functional Reqt Profiles … using the HA EA REFERENCE MODEL
  • Business Mission & Goals Capabilities Business processes Business information Business (service) Requirements (functional & non-functional) Business Objectives & Key Performance Measures Strategy (How…) DfT Vision & Goals Organisation Structure(s) Core Strategy Enablers Customers & Stakeholders Financial Accountability Building & Sustaining Capability To-Be Business Functions Enterprise Timeline Case for Action (sense of urgency for change) Key Business Policies Incident Mgt Traffic Mgt Projects HA Business Architecture detail showing where projects interact Information Mgt Infrastructure Mgt Common Resource Mgt … using the HA EA REFERENCE MODEL Using Non-Functional Reqt Profiles
    • The HA Business Architecture will be used as follows:
    Business Strategy Information Principles EA Principles Business Architecture Policy Note: A link to a structured principles & policies area will shortly be published To assimilate business architecture content into an Agency-wide business architecture and to maintain that content in a timely manner. To produce views or analyses of the architecture which are relevant, focussed and useful to the above stakeholders. Strategy and Planning To use the Business Architecture to assist joint understanding between service managers and service providers, in terms of the IS/IT services required to support required business services. Service Management To use the Business Architecture as a means of identifying, specifying and/or designing aligned IS/IT services required to support required business services. Development To assess the Agency’s portfolio of information projects, identifying alignment, divergence, replication and gaps. To escalate divergence, replication and gap issues upwards for informed decision-making – or to identify new projects which address such issues. Information Project Office To use the business architecture, its constructs and its content to assess the fit of projects in the Agency’s business plan and to identify re-use, alignment and divergence potential. To show architected business solutions using the business architecture language and constructs. Project Teams To communicate the concepts of the business architecture and promote best practice and mandated usage of it. CRG Team To mandate use of a common language and structure for business architecture, as a means of expressing the Agency’s Business Plan in detailed, maintainable form. To govern by way of alignment of technology solutions to business needs, and to make appropriate decisions where divergence or misalignment is identified. Information Directorate Use of Business Architecture (EA) Business Area
  • Business Strategy Information Principles EA Principles Business Architecture Policies Use of Architecture Alignment Information Policy Technology Services Security These areas are published & maintained as part of the Agency-wide Business Plan These areas are published & maintained within the Enterprise Architecture
  • Reference Model Structure & Use - 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
    • Later (when we model Technology) it enables classifications (taxonomies) to be set up…
    • … which facilitate a structured set of technology policies and standards, aligned to the business architecture!
  • Why do we need a Reference Model?
    • We need to view (complex) enterprise perspectives in a consistent way
    • … because we need to identify business aspects, not just technology solutions.
    • We 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.
    Why do we need an HA-specific Reference Model?
    • The standard models (TOGAF etc) are too technology-based
    • We need to reflect the complex of roadside – national – regional – central organisation.
    • We need something relatively simple.
    T.R.U.E. Information Dissemination T.R.U.E. Information Dissemination
  • The Reference Model (EARM) described by section Business Infrastructure Collaboration Operational Management Corporate Management Information & capabilities that support more than one other service. Generic services, not system specific, but used by a number of specific business services. e.g. collaboration, shared documents, “single version of truth” (e.g. state of the road network), workflow, work management, reference information , directories, business rules , standard data input & information publishing services, etc. Corporate governance aspects can also be placed in this area – policies, standards, & business rules & metadata (information about data).
    • Allows us to group, position & exploit data which is:
      • Is non-time-critical (i.e. not core operational data).
      • 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 information repositories & their related Information management & supply services.
      • Corporate Reference Data
    Back Office functions, corporate operational information processing services, “line of business” services & functions. These capabilities can be thought of as the unique components that form the core of our operational processes. Where a capability is used by more than one other capability, then we would consider placing them in the “Collaboration & Operational Intelligence” section. The base organisation in terms of Business Services, organisation, roles, etc upon which all other services are reliant. Delivery Interfaces The means by which input and output data is received, delivered & processed “at the front line”. It includes location types like RCCs, NTCC, Contact Centres & other types of “front line” business environments. Office desktop environments are also included Customer Delivery Channels Suppliers / Partners / Other Govt Depts Customer interaction with the HA Business – including data collection and information delivery ” The outside world” – interaction between HA and partners, suppliers, Government Departments & Agencies, etc. There are overlaps with Customer Delivery Channels - and advantages are to be gained from similar/identical input & output channels Service Management
    • Integration of:
    • Data
    • Functions
    • Services
    • Technologies & applications components.
    • Includes:
    • Security
    • Resiliency
    • Business Continuity
    • These functions form a virtual network of connections between services.
    Reference Model Areas
  • “ Sliced” (multi-view) Enterprise Model Perspectives using the Reference Model (EARM)
  • Capabilities & high level processes modelled using the standard Reference Model. Relevant views & levels will be produced according to need. All levels are aligned up to Level 0 which itself is aligned to the Business Plan. Level 0 is high level and conceptual. Created by the EA Team, It relates to the Business Plan and Strategy. From this is produced: Traffic Management Incident Management Infrastructure Management Information Management Common Capabilities Business Management
    • 2. Multiple, limited Level 2 pictures (“Views”)
    • These will be used by Project Teams to
    • Identify & clarify To-Be business capabilities
    • Modify & use for business solution architecture (POTIs)
    • Feed back their content to the EA Team
    • A single, Level 1 view showing “everything”.
    • Maintained by the EA Team. This is useful to (a few) users who want to look at the entire set of high level functions in the To-Be architecture – but is not useful to everyone because it is difficult to see particular areas or “themes” amongst all the detail.
    HA To-Be Business Capabilities - How it works Level 0 Level 1 “everything” Level 2 “Views” (Business) Infrastructure Operational Intelligence (Time Critical) Operational Capabilities Network Description & Referencing Security & Data Integration National State of the Network Performance Monitoring & Management Operational Management T.R.U.E. Information Dissemination ( T rusted, R eliable, U seful, E ffective) Governance Business Intelligence Information Input & Validation Collect Data Publish Intelligence Business Intelligence (non-time critical) “ One version of the truth” Business management & Supporting Services ) ) ) ) ) Infrastructure Publish Intelligence Delivery Interfaces Operational Intelligence (Time Critical) Operational Capabilities Integration Collect Data Network Description & Referencing Manage Facilities General Public Operational Partners Traffic Monitoring Communications Capability Service Providers (ISUs) CCTV & Roadside Data Storage DfT (Sec of State) Emergency Services Media (VASPs) Traffic Officers HR Finance HA To-Be Business Capabilities Map – Level 1 General Public (Informed Travellers) Operational Partners (Traffic Mgt Act) Roadside Communications Traffic Profiles (Road Timetable) National State of the Network Performance Monitoring Infrastructure Management Resource Management Office Systems Data & Information Management Scheduled Roadworks Planned Events Unplanned Events Traffic Condition Information Weather Information Abnormal Loads Information Situational Awareness Asset Management Operations Traffic Officers Management Vehicle Management Information input & validation Security Inter-system data exchange Phone/ Email/ Fax Communications Traffic Management Audit, Logging, etc Reviewing (Evaluation of Response) Modelling (What-if evaluations) Performance Analysis (PSA Targets) Policies & Standards Governance Planning (Development of Response) Corporate Metadata Registry Information Dissemination T.R.U.E. Information Web Signs& Signals X Phone Radio TV Inter-system data exchange Call/Contact Centre Procurement Incident Management Traffic Data/ Information Collection & Data Fusion Geo- Graphical presentatn (Other) Infrastructure Management Operations Traffic Management Operations Incident Management Operations Performance Monitoring & Management Performance Management Organise & Manage Business Data & Information
  • Business Infrastructure Collaboration Operational Management HA Road Network Definition HA Business Capabilities – High Level (Level 0) View National State of the Road Network Real-Time Performance Management T.R.U.E. Information Dissemination ( T rusted, R eliable, U seful, E ffective) Governance Business Intelligence Data Input & Validation Collect Data (Acquisition of Traffic & Travel Information from External Partners & Public) Publish Intelligence (Dissemination of Traffic & Travel Information to External Partners & Public) Corporate Management Business Management & Supporting Services Coordination with External Parties Resource Management Traffic Management Incident Management Service Management Security Business Continuity Service Integration Infrastructure Management Corporate Reference Information
  • Business Infrastructure Business Management & Supporting Services Publish Intelligence Collaboration Operational Management Service Management Collect Data HA Road Network Definition General Public (ERTs etc) HA Business Capabilities Model – Level 1 View Roadside Communications National State of the Road Network Performance Monitoring Data Input & Validation Inter-system data exchange Reviewing Modelling Performance Analysis Business Intelligence Planning Corporate Management T.R.U.E. Information Dissemination Web Phone Radio TV Inter-system data exchange Incident Management Geo- Graphical presentatn Real-Time Performance Management Performance Management Incident detection Incident Confirmation Impact Analysis Incident Response Incident Closure Road Network Modelling Location Reference Translation Roadside Data Storage Road-side Devices Traffic Management Strategic Network Coordination Tactical Traffic Management and Control Coordination of Traffic & Travel Information disseminated externally from the HA Coordination of Information disseminated internally around the HA Coordination with External Parties Traffic Management planning & co-ord Incident Management planning & co-ord Resource Management Infrastructure Management (Inventory) Data Management Programme Development Planning & Scheduling Governance Policies & Standards Corporate (meta)data catalogue Workflow Enterprise Architecture Audit & Assurance HR Finance Facilities Management Technology & Comms Mgmt Procurement Collection & Management of Historical Data Corporate Reference Information Business Rules Call/Contact Centre Reference Data Security Business Continuity Service Integration Disaster Recovery Resilience Enterprise Service Bus Access Control Single Sign-On ID Mgmt Network Security Traffic Monitoring CCTV Emergency Services Media (VASPs) Traffic Officers General Public (Informed Travellers) Operational Partners (Traffic Mgt Act) Forecast Traffic Condition Office Systems Forecast Events Current Events Current Traffic Condition People Management Vehicle Management Voice/Email/Fax Communications Signs& Signals X DfT (Sec of State) Major Projects Operational Partners (e.g. Maint Orgns) Service Providers (Incident Support Units)
  • Business Infrastructure Publish Intelligence Delivery Interfaces Collaboration Operational Management Service Management Collect Data To-Be Information Model – Level 1 Roadside Communications National State of the Road Network Office Systems Information input & validation Inter-system data exchange Traffic Management Corporate Metadata Registry Corporate Management Information Dissemination T.R.U.E. Information Incident Management Data & Information Management Modelling Planning Infrastructure Management Asset Configuration Data (including Site Data) Asset Faults & Defects Status of Assets CCTV Images Network Definitions Settings of Roadside Devices Traffic Management Plans & Policies Asset Details, Properties & Relationships Tracking of abnormal, dangerous, precious or perishable goods Maintenance SLAs Relationships of Communication Links & Networks Location & Status of Deployed Resources Network Performance Profile Data Power Distribution Network Details Functional Assignment & Operator Actions Log Traffic Data Events/Situations (traffic related on & off network) Events/Situations (non traffic related) Historical Network Performance Data Management Historical Network Performance Data Models Analysis & Planning Information Governance General Public (ERTs etc) Web Phone Radio TV Inter-system data exchange Geo- Graphical presentatn Asset Modelling “Sandpit” Traffic Monitoring CCTV & Roadside Data Storage Emergency Services Traffic Officers Major Projects Operational Partners (e.g. Maint Orgns) Service Providers (Incident Support Units) Media (Value Added Svce Providers) General Public (Informed Travellers) Operational Partners (Traffic Mgt Act) DfT (Sec of State) Signs& Signals X
  • Business Infrastructure Business Management & Supporting Services Collaboration Operational Management Service Management HA Road Network Definition General Public (ERTs etc) Roadside Communications National State of the Road Network Performance Monitoring Data Input & Validation Inter-system data exchange Reviewing Modelling Business Intelligence Planning Corporate Management T.R.U.E. Information Dissemination Web Phone Radio TV Inter-system data exchange Incident Management Geo- Graphical presentatn Real-Time Performance Management Performance Management Incident detection Incident Confirmation Impact Analysis Road Network Modelling Location Reference Translation Roadside Data Storage Road-side Devices Traffic Management Strategic Network Coordination Tactical Traffic Management and Control Coordination of Traffic & Travel Information disseminated externally from the HA Coordination of Information disseminated internally around the HA Coordination with External Parties Traffic Management planning & co-ord Incident Management planning & co-ord Resource Management Infrastructure Management Governance Corporate (meta)data catalogue Corporate Reference Information Business Rules Call/Contact Centre Security Business Continuity Service Integration Disaster Recovery Resilience Enterprise Service Bus Access Control National State of the Road Network Capabilities – (Filtered View) Traffic Monitoring CCTV Emergency Services Media (VASPs) Traffic Officers General Public (Informed Travellers) Operational Partners (Traffic Mgt Act) Forecast Traffic Condition Forecast Events Current Events Current Traffic Condition Voice/Email/Fax Communications Signs& Signals X DfT (Sec of State) Major Projects Operational Partners (e.g. Maint Orgns) Service Providers (Incident Support Units)
  • Business Infrastructure Business Management & Supporting Services Collaboration Operational Management Service Management HA Road Network Definition Roadside Communications National State of the Road Network Performance Monitoring Data Input & Validation Inter-system data exchange Reviewing Modelling Performance Analysis Business Intelligence Planning Corporate Management T.R.U.E. Information Dissemination Inter-system data exchange Incident Management Geo- Graphical presentatn Real-Time Performance Management Performance Management Impact Analysis Road Network Modelling Location Reference Translation Coordination of Information disseminated internally around the HA Coordination with External Parties Infrastructure Management (Inventory) Data Management Programme Development Planning & Scheduling Governance Policies & Standards Corporate (meta)data catalogue Audit & Assurance Finance Facilities Management Technology & Comms Mgmt Corporate Reference Information Business Rules Reference Data Security Business Continuity Service Integration Disaster Recovery Resilience Enterprise Service Bus Access Control Infrastructure Management Capabilities – (Filtered View) Procurement Traffic Monitoring Traffic Officers Operational Partners (Traffic Mgt Act) Forecast Traffic Condition Forecast Events Current Events Current Traffic Condition Voice/Email/Fax Communications DfT (Sec of State) Operational Partners (e.g. Maint Orgns) Service Providers (Incident Support Units)
  • Business Infrastructure Business Management & Supporting Services Collaboration Operational Management Service Management HA Road Network Definition Roadside Communications National State of the Road Network Data Input & Validation Inter-system data exchange Reviewing Business Intelligence Planning Corporate Management T.R.U.E. Information Dissemination Inter-system data exchange Incident Management Geo- Graphical presentatn Incident detection Incident Confirmation Impact Analysis Incident Response Incident Closure Road Network Modelling Location Reference Translation Traffic Management Strategic Network Coordination Tactical Traffic Management and Control Coordination of Traffic & Travel Information disseminated externally from the HA Coordination of Information disseminated internally around the HA Coordination with External Parties Incident Management planning & co-ord Resource Management Governance Workflow Technology & Comms Mgmt Collection & Management of Historical Data Corporate Reference Information Business Rules Call/Contact Centre Reference Data Security Business Continuity Service Integration Disaster Recovery Resilience Enterprise Service Bus Access Control Network Security Incident Management Capabilities – (Filtered View) Traffic Monitoring CCTV Emergency Services Traffic Officers Operational Partners (Traffic Mgt Act) Forecast Traffic Condition Forecast Events Current Events Current Traffic Condition People Management Vehicle Management Voice/Email/Fax Communications DfT (Sec of State) Operational Partners (e.g. Maint Orgns) Service Providers (Incident Support Units)
  • Business Infrastructure Business Management & Supporting Services Collaboration Operational Management Service Management HA Road Network Definition Roadside Communications National State of the Road Network Data Input & Validation Inter-system data exchange Modelling Business Intelligence Corporate Management T.R.U.E. Information Dissemination Inter-system data exchange Incident Management Geo- Graphical presentatn Impact Analysis Incident Response Incident Closure Road Network Modelling Location Reference Translation Road-side Devices Traffic Management Strategic Network Coordination Tactical Traffic Management and Control Coordination of Traffic & Travel Information disseminated externally from the HA Coordination of Information disseminated internally around the HA Coordination with External Parties Traffic Management planning & co-ord Incident Management planning & co-ord Resource Management Infrastructure Management (Inventory) Data Management Governance Workflow Technology & Comms Mgmt Collection & Management of Historical Data Corporate Reference Information Business Rules Call/Contact Centre Reference Data Security Business Continuity Service Integration Disaster Recovery Resilience Enterprise Service Bus Access Control Traffic Management Capabilities – (Filtered View) Traffic Monitoring CCTV Traffic Officers Operational Partners (Traffic Mgt Act) Forecast Traffic Condition Forecast Events Current Events Current Traffic Condition People Management Voice/Email/Fax Communications Signs& Signals X DfT (Sec of State) Operational Partners (e.g. Maint Orgns)
  • Business Infrastructure Publish Intelligence Delivery Interfaces Collaboration Operational Management Service Management Collect Data Traffic Monitoring Resource Management Capabilities – (Filtered View) Traffic Management Incident Management Governance Corporate Metadata Registry Corporate Management Information Dissemination T.R.U.E. Information Inter-system data exchange Infrastructure & People Management Traffic Data/ Information Collection & Data Fusion Mgt Internal Service Providers Mgt External Service Providers Resource Mgt pols Quality Mgt Define Perf Msrs Communications Capability Finance Data & Information Management Procurement Geo- Graphical presentatn Performance Monitoring & Management Modelling Planning Deployment of HA resources (TOs, ISUs, maintaining agent contractors) Respond to resource deployment requests Roadside Communications Automated data input & validation Inter-system data exchange Data input & validation requiring manual action National State of the Network HA Network Definition Network Reference Model 3rd Party Spatial Info Inventory Repository Operational Partners Service Providers (ISUs) Traffic Officers Operational Partners (Traffic Mgt Act) DfT (Sec of State) Office Systems Voice/ Email/ Fax Communications Forecast Traffic Condition Forecast Events Current Events Current Traffic Condition
  • Business Infrastructure Business Management & Supporting Services Collaboration Operational Management Service Management HA Road Network Definition Roadside Communications National State of the Road Network Performance Monitoring Data Input & Validation Inter-system data exchange Modelling Business Intelligence Planning Corporate Management T.R.U.E. Information Dissemination Inter-system data exchange Incident Management Geo- Graphical presentatn Real-Time Performance Management Performance Management Impact Analysis Incident Response Incident Closure Road Network Modelling Location Reference Translation Traffic Management Strategic Network Coordination Tactical Traffic Management and Control Coordination of Traffic & Travel Information disseminated externally from the HA Coordination of Information disseminated internally around the HA Coordination with External Parties Traffic Management planning & co-ord Incident Management planning & co-ord Resource Management Infrastructure Management Governance Workflow Audit & Assurance HR Facilities Management Procurement Collection & Management of Historical Data Corporate Reference Information Business Rules Reference Data Security Business Continuity Service Integration Enterprise Service Bus Access Control Resource Management Capabilities – (Filtered View) Traffic Monitoring Traffic Officers Operational Partners (Traffic Mgt Act) Forecast Traffic Condition Office Systems Forecast Events Current Events Current Traffic Condition People Management Vehicle Management Voice/Email/Fax Communications DfT (Sec of State) Operational Partners (e.g. Maint Orgns) Service Providers (Incident Support Units)
  • Business Infrastructure Business Management & Supporting Services Publish Intelligence Collaboration Operational Management Service Management Collect Data HA Road Network Definition General Public (ERTs etc) Roadside Communications Forecast Traffic Condition National State of the Road Network Performance Monitoring Forecast Events Current Events Current Traffic Condition Data Input & Validation Inter-system data exchange Reviewing Modelling Performance Analysis Business Intelligence Planning Corporate Management T.R.U.E. Information Dissemination Web Phone Radio TV Inter-system data exchange Incident Management Geo- Graphical presentatn Real-Time Performance Management Performance Management Road Network Modelling Location Reference Translation Roadside Data Storage Road-side Devices Traffic Management Coordination of Traffic & Travel Information disseminated externally from the HA Coordination of Information disseminated internally around the HA Coordination with External Parties Resource Management Infrastructure Management (Inventory) Data Management Governance Policies & Standards Corporate (meta)data catalogue Audit & Assurance Technology & Comms Mgmt Collection & Management of Historical Data Corporate Reference Information Business Rules Call/Contact Centre Reference Data Security Business Continuity Service Integration Disaster Recovery Resilience Enterprise Service Bus Access Control Single Sign-On ID Mgmt Network Security Information Management Capabilities – (Filtered View) Traffic Monitoring CCTV Emergency Services Media (VASPs) Traffic Officers General Public (Informed Travellers) Operational Partners (Traffic Mgt Act) Office Systems Voice/Email/Fax Communications Signs& Signals X DfT (Sec of State) Major Projects Operational Partners (e.g. Maint Orgns) Service Providers (Incident Support Units)
  • THE PROBLEM The Agency (& its partners) analyses the As-Is from a project scope perspective at the start of each project. Sometimes we analyse it from an organisational or data perspective. The problem is that analyses, coming as they do from various sources, are inevitably expressed in different styles, languages and levels of detail. This results in a “Tower of Babel” situation.
    • The Solution
    • Mandated Business Architecture - 1 language & agreed levels.
    • Reducing project lifecycle time by eliminating the need for translation, mapping & assimilation
    • Ensuring all players (internal & external) have a standard of modelling & presentation to work to & a consistent language of expression.
    • Helping us achieve better & wider understanding of where we are now, before determining where we want to be (by way of each project) & accordingly the most efficient business solution & requirements.
    • THE RESULT
    • We must map everything back into one language to understand it at an Enterprise level.
    • This causes us to be
      • Reactive
      • Inefficient – strategic benefits & issues may be missed
      • Replicating work - carrying out translations & mappings
      • Working against, rather than with, project teams & partners
    HA As-Is Business Models Word Visio Excel TI2011+ Technology Convergence (IPL) Technology Convergence (Cambridge) Different modelling standards & templates… at different levels & perspectives… Published in different media formats… ppt pdf ) ) Infrastructure Publish Intelligence Delivery Interfaces Operational Intelligence (Time Critical) Operational Capabilities Integration Collect Data Network Description & Referencing Manage Facilities General Public Operational Partners Traffic Monitoring Communications Capability Non-Functional Requirements Service Providers (ISUs) CCTV & Roadside Data Storage DfT (Sec of State) Emergency Services Media (VASPs) Traffic Officers HR Finance HA To-Be Business Capabilities Map – Level 1 General Public (Informed Travellers) Operational Partners (Traffic Mgt Act) Roadside Communications Traffic Profiles (Road Timetable) National State of the Network Performance Monitoring Infrastructure Management Resource Management Office Systems Data & Information Management Scheduled Roadworks Planned Events Unplanned Events Traffic Condition Information Weather Information Abnormal Loads Information Situational Awareness Asset Management Operations Traffic Officers Management Vehicle Management Information input & validation Security Inter-system data exchange Phone/ Email/ Fax Communications Traffic Management Audit, Logging, etc Reviewing (Evaluation of Response) Modelling (What-if evaluations) Performance Analysis (PSA Targets) Policies & Standards Governance Planning (Development of Response) Corporate Metadata Registry Business Intelligence (non-time critical) Information Dissemination T.R.U.E. Information Web Signs& Signals X Phone Radio TV Inter-system data exchange Call/Contact Centre Procurement Incident Management Traffic Data/ Information Collection & Data Fusion Geo- Graphical presentatn (Other) Infrastructure Management Operations Traffic Management Operations Incident Management Operations Performance Monitoring & Management Performance Management Organise & Manage Business Data & Information ) ) ) )
  • D3 - Provide Police or RCC with information D4 - Assistance for LHAs, OHAs, ONOs F3 – Delivery of Statistical Data C1 – Provision of VMS F1 – Provision of Travel Time via VMS C2 – Provision to Traffic England (IVR + Web) C3 – Provision of info indirectly to public via media organisations F2 – Provision to Atlas (operational partners) “ FINDING OUT” “ LEARNING” “ DOING” “ PROVIDING” “ ACQUIRING” “ OPERATING” “ ASSIMILATING” NTCC As-Is Business Activity Map D2 - Network performance reports + desktop service Speed, Flow, Journey Time CCTV, RCC data This model is based upon the existing service contract for the NTCC. It should be used as a starting point for breaking out Services and capabilities for 2011+, as well as determining overlaps & gaps with NTCC, RIU & NIU capabilities when modelling the To-Be Business Architecture Weather Info A2 – Scheduled Roadworks A3 – Planned Events A4 – Unplanned Events A5 – Traffic Condition Information A6 – Weather Information B1 – Offline devt of response B3 – Offline evaluation of response A1 – Network Description & Referencing E1 – Operate the Control Centre(s) E2 – Tours & Presentations E3 – Administration of TIH Police, RCCs General Public Operational Partners DfT, Agencies, etc “ SoS” Technology capturing atomic data (e.g. Telemetry) LHAs, OHAs, ONOs, etc D1 - Provide SoS with Planning, Roadworks & special order Abnormal Loads Communications Capability Non-Functional Requirements Service Providers Police, RCCs B2 – Online Strategic Selection of response
  • Coordinate response with Traffic Officers Coordinate response with Police & Partners “ LEARNING” “ PROVIDING” “ ACQUIRING” (Network Status & Incident Detection) “ OPERATING” RCC As-Is Business Activity Map Contractors “ ASSIMILATING” “ DOING” Provide Traffic Info & Traffic Management Coordinate response with Other RCCs “ FINDING OUT” Network Management Services Incident Management Services “ COORDINATION” This model is based upon a high level RCC analysis for The Technology Convergence Project. Weather Info Network Description & Referencing (Gazetteer/ Location) Operate the Control Centres General Public Operational Partners Roadside Equipment Data Gathering Communications Capability Non-Functional Requirements Automatic Traffic Management Emergency Services Other RCCs Scheduled Roadworks Planned Events Unplanned Events Traffic Condition Information Security Surveillance) Management of Incidents on the Network Management of Demand Management of Capacity Management of Resources Weather Information Planning (e.g. gaining & using intelligence) CCTV & Roadside Data Storage NTCC Emergency Services HA Vehicle Info logging Reviewing (e.g. Audit, Logging, etc) General Public Emergency Message Signs Signal Indicators X Traffic Officers
  • “ DOING” “ PROVIDING” “ ACQUIRING” “ ASSIMILATING” 2011+ Analysis - Traffic Information As-Is Business Function Map “ Reviewing” Static Planning External Entities Network Asset Management NILO ATLAS Email System Level Feed Telephone Exception Event Monitoring Police, Partners General Public DfT, Agencies, etc LHAs, OHAs, ONOs, etc Service Providers HA Business Managers Post Analysis NTCC Network Description RCC Network Description SRW Met Office AIL Team Other traffic-generating planned events (HAPMS) Incidents from External Parties LHAs DBFOs HA (other departments) Journey Times via VMS Incident protection & Clearance Localised management Re-Routeing/ Diversion Roadside Information (VMS) Core On Road Response Functions Incident Detection Incident Confirmation (Obtain basic Information) Confirm Full Details Analyse Incident Effects Event Data Interchange Real-Time Traffic Monitoring (Loops & ANPRs) CCTV Major Event/ response review Performance Monitoring & review System/ service Improvements Collate Information for statistical purposes Network Performance Analysis Traffic Monitoring Web IVR HAIL HA Traffic Radio Indirect (Radio,TV) Core Traffic Information Functions Statistics
  • THE PROBLEM When a project analyses & architects a business solution, the detail is documented in the project documentation, including the business case. The problem is that the detail is not documented at an Enterprise level – and therefore, no central, single source of definitive information exists about how, when and where solutions are applied & business capabilities are enhanced. .
    • The Solution
    • Model detail/content is maintained in a structured, referenceable form
    • Allowing descriptions, definitions, characteristics etc to be captured
    • Allowing links (or gaps in linkage) to be maintained through the architecture and to the business plan.
    • Allowing project impact on detail areas to be captured & maintained.
    • A baseline for further analysis & exploitation using specialised tools when available (later in 2008).
    • THE RESULT
    • Difficulties in relating the impact of projects upon the ever-changing business landscape, resulting in:
      • Lack of knowledge of capabilities (& state of capabilities)
      • Lack of knowledge of impact & implications following projects
    Business Architecture Content Detailed Content Analysis As Reqd Access the Business Architecture Repository Spreadsheet Here ) Infrastructure Publish Intelligence Delivery Interfaces Operational Intelligence (Time Critical) Operational Capabilities Integration Collect Data Network Description & Referencing Manage Facilities General Public Operational Partners Traffic Monitoring Communications Capability Non-Functional Requirements Service Providers (ISUs) CCTV & Roadside Data Storage DfT (Sec of State) Emergency Services Media (VASPs) Traffic Officers HR Finance HA To-Be Business Capabilities Map – Level 1 General Public (Informed Travellers) Operational Partners (Traffic Mgt Act) Roadside Communications Traffic Profiles (Road Timetable) National State of the Network Performance Monitoring Infrastructure Management Resource Management Office Systems Data & Information Management Scheduled Roadworks Planned Events Unplanned Events Traffic Condition Information Weather Information Abnormal Loads Information Situational Awareness Asset Management Operations Traffic Officers Management Vehicle Management Information input & validation Security Inter-system data exchange Phone/ Email/ Fax Communications Traffic Management Audit, Logging, etc Reviewing (Evaluation of Response) Modelling (What-if evaluations) Performance Analysis (PSA Targets) Policies & Standards Governance Planning (Development of Response) Corporate Metadata Registry Business Intelligence (non-time critical) Information Dissemination T.R.U.E. Information Web Signs& Signals X Phone Radio TV Inter-system data exchange Call/Contact Centre Procurement Incident Management Traffic Data/ Information Collection & Data Fusion Geo- Graphical presentatn (Other) Infrastructure Management Operations Traffic Management Operations Incident Management Operations Performance Monitoring & Management Performance Management Organise & Manage Business Data & Information ) ) )
  • Business Capabilities Timeline Business Capabilities Timeline will soon be accessible Here Now Project A Project B Project D Project C Programmes/ projects Capabilities Nichols statements of capability Information Strategy Transformation Strategy PSA Targets x x Positioning (Example of concept) The idea is to map the capabilities out that we identified and modelled in the Business Architecture, so that we can plan what capabilities are required (and when). In this way, we can manage (and initiate) projects which are planned from the outset to deliver the desired capabilities, in the right order, incrementally, over a set time period. At present, we are working the wrong way around – projects dictate when they deliver certain capabilities or functions, and we have to adjust the business transformation to meet with what projects deliver. The Business Capabilities Timeline will initially be maintained as a worksheet in the Business Architecture Excel spreadsheet. 2008 F M A M J J S A O N D J 2009 F M A M J J S A O N D J 2010 F M A M J J S A O N D J 2011 F M A M J J S A O N D J 2012 F M A M J J S A O N D J
  • Capabilities & POTIs…
    • Capability = “The practical ability to realise business benefit by a combination of P rocesses, O rganisation, T echnology & I nformation. Capabilities must be measurable over time and are delivered by one or more programmes/projects”.
    Blueprint POTI = P rocesses, O rganisation, T echnology, I nformation = MSP “Blueprint” Capability Processes Organisation Technology Information Processes Processes Information Information Technology Technology Tranche 1 Tranche 2 Tranche 3 Tranche 4 Tranche 5 2009 2010 2011 2012 2013 2015 Business Defines… Programmes Deliver…
  • Capabilities 2008 2009 2010 2012 Nichols statements of capability Estimating & Cost Capture for major projects 1 ver of truth for prog & project reporting for major projects Enhanced decision-making, risk mgmt, for major projects PSA Targets Integrated NW Perf for PSA report against PSA congestion/ safety targets for 08/09 Enhanced reporting against PSA targets for congestion and safety 2011 BI Strategy TI2011+ Network Performance Major Projects Programmes/ projects Tech Convergence Finance Strategic Positioning (Common Services) HA Network Definition Metadata Registry National State of the Network Tranche 1 Performance Management National State of the Network Tranche n National State of the Network Tranche 2 (eg SRW) Traffic Management Infrastructure Management BI Infrastructure supporting strategic devt New NW Performance Infrastructure Incident Management Information Management Integrated Asset Management Tranche n TI2011+ vision IAMS Tranche 1 IAMS Tranche 2 (integrated) Traffic Operations Mangaement (integrated) Incident Management
  • Programmes/ projects Capabilities 2008 2009 2010 2012 Nichols statements of capability Estimating & Cost Capture for major projects 1 ver of truth for prog & project reporting for major projects Enhanced decision-making, risk mgmt, for major projects PSA Targets Integrated NW Perf for PSA report against PSA congestion/ safety targets for 08/09 Enhanced reporting against PSA targets for congestion and safety 2011 Project D Project C Project E Finance Strategic Positioning (Common Services) HA Network Definition Metadata Registry National State of the Network Tranche 1 Performance Management National State of the Network Tranche n National State of the Network Tranche 2 (eg SRW) Traffic Management Infrastructure Management BI Infrastructure supporting strategic devt New NW Performance Infrastructure Incident Management Information Management Integrated Asset Management Tranche n TI2011+ vision IAMS Tranche 1 IAMS Tranche 2 (integrated) Traffic Operations Mangaement (integrated) Incident Management Common Services programme Programme B
  • We can model capabilities (in terms of how they relate to each other or are categorised)… AND … We can represent capabilities (in terms of interdependencies and delivery) on the timeline Business Infrastructure Collaboration & Operational Intelligence Operational Capabilities HA Network Definition HA To-Be Business Capabilities – High Level (0) View Security Data Integration National State of the Network Performance Monitoring & Management Operational Management T.R.U.E. Information Dissemination ( T rusted, R eliable, U seful, E ffective) Governance Business Intelligence Information Input & Validation Collect Data (Acquisition of Traffic & Travel Information from External Partners & Public) Publish Intelligence (Dissemination of Traffic & Travel Information to External Partners & Public) Corporate Intelligence “ One version of the truth” Business management & Supporting Services Coordination with External Organisations Infrastructure & People Management Traffic Management Incident Management 2008 2009 2010 Nichols statements of capability Estimating & Cost Capture for major projects 1 ver of truth for prog & project reporting for major projects Enhanced decision-making, risk mgmt, for major projects PSA Targets Integrated NW Perf for PSA report against PSA congestion/ safety targets for 08/09 Enhanced reporting against PSA targets for congestion and safety 2011 Finance Strategic Positioning (Common Services) HA Network Definition Metadata Registry National State of the Network Tranche 1 Performance Management National State of the Network Tranche n National State of the Network Tranche 2 (eg SRW) Traffic Management Infrastructure Management BI Infrastructure supporting strategic devt New NW Performance Infrastructure Incident Management Information Management Integrated Asset Management Tranche n TI2011+ vision IAMS Tranche 1 IAMS Tranche 2 (integrated) Traffic Operations Mangaement (integrated) Incident Management