Applied The OFCI Playbook

The Delivery War Room

Last reviewed

Advanced

What you'll learn

~50 min
  • Build a multi-project delivery calendar with date-based scheduling
  • Implement conflict detection for overlapping deliveries, crane availability, and staging constraints
  • Generate delivery day checklists with logistics requirements per equipment type
  • Export delivery schedules to HTML calendar views and ICS files

What you’re building

Here’s your next month: two generators arriving at SV9 on a flatbed that needs a 200-ton crane. A switchgear lineup coming to CH2 that requires a clear path from the loading dock through two corridors into the electrical room — and nobody’s measured the corridors yet. Twenty CRAHs showing up at DEN3 over three days that need staging space on the second floor. Oh, and the SV9 generator delivery? Same day the GC planned their concrete pour for the adjacent pad. Because of course it is.

Now, you’re currently tracking all of this in your head, in a shared Excel calendar that three people update inconsistently, and in a text thread with your rigger that you can’t find because it’s buried under 47 other conversations. That’s not a system. That’s a prayer.

If any of these deliveries collide — two pieces of equipment showing up on the same day at the same site when there’s only one crane available, or a delivery arriving when there’s no staging space because the previous delivery hasn’t been moved to final position — you can incur standby charges each day; use your vendor’s quoted rate. Plus schedule delays that ripple across the entire project like dominoes falling in slow motion while your PM sends you the Slack message nobody wants to get: “can we jump on a call?”

The Delivery War Room catches those collisions before they cost you money.

💬Delivery day is game day

Delivery day is game day. You’ve been tracking this equipment for months — submittals, lead times, budget approvals — and now the truck is pulling up. You need the right people (crane operator, rigger, electrician for the switchgear), the right access (dock reserved, corridors cleared, elevator locked out for freight), and the right timing (you can’t receive a chiller at 3 PM when the crane leaves at 4 PM). It’s like a drop day at the ABC store except the bottles weigh 40,000 pounds and you’re paying standby fees by the day if you’re not ready. This tool is your game-day playbook.

By the end of this lesson you’ll have a Node.js CLI tool that manages delivery schedules across multiple projects, detects conflicts and resource constraints before they become expensive phone calls, generates equipment-specific delivery day checklists so you don’t forget the one thing that screws everything up, and exports calendar views you can actually share with your GC without them saying “what am I looking at?”

ℹSoftware pattern: Resource-constrained scheduling with conflict detection

Delivery schedule + resource constraints (crane, staging, dock access) → conflict detection → resolution suggestions + logistics checklists. This pattern works for any resource-constrained scheduling: conference room booking, fleet management, construction sequencing, event logistics.


The showcase

This is the part where you see the whole tool laid out and think “holy shit, I’ve been doing all of this manually.”

  • Input: CSV with delivery dates, equipment types, site logistics requirements (crane needed, staging space, dock access hours). All the details you currently keep in six different places.
  • Conflict detection: Flags same-day deliveries at the same site, crane double-bookings, staging space overflows, and GC activity conflicts. Basically a referee for your delivery schedule that doesn’t care about anyone’s feelings.
  • Delivery checklists: Equipment-specific logistics requirements. Because a generator delivery (crane + flatbed + rigging crew + electrical disconnect) is a fundamentally different animal than a CRAH delivery (freight elevator + dollies + raised floor clearance). Generic checklists are how you end up with a chiller on a truck and no one who knows how to handle refrigerant.
  • Calendar view: HTML monthly calendar with color-coded delivery blocks per project. The thing you’ll pull up on your tablet when the GC asks “so what’s coming in next week?”
  • ICS export: Calendar events with full logistics details in the description, so your crane operator gets an invite that actually tells them what they’re picking up and how heavy it is.

Before you start

If your agent is still open from the previous lesson, exit that session first (/exit or Ctrl+D). Create a clean folder for this lesson and open it:

Terminal window
mkdir -p ~/ofci-playbook/06-delivery-war-room && cd ~/ofci-playbook/06-delivery-war-room

In Windows PowerShell:

Terminal window
mkdir ~/ofci-playbook/06-delivery-war-room; cd ~/ofci-playbook/06-delivery-war-room

Or open the folder directly in your desktop agent app. Start your agent the way Workbench Setup showed.

Switch to plan mode

Switch to Plan mode inside your session (Shift+Tab, /plan, or the mode picker) so the agent confirms your site conflict rules and equipment checklist requirements before generating files.

The conversation

Say what you want

Ask for the multi-project delivery coordinator in plain English:

I coordinate equipment deliveries across three data center sites. Help me build a tool called delivery-war-room that flags delivery conflicts, builds equipment-specific checklists, and exports HTML and ICS calendars. Ask me what you need first.

Answer its questions

Guide the agent’s questions with the logistics constraints for your sites:

