Skip to main content

Tools Site

The Iron Horse tools site is the authenticated internal dashboard surface for operational tools that read from BIRCH, Trackage, POD Tracker, and related Iron Horse systems.

Production URL: https://tools.ihrailsoftware.com

Most pages require Iron Horse Google SSO and an app permission grant. Super admins can manage app permissions from the admin area.

Current tool pages​

POD Tracker​

URL: https://tools.ihrailsoftware.com/pod-tracker

Purpose: Promise of Delivery planning and monthly production tracking.

Primary functions:

  • Shows cars projected out for a selected month.
  • Pulls BIRCH work order, status, labor, material, estimate, invoice, and projected-out-date information.
  • Tracks operational categories and follow-up notes.
  • Supports drill-downs for invoiced cars, completed cars, completed-not-invoiced cars, and remaining cars.
  • Provides POD updates through authenticated API routes.

Primary data sources:

  • birch.workorder
  • birch.workupdates
  • birch.statuscode
  • birch.railcar
  • birch.owner
  • birch.joblist
  • birch.time_log
  • pod_tracker support tables for notes/categories/goals

Car Date Tracker (CDT)​

URL: https://dashboard.ihrailsoftware.com/car-date-tracker

Purpose: Tracks closeout milestone dates for the current active BIRCH work order on cars in the CDT status scope.

Primary functions:

  • Lists only each car's latest active BIRCH work order when the latest status is 750 or 799+, excluding 999, TEMP*, and MITH* cars.
  • Shows the current BIRCH status code and title directly with the car number.
  • Lets authorized CDT editors use the pencil control and modal dropdown to append a new BIRCH status.
  • Protects status edits with the exact current BIRCH work_id, active-work-order checks, trusted-origin enforcement, and stale-status conflict detection.
  • Adds a BIRCH work-order audit comment containing the Central date/time, prior status, new status, authenticated actor, and CDT source; the BIRCH source column is Car Date Tracker.
  • Tracks Final Sent, Invoice Sent, Dispo Received, and Car Released dates with append-only audit comments.
  • Provides BIRCH comments and private CDT-only internal notes for the selected work order.

Primary data sources:

  • birch.workorder for the exact current active car/work-order identity
  • birch.workupdates for current status, status changes, and BIRCH comments
  • birch.statuscode for status dropdown codes/titles
  • birch.user for authenticated actor attribution
  • pod_tracker.car_date_tracker_dates and append-only CDT event/note tables

A CDT status change is a real BIRCH status movement. The audit comment uses the pattern 8/20/2026 @ 3:45 PM - 750 -> 799 - Employee Name - CDT. If another process changes the BIRCH status after the page was loaded, CDT rejects the stale save and refreshes the row instead of overwriting the newer status.

RAPID​

URL: https://tools.ihrailsoftware.com/RAPID

Purpose: RAPID/waybill and inbound railcar visibility workflow.

Primary functions:

  • Displays RAPID waybill/inbound car data.
  • Supports BIRCH model-order creation workflows where enabled.
  • Helps identify inbound equipment and operational records that need attention.

Primary data sources:

  • RAPID API/server routes on the Iron Horse API server
  • BIRCH work order and railcar tables for represented cars
  • Trackage/AEI context where available

Workforce Planning​

URL: https://tools.ihrailsoftware.com/public/workforce.html

Purpose: Labor and department workload planning.

Primary functions:

  • Summarizes estimated, actual, projected, and remaining hours by production department.
  • Shows department-level workload and car counts.
  • Uses active BIRCH work orders and time logs to support staffing and planning decisions.

Primary data sources:

  • birch.joblist
  • birch.jobcode
  • birch.job_or_revenue_category
  • birch.workorder
  • birch.workupdates
  • birch.time_log
  • birch.crews

Category Settings​

URL: https://tools.ihrailsoftware.com/public/category-settings.html

Purpose: Admin/configuration page for POD Tracker category behavior.

Primary functions:

  • Manages category configuration used by the POD Tracker.
  • Requires authenticated access and category-settings permission.

Primary data sources:

  • pod_tracker configuration tables
  • Authenticated API routes on the Iron Horse API server

Status Tracker​

URL: https://tools.ihrailsoftware.com/status-tracker

Purpose: Tracks cars that moved into BIRCH status 170 — CUSTOMER SERVICE HANDLING during a selected reporting period.

