Calculation of Allotment Usage

The following topics describe how usage is calculated for each allotment.

Web Services Operations Allotment

The Web service operation count is incremented whenever a Web service request is received and executed. A single Web service SOAP request, when processed, might result in one or more Web service operations being executed. For example, The following table shows the number of operations resulting for different types of request.

Table Examples of Number of Operations for Different Web Services Requests

Type of Request	Number of Operations
Nonquery operations
Account insert request containing a single Account record (with no child operations)	1
Contact update request containing 10 Contact records (with no child operations)	10
Account update request containing a single Account record with 3 Account Team records	4
Query operations
Simple query for a set of Accounts	1
Query for a set of Accounts and the associated Contacts for each Account	1 + n, where: 1 operation to retrieve the set of n Accounts matching the specified filter criteria n operations to retrieve the set of Contacts associated with each Account (1 operation for each Account)

Web Services Concurrent Request Allotment

The Web Services Concurrent Request allotment is a measure of the number of Web service requests (including both stateful and stateless requests) being processed by a company concurrently.