Operating model for the Splunk CoE
An operating model is a set of standard operating procedures and protocols. A successful Splunk implementation requires project management and organizational oversight and a well-defined operating model to help ensure consistent outcomes.
Benefits of an operating model
- Put resources in place for future growth
- With an operating model in place, you can do the kind of planning that will enable you to scale. You can anticipate staffing needs, codify procedures, and organize your resources in a way that provides room for future growth
Post the service catalog
The service catalog is a record of your current service offerings and processes. After completing the baseline event, your CSM will send your service catalog to you. Once you receive your service catalog, post it in a publicly accessible space (such as your team wiki, community, or internal web site).
To learn more about the baseline event, see Execute the baseline event for the Splunk Center of Excellence.
Identify the program manager
It is important to put a Program Manager in place with clear authority to manage operations for the entire CoE. The program manager plays one of the most crucial roles on your team.
This is a summary of the program manager's responsibilities:
- Drives decision-making
- Manages inter-dependencies between CoE Service Areas
- Ensures the CoE is built out in alignment with business objectives
- Oversees CoE metrics
- Is accountable for return on investment
- Promotes and facilitates program-wide communication
- Supports initiatives for knowledge sharing and collaboration
- Ensures executive alignment
For more information, see Roles and responsibilities for the Splunk CoE.
Complete service level definitions
Service level definitions include service level objectives (SLOs), service level agreements (SLAs), and case priorities.
Metrics for the Splunk CoE
Service areas and activities for the Splunk CoE
This documentation applies to the following versions of Splunk® Center of Excellence: current