{"statusCode":200,"headers":{"x-powered-by":"Express","access-control-allow-origin":"*","access-control-allow-methods":"GET, POST, OPTIONS","access-control-allow-headers":"Content-Type","accept-ranges":"bytes","cache-control":"public, max-age=0","last-modified":"Fri, 19 Jun 2026 21:06:57 GMT","etag":"W/\"7a8e-19ee1b55168\"","content-type":"text/html; charset=UTF-8","content-length":"31374"},"isBase64Encoded":false,"body":"\n\n\n \n \n GOLEM - Gas-tank Operational Levels: Equipment Monitor\n \n\n\n
\n

🗿 GOLEM

\n

Gas-tank Operational Levels: Equipment Monitor | MCS Automated GTM SIM Updates (3-hour cycle)

\n\n \n
\n

📋 Setup Instructions (click to expand)

\n
\n

To keep GOLEM running, your team needs:

\n\n
    \n
  1. \n Install the GOLEM Data Push Tampermonkey script
    \n Install Tampermonkey extension if you don't have it:\n tampermonkey.net
    \n Then install the GOLEM data push script:\n Install GOLEM Data Push Script\n
    2. \n\n
  2. \n Keep AAP Fleet Monitoring open in a browser tab
    \n Open AAP Fleet Monitoring
    \n The script runs in the background on this page — pushes data to GOLEM every 30 minutes and immediately on page load. No user action needed.\n
    3. \n\n
  3. \n At least one person per shift should have AAP open
    \n Multiple people can have it open — that's fine, it just means fresher data. If there's a gap between shifts (e.g., everyone closes for an hour), GOLEM uses the last data it received and continues posting updates normally. When the next shift opens AAP, fresh data flows immediately.\n
    4. \n\n
  4. \n Update the Active GTM Sites list regularly
    \n Sites enter and leave GTM gridlock throughout the day. To update GOLEM's site list:\n
      \n
    1. Go to the Gas Tank Model QuickSight Dashboard
      2. \n
    2. Select the \"Current State\" tab
      3. \n
    3. Download the CSV (click the export/download icon on the table)
      4. \n
    4. Open the CSV and copy the Site ID column for all sites at or above 85% utilization
      5. \n
    5. Paste the site codes into the \"📍 Active GTM Sites\" box below (comma-separated, e.g., SAT3, ATL2, DFW7)
      6. \n
    6. Click Update Sites — the Tampermonkey script will pick up the new list on its next cycle
      7. \n
    \n Do this whenever the GTM dashboard changes (typically every few hours during peak events).\n
    5. \n\n
  5. \n GOLEM itself runs 24/7 in AWS — no one needs to keep this dashboard open
    \n This UI is just for visibility, manual triggers, and site lookups. The automated 3-hour SIM updates happen in the background regardless of whether anyone is viewing this page.\n
    6. \n\n
  6. \n Verify data is flowing
    \n The \"Cached Sites\" count in the status bar shows how many sites have data. You can also check the 🗿 indicator in the bottom-left of the AAP page — it confirms the script is active. Click it to force an immediate push.\n
    7. \n
\n\n
\n 🗿 How it works:\n Tampermonkey (on AAP page) fetches damaged trailers + hostlers every 30 min → pushes to GOLEM in AWS → GOLEM posts MCS updates to GTM SIMs every 3 hours automatically.\n
\n\n
\n Edge cases:\n
    \n
  • Gap between shifts? GOLEM uses last received data (valid for up to 3 hours). Updates still post.
    • \n
  • Multiple people have AAP open? Great — more pushes = fresher data. No conflicts.
    • \n
  • Someone refreshes AAP? Also fine — script pushes fresh data immediately on page load.
    • \n
  • GOLEM will never post fake/mock data to a real SIM. If data is too stale, it skips until fresh data arrives.
    • \n
\n
\n
\n
\n\n \n
\n

System Status

\n
\n
-
Open GTM SIMs
\n
-
Over Damage Threshold
\n
-
Sites Tracked
\n
3h
Update Cycle
\n
\n
\n \n \n \n
\n
\n
\n
\n\n \n
\n ⚠️ Confirm user is connected to VPN before using GOLEM\n
\n\n \n
\n

📍 Step 1: Enter GTM Sites

\n

Enter site codes to monitor. Download the CSV from the GTM Dashboard (Current State tab) and paste Site IDs here. You can also add individual sites (e.g., SDF9) at any time.

\n

⚠️ This is a shared list — updating it replaces the previous list for all users.

\n
\n \n \n
\n
\n
\n\n \n
\n

🔍 Step 2: Site Lookup

\n

Enter a site code to see current damaged asset status — trailer/hostler counts, work request details, vendor assignments, and repair descriptions. Data pulled directly from TEDS.

\n
\n \n \n
\n
\n
\n\n \n
\n

📋 Step 3: Generate MCS Update (Copy & Paste)

\n

Generate the formatted MCS status update for a site, then copy and paste into the GTM SIM. Includes damaged trailer count, work request states, vendor assignments, and repair details.

\n
\n \n \n
\n
\n
\n ✅ Update generated — copy and paste into the SIM\n \n
\n 
\n      
\n    
\n      
\n      
\n    \n  \n\n  \n  
\n    
\n      
📊 Performance Metrics (Leadership View)
\n      
\n    
\n  
\n\n  \n  
\n    📊\n    
\n      \n      \n    
\n  
\n\n  \n\n\n"}