OTM v3.1 — Offshore Task Manager

—

Schedule Health

Loading…

—

Overall Progress

0

Overdue WOs

—

0

Days Without Incident

Safe

0

POB

—

Active Blockers & Alerts

Last Shift Progress

Submit EOS at end of shift — shift summary and progress changes will appear here.

Contractor / Team Performance

Milestone Gate Status

ERH Budget & Burn Rate

Actual Burn

—

h/day

Required Burn

—

h/day to milestone

Forecast End

—

at current burn rate

ERH Variance (Budget vs Remaining) —

Auto-Generated Shift Summary

Loading…

Latest Updates

EOS submissions · WO completions · Handover notes · Blockers

0

Complete

Done

0

In Progress

Active

0

On Hold

Blocked

0

Planned

Upcoming

0 / 140

POB

—

0 / 0

FSRs Onboard

FSR

—

Overall Progress (MH-weighted)

—

Est. Resource Hours Remaining

0h done

0

Overdue WOs

—

Stale Progress (>5 days)

Progress by Team

Overall Completion

Latest Updates

Critical Path — High Priority

	Work Order	Team	Progress	Target	Status

Open Alerts

14-Day Activity Trend

LTHX Campaign Status

Loading…

Shift Handover Notes

No handover notes

Team Utilization

Admin: ↑ Import CSV Select WOs via Bulk Select → Duplicate or Delete

Workstreams

Overarching activity tracks. Updated daily by workstream leads. Feed the P1 Onshore section of the Daily Report.

Start-up Sequence

Live status of the FPSO start-up sequence. Click any step to update status. Steps are organised by lane (system).

Jump to

Key Milestones & Forecast Dates

Schedule

Complete In Progress Planned On Hold Critical Path Today Milestone

S-Curve — Planned vs Actual Completion

Weekly Completion Rate

Critical Path — Work Remaining vs Time to Milestone

1

Work Orders

Review active WOs

2

POB List

Offshore personnel

3

Assign

Personnel to WOs

4

Optimise

Schedule & workload

Active Work Orders

Active Workers Available —

0——

0

Working Crew

0

Day Shift

0

Night Shift

0

Rest+FSR

0

Mobilising / Available

Teams

Personnel Register

Team Allocation Summary

Team	Lead	Size	Day	Night	Active Tasks	Complete	Planned	Utilization

Mob / Demob Timeline

0

Supply Vessels

0

Helo Pax (upcoming)

0

Non-Darwin Pax

0

Cargo Items

0

Materials O/S

0

Onboard

Personnel Movements — Flight Schedule

Derived from POB roster — grouped by flight leg

0

Scaffold Jobs

0

Rope Access Jobs

0

Crane Lifts

0

Scaffolders Offshore

0

Rope Access Offshore

—

Utilisation Today

0

Unallocated Today

0

Days Without Incident

Safe

0

Works Needing Permits

0

Day Shift Permits

0

Night Shift Permits

Permits to Work are managed in your external PTW system. This view identifies permit requirements from the work register and generates the daily input for your PTW office.

⚠ IMPORTANT — PTW Authorisation Required
The permit types and isolation requirements shown in this view are indicative only, derived from the work order register. All permits, isolations, gas tests and access requirements must be independently confirmed and formally issued under the PTW system, and are subject to approval by the OIM / Offshore Superintendent prior to work commencing. This tool does not replace or substitute any formal PTW, LOTO, or isolation certificate process.

Permits Required — In Progress Works

Reports

Daily executive report & weekly projects review — PDF export & stakeholder distribution

Report Date

Shift Period

OIM / Superintendent

End of Shift

0 changes

Work Orders

←

Select a work order

Tap any row on the left to update
progress, status and shift notes

≡ Shift Summary What was achieved · issues · handover instructions 0 words

Daily Report Narrative — P1 & P2 Scopes

Planned Activities for Next Shift

Notable Activities Beyond 72 Hours

Emerging Risks & Mitigations

Start-up Status Summary

⚠ Safety / Incident Log Log any incident, near miss, or safety observation from this shift

EOS Shift History

Loading...

▼

Checking storage…

—

Project Configuration

Project Name

Project Reference

Client / Operator

Contractor

Project Start

Planned Completion

Project Manager

Field Location

Days Without Incident

Max POB (Vessel Capacity Limit)

Rated capacity — not updated by POB import

Current POB Override (set manually if import count is wrong)

