Impact Store Application storage estimation
Summarize
Summary of Impact Store Application storage estimation
The Impact Store application stores collaboration and outcome tracking data within your ServiceNow instance, contributing to your overall storage footprint. Storage usage varies based on whether your instance is connected to the Impact Delivery Instance and the level of usage and collaboration activity.
Show less
Storage Behavior Based on Connection
- Not connected to Impact Delivery Instance: Data is generated only within your local instance. Storage consumption scales with feature usage such as health scans and generated reports, similar to other ServiceNow applications.
- Connected to Impact Delivery Instance: Data is initially migrated and periodically synchronized between your instance and ServiceNow experts (squads). This introduces additional data such as jointly defined outcomes, Product Adoption Roadmaps (PARs), Accelerator requests and updates, conversations, attachments, and supporting artifacts, leading to increased storage usage correlated with collaboration activity.
Key Factors Driving Storage Growth
Storage consumption in Impact primarily depends on:
- Number of outcomes tracked
- Number of Product Adoption Roadmaps (PARs)
- Volume and frequency of Accelerator requests and updates
- Frequency of conversations and collaboration records
- Use and size of attachments and supporting documents (major contributor to growth)
- Duration of data retention, influenced by cleanup and archiving policies
Estimated Storage Usage by Adoption Level
Storage footprint varies with usage intensity:
- Small (light usage): Limited outcomes (5–10), few PARs, minimal Accelerator activity, low collaboration, and few or no attachments.
- Medium (moderate usage): Moderate outcomes (10–20), multiple PARs, regular Accelerator activity, moderate attachments, ongoing collaboration.
- Large (high usage / mature adoption): High number of outcomes (25+), extensive PARs, frequent Accelerator usage, significant attachments including large files, and continuous collaboration with ServiceNow squads.
Key Considerations for ServiceNow Customers
Impact data storage directly affects your instance’s database usage and grows with feature use and collaboration volume. Customers should anticipate increased storage consumption as they engage more deeply with Impact capabilities and plan accordingly for capacity and data management strategies.
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 |
|---|---|
| Small (light usage) |
|
| Medium (moderate usage) |
|
| Large (high usage / mature adoption) |
|
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.