Terminal Operations
Capital-intensive extraction and processing programs where safety, regulation, and supply chain complexity define execution.
Inside this journey
-
Pre-Discovery
Align the room on outcomes, decision process, and constraints before deeper discovery.
-
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?
- 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?
- 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?
If Tanks Could Talk, What Would They Admit?
- How often do tank availability or spec surprises silently cost you margin or cause missed trades?
- 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?
- How do you currently record and share tank specs (capacity, heating, product compatibility) across teams?
- How confident are you in those published tank specs when it matters most (trade execution or loadout)?
When Scheduling Breaks, Who Pays the Tab?
- How often does informal scheduling or last-minute changes create demurrage or missed slot costs?
- 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?
- How do you currently calculate and bill demurrage, and who owns dispute resolution?
- How much scheduling flexibility (hours/days) would materially change your ability to capture market opportunities?
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?
- 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?
- 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?
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?
- 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?
- What maximum variance (e.g., ppm, percentage) do Finance and Trading accept before an investigation is triggered?
- 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?
- 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?
- Who controls network and VPN access for integrations, and how quickly can access be provisioned?
- How tolerant is your operations team for scheduled integration windows that require temporary process changes?
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?
- 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?
- What procurement, legal, or budget cycles could delay signing a statement of work?
- What is your target go/no-go date to begin a pilot or parallel run, and why is that date important?
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.
- 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)?
- 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)?
- How do operators balance ease-of-use versus feature richness—what trade-offs are acceptable?
- 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?
- 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?
- When could we realistically begin that pilot, and are there blackout windows (turnarounds, audits) we must avoid?
- 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?
-
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?
- Which commodity grades do you regularly move through those locations?
- Typical combined monthly throughput (incoming + outgoing) at these sites?
- Who holds operational ownership of the tanks and gauge records at these locations?
- 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?
- Think of the most recent custody dispute or measurement discrepancy — what was the primary cause?
- How long did the last major dispute take to resolve, and who bore the financial or contractual burden?
- When measurement disagreements happen, who typically escalates (trader, terminal ops, quality lab, legal)?
- 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?
- Which transport corridors do you depend on most and in what priority order?
- What are the top corridor constraints you face (choose up to three)?
- How quickly can you switch receipt or delivery mode (e.g., pipeline → rail → marine) when markets force a reroute?
- 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?
- How frequently are custody transfer instruments calibrated or proved, and who owns that 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?
- Where do you see the biggest blind spots in measurement today (sampling frequency, reconciliation lag, rounding practices, lost metadata)?
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?
- What systems must we integrate with to make this implementation useful (select all that apply)?
- Which field protocols or middleware are in play (e.g., Modbus, HART, OPC UA, custom TCP, REST APIs, EDI)?
- Who controls credentials, network zones, and firewall rules for field connectivity — and how long does access typically take to approve?
- 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?
- What are your internal governance checkpoints (procurement, safety, compliance, legal) and typical lead times for each?
- At what tolerance of measurement variance would trading/finance refuse to accept new platform figures during parallel run?
- Who will be the day-to-day owner for reconciliation during transition (ops, trading, finance, or shared)?
- 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?
- 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)?
- How perfect does custody measurement reconciliation need to be on day one of parallel ops before you’ll reduce contingency holds or payments?
- Which audit or compliance reports must match first (regulatory, tax, customer invoices, internal accounting)?
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?
- Which of the following pilot scopes would most convince you this solution works (pick one)?
- What timeline do you realistically need for a pilot to run before you can assess go/no-go (days/weeks/months)?
- What items do you need on a readiness checklist before committing to a pilot (data feeds, credentials, instrument access, safety permit)? List top three.
- Who should be in the room for a kickoff call (names & roles), and who will be our primary technical and commercial contacts?
-
-
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?
- 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?
- What’s the planning horizon your team typically operates on for storage, receipts, and deliveries?
- Who else needs to be involved or will sign off on changes to terminal capacity, scheduling, or custody systems?
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?
- 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?
- Estimate the typical scale of impact when a missed opportunity occurs due to tank constraints (choose the closest range).
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?
- How frequently do late arrivals, missed load windows, or unscheduled changes cause demurrage, stacking, or missed dispatches?
- 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)?
- Who typically initiates and owns scheduling changes today?
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?
- Which measurement methods do you currently rely on at receipt and delivery?
- 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?
- How important is having a single source of truth for inventory and custody during parallel operations? (1 = not important, 5 = mission-critical)
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?
- 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?
- How do you validate a blended batch meets pipeline/receiver specs today?
- What turnaround time for blend validation is acceptable to keep trading and shipping decisions agile?
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?
- How do you prefer acceptance criteria be structured—metric thresholds, scripted test scenarios, staged commercial cutover, or a mix?
- Who must sign the acceptance certificate or approve go-live from your side?
- What commercial remedies or safeguards would you expect if acceptance KPIs are not met?
- 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?
- 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?
- Which live data feeds and calibration artifacts will we need access to before cutover?
- 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?
-
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
-
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?
- What type(s) of level sensing do you prefer or currently use?
- Do the tanks operate in hazardous classified areas (e.g., Class I, Division 1/2)?
- Which communication protocols must sensors support for integration (select all that apply)?
- Are power and network (PoE/ethernet/fieldbus) available at each tank location?
- 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?
- Are current meters certified to local custody-transfer standards (e.g., API, OIML, local regulator)?
- What is the desired certification standard or authority for calibration?
- Provide the typical flow rates and viscosity/product types for meters requiring calibration.
- Are there preferred windows for onsite calibration to avoid interrupting operations?
- Do you require witness or joint acceptance by customer/trader during certification?
Deploy real-time inventory tracking dashboard
- Which inventory KPIs must be visible on day one (e.g., ullage, volume, mass, temperature-adjusted volume)?
- Who will be primary dashboard users (roles)?
- What refresh rate is required for dashboard data (seconds/minutes)?
- Do you require role-based views or restricted access to specific products/terminals?
- 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)?
- Do you require digital signatures or e-signature integration for acceptance?
- Should electronic documents be automatically routed to ERP/accounting and trading counterparties?
- Are there jurisdictional or contractual record retention requirements (duration and format)?
- Do transported modes (rail/truck/barge) require mobile/offline capture capabilities?
- 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?
- What types of transactions/data should flow to ERP (select all that apply)?
- Do you require real-time posting to ERP or batched transfers?
- Are there existing API credentials, sandbox environments, or documentation available?
- Are there special accounting rules (e.g., custody adjustments, rounding, temperature correction journals) we must implement?
- 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)?
- What telemetry points are required (e.g., flow, pressure, pump status, valve position)?
- Are there security/firewall or DMZ constraints for exposing SCADA telemetry to the platform?
- Do you require historian-level integration for long-term trending or only event/real-time data?
- 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?
- Do you require automated recipe-based blending or operator-assisted blending?
- 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?
- Will blending require lab-feedback loops (e.g., real-time quality sampling) or offline QC only?
Configure multi-modal loading/unloading controls
- Which transport modes and interfaces are active at the terminal?
- Do loading racks and dock controls have existing remote interfaces (PLC/API) for integration?
- What scheduling complexity is required (e.g., multi-leg shipments, composite loads, batch sequencing)?
- Are driver/mobile workflows and check-in/out processes required for truck loading?
- What safety interlocks or permissives must be enforced by the system before dispensing?
- 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)?
- Do temperature controls need to integrate with inventory and custody calculations (temperature correction)?
- Are there explosion-proof or hazardous-area requirements for control panels and sensors?
- What level of automated control is required (PID closed-loop, scheduled setpoints, manual overrides)?
- 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)?
- Do you currently have a leak detection vendor/system that must be integrated or replaced?
- What alarm thresholds and notification workflows should be configured for environmental events?
- Are environmental monitoring systems required to generate regulatory reports automatically?
- What site access and sensor maintenance windows are available for installation?
- Do you require integration with local emergency response or security systems?
-
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)
-
Deployment
Operationalize rollout with readiness checks, enablement, and outcome validation.
-
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?
- Which best describes your organization?
- Which commodities will you be moving or storing at this location?
- What triggered this search for terminal capacity or a new operating model?
- How soon do you need usable capacity or a working solution?
- Which outcomes would signal a successful engagement for you? (pick all that apply)
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?
- How often in the last 12 months have storage constraints or terminal issues directly affected a trade or shipment?
- When those issues happen, how does it typically feel inside your team—annoying, costly, embarrassing, or something else?
- 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)?
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?
- How much scheduling flexibility do you need—same‑day, 24–48 hour, weekly windows, or fixed allocations?
- Do you require priority windows or guaranteed berth/slot allocations for time‑sensitive trades? If yes, explain the frequency and impact.
- When you think about schedule failures (missed slots, late receipts), what downstream cost matters most—demurrage, lost margin, regulatory fines, or something else?
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?
- Have you experienced custody disputes with terminals before—what was the root cause (instrumentation, procedures, timing, or reconciliation process)?
- Who in your organization owns custody reconciliation and dispute resolution?
- How quickly do you need custody variances resolved to feel comfortable during a cutover period?
- 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?
- How many distinct product grades or blend recipes do you need the terminal to produce simultaneously?
- What is your acceptable tolerance for blend spec variance (e.g., API gravity, sulfur ppm) before a shipment is rejected or reclassified?
- 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?
- Which of these systems will need to integrate with the terminal platform?
- Which field/instrument protocols does your team commonly use or expect to receive (select all that apply)?
- Who will own integrations and instrument access on your side (IT, OT, third‑party integrator)?
- Are there access or security constraints (network segmentation, no remote access, vendor approvals) we should know about up front?
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)?
- How long of a parallel run do you consider safe before making this platform the 'system of record'?
- What rollback triggers would force you to halt a cutover and revert to legacy processes?
- 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?
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?
- 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)?
- Is there anything critical we haven't asked that would change how you evaluate terminal partners or platform vendors?
-
Deployment Enablement
Schedule and execute cutover tasks, coordinate teams, run operator training, and manage rollback criteria during parallel operation.
-
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?
- What’s the immediate reason you’re exploring a terminal operations platform right now?
- How soon do you need meaningful results (pilot or production) from this engagement?
- What two measurable outcomes will make you declare this project a success?
- 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?
- In the past 12 months, how many times did terminal capacity or scheduling issues force you to delay or cancel a trade or shipment?
- 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?
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?
- Describe the tanks that matter for your operations (select all that apply).
- Which measurement practices do you currently rely on at custody points?
- Have you had formal custody disputes in the past 5 years? If so, what were the usual causes?
- 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?
- How do you currently coordinate receipts and deliveries (pick all that apply)?
- On average, how many schedule changes or late-notice requests occur monthly that require operator intervention?
- 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?
- What accuracy tolerances do your counterparties or contracts require for custody measurement?
- How often are custody measurement devices calibrated and who owns that schedule?
- Which types of custody transfer equipment are in scope for the project?
- Have past measurement differences required accounting adjustments? If yes, how large were they typically (a rough order of magnitude)?
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?
- How many simultaneous blend recipes and product grades do you want the terminal to support?
- Which KPIs would you monitor daily after success (pick top 3)?
- Emotionally, what would success feel like for you and your team?
Integrations Everyone Assumes Will Be Easy (But Aren’t)
- Which single integration historically causes the longest delays or surprises on projects like this?
- Which systems must we integrate with for a successful deployment (select all that apply)?
- Which field protocols are in use at the terminals we’ll touch (pick all that apply)?
- 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?
- How do your operators typically respond to structured scheduling versus informal coordination?
- What training cadence and format works best for your operations team?
- 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)?
- 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?
- 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?
- 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)?
-
-
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