Claims and Contracts Management

1. What this tool is

CCM is the working surface for the commercial side of Contract MAF7025-003 (EWT/EPF, Mafraq). It shows the contractual clocks, the live matters, the variations and claims register, the correspondence log, the obligations register, and the governing documents. The doctrine behind it is the controlled document UER-2026-MAF-001-MMP-0001 (Documents section on the board); where this manual and that document disagree, the document governs. The contractual record itself lives in the UER document management system — this tool is the interface, not the archive.

2. Signing in

1. Open ccm.uerllc.hydrocarbonupgrading.com. You land on a Cloudflare Access sign-in page.
2. Enter your work email address exactly as registered, and ask for the code.
3. Cloudflare emails a one-time PIN to that address. Enter it and you are on the board.

Once signed in, the top right of the board shows your name, your maximum clearance, and your role. If the page instead says Not authorized with your email address, the sign-in worked but you are not in the tool's people list — email the CTO.

3. Who can do what

Independently of the role, your clearance caps what you see: an entry classified above your clearance does not appear for you at all, and when you raise an entry you cannot classify it above your own clearance. The classification ladder (Public, Commercial in Confidence, Internal, Controlled, Confidential) is defined in UER-2026-COR-STD-0012.

4. The board, section by section

4.1 Clock board

One card per contractual clock. A card shows the clock ID and title, its contractual basis and period, the owner, the trigger, the start date, and the deadline in red. The countdown chip reads:

A running clock has a gold left edge. Clocks are started, updated, and closed out by the tool operator as trigger events occur; the board itself is the read-out. When a clock starts because of something you handled (an instruction received, a claim event), make sure the correspondence is logged (section 4.4) so the start is evidenced.

4.2 Live matters

Cards for the currently open commercial matters — the few things that actually need attention this week. Each card shows the matter ID, a status pill (OPEN red, DRAFT amber, MONITOR blue, grey when folded), the value at stake where stated, and the next step in red. Matters are maintained by the tool operator; if a card's next step is yours and it is stale, say so in the diary of the related register entry.

4.3 Variations and claims register

The register of every instruction, variation, and claim. Columns: serial, type, subject, basis clause, value, state, next step, owner, date raised. Serials read CCM-2026-NNNN and are never reused. Type pills: Instruction amber, Variation blue, Claim red. States run Open → In progress → Submitted → Agreed → Closed, or Cancelled.

Above the table: the + Raise entry button, a Print board button (A4 landscape, with a print header naming who printed and when), a show closed checkbox (closed and cancelled entries are hidden unless ticked), and type/state filters.

Raising an entry — every field:

Submit and the entry appears with its serial. Click the serial to open the entry page (section 5).

4.4 Correspondence log

Every contractual letter, notice, and significant email, in and out. Columns: date, direction (in red, out green), parties, subject, clause triggered, clock, and who logged it. + Log correspondence opens the form: date (pre-filled today), direction, parties (e.g. "Mafraq → UES"), subject, the clause the item triggers, and a clock flag that links the item to a clock from the clock board. The log is append-only: a mistake is corrected by a new entry, never by editing. Log the day the item moves — an unlogged letter does not exist.

4.5 Obligations register

All obligations of Contract MAF7025-003, one row each, mirroring the controlled register UER-2026-MAF-001-REG-0001 (Documents section). Columns: Req (the register row ID, e.g. C-19), Clause, Party (Company / Contractor / both), Obligation (with notes in small print where present), Due rule, Owner, and the status chip:

+ Add obligation opens a small form (clause, party, obligation, due rule, owner, Req ID, status) for obligations that emerge after the register's rev 001 — new rows should also be reported to the CTO so the controlled register document stays in step.

4.6 Documents

The governing documents: the doctrine (UER-2026-COR-MMP-0001), this contract's how-to (UER-2026-MAF-001-MMP-0001), and the obligations register master (UER-2026-MAF-001-REG-0001). View opens the HTML, PDF downloads the PDF. The links always serve the current revision — if you printed a copy last month, it may be stale; check the revision on the cover.

5. The entry page (click a serial)

Each register entry has its own page with four parts:

• The entry — full details as raised.
• Update — change the state, basis clause, value, reassign the owner, or rewrite the next step, then Apply. Every change is recorded.
• Audit trail — who changed what, when. Automatic, complete, not editable.
• Diary — dated notes, append-only. This is where the reasoning lives: "called the Contract Holder, she confirmed X" — write it the same day. A correction is a new note, never an edit.

The page prints A4 portrait for meetings.

6. The everyday flows

An instruction arrives from the Company

1. Log it in the correspondence log the day it arrives (direction in, clause C3 Art. 6.1.2).
2. Raise a register entry of type Instruction with the basis clause and the next step.
3. If it costs money or time, the notice clocks start with the instruction — check the clock board and make sure the relevant clock is running; if not, tell the tool operator the same day.

A claim event happens

1. Raise a register entry of type Claim immediately — the claim clocks run from the event, not from when you get around to it.
2. Keep the contemporary records; add diary notes to the entry as facts accumulate.

You verified an obligation

1. Open the obligations register, find the row, and have its status flipped to MET — with the evidence named in the register row's notes or in a diary note on the related entry.

7. When something is wrong

The gates fail closed on purpose: if your session expires or a link 404s, sign in again rather than trying another URL. Your first sign-in on a new browser sends the tool operator a one-line notification — normal monitoring, not an alarm. Anything else — wrong data, a missing person, an action the tool refuses that you believe is yours — email the CTO (rainer.tesch@uerllc.com) with the tool, the time, and what you were doing.