Building Digital Reliability with Centric's Service Reliability Management
Shaping a future of predictable, reliable public services through strategic implementation of Service Reliability Management.
Understanding APM, SRM, and ITOM
To navigate our digital reliability journey effectively, it's essential to understand the relationship between three key components that form the foundation of our approach.
APM - The Project
Application Performance Management (APM) is the name of our project focused on implementing comprehensive service reliability across government digital services. This initiative drives the strategic transformation of how we monitor, manage, and optimize our digital infrastructure.
SRM - The Framework
Service Reliability Management (SRM) serves as the overarching framework and wrapper that structures our approach to reliability. It provides the methodological foundation, processes, and governance model that guides our implementation strategy.
ITOM - The Technology
IT Operations Management (ITOM) represents the family of products within ServiceNow that we leverage to execute our SRM framework. These tools provide the technical capabilities for monitoring, discovery, event management, and automation.
Together, these three elements create a comprehensive approach: the APM project implements the SRM framework using ITOM technologies to deliver reliable digital government services.
The Vision: Why SRM Matters
As a digital guiding partner for the Public Sector in the Netherlands, Centric understands that building and selling products is not enough. Reliability must be part of the package we offer, ensuring consistent service delivery that citizens can depend on.
Citizen-Focused Services
Reliable public services form the foundation of citizen trust. When digital government works seamlessly, it strengthens the relationship between citizens and institutions and the partnership between institutions and Centric.
Proactive Reliability
SRM shifts operations from reactive firefighting to proactive reliability engineering, preventing issues before they impact service delivery.
Transparent Ownership
Clear accountability and continual improvement pathways ensure services evolve to meet changing citizen needs while maintaining reliability.
Building Reliability Like a House
SRM Escalations & Workflows
Ensuring service stability through automated responses
Protected Visibility Layer
Contextualizing monitoring data for both technical and business perspectives
ITOM Health Monitoring
Centralizing all health data in one unified view
Service Mapping & CSDM Alignment
Creating standardized operational service views
CMDB & Discovery Readiness
The essential foundation for reliable service delivery
Foundation: CMDB Readiness
Accurate Infrastructure Inventory
Comprehensive documentation of all physical and virtual assets, providing the foundation for service mapping and reliability management.
Clear CI Ownership
Defined responsibility for all configuration items ensures accountability and speeds resolution when issues arise.
Operational Stability
A well-maintained CMDB acts as the single source of truth, enabling consistent service delivery and informed decision-making.
Ground Floor: Discovery & Service Mapping
Discovery
Automated identification of running assets creates visibility across the environment
Service Mapping
Visualization of dependencies and relationships that impact service delivery
CSDM Alignment
Integration of business context ensures technical issues are understood in terms of citizen impact
First Floor: ITOM Health & Monitoring
ACC Agents
Agent Client Collectors deployed on Linux and Windows backend servers gather detailed performance metrics directly from the infrastructure.
Health Log Analytics
Proactive detection through pattern recognition and anomaly identification enables issues to be addressed before they impact users.
Application Insights
Deep visibility into application performance connects infrastructure health to actual service experience for citizens.
AIOps
Artificial intelligence for IT operations provides intelligent automation and predictive analytics for truly proactive monitoring and incident prevention.
OpenTelemetry*
*Optional: End-to-end distributed tracing across complex systems ensures complete visibility into service interactions and dependencies.
Attic Level: Protection Layer
Operational Resilience
Even before SRM is fully implemented, the ITOM Health components provide critical protection against service disruptions. This layer acts as a protective shield, enabling teams to identify and address potential issues.
- Anomaly detection alerts
- Availability scoring
- Risk identification
Teams can already start consuming alerts via ExpressList, and basic notifications can be used to engage teams as protection measures are being established.
Reserved Capacity
Like an attic provides additional space in a home, this layer represents reserved capacity for escalation workflows and backup systems. It ensures services remain protected even when formal response pathways aren't fully established.
- Failover systems
- Redundant monitoring
- Incident prediction
Roof: SRM Workflows & ChatOps
Escalation Paths
Structured notification flows and on-call scheduling ensure the right people respond at the right time
Automated Workflows
Pre-defined response patterns trigger when reliability thresholds are breached
ChatOps Integration
Collaborative response platforms for immediate team communication during incidents
SLO Monitoring
Continuous tracking of service level objectives with automatic alerts on deviations
Value Realization for Digital Government
These metrics are derived from organizations that have successfully implemented SRM practices, based on industry benchmarks and Centric's implementation data. While our platform provides the tools and infrastructure to achieve these outcomes, success ultimately depends on team adoption and commitment to reliability practices.
99.9%
Service Uptime
Increased reliability through proactive monitoring and rapid response protocols
68%
Faster Recovery
Reduction in mean time to resolve incidents through automation and clear ownership
100%
Real-time Visibility
Complete transparency into service health and potential risks
24/7
Continuous Protection
Around-the-clock monitoring and automated response capabilities
Achieving these results requires consistent implementation of SRM practices, proper configuration of monitoring tools, and development of response playbooks. While Centric provides the technology foundation, teams are ultimately responsible for making the most of these capabilities through cultural adoption, continuous improvement, and ownership of their service reliability goals.
SRM Onboarding: Prerequisites & Setup (Epic 1)
The first stage of your SRM implementation journey focuses on establishing the organizational foundation necessary for successful adoption and long-term reliability management.
Define Governance Structure
Establish clear lines of authority and decision-making processes to support the SRM implementation. This includes defining escalation paths and approval workflows.
Create SRM Teams and Roles
Formalize team structures with specific responsibilities assigned before technical work begins. This ensures everyone understands their part in maintaining service reliability.
Validate Access Controls
Implement role-based access ensuring everyone has "just enough" permissions to fulfill their responsibilities while maintaining security by design.
Completing this foundational epic prepares your organization for the technical implementation phases that follow in the SRM onboarding journey.
CMDB & Discovery Readiness
Epic 2 in the SRM onboarding journey focuses on establishing a reliable foundation of configuration data to support your service reliability initiatives.
Baseline Assessment
Evaluate current CMDB state and identify gaps requiring attention before proceeding with SRM implementation.
2
CMDB Structure Definition
Organize configuration items into logical groupings aligned with business services and technical components.
Discovery Execution
Run comprehensive discovery scans to identify all infrastructure components and services within the environment.
Validation & Remediation
Verify discovered items against expected inventory and resolve any discrepancies or missing elements.
Service Mapping & CSDM Alignment
Business Service Layer
Define citizen-facing services and their requirements
Application Service Layer
Map software components supporting business functions
Technology Service Layer
Connect infrastructure elements to applications
ITOM Health & Monitoring Integration
Comprehensive monitoring infrastructure collects and correlates data from multiple sources to provide a unified view of service health, enabling proactive management and rapid response to potential issues.
Incident, Event & Alert Management
SLO Management & Error Budgets
Service Level Objectives (SLOs) define measurable reliability targets, while error budgets provide a framework for balancing innovation against stability. When SLOs are consistently met, teams can use remaining error budget for planned changes and feature deployments.
Post-Onboarding Validation & Improvement
Feedback Collection Process
Regular structured sessions with service teams to gather insights on SRM effectiveness. Includes surveys, facilitated workshops, and one-on-one interviews with key stakeholders to identify pain points and opportunities.
Metrics Refinement Strategy
Quarterly review of SLIs and SLOs to ensure they accurately reflect service performance and citizen expectations. Includes analysis of false positives/negatives and alignment with business outcomes.
Playbook Optimization
Post-incident reviews to evaluate response effectiveness and identify improvement opportunities. Playbooks are updated based on lessons learned and changing service requirements.
Team Training Program
Comprehensive education ensuring all team members can effectively navigate and leverage SRM capabilities. Includes hands-on workshops, documentation, and role-specific training modules.
Building a Reliability Culture
Celebrating Success
Recognizing teams that consistently meet or exceed reliability targets helps reinforce positive behaviors and builds momentum for continuous improvement efforts.
Blameless Post-Mortems
Creating a safe environment where teams can openly discuss incidents without fear of punishment encourages transparency and accelerates learning.
Cross-Team Collaboration
Breaking down silos between development and operations teams creates shared ownership for reliability and enables more effective problem-solving.
Moving into a Reliable Future
Resilient Services
SRM ensures Centric delivers consistently available, high-performance digital government services that citizens can depend on.
Measurable Reliability
Clear metrics and transparent reporting create accountability and drive continuous improvement in service delivery.
Empowered Teams
With the right tools and processes, teams shift from reactive troubleshooting to proactive reliability engineering.
Trusted Partnerships
Reliable services build trust between citizens, government agencies, and technology providers, creating a foundation for digital transformation.