What Services should be offered by an Enterprise Architecture Practice?

All depends, as usual.

1 Core EA practice

Let us consider that core EA practice is as defined in http://improving-bpm-systems.blogspot.ch/2015/12/enterprise-patterns-adagio-entarch.html

Its possible services are the following.

1.1 Architecture Governance Services

These services allow to define, execute, supervise, and review strategies, policies and procedures for

• business 
• applications 
• information 
• infrastructure 
• security

1.2 Architecture Delivery Services

The purpose of these services is to deliver architecture in accordance with its lifecycle and some specific of an enterprise. For example, a target architecture of an enterprise has three major parts:

1. Corporate Unified Business Execution (CUBE) platform see http://improving-bpm-systems.blogspot.ch/search/label/%23platform
2. Platform-based solutions see http://improving-bpm-systems.blogspot.ch/search/label/PEAS
3. Stand-alone applications

Then each of "smaller" services must address each of those parts.

1. Architecture Design Service
   • Platform
   • Platform-based solutions
   • Stand-alone solutions
2. Architecture Support Service
   • Platform
   • Platform-based solutions
   • Stand-alone solutions
3. Architecture Operations Service
   • Platform
   • Platform-based solutions
   • Stand-alone solutions
4. Architecture Evolution Service
   • Platform
   • Platform-based solutions
   • Stand-alone solutions

1.3 Innovations and optimisation services

Possible services:

• Training
• Knowledge dissemination
• Prototyping
• Experimentations
• Technology watch

2 Supporting EA practice to enable other functions

Possible services:

• EA services in the PMO processes
• EA services in procurement processes
• EA services in strategic planning processes

3 Reminder - check that set of service is complete

Know all your artefacts (i.e. those are under your responsibilities or those about which you are consulted ) and build services around these artefacts.

For each of artefact:

• Policy
  • RASCI
  • lifecycle = states+events+procedures
  • security
• Procedures (design, build, support, operations, maintenance) - depending of RASCI
• Catalogue
• Relationships to other artefacts

Thanks,

AS