Multi-instance Topologies
Summarize
Summary of Multi-instance Topologies
The Multi-instance Topologies Accelerator offers education for Impact customers on the business drivers and alternatives for implementing multiple production instances. It includes insights into four multi-instance topology options, detailing their use cases, strengths, weaknesses, and example process flows. The program features interactive sessions to help customers assess their own requirements in collaboration with their implementation providers.
Show less
Key Features
- Introductory Customer Session: An initial session to introduce the Accelerator, set expectations, and present business drivers for multiple instances.
- Customer Education Sessions: Two detailed sessions that cover multi-instance topologies, incorporating the customer's use cases and facilitating interactive activities.
- Follow-up Session: An optional Q&A opportunity for additional guidance on multi-instance topologies.
- Deliverables: Includes workshop slides, use case activities, and guidance for next steps.
Key Outcomes
Customers will gain a foundational understanding of multi-instance topologies, enabling them to evaluate their specific needs effectively. They will engage in facilitated discussions to inform their implementation architecture and ensure alignment with business strategy. The Accelerator also outlines necessary roles and responsibilities for successful implementation, including those of the Platform Owner, Administrator, and Architect.
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))