Concurrent floating-license peak measurement

What is being tested

Was a concurrent license fee based on the correct peak rather than the sum of daily users? The boundary for this investigation is concurrent floating-license peak measurement. Begin with the disputed transaction or population, then identify which license-server checkout log establishes the observed position and which concurrency definition supports the comparison. A difference in totals should not replace this question.

Evidence: license-server checkout log

For concurrent floating-license peak measurement, license-server checkout log must be linked to concurrency definition. Document the observation window, units, inclusion criteria and export version. Identify gaps and corrected events before using the total. Keep raw observations separate from derived quantities so a reviewer can reproduce the population without assuming every logged event is independently chargeable.

Evidence: concurrency definition

For concurrent floating-license peak measurement, concurrency definition must be linked to measurement window. Retain the applicable wording, effective dates and scope of covered transactions. Identify the event or population that controls the calculation. Do not silently replace a contractual definition with a dashboard label, customary practice or the latest published rule.

Evidence: measurement window

For concurrent floating-license peak measurement, measurement window must be linked to license invoice. Preserve the transaction identity, measured or accepted quantity and who confirmed the event. Distinguish physical evidence from later system posting. Where condition affects acceptance, retain the authorized disposition instead of using a raw observation as an automatic commercial conclusion.

Evidence: license invoice

For concurrent floating-license peak measurement, license invoice must be linked to license-server checkout log. Keep the issued document version and line-level quantity, currency and service period. A header total cannot establish which component is being tested. Retain later corrections as linked versions, so a replacement does not create a second liability.

Reconciliation logic

Reconstruct overlapping checkout intervals and compare the peak during the contractual window with the billed concurrency tier. Build the comparison at the level identified by license-server checkout log and retain the governing version from concurrency definition. Show intermediate classifications and excluded items separately; a net total can hide an unsupported component or a correctly offset correction.

Exception conditions

Many named users can share a smaller simultaneous pool. Treat the item as an unresolved exception only when the comparison described here cannot be supported by the linked license-server checkout log, concurrency definition, measurement window, license invoice. Document the conflicting input or rule. A plausible operational explanation requires validation, but it should not be discarded to maximize an apparent financial difference.

Human review and outcome

The application owner confirms held sessions and disconnected checkouts. Retain a concurrency trace and request explanation of an unsupported peak. Keep the reviewer's reason and source references with that disposition. A supported correction should be followed to the revised record or settlement; an accepted explanation can close the question with no adjustment. Missing authority or evidence should remain an open task rather than a confirmed recovery.

Limitations and processing boundary

Do not infer license removability from activity alone or describe a proposed configuration change as confirmed savings. The authoritative spend, license and contract producer is not complete; customer evidence and processing validation are prerequisites to production conclusions. In this scenario, absence of license-server checkout log or concurrency definition limits whether the comparison can be completed. The review method describes what people should validate, not a promise that AuditRes automatically detects or executes this specific outcome.

AuditRes pathway

Discuss concurrent floating-license peak measurement in the Technology Spend workspace. Review current plans, the shared platform and secure evidence requirements; use the existing contact path to confirm the sources and validation this scope requires.

AuditRes Technology Spend: Available for onboarding. Public previews use synthetic demonstration data; production processing remains gated until applicable customer sources and authoritative processors are connected and validated.

Neighboring financial questions

Technology Spend resource hub · All guides in this evidence collection