1 — What this tool is
The web version of the controlled form UER-2026-ENG-FRM-0001-00-001 Rev 003 (Universal Site Laboratory Test Record). You fill the record on screen, it autosaves as a draft on your device, and when the record is complete you commit it: a committed record is immutable — it cannot be edited or deleted, ever. Corrections are made by a new record that references the old one. Committed records live in the Record Archive.
Four pages, reachable from the top bar: New record (the form), Record Archive (committed records, read-only, with Check & approve), Customer Review (the customer's countersignature queue), Manuals & Procedures (the reference library).
2 — Signing in
- Open lab.uerllc.com. You land on a Cloudflare Access sign-in page.
- Enter your work email address exactly as registered, and ask for the code.
- Cloudflare emails a one-time PIN. Enter it and you are in.
Identity doctrine: the performer and checker identities on a record are stamped from your login — never from a typed field. The name you type in the form is a display label; the email that matters comes from the sign-in. Sign out ends the Access session.
3 — The record form, block by block
Block 1 — Sample Header
| Field | Notes |
|---|---|
| Record no. * | Format SITE-YYYY-MM-DD-NNN. This number is the record's identity — a duplicate number is refused at commit. |
| Date / Time * | Sample date and 24-hour time. |
| Sampled by * | Name and initials of the person who took the sample. |
| Process T / P at sample point | °C and kPa; the converted values (°F, psi) appear underneath automatically — conversions are computed, never typed over. |
| Chain-of-custody initials | One set of initials per handover. |
| Sample point * | wellhead / separator / tank inlet / tank outlet / truck / other (free text). |
| Sample context * | untreated or treated. The untreated-vs-treated pairing is doctrinal: an untreated record shows a pairing banner with Start treated twin, which opens a pre-linked treated record. A treated record requires the agent (% v/v) and the hours since treatment, and takes the twin's record number. |
Block 2 — Test Matrix
Tick the tests you performed and record the raw value as read. Per row you can also enter the test temperature, instrument ID/serial, calibration due date, analyst initials, time, the spec/limit, and the pass–fail call. Rows cover density/API gravity, Stabinger and rotational viscosity (rotational takes spindle no. and RPM), liquid- and vapor-phase H₂S, salinity, BS&W, true vapor pressure (fixed test temperature 45 °C), water by distillation, pour point, total sulfur, pH of separated water — plus two spare rows for any other test.
- Conversions (°API, cP, lb/1,000 bbl, psi, °F) are computed and shown — never overwritten.
- Viscosity is reported only together with its test temperature; density likewise.
- Liquid-phase H₂S is a dead-oil measurement: never infer the headspace concentration from it (Henry's law).
Block 3 — Completion
Retest reference (if this record duplicates or retests an earlier one), Analyst * (name — the performer email is stamped from the login and shown under the field), and remarks. The reviewer field is disabled on purpose: the checker is stamped automatically at review.
Block 4 — Attachments
Site photos, calibration certificates, third-party results — image, PDF, Word, Excel, max 25 MB each. Files upload immediately when picked and are stored with the record at commit.
4 — Drafts, autosave, export, print
- The form autosaves to this device every 0.4 s — the top bar shows the last save time. Drafts are per browser, not on the server.
- The drafts dropdown switches between saved drafts; New record starts a clean form.
- Export JSON downloads the draft as a file (backup / transfer).
- Print record sheet prints the faithful A4-landscape controlled-form sheet — note the footer rule: uncontrolled when printed unless record-numbered and entered in the site-lab register.
5 — Committing a record
Commit record opens a two-step confirmation with a summary. Read it:
- Single-person site: if you are both performer and checker, tick that box — the four-eyes principle is waived and the record is marked SELF-CHECKED. Use it only when it is true; the flag is visible to everyone, including the customer.
- Customer countersignature: tick to send the record to the customer's authorized signers — they are notified by email and the record appears in their review queue. Select the customer/project in the top bar first.
- A duplicate record number is refused — pick the next serial.
6 — Record Archive
Read-only register of all committed records: record no., date, sample point, context, performer, commit time (UTC), checker, status. Status chips:
| Chip | Meaning |
|---|---|
| UNCHECKED | Committed, not yet reviewed. |
| CHECKED | Reviewed and approved by a second person. |
| SELF-CHECKED | Performer and checker are the same person — flagged deliberately. |
| AWAITS CUSTOMER / CUSTOMER ✓ / CLARIFICATION | Customer countersignature state: in their queue / countersigned / sent back with a question. |
Click a row for the full record (attachments included) and Print. Check & approve is the reviewer's stamp: it works once per record, and the checker identity is stamped from the login — never typed. Checking your own record is technically possible but flagged as self-check; do it only under the single-person-site rule.
7 — Customer Review (for the customer's signers)
The customer's authorized reviewers see a queue of records awaiting countersignature. Each record is accepted individually: tick the reviewed records (or open one for full detail) and sign — the signature records who signed, when (UTC), and a content hash of exactly what was signed. Request clarification sends the record back to the lab with a note instead. A sign-in without a review mandate sees a "No review mandate" page — contact your UER counterpart if that is wrong.
8 — Manuals & Procedures
The reference library: instrument manuals and procedures, each with a title and description. Everyone signed in can list and download. Upload and delete are restricted to the tool owner — send new documents to the CTO with a title, a category (manual or procedure), and an identifiable filename.
9 — When something is wrong
Session expired → sign in again. A commit refused on a duplicate number → the record already exists; check the Archive. Anything else — a record that should not exist, a wrong stamp, an upload that fails under 25 MB — email the CTO (rainer.tesch@uerllc.com) with the record number, the time, and what you were doing. Retention doctrine: original in the site-lab binder, copy to the operations file.