JPI Solutions

One failed I/O card at an 800 MW power plant took a critical water process offline for up to 18 hours. The real obstacle was a Java-based config page that only one old laptop could still open. Why legacy tooling is an operational risk, and what proactive

"Digital transformation" lands flat in oil and gas, but it is a strategy, not a project. A plain-language definition, why ROI is hard to isolate but easy to see, and a practical roadmap from connecting your first PLC to solving real problems with data.

Our recap of ProveIt! 2026 in Dallas: a bigger conference, a strong people-over-AI theme, standout presentations from Thred, Abelera, and CESMII's I3X, and our team's work getting SM Profiles flowing through the conference UNS.

Automation covers a LOT of ground. When someone is talking about automation they might be talking about that small machine over there on the plant floor, a large facility with thousands of sensors and outputs, a SCADA system with thousands of sites, or a

JPI Solutions is heading to ProveIt! 2026 with a booth. ProveIt! makes vendors prove their solutions against a virtual factory UNS and disclose cost and implementation time. Find us at booth 48 and use code JPI for 25% off.

The Problem In natural gas production and processing facilities, operators routinely lose 5-15 minutes per trip walking between standalone compressor control panels and central plant control systems. During compressor startups, process upsets, or troubles

A quick reference for DLOG block status codes on Telepace SCADAPacks. Codes 10 through 17 are listed with their meaning and fix, from invalid log IDs and low RAM batteries to memory shortfalls that need a cold boot.

Manually copying files to back up a SCADA database risks corruption. ClearSCADA's built-in Backup Object makes safe backups on demand or on a schedule. How to create and configure it, name backups by date and time, and run it from ViewX.

Part two of our PowerShell API series. Load SCADA records from CSV, convert each one to JSON with a Unix timestamp, and POST it to a Swagger API using a bearer token. The full script is included, with a section-by-section breakdown.

Our Swagger API used OAuth 2.0 client credentials, and the bearer token kept expiring. How to request a fresh token from PowerShell 5.1, including the multipart form workaround that took some head bashing to figure out.