Setpoint Optimization Info

Setpoint optimization is run every 15 minutes by default from the SetpointOptimization row in tblSchedule

Phase shift due to incorrect top of stroke

This should be corrected in the POC by fixing the top of stroke setting, but can be worked around by turning phase shift corrections off in Well Config->Analysis options->Phase Shifted Surface Position

At the well shutdown when the crank arm is at its lowest point and the horsehead is at its highest point. Re adjust the wand and magnet to be lined up and restart the well.

Gathering setpoint data

This means XSPOC does not have all required data to provide recommendations. Wells will need to gather setpoint data for a minimum of zero or maximum of 20 days before recommendations will be given. Comms must be good during this time and cards must be pulling regularly.

If the pump condition is not good we will looking for better cards that we can make recommendations on. Hence gathering data. The statement is a bit generic so as we improve the screen and these statements we will be updating them but that is what is happening here, so there isn’t a problem really.  We do not make recommendations on wells with certain poor pump conditions such as Traveling Valve leak

Required data

Peak Load uses 20 days of data, can use as little as 7 days.

Min Load uses 20 days of data, can use as little as 7 days.

Pump fill Needs no data, just latest Card

Base fill Needs no data, just latest Card

Idle Time Requires scanning of inferred prod and idle time and requires user inputs of min and max idle time threshold and a period of days for the algorithm to run

Poor Communication Resons
The last good scan must be no older than 6 hrs, even with 100% good comms
If that phrase “Poor communications have been identified for this well … ” appears on a setpoint optimization other than Recommend Mode Idle time, then it is due to any of the following:
1. The comms percentage must be higher than 70%.
2. While trying to write to the controller, the comms attempt failed, and this isn’t a type of setpoint optimization that will retry the control action
3. For certain types of Setpoint optimization the controller will be read from, and again if that fails and there is no room for retry this will get applied