ERH Budget (Total Planned Resource Hours)

Slip Alert Threshold (days)

Dashboard banner appears when any milestone slips past this many days vs P6

Data Management

Import Reports

Accepts PDF, PPTX, DOCX, XLSX — parsed and merged automatically

Import P6 Schedule (PDF)

Import P6 Schedule PDF

P6 Re-Forecast Schedule (PDF) — imports activity dates, completion percentages, milestones and aligns with work orders

Import POB / Personnel

Import Master POB Loading (Excel)

Master POB Loading (Excel) — imports offshore personnel, mob/demob dates, B2B pairings and rotation patterns

PR/PO Materials Import

Import PR/PO register (Excel) — updates materials logistics with PO status, supplier, ETA onboard, delivery location and vessel/flight details

↑ Import PR/PO Excel

Vessel Forecast Schedule Import

Import OSV weekly schedule (Excel) — parses the Barossa vessel calendar format and displays a day-by-day vessel timeline on the Logistics page.

↑ Import Vessel Schedule

Automated Daily Report Email

Uses EmailJS (free, no backend required) to send an automated daily report to stakeholders. Setup guide — create a free account, add a service (Gmail/Outlook), create an email template.

EmailJS Public Key

Service ID

Template ID

Send Time (local, 24h)

Recipient Emails (one per line) — defaults to Stakeholder List above

Auto-send enabled (currently disabled — contact admin to enable)

Save & Backup

Auto-save: active

Backup to Local Drive

Saves a timestamped snapshot to your device. Recommended daily and before any major import.

Restore from Backup

Restoring overwrites all current data. Download a backup first.

Restore from Backup File

Reset

Merges the latest built-in Barossa work orders — skips any that already exist. Your custom WOs, persons, teams and settings are preserved.

Removes all data from browser storage. Use a backup to restore.

Version History

Auto-saved every 2 hours. Last 10 snapshots retained with restore capability.

Supabase Cloud Sync

Connect to Supabase for shared multi-user access. All team members load and save to the same database. Free tier supports up to 50 users.
supabase.com → New project → Settings → API

▶ First-time setup — SQL to run in Supabase SQL Editor

-- Run this once in Supabase SQL Editor (Database → SQL Editor → New query)

-- 1. Create the data table
create table if not exists otm_data (
  id          text primary key,
  project     text,
  data        jsonb,
  pushed_by   text,
  updated_at  timestamptz default now()
);

-- 2. Allow anonymous read/write (RLS off for simplicity)
--    For production, enable RLS and add policies per user role
alter table otm_data disable row level security;

-- 3. Grant access to the anon role
grant all on otm_data to anon;
grant all on otm_data to authenticated;

-- Done. Click Test Connection in OTM to verify.

Supabase Project URL

Supabase Anon Key (anon/public key — safe to share)

To auto-connect all users: open the HTML file, find SB_DEFAULT_URL and SB_DEFAULT_KEY near the top of the script and paste your values. Every user who opens the file connects automatically.

Bake Credentials into HTML

Downloads a copy of this file with your Supabase URL and key already written in. Upload that file to SharePoint — every user who opens it will auto-connect to the shared database without entering credentials.

OTM — Offshore Task Manager
Storage: browser localStorage

Stakeholder Emails — Report Distribution

One email per line. Used by the Share ✉ button on the Daily Report page.

User Management

Admin Only

Passwords visible to admin only. Stored locally — never transmitted to external servers.

Role permissions:
admin — full access incl. settings, data management, user administration
team — read + update WOs, add works, update progress, daily report — no settings access
shift — EOS Update only — progress sliders and shift notes, no other pages
readonly — view all data, generate and export reports — no editing
Credentials stored as SHA-256 hashes in localStorage. Sessions expire on browser close.

SharePoint Deployment Guide

How to install OTM as a persistent team tool on your SharePoint site

Option A — Document Library

Simplest. Upload the HTML file to a SharePoint Document Library. Users open it in the browser. Recommended for most teams.

Option B — Embed Web Part

Embed OTM inside a SharePoint page using an Embed or Script Editor web part. Team sees it without leaving SharePoint.

Option C — SharePoint + Supabase

Best for multi-user teams. SharePoint hosts the file; Supabase provides shared real-time database. All users see the same data.

Option D — Company Server / No External Cloud

For organisations that cannot use external cloud services. Three approaches: SharePoint List, company-hosted REST API, or shared JSON file on a file server.

