Description
Measure overlap between two supplied UTC service intervals.
Cross-border business records combine named parties, contract versions, currencies, fees, shipment terms and local-time transcriptions. A supplied rate direction or fee currency determines arithmetic, while an authentic-language or trade-rule label remains a record assertion. Local calculations do not establish actual settlement or governing obligations.
Measure overlap between two supplied UTC service intervals.
When to use this tool
Use International Service Time Overlap when you already have firstStartUtcMinutes, firstEndUtcMinutes, secondStartUtcMinutes, secondEndUtcMinutes and need to measure overlap between two supplied UTC service intervals.
How to use the tool and how it works
- Enter firstStartUtcMinutes, firstEndUtcMinutes, secondStartUtcMinutes, secondEndUtcMinutes. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read overlapMinutes. Use the output convention below.
Require each end>=start; return max(0,min(ends)-max(starts)) in minutes.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| firstStartUtcMinutes | First Start Utc Minutes | Required. Finite number. |
| firstEndUtcMinutes | First End Utc Minutes | Required. Finite number. |
| secondStartUtcMinutes | Second Start Utc Minutes | Required. Finite number. |
| secondEndUtcMinutes | Second End Utc Minutes | Required. Finite number. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| overlapMinutes | Intersection duration; a shared endpoint contributes zero minutes. | Required. Finite number. |
{
"input": {
"firstStartUtcMinutes": 480,
"firstEndUtcMinutes": 960,
"secondStartUtcMinutes": 840,
"secondEndUtcMinutes": 1200
},
"output": {
"overlapMinutes": 120
}
} Limitations and assumptions
- Touching intervals have zero overlap; no timezone conversion, staffing, opening hours or actual service availability is checked.
- Inputs must satisfy both the field types and the cross-field conditions above. Invalid input causes an error; a successful false flag or documented placeholder is a different result.
- Numeric calculations use binary floating point unless exact decimal-integer arithmetic is explicitly stated. No hidden measurement tolerance or decimal rounding is added; nonfinite or out-of-contract results are rejected. Numeric signed-zero results are exported as zero.
Alternative or Complementary methods
Review the original agreement, invoice, shipment and payment records with their stated editions and currency bases. Use complete contractual and valuation rules for actual obligations; supplied shares, labels and conversions are auditable components of that review.
References
Similar or alternative tools
- International Purchaseorder Dual Currency Amount
Convert a signed purchase-order amount using a supplied target-per-source rate.
- International Contract Governing Language Key
Preserve an explicit contract governing-language assertion and clause source.