Getting oriented, quickly

• Start with a quick snapshot, how many producing wells are in your portfolio today and how are they distributed by basin? Options: 1-50, 51-200, 201-500, 501-1,000, More than 1,000
• Breakdown your active lift types across those wells, by approximate count Options: Rod pump (sucker rod), ESP, Gas lift, Plunger lift, Other
• Which of the following best describes how your field coverage is organized today Options: Per-well pumper assignments, Per-field foreman with rotating pumpers, Contract crews only, Combination of in-house and contractors
• Estimate the average wells per pumper or foreman on a typical shift Options: 1-10, 11-25, 26-50, 51-100, More than 100
• Tell me about the most recent unplanned downtime incident, where it began, and who first noticed it
• Confirm whether you can provide a complete well inventory and at least 60 days of uptime and production history within 14 days, if not explain the blocker Options: Yes, available within 14 days, Available but requires more than 14 days, Not available electronically, requires manual collection, Not available

Where small problems turn into meaningful production loss

• If a single monitoring failure allowed 24 hours of downtime across a cluster, what would that cost in lost barrels and management attention this month?
• How often do you detect issues through remote surveillance versus receiving field-initiated reports Options: Mostly remote surveillance, Roughly half and half, Mostly field-initiated, We have little remote surveillance
• When a well falls below expected production, who is alerted first and what happens in the first four hours
• Walk me through the last time a small pump problem escalated into a workover, what signs were missed and why
• Name the top three recurring equipment or operational causes of deferred production in your portfolio
• Would the presence of an unresolved SCADA gap that prevents remote alarms stop you from running a meaningful pilot Options: Yes, it would stop the pilot, No, we can work around it, Only if the gap affects more than X% of pilot wells

Who keeps the wells running and how they actually work

• Who on your operations team has final authority to order a field crew to bypass production or schedule a workover
• Describe the training and certification levels for your pumpers and foremen, and any important gaps Options: Formal certification program, On the job training only, Mixed levels across teams, Contractor-dependent
• List the typical responsibilities you assign to a pumper versus a field technician during an abnormal condition
• When was the last time you adjusted staffing ratios because of a production spike or decline Options: Within 3 months, 3-12 months, Over 12 months, Never
• Do you have a documented escalation path from remote alarm to field dispatch that we can review during pilot planning Options: Yes, documented and available, Yes, documented but needs updating, No, informal process, No process exists
• Confirm whether a named field foreman or pumper can be assigned to the pilot wells for the trial period, if not what prevents that Options: Yes, dedicated assignment possible, Partial availability only, No, cannot dedicate staff

Designing a pilot that leaves no excuse

• Assuming the pilot runs 60 to 90 days, which single KPI would make you sign a multi-year agreement that week Options: Uptime improvement percentage, Average response time reduction, Net barrels recovered, Chemical cost reduction
• Outline the minimum well set characteristics you need for a meaningful pilot, such as lift type mix and baseline uptime
• How many wells do you want in the pilot and why that count versus a smaller or larger set Options: 10-20, 21-50, 51-100, Customized sample
• Identify the monitoring integrations and reporting feeds that are essential during the pilot Options: SCADA real-time telemetry, Production accounting export, Chemical dosing reports, Field dispatch logs, Other
• Estimate the acceptance thresholds you expect for uptime improvement, response time reduction, and chemical usage before you consider the pilot successful
• If the pilot fails to meet your stated threshold, who would make the call on whether to run an adjusted second pilot versus stopping the project Options: Production VP, Operations Director, Asset Manager, Finance

Known risks and fail points, tell me the hard truth

• Name the single regulatory, lease, or access constraint that would kill the pilot timeline if unresolved
• Identify any vendor or supplier agreement clauses that could block crew dispatch or limit which chemicals we may use during the pilot
• Could unresolved SCADA or production accounting integration gaps delay go-live, and who within your organization owns those endpoints
• Typically how long does your internal approval and safety review process take for new field procedures Options: Less than 2 weeks, 2-4 weeks, 4-8 weeks, More than 8 weeks
• Imagine a team member arguing the pilot is not realistic, what would they point to as proof