If it asksYou might say
What conflict types should it detect?Same-site same-day window overflow, crane double-bookings, staging area overflow over 2000 sqft, dock window collisions, and GC activity conflicts.
Are crane conflicts site-specific or portfolio-wide?Site-specific only: flag a crane conflict when two deliveries at the same project need a crane on the same date.
How should delivery day checklists work?Generate equipment-specific Markdown checklists for generators, switchgear, chillers, CRAHs, UPS, and PDUs.
Which projects and sample deliveries should it include?Create sample CSVs in data/ for SV9, CH2, and DEN3 with 5 to 8 deliveries each, including intentional conflicts.
Which subcommands should the CLI support?calendar, conflicts, checklist <delivery-id>, week, export-html, and export-ics.
ℹReference notes to hand the agent (or check against)click to expand

Use these CSV columns across data/sv9-deliveries.csv, data/ch2-deliveries.csv, and data/den3-deliveries.csv: delivery_id, project, equipment_type, description, vendor, delivery_date, delivery_window, crane_required, crane_tonnage, staging_area_sqft, dock_access, rigging_required, estimated_hours, gc_coordination, status, notes

  • delivery_window values: AM (7am-12pm), PM (12pm-5pm), FULL (7am-5pm)
  • status values: scheduled, confirmed, in-transit, delivered, delayed, rescheduled
  • Staging limit: 2000 sqft per site per day (placeholder staging capacity; set it for your site)
  • Equipment-specific checklists:
    • Generator: crane booking confirmation, flatbed route clearance, rigging crew scheduled, electrical disconnect verified, fuel tank empty for transport, EPA containment pad ready
    • Switchgear: corridor clearance measured, floor load capacity verified, electrical room access clear, rigging plan approved, temporary power available for testing
    • Chiller: crane booking, pipe connections prepped, isolation valves closed, refrigerant handling crew on standby, commissioning agent scheduled
    • CRAH: freight elevator reserved, raised floor clearance verified, dolly and pallet jack available, data hall power and piping ready
    • UPS: battery room ventilation verified, battery delivery separate from frame, rigging path clear, DC plant coordination
    • PDU: freight elevator access, rack row clearance, whip connections prepped
  • Packages: commander, csv-parse, cli-table3, and chalk@4 (chalk 5 and later are ES-module-only and break require()).

Read the plan

Before approving the plan, check four things:

  1. Same-site conflict scoping: All five conflict checks (window hours overflow, crane double-booking, staging overflow past the 2000 sqft placeholder, dock window overlap, and noted GC activity conflicts) compare deliveries within the same project on the same delivery_date.
  2. Actionable conflict output: Each flagged conflict reports its severity (warning vs. critical), the delivery IDs involved, and a concrete resolution suggestion.
  3. Equipment-specific checklists: checklist <delivery-id> matches equipment_type (generator, switchgear, chiller, crah, ups, pdu) rather than printing a generic list.
  4. Standalone HTML and ICS exports: export-html writes a self-contained monthly calendar with inline CSS (SV9 blue, CH2 green, DEN3 orange, red border on conflict days), and export-ics writes calendar events with logistics details.

If the plan checks crane or staging conflicts across different sites on the same day, fix that before approving:

Only flag crane, staging, and dock conflicts when two deliveries share both the same project code and the same delivery_date.

Approve the plan once all four items are covered, and ask the agent to save a Git checkpoint after the build works.


What you get

Fire it up

Ask your agent to install what is needed, scan all three sites for delivery conflicts, and generate a delivery-day checklist:

Install what the tool needs, run conflicts and week across SV9, CH2, and DEN3, and generate the delivery checklist for SV9-DEL-001.

If you prefer running the commands in a terminal yourself:

Terminal window
cd delivery-war-room
npm install
node src/index.js conflicts
node src/index.js week
node src/index.js checklist SV9-DEL-001

The conflicts command is the one that earns its keep immediately — it shows you every scheduling collision across your entire portfolio before any trucks roll. That crane double-booking on the 15th? Found it. That CRAH delivery scheduled the same day the GC is pouring the second floor slab? Caught it. The week command is your Monday morning briefing: here’s what’s coming in this week, across all sites, no surprises. And checklist gives you a printable, equipment-specific logistics plan for delivery day so you’re not standing in the parking lot going “wait, did anyone book the rigging crew?”

If something is off

ProblemFollow-up prompt
Conflict detection misses same-day deliveriesThe conflict detector isn't finding deliveries on the same date at the same site. Compare the calendar date (YYYY-MM-DD) without time-of-day offsets and flag any two deliveries that share both project code and delivery_date.
HTML calendar doesn’t render properlyThe HTML calendar file shows broken layout when opened from disk. Keep all styling self-contained inside the HTML file so the calendar renders cleanly in a browser without a server.
Checklists are generic for all equipmentEvery delivery gets the same generic checklist regardless of equipment type. Select the checklist template using the equipment_type column (generator, switchgear, chiller, crah, ups, pdu) and fall back to a generic checklist for unknown types.

🔧

When Things Go Wrong

Use the Symptom → Evidence → Request pattern: describe what you see, paste the error, then ask for a fix.

