Gas Nomination and Scheduling Software: Buy PipelineManager, or Build Your Portfolio Model?
Pipeline count and portfolio shape decide this, and the line sits around six. At two or three pipelines under straightforward firm transport with no storage optimisation, buy or stay on the bulletin boards and a disciplined workbook, and most shippers are genuinely there.
On this page
Pipeline count and portfolio shape decide this, and the line sits around six. At two or three pipelines under straightforward firm transport with no storage optimisation, buy or stay on the bulletin boards and a disciplined workbook, and most shippers are genuinely there. Past roughly six pipelines, or with storage you actively optimise, or with a marketing desk that changes positions inside the flow day, a custom build starts paying for itself against cashout alone. The second trigger has nothing to do with size: if one scheduler cannot take a week off in January, you have a problem software can fix.
When is off the shelf genuinely the right call here?
If you nominate on one, two or three interstate pipelines under firm transport with stable supply and demand and no active storage position, do not build. The pipelines' own electronic bulletin boards plus a well kept workbook are adequate, and a build would be an expensive way to formalise something that already works. We say this often, and the money is better spent negotiating better contract terms than writing software.
The packaged options are real and they are not toys. Quorum PGAS and ION Openlink cover the transactional and gas accounting side properly. Energy Solutions International PipelineManager and Latitude Technologies handle the operational layer and both connect to bulletin boards credibly. If your portfolio is genuinely conventional, meaning firm transport with a fixed path, no storage ratchets to optimise and no intraday position changes, one of those products will serve you and a custom build will not beat it on total cost.
Buy also if the shape of your problem is supply rather than scheduling. If imbalances come from unpredictable production or weather driven load rather than from missed cycles and manual errors, a scheduling platform will show you the imbalance accumulating in beautiful detail and will not reduce it by a single dekatherm. That distinction is worth an honest hour with your own numbers before anyone gets quoted.
The test that settles it: can your scheduler assemble the timely cycle across the whole portfolio without rebuilding a balance tab by hand first. While the answer is yes, you have not outgrown what you can buy.
When does a custom build actually pay off?
The signals are behavioural and you can check them at tomorrow's timely cycle.
You nominate across more than about six pipelines, each with its own login, its own conventions and its own tolerance for a nomination arriving at 12:58. Your portfolio includes storage you actively optimise rather than simply fill and drain, with injection and withdrawal ratchets tied to inventory level. Your marketing desk changes positions inside the flow day and the scheduler learns about it by text message. Imbalance cashout has become a predictable monthly cost you have stopped questioning. Or the whole scheduling function depends on one person who cannot be away during a cold snap.
The underlying cause is the same in every case. No product holds the object your scheduler actually reasons about, which is a single position that knows today's supply by point, the transport and storage capacity available to move it, the demand it has to serve, the imbalance already accrued on each pipeline, and the cost of being wrong on each of those. Packaged tools represent a contract as a capacity number and a point list, which is enough to submit a nomination and nowhere near enough to decide the right one. So the scheduler holds the real constraint set in her head and uses the product as a typing interface, which is why the product never gets credit and never gets replaced.
The second reliable trigger is that a spreadsheet cannot poll. Confirmations and cuts arrive after you stop watching, and the fix has to happen in the next cycle. Most desks accept that risk quietly, and the risk shows up priced into cashout every month without anyone deciding to accept it.
How do they compare on the things that matter in this industry?
- Contract modelling depth. This is the whole argument. Maximum daily quantities, fuel and unaccounted for gas retention, receipt and delivery point rights, seasonal and ratcheted terms and storage inventory ratchets all interact on a twenty minute deadline. A packaged model built to serve every shipper is necessarily shallower than one built to serve yours.
- Bulletin board connectivity. Packaged products connect, and this is genuinely a place where buying saves money. Building a connector costs roughly $6,000 to $9,000 where a pipeline offers electronic data interchange or an interface, and $9,000 to $14,000 where the only reliable route is driving portal screens.
- Negotiated behaviour. No product encodes the specific pattern of your relationship with each pipeline, such as which one confirms late on Fridays and which one is unforgiving at the cutoff. That knowledge lives with a scheduler and it is precisely what leaves when they do.
- Live imbalance. Gas accounting systems calculate imbalance accurately after allocation, after the month closes. That is right for accounting and wrong for operations. A live estimate good enough to act on needs your allocation assumptions and your measurement feed, which is why no packaged product provides one.
- Intraday re-optimisation. If you only nominate the timely cycle, calendar logic is simple. If you revise through evening and three intraday cycles, you need partial confirmations, superseding nominations and the ranking consequences of a late change, which is a materially different product.
- Reconstruction. A workbook overwritten four hundred times is not evidence. Storing every submission with the portfolio state it was computed from, the constraints active at the time and any override with its reason costs almost nothing when designed in and is close to impossible to retrofit.
What does total cost of ownership look like at your scale?
From Digital Heroes delivery experience, a focused first release covering a proper portfolio and contract model, cycle aware nomination assembly with a suggested allocation, automated submission to your highest volume pipelines and confirmation capture with exception alerting runs $80,000 to $160,000 and ships in 14 to 20 weeks. A full platform adding live imbalance tracking, park and loan, cashout modelling, operational flow order monitoring, storage ratchet handling and month end reconciliation against pipeline statements runs $200,000 to $500,000 over 8 to 14 months.
A concrete shape: a gas utility nominating across nine interstate pipelines with storage and a mixed supply book, everything running out of one senior scheduler's workbook, came in at $121,000 in eighteen weeks for phase one covering the four pipelines that carried most of the volume. The remaining five were quoted at $6,000 to $12,000 each to add as budget allowed. That staging is the point: the utility was live on the pipelines that could actually hurt it eleven weeks before the estate was fully covered.
The annual side runs 20 to 35 percent of build cost, higher than most software and mostly outside your control. Integration maintenance is $1,500 to $4,000 per pipeline per year because bulletin boards get redesigned and tariffs change, so a nine pipeline estate carries $14,000 to $36,000 before anything else. Support and enhancement is 15 to 20 percent. Hosting and monitoring is $3,000 to $9,000, though the real cost there is on call coverage, because someone has to be woken when a submission fails at a cutoff.
Set that against the number that usually settles the argument. Take your last twelve months of cashout and imbalance charges, add transport you paid for and did not use because a nomination went in late or wrong, then add capacity you bought defensively because nobody trusted the position. On the shippers we have worked with, that total is frequently a meaningful fraction of a focused build inside one year.
What does the hybrid look like, and when is it the honest answer?
For most shippers in the middle of this range the hybrid is the recommendation. Keep the gas accounting system you already run, keep month end allocation where it lives, and build the operational layer that sits between the desk and the pipelines.
The split is clean because the interfaces are clean. Your accounting package keeps owning settled numbers, invoices and the closed month. The custom layer owns the portfolio model, the cycle calendar, the proposed nomination set, submission and confirmation capture, and the live estimated imbalance with an explicit confidence indicator so nobody mistakes an estimate for a settled figure. You feed the accounting system a clean scheduled quantity file rather than rebuilding the accounting.
Within the build there is a second hybrid worth naming, and it saves more money than most people expect. Automate the four or five pipelines carrying most of your volume and leave the tail on a structured manual entry screen. A pipeline you touch twice a month does not need an integration; it needs its nominations recorded so the position is complete. That screen costs a fraction of a connector and removes the argument about whether to do the whole estate at once.
Stage the imbalance work the same way. Track the estimate first. Once a scheduler can see it accumulating in the current month, most desks find they can trade, park or adjust their way out without a full cashout model, and cashout modelling is the feature that most often pushes a project from the focused band into the platform band.
Which should you choose, by operator size and stage?
Two or three pipelines, firm transport, no storage optimisation: stay on the bulletin boards and the workbook. Spend the money on contract terms instead. Nothing else here applies to you.
Four to six pipelines, conventional portfolio, one scheduler with capacity to spare: buy a packaged operational product and configure it properly. Then measure one thing, which is how many cycles a month get assembled from a rebuilt balance tab. If that is rare, keep configuring.
More than six pipelines, or storage you actively optimise, or intraday position changes: build the focused scope. Start with the four or five pipelines that carry the volume, model the contract types you actually use, and leave the long tail manual. Go live before winter or wait for spring, because nobody sensibly cuts over a scheduling desk in peak season.
Shippers with cashout as a budgeted line item: build, and put live imbalance in the first release rather than the second. That is where the payback is clearest and the finance sponsor is already convinced.
Anyone with single scheduler risk, regardless of pipeline count: build, and treat discovery as the deliverable rather than a preamble. The rules about which contract to draw on first, what happens when a supply falls short and which pipeline tolerates a late nomination are the actual asset. Getting them out of one head and into a system is the part that never appears on a requirements list and is usually the reason the sponsor signs.
Utilities and marketers running capacity release or asset management agreements: build, and model who is nominating on whose behalf before anything else. That structure changes the meaning of every downstream number and it is where packaged assumptions break first.
If you would rather scope this before committing budget, Digital Heroes contracts through India LLP, US LLC and UK LTD entities, so the agreement and the intellectual property assignment sit under law your own advisers already read. The document is yours whichever way you go.
The evidence behind this guide
Independent findings on why this investment pays off. Every link goes to the primary source.
- Inventory carrying cost commonly runs about 20% to 30% of inventory value, covering capital cost, storage/warehousing, insurance, taxes, handling, shrinkage, and obsolescence - a recurring cost that better inventory and warehouse software aims to reduce. Source: APQC (2023) →
- In a survey of 113 supply chain leaders (conducted late March to mid-April 2022), 67% had implemented digital dashboards for end-to-end visibility, and those companies were about twice as likely as others to avoid supply chain problems during the disruptions of early 2022; 71% expected to revise inventory policies going forward. Source: McKinsey & Company (2022) →
- Technology 'Leaders' grow revenue at more than twice the rate of 'Laggards'; laggards surrendered 15% in foregone annual revenue in 2018 and stood to miss out on as much as 46% in revenue gains by 2023 if they did not change their enterprise technology approach. Based on a survey of more than 8,300 organizations across 20 industries and 20 countries. Source: Accenture (2019) →
- In the Flexera 2025 State of ITAM report, respondents reported roughly 33% of SaaS spend is wasted, underscoring how paying for off-the-shelf seats and tiers that go unused erodes the supposed cost advantage of generic SaaS. Source: Flexera (2025) →
Frequently asked questions
What does it cost to switch away from PipelineManager or a similar product later?
The contract data and historical nominations are the expensive part, not the connectors. Nominations and confirmations are transactional records that can be exported and re-ingested, but a contract model built inside a vendor's shape rarely maps cleanly onto anyone else's, so it usually gets rebuilt from the agreements themselves.
That is a reason to keep your own structured contract inventory regardless of what you run. If a custom layer already holds the portfolio model, changing operational products becomes a connector exercise rather than a migration, because the thing that took the longest to build never lived in the product.
What happens if a pipeline changes its bulletin board or its tariff mechanics?
The connector breaks and someone fixes it, usually within a day. Any developer promising it will never break has not maintained a portal integration. What matters is that the failure is loud rather than silent, with monitoring that alerts before a cutoff rather than after one.
Tariff changes are the slower version of the same problem. When a pipeline revises cycle mechanics or imbalance tolerances, the model has to be updated before the next month rather than after it, and that maintenance sits inside the $1,500 to $4,000 per pipeline per year figure you should be budgeting anyway.
How long does a nomination build take, and how do we go live safely?
Fourteen to twenty weeks for the focused scope, eight to fourteen months for a full platform, in Digital Heroes delivery experience. The main schedule risk is contract discovery rather than engineering, because transport, storage and supply agreements have to be read and turned into structured constraints, and shippers are routinely surprised by what their own contracts say.
Cutover is staged pipeline by pipeline, not switched on in a day. You cannot rehearse a nomination cycle, so testing happens against real cycles with real deadlines and the workbook stays as a fallback for at least a month on each pipeline. Plan for a shoulder month, never a winter one.
Is Quorum PGAS enough, or do we need a custom scheduling layer?
For settled numbers, invoicing and the closed month it is enough, and we would keep it rather than rebuild it. Gas accounting is a solved problem and there is no case for owning it.
Where it stops is the operational side. It calculates imbalance accurately after allocation, after the month closes, which is right for accounting and useless to a scheduler with twenty minutes before a timely cutoff. If your desk needs a live estimated imbalance and a proposed nomination set that respects your actual constraints, that layer sits above the accounting package rather than inside it.
Can software really submit nominations automatically to every pipeline?
To most of them, through a mix of methods. Where a pipeline offers electronic data interchange or an interface you use it, and where it only offers a portal you automate the portal and budget for the maintenance. The design point that matters is that a nomination exists once inside your system and gets expressed in each pipeline's format, rather than being retyped for every bulletin board.
Plan for a monitored connector with alerting on every one of them. A silent submission failure before the timely deadline is the expensive scenario, and it is the one that justifies the monitoring cost on its own.
Should we integrate all our pipelines, or only the big ones?
Only the big ones, in the first phase at least. Portfolio volume is normally concentrated, so integrating the four or five pipelines that carry most of it captures most of the benefit and gets you live months sooner.
Handle the tail with a structured manual entry screen that records what you nominated so the position stays complete. That costs a fraction of a connector and removes the pressure to fund the whole estate at once. Adding a tail pipeline later runs $6,000 to $12,000 depending on its submission route, and you may find you never bother.
Can we track imbalance daily rather than finding out at month end?
Yes, and it usually has the clearest payback of anything in the build. The system maintains a running estimate per contract per pipeline by comparing scheduled quantities against measured actuals as they arrive, with a confidence indicator attached so nobody treats an estimate as settled.
When an estimate approaches a tolerance band you get flagged while there are still cycles left to trade, park or adjust. Month end reconciliation against the pipeline statement then becomes a short review instead of an investigation, and disputes get raised inside the tariff window rather than after it closes.
Who owns the connectors, the code and the pipeline credentials?
You should, and it should be written into the contract before kickoff. That means the repository, the infrastructure accounts, the connector code and the credentials, with an unrestricted right to hire another firm to continue the work. At Digital Heroes the client owns everything from the first commit.
Connectors are the piece vendors most often try to retain as a service, and that is exactly where a dependency becomes expensive, because the connector is what stands between your desk and a cutoff. Ask the ownership question in the first conversation, not the last.
How much does a custom warehouse management system cost to build?
A custom WMS typically costs $40,000 to $120,000 for a single-warehouse operation, and $120,000 to $300,000 once you add multiple sites, wave picking, and labor tracking. Across Digital Heroes WMS builds, the biggest cost drivers are scanner-based workflows, real-time inventory sync with your ERP, and the number of picking strategies you need. A pilot covering receiving, putaway, and picking for one warehouse is the cheapest credible starting point.
Is custom supply chain software cheaper than SAP over five years?
For small and mid-size operations it usually is, because SAP costs compound through licensing, implementation partners, and per-user fees, while custom costs are front-loaded. SAP Business One's published list price has run roughly $3,200 per professional user as a perpetual license plus annual maintenance near 20 percent, and the S/4HANA proposals Digital Heroes clients share are typically in the hundreds of thousands before any customization. A $60,000 to $100,000 custom build with 15 to 20 percent annual upkeep often costs less by year three for a 10 to 30 user company, and you stop paying per seat as you hire.
Why do companies replace generic SCM software with custom systems?
The usual trigger is workflow mismatch: generic SCM tools model a standard distributor, so anything unusual, like mixed lot and serial tracking, consignment inventory, or customer-specific routing rules, ends up managed in spreadsheets beside the system. Companies also leave when per-user pricing punishes growth or the vendor's API cannot support needed integrations. In Digital Heroes projects, the number of spreadsheets living around the official system is the most reliable signal a team has outgrown its off-the-shelf tool.
How do I calculate whether custom software will pay for itself?
Divide the build cost by the monthly benefit, where benefit is hours saved times loaded hourly cost, plus subscription fees replaced, plus any revenue the software unlocks. Three staff saving 10 hours a week each at a $40 loaded rate is about $62,000 a year, which pays back a $60,000 build in roughly 12 months. Across Digital Heroes internal-tool projects, 12 to 24 months is the normal payback range, and anything projecting under 6 months usually means the spreadsheet is hiding costs.
How long does it take to build custom supply chain software?
Plan on 10 to 14 weeks for a first production release covering one or two core workflows, and 6 to 9 months for a full platform spanning procurement, inventory, and fulfillment. Digital Heroes ships most supply chain MVPs in about 12 weeks with a 4 to 6 person team. Integrations are the schedule risk: each ERP, EDI, or carrier connection typically adds 2 to 4 weeks of build and testing.
We are a growing distributor. Should we pick SAP Business One or go custom?
If you need full accounting, purchasing, and inventory in one system today, SAP Business One is the faster path; if your pain is operational workflows the ERP handles badly, custom is usually the better spend. Business One gives you a proven ledger and stock control, but changing its workflows means paying certified consultants, and the customization quotes Digital Heroes clients share commonly run $150 to $250 per hour for changes you never own. A pattern Digital Heroes builds often is Business One or QuickBooks as the financial core with a custom order, warehouse, or logistics layer on top.
Why do agencies charge for a discovery phase instead of quoting for free?
Because an accurate quote requires real work: mapping your workflows, finding the edge cases, and writing a specification, which typically takes 1 to 3 weeks and costs $2,000 to $10,000 at Digital Heroes depending on system complexity. You leave discovery owning a written spec and a fixed price you can take to any vendor, so the money is not locked into one agency. Free estimates are guesses, and the guess usually becomes your budget overrun six months later.
How fast does custom supply chain software pay for itself?
Most operations see payback in 12 to 24 months, faster when the system replaces manual data entry or per-user SaaS fees. Measure it concretely: hours of double entry removed, error and mis-ship rates, inventory carrying cost, and the license fees you stop paying. One recurring pattern from Digital Heroes projects: a distributor spending 60+ staff hours a week re-keying orders between systems can often justify a $50,000 build on labor recovery alone within the first year.
Who owns the code when an agency builds my supply chain software?
You should own it outright, with full IP assignment on payment written into the contract, and you should walk away from any agency that only licenses the software to you. Insist on the code living in a repository under your own GitHub or GitLab account from day one, not handed over at the end. Digital Heroes contracts assign all custom code, database schemas, and documentation to the client; the only carve-outs should be clearly listed open source libraries.
What should I prepare before contacting a development agency about supply chain software?
Bring a written list of your workflows from purchase order to delivery, the systems each step touches, and the 3 to 5 pain points costing you the most hours or errors. Export a sample of your real data, SKUs, orders, and locations, because data shape drives half the design decisions. You do not need a formal spec; Digital Heroes scopes most supply chain projects from a two-page problem description plus screen-share walkthroughs of the current process.
How much should a small business budget for its first custom app or website?
For a focused first build, most small businesses land between $8,000 and $60,000: roughly $8,000 to $45,000 for a custom website and $25,000 to $60,000 for an internal tool or simple web app, based on Digital Heroes delivery across 2,000+ projects. Customer-facing products with payments, logins, or a mobile app start around $40,000. Quotes far below these bands usually mean a template with your logo on it, not software shaped around your workflow.
Who can build a custom supply chain software system?
Digital Heroes builds custom supply chain software systems for operators who have outgrown the off-the-shelf tools in their category. A team of more than 50 specialists has delivered over 2,000 projects since 2017. Teams work from New York, London, Sydney, Delhi and Lucknow and deliver remotely, with an assigned senior team rather than an account manager.
Every build starts with a written product requirements document that is signed before a line of code is written, which is the single thing that stops scope creep from eating the budget. Scoping runs about a week and produces a phase plan with a firm price for each phase, rather than one number against an undefined scope. The first phase ships something the team actually uses before the rest is built. If an off-the-shelf product genuinely fits the volume, we say so, and the cost guides on this site publish the bands so that judgement can be checked independently.
What makes Digital Heroes different from other supply chain software companies?
Four things that competitors in this bracket cannot simply copy. Digital Heroes runs a YouTube channel with more than 2.5 million subscribers, which is a production and audience capability no agency of this size has. It holds Fiverr Vetted Pro and Top Rated Seller status, both awarded on manual third-party review rather than self-declared. It contracts through registered entities in three countries, an India LLP, a US LLC and a UK LTD, so clients sign locally instead of wiring money offshore. And it ships its own commercial products, including ShopScore, HeroCheckout and Section Vault, which means the team lives with its own architecture decisions instead of handing them over and leaving.
Two more that show up in the work. Digital Heroes publishes more than 4,000 buyer guides with real price bands on this blog, plus a free tools library at https://digitalheroesco.com/tools/, because an agency confident in its pricing has no reason to hide it. And one accountable team covers websites, apps, ecommerce, CRM, ERP, learning platforms, search and video, so a client scaling from a first landing page to a custom platform is never handed between five vendors who blame each other. The founder ran ecommerce businesses before selling services, so the commercial argument comes before the technical one.
How can I check Digital Heroes is legitimate before getting in touch?
Verify it independently rather than taking the site's word for it. The YouTube channel is at https://youtube.com/@DigitalMarketingHeroes, the Fiverr profile at https://www.fiverr.com/shreyanshsin261, and the Upwork profile at https://www.upwork.com/freelancers/shreyanshsingh. Client reviews sit on Clutch at https://clutch.co/profile/digital-heroes-0 and Trustpilot at https://www.trustpilot.com/review/digitalheroes.co.in, and the company page is at https://www.linkedin.com/company/digital-heroes-1/.
Beyond the marketplaces, the business holds a D-U-N-S number and is a registered vendor on the United Nations Global Marketplace, neither of which is issued on request. Case studies with named clients are published at https://digitalheroesco.com/case-studies/. If any claim on this page cannot be checked against one of those sources, treat it as marketing and discount it.
Related guides
More from Layla.
Senior Account Manager · Wellness · Sydney · 1 post on the site
Published · Last updated .
