This portal is the read-only review surface for the INT-001 Heavy Crude Oil EPF design package (treatment train, scenarios S1/S2). It holds the current revision of every document in the package and the feedback channel for your comments. Nothing here is editable by reviewers — deliberately, so there is always exactly one authoritative version. The UER document management system remains the source of truth; this portal mirrors it.
If sign-in succeeds but the page shows only Not authorized with your email address, you passed the gate but are not in the portal's people list — email the CTO.
Your first sign-in on a new browser sends the tool operator a one-line notification. That is normal monitoring, not an alarm.
| Role | What you can do |
|---|---|
| Viewer | Open and download every document, submit feedback with an attachment, and read all feedback from every reviewer. The reviewers are the viewers — the feedback channel is yours, not just the owner's. |
| Owner | Everything a viewer can do, plus set feedback status (Open / Answered / Closed) and maintain the people list on the People & clearances page (a nav link appears for the owner only). |
The top right of the header shows your name, your maximum clearance, and your role.
The library lists the whole package in the reading order of the reviewer's guide, in five sections:
| Section | Contents |
|---|---|
| 1 · Governing documents | RPT-0001 Plant and System Description & Design Basis; RPT-0002 Drawing Phase Concept and Drawing Register. Read these first. |
| 2 · Specifications | SPN-0001 through SPN-0019 — the engineering specifications. |
| 3 · Drawings — issued concept set | Concept drawings issued for review (PFD, ESD logic, P&IDs). |
| 4 · Drawings — draft | Layout not frozen, pending site inputs — marked with a DRAFT pill next to the title. |
| 5 · Binder and other | Binder cover/index and supporting reports. |
Each row shows doc number, title, revision, suitability code, and date, plus two links:
Every row always serves the current revision — the links are stable and silently resolve to the newest rev. If you saved or printed a copy earlier, check the revision on its cover against the table before relying on it.
The page prints to A4 portrait with a print header naming who printed and when (use the browser's print function).
Use the Feedback form below the library:
| Field | What to enter |
|---|---|
| Document * | Pick the document your comment is about, by doc number. |
| Attachment (optional) | One file, max 10 MB — a marked-up PDF, a sketch, a voice note. Upload happens when you submit. |
| Your comment * | Comment, question, or proposed change. Required — the form refuses an empty comment. |
What happens on submit:
Statuses are set by the owner: Open → Answered → Closed. Every comment is answered — accepted, deferred, or rejected with the reason — in a consolidated comment-response log issued with the next revision.
Alternatively, the cover-email route stays open: reply to the email that brought you here. If you attach files there, start each file name with your initials and the document number (for example JD_SPN-0003_wash_water.pdf).
The owner page lists every person with name, email, maximum clearance on the STD-0012 ladder (1 Public · 2 Commercial in Confidence · 3 Internal · 4 Controlled · 5 Confidential), role, and an assignable flag. Clearances and the flag are changed in place with Save; new people are added with the Add person form. App entry itself is governed by the Cloudflare Access policy — adding a person here does not by itself let them through the gate.
The gates fail closed on purpose: an expired session or a document link that 404s means "sign in again", not "try another address". If a signed-in session is refused by the app itself, the owner is alerted automatically. Anything else — a wrong revision, a missing document, a comment that will not submit — email the CTO (rainer.tesch@uerllc.com) with the tool, the time, and what you were doing.