Multi-instance Topologies
Summarize
Summary of Multi-instance Topologies
The Multi-instance Topologies Accelerator is designed for Impact customers to gain foundational knowledge about the business drivers that justify using multiple production instances within a single-customer ServiceNow implementation. It introduces four different multi-instance topology alternatives, explaining each with descriptions, use cases, strengths and weaknesses, and example process flows. The Accelerator includes interactive sessions to help customers evaluate their multi-instance requirements and collaborate with their implementation provider on architecture design.
Show less
This Accelerator is available in the Advanced and Total packages.
Key Features
- Introductory Customer Session (up to 60 minutes): Introduces the Accelerator, sets expectations, explains business drivers for multiple production instances, presents four topology options, and requests customer inputs such as use cases and questionnaires.
- Customer Education Sessions #1 and #2 (up to 120 minutes each): Deliver detailed presentations on business drivers and the four topologies split across two sessions, including interactive activities based on customer-provided use cases, and provide advisory guidance on next steps.
- Follow-up Customer Session (optional, up to 60 minutes): Offers a Q&A opportunity for additional clarification on multi-instance topology education and guidance.
- Deliverables: Workshop slides, multi-instance topology use case activities, guidance for next steps, and requested customer resources.
Customer Responsibilities
Customers must provide key roles to support the process:
- Platform Owner: Accountable for overall platform governance and alignment with business strategy.
- Platform Administrator: Manages day-to-day platform administration.
- ServiceNow Platform Architect: Oversees platform architecture, strategy, and governance.
- Enterprise Architect(s): Ensures alignment with organizational strategy, processes, policies, and standards.
- Service Owner(s) (Recommended): Manages data and process flows for specific services or integrations.
Prerequisites and Requested Information
Completion of the “How to Tackle Architectural Implementation Models” workshop is required before engaging with this Accelerator. Customers are also requested to provide outputs from that workshop to inform the multi-instance topology discussions.
Scope and Exclusions
This Accelerator focuses on education and guidance about multi-instance topologies rather than detailed architecture design, technical implementation, or integration specifics. It does not cover:
- Multi-instance architecture design recommendations
- Technical integration or detailed architecture blueprints
- Enterprise architecture review
- Managed Service Provider or multi-customer multi-instance configurations
- Sub-production instances such as development, test, or UAT environments
Customers seeking these detailed design or implementation services should engage with their Enterprise Architect or ServiceNow implementation provider separately.
This Accelerator provides education on drivers and topology alternatives to support multiple production instance implementations delivered within the context of a single-customer production implementation.
Overview
The Multi-instance Topologies Accelerator provides Impact customers with facilitated education sessions that establish a foundational understanding of the common business drivers that could warrant multiple production instances and an introduction to four multi-instance topology alternatives.
The overview for each topology includes a description, topology-related use cases, strengths and weaknesses, and example process flows. The education sessions are interspersed with interactive use case activities, so that following the completion of the Accelerator, you may continue to evaluate your own multi-instance requirements by engaging your implementation provider to develop an implementation architecture.
What You Get
- Introductory Customer Session (up to 60 minutes)
- Introduce Accelerator and set expectations on process and depth of deliverable
- Communicate expectation for Customer participation
- Introduce business drivers for multiple production instances
- Introduce four multi-instance topologies
- Request completion of intake questionnaire, three use cases, and provide any other requested inputs
- Customer Education Session #1 (up to 120 minutes)
- Present business drivers for multiple production instances, referencing use cases provided by the customer
- Present two multi-instance topologies
- Conduct interactive activities based on relevant customer-provided use cases
- Customer Education Session #2 (up to 120 minutes)
- Present two multi-instance topologies, which may or may not reference the customer’s use cases
- Conduct interactive activities based on relevant customer-provided use cases
- Advisory guidance for next steps
- Follow-up Customer Session (optional upon Customer request - up to 60 minutes)
- Opportunity for Q&A related to the multi-instance topologies education and guidance
- Multi-instance Topologies Deliverables
- Workshop slides
- Multi-instance topology use case activities
- Guidance for next steps
Requested customer resources
| Customer Resource | Responsibilities |
|---|---|
| Platform Owner (Required) | Responsible for the overall accountability of the ServiceNow platform. Provides leadership and oversight to the System Administrators, ensures team alignment to business strategy and the ServiceNow roadmap, and is actively involved in the overarching governance of the platform. |
| Platform Administrator (Required) | Responsible for the day-to-day administration of the ServiceNow platform. |
| ServiceNow Platform Architect (Required) | Responsible for overall ServiceNow platform architecture, strategy, and governance. |
Enterprise Architect(s) (Required) |
Provides a holistic view of the organization’s strategy, processes, and other systems, including any necessary policy or organizational requirements. Helps guide the Platform Owner to align with technical or functional standards. |
| Service Owner(s) (Recommended) | Responsible for data and process flows related to a specific service, process, or an integration. |
Pre-requisite
The completion of the workshop, How to Tackle Architectural Implementation Models, is required. For more information, contact your Enterprise Architect.
Requested Information Access
The output deliverables from the How to Tackle Architectural Implementation Models workshop are requested.
Exceptions
- Multi-instance topology architecture design recommendations
- Multi-instance technical implementation / technical integration detailed architecture
- Enterprise architecture review
- Detailed architecture blueprint for multi-instance configuration
- How to integrate multiple production instances
- Topology considerations for Managed Service Provider and/or multiple customer multi-instance configurations
- Multiple sub-production instances, for example, development, test, or user acceptance test (UAT))