Symptom
The crane conflict detection flags deliveries at different sites
Evidence
A generator delivery at SV9 and a chiller delivery at CH2 on the same day are flagged as a crane conflict, but they're at different sites with different cranes
What to ask the AI
"Crane conflicts should only be flagged for deliveries at the SAME site on the same date. Each site has its own crane arrangements. Fix the conflict detection to check both delivery_date AND project code match before flagging a crane conflict."
Symptom
The week command shows the wrong week's deliveries
Evidence
Running 'week' on a Monday shows deliveries from last week instead of this week
What to ask the AI
"The week command should default to showing the current Monday through Sunday. Calculate the start of the current week (most recent Monday) and filter deliveries where delivery_date falls between Monday and Sunday inclusive. If --date is specified, show the week containing that date."

How it works (the 2-minute explanation)

Let’s walk through what’s actually happening, because “conflict detection” sounds fancy but it’s honestly pretty straightforward logic — just logic you don’t want to do in your head while managing three active sites.

  1. CSV loader reads delivery schedules from all your project files and merges them into one unified timeline. This is the step that replaces your shared Excel calendar that Dave keeps saving over with his version. One source of truth, all projects, no merge conflicts.
  2. Conflict detection cross-references every delivery by date, site, and resource requirements. It checks five things: same-day same-site collisions, crane double-bookings, staging space overflows, dock access conflicts, and GC activity overlaps. For each conflict, it tells you exactly what’s clashing and suggests how to fix it. It’s doing the spatial and temporal reasoning that you currently do in your head while driving between sites — except it doesn’t miss things because it’s not also thinking about lunch.
  3. Checklist generator knows that a generator delivery and a CRAH delivery are completely different animals. Generator needs a crane, rigging crew, EPA containment pad, and someone to verify the electrical disconnect. CRAHs need a freight elevator reservation, dollies, and raised floor clearance. The tool selects the right checklist for the equipment type and formats it as a printable Markdown document with checkboxes you can actually check off on your tablet in the field.
  4. Calendar renderer maps everything onto a monthly grid with color-coding by project and red borders on conflict days. This is what you pull up when the GC asks “what do we have coming in?” and you want to look like you have your shit together. Which, now, you actually do.

Customize it

Once this is running, you’re going to immediately think of two things you wish it did. Here are the obvious ones.

Add delivery status tracking

Add a track <delivery-id> --status <status> --notes <text> subcommand that persists status updates to the project CSV, plus a dashboard view counting deliveries across scheduled, confirmed, in-transit, and delivered.

Add weather integration

Check forecasts against your crane manufacturer’s wind limit (25 mph below is a placeholder) using a weather API your project is licensed to use (api.weather.gov is free for any purpose; Open-Meteo’s free API is for non-commercial use only, so a work tool needs its paid licence):

Add a --weather flag to the week command that queries api.weather.gov, caches results, and flags delivery dates with over 50% rain probability or wind speeds above a configurable mph limit.

Key takeaways

  • Conflict detection catches costly scheduling mistakes — overlapping deliveries can leave a crane idle and trigger standby charges. Check the schedule before confirming deliveries. Five minutes running this tool on Monday morning saves you that call to your VP where you explain why there’s a standby charge on the invoice.
  • Generic checklists are how things get missed — a generator delivery has exactly nothing in common with a PDU delivery from a logistics standpoint. If your checklist doesn’t know the difference between “reserve a 200-ton crane” and “reserve the freight elevator,” someone’s going to be standing in a parking lot making panicked phone calls at 7 AM.
  • The HTML calendar is your secret weapon for GC coordination — sharing a color-coded calendar with your GC, crane company, and rigging crew gets everyone looking at the same picture. No more “I didn’t know that was coming in Tuesday.” Yes you did. It was on the calendar. The one I sent you. Twice.
  • Portfolio-wide delivery views show you when you’re spread too thin — when you’re managing three active builds, seeing all deliveries on one calendar helps you spot the weeks where you’ve got critical deliveries at two different sites on the same day. There’s no crane conflict, but there’s a YOU conflict — you can’t be in two places at once, and some deliveries need you there personally.

KNOWLEDGE CHECK

The conflict detector flags two deliveries at SV9 on the same day: a 2500kW generator (needs 200-ton crane, FULL day window, 1500 sqft staging) and twenty PDUs (needs freight elevator, AM window, 400 sqft staging). What's the right resolution?


What’s next

You’ve got budgets tracked and deliveries coordinated. Your equipment is arriving on time, to the right site, with the right crew and the right crane. Nobody’s paying standby charges. Nobody’s getting surprised. You look like you have your shit together — because you actually do.

Next up is The Executive Briefing Generator — the tool that pulls data from everything you’ve built so far (RFPs, vendor scores, submittals, lead times, budgets, deliveries) and produces portfolio-level scorecards, risk heat maps, and AI-generated narrative briefings for your VP’s monthly review. This is where the individual tools stop being individual tools and start being an integrated procurement intelligence platform. It’s the answer to “where do we stand?” that doesn’t require you to spend a weekend assembling slides.

intellimetrics · Arlington, VA
© 2026 intellimetrics.net
Search lessons