Alternatives on the table

• Describe the incumbent providers or internal groups you would default to if you kept the current approach and why
• Select which of these options are still under active consideration Options: Stick with incumbent, Build internal ops capability, Use multiple local contractors, Do nothing for now
• Under what circumstances would your team choose to keep the current provider rather than change to an outside partner
• Has anyone internally proposed building this capability in-house and if so what headcount or budget ask was suggested Options: Yes, headcount suggested, Yes, capital equipment suggested, No in-house proposal, Planning stage only
• Tell us whether a lower price from your incumbent would cause you to stop the procurement process and what additional evidence you would need to change vendors

Are you technically ready to connect and run the pilot

• List the systems and APIs that must be accessible for monitoring and accounting integration and name the technical owner for each
• Is there an existing API or data feed for SCADA and daily production that we can subscribe to, or will hardware installation be required Options: API available and documented, API exists but undocumented, Hardware installation required, No clear data feed
• Do you have a preferred endpoint authentication method and can you name the current credential owner Options: Bearer token, Basic auth, VPN/Private link, Other
• Rate how clean and time-aligned your historical production and chemical usage data are on a scale of 1 to 5 Options: 1 - Very poor, 2 - Poor, 3 - Fair, 4 - Good, 5 - Excellent
• Where are the biggest physical access constraints for sending field crews, such as gated pads, horse leases, or seasonal roads
• Identify the person in your security or legal teams who must review data sharing agreements and how long that review usually takes
• Can your team grant API access and credentials for the pilot within 30 days Options: Yes, Yes with caveats, No

If the pilot proves the case, what happens next

• Assuming the pilot hits the agreed metrics, which internal approvals are required and what is your target sign date
• Give an expected approval window for finance to sign off on an ongoing per-well price if the pilot numbers hold Options: Immediate (within 1 week), 2-4 weeks, 1-3 months, Longer than 3 months
• Provide the roles or names of the final signatories and any procurement constraints that would change the commercial terms
• What single unresolved risk would make you delay a deployment even if the pilot succeeds
• Select which post-pilot milestones must be met before we begin phased scaling Options: Data integration validated, Field staffing confirmed, Commercial terms signed, Safety and compliance checks complete
• Please propose a preferred follow-up planning session date if the pilot meets acceptance on day 90 Options: Within 1 week, Within 2 weeks, Within 1 month, Later than 1 month

• Operations Walkthrough, Solution Experience

• Confirm the current state and its cost
• You confirm that the demonstrated field plus remote workflow closes the surveillance gaps you described and shortens the path to resolving well events.
• Deliver a tailored pilot operations plan with staffing roster, monitoring thresholds, shift windows, and escalation paths within five business days.
• Provide the list of pilot wells with current uptime baselines, lift types, access permissions, and any known chronic issues.
• Walk through the field team workflow in your context
• You confirm the reporting format and cadence provide the data your production and finance teams need to evaluate pilot results.
• Walk through the remote surveillance and alerting scenario
• You agree on the pilot well set, the baseline metrics required, and the acceptance criteria that will demonstrate value at 60 to 90 days.
• Confirm target acceptance criteria for uptime improvement, average response time, and reporting quality for the pilot evaluation.
• Review reporting and escalation handoffs
• Validate that this matches your needs
• Agree next steps and pilot deliverables

• Operations Walkthrough, Solution Experience
• Operations Walkthrough Deck
• Operations Walkthrough Brief

• meeting
• slides
• document

• Operate 60-90 Day Pilot on 20-50 Wells
• Deploy Production Foremen and Pumpers
• Deploy Remote Monitoring Platform to Wells
• Install and Calibrate Wellsite Monitoring Hardware
• 24/7 Remote Production Surveillance and Alerting
• Daily Production Reporting and Data Delivery
• Rod Pump Operations and Optimization
• ESP Monitoring and Performance Optimization
• Gas Lift Operations and Optimization
• Plunger Lift Service and Optimization
• Chemical Treatment Program Implementation
• Flowback Operations and Well Cleanup
• Field Troubleshooting to Prevent Workovers
• Integrate Monitoring with SCADA and Production Accounting
• Monthly Production Review and Optimization Recommendations

