flow-time dial · meter band gauge

Cross-Check Observed Work-in-Progress Against Rate Times Mean Flow Time

An open-work count and a completion rate are not comparable until elapsed flow time supplies the missing unit. Put all three on a lane-level dial before explaining why a service backlog appears different from its normal operating model.

1 · Disjoint service lane | completions per day | mean flow time in days | observed open items

FIRST-LOAD

HYPOTHESIS / PROTOTYPE — checkout unavailable. Calculation is local. A draft is saved automatically in this browser profile when storage is available; Reset to sample clears it. Optional Pro history stores only five summaries and has its own deletion control. State links encode your inputs and can remain in browser history, clipboard or recipients’ records; share only non-sensitive rows. Optional external AI formatting leaves this device. The required site analytics beacon reports page activity; shared URLs contain encoded inputs. Do not treat an encoded URL as private. The calculator has no input-collection endpoint.

Data note: The flow-time dial processes Disjoint service lane | completions per day | mean flow time in days | observed open items locally. Starter/sample selection and Run compute in this tab; no input is sent by the calculator. A local draft may be saved; explicit state-link sharing or optional external AI formatting can disclose inputs. Use non-sensitive labels.

Perspective: Before: an open count was compared with a daily rate without matching units. After: explicit flow time supplies a model and each lane keeps its signed disagreement.

2 · Read the flow-time dial

Restricted operations-model arithmetic only, not a staffing recommendation or service guarantee. Ask the operations owner or a qualified operations analyst to confirm system boundaries, compatible averages and steady-flow assumptions before acting on a gap.

Paid layer: flow-time dial filing layer

one-time step · the free reading above stays complete

hidden patterns detected after your first run

Free tier

one complete unwatermarked flow-time dial run in the app
three labeled samples and unlimited article-demo calculations
complete result text and a user-triggered input-state link

What $4 one-time adds

unlimited subsequent flow-time dial app calculations after a local convenience signal
print the flow-time dial with visible assumptions and its safety boundary
CSV of the displayed items observed minus modeled and row workings; conditional estimate uses your manual-retyping minutes
five local reading summaries (headline/count/time), not saved full inputs or cross-device backups

HYPOTHESIS / PROTOTYPE: $4 is a proposed one-time price for filing the flow-time dial, not a current sales offer. No measured time saving or buyer demand is claimed. The optional manual-retyping baseline above estimates one export’s retyping budget only; it does not change the calculation or guarantee savings.

Local history (this device)

No saved runs yet — your first run files here.

Filing prototype — checkout unavailable

Checkout is unavailable. Browser-local, profile-scoped convenience gating is best-effort, not server-verified access. A URL or browser flag is not proof of payment. Clearing browser data removes local state; no account or cross-device recovery is provided.

Optional filing controls are a local prototype.

Checkout is unavailable. The reading above is complete; print, CSV and five local summaries are optional enhancements, not hidden answers.

Before using the flow-time dial

Little's-law-style accounting relates average work-in-progress, average throughput and mean time within one consistent system boundary under stable conditions. A single snapshot is not automatically the long-run average. Completions must be counted in the same item units as open work, and flow time must cover the entire same lane from entry to exit. Use calendar days or workdays consistently; the app does not convert between them. Lanes must be disjoint if their quantities are added. The review percentage measures abs(observed-model)/model, with zero-model cases explicitly labeled unavailable for that relative ratio. It is a discussion threshold, not proof of instability, inefficiency or a staffing requirement.

Boundary and sources

Method: Items/day multiplied by days produces modeled items. Subtract modeled items from the observed count for each lane. The dial counts rows beyond your relative review mark, while the row retains actual item quantities. The total gap adds only disjoint lanes' counts and should be read beside the individual differences so cancellation remains visible.
All sample records, dates, quantities and labels are invented. No outside policy, contract, rate, clock offset, measurement or accessibility standard is represented as verified.
Google’s official pricing documentation, fetched 2026-10-01, says AI Studio is free in available regions. Optional formatting may require a Google account; manual local entry requires none. Limits can change and free-tier content may be used to improve products. Do not send private records.

Mechanism: competence-autonomy-loop

Optional AI formatting, never the calculation

Manual entry completes this flow-time dial for free without signup. If available to you, the free AI Studio interface linked in the sources may format fictional or non-sensitive notes; external access may require an account. No API key or AI call is built into this tool. Free-tier content may be used to improve products. Review each cell and transcribe it to the labeled row schema; do not paste the JSON object into the row box.

Format only these fictional or non-sensitive notes for a flow-time dial. Return strict JSON shaped as {"rows": [{"label": "string", "cells": ["string", "string", "string"]}], "setting": "string"}. The columns are Disjoint service lane | completions per day | mean flow time in days | observed open items; the setting is Relative-model-gap review mark (%). Keep all supplied strings and quantities exactly; do not calculate, infer missing entries, invent dates or add advice. If any required value is missing, return an empty rows array and ask me for it separately. I will verify every cell against my source and manually transcribe rows using vertical bars before running the local calculator.

An AI response is not executed, fetched or trusted as a result. Missing values remain questions; the strict local parser checks the rows you actually enter.