Inspection Package Tracker

TULSA EAST COMPLEX
saved
Connect shared backend (one-time setup)
  1. Go to console.firebase.google.com, sign in with any Google account, and click Add project. Name it anything (e.g. "tulsa-east-tracker"). You can skip Google Analytics.
  2. In the left sidebar under Build, click Realtime Database → Create Database. Pick any location, and start in test mode.
  3. Once created, click the Rules tab and replace the contents with:
    {"rules": {".read": true, ".write": true}} then click Publish. (This keeps it open to anyone with the link — fine for an internal team tool, but ask if you'd rather lock it down further.)
  4. Click the gear icon → Project settings → scroll to Your apps → click the </> (web) icon → register the app (any nickname) → copy the firebaseConfig object it shows you.
  5. Open this HTML file in a text editor, find const FIREBASE_CONFIG = { near the top of the script, and paste your values in over the YOUR_... placeholders. Save, re-upload to your web host, and reload the page.
  6. For file/photo attachments: in the Firebase console left sidebar under Build, click Storage → Get started → accept the defaults. Then click the Rules tab and replace the contents with:
    rules_version = '2';
    service firebase.storage {
      match /b/{bucket}/o {
        match /{allPaths=**} {
          allow read, write: if true;
        }
      }
    }     then click Publish. No extra config values needed — it uses the same firebaseConfig block above.

Assignable names

Unit Equipment ID Circuit Event Type Headline Schedule Date NDE Vendor Status Assigned To Notes Files
Edits and uploaded batches save to the shared tracker backend and sync to everyone viewing this page. Uploading a batch skips any circuit/vessel already in the tracker (same Unit + Equipment + Circuit + Event Type) — existing entries and their status/assignment/notes are never overwritten.