Industrial & Manufacturing Oil, Gas & Natural Resources Downstream & Refining

Terminal Operations

Capital-intensive extraction and processing programs where safety, regulation, and supply chain complexity define execution.

Kinder Morgan Buckeye Partners NuStar Energy Magellan
Inside this journey
  1. Pre-Discovery

    Align the room on outcomes, decision process, and constraints before deeper discovery.

    1. Stakeholder Alignment

      Confirm decision roles, timeline, and ‘must have’ outcomes across trading, operations, and compliance stakeholders.

      Alignment Questions

      Quick Start: What Brought You to This Table Today?

      • What immediate event or business pressure prompted this conversation? Options: New pipeline connection, Refinery turnaround/maintenance, Trading opportunity (basis dislocation), Regulatory change or audit, Modernizing legacy systems, Other
      • Who on your team is most eager for change—and what outcome are they pushing for?
      • What timeline do you feel would make this initiative urgent rather than optional? Options: Immediately (weeks), This quarter, Within 3–6 months, 6–12 months, No firm timeline
      • Have you tried any fixes already (manual processes, scripts, interim vendors)? What worked and what didn’t?
      • Which one measurable business result would make prioritizing this project an easy decision for your leadership? Options: Reduce demurrage $/month, Increase trade capture rate, Improve custody reconciliation accuracy, Increase effective throughput, Reduce operator time on scheduling, Other

      If Tanks Could Talk, What Would They Admit?

      • How often do tank availability or spec surprises silently cost you margin or cause missed trades? Options: Daily, Weekly, Monthly, Rarely, Unsure
      • Tell us about the most recent time a tank constraint prevented a shipment or trade—what happened and what were the financial or operational consequences?
      • What are the main reasons tanks become unavailable in your operations? Options: Planned maintenance/turnaround, Contamination/quality hold, Measurement discrepancies, Capacity reserved for other customers, Access/transport corridor constraints, Other
      • How do you currently record and share tank specs (capacity, heating, product compatibility) across teams? Options: Spreadsheet(s), ERP or terminal software, Paper logs, SCADA annotations, Combination, Other
      • How confident are you in those published tank specs when it matters most (trade execution or loadout)? Options: Very confident, Somewhat confident, Not confident, We don’t publish specs reliably

      When Scheduling Breaks, Who Pays the Tab?

      • How often does informal scheduling or last-minute changes create demurrage or missed slot costs? Options: Very often, Often, Occasionally, Rarely, Never
      • Walk me through a typical scheduling request today—from the customer request to final load/receipt. Where are the handoffs?
      • Where do delays or mismatches most commonly occur in that flow? Options: Slot allocation, Pump capacity, Lab verification, Transportation arrival windows, Manual coordination emails/calls, Other
      • How do you currently calculate and bill demurrage, and who owns dispute resolution? Options: Ops bills and disputes, Commercial resolves disputes, Finance handles accounting disputes, Third-party mediator, No formal process
      • How much scheduling flexibility (hours/days) would materially change your ability to capture market opportunities? Options: Same day, 24–48 hours, 3–7 days, Flexible within month, Timing doesn't matter

      What Keeps Your Traders Up at Night?

      • If a significant basis dislocation opened tomorrow, what's the single operational constraint most likely to stop you from capturing it? Options: Tank availability, Blending limitations, Inflexible scheduling, Measurement uncertainty, Transport bottlenecks, Other
      • Share an example of a missed trading opportunity tied to terminal constraints—what value was at stake and what broke down operationally?
      • How central is on-demand blending at our terminal to your trading strategy? Options: Mission critical, Important but not essential, Nice-to-have, Not required
      • Which blend parameters (e.g., density, sulfur, Reid vapor pressure) and tolerances must be met for your trades to be acceptable?
      • How fast does a trader expect a custom blend to be available from request to loadable product? Options: Same day, 24–48 hours, 3–5 days, Longer

      Do You Trust the Numbers That Move Your Money?

      • If a new custody measurement differed from your legacy records during cutover, how serious would the fallout be? Options: Minor reconciliation effort, Significant accounting dispute, Regulatory audit risk, Deal cancellation risk, Unsure
      • Describe your current custody transfer methods and which standards you rely on (gauging, meters, lab protocols, ASTM methods).
      • How often have custody reconciliations led to formal disputes in the last 12 months? Options: None, 1–2, 3–5, More than 5, Unsure
      • What maximum variance (e.g., ppm, percentage) do Finance and Trading accept before an investigation is triggered? Options: <0.05%, <0.1%, <0.5%, <1%, No defined tolerance
      • Who must sign off on any calibration, meter swap, or acceptance criteria during cutover?

      Hidden Complexity: Who and What Will We Actually Have to Connect To?

      • How many 'special' or proprietary integrations (PLCs, vendor gateways, lab systems) will we need to accommodate? Options: None, 1–2, 3–5, More than 5, Unsure
      • List the systems and device classes we would need to integrate with (ERP, pipeline SCADA, specific PLC brands, lab LIMS, loading controllers).
      • Which field instruments or vendors use proprietary protocols that typically require site adapters or vendor support?
      • Which data feeds can you provide in near real time today? Options: Tank gauging, Flow meters, SCADA events/alarms, Lab results, Scheduling/EDI, Billing/ERP, None
      • Who controls network and VPN access for integrations, and how quickly can access be provisioned? Options: Ops/OT team, IT team, Third-party integrator, Site owner (third party), Unsure
      • How tolerant is your operations team for scheduled integration windows that require temporary process changes? Options: Very tolerant, Somewhat tolerant, Limited tolerance, Not tolerant

      Who's At The Table and Who Signs?

      • If we proved a clear ROI on demurrage reduction and trade capture, would your organization accelerate procurement and integration timelines? Options: Yes, immediately, Yes, within current cycle, Depends on budget window, No, timeline fixed
      • Who are the decision-makers and their main priorities (e.g., Trader = margin; Ops = safety; Compliance = reporting)? Please list names/titles if possible.
      • Do you have an executive sponsor and a day-to-day project owner identified? Options: Both identified, Executive sponsor only, Project owner only, Neither yet
      • What procurement, legal, or budget cycles could delay signing a statement of work? Options: Quarterly procurement window, Annual budget cycle, Lengthy legal review, No formal cycles, Other
      • What is your target go/no-go date to begin a pilot or parallel run, and why is that date important? Options: Within 30 days, 30–60 days, 60–90 days, After next budget cycle, Other

      What Would Success Actually Feel Like For Your Team?

      • If this platform became the record of truth, which single business metric must improve within 6 months for you to call it a success?
      • Choose up to three KPIs that will define success for your organization. Options: Demurrage $/month, Trade capture rate, Custody reconciliation variance, Throughput utilization, Scheduling lead time, Operator time spent on coordination, Compliance report accuracy
      • Describe the reconciliation and acceptance workflow Finance and Trading would require during cutover to be comfortable switching the ‘system of record’.
      • What stakeholder testimonials, reports, or sign-offs will be necessary to finalize acceptance?
      • Even if KPIs look good, what lingering concerns could stop you from declaring the project a success?

      What Would Make You Pause — and How Do We Prevent It?

      • What single issue is most likely to cause you to pause or cancel after a pilot (e.g., measurement variance, integration delays, operator resistance)? Options: Measurement discrepancies, Integration complexity, Operator adoption issues, Commercial terms, Regulatory non-compliance, Other
      • Tell us about a past technology project that stalled here—what were the root causes and how long did recovery take?
      • Which contractual protections or SLAs would make leadership comfortable signing (select all that apply)? Options: Measurement accuracy SLA, Integration delivery milestones, Financial penalties for missed deadlines, Support/incident SLA, Acceptance test criteria included, Other
      • How do operators balance ease-of-use versus feature richness—what trade-offs are acceptable? Options: Prefer simplicity first, Need full features even if complex, Balanced approach, Depends on user role
      • What remnants of legacy process are non-negotiable and must remain during transition?

      Small Bets, Big Moves: What Should Our First Pilot Look Like?

      • What minimal pilot would prove value quickly while minimizing accounting and operational exposure? Options: Parallel run on one product/tank, Meter and custody-only reconciliation, Scheduling workflow trial, Blending test on one manifold, Integration smoke test with SCADA, Other
      • What data, systems access, and on-site participants would you commit to for that pilot?
      • Who will be our single point of contact to coordinate operations, IT, and commercial stakeholders during a pilot? Options: Operations manager, IT/OT manager, Commercial lead (trading/shipper), Third-party integrator, Other
      • When could we realistically begin that pilot, and are there blackout windows (turnarounds, audits) we must avoid? Options: Within 2 weeks, 2–4 weeks, 1–2 months, After scheduled turnaround, Other
      • What specific acceptance criteria should we include in the pilot so your team can objectively evaluate success?
      • Any final concerns or constraints we should address in our proposed pilot plan?
    2. Current State Mapping

      Document terminals, transport corridors, tank specs, measurement practices, past custody disputes, and integration constraints.

      Current State

      Quick Snapshot: The Small Set of Facts That Tell the Whole Story

      • Which facilities or hubs are you currently using today for storage, blending, or custody handoffs? Options: Owned terminal(s), Third-party terminal(s), Pipeline hub(s), Rail yard(s), Marine dock(s)/barge, Aggregator/merchant storage, Other (describe below)
      • Which commodity grades do you regularly move through those locations? Options: Crude (light sweet), Crude (heavy/sour), Gasoline, Diesel/ULSD, Jet/Kero, Naphtha, Feedstocks/chemicals, Other (specify)
      • Typical combined monthly throughput (incoming + outgoing) at these sites? Options: < 10k bbl, 10k–50k bbl, 50k–200k bbl, 200k–1M bbl, > 1M bbl
      • Who holds operational ownership of the tanks and gauge records at these locations? Options: We own & operate, Third-party operator manages operations, Leased tanks under our control, Split ownership across parties, Varies by site — explain below
      • If there’s anything unusual about your footprint (shared tanks, hot-taps, cross-leased capacity, embargo windows), summarize it here.

      If This Breaks, Where Will You Feel the Heat?

      • How often does a custody or measurement issue turn into real financial loss (not just paperwork) for your team? Options: Multiple times a year, Once a year, Every few years, Rarely/Never, Unsure
      • Think of the most recent custody dispute or measurement discrepancy — what was the primary cause? Options: Gauge error (manual), Instrumentation drift/prover issues, Sampling/split-sample disagreement, Documentation/EDI mismatch, Commingling or contamination, Other (describe)
      • How long did the last major dispute take to resolve, and who bore the financial or contractual burden? Options: Resolved <1 week, 1–4 weeks, 1–3 months, >3 months, Still unresolved
      • When measurement disagreements happen, who typically escalates (trader, terminal ops, quality lab, legal)? Options: Commodity trader, Supply chain/operations, Terminal operator, Quality/lab, Commercial/legal, Other
      • How does a custody dispute feel for your team (time sink, reputational risk, lost margin, operational chaos)? Give an example of the impact.

      Where The Pipes, Rails, and Barges Actually Meet — And Where They Jam

      • If we asked your ops lead whether a sudden 30% volume spike could be handled across your corridors today, what's the honest answer? Options: Yes — confident, Probably, with overtime/contingency, Only on certain corridors, No — would create significant delays, Unsure
      • Which transport corridors do you depend on most and in what priority order? Options: Pipeline (inbound/outbound), Coastal barges/short-sea, Deep-sea marine, Rail (unit trains), Truck (local/regional), Intermodal shuttle
      • What are the top corridor constraints you face (choose up to three)? Options: Draft/berth limitations, Pipeline nomination windows, Railcar/locomotive availability, Truck driver scarcity, Port congestion/soak time, Customs/regulatory delays, Seasonal ice/weather
      • How quickly can you switch receipt or delivery mode (e.g., pipeline → rail → marine) when markets force a reroute? Options: Same day, 48–72 hours, 1–2 weeks, >2 weeks, Not feasible
      • Describe a time when a corridor change either saved you a trade or prevented revenue loss — what enabled it?

      Under the Steel: Tanks, Manifolds, and Measurement That Make or Break Trust

      • Which tank-level and custody-measurement technologies are installed today at your primary sites? Options: Manual sounding, Dipstick/manual gauge, Automatic level/radar, Temperature/stratification sensors, In-line flowmeters (turbine/ultrasonic), Master meter & prover, Laboratory sampling only, Other
      • How frequently are custody transfer instruments calibrated or proved, and who owns that schedule? Options: Monthly, Quarterly, Bi-annually, Annually, Ad-hoc/after issues, No formal schedule
      • What are your tank specs we must know: heated/insulated, internal coating, max working capacity, and any special product compatibility restrictions?
      • Does your blending manifold (or equivalent) support simultaneous multi-grade operations? If yes, what’s the max concurrent grades? Options: No blending manifold, Yes — up to 4 grades, Yes — 5–8 grades, Yes — 9–12 grades, Yes — >12 grades, Unsure
      • Where do you see the biggest blind spots in measurement today (sampling frequency, reconciliation lag, rounding practices, lost metadata)? Options: Sampling frequency, Reconciliation lag, Data lineage/metadata gaps, Manual transcription errors, Prover/calibration gaps, Other (describe)

      Integration Nightmares We Need to Stop Pretending Are 'Just Part of the Job'

      • Which past integration problem(s) caused timelines to slip or pilots to fail? Options: No access to PLC/SCADA, Proprietary field protocols, ERP data model mismatch, Security/IT blocked connectivity, Lab system differences, EDI/partner formatting issues, Other (explain)
      • What systems must we integrate with to make this implementation useful (select all that apply)? Options: Site SCADA/PLC, ERP/financial system, Scheduler/TOS, Pipeline operator API, Lab information management (LIMS), Rail/ship loading control, Third-party custody systems, Custom in-house tools
      • Which field protocols or middleware are in play (e.g., Modbus, HART, OPC UA, custom TCP, REST APIs, EDI)? Options: Modbus, HART, OPC-UA, Proprietary vendor protocol, REST/JSON API, SOAP/EDI, None / manual only, Unsure
      • Who controls credentials, network zones, and firewall rules for field connectivity — and how long does access typically take to approve? Options: Site IT (internal) — days, Site IT — weeks, Corporate security — weeks, Terminal operator — days, Third-party vendor — variable, No formal owner / ad-hoc
      • If we need to deploy an edge agent or remove manual CSV exchanges, what practical constraints should we know (certs, air-gapped networks, vendor approvals)?

      Who Signs Off When Someone Needs to Move Fast (and Who Won’t)?

      • When a market opportunity requires us to onboard a site quickly, who has final authority to approve go-live for custody and accounting? Options: Head of Trading, Supply Chain/Logistics Director, Terminal Ops Manager, Commercial/Legal, Finance/Accounting, Joint sign-off
      • What are your internal governance checkpoints (procurement, safety, compliance, legal) and typical lead times for each? Options: Procurement (days), Procurement (weeks), Safety review required, Regulatory inspection required, Legal/commercial negotiation, No formal checkpoints
      • At what tolerance of measurement variance would trading/finance refuse to accept new platform figures during parallel run? Options: < 0.05%, < 0.1%, < 0.25%, < 0.5%, > 0.5%
      • Who will be the day-to-day owner for reconciliation during transition (ops, trading, finance, or shared)? Options: Operations, Trading desk, Finance/accounting, Shared rota, Third-party reconciler
      • How do decision timelines vary under pressure — can approvals be expedited, and if so, how?

      What 'Perfect' Would Actually Change in Your World (Numbers, Not Promises)

      • If this program succeeded exactly as you needed, which three measurable outcomes would you point to first? Options: Reduced demurrage costs, Fewer custody disputes, Higher schedule adherence, Faster settlement cycles, Better blending margin capture, Lower operational headcount/time
      • What specific demurrage or margin numbers would make you declare success (e.g., reduce demurrage by X%, capture Y bbl/week of spread opportunities)?
      • What are acceptable operational tolerances for scheduling changes and late arrivals (in hours or % of loads)? Options: < 1 hour / <1%, 1–4 hours / 1–5%, 4–12 hours / 5–15%, >12 hours / >15%, Depends on corridor
      • How perfect does custody measurement reconciliation need to be on day one of parallel ops before you’ll reduce contingency holds or payments? Options: Exact parity, Within agreed tolerance (specify), Clear trend of convergence, Not required to reduce holds
      • Which audit or compliance reports must match first (regulatory, tax, customer invoices, internal accounting)? Options: Regulatory reporting, Customer invoicing, Internal accounting, Tax reporting, All of the above

      Next Steps Without Surprises: What We Need From You (and What You'll Get Back)

      • What barriers would cause you to pause or delay starting integration in the next 90 days? Options: Budget approval, Access to field systems, Safety/compliance hold, Labor/union issues, Internal resource bandwidth, Regulatory approvals, Other (explain)
      • Which of the following pilot scopes would most convince you this solution works (pick one)? Options: Single tank + custody meter reconciliation, Full site: inventory + scheduling + billing, Blending manifold + sample reconciliation, Corridor reroute test (pipeline→rail), Parallel accounting for a single product stream
      • What timeline do you realistically need for a pilot to run before you can assess go/no-go (days/weeks/months)? Options: 1–2 weeks, 3–4 weeks, 1–3 months, 3–6 months, Unsure
      • What items do you need on a readiness checklist before committing to a pilot (data feeds, credentials, instrument access, safety permit)? List top three. Options: Data feeds (SCADA/PLC), Credentials/API access, On-site safety permit, Calibration/prover schedule, Operator training slots, Integration testing window
      • Who should be in the room for a kickoff call (names & roles), and who will be our primary technical and commercial contacts?
  2. Customer Discovery

    Clarify desired throughput, blending needs, custody accuracy tolerances, scheduling flexibility, and success signals.

    Discovery Questions

    Start Here: Who You Are and What’s On the Line

    • To begin, which of the following best describes your primary role and responsibility related to storage and scheduling? Options: Commodity Trader / Desk, Supply Chain / Logistics Manager, Terminal Operations Manager, Risk & Compliance, Commercial / Sales, IT / Integration Lead, Other
    • Tell us, in a sentence or two, what outcome you need this quarter that makes terminal capacity or a scheduling platform a priority.
    • Which of these events triggered your interest right now? Options: New pipeline connection, Refinery turnaround / outage, Trading opportunity at hub, Regulatory or compliance change, Persistent terminal congestion, Commercial dispute with terminal, Other
    • What’s the planning horizon your team typically operates on for storage, receipts, and deliveries? Options: Intraday (hours), 1–7 days, 1–4 weeks, 1–3 months, 3+ months
    • Who else needs to be involved or will sign off on changes to terminal capacity, scheduling, or custody systems? Options: Trading/Desk leadership, Terminal operations, Compliance / Legal, Finance / Accounting, Third-party logistics, Customer representatives, Other

    What Would Happen If Tanks Suddenly Disappeared?

    • If tank capacity at a key hub were suddenly unavailable, what would be the first, most serious consequence for your business?
    • How often do capacity shortages, tank allocation conflicts, or unexpected tank quarantines occur today? Options: Daily, Weekly, Monthly, Quarterly, Rarely/Never
    • Give a short example of a recent event where tank unavailability or allocation prevented you from executing a trade or caused operational disruption.
    • When these shortages happen, who absorbs the commercial loss or operational stress most often? Options: Trading desk, Operations, Customers/Shippers, Finance, Split across functions
    • Estimate the typical scale of impact when a missed opportunity occurs due to tank constraints (choose the closest range). Options: <$50k, $50k–$250k, $250k–$1M, >$1M, Prefer not to disclose

    When the Schedule Breaks, Where Does It Hurt?

    • Imagine scheduling was flawless for the next 30 days—what single KPI or outcome on your dashboard would improve first?
    • How would you describe your current scheduling and release process right now? Options: Informal calls / texts, Email and spreadsheets, Basic scheduling software, Dedicated TOS/terminal system, Third-party logistics platform
    • How frequently do late arrivals, missed load windows, or unscheduled changes cause demurrage, stacking, or missed dispatches? Options: Daily, Weekly, Monthly, Occasionally, Rarely/Never
    • Describe one recurring scheduling scenario that regularly blocks a profitable trade or creates customer friction.
    • What scheduling flexibility do you need to avoid those failures (select the closest fit)? Options: Intraday hour-level adjustments, 24–48 hour window flexibility, 3–7 day reschedules without penalty, Flexible within week, Ad-hoc with notice
    • Who typically initiates and owns scheduling changes today? Options: Trading desk, Terminal operations, Customer service, Third-party logistics, Carrier/rail operator

    How Tight Is Your Measurement Tolerance — and What Happens When It’s Not Met?

    • If custody measurement were off by 0.5% consistently across your hub, what would that mean for P&L, relationships, and regulatory exposure?
    • What custody accuracy tolerance do your commercial contracts and regulators require? Options: 0.01–0.1%, 0.1–0.5%, 0.5–1.0%, >1.0%, Unsure
    • Which measurement methods do you currently rely on at receipt and delivery? Options: Tank gauging (strapping), Metering (turbine/ultrasonic), LACT (lease automated custody transfer), Third-party shore/ship survey, Density/temperature compensated meters, Other
    • Tell us about any custody or inventory reconciliations in the last 12 months—how were they found, and how did resolution impact accounting or relationships?
    • What discrepancy threshold would you consider material enough to trigger an escrow, dispute, or holdback during cutover? Options: <0.1%, 0.1–0.5%, 0.5–1.0%, >1.0%, Undetermined
    • How important is having a single source of truth for inventory and custody during parallel operations? (1 = not important, 5 = mission-critical) Options: 1, 2, 3, 4, 5

    Blending: The Opportunity You’re Missing (or Already Capturing)

    • If you could blend on demand to capture every grade spread, roughly how much incremental margin or how many trades per month could you reasonably expect?
    • How often do you require custom blends versus standard terminal grades? Options: Daily, Weekly, Monthly, Occasionally, Never
    • What physical or procedural constraints limit blending today (manifold count, heating, compatibility, lab capacity, paperwork)?
    • Which blend specifications are most critical for your commercial and regulatory acceptance? Options: API gravity, Sulfur content, Reid Vapor Pressure (RVP), Aromatics / Distillation, Color/odor, Other
    • How do you validate a blended batch meets pipeline/receiver specs today? Options: In-line sensors, Lab assay with turnaround, Third-party sampling, Supplier certificates, Post-receipt acceptance
    • What turnaround time for blend validation is acceptable to keep trading and shipping decisions agile? Options: <1 hour, 1–4 hours, 4–24 hours, >24 hours

    How Will You Know We Delivered — The Signals That Matter

    • If we agreed to a deployment today, what outcome in the first 90 days would make you say, 'That was worth it'?
    • What are the top success signals you’ll watch during acceptance? Options: Accurate custody reconciliation, No demurrage incidents, On-time scheduling adherence, Blending accuracy to spec, Operator adoption and reduced manual work, Regulatory reporting accuracy
    • How do you prefer acceptance criteria be structured—metric thresholds, scripted test scenarios, staged commercial cutover, or a mix? Options: Metric thresholds, Scripted test scenarios, Staged/commercial cutover, Mixed approach
    • Who must sign the acceptance certificate or approve go-live from your side? Options: Trading head, Operations manager, Compliance/Legal, Finance/Accounting, IT/Integration, Customer rep
    • What commercial remedies or safeguards would you expect if acceptance KPIs are not met? Options: Payment holdback / escrow, Extended parallel run, Service credits / SLA penalties, Rollback option, Other
    • Which operational KPI thresholds are non-negotiable for you (list the top 2–3 with values if possible)?

    Getting There: Transition, Integrations, and Risks We Must Manage

    • What’s the single biggest fear that would make you hesitate to switch platforms or formalize scheduling with a terminal operator?
    • Which integrations must be live at go‑live for you to operate without manual workarounds? Options: ERP/Accounting, Pipeline SCADA/Telemetry, Tank gauges / PLCs, Railcar / fleet systems, Port/berth handling, EDI / commercial messaging
    • Are there any proprietary field protocols, vendor systems, or legacy devices we should plan for? Please name them and the vendor if possible.
    • What cutover approach best fits your risk tolerance and calendar? Options: Parallel run (preferred), Phased by module, Big bang on a quiet window, Hybrid phased + parallel
    • Which live data feeds and calibration artifacts will we need access to before cutover? Options: Real-time tank levels, Meter pulses & flow data, Temperature/density sensors, Historical custody records, Calibration & certificate logs
    • Who are the internal champions and the likely blockers (names/roles), and how should we engage them to ensure adoption?
    • Realistically, when could your team commit to the integration and training timeline required for a 3–6 month adoption? Options: Immediately, Within 2 weeks, Within 1 month, 1–3 months, >3 months
  3. Solution Experience

    Use the customer’s scenarios to show how integrated inventory, scheduling, blending, and custody workflows deliver the target outcomes and mitigate demurrage and measurement risk.

    Experience Meetings

    • Pre-Experience Alignment & Data Readiness
    • Consequence Quantification Workshop
    • Solution Experience — Inventory & Scheduling Scenario Walkthrough
    • Solution Experience — Blending & Custody Transfer Scenario Walkthrough
    • Validation, Acceptance Criteria & Decision Alignment
    • Agree on calibration approach and numeric acceptance tolerances for custody variance.
    • Introductions & Objectives
    • Customer Ops: Validate incident timelines and confirm any missing incident documentation.
    • Seller: Prepare the demonstration metrics dashboard templates that will display the quantified outcomes during walkthroughs.
    • One-sentence Reconfirm (State → Consequence → Future)
    • Prove that inventory and scheduling integration produces the single-source truth and operational decisions that reduce demurrage.
    • Obtain explicit customer confirmation that the demonstrated outcomes match the defined future state.
    • Identify any integration or configuration gaps needed to reproduce the outcome in production.
    • Seller: Deliver list of required integration endpoints and data transformation rules discovered during the walkthrough.
    • Customer IT/Ops: Schedule instrumentation/SCADA access windows for final testing.
    • Seller: Update scenario configuration with customer feedback and retest any mismatches.
    • Anchor: State → Consequence → Future
    • Demonstrate blending capability and that it produces the required product specs and margin capture opportunities.
    • Prove custody transfer accuracy workflow and reconciliation that mitigates accounting risk.
    • Schedule: Lock dates for the scenario walkthrough sessions and invite necessary stakeholders.
    • Customer Measurement Lead: Provide recent calibration records and identify preferred acceptance tolerances for custody variance.
    • Seller: Draft parallel accounting & calibration runbook for the agreed scenarios.
    • Ops: Schedule a joint calibration window and assign participants for the parallel run.
    • Executive Summary of Evidence
    • Obtain a clear decision to move to Solution Scope or a defined list of remaining evidence requirements.
    • Agree and document measurable acceptance criteria tied to financial/risk thresholds.
    • Assign owners and a timeline for integrations, calibration, and acceptance testing.
    • Seller: Publish a one-page Validation Summary with test results, acceptance criteria, and recommended next steps.
    • Customer: Provide formal sign-off or list of additional evidence required within agreed SLA.
    • Both Parties: Schedule Solution Scope kick-off (date, attendees, initial agenda) if decision is to proceed.
    • Customer and seller agree on crystal-clear current state in one sentence.
    • Consequences are explicitly stated and tied to data sources (invoices, logs).
    • Future state outcome is defined in one sentence and accepted by stakeholders.
    • All required datasets, access, and owners are identified and committed with delivery dates.
    • Customer: Deliver required datasets (inventory snapshots, custody logs, demurrage invoices) to shared workspace.
    • Seller: Prepare scenario mapping document linking each dataset to the platform flows to be demonstrated.
    • Ops: Grant read-only access or arrange sandbox data extracts for scheduled walkthroughs.
    • Recap Current State & Stakes
    • Create an explicit, quantified statement of consequence (money, time, risk) tied to evidence.
    • Prioritize scenario(s) by financial/risk impact to focus subsequent experience effort.
    • Set urgency thresholds that define success metrics for the experience.
    • Finance: Produce a short impact model for selected scenarios (spread capture loss, demurrage per day, measurement variance exposure).
    • One-sentence Current State
    • Scenario Setup & Assumptions
    • Review Historical Incidents
    • Review Quantified Consequences vs. Demonstrated Mitigations
    • Scenario Parameters & Constraints
    • Live Walkthrough — Blending Execution
    • Live Walkthrough — Inventory Synchronization
    • Model Financial Impact
    • Present Proposed Acceptance Criteria & Tests
    • One-sentence Consequence
    • Risk & Compliance Exposure
    • Live Walkthrough — Custody Transfer & Reconciliation
    • Live Walkthrough — Scheduling Conflict Resolution
    • One-sentence Future State
    • Roles, Responsibilities & Timeline to Scope
    • Outcome Metrics & Demurrage Mitigation Proof
    • Calibration & Parallel Accounting Plan
    • Decision & Next Steps
    • Agree Urgency Thresholds
    • Data & Access Checklist
    • Scope & Logistics for Walkthroughs
    • Validation & Forced Confirmation
    • Validation Checkpoint
  4. Solution Scope

    Define modules (inventory, scheduling, blending, custody transfer, compliance), integrations, responsibilities, and measurable acceptance criteria.

    Scope Configuration

    • Install and integrate tank level sensors
    • Calibrate and certify custody transfer flow meters
    • Deploy real-time inventory tracking dashboard
    • Implement electronic custody transfer documentation
    • Integrate ERP and accounting via API
    • Connect pipeline SCADA and telemetry interfaces
    • Deploy blending manifold control and recipes
    • Configure multi-modal loading/unloading controls
    • Commission heated tank temperature control systems
    • Install leak detection and environmental monitoring
    • Enable automated regulatory compliance reporting
    • Train terminal operators on platform operation

    Scope Questions

    Install and integrate tank level sensors

    • How many tanks require level sensor installation or replacement? Options: 1-5, 6-20, 21-50, More than 50
    • What type(s) of level sensing do you prefer or currently use? Options: Radar (non-contact), Guided wave radar, Ultrasonic, Float/shaft encoder, Pressure/transmitter, Other
    • Do the tanks operate in hazardous classified areas (e.g., Class I, Division 1/2)? Options: Yes, No, Unknown
    • Which communication protocols must sensors support for integration (select all that apply)? Options: MODBUS RTU, MODBUS TCP, OPC-UA, 4-20mA/HART, Proprietary serial, Other
    • Are power and network (PoE/ethernet/fieldbus) available at each tank location? Options: Power available only, Power and network available, Network available only, Neither available - need trenching/cabling
    • What accuracy and update frequency are required for level readings (e.g., custody vs operational)?

    Calibrate and certify custody transfer flow meters

    • Which meter technologies are in scope for calibration/certification? Options: Turbine, Coriolis, Ultrasonic, Positive displacement, Orifice/DP, Other
    • Are current meters certified to local custody-transfer standards (e.g., API, OIML, local regulator)? Options: Yes - provide certificates, No, Partially/Some meters only
    • What is the desired certification standard or authority for calibration? Options: API MPMS, OIML, Local regulator, Third-party NMI/accredited lab, Other
    • Provide the typical flow rates and viscosity/product types for meters requiring calibration.
    • Are there preferred windows for onsite calibration to avoid interrupting operations? Options: Day shift, Night shift, Planned shutdown window, Any time with notice
    • Do you require witness or joint acceptance by customer/trader during certification? Options: Yes, No, Maybe - depends on cost

    Deploy real-time inventory tracking dashboard

    • Which inventory KPIs must be visible on day one (e.g., ullage, volume, mass, temperature-adjusted volume)? Options: Ullage, Volume (m3), Mass (tonnes), Temperature-corrected volume, Available free capacity, Other
    • Who will be primary dashboard users (roles)? Options: Operations/onsite, Trading, Supply chain/planners, Accounting, Compliance, Other
    • What refresh rate is required for dashboard data (seconds/minutes)? Options: Real-time (<5s), Near real-time (5-60s), Minute updates (1-5m), 5-15 minute updates, Hourly
    • Do you require role-based views or restricted access to specific products/terminals? Options: Yes, No
    • Are there existing BI/reporting tools to integrate with (e.g., Power BI, Tableau)? If yes, specify.
    • What acceptance criteria define a successful dashboard deployment (e.g., data latency < X, accuracy within Y%)?

    Implement electronic custody transfer documentation

    • Which documents must be digitized for custody transfer (e.g., BOL, QA certificates, meter tickets)? Options: Bill of Lading (BOL), Meter ticket, Quality certificate (lab), Weighbridge ticket, Delivery receipt, Other
    • Do you require digital signatures or e-signature integration for acceptance? Options: Yes - legally binding e-signatures, Signature capture only (non-binding), No
    • Should electronic documents be automatically routed to ERP/accounting and trading counterparties? Options: Yes - both, Only ERP/accounting, Only counterparties, No automated routing
    • Are there jurisdictional or contractual record retention requirements (duration and format)?
    • Do transported modes (rail/truck/barge) require mobile/offline capture capabilities? Options: Yes - mobile/offline required, No - terminal-only capture
    • What dispute-resolution or audit workflows must be supported for contested transfers?

    Integrate ERP and accounting via API

    • Which ERP/accounting systems must be integrated? Options: SAP ECC/S4, Oracle EBS/Cloud, Microsoft Dynamics, IFS, Custom/Proprietary, Other
    • What types of transactions/data should flow to ERP (select all that apply)? Options: Invoicing, Inventory movements, Meter/transfer tickets, Quality certificates, Cost/allocation data, Other
    • Do you require real-time posting to ERP or batched transfers? Options: Real-time, Near-real-time, Daily batch, Custom schedule
    • Are there existing API credentials, sandbox environments, or documentation available? Options: Yes - provide docs/credentials, No - need vendor assistance, Partially
    • Are there special accounting rules (e.g., custody adjustments, rounding, temperature correction journals) we must implement? Options: Yes, No, Unsure - will provide details
    • Who is the ERP owner and what are SLAs for integration support and testing?

    Connect pipeline SCADA and telemetry interfaces

    • Which pipeline SCADA vendors/protocols are in use (e.g., SCADA historian, OPC, Modbus, DNP3)? Options: OPC-UA, MODBUS TCP/RTU, DNP3, Proprietary SCADA, PI Historian, Other
    • What telemetry points are required (e.g., flow, pressure, pump status, valve position)? Options: Flow, Pressure, Temperature, Pump status, Valve position, Other
    • Are there security/firewall or DMZ constraints for exposing SCADA telemetry to the platform? Options: Yes - strict/air-gapped, Yes - DMZ available, No special constraints
    • Do you require historian-level integration for long-term trending or only event/real-time data? Options: Historian and real-time, Real-time only, Event logs only
    • What bandwidth and latency expectations exist for SCADA feeds?
    • Who are the pipeline/SCADA contacts and what change control windows are available for testing?

    Deploy blending manifold control and recipes

    • How many simultaneous product grades must the manifold support? Options: 1-3, 4-6, 7-10, More than 10
    • Do you require automated recipe-based blending or operator-assisted blending? Options: Fully automated recipes, Operator-assisted with guidance, Manual only
    • What blending accuracy and tolerances are needed (e.g., percentage spec, API gravity limits)?
    • Are there existing PLCs/controls to integrate with (brand/model)?
    • Do recipes need version control, approval workflows, and audit trails? Options: Yes - full versioning and approvals, Basic change log only, No
    • Will blending require lab-feedback loops (e.g., real-time quality sampling) or offline QC only? Options: Real-time feedback, Periodic lab sampling, Offline QC only

    Configure multi-modal loading/unloading controls

    • Which transport modes and interfaces are active at the terminal? Options: Pipeline, Marine/barge, Rail, Truck, Intermodal/transload
    • Do loading racks and dock controls have existing remote interfaces (PLC/API) for integration? Options: Yes - PLC/API available, No - manual controls only, Partial
    • What scheduling complexity is required (e.g., multi-leg shipments, composite loads, batch sequencing)? Options: Simple single-leg, Multi-leg scheduling, Composite/batch sequencing, Complex constraints
    • Are driver/mobile workflows and check-in/out processes required for truck loading? Options: Yes - mobile check-in required, No - terminal staff handle
    • What safety interlocks or permissives must be enforced by the system before dispensing? Options: Hose grounding, Tank level interlocks, Product compatibility checks, Emergency stop, All of the above
    • What acceptance criteria define successful loading control integration (throughput rates, error rate thresholds)?

    Commission heated tank temperature control systems

    • Which tanks require temperature control and what target temperature ranges?
    • What heating systems are installed (steam coils, electric heaters, thermal oil)? Options: Steam coils, Electric heating, Thermal oil, External heat trace, Other
    • Do temperature controls need to integrate with inventory and custody calculations (temperature correction)? Options: Yes - integrate and correct volumes, No - independent monitoring only
    • Are there explosion-proof or hazardous-area requirements for control panels and sensors? Options: Yes - Ex-rated required, No
    • What level of automated control is required (PID closed-loop, scheduled setpoints, manual overrides)? Options: PID closed-loop, Scheduled setpoints, Manual with alarms
    • What commissioning tests and acceptance criteria are expected (temperature stability, response time)?

    Install leak detection and environmental monitoring

    • Which environmental sensors are required (soil, groundwater, vapor, perimeter gas, fencing alarms)? Options: Soil/groundwater sensors, Vapor detectors, Perimeter gas detection, Tank bottom leak detection, Stormwater/runoff monitors, Other
    • Do you currently have a leak detection vendor/system that must be integrated or replaced? Options: Integrate existing, Replace with new system, No current system
    • What alarm thresholds and notification workflows should be configured for environmental events?
    • Are environmental monitoring systems required to generate regulatory reports automatically? Options: Yes, No, Partial
    • What site access and sensor maintenance windows are available for installation? Options: Normal business hours, Night/weekend work allowed, Planned shutdown windows only
    • Do you require integration with local emergency response or security systems? Options: Yes - integrate alarms/locks, No
  5. Mutual Commit

    Finalize commercial terms, integration responsibilities, calibration plans, acceptance criteria, and risk mitigations for transition.

    Agreement Modules

    • Statement of Work (SOW)
    • Master Services Agreement (MSA)
    • Commercial Terms & Pricing
    • Billing & Payment Schedule
    • Integration Responsibility Matrix
    • Data & API Access Agreement
    • Calibration & Custody Acceptance Plan
    • Acceptance Criteria Sign-off
    • Risk Allocation & Mitigation Schedule
    • Insurance & Indemnity Certificates
    • Implementation Timeline & Milestones
    • Change Order & Scope Management
    • Go/No-Go & Cutover Authorization
    • Parallel Accounting & Reconciliation Plan
    • Training & Operator Competency Commitment
    • Support & Service Level Agreement (SLA)
    • Compliance & Regulatory Reporting Addendum
    • Termination & Transition Plan
    • Confidentiality & Data Protection Agreement (NDA/DPA)
  6. Deployment

    Operationalize rollout with readiness checks, enablement, and outcome validation.

    1. Pre-Deployment Readiness

      Confirm data feeds, instrumentation access, test windows, parallel accounting plan, and owners for integrations and calibration.

      Readiness Questions

      Quick Snapshot: Who You are and what's top of mind

      • What is your role and primary responsibility for terminal, storage, or scheduling decisions? Options: Logistics Director, Commodity Trader, Supply Chain Manager, Terminal Operations Manager, Commercial/Trading Ops, Procurement, Other
      • Which best describes your organization? Options: Refinery, Fuel distributor/wholesaler, Crude oil producer, Petrochemical company, Third‑party logistics/terminals, Trading firm, Other
      • Which commodities will you be moving or storing at this location? Options: Crude oil, Gasoline, Diesel, Jet fuel/kerosene, NGLs, Feedstocks, Blended products, Other
      • What triggered this search for terminal capacity or a new operating model? Options: New pipeline connection, Refinery turnaround, Trading opportunity / basis dislocation, Seasonal peak shipping, Regulatory/compliance change, Chronic tank unavailability, Other
      • How soon do you need usable capacity or a working solution? Options: Immediately (<1 month), 1–3 months, 3–6 months, 6–12 months, Flexible / exploratory
      • Which outcomes would signal a successful engagement for you? (pick all that apply) Options: Guaranteed tank availability on key dates, Flexible scheduling windows, Measurement accuracy within tolerance, Blending capacity for custom grades, Seamless ERP/SCADA integrations, Minimal demurrage exposure, Clear ownership of integration tasks

      Why this feels urgent — what happens if this fails?

      • If you couldn’t secure reliable storage or throughput at this hub, which business outcome would be most at risk? Options: A critical spread trade, Scheduled refinery feedstock delivery, Avoiding demurrage costs, Customer deliveries / service levels, Regulatory compliance, Other
      • How often in the last 12 months have storage constraints or terminal issues directly affected a trade or shipment? Options: Multiple times per month, Monthly, Quarterly, A few times a year, Never
      • When those issues happen, how does it typically feel inside your team—annoying, costly, embarrassing, or something else? Options: Annoying but manageable, Costly and escalates to finance, Creates cross‑team finger‑pointing, Threatens customer relationships, Other
      • Can you describe a recent incident where a terminal limitation or scheduling delay created measurable impact? Please include what went wrong and the financial or operational consequence.
      • Who needs to be reassured internally for this project to move forward (roles and level of concern)? Options: Trading desk, Supply chain/ops leadership, Finance/accounting, Quality/compliance, Field operations, IT/OT, Other

      Where capacity and timing really get tested

      • What is the peak throughput rate you'd want this terminal to reliably support (bbl/day or MT/day)?
      • How variable is your expected throughput—do you plan steady receipts/deliveries or big, infrequent moves? Options: Steady daily/weekly volumes, Periodic large receipts/deliveries, Highly variable depending on market, Seasonal peaks, Other
      • How much scheduling flexibility do you need—same‑day, 24–48 hour, weekly windows, or fixed allocations? Options: Same‑day / immediate, 24–48 hours, Weekly windows, Fixed allocations with notice, A mix depending on product
      • Do you require priority windows or guaranteed berth/slot allocations for time‑sensitive trades? If yes, explain the frequency and impact. Options: Yes, for critical trades, Occasionally, Rarely, No
      • When you think about schedule failures (missed slots, late receipts), what downstream cost matters most—demurrage, lost margin, regulatory fines, or something else? Options: Demurrage, Lost trading margin, Customer service penalties, Operational rework/overtime, Regulatory or environmental fines, Other

      Where measurement and custody keep you up at night

      • When custody transfer measurement disagrees with your books, how large does the difference typically need to be before you escalate? Options: <$1,000, $1k–10k, $10k–100k, $100k–1M, >$1M
      • Have you experienced custody disputes with terminals before—what was the root cause (instrumentation, procedures, timing, or reconciliation process)? Options: Instrumentation/calibration, Paper/manual data entry, Timing of measurements, Differing measurement standards, Integration/data mismatch, No disputes
      • Who in your organization owns custody reconciliation and dispute resolution? Options: Trading desk, Finance/Accounting, Operations/Terminal team, Quality/Metrology, Legal/Commercial, Other
      • How quickly do you need custody variances resolved to feel comfortable during a cutover period? Options: Same day, 48–72 hours, Within a week, Within a month, Longer
      • Tell us about the last custody variance you considered material—what happened, who was involved, and how was it resolved?

      What would a trusted scheduling and blending experience change for you?

      • If schedules were visible and enforced across all parties, what would break less often, and why does that matter financially or operationally?
      • How are blending decisions made today—centrally by trading, locally by operations, or a mix—and what frictions arise from that model? Options: Centralized trading, Operations/local teams, Shared governance, Third‑party blenders, Other
      • How many distinct product grades or blend recipes do you need the terminal to produce simultaneously? Options: 1–2, 3–5, 6–9, 10–12, 12+
      • What is your acceptable tolerance for blend spec variance (e.g., API gravity, sulfur ppm) before a shipment is rejected or reclassified? Options: Very tight (laboratory spec only), Moderate (small tolerance), Loose (operational tolerance), Depends on customer/product
      • How would increased blending flexibility—more grades, faster turn times—translate into commercial opportunity for you?

      Integration Reality Check: can the tech talk to yours?

      • How confident are you that your systems (ERP, trading, accounting) can ingest live inventory and custody data from a terminal without extensive rework? Options: Very confident, Somewhat confident, Unsure, Not confident
      • Which of these systems will need to integrate with the terminal platform? Options: ERP (e.g., SAP/Oracle), Trading/blotter systems, Accounting/general ledger, Pipeline SCADA, Loading/rack control systems, Laboratory/QA systems, Other
      • Which field/instrument protocols does your team commonly use or expect to receive (select all that apply)? Options: MODBUS, OPC-UA, PROFINET, Serial/legacy proprietary, REST/API, EBCDIC/flat files, Other
      • Who will own integrations and instrument access on your side (IT, OT, third‑party integrator)? Options: IT, OT/Field Engineering, Third‑party systems integrator, Vendor/terminal integration team, Shared ownership
      • Are there access or security constraints (network segmentation, no remote access, vendor approvals) we should know about up front? Options: Full access with standard IT controls, Restricted OT network - limited access, No remote access allowed, Requires special approvals, Unsure / need to confirm

      Acceptance, risk and the human side of change

      • What's the single most important acceptance criterion for you at cutover (e.g., custody reconciliation within X, throughput target, blend accuracy)? Options: Custody reconciliation tolerance, Sustained throughput target, Blend accuracy within spec, Seamless integration with ERP, Operator competency demonstrated, Other
      • How long of a parallel run do you consider safe before making this platform the 'system of record'? Options: Hours to a day, 48–72 hours, 1–2 weeks, Several weeks, Depends on outcomes
      • What rollback triggers would force you to halt a cutover and revert to legacy processes? Options: Custody variance exceeds tolerance, Throughput below target, Critical integration failures, Safety or compliance alarms, Operator inability to execute, Other
      • Describe how your operators and trading desk typically respond to new structured scheduling or stricter operating guardrails—what resistance or adoption cues have you seen?
      • What training or enablement would make your team confident on day one of parallel operations? Options: Hands‑on operator sessions, Simulation drills, SOP documentation and checklists, On‑call support during cutover, Recorded training + assessments, Other

      Decision and next steps: what would make this an easy yes?

      • Assuming we address measurement, scheduling, and integrations, what remaining objections would still prevent you from moving forward?
      • Who are the internal decision‑makers and what approval gates must be cleared (names/functions and their primary concern)?
      • What timeline and milestones would make a proposed solution compelling—fast ramp, staged pilot, or extended validation? Options: Fast ramp (1–3 months), Staged pilot then roll, Extended validation (3–6 months), Unsure / need to discuss
      • What would you like us to demonstrate or produce in the next meeting to make progress (e.g., integration plan, custody tolerance table, pilot schedule)? Options: Integration/data map, Custody reconciliation plan, Pilot/test windows, Operator training plan, Commercial terms and responsibilities, Other
      • Is there anything critical we haven't asked that would change how you evaluate terminal partners or platform vendors?
    2. Deployment Enablement

      Schedule and execute cutover tasks, coordinate teams, run operator training, and manage rollback criteria during parallel operation.

    3. Validation Checklist

      Perform custody transfer reconciliation, throughput stress tests, blending scenarios, and compliance report validation against acceptance criteria.

      Validation Questions

      Quick Snapshot — Who Are We Helping Today?

      • Which best describes your role and primary area of responsibility? Options: Commodity Trader, Supply Chain / Logistics Manager, Terminal Operations Manager, Measurement / Custody Engineer, Compliance / Regulatory Lead, IT / Integration Lead, Other
      • What’s the immediate reason you’re exploring a terminal operations platform right now? Options: New pipeline connection / hub access, Refinery turnaround / pre-positioning, Need storage for trading strategy, Recurring demurrage or congestion, Regulatory reporting concerns, Modernization / replace manual processes, Other
      • How soon do you need meaningful results (pilot or production) from this engagement? Options: Immediately / within 30 days, 1–3 months, 3–6 months, 6–12 months, No firm timeline yet
      • What two measurable outcomes will make you declare this project a success? Options: Reduced demurrage (hours/dollars), Improved custody measurement accuracy (%), Increased usable throughput (bbl/day), Faster scheduling turnarounds (hours), Fewer custody disputes, Successful ERP / SCADA integration, Reduced operator errors, Other
      • Are there internal blackout dates, approval gates, or procurement windows we should honor?

      If You Miss This Window, What Really Breaks?

      • Imagine next peak season — what is the real business cost if you can’t access tank capacity or scheduling flexibility?
      • Which of these consequences have you experienced or fear most when terminal access is constrained? Options: Demurrage charges, Missed trading opportunities, Forced product swaps / poor blends, Regulatory fines / reporting failures, Customer service failures, Operational overtime / rush costs, Other
      • In the past 12 months, how many times did terminal capacity or scheduling issues force you to delay or cancel a trade or shipment? Options: 0, 1–2, 3–5, 6–10, More than 10
      • Tell us about the most painful recent instance where capacity or scheduling issues hit your P&L or operations—what happened and what was the fallout?
      • Which internal stakeholder groups feel this pressure most acutely? Options: Commodity Trading, Operations / Terminal, Commercial / Sales, Compliance / Legal, Finance / Accounting, Logistics / Transportation, Other

      What’s Truly in Your Tanks and Pipes?

      • When was the last time your reported inventory didn’t match physical or accounting records—and what did it reveal about your measurement chain?
      • Which terminal types and transport corridors do you use for the work that matters to this project? Options: Pipeline hub, Refinery terminal, Marine dock / barge, Rail siding, Truck rack, Third-party storage, Other
      • Describe the tanks that matter for your operations (select all that apply). Options: Heated tanks, Insulated tanks, Floating roof, Fixed roof, Blend manifold connected, Single-product tanks, Multi-grade tanks
      • Which measurement practices do you currently rely on at custody points? Options: Manual tank gauging, Automatic level probes (radar/ultrasonic), Coriolis meters, Turbine / PD flowmeters, LACT units, Strapped tank tables, Sampling & lab analysis
      • Have you had formal custody disputes in the past 5 years? If so, what were the usual causes? Options: Yes — measurement discrepancy, Yes — documentation timing, Yes — handshake/scheduling mismatch, No disputes, Prefer not to say
      • Are there physical or contractual constraints (e.g., receiver certification, pipeline pressure limits, tank product compatibility) we should know about?

      Where Handoffs Turn Into Headaches

      • Which recurring handoff do you secretly expect to fail when volume or complexity ramps up—scheduling, custody, billing, or something else? Options: Scheduling / load planning, Custody measurement & transfer, Blending handoffs, Billing / invoicing, ERP reconciliation, Regulatory reporting, Other
      • How do you currently coordinate receipts and deliveries (pick all that apply)? Options: Phone calls, Email threads, Shared spreadsheets, TMS / scheduling software, EDI / API exchanges, Informal operator coordination
      • On average, how many schedule changes or late-notice requests occur monthly that require operator intervention? Options: 0–5, 6–15, 16–30, 31–60, More than 60
      • Who typically authorizes last-minute schedule changes and how do operators feel about that process?
      • Which communication breakdowns have led to financial or operational loss (examples: missed ship windows, double-booked racks, incorrect bills)?

      If Measurements Aren’t Trusted, Nothing Else Matters

      • If a counterparty challenged a custody transfer today, how confident are you that your evidence would hold up in arbitration? Options: Very confident, Somewhat confident, Uncertain, Likely not confident
      • What accuracy tolerances do your counterparties or contracts require for custody measurement? Options: ±0.1%, ±0.25%, ±0.5%, ±1.0%, No explicit tolerance
      • How often are custody measurement devices calibrated and who owns that schedule? Options: Monthly, Quarterly, Annually, On-demand / after incident, Don’t know
      • Which types of custody transfer equipment are in scope for the project? Options: LACT / custody flowmeters, Coriolis meters, Strapped tanks & level sensors, Sampling systems / labs, Tank gauging via manual methods, Other
      • Have past measurement differences required accounting adjustments? If yes, how large were they typically (a rough order of magnitude)? Options: Negligible (under 0.1% of volume), Small (0.1–0.5%), Moderate (0.5–1%), Material (over 1%), Not tracked

      Imagine a Day When Everything Just Flows

      • If scheduling, blending, and custody accuracy were flawless tomorrow, what would you do differently in trading or operations?
      • How much additional throughput (bbl/day) or margin opportunity ($/month) would justify the investment for you? Options: Under 1,000 bbl/day or <$10k/month, 1,000–5,000 bbl/day or $10k–$50k/month, 5,000–20,000 bbl/day or $50k–$200k/month, More than 20,000 bbl/day or >$200k/month, Not sure / need analysis
      • How many simultaneous blend recipes and product grades do you want the terminal to support? Options: 1–3 grades, 4–6 grades, 7–12 grades, More than 12 grades
      • Which KPIs would you monitor daily after success (pick top 3)? Options: On-time load %, Demurrage $/day, Measurement variance %, Throughput utilization %, Number of scheduling exceptions, Customer satisfaction / SLA
      • Emotionally, what would success feel like for you and your team? Options: Relief from firefighting, Greater confidence in trades, Pride in operational excellence, Reduced stress for operators, Other

      Integrations Everyone Assumes Will Be Easy (But Aren’t)

      • Which single integration historically causes the longest delays or surprises on projects like this? Options: SCADA / field instrumentation, ERP / accounting, Trading & scheduling systems, Third-party pipeline APIs, LACT / meter vendor systems, Lab / QA systems, Other
      • Which systems must we integrate with for a successful deployment (select all that apply)? Options: Plant / Terminal SCADA, ERP (SAP, Oracle, etc.), Trading system / OMS, Scheduling / TMS, Metering / LACT vendor, Third-party terminal operators, Custom / legacy proprietary system
      • Which field protocols are in use at the terminals we’ll touch (pick all that apply)? Options: Modbus RTU/TCP, OPC-UA, DNP3, Proprietary vendor API, REST / HTTPS, Serial / legacy protocols, Not sure
      • Who owns each integration on your side (name, role, and availability for discovery calls)?
      • What test windows or maintenance outages could we use for integration testing and parallel runs?

      People: Allies, Skeptics, and Quiet Blockers

      • Who in your organization would lose informal control if scheduling and custody were centralized—and how might they react?
      • Who needs to be convinced for procurement and who will sign acceptance at cutover? Options: Trading desk head, Ops/Terminal manager, CFO / Finance, Compliance / Legal, Site safety manager, Other
      • How do your operators typically respond to structured scheduling versus informal coordination? Options: Welcoming — it reduces chaos, Cautiously optimistic, Resistant — prefers familiar ways, Mixed across shifts
      • What training cadence and format works best for your operations team? Options: Hands-on classroom + site labs, Remote video modules, Train-the-trainer, Shadowing during parallel ops, Combination
      • Who could be an internal champion for this program and why would they care?

      Acceptance — The Tests That Will Make or Break Go-Live

      • What single acceptance-test failure would force you to delay cutover until corrected?
      • Which formal acceptance tests do you require before sign-off (select all that apply)? Options: Custody transfer reconciliation within tolerance, Throughput stress tests at peak volumes, Blending accuracy / recipe validation, Compliance report parity with legacy, Parallel accounting reconciliation, Operator competency demonstration
      • Who on your team must approve each acceptance test (role names), and who will perform reconciliation?
      • Do you require a parallel accounting period? If so, how long? Options: No parallel accounting, 1–2 weeks, 3–4 weeks, 1–3 months, Other / TBD
      • What rollback criteria or go/no-go gates do you want in the cutover playbook?

      If We Leave Today, What’s The Next Step?

      • If you decided to proceed with us, what would you insist on seeing delivered in the first 30 days?
      • Which pilot scope would you prefer to validate value quickly? Options: Single tank & one LACT meter, Single terminal, multiple tanks, Single product across multi-modal corridors, Full site pilot with ERP integration, Other
      • What budget or procurement constraints should we align to (purchase order, contract length, milestone payments)?
      • What are the top three risks you want explicit mitigation plans for before contract execution?
      • Who should we schedule the next alignment call with (name, role, best contact times)?
  7. Success

    Confirm outcomes against success signals, finalize accounting for cutover, capture lessons learned, and track issues and enhancements.

    Success Reviews

    • Success Confirmation & Acceptance Review
    • Cutover Accounting Finalization
    • Lessons Learned & Operational Improvement Workshop
    • Issues, Enhancements & Backlog Prioritization
    • Customer Handoff, Monitoring & Support Plan

    Issues & Enhancements

    • Create prioritized tickets in the issue tracker with owners, acceptance criteria, and due dates.
    • Schedule required refresher training sessions and update training materials.
    • Update SOPs/runbooks and publish version-controlled documents to the operations repository.
    • Open Issues Triage
    • Prioritize the backlog clearly so high-impact issues and mandatory compliance fixes are scheduled immediately.
    • Assign responsible owners and realistic delivery dates for each prioritized item.
    • Agree on the cadence for patches/releases and communication plans to stakeholders.
    • Welcome & Objectives
    • Publish a short-term roadmap reflecting committed fixes and enhancement delivery windows.
    • Schedule a recurring backlog review cadence (e.g., weekly or bi-weekly) until stabilized.
    • Handoff Summary & Responsibilities
    • Confirm steady-state support responsibilities and ensure customer has required access and contacts.
    • Ensure monitoring and alerting are configured, validated, and understood by both parties.
    • Set a recurring governance cadence to monitor performance, issues, and continuous improvement.
    • Deliver handoff package including runbooks, access lists, dashboards links, and SLA document to the customer's operations team.
    • Provision access for monitoring dashboards and confirm alert notifications to on-call contacts.
    • Schedule the first 30/60/90-day performance review meetings and identify expected attendees.
    • Validate measured outcomes against each success signal and obtain formal acceptance or conditional acceptance.
    • Document and quantify any remaining discrepancies and their business impact.
    • Assign clear owners and deadlines for remediation items required for final sign-off.
    • Publish formal acceptance certificate or conditional acceptance statement with referenced evidence package.
    • Open remediation tickets for each discrepancy with owner, priority, and target close date.
    • Schedule a short follow-up acceptance verification once remediation items are closed.
    • Parallel Run & Reconciliation Summary
    • Agree and document the accounting treatment for all cutover variances and finalize the cutover posting calendar.
    • Obtain sign-off authorities for the final accounting package and define escalation paths for disputed amounts.
    • Ensure regulatory reporting requirements related to custody or inventory adjustments are identified and scheduled.
    • Prepare and circulate final journal entry batch with supporting reconciliation files for finance sign-off.
    • File any required regulatory notifications and retain stamped/dated confirmations.
    • Document rollback accounting procedures and owners in case parallel operation requires reversion.
    • Incident & Near-Miss Review
    • Create a prioritized list of operational improvements with owners and due dates.
    • Identify immediate mitigations for any high-risk process gaps uncovered.
    • Agree a schedule to update runbooks, training materials, and operator checklists.
    • Produce a Lessons Learned report summarizing root causes, proposed fixes, and owners.
    • Success Signals Readout
    • Enhancement Requests Review
    • Monitoring, Alerts & KPIs
    • Operator & Process Feedback
    • Measurement Delta Adjustment Methodology
    • Journal Entries & Cutover Calendar
    • Training & Documentation Gaps
    • Support Model & Escalation Paths
    • Discrepancies, Financial Consequence & Risk
    • Prioritization & Roadmap Alignment
    • Acceptance Decision & Conditions
    • Ownership, SLAs & Release Cadence
    • Optimization Cadence & Review Meetings
    • Approvals, Signatories & Regulatory Notifications
    • Actionable Improvements & Owners
    • Next Steps & Owner Assignments
First-Party AI

1-2 minutes please — Your AI agent is working

First-Party AI™ can make mistakes. Always check important information.