Default date range: current calendar week, Sunday through Saturday.

Other date filters:

  • Calendar month and year selector
  • Custom from/to date pickers

Top cards:

  • Cars moved to status 170 in the selected period
  • Cars currently under inspection, status 151

Main table columns:

  • Car Number
  • Work Order
  • Arrival Date
  • Date Estimate Was Done
  • Employee That Did Inspection
  • Employee That Did Estimate

Behavior:

  • All columns are sortable by clicking the table header.
  • The page auto-refreshes every 60 seconds while preserving filters, search, and sort.
  • Clicking the car number opens a modal showing status history for that selected work order only.
  • The modal shows chronological status changes with status code, status name, changed-by user, and date/time.

Primary data sources:

  • birch.workupdates for status movements
  • birch.workorder for car and work order details
  • birch.statuscode for status names
  • birch.user for the employee who changed the status

Important implementation detail: the modal status history must be filtered by the selected work_id and work_order, not by car number alone. Some cars have multiple yard visits/work orders, and car-wide history would mix visits.

Direct Hours Tracker​

URL: https://tools.ihrailsoftware.com/department-hours-report

Purpose: Compares direct and indirect timeclock hours with effective-dated direct-hours goals for Cleaning, Valve, Paint, Repair, and PD, with a plant-wide Total.

Primary functions:

  • Defaults to the current calendar month and supports month/year selection.
  • Shows Employees Working / Assigned for each department and Total. Assigned means the current active direct roster; Working means a member of that roster with any timeclock entry in the selected month.
  • Clicking a ratio opens Working and Not Working employee lists. The Total popup groups those lists by department.
  • Calculates Goal Direct Hours from employees working and the effective daily-goal rate for each Monday–Friday date in the selected month.
  • Lets scheduler editors and super admins adjust a department's daily goal for the current month. The server applies the change on the current America/Chicago plant date; it carries forward through month end until a later edit and resets to the 8-hour baseline in a new month.
  • Preserves append-only adjustment history with the authenticated actor.
  • Shows Direct Hours, Indirect Hours, aggregate Percentage from Goal, and a working-employee-weighted Total daily goal.
  • Uses the same scheduler/POD Tracker permission boundary while the tracker remains a standalone page.

Primary data sources:

  • birch.time_log for month participation and completed direct/indirect hours
  • birch.crews for current active direct department assignments
  • pod_tracker.dht_daily_goal_adjustments for append-only effective-dated department goals

Direct time is classified by a null indirect_labor_id; indirect time has an indirect_labor_id. Hour totals require completed entries, while Working status uses any selected-month entry. BIRCH does not currently preserve effective-dated crew assignment history, so historical Assigned values reflect the current active direct roster when the report is loaded.

Admin and permissions pages​

URLs:

Purpose: Super-admin management for users, permissions, dashboards, and app access.

Primary functions:

  • Manage authorized users.
  • Approve or deny pending users.
  • Grant app-level access such as scheduler, rapid, workforce, and category-settings.

TV and shop-floor display pages​

URLs include:

Purpose: Read-only shop-floor/TV displays for labor, department, revenue-recognition, leaderboard, and scoreboard views.

Primary data sources:

  • BIRCH labor/time-log data
  • BIRCH work orders and job/revenue categories
  • Iron Horse API server summary endpoints

Pi Manager / Dashman​

URLs:

Purpose: Admin-managed dashboard/kiosk tooling for Raspberry Pi or display clients.

Access: admin-only.

Detailed operations guide: Raspberry Pi TV Displays

The Pi TV Displays guide covers the bill of materials, SD-card flashing, first-boot setup, kiosk client scripts, Pi Manager asset queues, department dashboard URLs, Tailscale access, troubleshooting, and the process for adding new TV display items.

Operational notes​

  • The live tools app is served from /home/ubuntu/api-server on the Iron Horse API server.
  • Main PM2 process: ironhorse-api.
  • Most page routes are implemented in /home/ubuntu/api-server/src/index.ts and compiled to /home/ubuntu/api-server/dist/index.js.
  • Static pages live under /home/ubuntu/api-server/public/.
  • For changes, edit TypeScript/source HTML, run npx tsc --noEmit, compile with npx tsc, restart ironhorse-api, and verify the live route.
  • Do not document database passwords, API tokens, private keys, OAuth secrets, or raw credential URLs.