When determining the Salesforce resource limits (sizing) needed to run a Salesforce org with Nextian, the following key factors must be considered:
- Object Storage where Salesforce stores accounts, services, orders, tasks, cases and other records.
- File Storage where Salesforce stores file attachments (quote PDFs, order documents, case screenshots, etc.).
- API Calls made by the Nextian Monitoring Integration as it updates elements and services: status, availability and performance metrics.
Additional factors, such as the number of emails sent, users, and third-party software (e.g., DocuSign envelopes), need to be evaluated on a case-by-case basis.
The specific storage and API needs will depend on various aspects, including:
- Number of accounts and services (circuits, virtual servers, software subscriptions, etc.)
- Total and monitored elements per service
- Number of performance metrics
- Number and frequency of change orders during service lifetime
- Whether customer cases are stored in Salesforce or an external customer support system
- Order and case comments volumes
The additional required resources can be estimated using the following table:
| Resource | Estimate |
|---|---|
| Object Storage | 100K-0.5MB per service* |
| File Storage | 1MB-2MB per service* |
| API | 4K API calls per 10,000 monitored elements |
* Object and file storage can be significantly reduced by implementing a retention policy to remove historical orders, inactive services, and closed cases past a certain age.
| Important | The numbers below are approximate and provided as general guidelines. Actual values may vary. Contact us for your detailed Salesforce sizing assessment. |