Option A — Document Library (Recommended for Getting Started)

Prerequisites

✓ Microsoft 365 account with SharePoint access
✓ Site Owner or Contributor permissions on the target SharePoint site
✓ The OTM HTML file saved to your computer
✓ Modern browser (Edge, Chrome, Firefox)

Storage Behaviour

Important: When opened from SharePoint without Supabase, each user's browser stores data locally (localStorage). This means each user has their own copy of the data. For shared team data, add Supabase (Option C).

1

Navigate to your SharePoint site

Go to your project SharePoint site. From the left navigation, click Documents (or any Document Library where project files are stored — e.g. "Project Tools" or "Engineering"). If no suitable library exists, create one: Site Contents → New → Document Library.

2

Upload the OTM HTML file

Click Upload → Files in the toolbar. Select your OTM_v1.0.html file and upload. SharePoint will store it in the library. You can create a dedicated folder if preferred (e.g. Tools / OTM).

3

Open OTM in the browser

Click the uploaded file in the library. SharePoint will open it in the browser (Edge/Chrome). The app loads fully — all functionality works without any server or backend.

Tip: Right-click the file → Copy link → share this direct URL with your team. Bookmark it for quick access.

4

Set permissions

Right-click the file → Manage Access. Share with specific people or your project SharePoint group. Recommend: Can view for most users (OTM handles its own role-based access internally). The HTML file itself does not need edit permissions for users to run the tool.

5

Updating OTM (when new versions are released)

Download a data backup first (Settings → Download Backup). Upload the new HTML file to the same library location, replacing the old file. Restore the data backup in the new version. Your data is preserved in the backup JSON — not in the HTML file itself.

Option C — SharePoint + Supabase (Recommended for Multi-User Teams)

What this gives you

✓ One shared database — all users see the same data
✓ Real-time sync — changes appear for everyone
✓ Free up to 500MB / 50,000 rows (Supabase free tier)
✓ No server to manage — fully managed cloud database
✓ SharePoint remains the access point and permissions layer

What you need

✓ Free Supabase account (supabase.com)
✓ 5 minutes to run the setup SQL
✓ Ability to edit the HTML file (any text editor — Notepad works)
✓ SharePoint site with Document Library

1

Create a Supabase project

Go to supabase.com → Start your project → Sign up (free) → New project. Choose a name (e.g. OTM-Barossa), set a database password, and select the region closest to your team. Wait ~2 minutes for the project to provision.

2

Run the setup SQL

In your Supabase dashboard: Database → SQL Editor → New query. Paste and run the SQL shown in the Cloud Sync card above. This creates the otm_data table. You will see "Success. No rows returned" — this is correct.

3

Get your API credentials

In Supabase: Project Settings → API. Copy two values:
• Project URL — looks like https://abcdefgh.supabase.co
• anon / public key — a long JWT token starting with eyJ…
The anon key is safe to share — it is read-only without Row Level Security enabled.

4

Bake the credentials into the HTML file

Open the OTM HTML file in any text editor (Notepad, VS Code, etc.). Use Find (Ctrl+F) to search for SB_DEFAULT_URL. You will find two lines near the top of the JavaScript section:

const SB_DEFAULT_URL = 'https://pbnxloauowtsryruqmab.supabase.co';
const SB_DEFAULT_KEY = 'sb_publishable_v_5P4rc57vr1i6xqUa1VeA_KCCgI8IB';

const OTM_VERSION = 'v3.2 (2026-04-27) — coherence validators'; Replace the empty strings with your credentials:

const SB_DEFAULT_URL = 'https://abcdefgh.supabase.co';
const SB_DEFAULT_KEY = 'eyJhbGci...';

Save the file. Every user who opens this file will automatically connect to the shared database.

5

Upload to SharePoint and test

Follow Option A steps 1–4 to upload the configured file to your SharePoint Document Library. Open it, go to Settings → Cloud Sync → Test Connection. You should see "Connected" with a green indicator. Push your initial data with Push ↑. Share the SharePoint file URL with your team — they will all load from and save to the same Supabase database.

6

Ongoing sync behaviour

OTM auto-pushes to Supabase 30 seconds after any change. The ☁ Cloud badge in the top bar confirms sync is active. For multi-user scenarios where two people edit simultaneously, the last push wins — coordinate with your team using the built-in user roles (admin edits, viewers read-only). Recommend: one admin user makes all data changes; other users operate as Team or Viewer roles.

