1. HA Enterprise Architecture Common Services in EA Version 1.0

2. A discrete, scoped service:.. which may be a business service or an IS/IT service … used by one or more “service users” (which will usually be other business services/functions or Information Systems). … pan-agency … with clearly defined, maintained & published interface(s) … & clearly defined (centralised) management & sponsorship. What is a “Common Service”? Common Service Service User

3. More about “Common Services” Common Services must be catalogued & referenced through a service catalogue, enabling projects & system owners to see what services are offered/planned/undergoing change. Where only one current service user is defined, this may be because in the future, the service will be used by more service users. Alternatively, it may be scoped & managed as a discrete service because it carries out discrete functions that make it expedient to keep it logically separated from (say) a parent business service/function or IS/IT service/function (for example, unique technology standards/protocols). Common Service Service User

4. Benefits of Common Services Single, definitive source of information & function. Consistency of functional & non-functional characteristics. Minimises costs - procurement, development, resource, skills. As catalogue of services increases, so projects are rationalised (because they use more common services). Can use the best technology for the job (where it’s an IS/IT service). Maintainable. Rightsized (enabling flexibility & change when required). Is flexible to organisational change. Can be in-house or bought as a service as required. Common Service Service User

5. Example: Business Service Architecture Approach to Spatial Data Pavements Service Spatial Data Service Primary Business Service “Child” Business Services Common Business Services Drainage Service Streetlamps Service Lane Booking Service Used By Spatial data Maintenance Updates/Updated By One standard procedure for locating/describing positions, using standard map visualisation & selection. Ability to represent positions using different (accepted) standards & to describe these positions.

6. …Translated to a Systems-oriented approach (this is the ideal, not current reality!) HAPMS Spatial Data Service e.g. “Son of ENM” Primary Service “Child” Services Common Services DrainageEPSNOMAD Used By Spatial data Maintenance Updates/Updated By One standard IS/IT service for locating/describing positions, using standard map visualisation & selection. Includes/coupled to a service which maintains the spatial data in a timely & consistent manner

7. Systems that could use a common Spatial Data system (current & planned) HAPMS Spatial Data Service e.g. “Son of ENM” Applications using locational referencing Common Service DrainageEPSNOMAD One standard procedure for locating/describing positions, using standard map visualisation & selection. Ability to represent positions using different (accepted) standards & to describe these positions. SMISGeotechIAMS NTCC (systems) RCC (Systems) ExxorHATRISBI Strategy Value Management Prioritisation Lane Booking C&CTraffic Data

8. Infrastructure Collaborative & Common Services Core Processing Capabilities Corporate Information Delivery Interfaces Customer Delivery ChannelsSuppliers / Partners / OGDs Integration Typical Common IS/IT Services - Mapped onto the EA Reference model Input Services Output Services Enterprise Application Integration Single Sign-On Directories Reference Data Workflow Spatial positioning e.g. data hubs Business Intelligence & Reporting Business Rules