Yes. iPOC runs within the Ignition Gateway and Perspective environment. An existing Ignition deployment is required. If you are not yet running Ignition, the evaluation conversation typically begins there.

iPOC supports multiple POC manufacturers including Lufkin, Weatherford, SMARTEN, Unico, and GE, among others. Contact us or view the full supported controller list for current availability. Support is validated per controller family and firmware version.

iPOC collects data through Modbus TCP, Modbus RTU, and OPC UA. Either directly or through existing polling engines such as Autosol, Kepware, or TOP Server. The collection method depends on your field communications infrastructure and controller type.

Yes. iPOC is designed to leverage existing polling infrastructure where appropriate. This is one of the primary reasons existing Ignition environments can integrate iPOC without requiring field re-instrumentation.

Remote control actions include Start, Stop, Idle, Alarm Reset, Clock Set, and supported controller configuration. Available actions depend on the controller type and communication method. All actions are subject to role-based permissions and are fully audited.

Yes. iPOC captures surface and downhole dynamometer cards and displays them alongside current and historical operating data. Card availability depends on the controller type and whether the controller supports downhole card calculation.

Controller alarms are centralized through the Ignition alarm architecture. Notifications can be routed through supported channels including SMS, voice, email, and collaboration platforms using your existing Ignition alarm configuration.

iPOC uses the Ignition authentication and role-based access control system. User management, permissions, and audit logging are handled at the Ignition level. No separate user directory or access control system is required.

Yes. Artificial lift data can be made available to other operational and enterprise systems through OPC UA, MQTT, SQL, REST APIs, and other supported interfaces.

iPOC can be deployed alongside or in replacement of an existing artificial lift monitoring system. Because it reuses existing field hardware, communications, and the Ignition environment, migration can be phased rather than requiring a full cutover. The specifics depend on your current environment.

A 45-day trial is available. It typically follows technical discovery and an initial demonstration, when both parties have confirmed that iPOC is architecturally appropriate for the environment. Contact us to start that conversation.