Supabase free tier limits: 500MB database, 1GB file storage, 50,000 monthly active users, 2GB bandwidth. More than sufficient for a typical offshore project team of 5–50 users over a 6–12 month campaign.

Option D — Company Server / No External Cloud

Use this option when your organisation's IT policy prohibits data leaving the corporate network, or when Supabase (Option C) is not permitted. Three approaches are available — choose the one that matches your infrastructure.

SharePoint List as Database

OTM reads and writes data to a SharePoint List via the Microsoft Graph API. Data never leaves your Microsoft 365 tenancy. Requires an Azure AD App Registration (one-time setup by IT).

Advantages

✓ Data stays in Microsoft 365
✓ Uses your existing SharePoint licence
✓ Full audit trail via SharePoint versioning
✓ IT-approved data residency
✓ Permissions inherit from SharePoint groups

Requirements

✓ Microsoft 365 / SharePoint Online
✓ Azure AD App Registration (IT)
✓ Graph API permissions: Sites.ReadWrite.All
✓ Client ID from App Registration
✓ MSAL.js loaded (Microsoft library)

1

IT: Register an Azure AD Application

Ask your IT administrator to go to Azure Portal → Azure Active Directory → App Registrations → New Registration. Name it OTM-SharePoint. Set Redirect URI to Single-page application (SPA) and enter the SharePoint URL where OTM will be hosted (e.g. https://yourcompany.sharepoint.com/sites/project/Documents/OTM.html). Under API Permissions, add Microsoft Graph → Delegated → Sites.ReadWrite.All and grant admin consent. Note the Application (client) ID — you will need it.

2

Create the SharePoint List

On your SharePoint site: Site Contents → New → List → Blank list. Name it OTM_Data. Add one column: Add column → Multiple lines of text → name it payload. Set Maximum number of characters to 1,000,000 (or maximum allowed). This list stores the OTM database as a single JSON payload per project.

3

Configure OTM to use Graph API

Open the OTM HTML file in a text editor. Near the top of the script, find the Supabase config constants and add these lines below them:

const SP_CLIENT_ID  = 'YOUR-AZURE-APP-CLIENT-ID';
const SP_TENANT_ID  = 'YOUR-TENANT-ID';
const SP_SITE_URL   = 'https://yourcompany.sharepoint.com/sites/project';
const SP_LIST_NAME  = 'OTM_Data';
const SP_ROW_TITLE  = 'OTM-' + (db.settings.projectRef || 'default');

Replace the placeholder values with your App Registration details. The Tenant ID is found in Azure AD → Overview.

4

How the sync works (for IT / developers)

OTM serialises its entire database to JSON and writes it to a single SharePoint List item via PATCH /sites/{site-id}/lists/{list-id}/items/{item-id} using the Microsoft Graph API with MSAL.js for authentication (interactive login on first use, silent token refresh thereafter). Read uses GET on the same endpoint. This is identical in architecture to the Supabase option but uses Microsoft infrastructure entirely.

Note: The Graph API / MSAL integration is not pre-built in OTM v2.0 — it requires a developer to add the MSAL.js library and replace the Supabase fetch calls in sbPush() / sbPull() with Graph API calls. Contact your system administrator for a configured build. Estimated effort: 4–8 hours for a developer familiar with MSAL.js.

Company-Hosted REST API

OTM is designed to talk to any REST API that accepts JSON. If your company runs an internal API server (Node.js, Python/FastAPI, .NET, etc.) on a company server or IIS, OTM can use it as a storage backend with minimal modification. Data stays entirely on-premises.

What your API needs to do

GET /otm/{projectId} — return the stored JSON
POST /otm/{projectId} — save/overwrite the JSON
CORS headers for the SharePoint origin
Basic auth or API key header (optional)

Suitable platforms

✓ Node.js / Express on company server
✓ Python FastAPI / Flask on IIS
✓ .NET Web API on IIS / Windows Server
✓ Azure App Service (internal)
✓ Any platform that can serve JSON over HTTP

Minimal Node.js / Express server example

// server.js — run on company server: node server.js
const express = require('express');
const fs      = require('fs');
const app     = express();
app.use(express.json({ limit: '10mb' }));

// Allow requests from your SharePoint domain
app.use((req, res, next) => {
  res.header('Access-Control-Allow-Origin', 'https://yourcompany.sharepoint.com');
  res.header('Access-Control-Allow-Headers', 'Content-Type, X-API-Key');
  res.header('Access-Control-Allow-Methods', 'GET, POST, OPTIONS');
  if (req.method === 'OPTIONS') return res.sendStatus(204);
  next();
});

// Simple API key check (optional but recommended)
app.use((req, res, next) => {
  if (req.headers['x-api-key'] !== 'YOUR-SECRET-KEY') return res.sendStatus(401);
  next();
});

// GET  /otm/:projectId  — load data
app.get('/otm/:id', (req, res) => {
  const file = `./data/${req.params.id}.json`;
  if (!fs.existsSync(file)) return res.json({});
  res.json(JSON.parse(fs.readFileSync(file)));
});

// POST /otm/:projectId  — save data
app.post('/otm/:id', (req, res) => {
  fs.mkdirSync('./data', { recursive: true });
  fs.writeFileSync(`./data/${req.params.id}.json`, JSON.stringify(req.body));
  res.json({ ok: true });
});

app.listen(3000, () => console.log('OTM API running on port 3000'));

1

Deploy the server on your company network

Save the server code above as server.js on a Windows or Linux server accessible from all users' desktops. Run npm install express && node server.js. Note the server's internal IP or hostname (e.g. http://srv-app01:3000). IT will need to open the port in the local firewall if required.

2

Point OTM at your server

Open the OTM HTML file in a text editor. Replace the Supabase constants with:

const SB_DEFAULT_URL = 'http://srv-app01:3000'; // your server
const SB_DEFAULT_KEY = 'YOUR-SECRET-KEY';       // matches server check

Because OTM's push/pull uses the same URL + key pattern as Supabase (just without the Supabase-specific headers), this works without modifying the push/pull functions — the server simply accepts JSON on the same routes.

Why this works: OTM's sbPush() sends a JSON body to POST {url}/rest/v1/otm_data. Your server just needs to respond to that path with a 200. The REST path can be adjusted in the sbRequest() function in the OTM script if needed.

Shared JSON File — Simplest On-Premises Option

The simplest approach with no server software required. The OTM database is saved as a .json file on a network share or SharePoint document library. Users manually load and save this file. Suitable for small teams (<5 users) where simultaneous editing is unlikely.

How it works

1. One person edits OTM and clicks Download Backup (.json)
2. Saves the file to the shared folder / SharePoint library
3. Next user opens OTM → Restore from Backup File → picks the shared file
4. Makes changes → saves backup → replaces the file

Think of it as a shared "checked out" document — one editor at a time.

Best suited for

✓ Single editor (supervisor) with read-only viewers
✓ Teams with a clear shift handover process
✓ Environments where IT approval for any server is slow
✓ Proving the concept before committing to a sync solution

⚠ Not suitable for concurrent multi-user editing

Recommended workflow

↓

Load

Restore from shared .json file

∕️

Edit

Update WOs, progress, resources

↓

Save

Download Backup → replace shared file

◉

Notify

Tell team the file is updated

1

Create a shared folder location

Create a dedicated folder in your SharePoint Document Library (e.g. Shared Documents / OTM / Live Data /) or on a mapped network drive accessible to all team members. Agree a single canonical filename, e.g. OTM_LIVE_DATA.json. This is the single source of truth.

2

Establish a clear handover protocol

Agree with your team: only the current shift admin loads and saves data. At shift handover, the outgoing supervisor saves the backup and uploads it to the shared location. The incoming supervisor restores from it at the start of their shift. This prevents data conflicts. Use the built-in Shift Handover Report (Daily Report → Shift Handover tab) to document the changeover.

3

Enable SharePoint version history for safety

In the SharePoint library where the JSON file is stored: Library Settings → Versioning Settings → Create major versions. Set Keep the following number of major versions to at least 30. This gives you a full 30-save history and the ability to roll back any accidental overwrites.

Upgrade path: Start with the shared file approach to get the team using OTM immediately. Once the workflow is established, migrate to Option C (Supabase) or the company REST API approach for automatic sync. The backup/restore mechanism is fully compatible — your data migrates without loss.

Option Comparison

Option	Setup effort	IT involvement	Real-time sync	External cloud	Best for
A — Doc Library	5 min	None	✗	None	Single user
C — Supabase	30 min	None	✓	Supabase	Most teams
D1 — SP List	4–8 hrs	Required	✓	None	Corp IT policy
D2 — REST API	2–4 hrs	Server access	✓	None	Dev available
D3 — Shared File	10 min	None	Manual	None	Small teams

OTM — Offshore Task Manager

Field Operations Manual · Barossa FPSO Commissioning Campaign · Santos / BW Offshore

What is OTM?
OTM is a single-file web application built specifically for managing the Barossa FPSO offshore commissioning campaign. It runs entirely in the browser — no installation, no server, no IT involvement. All campaign data (work orders, personnel, progress, shift records) lives in the app and syncs to a shared cloud database so the entire team sees the same picture in real time.

Who uses it
OIM, Commissioning Lead, Team Leads, Shift Crew, Santos stakeholders

When to update
End of each shift via EOS Update. Anytime a WO status or progress changes.

Key output
5-page PDF daily report, shift handover, stakeholder email summary

Module Guide

Executive Summary

KPI dashboard for OIM and Santos leadership

▾

Works Register

36 campaign work orders — the source of truth

▾

Workflow

Crew assignment and schedule optimisation

▾

Schedule

Gantt chart, milestone timeline, P6 import

▾

Teams & Resources

POB board, shift allocation, workload analysis

▾

Logistics

Flights, vessels, materials pipeline

▾

Safety & Permits

DWI tracker, permit planning, incident log, safety matrix

▾

Reports

Daily & weekly PDF reports, shift handover, stakeholder email

▾

EOS Update

End of shift — the most important daily task

▾

Roles & Access

Username

Role

What they can do

admin

Admin

Everything — edit, import, settings, user management, reset data, view passwords

bwoteam

Team

Read + update WOs, EOS, add people and FSRs, handover notes, incidents — no settings

shift

Shift

EOS Update only — progress sliders and shift notes. No other pages.

viewer

Viewer

View all data, export PDF and reports — no editing of any kind

Passwords visible to admin in Settings → User Management. Contact admin to obtain or reset credentials.

Troubleshooting

Handover report shows no data
EOS must be submitted at least once. EOS Update → update at least one WO → write a shift summary → Submit EOS. The handover populates automatically.

Schedule Health shows no milestone
Milestone dates are computed from WO end dates. Check Settings → Project Configuration that IPT, FPT, PC, and Steam dates are set. Missing WO end dates prevent computation.

ERH burn rate looks too low
Set the campaign start date in Settings → Project Configuration. An early start date inflates the denominator. The rate uses actual EOS submissions — it self-corrects as data builds up.

Mob/demob dates off by one day
Check Excel cell codes — a marks exact mob date. Edit directly on the POB board (click the person) or re-import the corrected Excel from Settings.

Cloud sync failing
Settings → Supabase Cloud Sync → verify URL and anon key → Test Connection. On restricted networks the Supabase endpoint may be blocked — use local mode and share the exported HTML.

Reset to original Barossa seed data
Settings → Danger Zone → Reset to Seed Data. Wipes all data and restores the v3.0 baseline — 36 consolidated WOs, seed personnel, seed vessels. Export data first as backup.

POB Excel Import — Cell Codes

Code

Meaning

Effect

a

Arriving

Mob date = this column date

1

Present offshore

First 1 = mob boundary, last 1 = demob boundary

d

Departing

Demob date = this column date

blank

Not present

Absent — used for boundary detection

Settings → Import Master POB Loading (Excel). File must follow the standard BW Offshore roster format. Date parsing uses local date components to avoid UTC off-by-one issues (UTC+8).

Cloud Sync — Supabase Setup

For multi-user team access, connect a Supabase database. All users see the same live data. Without Supabase, data is local to each browser session only.

Create free project at supabase.com
SQL Editor: CREATE TABLE otm_data (id text primary key, data jsonb, pushed_by text, updated_at timestamptz);
Settings → Supabase Cloud Sync → paste Project URL and anon key → Save → Test Connection
Push ↑ to upload your data. Pull ↓ to get the latest from the cloud.
Download Pre-Configured HTML — bakes credentials into the file for SharePoint/intranet deployment.

Auto-sync pushes 30 seconds after any change. The ☁ Cloud badge in the top bar confirms sync is active. For multi-user scenarios, coordinate edits — last push wins.

OTM — Offshore Task Manager
Built for Barossa FPSO Commissioning Campaign · Santos / BW Offshore