Operate 60-90 Day Pilot on 20-50 Wells

• Select the pilot well count you want to include Options: 20-25, 26-35, 36-50
• Which specific well IDs, leases, or asset names should be in the pilot (list well IDs preferred)
• Provide the target pilot duration in days Options: 60, 75, 90
• Specify the single primary KPI you will use to judge pilot success Options: Uptime % (absolute increase), Mean time to respond (hours), Daily production bbls/day increase, Chemical cost reduction %
• Identify any wells to exclude from the pilot and why (for example: active workovers, H2S, unique contracts)
• What acceptance criteria will confirm pilot success across the selected wells (give measurable thresholds, e.g., uptime +X percentage points, max response time < Y hours, chemical cost reduction >= Z%)

Deploy Production Foremen and Pumpers

• Describe the staffing model you prefer for the pilot (dedicated foreman per field, shared foreman, pumper schedule) Options: Dedicated foreman per field, Shared foreman across multiple fields, Daily pumper rounds with on-call foreman, Custom (describe)
• How many field personnel do you expect us to deploy per X wells (enter ratio or absolute counts)
• Specify typical field shift windows or access windows for your leases (start/end times or daylight-only) Options: Daylight only, 8-hour shift windows, 12-hour shift windows, Flexible/on-call
• List required certifications, site-specific safety requirements, or permit items your field crews must hold (for example: HSE orientation, H2S training, confined space)
• Confirm who will provide PPE and site-specific equipment (you provide, we provide, mixed) Options: You provide, We provide, Shared/Specify details
• Specify the expected on-site response SLA for a pump-off or critical equipment failure during the pilot (hours to arrive on location) Options: <4 hours, 4-8 hours, 8-24 hours, Next business day

Deploy Remote Monitoring Platform to Wells

• Which telemetry variables do you want monitored for each well (select all that apply) Options: Wellhead pressure, Casing pressure, Tubing pressure, Pump motor current, Polish rod position, Fluid level / tank level, Choke position, Other
• Select your preferred telemetry refresh rate for operational alerts Options: 30 seconds, 1 minute, 5 minutes, 15 minutes
• Indicate whether you require remote configuration access to device endpoints or view-only dashboards Options: Remote configuration access, View-only dashboards, Both depending on role
• Describe any existing telemetry platforms or tags we must map from (for example: SCADA tag list, RTU export CSV, MQTT topic)
• Are there wells with limited cellular coverage or that require satellite telemetry Options: Yes - specify wells, No
• Specify any regional data residency or retention constraints for telemetry data during the pilot Options: 30 days, 90 days, 1 year, Custom

Install and Calibrate Wellsite Monitoring Hardware

• Which sensor/hardware mounting types will be used at your sites (surface flowline, wellhead clamp, tank level float, submersible) Options: Wellhead clamp sensors, Flowline meters, Tank level floats, Submersible level sensors, Other
• Specify power source at each pilot well (solar + battery, mains, generator) and any wells with constrained power Options: Solar + battery, Mains power, Diesel generator, No reliable power (requires site visit)
• Which communications transport should we plan for if coverage varies by well (cellular, private radio, satellite, ethernet) Options: Cellular, Private radio, Satellite, Ethernet/leased line
• Describe the calibration checks you require for pressure, current, and level sensors (for example: span check within X%, compare to field gauge)
• What acceptance evidence will validate hardware is installed and calibrated (for example: continuous streaming for 72 hours, sensor accuracy within X% vs referenced gauge)
• List any site access constraints or permit requirements for installing hardware at the listed wells

24/7 Remote Production Surveillance and Alerting

