HA Enterprise ArchitectureCommon Services in EA
Version 1.0
• 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 Service User
Service User
Service User
Service User
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 Service User
Service User
Service User
Service User
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 Service User
Service User
Service User
Service User
Example: Business Service Architecture Approach to Spatial Data
PavementsService
Spatial DataService
Primary BusinessService
“Child” BusinessServices
Common Business Services
DrainageService
StreetlampsService
Lane BookingService
Used By
Spatial dataMaintenance 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.
…Translated to a Systems-oriented approach (this is the ideal, not current reality!)
HAPMS
Spatial DataService e.g. “Son of ENM”
Primary Service
“Child” Services
Common Services
Drainage EPS NOMAD
Used By
Spatial dataMaintenance 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
Systems that could use a common Spatial Data system(current & planned)
HAPMS
Spatial DataService e.g. “Son of ENM”
Applications using locational referencing
Common Service
Drainage EPS NOMAD
One standard procedure for locating/describing positions, using standard map visualisation & selection. Ability to represent positions using different (accepted) standards & to describe these positions.
SMIS Geotech IAMS NTCC(systems)
RCC(Systems) Exxor HATRIS BI Strategy
ValueManagementPrioritisation
LaneBooking C&C Traffic Data
Infrastructure
Collaborative & Common Services
Core Processing Capabilities
Corporate Information
Delivery Interfaces
Customer Delivery Channels Suppliers / Partners / OGDs
Integration
Typical CommonIS/IT Services
- Mapped onto the EA Reference model
Input Services OutputServices
EnterpriseApplicationIntegration
SingleSign-On
Directories
ReferenceDataWorkflowSpatial
positioning
e.g. data hubs
BusinessIntelligence& Reporting
BusinessRules
Top Related