Integration patterns written up with the flow, what was tested and what is out of scope. Each article says whether it ran against real systems, mocks or a simulated service, and links to screenshots where a run was captured. Customer names are not published.
Reference integration: maintenance to ERP
How OpexFlow carries goods issues and work order confirmations from OpexMX to SAP so that each one is either confirmed by SAP or visible as an open item: accepted once, tallied on both sides, checked every night, and parked for a person when SAP refuses it.
Reference flow, tested against a simulated SAP middleware.
Read the case studyReference integration: ERP ledger to database
How a scheduled flow copies the Epicor Kinetic general ledger journal detail into Postgres without silent loss: one request per fiscal year, period and book, a count check that refuses a short partition, an upsert that makes a re-run harmless, retries on 429 and 503, dead letters for 400 and 401, an alert when a pull fails, and a nightly comparison of Epicor and Postgres totals.
Reference flow, run against responses recorded from Epicor’s demo company (EPIC06) and replayed by a mock server. No live Epicor server was called.
Read the case studyReference integration: MES, CMMS and ERP on one event backbone
How OpexFlow sits on a NATS JetStream backbone between OpexMES, OpexMX and an ERP: every message is checked against its contract, accepted once, kept in Postgres and passed on, and a message that breaks the contract or arrives twice never reaches a system.
Reference flows, run end to end against NATS JetStream 2.10, ClickHouse and Postgres in Docker. OpexMES, OpexMX and the ERP are simulated with contract-valid messages.
Read the case studyReference integration: machine data to a time-series store
How OpexFlow lands high-volume machine telemetry from JetStream in ClickHouse in batches, what the ClickHouse sink does while the database is down, and the one case where rows can still be lost.
Reference flow, run against NATS JetStream 2.10 and ClickHouse 24.8 in Docker with simulated machines publishing telemetry.v1 records. One limit, a restart during an outage, was measured and is stated below.
Read the case studyReference integration: event history and work order record
How OpexFlow turns work order and alarm events from JetStream into rows people can query in Postgres: one row per event, one row per work order, safe against a resend, a redelivery and an arrival in the wrong order.
Reference flows, run against NATS JetStream 2.10 and Postgres 16 in Docker. The producers are simulated with contract-valid messages.
Read the case studyReference integration: plant edge to cloud
How a plant’s OpexFlow node sends machine records to a hosted OpexFlow without opening an inbound port, and what happens to those records when the WAN or the hosted side is down: they wait on disk, arrive in order, are stored once, and a wrong secret never loses one.
Reference deployment in the repository, exercised end to end over TCP in the integration tests.
Read the case studyReference integration: finance approval
How a flow holds a large journal for a named approver before it is posted to an ERP, what happens to a rejection or a timeout, and how the switch from read-only to live posting is signed off by a second person in a protected environment.
Reference flow, shipped as an example in the editor with a bundled mock ERP. Approval and go-live behaviour are covered by the repository’s tests.
Read the case studyReference integration: partner file to database
How a flow picks up a partner’s price file from an SFTP server, checks the server’s identity, imports each row once even when the file is retried, adds names from a code list, upserts into Postgres, and parks a row it cannot match for correction.
Reference flow, shipped as an example in the editor with a local mock SFTP directory. Postgres has no mock.
Read the case studyIndonesian theme park and resort group
Two flows for a theme park and resort group: buying an annual pass, with an undo for every step, and posting daily sales to NetSuite with settlement matching and a nightly exception report. One flow document, three environments, and stand-ins for every system that has no sandbox yet.
Proof of concept. Every external system is a mock. Not in production.
Read the case studyIndonesian food manufacturer
A production order should set the right message, batch and dates on every coding printer of a line, and refuse a format a printer does not know. The flow below targets production lines, not individual printers, so adding a printer needs no flow edit. It covers 43 printers across five models.
Flow and printer configuration prepared for commissioning. No line results are reported here.
Read the case studyRun one binary, connect a PLC, a CNC or a webhook, and watch the records arrive in the editor.
Sizing questions or an air-gapped install? Email marketing@opexcg.com or read the quick start.