LensReading which lens this session carries.

Client intake

Client Intake and Baseline

Load a cost and volume extract from the client.

Load a file

CSV, up to 5,000 rows. Weekly periods.

Columns, in any order: period, process, transactions, labor_hours, labor_cost_usd, system_cost_usd. A process is matched to a tower by code, then name, then a known alias. A row that fails a check is kept out and listed; the rest load.

Loading a file needs the Process owner role or above.

Tower by tower

No file loaded yet

Load the sample or a client file to see the comparison.

Files loaded

Newest first. A refused file is kept with its reason.

No file has been loaded for this tenant.

Actions

What is waiting on a person

A client extract only becomes a baseline once every row lands on a tower.

Nothing on this surface is currently sitting with a person. An unmapped row is cost the baseline cannot place. Map it or exclude it on the record.

Operations

What this desk is allowed to start

A surface that only reports is not operable.

Trigger and bound

Across tenants, 0 extract batches have been received, holding 0 accepted rows.

Live observability

What the record shows right now

Where accepted rows landed.

Current distribution

0 rows

No rows are held on this surface yet.

Is policy and strategy coming to fruition

Whether the written intent is holding here

Not yet. No client extract has been loaded.

Not holding on the record

The intent is that a client baseline is measured from their own records, never assumed.