• Select the severity tiers and corresponding on-call response for alerts Options: Critical - immediate on-call, High - respond within 4 hours, Medium - next shift, Low - next business day
• Which alerting channels should be used for each tier (SMS, email, phone call, platform notification) Options: SMS, Email, Phone call, Platform notification, Integration to your ticketing system
• Specify the operational logic to generate an automatic site dispatch (for example: pump current > X for Y minutes, sudden pressure drop > Z psi)
• Do you require 24/7 human monitoring with night-shift analysts or automated-first with escalation to on-call Options: 24/7 human monitoring, Automated-first with on-call escalation, Hybrid
• Provide the escalation contact list and preferred escalation order for field incidents during the pilot
• Are simulated incident drills or alarm replay sessions required before go-live for the pilot Options: Yes - schedule drill, No

Daily Production Reporting and Data Delivery

• Select the daily report delivery format you require Options: CSV export, PDF summary, API push (JSON), Dashboard link only
• Which fields must appear in the daily report for each well (select all that apply) Options: Uptime %, Daily production (bbls), Pump runtime hours, Chemical gallons used, Alerts triggered, Open work orders
• Indicate the recipient list for daily reports and whether distribution should be automated Options: Automated to list, Manual send, API only
• What data validation rules must be applied before report delivery (for example: no negative volumes, continuity checks vs previous day)
• Select the acceptable latency for daily production data to appear in the delivered report Options: <1 hour, <4 hours, Same business day, Next day
• What acceptance evidence will confirm reporting quality for the pilot (examples: data accuracy > X%, automated delivery success rate > Y%)

Rod Pump Operations and Optimization

• Which rod pump diagnostics do you want monitored (pump card/dynamometer, polish rod load, pump-off detection, tubing fillage) Options: Dynamometer/pump card, Polish rod load, Pump-off detection, Tubing fillage, Other
• Specify target pump-off cutoff settings or rules you prefer during pilot optimization
• How frequently should rod pump rod-surface inspections be scheduled during the pilot Options: Daily, Weekly, Biweekly, As-needed based on alerts
• List any existing rod pump performance baselines or dynamometer files you can provide to inform optimization
• Do you require chemical injection coordination as part of rod pump optimization (for foamers, paraffin control, scale inhibitors) Options: Yes, No
• Provide the escalation rule for suspected mechanical failure discovered via rod card analysis (for example: immediate on-site inspection if polished rod load crosses X)

ESP Monitoring and Performance Optimization

• Which ESP parameters must be captured and trended (motor current, frequency, pump intake pressure, motor temperature) Options: Motor current, Frequency, Pump intake pressure, Motor temperature, Vibration
• Specify the alarm thresholds for ESP conditions that require immediate action
• Do you have existing start-up and run procedures for ESPs we must follow or adapt Options: Yes - will provide, No - need standard procedure
• Estimate the acceptable margin for motor current fluctuation before we trigger investigation Options: ±5%, ±10%, ±20%, Custom
• List spare parts or consumables you expect us to hold on-site for ESP troubleshooting during the pilot
• Indicate whether surface variable frequency drive (VFD) data integration is required for optimization Options: Yes, No

Gas Lift Operations and Optimization

• Specify which gas lift wells and line pressures will be part of the pilot
• Which gas injection control variables should be monitored and adjusted (injection pressure, valve position, flow), Options: Injection pressure, Valve position, Gas flow rate
• Describe the gas allocation limitations or LP/HP source constraints we must operate within
• How frequently should we review gas lift schedules and perform valve tuning during the pilot Options: Daily, Weekly, Biweekly, As-needed
• Are you tracking gas usage to a specific metric for acceptance (for example: gas bcf reduction per bbl of production) Options: Yes - specify metric, No
• Provide the safety or regulatory constraints for changing gas lift setpoints at your sites

Plunger Lift Service and Optimization

• Which wells use plunger lift and what plunger detection method is installed (magnetic sensor, acoustic, timer) Options: Magnetic sensor, Acoustic sensor, Timer-based, No sensor / manual
• Specify desired plunger cycle targets or production objectives for optimization
• How should we handle wells with frequent plunger hang-ups during the pilot Options: Schedule on-site plunger retrieval, Attempt remote restart sequences, Both depending on severity
• Do you require installation of plunger-specific telemetry (plunger position, rodless sensor) as part of the pilot Options: Yes, No
• List any plunger spare parts or vendor restrictions we must observe
• Indicate the acceptance threshold for plunger lift improvement (for example: cycles per day increase or downtime reduction)

