Every move.
Smarter
Planning and control for casing-pipe (OCTG) yards. Simulate a move before anyone touches a joint, and keep the planner, the yard and the programme on one picture.
13⅜ in · 36 jt
9⅝ in · 42 jt
9⅝ in · 40 jt
7 in · 58 jt
7 in · 54 jt
13⅜ in · 30 jt
9⅝ in · 44 jt
9⅝ in · 42 jt
Clear
13⅜ in · 34 jt
7 in · 60 jt
9⅝ in · 40 jt
7 in · 56 jt
13⅜ in · 32 jt
Clear
Clear
9⅝ in · 40 jt
7 in · 52 jt
13⅜ in · 36 jt
9⅝ in · 44 jt
7 in · 58 jt
Clear
9⅝ in · 38 jt
13⅜ in · 28 jt
The plan is only as good as its last manual update.
Plans live in workbooks
A casing programme runs to thousands of tonnes and more than a year, and in most operations it lives in a hand-maintained spreadsheet that is rebuilt by hand every time something moves.
Moves are discovered after the fact
Yard capacity is exceeded before anyone saw it coming, and haulage gets booked against yesterday's plan. Overflow surprises and trailer shortfalls show up on the day.
No shared picture
The planner, the yard and the programme each work from their own version. What-if questions take days, so they often go unasked, and totals are typed in and impossible to trace back.
From your workbook to a plan you can run.
Change one assumption and see the whole plan.
- 01
Load the workbook
Start from the workbook your planner already keeps. Yards, pipe sizes, arrival schedules and capacities are all editable in the app.
- 02
Build the live yard plan
A daily simulation steps through every day of the horizon. Stock levels, trailer trips, overflow and ton-days are outputs of the plan, not numbers someone types in.
- 03
Simulate a change
Apply a what-if such as a delayed reception or slower threading. Every view, report and export recomputes together, in milliseconds.
- 04
Execute with the yard
Post actuals to the movement ledger and track plan against actual, with tolerance bands and an adherence score.
- 05
Report with the AI Report Builder
Describe the report you need in plain language and refine it with follow-ups. The engine computes every number.
Everything the yard plan needs, in one place.
Nothing is hard-coded. YardFlow is configured for a yard, not rebuilt for it.
AI Report Builder
Describe the report you want in plain language, then refine it with follow-ups.
Daily simulation engine
Recomputes the full horizon in milliseconds, and every figure is derived.
Forward occupancy forecasting
Daily on-ground tonnage against the capacity line, with overflow-yard and at-contractor bands, per-size stock curves and an actuals overlay.
Monthly execution plans
Day-grid threading schedules per casing size, with weekday calendars and daily production blocks per batch.
QA release scheduling
Release per batch or for the full batch, with a configurable lead time.
Trailer and logistics demand
Trips across every movement leg, with each figure traceable to a formula.
Two-yard balance
Overflow and backfill modelling, with ton-days showing storage-cost exposure.
Data Explorer
A heat-strip calendar of every day by every pipe size, with movement detail and trailer legs one click away.
Scenario studio
Compare delivery, overflow and backfill scenarios, including a mandatory downside case, and build your own.
What-if circumstances
Named bundles such as threading at 50% production or reception delayed by ten days. Apply one and everything recomputes.
Sensitivity analysis
Ranks which assumption moves the plan the most.
Immutable movement ledger
Posted actuals are the single source of truth, and corrections are counter-transactions, never edits.
Plan-versus-actual deviation
Tolerance bands and an adherence score show where the yard is drifting from the plan.
Role-based access control
Real authentication, with permissions set by role.
Excel export
A 41-sheet workbook with native, recalculating charts, built to match the planner's existing layout, colours and chart types.
Full-granularity data dump
One row per day per pipe size, with every stock level, movement and trailer leg.
Ask for the report in plain language.
The AI Report Builder turns a plain-language request into a finished report. The planner says what they need, and refines it with follow-ups the way they would brief a colleague.
- Describe the report you want, for example the stock on the ground in both yards and how it changes across the plan.
- The builder selects the variables, filters and report blocks.
- Refine with follow-ups until the report shows what you need.
- Operations, QHSE and commercial teams get the view they need without learning the tool, or asking the one person who knows the workbook.
The builder assembles the report and the simulation engine computes every number. It never invents figures.
Built for people who move casing pipe.
Oilfield tubular (OCTG) yard operators
Yard and logistics managers who need to know where the pipe is, have trailers when they are needed, and avoid overflow surprises.
Casing programmes
Planning leads and operations directors who need programme delivery, cost exposure and risk visible, with numbers they can defend.
Quality and commercial teams
QHSE coordinators who need release timing, traceability and audit, and commercial leads who need credible delivery dates for the customer.
Common questions
What data does YardFlow need?
It starts from the planner's workbook. Yards, pipe sizes, arrival schedules, capacities and every planning variable can then be edited in the app. How the workbook is brought in is agreed during onboarding.
How does the simulation work?
A deterministic daily simulation steps through every day of the horizon, moving pipe through the flow according to the arrival schedule, threading rates, QA lead times, capacities and dispatch plan. Change an input and the whole horizon recomputes, so every view, report and export updates together.
Who uses it?
Planning leads and yard or logistics managers use it day to day. Operations directors, QHSE coordinators and commercial leads use it to see programme delivery, release timing and delivery dates, with access set by role.
What does the AI Report Builder do?
It builds the report you describe in plain language, selecting the variables, filters and report blocks, and you refine it with follow-ups. The simulation engine computes every number, so the builder never invents figures.
Can we trace a figure back to its source?
Yes. Every figure comes from one of two places: a formula for planned values, or a row in the movement ledger for actuals. Totals are never typed in, and corrections are posted as counter-transactions rather than edits.
What do we provide, and what does the team configure?
You provide the workbook and the yard's details. The ClearLoft team configures YardFlow around them. The exact split is agreed during onboarding.
Talk to us about your yard.
Tell us how your casing programme runs today, and we will show you how YardFlow would plan it.