Impact storage estimation
Summarize
Summary of Impact storage estimation
The Impact store application in ServiceNow retains data inside your instance, influencing your overall storage consumption. Storage demands vary based on whether your instance is connected to the Impact Delivery Instance and the extent of collaboration activities with ServiceNow experts (squads).
Show less
Storage Behavior Based on Connection
Not connected to Impact Delivery Instance: Data is generated solely within your instance, such as health scan reports. Storage usage scales proportionally with feature usage, similar to other ServiceNow applications.
Connected to Impact Delivery Instance: Data is migrated and periodically synchronized to support collaboration. Additional data stored includes:
- Jointly defined and tracked outcomes
- Product Adoption Roadmaps (PARs)
- Accelerator requests and execution updates
- Conversations and collaboration records
- Attachments and supporting artifacts shared by squads
This collaboration leads to incremental storage growth tied to activity levels.
Factors Driving Storage Growth
- Number of outcomes tracked
- Number of Product Adoption Roadmaps
- Volume and frequency of Accelerator requests and updates
- Frequency of conversations and collaboration
- Use and size of attachments and supporting documents (major contributor)
- Data retention duration influenced by cleanup and archiving policies
Estimated Storage Ranges
Storage usage varies with adoption and activity level:
- Small (light usage): Limited outcomes and PARs, minimal Accelerator activity, low collaboration, typically less than 0.5 GB.
- Medium (moderate usage): Moderate outcomes and PARs, regular Accelerator interactions, moderate attachments, ongoing collaboration, 0.5 GB to 10 GB.
- Large (high usage/mature adoption): High number of outcomes and PARs, frequent Accelerator use, significant attachments (large files like PPTs and images), continuous collaboration, exceeding 10 GB.
Key Considerations for ServiceNow Customers
Because Impact data resides within your instance, it directly affects your database storage usage. Storage growth correlates with your organization’s engagement level with Impact features and collaboration intensity. Planning for storage should consider expected usage tiers and the potential increase due to attachments and ongoing collaborative activities.
The Impact store app stores data within your ServiceNow instance and contributes to your instance's overall storage footprint. Storage usage varies depending on whether your instance is connected to the Impact Delivery Instance and on the level of collaboration activity.
Why Impact storage may differ from other applications
Unlike most applications that generate data only within your instance, Impact enables ongoing collaboration between your organization and ServiceNow experts (squads). When connected to the Impact Delivery Instance, this collaboration migrates and synchronizes additional data into your instance, increasing its storage footprint beyond what is generated locally.
How storage usage changes based on connection
Storage behavior differs depending on whether your instance is connected to the Impact Delivery Instance.
- Not connected to the Impact Delivery Instance
-
Data is generated only within your instance. For example, running health scans produces reports and findings that consume storage. The storage footprint scales proportionally with feature usage, where more health scans or more generated records result in more storage consumption, similar to other ServiceNow applications.
- Connected to the Impact Delivery Instance
-
Data is initially migrated and then periodically synchronized, enabling collaboration between your organization and your Impact squads. Additional data is introduced into your instance, including:
- Outcomes defined and tracked jointly
- Product Adoption Roadmaps (PARs) created by the Squad
- Accelerator requests and execution updates
- Conversations and collaboration records
- Attachments and supporting artifacts shared by the Squad
This results in an incremental increase in storage usage based on the level of collaboration and activity.
What drives storage growth
Storage usage in Impact is primarily driven by the following factors:
- Number of outcomes being tracked
- Number of Product Adoption Roadmaps (PARs)
- Volume of Accelerator requests and updates
- Frequency of conversations and collaboration
- Use and size of attachments and supporting documents, which typically contribute the most to storage growth
- Duration of data retention, effected by cleanup and archiving rules
Illustrative storage footprint ranges
The following ranges are indicative examples to help estimate potential storage usage based on typical usage patterns. Actual values may vary based on implementation and usage.
| Usage tier | Typical characteristics | Estimated storage impact |
|---|---|---|
| Small (light usage) |
|
Less than 0.5 GB |
| Medium (moderate usage) |
|
0.5 GB- 10 GB |
| Large (high usage / mature adoption) |
|
10 GB+ |
Key considerations
- Impact data is stored within your instance and contributes to overall database storage usage.
- Storage growth is directly correlated with feature usage and collaboration levels.
- Higher engagement with Impact capabilities may result in increased storage consumption.