• desired_state
• current_state
• stakeholders
• gaps
• success_criteria
• decision_readiness
• desired_state
• decision_readiness
• current_state
• success_criteria
• gaps
• stakeholders
• desired_state
• success_criteria
• stakeholders
• gaps
• current_state
• decision_readiness
• decision_readiness
• decision_readiness
• decision_readiness
• decision_readiness

• Master Services Agreement (MSA)
• Statement of Work (SOW)
• Service Level Agreement (SLA)
• Pricing & Order Form
• Pilot Acceptance Certificate
• Data Sharing & Integration Addendum
• Roles & Responsibilities Matrix
• Onboarding & Transition Plan
• Change Order Agreement
• Termination & Exit Agreement
• Confidentiality & IP License Addendum
• Payment Schedule Agreement
• Safety & Regulatory Compliance Addendum

• Go-live Health Check
• First Measurement Review
• Post-Acceptance Realization Review
• Quarterly Operational Review

• Adjust monitoring thresholds, escalation rules, or staffing windows where metrics indicate a sustained deviation from targets.
• Present realized performance versus pilot baselines and acceptance targets
• Confirm that realized uptime and response time improvements meet or are on a credible path to the Pilot Performance Evaluation targets.
• Agree a prioritized optimization backlog with expected metric impact and target implementation windows.
• Ensure all remaining issues and enhancement requests have documented resolution plans and target dates.
• Publish the prioritized optimization backlog with expected metric impact, acceptance criteria, and target delivery dates.
• Deliver a final performance summary report that references Pilot Performance Evaluation targets and pilot baselines.
• Record resolution plans and timelines for each open issue and enhancement request in the shared issue channel.
• Quarterly performance review
• Maintain or improve uptime percentage and average response time quarter-over-quarter relative to pilot baselines.
• Ensure optimizations are producing measurable improvements and that at least the top priority enhancements have delivery windows.
• Keep the open issue and enhancement queue actively prioritized and on a documented resolution path.
• Provide a quarter-over-quarter performance dashboard export showing uptime and response time trends and comparison to pilot baselines.
• Update enhancement request statuses with expected delivery windows and publish the revised prioritization.
• Re-confirm success criteria and ownership
• Critical integrations and access paths validated and passing smoke tests.
• Open go-live blockers and incidents identified with a remediation plan and target dates.
• Primary user and field crew onboarding status confirmed and gaps scheduled for closure.
• Publish a remediation plan listing each open blocker, acceptance test, and target resolution date.
• Deliver a snapshot of initial platform usage and field adoption metrics for async review.
• Provide an integration error log with proposed fixes and timelines for each issue.
• Present first measurement data versus baselines
• Determine whether uptime percentage and average response time trends are moving toward the Pilot Performance Evaluation targets.
• Agree root causes for any shortfalls and a prioritized corrective action list with delivery dates.
• Confirm the data window and schedule for the acceptance checkpoint documented in Pilot Performance Evaluation.
• Publish the measurement report with raw data extracts, calculation methods, and comparisons to Pilot Performance Evaluation targets.
• Document root-cause analyses for each failing metric and list specific remediation tasks with target dates.
• Update monitoring thresholds or escalation rules based on agreed corrective actions and publish the changes.
• Review and prioritize optimization recommendations
• Diagnose gaps and root causes
• Deployment and integration validation
• Review implemented optimizations and measured impact
• Open issues, escalation status, and blocker burn-down
• Early adoption and usage signals
• Open issues and enhancement request triage
• Agree corrective actions and timelines
• Enhancement request pipeline and prioritization
• Incidents, blockers, and defect triage
• Confirm next checkpoint toward acceptance
• Confirm operational handover and continuing monitoring cadence
• Operational adjustments and staffing notes
• Agree immediate remediation actions