← Back to Dashboard
Data Management
Manage master data: Personnel, Assessor, Job Requirements, Audit Logs
| Worker ID | Name | Position | Department | Contractor | Status | |
|---|---|---|---|---|---|---|
| Loading… | ||||||
| Name | Title | Department | Type | Status | ||
|---|---|---|---|---|---|---|
| Loading… | ||||||
| Department | Position | Min. Experience | Certifications | Documents | |
|---|---|---|---|---|---|
| Loading… | |||||
Positions used by contractors in their applications that are not in the Job Requirements master.
While a position is missing from the master, its applications have no document checklist, so completeness is never checked on submit.
Spellings that differ only in word order or letter case are already grouped into one row (e.g. Disposal Operator + Operator Disposal). Tick normalise spelling so past applications are rewritten too; without it the other variants reappear here tomorrow.
| Department | Position | Usage | Contracts | |
|---|---|---|---|---|
| Loading… | ||||
| Name | Department | Sort | Status | Notes | |
|---|---|---|---|---|---|
| Loading… | |||||
About Locations: Destination locations/rigs used by contractors when submitting SBTC applications.
Current set: Drilling (Rig PVD-2, Rig PVD-3, AHTS, Survey) and Well Intervention (Seapup-1/2/3, WLWI).
Add or edit anytime as operations require.
Function Readiness
Which function is closest to running SBTC on its own, and what is still missing.
Loading…
Adding a brand-new function needs a migration.
A function can only own applications, certificates and locations if its name also exists as a
department label in the database, and adding one is a one-way change that cannot be
undone. Ask for a migration (sql/) rather than expecting a button here. Renaming,
reordering and activating existing functions is done below.
Operating Zones
Zona 5 (PHE ONWJ), Zona 6 (PHE OSES), Zona 7 (Pertamina EP)…
| Code | Name | Sort | Status | |
|---|---|---|---|---|
| Loading… | ||||
A new zone does not isolate anything yet.
Today
zone_id exists only on user accounts. No application, worker, contractor or
contract carries a zone, and no screen filters by one, so a zone added here is a label you can
attach to a user and nothing more. That is deliberate: wiring a column that always holds the same
single value into eight tables costs work with no buyer. When a second zone genuinely starts
operating, the work is to carry zone_id into the data tables and filter on it.
| Time | User | Action | Table | Description | IP |
|---|---|---|---|---|---|
| Loading… | |||||