Schedulings API

Hi all!

We’d like to be able to create/read/update scheduling through ComboCurve’s API.

Currently we use the schedule dates exposed in the wells endpoints (e.g., drillStartDate), but that doesn’t work well if multiple schedules exist in ComboCurve (e.g., running schedule sensitivities and switching between them). For that reason some people have requested us to work with ComboCurve schedulings directly instead, so we were wondering if endpoints could be added to support this.

For now we plan to work around this limitation by creating templates in a TSV format that can be pasted directly into the schedule for updates, but it’s inconvenient because these schedules are updated frequently. Long term we’d want the workflow to be much smoother and not have any manual copy/paste steps.

Thank you,
Josh

@josh Thank you for the suggestion and the limitations you are encountering. I will pass this request on to our Product Manager for consideration.

1 Like

Sounds great, thank you @Danny_Cooney! I’d also be happy to elaborate more about our use case if that would be helpful.

@Danny_Cooney This has come up a few more times lately for companies who create drill schedules outside of ComboCurve and want to import multiple schedules. e.g., creating different drill schedules outside of ComboCurve, then importing to ComboCurve for full economic comparisons.

Is there a chance this will be included in a future release, or should we plan to work around this? We could automate the UI programmatically to perform the import without an API, but we’d prefer not to do that.

@josh,
Let me introduce you to @Andrew_Towers (API Product Manager). Reach out to him to discuss your insights/needs/ and ideas for your suggested improvements.

1 Like

@josh Glad to connect! Would you like to hop into a discovery call in the next few weeks? I’d love to learn more about your workflows and pain points and see how we can support your team. Let me know, and I’ll find a time in our calendars to sync!

1 Like

Absolutely, I’d be happy to talk more about my use case. You can book a time in my calendar (Calendly - Josh Groves) or email me at josh@pod2.co to find a time.

Fantastic! I will schedule a call today. Feel free to invite any of your teammates. @Danny_Cooney and @HGantz will join, too!

1 Like

@Danny_Cooney @HGantz Some more people have been asking about this lately, is there a chance it might be implemented this over the next few months? We’re working around it by copy/pasting schedules to import into ComboCurve, but makes quick iterations difficult

Sorry to keep bumping this but people are still requesting this. I’m not sure how other companies with multiple schedules work around this today, but these are the workarounds I’ve considered:

  • requiring schedules to move through the Excel import (to import into the scheduling module in bulk)
  • asking people to copy wells into multiple projects (one project per schedule scenario) to be able to integrate with well headers instead of the scheduling module
  • programmatically driving the ComboCurve UI itself (perform the Excel import automatically without user interaction)

All of these workarounds don’t seem great though. Is there anything else I could do in the meantime?

Josh,
Contact your Customer Support Rep. They should be able to support you in this request.

Thanks @Danny_Cooney. I don’t have a Customer Support Rep unfortunately, I’m a software vendor (Pod2) that uses ComboCurve’s API for integrations on behalf of other companies.

I’ve encouraged several companies to reach out to their ComboCurve reps but this is a bit tricky in practice. Usually they’re not familiar with ComboCurve’s API because they’re indirectly using it through Pod2’s software, and might not feel comfortable speaking to the request.