add on to TSC (N6q)

Question 1

what we do and don’t do

Answer 1

Maybe it would be helpful for me to speak a bit about what we do and don’t do. For starters, we optimize the efficiency of individual compressors in the fleet. So, the specific operating instructions we generate are around things like pocket settings, valve replacements, horsepower settings to stop wasting fuel gas or push more gas through. What we don’t do is optimize the gathering network. We don’t recommend capital expenditures or expensive major re-configurations. (41 seconds)

We don’t just let our client know when a valve has failed, a rod load has exceeded tolerance or a catastrophic failure has occurred.

Question 2

what we do and don’t do - continued

Answer 2

We don’t recommend capital expenditures or expensive major re-configurations. We don’t just let our client know when a valve has failed, a rod load has exceeded tolerance or a catastrophic failure has occurred. What we do is give predictive warnings on when those sorts of things are most likely to happen based on our algorithms combined with the client’s operating data. We aren’t an invasive device requiring compressor downtime to operate. What we are is software-as-a-service that gives daily prioritized alerts based on where the client can prevent the most monetary loss. (~52 second) I’m not sure I’m being clear. Am I helping at all?

Question 3

predictive maintenance (DQ possibility of need for) - [key f/up Q’s to ask after a couple minutes discussion following initial TSC]

Answer 3

1. How do you know when it’s time to replace a piston ring?

Question 4

prompts for “what we do and don’t do - continued”

Answer 4

• capital (don’t)
• failed (don’t)
• predictive (do)
• invasive (aren’t)
• SaaS (are)
• sure (I’m not)

Question 5

prompts for “what we do and don’t do”

Answer 5

• optimize the efficiency (of *individual*) (do)
• specific operation instructions (so)
• gathering network (don’t)
• capital expenditures (or expensive) (don’t)
• has failed (don’t)